Adapter framework

[Former Member]

Hello Experts,

Can you please provide me good understanding of the following:

1. What is AdapterFramework? why do we need it?

2. what is Transport Protocol and Message protocol in Adapter CC parameters?

3.In what format does the message come from Sending system to XI and what happens after it reaches XI?

4. Please can you let me know as what is Full life cycle project and Implementation project?

Thakyou in advance and regards,

Aaron.

[Former Member]

Hi chinnu raj ,

>>1. What is AdapterFramework? why do we need it?

What are XI Adapters?

Adapters enable communication between the XI integration engine and an application system. This leads to the compatibility

between heterogeneous systems.Adapters convert the XI protocol (SOAP with attachments over HTTP) to the protocol spoken by the

application system and vice-versa.The key purpose of XI is to integrate heterogeneous systems and adapters are the key enabler

to achieving this goal

Adapter Categories

Application adapters provided by SAP (IDoc and RFC) and 3rd party vendors (Seeburger, Siebel, Oracle, ...)

Technical adapters relate to specific protocols

File systems (FTP / File)

RDBMS systems (JDBC)

Messaging systems (JMS)

Web services (SOAP)

Mail servers (SMTP)

SAP Business Connector

Marketplaces

Industry standard adapters

RosettaNet

CIDX

SAP XI requires an adapter framework to communicate outside of the SAP system. These adapters translate code from external applications to an XML message for NetWeaver processes using the Java Connector Architecture.It is a part of the Adapter Engine, which provides interfaces for configuring, managing, and monitoring adapters.

Structure of the Adapter Framework

http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/content.htm

Adapter for SAP XI environment

http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/d...

>> 2. what is Transport Protocol and Message protocol in Adapter CC parameters?

Transport Protocol and Message protocol gain improtance when we send or recieve e-mails thru MAIL ADAPTER.

Check the following website which gives all details :

http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm

>>3.In what format does the message come from Sending system to XI and what happens after it reaches XI?

This completly depends on source system. Suppose the source system is R/3, message comes in IDOC format & by using IDoc Adapter in sending system it is converted to XML format & this XML format is sent to XI

SO THE FINAL FORMAT WHICH THE XI RECIEVES IS ONLY XML.

If sender system sends file message comes in .TXT format & by using FILE Adapter, we convert this into XML format & send it to XI.

>>4. Please can you let me know as what is Full life cycle project and Implementation project?

Full life cycle project : means starting from developing blue-print at customer side to GO-LIVE stage & after GO-LIVE also we do data transfer operations everything.

Implementation project : means from scratch we develop the object & our goal is only GO-LIVE . we r not bothered after this.

cheers!

gyanaraj

****Pls reward points if u find this helpful

[Former Member]

Hi chinnu,

1. What is AdapterFramework? why do we need it?

The Adapter Framework is the basis of the Adapter Engine. The Adapter Framework is based on the SAP J2EE Engine and the J2EE Connector Architecture (JCA). The Adapter Framework provides interfaces for configuration, management, and monitoring of adapters.

The Adapter Framework has its own queuing and logging services. This means that you can run the Adapter Engine temporarily without a connection to the Integration Server.

see these links

http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/content.htm

2. what is Transport Protocol and Message protocol in Adapter CC parameters?

transport protocol is common to all adapters..

HTTP/HTTPS

Message protocol is diffrent...for different adapters....

3.In what format does the message come from Sending system to XI and what happens after it reaches XI?

Adapter engine converts any message to XML message and vice versa.....

so when a message comes to XI from sender system... no matter what format it is..AE convert it to XML format.....(since XI can understand only XML messages)...similerly..wen message is coming out from XI.. AE converts it to the format RCVR system wants..

4. Please can you let me know as what is Full life cycle project and Implementation project?

blueprint

design

development

testing

deployment

search on sdn .. u will find more details....

Regards

Biplab

[Former Member]

Hi,

Adapter Framework

The Adapter Framework is part of the Adapter Engine and the PCK. It provides interfaces for configuring, managing, and monitoring adapters. The Adapter Framework is used to connect any external system to SAP Exchange Infrastructure.

The Adapter Framework is based on the SAP J2EE Engine and the J2EE Connector Architecture (JCA).

Adapter Framework is based on SAP J2EE Engine as part of SAP

Web AS

�� Adapter Framework inherits properties and features such as

scalability, clustering, high availability, thread management, etc.

Adapter Framework provides its own queuing and logging services

�� Temporary stand-alone operation without connection to an

Integration Server is possible, while still providing e. g. guaranteed

exactly once messaging to and from connected application system

The Adapter Framework is responsible for communication between the SAP XI Integration Server and any SAP or non-SAP systems.

The Adapter Framework communicates using JCA 1.0 connections (2) and the JCA 1.0 Common Client Interface (CCI) with an adapter. The JCA 1.0 container of the SAP J2EE server uses the JCA 1.0 Service Programming Interface (SPI) to exchange server-relevant information with the adapter according to JCA 1.0 (1). Therefore, the adapter must be a JCA 1.0-compliant resource adapter. Since JCA 1.0 does not define the communication direction from the adapter to the Adapter Framework (application in the JCA sense), the Adapter Framework is called from the adapter with a standard Enterprise JavaBean 2.0 session bean.

A message from the Integration Server is received in the Adapter Framework by the messaging service. Based on the receiver information, the corresponding module chain is selected in the module processor for further processing.

The Adapter Framework contains two default module chains: one for the sender/inbound direction and one for the receiver/outbound direction. You can use these default module chains for your adapter if the entire message processing is executed within the adapter. You can enhance the default module chains with customer-specific modules. The module processor controls the steps in the module chain by calling generic and, if defined, adapter-specific modules (3). The last module in the module chain forwards the message to the adapter using JCA CCI (2). The adapter transfers the message to the connected system.

Transport Protocol and Message protocol in Adapter CC parameters

Transport Protocol

This parameter defines the transport protocol for processing the message.

Message Protocol

This parameter defines the message protocol for processing the message.

The transport protocol (TransportProtocol) and message protocol (MessageProtocol) elements can contain a range of referenced Attributes or AttributeTables. Both have the same structure

http://help.sap.com/saphelp_nw04/helpdata/en/79/e462405c910272e10000000a155106/frameset.htm

In what format does the message come from Sending system to XI and what happens after it reaches XI

The Adapter Framework controls the exchange of synchronous and asynchronous XI messages and communicates with the Integration Server to do this. The adapters in the Adapter Framework convert XI messages to the protocols of connected external systems and the other way around.

If your adapter provides a mechanism to create WSDL, XSD, or DTD files to create message metadata.

The loading of example XML documents is supported but should be avoided, as it does not describe all document variants.

You use the Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and external systems. You use the various adapters in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.

Please go through below link

SAP NW 7.0 Process Integration - Adapter Framework & Adapter Strategy

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40faf9ae-1ce5-2910-f89c-f187628e...

SAP NetWeaver End-to-End Process Integration: Adapter Framework

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0ee90b6-e726-2a10-528b-bd493ab5...

Development of Adapters for the SAP XI Adapter Framework

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7bf6e190-0201-0010-83b7-cc557eb7...

Structure of the Adapter Framework

http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/frameset.htm

Adapter Framework Module Interfaces (SAP Library - Partner Connectivity Kit)

http://help.sap.com/saphelp_nw04/helpdata/en/32/43d84072378031e10000000a1550b0/frameset.htm

Full life cycle project and Implementation project

End-to-End Process Integration: New Features with SAP NetWeaver 2004s Relevant for SAP Exchange Infrastructure Customers

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0f251f4-bd11-2a10-b4b8-9c394f89...

The ASAP Implementation Roadmap for Exchange Infrastructure provides guidance for the implementation teams embarking on implementation project of SAP XI Solution. The roadmap covers methodological process, content and technical aspects of an SAP Exchange Infrastructure implementation project. The deliverable based roadmap makes it easy for the project team to identify key deliverables, related outputs and enables project manager to run projects more efficiently. Note: This roadmap is a subset of the ASAP Implementation Roadmap and covers steps specific for XI implementation. If your project includes other SAP Solutions we recommend to use the full ASAP Implementation Roadmap.

See in SDLC, we need to follow the below steps,

1. Project Preparation

2. Business Blueprint

3. Realization

4. Final Preparation

5. Go-Live and Support

Here 1. Project Preparation and 2. Business Blueprint are the key responsible for Architect and Team Leads.Here they prepares the complete technical documentationsfor all the interfaces depending upon the requirements of the client.

In realizaiton he will develop all the interfaces. Once you develop you will move all the objects to QA and then in prod.

If there are any changes you will make in dev and move once again in QA and prod in Final preparation.

During Go live and support you will monitor all theinterfaces. If they have any issues you will resolve them.

For documentation about XI interfaces see the below link

/people/krishna.moorthyp/blog/2006/07/29/documentation-html-editor-in-xi

Thanks

Swarup

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0f251f4-bd11-2a10-b4b8-9c394f89...

Edited by: Swarup Sawant on Jan 30, 2008 6:45 PM

[Former Member]

Hi Chinnu,

SAP XI requires an adapter framework to communicate outside of the SAP system.

These adapters translate code from external applications to an XML message for NetWeaver processes using the Java Connector Architecture.

for more info on this, you can just refer the following link:

http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/content.htm

I hope it will help you.

Regards,

Saurabh...

Reward with points if found helpful.

[Former Member]

Hi,

here it goes ....

UNDERSTANDING MESSAGE FLOW IN XI

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi

cheers,

Sunil.