Transferring deployable packages to the deployment drop server

When you need to deploy code or other file changes into an IBM Sterling® Order Management System environment, you must first include the deployable package, or build artifact, on an intermediary file transfer drop server. The deployable package can then be retrieved from the drop server for deployment into an IBM Sterling Order Management System environment.

For deploying changes for an IBM Sterling Order Management System application, the IBM® UrbanCode® Deploy Selfserv tool automatically retrieves new versions of deployable packages from 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 for later deployment.

Before you begin

Ensure that the following conditions are met:

You have the required permission level and login credentials to access the files and directories on the drop server. You can request access and connection information for the server through a service request ticket. As part of the implementation process for setting up your IBM Sterling Order Management System service, IBM provides you with the information that you need to access this site. This information includes the following credentials and configuration information:
- The user or client ID that you need to access the server.
- The IP address and port number for the drop server.
- The parent directory where you need to deploy your files. By default, this directory is /home/$CLIENT, where $CLIENT is the name of the specific directory for your company client ID. You must include your deployable packages within the appropriate subdirectory in your $CLIENT directory.
The deployable package conforms to the required technical specifications. For more information, see Building IBM Sterling Order Management System deployable packages.If you are transferring a deployable package with a file transfer tool that transfers the file with a different file format than the expected format, you must convert the file to the expected format after the transfer is complete. For example, deployable packages for a IBM Sterling Order Management System must be a compressed .zip file. If your transfer tool transfers the file as a .tmp temporary file, you must convert the file to a compressed .zip file after the transfer is complete.

Procedure

Set up your preferred file transfer tool to establish a connection to your drop server. Use your login credentials to access the server.
You can use a Secure Copy Protocol to copy files to this site. For example, use a secure file transfer tool such as WinSCP or FileZilla.

When you are setting up your file transfer tool, create entries for deploying files to all instances of your IBM Sterling Order Management System environments. For example, for a IBM Sterling Order Management System, you must create entries for the authoring and live instances in each environment. However, you do not need to create more than one endpoint machine. All connections are created over locally mapped ports, such as port 1901 for live instances and port 1902 for authoring instances. If your target environment includes multiple live servers, define an entry for each server. For instance, 1901 for live server 1 and 1906 for live server 2.
Connect to the drop server through your file transfer tool.
Copy the deployable package from your build server environment to the drop server.
When you are transferring packages to the drop server, you must copy the package to the correct directory within your /home/$CLIENT directory structure:
- Include IBM Sterling Order Management System deployment JAR files within the /home/$CLIENT/om_deploy directory.
- Include any other type of file within a directory of your choice within the parent /home/$CLIENT directory.