|
Log trace
|
methodtrace-filepath
|
Method trace/exception log output destination path
|
Y
|
Y
|
Y
|
|
requesttrace-filepath
|
Request trace output destination path
|
Y
|
Y
|
Y
|
|
telegramtrace-filepath
|
User message trace output destination path
|
Y
|
Y
|
Y
|
|
methodtrace-filenum
|
Maximum number of method trace files
|
Y
|
Y
|
Y
|
|
requesttrace-filenum
|
Maximum number of request trace files
|
Y
|
Y
|
Y
|
|
telegramtrace-filenum
|
Maximum number of user message trace files
|
Y
|
Y
|
Y
|
|
bpacttrace-filenum
|
Maximum number of activity trace files for business processes
|
Y
|
Y
|
Y
|
|
methodtrace-filesize
|
Maximum size of 1 method trace file
|
Y
|
Y
|
Y
|
|
requesttrace-filesize
|
Maximum size of 1 request trace file
|
Y
|
Y
|
Y
|
|
telegramtrace-filesize
|
Maximum size of 1 user message trace file
|
Y
|
Y
|
Y
|
|
bpacttrace-filesize
|
Maximum size of each activity trace file for business processes
|
Y
|
Y
|
Y
|
|
bpacttrace-extend-item
|
Additional output item in the activity trace files for business processes
|
Y
|
Y
|
Y
|
|
telegramtrace-trigger
|
Trigger for output of user message trace
|
Y
|
Y
|
Y
|
|
telegramtrace-component-type-filepath
|
Path of the component-type configuration file for the user message trace
|
Y
|
Y
|
Y
|
|
telegramtrace-component-id-filepath
|
Path of the component-ID configuration file for the user message trace
|
Y
|
Y
|
Y
|
|
methodtrace-level
|
Method trace output level
|
Y
|
Y
|
Y
|
|
requesttrace
|
Existence of request trace extraction
|
Y
|
Y
|
Y
|
|
telegramtrace
|
Existence of user message trace extraction
|
Y
|
Y
|
Y
|
|
bpacttrace
|
Whether to collect the activity trace for business processes
|
Y
|
Y
|
Y
|
|
bptrace-level
|
Output level of method trace of business process infrastructure
|
Y
|
Y
|
Y
|
|
bptrace-filenum
|
Number of method trace files of business process infrastructure
|
Y
|
Y
|
Y
|
|
bptrace-filesize
|
Size of method trace of business process infrastructure
|
Y
|
Y
|
Y
|
|
bpexptrace-filenum
|
Number of exception log files of business process infrastructure
|
Y
|
Y
|
Y
|
|
bpexptrace-filesize
|
Size of exception log files of business process infrastructure
|
Y
|
Y
|
Y
|
|
cscexptrace-filenum
|
Number of exception log files of messaging infrastructure
|
Y
|
Y
|
Y
|
|
cscexptrace-filesize
|
Size of exception log files of messaging infrastructure
|
Y
|
Y
|
Y
|
|
Standard reception relation
|
request-ejb.instance.minimum
|
Minimum number of instances of standard synchronous reception (SessionBean)
|
Y
|
Y
|
Y
|
|
request-ejb.instance.maximum
|
Maximum number of instances of standard synchronous reception (SessionBean)
|
Y
|
Y
|
Y
|
|
request-ejb.ctm
|
Existence of use of CTM integration
|
Y
|
Y
|
Y
|
|
request-ejb.parallel.count
|
Number of threads prepared for invocation of application by CTM
|
Y
|
Y
|
Y
|
|
request-ejb.optional.name
|
Optional name of standard synchronous reception (SessionBean)
|
Y
|
Y
|
Y
|
|
request-soap.instance.minimum
|
Minimum number of simultaneous executions of standard synchronous reception (Web service or SOAP1.1)
|
Y
|
Y
|
Y
|
|
request-soap.instance.maximum
|
Maximum number of simultaneous executions of standard synchronous reception (Web service or SOAP1.1)
|
Y
|
Y
|
Y
|
|
request-soap.exclusive.threads
|
Number of dedicated threads of standard synchronous reception (Web service or SOAP1.1)
|
Y
|
Y
|
Y
|
|
request-soap.queue-size
|
Size of pending queue of standard synchronous reception (Web service or SOAP1.1)
|
Y
|
Y
|
Y
|
|
request-soap1_2.instance.minimum
|
Minimum number of simultaneous executions of standard synchronous reception (Web service or SOAP1.2)
|
Y
|
Y
|
Y
|
|
request-soap1_2.instance.maximum
|
Maximum number of simultaneous executions of standard synchronous reception (Web service or SOAP1.2)
|
Y
|
Y
|
Y
|
|
request-soap1_2.exclusive.threads
|
Number of dedicated threads of standard synchronous reception (Web service or SOAP1.2)
|
Y
|
Y
|
Y
|
|
request-soap1_2.queue-size
|
Size of pending queue of standard synchronous reception (Web service or SOAP1.2)
|
Y
|
Y
|
Y
|
|
request-jms.instance.maximum
|
Maximum number of instances of standard asynchronous reception (MDB(WS-R))
|
N
|
Y
|
N
|
|
request-jms.rollback-count
|
Number of times that rollback warning message of standard asynchronous reception (MDB(WS-R)) is output
|
N
|
Y
|
N
|
|
receptionstop-monitor-timer
|
Timeout time of reception queue monitoring
|
N
|
Y
|
N
|
|
csc-receptionstop-timeout
|
Communication timeout time of reception end standby
|
Y
|
Y
|
Y
|
|
Service adapter relation
|
soapfault-targetnamespace-filepath
|
Whether to handle SOAP Fault as a user-defined exception
|
Y
|
Y
|
Y
|
|
soapfault-handling-mode
|
Selection of the operation mode of the fault determination processing to be used if a received message includes a SOAP fault
|
Y
|
Y
|
Y
|
|
oa-adapter-character-code
|
Character encoding of messages to be exchanged between the Object Access adapter and a service component
|
Y
|
Y
|
Y
|
|
Data transformation relation
|
formatdef-maxcache-num
|
Number of format definitions that can be cached
|
Y
|
Y
|
Y
|
|
transformdef-maxcache-num
|
Number of data transformation definitions that can be cached
|
Y
|
Y
|
Y
|
|
xmltelegram-maxcache-num
|
Number of XML messages that can be cached
|
Y
|
Y
|
Y
|
|
telegram-validation
|
Whether or not to validate whether sending and receiving messages is suitable for the message format
|
Y#
|
Y#
|
Y
|
|
xmltelegram-namespace-complement
|
Whether to supplement the name space declaration corresponding to the name space prefix specified in the attribute value in
XML message
|
Y
|
Y
|
Y
|
|
telegram-undefined-character-code
|
Whether to continue the process if an undefined character code is detected in the character code conversion process of binary
data
|
Y
|
Y
|
Y
|
|
telegram-notfound-soapheader
|
Whether to continue the process if the header specified in sent and received messages does not exist for the reception definition
file, service adapter definition file or business process definition file
|
Y
|
Y
|
Y
|
|
validation-activity
|
Whether to validate the message type variable (XML) by validation activity
|
Y
|
Y
|
Y
|
|
transform-binary-error-check
|
Whether to check errors during binary data transformation
|
Y
|
Y
|
Y
|
|
code-table-root-path
|
Absolute path of the root path of the code conversion table storage path
|
Y
|
Y
|
Y
|
|
Business process relation
|
syserr-to-fault-convert
|
Whether to cause universal fault if a system exception occurs in data transformation activity, assign activity or switch activity
|
Y
|
Y
|
Y
|
|
validate-fault-compatible
|
Whether the fault message format sent by validation fault is to be in the format used in 09-00 or lower
|
Y
|
Y
|
Y
|
|
bp-reply-after-min-thread-pool-size
|
Minimum number of threads used to perform activities after response activity
|
Y
|
Y
|
Y
|
|
bp-reply-after-max-thread-pool-size
|
Maximum number of threads used to perform activities after response activity
|
Y
|
Y
|
Y
|
|
bp-reply-after-thread-pool-keep-alive
|
Maintenance time of threads used to perform activities after response activity
|
Y
|
Y
|
Y
|
|
service-emulate.enable
|
Whether to perform service emulation
|
Y
|
Y
|
Y
|
|
service-emulate-def-filepath
|
Absolute path of the definition file for emulated configuration information
|
Y
|
Y
|
Y
|
|
J2EE relation
|
j2ee-stopapp-timeout
|
Monitoring time when J2EE application stops
|
Y
|
Y
|
Y
|
|
startcsc-timeout
|
Monitoring time when J2EE server starts
|
Y
|
Y
|
Y
|
|
stopcsc-timeout
|
Monitoring time when J2EE server stops
|
Y
|
Y
|
Y
|
|
Monitoring command communication timeout time
|
csc-command-timeout
|
Command communication timeout time
|
Y
|
Y
|
Y
|
|
csc-precache-timeout
|
EJB communication timeout in the business process for advance cache process
|
Y
|
Y
|
Y
|
|
Cookie information inheritance
|
cookie-parsing
|
Whether to inherit Cookie
|
Y
|
Y
|
Y
|
|
Folder relation
|
work-folder
|
Absolute path of operation folder route
|
Y
|
Y
|
Y
|
|
common-folder-<Common folder definition name>
|
Absolute path of common folders
|
Y
|
Y
|
Y
|
|
DB adapter relation
|
dba-separate-transaction
|
Whether to start DB adapter transaction separately from the business process
|
Y
|
Y
|
Y
|
|
Component common UOC relation
|
common-uoc-prop-path
|
Property file storage folder for component common UOC
|
Y
|
Y
|
Y
|
|
HCSC server relation
|
short-processid-servername
|
HCSC server name identifier used by process instance identifier
|
Y
|
Y
|
Y
|
|
short-processid
|
Whether to reduce process instance identifier
|
Y
|
Y
|
Y
|
|
Instance pool
|
xml-pooled-instance-minimum
|
Minimum number of instance pools of the class used in XML process
|
Y
|
Y
|
Y
|
|
xml-pooled-instance-maximum
|
Maximum number of instance pools of the class used in XML process
|
Y
|
Y
|
Y
|
|
Custom reception related
|
request-id-separate-key
|
New request ID split key
|
Y
|
Y
|
Y
|
|
File event related
|
fileevent-reception.monitored-file.enabled
|
Whether to enable the file monitoring function
|
Y
|
Y
|
Y
|
|
fileevent-reception.monitored-folder
|
Path of the monitoring-target folder
|
Y
|
Y
|
Y
|
|
fileevent-reception.monitor-interval
|
File monitoring interval
|
Y
|
Y
|
Y
|
|
fileevent-reception.monitor-starting.delay
|
Time to wait before the file monitoring starts
|
Y
|
Y
|
Y
|