XML Gateway / OXTA message header

How do we tell XML Gateway not to put the hub username/password in the transaction header?

Thanks for the advice. I checked the Workflow Status monitor I did get an error...
Internal Name          ECXERROR
Description          XML Gateway Error Processing
Message Direction          O
Error Name          1
ECX Error Type          20
ECX Return Code          1
ECX Error Message          Attribute 'xmlns' used but not declared.
This seems to be an xml namespace error. Can anyone tell me how to solve this problem?
Thanks,
-Jason

Similar Messages

XML Gateway OXTA submit to eBusiness Suite Problems

Hi all,
I am using XML gateway to receive an inbound transaction from a custom web service i built.
It uses an OXTA connection over HTTP
I basically copied it from the XML Gateway User guide...
http://download.oracle.com/docs/cd/B34956_01/current/acrobat/120ecxug.pdf
And on page 7-21 it says
"The receiving Web server sends the message response back to the sending Web server.
The message response includes Message Receipt ID, Status Code, and Status
Description. A status code of 1000 implies the message was successfully posted."
I get a status code of 1000 which was great!
But the message doesn't really get to the eBusiness Suite. There is a problem somewhere but I don't know where.
If XML Gateway says the message is ok, but eBusiness suite doesn't get it...where is the issue? Maybe in workflow? How do I test this if I get a 'ok' status back? What should I look for?
Any help would be much appreciated.
-Jason
My OXTA Submit Message Procedure:
public Status submitMessage(SyncMessageType message) throws Exception {
URL url = new URL(address);
HttpURLConnection con = (HttpURLConnection) url.openConnection();
StringBuffer buff = new StringBuffer(3000);
getPostString(message, buff);
con.setDoInput(true);
con.setDoOutput(true);
con.setRequestMethod("POST");
OutputStream os = con.getOutputStream();
OutputStreamWriter writer = new OutputStreamWriter(con.getOutputStream(),CHARSET);
writer.write(buff.toString());
writer.flush();
Status status = new Status();
status.setCode(Integer.parseInt(con.getHeaderField("STATUS_CODE")));
status.setDescription(con.getHeaderField("STATUS_DESCRIPTION"));
System.out.println(buff.toString());
return status;
}

Thanks for the advice. I checked the Workflow Status monitor I did get an error...
Internal Name          ECXERROR
Description          XML Gateway Error Processing
Message Direction          O
Error Name          1
ECX Error Type          20
ECX Return Code          1
ECX Error Message          Attribute 'xmlns' used but not declared.
This seems to be an xml namespace error. Can anyone tell me how to solve this problem?
Thanks,
-Jason

Got error: Location Code is not enabled in the XML Gateway Server

Hi,
When I perform Compliance rule screening on GTM - Globel Trade Management,that I defined GTM as an Trading Partner on EBS R12.1.3,
GTM can send response to EBS,but I see the following error message via Transaction Monitor on EBS workflow:
[The Standard:OAG, Transaction Type:ITM , Transaction SubType:EXPORT_COMPLIANCE and Location Code GTM6.2 is not enabled in the XML Gateway Server. Pls check your Setup.]
On EBS,I defined an ITM Partner for GTM,named 'GTM6.2',according to the document created by you: ITM Setup.doc
and I also finished the following steps:
1. ITM Application Users
2.ITM Partner Service Types
3.ITM Parameter Setup
4.Order Type Creation: ITM Only
5.Customer Creation: create a customer named 'GTM6.2', also enter 'GTM6.2' as EDI Location
6.Define Transactions on XML Gateway as following:
<Header>:
Party Type: Customer
Transaction Type: ITM
Transaction Sub Type: EXPORT_COMPLIANCE
<External Transactions (Lines)>:
Standard Code: OAG
External Transaction Type: ITM
External Transaction Sub Type: EXPORT_COMPLAINCE
Queue: APPLSYS.ECX_IN_OAG_Q
7.Define Trading Partners on XML Gateway as following:
<Header>:
Trading Partner Type: Customer
Trading Partner Name: GTM6.2
<Trading Partner Details>:
Transaction Type: ITM
External Transaction Type: ITM
External Transaction Sub Type: EXPORT_COMPLAINCE
Map: WSHITEIN
Source Trading Partner Location Code: GTM6.2 (same as the value what defined in EDI Location for customer)
I think the combination of External Transaction Type, External Transaction Subtype, Standard Code,Source Trading Partner Location Code
should be existing once done above steps, I have no idea why the error prompted.
Does someone can tell how to trace the error?
Thanks,
Rambler

user12254038 wrote:
Can you send any supporting documents on ITM Setup? My client is implementing ITM for the first time and I wanted to know more details on how it works in R12.1.3 version of EBS?Oracle International Trade Management (ITM) Partner Integration: Specifications [ID 572524.1]
International Trade Management Integration [ID 259691.1]
How Can I Tell if International Trade Management is Installed or Not? [ID 742539.1]
What are the Required Setups for International Trade Management (ITM) Flows in Shipping Execution? [ID 782861.1]
What Patches Provide the Latest Fixes and Enhancements for ITM Adapter? [ID 465122.1]
How to Generate Debug Information From ITM Adapter for XML Processing [ID 738925.1]
How to Generate Debug File for International Trade Management (ITM) [ID 1294853.1]
Thanks,
Hussein

Need to send XML msg to TP using B2B, but format should be Orcl XML Gateway

Current Interface:
==================
We have an EBS 11.5.10 with XML Gateway.
Actively we were exchanging XML data with 5 trading partners (different application maintained by 3rd party) using EBS XML Gateway.
XML Gateway uses OAG Format (attached the format bellow)
Future Interface:
=================
Our company is in process of moving our EBS 11.5.10 app to Oracle Fusion Apps.
Oracle Fusion app interfaces will be using Fusion Middleware and B2B.
For that we doing a POC interface between a Fusion MDM and 1 Trading Partner.
Problem:
========
But, when sending XML message to other TP using B2B, the format is different. i.e. Message in the XML Format.
Eg.
<?xml version="1.0" ?><OUTB_FUS_IND_DATA> <OUTB_FUS_IND TRANSACTION_TYPE="TP_INDIVIDUAL_OB" TRANSACTION_SUBTYPE="INDIVIDUAL.UPDATE"> <OUTB_FUS_IND KEYVALUE="100010058799220" PERSON_FIRST_NAME="Xyz" PERSON_LAST_NAME="Abc"/> </OUTB_FUS_IND></OUTB_FUS_IND_DATA>
Oracle XML Gateway send message with message envelop, which have attributes as text field and payload in the XML message format (XML Gateway envelope details is below).
(Sample XML messages goes out: HTTP Body
TRANSPORT_PROTOCOL=OXTA
TRANSPORT_PROTOCOL_VERSION=1.0
REQUEST_TYPE=SEND
MESSAGE_ID=A1234567890ZZ0987654321
MESSAGE_TYPE=XML
MESSAGE_STANDARD=OAG
TRANSACTION_TYPE=TP_INDIVIDUAL_IB
TRANSACTION_SUBTYPE=INDIVIDUAL.UPDATE
DOCUMENT_NUMBER=12345
PARTYID=9999
PARTY_SITE_ID=8888
PROTOCOL_TYPE=HTTPSu2013OXTA
PROTOCOL_ADDRESS=HTTPS://www.me.com/servlets/oracle.ecx.oxta.
Therefore, when I receive the document in PI the mapping fails due to an incorrectly formed message payload. For example:
TRANSPORT_PROTOCOL=OXTA&TRANSPORT_PROTOCOL_VERSION=1.0&REQUEST_TYPE=SEND&MESSAGE_ID=9EA3BD2......
We want B2B send messages to other TP as same way XML gateway use to send.
How we solve this issue?
XML Gateway Envelope (Manual)
=====================
In addition to the business document such as a purchase order or invoice in the XML Payload, a set of message attributes are transmitted. Collectively, these attributes are called the XML Gateway envelope.
This section discusses the XML Gateway envelope and its data in the validation process for inbound messages, or its source of data for its creation for outbound messages. Data entered into the Trading Partner Setup form is referred to as data in the trading partner table. Data entered into the Define Transactions form is referred to as data in the transaction table.
Most of the data elements are copied from the Trading Partner tables or the Transaction tables to the XML Gateway envelope.
Attribute
=========
MESSAGE_TYPE
MESSAGE_STANDARD
TRANSACTION_TYPE
TRANSACTION_SUBTYPE
DOCUMENT_NUMBER
PARTYID
SOURCE_TP_LOCATION_CODE
PARTY_TYPE
PROTOCOL_TYPE
PROTOCOL_ADDRESS
USERNAME
PASSWORD
ATTRIBUTE1
ATTRIBUTE2
ATTRIBUTE3
ATTRIBUTE4
ATTRIBUTE5
PAYLOAD

First of all EBiz and B2B/BPEL are two different products meant for different purpose and hence you cannot expect that EBiz and B2B/BPEL should have same functionality.
Whatever headers you have mentioned, those are added by OXTA (Oracle Transport Agent) which is part of EBiz. You can add almost all these headers in Oracle B2B in "Additional transport headers" section of Transport Protocol Parameter.
Search for "Additional transport headers" at below link -
http://docs.oracle.com/cd/E23943_01/user.1111/e10229/b2b_tps.htm#BABBCDHI
Regards,
Anuj

[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]

Error in inbound processing: EDI message - XML Gateway

Hello!
I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
In the beginning of b2b.log I see this:
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
After I copy the edi file to the incoming directory B2B starts processing the file:
2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
Protocol = File
Version = 1.0
Transport Header
filename:00003442_23.CMS
filesize:12345
file_ext:CMS
fullpath:C:\xa_endpoint\00003442_23.CMS
timestamp:2009-07-06T16:14:29.393+01:00
As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
     at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
     at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
Last message repeats once more and then:
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
     at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
     at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
     at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
     at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
     at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
Error repeats a few times.
Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
Could anyone help with this? What could be wrong?
Thanks in advance.
Kind regards,
Wanda
PS. I've checked all threads that might have anything to do with this, but found nothing useful.

Hi Anuj,
thanks for taking the time to examine the file.
Answers to your questions:
1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
Installed Patch List:
=====================
1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
3. In theory the sysadmin should have run it, but how could I double-check this?
I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
also I tried the following values:
C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
true (I had no other idea)
Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
If I remove or comment the above line from tip.properties, then no transport log files are created.
I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
Changing it back to XML Gateway (and re-deploying) causes all original problems.
Regards,
Wanda

How to view SOAP header generated from XML Gateway ?

Hi All,
I am using XML Gateway integrate EBS and trading partner using web services.
Currently I am having problem with including wsse authorization information in the outbound message of EBS.
I am able to view the payload in the transaction monitor but not able to check the SOAP header of message.
How to view the current SOAP header generated by EBS and/or include the wsse information which are required by recipient trading partners ?
Thanks in advance for your help.
Regards,
Ram

No, this XML is the whole XI message and it is not sent by the SOAP (axis) adapter. If you want to see exactly what is sent, try checking it with the TCPGateway tool as advised on the SOAP FAQ note
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
Under question "Q: How can I trace the whole message?". Otherwise, on SXMB_MONI, try selecting the PAYLOAD item on the left menu and, on the payload on the right, right-click and select "VIEW SOURCE".

Oracle XML Gateway Message Designer for Oracle EBS R12.1.2

Goog Day to everyone!
I'm Looking for the tool "XML Gateway Message Designer". I have found in Metalink(Oracle Support) the note ID 557101.1, here explain how to get the message designer for Oracle Apps R12. It says that you have to download the patch 4066964. This patch install the Oracle Workflow Builder (2.6.3.0.1) and the Oracle XML Gateway Message Designer (2.6.3). This tools are supported to be used with Oracle Apps 11.5.10 and 12.0.X.
The release of Oracle Apps that I'm using is 12.1.2.
Questions:
- The version of the Message Designer that you get from patch 4066964 works for OraApps R12.1.2 ?
- The version of the Workflow Builder that you get from patch 4066964 works for OraApps R12.1.2 ?
- If the version of Message Designer doesn't work with OraApps R12.1.2, where can I find one that works with it?
Thanks for your advice.
LCJ

Hi Hussein,
Thanks for replay.
I downloaded the rapid install package from e-delivery. The B53824-01_4of4 was the OWB installer, and it has a readme file that says: "+This patch contains Oracle Workflow Builder (version 2.6.3.0.1) and Oracle XML Gateway Message Designer (version 2.6.3). These client tools are supported for use with an Oracle E-Business Suite Release 12.1 instance.+"
I believe, as well as you, that it should be work for 12.1.2.
I'm gonna make some test, and in a few days I will post my results.
Thanks for the help.
LCJ

Posting XML via HTTP post returns "Envelope missing in SOAP message header"

Hi,
I am trying to post a simple XML message directly to the integration server using an html document, where the form that contains the XML message is a simple
<b><FORM action="http://servername:8000/sap/xi/engine?type=entry" method="post"></b>
So, I add my xml message like this:
<?xml version="1.0" encoding="UTF-8">
<ns:PlantMaintenanceMessageType xmlns:ns="http://sap.com/demo/plantmaintenance">
      <EquipmentID>SLIEQUIP5</EquipmentID>
      <FunctionalLocation>KB</FunctionalLocation>
      <Date/>
      <Time/>
</ns:PlantMaintenanceMessageType>
but I get a message back from the Integration Server as:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
<SAP:P1>Envelope</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<b><SAP:Stack>XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack></b>
</SAP:Error>
Seems like I am missing the Envelope so my Integration Server can understand my post. What does the Envelope look like or should conatain so that the Integration Server accepts my XML file ?
Thanks !

This is the trace
<?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="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<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.1</Trace>
<Trace level="2" type="T">Host = sapqxh:8020</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.228.137.106</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</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="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:04Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTL0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTL0000</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MIOA_US139_EmployeeData*</Trace>
<Trace level="1" type="T">select interface namespace urn:abbott-com:US139</Trace>
<Trace level="1" type="T">found interface MIOA_US139_EmployeeData</Trace>
<Trace level="1" type="T">found action ARCH</Trace>
<Trace level="1" type="T">set interface action to ARCH</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET 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">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</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">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</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_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - BS_AIMS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-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">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</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">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</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_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_AIMS MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2008-07-18T14:19:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</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_RECEIVER_SPLIT</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">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</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_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTM0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</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">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</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_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 3CCA7AE76D3F33F19F8D7A8DAD494E65</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping C387A5F00F8B11DCAB84C751AAE12E82</Trace>
<Trace level="1" type="T">Interface Mapping urn:abbott-com:US139 IM_US139_EmployeeData</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_US139_EmployeeData_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_.</Trace>
<Trace level="3" type="T">Load c387a5f0-0f8b-11dc-ab84-c751aae12e82, urn:abbott-com:US139, -1, com/sap/xi/tf/_MM_US139_EmployeeData_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_US139_EmployeeData_.class (urn:abbott-com:US139, -1) in swcv c387a5f0-0f8b-11dc-ab84-c751aae12e82.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_ completed. (executeStep() of com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:22:07Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</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_OUTBINDING</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">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</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_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-QEHCLNT230</Trace>
<Trace level="2" type="T">-BS_AIMS</Trace>
<Trace level="2" type="T">urn:abbott-com:US139.MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">Channel found: - BS_AIMS - CC_BS_AIMS_File_Out_09</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="Timestamp">2008-07-18T14:22:18Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Unknown channel type: File</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</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">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</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_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="2" type="T">Adapter Framework(s) found</Trace>
<Trace level="2" type="T">Service Port(s) found - take first one</Trace>
<Trace level="2" type="T">URL found</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="3" type="T">URL = http://sapqxh:52000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = PIISUSER</Trace>
<Trace level="3" type="T">Cached =</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="1" type="T">Empty response received!</Trace>
<Trace level="3" type="System_Error">HTTP-client: error response=</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>

Dequeuing XML Gateway Messages enqueued with WF_SEND with Block Mode = Y

I am developing a process to dequeue message from the ECX_OUTBOUND queue. The message is enqueued by an Oracle Workflow processes which raises a WF_SEND event. The Block Mode attribute of the WF_SEND event is set to "Y" which causes the workflow activity to wait for a response from the messaging system. The XML Gateway User's Guide says "the messaging system (such as OTA or Webmethods) will return the delivery status regardless of success or failure".
My process successfully dequeues the message but the workflow process remains active waiting for a response.
How do I return a response (the delivery status) to XML Gateway to cause the workflow to continue or error?

Hi,
Run the diagnostics script in (Note: 732295.1 - R12.0.6+ : Oracle Application Object Library XML Gateway Engine Setup Test) and see if it returns any error/warning messages.
Regards,
Hussein

Seeking examples of custom XML Gateway message map

I've been asked to create some custom XML Gateway message maps for inbound/outbound XML data feeds.
I've followed along at [this tutorial|http://docs.oracle.com/cd/E12839_01/integration.1111/e10537/T430238T430339.htm#T430357], but it stops short of telling me how to define a custom message map.
Does anyone know of a resource I could look at - a web site, book, etc., that would cover the creation of a custom message map?

Have a look
http://docs.oracle.com/cd/E18727_01/doc.121/e12954/T319774T319778.htm

How to recover from XML gateway error when generating outbound message

Hi,
Due to a misconfiguration in other part of the system, our Purchase Order Request map (RosettaNet PIP3A4) failed on few dozen of orders and ended with an error.
How can we restart the process and retry the map generation in XML Gateway (as now the problem is fixed)?
Many thanks in advance,
Regards
Kamil

Hi Kamil;
please check below and see its helpful:
http://download.oracle.com/docs/cd/B31017_01/core.1013/b28764/esb002.htm
http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28211.pdf
Regard
Helios

XML Gateway outbound from BPEL

We are trying to get the data from EBS using BPEL Process through XML Gateway outbound.
We created XML Gateway DTD and Map and successfully posting to ECX_OUTBOUND and other sysyems(WebMethods).
Now we are trying access it from BPEL. We created Receive activity to get the XML Payload from ECX_OUTBOUND. But Process is struck in receive activity. Receive activity is waiting for response.
I am not sure we may be doing some thing wrong. Please help us.

I have created screen-shots to show that.
Receive
Variable
Port
I have also tried adding header variable to receive activity in xml but it's not working
<receive name="Receive_1" createInstance="yes"
variable="Receive_1_Dequeue_InputVariable_1"
partnerLink="ECX_OUTBOUND" portType="ns1:Dequeue_ptt"
operation="Dequeue" bpelx:headerVariable="Variable_1"/>
Thanks for your help
Pawel
What's more: When I change port type operation input message to Header_msg i gets the message to my Variable_1 of type Header_msg but data loaded to it is in format of this PROCESS_PO_007_msg
I've found in documentation:
Supporting for Normalized Message Properties
To effectively set applications context values required in a BPEL process or to populate
mandatory header variables for XML Gateway inbound transactions to complete
successfully, Adapter for Oracle Applications provides a flexible mechanism that allows
each context value and header variable to be set and passed in the adapter user interface
directly through the Invoke activity. This message normalization feature not only
provides a flexible solution on header support, but also simplifies the design-time tasks
without using an Assign activity to pass header values.
Setting Message Properties for Applications Context
But there is nothing about Outbound transactions....
Edited by: pawel.fidelus on 2009-12-18 02:59
Edited by: pawel.fidelus on 2009-12-18 03:37

Support on 'Base64 encoding in XML gateway Web service SOAP content'

Hi Experts,
IHAC who's requirement is as follows:
They are currently using Web service protocol to send order information from Oracle Applications to their trading partner.
But need to encode the payload in base64 encoding in the SOAP request.
Further details:
=====================================================================
Current SOAP request is,
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:bac="http://backend.ws.gtas.gridnode.com">
<soapenv:Header/>
<soapenv:Body>
<bac:backendImport4>
<bac:username>?</bac:username>
<bac:password>?</bac:password>
<bac:recipient>?</bac:recipient>
<bac:contentFileName>?</bac:contentFileName>
<bac:content>
<EMPLOYEE>
<EMPLOYEE_DATA>
<EMAIL_ADDRESS/>
<EMPLOYEE_ID>81</EMPLOYEE_ID>
<EMPLOYEE_NUM>2</EMPLOYEE_NUM>
<FIRST_NAME/>
<FULL_NAME>Eddi.S,</FULL_NAME>
<LAST_NAME>Eddi.S</LAST_NAME>
<MIDDLE_NAME/>
</EMPLOYEE_DATA>
</EMPLOYEE>
</bac:content>
<bac:docType>?</bac:docType>
</bac:backendImport4>
</soapenv:Body>
</soapenv:Envelope>
Required SOAP request with base64 encoding is:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:bac="http://backend.ws.gtas.gridnode.com">
<soapenv:Header/>
<soapenv:Body>
<bac:backendImport4>
<bac:username>?</bac:username>
<bac:password>?</bac:password>
<bac:recipient>?</bac:recipient>
<bac:contentFileName>?</bac:contentFileName>
<bac:content>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=
</bac:content>
<bac:docType>?</bac:docType>
</bac:backendImport4>
</soapenv:Body>
</soapenv:Envelope>
The issue in question is the content within the element <bac:content>.
Base64 encoding of the payload
<EMPLOYEE>
<EMPLOYEE_DATA>
<EMAIL_ADDRESS/>
<EMPLOYEE_ID>81</EMPLOYEE_ID>
<EMPLOYEE_NUM>2</EMPLOYEE_NUM>
<FIRST_NAME/>
<FULL_NAME>Eddi.S,</FULL_NAME>
<LAST_NAME>Eddi.S</LAST_NAME>
<MIDDLE_NAME/>
</EMPLOYEE_DATA>
</EMPLOYEE>
is
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=
========================================================================
Is there a way in XML gateway to encode the payload automatically to base64 encoding so that it can accommodate the unicode
Is there any way to encode the order information from EBS tables to base64 format in the outbound SOAP request ? Is this supported . If yes, how.?
Does this involve customization. Is it possible to use encoder/decoder provided in sites such as XSL on top of XML : http://gandhimukul.tripod.com/xslt/base64-xslt.html
Basically, They are trying to use XML Gateway to send and receive messages to a Trading Partner via SOAP. The issues is
1. Outbound: The TP web service can only receive xml content that is encoded in base 64 binary format. How do we configure to encode content using base64
2. Inbound: They want to receive messages using the SOAP architecture into XML gateway.
Please let us know if you have any detailed configuration document for this purpose. Please advise and share relevant details.
regards,
Ajith

Hi Gurvinder,
Thanks for looking into this. Just to clarify again.
example XML content:
<?xml version="1.0" encoding="UTF-8" standalone='no'?>
<!DOCTYPE EMPLOYEE>

<EMPLOYEE>
<EMPLOYEE_DATA>
<EMAIL_ADDRESS/>
<EMPLOYEE_ID>81</EMPLOYEE_ID>
<EMPLOYEE_NUM>2</EMPLOYEE_NUM>
<FIRST_NAME/>
<FULL_NAME>Eddi.S,</FULL_NAME>
<LAST_NAME>Eddi.S</LAST_NAME>
<MIDDLE_NAME/>
</EMPLOYEE_DATA>
</EMPLOYEE>
Sample Soap message that needs to be sent to our service provider is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
- <soapenv:Body>
- <ns5:backendImport5 xmlns:ns5="http://backend.ws.gtas.gridnode.com">
<ns5:username>admin</ns5:username>
<ns5:password>admin1</ns5:password>
<ns5:recipient>GT424</ns5:recipient>
<ns5:contentFileName>cabotTest.xml</ns5:contentFileName>
<ns5:content>PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=</ns5:content>
<ns5:docType>3C3RN</ns5:docType>
</ns5:backendImport5>
</soapenv:Body>
</soapenv:Envelope>
. The xml content provided need to be encoded as base 64 encoding. The following is the equivalent of above xml content.
<ns5:content>PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9J25vJz8+DQo8IURPQ1RZUEUgRU1QTE9ZRUU+DQo8IS0tIE9yYWNsZSBlWHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSBHYXRld2F5IFNlcnZlciAgLS0+DQo8RU1QTE9ZRUU+DQogIDxFTVBMT1lFRV9EQVRBPg0KICAgIDxFTUFJTF9BRERSRVNTLz4NCiAgICA8RU1QTE9ZRUVfSUQ+ODE8L0VNUExPWUVFX0lEPg0KICAgIDxFTVBMT1lFRV9OVU0+MjwvRU1QTE9ZRUVfTlVNPg0KICAgIDxGSVJTVF9OQU1FLz4NCiAgICA8RlVMTF9OQU1FPkVkZGkuUyw8L0ZVTExfTkFNRT4NCiAgICA8TEFTVF9OQU1FPkVkZGkuUzwvTEFTVF9OQU1FPg0KICAgIDxNSURETEVfTkFNRS8+DQogIDwvRU1QTE9ZRUVfREFUQT4NCjwvRU1QTE9ZRUU+DQo=</ns5:content>
See that the content is encoded using the base64 format.
Please help us to know how we can configure XML gateway to achieve this.
Regards,
Ajith

Sending document to oracle xml gateway web service and body is url encoded

Hello,
a question from a complete newbie to web services. I have some code that is sending a soap message to an oracle xml gateway web service. In the soap message the values in the soap body look like &lt ;CNTROLAREA&gt ;
when I would be expecting <CNTROLAREA>. What I have been told is that the content of the ReceiveDocument element has been url encoded which causes the &lt and to correct it I need to change the paramater type from object to xmlnode and to build the request as an xmldocument. The xmlnode and xmldocument comes from a .net guy so I've been trying to find the equivalent in java but am not having any luck. I have a lot of reading to do but was wondering if someone might be able to point me in the right direction on how to correct the problem. I captured the soap message being sent using tcpmon. Why does the body have the &lt instead of the < as I was expecting and is there an xmldocument type? The header part of the soap message looks as I expect. "><soapenv:Header><ns1:XMLGateway_Header xmlns:ns1="http://xmlns.oracle.com/apps/fnd/XMLGateway"><ns1:MESSAGE_TYPE>XML</ns1:MESSAGE_TYPE>. It is being sent as a com.oracle.xmlns.apps.fnd.XMLGateway.XMLGateway_Header type.
thanks
Thanks
Edited by: twf123 on May 5, 2010 11:59 AM
Edited by: twf123 on May 5, 2010 12:00 PM

twf123 wrote:
What I have been told is that the content of the ReceiveDocument element has been url encoded which causes the &lt and to correct it I need to change the paramater type from object to xmlnode and to build the request as an xmldocument. Where do you change the parameter type?
The xmlnode and xmldocument comes from a .net guy so I've been trying to find the equivalent in java but am not having any luck. How do you get the data from .net guy? Which interface do you use? What processing do you do after receiving the data?

XML Gateway / OXTA message header

Similar Messages

Maybe you are looking for