Testing XI interface

Hi:
suppose i want to test xml messages in RWB in Test message. I am getting constant payloads of xml message.
We need to populate fields in that screen : Message interface ,interface namespace ,user name and password.
There is also a url :
1) In the code for a web page i found a global.asa file ,can i point in that file where i need to redirect the xml payloads. if so then all xml payloads could be directed there and interface could work.
2) The fields Message interface ,interface namespace ,user name and password.
can be hardocded .? so that no one could go and change these fields?
Thnx

HI :
From my RWB : using Test message and putting required paramaeters i am able to see response in SXMB_MONI but when i run thorugh ABAP client i get http :404 payload not found.
i am putting payload from Message mapping using TEST and getiing the source
can someone help?
Thnx

Similar Messages

Getting Java mapping errors when testing my Interface mapping

Hi,
I'm trying to test my interface mapping from IR, I keep getting these exceptions. All I'm doing in my interface mapping is I have two mapping programs a XSLT mapping with java helper functions with the XSL and a message mapping. In the test it pass thru the XSLT mapping but fails at Message mapping and throws the following exception. Any help on this is really appreciated.
10:03:26 Start of test
Call XSLT processor with stylsheet com/earthlink/xi/mapping/xmlc_to_crm_resp.xsl.
START APPLICATION TRACE ***
Response:
0
END APPLICATION TRACE ***
Returned form XSLT processor.
Call method execute of the application Java mapping com.sap.xi.tf._MM_XMLC_RESP_
Error during appliction Java mapping com/sap/xi/tf/_MM_XMLC_RESP_
java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrep.server.mapping.ibrun.RepJavaMapping.execute(RepJavaMapping.java:73) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
10:03:26 End of test

Joe,
most likely your XSLT is outputting a not well-formed XML message.
Remove message mapping from the mapping list and execute it again, to check output.
Also, for mapping debugging in java enhanced function inside XSLT mappings, use the following:
1st, you need to pass the "inputparam" parameter from the XSLT runtime to the Java function (it needs to be one of the input parameters for the executed java function).
In the Java code itself, implement the following code:
AbstractTrace trace = (AbstractTrace) param.get(StreamTransformationConstants.MAPPING_TRACE);
trace.addInfo("Log your message here!");
where <i>param</i> is the input parameter refering to the <i>inputparam</i> from XSLT.
The AbstractTrace and StreamTransformationConstants classes can be found in the aii_map_api.jar file (used in Java mappings).
Regards,
Henrique.

How to test the interfaces in XI ?

Hi ,
Our Xi system is being upgraded from 3.0 to 7.0. I was asked to test the interfaces once the upgradation is done. I am not sure how this testing is to be done and will there be aby test plan for this??
Can some one help me on this ??
Thanks in Advance,
Hemanthika

To test, you must have imported all your scenarios in to your new system.then couple of general tips,
1.testing can be done only after understanding the scenario.
For this, u refer to the integration scenario in ur design. so this shall give u an idea about all the systems involved in integration and how the data flowing is between them and what kind of systems they are?
2. For testdata, you might need of business or functional team as you cannot have any info on the file formats etc(depending on different scenarios invloved like R3, SOAP Databse etc)
these are only general tips. but u can refer to many of the trouble shooting guides already available blogs in sdn for any sought of inputs.But then, SDN is always there.
you can test/monitor ur results in RWB->component monitoring
also in sxmb_moni
thanks
kiran
Edited by: kiran dasari on Mar 17, 2008 4:44 PM

Testing ALE Interface

Hi Friends,
How do we test ALE Interface.
Please provide me with stpes for configuring the ALE Interface for SAP-SAP,SAP-Non SAP scenarios on Outbound & Inbound Systems.
After configuring,How do we send the data.
<REMOVED BY MODERATOR>
Thanks
Edited by: Alvaro Tejada Galindo on Feb 14, 2008 11:01 AM

Hi Annapurna,
you can try these links as well .
IDOCS:
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.sapgenie.com/sapedi/idoc_abap.htm
ALE/IDOCS:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
or have a look at this thread..
https://forums.sdn.sap.com/click.jspa?searchID=8882009&messageID=4770944
Regards,
Ramesh.

Testing the Interface

Hi Team
i have to test an interface. In my scenario there is no IR Part involved, no mapping , only ID part is involved. i am using two adapters, sender is JMS and receiver is IDOC, for this scenario i have to test whether the interafce is working fine or not???
plz help me out

Hi,
first option with adapter
put the message into the JMS queue (depending on the jms provider you use it will be done in a different way)
and check the IDOC in WE02
second option without an adapter
open test page in RWB and put the message there
check the WE02 (IDOC)
remember:
use messages prepared by the one who designed the interface - to check all possible cases
you can also do a stress test if the interface will be passing lots of data
Regards,
Michal Krawczyk

Getting error in Component Interface (Test Component Interface) --

Hi,
I created new CI for workers/Consumers in peoplesoft CRM .. when I am testing the same CI using test component interface property ... I am getting the below error.
BO Search cannot be performed in the Component Interface. (18076,5115)
*Error loading Component Processor {RD_WORKER_CI} (91,24)*
Failed to create the Component Interface (91,61)
Even though I tested tested for delivered Component Interfaces also.. for those CI's also I am getting same errors. (RD_WORKER_CI_CLA, RD_WORKER_CI_AAF)
I created some of the CI's in HCM and ELM module and tested ... In those modules working fine but not working CRM ... getting the above errors.
Can any one please help me on this.
Thanks
-Venkat

There is RBQ_BOSRCH_QCCREATE.Runtime.Control.Controller.OnExecute PeopleCode (search for string "18076, 5115" in this PeopleCode) that is preventing your CI to work. I tried commenting this PeopleCode but it creates other problems. I am not sure why this code is there.
There is another component that PeopleSoft delivers RD_WORKER_CI which you can use to build your CI. I am not sure if it will populate and update all the fields that you needed in the first place.
Let me know if any other solutions worked for you.

Using J-meter for testing PI interfaces

Hi all,
I am planning to use j-meter for performance testing of PI interfaces. The concerned interfaces have an abap proxy to trigger the message at the sender SAP system. The receiver end is a database.
Need information on how to use/configure the j-meter for this scenario. Also, using j-meter can we send message payload to integration engine directly or is it sent to through adapter engine only?
Any kind of help is appreciated.
Thanks,
Amit

Thanks for the response Ajay.
I have configured the j-meter to send http request to inegration engine of PI.
The request xml that I am sending is as follows:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
<SOAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1">
</SOAP:Main>
</SOAP:Header>
     <SOAP:Body>
          <ns1:UnitOfMeasure xmlns:ns1="urn:sapappl:mdm:cp:eame:masterdata:uom:620">
               <Record>
                    <FinishedMaterialCode>000000000000000233</FinishedMaterialCode>
                    <BaseUOM>KG</BaseUOM>
                    <AlternateUOM>GEB</AlternateUOM>
                    <UnitsInAlternateUOM>100</UnitsInAlternateUOM>
                    <UnitsInBaseUOM>2268</UnitsInBaseUOM>
                    <Active_Deleted></Active_Deleted>
               </Record>
          </ns1:UnitOfMeasure>
     </SOAP:Body>
</SOAP:Envelope>
I am getting the following response from the XI:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER"/><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>System error in parser
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Any pointers as to why PI is not able to parse the request header?
Thanks,
Amit

Cannot test the Interface mapping for abapmapping

Dear all,
i am trying to go to the test tab in the interface mapping foe testing a abap mapping.
but it is giving me this error " unable to test . you cannot test the program in the test environment "
is this some authorisation issue

login to ABAP stack of XI and is the transaction SXI_MAPPING_TEST to test ABAP mapping

Testing same interfaces from other Business System

Hi,
Till now we have been testing with BIDCLNT100.
Now we want to continue testing with BIDCLNT200 for which there was no config before.
Apart from adding new Business System for new client in SLD, what is needed to be done in ID to configure interfaces for this client.
Regards,
Anirudh.

Hi Prateek,
I think I also need to add the SWCV which are used for these scenarios to this new BS in SLD.
Please confirm.
Also, will there be any changes in IR?
regards,
Aniurdh.

Testing of interface

Hello,
Can any suggest a how do i prepare unit cases to test interfaces in ODI,
Thanks
RB

Interface is just a INSERT SQL query for tables. So you can prepare the test case based on the purpose of the interface or else function of the interface.

Error when test an INterface with SOAP Sender CC

Hello everybody,
I'm testing a Scenario that goes as follows Web Service Consumer-> PI 7.0 -> RFC, now I've already tried to test it with Altova XML Spy, and with the WebServcies Navigator Tool of UDDI, now I'm getting the next error in both cases:
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/7.00
Content-Type: text/xml; charset=utf-8
Date: Tue, 16 Dec 2008 22:10:42 GMT
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
      <detail>
        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
          <context>XIAdapter</context>
          <code>RecoverableException</code>
          <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: java.net.ConnectException: Connection refused: connect
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:157)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:850)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
now in the RW in the communication channel I', getting history as follows:
error ocurred
request received
but no more about it, and I can't see the message in SXMB_MONI, can anyone tell me something about what could be wrong, thanks in advance.
Regards.

Check if the XI RFC destination is working fine. ALso check the sap note no.804124, 807000 .
Thanks!

Idea about how-to using 'Agilent Wireless Test Manager' interfaces in Labview ?

Hello everyone,
I am not sure whether it is appropriate to post this here.
Currently I got a Wireless Test Manager CD(Agilent E6560A) and is trying to convert some functionalities inside class 'cdmaTXMeasTests' into labview.
I am doing the 'code domain power testing' module with labview, which is well done in that 'cdmaTXMeasTests'.
I am wondering if any one could provide me some idea how to use that 'cdmaTXMeasTests' in my labview without rebuild the wheel.
( I am not sure whether that would work, Are the libaries used by wireless test manager a ActiveXDLL that could be used by labview ? Or there is some other way to do it or not?)
Any idea is well appreciated,
+Kunsheng Chen

Good Afternoon Kunsheng Chen,
It seems like you are trying to port your DLL. Rather, I would suggest using a Call Library Function Node (right-click the Block Diagram, Functions>>Connectivity>>Libraries & Executables>>Call Library Function Node).
From the Agilent website, this is a C dll so you will be able to access it using this VI in LabVIEW with no problems. You might want to contact Agilent to see if this DLL has ActiveX components. Alternatively, you can simply browse the list of ActiveX components on your computer.
The following links may provide some useful information for using a DLL in LabVIEW.
An Overview of Accessing DLLs or Shared Libraries from LabVIEW
   http://zone.ni.com/devzone/cda/tut/p/id/3009
Call Library Function Node
   http://zone.ni.com/reference/en-XX/help/371361E-01/glang/call_library_function/
Using Existing C Code or a DLL in LabVIEW
   http://decibel.ni.com/content/docs/DOC-1690
Regards,
Charlie Piazza
Staff Product Support Engineer, RF
National Instruments

Interface mapping test successful, throws exception in BPM

Hi.
We are having a problem with an Interface mapping which works when
tested in Integration Builder, but throws an Exception when it is part
of the Transformation in a BPM.
The scenarion is such:
1. The sender calls the outbound interface using a web service.
2. XI uses the input and passes to the Integration Process
3. In the BPM, a LOGON message is built to call the web service as
specified by an external web service . The input and
output messages are just a single string, in which the other XML is
embedded.
4. XI receives a response from the web service call
5. XI Extracts the sessionId from the response and combines it with the
initial input (Step 1) to create the query for the query message in
the web service.
It is in Step 5 where the transformation fails, with an Exception in
the DefaultTrace.trc as
Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Thrown:
MESSAGE ID: com.sap.aii.ibrun.server.mapping.rb_MappingRuntimeException.EXCEPTION_DURING_EXECUTE
com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
I have extracted the data from the initial request (step 1) and the
logon response (step 4) and using these I have tested the Interface
Mapping. There is no problem with this and the tests are successful.
From what I can see, because the Response field in the LOGONResponse
contains more XML tags, XI must be parsing it and assuming the tags are
tags in the message, and not just the string, thus it is complaining
that the XSD types do not match. This extra XML Parsing does not take
place in the Interface Mapping Test.
I have put the response into a User Defined Function which just has one
line "return new String("Hello")" and that fails. However, if this UDF
does not have the Response as the input, it does not complain.
Please advise.
--Reenal

hi
You will have to use specific replacements for you xml tags if it is coming as a paramter
replace '<' with <
replace '>' with >
for eg: I want to pass <TakeIt>200</TakeIt> as value to Element <A>
Mapping won't work if it is passed like
a) <A><TakeIt>200</TakeIt></A> - Wrong
Instead the replace the angle brackets
b) <A><TakeIt>200</TakeIt></A> - Correct
While testing the mapping in IR (a) will work bcoz the test tool will convert it to (b) format. Check the xml source in test tool.
So ensure the web response is like (b)
rgds,
Arun

Interface and conversion testing of SAP environments with Master Data

Hi guy's
Please let me know if some one of you know about SAP Conversion Project. Below you have more description:
- testing of Interfaces from Legacy Systems
- testing of conversion programs used in the conversion or transposition of data from legacy systems
- data cleansing activities associated with conversion
- identify and populate various SAP environments with Master Data necessary for both conversion and interface testing
Any detail info in that and what kind of knowledge you need to have in some of project will be useful.
Thanks in advance
Adeel

Hi Yannick,
I am trying to do the exact same thing. Have you gotten any further on this issue?

Problem in testing the Webservice interface?

Hello All,
I created and deployed one webservice in the Xi system and SAP communication done using the RFC.
same like below link.
http://www.riyaz.net/blog/xipi-consuming-xi-web-services-using-web-dynpro-part-i/technology/sap/6/
but now problem is the external system is not ready to test the interface, i need to test the interface from the XI end.
How to test the scenario using other then XMLspy and SOAPUI?
Thanks and Regards,
Chinna

Dear Chinna,
Is your requirement to make full end-to-end test or make a simulation?
If you need simulation only, then PI's functionality available in Runtime Workbench and Test Confiuration tool available in Integration Builder and mentioned by Abhishek is OK.
In case the requirement is to make end-to-end test, I would suggest to use external SOAP client software in order to generate SOAP requests and send them to PI. Please advise why XML Spy and soapUI do not suit you? Actually, you can use any software which can generate SOAP request, send it to the specific endpoint and handle response.
My regards,
Vadim

Testing XI interface

Similar Messages

Maybe you are looking for