Automated deployment utility

The automated deployment utility can be used to deploy components of Payment Feature Services to a local or a remote WebSphere® Application Server deployment manager or server. It is designed to reduce the amount of time that is needed to deploy multiple components of Payment Feature Services.

The automated deployment utility is also a reference implementation of a deployment utility that works with most deployment environments. If this implementation does not meet the requirements for a specific deployment environment, the following options are available for deploying into that unique environment:
  • Configure any WebSphere Application Server settings that are unique to the deployment environment before you run the ADU. The ADU does not change existing WebSphere Application Server settings during the deployment.
  • Use the ADU to deploy only the Payment Feature Services components that are compatible with the ADU deployment process. Then, manually deploy the components that require a unique configuration after the ADU is run.
  • Create your own utility to support the unique deployment environment. The ADU can be used as a reference for the new utility. The source code for the ADU is included in its JAR file and can be modified as needed. The user is responsible for supporting the modified utility.
The utility is installed by the following features:
  • FTM for Digital Payments
  • FTM for Corporate Payment Services

It needs to be run from the directory in which it was installed. For example, on the AIX® operating system, the automated deployment utility and its corresponding deployment configuration utilities are installed in the install_directory/shared/v3213/pfs/DeploymentUtility directory by default.

A configuration file for the utility provides information that is needed for the deployment, such as which deployment parameter information (token) file is to be used. To deploy to more than one server without using a deployment manager, use a separate configuration and token file for each server. Separate files are needed because the information used to connect to a server is located in the common section of a token file.

The token file that is specified in the automated deployment utility configuration file defines the name and SOAP port of the WebSphere Application Server profile to use for the deployment. The utility connects to the WebSphere Application Server profile over a secure connection. If the local profile does not exist, the utility creates the profile, copies the truststore and keystore files from WebSphere Application Server, and creates security properties files to use those truststore and keystore files. If the WebSphere Application Server profile does exist, security must be enabled and correctly configured in the profile for the deployment to succeed. You must ensure that the automated deployment utility is using the correct security files to connect to the selected profile.

The automated deployment utility does not deploy the IBM® App Connect Enterprise applications. Use the FTM deployment utility to deploy them. Examples of these applications are shown in the following list:
  • Digital Payments reference application
  • CPS reference application
  • OFAC simulator for Vetting

Creating deployment parameter information (token) files

Use only the ADU token file wizard that was installed with the automated deployment utility and FTM deployment utility to create the token file for deploying the components in that installation. Do not use it to create the token files to deploy different versions of the components or components from different installations. The automated deployment utility (ADU) displays an error and does not do the deployment when the version of the token file and the version of the components to be deployed do not match.

The token files from an existing deployment configuration can be used with the automated deployment utility and its corresponding utilities, but the format of the files must be converted before they are used. To create a new token file from an existing file, use the existing token file as input to the ADU token file wizard and then save the results with a new file name.
Note: If an existing deployment configuration has multiple token files for the different components, merge those token files into a single token file and then provide the single file as input to the ADU token file wizard.

Additional information

The automated deployment utility also has the following requirements:
  • A Java™ virtual machine that includes the IBM JCE Java Cryptography Extensions. The Java virtual machine that was installed when the features were installed can be used.
  • JAR files from the version of WebSphere Application Server that is being deployed to.