6.5.9 Component-type configuration file
- Organization of this subsection
(1) Format
[HCSC-component-type] ... [HCSC-component-type]
(2) Function
Specifies the types of HCSC components to output information for the user message. You can specify one HCSC component type in one line. Specify this file in the J2SE property file format.
- Reference note
-
To specify whether to output the user message traces based on HCSC component IDs, set up the component-ID configuration file.
You can set up both the component-ID configuration file and the component-type configuration file. If you specify the same HCSC component in both of these files, the setting of the component-ID configuration file will be applied.
(3) File storage location
The template file is stored in the following location:
service-platform-installation-directory\CSC\config\msg\templates\csctelegram_component_type.properties
You can store the created component-type configuration file with any name and in any location.
To enable the created component-type configuration file, specify the path in the telegramtrace-component-type-filepath property of the HCSC server runtime definition file.
(4) Specifiable parameters
HCSC-component-type
Specify the type of the HCSC component for which information is output for the user message trace. You can specify the types of HCSC components in the following table.
|
Type |
Specified value |
||
|---|---|---|---|
|
Reception |
Standard reception |
Standard reception (Web Services) |
reception.standard.soap |
|
Standard reception (SessionBean) |
reception.standard.ejb |
||
|
Standard reception (MDB (WS-R)) |
reception.standard.wsr |
||
|
Standard reception (MDB (database queue)) |
reception.standard.dbq |
||
|
User-defined reception |
SOAP reception |
reception.urecp.soap |
|
|
TP1/RPC reception |
reception.urecp.tp1 |
||
|
FTP reception |
reception.urecp.ftp |
||
|
HTTP reception |
reception.urecp.http |
||
|
Message Queue reception |
reception.urecp.mq |
||
|
File event reception |
reception.urecp.fileevent |
||
|
Custom reception |
reception.urecp.rcpfw |
||
|
Service adapter |
SOAP adapter |
adapter.soap |
|
|
SessionBean adapter |
adapter.ejb |
||
|
MDB (WS-R) adapter |
adapter.wsr |
||
|
MDB (database queue) adapter |
adapter.dbq |
||
|
DB adapter |
adapter.db |
||
|
TP1 adapter |
adapter.tp1 |
||
|
File adapter |
adapter.ff |
||
|
Object Access adapter |
adapter.oa |
||
|
Message Queue adapter |
adapter.mq |
||
|
FTP adapter |
adapter.ftp |
||
|
File operations adapter |
adapter.fop |
||
|
Mail adapter |
adapter.mail |
||
|
HTTP adapter |
adapter.http |
||
|
Command adapter |
adapter.cmd |
||
|
SFTP adapter |
adapter.sftp |
||
|
Custom adapter |
adapter.custom |
||
(5) Example of coding
-
The following shows an example of coding when information for only FTP receptions and FTP adapters is output for the user message trace.
reception.urecp.ftp adapter.ftp