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.

Note: If there are dependencies between the customizations, it is up to you to determine the order in which the packages should be deployed. For example, if you want to deploy an OMS package and a Call Center package, it is your decision to choose which package to deploy first.

About this task

Note: 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.
The base OMS version with a minor version update (minor update) is available for deployment in your non-production and production environments according to the following conditions.
  • The minor update for the non-production environment is available based on the OMS base version that is currently deployed.
  • The minor update for the production environment is available based on the OMS base version that is deployed in your preproduction environment.
The following rules are applicable for deploying a minor OMS update in your environment.
  • If the latest base version is already deployed in your environment, you can deploy the customization only on that version and you do not get an option to select any other base version.
  • If your environment is locked by IBM, you can deploy the customization only on the locked version of the environment, which is your current base version. You do not get the option to select any other version. To unlock your environment, you must raise a ticket with IBM Support.
  • If your environment is not locked, you can deploy the customization according to the following conditions:
    • If you are deploying the customization in a non-production environment and your environment is on an older base OMS version, then the latest minor update version and the immediate previous version are available for selection during update. In this case, a warning is displayed to indicate your environment is on an older version. It is mandatory to update your environment to either latest minor update or the immediate previous version.
    • If your non-production environment is on the immediate previous version of the latest minor update version, you can either select the given option to update your environment to the latest minor update or stay on the current deployed version.
    • If you are deploying the customization in a production environment, the version that is deployed in the preproduction environment is considered as the base version.
      • If the production environment is on a lower version than the preproduction environment, the option to select the preproduction version and the version before the preproduction version are available for update in the production environment.
      • If the production and preproduction environment are on the same version, no option to select the base version is provided and the current version of the preproduction environment is selected by default.
Note:
  • If you have multiple preproduction environments, the first preproduction environment that was created is considered as the base environment for your production environment. If you want to lock or unlock your current environment, you must raise a ticket with IBM Support.
  • For more information about major and minor updates, see Major updates and Minor updates.

When you select the option to deploy customization, a process is started and the status is displayed in the processes list. The deployment status is available in the log. 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.