Deployment options
The following methods are available to deploy the components. Carefully consider the options and select the
appropriate method for the environment.
Note: Ensure that any prerequisite tasks are completed before you
deploy the components. Refer to the following topics for a description of the tasks that are needed and the
order in which they must be done:
- For Corporate Payment Services: Corporate Payment Services Installation Overview
- For Digital Payments: Digital Payments Installation Overview
Deploying your Payment Feature Services Java™ Platform, Enterprise Edition applications within the same server or cluster as the FTM Java Platform, Enterprise Edition applications is not supported.
The deployment options are:
- FTM Deployment and ADU Token File Wizard Utilities
- The ADU token file wizard simplifies the deployment configuration process by saving the
deployment parameter information (tokens) in a file that can be retrieved. The tokens are used in the FTM
deployment utility deployment scripts. When the information is retrieved, the user can deploy the components
without reentering the deployment information. The parameter information is stored in a file that can be
encrypted. There is a single deployment parameter information (token) file for all of the components. Users
with multiple configurations can have a different token file for each configuration.Note:
- The FTM Deployment utility deploys only the IBM® App Connect Enterprise applications and does not deploy the WebSphere® Application Server components. Use the Automated deployment utility to deploy the components to WebSphere Application Server.
- Use the ADU Token File Wizard to create token files for both the FTM Deployment utility and the Automated deployment utility.
- Automated deployment utility
- The utility deploys components of Payment Feature Services to a WebSphere Application Server deployment
manager or server. It is designed to reduce the amount of time that is required to deploy multiple components
of Payment Feature Services. It uses the same deployment parameter information (token) files as the
FTM Deployment Utility. For more information, see Automated deployment
utility.Note: The automated deployment utility does not deploy the IBM App Connect Enterprise applications.
- Manually deploy the application in WebSphere
- The WebSphere Application Server Administration Console is used to manually customize the application in WebSphere. For instructions, see Manually Deploy in the WebSphere Application Server.