Validating and Deploying Applications through Performance Management Architect

  To validate and deploy a Profitability and Cost Management application in Performance Management Architect:

  1. From EPM Workspace, select Navigate, then Administer, and then Application Library to display the Application Library.

  2. Right-click the application name, and select Validate to validate the newly created Profitability and Cost Management application in Performance Management Architect. For Profitability and Cost Management validation conditions, see Profitability and Cost Management Validations.

    When the validation is complete, the Job Task dialog box is displayed, showing the associated job number.

  3. Click the link for the associated job to view the Job Console.

  4. Review the Job Console Summary, and if there are errors, click the validation log link under Attachments to see a complete listing of all validation errors or messages.

  5. Fix any errors listed in the Validation Log.

  6. Repeat step 2 to step 5 until the validation succeeds with no errors.

    The application is ready to be deployed.

  7. In the Application Library, right-click the application name, and select Deploy from the drop-down list.

    Applications are validated before they are deployed. Any validation errors display in the Job Console. You must correct all validation errors before deploying. When the validation is complete, the Deploy dialog box is displayed.

    Use the Deploy dialog box to specify the application, instance, any deployment notes, web and application servers, and the Shared Services Project for the application that is being deployed.
  8. Provide the required information for the deployment:

    • Optional: Under Notes, add notes pertaining to the deployment of this application. These notes are appended to the job description in the Job Console. This text field allows up to 200 characters and may contain any characters.

    • Under Instance Name, select the name of the Profitability and Cost Management installation to which you want to deploy the application.

      A Profitability and Cost Management application may be installed on a single machine, or on more than one machine as part of a cluster. Each installation, or instance, is displayed on the Instance Name drop-down list. Default is the name of the instance used by the Configurator Tool for the first installation.

    • Select the Application Server.

    • Under Shared Services Project, select the Profitability and Cost Management application group to which this application is to be assigned.

    • Optional: Decide whether Full Deploy should be selected, as follows:

      • If this is the first deployment of the application, the Full Deploy checkbox is disabled because Performance Management Architect automatically sends all dimensions to Profitability and Cost Management.

      • If Full Deploy is checked for any subsequent deployment, then Performance Management Architect sends all dimensions to Profitability and Cost Management.

      • If Full Deploy is not checked, then Performance Management Architect sends only modified dimensions to Profitability and Cost Management. If no changes were made to a dimension, then that dimension is not included in the deployment.

  9. Click Deploy.

    The Job Task window is displayed, to confirm the Validation Job has been submitted, and display the Job ID.

  10. On the Job Task window, click the link to display the job status.

    When the job is complete, a message is displayed under Detail to indicate the new application has been created and deployed to Profitability and Cost Management. The new application is available for selection.

    Note:

    If the deployment of the application is not successfully completed, from the Application Library, right-click the application name, and select Application Cleanup. This option forces a delete call to both Shared Services and Profitability and Cost Management to remove any traces of the application, and resets the application in Performance Management Architect to the undeployed state.