Installing the connector for mySAP.com and related files
The connector consists of two parts that need to be installed:
the connector's application-specific component and SAP's
RFC library.
After you have installed the
required connector files, you must download and install the Java
Connector (SAP JCo) files. For details about downloading and installing
the SAP JCo files, see Installing the SAP JCo.
Note:
Installer adds a menu option for the connector's
application-specific component to the IBM WebSphere business integration
adapters menu. For a fast way to start the connector, create a shortcut
to this component on the desktop.
Installing connectors on remote machines
You can install and run the connector on a remote machine.
Install the integration broker on one machine and the connector
on another machine. It is recommended but not required that both
machines be on the same subnet.
Installing multiple connectors
To enable the integration broker to
handle multiple business objects for SAP at the same time, you may
want to install and configure multiple connector components for an
SAP system and customize each connector to handle specific business
objects.
Each connector component can subscribe to certain business objects
depending on their type (such as Customer or Purchase Order). Because
you can have multiple connectors accessing the same SAP application,
each connector can process events and pass them on to the integration
broker. In addition, multiple connectors can support multiple business
object requests at the same time. This increases throughput and
speeds up the transfer of data into and out of the SAP application.
It is recommended that you choose a unique naming convention
for each connector component. For example, if you are using two
connectors you could name them SAP1Connector and SAP2Connector.
To install multiple connector components, do the following:
- Install each of the connectors as described in Installation Guide for WebSphere Business Integration Adapters.
This includes the connector shared library files. Give a unique
name to each connector you install, and verify that you have the supporting
connector files.
If you are installing multiple connectors on the same machine,
you need only make a copy of the shared library files and rename
them. You do not need to install the transports again.
- Create a copy of the startup script:
- On UNIX, make a copy of the existing connector_manager_SAP file for starting the connector, and rename the file to match
the name of the connector.
- On Windows, make a copy of the existing shortcut to the start_SAP.bat file, and rename the shortcut file to match the name of the
connector. Add the name of the connector as a parameter of the connector
shortcut.
- Make a copy of the connector template file, rename it to match
the new connector name, and then copy it to the repository directory (if IBM WebSphere MQ Integrator is the integration
broker), or load it into the IBM WebSphere repository (if WebSphere
InterChange Server is the integration broker).
- Make a copy of the connector class file, CWSAP.jar and rename it to the unique connector name, such as CWSAP1.jar.
- Initialize the connector configuration properties so that all
connectors poll the same SAP application for events.
- Only if the IBM WebSphere InterChange Server is the integration
broker, add map references for each connector.
- Specify the business objects supported by each connector.
- Only if WebSphere InterChange Server is the integration broker,
assign collaborations to the appropriate connectors. Currently,
a collaboration can be handled by only one connector. If collaborations
are already set up, you may need to stop them and then rebind the
ports.
- If you are using the ABAP Extension Module for business object
handing, set up the distribution of events to each connector that
you install. Use IBM WebSphere BI Station (transaction /n/CWLD/HOME). See Setting up event distribution for instructions on setting up event distribution
for each combination of business object, integration broker, and
connector.
Important:
If a business object is not configured to go to a particular
connector, the business object is sent to the next connector that
polls for events. If a business object is configured to go to a
particular connector, as for example during the testing phase, but
the connector is not used in the production phase, the event queue
for the connector fills up. To remedy this situation, delete the
connector/business object configuration in the Event Distribution
window (transaction /CWLD/RH).
