Verify the local package deployment

  1. Sign in to CSSP.
  2. Select Configuration Management > Deployed Local Packages.
  3. Click the package from the list of deployed packages.
  4. Click each of these tabs to view the package information and the information about each stage of the deployment process:
    Overview
    This tab contains package information and the overall status of the deployment.
    Stage 1 - Export Target Tenant
    If a Compare report is selected, the first step involves exporting the current resources of the target tenant so they can be compared to the local package that is being deployed. This tab shows the status for the export of each application in the target tenant. The tab for this stage is not available if the Generate Compare Report check box is not selected in the package deployment request.
    Stage 2 - Compare
    This tab shows the compare status for each application.

    If the Generate Compare Report check box option is selected, the Review Compare Report option becomes available after you create the report . After you review the report, click Continue Deployment. Otherwise, the deployment process does not proceed.

    If the Generate Compare Report check box is not selected in the package deployment request, the tab for this stage is not available and no action is necessary.

    You can use Compare reports to review the changes that a source package makes to your target tenant before you deploy the package. Compare reports help eliminate the risk of deploying unwanted changes to your target tenant.

    The Compare report provides a header with high-level information about the deployment, data panels with details for each resource in a package, and a selection panel to navigate through the resource data panels.

    The report header shows the customer's name and the source and target tenants for the package deployment.

    You can use resource data panels to make resource-level comparisons between your source and target tenants. Each resource has a data panel with rows for the fields associated with that resource and the value of the fields in the source and target tenants. Double-click a row to open a more detailed comparison of the source and target field, and then click Diff to highlight the differences between the two.

    Use the selection panel to navigate to specific resource data panels. The selection panel shows the resource categories hierarchically. Select a category to show the resource data panels for that category.

    Use the selection panel to filter resources by application with the Application item list. If the Show only differences box is selected, only resources with differences in the source and target tenants are displayed. Use the Search bar to search for a specific resource or category.

    The selection panel provides counters that indicate the number of differences in the source and target tenants. The green counter represents the number of new resources being added to the target tenant from the source. The red counter shows how many resources are different between the source and target tenants.

    You can use the selection panel to download an .xlsx file of the Compare report for individual applications. Thus, you can share data from the Compare report outside of the CSSP. To download the Compare report for an individual application, perform these steps:

    1. In the selection panel, select the application from the Application item list.
    2. Click the Download icon.
    Stage 3 - Validate
    The validation process ensures that the resources from the package are compatible with the resources in the target tenant. This validation process provides information about incompatibilities between the local package and the target tenant. When incompatibilities are found, messages are provided that indicate the nature of the incompatibilities. To review the validation messages, click View Messages and select the desired application from the list.

    These message types are available:

    • Info: Corresponds to a success status.
    • Warning: Corresponds to an evaluate status.
    • Error: Corresponds to a failure status.

    If the validation stage is successful for each application, the overall validation status is Success and the deployment automatically continues to the next stage. Viewing the info messages is optional in this case.

    For further assistance with failures, submit a case on Infor Concierge for the support team of the failed application. Ensure you include the message details and the RequestId.

    If the validation stage yields an application with the status of Evaluate, perform these steps:

    1. Click View next to the application to view the warning message. To view the full message, click Full Message in the View column.
    2. After you read the messages and decide to continue, select the Accept and acknowledge check box. Then, click Yes on the confirmation screen.
    3. Close the Validation Messages window.
    4. Click Continue Deployment.

    Some messages only provide information and do not require an action. Other messages convey information about more serious incompatibilities. To better understand a failure or evaluate message, see the "Validation failed" topic in the application-specific guides for details. These guides are included in the CloudSuite documentation libraries as well as the application-specific documentation libraries. The guides are under the Configuration Management heading in the documentation library.

    Stage 4 - Deploy
    This tab shows the deployment status of each application. If this stage fails, identify the issue and resolve it using the messages returned by the application. For further assistance with failures, submit a case on Infor Concierge for the support team of the failed application. Ensure you include the message details and the RequestId.
    Stage 5 - Post Deploy
    Some application deployments are complete at the end of stage 4. Other applications require additional processing. The status is displayed for those applications on this tab. When the status of this step is Success, the package has been deployed to the target tenant. If this stage fails, correct the issue and resubmit the deployment.