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.
ccppmod144
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 following resources can help you plan your installation or upgrade:
Use the following checklist to assist you with new installations. As a SaaS customer administrator, many of these steps are performed for you; however, in some cases you can configure one or more supported options.
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
Complete the Pre-Install Tasks
  1. Verify the third-party software that is supported for this release. See 
    Compatibilities
     in the
    Release Notes
    .
  2. 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.
  3. Request confirmation from CA that the Installation Checker (checkinstall) yields a passing result on the designated server for the new installation or upgrade. Although this utility runs automatically at the start and end of installations and upgrades, on-premise administrators can also run it as a standalone utility to verify that your system is ready for the installation. As a SaaS customer, you cannot run this utility; however, you can work with CA Support to troubleshoot the kinds of issues that might be impacting your test or production SaaS instance. 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 on a sandbox or test environment 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
For example, if customizations are detected, work with CA Support to generate a discovery report to resolve customizations before you upgrade.
Complete the Post-Install Tasks
  • To verify that 
    Clarity Project and Portfolio Management (PPM)
     is accessible from a browser, connect using the configured 
    Entry URL 
    value for your organization and product instance. The Entry URL is configured for you by CA. If you have multiple application instances, the URL can point to a load balancer. If you have a single-server installation, the URL points to your
    Clarity Project and Portfolio Management (PPM)
    application server instance. For example, ondemand.ca.com or https://<server_name>.ondemand.ca.com/niku/nu
  • Change your default password.
  • Install any add-ins that you intend to use with this release. See Add-Ins and Integrations.
  • Identify the 
    Clarity Project and Portfolio Management (PPM)
     views that require configuration before business users can access them.
  • Configure portlets and pages as appropriate to expose or hide any new functionality available in the new release.
  • Update access rights for users, groups, or OBS instances with new or updated security rights that are introduced in this release.