Seeburger OFTP_ISDN Adapter

[mf_haq]

Hi Folks,

Recently we configured Seeburger OFTP_ISDN Adapter and performed post installation steps as below.

1. Imported SEEBURGER_EDI_ADAPTER 7.1 of seeburger files to SLD

2. SWCV imported to ESR, created name space and created OFTP_ISDN adapter metadata's

3. In ID created party and Comm Channles.

A. In Party configuration "Agency - 'ODETTE', Scheme - OFTP and Name - 00013SUPPLIER details also not visible to add in PARTY.

B. We are following Seebuger 'master guide'. While creating sender or receiver comm.channels, selecting SEEBURGER_EDI_ADAPTER 7.1 of seeburger SWCV in this case transport&message protocols are showing only STP 1.0 & SMP 2.0 where it has to show..transport protocol - ISDN, Message protocol - OFTP

Note: Suppose if am using SWCV as SEEBURGER_ADAPTER of seeburger (version 3.0) then am getting correct

transport protocol - ISDN, Message protocol - OFTP

Please suggest on this why we are not getting transport protocol - ISDN, Message protocol - OFTP or any additional settings/config needs to do.

Regards,

MFH

[S0003485845]

Hello,

regarding question A:

This is standard PI functionality. You just have to include an additional identifier and then insert the mentioned parameters

Agency : ODETTE

Scheme: OFTP

Name:   "whatever SFID-Code this Party will be using"

regarding question B:

This sounds like the adapter-metadata is not imported correct, meaning either the name or the namespace does not fit (in the Repository setup).

Or you have imported a wrong metadata-file.

Can you explain the steps that you have made in the repository to have the metadata included ?

Best Regards

[mf_haq]

Hi,

Thanks for your reply.

Question A:

This is standard PI functionality. You just have to include an additional identifier and then insert the mentioned parameters

Where will have additional identifer & How to add AGENCY&SCHEME for that???

Question B: I agree with you. more chances is related to

Ans for your question:

1. Imported SLD_SWCV_EDI_ADAPTERS_7.1 ZIP file in to SLD and add the same to Product: SEEBURGER_EDI_SOLUTION

2. Imported SXCV in to ESR

3. Created Name space: http://seeburger.com/xi

4. created Adapter meta data and selected above SWCV that we imported in to SLD (SLD_SWCV_EDI_ADAPTERS_7.1 ) these are steps we performed in ESR.

Then try to create PARTY and channles but we are getting different protocols

like Transport protocol - STP 1.0 ; Message protocol - SMP 2.0

Expectation: This problem is related to only SWCV that v imported in SLD. Please reply if any other thoughts and alternative/Ideas.

Regards,

MFH

[mf_haq]

Hi,

Communication channels configuration: does we have this details in master guide. or from where i will get channel connection parameters. Any idea.

Thanks