Cross-Context Flows › How to Configure a Cross-Context Flow

How to Configure a Cross-Context Flow

To utilize Cross-Context Flows, configuration of Load Module mappings must be done. In addition, a Java Message Service (JMS) must be configured in the Application Server. The Build Tool allows for configuration of the Load Module mapping along with the JMS connection factory and queue names.

An application may have all of its load modules assembled together in a single context, or the load modules may be separated into independently deployed contexts. You should keep in mind; however, that communicating across separately deployed context will have a negative impact on performance.

It is recommended to name your load modules in a way that enables you to identify them quickly when configuring for cross-context. For example, including an identifier for the model in the load module name will help you identify the local and remote load modules at assembly time. For example, if you have two CBD component models, you might name your load modules with CBD1LM1, CBD1LM2, CBD2LM1, and CBD2LM2. This makes it very clear at assemble time which load modules come from CBD1 and CBD2.

There are two main methods of configuring the Load Module mapping between procedure steps that reside in different contexts:

• Build Tool Configuration—lets the user define the URLs of Load Modules that belong to procedure steps in different contexts. A list of all Load Modules referenced by the currently selected Load Modules will be displayed for configuration. The Load Module mapping must be set to the full URL of the Application Server Context

  For example:

  http://www3.ca.com/press

• WindowManagerCfgExit.java—is a source file whose default behavior returns the URL as it is passed. This exit lets the application designer define a mapping algorithm between load modules and URLs. Java code can be used to override the URL mappings that were defined during the Cross-Context configuration when assembling the application. The compiled version of WindowManagerCfgExit.java, WindowManagerCfgExit.class, will be included along with all other user exits into the runtime jar file as built by the Assemble process.