Integration engine 7.1 - abap or java

Hello All,
Is intergration engine in 7.1 and above is on ABAP or JAVA?
Thanks..HP

Hi,
Integration engine in PI 7.1 is on ABAP.
Regards,
Chandra

Similar Messages

Business Engine and Integration Engine based on which Engine ABAP or Java

give me information about Business Engine and Integration Engine based on which Engine ABAP or Java Engine.
What is Xapps and how it is related to XI

Hi Sridhar
About your other question:
an ESR ( enterprise services repository) is central to xApps, and XI enables ESR.
You can find more info on xapps and the CAF ( composite application framework) here :https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/831740fa-0c01-0010-fc94-8b312e7fec2d [original link is broken]
Hope this helps
Thanks
Hari

Java.lang.Exception error during XML validation by Integration Engine

Hi professionals,
We are trying to use XML validation by the Integration Engine.
Step 1:
We created an appropriate directory structure where we had to store the structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is
assigned.
Step 2:
We also changed the references in the xsd to exclude all the subdirectory references.
e.g folder1/folder2/abc.xsd is become abc.xsd only
Step 3:
We stored both xsdu2019s (schema xsd and referenced xsd to the directory created in step 1)
Step 4:
We changed the directory and xsdu2019s permissions to 777 (we chose 777 for testing purpose).
Step 5:
We changed the property schema validation of the sender agreement to Validation by Integration Engine.
Step 6:
We checked RFC destination for AI_VALIDATION_JCOSERVER on AS ABAP and AS Java and establish an successful connection test.
RESTULTS
The result of those steps is an error message in the message monitor of PI with the error tekst:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="XML_VALIDATION_INB">CX_XMS_SYSERR_VALIDATION</SAP:Code>
<SAP:P1>java.lang.Exception</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>not used at the moment.</SAP:AdditionalText>
<SAP:Stack>System error occurred during XML validation</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please assist in how to solve this issueu2026.
Regards, Sjaak.

I would suggest follow Appendix A to know the exact path and since you have one XSD referring other XSD check the steps mentioned in Appendix B .... there seems to be some error in referencing ...Appendix A and B are on page 12 & 13 of this document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?quicklink=index&overridelayout=true
Regards,
Abhishek.

Java bean, works in Integration Engine but does not work in Adapter Engine.

In connection to the following thread:
PayloadZipBean - variable filename inside the archive
I am trying to use the same bean.
However I can see, that the bean is working correctly when I use Integration Engine.
But if I am using ICo (AAE) and using the same bean in the receiver, I can see, that the bean gets called but does not work correctly.
The audit log added to my bean shows, that the bean could read the filename correctly from the Dyanic Config in the message, but it cannot write the same into the message.
Could you please help on this?

Your above posted system details show multiple Java Console extensions.
You can uninstall (remove) the Java Console extensions and disable the Java Quick Starter extension, you do not need them to run Java applets.
See http://kb.mozillazine.org/Java#Multiple_Java_Console_extensions
See also http://www.java.com/en/download/help/quickstarter.xml - What is Java Quick Starter (JQS)? What is the benefit of running JQS? - 6.0
Disable the Java Quick Starter extension: Tools -> Addons -> Extensions
Control Panel -> Java -> Advanced tab -> Miscellaneous -> Java Quick Starter (disable)
You can try a direct connection: 
Control Panel > Java > General tab > "Network Settings...": "Direct Connection" (enable)

Integration Engine Message Id in ABAP Proxy

Hi,
I have a scenario sending to XI from CRM using an ABAP Proxy.
I need to get the message id generated in the local Integration Engine when a message is sent via the ABAP Proxy or received into the ABAP Proxy.
I see there is a way of doing this in XI and also thought I had found a way of getting it in the proxy in CRM but this does not seem to work correctly even though i can see the message ID being created in the proxy call to XI.
I am trying to get the message id immediately after the proxy call to XI.
Kind regards
Colin.

Hi Colin,
as far as I know, it is possible. Have a look at the online help on abap proxies and check out the determination of message id:
http://help.sap.com/saphelp_nw04/helpdata/en/a1/082589fc4246f09793039d5fb01a17/content.htm
Hope that helps,
regards, jaime

Web Report - ABAP Vs JAVA engine - ABAP 10 times faster than JAVA

Guys,
I want to share what we found in our project and see if any of you have insights
into our findings.We are on NW2004S SP14 and we are moving to SP15 in a couple of weeks.We created query, developed WAD for it and executing the WAD takes for this query takes 22 secs (Vs 2 secs using ABAP) the query output has 1 million records and most of the actions we take from that point on like right click on account takes 20 secs (Vs 0 secs/instant using ABAP) , drilldown to level 4 of account hierarchy takes 58 secs (Vs 5 secs using ABAP), drilldown on cost center level 6 takes 42 secs (Vs 4 secs using ABAP), , right click on cost center takes 32 secs (Vs 3 secs using ABAP), ..etc.
Basically every action we take in the JAVA report takes an average of 28 secs.There are 9 aggregates built on the cube that are barely hit by this query but the same query performing same actions with same selections hit the aggregates many many times.The questions I have is why is ABAP so fast compared to JAVA ? What is true explanation behind this behavior ? What are the dis-advantages by using ABAP engine ? Users are loving the performance and features of ABAP while they weren't really on board with the original JAVA report (as it was slow). ABAP is sure enough 10 times faster than JAVA. Query/Query Properties are exactly the same in ABAP and JAVA.Please explain.
Cheers
RT

Hi All,
Thanks to all you for your responses. I appreciate your time for going through my questions and coming forward to express your views.
However, I was looking for more specific "factual" answers. My question is "What does a client miss if they opt to install only ABAP based BI 7.0, as against JAVA Based BI 7.0"
thanks again.
Naga

Registration of Business system for the Integration Engine Java in the SLD issue

Hi,
We have completed the installation of PI-AEX 7.4 SR1 then we ran the below wizards successfully.
- Configuration Wizard: PI-AEX initial setup
- Configuration Wizard: PI Self Test for AEX
However when we were Checking the AEX Configuration as per help.sap.com
Check the registration of a business system for the Integration Engine Java in the SLD:
 Enter https://<host>:<port>/sld .
 Choose Start of the navigation path Business System Next navigation step Integration Engine Java <SID> Next navigation step Integration End of the navigation path.
 The pipeline URL must be: http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet?ximessage=true .
More information: SAP Note 1435392
for us the Pipeline URL is as below
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
and the rest " ?ximessage=true " is not there.
Also we ran the below wizard
Configuration Wizard: PI Self Test for AEX
and it finished successfully without any issue.
Any Suggestions what could be missing.
Thanks,
Regard
Ahmed Mohammed

Hi,
I found the below SAPNOTE which confirms that the Pipeline URL should be
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
1564449 - PI CTC Wrong Pipeline Url after AEX Initial Setup
However on help.sap.com it is different.
Any one experienced the same ?
Regards
Ahmed Mohammed

Integrated planning in sneak preview of java and abap versions of nw 2004s

Hello all,
I installed both AS ABAP and AS JAVA of the sneak preview netweaver 2004s,but unable to run integrated planning.I searched the forum and sap notes but did not find specific required steps to configure.Anyone able to run integrated planning of the preview versions ? does it involve extensive configuration ? Could someone post the necessary steps to configure.I checked the SLD and it is running but did not have any 'technical systems' configured.I created a technical system for ABAP and JAVA manually myself.The jco destinations still shows 'No SLD connection' with a red button beside it.
Then I went to visual administrator and checked SLD data supplier service.It looks like it is lot of BASIS work to configure this.Please let me know if someone has simple steps to configure and run integrated planning just after installing sneakpreview versions of nw 2004s ABAP and JAVA.
Thanks

Hi Steffen,
all you need for this type of communication is already included in the WAS. There's a lot of documentation available:
JCO (Java Connector for ABAP backends): http://help.sap.com/saphelp_nw04/helpdata/en/35/42e13d82fcfb34e10000000a114084/frameset.htm
Generating proxies "around" JCO (very useful feature of the developer studio):
http://help.sap.com/saphelp_nw04/helpdata/en/ed/897483ea5011d6b2e800508b6b8a93/frameset.htm
Using ABAP EIS in a transactional J2EE environment via J2EE connector architecture: http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5caa85b11d6b28500508b5d5211/frameset.htm
This should be sufficient for the beginning
Hope that helps.
Best regards
Stefan

Problems with namespace XML Parsing of ABAP PI 7.0 Integration Engine

Hi,
I discovered the following problem.
The customer sends a SOAP message with is forwarded through a SOAP Adapter in the integration engine.
The structure of the message is very simple:
<Envelope>
<Body>
<ORDERS05>...</ORDERS05>
</Body>
</Envelope>
The customer adds the namespace information a special way:
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope">
<Body>
<orders05 xmlns="">...</orders05>
</Body>
<Envelope>
Here the namespaces is declared in the first element. It should be inherited into all child elements. The 'orders05' should not have the namespace ' xmlns="http://schemas.xmlsoap.org/soap/envelope" ', therefore the namespace is overwritten with ' xmlns="" '. However I don't know if this is a correct xml statement, the SAP system did not understand this.
The integration throws an error which is stated in the message in the adapter engine:
2008-11-06 17:31:44 Fehler SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIProtocol/ITEM_MISSING; Params: /@mustUnderstand, ST: ST_XMS_MSGHDR30_RM; AdditionalText: Attribut 'mustUnderstand' erwartet; ApplicationFaultMessage: ; ErrorStack: Das XML-Element /@mustUnderstand fehlt im SOAP-Message Header (SAP XI Extension) Attribut 'mustUnderstand' erwartet
2008-11-06 17:31:44 Fehler Fehler beim Übertragen der Message zum Endpunkt http://kas052.hauni.koerber.de:8036/sap/xi/engine?type=entry über die Verbindung SOAP_http://sap.com/xi/XI/System. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header
If I changed the SOAP message to the common format, it is accepted by the integration engine.
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope">
<SOAP:Body>
<orders05>...</orders05>
</SOAP:Body>
</SOAP:Envelope>
Here the namespace ' xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope" ' is defined with a prefix and assigned to the elements 'envelope' and 'body'. The 'orders05' element has no namespace.
However due to the xml syntax both messages are the same, so why the integration engine handle the messages different?
Best regards,
Nils Kloth

The valid SOAP format supported by XI is as follows
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
 <m:MessageTypeName xmlns:m="Some-URI">
 <Price>34.5</Price>
 </m:MessageTypeName>
</SOAP:Body>
</SOAP:Envelope>
Ur sender system is not sending the data in correct Soap format and thats the cause of message rejection. The option you have to use the Soap adapter in "no soap" mode.
Regards,
Prateek

ABAP and JAVA sync issue

Hello,
We are having MI 7.0 at SPS15.Am trying to apply add to our system(we created SDA file from NWA as an addon).SDA addon getting deployed but its not getting sync between ABAP and Java stack even if is run reload sever time from NWA->Administrator->Mobile Infrastructure->Mobile Components.I can see add-on when i check from SDM but it cannot see when i search under Mobile component in NWA.Application logs shows below error.
#703543993#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##8e6d577024d511e1a299001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_10##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592001800000015000030100004B3E6C1311ED1#1323703575929#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##a19424a024d511e18ede001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_9##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBea                                                                                n#Plain####
#1.#001635730592000F00000016000030100004B3E6C662CEBE#1323703663073#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_ADMIN#47##n/a##d588777024d511e1c64a001635730592#SAPEngine_A                                                                                pplication_Thread[impl:3]_18##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerB                                                                                ean#Plain####
#1.#001635730592002000000015000030100004B3E6CDC2D7E4#1323703786809#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##1f482a9024d611e18dc1001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_29##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#00163573059200260000000C000030100004B3E6D02A2DDA#1323703827137#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##37527e6024d611e1a43c001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_39##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#00163573059200350000000B000030100004B3E6D1150767#1323703842528#/Applications                                                                                #sap.com/tcwddispwda#com.sap.ip.mi.admin.wd.paramset.Details.Method-->wdDoModi                                                                                fyView()#J2EE_ADMIN#56##uwsvt729.merck.com_VZ1_12609950#J2EE_ADMIN#2e05832024d61                                                                                1e1b753001635730592#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#com.sap                                                                                .ip.mi.admin.wd.paramset.Details#Plain###Specify all parameters#
#1.#00163573059200250000007C000030100004B3E6F8460AEE#1323704500063#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##c86ab33024d711e185b5001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_22##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592002F00000015000030100004B3E728C1AF02#1323705313486#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##ad1da59024d911e1a138001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_37##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592000F0000000000002A400004B3E754A629F8#1323706045836#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter#J2E                                                                                E_GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[im                                                                                pl:3]_26##0#0#Info#1#com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter#Plain###CMS o                                                                                rganizer proxy is waiting for requests#
#1.#001635730592000F0000000100002A400004B3E754A659EE#1323706045848#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.serverAPI.CmsManagerAdapter#J2EE_                                                                                GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl                                                                                :3]_26##0#0#Info#1#com.sap.cms.pcs.serverAPI.CmsManagerAdapter#Plain###CMS manag                                                                                er proxy is waiting for requests#
#1.#001635730592000F0000000200002A400004B3E754A6715D#1323706045854#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.transport.proxy.CmsLogViewer#J2EE                                                                                GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngineApplication_Thread[imp                                                                                l:3]_26##0#0#Info#1#com.sap.cms.pcs.transport.proxy.CmsLogViewer#Plain###CMS Log                                                                                Viewer is waiting for requests#
#1.#001635730592000F0000000300002A400004B3E754A67B77#1323706045857#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###CMS recovery servlet is wai                                                                                ting for requests#
#1.#001635730592000F0000000400002A400004B3E754A67CE5#1323706045857#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###start recovery#
#1.#001635730592000F0000000500002A400004B3E754AA7F91#1323706046120#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###CMS recovery found 0 QueueItem(s) wi                                                                                th state Import running in 0 queue(s). Start check if they are really running or                                                                                need recovery.#
#1.#001635730592000F0000000600002A400004B3E754AA8344#1323706046121#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###Finished check and recovery for all                                                                                CMS QueueItems of state Import running. Checked Items: 0; Recovered Items: 0; Re                                                                                covery Failed Items: 0; Real running Items: 0#
#1.#001635730592000F0000000700002A400004B3E754AAACBA#1323706046132#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###CMS recovery found 0 QueueItem(s) wi                                                                                th state Assembly running in 0 queue(s). Start check if they are really running                                                                                or need recovery.#
#1.#001635730592000F0000000800002A400004B3E754AAAEE5#1323706046132#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###Finished check and recovery for all                                                                                CMS QueueItems of state Assembly running. Checked Items: 0; Recovered Items: 0;                                                                                Recovery Failed Items: 0; Real running Items: 0#
#1.#001635730592000F0000000900002A400004B3E754AAB68F#1323706046134#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###finished recovery#
#1.#00163573059200140000000300002A400004B3E7AA40154F#1323707482010#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##b9c439d024de11e1a4ee001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_10##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
Thanks

Hi,
Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
Ever wondered how and where the XI pipeline gets executed? It happens in the ABAP stack.
All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
Take a look at the XI overview doc to understand this better,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3d3c390-0201-0010-c490-bd85917138c8
Regards,
Bhavesh

ABAP aND Java Stack

Whats the use of an ABAP and Java Stacks in XI? What exactly they are doing for XI?
Thanks.

Hi,
Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
Ever wondered how and where the XI pipeline gets executed? It happens in the ABAP stack.
All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
Take a look at the XI overview doc to understand this better,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3d3c390-0201-0010-c490-bd85917138c8
Regards,
Bhavesh

File-File: Message are in Waiting state in Integration Engine

Hi,
I am trying to execute File-File integration scenario and the message is in Waiting state in Integration Engine.
I am getting the following error in sxmb_moni:
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>Server repository could not create function template for 'SMPP_CALL_JAVA_RUNTIME</SAP:P1>
I am getting the following error in the Visual Admin Trace:
com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template for 'SMPP_CALL_JAVA_RUNTIME3' caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: User SAPJSF has no RFC authorization for function group SYST .
Can any one tell me how to provide RFC authorization to SAPJSF user.
Thanks in advance,
Nagarjuna

hi,
that is the reason for your problem
The user entered for LOGON in that does not have the requisite privileges.
Would sugget you contact your basis team and ask them to make the connection going. Then, this problem will be resolved.
To add more, SLDAPI and the rest are used for the connection between your ABAP and JAVA Stack. As, your mapping gets executed in the JAVA stack, during the execution, as this connection failed, so did your process.
Get this onnection up and reunning and it willsolve this issue.
Regards,
Bhavesh

How ABAP and JAVA stacks are connecting

Hi Experts,
I have a doubt in pi. We are developing Message Mapping in IR, it means it is running on JAVA STACK. But we are checking any mapping error in SXMB_MONI which will run on ABAP STACK.
Now My doubt is " How JAVA and ABAP stacks are connecting to each other and How we are able to see Mapping error in Integration Engine which resides on ABAP stack even though we create Mapping in IR which runs on Java".
Thanks&Regards ,
Gajapathi.

Hi Gajapathi,
How JAVA and ABAP stacks are connecting to each other
PI manages using single database for both JAVA and ABAP servers. But both access them using different schema. They connect using RFC protocol via SAP Java Connector (JCo Connector).
How we are able to see Mapping error in Integration Engine
which resides on ABAP stack even though we create Mapping in IR which runs on Java".
So when you create a object be it mapping or interface or any XI objects, it is stored in Single Database. When you use ABAP sxmb_moni for monitoring the message, it uses ABAP related schema to access the message.
I hope it answers you query.
Regards
Ramesh

[Integration Engine Configuration Data] Error: No access to system landscap

Hi all,
When configuring Integration Engine Data (To go to 'Integration Engine Configuration Data' screen: Tcode: SXMB_ADM -> Choose: Integration Engine Configuration -> F8), we want to load Configuration from System Lanscape by choose F6, an error occur with message as below:
No access to system landscap
So that we can't load configuration from our System Landscape.
We have correctly configured other below:
     - We use http port for corresponding Integration Server.
     - Business System with role 'Integration Server' created correctly in SLD.
     - T-code SLDCHECK is all OK.
     - T-code SXI_CACHE is all OK.
Anyone can please help me correct this error ?
Point will be reward for any valuable answer,
Thanks a lot,
Vinh Vo

Please can you check if your RFC destination SAPSLDAPI and LCRSAPRFC are working both ABAP and Java stack.
just check the reply from Udo and jai's reply
R3 Connecte XI 3.0 Problem
also check page no 18
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283

Using the SOAP inbound channel of the Integration Engine

Hi,
I am following the blog of Stefan Grube.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
However I have difficulties.
Is this blog still relevant for SAP PI7.10?
I have set this up as a test for a scenario I have.
Current Scenario NOT using your Blog and working perfectly.
SandBox PI Development PI
File > SOAP > SOAP > ABAP Proxy
What I am attempting now is.
SandBox PI Development PI
File > SOAP > Integration Engine > ABAP Proxy
I am using our SAP PI Sandbox to push a SOAP message using a Receiver SOAP adapter channel.
Transport Protocol: u201CHTTPu201D
Message Protocol: u201CSOAPu201D
Conversion Parameters: u201CDo not Use SOAP Envelopeu201D
Target URL: u201Chttp://<Integratio Server Host Development PI>:<Port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=FigmentD&Interface=urn:figment-co-za:fleetcard:efuel_50ppm^oa_Msg50ppm&QualityOfService=ExactlyOnce&sap-user=<PIAPPLUSER>&sap-password=<PASSWORD>u201D
SOAP Action: u201Chttp://sap.com/xi/WebService/soap1.1u201D
I am however getting the following error on the SandBox Pi AE.
u201CSOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 MOVED TEMPORARILYu201D
Please can you assist in this matter.
Regards
Willie Hugo

Hi williem,
Stefans weblog works great. The error you are getting is some wrong data you are sending. Please verify the data you are sending is correct. Also check this threads for the same errror:
ADAPTER.HTTP_EXCEPTION / HTTP 302 Moved Temporarily
Re: SOAP client receives HTTP 302 Found
Re: Synchronous RFC-XI-Web Service with no request method
HTTP Error (302) Found when calling Web Service on XI
Regards,
---Satish

Integration engine 7.1 - abap or java

Similar Messages

Maybe you are looking for