Message subject in seeburger sender AS2 adapter

Hi Experts,
I read few fourms regarding message subject in seeburger and in those below forum is related to my problem
AS2 Sender adapter.. How we can receive 2 messages from same partner??
like how we can identify different message types when we receive from partner
A) using AS2 ID and message subject
If we give message subject as * it will receive all the message but how to identify them as our partner is not providing message
subject.
I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter

Hi,
> Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter
When message comes to PI, initially it goes to seeburger workbench, here based on the EDI type (ANSI X12 or EDIFACT or...), EDI Version (4010 or 4020 or...) and Signal (850 or 810 or ....) it determines the respective mapping (E2X or X2E) program, this is done by Classifier.
When we are sending outbound scenarios and using MDN option then message subject plays an important role. Once we send the outbound signal we can get the ack(997) signal, based on AS2ID and message subject it identifies the respective 997 inbouns scenario.
> I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Seeburger is used if you are handling the EDI data but here you are using XCBL so you no need to use the seeburger adapters.
Regards,
Venkata Ramesh

Similar Messages

Seeburger Sender AS2 adapter

We have a customer who purchased Seeburger AS2 Adapter. They have WAN setup with Inovis which is having AS2. Now we are in the process of setting up the AS2 using seeburger for them. if we use Seeburger AS2 adapter, then trading partners have to send their documents to the following path
http://<Server Name> :50000/SeeburgerAS2/AS2Server
Seeburger AS2 adapter will receive the documents posted to the above URL & Process them using XI
The problem we are facing is the Sender Seeburger AS2 adapter doesnt have a mechanism to Poll the Inovis AS2 Mailbox and receive the documents.
Does any one have a solution to Poll & fetch the documents from Inovis AS2 mailbox.
With Regards
K.Varadharajan

HI,
The message which are coming to XI will be picked up based on two things:
1) AS2 ID of the partner which is dicussed above and the second one is
2) Message subject :
Message Subject
This subject will be compared with the subject in the received message. This is used to find the correct channel for the inbound message. Wildcards are allowed.
There is a defined order in which the matching inbound channel is looked up. First the adapter looks for a sender channel with a message subject configured.
If there is one channel with a matching subject configured, the channel is used for forwarding the received payload to the XI system.
If there is no channel configured with an matching subject the received payload is rejected.
If there is one channel configured with a matching subject and another channel with a wildcard both channels will match. In this case the received payload is forwarded to the channel without wildcard configured.
If there is more than one channel configured with a matching subject, the payload is rejected.
I hopw it has answered ur question.
Thanks and regards,
Chirag
Reward points for helpful answers.

Error in Sender AS2 adapter

Hi Expert,
I have configured sender AS2 adapter as per the sap guide. and share our url and AS2 name.Now when the partner is trying to send the file from their side they are gettting the following error message and in SAP PO we have not received any file via AS2 sender adapter.
We have checked the fire walls and its working fine.
2014.04.09
01:15:03:128 0326030999 PHDR OK HTTP Response-Line = (HTTP/1.1 302 Found)
2014.04.09 01:15:03:128
0326030999 PHDR ERR Trading Partner rejected the transaction
2014.04.09 01:15:03:128 0326030999 HPOS ERR Requested synchronous receipt not
returned
2014.04.09 01:15:03:128 0326030999 HPOS ERR One or more errors occurred with
this transaction. m_nErr=(2103)
Regards
Kasturika

Hi Harish,
I have change the as2 url from http://<host>:<port>/AS2 to http://<host>:<port>/AS2/B2B and now are partner is facing differnt error
2014.04.22
03:06:04:400 0637647174 PHDR OK HTTP Response-Line = (HTTP/1.1 401
Unauthorized)
2014.04.22 03:06:04:400 0637647174 PHDR ERR Trading
Partner rejected the transaction
I had checked with my partner to use the http authentication and share our user id and password. but they said that they are not using http authentication.
we also shared our public key certificate and import theirs in our nwa- certificates and keys .
Please share if anything more i need to configure.

Seeburger - XI AS2 Adapter Sender service configuration

Hi,
I need to know how to configure the seeburger AS2 adapter sender service in XI ( EDI -
> IDOC).
I have some pre-requisites that are needed to setup.
1. SSL certificate
2. AS2 Certificate (public key)
Kindly anyone provide me the guidance or if any docs/pdf's. your help is appreciated.
Thanks,
lakshmi

Refer these
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Thanks

Sender AS2 Adapter Setup

Hi,
I am trying to send an EDIFACT file to IDOC through AS2 Adapter (sender). Can you please tell me how to configure the sender AS2 Channel.I have configured it, but it is giving me the following error in Channel Monitoring.
Alert: Maximum number of retries reached. Retry 20. Message initiation failed: Adapter call failed. Reason: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order;, failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order; [4/30/09 4:19 PM]
Please share your valuable inputs.
Thanks,
Amit..

Hi,
follow the below steps;
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
-S

Sender AS2 adapter settings for Asynchronous MDN

Hello,
I need to configure the settings for AS2 sender adapter for Asynchronous MDN.
In order to configure the asynchrounous MDN Settings which parametrs i need to fill in the channel from below
1) Use Proxy
2) Proxy Server
3) Proxy Port
4) Proxy User
5) Proxy Password
6) Proxy Realm
7) Proxy Protocol
8) Server Certificate (Keystore)
9) Private Key for Client Authentication
Thanks
Srinivas

Hi,
The MDN asynchronous mode is for the AS2 receiver adapter and not sender.
If you want to use a proxy server, then only you would need to provide the details that you have mentioned and if you are using encryption, you would need to provide the encryption certificate in the corresponding receiver agreement where the comm channel is used.
Also, for asynchronous MDN, you would need to configure a report channel (AS2 sender adapter with message protocol reports) and sender agreement. You need this even if Refer to XI system option is disabled in the AS2 receiver adapter.
Regards

Duplicate message handling in the sender file adapter

Hi,
I enabled duplicate file handling check in the sender file adapter so that whenever there is a duplicate file it should send me an alert also it should disable the channel so that i do not get that duplicate file alert message again and again.
My question is will it activate the channel again as soon as a new file arrives or do i need to manually do that.
Michal's PI tips: Duplicate handling in file adapter - 7.31

Hi Hema,
You will have to activate the channel manually. The idea behind the 'disable' functionality is to avoid further file processing through that channel which can only start once the channel is activated again manually.
Regards,
Abhishek

SOAP message size limitation for sender soap adapter

Hi All,
We are facing critical production issue in case of sender SOAP Adapter,
If the sender soap message is having 114359 Bytes than the Third party is getting exception and SOAP request is not reaching XI.
If the message size is less then 100kbytes then no exception will come.
Is this a limitation that SOAP message size should not exceed 100kbyte?
Thnaks in advance
Best Regards,
Harleen Kaur Chadha

Hi ,
Thanks for your inputs,Could you please tell me which hardware configurations are you talking about?
Are you people talking about harware configurations for XI?
Best Regards,
Harleen Kaur Chadha

Connectivity from Customer to sender AS2 adapter

Hi Guys,
My scenario is EDI to File, to send the data we provided our HTTP IP, port and URL to customer, here URL is https://<host_name>:<port> by using this URL we are able to receive the message upto our network, so how to get that data from network to PI System?
Any other thing we need to add to the URL path like https://<host_name>:<port>/AS2 ID or ..... ?
If yes how exactly we know we need to add AS2 or EDI or ......
Please advice me.
Thanks
Ramesh

Hi Sanju,
If we are getting the 405 error means it is success (In one of Seeburger documentation they mentioned).
My scenario is EDI to file, next file to FCC at the same time send 997 to sender, who sends the actual data.
I am able to get the message to my network (ports are open, firewall allows the data), but not getting to PI or Seeburger system.
Any one please suggest me the possible ways to trouble shoot that error.
Thanks
Ramesh

Sender AS2 adapter

Hello All,
i am doing scenario where edi document from external party goes into sap system as an idoc (i.e. edi to idoc scenario).
i done all configuration party. when i am testing my interface through configuration test it is working successfully. but it is failing in sxmb_moni saying "No receiver could be determined".
Eventhough i create proper recevier determination and recevier agreement.
could you please answer my question.

Hi,
there are many possibilities for the receiver determination error.
1) Configuration mistake
Receiver determination depends upon:
a) Sender business system
b) Sender Interface
c) namespcae under which sender interface is configured in ESR
Check for the values in MONI and compare them with the config (Receiver determination) in ID.
The above values should match in MONI and ID.
So please check each and everything.
2) Cache refresh (please check cache notifications in ID)
3) When the business system not found in SLD.

Seeburger AS2 Adapter: Receiving multiple messages

Hi guys,
I'm having some trouble using AS2 Adapter for receiving multiple messages. The problem is really similar to Peter's problem.
Seebuger AS2 adapter for XI as sender for multiple messages
I have it configured for one scenario and it's working fine. The problem is when I'm trying to receive other messages for the same Party but different services. Meaning, I've one Party(example BMW) and several services (BMW_DE, BMW_USA, etc). I'm able to receive messages from service BMW_DE but when configuring BMW_USA I'm getting HTTP 403 Forbidden.
This error may have different reasons:
a) You or your partner has entered an incorrect AS2 ID for one of the involved parties.
b) A valid sender agreement is missing.
c) There are more then one AS2 sender agreements with the same sender AND receiver party.
d) The corresponding inbound channel is set to inactive.
And the problem is that there are two sender agreements. Although the services are different, XI is not able to find the correct sender agreement to be used. After deleting the second second agreement, I'm able to send the respective message....
Can anyone give me a hint on how to solve this problem?

Hi,
this is done by different AS2 subjects. The sender agreement is selected based on this. So create separate AS2 receiver adapters for every message you need and put there different message subjects.
So if you'll have 3 AS2 receiver channels with subjects:
MessageType1_DE
MessageType1_US
the AS2 adapter will work like following:
first it tries to find an exact message subject, if it is found, message is "assigned" to this sender agreement. If no exact message matches the subject, then wildcards are used. (this mechanism is described in the Seeburger AS2 guide).
If you are getting 403 HTTP code, there may be also problem with authentication certificates.
Another problem may be, you don't have configured AS2 receiver channel for current subject.
Does this help you? Or you meant it another way?
Peter
p.s. check the answer above my post, Vardharajan's right
Edited by: Peter Jarunek on May 19, 2008 2:11 PM

Dynamically selection of Message Subject in AS2 adapter. Urgent Help..!!

Hi All,
I need to send the message to partner by using AS2 adapter.
And i need to keep the Message Subject by taking dynamically from the payload message.
ie. Iam sending the Purchase Order to Partner and i need to pass OrderNO which is coming in one field of my strcture to the message subject.
How i can select dynamically the Orderno and pass into message subject of AS2 Receiver adapter??
In the Seeburger AS2adpter manual, they provide the answer by using module parameters like
http://seeburger.com/xi/common/dtsubject   DYNSUBJECT
But i don't know how to put particular field into it.
Any idea abt this?
Regards
Deepthi.

Hi Deepthi,
I think this would help you in configuring Dynamically selection of Message Subject.
Supported dynamic attributes are:
dtSubject if the subject parameter is set in the XI message and the AS2 receiver channel is
      configured to use all non-empty or subject attribute, it will be treated as the message subject
      by the AS2 adapter;
dtAS2FileName the name of the payload. This is an attribute of the Content-Disposition
      header. With this AS2 is compatible with AS2 Filename Preservation draft.
dtAS2ContentType for Example application/xml, depending on the payload type
To enable the usage of Dynamic Attributes, there is a special dedicated section in receiver channel.
Dynamic attributes are used if the Use dynamic attributes setting is checked in the receiver channel.
If the the setting Use non-empty attributes is not selected, all known attributes are used for
configuration if the attribute is present.
Mention Check boxes for these
          Use dynamic Attributes
          Subject
Dynamically set attributes override static channel attributes. Example: the subject attrib
in receiver channels overrides the channel attribute.
Here is an example how to set them. Channel tab Module->Module Configuration:
Module Key: 1
Parameter Name: http://seeburger.com/xi/common/dtsubject
Parameter Value: DYNSUBJECT
Message Subject: This subject will be compared with the subject in the received message. This is used to find the correct channel for the inbound message.
Wildcards are allowed.
Regards,
Varun Reddy.K

Seebuger AS2 adapter for XI as sender for multiple messages

Hi all,
Has anyone managed to configure the Seeburger AS2 adapter for XI successfully to process multiple inbound message types.
We have an issue here with inbound messages being received by the AS2 adapter. We currently have it configured for inbound deliveries which is working fine. The issue is that we would now like to send other messages as well. It seems the AS2 adapter only looks at the sender/receiver party combination to determine the correct sender agreement, but does not look at the message type which is a limitation. I have heard mention of a splitter module which can be used to distinguish between different messages and pass them to the correct sender agreement for processing, information on this is thin on the ground to non existent. What is the name of the module? Is it specified in your sender AS2 adapter with parameters? Is it wrapped as an adapter? How do you configure the module to split and pass specific messages etc... Any help on this would be much appreciated.
Thx,
Pete

Hi Rudy,
the Classifier/BIC/Splitter - Solution is mainly designed for EDI-Messages that cannot be handled directly by XI.
IF you use pure XML-messages you should be able to handle it with XI-basic-functionality since this is what XI can handle itself.
Depending on how different your XML-Messages are, the effort will be very small or a little bit bigger.
In the ReceiverDetermination it should be possible for you to check whether certain XML-TAGs are existing or what the content for certain TAGs is BAsed on this information you can route the messages in a correct way.
(Of course you might have to create your own XSD for this containing the important TAGs of each message, so you can setup your Conditions)
Btw. the Seeburger BIC-Adapter can provide also this functionality, but this also needs to be customized)
Greetings
Stefan

How to deal Inhouse files using Seeburger AS2 adapter...!!!

Hi all,
Has anyone managed to configure the Seeburger AS2 adapter for XI successfully to process multiple inbound message types.
We have an issue here with inbound messages being received by the AS2 adapter. We currently have it configured for inbound deliveries(Which deals with EDI files) which is working fine. The issue is that we would now like to send other messages as well. It seems the AS2 adapter only looks at the sender/receiver party combination to determine the correct sender agreement, but does not look at the message type which is a limitation. I have heard mention of a splitter module which can be used to distinguish between different messages and pass them to the correct sender agreement for processing, information on this is thin on the ground to non existent.
I have few custom Inhouse files where i need to recieve through AS2 adapter.
I need to differentiate the messages hitting to my communication channel.
ex:
1st message will be having
HDR PICKS
2nd message will be having
HDR PURCH
so based on the second field which has "PICKS" or "PURCH" , i need to pass the message to run the corresponding map.
How i need to configure to acheive these kind of custom Inhouse files through AS2 adapter??
Do i need to use splitter for these as well?? If yes how i need to use?
Is there any setting we can make at Sender AS2 adapter to differentiate each message??
Waiting for the answers.
Kindly reply if anyone knows.
Thanks&Regards
Seema.

Hi,
i have setup a scenario with edifact (different message types) using as2.
first i had to create a mapping using bic.
edifact_xxxx
in: edifact_service
out: functional acknowledgement.
in the mapping code i adjusted the called mapping, standard it will use see* changed it to e2x* (custom mapping)
in your case using flatfiles maybe you should take a look at the VDA structure, these files are also defined under inhouse.
when you define a input file adapter are you getting a classifier message?
like
<classifier><type>Edifact</type><classifierMappingID>XXXX</classifierMappingID><encoding>US-ASCII</encoding><additionalIdentifier></additionalIdentifier></classifier>

AS2 adapter-- Module tab configuration to call seeburger std mappings..!

Hi Experts,
Seeburger has been installed and i want to use AS2 adapter to make use the seeburger standard mappings.
When i opened the module tab, its been found that for
Sender AS2 adapter:
Module Name                                     Module Key
localejbs/Seeburger/solution/as2             solutionid
localejbs/CallSapAdapter                         exit
Module configuration
_Modulekey      ParameterName               ParameterValue_
Solutionid           Mappingname               SEE_ORDERS_UN_...
can i use the above steps??
Is solutionid is enough to call the seeburger mapping?
or
do i need to use the Bic module to call the seeburger std mapping like below?
Module Name                                    Module Key
localjbs/CallBicXIRaBean                         bic
Module configuration
Modulekey     ParameterName               Parameter Value
Bic               Mappingname              SEE_ORDERS_UN_...
Kindly let me know.
Regards
Krupa.

HI,
For module configuration for As2 refer the below help.
Sender configuration:
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
Refer the below thread which has the same discussion.
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Thanks and Regrds,
Chirag

Message subject in seeburger sender AS2 adapter

Similar Messages

Maybe you are looking for