Installation procedure

To install the Corporate Payment Services reference application, do the following steps:
  1. Create the FTM queue manager if it was not already created.
  2. Create the IBM® MQ queues used by the CPS reference application:
    1. Locate the IBM MQ script for the appropriate operating system in the list of installation files in Table 1.
    2. Run the following command: 
      runmqsc your_QManager_name < gpyQueues-CreateReference.txt
      where your_QManager_name is the name of the FTM queue manager.
      Note: The runmqsc command needs to be run from the IBM MQ bin subdirectory.
  3. Create the FTM core database if it was not already created.
    Note: The name of the database and the database schema are required to proceed with the installation.
  4. Add the FTM runtime Java™ classes and resources to the class path environment variable if they were not already added. For more information, see Setting up FTM IBM MQ and IBM App Connect Enterprise resources.
  5. Install the FTM Operations and Administration Console and configure it to use your database. For more information, see Installing the FTM Operations and Administration Console.
    • When you create the JMS queue definition, use the values that are shown in the following table to send commands to the reference application,
      Table 1. Corporate Payment Services reference application FTM command JMS queue definition
      Field Value
      Provider WebSphere® MQ messaging provider
      Name ftmQCPS
      JNDI name jms/ftmq/CPS Reference
      Description FTM CPS Reference console queue
      Queue Name FXH.GPY.COMMAND
  6. Create the definitions for the finite state machine and static configuration values in the database.
    1. Locate the database script installation instructions for the appropriate operating system. For more information about the installation files, see Table 1.
    2. Connect to the FTM database and follow the instructions.
  7. To run the CPS reference application flows, deploy the IBM App Connect Enterprise archive file to its own execution group. Use the IBM App Connect Toolkit or IBM MQ Explorer.