IBM CICS Transaction Gateway Connector

Click the popup and check for available updates. 

Click the Connector version checkbox, click Next, and follow the instructions provided by the user interface. 

Restart Studio when prompted. 

After restarting, when creating a flow and using the connector, if you have several versions of the connector installed, you may be asked which version you would like to use. Choose the version you would like to use.

Create a new Mule Project in Anypoint Studio and fill in the IBM CTG credentials in src/main/resources/mule-app.properties.

  
1
2
3
4
5

  
ctg.host=<HOST>
ctg.port=<PORT>
ctg.serverName=<SERVER_NAME>
ctg.username=<USERNAME>
ctg.password=<PASSWORD>

Drag an HTTP connector onto the canvas and leave the default values for Host and Port and set the path to /test/ec01.

Drag an IBM CTG component onto the canvas and add a new Global Element to configure a standard (non-SSL) connection.

Double-click the IBM CTG component, select the operation Execute and configure the following parameters:

Add a Transform Message between the HTTP and the IBM CTG components. The connector does not provide dynamic/static metadata but allows users to define custom types using the Metadata Type tool.

Add a Transform Message after the IBM CTG to extract the results in a JSON format.

  
1
2
3
4
5
6
7

  
%dw 1.0
%output application/json
---
{
        date: payload[0].LK-DATE-OUT,
        time: payload[0].LK-TIME-OUT
}

Add a Logger at the end of the flow.

Save the changes and deploy the Mule Application. Open a browser and make a request to http://localhost:8081/ec01. The result should be similar to:

{
    date: "06/09/17",
    time: "13:41:17"
}

Perform steps 1 to 3 from the previous example and set the HTTP path to /ec03.

Double-clic the IBM CTG component, select the operation Execute and configure the following parameters:

Add a Transform Message between the HTTP and the IBM CTG components.

Add a Transform Messager after the IBM CTG to convert the result into readable format.

Add a Logger at the end of the flow.

Save the changes and deploy the Mule Application. Open a browser and make a request to http://localhost:8081/ec03. The result should be similar to:

{
   cics-date-time: "06/09/2017 13:57:25"
}

Perform steps 1 to 3 from the previous example and set the HTTP path to /test/ec02.

In the Global Elements tab, add a new Bitronix Transaction Manager without further configurations.

Drag a Transactional element next to the HTTP and configure according to the table below:

Double-clic the IBM CTG component, select the operation Execute using COMMAREA and configure the following parameters:

Add a Transform Message between the HTTP and the IBM CTG components. The connector does not provide dynamic/static metadata but allows users to define custom types using the Metadata Type tool.

Add a Transform Message after the IBM CTG to extract the results in a JSON format.

  
1
2
3
4
5
6
7

  
%dw 1.0
%output application/json
---
{
        count: trim payload[0].LK-COUNT,
        lowVal: payload[0].LK-LOWVAL
}

Add a Logger at the end of the flow.

Save the changes, deploy the Mule Application. Open a browser and make a request to http://localhost:8081/ec02. The result should be similar to:

{
    count: "000001235TH RUN OF EC02",
    lowVal: null
}

Place a schema file under src/main/resources directory, normally in .ffd format.

Go to the Metadata tab of the connector operation and click the Add metadata button.

Click Add to create a new type and provide and ID for it (i.e. ec01-in-type for the program EC01 input data).

Select type Copybook, then Schema and provide the location of the schema file.

This will populate a drop-down with a list of available data segments. Choose the one you need and click the Select button to save the configuration.

Drag a DataWeave transformer before the IBM CTG component. Metadata fields will become available to build the mapping.