The linkage properties file tells the gateway servlet where to find the web transactions and how to communicate with the web transactions. The function provided by the file is similar to the function provided by the linkage table in VisualAge® Generator Client/Server programs. This file is specified by the hptLinkageProperties parameter in the gateway servlet parameters. By default, the linkage properties are stored in the csogw.properties file in the Java™ Resources folder.
The linkage properties file contains three types of entries: application, serverLinkage, and options. Each application entry identifies one or more web transactions and is related to serverLinkage entries that indicate how to connect to those web transactions.
application.WEBUITRAN=CICS5
application.WEBUI*=CICS5
application.STF*=idaho
application.MATT*=IMSC
application.BASIC*=rtpas400
application.Z*=remoteC
serverLinkage.CICS5.commtype=CICSECI
serverLinkage.CICS5.contable=CSOE037
serverLinkage.CICS5.location=nracics5
serverLinkage.CICS5.serverid=CPMI
serverLinkage.CICS5.javaProperty=my.pkg
serverLinkage.idaho.commtype=TCPIP
serverLinkage.idaho.contable=CSOX437
serverLinkage.idaho.location=machine01
serverLinkage.idaho.serverid=9877
serverLinkage.idaho.javaProperty=my.pak
serverLinkage.IMSC.commtype=TCPIMS
serverLinkage.IMSC.contable=CSOE037
serverLinkage.IMSC.location=carimsc
serverLinkage.IMSC.tcpport=4000
serverLinkage.IMSC.javaProperty=my.pak
serverLinkage.IMSC.imsgroupid=mygroup
serverLinkage.IMSC.imsdestid=IMSC
serverLinkage.IMSC.serverid=*
serverLinkage.rtpas400.commtype=as400
serverLinkage.rtpas400.contable=CSOE037
serverLinkage.rtpas400.location=rtpas400
serverLinkage.rtpas400.javaProperty=my.pag
serverLinkage.rtpas400.library=sdearth
serverLinkage.remoteC.commtype=cicseci
serverLinkage.remoteC.contable=CSOI1252
serverLinkage.remoteC.location=CSONT2
serverLinkage.remoteC.serverid=CPMI
serverLinkage.remoteC.ctgLocation=ctghostname
serverLinkage.remoteC.ctgPort=2006
serverLinkage.remoteC.javaProperty=my.cicspkg
application.webtran=servername
The final character can be the wildcard character (*). The entry application.webui*=CICS5, for example, is used for all web transactions that start with the characters webui.
application.webui*=abc
application.webuit*=def
In this case, the second statement
is usedapplication.SERVER1=CICS5
To access a web transaction called SERVER1, the gateway servlet refers to the serverLinkage entries that are identified by CICS5.
serverLinkage.servername.parameter=value
An arbitrary name that you assign to a set of serverLinkage entries for a particular web transaction. The name must be present in an application entry.
CSOzxxxx;
The Java conversion routines convert the data in accordance with the data definitions in the UI record. For more information on conversion tables for different languages and platforms, see the VisualAge Generator Client/Server Communications Guide.
The default is the value specified for contable.
For commtype=TCPIMS, commtype=TCPIP, or commtype=AS400, specifies the TCP/IP host name of the machine where the web transaction resides.
This option is not required when using JCICS to call CICS programs residing under the same CICS region as the gateway servlet.
To avoid starting CPMI when the trans-id is not CPMI, prepend tpn_ to the trans_id. If the trans-id is WEBT, for example, specify tpn_WEBT; but if the trans-id is CPMI, specify only CPMI. If you specify WEBT without tpn_, CICS starts CPMI, which in turn switches control to WEBT.
For commType=JCICS, specifies the CICS trans-id for the catcher in the remote CICS region (default is CPMI). The trans-id you specify must point to DFHMIRS. This option is ignored when using JCICS to call CICS programs residing under the same CICS region as the gateway servlet.
For commtype=TCPIP, serverid specifies the port number of the listening socket on the machine where the web transaction resides.
For commtype=TCPIMS, serverid specifies the IMS transaction code. If you set serverid=*, the value of servername is used as the transaction code.
For commtype=AS/400, serverid is not used.
This entry lets you dynamically put into effect any changes made to the linkage properties file, without your being required to stop and start the web application server. Web transactions initiated after the inspection are invoked with the new values. A value of 0 indicates that the gateway servlet reviews the linkage properties file only at startup.