About Transport Protocol File(Axis)

Hi All,
In my Scenario i am using SOAP Adapter at Receiver Side..
While Creating Communication Channel For Receiver In Transport Protocol we have many options like HTTP,SMTP,File(Axis) etc.
In which case we opt File(Axis)?

Hi Deepthi,
You configure the receiver Axis SOAP adapter to send information from the Integration Server or the PCK to remote clients or Web service servers.
Check the below link :-
http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm
and check the heading -- Configuring the Receiver Axis SOAP Adapter
under the below thread
http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a3c48c87cd0039e10000000a11466f/frameset.htm
Regards,
Rohit

Similar Messages

What is the transport protocol File (Axis) in the SOAP Adapter

Hi,
for a SOAP Receiver Adapter it's possible to choose 'File (Axis)' as transport protocol.
How does it work and is there some documentation about it?
Thanks and regards
Patrick

Hi,
thanks for your answers.
@Prateek
Yes I tried -> Doesn't say so much
@Vinod
The first thread didn't helped me and I have seen already the second one.
@kummari
The question is how can I use it?
@Gabriel
>The adapter uses transport protocol(File (Axis)) to send SOAP messages as text file
Could you please explain it a little more detailed (maybe with an example)?
My question is about in which scenarios it makes sense to use this transport protocol and how is it used?
Thanks and regards
Patrick

File to File scenario using Transport Protocol FTP Problem

Hi,
my scenario is a file to file scenario using Transport Protocol FTP
there are 3 systems involved
a. computer 1 ( My system-source)
b. computer 2 (XI server)
c. computer 3 (Target system)
I want XI to pick file from computer 1 and post it to computer 3
I am logging on to XI server from computer 1(thro SAP GUI),
Sender communication channel :
Transport protocol:FTP
Messsage protocol: file
In FTP connection Parameters:
Server: computer 1 IP address
port:21
User name and PW---> I have given computer 1 Username and password.
Connection mode: permanently
Transfer mode: Binary
Folder: C:\ftproot\output
filename : given
In Receiver Communication Channel
Transport protocol:FTP
Message protocol: file
In FTP connection Parameters:
Server: computer 3 IP address
port:21
User name and PW---> I have given computer 3 Username and password.
Connection mode: permanently
Transfer mode: Binary
Put File: Use Temporary File
Folder:
eccserver\saploc\tmp
filename scheme: given
When I activate the scenario file is not getting picked from the source
In Adapter Framework: Message says up and running No message processing now
How to check FTP server is up and running on computer 1 (source system)and Computer 2 (XI server)?
What could be the problem ?
Thanks
dushanth

Hi
Consider that I dont have FTP installed on my computer. According to this blog
/people/shabarish.vijayakumar/blog/2006/08/01/along-came-a-file-adapter-mr-ftp-and-rest-of-the-gang
I have configured.
In sender comm channel I have given Ipaddress of computer 1 (which has a file to be picked)
In Receiver Comm channel I have given IP address of computer 3 (in which file to be posted)
and computer 2 is the XI server
Computer 1 has FTP installed
1. XI server should have FTP installed or not ? IF yes is it FTP client or FTP server or Guild FTP (according to the blog is enough)
2. Computer 3 should have FTP installed or not ?
Please help me I am really confused.
Thanks
dushanth

File to file scenario but transport protocol is NFS

send me step by step screenshot for file to file in sap pi 7.1 scenario but transport protocol is NFS

Hi,
Send your email id.
Sreeni.

What is difference between transport protocol and message protocol

what is difference between transport protocol and message protocol
please give definition and small explanation

Hi,
Transport protocol gives information about outside of message details, kind of system, security details.
A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol).
Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP.
Message protocol gives you an idea of message type XI payload
http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm

Getting error using the EMail Transport Protocol

Hi Gurus,
I am using the EMail Transport Protocol (Custom Document over Generic Exchange).
I am able to send the document using this protocol to a exchange server successfully. but when tried to receive the document from exchange server to Oracle B2B. I am getting the below error.
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
 at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
 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)
As per my knowledge all necessary properties are reaching Oracle B2B. Please go through the b2b.log content below.
2009.05.14 at 13:16:56:994: Thread-20: B2B - (DEBUG)
Protocol = Email
Version = null
Transport Header
SUBJECT:Test Message from SP
ACTION_NAME:CSVProcess
DATE:Thu, 14 May 2009 12:16:46 GMT
CONNECTION:close
TO:[email protected]
CONTENT-TYPE:multipart/mixed; boundary="----=_Part_3_11019994.1242303406228"
MIME-VERSION:1.0
X-MAILER:IPTransport
FROM_PARTY:EmailTP_GI
DOCTYPE_NAME:CSVProcess_DT
DOCTYPE_REVISION:1.0
FROM:EmailTP_GI
MESSAGE-ID:AC18E52A1213F0D9FB9000001629E7B0
RECEIVED:from INBAAMPC00933 ([172.24.229.42]) by vitz.techm.com (IceWarp 9.1.1) with ESMTP id VRE73645 for <[email protected]>; Thu, 14 May 2009 13:16:45 +0100
TO_PARTY:EmailSP_GI
Content-Type:application/b2b; name="Test Message from SP"
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) InterfaceListener:onMessage - Invoke inbound callout - null - null
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) InterfaceListenersyncAckEBMSchecking header names
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2009.05.14 at 13:16:57:088: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2009.05.14 at 13:16:57:088: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:onMessage sendEventtrue
2009.05.14 at 13:16:57:088: Thread-20: B2B - (DEBUG) DBContext commit: Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.05.14 at 13:16:57:104: Thread-19: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:unpack:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMessageContent:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processInputStreamOrStringMessage:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processInputStreamOrStringMessage:Content Type = application/b2b; name="Test Message from SP"
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:newMimeBodyPart.getAllHeaders()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:getting content info
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:setContentTypeInfo:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:setContentTypeInfo:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:newMimeBodyPart.getContent()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:check content type(InputStream/String)
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:contentObj instanceof InputStream
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:addMimeBodyPartToMessageInfoString()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processInputStreamOrStringMessage:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMessageContent:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:doUnpack:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:unpack:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {Email}
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromTPoveride = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = EmailTP_GI tmpFromParty :EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromTPName ..GOT FROM CACHE= null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Remote TP Name = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: Generic Identifier Value: EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage toTPoveride = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Host TP Name = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: Generic Identifier Value: EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: Generic Identifier Value: [email protected]
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP [email protected]
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
 at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
 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.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {SUBJECT=Test Message from SP, ACTION_NAME=CSVProcess, DATE=Thu, 14 May 2009 12:16:46 GMT, CONNECTION=close, [email protected], CONTENT-TYPE=multipart/mixed; boundary="----=_Part_3_11019994.1242303406228", MIME-VERSION=1.0, X-MAILER=IPTransport, FROM_PARTY=EmailTP_GI, DOCTYPE_NAME=CSVProcess_DT, DOCTYPE_REVISION=1.0, FROM=EmailTP_GI, MESSAGE-ID=AC18E52A1213F0D9FB9000001629E7B0, RECEIVED=from INBAAMPC00933 ([172.24.229.42]) by vitz.techm.com (IceWarp 9.1.1) with ESMTP id VRE73645 for <[email protected]>; Thu, 14 May 2009 13:16:45 +0100, TO_PARTY=EmailSP_GI, Content-Type=application/b2b; name="Test Message from SP"}
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2009.05.14 at 13:16:57:135: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2009.05.14 at 13:16:57:151: Thread-20: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.05.14 at 13:16:57:151: Thread-20: B2B - (DEBUG) DBContext commit: Leave
2009.05.14 at 13:16:57:370: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value Generic [email protected]
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = AC18E52A1213F0D9FB9000001629E7B0
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2009.05.14 at 13:16:57:433: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2009.05.14 at 13:16:57:433: Thread-19: B2B - (DEBUG) Engine:notifyApp Enter
2009.05.14 at 13:16:57:433: Thread-19: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>AC18E5411213F0DCB100000013829EB0</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (INBAAMPC00883)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
 at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
 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)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) Engine:notifyApp Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) DBContext commit: Enter
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) DBContext commit: Leave
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
Kindly look into this.
Regards,
Vithal

Hi Nandagopal,
I have configured email idc to send the payload as an attachment. & the attachment I am trying is send is a simple text file. So I am stuck here, how can I check against xPath for the mail :(.
I have copied the sample message below which is there in the SMTP server & ready to be fetched by Oracle B2B. This is how message looks like in the exchange server, before it gets consumed by Oracle B2B.
============================================================
Message-ID: AC18E52A121544A46D4000001629E840
DATE: Mon, 18 May 2009 15:15:02 GMT
From: [email protected]
FROM: EmailTP_GI
To: [email protected]
Subject: Test Message from SP
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="----=_Part_6_17282414.1242659702625"
X-Mailer: IPTransport
ACTION_NAME: CSVProcess
DOCTYPE_NAME: CSVProcess_DT
FROM_PARTY: EmailTP_GI
DOCTYPE_REVISION: 1.0
TO_PARTY: EmailSP_GI
Connection: close
------=_Part_6_17282414.1242659702625
Content-Type: application/b2b; name="Test Message from SP"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Test Message from SP"
PGRvY3VtZW50IHhzaTpzY2hlbWFMb2NhdGlvbj0iaHR0cDovL0JUZUJvbmQuaHAuY29tIGZpbGU6
L0Q6L3RyYW5zZm9ybWF0aW9uLWVuZ2luZS9yaWNoYXJkL3NjaGVtYTAueHNkIiB4bWxuczp4c2k9
Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvWE1MU2NoZW1hLWluc3RhbmNlIiB4bWxucz0iaHR0cDov
L0JUZUJvbmQuaHAuY29tIj4KCgogICAgPHRyYW5zX2lkPnRyYW5zX2lkMDwvdHJhbnNfaWQ+Cgog
ICAgPGUyZV9pZD5lMmVfaWQwPC9lMmVfaWQ+CgogICAgPG1zZ190c3RhbXA+MjAwNi0wNS0wNFQx
ODoxMzo1MS4wWjwvbXNnX3RzdGFtcD4KCiAgICA8dHJhbnNfdHlwZT5JTkNJREVOVDwvdHJhbnNf
dHlwZT4KCiAgICA8dHJhbnNfc3ViX3R5cGU+Q1JFQVRFPC90cmFuc19zdWJfdHlwZT4KCiAgICA8
c2NfdHlwZT5JTjwvc2NfdHlwZT4KICAgIDxzZW5kZXJfaWQ+c2VuZGVyX2lkMDwvc2VuZGVyX2lk
PgoKICAgIDxzZW5kZXJfdGlja2V0X2lkPnNlbmRlcl90aWNrZXRfaWQwPC9zZW5kZXJfdGlja2V0
X2lkPgogICAgPGRlc3RfaWQ+ZGVzdF9pZDA8L2Rlc3RfaWQ+CiAgICA8ZGVzdF90aWNrZXRfaWQ+
ZGVzdF90aWNrZXRfaWQwPC9kZXN0X3RpY2tldF9pZD4KCiA8YWNrX3N0YXR1cz5hY2s8L2Fja19z
dGF0dXM+CiAgICA8YWNrX21zZz5hY2ttc2c8L2Fja19tc2c+CiAgICA8Y2FsbGVyPgogICAgICAg
IDxzZWFyY2hjb2RlPnNlYXJjaDwvc2VhcmNoY29kZT4KICAgICAgICA8ZW1haWw+YnRzZW50cnlA
YnQuY29tPC9lbWFpbD4KICAgICAgICA8Zmlyc3RfbmFtZT5Tb3VyYXY8L2ZpcnN0X25hbWU+CiAg
ICAgICAgPGxhc3RfbmFtZT5HYW5ndWx5PC9sYXN0X25hbWU+CiAgICAgICAgPHRlbGVwaG9uZT4x
MjM0NTY8L3RlbGVwaG9uZT4KICAgICAgICA8c3RyZWV0MT5TYWx0IExha2UgQ2l0eTwvc3RyZWV0
MT4KICAgICAgICA8c3RyZWV0Mj5Lb2w8L3N0cmVldDI+CiAgICAgICAgPGNpdHk+S29sa2F0YTwv
Y2l0eT4KICAgICAgICA8c3RhdGVfcHJvdmluY2U+V2VzdCBCZW5nYWw8L3N0YXRlX3Byb3ZpbmNl
PgogICAgICAgIDxjb3VudHJ5PkluZGlhPC9jb3VudHJ5PgogICAgICAgIDx6aXBfY29kZT41NjAw
MTY8L3ppcF9jb2RlPgogICAgPC9jYWxsZXI+CgogICAgPHByaW9yaXR5PkhpZ2g8L3ByaW9yaXR5
PgogICAgPGltcGFjdD5EaWFzdHJvdXM8L2ltcGFjdD4KICAgIDxzdGF0dXM+QWN0aXZlPC9zdGF0
dXM+CiAgICA8c3RhdHVzX2NoYW5nZV90c3RhbXA+CiAgICAgICAgMjAwMi0xMC0xMFQxMjowMDow
MC0wNTowMAogICAgPC9zdGF0dXNfY2hhbmdlX3RzdGFtcD4KCgoKCgogICAgPGhwX2lkPmhwX2lk
MDwvaHBfaWQ+CiAgICA8Y2VfaWQ+Y2VfaWQwPC9jZV9pZD4KCgo8ZGVzY3JpcHRpb24+Tm8gY29v
bDwvZGVzY3JpcHRpb24+CiAgICA8aW5mbz5UaGlzIGlzIGNvb2w8L2luZm8+CiAgICA8d29ya2xv
Zz5sb2dnaW5mPC93b3JrbG9nPgogICAgPHdvcmtncm91cD5JbmRlZWQ8L3dvcmtncm91cD4KICAg
IDxjbGFzc2lmaWNhdGlvbj5jbGFzczwvY2xhc3NpZmljYXRpb24+CiAgICA8Y2xvc3VyZV9jb2Rl
PjExMjwvY2xvc3VyZV9jb2RlPgogICAgPGNsb3N1cmVfY29kZV9kZXNjPjEwMDwvY2xvc3VyZV9j
b2RlX2Rlc2M+CiAgICA8c29sdXRpb24+UmVxdWlyZXM8L3NvbHV0aW9uPgoKCjxjb21wbGV0aW9u
X2RhdGU+MjAwMi0xMC0xMFQxMjowMDowMC0wNTowMDwvY29tcGxldGlvbl9kYXRlPgogICAgPGNj
ZD4yMDAyLTEwLTEwVDEyOjAwOjAwLTA1OjAwPC9jY2Q+CiAgICA8Y2NkX2RldGFpbHM+VGVjaE08
L2NjZF9kZXRhaWxzPgoKCgo8Y2k+CiAgICAgICAgPHNlYXJjaGNvZGU+NTYwMDE2PC9zZWFyY2hj
b2RlPgogICAgICAgIDxzdHJlZXQxPjJuZCBDcm9zcyA0dGggTWFpbjwvc3RyZWV0MT4KICAgICAg
ICA8c3RyZWV0Mj5TYWRhbmFuZCBOYWdhcjwvc3RyZWV0Mj4KICAgICAgICA8Y2l0eT5CYW5nYWxv
cmU8L2NpdHk+CiAgICAgICAgPHN0YXRlPkthcm5hdGFrYTwvc3RhdGU+CiAgICAgICAgPHppcGNv
ZGU+NTYwMDE2PC96aXBjb2RlPgogICAgICAgIDxjb3VudHJ5PkluZGlhPC9jb3VudHJ5PgogICAg
ICAgIDxtYWtlPkluZGlhPC9tYWtlPgogICAgICAgIDxtb2RlbD4xOTk2PC9tb2RlbD4KICAgICAg
ICA8c2VyaWFsX25vPjEyMzQ1Njc4OTwvc2VyaWFsX25vPgogICAgICAgIDxhc3NldF9ubz4xMjM0
NTY3ODk8L2Fzc2V0X25vPgogICAgICAgIDxuYW1lMT5Sb2NrPC9uYW1lMT4KICAgICAgICA8bmFt
ZTI+T248L25hbWUyPgogICAgICAgIAogICAgPC9jaT4KCgo8c2VydmljZT5NTEM8L3NlcnZpY2U+
CiAgICA8c2VydmljZV9pbXBhY3RlZD5ZZXM8L3NlcnZpY2VfaW1wYWN0ZWQ+CiAgIDwhLS0gPGNs
b3N1cmVfZGF0ZT4yMDAyLTEwLTEwVDEyOjAwOjAwLTA1OjAwPC9jbG9zdXJlX2RhdGU+IC0tPgog
ICAgPHJlZ19jcmVhdGVkPjIwMDItMTAtMTBUMTI6MDA6MDAtMDU6MDA8L3JlZ19jcmVhdGVkPgog
ICAgPHRhcmdldF9kYXRlPjIwMDItMTAtMTBUMTI6MDA6MDAtMDU6MDA8L3RhcmdldF9kYXRlPgoK
ICAgIDxyZXFfc3RhcnRfdHN0YW1wPjIwMDItMTAtMTBUMTI6MDA6MDAtMDU6MDA8L3JlcV9zdGFy
dF90c3RhbXA+CjxlY2hvPnNpbXBsZTwvZWNobz4KCgoKPC9kb2N1bWVudD4=
------=_Part_6_17282414.1242659702625--
======================================================
Regards,
Vithal

AS2 as transport protocol and AS2xml as message protocol

Dear All
AS2 adapter has been installed in our landscape ,when I am trying to select the transport protocol and message protocol ,I can only see AS2 as transport protocol and AS2xml as the message protocol instead of the normal HTTP/ HTTPs for the Transport protocol and AS2 as message protocol.COuld anyone tell me if there is a problem.We need to send xml messages over the AS2 adapter and receive MDN's.

Hi Arjun,
Refer below forum threads which was replied which talks about the configuration which need to be done for AS2 adapter. It will be helpful:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
Re: Regarding Seeburger AS2 Adapter
Regards,
Vinod.

Transport protocol and authentication method

Hi gurus,
i am trying to configure EBP-SUS, i am not having access to solution manager .
I am working on SRM_SERVER 5.5.
can somebody who has configured EBP-SUS give me more information about the transport protocol and the authenticaton method.

solved by self

NFS or FTP transport protocol

what is the difference between NFS and FTP transport protocol? and when do we use them?
Regards,
Ashish Goyal

NFS stands for File System.
Both of NFS and FTP should make the following specifications for file:
File name schema:
 Name of the file
File Construction Mode:
Create file, append to existing file, or specify additional parameters for the file name
File Type:
Binary or text file (in the case of the latter also specify the file encoding as a code page)
Operating System Command:
To be executed after successful processing (you can use placeholders for the file name)
Additionally,If you specify NFS as the transport protocol, the only other specification you need to make is the Target Directory in which the file is to be generated.
But if you want use FTP, following specifications should be made:
Server
 Host name or IP address of the FTP server
Port
 Port number of the FTP server (default: 21)
Connect Mode
 The connection can be permanently open, or it can be established for each file transfer
Transfer Mode
 Text or binary data transfer
Put File
 Direct or temporary file (collected before final transfer)
Folder
 Target folder for the file
Logon Data
 User/password, or anonymous (anonymous/anonymous)
Check this one
FTP Vs NFS
Message was edited by: YiNing Mao

I want help getting started in transporting PDF files.

I have purchased the ability to transport PDF files. I have clicked on my account and e-mail several times. However, it will not respond.
Thank you.

I'm guessing, Adobe SendNow https://www.acrobat.com/sendnow/
but that's all I know about it.

Changes on Transport Protocol Params under Channels not reflecting

Hello
For a Trading Partner setup in B2B, we already have a HTTP Transport Protocol channel defined, I changed the URL, User and Password today but still outbound pointing and using the old URL and sending files to the Trading Partner. Do i need to bounce or restart anything to reflect new changes so that system will use new URL?
Thanks!

Can you try doing save-validate-deploy on your agreement which is using that channel and retry again .
Thanks,
Sasmit.

Transport Protocol Error

We are getting the following error while running a program to dowload files from a secure ftp server. The same code runs from a local machine but it fails from a server machine.
We are using lotus domino serer to run the agent on the sever
We would be greatful if you could throw some light on this.
09/16/2005 10:11:04 AM HTTP JVM: SSH Object = com.sshtools.j2ssh.SshClient@1eef26b5
09/16/2005 10:11:04 AM HTTP JVM: [INFO] TransportProtocolCommon - -Starting transport protocol
09/16/2005 10:11:04 AM HTTP JVM: [INFO] TransportProtocolCommon - -Registering transport protocol messages with inputstream
09/16/2005 10:11:04 AM HTTP JVM: [ERROR] TransportProtocolCommon - -The Transport Protocol thread failed <java.lang.NoClassDefFoundError: javax/crypto/KeyAgreement>java.lang.NoClassDefFoundError: javax/crypto/KeyAgreement
at com.sshtools.j2ssh.transport.kex.DhGroup1Sha1.onInit(Unknown Source)
at com.sshtools.j2ssh.transport.kex.SshKeyExchange.init(Unknown Source)
at com.sshtools.j2ssh.transport.TransportProtocolCommon.run(Unknown Source)

The problem was occuring because a mistake has been made in the notes.ini file regarding the classpath entries. The wrong classpath entry is deleted and the program works fine now.
Notes.ini is the file which contains the configuration settings of the lotus server.
Regards,
Rajiv

Getting an error message about a missing file when I try to open Firefox

When I tried to open Firefox today I received a message about a missing file (Wrusr.ddl) and that Firefox was not able to open. I tried uninstalling and reinstalling but it did not work. I have no idea what that file is or where is went. I used Firefox 2 days ago and it was working fine. The only thing that changed between then and today was that I renewed my antivirus software but I definitely did not delete any files and I made sure that Firefox is allowed to access the internet. I've been using that same software (Webroot) with Firefox for years and never had any issues before today. Any help would be greatly appreciated! I have included a screenshot of the error message below.

hello angelag.132, the WRusr.dll file is part of Webroot SecureAnywhere - try to reinstall or uninstall that software.

Is there a way to see the details of transport request files

hello friends
for some reason when I try to create a package with objects like function group and function modules, I am not able to import the function modules on the other server.
So i would like to see if the transport request files that I have created (K900226.EC1 and R900226.EC1) has these modules included in them.
Is there a way that I can see what objects are included in the released transport request files.
Your help will be greatly appreciated.
Thanks
Ram

Hi Ram,
You can see the objects included in a transport request by going to se09 and opening your transport request and drill down to the task and below the task you would have all the objects that are included in the tranport. You can also use se03 to get the details by drilling down the tansport request.
The problem with importing the function module might be because either the function module or the function group may not be active which may cause the tranport to fail. please check if both are active or not.

Transport protocol SMTP in Mail Sender Adapter

Hi Experts,
How can I use SMTP as the Transport Protocol instead of POP3 / IMAP4 protocols in the Mail Sender Adapter.
I am referring Note 856599 - FAQ Mail Adapter.pdf but not getting a l
" 9. Other Questions
Q: How can I configure my sender channel for my SMTP server?
A: You can specify your SMTP server as URL. For example, if your
server is called host, your URL should look like
smtp://host:port/ "
Regards,
Shobhit

Hi
How can I use SMTP as the Transport Protocol instead of POP3 / IMAP4 protocols in the Mail Sender Adapter.
In case of sending mail from XI you can use SMTP. To read mails you need POP3
IMAP works for both.
Yes in XI mail adapter receiver type. URL field you can use URL like
SMTP://Mailhost.com
Refer this
The specified item was not found.
Thanks
Gaurav

About Transport Protocol File(Axis)

Similar Messages

Maybe you are looking for