Patterns: Implementing Self-Service in an SOA Environment

Chapter 12. J2EE Connector Architecture scenario 441

2. Compile the MARTACCT.ccp file and add MARTACCT.ibmcob file in the bin

directory for the CICS region.

3. Start the region.

4. Test the program using the Local CICSTERM program.

12.6 System management guidelines for JCA

This section provides system management guidelines for J2EE

Connector-enabled applications and the underlying CICS environment. We look

at the following topics:

򐂰 12.6.1, “Logging and tracing” on page 441

򐂰 12.6.2, “Performance monitoring and tuning” on page 442

򐂰 12.6.3, “Scalability and availability considerations” on page 444

򐂰 12.6.4, “Security considerations” on page 448

12.6.1 Logging and tracing

It is often helpful to examine log and trace files when your application

experiences J2EE Connector errors or problems.

Application logging

It is always important for applications to record their activity to a logging facility.

When you write a log to the standard output file or standard error file, the

application server will record it to the corresponding log files.

Connection factory trace

Connection factory classes can be traced using the WebSphere Application

Server trace service. The trace level can also be set as a connection factory

property in WebSphere administrative console.

Connection factory tracing is often not particularly helpful when debugging the

CICS interaction. CICS TG tracing is usually the better option.

CICS TG trace

CICS Transaction Gateway (CICS TG) trace records detail activities of the CICS

TG gateway daemon, such as the processing of ECI requests from clients. The

four levels of tracing are: