Install CA PPM

Before you install , plan the installation and all environment details. Repeat the configuration planning process for the pilot, test, QA, training, and production environments.
ccppmop142
Before you install 
Clarity Project and Portfolio Management (PPM)
, plan the installation and all environment details. Repeat the configuration planning process for the pilot, test, QA, training, and production environments.
: The documentation in this section applies mostly to on-premise customers. Installations and upgrades for SaaS customers are provided with the product. However, SaaS administrators are subject to many of the same options, constraints, and requirements.
 
This diagram shows the steps for a new installation of CA PPM
This diagram shows the steps for a new installation of CA PPM
2
Planning: Review the Installation Prerequisites
  1. Backup your installation directory and database if you want to keep one from a previous installation.
  2. Verify the third-party software that is supported for this release. See 
    Compatibilities
     in the Release Notes (On Premise).
  3. Verify that you have the required license key information to install some third-party software products. See the documentation or readme file on the installation media.
  4. Verify that you have administrator rights for the servers.
  5. Disable any custom database triggers, custom unique restraints, or antivirus scanners that can interfere with the installation scripts.
  6. Spaces in the PATH variable may cause difficulty on a Windows server. You can escape the entries using quotes. Another option is to replace the entries with their short 8.3 file names. For example, to escape the spaces, change the entry ;
    C:\Program Files (x86)\;
     to 
    ;"C:\Program Files (x86)\";
    In this example, the spaces can also be avoided with the short name 
    C:\Progra~2\:
    To determine short file names for a path, see the Microsoft Windows documentation.
  7. Verify you can access the installation media and database images. 
    Clarity Project and Portfolio Management (PPM)
     uses a backup-based database deployment mechanism. Instead of building the database during the installation, a pre-built, fully populated database backup base image is provided on the installation media. The image contains everything that a new installation requires. The installation media contains the following base images:
    • A Microsoft SQL Server base image that is compatible with all supported SQL Server versions.
    • An Oracle base image that is compatible with all supported Oracle versions.
    : Mirroring and replication of the
    Clarity Project and Portfolio Management (PPM)
    database (SQL Server or Oracle) are not supported.
  8. Verify that you do not install a test or development environment on the same server as a production environment.
  9. As a database administrator, follow the Oracle or Microsoft SQL Server documentation to install the database software. Verify that the database software is operational before you configure it for 
    Clarity Project and Portfolio Management (PPM)
    .
  10. Oracle/CABI Requirement
    : The 32-bit Oracle client software is required on the same report server as CA Business Intelligence (CABI). For more information, see the CA Business Intelligence documentation at docops.ca.com.
Planning: Manage Services with CSA
During and after the installation, use CA PPM System Administration (CSA) to stop, start, and monitor the services in the cluster. The Jaspersoft and database servers are unmanaged, a standard practice for most organizations.
Clarity Project and Portfolio Management (PPM)
 is comprised of the server services that run on the application server. By default, all services are 
managed
. A managed service is one that is started, stopped, and monitored from CSA using local beacon services running on each system.
Most of the services can be left unmanaged, if desired. An unmanaged service operates the same as a managed service with one difference: The 
Clarity Project and Portfolio Management (PPM)
 System Administration application cannot control or monitor an unmanaged service. The database server, the reports server, and the application server (in some instances) can be unmanaged.
The 
Clarity Project and Portfolio Management (PPM)
 services include:
  • app: 
    The 
    application service
     handles client requests. You can use one or more 
    app 
    services for each cluster. You can configure multiple instances for each server. The app server is always managed.
  • beacon: 
    The 
    beacon service
     is used to manage a cluster. You can use one beacon service for each server in the cluster.
  • bg: 
    You can use one or more 
    background services
     for each cluster. You can configure multiple instances for each server. You are required to manage bg services.
  • db: 
    You can use one Oracle or Microsoft SQL Server 
    database service
     for each cluster. Databases can be managed or unmanaged.
  • nsa: 
    The 
    system administration service 
    is always managed
    .
     You can use one nsa service for each cluster.
Database: Configure a 
Clarity Project and Portfolio Management (PPM)
 Database with Oracle
Complete the following tasks in the order presented to configure Oracle for use with 
Clarity Project and Portfolio Management (PPM)
.
  1. For extended character handling on an Oracle server, set the NLS language to AL32UTF8.
    1. UNIX
      : Edit the UNIX user profile to add the NLS_LANG variable:
      NLS_LANG=AMERICAN_AMERICA.AL32UTF8EXPORT NLS_LANG
    2. Windows: 
      Start the registry editor:
      1. From the Start menu, select Run, and enter 
        regedit
        .
      2. Go to 
        HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\<
        Oracle Home
        >
         and change the value for key NLS_LANG to:
        AMERICAN_AMERICA.AL32UTF8
  2. Set the required parameters in the following table for your new database:
    Name
    Value
    Character Set
    AL32UTF8
    National Character Set
    UTF8/AL16UTF16
    nls_date_format
    YYYY-MM-DD HH24:MI:SS
    nls_sort
    BINARY
    nls_comp
    BINARY
    query_rewrite_enabled
    true
    Cursor_sharing
    FORCE
  3. Set the following parameter values to optimize performance when running 
    Clarity Project and Portfolio Management (PPM)
     with Oracle 12.1.0.2:
    1. optimizer_adaptive_features=false 
    2. optimizer_inmemory_aware=false 
    3. optimizer_adaptive_reporting_only=true
  4. The following initNIKU.ora file uses Automatic Memory Management (AMM). The following samples are the recommended parameter settings. However, you can adjust the settings according to your environment.
Windows
*.audit_file_dest='C:\apps\oracle\admin\niku\adump' *.audit_trail='db' *.compatible='11.2.0' *.control_files='C:\apps\oracle\oradata\niku\control01.ctl','C:\apps\oracle\oradata\niku\control02.ctl' *.cursor_sharing='FORCE' *.db_block_size=8192 *.db_domain='' *.db_name='niku' *.diagnostic_dest='C:\apps\oracle' *.job_queue_processes=20 *.memory_max_target=16G *.memory_target=12G *.nls_comp='binary' *.nls_date_format='YYYY-MM-DD HH24:MI:SS' *.nls_sort='binary' *.open_cursors=1000 *.processes=1000 *.remote_login_passwordfile='EXCLUSIVE' *.sessions=1000 *.session_cached_cursors=1000 *.sga_max_size=0 *.sort_area_size=0 *.streams_pool_size=512M
Linux (Non-Windows)
*.compatible='11.2.0' *.control_files='/niku/oracle/oradata/niku/control01.ctl','/niku/oracle/oradata/niku/control02.ctl','/niku/oracle/oradata/niku/control03.ctl' *.core_dump_dest='/niku/oracle/admin/niku/cdump' *.cursor_sharing='FORCE' *.db_block_size=8192 *.db_cache_size=16777216 *.db_domain='' *.db_file_multiblock_read_count=16 *.db_name='niku' *.diagnostic_dest='/niku/oracle/admin/niku/udump' *.filesystemio_options='SetAll' *** for non ASM instances. *.job_queue_processes=20 *.memory_max_target=16G *.memory_target=12G *.nls_comp='binary' *.nls_date_format='YYYY-MM-DD HH24:MI:SS' *.nls_sort='binary' *.open_cursors=1000 *.processes=1000 *.remote_login_passwordfile='EXCLUSIVE' *.sessions=1000 *.session_cached_cursors=1000 *.sga_max_size=0 *.sga_target=0 *.sort_area_size=0 *.streams_pool_size=512M *.undo_management='AUTO' *.undo_tablespace='UNDOTBS1' *** The memory target and tablespace sizes can be adjusted depending upon the customer implementation. If customers are using Linux Huge pages, the DBA can disable AMM and use SGA and PGA instead, until Oracle supports AMM and Linux Huge pages.   SQLNET.ora parameters: NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT) SQLNET.INBOUND_CONNECT_TIMEOUT = 0 SQLNET.SEND_TIMEOUT = 600 (Applicable for Oracle 11.2.0.4, Oracle Bug 18841764)
Create the 
Clarity Project and Portfolio Management (PPM)
 Required Oracle Tablespaces (Sample Script)
To create the required tablespaces for 
Clarity Project and Portfolio Management (PPM)
 to work with Oracle, use the following script and adjust the size as appropriate. The Oracle software and database instance must already be created.
The schema in the backup is NIKU, and the tablespaces are shown in the following example:
  • INDX_LARGE
  • INDX_SMALL
  • USERS_LARGE
  • USERS_SMALL
CREATE TABLESPACE "USERS_LARGE" DATAFILE '<ORACLE_BASE>\ORADATA\<SID>\USERS_LARGE.DBF' SIZE 2G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 10G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE "USERS_SMALL" DATAFILE '<ORACLE_BASE>\ORADATA\<SID>\USERS_SMALL.DBF' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 4G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE "INDX_LARGE" DATAFILE '<ORACLE_BASE>\ORADATA\<SID>\INDX_LARGE.DBF' SIZE 2G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 10G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE "INDX_SMALL" DATAFILE '<ORACLE_BASE>\ORADATA\<SID>\INDX_SMALL.DBF' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 4G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
Example: Creating Tablespaces
ORACLE_BASE= c:\apps\oracle SID=NIKU CREATE TABLESPACE "USERS_LARGE" DATAFILE 'C:\APPS\ORACLE\ORADATA\NIKU\USERS_LARGE.DBF' SIZE 2G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 10G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE "USERS_SMALL" DATAFILE 'C:\APPS\ORACLE\ORADATA\NIKU\USERS_SMALL.DBF' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 4G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE "INDX_LARGE" DATAFILE 'C:\APPS\ORACLE\ORADATA\NIKU\INDX_LARGE.DBF' SIZE 2G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 10G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE "INDX_SMALL" DATAFILE 'C:\APPS\ORACLE\ORADATA\NIKU\INDX_SMALL.DBF' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE 4G LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
Set the 
Clarity Project and Portfolio Management (PPM)
 Database Required Oracle User Privileges
The following sample script shows the required privileges for a 
Clarity Project and Portfolio Management (PPM)
 schema user. (DEFAULT TABLESPACE USERS_LARGE):
CREATE USER CLARITY IDENTIFIED BY CLARITY DEFAULT TABLESPACE USERS_LARGE TEMPORARY TABLESPACE TEMP PROFILE DEFAULT; GRANT CREATE SESSION TO CLARITY; GRANT ALTER SESSION TO CLARITY; GRANT CREATE TABLE TO CLARITY; GRANT CREATE TRIGGER TO CLARITY; GRANT CREATE VIEW TO CLARITY; GRANT QUERY REWRITE TO CLARITY; GRANT CREATE PROCEDURE TO CLARITY; GRANT UNLIMITED TABLESPACE TO CLARITY; GRANT CREATE JOB TO CLARITY; GRANT CONNECT TO CLARITY; GRANT RESOURCE TO CLARITY;
Configure the Oracle Net Service Name
On Windows, the Database Configuration Assistant automatically creates the CA PPM service. If the service name is sufficient, you can skip this step.
  1. Start the Oracle Net Configuration Assistant:
    UNIX
    <oracle home>/bin/netca &
    Windows
    Start Menu, Programs, Oracle, Oracle Home, Configuration and Migration Tools, Net Configuration Assistant.
  2. To create the TNS entry, use the information in the following table:
Oracle Net Configuration Assistant Screen
Option
Value
Welcome
Local Net Service Name Configuration
Selected
Net Service Name Configuration
Service Name
Enter the service name provided during the Oracle database installation.
Default:
niku
TCP/IP
Host Name
<database server name>
Import the 
Clarity Project and Portfolio Management (PPM)
 Oracle Database Backup Image
The Oracle database backup that 
Clarity Project and Portfolio Management (PPM)
 provides contains the complete schema that is needed for a new installation. The schema in the backup is NIKU, and the tablespaces are:
  • INDX_LARGE
  • INDX_SMALL
  • USERS_LARGE
  • USERS_SMALL
If you need a schema or tablespace remapping, use the Datapump options. For complete information about database import operations and the available options for using the Oracle Datapump, search the Oracle website.
Follow these steps:
  1. In the 
    Clarity Project and Portfolio Management (PPM)
     installation media, locate the Oracle database image in the <root>/database folder.
  2. Save the database backup to a location on the database server.
  3. Initiate a sqlplus session as the system user and create an import directory by completing these steps:
    1. To log in to sqlplus, enter the following command:
      > sqlplus system/<system_password>
    2. In sqlplus, run the query to create an import directory.
      SQL> create or replace directory import_directory as '<database backup location>';
    3. Exit sqlplus.
  4. To initiate the import, issue the following command:
    > impdp system/<system_password> DIRECTORY=import_directory transform=oid:n DUMPFILE=oracle_base.db SCHEMAS=niku LOGFILE=import.log
    An import.log is generated in the same location as the database backup. Import errors are expected as there are dependencies between the imported items. Once the import has completed, you can recompile the database to resolve invalid objects.
    If you are using different tablespaces than the ones provided in the backup image, provide tablespace remapping parameters. For information about tablespace remapping parameters, see the Oracle documentation for impdp.
  5. To compile invalid objects from the import, log in to sqlplus as the sys user as 
    sysdba 
    and issue the following command:
    SQL> @utlrp.sql
    The utlrp.sql and utlprp.sql scripts are provided by Oracle to recompile all invalid objects in the database. They are located in the $ORACLE_HOME/rdbms/admin directory.
    To recompile invalid objects from the 
    Clarity Project and Portfolio Management (PPM)
     Install bin folder, run the following command:
    admin db compile
Configure Oracle Database Connectivity
  1. Verify that the NLS language setting in the operating system is AL32UTF-8.
  2. Configure an Oracle net listener service. During an Oracle installation, the Oracle Net Configuration Assistant is typically launched automatically to create the default listener. If you already have a configured TNS Listener on the server, you can skip these steps.
    1. UNIX
      : Start the Oracle Net Configuration Assistant for UNIX or Windows using the appropriate command: 
      <oracle home>/bin/netca &
    2. Windows: 
      Start Menu, Programs, Oracle,
       Oracle Home, 
      Configuration and Migration Tools, Net Configuration Assistant
  3. To create the TNS listener, use the information in the following table:
    Oracle Screen
    Option
    Value
    Welcome
    Listener Configuration
    Selected
    Listener Configuration, Listener
    Add
    Selected
    Listener Configuration, Listener Name
    Listener Name
    <choose a name>
  4. Configure an Oracle Net Manager Service Name:
    1. To launch the Oracle Net Manager for UNIX:
      <oracle home>/bin/netasst &
    2. To launch the Oracle Net Manager for Windows:
      Start Menu, Programs, Oracle, 
      Oracle Home, 
      Configuration and Migration Tools, Net Manager
  5. Use the information in the following table to create the Oracle Net Manager service name.
Oracle Net Configuration Assistant Screen
Option
Value
Net Service Name Wizard
Service Name
clarity
Protocol
Protocol
TCP/IP
Protocol Settings
Host Name
Server IP Address or DNS Hostname
Protocol Settings
Port
Server Port
Service
Service Name
clarity
 
Database: Configure a 
Clarity Project and Portfolio Management (PPM)
 Database with Microsoft SQL Server
Instead of Oracle, you can use SQL Server. After you install SQL Server, complete the following tasks in the order presented to import and configure the database for use with 
Clarity Project and Portfolio Management (PPM)
.
  1. Set up valid login credentials for 
    Clarity Project and Portfolio Management (PPM)
    . This login name and password are the values that you specify in CSA to log in to the database. The login name and password can be any combination. 
  2. Set the Microsoft SQL Server Database Schema name as 
    niku
    .
     
    This name must be the Default Schema for the login user you created on the Microsoft SQL server.
  3. Import the database backup image. On the 
    Clarity Project and Portfolio Management (PPM)
     installation media, locate the MSSQL database image in the <root>/database folder.
  4. Save the database backup to a temporary location on the database server.
  5. Use the Restore Database tool in Microsoft SQL Server Management Studio to restore the base image.
    To database: niku
    From device: c:\<
    temporary location you saved the database image to
    > \mssql_base.db
  6. Verify the import, and remove the temporary folder and its contents.
  7. Associate the imported database with your SQL server security user by running the following pl/sql as the sa user:
    USE niku ALTER USER niku WITH LOGIN=<your security user>
  8. To grant the VIEW SERVER STATE to the <
    your security user
    > user, use the following command:
    GRANT VIEW SERVER STATE to <your security user>
Review the Imported SQL Server Database Options
Mixed collations settings are not supported. If you change the server-level default from SQL_Latin1_General_CP1_CI_AS to another collation, create a new SQL Server instance with the correct collation SQL_Latin1_General_CP1_CI_AS before creating the
Clarity Project and Portfolio Management (PPM)
database.
The import procedure creates the database with the options in the following table. Review these options to verify that they meet your requirements.
Option
Value
ARITHABORT
ANSI NULLS
QUOTED IDENTIFIER
ON
To apply, execute:
ALTER DATABASE <database>
SET ARITHABORT ON
ALTER DATABASE <database>
SET ANSI_NULLS ON
ALTER DATABASE <database>
SET QUOTED_IDENTIFIER ON
Compatibility level
MS SQL 2012: 110
To apply, execute:
EXEC SP_DBCMPTLEVEL <database>, 110
MS SQL 2014: 120
To apply, execute:
EXEC SP_DBCMPTLEVEL <database>, 120
Database Schema Name
niku
The login name can be anything, but the default schema name for the login user must be
niku
.
Database user roles
db_owner
The database user must be able to alter the
Clarity Project and Portfolio Management (PPM)
-schema and otherwise own the database.
READ COMMITTED SNAPSHOT
ON
To apply, execute:
ALTER DATABASE <database>
SET READ_COMMITTED_SNAPSHOT ON
VIEW_SERVER_STATE
Granted to database user. To apply, execute:
GRANT VIEW SERVER STATE to niku
REMOTE QUERY TIMEOUT
sp_configure 'remote query timeout',0
reconfigure with override
 
Configure the Tomcat Application Server
  1. Keep your systems up to date with the latest patches. See your vendor documentation for more information.
  2. To upgrade from a prior release running generic J2EE, verify that the DataDirect JDBC driver JAR files in your application server environments are current. The files must be updated to the driver JAR files included with the current release.
  3. Install the appropriate versions of the following software on each server that you plan to include in a cluster. The products that you install on a server depend on the services the server runs.
    Service
    Required Product
    Database service (db)
    Oracle or Microsoft SQL Server
    Clarity System Administrator service (nsa),
    Clarity Project and Portfolio Management (PPM)
    Application (app) service
    Apache Tomcat or IBM WebSphere (supported only on legacy IBM AIX deployments)
    Reporting Service (reports)
    BusinessObjects Report Server
    Clarity Project and Portfolio Management (PPM)
    Background service (bg), Beacon service
    Java JDK only
  4. Some third-party library JAR files (currently, jgroups-all.jar and xinclude.jar) are shipped separately from the image. The install.jar image does not contain the third-party files. Any install packages for a previous version of 
    Clarity Project and Portfolio Management (PPM)
     that are included in the install.jar also exclude the JAR files. For each release, the files are bundled into a third-party JAR library file. The file name uses the following format: 
    thirdparty.libs.<release number>.jar 
    (for example, thirdparty.libs.14.3.0.jar). To make the files available, retrieve the thirdparty.libs.<
    release number
    >.jar
     
    file from the installation media. Place the file in a location that is accessible to the installer.
    If you place the JAR file in the installation directory, the installer does not prompt you for the location of the file.
  5. Install Java. All new installations or upgrades require Java. Depending on your environment, you may also require previous JDKs. If you are upgrading from a version earlier than Release 12.0.6, both Java 8 and Java 7 are required.
    1. Navigate to the installation media that you downloaded, or download the latest JDK from the vendor website.
    2. On Linux:
      1. Log in to the server as root and go to the cd /usr directory.
      2. Extract the jdk-8u40-linux-x64.tar.gz file. By default, the JDK is installed in /usr/jdk1.8.0_40
    3. On Windows: 
      1. Run the following command from your download location:
        <drive>\Java\jdk-8u40-windows-x64.exe
      2. Follow the on-screen instructions but do not use the default Program Files directory. The JDK is installed by default in C:\program files\java\jdk1.8.0_40
        Clarity Project and Portfolio Management (PPM)
         cannot have spaces in the folder path to the JDK. To simplify the installation, install the JDK in a root directory (for example, C:\JDK1.8.0_40).
  6. Set or update the environment variables (JAVA_HOME and PATH) to point to the new JDK.
  7. The Java Runtime Environment (JRE) is updated frequently with fixes for security issues, including issues that are unknown at the time 
    Clarity Project and Portfolio Management (PPM)
     is released. To ensure that you have the latest fixes, download the most recent version 8 JDK from the Oracle website. 
    Clarity Project and Portfolio Management (PPM)
     does not require the public JRE installation. For the minimum software requirements for this release, see 
    Compatibilities
     in the Release Notes (On Premise).
Install the Java 8 JDK (IBM AIX)
Follow these steps:
  1. Download the latest Java 8 JDK install image from IBM and transfer the image to the target server.
  2. Log in to the server as 
    root
    .
  3. Go to the following directory:
    cd /usr
  4. Extract the following SDK tar file from the install image:
    tar xvf <download directory>/Java/Java8_64.sdk.tar.gz (64-bit)
  5. Install the JDK using smitty. 
    The JDK is installed in the following default directory:
    /usr/java8_64
    Clarity Project and Portfolio Management (PPM)
     does not require the Public JRE installation.
Configure the Application Server Environment (UNIX Requirements)
To update the environment variables on UNIX, edit the UNIX user (.profile) file and add or modify the following system variables:
  • JAVA_HOME
    Shell scripts use this variable to locate the correct Java home directory.
    Example:
    JAVA_HOME=/<
    Java 8 home directory
    >
    export JAVA_HOME
    The following table lists the default Java home locations for the supported UNIX platforms. This location can vary according to how your software is installed.
UNIX Vendor
Default JAVA_HOME
Red Hat Linux
/usr/jdk1.8.0_xx
SUSE Enterprise Linux 9
/usr/jdk1.8.0_xx
IBM AIX
/usr/java8_64
  • PATH
    Locates the command-line utilities. Add the following information to the beginning of the existing PATH system variable:
    Example (all platforms):
    PATH=/<clarity home>/bin:$JAVA_HOME/bin:$PATH
    export PATH
Best Practice:
 Keep your systems up to date with the latest patches available. See your vendor documentation for more information.
Configure the Application Server Environment (Windows Requirements)
To update the environment variables on Windows, open the Control Panel and add or modify the following system variables:
  • JAVA_HOME
    Specifies the JDK home directory only, and is not a path variable. Therefore, only
     
    the home directory can be present in the JAVA_HOME value. 
    Name: JAVA_HOME
    Value: <
    Java 8 home directory
    >
    The JAVA_HOME value cannot contain the semi-colon (;) character. If the value has a trailing backslash (\) at the end, the checkinstall script skips all scripts.
  • PATH
    Locates the command-line utilities. Add the following information to the beginning of the existing PATH system variable:
    Name: PATH
    Value: <
    clarity home
    >\bin;%JAVA_HOME%\bin;%PATH
Configure IBM WebSphere
Information for a 
Clarity Project and Portfolio Management (PPM)
 implementation is only provided, and assumes that IBM WebSphere is installed and operational.
To configure IBM WebSphere, complete the following actions:
For information about using the Admin console to set the configuration properties for operating an enterprise application, see the IBM WebSphere documentation.
Update the Classpath with the DataDirect JDBC Drivers
Clarity Project and Portfolio Management (PPM)
 includes its own branded DataDirect JDBC drivers for Oracle and Microsoft SQL Server. Place the JAR files on the IBM WebSphere system classpath.
Follow these steps:
  1. Select AdminConsole, Environment, Websphere Variables.
  2. Set the user-defined JDBC DRIVER PATH to 
    <jars_location_on_server_machine>. 
    For example, ${WAS_LIBS_DIR}/ext.
  3. Make sure that the following JAR files are in the directory you specified in the preceding step:
    c-sqlserver.jar
    c-oracle.jar
    c-clarity.jar
Set the WebSphere JDBC Provider Values (Oracle)
The following procedure explains how to set the WebSphere JDBC provider values for Oracle.
Follow these steps:
  1. Select AdminConsole, JDBC, JDBC Providers.
  2. Set the following values:
    Database Type:
     User-defined
    Implementation Class Name:
     com.ca.clarity.jdbcx.oracle.OracleDataSource
    Name:
     
    <JDBC data provider name>
    . For example, 
    Clarity Project and Portfolio Management (PPM)
     Oracle JDBCProvider
    Description:
     No specific requirements
    Classpath:
     
    ${User-defined_JDBC_DRIVER_PATH}/c-oracle.jar
    ${User-defined_JDBC_DRIVER_PATH}/c-clarity.jar
  3. Click Finish and save to the master configuration.
Set the WebSphere JDBC Data Sources (Oracle)
The following procedure explains how to set the WebSphere JDBC data sources for Oracle.
After you set the JDBC data sources, restart the server before you continue.
Follow these steps:
  1. Select AdminConsole, Resources, JDBC, Data Sources.
  2. Select the scope for the Data Source, typically the server1 Cell, and click New.
  3. Set the following properties:
    Name:
     
    <Data Source Name>
    . For example, CAPPMOracleDS
    JNDI Name:
     jdbc/NikuDS
    Component-managed Authentication alias and XA recovery authentication alias:
     None
    JDBC Provider:
     
    <CA PPM Oracle JDBC provider>
    Data Store Helper Class Name:
     com.ibm.websphere.rsadapter.GenericDataStoreHelper
    Use This Data Source in Container Managed Persistence (CMP):
     Selected
  4. Click Finish and save to the master configuration.
Configure the WebSphere Data Source and Connection Pool Properties (Oracle)
The following procedure explains how to configure the WebSphere data source and connection pool properties for Oracle.
Follow these steps:
  1. Select AdminConsole, Resources, JDBC, Data Sources, 
    <Data_Source_Name>
    , Custom Properties.
  2. Define the following properties. These properties are case-sensitive.
    • serverName
      Value: 
      <DB_System_NAME>
      Type: String
    • user
      Value: 
      <dbUser>
      Type: String
    • password
      Value: 
      <dbUserPassword>
      Type: String
    • portNumber
      Value: 
      <dbPortNumber>
      . For example, 1521
      Type: String
    • SID
      Value: 
      <Oracle_db_SID>
      Type: String
    • insensitiveResultSetBufferSize
      Value: 0
      Type: Integer
    • batchPerformanceWorkaround
      Value: True
      Type: Boolean
    • serverType
      Value: dedicated
      Type: String
    • supportLinks
      Value: True
      Type: Boolean
  3. Save the changes to the master configuration.
  4. Select AdminConsole, Resources, JDBC, Data Sources, ClarityOracleDS, WebSphere Application Server Data Source Properties and set the following value:
    Statement Cache Size = 0
    This setting determines the number of JDBC prepared statements that can be cached for each connection. Setting this value to a non-zero number improves performance for small applications, but it wastes resources when running applications like 
    Clarity Project and Portfolio Management (PPM)
     that execute many statements.
  5. Save the changes to the master configuration.
  6. Select AdminConsole, JDBC, Data Sources, ClarityOracleDS, Connection Pool Properties and set the following value:
    Max Connections = Between 50 and 1000
    You can tune this setting according to the size of your 
    Clarity Project and Portfolio Management (PPM)
     installation. The default setting of 10 is not sufficient and must be changed.
  7. Save the changes to the master configuration.
  8. Restart the server.
Set the WebSphere JDBC Provider Values (Microsoft SQL Server)
The following procedure explains how to set the WebSphere JDBC Provider Values for SQL Server.
Follow these steps:
  1. Select AdminConsole, Resources, JDBC, JDBC Providers.
  2. Set the following values:
    Database Type:
     User-defined
    Implementation Class Name:
     com.ca.clarity.jdbcx.sqlserver.SQLServerDataSource
    Name:
     
    <JDBC data provider name>
    . For example, CA PPM SQLServer JDBCProvider
    Description:
     No specific requirements
    Classpath:
     
    ${User-defined_JDBC_DRIVER_PATH}/c-sqlserver.jar
    ${User-defined_JDBC_DRIVER_PATH}/c-clarity.jar
  3. Click Finish and save to the master configuration.
  4. Restart the server.
Set the WebSphere JDBC Data Sources (Microsoft SQL Server)
The following procedure explains how to set the WebSphere JDBC data sources for SQL Server.
Follow these steps:
  1. Select AdminConsole, JDBC, Data Sources.
  2. Select the scope for the Data Source, typically the server1 Cell, and click New.
  3. Set the following properties:
    Name:
     
    <Data Source Name>
    . For example, CAPPMSQLServerDS
    JNDI Name:
     jdbc/NikuDS
    Component-managed Authentication alias and XA recovery authentication alias:
     None
    JDBC Provider:
     
    <CA PPM SQLServer JDBC provider>
    Data Store Helper Class Name:
     com.ibm.websphere.rsadapter.GenericDataStoreHelper
    Use This Data Source in Container Managed Persistence (CMP):
     Selected
  4. Click Finish and save to the master configuration.
  5. Restart the server.
Configure the WebSphere Data Source and Connection Pool Properties (Microsoft SQL Server)
The following procedure explains how to configure the WebSphere JDBC data source and connection pool properties for SQL Server.
Follow these steps:
  1. Select AdminConsole, JDBC, Data Sources, 
    <Data_Source_Name>
    , Custom Properties.
  2. Define the following properties. These properties are case-sensitive.
    • serverName
      Value: 
      <DB_serverURI>
      Type: String
    • user
      Value: 
      <dbUser>
      Type: String
    • password
      Value: 
      <dbUserPassword>
      Type: String
    • enable2Phase
      Value: False
      Type: Boolean
    • portNumber
      Value: 
      <dbPortNumber>
      Type: String
    • insensitiveResultSetBufferSize
      Value: 0
      Type: Integer
    • databaseName
      Value: 
      <dbName>
      Type: String
    • programName
      Value: Clarity
      Type: String
    • dateTimeInputParameterType
      Value: dateTime
      Type: String
  3. Save the changes to the master configuration.
  4. Select AdminConsole, JDBC, Data Sources, ClaritySQLServerDS, WebSphere Application Server Data Source Properties and set the following value:
    Statement Cache Size = 0
    This setting determines the number of JDBC prepared statements that can be cached for each connection. Setting this value to a non-zero number improves performance for small applications, but it wastes resources when running applications like 
    Clarity Project and Portfolio Management (PPM)
     that execute many statements.
  5. Save the changes to the master configuration.
  6. Select AdminConsole, JDBC, Data Sources, ClaritySQLServerDS, Connection Pool Properties and set the following value:
    Max Connections = Between 50 and 1000.
    You can tune this setting according to the size of your 
    Clarity Project and Portfolio Management (PPM)
     installation. The default setting of 10 is not sufficient and must be changed.
  7. Save the changes to the master configuration.
  8. Restart the server.
Configure the HttpSessionIdLength Property
When you log in to 
Clarity Project and Portfolio Management (PPM)
 on a WebSphere application server, every time you navigate or click a link in 
Clarity Project and Portfolio Management (PPM)
, a message is generated in the SystemOut.log. Here are some examples of the messages:
  • [12/22/14 6:29:37:389 EST] 0000007f WASSessionCor W SessionAffinityManager setNextId Detected JSESSIONID with invalid length; expected length of 23, found 28, setting: 374584CA9C744A43D2F440D63BBD to null.
  • [12/22/14 6:31:06:958 EST] 0000007e WASSessionCor W SessionAffinityManager setNextId Detected JSESSIONID with invalid length; expected length of 23, found 28, setting: 374584CA9C744A43D2F440D63BBD to null.
To avoid these messages, set the 
HttpSessionIdLength 
property as 28 in IBM WebSphere. This property can be set in the custom properties page and is case-sensitive. For more information about how to set this property, see the IBM WebSphere documentation.
Define the Shared Libraries
Shared libraries are a set of files to be shared by deployed applications.
Follow these steps:
  1. Select AdminConsole, Environment, WebSphere variables.
  2. Set the User-defined_CLARITY_INSTALL_PATH to 
    <jars_location_on_server_machine>.
  3. Make sure that the following JAR files are in the directory you specified in the previous step:
    • httpclient.jar
    • httpcore.jar
  4. Select AdminConsole, Environment, Shared libraries.
  5. Select the scope for the shared libraries and click New.
  6. Set the following properties:
    Name:
    <Shared Libraries>
    . For example, Clarity Shared libraries.
    Description:
     No specific requirements
    Classpath:
    ${User-defined_CLARITY_INSTALL_PATH}/httpclient.jar
    ${User-defined_CLARITY_INSTALL_PATH }/httpcore.jar.
    Use an isolated class loader for this shared library:
     Selected
  7. Click Apply and save to the master configuration.
Configure the Security Providers
You must configure the security providers for Jaspersoft integration when 
Clarity Project and Portfolio Management (PPM)
 is running on WebSphere and Jaspersoft is running on Tomcat. Complete the following steps if Java Cryptography Extension Key Store (JCEKS) is not provided as the security provider for WebSphere application server and Java environments.
Follow these steps:
  1. Locate the IBM JDK in the WebSphere Application Server.
  2. Copy the 
    sunjce_provider.jar
     available in Sun JDK 1.7 or 1.8 /jre/lib/ext to IBM SDK/jre/lib/ext/. (See the Release Notes for the supported JDK version.)
  3. Restart the WebSphere application server using this JDK.
  4. Install unlimited Java Cryptography Extension (JCE) restriction libraries if there are any restriction policies.
Perform the Pre-Install Script Steps
  1. Verify that the database setup is complete.
  2. Install Apache Tomcat on the application server.
    1. Navigate to the installation media that you downloaded and locate the apache-tomcat-8.0.xx.zip file.
    2. Copy the file to the root directory or create an application directory (/tomcat).
    3. Extract the .zip file using the following command: 
      jar xvf <drive>/Tomcat/apache-tomcat-8.0.xx.zip
      The apache-tomcat-8 application is created in the folder where you extracted the files. This folder becomes the Apache Tomcat home directory. (See the Release Notes for the supported Tomcat version.)
  3. Verify that the appropriate third-party software has been installed on all of the servers that you plan to use in the cluster.
  4. Familiarize yourself with CSA. To complete the configuration after you run the installation script, use CSA. For an Apache Tomcat J2EE application server, the installation script installs and starts CSA automatically.
  5. For a Generic J2EE application server, you are required to deploy the nsa.ear file that the installation script creates before starting CSA.
  6. If you use IBM WebSphere, select Generic J2EE as the J2EE server vendor during the installation.
  7. Every server in a cluster must have the same multicast address value. The nsa service uses the address to discover the Beacon services in the cluster. This value is defined in the Server Properties in CSA.
  8. Designate one server as the administration server. If you are using a Generic J2EE application server as the administration server, it must also be the J2EE application server administration console.
  9. The HTTP and HTTPS Entry URL fields for the server in CSA cannot be 
    localhost 
    when Jaspersoft is integrated with 
    Clarity Project and Portfolio Management (PPM)
    . When you use Jaspersoft, the URLs must be explicitly entered on the Application subtab of the Properties tab for the 
    Clarity Project and Portfolio Management (PPM)
     server. For example:
    HTTP Entry URL: http://<server name>:<port> HTTPS Entry URL: https://<server name>:<port>
Run the Installation Checker (checkinstall)
Run the Installation Checker (checkinstall) on the designated server for a new installation or upgrade. Although this utility runs automatically at the start and end of installations and upgrades, you can also run it as a standalone utility to verify that your system is ready for the installation.
The utility detects the following:
  • Disk Space
  • Oracle Database Table-Space and Partitioned Tables
  • Duplicate GL Allocation Slices
  • Duplicate/Multiple Idea-to-OBS Associations
  • Seeded Custom Object Code Conflicts
  • Invalid Matrix Rows
  • Other Validations
The Installation Checker can help you assess a new installation or upgrade before you start the actual process. The Installation Checker runs automatically after an upgrade to validate the success or failure of the upgrade process. The utility produces a zipped report archive file that can help you plan an installation or upgrade.
When the Installation checker is invoked as a standalone utility or automatically at the end of an upgrade attempt, a zipped report archive is created. The archive contains the following files:
  • precheck-results.xml and precheck-results.html.
  • postcheck-results.xml and postcheck-results.html. These files are present only if the Installation Checker is invoked through the upgrade process.
  • install.log (if available).
  • checkinstall.log.
  • database output customization files (if present).
  • admin.log from the target directory (if present).
  • install.properties (if present).
  • checkinstall.properties (if present).
  • checkinstall-version.properties.
The archive has a timestamp encoded name (for example, checkinstall-results_2018-04-17_16-48-31.zip). The file is located in the checkinstall/check-logs directory, and if possible, the file is copied into the <target runtime dir>/logs/checkinstall directory.
Each individual check produces one of the result codes in the following table with a diagnostic message.
Code
Description
INFO
Indicates that the check was successful and no potential problems were detected. Specific advice can be present to aid in planning the installation or upgrade.
WARNING
Indicates a potential problem. Details are contained in the message. Address the problem before running the installation or upgrade.
ERROR
Indicates a serious installation or upgrade problem. Details are contained in the message. The installation or upgrade process does not continue when one or more error conditions exist.
The following image shows a sample pre-check results page:
image2017-7-21 9:7:46.png
 
Follow these steps:
  1. Extract the 
    Clarity Project and Portfolio Management (PPM)
     installer to the 
    Clarity Project and Portfolio Management (PPM)
     application server.
  2. Open a command prompt and navigate to the checkinstall directory located in the directory to which you extracted the installer.
  3. Invoke the checkinstall command:
    LINUX:
    sh checkinstall.sh
    Windows:
    checkinstall.bat
    You are asked for the Operator Username and Operator Email. This information refers to the user who is upgrading or installing and the email of the user. This information is stored as a record in the installation log.
  4. Verify the results. The results include any warnings and errors, and also indicate customizations made to the application. Review the customizations and make adjustments for the upgrade as necessary.
 
Run the Installation Script
If you are installing a cluster, run the installation script on 
each server
 that you plan to include in the cluster. When the installation script finishes, the installation process is not yet complete. Finish the installation tasks and configuration using the 
Clarity Project and Portfolio Management (PPM)
 System Administration application.
Record the
Clarity Project and Portfolio Management (PPM)
System Administration password that is created during the installation. The password is required to log in to
Clarity Project and Portfolio Management (PPM)
System Administration and complete the installation.
During the Apache Tomcat installation, you are asked if you want to install
Clarity Project and Portfolio Management (PPM)
System Administration locally. Enter
true
for the administration server only. For other servers in the cluster, enter
false
.
Follow these steps:
  1. From the command prompt, navigate to the directory where you want to unpack the installer file, and type the following commands:
    mkdir temp cd temp
  2. From the directory, run the JAR command to extract install.jar from the installation media:
    jar -xvf <path of the installation media>/install.jar
  3. Run the installation script using the following commands:
    LINUX:
    chmod +x ./install.sh sh ./install.sh
    Windows:
    install.bat
  4. To complete the command-line installation, follow the on-screen instructions. The workflow and instructions for an installation appear in a single phase at the beginning.
    See the following list for installation property descriptions:
    • Third Parties Libraries Jar Directory
      Specifies the directory where the installer can find the thirdparty.libs.14.1.0.jar file when the file is not in the current directory.
    • Clarity Project and Portfolio Management (PPM)
       Home Directory
      Specifies the directory in which to install 
      Clarity Project and Portfolio Management (PPM)
      . This directory is created if it does not exist.
    • JDK 1.8.0 Home Directory
      The Java JDK version 1.8.0_40 or higher. For example: C:\JDK1.8.0_40, /usr/jdk1.8.0_40, or /usr/Java8_64. (See the Release Notes for the supported JDK version.)
    • Beacon Multicast Address
      The multicast address that the Beacon and 
      Clarity Project and Portfolio Management (PPM)
       System Administration use for service discovery. Each 
      Clarity Project and Portfolio Management (PPM)
       cluster requires a unique IP address. The multicast address must be in the Class address range between 224.0.0.0 and 239.255.255.255. Each server within a cluster must use the same address and port. 
      Default value: 230.0.0.1
      We recommend an IP address in the 239.x.x.x subnet.
    • Beacon Multicast Port
      The port that the Beacon and 
      Clarity Project and Portfolio Management (PPM)
       System Administration use for service discovery. Each 
      Clarity Project and Portfolio Management (PPM)
       cluster requires a unique IP address. Each server within a cluster must use the same address and port.
      Default value: 9090
    • Beacon Client Port
      Defines the server port number that the Beacon service uses.
      Default value: 9091
    • Super User Command Prefix
      (UNIX only) The optional command prefix utility, such as sudo, to execute root-level commands. For example, you can implement a root-level command when choosing a socket port below 1024 because root-level access is required to allocate it.
    • Super User Name
      (UNIX only) The optional replacement for the 
      root superuser
       name. This name can be used alone or with the superuser command prefix. For example, if used with sudo, specify the user to which sudo rights are given here. If you are not using sudo, set this value to the user name of the user installing and running 
      Clarity Project and Portfolio Management (PPM)
      . If you are not running 
      Clarity Project and Portfolio Management (PPM)
       as root, set this value to the user name of the user who runs 
      Clarity Project and Portfolio Management (PPM)
       services.
    • J2EE Server Vendor
      Specify the J2EE server vendor: Generic J2EE. The supported generic J2EE vendor is IBM WebSphere (for IBM AIX only).
    • Install 
      Clarity Project and Portfolio Management (PPM)
       System Administration (CSA)
      (Apache Tomcat only) Specifies whether to install 
      Clarity Project and Portfolio Management (PPM)
       System Administration on the current server. Enter one of the following values:
      • If you are installing 
        Clarity Project and Portfolio Management (PPM)
         System Administration on this server, enter 
        true
        .
      • Otherwise, enter 
        false
        .
    • Tomcat 8 Home Directory
      (Apache Tomcat only) Defines the Apache Tomcat 8 home directory. (See the Release Notes for the supported Tomcat version.)
    • CSA Web Port
      (Apache Tomcat only) Defines the web port number that 
      Clarity Project and Portfolio Management (PPM)
       System Administration uses in a UNIX system. This value must be greater than 1024; otherwise, the service must run as root.
      Default value: 8090
    • Enter password
      (Apache Tomcat only) Specifies the 
      Clarity Project and Portfolio Management (PPM)
       System Administration password.
      Default value: admin
    • Operator User Name
      Specifies the user name of the operator who is running the installation script. This information is kept as a record in the installation log.
    • Operator Email Address
      Specifies the email address of the operator who is running the installation script. This information is kept as a record in the installation log.
    • Acknowledge reviewing Install Guide and Change Impact & Upgrade Guide
      This prompt records a response from installing users that they have read both 
      Installing and Upgrading 
      and 
      Change Impact and Upgrade.
Complete the Installation for Apache Tomcat
These steps explain how to complete the 
Clarity Project and Portfolio Management (PPM)
 installation in a configuration running the Apache Tomcat application server.
Follow these steps:
  1. Open the 
    Clarity Project and Portfolio Management (PPM)
     System Administration application using the following URL:
    URL: http://<
    hostname
    >:8090
    If you specified a 
    Clarity Project and Portfolio Management (PPM)
     System Administration port number other than 8090, use that value instead of 8090 in the URL.
  2. Log in using the password that you created during the initial installation.
  3. In the left navigation panel, click Servers and select the local server.
  4. Click each subtab that is listed on the Properties tab and complete the fields necessary for your configuration of 
    Clarity Project and Portfolio Management (PPM)
    1. Set the 
      Bind Address
       to the IP address of the primary NIC on the server. If the server is part of a cluster, ensure that this IP address is on an IP subnet that includes the other servers as members. Set the bind addresses of the other servers to their IP address. Set the bind address for multicast to work properly. If you change the multicast address or the bind address, you can receive a system error as you navigate away from the subtab page. If you receive an error, log out from CSA, and then log back in and continue the configuration.
    2. To learn more about other fields, see CSA: CA Clarity System Administration.
  5. Add the application and background services.
    1. Click All Services.
    2. Click Add to see the available services.
    3. Select the 
      Clarity Project and Portfolio Management (PPM)
       Application and 
      Clarity Project and Portfolio Management (PPM)
       Background services and click Add.
    4. Select all the services and click Deploy.
    5. Select all the services and click Start
  6. To verify that 
    Clarity Project and Portfolio Management (PPM)
     is accessible from a browser, connect using the configured 
    Entry URL 
    value.
    The Entry URL is configured in 
    Clarity Project and Portfolio Management (PPM)
     System Administration on the Application subtab. If you have multiple application servers, the Entry URL points to the load balancer. If you have a single-server installation, the Entry URL points to the application server.
    The Entry URL has the following format: http://<
    server name
    >:<
    port
    >/niku/nu
    The default user ID and password are admin/admin. If the default HTTP port value of 80 is used, you do not have to specify the <
    port
    > value.
 
Complete the Installation for IBM WebSphere
These steps explain how to complete the 
Clarity Project and Portfolio Management (PPM)
 installation in a configuration running an IBM WebSphere application server.
The
Clarity Project and Portfolio Management (PPM)
System Administration (nsa.ear) and
Clarity Project and Portfolio Management (PPM)
Application (niku.ear) must be deployed on separate
instances
within IBM WebSphere. An instance represents a JVM. These two 
Clarity Project and Portfolio Management (PPM)
 applications cannot share the same JVM instance and do not work correctly when deployed in that manner.
Follow these steps:
  1. To deploy the nsa.ear file and set up the 
    Clarity Project and Portfolio Management (PPM)
     System Administration console, use the administration console that the application software vendor provides.
    The installation script creates and places the nsa.ear file in the 
    Clarity Project and Portfolio Management (PPM)
     home directory.
    For information about deploying using the administration console, see the IBM WebSphere documentation.
  2. Start the 
    Clarity Project and Portfolio Management (PPM)
     System Administration application using the following URL:
    http://<
    hostname
    >:9080/nsa/app
  3. Log in using the password that you created during the initial installation.
  4. In the left navigation panel, click Servers and select the local server.
  5. Click each subtab that is listed on the Properties tab and complete the fields necessary for your configuration of 
    Clarity Project and Portfolio Management (PPM)
    .
    For complete information about all of the fields that are found on the subtabs, see
    Clarity Project and Portfolio Management (PPM)
    System Administration (CSA) Server Properties
    .
    The following field requires explanation:
    • Bind Address
      Specifies the IP addresses of every primary server NIC in the cluster that is used for 
      Clarity Project and Portfolio Management (PPM)
       and multicast traffic. The addresses are comma-separated if there is more than one server in the cluster. If the servers are part of a cluster, ensure that the IP addresses entered are on the same IP subnet for multicast to work properly.
      For example: 192.168.1.10, 192.168.1.11, 192.168.1.12.
      If you change the multicast address or the bind address, you could receive a system error as you navigate away from the subtab page. If you receive an error, log out from 
      Clarity Project and Portfolio Management (PPM)
       System Administration; then, log back in and continue the configuration.
  6. To add the database, background, and reports services, complete the following actions:
    1. Click All Services.
    2. Click Add to see the available services.
    3. Select the services and click Add.
  7. Start the database service.
    1. Click All Services.
    2. Select the Database service and click Start.
  8. To package the niku.ear file, complete the following steps:
    1. In the left navigation pane, click Install and Upgrade.
    2. Click Package Application EAR.
    3. Click Create Package.
      A Status window appears and displays the status until the EAR file is created in the Clarity home directory:
      <clarity home>/niku.ear
  9. Start the remaining services.
  10. From the J2EE application server administration console, deploy the 
    Clarity Project and Portfolio Management (PPM)
     application (niku.ear file).
    For information about deploying the niku.ear file from the server administration console, see the documentation from the vendor (IBM WebSphere).
  11. To verify that 
    Clarity Project and Portfolio Management (PPM)
     is accessible from a browser, connect using the configured 
    Entry URL 
    value.
    The Entry URL is configured in 
    Clarity Project and Portfolio Management (PPM)
     System Administration on the Application subtab. If you have multiple application servers, the Entry URL points to the load balancer. If you have a single-server installation, the Entry URL points to the application server.
    The Entry URL has the following format:
    http://<
    server name
    >/niku/nu
    The default user ID and password are admin/admin.
Set Up Class Loader
Set up the class loader to reuse the same libraries for both 
Clarity Project and Portfolio Management (PPM)
 and Jaspersoft.
Follow these steps:
  1. Select AdminConsole, Applications, Application types, WebSphere enterprise applications.
  2. Click <clarityapp>.
  3. Under Detail Properties, click Class loading and update detection.
  4. Select 
    Classes loaded with parent class loader first
     in the Class loader order section.
  5. Select 
    Single class loader for application
     in the WAR class loader policy section.
  6. Click Apply.
Create Shared Libraries in WebSphere
Create shared libraries in WebSphere if you do not already have these libraries.
  1. Navigate to Admin Console, Environment, Shared Libraries.
  2. Select the scope of the cell (for example, 
    Cell=gajva01-VM56769Node01Cell, Profile=AppSrv01
    ).
  3. Click New and set the following values:
    Name: 
    Clarity Shared libraries
    Description: 
    Required for Jaspersoft communication
    Classpath: 
    <ClarityInstallLib path>/httpclient.jar, <ClarityInstallLib path>/httpcore.jar
  4. Select the option "Use an isolated class loader for this shared library".
  5. Save the configuration.
Add the Shared Libraries to the Application
The following procedure explains how to add the shared libraries.
Follow these steps:
  1. Select AdminConsole, Applications, Application Types, WebSphere enterprise applications.
  2. Click <clarityapp>
  3. Under References, click Shared library references.
  4. Select the Clarity Web module and click Reference shared libraries.
  5. Move Clarity Shared libraries to the Selected list and click OK.
  6. Select the Jasper Web module and click Reference shared libraries.
  7. Move Clarity Shared libraries to the Selected list and click OK.
Verify the Installation
You can run a health check on any server. The health check generates a report for each server that is selected and verifies aspects of the installation. The report contains a list of categorized line items, each with an associated status. Examples of line items include the testing of ports, database parameters, and third-party software product installation.
Follow these steps:
  1. Log in to 
    Clarity Project and Portfolio Management (PPM)
     System Administration.
  2. On the Overview page, select the check box next to each server that you want to include in the report, and click Run Health Check.
  3. View the log files in CSA for the servers in a cluster:
    1. Click Servers in the left navigation pane.
    2. Click the server name and click Logs.
    3. In the Log File field, select the log file that you want to view and click Go. Limit the amount of data by selecting a value in the Max Size field.
    4. (Optional) To download the file, click Download and specify a target location.
  4. Verify the time settings are identical. For functionality and accuracy of data in 
    Clarity Project and Portfolio Management (PPM)
     and all jobs, including the Load Data Warehouse Job, verify the following:
    1. The server time is the same (preferable, down to the second) on the 
      Clarity Project and Portfolio Management (PPM)
       application server, 
      Clarity Project and Portfolio Management (PPM)
       database server, and Data Warehouse database server.
    2. The timezone, date, and time is the same on the 
      Clarity Project and Portfolio Management (PPM)
       application server and database servers in the same environment. Do not allow any differences.
    This synchronization is necessary because the Load Data Warehouse job imports data based on the last_updated_date field on the object instances. If the date and time on the servers do not match, data may not be loaded into the Data Warehouse. For other jobs, if the date and time do not match, the job may not start. Or, the job may start later than expected, leading to inaccurate data.