Specify the Connect:Direct process to start by using the ConnectDirectProcessDefinition.xml file

Specify which Connect:Direct process to start as part of a Managed File Transfer transfer. Managed File Transfer provides an XML file that we can edit to specify process definitions.

About this task

The fteCreateCDAgent command creates the file ConnectDirectProcessDefinitions.xml in the agent configuration directory MQ_DATA_PATH/mqft/config/coordination_queue_manager/agents/cd_bridge_agent_name. Before we can call user-defined Connect:Direct processes from the Connect:Direct bridge agent, we must set up process definitions by editing this file.

For each process that we want to specify to call as part of a transfer through the Connect:Direct bridge, perform the following steps:

Procedure

1. Define the Connect:Direct process that we want the Connect:Direct bridge agent to call as part of the transfer and save the process template in a file.
2. Open the MQ_DATA_PATH/mqft/config/coordination_queue_manager/agents/cd_bridge_agent_name/ConnectDirectProcessDefinitions.xml file in a text editor.
3. Create a <processSet> element.
4. Inside the <processSet> element, create a <condition> element.
5. Inside the <condition> element, create one or more elements that define a condition that the transfer request must match to call the Connect:Direct process you defined in Step 1. These elements can be either <match> elements or <defined> elements.
   • Use a <match> element to specify that the value of a variable must match a pattern. Create the <match> element with the following attributes:
     • variable - the name of the variable whose value is compared. The variable is an intrinsic symbol. For more information, see Substitution variables for use with user-defined Connect:Direct processes.
     • value - the pattern to compare to the value of the specified variable.
     • Optional: pattern - the type of pattern used by the value of the value attribute. This pattern type can be wildcard or regex. This attribute is optional and the default is wildcard.

   • Use a <defined> element to specify that a variable must have a value defined. Create the <defined> element with the following attribute:
     • variable - the name of the variable that must have a value defined. The variable is an intrinsic symbol. For more information, see Substitution variables for use with user-defined Connect:Direct processes.

   The conditions specified within the <condition> element are combined with a logical AND. All conditions must be met for the Connect:Direct bridge agent to call the process specified by this <processSet> element. If we do not specify a <condition> element, the process set matches all transfers.

6. Inside the <processSet> element, create a <process> element.
7. Inside the <process> element, create a <transfer> element. The transfer element specifies the Connect:Direct process that the Connect:Direct bridge agent calls as part of the transfer. Create the <transfer> element with the following attribute:
   • process- - the location of the Connect:Direct process that you defined in step 1. The location of this file is specified with an absolute path or relative to the MQ_DATA_PATH/mqft/config/coordination_queue_manager/agents/cd_bridge_agent_name directory.

Results

When searching for a condition match, the Connect:Direct bridge agent searches from the start of the file to the end of the file. The first match that is found is the one that is used. Parent topic: Submitting a user-defined Connect:Direct process from a file transfer request

Related information

• Connect:Direct process definition file format
• fteCreateCDAgent: create a Connect:Direct bridge agent
• Configure the Connect:Direct bridge