About interface message

Hi,
From the manual, message is created from session. That's to say,we can only use the method of the message in the main programe. It's better if we can use message type in class made, not only in the main programe,can we?
Thanks,
Ping

Thank you for your reply.
Maybe i didn't make it clear: i get used to j2se development, and it's easy to use. However, because jms is a part of j2ee, we should use other development tool. i have some little applications about cryptography developed in j2se, and i want to use jms for use of message sending and receiving, How can I do?
Cheers,
Ping

Similar Messages

About interface mapping

what are there case about interface mapping?
i knew that the following:
outbound to inbound
abstract to abstract.
what else the case?

Hi joy zheng ,
These r the details about interface mapping :
Interface Mappings
You can define mappings for an interface pair (source and target interface) by using message interfaces and message types in the Integration Repository.You can also define the corresponding mappings when the source or target interface is an IDoc, an RFC, or another interface connected by an adapter.
When defining mapping programs for request, response, or fault messages, the definition is first separated from the interfaces that reference the corresponding message types. Furthermore, you can reuse a message type for multiple interfaces. This means that the simple definition of a mapping program is not sufficient to establish a connection (that is based on the assignment of outbound and inbound interfaces).
This role is undertaken by the interface mapping:
●     An interface mapping specifies the corresponding mapping programs for request, response, or fault messages for a selected interface pair. You use an interface mapping to register mappings for an interface pair.
●     You can also specify multiple mapping programs to be executed one after the other in the case of requests and responses for an interface mapping.
You can also define multiple interface mappings for the same interface pair, to provide multiple variants in the Integration Repository. At configuration time, the customer can select the appropriate mapping in an interface determination and save it in the Integration Directory
Use :
Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time . The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.
Features
Executing Multiple Mapping Programs for One Direction
By using an interface mapping you can execute multiple mapping programs consecutively for the transformation of a request or response message. In such cases, an interface mapping comprises multiple steps for which the following applies:
●     The steps are executed in the sequence specified (from top to bottom). The result of the mapping program from the previous step is forwarded to the mapping program of the subsequent step.
●     Each step can reference a mapping program that executes a 1:1, 1:n, n:1, or an m:n transformation. In the case of multi-mappings (1:n, n:1, or m:n), the previous step must create the same number of messages that the subsequent step expects.
●     Multi-mappings use one envelope to put all messages in one structure. If one of the steps references a multi-mapping program, all subsequent steps must use the same envelope.
The mapping for a request message comprises two message mapping programs: one 1:1 transformation and one 1:n transformation. Since the latter message mapping uses the multi-mapping envelope for both the target message and the source message, the message mapping for the 1:1 transformation must also create a transformation result with a multi-mapping envelope.
You do not strictly need to divide up one direction of the whole mapping into different steps. However, this enables all the message formats in one system landscape to be mapped to a central message format, for example. This results in less mapping programs being required because you no longer need to be able to map all the different message formats to each other.
Activities
       1.      Create your interface mapping on the design maintenance screen of the Integration Builder (see also: Creating an Object).
You can also create multiple interface mappings for the same interface pair.
       2.      Enter the source and target interfaces that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. The following restrictions apply:
○     If you want to use the interface mapping in a transformation step in an integration process, you must only specify abstract message interfaces. Furthermore, all objects (integration process, interface mapping, and all objects referenced by the interface mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help) (see also: Underlying Software Component Versions).
○     If you want to map multiple messages to each other by using a multi-mapping, you can only specify asynchronous interfaces (for further restrictions, see: Multi-Mappings). If any message interfaces are missing, you can also create them by using the functionCreate New Object ().
If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name in this case.
       3.      To import the properties of the interfaces, choose Read Interfaces. The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).
       4.      To develop an external mapping program, export the XSD schema of the respective request or response message as a zip file after you have imported the interfaces. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema.
       5.      To reference a mapping program for the respective message, you have the following options:
○     Select an existing mapping program from the Integration Repository by using the input help (). If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the Integration Repository (in multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.
○     You can create message mappings directly from the interface mapping. To do this, select the mapping type Message Mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping () in the Mapping Program frame. The Integration Builder copies the specifications of the messages and their occurrence directly from the interface mapping.
An interface mapping can only reference mapping programs that belong to the same or an underlying software component version of the interface mapping. This ensures that the mapping program can be shipped together with the interface mapping (see: Software Logistics).
       6.      If you are not using a mapping for a fault message, you can execute multiple mapping programs in succession for request and response messages:
○     To insert an additional line for a mapping program, choose .
○     To delete the registration for a mapping program, choose .
At runtime, the mapping programs are executed from top to bottom.
       7.      Save the interface mapping.
The following web-site gives complete details about interface mapping :
http://help.sap.com/saphelp_nw2004s/helpdata/en/12/05731a10264057badc32d3d3957015/content.htm
**********Please reward points if u find this useful
cheers,
gyanaraj

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
help me.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
HI Arivazhagan K,
Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
Best regards,
Angie
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.

Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

Hi all,
I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The entire trace is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="3" type="T">Sender scheme external =</Trace>
<Trace level="3" type="T">Sender agency external =</Trace>
<Trace level="3" type="T">Sender party external =</Trace>
<Trace level="3" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Determining the sender agreement</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="1" type="T">Remote address = 10.66.10.160</Trace>
<Trace level="1" type="T">User = SFUSER</Trace>
<Trace level="1" type="T">Process ID: 760</Trace>
<Trace level="1" type="T">Work Process ID: 10</Trace>
<Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>
<Trace level="1" type="T">Hop engine type = IS</Trace>
<Trace level="1" type="T">Hop adapter name = XI</Trace>
<Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
<Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
<Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>
<Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>
<Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>
<Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>
<Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>
<Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message</Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Skip Inbound Validation =</Trace>
<Trace level="3" type="T">Skip Outbound Validation =</Trace>
<Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T

HI,
Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
Patch level of XIAF:
1. customers SAP PI level is
Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
2. our SAP PI level is
Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
What do you think ?
Thanks

File to RFC Error com.sap.engine.interfaces.messaging.api.exception.Messagi

Hi ,
I am doing File to RFC Scenario.
My file get picked and I able to view the audit log under RWB message monitoring.
Here I am getting the error
u201CTransmitting the message to endpoint dest://XI_INTEGRATION_SERVER using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message using HTTPTransmitter. Reason: java.net.MalformedURLException: unknown protocol: dest.
Can any one tell me what is the reason.
Regards, Navneet

Hi Prakasu,
I am using PI 7.1 version .
When I opened SMICM there I am finding the HTTP Port as 52000.and the BS at SLD are also using the same Port in URL..
And when i verified with the Basis they confirmed that Exchange profile is set correctly.
But My file adapter is still not able to send the data to IS.
Than I configured a scenario file to file without IR object and in this case data is coming to IS and it is succesfull also.
what is the reason that in this case file adapter not able to push the data to IS.
I used File adapter with NFS protocol.
regards,
navneet

SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

Hi,
I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
This is the error that I get when sending a message to the interface
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
     at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
Thanks,
Rashmi.

Hi Rashmi,
I also think your problem is data related.
Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
Best Regards, Trevor

Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

Hi guys,
we are using PI 7.11.
With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
This works fine.
Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
Afterwards I treied to restart the message.
Following error occurs.
com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
trying restart the failed message ends up in the error specified aboce.
Anyone faced the same issue already?
Kind regards
Jochen

HI Jochen,
I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
To do a CPA Cache Refresh from the Adapter Engine:
To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
http://<host>:<port>/CPACache/refresh?mode=delta|full
The Monitoring url is like this:
http://<host>:<port>/CPACache
Check this How-to Guide on Cache, it will be useful:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
Thanks
Dhwani

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
     <gesellschaft>03</gesellschaft>
     <filiale>000</filiale>
     <satzart>11</satzart>
     <datum>00000000</datum>
     <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

Com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax

Hello,
Please explain me the error :
com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/primavera/integration/server/ServerFacade : cannot initialize class because prior initialization attempt failed
Where should I find the issue and how to correct it.
Regards

Hi,
This seems to be related to some deployed components on J2EE-engine being corrupt. Try re-deploy the primavera-component to fix the error. I'm guessing this component is some 3rd party or custom developed component?
Also make sure this component compiles correctly if it's a custom development component.
Br,
Kenneth

Com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException

Hi All,
PI 7.1 is sending the following error:
2009-12-10 15:55:00     Information     Trying to put the message into the send queue.
2009-12-10 15:55:00     Error     Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK.
2009-12-10 15:55:00     Error     Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK
2009-12-10 15:55:00     Error     MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK
I didn't find anything into OSS... =(   Does anybody can help me?
I really appreciate your help
Regards,
Gilberto Martínez

Hi Suman,
Which PI version you are using? Is it double stack?
We also faced a similar problem few days back.
We have tried a below approach and succeeded.
Can you please check with T-code SXMB_MONI if there are any queues are stopped (Red circle symbol written STOP on it).
Go to t-code SMQ1/SMQ2 and click on the line items, it will open another session which will display the details of message status (Green flag-scheduled).
Click on the Resend button on the tool bar, it will show a pop-up there click on Retain button.
This will help you to restart a stucked EOIO/EO messages.
P.S: You have to determine that how many such kind of queues are stopped and so you have to manually restart those scheduled messages.
Also refer to this thread Queue stopped in sxmb_moni
Try this if it helps.
Regards,
Dipen.

About the warning about changes message.

Hi all,
There is a messageChoice on the page,and the messageChoice must fire an action.But if the action is fired,then I click on the other tab or link, warning about changes message will not occur and directly farward to the other page.Is that possible that popup the warning about changes message after the messageChoice's event was fired ?
Thanks,
binghao

Hi,
this question is hard to understand. I don't see a messageChoice component in ADF Faces, can you give more details to your usecase and the components involved
Frank

Question about Interface

Hi everyone,
I have a question about interface :
an interface can only have abstract methods, right ?
so how come ResultSet (which is an interface) has methods like next() which can't be abstract otherwise it wouldn't do anything ?
thanks for answering !

an interface can only have abstract methods, right ?Yes. All methods in an interface are inherently public and abstract.
so how come ResultSet (which is an interface) has
methods like next() which can't be abstract otherwise
it wouldn't do anything ?It defines the next() method for classes that implement the interface. When you get a ResultSet reference returned from a method call, you're not getting a reference to an interface; you're getting a reference to an object that implements that interface (or null, as the case may be).

The "about:tabs" message always appears. The close button appears inactive so checking the "don't show this again" option doesn't work.

I am running Firefox 3.6.13 under windows/xp. All of a sudden, when opening a new tab the "about:tabs" message comes up all the time. I checked the box labeled "do not show this message again" but the "close" box seems to be inactive. Pressing it has no affect so apparently the option to suppress the message is not set. The new tab must be closed manually.

I lost several App Icons after install of 3.0 upgrade. Facebook, Tweetie, Birdhouse and a few others are no longer on the home screen, but they do sync through iTunes and I can access them if I move the home screen to the right (to show the spotlight search screen) and I can open them, the icons just won't show up. It is very inconvenient, hope Apple creates a fix for this soon.

Scripting Interface message

I am getting the scripting interface message whenever I close iTunes. I know what's causing it, I just want to know if there's a way I can prevent it from popping up every time I close iTunes. I don't want to stop using the thing that's causing it.

Hi, welcome to Apple Discussions.
You don't have to stop using the thing that's causing it, but you should close that before you close iTunes so that it can release the scripting object that it has created. As far as I'm aware there is no other way to suppress that warning message.
tt2

Jar for the package com.sap.engine.interfaces.messaging.api

Dear All,
I am writing a UDF where we want to use the Payload class of package com.sap.engine.interfaces.messaging.api. We are not getting the corresponding jar file.
Please suggest what should be the jar file.
Thanks and Regards,
Rana Brata De

this you can not use at mapping runtime. You can use this API only in Adapter modules.
What is your requirement?
Edited by: Praveen Gujjeti on Feb 27, 2012 4:38 PM

About interface message

Similar Messages

Maybe you are looking for