cancel
Showing results for 
Search instead for 
Did you mean: 

Error in AS2 adapter. Object not found in lookup of as2.. Its urgent..!!

Former Member
0 Kudos

Hi AS2 experts,

*When i tried sending an xml to partner system using AS2 adapter.. Mapping is succesfull and message is failing in receiver AS2 adapter.

1. I used the following parameters in AS2 Module.

ModuleName Module Key

localejbs/Seeburger/solution/as2 solutionid

localejbs/ModuleProcessorExitBean exit

ModuleKey ParameterName ParameterValue

exit JNDIName deployedAdapters/SeeXIAS2/shareable/SeeXIAS2

Iam getting the following error.

Success MP: Processing local module localejbs/Seeburger/solution/as2

Error : MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2.

Error : Exception caught by adapter framework: Object not found in lookup of as2.

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: Object not found in lookup of as2.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2..

2. When i tried by removing Modulename "localejbs/Seeburger/solution/as2"

It is showing the below error like AS2ID is missing.. but its there in party configuration.

Error :

Unable to forward message to JCA adapter. Reason: 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..

Can anyone has idea what might be wrong.

Kindly suggest me asap.

Thank You.

Regards

Seema.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

AS2ID is mandatory for both sender and receiver side.

So i provide the Partys names in Header Mapping for both sender and reciver partners.Although i used business system(without party) for my R/3 system.

Only Party name i used in Header mapping .. I haven't used anywhere in my confuguration.

Thanks everyone.

-Seema.

Former Member
0 Kudos

Hi,

Plesae go through below links

/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact

EDI Adapter by SeeBurger

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d13916...

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-aff3bbf7...

Integrating XI with SeeBurger

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e...

and

Check with below configuration

Configuration for AS2 or simple file adapter.

We are using this module configuration for converting EDI D96A format to XML:

1 localejbs/CallBicXIRaBean Local Enterprise Bean bic

2 localejbs/CallSapAdapter Local Enterprise Bean 0

bic destSourceMsg MainDocument

bic destTargetMsg MainDocument

bic logAttID ConverterLog

bic mappingName See_E2X_ORDERS_UN_D96A

bic saveSourceMsg ORIGINAL_EDI

can someone please tell me the module configuration for reverse mapping at receiver end,i.e.,XML to EDI D96A

basically,I need mapping name for this.

Scheme=AS2ID

Name = WAN network no of the partner who is sending the file

Sender AS2 adapter configuration:

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 which does the conversion of EDI-XML.

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

File receiver:

localejbs/CallBicXIRaBean bic

CallSapAdapter 0

Module configuration:

bic= destSourceMsg = MainDocument

bic= destTargetMsg = MainDocument

bic= mappingName= See_X2E_EDIFACT_ORDERS_UN_D93A

ONly the mapping program name changes from E2X to X2E. IN ur case it will be See_X2E_ORDERS_UN_D96A

Thanks

Swarup

Former Member
0 Kudos

Hi Seema,

Have u used the AS2ID at the reciever channel. Have u used the mapping name in module so that it will covnver the XML to EDI format.

use the same mapping configuration which u have done in sender side.

thnx

chirag

Former Member
0 Kudos

Hi Chirag,

Thanks for your reply.

>> Have u used the AS2ID at the reciever channel

I used the AS2ID in Party configuration.

Do you think we need to use in AS2ID in receiver channel??where we need to use??

>> Have u used the mapping name in module so that it will covnver the XML to EDI format.

Iam not doing any conversions here.Just iam passing a sample xml which will come out of my mapping.

I need to pass the file to partner system.thats it.

Pls help me.. its very urgent.

-Seema.

Former Member
0 Kudos

Hi,

Have u done the below configuration in party idnetifier tab.

Scheme=AS2ID

Name = WAN network no of the partner who is sending the file

Can u check the message monitoring in RWB component monitoring or in the RWB of seeburger which is similar to RWB. Also check the receiver communication channel status.

Thnx

Chirag

Former Member
0 Kudos

>> Have u done the below configuration in party idnetifier tab.

>> Scheme=AS2ID

>> Name = WAN network no of the partner who is sending the file

Yes i gave those details.

>> Also check the receiver communication channel status.

See my first message.. i mentioned the error clearly.

>> RWB of seeburger which is similar to RWB.

Nothing is showing here.. i think still the message is strucked in AS2 adapter.. still it hasn't gone out.

-Seema.

Former Member
0 Kudos

Hi seema,

Ur all other AS2 to IDOC scenarios are working correctly? or u r facing the problem with outbound AS2 case only.

I think the configuration is proper. Can u check the sender agreement whether u have given the sender and receiver party name.

Thnx

Chirag

Former Member
0 Kudos

Hi,

>> Ur all other AS2 to IDOC scenarios are working correctly? or u r facing the problem with outbound AS2 case only.

This is the first scenario iam working on AS2.So trying with outbound scenario (Idoc to File).

>> I think the configuration is proper. Can u check the sender agreement whether u have given the sender and receiver party name.

Yes.. configuration is correct.

No need of sender agreement here since it is a Idoc to File scenario.

Anything to do with Modulename "localejbs/Seeburger/solution/as2" and Moule Key "Solutionid"

I need to provide any parametername and parameter value for "solution id"

I dunno whats happening....

-Seema.

Former Member
0 Kudos

Hi,

I dont remenber what configuration i have used in receiver AS2 adapter i need to refer the docs may be then only i can give u the answers.

Thnx

Chirag

Former Member
0 Kudos

Hi Chirag,

Can you reply by today.. Its urgent for me.

If possible .. will you pls send the documents to reddy.seema@gmail.com for both outbound and inbound scenario.

Pls... will be waiting for your documents.

Thank You.

Seema.

Former Member
0 Kudos

Any more answers...

Waiting for the reply.

-Seema.

Former Member
0 Kudos

Hi Seema,

Hoping this might help you:

Processing Sequence

1 localejbs/CallBicXIRaBean - Local Enterprise Bean - bic

2 localejbs/Seeburger/solution/as2 - Local Enterprise Bean - solutionid

3 localejbs/ModuleProcessorExitBean - Local Enterprise Bean - exit

Module Configuration

bic destSourceMsg MainDocument

bic destTargetMsg MainDocument

bic mappingName See_X2E_ANSIX12_850_V4010 (for instance)

exit JNDIName deployedAdapters/SeeXIAS2/shareable/SeeXIAS2

Regards,

Lex