Adapter trace

Hi experts!
I am developing an adapter on PI 7.0 that complains with JCA 1.0, based on sampleAdapter delivered by SAP.
A lot of trace calls are made on my code: trace.entering(...), trace.exiting(...), trace.catching(...) but none of them appear at nwa logs.
The file structure of MyAdapter.sda is the following:
META-INF\application-j2ee-engine.xml
META-INF\application.xml
META-INF\log-configuration.xml
META-INF\MANIFEST.MF
META-INF\SAP_MANIFEST.MF
META-INF\sda-dd.xml
MyAdapter.rar
And the structure of MyAdapter.rar is:
META-INF\connector-j2ee-engine.xml
META-INF\MANIFEST.MF
META-INF\ra.xml
MyAdapter.jar
When I make the deploy at Visual Administrator, I can see the tab Log Configurator with the data of log-configuration.xml that is on sda:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">
<log-configuration>
     <log-formatters>
          <log-formatter
               name="trc"
               pattern="%26d %150l [%t] %10s: %m"
               type="TraceFormatter"/>
     </log-formatters>
     <log-destinations>
          <log-destination
               count="5"
               effective-severity="ALL"
               limit="2000000"
               name="MyAdapter.trc"
               pattern="./log/applications/mycompany.MyAdapter/default.trc"
               type="FileLog">
               <formatter-ref name="trc"/>
          </log-destination>
     </log-destinations>
     <log-controllers>
          <log-controller
               name="mycompany.MyAdapter"
               effective-severity="ALL">
               <associated-destinations>
                    <destination-ref
                         association-type="LOG"
                         name="MyAdapter.trc"/>
               </associated-destinations>
          </log-controller>
     </log-controllers>
</log-configuration>
At Service > Log Configurator >Locations, I can also see those configured values. But nothing is logged on trace.
Is there something missing?

Hi, Soctt,
Go to the J2ee Visual Admin tool. Check the service Log configurator. Go to the RFC adapter file and set the trace level to debig mode. Save it. Noe try to test your sceanrio and check the file system for the traces...You have more info from the trace now.
Looks like you have a problem with the data you trying to send thorouch XI.
Regards
Prasad

Similar Messages

  • OS commands from File adapter Trace logs?

    Hi All,
    I am running some UNIX OS commands from File adapter as showing in below Blog.
    Problem is that in SXMB_MONI & in Runtime workbench I can not see any Trace logs written by those UNIX OS commands.
    Even I am writing echo messages.
    Runtime Workbench says only OS command file executed.
    Please guide me where I can see OS trace if some OS command fails?
    Any transaction code even at BASIS level exist?
    Or the only other way round exist is I need to write log into some files.
    /people/daniel.graversen/blog/2008/12/11/sftp-with-pi-the-openssh-way
    I am using PI7.1.
    Regards

    I think no solution, other then writing ABAP code using RFC SXPG_COMMAND_EXECUTE and put log/trace in some table/application.

  • RFC Adapter Trace!

    Hi Everybody,
    I'm currently trying to debug a problem with the RFC adapter. Is there a flag that can be set that would allow me to see the actual JCO code being executed by the RFC adapter? I'm in a situation where the RFC is being executed and it's generating an error message but it seems to be data related...however, the data in the XML looks correct so I need to see how the RFC adapter is interpreting the XML message. Of course, I'm definitely open to any other ideas that you may have.
    Thanks alot,
    ...Scottd
    p.s.I'm using XI 3.0!

    Hi, Soctt,
    Go to the J2ee Visual Admin tool. Check the service Log configurator. Go to the RFC adapter file and set the trace level to debig mode. Save it. Noe try to test your sceanrio and check the file system for the traces...You have more info from the trace now.
    Looks like you have a problem with the data you trying to send thorouch XI.
    Regards
    Prasad

  • JDBC adapter trace logs

    We turned on the trace in visual administration tool for JDBC adapter thro' VA>Service>Log configuration>>locations>>com>>sap>>aii>>adapter>>JDBC.
    Where should I look in visual adminitration tool for the trace log for JDBC adapter?
    We are using Acknowledgment=Transport in Asynchonous "SEND" step of BPM to receive acknowlegement of updating database.
    It is updating database but in Tcode-SXMB_MONI, Ack Status = ? "still waiting acknowledgement"
    Can someone please help me to figure out where should I look for JDBC logs and why we are not able to receive acknowlegement?
    Thanks in advance!
    Mrudula

    Hi,
    - log on to the Visual Administrator
    - start service - Log Viewer
    - cluster -> server -> logs
    - choose defaultTrace.trc
    did you set tracing level to debug for JDBC adapter..
    Cheers,
    Naveen

  • Sample adapter Trace

    Hi. Can anyone tell me how to view the Trace or log file for the sample adapter (sample_ra.sda). I would like to know the location to which the trace is written out and also the severity level.
    --Jai

    Hi,
    a) In order to trace the message you have go to runtime workbench
    b) Select message monitoring
    c) Select message press  detail display where in you can see and trace ur message
    Regards,
    G.Varun Kumar

  • WS To IDOC"CONTENTS OF TRACE IN SXMB_MONI"

    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external =</Trace>
      <Trace level="1" type="T">Sender agency external =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
      <Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>
      <Trace level="2" type="T">Host = pitest.monet.local:8001</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
      <Trace level="2" type="T">Remote address = 10.10.10.26</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
      <Trace level="3" type="T">Getting type of XMB...</Trace>
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
      <Trace level="3" type="T">No triggers found. OK.</Trace>
      </Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="3" type="T">system-ID = PIT</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 5026E2B502F9F54DBD148EDBC5DF0C28</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = 5026E2B502F9F54DBD148EDBC5DF0C28</Trace>
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTI0008</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = 5026E2B502F9F54DBD148EDBC5DF0C28</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">OK.</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = PIT</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - ERP_D_ADR200</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 001</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) ERP_D_ADR200 ATT_ABS.ATT_ABS01</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: ATT_ABS.ATT_ABS01</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="2" type="T">got property produced by receiver determination</Trace>
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO4___0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
      <Trace level="2" type="T">Increment log sequence to 005</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = PIT</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Begin of pipeline processing PLSRVID = CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 5BAFC07158603569AB7C47D94F4A8927</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 1D47292048CD11DB8AD9FDDE0A0A0A5E</Trace>
      <Trace level="1" type="T">Interface Mapping http://www.gemsconsult.com/LAB_ABA/pcp/wstoidoc PublishLeaveStatus_2_ATT_ABS</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_.</Trace>
      <Trace level="3" type="T">Load 1d472920-48cd-11db-8ad9-fdde0a0a0a5e, http://www.gemsconsult.com/LAB_ABA/pcp/wstoidoc, -1, com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_.class.</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_.class (http://www.gemsconsult.com/LAB_ABA/pcp/wstoidoc, -1) in swcv 1d472920-48cd-11db-8ad9-fdde0a0a0a5e.</Trace>
      <Trace level="3" type="T">Loaded class com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_ completed. (executeStep() of com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 005</Trace>
      <Trace level="3" type="T">Message version 005</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
      <Trace level="2" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
      <Trace level="2" type="T">-KCRS_3RDP_D</Trace>
      <Trace level="2" type="T">-ERP_D_ADR200</Trace>
      <Trace level="2" type="T">urn:sap-com:document:sap:idoc:messages.ATT_ABS.ATT_ABS01</Trace>
      <Trace level="2" type="T">Channel found: - ERP_D_ADR200 - IDOC_OUT_ADR200</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 006</Trace>
      <Trace level="3" type="T">Message version 006</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS =</Trace>
      <Trace level="3" type="T">P_IFNAME =</Trace>
      <Trace level="3" type="T">P_METHOD =</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Channel for IDOC adapter: IDoc</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = IDOC</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS = CL_IDX_IDOC_SERVICE</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">---- Outbound IDoc-Adapter -
    </Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
      <Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
      <Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
      <Trace level="2" type="T">RFCDEST : ADR_200</Trace>
      <Trace level="2" type="T">Port : SAPADR</Trace>
      <Trace level="2" type="T">Docrel :</Trace>
      <Trace level="2" type="T">Version : 3</Trace>
      <Trace level="2" type="T">Saprel : 700</Trace>
      <Trace level="2" type="T">Queue-ID:</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
      <Trace level="1" type="T">Sender service KCRS_3RDP_D</Trace>
      <Trace level="1" type="T">Receiver service ERP_D_ADR200</Trace>
      <Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
    - <Trace level="1" type="B" name="IDX_XML_TO_IDOC">
      <Trace level="1" type="T">Parse XML-BODY</Trace>
      <Trace level="1" type="T">Get the Metadata for port SAPADR</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
      <Trace level="2" type="T">Port : SAPADR</Trace>
      <Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
      <Trace level="2" type="T">Cimtyp :</Trace>
      <Trace level="2" type="T">Release :</Trace>
      <Trace level="2" type="T">Version : 3</Trace>
      <Trace level="2" type="T">Direction : 2</Trace>
      <Trace level="2" type="T">SAPREL : 700</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="1" type="T">Convert one IDoc</Trace>
      <Trace level="2" type="T">Convert Control Record</Trace>
      <Trace level="2" type="T">Convert Data Records</Trace>
      <Trace level="3" type="T">Segment= E1BP7011_1</Trace>
      <Trace level="2" type="T">Number of found Data records: 1</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
      <Trace level="2" type="T">Port : SAPADR</Trace>
      <Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
      <Trace level="2" type="T">Cimtyp :</Trace>
      <Trace level="2" type="T">RFC-Dest :</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>
      </Trace>
      <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
      <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
    - <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">
      <Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= ADR_200</Trace>
      <Trace level="2" type="T">Used TID = 0A0A0A57187045C0420A1468</Trace>
      </Trace>
      <Trace level="2" type="T">TID : 0A0A0A57187045C0420A1468</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 007</Trace>
      <Trace level="3" type="T">Message version 007</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="T">Async processing: skip mapping of response</Trace>
      </Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Async processing completed OK.</Trace>
      <Trace level="3" type="T">system-ID = PIT</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-31T07:15:22Z CST</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 003</Trace>
      <Trace level="3" type="T">Message version 008</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>

    Hi,
    What you want.
    Regards
    Chilla..

  • J2SE file adapter

    i,
    When I post a XI message via SAP PI 7.10 SP7 integration server to a J2SE adapter engine to a file adapter, then when I use mode "XMB2FILE" in the receiver file adapter configuration on the J2SE Adapter Engine then the XML file is delivered into the appropriate folder with the correct XML format and content (As expected). However when I change the mode to XMB2FILEWITHCONVERSION then message fails in the integration Engine on the PI server.
    With:
    <Trace level="2" type="T">Addressing mode: url</Trace>
      <Trace level="3" type="T">Host = "HOST"</Trace>
      <Trace level="3" type="T">Port = 8111</Trace>
      <Trace level="3" type="T">Transport protocol = HTTP 1.0</Trace>
      <Trace level="3" type="T">Message protocol =</Trace>
      <Trace level="3" type="T">Path = /file/receiver?action=execute&pipelineid=Receiver</Trace>
      <Trace level="2" type="T">Auth mode: basicNonSAP</Trace>
      <Trace level="3" type="T">Conversion of language from char2 to char1</Trace>
      <Trace level="3" type="T">User = rip</Trace>
      <Trace level="3" type="T">Client =</Trace>
      <Trace level="3" type="T">Language =</Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Security: Basic authentication</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 500</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="3" type="System_Error">Error while sending by HTTP (error code: 500, error text: Internal Server Error:java.lang.NullPointerException)</Trace>
      </Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Persist Message in Retry State</Trace>
    A file is created in the target folder with no content and each time PI retries a new file is created.
    If I look at the J2SE adapter trace file the following error is displayed:
    Apr 3, 2009 3:05:03 PM   ...i.messaging.adapter.XMB2FileProcessor [Thread[Thread-1145,5,main]] Error: Message processing failed with
    java.lang.NullPointerException
         at com.sap.aii.af.sdk.xi.adapter.Conversion.convertXML2Plain(Conversion.java:621)
         at com.sap.aii.messaging.adapter.XMB2FileProcessor.persistFile(ModuleXMB2File.java:1658)
         at com.sap.aii.messaging.adapter.XMB2FileProcessor.onMessage(ModuleXMB2File.java:1346)
         at com.sap.aii.messaging.adapter.ModuleHttpServer$ListenerDetails.onMessage(ModuleHttpServer.java:448)
         at com.sap.aii.af.sdk.xi.net.HTTPRequest.run(ServerHttpImpl.java:437)
    Please can you assist in the resolution of this problem?
    Regards
    Willie Hugo

    Hi Stefan,
    Thank for the prompt reply. I am sending the XI message to a plain J2SE Adapter Engine. As I under stand the process, the XI message XML to flat file conversion will take place in the J2SE Adapter Engine in the File Adapter, configured there. If I under stand correctly we need to deploy a patch to the J2SE Adapter Engine and the note refers to XI 3.00 & 7.00, these Adapter Engines I can only assume is J2EE. Also the scenario described in the note is from csv to XML and not the required XML to CSV.
    Please can you assist further?
    Regards
    Willie Hugo

  • RFC receiver adapter issue - ECC side we are seeing blank data for the RFC

    Hi All,
    We are using Receiver RFC adapter to call a custom RFC (Synchronous call). It was working fine, but recently RFC was modified (They added new fields). We re-imported the RFC into ESR and also modified the mapping to reflect the new RFC strucuture. Now when we execute the RFC, at the ECC side no data is beeing seen. On the PI side we see data in sxmb_moni. It looks fine. However we don't see anydata in ECC.  We did full cache refresh but it did not help.
    Please let me know if anyone has any thoughts on this issue.
    Thanks
    -Pradeep

    I enabled the the RFC adapter trace in PI. It appears like adapter is not sending the structure and tabled that are populated. IT is sending only 230 bytes. Any clue why would rfc adapter drop the tables and structures??
    FUNCTION Z_FI_AA_BAPI_ASSET_CHANGE
        handle = 2
        parameter   = <null>
        parameter   = <null>
        tables = <null>
    >>>> [2] <unknown> EXT <ac: 6> >>> FLUSH (READ) (88578752)
    Send RFCHEADER [2]: 01/BIG/IEEE/SPACE-U2/52494850
    Send UNICODE-RFCHEADER [2]: cp:4102/ce:IGNORE/et:6/cs:2/rc:0x00000023
    UUID: send_rfcuuid B6D708F0-B946-11E0-BC35-EEB4AC138154
    UUID:  RfcCallNew send the uuid to the partner:B6D708F0-B946-11E0-BC35-EEB4AC138154
    >>>> [2] <unknown> EXT <ac: 7> >>> WRITE (88578752)
    000000 | 01010008 01020105 04010002 01010103 |................
    000010 | 00040000 020B0103 0106000B 04010002 |................
    000020 | 01060200 00002301 06000700 1A003100 |......#.......1.
    000030 | 37003200 2E003100 39002E00 31003200 |7.2...1.9...1.2.
    000040 | 39002E00 38003400 07001100 02004500 |9...8.4.......E.
    000050 | 11001200 06003600 34003200 12001300 |......6.4.2.....
    000060 | 08003700 30003000 20001300 08001800 |..7.0.0. .......
    000070 | 73006100 70007000 69002D00 64006500 |s.a.p.p.i.-.d.e.
    000080 | 76002D00 64003100 08000600 28007300 |v.-.d.1.....(.s.
    000090 | 61007000 72006400 62002D00 64006500 |a.p.r.d.b.-.d.e.
    0000a0 | 76002D00 64003000 5F004400 52003300 |v.-.d.0._.D.R.3.
    0000b0 | 5F003000 30000605 140010B6 D708F0B9 |_.0.0...........
    0000c0 | 4611E0BC 35EEB4AC 13815405 14050200 |F...5.....T.....
    0000d0 | 00050200 0B000600 36003400 32000B01 |........6.4.2...
    0000e0 | 02003200 5A005F00 46004900 5F004100 |..2.Z._.F.I._.A.
    0000f0 | 41005F00 42004100 50004900 5F004100 |A._.B.A.P.I._.A.
    000100 | 53005300 45005400 5F004300 48004100 |S.S.E.T._.C.H.A.
    000110 | 4E004700 45010203 37000003 37051400 |N.G.E...7...7...
    000120 | 10B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....
    000130 | 54051401 3100E62A 54482A03 00E60000 |T...1..TH.....
    000140 | 00000000 00000000 00000000 00000000 |................
    000150 | 00000000 00000000 00000000 00000000 |................
    000160 | 00000000 00000000 00000000 00000000 |................
    000170 | 00000000 00000000 00000000 00000000 |................
    000180 | 00000000 00000000 00000000 00000000 |................
    000190 | 00000000 00000000 00000000 00000000 |................
    0001a0 | 00000000 00000000 00000000 73617070 |............sapp
    0001b0 | 692D6465 762D6431 5F445049 5F313839 |i-dev-d1_DPI_189
    0001c0 | 34303530 00000000 00000000 63303432 |4050........c042
    0001d0 | 35313733 62393435 31316530 38373562 |5173b94511e0875b
    0001e0 | 30303030 30303163 65366132 00000000 |0000001ce6a2....
    0001f0 | 02C04251 73B94511 E0875B00 00001CE6 |..BQs.E...[.....
    000200 | A2B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....
    000210 | 54000000 01000000 002A5448 2A0131FF |T........TH.1.
    000220 | FF0000FF FF000000 00000000 00000000 |................
       >> CPIC native call CMSEND [2] convid: 88578752 14:23:39,159
       << CPIC native call CMSEND [2] convid: 88578752 rc: 0 14:23:39,159

  • Error in pushing a request to R3 System using RFC Adapter

    I am trying to send a request to R3 system using an RFC Adapter as my end point and pointing to
    the Application server of the  R3 box.
    In the Transaction SM58 I see and error saying "<i><b>Exception in handleRequest of server Xmb2RfcService: java.lang.Exception:</b></i>"
    Here are the corresponding details:
    Caller: CENTRALADMIN
    Function Module: SRFC_ADAPTER_SERVICE
    Target System: AI_RFCADAPTER_JCOSERVER
    Host: .... (The XI Server)
    Program: SAPMSSY1
    Clnt: 100
    As per the SRFC_ADAPTER_SERVICE function module, the <i><b>purpose stated so...
    "This function is the glue between the JCo RFC Inbound Adapter and the XMS Pipeline."</b></i>
    By the by the RFC adapter is started and I can see no activity in the log after startup.
    I would really appreciate for any idea/leads in solving this. Thanks.<b></b>

    Here are the details
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Config File for RFC Adapter%%%%%%%%%%%%%%%%%%%%
    RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE
    classname=com.sap.aii.rfcadapter.core.RfcAdapterModule
    RFC ADAPTER CONFIGURATION PROPERTIES
    Tue Jan 21 13:27:43 CET 2003
    1. GENERAL SECTION
      1.1 trace settings
    RfcAdapter.trace=2
    -> adapter trace level 0 = none
                           1 = error
                           2 = standard
                           3 = request
                           4 = payload
                           5 = binary payload outbound
    #RfcAdapter.traceStack=0
    #RfcAdapter.listenException=0
    #RfcAdapter.listenState=0
    -> additional trace switches (in general not needed)
    RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log
    -> name of trace file (traces to stdout if not specified)
       NOTE: in a productive environment, the trace file should be written to the
             log-file directory of the Adapter Engine
      1.2 connectivity settings
    RfcAdapter.registerInbound=sourceBackendXD1
    -> space-delimited list of logical names for inbound R/3 systems subsections.
       The adapter will register with all R/3 systems defined in this list and
       those systems can send RFC requests into the XI via an RFC destination
       that has to be setup in SM59 to point to the RFC Adapter
    RfcAdapter.accessInbound=toXmb
    -> logical name for inbound access to XMB subsection
    RfcAdapter.registerOutbound=fromXmb
    -> logical name for outbound access from XMB subsection
    RfcAdapter.accessOutbound=targetBackend
    -> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.
       This is an option to speed up connection setup during request processing. The RFC Adapter
       preallocates sessions to all listed R/3 systems.
    RfcAdapter.clientCloseConn=1
    -> close calling connections after call (1) or just reset session (0)
       NOTE: the reset mechanism is slightly faster for request processing. However, it does
             not re-connect after a target system shutdown and hence requires a restart of the
             RFC Adapter in such a situation.
    #RfcAdapter.maxDynPools=128
    -> maximum number of dynamically allocated client pools to access outbound R/3 systems
    #RfcAdapter.minDynPoolSize=4
    -> initial number of clients in dynamically allocated client pools
    #RfcAdapter.incDynPoolSize=4
    -> increment number of clients in dynamically allocated client pools
    #RfcAdapter.maxDynPoolSize=64
    -> maximum number of clients in dynamically allocated client pools
    2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS
    (one subsection per incoming R/3 system; requires callback service user for repository access)
    RfcAdapter.sourceBackendXD1.host=db03
    RfcAdapter.sourceBackendXD1.sysnr=00
    RfcAdapter.sourceBackendXD1.progid=Rfc2XmbService
    -> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService
    RfcAdapter.sourceBackendXD1.poolsize=5
    RfcAdapter.sourceBackendXD1.unicode=1
    -> source system is Unicode installation (1) or not (0)
    RfcAdapter.sourceBackendXD1.client=500
    RfcAdapter.sourceBackendXD1.user=XIAPPLUSER
    RfcAdapter.sourceBackendXD1.passwd=********
    RfcAdapter.sourceBackendXD1.lang=EN
    RfcAdapter.sourceBackendXD1.trace=2
    -> enable RFC trace for this connection (1) or not (0)
    #RfcAdapter.sourceBackendXD1.sncName=<SNC_name_of_adapter>
    -> e.g. RfcAdapter.sourceBackendXD1.sncName=p:CN=USERNAME, O=ORGNAME, C=DE
    #RfcAdapter.sourceBackendXD1.sncLib=<SNC_library_path>
    -> e.g. on Win2K: RfcAdapter.sourceBackendXD1.sncLib=C:
    Program Files
    SECUDE
    SECUDE for R3
    secude.dll
    #RfcAdapter.sourceBackendXD1.sncQop=<SNC_quality_of_protection>
    -> 1,2,3,8,9 e.g. RfcAdapter.sourceBackendXD1.sncQop=1
    #RfcAdapter.sourceBackendXD1.sncAcl=<SNC_access_control_list>
    -> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q
    #RfcAdapter.sourceBackendXD1.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE
    #RfcAdapter.sourceBackendXD1.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE
    -> details for peer ACL lists
    3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE
    (only one entry possible)
    RfcAdapter.toXmb.host=web03
    RfcAdapter.toXmb.sysnr=00
    RfcAdapter.toXmb.poolsize=5
    RfcAdapter.toXmb.client=100
    RfcAdapter.toXmb.user=XIAPPLUSER
    RfcAdapter.toXmb.passwd=******
    RfcAdapter.toXmb.lang=EN
    RfcAdapter.toXmb.trace=2
    4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE
    (only one entry possible)
    RfcAdapter.fromXmb.host=web03
    RfcAdapter.fromXmb.sysnr=00
    RfcAdapter.fromXmb.progid=Xmb2RfcService
    this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59
    RfcAdapter.fromXmb.poolsize=5
    RfcAdapter.fromXmb.unicode=1
    -> source system is Unicode installation (1) or not (0)
    RfcAdapter.fromXmb.trace=2
    5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS
    (one subsection per outgoing R/3 system; pre-allocated connection pools via service user)
    RfcAdapter.targetBackend.host=db03
    RfcAdapter.targetBackend.sysnr=00
    RfcAdapter.targetBackend.poolsize=5
    RfcAdapter.targetBackend.client=500
    RfcAdapter.targetBackend.user=XIAPPLUSER
    RfcAdapter.targetBackend.passwd=*******
    RfcAdapter.targetBackend.lang=EN
    RfcAdapter.targetBackend.trace=2
    END OF RFC ADAPTER CONFIGURATION PROPERTIES
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Log data for the adapter%%%%%%%%%%%%%%%%%%%%%%%%%%
    Fri Sep 24 09:50:09 EDT 2004 *****
    09:50:09 (6011): RFC adapter initialized
    09:50:09 (6031): RFC adapter started
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%SM59 entries on the XI box%%%%%%%%%%%%%%%%%%%%%%%%%%
    Name: AI_RFCADAPTER_JCOSERVER
    Program ID: Xmb2RfcService
    Action Type: Registered Server Program
    Gateway: web03  (Local XI box)
    Gateway Service: sapgw00 (00 is the system number)
    Name: XI_SERVER
    Program ID: Rfc2XmbService
    Action Type: Registered Server Program
    Gateway: db03  (R3 box)
    Gateway Service: sapgw00 (00 is the system number for R3)
    Both the entries are tested fine.

  • XI3.0: SOAP-Adapter Exception

    Hi All,
    I'm trying to send a message to a web service via the SOAP adapter.
    Unfortunately the SOAP adapter throws the following exception:
    <i>
    SOAP: error occured: com.sap.aii.messaging.srt.BubbleException: Failed to call the endpoint: HTTP 0 null [null "null"]; nested exception caused by: java.net.SocketException: Connection timed out:could be due to invalid address
    </i>
    It seems to be that the configured URL does not reach the SOAP adapter.
    We use the central J2EE Adapter Engine.
    Any hints?
    How do I sitch on detailed tracing or logging for the SOAP Adapter? The Audit Log does not contain very much information.
    I hope anybody is able to help.
    Regards,
      Marc

    Hi Alessandro,
    we solved the problem.
    The problem was caused by a firewall. The used port was blocked there. We just reconfigured the firewall and all went fine.
    In the meantime I learned somthing about the error message.
    "Failed to call the endpoint: HTTP 0 null"
    This means that the adapter called the configured endpoint. The "HTTP 0 null" is the result code and error text of the http call. So it returned with error code "0" and it has no associated error text "null".
    Another hint that may help you is the OSS note 761921. This note describes how to get an adapter trace.
    Hope this reply helps.
    Regards,
      Marc

  • Why is the RFC Adapter so unstable

    Hi all,
    I have a scenario where an IDOC is sent from the sender system and an RFC enabled Function Module is called on the target system. Sometimes I get an error in the Adapter for no aparent reason. I check the RFC adapter trace file but none of the exceptions was raised and I am not able to see what was the problem.
    But, if I restart the RFC Adapter and send the IDOC again, everything's allright. Why? Is there any other trace avilable somewhere? Is there any way to restart the RFC Adapter periodically and automatically?
    Thanks and regards,
    Nuno

    This sounds like a bizarre scenario.  Why would a Idoc (asynchronous) be calling an RFC (synchronous)?
    Unless the RFC is doing update?  Then you have more problems.  You are mixing your QoS from EO to BE.  The delivery is no longer guaranteed.  The posting to the RFC could work but XI may not get the acknowledgement - RFC adapter does not do commit so you must have a commit in the remote function.  If no acknowledgement is received, do you resend and risk duplicate updates?  How do you guarantee EO delivery?  The sender system is right in expecting EO for it's outbound Idoc.
    In all the training material RFC is intended for data retrieval, not data posting.  This is consistently done with Idoc (EO, or EOIO).
    I would consider changing the scenario to Idoc->xi->Idoc.

  • JDBC Adapter debugging parameter

    Dear gurus,
    We wanna activate the debugging parameter for the JDBC adapter to generate logs in XI 3.0.
    Please comment !!!!
    Regards,

    I cannot find how to set the parameter for activating the trace for JDBC adapter.
    The exact path is given in the question here in this thread
    JDBC adapter trace logs
    help me in activating the parameter logSQLStatement
    As already been suggested refer note:801367
    I think this parameter is available in XI3.0 also.Just go to the advanced mode of the JDBC channel and select it.

  • File adapter didn't read the whole file

    Hi folks,
    we use the file adapter since 1 year and in the majority of cases it works fine. But sometimes the file adapter didn't read the whole file. In SAP we are missing some parts. Funnily enough in this cases he archive the whole file and not only the executed parts . Know anybody whats the reason of this effect and how we can solve it?
    Kind regards Johann M.

    Johann
    I think you miss understood me/I didn;t explain myself very well....
    If you take the file that doesn't work/process correctly, can you replicate the issue where the whole file is not copied across.
    If you can, you should be able to extend the FTP/File adapter trace file to find the cause if this issue.
    Log onto Visual Admin.
    &#61680;     Services
    &#61680;     Log Configurator
    &#61680;     Locations
    &#61680;     Choose the location (Java package) and the tracing level (severity)
    (for example, com.sap.aii.adapter.file)
    &#61680;     Root Location > com > sap > aii > File
    &#61680;     Set the severity and choose Copy Severity to Subtree
    Run interface and then check the trace file - remember to switch this back to Error...

  • DS 4.0 MSExcel adapter error

    Hi all,
    we have installed Data Services 4.0 in Linux SLES 11. It is a distributed installation with Data Services (job Server, Access server, Message Client, ODBC driver) on one server and DS integration to BI 4.0 on second server (DS Management Console and APS services).
    The problem which I experienced is a problem with Adapters. When I successfully add MSExcel adapter and try to start it, the Data Services suddenly end up with an communication failure below:
    2/24/12 10:45:58 AM Thread[main,5,main]         Unable to connect to job server '<hostname>:6600'. Error= Communication failure. ^M
    2/24/12 10:45:58 AM Thread[main,5,main]         com.acta.adapter.sdk.AdapterException: Unable to connect to job server '<hostname>:6600'. Error= Communication failure.
            at com.acta.adapter.sdk.AdapterEnvironmentImpl.init(AdapterEnvironmentImpl.java:184)
            at com.acta.adapter.sdk.AdapterRunnerImpl.initAdapter(AdapterRunnerImpl.java:231)
            at com.acta.adapter.sdk.AdapterMain.main(AdapterMain.java:46)
    I am able to add other adapter and run them, the problem is only with the MSExcel. After the error occurs, there is no way how to stop or remove the adapter as in the DS Management Console you permanently see this error and only deleting of adapter.key and startup_script.xml on OS level resolves the issue. But than I have to recreate the whole Adapters again (and just for sure I created a new Job server again).
    Any help is appreciated.
    Thanks!
    Erik.

    Hi Erik,
    Thanks for your reply, In my Case SSL is Enabled but here i am getting the message from other extenal sources but suddenly it crash and failed.
    This issus is still there in BODS 3.2 and i already refer below SNotes regarding that but noluck.
    1824972 - Get error: "Unable to connect to the Job Server '<Server Name>:<Port>'. Error: Connection refused. (BODI-3016234)" when try to run job from Data Services Management Console
    I am getiing the below error in Adapter Trace and Error Log:
    Adapter Trace Log Details:
    /30/13 5:38:57 AM Thread[Thread-26,5,main]  JMSGetOperation: getMessageFromRequestQueue function out
    7/30/13 5:38:57 AM Thread[Thread-26,5,main]  JMSGetOperation: Poll function out
    7/30/13 5:38:57 AM Thread[Thread-26,5,main]  JMSGetOperation: Poll function in...
    7/30/13 5:38:57 AM Thread[Thread-26,5,main]  JMSGetOperation: getMessageFromRequestQueue function in...
    7/30/13 5:38:58 AM Thread[Thread-22,5,main]  JMSGetOperation: getMessageFromRequestQueue function out
    7/30/13 5:38:58 AM Thread[Thread-22,5,main]  JMSGetOperation: Poll function out
    7/30/13 5:38:58 AM Thread[Thread-22,5,main]  JMSGetOperation: Poll function in...
    7/30/13 5:38:58 AM Thread[Thread-22,5,main]  JMSGetOperation: getMessageFromRequestQueue function in...
    7/30/13 5:38:58 AM Thread[Thread-28,5,main]  JMSGetOperation: getMessageFromRequestQueue function out
    7/30/13 5:38:58 AM Thread[Thread-28,5,main]  JMSGetOperation: Poll function out
    7/30/13 5:38:58 AM Thread[Thread-28,5,main]  JMSGetOperation: Poll function in...
    7/30/13 5:38:58 AM Thread[Thread-28,5,main]  JMSGetOperation: getMessageFromRequestQueue function in...
    7/30/13 5:38:58 AM Thread[Thread-27,5,main]  JMSGetOperation: getMessageFromRequestQueue function out
    7/30/13 5:38:58 AM Thread[Thread-27,5,main]  JMSGetOperation: Poll function out
    7/30/13 5:38:58 AM Thread[Thread-27,5,main]  JMSGetOperation: Poll function in...
    Adapter Error Log Details:
    Unable to connect to job server 'sapdsq01:4001'. Error= Client id adapter.JMS_Adapter_QA is already in use
    7/29/13 7:19:52 AM  com.acta.adapter.sdk.AdapterException: Unable to connect to job server 'sapdsq01:4001'. Error= Client id adapter.JMS_Adapter_QA is already in use
    at com.acta.adapter.sdk.AdapterEnvironmentImpl.init(AdapterEnvironmentImpl.java:185)
    at com.acta.adapter.sdk.AdapterRunnerImpl.initAdapter(AdapterRunnerImpl.java:251)
    at com.acta.adapter.sdk.AdapterMain.main(AdapterMain.java:46)
    Thanks,
    Daya

  • Unable to create a new tcp/ip connection in sm59

    Hello Friends,
    We are trying to connect genesys cti gplus adapter to SAP ERP.
    While testing  new tcp/ip RFC Connection in SM59 , the connection test failed.
    Error  Details:
    Logon :                     Connection error
    Error Details     Error when opening an RFC connection.
    Is it something to do with librfc32.dll file ?  Do we need to register this file? There is one librfc32.dll in C:/win/system32. Do we need to replace this .dll with the current version of librfc32.dll.
    I could find some errors in our gplus adapter trace file.
    Can someone please help me in this. U can reply me on <email address deleted by moderator>
    Thanks in Advance.
    >TS> Sun Oct 21 12:00:45 2007
    T:9944 Error in program 'Dummy': ======> Connect to SAP gateway failed
    Connect_PM  TPNAME=SPS.PROG, GWHOST=MB3AP1024, GWSERV=3300
    LOCATION    CPIC (TCP/IP) on local host MB3AP1021
    ERROR       partner 'MB3AP1024:3300' not reached
    TIME        Sun Oct 21 12:00:45 2007
    RELEASE     710
    COMPONENT   NI (network interface)
    VERSION     39
    RC          -10
    MODULE      nixxi.cpp
    LINE        2985
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     14789

    Hi,
    It seems to me that your genesys cti gplus adpater is of the registration type.
    And from the error file, it could not contact the SAP gateway to register.
    It is so logical that the connection test from SM59 fails.
    Check the hostname of your SAP gateway. Is it really in capital letters ?
    Are you able to ping it from your adapter host ?
    Is the system number of your SAP system 00 ?
    You are not supposed to ask for information at your  email address.
    A  public forum is designed to share information among its users.
    Regards,
    Olivier

Maybe you are looking for