Configuration

In addition to normal component installation and configuration, there are other areas that require configuration. They are:
  • importing configuration data worksheets
  • importing and activating the Business Rules workflows
  • configuring the XML files for the Transaction Server scheduler, listener profile, and extraction profile.
  • changing the configuration for one or more components

The Common Services base component provides the data setup utility (DSU), which allows a user to import configuration data instead of using the base Control Center. A reference set of import worksheets are provided with the components and features. These worksheets provide an integrated end to end flow. The component worksheets build on each other, so there is an order dependency among the components.

Business Rules comes with several workflows. Some of the flows are used in the reference implementation. If some components are not installed, the nodes for those components in the workflows need to be removed.
Note: The Gateway configuration sample file comes already configured to use the workflows.

The Transaction Server uses a scheduler XML for configuring how work flows to other components and other activities such as partitioning database tables. Events occur within the Transaction Server, or are sent to the Transaction Server by using WebSphere® MQ. If the scheduler XML indicates that another component needs to perform some action on behalf of that event, a WebSphere MQ message is sent to that component. The reference scheduler XML configuration file must be updated with the WebSphere MQ deployment for the appropriate settings for the queue manager and host name. If a component or payment type in the configuration is not being used, remove its configuration from the XML file by commenting it out or by deleting the stanzas. For more information on the scheduler XML, see Events and communication with external applications.

FTM provides several IBM® MQ reference files for creating and clearing queues based on the default names. View the reference files for the instructions to run the script. These reference files are available in the FTM artifacts pod.

For more information about getting files from the artifacts container for your offering, see Getting the files from the artifacts container for your FTM offering.