cancel
Showing results for 
Search instead for 
Did you mean: 

3rd party adapter integration into XI

former_member185881
Active Participant
0 Kudos

Dear Experts

I wanted to know how 3rd party adapters are integrated into XI?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Dheeraj,

The 3rd party adapters must be installed via Deploy Tool or JSPM. But u should have a sda file with the adpater content.

see here for more details on JSPM

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5006901f-925c-2910-5f98-9ae26cc0...

Thanqs

Biplab

Former Member
0 Kudos

Hi Dheer,

There many third party adapters available in market.

One example is seeburger:

U need to follow the below steps for integration into XI:

For the same requirement you need to follow the below steps:

1) First deploye the Std seeburger mapping provided by see burger on XI

2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.

3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.

5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.

if u need process then let me know I will send u the configuration threads which is required for integration.

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

Brief about seeburger:

Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.

The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.

Supported EDI formats include:

• ANSI

• EDIFACT

• INHOUSE

• IDOC

• XML Schema

• XML DTD

• CSV

• Delimited Data

• positional data

• SWIFT

• EANCOM

and many more.

See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.

refer belwo weblog:

/people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules

Thnx

Chirag

Edited by: Chirag Gohil on Feb 25, 2008 12:51 PM

Answers (4)

Answers (4)

Former Member
0 Kudos

First integate that third party server on XI server and do some configurations.

But installing the third party adapter is BASIS role, after install we should do some configuration steps.

Former Member
0 Kudos

Within the framework of the NetWeaver technology, SAP® offers the option of integrating external or third-party systems simply and efficiently into the business processes of a system through the SAP® XI Exchange Infrastructure 3.0 (XI). To do this, SAP's® XI Adapter Framework provides a standardized interface making it possible for third-party suppliers to integrate existing applications and data resources into the SAP® world through so-called XI adapters. The conformity of an adapter with the SAP® standard can be ensured by certification by SAP®. This guarantees for the customer that XI adapter implemented by a third-party supplier can still be operated in the SAP® environment with no problems.

Consist Software Solutions offers in cooperation with Mummert Consulting AG an SAP® XI adapter for the integration of third-party systems using the Attunity Connect product family. The certification of this adapter by SAP® for the Adabas C database had taken place in August 2005.

SAP® XI Adapter Framework

The SAP® XI Adapter Framework is based on the Java/J2EE Connector Architecture (JCA) developed by Sun Microsystems. This was extended by SAP® on the one hand with the requirements of a message-based data exchange, and on the other with the specifics of the SAP® XI technology. Basically, the following two integration scenarios are supported:

Outbound

synchronous or asynchronous access from SAP® XI to external systems

Inbound

The external system independently sends data/messages to SAP® XI

Moreover, there are different levels of "quality of service" defined for data exchange (e.g. "BestEffort"). The options for support of the different processing scenarios by an adapter are primarily determined by the functionality of the target system to be integrated. For example, not all systems are capable in themselves of actively generating notifications.

Besides pure data exchange functionality of an adapter, the SAP® XI Adapter Framework defines a series of requirements that an adapter must fulfill for smooth operation and support by SAP®. These are primarily:

a standardized installation using SAP® SDA archive files

configuration through the central SAP® System Landscape Directory (SLD)

integration into the administration and monitoring tools of SAP® XI (logging, adapter monitoring, start and stop, and so on).

SAP® XI Attunity Connect Adapter by Consist Software Solutions

The SAP® XI Attunity Connect Adapter provides the following basic functionalities for the integration of Attunity Connect-based products:

Integration scenario: Outbound BestEffort

Configuration, logging, and monitoring

Certification for the Adabas C target system

Former Member
0 Kudos

Hi Dheeraj,

The 3rd party adapters must be installed via Deploy Tool or JSPM. But u should have a sda file with the adpater content,In addition to that you will need partner connectivity kit as well,

The following stages are involved in using XML for the interchange of commercial EDI messages:

identification of suitable data sets for electronic business transactions

development of XML document type definitions (DTDs) that formally define the relationships of the fields that are to form a particular class of EDI messages

the definition of application-specific extensions to standard message types

the creation of instances of specific types of electronic business message

the validation of the contents of messages

the transmission and receipt of electronic business messages

the processing of electronic business messages using DataBots.

http://www.eccnet.com/xmledi/guidelines-styled.xmlThank you

priyank

Former Member
0 Kudos

First integate that third party server on XI server and do some configurations.

But installing the third party adapter is BASIS role, after install we should do some configuration steps.