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 7.0.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 iWay Adapter for Connect Direct requires the following library files:

• CDJAI.jar
• JMS.jar

The CDJAI.jar library file is used to implement Java APIs.

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\iway7\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\iway7\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\iway7\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 iWay Integration Solution for FIX requires the B2BITS® FIX Engine.

The B2BITS® FIX Engine is packaged as an archive (B2Bits_jar.zip) and can be downloaded from:

http://techsupport.informationbuilders.com/

For more information on installing the B2BITS® FIX Engine and configuring the iWay Integration Solution for FIX, see the iWay Integration Solution for FIX User’s Guide.

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

For EnterpriseOne 9.0 (Tools Release 8.98):

Base_JAR.jar

JdeNet_JAR.jar

System_JAR.jar

Connector.jar

EventProcessor_EJB.jar

EventProcessor_JAR.jar

commons-httpclient-3.0.jar

jmxri.jar

jmxremote_optional.jar

ManagementAgent_JAR.jar

log4j.jar

For EnterpriseOne 9.10 (Tools Release 9.1.0.4):

Base_JAR.jar

JdeNet_JAR.jar

System_JAR.jar

Connector.jar

EventProcessor_EJB.jar

EventProcessor_JAR.jar

commons-httpclient-3.0.jar

jmxremote.jar

commons-logging.jar

jmxri.jar

jmxremote_optional.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\iway7\lib

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

C:\Program Files\iway7\lib

Before installing iWay Application Protocol Adapter for LDAP, iWay Service Manager (iSM) Version 7.0 or higher must be installed on a system that is running Java 2 Standard Edition (J2SE™) JDK 1.7 or higher. For more information, see Installing iWay 7.0.7 Service Manager Components.

All required .jar library files for the iWay Application Adapter for Microsoft Dynamics 2011 CRM On-Premises are provided in the iWay \lib folder.

Note: The iWay Application Adapter for Microsoft Dynamics CRM (Compatibility Mode) cannot be used with Microsoft CRM 2013.

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

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

In iWay Service Manager (iSM) Version 7.0.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.

The iWay Application Adapter for mySAP 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)

No other connection methods and interface types are 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.7nn. In this section, nn refers to release specifications. For a list of supported platforms and exact library names, refer to SAP Note 1077727. Use the SAP note to ensure the JVM and the JCo are compatible for the selected hardware and software platform.

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.

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 (ojdbc6.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\iway7\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.

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

Note that the adapter goes by the PeopleTools release and not by the PeopleSoft application version.

Note: You must connect with only one version of an EIS at a given point in time. You cannot connect to two different versions of PeopleTools using the adapter. Do not use two versions of an EIS library file simultaneously. You also cannot use the library files for two different versions in the \lib folder.

Required Library Files

This section lists the library files that are required by the iWay Application Adapter for PeopleSoft.

• PeopleSoft Java Object Adapter file (psjoa.jar)

  This file provides a low-level interface between client applications and PeopleSoft. This file is provided with PeopleSoft in the <PeopleSoft_Home>\web\PSJOA directory. The psjoa.jar file is different for every version of PeopleSoft. When you upgrade your PeopleTools release, ensure that you copy the psjoa.jar file for the new release into the <iWAY_Home>\lib directory and restart all components.

• pstools.properties

  This file is required for PeopleTools 8.1x. This file belongs in the <PeopleSoft_Home>\web\jmac directory.

• PeopleSoft Generated Java APIs

  For more information on generating the Component Interface Java APIs, see the iWay Application Adapter for PeopleSoft User's Guide.

All the library files for the PeopleSoft adapter must be copied to the specific directory, such as <iWAY_Home>\lib.

iWay Technology Adapter for RDBMS connects iSM to various database engines that have an available JDBC compliant driver from the database or third party vendor. Generally, the JDBC driver should match the database version as well as the version of the JVM that is hosting iSM. Database versions that have reached the end of their vendor supported lifecycle are no longer supported by iSM and the iWay Technology Adapter for RDBMS.

All JDBC drivers are installed in the \lib. For example:

• On Windows:

  iway7\lib

• On UNIX (for example, Linux and AIX):

  $IWAYHOME/lib

The iWay Application Adapter for SAP R/3 using SAP JCo 2 is no longer supported. SAP has discontinued support for SAP JCo 2 and as a result, iWay cannot offer the adapter on unsupported versions of the JCo. For all SAP adapter installations, 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. The mySAP ERP adapter will support SAP releases from SAP R/3 4.6C to SAP ERP 7.

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

For Siebel Versions 6.3 - 8.1, 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\iway7\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 - 8.1

  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.

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 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.

The iWay Emulation Adapter (3270/5250) includes the Telnet Designer, which is a tool to create screen-based interactions that can run with the adapter. The Telnet Designer is supported on Windows platforms only.

If the adapter is installed on a UNIX platform, then you will need to copy the Telnet Designer component, in binary format, from the UNIX system to the Windows system.

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

The following file is required.

tibrvj.jar

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

C:\Program Files\iway7\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.