The commcfg.properties file provides the following users the ability to override the generated communication type and communications parameters at the time a given flow is executed.
#
# CA Gen
# Copyright (c) 2013 CA. All rights reserved.
#
# commcfg.properties - Communications configuration file for Gen.
#
# This file should be modified to associate TRANCODEs with the locations of
# Gen servers. It can also be used to control some runtime behaviors of
# a Gen application/proxy. This file must reside in a location where the
# JVM can load it at application execution.
#
############## 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}
#
# NOTE: Unlike the C++ implementation of commcfg.ini, the Java implementation
# of commcfg.properties does not differentiate between MQSeries local
# verses remote queue manager within this property. Thus the property
# values of MQS and MQSC are functionally identical. The local verses
# remote queue manager distinction is handled via the MQChannel and
# MQHostname properties located in the MQSeries section of this file.
# Please note the positional ordering of Queue Manager and Queue Name
# must be maintained.
#
# For ECI the format is:
# <TRANCODE>=ECI <protocol> <address> CA Portal <system> \
# {Client Security Class} {Server Security Class}
# (For ECI, <protocol> may be local, tcp, auto, http, https, or ssl.)
#
# NOTE: Unlike the C++ implementation of commcfg.ini, the Java implementation
# of commcfg.properties allows the CICS transaction id to be set to a value
# other than CPMI. More information about this can be found in the ECI
# section of this file.
#
# For EJBRMI the format is:
# <TRANCODE>=EJBRMI {Initial Factory Class} {Name Manager URL}
#
# 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)
#
# 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
#
# An MQSeries example
# ABCD=MQS myQmgr myLocalQ
# ABC*=MQS myQmgr myLocalQ
# *=MQS
#
# This example would:
# - Route an exact match of ABCD to queue manager myQmgr, local queue myLocalQ
# - Route all TRANCODEs starting with ABC (but not ABCD) to myQmgr/myLocalQ
# - Route all other TRANCODEs to myQmgr
#
###########################################
############## CACHING ####################
#
# The commcfg.properties 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 seconds 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 #(no timeout, default)
# CACHETIMEOUT=180 #(3 minute timeout)
# CACHETIMEOUT=NEVER #(cache will never be reread)
#
# 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.
#
# NOTE: Depending on how the commcfg.properties file is deployed in the
# CLASSPATH of the JVM and what the behaviors of the JVM class loader are, the
# file may never be reloaded regardless of the CACHETIMEOUT setting. Basically, the
# JVM may make its own local cache of the file after loading it once and would
# then simply never reread it no matter how frequently the application code requested
# it.
#
###########################################
#CACHETIMEOUT=0
############### TRACING ##################
#
# The commcfg.properties file can be used to enable and disable tracing within
# the proxy 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.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 specifiled file. Please make sure
# that the you have read/write permission for the same.
# CMIDEBUG=ON FILENAME
#
# The traces written to a file will be written to a file called trace.out.
# The traces written to the system will be written to standard output, which
# might be the Java Console, a command shell, or a service logfile depending
# on how the program consuming the proxy was started.
#
###########################################
#CMIDEBUG=ON
############### MQSeries ##################
#
# The commcfg.properties file can be used to modify some of the environmental
# settings used by MQSeries. In particular, these set any of the
# MQEnvironment settings. 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=myChannel
#MQHostname=localhost
#MQPort=1414
#MQUserID=myUser
#MQPassword=myPassword
############### ECI ##################
#
# Gen applications use the ECI_call_type of ECI_SYNC for the ECIRequestType of
# the ECI cooperative flow. An ECI call results in a CICS Distributed Program Link
# (DPL) call using the CICS provided Mirror Program (DFHMIRS) to invoke the requested
# Gen server. Gen ECI cooperative flows pre-set the transaction id that CICS uses to
# execute the Mirror Program to CPMI.
# In some cases it may be desirable to use a transaction id other then CPMI to refer
# to refer to the CICS Mirror Program (DFHMIRS). Setting ECIUseSyncTpn=Yes will
# result in the trancode associated with the target server application to be used as
# the transid in place of CPMI.
#
# NOTE:
# If ECIUseSyncTPN flag is used the relevant trancode must be defined in CICS to point
# to the DFHMIRS program and use profile DFHCICSA.
# This trancode cannot be shared by Gen applications using ECI and non-ECI cooperative
# flows.
#
# See the ECI documentation for the uses of the various request types.
#
###########################################
#ECIUseSyncTpn=YES
############ TUXEDO / JOLT ##############
#
# The commcfg.properties file can be used to set the Jolt System Network Address
# (JSL_NETWORK_ADDRESS) to point to the Remote System & Port Number hosting the JSL.
#
# This value in turn can be overridden by modifying the Security Exit that is
# invoked prior to the flow.
#
#########################################
#JSL_NETWORK_ADDRESS=//localhost:portNumber
|
Copyright © 2014 CA.
All rights reserved.
|
|