Deploying a global package

Before a global package can be deployed to your PRD tenant, the package must first be deployed to another tenant such as TST, TRN, or DEV. This is to prevent corruption of the PRD tenant.

1. Sign in to CSSP.
2. Select Configuration Management > Entitled Global Packages.
3. Click the hyperlink of the global package you want to deploy. The Global Package Details page displays.
4. From the Available Package Version list, select the version you want to deploy. You can select any version, with two exceptions:
   1. You are deploying a version to a PRD tenant which is newer than any version you have deployed to a non-PRD tenant.
   2. You are deploying a version to a tenant where a later version than the one you selected has already been deployed.
5. From the Target Tenant list, select the tenant to which to deploy the package.
6. Once you have selected a target tenant and a version, the Dependent Package list populates accordingly. If that package version depends on any other global packages (such as some object or integration that needs to first be installed on the target tenant via another Global Package), then the packages that satisfy the dependency are listed in the table at the bottom of the screen.
   Caution: These packages must be deployed before your selected version can be deployed to the target.
   1. Click the Deploy button to open the Deploy Global Package Wizard for each dependent package, or click Compare to open and complete the Compare Global Package Wizard so that you can preview the resources that will be deployed.
   2. Complete the deployment wizard and wait for the deployment to be completed before deploying the package version you originally intended to deploy.
7. From the Global Package Details page, click Deploy. The Deploy Global Package Wizard displays.
8. Optionally, select the Generate Compare Report check box to generate a report previewing the changes to the target tenant before the changes are deployed.
9. Click Next to open the Dependent Global Packages page.
10. If any dependent global packages are listed, those must be deployed to the target tenant before the current package can be deployed, unless the Package Type column's value is BuiltIn. BuiltIn means that the dependent package is automatically deployed as part of the current deployment. If the value in the Deployed Package Version column does not match the value in the Latest Package Version column for any dependent package, we recommend you exit the wizard and deploy the listed packages.
11. If no dependent packages are listed or if the listed packages have the package type of BuiltIn or the value in the Deployed Package Version column matches the value in the Latest Package Version column, click Next to open the Package Version Applications page.
12. Select each application to include in the deployment and choose a target organization for each selected application.
13. Click Next to open the Define Custom Infrastructure Parameters page.
14. Some applications may use custom infrastructure parameters. These parameters can change how certain resources are deployed. For example, you can enter a user name or password field for a resource or choose whether the resource should overwrite or merge a given value in the target tenant.

    Values for these parameters can be specified during this step. See the Infor Configuration Management Reference Guide for Global Packages for your application for information on the parameters. If any parameters are not documented, open a support case in Infor Concierge for the application support team to provide assistance.

15. Click Next to open the Review and Submit page.
16. Review the deployment details, including the target tenant, applications, organizations, and resources. After you are finished reviewing, click Submit to launch the deployment.