Tracing JCo Calls 

Use

Use this procedure to trace JCo calls coming from the SAP systems. The JCo traces write information about the invocated methods and the data passed through the underlying communication layers throughout the call.

The activation of JCo traces significantly slows down the communication. Therefore, you must only activate them on a development support request.

Procedure

...

       1.      In the J2EE Engine Visual Administrator, choose Server → Services → JCo RFC Provider →Runtime.

       2.      Choose the Special Settings tab.

Use one or more of the options below to activate different types of traces on the JCo calls:

                            a.      JCo Trace Level – you can choose the trace level from 0 to 10, where 10 is the highest and most detailed level of tracing. The JCo traces are written into folder <install_dir>\j2ee\cluster\server<xx> and have format JCO*.trc (for example, JCO050914_163247845.trc).

                            b.      JRFC Trace – a JCo tracing for a single connection. The JRFC traces are written into folder <install_dir>\j2ee\cluster\server<xx> and have format jrfc*.trc (for example, jrfc01268_05104.trc).

                            c.      Global JRFC Trace – a JCo tracing for all connections.

                            d.      CPIC Trace Level – Common Programming Interface - Communication (CPIC) tracing. This is the communication layer under JRFC (or JCo). You can choose a trace level from 0 to 3, where 3 is the highest and most detailed level of tracing.

The CPIC traces are written into <install_dir>\work\dev_server<xx> file.

                            e.      JARM – activates the Java Application Response Time Measurement trace. For more information about JARM, see Java Application Response Time Measurement.

                              f.      Local bundle – select this indicator, if you want the bundle to run only on the current cluster element.

       3.      Choose Set.