commcfg.txt

The commcfg.txt file provides the following users the ability to override the generated communication type, and communications parameters at the time a given flow is executed.
ASP.NET Web Generation clients
.NET Proxy clients
.NET Servers flowing to other CA Gen servers
# CA Gen
# Copyright (c) 2013 CA. All rights reserved.
#
#   commcfg.txt - Communications configuration file for CA Gen .NET support.
#
# This file should be modified to associate TRANCODEs with the locations of
# CA Gen servers.  It can also be used to control some runtime 
# behaviors of an CA Gen application/proxy. 
#
# The file must be placed in the application private path, the
# application base directory, a subdirectory under the application base 
# directory.
#
##############  TRANCODES #################
#
# To associate TRANCODEs with hosts, an entry must exist in this file to point
# to the associated host. The format of a line within this file is dependant
# on what communication type will be used.  <...> is required, {...} is 
# optional.
# For TCP/IP the format is:
#           <TRANCODE>=TCP <host> <service/port> {connection_persistence}
#              connection_persistence:  optional, controlled by client runtime
#                          Not Specified  -  for persistent connection
#                                     'Y' -  for persistent connections
#                                     'N' -  for non persistent connections
#
# For IMS TCP/IP Direct connect the format is:
#           <TRANCODE>=ITP <host> <service/port> {connection_persistence}
#              connection_persistence:  optional, controlled by client runtime
#                          Not Specified  -  for persistent connection
#                                     'Y' -  for persistent connections
#                                     'N' -  for non persistent connections
#
# For MQSeries (MQS) the format is:
#           <TRANCODE>=MQS {Queue Manager} {Queue Name} {Reply Queue Name}
# For MQSeries (MQI-client) the format is:
#           <TRANCODE>=MQSC {Queue Manager} {Queue Name} {Reply Queue Name}
#
# For NET the format is
#           <TRANCODE>=NET <hostName> <portNumber> <protocolCode>
#                      protocolCode can be : 'S' for Http/Soap
#                                            'B' for Http/Binary
# For Web Services the format is:
#           <TRANCODE>=WS <baseURL> <contextType>
#                     baseURL: Scheme, Domain and Port of a Web Service end point URL
#                          ex: http://<hostname>:CA Portal
#                     contextType: part of the path of a Gen Web Service end point URL
#                          'P' to use ProcedureStep Name (with WebLogic)
#                          'L' to use LoadModule Name (everywhere else)
#
#### Examples for TCP/IP
# It is possible to declare "wild-card" style TRANCODEs.  This is
# accomplished by ending the TRANCODE with a '*'.  An example use is:
#
#     ABCD=TCP myhost1 2008 N
#     ABC*=TCP myhost2 2008 Y
#     A*=TCP myhost3 2008
#     *=TCP myhost4 2008
#
# This example would:
#   - Route an exact match of ABCD to myhost1 using non persistent socket
#     connections
#   - Route all TRANCODEs starting with ABC (but not ABCD) to myhost2 using
#     persistent socket connections
#   - Route all TRANCODEs starting with A (but not ABC) to myhost3 using
#     persistent socket connections
#   - Route all other TRANCODEs to myhost4 using persistent socket connections
#
###########################################
#*=TCP localhost 2008


#### Examples for MQSeries
# It is possible to declare "wild-card" style TRANCODEs.  This is
# accomplished by ending the TRANCODE with a '*'.  An example use is:
#
#     ABCD=MQS QManager QName ReplyQName
#     ABC*=MQS QManager QName
#     A*=MQS QManager
#     *=MQS 
#
# If any items are missing (QManager, Qname, ReplyQName) the default
# values defined within the model at generation time will be used.
#
############### MQSeries MQEnvironment ##################
#
# The commcfg.txt file can be used to modify the MQSeries MQEnvironment
# class properties.  Optionally these settings may be accomplished
# programmatically via the MQSDynamicCoopFlowExit class.
#
# See the MQSeries documentation for the proper values to be used for the
# following settings.
#
#   Note:    The MQChannel and MQHostname properties are required if the target
#            Queue manager is located on a remote system. Failure to specify
#            these properties will result in a connection attempt to a locally
#            defined Queue manager. This local connection may fail if the 
#            MQSeries product is not properly configured with a local Queue
#            manager defined.
#            One symptom of this failure is MQSeries runtime dll load failures
#            if the MQSeries server software is not installed. If all Queue
#            managers are to located on remote machines, only MQSeries Client
#            software is required.
#            MQPort needs to be set to the TCP port number as defined within the
#            target queue manager configuration. A default value of 1414 will be
#            used if not overridden here.
#
###########################################
#MQChannel=DEFAULT.MQI.CHANNEL
#MQHostname=hostname
#MQPort=1414
#
# Secure Socket Layer values for MQSeries client connections
# SSLKeyRepository value should not contain a .sto suffix.
# the value "c:\mq\sslstore" implies "c:\mq\sslstore.sto"
#
#MQSSLKeyRepository=c:\mqm\sslstore
#MQSSLCipherSpec=NULL_MD5
# PeerName is an SSL Distinguished Name pattern
#MQSSLPeerName = "CN=QMGR*, OU=Company, OU=Product";
#
###########################################

############## CACHING ####################
#
# The commcfg.txt file may also be used to control how the Gen runtimes
# cache this file.  By default caching is not performed and the file is
# reread and reparsed for each flow out of the running application.  This allows
# file changes to be reflected immediately.
#
# That default behavior may not be ideal in all environments.  Therefore the
# special token 'CACHETIMEOUT' can be set to control the number of milliseconds
# to wait between rereading of the file.  All flows that occur between the read
# and the timeout use the cached version of the file in memory.  The first flow
# after the timeout has expired will force the file to be reread and the timeout
# to restart.  An example is:
#
#    CACHETIMEOUT=0      #(always timeout)
#    CACHETIMEOUT=180000 #(3 minute timeout)
#    CACHETIMEOUT=NEVER  #(cache will never be reread, default)
#
# The timeout is only useful within one process.  The NEVER setting will require
# the process to be stopped and the runtime to be unloaded before
# rereading the file.
#
###########################################
#CACHETIMEOUT=NEVER

############### TRACING ##################
#
# The commcfg.txt file can be used to enable and disable tracing within
# the runtimes.  Use the special token 'CMIDEBUG' to enable and disable
# the tracing.  Examples of the use of this token are:
#
# To turn tracing off. Default.
#        CMIDEBUG=OFF
# To turn tracing on and write to the default file: trace.{pid}.out)
#        CMIDEBUG=ON
# To turn tracing on, and write to system: standard output, which
# might be the console, a command shell, or a service logfile depending
# on how the program was started.
#        CMIDEBUG=ON SYSTEM
# To turn tracing on and write to user specified file. Please make sure
# that the you have read/write permission for the same.
#        CMIDEBUG=ON FILENAME
#
###########################################
#CMIDEBUG=ON