What is the difference between

[Former Member]

Hi Gurus,

Can you please let me know the difference between the below topics,

1) Software catalog & system Catalog

2) Business System & Technical System

3) Message Type & Message Interface

4) ABAP Proxies & Java Proxies

Thanks

jaya

[Former Member]

Hi Jaya,

well, to really understand the difference you will need about three days with a good book (check out http://www.amazon.com/SAP-Exchange-Infrastructure-integrating-technology/dp/159229037X/ref=sr_1_1/00... and access to a system, or even a BIT400 training course. But let's try:

1) The software catalog is a catalog (bunch of database tables) in the SLD (software landscape directory) containing the names of software products (e.g. SAP R/3), software product versions (e.g. SAP R/3 4.6c, SAP R/3 4.7), software components (e.g. ABAP Workbench), and software component versions (e.g. ABAP Workbench version 4.6c)

The system catalog is a catalog in the SLD containing the names (and a few other attributes) of technical and business systems in the system landscape of the company.

2.) A business system is a system sending and receiving messages (see 3) via message interfaces (see 3). The names of business systems are stored in the SLD and used by XI to identify (give names to) senders and receivers.

A business system runs on exactly one technical system. A technical system is for example an SAP R/3 Enterprise system with System ID P01. Each client of this technical system corresponds to exactly one business system. This means, that on one technical system, several business systems may be running.

3.) A message interface in the interface repository of XI describes, what message types a software component version can send out or receive. A message type describes just a single message. A message interface refers (in the case of a synchronous message interface) to two different message types: the request message type (sent out from the sender to the receiver), and the response message type (expected back by the original sender from the receiver)

4) Proxies are classes which are generated from message interfaces. These classes enable a software developer to create software components that implement a message interface that sends and receives message types as described in the interface repository. In other words: The software developer calls a method in the generated class to send out a message.

The benefit of using proxies is, that proxies can communicate to XI in the native XI protocol (SOAP with attachments).

Depending on whether he wants to program in ABAP or in Java, he will generate an ABAP or a Java proxy.

But your questions strongly suggest: Get a book and take three days to read it cover to cover, sitting next to an XI system and trying everything out.

Cheers and good luck

Michael

[Former Member]

Sri,

I would suggest to go to SAP help and put these fields in Search box. You will get the exact help on this.

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

---Satish

[Former Member]

Hi Satish,

Thanks for your information, i gone through all the documents but i need in simple terms. If you dont mind can you please explain me with simple example.

Thanks

Jaya

[former_member335553]

HI

The SLD contains sotware catalog( also known as component repository in version 3.0)describes the installed products and their constituent components in the system landscape. The software catalog is delivered with the content about all SAP products. External vendor information can be included /exended .

a Software Catalog of all installable SAP products and software components. It also includes information about support packages and dependencies between the products and software components. This information is the basis for the description of the system landscape.(IncludesProducts and s/w components)

System catalog also called landscape directory contains the informaion about all the systems installed in the landscape and their connections (Includes Technical and business systems)

Difference

Information from the software catalog is used in the IR and the information from the system catalog is used in the ID.

Just have a look at this link

http://help.sap.com/saphelp_nw2004s/helpdata/en/a2/2999ef97ea2b4790165f9ca5c05c41/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/9e/35d022edd4d646a53a56a4da60f9db/frameset.htm

Technical system : Refers to the physical system in the landscape Can be a ERP, J2EE etc

Business system: Provides a logical view of the technical system that function as senders or receivers within the SAP Exchange Infrastructure

Eg Specific client in SaP server

These entries are created in the SLD. If you are not sure to do with SLD level, you can always create a Business Service, ie Abstract Service to configure your scenario. Here there is no SLD entry.. You can create Business Service in Integration Diretcory

Go through this link for the same

http://help.sap.com/saphelp_nw2004s/helpdata/en/42/c817d9d2296bb2e10000000a1553f6/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm

Message type and Messge interface

A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:

· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.

· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.

3)message interface

You use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

ABAP and java proxy

ABAP proxy generation is part of the SAP Web AS 6.40. proxies communicate by using the Web service infrastructure and by using SAP Exchange Infrastructure. ABAP proxies that were generated from message interfaces in the Integration Repository (IR) can be used in both infrastructures. This means that if none of the Integration Server services are required for a proxy-to-proxy communication scenario in ABAP, you can use a point-to-point connection using the Web service infrastructure instead.

- Java proxy generation in the Integration Builder (Design) generates proxies from message interfaces in the Integration Repository. Java proxy generation packs the proxy objects in a Jar file, which you can save locally. You use the generated classes in J2EE applications on the SAP J2EE Engine.