Next-generation platform

Deploying customization on the next-generation platform

Users with the Developer role can deploy a customization and can update their environment by using Self Service.

When you try to deploy a customization, Self Service checks your environment and if you are not on the latest minor version within your OMS release, it provides you an option to update to one of the two most recent minor versions of the release.

About this task

The deployments for your environment are listed in the Deployments tab for 60 days from the date of deployment. The logs are available for 30 days. For more information about viewing logs, see Viewing logs for deploying customization.

Before deploying a customization, review the deployment planning considerations. For more information, see Deployment planning considerations for customizations.

The base OMS version that is available for deployment depends on the current environment type and version. The following rules apply when you deploy minor OMS updates:
  • If the latest base version is already deployed in your environment, you can deploy the customization only on that version.
  • If IBM locks your environment, you can deploy the customization only on the locked version. To unlock your environment, raise a ticket with IBM Support.
  • If your environment is not locked, the available versions depend on the environment type and current version:
    Non-production environments
    • If the environment uses an older OMS base version, you must update to either the latest minor update version or the previous minor update version before deploying the customization. A warning is displayed when the environment is not on a supported version.
    • If the environment uses the previous minor update version, you can update to the latest minor update version or remain on the current version.
    Production environments
    • The version that is deployed in the preproduction environment is used as the base version.
    • If the production environment uses an earlier version than the preproduction environment, you can select either the preproduction version or the previous version for deployment.
    • If the production and preproduction environments use the same version, the preproduction version is selected automatically and no base version options are displayed.

If you have multiple preproduction environments, the first preproduction environment that was created is used as the base environment for the production environment.

For more information about major and minor updates, see Major updates and Minor updates.

When you deploy a customization, a process starts and its status is displayed in the process list. Deployment status information is also available in the logs. For more information, see Viewing logs for deploying customization.

Procedure

  1. Access Self Service with your IBMid.
  2. From the Self Serve menu, select Environments.

    The Environments dashboard is displayed.

  3. From the list of environments, select the environment where you want to deploy a customization.
  4. In the Customizations tab, click Packages.
  5. Click Deploy for the customization jar that you want to deploy and then select the customization extension JAR file.
  6. If the Select base version option is displayed, select a base version from the list based on the rules that are listed here.
  7. Optional: Select the Schedule deployment to a future start time and date checkbox if you want to schedule the deployment of the customization.
    Select the date and time for scheduling the deployment.
    Note: The time is scheduled in the UTC time zone.
  8. Optional: Enter a description in the Notes field.
  9. Click Submit.
    Note: If any process is in progress in the Processes tab and a deployment process is run from the Deployments tab, it is added in the queue and is started after the processes under the Processes tab are complete.