Parlant amb el SAP des MB

SAP is the largest Enterprise Resource Planning (ERP) solution provider. SAP is actually the name of the company, officially SAP AG, based on the phrase Systeme, Anwendungen und Produkte in der Datenverarbeitung.

Systems Applications Products in Data Processing (SAP) is a client/server application that helps you manage your business processes in sales, materials management, and distribution. SAP has mainframe and UNIX solutions to support an interface for an EDI subsystem.

The R/3 product is their client-server solution for Enterprise Resource Planning. mySAP.com is the current offering. It is an evolution of R/3 bundled with a number of additional components, as CRM, Business Warehouse plus SAP's middleware platform, SAP NetWeaver.

• R/3 : realtime data processing
• APO : advanced planner and optimizer
• BW : bussiness information warehouse
• CRM : customer relationship management
• SRM : supplier relationship management
• HRMS : human resource management systems
• PLM : product lifetime management
• XI : exchange infrastructute = SAP integration broker !
• KW : knowledge warehouse

El XI es la eina de integració de moduls SAP, així com la única via de comunicació amb l'exterior.
Parla MQ i JMS amb el "Adapter for (SAP) XI" que porta el MB.

    .--------.           .--------.
    |        |           |        |
    |  SAP   |           |  SAP   |
    |        |           |        |
    .--------.           .--------.
        |                |        |
        |                |   XI   |
        |                |        |
        |                .--------.
        |                    |
        |                    |
  .-----------.        .-----------.
  |           |        |           |
  | Adapter   |        | Adapter   |
  | for mySAP |        | for XI    |
  |           |        |           |
  .-----------.        .-----------.

Detalls XI :

• XI
• SAP - search fo "XI" !
• XI

SAP Exchange Infrastructure (SAP XI) enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other.

url

SAP generates application data in the SAP Intermediate Document (IDOC) layout.

url

The connected systems transfer or receive IDocs through their IDoc RFC interface.

iDoc adapter

iDoc sample and links

SAP designed IDocs ("Intermediate Documents") for exactly this purpose -- for encapsulating, moving around, and processing just the sections of data needed for specific purposes.

url

Un mensaje IDoc ALE típico que se ha enviado desde SAP al enlace WebSphere MQ para R3 consta de una cabecera MQMD, una cabecera MQSAPH y el propio IDoc ALE. El IDoc consta de estructuras de tamaño fijas:

• La primera estructura es la estructura de control (DC). Este es un elemento complejo con una longitud de 524 bytes que contiene un conjunto fijo de elemento simples definidos por SAP.
• Una o varias Estructuras de datos (DD). Cada DD es un elemento complejo con una longitud de 1063 bytes que contiene un conjunto fijo de elementos simples definidos por SAP que ocupa 63 bytes, seguido de 1000 bytes de datos de segmento definidos por el usuario.

url

MQSAPH fields - 12 parser's ! WS MB Information Center [*****] See Pager sample {com.ibm.etools.mft.samples.pager.res} & See Soccer Results sample ! {com.ibm.etools.mft.samples.soccer.res} [ VMware MB - c:\PF\ibm\ws\evtoolkit\eclipse\plugins\com ... ]

See Manipulating messages in the IDoc domain - url from SAP IDOC to XML and viceversa - url

Your best bet to answer this question before someone else does is to use AMQSBCG to dump a message produced by SAP.

Todos los campos se deben especificar y establecer. La sintaxis es:

Los nombres de campo, que se deben especificar en orden, son:

url

url

url

• BAPI's are programming interface to access SAP Database from within SAP or other development platforms external to R/3 that support the Remote Function Call (RFC) protocol. The main objective of BAPI is to achieve integration between the R/3 System and external applications, legacy systems etc. This gives you the option to have non-SAP front-end for occasional users.

• ALE is also programming interface. The integration of various applications is achieved by using synchronous and asynchronous communication, rather than by means of a central database.
  It uses RFC API.

url

The R3/Link product consists of an inbound server, reading IDOCs from an input queue and passing them into SAP, and an outbound server, reading IDOCs from SAP and writing them to an output queue. Both these apps run on the MQ machine, and make a TCP connection to the SAP system using SAP RFC calls.

MQ Series link for R/3 User Guide

MQ Series link for R/3 User Guide (on-line)

MQ Series Link for R/3 v 1.2 CSD03

• que son els conectores standard MYSAP ?
• el accés des Domino a MB (Message Broker) es via JMS, fent servir el adaptador MQ standard.
• el accés des SAP es mitjançant el Adapter For MySAP ...
• ens cal MQ al SAP : url

What is RFC ? Remote Function Call
ICS had a "RFC trace" - does MB have anything similar ?

David : the adapter uses JCO to access LIBRFC32.DLL, the RFC API.

Yo prefiero el JCA adapter que viene con Broker 6.1 [emir]

Toolkit [6.1] + "SAP" ; [int]

You get everything in the standard version and you are allowed to use them in "unit test" but to use them for real you have to pay an additional license fee for the sap nodes (they have a pid I believe). Their sales person should be able to work out a price. From the technical side nothing else has to be installed. In fact there is no direct checking or enforcement on our part in the code.
Regards, John.
John Reeve, WebSphere Message Broker Developer

SAP delivered files:

• sapjco.jar
• sapjcorfc.dll or libsapjcorfc.so
• librfc32.dll or librfccm.so

Download these files for your operating system from the SAP Service Marketplace, and save them to a directory, such as C:\SAP_LIB.

Set the location of the SAP prerequisite files using the following command:

To check that the values have been set correctly, run the following command:

MB v 6.1 "Message Flows", page 236 [244/1580]

Pend8888

The SAPInput node allows you to interact with SAP applications. For example, the SAPInput node monitors an SAP system for any new purchase orders. When a new purchase order occurs, the SAPInput node generates a message tree that represents the business object with the new purchase order details. The message tree is propagated to the Out terminal so that the rest of the message flow can use the data to update other systems, or to audit the changes.

MB v 6.1 "Message Flows", page 996 [1004/1580]

When you get a message, try it this way

1. copy the Properties folder
2. create the MQMD and then set any properties you might need in the MQMD
3. copy the Data

Have you looked at the data coming into the flow with a trace node ? This will help you name the folders correctly ( get a trace of the root )

The SAPRequest node allows you to interact with SAP applications. For example, the SAPRequest node requests information from a SAP Enterprise Information System (EIS). A customer business object is sent to SAP, causing SAP to retrieve information about a customer, such as an address and account details. The response information that is retrieved by the SAPRequest node can then be used by the rest of the message flow. The SAPRequest node can send and receive business data.

MB v 6.1 "Message Flows", page 1000 [1008/1580]

Els samples diuen de fer servir :

• SM59 = RFC connection
• BD54 = Logical System
• BD64 = Distribution Model
• WE20 = Partner Profile

Inbound adapters allow data to be passed from the EIS system to the MB.

• Switch to the Broker Application Development perspective.
• Expand the SapInboundMatMasSampleMSet message set project.
• Double click SapMatMasInbound.inadapter to open an editor where you can specify the connection parameters required to access your SAP system.
• Click Adapters > Inbound > SAP.
• Enter the following settings in the editor:
  • Hostname or IP address of the SAP Application server.
  • RFC Program ID, for example, SAMPRFC.
  • Gateway hostname or IP address.
  • Gateway service, for example, sapgw00.
    The Gateway Service can be found using transaction code SMGW (Gateway monitor) under the column titled Remote TP Name.
  • SAP Client ID (from SAP txn SCC4).
  • Language Code if the language is not English.
  • SAP System Number.
  • Username for SAP system.
  • Password corresponding to the username.
  Save the updated adapter.

Outbound adapters allow data to be passed from the MB to the EIS system.

Open

1. Help
2. Samples gallery
3. Technology samples
4. Message Broker
5. Transports and connectivity
6. SAP connectivity
7. 2 samples : Input & Request.

The Object Discovery Agent (ODA) and Bussiness Object Designer (BOD) are two design-time tools that can be used to extract metadata from the target system - in this case, SAP.

The ODA is the connector-specific component that connects to the targer system and then waits for requests to obtain metadata. The BOD connects to the ODA and requests metedata from it. The BOD displays the data returned, allowing the user to edit it if they wish, and then saves this metadata as XML schemas (.xsd files).

The ODA acts as an intermediary between BOD and SAP, and is used to extract IDoc metadata from the target SAP system.

ALE & iDoc

RFC & BAPI

SAP and WBI MB Integration for Dummies v0.pdf (?)
SAP and WebSphere Message Broker Integration for Beginners v1.2.pdf (?)

Top

The IBM MQSeries Link for SAP R/3 allows us to both put and get data into and out of SAP R/3 from and to other data sources and legacy applications. It consists of three parts:

• MQSeries
• MQSeries Integrator
• The SAP Integration Libraries

The MQSeries SAP Link uses ALE to load SAP IDoc metadata into the MQSeries Integrator Formatter. This means that it can handle bidirectional IDoc formats.
A library of IDocs is provided and additional or customized IDocs can be loaded dynamically into the Formatter via the IDoc loader.

Using the MQSeries Integrator Version 1.0 , SG24-5386-00

• description
• Name / IP of the SAP Application Server
• System ID
• System Number
• Client Number, User & Password

• SAP Input node
• SAP Request node
• Wizard to discover business object information from SAP system and generate connection definitions - Enterprise Metadata Discovery Wizard

Generates :

• Adapter Component
• Message Set definition (DataObject domain)

High-level steps :

• connect to EIS
• select services
• select business objects
• select operations
• refine connection properties for broker runtime
• generate message set

Adapter Connection Wizard can be invoked from :

• Menu option : File -> New -> Adapter Connection
• Broker Development View : right click, New -> Adapter Connection
• using Quick start wizard : Broker Development view + "Start from adapter connection"

WMB61_Beta_Adapters.ppt

Lola:\h:\SAP_SAG - Win & Linux

ST11 = see RFC trace