Interacting with an SAP application
To interact with an SAP application,
obtain external software dependencies, run the Adapter Connection
wizard, develop a message flow, then deploy the relevant resources.
To connect to an SAP application, the
SAP adapter requires certain files and libraries. You must store these
files so that they are accessible to the Adapter Connection wizard.
The wizard creates various resources, such as an adapter component
and message flow. After you have completed the wizard, you can develop
a message flow to define the interaction with the SAP application,
then deploy the relevant resources.
- To obtain software dependencies, follow the instructions
in Adding external software dependencies for SAP.
- Optional: If you are using Application Link Enabling (ALE)
processing, register a Remote Function Call (RFC) destination on the
SAP server and configure the SAP server, as described in Configuring the SAP server to work with the adapter.
- Optional: To set up SAP for high availability, see Setting up SAP for high availability.
- Before you run the Adapter Connection wizard, gather the
following information from your SAP administrator:
- SAP system user name
- SAP system password
- SAP host name or IP address
- SAP Client ID (for example, 001)
- SAP system number (for example, 00)
- Language code (for example, EN)
You might also need to gather some specific information from
your SAP administrator about the items that you are discovering. For
example, if you are discovering IDocs, you need the appropriate information
to complete the following fields:
- IDoc name
- Version
- SAP outbound
- Verbs (create, update, delete)
- Partner number
- Message type
For more information, see SAP connection properties for the Adapter Connection wizard.
- To connect to SAP by using the Adapter Connection wizard,
and create a message flow, follow the instructions in Connecting to an EIS by using the Adapter Connection wizard.
- Develop your message flow to define the interaction with
the SAP application.
For example, to route IDocs to
separate messages, follow the instructions in Routing IDocs to separate message flows.
- Optional: To propagate security credentials to an SAP request,
see Propagating security credentials to Siebel and SAP requests.
- Deploy the appropriate resources, as described in Deploying a message flow that uses WebSphere Adapters.
- Optional: To change connection details for SAP adapters,
see Changing connection details for SAP adapters.
- Optional: To enhance existing adapters with newly discovered
objects, see Enhancing existing adapters with newly discovered objects.
Last updated Friday, 21 July 2017