cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Integration Repository

Former Member
0 Likes
1,947

Hi

what is integration repository.. what is the exact purpose of this .. in interview how can we explain this in effictively..?

thanks

Babu

View Entire Topic
Former Member
0 Likes

Hi BABU ,

This is the detailed description of Intergration Repository :

Objects created at design time are saved in the Intergration Repository & objects created at configuration time are saved in the Intergration Directory. objects defined in the Intergration Repository are defined during the development phase of the project & are part of the business package that can be delivered to the customer.Integration Server uses the Integration Knowledge built using the Intergration Repository & Intergration Directory.

At design time of the Integration Objects, the component information is extracted from the SLD (System Landscape Directory)to define business scenarios(The Integration objects - namely, data types, message interfaces, message mappings, interface mappings- r configured using the Intergration Repository .)

Modeling using the Intergration Repository :

The Intergration Repository is part of the Integration Builder tool that helps in building the design-time knowledge.

Communication in SAP XI is interface based. i.e , messages are generally created by calling an interface. SAP XI supports 2 approaches for implementing a cross-system process:

1)Outside-In : The relevant interfaces for the cross-system process are created in the Integration Builder. These message interfaces are a programming language-independent description in XML. These message interfaces are used to generate callable interfaces(proxies) in target systems.

2) Inside-Out : The functions that are to be called using SAP XI already exist in the application systems. To use an interface description of these functions in the design process, import specific interface descriptions to the Intergration Repository by using the Integration Builder.

The 2 approaches can be comined. Regardless of the interfaces that r required for u'r cross-system process, u must work simultaneously in the following development environments during design time:

1)Use the Integration Builder to design & define all objects affecting message exchange. In some cases , u can use external tools & import objects to the intergration repository.

2)Implement message processing in u'r application program by using the development environment of u'r application systems.

Design objects in the Integration Builder

The design objects that developers can create in the Intergration Repository by using Integration Builder r as follows :

Business scenarios

Business proccsess ( BPEL )

MAPPINGS ( XSLT, JAVA)

Context Objects( XPATH)

External Definition(WSDL,XSD,DTD)

Message interfaces(XSD)

Message types

Data types

The Integration Builder(integration repository) allows u 2 edit the following objects using the corresponding graphical editors :

1)Business scenarios describe the communication between application components on a higher level of abstraction.

2)Business proccsess r executable proccsess on the integration server

3)Mappings r used 2 define structure or value mappings between messages that r exchanged between interfaces. These mappings can be defined as graphical message mappings or they can be imported into the integration repository as XSLT or Java Archives.

4 )Context Objects mask access to elements or attributes in the payload. For Example, elements can be specified in a deeply nested message structure by using the short name of a Context Object, thus sparing u the long hierarchy path.

5) Data types & Message types describe the structure of messages that r 2 be exchanged using Message interfaces. Developers use Message interfaces to generate proxies in application systems.

The entire content of the Intergration Repository can be shipped. together, these objects are referred as Process Integration Content, abbrviated as XI content. Using a software componet version from the System Landscape Directory, the smallest possible shipment unit is defined for a number of objects that belong together in the integration repository

The following formats u can import to and export from the integration repository:

BPEL -


> Business proccsess -


> BPEL

XSLT -


> Mappings

(java)

WSDL

XSD -


> Interfaces -


> WSDL

DTD XSD

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

cheers,

gyanaraj