Optimize for Infrastructure Version 9.7
 —  Guide for Enterprise Transaction Systems  —

Tracing the EntireX Communication in the Infrastructure Data Collector

This document covers the following topics:


Activating the Trace

You activate the trace by configuring the ETS Resource Module settings of the Infrastructure Data Collector. For detailed information, see Defining ETS Resource Module Settings in the Configuring BAM guide.

You can change the default value of the Trace Level property to any values described below.

Top of page

Trace Levels

Logging for the EntireX communication is enabled with one of the following trace levels.

Trace Level 6

With trace level 6, each call between the data collector package and EntireX Broker is logged.

Trace Level 7

With trace level 7, each call and the data between the data collector package and EntireX Broker is logged.

Top of page

Location of the Log File

The trace data is written to a file which has the following name:

entirexyyyymmdd.log

This file is located in the following directory:

installation-directory\profiles\InfraDC\logs

Top of page

Reading the Output

Trace Level 6

Example:

2009-09-14 00:06:07.776/PollThreads:MyHost:1971 
SEND(BID=MyHost:1971,UID=OPTIMIZE,CID=NEW,SC=SAG,SN=ETBCIS,SV=INFO,W=5S,
SL=559,RL=7168,LS=CP1252,API=9,XRL=0,ANODE=MyHost,ATYPE=Java,AVERS=8.0.1.20,
ANAME=Java Runtime,ETXL=256,PU=09Sep13-030944-000000-00000J)

2009-09-14 00:06:07.776/PollThreads:MyHost:1971   SEND returns: 
CID=10000000000003QP,EC=00000000,RETL=112,SEQID=9237,UOWST=RECV_NONE,
TXT=Successful response

This means, the data collector for MyHost:1971 sends 559 bytes to the server SAG/ETBCIS/INFO. EntireX Broker returns 112 bytes and confirms.

Trace Level 7

Example:

2009-09-21 14:34:55.548/Thread-87 
SEND(BID=MyHost:1973,UID=dba,CID=NONE,SC=RPC,SN=OPT_SERVER,
SV=CALLNAT,W=60S,SL=357,RL=7168,LS=CP1252,API=9,XRL=0,ANODE=MyHost,
ATYPE=Java,AVERS=8.0.1.20,ANAME=Java Runtime,ETXL=256,RPCPGM=OPTDISC,
PU=09Sep20-031855-000000-00000D)
2009-09-21 14:34:55.548/Thread-87 Sending Data 357 bytes:
00000000     32303230 2A525043  2A303030 30303030  |2020*RPC*0000000|
00000010     30393230 30303030  30303038 36303030  |0920000000086000|
00000020     30303030 31373830  30303030 30303131  |0000178000000011|
00000030     36303030 30303030  32393430 30303030  |6000000029400000|
00000040     30303036 33303030  30303030 30202020  |0006300000000   |
00000050     4E433030 30303030  30303135 4C423D30  |NC0000000015LB=0|
00000060     2C554944 3D332C64  6261504D 3D372C4F  |,UID=3,dbaPM=7,O|
00000070     50544449 53435054  3D35342C 456E7469  |PTDISCPT=54,Enti|
00000080     72655820 4A617661  20525043 20436C69  |reX Java RPC Cli|
00000090     656E7420 382E302E  312E3230 2057696E  |ent 8.0.1.20 Win|
000000A0     646F7773 20323030  3320352E 32207838  |dows 2003 5.2 x8|
000000B0     362E4D49 342C304D  49342C30 4F412856  |6.MI4,0MI4,0OA(V|
000000C0     29302C30 4F49342C  304F4934 2C305349  |)0,0OI4,0OI4,0SI|
000000D0     342C3053 41285629  302C3053 47285529  |4,0SA(V)0,0SG(U)|
000000E0     312C312C 30534128  5629302C 30534128  |1,1,0SA(V)0,0SA(|
000000F0     562C5529 302C302C  30534728 5529322C  |V,U)0,0,0SG(U)2,|
00000100     312C3053 4128562C  5529302C 302C3053  |1,0SA(V,U)0,0,0S|
00000110     4128562C 5529302C  302C3053 47322C30  |A(V,U)0,0,0SG2,0|
00000120     5347312C 302E2B30  30303030 30303030  |SG1,0.+000000000|
00000130     312B3030 30303030  30303031 31362C4F  |1+000000000116,O|
00000140     50545F57 42453120  73727677 6265312B  |PT_SERVER MyHost|
00000150     30303030 30303030  30372B30 30303030  |+0000000007+0000|
00000160     30303030 30                           |000000           |

2009-09-21 14:34:55.548/Thread-87 Received Data 313 bytes:
00000000     32303230 2A525043  2A303030 30303030  |2020*RPC*0000000|
00000010     30393630 30303030  30303231 37303030  |0960000000217000|
00000020     30303030 30303030  30303030 30303030  |0000000000000000|
              -same as above-
00000040     30303030 30303031  32363937 35202020  |0000000126975   |
00000050     4E433030 30303030  30303030 20202020  |NC0000000000    |
00000060     4E443D39 302C3135  30365365 72766572  |ND=90,1506Server|
00000070     30323031 30312C20  20202020 20202020  |020101,         |
00000080     20202020 20202020  20202020 20202020  |                |
              -same as above-
000000C0     45543D35 392C4F50  54444953 43202039  |ET=59,OPTDISC  9|
000000D0     39393920 4E415436  39373520 53656375  |999 NAT6975 Secu|
000000E0     72697479 20657272  6F72206F 6E205365  |rity error on Se|
000000F0     72766572 2C207265  61736F6E 2031202C  |rver, reason 1 ,|
00000100     2E4E453D 31382C30  312C4F50 54444953  |.NE=18,01,OPTDIS|
00000110     43203939 39393031  4F50543D 32362C4E  |C 999901OPT=26,N|
00000120     61747572 616C2052  50432053 65727665  |atural RPC Serve|
00000130     72205250 43363333  2E                 |r RPC633.       |
2009-09-21 14:34:55.548/Thread-87   SEND returns: EC=00000000,RETL=313,
SEQID=62,UOWST=RECV_NONE,TXT=Successful response
2009-09-21 14:34:55.548/Thread-87 Broker Error 1001 0012: OPTDISC  
9999 NAT6975 Security error on Server, reason 1 ,., NE=01,OPTDISC 999901O

Here, we see that the data collector tries an OPTDISC call to the server OPT_SERVER and gets a security error.

Top of page