cancel
Showing results for 
Search instead for 
Did you mean: 

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

Former Member
0 Kudos

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.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

No need to use module

localejbs/Seeburger/solution/as2 solutionid

Former Member
0 Kudos

The solutionid module is required by licence to be placed in the module chain. It does not have any functional impact on your message processing. The module is for volume licence audits.

Former Member
0 Kudos

hi

To call the seeburger standard mapping u hv to use the BIC module in the module configuration.

like :

bic module parameter/mapping name/context (EDI to XML or XML to EDI).

mapping name should for the perticular context.

regards

Manas

Former Member
0 Kudos

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.

Thanks and Regrds,

Chirag

Former Member
0 Kudos

Hi Chirag,

Thanks for the reply.

I know those steps when we use Bic as a Module key.

But here in our project they have installed seeburger AS2 adapter and by default i got "solutionid" as a module key in the module tab like below.

Module Name Module Key

localejbs/Seeburger/solution/as2 solutionid

localejbs/CallSapAdapter 0

Now i got confused

1. whether we can go ahead by using the "Solutionid" as a modulekey (Is it something like Bic advanced version??)

or

2. I need to remove that

Modulename (localejbs/Seeburger/solution/as2) and

Module Key(solutionid)

and add

Modulename (localejbs/CallBicXIRaBean) and

Module Key(bic)

Total confusion which module name and module key we need to use to access the standard mapping for AS2 adapter.

Please let me know if you have an idea abt this.

Thanks

Krupa.

Former Member
0 Kudos

HI,

IN my last project I have used the same module at the receiver end and it worked for me, try to use the same.

Module Name Module Key

localejbs/CallBicXIRaBean bic

localejbs/Seeburger/solution/as2 solutionid

localejbs/CallSapAdapter exit

Module configuration

Modulekey ParameterName ParameterValue

bic= destSourceMsg = MainDocument

bic= destTargetMsg = MainDocument

bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A

Exit=JNDIName=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2

Hope this clears your doubt.

Thnx

Chirag

Reward points if it helps

Former Member
0 Kudos

Hi Chirag,

Thanks for the reply.

I will try the for the same and let you know. Still we didnt get the connection for testing.

Regards

Krupakar.