Legacy platform

Importing deployable artifacts into the IBM UrbanCode Deploy Selfserv tool

If a deployable package that you want to deploy with the IBM UrbanCode Deploy Selfserv tool is not available within CodeStation to deploy, you can import the package from your drop server. You must use the IBM UrbanCode Deploy Selfserv tool to import an artifact or new version of an artifact. You cannot directly access CodeStation.

Before you begin

Ensure that the following conditions are met
  • The deployable package conforms to the required technical specifications.
  • The deployable package is transferred to the drop server.

    The package must be included within the correct directory on the drop server. The IBM UrbanCode Deploy Selfserv tool checks the configured build path on the drop server every hour for new versions of a deployed artifact. If a new version of a deployable artifact is found, the tool automatically imports the artifact into CodeStation.

    If you want to change how the self-service tool imports new versions of artifacts automatically, you can change the settings on the Configuration tab for the component.

    By default, the tool checks the following directories for new versions for IBM Sterling Order Management System packages:
    Component Default directory
    IBM Sterling Order Management System deployment. /home/clientID/om_deploy
  • You have access and login credentials for the IBM UrbanCode Deploy Selfserv tool. You can request access through a service request ticket.

Procedure

  1. Access the IBM UrbanCode Deploy Selfserv tool dashboard.
  2. From the Dashboard, click the Components tab.
    The tab shows all of the components items for which you have deployment access.
  3. Select the application component.
  4. Click the Versions tab.
  5. Click Import New Versions.
  6. Select the build artifact deployable artifact to import.