MDM adapter Non-XML Inbound Messaging

Hi all,
I have a scenario where I transport a csv file via PI (NW711_05_REL) to MDM using the File adapter (sender) and MDM adapter 7.1 7.1 (receiver).
The message is sent through to the MDM port fine, and it seems to choose xml as default file type and PI MSG ID as file name.
This results in an xml file with csv content.
As I want to put the file on the port with its original file type (csv) and name, I need to tweak the MDM adapter a bit. For this I have tried to find MDM specific modules, but have been unable to do so.
I have found a u201Cwork aroundu201D by using u201CSet Adapter Specific Message Attributeu201D on the sender file adapter u2013 described on help.sap.com
Configuring the sender file adapter as described in http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/content.htm i am able to set the "FileName" attribute in dynamic configuration.
This enables me to get some of the desired effect, as the file on the MDM port is now a csv file u2013 half way there!! However the file name remains PI MSG ID...
Am I missing something here or is the adapter not working as intended? I donu2019t understand why it should only use the file type when the entire filename and type is there. I would assume that the entire filename and extension would be used in the MDM port.
I have tried achieving the desired result by using the "AF_Modules/DynamicConfigurationBean" on a JMS adapter, but the result is the same.
I would like to avoid developing my own custom module to handle this, as it seems like it should be possible to handle in a more standard way.
I hope someone out there can help me out, and hope to see a lot of good replies.
Best Regards,
Jesper

have you gone thur these settings?
Non-XML Inbound Messaging
When the backend system uses the PI File Adapter sender as the communication channel to deliver messages to the PI server, and the receiving MDM channel corresponds to an inbound MDM port of type other than XML (for example, Flat text file), then you must enable the File Adapter Specific Message Attribute named File Name as follows:
       1.      Edit the corresponding File Adapter sender communication channel.
       2.      In the Advanced tab, choose Set Adapter Specific Message Attribute.
       3.      Choose the File Name.
       4.      Save and activate the changes.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/frameset.htm

Similar Messages

Loading to database with XML Inbound Message

We need to recibe XML invoices from suppliers using XML Gateway, we have a DTD and Message Map based on the XML structure defined by Treasury, when we process the XML using ECX_INBOUND the Transaction Monitor shows the processing Status Success but no data is loaded to DB.
The custum map is calling the action to insert into Database Table as a Post Process Activity on the Target database tables.
we kindly asking for help because we have no idea what that is failing.

I have encountered the same situation while following the example:
Step by Step Guide to Creating an Inbound XML Gateway Transaction for Applications 11i [ID 329903.1]
My inbound messages were received and en-queued, then they were de-queued, but now they just had "Pending" status in the transaction monitor. The post-process action does not occur at all.
All the Workflow agent listeners are up and running. However, I do see an error in the log:
Module: wf.plsql.WF_EVENT.GetSourceAgentGUID.Error
Message Text: Specified source agent row does not exist in database. Setting to NULL.
Any thoughts?
~Alan

Content conversion using PI MDM adapter in PI 7.1

Hello All,
I am using the PI MDM adapter in PI 7.1.
I have a scenario ECC - PI - MDM . ECC will send an IDoc to PI and we need to send a flat file to MDM.
So is it possible to convert the IDoc XML in PI to flat file using PI MDM adapter , and if yes then how ?
Please help
Regards,
Loveena

Hi Loveena,
Check the "Non-XML Inbound Messaging" section in the following document (Page 15)
https://websmp205.sap-ag.de/~sapidb/011000358700001890482008E
Regards,
Ravi kanth Talagana

Non XML attachment to XML in sender mail adapter

Hi,
I am working with sender mail adapter and usng payloadswapbean. My attachment is non XML and I need to convert it in to XML in order to mapping. How can I do that? Can someone explain if can I use MessageTransformBean for this purpose and if so, how?
Or any other method for doing this?
Thanks,
Rakesh

Is the attachment in text format? If yes, then after the usage of PayloadSwapBean, you may try using MessageTransformBean in the same module chain. And you will be able to convert it into xml format.
Regards,
Prateek

[URGENT] Get Inbound Message in EBS Using XML Gateway + SOAP

Hi experts,
I want to ask you about how to process the inbound message using XML Gateway and SOAP protocol.
I have 2 EBS instances, let's called it A (source) and B (destination).
FYI, I'm following this ebook: "Oracle E-Business Suite Development and Extensibility Handbook" in chapter 12 regarding Oracle XML Gateway.
So I don't use BPEL PM to do this.
I'm just using EBS with XML Gateway and Integrated SOA Gateway responsibilities.
When I tried to send the XML from A to B using OXTA, it's success, the data can be processed in B and could store in the database.
But when I tried to use SOAP, the XML message that has been sent from A is success, and when I check it on B (Integrated SOA Gateway -> SOA Monitor), the message is in there and I can see the SOAP request and response as well.
SOAP request:
<?xml version="1.0" encoding="UTF-8" ?>
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://xmlns.oracle.com/apps/fnd/XMLGateway" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
- <env:Header>
- <ns0:XMLGateway_Header>
<ns0:MESSAGE_TYPE>XML</ns0:MESSAGE_TYPE>
<ns0:MESSAGE_STANDARD>OAG</ns0:MESSAGE_STANDARD>
<ns0:TRANSACTION_TYPE>XKLB</ns0:TRANSACTION_TYPE>
<ns0:TRANSACTION_SUBTYPE>ORDER_DETAILS_XO</ns0:TRANSACTION_SUBTYPE>
<ns0:DOCUMENT_NUMBER>9282</ns0:DOCUMENT_NUMBER>
<ns0:PARTY_SITE_ID>142</ns0:PARTY_SITE_ID>
<ns0:USERNAME>cons.ade</ns0:USERNAME>
<ns0:PASSWORD>cons.ade</ns0:PASSWORD>
</ns0:XMLGateway_Header>
</env:Header>
- <env:Body>
<ns0:ReceiveDocument xsi:type="xsd:string"><ORDER_DETAILS_XO xmlns=""> <ORDER> <ORDNO>100002</ORDNO> <ORDWT>100002</ORDWT> <RDATE/> <CITY>JAKARTA</CITY> <ZIP>17121</ZIP> </ORDER> </ORDER_DETAILS_XO></ns0:ReceiveDocument>
</env:Body>
</env:Envelope>
SOAP response:
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
- <env:Body>
- <ReceiveDocument_Response xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">
<ResponseCode xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">200</ResponseCode>
<ResponseMsgId xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">BD4EAD91E76051D5E0440021287448DA</ResponseMsgId>
<ResponseInfo xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">Document received and pushed into queue for asynchronous processing. Enqueued message id is 'BD4EAD91E76051D5E0440021287448DA'.</ResponseInfo>
</ReceiveDocument_Response>
</env:Body>
</env:Envelope>
But the problem is the message that has been got in B can't store into the database yet.
I had already changed the Queue in the XML Gateway -> Define Transaction, from APPLSYS.ECX_IN_OAG_Q (this is for OXTA) to APPLSYS.WF_WS_JMS_IN.
After I invoke the webservice and the SOAP message has been got in B, I checked APPLSYS.WF_WS_JMS_IN in database and there is 1 record, the value of USER_DATA column is:
((, , , , , , ((BES_EVENT_NAME, 100, oracle.apps.fnd.wf.ws.inbound.xmltx.receive, , 27), (BES_EVENT_KEY, 100, 796550960, , 27), (BES_PRIORITY, 200, , 1, 23), (BES_FROM_AGENT, 100, [email protected], , 27), (BES_TO_AGENT, 100, [email protected], , 27), (MSG_ID, 100, 1334117503435, , 27), (ECX_MESSAGE_TYPE, 100, XML, , 27), (ECX_MESSAGE_STANDARD, 100, OAG, , 27), (ECX_PARTY_SITE_ID, 100, 142, , 27), (WS_PORT_OPERATION, 100, ReceiveDocument, , 27), (ECX_TRIGGER_ID, 100, 7101, , 27), (UserId, 100, 3020, , 27), (ECX_USERNAME, 100, CONS.ADE, , 27), (ECX_TRANSACTION_SUBTYPE, 100, ORDER_DETAILS_XO, , 27), (ECX_PASSWORD, 100, CONS.ADE, , 27), (ECX_DOCUMENT_NUMBER, 100, 9285, , 27), (BES_PAYLOAD_OBJECT, 100, false, , 27), (ECX_ATTACHMENTS, 100, , , 27), (ECX_TRANSACTION_TYPE, 100, XKLB, , 27), , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , )), 0, , )
When I tried to select APPLSYS.WF_WS_JMS_IN for the 2nd time, there is no result, which means the business event has been triggered, right?
So in this point I still don't have any idea why the process is (likely) ended after enter the Queue and the message can't store into B's database yet.
Do I miss any setup when changing from OXTA into SOAP protocol to send XML message?
Any urgent help most appreciated.
Best Regards,
Rheza

Hi,
Did you ever get any answers to this? We are thinking about the same thing.
Thanks
Darma
[email protected]

Receiver MDM adapter not working !!! Please suggest !!!

Hi Experts ,
mine is a idoc to MDM adapter scenerio. The idoc message is successfully passing the PI integration engine , but failing in the adapter engine ( MDM communication channel ) giving the following message.
Configuration error: Can not create repository session - server=xxxxxx.XX.XXXXXX.net serverUser=Admin repository=xxxxxxxx user=Admin]' caused by: The specified MDM repository was not found on the server (xxxxxx) Configured MDM access parameters for inbound port: [ MDM Server: xxxxx.xx.xxxxxx.net , Repository: xxxxxxxxxx , Port Code: CREMMDM0XIncrementalData , Remote System Code: ECC , DBMS Server: xxxxxx.xx.xxxxxx.net , DBMS Type: ORCL
I have tried connecting to the same MDM server using a receiver file adapter and it is working absolutely fine. But dont know why the mdm adapter is giving the following error. I have cross checked the adapter parameters with the MDM guy. They are OK.
I was wondering this was a version / service error, how can I chack the service pack of MDM Comm channel .
Please suggest . Urgent
Regards,
Arnab.
Edited by: Arnab Mondal on Jan 19, 2012 12:04 PM
Anything guys??
Any feed guys??
Edited by: Arnab Mondal on Jan 20, 2012 5:37 AM

Try a reset, which is similar to a computer restart and is done by pressing and holding the home button and the sleep/wake or on/off button simultaneously until you see the Apple logo and then release.

Axis adapter receiver handle fault message

Hi
We have a Sync interface which makes a Proxy call from ECC to PI 7.3 and then PI makes Soap(Axis) Sync call to Web sevice. We are having issues when handling SOAP 1.2 fault message.
Below is the actual fault response from Webserver:
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
 <env:Header/>
 <env:Body>
 <env:Fault>
 <env:Code>
 <env:Value>env:Receiver</env:Value>
 </env:Code>
 <env:Reason>
 <env:Text xml:lang="en">FaultMsg</env:Text>
 </env:Reason>
 <env:Detail>
 <ns2:servicefault xmlns:ns2="https://hostname.de/webservice/0400-0005">
 </ns2:servicefault>
 </env:Detail>
 </env:Fault>
 </env:Body>
</env:Envelope>
But PI receives this response like system error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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: FaultMsg</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked this way http://scn.sap.com/thread/1675917 but it doesn't fit for Axis adapter.
Please let me for any clues how to handle this fault response.
Regards, Dzmitry

Hi,
I'm working with Dzmitry on the issue since last week. After analyzing the implementation and checking some SAP notes I came to the following conclusion:
According to note 856597 the fault behavior of axis adapter is as follows:
" A: The receiver adapter expects a SOAP message as response. For
synchrnous calls, a successful response should be returned with
HTTP 200. In this case, the content of the SOAP body will be
returned to the caller as the response payload. When some error
occurs, the SOAP message may contain the SOAP fault element. In
this case, when the fault detail element is not empty, its
content will be returned as the fault payload in an application
error message. For others, a system error message will be
returned to the caller."
The example shows a SOAP 1.1 fault message with a "detail" node being mapped to an application fault.
As we are using SOAP 1.2 the namespace as well as structure of the fault defers. I assume that the module responsible for the transformation from AXIS message to XI message within the module chain does not recognize the detail node on out soap 1.2 fault.
Therefore the solution would be to insert a custom AXIS handler before com.sap.aii.axis.xi.XI30OutboundHandle mapping the soap 1.2 fault to a soap 1.1 fault.
Is there something like a short how to on how to implement Axis handler and how to deploy it. Sap help only says to package it into sda file....
Thanks a lot in advance!!!
BR,
Eugen

Can a Java Mapping be used on non-xml data

I would like to use a java mapping to transform non-xml formatted data to an IDOC or XML format.
1) Does the input or output of a Java Map have to be XML.
2) If possible can the test feature be used to load and test a non-xml data file.
3) Any comments or lessons learned in this area.

Hi Johan,
below are some suggestions for your scenario:

1) Structured flat picked up using J2EE FTP adapter.
Indeed; you can use the file adapter to receive/retrieve this file from "any" third party system.
2) Structured flat converted to XML (Using JAVA mapping?)
When you send any message to XI, it's the adapter's task to convert this message into a XI understandable format i.e. SOAP. So the flat file to XML conversion is not your concern.
However, if you need to perform any data transformation (input file to IDOC) then you can opt for XSLT (XML stylesheets), Java mappings or the XI mapping tool within the repository. Based on my own experience with IDOC mapping, I can tell you that XSLT and/or Java mapping is the best way to achieve this kind of mapping.
3) XML mapped to SAP IDoc using graphical editor.
See comments point 2)
Cheers,
Rob.
Message was edited by: Rob Viana

Inbound Message Fails with Send Exp"

We are on 10.1.2.0.2 and tryting to test (ebms ) outbound/inbound messaging with a trading partner. The outbound from us to TP works great, but on inbound from the TP we are seing the following errors: (This works on 10.1.2.0.0)
Machine Info: (devb2b.helenachemical.com)
Description: B2B adapter general error
StackTrace:
Error -: AIP-50031: B2B adapter general error: Error -: AIP-50025: Repository error : Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "DEST Partnre", To party[NAME] "SOURCE Partner", Business action name "SendResponseEnd"; also verify agreement effectiveToDate
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1735)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2294)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2193)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2148)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
 at java.lang.Thread.run(Thread.java:534)
Caused by: Error -: AIP-50025: Repository error : Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "DEST Partner", To party[NAME] "SOURCE Partner", Business action name "SendResponseEnd"; also verify agreement effectiveToDate
 at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPType(RepoDataAccessor.java:1852)
 at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:167)
 at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:495)
 at oracle.tip.adapter.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:226)
 at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:3568)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1614)
 ... 6 more
Caused by: Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "DEST Partner", To party[NAME] "SOURCE Partner", Business action name "SendResponseEnd"; also verify agreement effectiveToDate
 at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPName(RepoDataAccessor.java:2176)
 at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPType(RepoDataAccessor.java:1839)
 ... 11 more
Any ideas on what is different in the newer version of B2B
Thanks
PT

Hi Ramesh,
Found this issue- in the new release the Business Action name and choreography name must match to work with TP on custom document over ebms.
We still have issues,,, the TP's that are working currently on 10.1.2.0 are no more working. For example:
The following wire envelope was sent from one of our TP:
--MIME_boundary
Content-ID: <1dac9c73-bba3-4fc3-a756-0134872b03d2ebxml-Header>
Content-Type: text/xml
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soapenv:Header xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:MessageHeader eb:version="2.0" soapenv:mustUnderstand="1"><eb:From xmlns:axis2ns1561="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:PartyId xmlns:axis2ns1562="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" axis2ns1562:type="DUNS+4">8097318700000</eb:PartyId></eb:From><eb:To xmlns:axis2ns1563="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:PartyId xmlns:axis2ns1564="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" axis2ns1564:type="DUNS">0070367590000</eb:PartyId></eb:To><eb:CPAId xmlns:axis2ns1565="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">OrderCreate</eb:CPAId><eb:ConversationId xmlns:axis2ns1566="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">7229ce0c-4b6a-419c-b301-ef28708fda68</eb:ConversationId><eb:Service xmlns:axis2ns1567="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">uri:OrderCreate</eb:Service><eb:Action xmlns:axis2ns1568="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">SendResponseEnd</eb:Action><eb:MessageData xmlns:axis2ns1571="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:MessageId xmlns:axis2ns1572="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">1dac9c73-bba3-4fc3-a756-0134872b03d2</eb:MessageId><eb:Timestamp xmlns:axis2ns1573="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">2008-05-28T10:33:55Z</eb:Timestamp></eb:MessageData><eb:DuplicateElimination xmlns:axis2ns1574="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" /></eb:MessageHeader><eb:AckRequested eb:signed="false" eb:version="2.0" soapenv:mustUnderstand="1" /></soapenv:Header><soapenv:Body><eb:Manifest eb:id="Manifest" eb:version="2.0"><eb:Reference eb:id="Payload-1" xlink:href="1dac9c73-bba3-4fc3-a756-0134872b03d2-body1" xlink:type="simple" /></eb:Manifest></soapenv:Body></soapenv:Envelope>
On the Ack, B2B is sending the following:
SOAPAction="ebXML"
Content-Type=multipart/related;type="text/xml";boundary="----=_Part_29_18537968.1211985238867";start="<ebxheader-0A27EBC811A2FF31B3B00000C6520000>"
Content-Length=1744
------=_Part_29_18537968.1211985238867
Content-Type: text/xml
Content-ID: <ebxheader-0A27EBC811A2FF31B3B00000C6520000>
<?xml version="1.0" encoding="utf-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><env:Header><eb:MessageHeader env:mustUnderstand="1" eb:version="2.0"><eb:From><eb:PartyId eb:type="ebMS Identifier">0070367590000</eb:PartyId></eb:From><eb:To><eb:PartyId eb:type="ebMS Identifier">8097318700000</eb:PartyId></eb:To><eb:CPAId>SendResponseEnd</eb:CPAId><eb:ConversationId>7229ce0c-4b6a-419c-b301-ef28708fda68</eb:ConversationId><eb:Service>urn:oasis:names:tc:ebxml-msg:service</eb:Service><eb:Action>Acknowledgment</eb:Action><eb:MessageData><eb:MessageId>Helena Operating Unit@0A27EBC811A2FF31B4400000C6530000</eb:MessageId><eb:Timestamp>2008-05-28T14:33:58.000Z</eb:Timestamp><eb:RefToMessageId>1dac9c73-bba3-4fc3-a756-0134872b03d2</eb:RefToMessageId></eb:MessageData></eb:MessageHeader><eb:Acknowledgment env:actor="urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH" env:mustUnderstand="1" eb:version="2.0"><eb:Timestamp>2008-05-28T14:33:58.000Z</eb:Timestamp><eb:RefToMessageId>1dac9c73-bba3-4fc3-a756-0134872b03d2</eb:RefToMessageId></eb:Acknowledgment></env:Header><env:Body/></env:Envelope>
------=_Part_29_18537968.1211985238867--
They send us Service: uri:orderCreate; Action: SendResponseEnd; CPAID: OrderCreate.
We send in the Ack:
Service: urn:oasis:name:tc:ebxml-msg:sercice; Action:Acknowledgment: CPAID:SendResponseEnd
Where is it pulling the CPAID? or why is it using the Business Action Name?
The message shows complete on our side, but does not get completed on TP side, and since they are they are the initiator they retry 2 times befoer they stop and this is causing duplicte errors on our side. They are using Nexus ebms engine.
Any info on this is appreciated. We are using ebms 2.0
Thanks
PT

Can the AQ Adapter send a JMS Message?

I'm trying to use the AQ adapter to enqueue an XML message into a queue who's payload type is AQ$JMS_TEXT_MESSAGE so that it can be consumed by a Message Driven Bean in OC4J.
Simply sending the XML reults in:
"AQ Adapter: ** Error ** Can not enqueue messages to queue PLEDGE. ADT Payload defined for Queue PLEDGE does not match with OAI Message. Please check attribute "Pledge". In order for the AQ Adapter to enqueue OAI messages to the queue, the queue payload must match the ADT imported through iStudio."
I tried importing the AQ%JMS_TEXT_MESSAGE but can't see any easy way to construct it.
Is this even possible?
-Doug

Doug,
the AQ$JMS_TEXT_MESSAGE is an object type. So you'll need to import that type as your application view.
The problem with this JMS objecttype is how to populate it.
When your text (XML) is more than 4000 characters in length, the TEXT_LOB attribute should get the text. If less, the TEXT_VC attribute should get the text. In any case, the TEXT_LEN should be set to the length of the XML.
AFAIK, you can't currently do this with InterConnect directly.
The most popular solution is to have InterConnect deliver this message to a simple non-JMS queue and have some PL/SQL or java code convert it to a proper JMS text message and put it in the JMS text queue.
There are some features in the DBMS_AQ package to register a plsql procedure to be triggered when a message arrives (dbms_aq.register). That could be a procedure which converts the message for you.
In ProcessConnect (coming soon) there is a dedicated JMS adapter available.
HTH, Marc

MDM Adapter doubt

Hi
what are all the advantages of using MDM adpater in PI 7.1
1.Will MDM adapter accesses directly the repository (in console or data manager or syndicator)?
2.How MDM adapter can be compared with import manager or syndicator .
3. MDM adpater enables to load the data directly to any repository ?
4. how the integration of PI7.1 with MDM 7.1 takes place ?
am bit confused, can you pls explain ?
thanks
manian

Hi Manian,
Please go through this link; it will give you a good idea about the new features of MDM 7.1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d0b0e7-f144-2b10-17a2-982103c96ac0
Some key points on MDM-PI Adapter; this will definitely answer all your questions:
1. MDM 7.1 will offer new functionality to directly push/pull data into/from MDM using the MDM JAVA API.
2. The MDM PI Adapter will support SAP Netweaver PI 7.0 and 7.1
3. The MDM PI adapter is shipped as a separate file to be deployed on the PI adapter engine.
4. Message flow between PI and MDM can be monitored end to end (e.g. show if messages have been recieved and properly imported into MDM)
5. Error handling is improved because the Communication Channel in PI is pointing to one specific Repository Port.
6. Restarting of messages if a service is unavailable is possible.
7. Configuration/System landscape setup/Integration
       (a) MDM Adapter can be used instead of the File Adapter.
       (b) Configuration of FTP is no longer needed.
       (c) MDM Adapter is easy to implement and straight forward to monitor.
       (d) Higher reliability of data transfer.
8. Message Flow PI to MDM
       (a) Data sent from any connected system to PI is stored within PI's internal database.
       (b) XML message is forwarded to the defined communication channel (MDM PI Adapter).
       (c) MDM JCA Adapter itself invokes the MDM JAVA API sends the message to MDM using MDIS Port Functions.
       (d) Store the message in XMl format in XML format into the corresponding MDIS port folder so that MDIS can import the files independently.
       (e) "Finished import event" is thrown by MDIS and caught by the MDM JCA Adapter.
        (f) The import status is used to update the PI monitoring accordingly.
9. Message flow from MDM to PI
       (a) The Syndication event is triggered by MDSS as soon as the syndication is finished.
       (b) The data is available as XML file in the corresponding port folder.
       (c) The MDM JCA Adapter catches the syndication event and uses the MDSS Port functions to retrieve the data.
       (d) PI XMl message is created and sent to the PI AF for reciever determination and further message processing.
       (e) It is important to understand that only MDSS is able to throw the syndication event.
       (f) A manual syndication using the syndicator does not throw this event, meaning that the MDM 7.1 PI adapter is unable to pick the XMl message coming from manual syndication.
All these points should give you a very clear picture of all the abilities of MDM-PI Adapter.
Hope this will answer most of your questions.
Regards,
Varun

How to add exactly 2 NON XML caracters at the end of a SOAP body

Hello all I am trying to add two (and only two) extra non xml caracters "AA" at the END of a SOAP body using the JAXWS handlers as so:
HTTP/1.1 200 OK
Content-Type: text/xml;charset=UTF-8
Content-Length: 131
Content-Length: 131
Server: Jetty(7.x.y-SNAPSHOT)
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body></SOAP-ENV:Body></SOAP-ENV:Envelope>
AA
The problem is that if you try to add them to the SOAP body (see code below) you get a XML Unmarshalling exception. If I add "AA" as a soap attachment I get MORE than 2 caracters after the SOAP body (which I don't want)
Here is the my SOAPHandler code :
@Override
public boolean handleMessage(SOAPMessageContext mc) {
if (Boolean.TRUE.equals(mc.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY))) {
try {
SOAPMessage message = context.getMessage()
String stringSoapMessage= getMsgAsString(message);
stringSoapMessage += "ss";
message.getSOAPPart().setContent((Source) new StreamSource(new ByteArrayInputStream(msg.getBytes())));
message.saveChanges();
context.setMessage(message);
} catch (Exception e1) {
return true;
public String getMsgAsString(SOAPMessage message) throws SOAPException {
String msg = null;
try {
ByteArrayOutputStream baos = new ByteArrayOutputStream();
message.writeTo(baos);
msg = baos.toString();
} catch (Exception e) {
e.printStackTrace();
return msg;
so my question is this: is there any way to add exactly 2 non xml caracters at the end of the soap body using jaxws handlers ? I have spent several weeks on this so it is not an easy question...
Thanks,
Fred.

Yes I have done it using CFX interceptors. But the runtime dependencies needed were too big for this particular use. I mean having to use these:
apache/cxf/cxf-bundle/2.6.0/cxf-bundle-2.6.0.jar
org/apache/neethi/neethi/3.0.2/neethi-3.0.2.jar
wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.jar
/org/codehaus/woodstox/wstx-asl/3.2.4/wstx-asl-3.2.4.jar
org/apache/ws/xmlschema/xmlschema-core/2.0.2/xmlschema-core-2.0.2.jar
org/mortbay/jetty/jetty-util/6.0.2/jetty-util-6.0.2.jar
org/eclipse/jetty/jetty-util/7.5.4.v20111024/jetty-util-7.5.4.v20111024.jar
org/apache/geronimo/specs/geronimo-servlet_2.5_spec/1.1.2/geronimo-servlet_2.5_spec-1.1.2.jar
org/apache/geronimo/specs/geronimo-javamail_1.4_spec/1.7.1/geronimo-javamail_1.4_spec-1.7.1.jar
org/apache/geronimo/specs/geronimo-servlet_3.0_spec/1.0/geronimo-servlet_3.0_spec-1.0.jar
org/eclipse/jetty/jetty-http/7.5.4.v20111024/jetty-http-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-server/7.5.4.v20111024/jetty-server-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-io/7.5.4.v20111024/jetty-io-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-continuation/7.5.4.v20111024/jetty-continuation-7.5.4.v20111024.jar
to add two caracters at the end of a soap message seems like over kill. If this is the only way to do this then i'll do it this way but it just seems like the implementation of the JAXWS API in JDK 6 seems inches away from being able to do this no ?
Thanks for the replies,
Fred

Wrong port in FTP receiver adapter - no errors in message monitoring?

Hello all
We're on XI 3.0 SP16 and have created / configured a HTTP XML -> XI -> FTP Server scenario. In the receiver comm. channel (ftp) we had specified a wrong port number and always wondered, why we never got errors in message monitoring. Everything seemed to be processed correctly... but no file arrived on the FTP server (receiver) side!
After correcting the wrong FTP port number in the receiver FTP comm. channel everything went fine.
We now encountered a similar problem with a RFC receiver adapter. We're using it in another scenario HTTP XML -> XI -> RFC to SAP R/3 (4.7).
For some reason it died (red status in adapter monitor) and it was no more possible to do RFC calls from XI to SAP R/3 (normal RFC adapter, NO proxies).
In XI message monitor everything seemed to be ok but no message arrived till SAP R/3. Nothing in any queue...
After deactivating and reactivation the RFC receiver comm. channel it worked again BUT ALL PREVIOUSLY SENT messages seem to be lost.
Is it really the way it works? Does XI integration engine at runtime NOT catch whether or not a RFC or FTP receiver adapter died, thus is not able to tell somewhere in message monitor that a message could not be delivered at all?
I'm really confused here but hopefully I simply don't understand some easy principles to take into account...
Our SAP R/3 is on rel. 4.70 with Web AS 6.20. The XI 3.0 plugin is not installed. Do we need to go with server proxies there and use QOS = best effort?!?
Thanks for some suggestions.
Best regards,
Renaud

Hi Michal
Thanks... works great for normal XML based messages!
Now, what if I wanted to pass binary files from one ftp server via BPM to another ftp server in order to enable the transport acknowledgment?
The files polled from ftp server using the ftp sender adapter are all in binary format (ARJ). No xml data in there. How should the message format look like in BPM for the receiving step? Or: how to make sure not to loose the binary content when passing through BPMs?
I need this sort of scenario because of the tansport acknowledgment and because I need to have some sort of message splitting (send the binary file over to a second ftp server and additionally send some kind of info message to SAP R/3 regarding thin binary file).
BTW: in the MessagingSystem/monitor/monitor.jsp I do not see sender / receiver information. Is this normal? It's quite of a bad thing to look inside each message in order to find out what message I'm having in front of me...
Thanks a lot for your support and patience!
Kind regards,
Renaud

AS2 adapter error during inbound processing

Hello,
We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
In the RWB the communication channel (CC_AS2_Sender) gives the following error:
"Message inititiation failed: Processing error"
The message itself gives the following error:
"Inbound message processing failed! performing rollback
Can anyone help us with this?
Thanks in advance.
Regards,
Marco

Hi Marco,
the message is not forwarded to the intergration egine because there might be an error in your communication channel.
Are there any other modules in the module chain of this communication channel?
Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
Did you also restart the Java Stack after the Upgrade?
regards,
Daniel
Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

Reg: MDM adapter in PI 7.1

Dear All,
My scenario is IDOC PI(7.1) MDM(7.1) .
In moni it is showing successful and when checked in Runtime workbench for MDM adapter (receiver communication channel) it is showing error as,
"Message processing failed. Cause: java.lang.Exception: JNDI name of the ra connectionFactory is not configured. Go to the directory and create a value with name 'JNDIName' and value 'deployedAdapters/<ra name>/shareable/<ra name>' as module configuration data of the module 'ModuleProcessorExitBean' "
Can anyone suggest me on this.
Regards,
Lavanya.B

Hi Rajesh,
Thanks for the reply.In the Receiver MDM Adapter, we have two things,
Processing sequence
Module Name type Module key
localejbs/ModuleProcessorExitBean Local Enterprise Bean 1 (default)
Module Configuration
Module key Parameter Name Parameter Value
Could you please explain me in detail what need to filled as this is the first time I am configuring the MDM Adapter.
Regards,
Lavanya

MDM adapter Non-XML Inbound Messaging

Similar Messages

Maybe you are looking for