As2 Server

Hi,
I have an As2 server name configured. How do I check whether this http address is right or wrong.
I can;t ping and check as it is https://
Let me know how to check it.
My as2 address is like http://as2.ppp.net:5080/quality (This is just an example and not the right URL)
As it is AS2, should it be as https or http.
Regards
Krish

Hi,
Please check these if I understand it clearly
HTTP/S: https://<xihost_name>:<https_j2ee_port>/SeeburgerAS2/AS2Server
regards,
Satya.

Similar Messages

AS2 Server - Error

Hi All,
Seeburger AS2 adapter is used in the integration. So while opening the AS2 server using the URL http://<host>:<port>/SeeburgerAS2/AS2Server, I am getting the following error
500 Internal Server Error
Application error occurred during request processing.
Details: Error [javax.servlet.ServletException: HTTPController.service ### ERROR CAUGHT ### : java.lang.OutOfMemoryError
original stack trace -> ].
Exception id: [00144F8180E4002A000006E0000059DD000457A3954D16C9].
Can any one provide the solution to solve the above error.
Thank You
Reagards
Prakash

Hi,
Iam not sure about Whether this will solve your Problem or not
just have a look at this
Solving Out of Memory problem Using JNLP
Regards
Seshagiri

** Is it possible to send message directly to the AS2 server using URL

Hi friends,
We have Axway (B2B) Integration software trial version. We have XI system in which AS2 adapter is installed. We want to send EDI file directly from Axway to AS2 adapter of XI by calling the AS2 server URL.
http://<server>:50100/SeeburgerAS2/AS2Server
We have created one File to File scenario in Axway. We have one File to AS2 scenario in XI also. Now, Presently, the scenario in Axway works like, to pick the file from Axway and delivers the output file which is the source directory mentioned in sender CC of XI thru FTP in Axway. Then, XI automatically poll this file and send to AS2 adpater. Instead, we want to send EDI file directly from Axway to AS2 server. We tried the scenario in Axway, but not able to call the URL directly. Any idea, friends.
Kindly reply friends.
Thanking you.
Kind Regards,
Jeg P.

ok, and i answered you
where's the problem? why you can not send this message? is the problem in axway? or you can't see message in the XI? If you can send it from axway and it doesn't reach the XI, what information do you have in your axway log?
p.

Steps to Process standard EDI ANSI X12 997 file from AS2 Server

Hi All,
I have a scenario where we are receiving PO files from an EDI third party via AS2 adapter.
In return, we are sending PO Acknowledgement and Invoice files to the third party via AS2 adapter.
The fomat of the incoming and outgoing files are ANSI X12 (850 for PO, 855 for PO Ack and 810 for Invoices).
Currently client has informed that they are going to send an EDI ANSI X12 997 (Functional Ack) file for each PO Ack or Invoice they receive.
Kindly let me know steps to configure in SAP PI 7.1 to accept the inbound 997 files successfully and place them as it is in PI application server.
Regards,
Subhajit.

Hi , I too have the same requirement.
i am using
Jdev 11.1.1.6
Oracle Editor : 7.0.5.4016
Document Protocol : EDI_X12
Document type : 810 (Invoice )
Version: 4010
Weblogic server :11.1.1.6.0
I followed all the steps to create EDI X12 810 ecs file, converted this to .xsd and then to .dat in Oracle Document Editor as explained in the B2B user guide.
I also configured the trading partner , created agreements and deployed in B2B console. There is no mistake . as i can able to see the def file while configuring Oracle B2B in my Jdev.
I deployed the same process . But no instance is creating for my process. I also configured listing channel to Generic File 1.0. please help me out in this . Thank you.

Sender AS2 to SAP PO; 403 forbidden error

Hello Experts,
I am using the AS2 adapter from the B2B Addon.
I am stuck in the scenario Sender AS2 -> SAP PO; with the 403 forbidden error.
Few queries;
1. Is virtual receiver mandatory ?
2. Is is mandatory to have party for sender and receiver. Currently I am having only Sender ( Party + Comm. Component ) and Receiver ( Comm. Component ( Partner Type = LS )).
Can you help please.
Thanks
Saurabh

Hi Harish,
Thanks for your quick response.
I have configured with the following details :
Sender Party : ABC ( 009 | GLN | 333333333 )
Sender Component : DEF
Receiver Party : PQR ( 009 | GLN | 111111111 )
Receiver Component : XYZ
Sender AS2 adapter :
Expected URL : http://10.194.35.20:8080/as2/HttpReceiver
Message ID Left : .*
Message ID Right : .*
Sender AS2 name : 333333333
Receivers AS2 name : 111111111
Expected subject : AS2 message
Partners in Mendelson :
Partner 1 :
( Local station )
1. Name : Mendelson_AS2
2. AS2 ID : 333333333
3. Email : [email protected]
MDN tab : http://<Mendelson desktop PC IP>:8080/as2/HttpReceiver
Parnter 2 :
1. Name : PQR
2. AS2 ID : 111111111
3. Email : [email protected]
Receipt URL : http://<PI-Host>:<PI-PORT>/AS2/.*
Payload subject : AS2 message
Error details :
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Transmission failed, remote AS2 server reports "Forbidden".
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: HTTP 403
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Message payload stored to

AS2 Adapter

Hi Experts,
I have got a special requirement, can you please suggest is this requirement is possible or not in SAP PI using seeburger AS2 adapter. We have a got probelm in Our GIS System in setting up AS2 profiles for one of our customer. So we thought of using Seeburger AS2 adapter for this requirement.
By using the Seeburger AS2 adapter I have to receive and Post EDI messages. I have to decrypt the Inbound message and need to stage on the PI Server, No need of message mapping and posting to receiver system. We have a process in GIS system to pick the file from PI Server and do the mapping and post the output data to ORD System.
For the outbound transactions like 855 and 856, GIS will generates the EDI 855 and 856 files on PI Server. Seeburger AS2 adapter need to encrypt this messages and send to partner's AS2 server.
Is the above requirement is feasilble in SAP PI using AS2 adapter?
Any other ideas on this is greatly appreciated
Thanks,
Kishore

I have to decrypt the Inbound message and need to stage on the PI Server, No need of message mapping and posting to receiver system.
For inbound cases, you may use PI as the receiver system and use NFS protocol of File adapter to put the file on PI server. If you use decryption certificate at sender, you may perform the decryption very well.
Seeburger AS2 adapter need to encrypt this messages and send to partner's AS2 server.
This can again be done by the encryption certificate shared with the third party using receiver AS2 adapter.
Is the above requirement is feasilble in SAP PI using AS2 adapter?
Yes.
Regards,
Prateek

Error is Receiver AS2 adaptor used for Idoc to AS2 scenario

Hello Experts,
   I am doing Idoc to AS2 B2B scenario where I am getting below error message in runtime workbench comm channel monitoring.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
Sending failed.
Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 10/16/09 9:06 AM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321)
AS2 Adapter failure
Processing task
Sending called.
Message processing started
Basis has already configured the AS2 Server with Certificates and provided me the below details for receiver agreement and those are put in Receiver agreement.
AS2 sender Configuration:
Authentication certificate à TRUSTEDAS2certAS2_datapool
AS2 Receiver Configuration:
Decryption Key à TRUSTEDAS2certXXXenterprise2008
Signing Key à TRUSTEDAS2certXXXenterprise2008
XXX is my receiver partner
For the Receiver party XXX I have maintained the Identifier as given below
*Agency----
Scheme-------Name*
http://sap.com/xi/XI--XIParty--
XXX
Seeburger----
AS2ID----
XXX_AS2ID
There is no need for sender agreement for Sender IDoc but still I tried to created R3 as sender party and R3 Business system, used it for the scenario and created sender agreement for sender Idoc but received same error message in Runtime workbench.
R2 system sender party is also set with identifier with AS2 ID.
MDN mode is set to no MDN in the receiver AS2 communication channel.
Please suggest me if something is missing or wrong in the configuration.
Thanks in advance.
Vinit

Hi Larry,
   The solution was very simple.
It was problem with the basic understanding of system and configuration.
Idoc is send sent by R3 ERP system and target is Partner Party. As ERP system is Business system and not the party w.r.t XI/PI terminology, we are not supposed to use Sender party as Sender ERP system but just use Business system as sender without any sender party. So in this way PI system could recognize that the data is coming from R3 system which is nothing but PI Business system.
Now question comes where to user the Serder Party which was defined with AS2 ID? So answer is in the receiver determination we have to mention the Sender party and sender service in the header mapping part (Also mention receiver party and service).
So in my case problem was with sernder party. I mentioned sender party in all receiver determination, Interface determination, Sender Agreement and receiver agreement where only sender service ie sender system was required. And as I configured my scenario without sender party it worked because PI could recognize the sender R3 system and AS2 ID was recognized form the Header mapping of Receiver Agreement.
Kindly let me know if it works and if you require snap shots of my configuration then I can send you the same.
Regards,
Vinit

Error receiving AS2 message from partner: B2B-50037: B2B inbound message processing error

B2B/SOA 11.1.1.6.0
We are setting a new trading partner and when we started document transmissions we are getting errors on the inbound messages: B2B-50037: B2B inbound message processing error.
The attachment shows the relevant lines from the soa log and diagnostic log files. Here is the error detail that shows:
[URI: /b2b/httpreceiver] Error -: B2B-50037: B2B inbound message processing error[[
Error -: B2B-50037: B2B inbound message processing error
 at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3143)
 at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
 at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:403)
 at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:214)
 at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
From the b2b_wire_message we get these Protocol_Transport_BINDINGS:
ChannelName=TransportServlet
Reverse-Via=LIN-ISA1
AS2-To=accobra.....
Date=Fri, 26 Sep 2014 05:46:17 +0000
AS2-Version=1.2
AS2-From=K.......
Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1
Disposition-Notification-To=http://<ip&port>/as2in
Message-ID=<[email protected]>
MSG_RECEIVED_TIME=Fri Sep 26 00:46:17 CDT 2014
ECID-Context=1.0050z5j^buc6yGn6wnZf6G0002f60007bt;kXjE1ZDLIPGIj2QCYV8QoKSSmLRO_PQT_IS
Content-Type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
Proxy-Client-IP=172.17.25.101
MIME-Version=1.0
User-Agent=e-integration AS2 Server V 6.1.8
X-Forwarded-For=172.17.25.101
Content-Length=3602
Host=nalinsoa05.abd.ad.acco.com
x-weblogic-cluster-hash=QoZzGUzdcjBD5fGIE8Uos5abiHI
EDIINT-Features=multiple-attachments, CEM
Connection=Keep-Alive
X-WebLogic-KeepAliveSecs=30
X-WebLogic-Request-ClusterInfo=true
The message creates a wire message, business message, and an application message.
What doesn't happen is no MDN gets sent back to the partner. It should be a synchronous MDN.
We have double checked the certificates on both ends and they are OK.
The document and Agreement get recognized OK:
Refer To Message
Refer To Message
Sender Type
AS2 Identifier
Sender Value
K. . .
Receiver Type
AS2 Identifier
Receiver Value
accobr. . .
Sender
K. . . l
Receiver
ACCO . . .
Agreement Id
K. . .l_EDI_X12_4010_856_856Def_Inbound
Agreement
K. . .l_EDI_X12_4010_856_856Def_Inbound
Document Type
856
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
INBOUND
State
MSG_ERROR
Acknowledgement Mode
SYNC
Response Mode
ASYNC
Send Time Stamp
09/26/2014 12:46:17 AM
Receive Time Stamp
09/26/2014 12:46:17 AM
The error is vague enough to provide little or no help in locating the root cause of the issue.
Any assistance in providing information on how to get this working would be greatly appreciated.
We do have dozens of other AS2 partners working in this instance just foe reference. We are just having issues with this new partner setup.
Thank you.
Regards,
Ken

Ken,
I am observing the Ack Mode is set as "SYNC" . This is selected by default. This option is available in the channel configuration section
If the usecase is not SYNC, please change as ASYNC and test. It should work.

TP Agreement Not Found -- OAGIS XML document over AS2

Hi,
I am getting TP Agreement not found error while receiving OAGIS XML document over AS2. Below is error message.
Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND
I am not sure why it says null-INBOUND. It appears like it is not able to identify Document Version. DOCTYPE_REVISION=7.2.1 is being passed in the AS2 transport headers but still it does not recognize the version.
I am not sure what is missing. Please give some ideas hints.
Below is the Business Message:----
Id AC12149513F1F78141400000E7DEDE00
Message Id AC12149513F1F78136200000E7DED800
Refer To Message Refer To Message
Sender Type AS2 Identifier
Sender Value SOALocal
Receiver Type AS2 Identifier
Receiver Value PowellIndustries
Sender SOALocal
Receiver Powell
Agreement Id
Agreement
Document Type PROCESS_INVOICE_002
Document Protocol OAG
Document Version 7.2.1
Message Type REQ
Direction INBOUND
State MSG_ERROR
Acknowledgement Mode NONE
Response Mode ASYNC
Send Time Stamp 06/07/2013 11:28:49 AM
Receive Time Stamp 06/07/2013 11:28:50 AM
Document Retry Interval(Channel) 0
Document Remaining Retry(Channel) 0
Document Retry Interval(Agreement)
Document Remaining Retry(Agreement)
Native Message Size 10788
Translated Message Size
Business Action Name
Business Transaction Name
Xpath Name1
Xpath Value1
Xpath Expression1
Xpath Name2
Xpath Value2
Xpath Expression2
Xpath Name3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
Correlation To XPath Value
Correlation To XPath Expression
Wire Message Wire Message
Application Message Application Message
Payload Storage Payload Storage
Attachment Attachment
Label
Collaboration Id AC12149513F1F7813BF00000E7DEDB00
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name AS2
Exchange Protocol Version 1.1
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code B2B-50547
Error Description Machine Info: (pwl.pri) Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
Below is the Wire Message:----
Id AC12149513F1F78115400000E7DED600
Message Id AC12149513F1F78115400000E7DED600
Business Message AC12149513F1F78141400000E7DEDE00
Packed Message Packed Message
Payload Payload
Protocol Message Id <38383939373331343630313931303737@SOALocal>
Refer To Protocol Message Id
Protocol Collaboration Id
Protocol Transport Binding ChannelName=SOALocal dcID=CHANNEL_nlzbB-7511847722850817684 AS2-To=PowellIndustries DOCTYPE_NAME=PROCESS_INVOICE_002 TE=trailers, deflate, gzip, compress DOCTYPE_REVISION=7.2.1 Date=Fri, 07 Jun 2013 16:28:49 GMT AS2-Version=1.1 Accept-Encoding=gzip, x-gzip, compress, x-compress AS2-From=SOALocal url=http://pwl.pri/b2b/transportServlet Content-Transfer-Encoding=binary Message-ID=<38383939373331343630313931303737@SOALocal> Content-type=application/pkcs7-mime; smime-type="enveloped-data" MSG_RECEIVED_TIME=Fri Jun 07 11:28:49 CDT 2013 ECID-Context=1.71b9d2a41e5aaef0:-10db6371:13f1ee6cb74:-8000-000000000000276d;khvE MIME-version=1.0 tpName=PowellIndustries User-Agent=AS2 Server Oracle HTTPClient Version 10h Content-Length=13663 Host=pwl.pri:8001 Connection=close, TE useProxy=false From=SOALocal additionalHeaders=DOCTYPE_NAME=PROCESS_INVOICE_002#DOCTYPE_REVISION=7.2.1
Message Digest Message Digest
Digest Algorithm md5
Transport Protocol HTTP
Transport Protocol Version 1.1
Url http://pwl.pri:8001/b2b/transportServlet
security
Transport Headers ChannelName=SOALocal dcID=CHANNEL_nlzbB-7511847722850817684 AS2-To=PowellIndustries DOCTYPE_NAME=PROCESS_INVOICE_002 TE=trailers, deflate, gzip, compress DOCTYPE_REVISION=7.2.1 Date=Fri, 07 Jun 2013 16:28:49 GMT AS2-Version=1.1 Accept-Encoding=gzip, x-gzip, compress, x-compress AS2-From=SOALocal url=http://pwl.pri:8001/b2b/transportServlet Content-Transfer-Encoding=binary Message-ID=<38383939373331343630313931303737@SOALocal> Content-type=application/pkcs7-mime; smime-type="enveloped-data" MSG_RECEIVED_TIME=Fri Jun 07 11:28:49 CDT 2013 ECID-Context=1.71b9d2a41e5aaef0:-10db6371:13f1ee6cb74:-8000-000000000000276d;khvE MIME-version=1.0 tpName=PowellIndustries User-Agent=AS2 Server Oracle HTTPClient Version 10h Content-Length=13663 Host=pwl.pri:8001 Connection=close, TE useProxy=false From=SOALocal additionalHeaders=DOCTYPE_NAME=PROCESS_INVOICE_002#DOCTYPE_REVISION=7.2.1
certificates certificates
State ERROR
Reattempt Count
Error Code B2B-50547
Error Description Machine Info: (pwl.pri) Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
Error Text Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
exchangeRetryInterval
exchangeRemainingRetry
Message Size 10788
Thanks
Ismail M.

Hi Anuj,
Here is the payload from the wire message. We are using 11.1.1.6.0
<?xml version = '1.0' encoding = 'UTF-8'?>
<PROCESS_INVOICE_002 xmlns="http://www.openapplications.org/171_process_invoice_002">
<CNTROLAREA xmlns="">
 <BSR>
 <VERB value="PROCESS">PROCESS</VERB>
 <NOUN value="INVOICE">INVOICE</NOUN>
 <REVISION value="002">002</REVISION>
 </BSR>
 <SENDER>
 <LOGICALID>POWELLIND</LOGICALID>
 <COMPONENT>B2B</COMPONENT>
 <TASK/>
 <REFERENCEID/>
 <CONFIRMATION>0</CONFIRMATION>
 <LANGUAGE>ENG</LANGUAGE>
 <CODEPAGE/>
 <AUTHID>oracle B2B</AUTHID>
 </SENDER>
 <DATETIME qualifier="CREATION">
 <YEAR/>
 <MONTH/>
 <DAY/>
 <HOUR/>
 <MINUTE/>
 <SECOND/>
 <SUBSECOND/>
 <TIMEZONE/>
 </DATETIME>
</CNTROLAREA>
<DATAAREA xmlns="">
 <PROCESS_INVOICE>
 <INVHEADER>
 <AMOUNT qualifier="DOCUMENT" type="T" index="1">
 <VALUE>5413</VALUE>
 <NUMOFDEC>2</NUMOFDEC>
 <SIGN>+</SIGN>
 <CURRENCY>USD</CURRENCY>
 <DRCR>D</DRCR>
 </AMOUNT>
 <DATETIME qualifier="DOCUMENT" index="1">
 <YEAR>2013</YEAR>
 <MONTH>03</MONTH>
 <DAY>15</DAY>
 <HOUR>00</HOUR>
 <MINUTE>00</MINUTE>
 <SECOND>00</SECOND>
 <SUBSECOND>0000</SUBSECOND>
 <TIMEZONE>-0500</TIMEZONE>
 </DATETIME>
 <DOCUMENTID>1000182</DOCUMENTID>
 <DESCRIPTN/>
 <DOCTYPE/>
 <PAYMETHOD/>
 <REASONCODE/>
 <USERAREA/>
 <PARTNER>
 <NAME index="1">Powell US Operating Unit</NAME>
 <ONETIME/>
 <PARTNRID/>
 <PARTNRTYPE>Supplier</PARTNRTYPE>
 <SYNCIND/>
 <ACTIVE/>
 <CURRENCY/>
 <DESCRIPTN/>
 <DUNSNUMBER/>
 <GLENTITYS/>
 <NAME index="1">Powell US Operating Unit</NAME>
 <PARENTID/>
 <PARTNRIDX/>
 <PARTNRRATG/>
 <PARTNRROLE/>
 <PAYMETHOD/>
 <TAXEXEMPT/>
 <TAXID/>
 <TERMID/>
 <USERAREA/>
 <CONTACT>
 <NAME index="1">No Sales Credit</NAME>
 <CONTCTTYPE/>
 <DESCRIPTN/>
 <EMAIL/>
 <FAX index="1"/>
 <TELEPHONE index="1"/>
 <USERAREA/>
 </CONTACT>
 </PARTNER>
 <PARTNER>
 <NAME index="1">PO Box 843823, Dallas, Dallas, TX, 75284-3823, United States</NAME>
 <ONETIME/>
 <PARTNRID/>
 <PARTNRTYPE>RemitTo</PARTNRTYPE>
 <SYNCIND/>
 <ACTIVE/>
 <CURRENCY/>
 <DESCRIPTN/>
 <DUNSNUMBER/>
 <GLENTITYS/>
 <NAME index="1">PO Box 843823, Dallas, Dallas, TX, 75284-3823, United States</NAME>
 <PARENTID/>
 <PARTNRIDX/>
 <PARTNRRATG/>
 <PARTNRROLE/>
 <PAYMETHOD/>
 <TAXEXEMPT/>
 <TAXID/>
 <TERMID/>
 <USERAREA/>
 <ADDRESS>
 <ADDRLINE index="1">PO Box 843823</ADDRLINE>
 <ADDRTYPE/>
 <CITY>Dallas</CITY>
 <COUNTRY>United States</COUNTRY>
 <COUNTY>Dallas</COUNTY>
 <DESCRIPTN/>
 <FAX index="1"/>
 <POSTALCODE/>
 <REGION/>
 <STATEPROVN>TX</STATEPROVN>
 <TAXJRSDCTN/>
 <TELEPHONE index="1"/>
 <URL/>
 <USERAREA/>
 </ADDRESS>
 <CONTACT>
 <NAME index="1"/>
 <CONTCTTYPE/>
 <DESCRIPTN/>
 <EMAIL/>
 <FAX index="1"/>
 <TELEPHONE index="1"/>
 <USERAREA/>
 </CONTACT>
 </PARTNER>
 <PARTNER>
 <NAME index="1"/>
 <ONETIME/>
 <PARTNRID/>
 <PARTNRTYPE>Carrier</PARTNRTYPE>
 <SYNCIND/>
 <ACTIVE/>
 <CURRENCY/>
 <DESCRIPTN/>
 <DUNSNUMBER/>
 <GLENTITYS/>
 <NAME index="1"/>
 <PARENTID/>
 <PARTNRIDX/>
 <PARTNRRATG/>
 <PARTNRROLE/>
 <PAYMETHOD/>
 <TAXEXEMPT/>
 <TAXID/>
 <TERMID/>
 <USERAREA/>
 <ADDRESS>
 <ADDRLINE index="1"/>
 <ADDRTYPE/>
 <CITY/>
 <COUNTRY/>
 <COUNTY/>
 <DESCRIPTN/>
 <FAX index="1"/>
 <POSTALCODE/>
 <REGION/>
 <STATEPROVN/>
 <TAXJRSDCTN/>
 <TELEPHONE index="1"/>
 <URL/>
 <USERAREA/>
 </ADDRESS>
 <CONTACT>
 <NAME index="1"/>
 <CONTCTTYPE/>
 <DESCRIPTN/>
 <EMAIL/>
 <FAX index="1"/>
 <TELEPHONE index="1"/>
 <USERAREA/>
 </CONTACT>
 </PARTNER>
 <DOCUMNTREF>
 <DOCTYPE>INV</DOCTYPE>
 <DOCUMENTID>10005:21009</DOCUMENTID>
 <PARTNRID/>
 <PARTNRTYPE>Supplier</PARTNRTYPE>
 <DESCRIPTN/>
 <DOCUMENTRV/>
 <LINENUM/>
 <NOTES index="1"/>
 <SCHLINENUM/>
 <SUBLINENUM/>
 <USERAREA/>
 </DOCUMNTREF>
 <INVTAX>
 <AMOUNT qualifier="TAX" type="T" index="1">
 <VALUE>413</VALUE>
 <NUMOFDEC>2</NUMOFDEC>
 <SIGN>+</SIGN>
 <CURRENCY>USD</CURRENCY>
 <DRCR>D</DRCR>
 </AMOUNT>
 <AMOUNT qualifier="TAXBASE" type="T" index="1">
 <VALUE>5413</VALUE>
 <NUMOFDEC>2</NUMOFDEC>
 <SIGN>+</SIGN>
 <CURRENCY>USD</CURRENCY>
 <DRCR>D</DRCR>
 </AMOUNT>
 <QUANTITY qualifier="PERCENT">
 <VALUE/>
 <NUMOFDEC/>
 <SIGN/>
 <UOM/>
 </QUANTITY>
 <DESCRIPTN/>
 <LINENUM/>
 <TAXCODE/>
 <TAXJRSDCTN/>
 <USERAREA/>
 </INVTAX>
 <PYMTTERM>
 <AMOUNT qualifier="DISCNT" type="T" index="1">
 <VALUE/>
 <NUMOFDEC/>
 <SIGN/>
 <CURRENCY/>
 <DRCR/>
 </AMOUNT>
 <DATETIME qualifier="DISCNT" index="1">
 <YEAR/>
 <MONTH/>
 <DAY/>
 <HOUR/>
 <MINUTE/>
 <SECOND/>
 <SUBSECOND/>
 <TIMEZONE/>
 </DATETIME>
 <DATETIME qualifier="DUE" index="1">
 <YEAR>2013</YEAR>
 <MONTH>04</MONTH>
 <DAY>14</DAY>
 <HOUR>00</HOUR>
 <MINUTE>00</MINUTE>
 <SECOND>00</SECOND>
 <SUBSECOND>0000</SUBSECOND>
 <TIMEZONE>-0500</TIMEZONE>
 </DATETIME>
 <DATETIME qualifier="PYMTTERM" index="1">
 <YEAR>1952</YEAR>
 <MONTH>01</MONTH>
 <DAY>01</DAY>
 <HOUR>00</HOUR>
 <MINUTE>00</MINUTE>
 <SECOND>00</SECOND>
 <SUBSECOND>0000</SUBSECOND>
 <TIMEZONE>-0600</TIMEZONE>
 </DATETIME>
 <DESCRIPTN>Net Due in 30 Days</DESCRIPTN>
 <TERMID>30 NET</TERMID>
 <USERAREA>
 <AMOUNT qualifier="TOTAL" type="T" index="1">
 <VALUE>5413</VALUE>
 <NUMOFDEC>2</NUMOFDEC>
 <SIGN>+</SIGN>
 <CURRENCY/>
 <DRCR>D</DRCR>
 </AMOUNT>
 </USERAREA>
 </PYMTTERM>
 </INVHEADER>
 <INVLINE>
 <AMOUNT qualifier="EXTENDED" type="T" index="1">
 <VALUE>50</VALUE>
 <NUMOFDEC/>
 <SIGN>+</SIGN>
 <CURRENCY/>
 <DRCR>D</DRCR>
 </AMOUNT>
 <OPERAMT qualifier="UNIT" type="T">
 <VALUE>5</VALUE>
 <NUMOFDEC/>
 <SIGN>+</SIGN>
 <CURRENCY/>
 <UOMVALUE>1</UOMVALUE>
 <UOMNUMDEC>0</UOMNUMDEC>
 <UOM/>
 </OPERAMT>
 <QUANTITY qualifier="ITEM">
 <VALUE>10</VALUE>
 <NUMOFDEC/>
 <SIGN>+</SIGN>
 <UOM/>
 </QUANTITY>
 <LINENUM>1</LINENUM>
 <DESCRIPTN>11GA SHEET STEEL HOT ROLLED-PICKLED-OILED COMMERCIAL QUALITY.</DESCRIPTN>
 <ITEM>11GA SHEET STEEL HOT ROLLED-PICKLED-OILED COMMERCIAL QUALITY.</ITEM>
 <ITEMTYPE/>
 <ITEMX>11HRPO</ITEMX>
 <OPENITEM/>
 <PROJACTVTY/>
 <UNIT>LB</UNIT>
 <UPC/>
 <USERAREA/>
 <DOCUMNTREF>
 <DOCTYPE>LINE</DOCTYPE>
 <DOCUMENTID>10005:21009:19019</DOCUMENTID>
 <PARTNRID/>
 <PARTNRTYPE>Supplier</PARTNRTYPE>
 <DESCRIPTN/>
 <USERAREA/>
 </DOCUMNTREF>
 <DOCUMNTREF>
 <DOCTYPE>SalesOrder</DOCTYPE>
 <DOCUMENTID>600813</DOCUMENTID>
 <PARTNRID/>
 <PARTNRTYPE/>
 <DESCRIPTN/>
 <USERAREA/>
 </DOCUMNTREF>
 <DOCUMNTREF>
 <DOCTYPE>PurchaseOrder</DOCTYPE>
 <DOCUMENTID>TEST123</DOCUMENTID>
 <PARTNRID>N/A</PARTNRID>
 <PARTNRTYPE>Customer</PARTNRTYPE>
 <DESCRIPTN/>
 <DOCUMENTRV/>
 <LINENUM/>
 <SCHLINENUM/>
 </DOCUMNTREF>
 </INVLINE>
 </PROCESS_INVOICE>
</DATAAREA>
</PROCESS_INVOICE_002>

AS2 sender communication channel

Hi All,
I have one As2 to proxy scenario, using AS2 sender adapter,PI will be receiving flat file from party and I am performing content conversion in sender As2 channel, there is no mapping involved, and PI is sending this data to SAP system via proxy using integrated configuration.
I have used 2 parties, one sender and one receiver, used 2 business components corresponding to each and one SAP system BC.I have mentioned AS2 ids in both the parties, and did the header mapping for receiver in integrated configuration ->Outbound processing tab.
Now when the file is pushed from AS2 server, there is no log in sender channel monitoring, means the file is not getting picked up from the AS2 server at all.
Can anyone please provide inputs how can we debug this problem.
Thanks,
Ruchi

Hi,
If you are using Seeburger AS2 adapter, then:
1. Check if the URL http://XXXXX:50000/SeeburgerAS2/AS2Server is up. It should show-"405 Method Not Allowed "
2. Check for AS2 messages in Seeburger workbench message-MessageIdStore Monitor
Thanks
Rajeev Gupta

Error in AS2 RCV adapter.. SEEBURGER AS2: 307 Temporary Redirect #

Hi all,
Iam just doing File to File scenario and passing the resultant file to Partner system through AS2 adapter.
I gave the following details in AS2 RCV adapter..
SND>XI->Webdispatcher--->Partner.
My message will be reached to webdispatcher.. from there it will route to Partner Url.
So i will be giving my webdispatcher URL in my AS2 RCV adapter.
TP : HTTP
MP : AS2
Server : vvvvvv.com.NZ
Port : 50000
Url : /as2gs1/partnera
Message is processed succesfully but its failing in AS2 RCV adapter with following error.
Success      SEEBURGER/AS2: Received order from system.
Error      Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
Error      MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
Error      Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
Error      Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #.
Error      The message status set to NDLV.
Kindly let me know if anyone know th solution.
Regards
Seema.

Hi Peter,
>> a, what do you mean with the Web Dispatcher?
We are not using the partner URL directly.We will be using Webdispatcher URL .. from there they have written the rule to goto Partner URL.
>> b, you receive a HTTP code 307, which means that the target AS2 location has been moved. Try to connect the target AS2 server on the URL and check, if it is really there and if it is working.
Looks like this is working.. its showed success state for a while and after few minutes.. its showing the below error in communication channel monitoring.
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address #.
This is the error it is showing in Seeburger Monitoring.
State                          : Error on send, will be retried
Status Description : Could not deliver as2 message to partner: java.net.SocketException: Connection timed out:could be due to invalid address # null
What is this error?
Do u think there is no problem with AS2 adapter.. its the problem wit webdispatcher.??
Waiting for your reply.
-Seema.

Seeburger AS2 receiver adapter conf PI 7.1

Dear All,
I have seen a changed AS2 adapter on PI 7.1,the options are totally different than what we have in previous version of AS2 adapter.
I am looking for seeburger AS2 adapter documents and configuration steps for PI7.1 version.
Any inputs...
chirag
Edited by: Chirag Gohil on Sep 8, 2010 5:03 AM

AS2Receiver:
ModuleName: localejbs/ModuleProcessorExitBean
Type: Local Enterprise Bean
Module Key: Exit
-_Module Parameter_-
Module Key: Exit
Parameter Name: JNDIName
Parameter Value: deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
-_Parameters Tab_-
HTTP
Server - Computer with listening AS2 Server
Port - Port of the endpoint with listening AS2 Server
URL Path - Path to the endpoint with listening AS2 server
HTTP Timeout - Timeout in seconds for waiting for server's response
HTTP Keep Alive - If enabled, the HTTP session is re-used. This optimizes the performance.
Basic Authentication
User - User for basic authentication
Password - Password for basic authentication
Realm - Realm for basic authentication
Proxy
Proxy Server - Your proxy server
Proxy Port - The port of the proxy server
Proxy User - User for optional authentication
Proxy Password - Password for optional authentication
Proxy Protocol - Select either - HTTP 1.0 or -HTTP 1.1
AS2
Compress - Select this option if the payload is to be compressed
Sign - Select this if the payload is to be signed
Signing Algorithm - Select an algorithm which is applied for signing the payload; we recommend "SHA-12"
Encrypt - Select this, if the payload is to be encrypted
Encryption Algorithm - Select an algorithm that is used for encrypting the payload; we recommend "RC2/128" or "3DES"
MDN Mode - SYNC to request a synchronous MDN; ASYNC to request an asynchronous MDN; NONE if no MDN is required
Receipt Delivery Address - Enter the URL of the Asynchronous MDNs that are to be delivered (i.e. the URL of your own AS2 server)
MDN Timeout - Enter a time period (in min), after which an outstanding asynchronous MDN will be interpreted as an error. The value "0" means no timeout
Sign MDN - Select this option, if the MDN is to be signed
Message Subject - This text is sent to the server within the optional HTTP header "subject"
Content Type - The content type should be set. A random content type can be set, but we recommend one of the following
= "application/edifact" for EDIFACT files
= "application/edi-x12" for ANSI X.12 files
= "application/xml" for XML files
= "text/plain" for plain text files
= "application/octet-stream" for arbitrary binary files
Delivery transmission report - A special transmission report is delivered to the report channel

Error in AS2 reciever Communication channel

Hi all,
We are working on Idoc to AS2 scenario using SAP PI 7.1. we have installed the certificates provided by the AS2 partner on the PI system and used them in the Reciever agreement. When trying to test this interface, we are getting the following error in AS2 communication channel:
Message-Verarbeitung fehlgeschlagen. Grund: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ediint.edi.EDIMessageException: EDI message composing failed: signature generation failed: signature generation failed: java.security.NoSuchProviderException: provider BC not found., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ediint.edi.EDIMessageException: EDI message composing failed: signature generation failed: signature generation failed: java.security.NoSuchProviderException: provider BC not found.
Can anyone please help us in resolving this?
Regards
Jagruthi

Hi Jagruti,
I am also looking for the same scenarios with Receiver AS2 adapter on PI 7.1
I have noticed that in my AS2 receiver adaper i am not getting AS2 server details instead the conf is different from previous AS2 adapter.
I am getting below options
channel attribute for RTP
Scurity attribute for RTP etc.
can u pls help me whether anything is missing in deployment why I am not getting other optins.
can u also share any conf doc which u hav
chirag

AS2 common practices and party definitions

Dear reader,
I've a question about AS2 identifiers and common practices as is explained in more detail below:
Context
We have implemented Seeburger AS2 adapter on SAP XI.
In our SAP XI environment we have depict parties in SAP R/3 (customers vendors etc) in SAP XI as well to enable clear depiction of message flows.
For large companies we may find several SAP XI parties because the company may have and an office in Canada and an office in the US. (These are two parties in the SAP R/3 system as well)
The company uses one AS2 server to communicate.
Seeburger AS2 adapter allows one AS2 identifier to be defined for one SAP XI party. It is not possible to define the same AS2 identifier for two SAP XI parties.
Questions
Is it common practice for large company to use one AS2 identifier for all their offices? Can we expect to have several AS2 identifiers, one per office?
If large companies only use one AS2 identifier is it wise to introduce a new SAP XI party specifically for AS2 communications and tigh the AS2 identifier to this party?
Note the questions above only apply to inbound processing. For outbound processing the sender and receiver party (AS2 identifier) can be set using a header map in an receiver agreement.
Your help is appriciated.
Best Regards,
Harald Kastelijn
Message was edited by:
Harald Kastelijn

Harald,
I think that the best way is to create different services for every division under the party (company) with multiple divisions. (Exp. for Party BMW you can have services BMW_DE and BMW_USA). AS2 ID is unique and even for large companies (if they have one IT department) is possible using of the same AS2 ID.
Regards
Naycho

Seeburger AS2 -Message Dumping

Hi All,
We are able to receive and send message from and to third party mail box successfully. But when we enable message dumping for debugging via J2EE Admin for AS2 Adapter we are not able to receive message from the third party mail box.
As per SEEBURGER EDIINT AS2 Adapter for SAP Exchange Infrastructure 3.0 document it is given as follows
"For debugging purposes, it is possible to dump the complete AS2 message or MDN to a directory on the SAP XI Server. The outbound and incoming AS2 messages are stored with complete HTTP headers. This also applies to the outbound and incoming MDNs."
So can anyone provide help to solve the issue.
Regards,
Prakash

Hi Prateek,
If message dumping is enabled then message is not reaching to the AS2 server and third party mail box receiving some error as not able to send message to the partner.
If meesage dumping is disabled then the message is reaching to the AS2 server successfully.
As we need to communicate with two mail box .So message exchange with one mail box is successfull and when second mail box pushes data to our As2 server it is not reaching and the partner is telling that negative MDN is received.
But when we check in the seeburger monitoring message from the second mail box is not shown, as i know that negative MDN is sent in cases like decryption is failed.
For debugging the above case message dumping is enabled and checked with the first mail box but it is also failing as I explained previously.
Seeburger Version is 1.7.1
So can you provide some solution to solve the issue with message dumping.
Regards,
Prakash

As2 Server

Similar Messages

Maybe you are looking for