Preparing the environment for WebSphere Adapters nodes

Before you can use the WebSphere® Adapters nodes, you must set up the IBM® App Connect Enterprise runtime environment so that you can access the Enterprise Information System (EIS).

Before you begin

Read WebSphere Adapters nodes.

About this task

To enable the WebSphere Adapters nodes in the IBM App Connect Enterprise runtime environment, configure the integration server with the location of the EIS provider JAR files and native libraries. (On Windows, the location of the JAR files cannot be a mapped network drive on a remote Windows computer; the directory must be local or on a Storage Area Network (SAN) disk.)
The integration server configuration file (server.conf.yaml) contains a section for connector providers, which defines the location of the required JAR files and native libraries, as you can see in the following example:
ConnectorProviders:
  SAPConnectorProvider:
    jarsURL: default_Path     # Set to the absolute path containing the SAP JCo JARs
    nativeLibs: default_Path  # Set to the absolute path containing the SAP JCo libraries
By default, the location is set to default_Path, which indicates that the JAR files and libraries can be found in the integration server's shared-classes directory.

Procedure

To configure the integration server with the location of required JAR files and libraries, complete the following steps.

  1. The WebSphere Adapters nodes require libraries from the EIS vendors. For more information on how to obtain and use these libraries, see Developing message flows that use WebSphere Adapters.
  2. Use a YAML editor to open the server.conf.yaml file, then find the ConnectorProviders section.

    You can edit the file by using the built-in YAML editor that is provided in the IBM App Connect Enterprise Toolkit, either by double-clicking the file in the Application Development view or by right-clicking the file and selecting Open with > YAML editor. If you choose to edit the file by using a plain text editor, ensure that you do not include any tab characters (which are not valid in YAML) and use a YAML validation tool to validate the contents of your file.

    For more information, see Configuring an integration server by modifying the server.conf.yaml file.

  3. Set the jarsURL property to the absolute path where the JAR files are stored.
  4. Set the nativeLibs property to the absolute path where the native libraries are stored.
  5. Save the server.conf.yaml file.

What to do next

When you have set up the environment for the WebSphere Adapters nodes, you can perform the preparatory tasks that are listed in Developing message flows that use WebSphere Adapters.