***Stack of XI adapter

I know that Proxies (sender) doesn't use the adapter.If we use receiver as a proxy we need an adapter.
Where does this XI adapter lie in case of receiver.
I think it is JAVAstack.right?
Thanks,
Srinivasa

> I know that Proxies (sender) doesn't use the adapter.If we use receiver as a proxy we need an adapter.
I think you are talking about communication channels, not adapter.
> Where does this XI adapter lie in case of receiver.
XI adapter is in ABAP stack, no difference between sender and receiver.

Similar Messages

PI 7.4 single stack web service adapter alternative

Hi All,
Looking at upgrading from 7.11 dual stack to 7.4 single stack and I know the web service adapter is no longer available (at least according to anything I have read, but I understand it is in the pipeline).
How do we provide and consume web services on a single stack environment?
I have looked hard, but if the answer has been before me I have failed to recognise it due to my own limitations.
If someone could point me in the direction of any articles/blogs/discussions that answer my question or can answer the question I would be very grateful.
thanks in advance
Julian

Hello Julian,
WS adapter has not been migrated from ABAP stack to Java stack so far - so, in Java-only installation options of PI, there is no analogue for it from functional replacement perspective.
For web services consumption, the SOAP adapter can be used, but it is applicable for plain SOAP communication, not for WS-RM.
Regards,
Vadim

Unknown receiver adapter (name = SOAP)

Hi,
I have an IDOC-XI-SOAP(Web service) scenario which is resulting in the following error
<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="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>SOAP</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown receiver adapter (name = SOAP)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any pointers..?

hi Siru TK
Check with thread
receiver soap error
Error in SOAP synchronus request.
Thanks!!

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

PI Pipeline Doubt : Pipeline Steps in ABAP stack and JAVA stack

Hello
Can anyone please assist me with which stages steps of the PI Pipeline are executed on the Java or the ABAP stack.
Receiver Determination
Interface Determination
Message Split
Message Mapping
Technical routing
Call Adapter
Also can anyone please provide links relating to the PI architecture diagram describing it from ABAP and Java Stack Perspective and not from the Components perspective i.e. Integration Repository and Directory.
Thanks.
Kiran

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.
Most of XI pipelines 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.
Message, Java & XSLT (under Imported Archives) mappings are executed at Java stack;
ABAP & XSLT (in ABAP stack) mappings are executed at ABAP stack.
PI Architecture look threads
Architecture
/message/5802842#5802842 [original link is broken]

Java and ABAP Stack

Hi All,
I am still not clear about role/function of java and abap stack in XI.
Can anybody explain?

Sireesha,
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.
Most of XI pipelines 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.
please go through links::
ABAP and JAVA in Netweaver stack
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/4aa47d27-0a01-0010-5db4-bb62dfc8c069?prtmode=navigate

Unknown outbound adapter (name = SOAP)

Hi folks,
I am working on a PROXY --> PI --> SOAP scenario. I get this error in PI'S SXMB_MONI. How to resolve this issue and what is causing it?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<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="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>SOAP</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown outbound adapter (name = SOAP)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is very much appreciated.
Regards,
Adil Khalil

Hi Adil
Have you tried out the solution provided by Nisar Khan in the thread below. It looks similar to your case.
http://scn.sap.com/thread/609965
Here is another case similar to yours. You need to check if your SLD and cache are ok.
RFC Adapter Problem: Adapter Engine Field Blank
Rgds
Eng Swee

RFC Adapter Problem: Adapter Engine Field Blank

Hi,
I want to invoke a BAPI defined on a R/3 system. I am trying to create a RFC Adapter in the Integration Directory by creating a communication channel.
The problem I am facing is that when I define the Adapter Type as RFC, the Adapter Engine dropdown list is blank and it does not contain any entries.
On passing a document through XI, I can see the following error in the monitor:
<SAP:Code area="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>RFC</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown receiver adapter (name = RFC)</SAP:Stack>
what do i need to configure on the XI and R/3 side ?
thanks,
Manish

i followed the steps but i am not getting the populated adapter engine list.
Actually, the Association shows a list of logical systems to be added (Application System, BC Application Server, BC Central Server Instance .....). I experimented with many systems but it is not working.
My basic problem is I need to call a BAPI from XI. The XI monitor shows the error :
Adapter Name Invalid.
Unknown Receiver Adapter (name=RFC).
Now, for the RFC adapter, I have not given it any name. My Communication Channel is called GeneratedChannelRFC. I am not sure where this error is coming from. I would appreciate any help to solve this error.
thanks,
Manish

Trying to integrate with User Messaging Service adapter in SOA suite.Can it be possible through an JMS interface.

Trying to integrate with User Messaging Service adapter in SOA suite. Can it be possible through an JMS interface.
I have an JMS backend integrated to Oracle B2B. Is it possible to send an email protocol message using JMS interface to B2B where User messaging Service has been implemented. The adapters required for UMS have been deployed and the sdpmessaging jar files also have been added to the classpath. The only problem i face is i dont have an BPEL system to integrate where as in the forums it has been mentioned how to post a message using BPEL.
Please let me know if there is a way to integrate the adapter with JMS interface.
Thanks in advance
Deepak

If I remember correct, to use JCA adapter with SOA stack requires that adapter implement some Oracle API.
The Adapter SDK is a light-weight tool kit that enables rapid implementation and deployment --- http://www.oracle.com/technology/products/integration/adapters/pdf/DS_OracleASAdapter.pdf
http://download.oracle.com/docs/cd/B16981_04/current/acrobat/cct115dg.pdf
Mostly you will have to wrap your jca adapter to make it available in SOA suite/stack.
Other option is that you adapter provider would have given CCI interface or some custom interface which can be used for invoking adapter end-points.
Manoj

Bluetooth stack/jabra a320s dongle

i bought jabra a320s which came with widcomm drivers and i have toshiba bluetooth stack on my S300m laptop. The toshiba bluetooth stack is not recognising my A320s dongle. it says please plugin BT adapter. i uninstalled widcomm and tried with toshiba v6.10...and also v6.30....i want my a320s to work with toshiba rather than widcomm bluetooth software.
How do i do it?

Common error to the jabra hardware, go to the jabra website and ensure that they posted a Vista bluetooth stack driver. You may not have a choice but use their driver. Toshiba Bluetooth stack is genuinely adaptable to all hardware device with few exceptions.

MBP 15' 2011 Mini display port to LED monitor/TV resolution issue

Hello,
I have just bought a Mini Display - VGA adaptor which I am plugging to a Samsung 23' LED monitor via a VGA/DVI adaptor. I manage to get a clone view but unfortunately, the maximum resolution offered is 1650x1050 when my Samsung LED monitor has resolution of 1920x1080. Therefore, part of the screen remains black.
... also, when I plug the Mini display port to VGA to my Philips 47' VGA port, I got a message that there must be a problem with the connection and again, maximum resolution offered if 1440x10.. and therefore 20% of my TV screen space remains black.
At last, when I launch Windows7 via bootcamp, this is even wost : when I select the max resolution (1440x10..), the pictures remains freezed on my TV and I can't even move the mouse (while the mouse is moving on the MBP screen...). Only coming back to a very small resolution 800x600 or so will enable me to get control of the win7 desktop on my TV...
Thank you in advance for your help
Greg

I have just bought a Mini Display - VGA adaptor which I am plugging to a Samsung 23' LED monitor via a VGA/DVI adaptor. I manage to get a clone view but unfortunately, the maximum resolution offered is 1650x1050 when my Samsung LED monitor has resolution of 1920x1080. Therefore, part of the screen remains black.
If you are using the monitor in Mirrored mode, its resolution setting will always be exactly the same as that of the built-in display. I presume you have the high-res 15" MBP display, with a native resolution of 1680 x 1050. If that's true, I suspect your monitor is indeed in Mirrored mode, and that's why you can't set the monitor to its native 1920 x 1080 resolution. If you press Command+F1 to toggle the mnitor into Extended Desktop mode, you'll be able to set its resolution independently of the built-in display. Or if you use only the external monitor, with the MBP display closed, you'll be able to set the monitor's resolution to whatever it supports.
http://support.apple.com/kb/HT3131
Stacking one video adapter on top of another is usually a recipe for trouble. It's always best to keep things as simple as possible. Use one adapter that gets you from mini-Displayport to whatever input you want to use on the TV or monitor.

BI ABAP and BI PORTAL

Hi
I would like to know some basic information on the following questions:
1. What is BI ABAP stack and BI ABAP System?
2. What is BI Portal and its use?
3. How can we know that J2EE is installed on BI Server?
4. How does this all together work?
Regards
Annie

Hi ,
Ans 1.
Tha ABAP stack consists of your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine
t-code: sxmb_ifr for IR,ID,RWB,SLD.
sxmb_moni to monitor the messages in integration engine
Ans 2. bi portal
The enterprise portal is the front-end component for SAP NetWeaver. It offers a single point of access to SAP and non-SAP information sources, enterprise applications, information repositories, databases and services in and outside your organizationall integrated into a single user experience. It also provides tools to manage this knowledge, to analyze and interrelate it, and to share and collaborate on the basis of it.
This link can provide more information:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/76bd3b57743b09e10000000a11402f/content.htm
check this to instal..
Download SAP J2EE Engine
regards,
shikha

Not possible to run CodedUI tests on Windows 7 embedded

Hi all,
I am trying to get my CodedUI tests running on the target machine with Windows 7 Embedded.
For that, I installed on the target machine:
Visual Studio 2010 Test Agent
VS2010 SP1
Next I try to run the CodedUI test from the command line using mstest.exe (since no Visual Studio may be installed on target
machine). However, before even executing the first line of code in my test, mstest fails after showing a popup window with following message:
"the ordinal 459 could not be located in the dynamic link library urlmon.dll"
When looking in the detailed logs of QTAgent32.exe I see a 'System.BadImageFormatException' thrown by the PluginManager of CodedUI when trying to
start an Internet Explorer plugin. See detailed stacktrace below this message.
This might be caused by the fact that this Windows Embedded installation does not contain Internet Explorer (for security reasons). The CodedUI test
and application under test however do not need Internet Explorer at all, the application is a WPF application.
So, my questions:
- Does anyone know how to get rid of this error without installing Internet Explorer?
- Any ways to prevent MsTest.exe to start the IE extension for a CodedUI test?
Some things I tried already but did not bring success:
- Run a completely empty CodedUI test; it triggers the same error.
- Remove IE extensions from C:\Program Files (x86)\Common Files\Microsoft Shared\VSTT\10.0
- Remove unneeded things (datacollectors) from MsTestSettings file.
Any help/ideas appreciated!
Jan Lavrijsen
Complete stack trace:
Agent: adapter run thread for test 'CutPowerDuringImport' with id 'b7c688eb-89ac-4654-b638-a5699f579871'
»DebugInfo
»Trace »FirstChanceException
»FirstChanceException 'Microsoft' causing 'System.BadImageFormatException' - Retrieving the COM class factory for component with CLSID {25336920-03F9-11CF-8FD0-00AA00686F13} failed due to the following error: 800700b6 The operating system
cannot run . (Exception from HRESULT: 0x800700B6).
»[CausedBy=Microsoft],[FirstChanceException=System.BadImageFormatException],[Count=1]
»CallStack: at Microsoft.VisualStudio.TestTools.UITest.Extension.IE.IETestPlugin.StartSession(System.Boolean recordingSession) [IL: 0x19][Native: 0x4B]
at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestPluginManager.StartSession(System.Boolean recordingSession) [IL: 0x2B][Native: 0x95]
at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestService.StartSession(System.Boolean recordingSession) [IL: 0x34][Native: 0xA9]
at Microsoft.VisualStudio.TestTools.UITesting.Playback.StartSession() [IL: 0x37][Native: 0x6C]
at Microsoft.VisualStudio.TestTools.UITesting.Playback.Initialize() [IL: 0xB5][Native: 0x163]
at Microsoft.VisualStudio.TestTools.UITesting.CodedUITestExtensionExecution.BeforeTestInitialize(System.Object sender,Microsoft.VisualStudio.TestTools.UnitTesting.BeforeTestInitializeEventArgs e) [IL: 0x3C][Native: 0x76]
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecution.RaiseBeforeTestInitialize(Microsoft.VisualStudio.TestTools.UnitTesting.BeforeTestInitializeEventArgs args) [IL: 0x15][Native: 0x17]
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.RunInitializeMethod() [IL: 0x3E][Native: 0x96]
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.ExecuteTest() [IL: 0x8D][Native: 0x113]
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.Execute(Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestResult result) [IL: 0x46][Native: 0xD1]
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestRunner.ExecuteSingleTest(Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter executer,Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestElement test,Microsoft.VisualStudio.TestTools.Execution.ITestContext
testContext,Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestAdapterContext userContext,System.Boolean isLoadTest) [IL: 0x27][Native: 0x55]
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestRunner.Run(Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestElement test,Microsoft.VisualStudio.TestTools.Execution.ITestContext testContext,System.Boolean isLoadTest,System.Boolean
useMultipleCpus) [IL: 0x109][Native: 0x32B]

Hi Jan,
Thanks for your response:)
I think it is a good feedback for this issue, but as far I know, it is by design now, we need to use the IE extension for test projects. My understanding is that it would find the accordant UI Test Controls with your app UI controls, so it would search all
test controls include the IE controls, and then use one real UITestControl to instantiate an object which is equal to the real UI control, so we could playback the recorded action.
WinButton uICloseButton = this.UISnippingToolWindow.UISnippingToolTitleBar.UICloseButton;
But I think you can submit this feedback to Microsoft Connect feedback portal:
http://connect.microsoft.com/VisualStudio/feedback/CreateFeedback.aspx,maybe
Microsoft engineers will share us a more plausible explanation.
Thanks for your understanding.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

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

Xmltype.createxml not working after upgrading to 11202 from 10203

Hi,
i was referred here from Java Database Connectivity (JDBC) forum. the link to the original post:
using XML with websphere jdbc adapter 2.6 on 11.2.0.2
again, the adapter is using the function xmltype.createxml (and there it uses xmltype_lib) and it fails right at the beginning because it cannot parse the xml properly.
so what im asking is, was there any major changes from 10.2 to 11.2 to the way xml creation works? maybe a different encoding? how can i check the encoding of the xml created? is there a property for it?
thanks in advance.
Edited by: andrey on Mar 12, 2012 4:47 AM

yes the client and the server are same version.
the error stack from the adapter:
[Time: 2012/03/13 13:00:00.177] [system: ConnectorAgent] [SS: jdbc_orclConnector] [Thread: JDBC_ORCL.REQUECTQUEUEJmsThreadPool.thread18(#746207754)] [Type:error] [MsgID: 10556] [Mesg: Exception Detail: com.crossworlds.cwconnectorapi.exceptions.VerbProcessingFailedException
[Type: Error] [MsgID:37010] [Mesg: Stored Procedure Execution Failed: java.SQLException: [IBM-CrossWorlds][Oracle JDBC Driver][Oracle]
ora-30676: socket read or write failed
ora-06512: at "SYS.XMLTYPE", line 5
ora-06512: at "SCHEMA_NAME.FUNC_NAME", line 1695
ora-06512: at "SCHEMA_NAME.FUNC_NAME", line 78
ora-06512: at line 1

***Stack of XI adapter

Similar Messages

Maybe you are looking for