iWay Adapters for the following data sources, systems, or protocols do not require third-party files or initial configuration:

• AS1/AS2
• CICS Transaction Adapter (XML)
• eMail
• Flat Files
• HIPAA
• HL7
• IMS
• IMS Database (iWay Adapter for RDBMS)
• IMS Transaction Manager
• EDI X12
• iWay/WebFOCUS (EDA) Server (iWay Adapter for RDBMS)
• Lawson
• Microsoft Message Queueing (MSMQ)
• SWIFT

Access to the following legacy mainframe data sources is provided through an iWay (EDA) Full-Function Server component that must be installed and configured on the mainframe.

• Adabas
• BULL GCOS
• Datacom
• Flat Files
• CA-IDMS/DB
• CA-IDMS/SQL
• Millennium
• MODEL 204
• Supra
• Teradata
• Total
• VSAM

Access to and from these data sources are accomplished by first connecting to the iWay Server. Adapters for other legacy data sources do not require an iWay Server.

To configure legacy data adapters for use with iWay 6.1.7 SM:

1. Install an iWay Server on the mainframe containing the data sources you wish to access.

   For information on iWay Server installation and configuration, see the WebFOCUS and iWay Server Installation manual and refer to the Server for z/OS chapter.

2. Configure the iWay Server to access the data source using the iWay Full-Function Server Administration Console. The Administration Console help explains the required steps. These steps also appear in the Data Adapter Administrator User's Guide and the Server Administration for UNIX, Windows NT OpenVMS, OS/400, & z/OS manual.
3. Install the iWay Data Management Administration Tools (DMAT) Suite on a Windows machine as explained in the iWay Data Management Administration Tools Suite Installation Guide.
4. Use the Catalog Administrator (installed with iWay DMAT) to add stored procedures to the iWay Server catalog so the procedures are accessible from iWay Explorer.

   For information on adding stored procedures, see the iWay Catalog Administrator manual.

The DB2 JDBC driver (db2java.zip) is required. This is installed as part of the DB2 server. The default location on the Windows platform is similar to the following:

C:\Program Files\IBM\SQLLIB\java\db2java.zip

Copy this file into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

For DB2 Version 7, you may need to run the usejdbc2.bat file supplied with DB2. Obtain the usejdbc2.bat from your DB2 server or download the current version from the DB2 JDBC driver download webpage. This process builds the proper JDBC 2.0-compliant version of the db2java.zip file. To run the usejdbc2 procedure, you must stop the DB2 instance.

This section provides the supported versions and required library files for the iWay Technology Adapter for ESRI (GEOLoad).

Note: The iWay Technology Adapter for ESRI (GEOLoad) is supported only on Windows platforms.

Supported Versions

• ArcSDE Version 9.0, 9.2, and 9.3 (For ESRILOAD)

  Note: ArcSDE is a part of ArcGIS in Version 9.2 and 9.3. However, ArcSDE is still only supported through the ArcSDE API. It is not supported through any other API, including ArcObjects.

• GDT Matchmaker Version 6 (For Geocoding)

Required Library Files

ArcSDE Version 9.0 (For ESRILOAD):

• jpe90_sdk.jar
• jsde90_sdk.jar

  Copy these files into the iWay lib directory, for example:

  C:\Program Files\iWay61\lib

ArcSDE Version 9.2 (For ESRILOAD):

• jsde92_sdk.jar
• jpe92_sdk.jar
• icu4j_3_2.jar
• concurrent.jar

  Copy these files into the iWay lib directory, for example:

  C:\Program Files\iWay61\lib

ArcSDE Version 9.3 (For ESRILOAD):

• jsde_sdk.jar
• jpe_sdk.jar
• icu4j_3_2.jar
• concurrent.jar

  Copy these files into the iWay lib directory, for example:

  C:\Program Files\iWay61\lib

GDT Matchmaker Version 6 (For Geocoding):

• mmaxwus3.dll
• usgeo.dll
• usattr.dll

  On Windows platforms, these files must be copied into the system32 directory, for example:

  C:\WINNT\system32

  or

  C:\WINDOWS\system32

The JDBC driver for Informix is required:

ifxjdbc.jar

You can download this driver from the Informix website as an archive. Copy the driver into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

J.D. Edwards EnterpriseOne (OneWorld) Java-based ThinNet API is required. This is normally distributed as JAR files with the J.D. Edwards installation media. These files may vary depending on the J.D. Edwards release. They usually consist of the following:

For J.D. Edwards OneWorld B7333 (XE) and B7334 (ERP8):

Kernel.jar

Connector.jar

For EnterpriseOne 8.10:

Kernel.jar

Connector.jar

jdeutil.jar

log4j.jar

For EnterpriseOne 8.11:

Base_JAR.jar

JdeNet_JAR.jar

System_JAR.jar

Connector.jar

log4j.jar

For EnterpriseOne 8.12 (Tools Release 8.96.2.0):

Base_JAR.jar

JdeNet_JAR.jar

System_JAR.jar

Connector.jar

EventProcessor_EJB.jar

EventProcessor_JAR.jar

log4j.jar

For EnterpriseOne 8.12 (Tools Release 8.97.1.2 and 8.97.2.0):

Base_JAR.jar

JdeNet_JAR.jar

System_JAR.jar

Connector.jar

EventProcessor_EJB.jar

EventProcessor_JAR.jar

commons-httpclient-3.0.jar

jmxri.jar

ManagementAgent_JAR.jar

log4j.jar

Note: These files are located in the \\system\classes folder on the JDE Client and the Deployment Server.

You must copy the JAR files into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

The DB2/400 JDBC driver (jt400.jar) is required. Copy the driver into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

The JMS listener requires the JMS specific JAR files supplied by the JMS vendor. Copy the JAR files into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

For TIBCO Enterprise for JMS software, this is:

Tibjms.jar

Tibjmsnaming.jar

jms.jar

tibjmsadmin.jar

When running components through BEA WebLogic Server, this is weblogic.jar.

The iWay Technology Adapter for Microsoft .NET allows you to expose Microsoft .NET assemblies in a J2EE platform without requiring any additional custom attributes or wrapper code.

Microsoft .NET Versions 2.0 - 4.0 are supported by the adapter.

In iWay Service Manager (iSM) Version 6.1.7, the iWay Technology Adapter for Microsoft .NET supports 32- and 64-bit JVM environments. The required components for both environments are automatically installed. During the iSM installation process, ensure that Microsoft .NET is selected under the Technology Adapters category in the Adapter Selection pane, as shown in the following image.

The following JAR file is needed:

com.ibm.mq.jar

Copy these files into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

When running components through an application server, also add these files to the application server CLASSPATH.

Also ensure that one of the following MQSeries directories is in the search PATH of any user ID that runs iWay components.

MQSeries\Java\lib

or

WebSphereMQ\Java\lib

The iWay Application Adapter for SAP ERP uses the SAP Java Connector (JCo) to communicate with SAP ABAP system targets. The following protocols and document styles are supported:

• SAP ALE Intermediate Document (IDOC)
• Remote Function Call (RFC)
• Business API (BAPI)

Any other connection methods and interface types are not supported.

The official supported platform for the iWay Application Adapter for mySAP ERP is SAP Java Connector (JCo) Version 3.nn for Java Version 1.6nn. In this section, nn refers to release specifications. For a list of supported platforms and exact library names, refer to SAP Note 1077727.

iWay Software also supports legacy implementations with SAP JCo Version 2.nn using java 1.5nn. For a list of supported platforms and exact library names, refer to SAP Note 549268.

All new adapter development is being implemented on SAP JCo Version 3.nn platforms. Only bug fixes and patches are being maintained on SAP JCo Version 2.nn platforms.

Not all SAP supported platforms are supported by iWay Service Manager. For more information, check the list of iWay supported platforms to ensure compatibility.

The SAP JCo library files must be downloaded from the SAP Service Marketplace. A valid SAP support ID is required to access the SAP Service Marketplace. For assistance, contact your SAP administrator. For more information on installing, configuring, and verifying the iWay Application Adapter for mySAP ERP, see the iWay Application Adapter for mySAP ERP User's Guide.

To install iWay Application Adapter for mySAP ERP (SAP JCo 3.0), ensure that MySAP JCO 30 is selected under the Application Adapters category in the Adapter Selection pane during the iSM installation process, as shown in the following image:

The iSM installation process automatically adds the iwmysap30.jar file to the <ism_home>\lib directory.

<ism_home>\lib

<ism_home>/lib

<ism_home>/lib

<ism_home>/lib

Oracle JDBC driver (ojdbc14.jar) is required by the iWay Application Adapter for Oracle E-Business Suite. You must copy this .JAR file into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

To use iWay Concurrent Program request functionality, you must install and configure Oracle Client on the Oracle database that supports Oracle E-Business Suite.

Installing the iWay Oracle API Wrapper

If you want to use the iWay Application Adapter for Oracle E-Business Suite to interact with Oracle APIs (Stored Procedures and Packages), you must install the iWay Oracle API wrapper. For more information, see the iWay Application Adapter for Oracle E-Business Suite User’s Guide.

Installing the GETCLOB Procedure

The GETCLOB procedure must be installed under the schema the adapter uses to run Oracle APIs. For more information, see the iWay Application Adapter for Oracle E-Business Suite User’s Guide.

The following JAR files are required:

aqapi12.jar
ons.jar

As well as the Oracle JDBC driver:

ojdbc14.jar

Copy these files into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

The Oracle JDBC driver is required:

ojdbc14.jar

Copy this file into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

You can download this driver from the Oracle website at:

http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html

For more information on Oracle JDBC issues, see the Oracle JDBC FAQ at:

http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm

This section indicates which combination of releases and system platforms are supported for the iWay Application Adapter for PeopleSoft.

PeopleSoft Platform	PeopleSoft Release	PeopleTools Release Level
All PeopleSoft supported platforms (Windows, Solaris, AIX, Linux, and HP-UX).	8.1 8.4	8.16.03 - 8.22 8.40.05 - 8.52

See the requirements in the corresponding sections for specific target data sources:

• For DB2, see DB2 Net Driver (iWay Adapter for RDBMS).
• For Oracle, see Oracle (iWay Adapter for RDBMS).
• For SQL Server, see SQL Server (iWay Adapter for RDBMS).

The iWay Application Adapter for SAP R/3 is deprecated. As a result, please use the iWay Application Adapter for mySAP ERP instead. The installation instructions for mySAP ERP should be followed in any scenario that requires the SAP R/3 adapter.

For more information, see MySAP ERP (SAP Java Connector Version 3.x).

For Siebel Versions 6.3 - 8.0, Siebel Java Data Bean API is required. This is distributed as JAR files with the Siebel Thin Client.

Copy the required JAR files into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

The required files vary by Siebel release in both content and name. Therefore, the Siebel Thin Client provided with the target Siebel system must always be used with the adapter, for example:

• Siebel 6.3.x

  SiebelTcOM.jar
  SiebelTcCommon.jar
  SiebelTC_enu.jar
  SiebelDataBean.jar

• Siebel 7.0.3

  SiebelJI_Common.jar
  SiebelJI_enu.jar

• Siebel 7.5.2

  SiebelJI_Common.jar
  SiebelJI_enu.jar
  SiebelJI.jar

• Siebel 7.7 - 7.8.2

  SiebelJI_enu.jar
  Siebel.jar

• Siebel 8.0

  SiebelJI_enu.jar
  Siebel.jar

The Siebel COM-based API (Windows only) requires the Siebel Thin Client to be installed and accessible to the adapter.

The following files are for English language implementations:

SiebelTC_enu.jar
SiebelJI_enu.jar 

For non-English installations, the last three letters (_enu) vary.

If you are using MQSeries as a transport, your system must meet the requirements for MQSeries.

Siebel Version 6.2 and Lower Connectivity Prerequisites

You must perform additional steps to connect to a Siebel system (version 6.2 and lower) using COM connectivity for an iBSP configuration. For more information, see the iWay Application Adapter for Siebel User's Guide.

Configuring Connection Pooling for Siebel

To configure connection pooling for Siebel, you must create a siebel.properties file for use with the iWay Application Adapter for Siebel. For more information on how to configure the siebel.properties file, see the iWay Application Adapter for Siebel User's Guide.

The SQL Server JDBC driver is required.

• For SQL Server 2005 and SQL Server 2008, there is one file.

  sqljdbc.jar

Copy the driver file or files into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

You can download the driver free of charge from:

http://microsoft.com

The iWay Emulation Adapter (3270/5250) links new business applications to mainframe-based business logic through IBM 3270 and 5250 terminal screens and data streams. It enables you to transform your 3270 or 5250 mainframe screens into HTML pages or to create a remote procedure request (RPC) to transform the output of screens into an answer set. The adapter provides a simple, lightweight, and scalable way to reuse the business logic and data of terminal applications.

The iWay Emulation Adapter (3270/5250) requires client components that you must configure after installing iWay. The two client components are:

• The run-time component, which is supported on:
  • Microsoft Windows 2000 with SP2 and Windows 2003.
  • UNIX.
  • z/OS (under UNIX System Services).
• The Telnet Designer, which is supported on:
  • Microsoft Windows 2000 with SP2, Windows 2003, and Windows XP SP1.

To run the Emulation Adapter on a UNIX system, you need the Emulation Adapter client components on the UNIX system and also the adapter client components on a Windows system. This enables you to use the Telnet Designer, which is supported on Windows platforms only.

The iWay Emulation Adapter requires client components, including the Telnet Designer, that are configured when you install iWay 6.1.7 SM. Depending on the options you chose during the iWay installation, they may already be installed.

For information about using the adapter, including the Telnet Designer, see the iWay Emulation Adapter (3270/5250) User's Guide.

The JDBC driver for Sybase servers (jConnect for JDBC) is required.

You can download the driver (jconn2.jar) from the Sybase downloads website:

http://www.sybase.com/downloads

Obtain the jConnect.zip file that corresponds to your version of Sybase and follow the steps described on the jConnect download page to extract the JDBC driver.

Copy the JDBC driver files into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

The following file is required.

tibrvj.jar

Copy this file into the iWay lib directory, for example:

C:\Program Files\iWay61\lib

In addition to the Java file, tibrvj.jar, the iWay Adapter for TIBCO requires several TIBCO binary files. These files are stored in the following TIBCO directory:

C:\tibco\tibrv\bin

This directory must be added to the search PATH variable of any user ID that runs iWay components.