SOAP interface determination

Hi
A more philosophical question this time.
I am somehow familiar with SOAP and AFAIK the invoked method name, is given by the first XML element inside Body tag? Right?
So. Assuming, I am right, how XI SOAP adapter determines the correct interface? In communication channel there is a box to fill with "default interface" information... it is strange to have such a configuration box as if client send a request to unknown SOAP method an exception should be thrown and not a "default interface" used.
Also it is interesting that for SOAP channel it is possible to use the "nosoap" option... it does not make no sense as the called interface name is defined inside the soap body.
So any comments to describe how SAP XI treats SOAP request for determining the right method...
Thanks for you opinions and links to related materials.
PS. Answers rewarded

Hi
Thanks for the response... I have some issues with terms so maybe You could help me to clear things up.
> > ...
> The method name is relevant for a web service. The XI
> only routes the SOAP message to a receiver, so it
> does not care about the method.
> > ...
> The interface is not the same as the method.
In SOAP/WSDL terms there are operations in collected into one port (or service if we consider the option that only one port is defined inside WSDL service element). Right?
and each operation has (again lets make a simplification that there are synchronous SOAP operations discussed) a request message and a response message.
In XI/IR there are interfaces that have message types. Each message type can be built using one data type. And in scenario configuration I am able to define connections (using communication channel templates) between interfaces.
So. If an XI Interface is not the same thing as SOAP operations then how is it possible to use mappings? Any hints?
Or XI restricts the WSDL definition so that inside a wsdl:service there can be only one wsdl:port definition and used binding (and portType) can contain declarations for only one operation?
Pleas help me out with this
I appreciate it a lot

Similar Messages

When we will go for Ectended Interface Determination

extended interface determination example give me any one...
Regards,
Vinay

Enhanced (Mapping-Based) Interface Determination
Use
In an enhanced interface determination, you do not enter the inbound interfaces manually, but first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
For example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping). In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
Procedure at Runtime During Message Split
Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
Receiver Interfaces of Bulk Messages and Individual Messages
The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:
-          RFC adapter
-          SAP Business Connector adapter
-          File/FTP adapter
-          JDBC adapter
-          JMS adapter
-          SOAP adapter
-          Marketplace adapter
-          Mail adapter
-          RNIF adapter
-          CIDX adapter
The adapters also have to all run on the same Adapter Engine.
Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
Attachments from the original message are not appended to the messages resulting from the message split.
Activities
To execute a mapping-based message split, perform the following steps:
       1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
       2.      Integration Directory: Define the interface determination.
Note the following:
○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
○     The interface determination type must be set to Enhanced.
○     Select the multi-mapping you defined previously from the Integration Repository.
To select the interface mapping, use the input help ( ).
The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
regards,
Raj

Interface determination not found

Hi,
I am reading a file and trying to send it through a SOAP adapter.
I am getting the below error
Error when determining the inbound interface: No interface determination found for outbound interface http://test.com.testFlies_OB: Error while determining root tag of XML: BOM / charset detection failed
No interface determination found for outbound interface http://test.com.testFlies_OB: Error while determining root tag of XML: BOM / charset detection failed
Error while determining root tag of XML: BOM / charset detection failed
Error while parsing an XML stream: &#39;BOM / charset detection failed&#39
Need help.

Hi,
just check in ID, whether in receiver determination, you have specified interface determination.........if yes, then check whether it is activated or not............if not activated, then activate it...........
if it is activated and still you get this error, then ask your basis guys to do a full CPACache refresh using XIDIRUSER..........then re-run your scenario.
Regards,
Rajeev Gupta

Receiver and Interface Determination, Sender and Receiver Agreement

Hi Experts,
Could you please tell me, what Receiver Determination, Interface Determination, Sender Agreement and Receiver Agreement we have to use for the below blog.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
Regards
Sara

Hi Sara,
WS->BP
Receiver Determination: Sender IF, Sender NS, Sender BS determine the BP
Interface Determination: Sender IF, Sender NS, Sender BS determine your start msg IF (abstr IF) and IF mapping
Sender Agreement: SOAP sender channel for that Sender IF, Sender NS, Sender BS
Receiver Agreement: not reqired
BP->DB
Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (DB)
Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
Sender Agreement: not reqired
Receiver Agreement: JDBC receiver channel for that Inbound IF, NS and 3rd party BS
BP->File
Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (File)
Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
Sender Agreement: not required
Receiver Agreement: File receiver channel for that Inbound IF, NS and 3rd party BS
Regards,
Udo

HTTP to RFC Interface Determination problem

Hi experts,
I am doing HTTP <-> RFC scenario mentioned in blog
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
almost everthing is done; but while configuring the interface determination, i am not able to see the inbound interface.
your valuable help would be appreciated
Regards
Sumit Bhutani

Hi Bhavesh,
Thanks for your quick response; this problem has been resolved, but while testing my scenario using RWB i am getting this error.
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read payload from the message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please suggest on this
Thanks
Sumit

Extended Receiver & Extended Interface Determination

Hi Experts,
Can any tell me what is Extended Receiver & Extended Interface Determination.
And the Difference between Standard Receiver & Standard Interface Determination.
were to use Extended Receiver & Extended Interface Determination.
Thanks in advance
Shakif

Hi,
Standard Receiver Determination Features
Specifying Receivers
You can specify receiver parties and receiver services. To specify the receiver in more detail, you have the following options:
●     Select the receiver from the Integration Directory
●     Specify a constant value for the receiver
●     Determine the receiver dynamically from the message content
To enter the necessary details, use the following:
●     The party editor for specifying the receiver party
●     The service editor for specifying the receiver service
To call the relevant editor, in the Display/Edit Receiver Determination editor in the Configured Receivers frame, call the Input Help ( ) in either the Party or Service column.
Defining Conditions
You also have the option of specifying the conditions to be applied when forwarding a message to the receiver(s) in a receiver determination.
Generally, a condition relates to the contents of a message; if a specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver(s).
●     If you want to specify a new condition for forwarding the message to a receiver, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert New Condition () and call the condition editor by using the input help ().
●     If you want to specify a new condition for forwarding the message to multiple receivers, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert Line After Selection ( ) and call the condition editor by using the input help ().
In the condition editor, you can select an element from the message payload and specify a value with which the value of this element is to be compared at runtime.
Enhanced Receiver Determination
Use
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
You can of course formulate conditions in a standard receiver determination that relate to the content of the message. However, you have to specify the names of the receivers (to which the message is sent under the formulated condition) explicitly in the receiver determination. If you create an enhanced receiver determination, you do not have to specify receiver names at this stage.
Integration
During the definition of the interface mapping, you assign the abstract message interface ReceiverDetermination as the target interface. The message interface ReceiverDetermination is in the Integration Repository in the software component SAP BASIS (namespace http://sap.com/xi/XI/System).
The message interface uses the message type Receivers and the data type Receivers. The data type Receivers describes a list of receivers and has the following structure:
The following instance of the data type Receivers contains two receivers. The first receiver comprises a party and service and is identified by a DUNS number; the second receiver comprises a service without a party.
<Receivers>
<Receiver>
    <Party agency=016 scheme=DUNS>123456789</Party>
    <Service>MyService</Service>
</Receiver>
<Receiver>
    <Party agency=http://sap.com/xi/XI scheme=XIParty></Party>
    <Service>ABC_200</Service>
</Receiver>
</Receivers>
You can specify party and service for each receiver.
Activities
       1.      Integration Repository: Define the interface mapping. Assign the message interface ReceiverDetermination as the target interface (see above).
       2.      Integration Repository: Define the message mapping or mapping program that is to determine the receivers at runtime. Assign the message mapping or mapping program to the interface mapping.
       3.      Integration Directory: Define an (enhanced) receiver determination.
○     Enter the outbound interface of the interface mapping from step 1 in the key of the receiver determination as the outbound interface.
○     Assign the interface mapping created in step 1 to the receiver determination.
Standard Interface Determination
Use
You can specify to which inbound interfaces at the receiver the message is to be sent at runtime. You also have the option of specifying a mapping and (when multiple inbound interfaces are defined) a condition for each inbound interface.
Note the following fundamental cases when assigning multiple inbound interfaces:
Multiple Different Inbound Interfaces
Imagine you enter the following interface assignment.
Inbound Interface
Condition
Interface Mapping
IF_1
M_1
IF_2
M_2
After the interface determination is evaluated, this results in two messages with the same payload at runtime. A different mapping (either M1 or M_2) is executed for both messages and then they are forwarded to the two interfaces (either IF_1 or IF_2) at the receiver.
Multiple Identical Inbound Interfaces with Conditions
Imagine you enter the following interface assignment.
Inbound Interface
Condition
Interface Mapping
IF_1
B_1
M_1
IF_1
B_2
M_2
In this case, the conditions are evaluated during the interface determination step. If condition B_1 is true, then mapping M_1 is executed; if condition B_2 is true, then mapping M_2 is executed. The message is forwarded to the same inbound interface at the receiver in both cases. Unlike in the case described above, this does not result in multiple messages with the same payload because only one condition can ever be true at runtime.
Features
You enter the assignment between the outbound interface and the inbound interface(s) in a table. Each table line represents exactly one assignment between the outbound interface and an inbound interface. To insert or delete lines, choose Insert One Line After Selection () or Delete Selected Line ().
Enhanced (Mapping-Based) Interface Determination
Use
In an enhanced interface determination you do not enter the inbound interfaces manually, but instead first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
For example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping). In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
Procedure at Runtime During Message Split
Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
Receiver Interfaces of Bulk Messages and Individual Messages
The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:
-          RFC Adapter
-          SAP Business Connector Adapter
-          File/FTP Adapter
-          JDBC Adapter
-          JMS Adapter
-          SOAP adapter
-          Marketplace adapter
-          Mail Adapter
-          RNIF adapter
-          CIDX Adapter
The adapters also have to all run on the same Adapter Engine.
Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
Attachments from the original message are not appended to the messages resulting from the message split.
Activities
To execute a mapping-based message split, perform the following steps:
       1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
       2.      Integration Directory: Define the interface determination.
Note the following:
○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
○     The interface determination type must be set to Enhanced.
○     Select the multi-mapping you defined previously from the Integration Repository.
To do so, call input help ().
The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
Regards,
Phani
Reward points if Helpful

Interface determination issue.

Hi Experts,
We are using Idoc(Matmas) to file scenario wherein we are facing the below issue
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="IF_DETERMINATION">NO_IIF_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to find an inbound interface</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The condition used in Interface determination is /Zmatmas05/idoc/e1maram/mstae=mw
Please let me know how to rectify this issue.
Thanks & Regards,
Ranganath.

Hello,
Try using double slash in your xPath (for PI7.1) instead of just one, so from
/Zmatmas05/idoc/e1maram/mstae=mw
to
//Zmatmas05/idoc/e1maram/mstae=mw
Hope this helps,
Mark

Error while testing File-PI-SOAP interface

Dear All,
We are working on File-PI-SOAP interface in which we have exposed a functional module from ECC server as receiver webservice. When we are testing the the interface we are getting following error :
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 407 Proxy Authentication Required.
In the receiver SOAP communication channel we have provided the required ECC login & proxy authentication credentials and also we are able to open the URL from PI server. Kindly let us know what more settings are required o make this interface running.
Regards,
NJ

Hi,
This is a synchronous interface and I want to send the output from webservice as a file to third party system.
We are just working on a demo interface, so we have created a webservice of a function module of ECC and also our interface is File-PI-SOAP.
We have also given the login credentials for proxy authentication but still we are getting the error the
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 407 Proxy Authentication Required
Kindly let us know, how can we resolve this error.
Regards,
NJ

Interface determination Issue in PI7.1

Hi ,
I am working on PI 7.1
Problem 1:
I am not able create any interface determination objects. There is a lock object created everytime I use the wizard. Unlocking the object and run the cache refresh has not helped..
I am able to create the interface determination manually after removing the lock. But now I am not able to associate a operation/interface mapping to the Interface determination . After I selected a message/service interface in the Interface determination, I clicked on the mapping option. The possible mapping was showed up on the list. But once I select one option from the list it does not show up in the interface determination. The field remains blank.
Problem 2:
I am unable to open the existing interface determination also. These interface determinations are present in the DEV environment.I have taken the system copy of the dev environment on the UAT environment.I am getting the below error when i try to open the interface determination
====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
====================================================================
== Content from the LogHandler =====================================
====================================================================
#300 11:56:48 [AWT-EventQueue-2] WARNING com.sap.aii.utilxi.swing.toolkit.ButtonPanel: Special button of type 4 was not added in order (class com.sap.aii.utilxi.swing.toolkit.ButtonPanel)
#299 11:56:48 [AWT-EventQueue-2] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)

Hi Shilpa,
Ask your basis guys to check the SP level of JAVA components in system component information of your PI7.1 system............ask them to check for patches for your SP level of PI7.1 or upgrade to a higer SP level...........
Also try this from your PI IB webpage, go to Administration - JAVA web start administration - then click on execute link in the status window and do a reinitialization of your JAVA web start...........then close your ID and reopen your ID........then create your interface determination again in ID...........
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:05 AM
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:25 AM

Error while opening the Interface determination

Hi,
I am working on PI system(unix platform) which is a system copy(from a windows platform).
When i tried opening few interface determinations which are already present in ID, it gives me following Error.
====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:643)
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:612)
     at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:160)
     at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)
     at $Proxy26.read(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)
     at $Proxy27.read(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sap.aii.ib.clsif.login.BeanProxy.invoke(BeanProxy.java:114)
     at $Proxy27.read(Unknown Source)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:101)
     ... 39 more
Caused by: java.io.InvalidClassException: com.sap.aii.ib.bom.gen.container.ContainerElementState$XsdSimpleState; local class incompatible: stream classdesc serialVersionUID = 42, local class serialVersionUID = -6470496719860432109
     at java.io.ObjectStreamClass.initNonProxy(Unknown Source)
     at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
     at java.io.ObjectInputStream.readClassDesc(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.readObject(Unknown Source)
     at java.util.Hashtable.readObject(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.readArray(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.readObject(Unknown Source)
     at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.readResult(P4InvocationHandler.java:303)
     at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:138)
     ... 52 more

Hi,
This is the problem with the XI system. You have to add some patches.
For that check this link same problem solved here.
PI 7.1 : Java exception creating new "Integration process"
Thanks.

Interface determination : How to populate an Operation Mapping parameter

Hi experts,
I'm creating an interface determination, I have an Operation Mapping in it. This operation mapping has an inbound parameter. When Configurating this parameter I can choose between putting a constant or getting the value from a "container". Does anybody knows where this container will be? Is it possible to take the parameter from an export parameter from Integration Process(BPM)?
My interface:
BPM->IDOC
Regards
Gonzalo

Hi Stefan,
What I wanted is leaving the mapping outside the BPM, instead that I can leave it inside and the result will be the wanted. What you mean implies something similar.
I'm going to explain why, from the process dessign point of view, I want to leave the mapping outside.
1.-I send an IDOC from my ERP
2.-This IDOCs starts a BPM who, in a synchronous way, makes some updates in a DB.
3.- Functionally speaking this updates could return a 0 if OK or a -1 if NOK
4.-The BPM have to return an ACK to the ERP.
For constructing this ACK I need my original IDOC and the result of the updates (-1 or 0).
-If I put the mapping inside the BPM it will work (and that will probably be the final solution).
-But, for a better performance and dessign, I wanted to leave the mapping outside.
-I also want to know if the container in the interface determination we talked before can be used or what it means. (So let me know if you find out something about)
-The third reason is that I find interesting speak about this topics in the forum if you know what I mean :-D
Regards
Gonzalo

Receiver Determination and Interface Determination Condition conflict in ICO

Hi,
I found a strange issue today while configuring two receivers using the Receiver and Interface Determination conditions.
Sender - Proxy Service
Receiver1 - ReceiverA
Receiver2 - ReceiverB
Receiver Determination Condition : When Field1 = 100, message should flow to ReceiverA and ReceiverB
Interface Determination Condition (ReceiverA) : When Field1=100 and Field2=50 message should flow to a specific interface in ReceiverA
There is no Interface Determination condition for ReceiverB, for all messages having Field1=100, it should go to ReceiverB.
Test Scenarios:
1) Field1=100, Field2=50 : Message flows successfully to ReceiverA and ReceiverB
2) Field1=100, Field2=89 : Message fails to process from ECC itself throwing Interface Determination not found error. Ideally this is a positive scenario for ReceiverB and it should send the message to ReceiverB without any errors. But, this did not happen in this case
I tried the same by configuring the conditions completely in Receiver Determination itself without using the Interface Determination, it worked perfectly fine. But, just wanted to understand that if this is an expected behavior.

Hi Sherin,
As there are two receivers Receiver A and Receiver B.You need to create two bussiness components and two communcication channels for two receivers and one Reciver Determination, two Interface Determination,two Receiver Agreement.In Receiver Determination you need to keep the below and condition.
In the above screenshot the two receiver are Receiver B and Receiver C and Field 1 is Key_Value and Field2 is Emp_ID.
If the Key_Value=100 and Emp_ID =22 then the message should go to both the receivers B & C by keeping the following AND condition
If the Key_Value=100 and Emp_ID is not equal to 22 then the message should go only to Receiver B by keeping the following condition
You need not keep any condition in Interface Determination just create 2 Interface determination for two receivers.
Hope this helps you.
Thanks,
Durga.

Enhanced Interface Determination in PI 7.1

Hi All,
My scenerio will work as follows
The changes in the process order will triggered by the client system .I will get the already converted XML file.I have used the file adapter in the sender side to pick the file.At the receiver side I am using the 3 custom BAPIs.I have used 3 message interface instead of multi-mapping as the inbound interfaces.
The Logic is like that:
If the Process order status is = 1 then call BAPI 1,if it 2 then call BAPI 2 & call BAPI 3.
Please tell me the following
1.Is there Enhanced Interface Detrmination option available in PI 7.1?If so then can I mention or call 2 BAPIs in one condition over there?Do I need to write ABAP condition?
2.Is Enhanced interface Determination possible when I have used 3 inbound interfaces instead of multi-mapping?
3.From my point of view I need the following in my scenerio
- 3 message mappings(Graphical Mappings),
- 3 interface mappings,
- 1 sender agreement,
- 1 receiver determination,
-1 interface determination(with 2 conditions in it),
-3 receiver agreements.
Am I right?
4.How many sender and receiver agreements do I need?
5.Do I need to go for Enhanced receiver determination?
Thanks in advance.

the same status node in the source file on which I will impose check will call the selective inbound interface based on the
status node.Is it?If so,then do I need to mention anything other than the check condition in XPATH e.g.do I need to mention any
mapping program or inbound interface (though I dont thing so but I am still confused) ?
Yes, apart from specifying the condition in the Condition Editor you also should mention the corresponding Inbound Service Interface and Interface Mapping (if any).
Condition will only cause the execution of that particular line and wont automatically call the mapping/ interface (unless these are specified in the Interface Determination).
Is XPATH the alternative option in condition editor which can be skipped though I would surely like to go through it as
much as possible?
XPATH is the easiest option to specify a condition....other option includes the use of a Context Object.
So as of now think that you cannot skip XPATH (for this particular requirement).
Once you become an expert in using a XPATH (which you can in a days period) you can try out for Context Objects.
Regarding Test Case:
There is no standard template for this.....i would suggest check with peers in your company.....many a times companies have their own templates for test cases alongwith the possible cases....then referring to those test cases you can build the cases for your scenario. Avoid a direct copy of the test cases.....many wont be relevant for your case.
Regards,
Abhishek.

Condition Based Interface Determination in ICO (AAE) - PI 7.1 EHP1

Hi Friends,
We have PI 7.1 EHP1 - SP 04.
In our scenario, we have 1 outbound interface and 2 inbound interface. Based on condition, it needs to select the first inbound interface or second inbound interface.
In the normal configuration, we are able to select. (By click + icon and add condition in the Receiver Interfaces in Interface Determination Step)
When we create configuration using ICO (Integrated Configuration), there is no option in "Receiver Interfaces" Tab to add two inbound interfaces with condition.
Could you please clarify how do we do this in ICO?
Kind regards,
Jegathees P.

IMHO, condition based interface determination is not possible in ICO.
Use Multiple inbound service interfaces... You can handle in design level .. ESR level.
Check the Abhishek's blog... This might be helpful.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1571?quicklink=index&overridelayout=true
Note: Since in your case you need two receiver agreements, you cannot handle through ICO. The above link might be helpful to do multimapping without BPM.
Edited by: Baskar Gopal on Apr 26, 2011 9:53 AM

PI 7.1 Condition in interface-determination

Hi everybody,
I want to process interface determinations depending on payload. But when opening the condition editor in interface determination, the interface on which to apply the condition is not obtained!
What could be the reason?
Thanks
Regards Mario

Hey Mario .. that's a bug. Thanks for pointing this out. Never noticed till now
Regards,
Neetesh

SOAP interface determination

Similar Messages

Maybe you are looking for