C:\Program Files\iWay60\lib

x

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

• 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
• Transora
• UCCnet

x

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 is 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.0.1 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 Server Full Function Server Web Console. The Web 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's catalog so the procedures are accessible from iWay Explorer.

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

x

BouncyCastle files are required. The current names of the BouncyCastle .JAR files for Java 1.5 are:

bcmail-jdk15-141.jar

bcprov-jdk15-141.jar

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

C:\Program Files\iWay60\lib

x

This section provides the supported versions, required library files, and installation prerequisites for the iWay Application System Adapter for Amdocs ClarifyCRM.

Note: The iWay Application System Adapter for Amdocs ClarifyCRM is supported only on Windows platforms with a Microsoft SQL Server database.

Supported Versions

• 10.1
• 11.5
• 12.0
• 12.5
• Amdocs CRM Version 6

Required Library Files

For ClarifyCRM version 10.1, 11.5, 12.0, and 12.5:

• clfycbo.jar

For Amdocs CRM Version 6:

• clfycbo.jar
• jdom.jar

Installation Prerequisites

The following steps must be completed before using the iWay Application System Adapter for Amdocs ClarifyCRM.

1. Install your CBO application (for example, ClarifyCRM eSupport) in Server mode on the same machine where the iWay Application System Adapter for Amdocs ClarifyCRM is installed.
2. Copy the required library files (.JAR files) for the Clarify CBO APIs (for example, clfycbo.jar or clfycore.jar) into the iWay lib directory, for example:

   C:\Program Files\iWay60\lib

3. Add the bin folder (for example: \\ClarifyCRM13.1\eSupport\Clarify\bin) of the CBO application to the System PATH.
4. Install the database client (for example, Microsoft SQL Server) on the same machine where the iWay Application System Adapter for Amdocs ClarifyCRM will be used.
5. Verify that you are able to successfully execute the TestCboInstallJava and the Run_TestCboInstallJava utilities, which are delivered by Clarify.

For more information on how to configure CBO integration, see the Configuring CBO Settings section in the System Administration Guide, which is provided by Clarify.

x

Your ORB provider's API JAVA libraries are required and should be copied into the iWay lib directory, for example:

C:\Program Files\iWay60\lib

For ORBACUS, these are the following files:

OB.jar

OBnaming.jar

Note: If you use a third party application server, you should add these files to its CLASSPATH.

For ORBACUS, you should also add these to your WebLogic Domain CLASSPATH.

x

The DB2 JDBC driver (db2java.zip) is required. This is installed as part of the DB2 server. The default location on Windows 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\iWay60\lib

For DB2 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 Web page. 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.

x

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\iWay60\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\iWay60\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\iWay60\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

x

The JDBC driver for Informix is required:

ifxjdbc.jar

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

C:\Program Files\iWay60\lib

x

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\iWay60\lib

x

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

C:\Program Files\iWay60\lib

x

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

x

The Oracle JDBC driver is required. This is typically

ojdbc14.jar

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

C:\Program Files\iWay60\lib

x

The Progress JDBC Type 2 driver is required. The following files are needed:

jdbc.jar

progress.jar

JdbcProgress.dll

Procli92.dll

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

C:\Program Files\iWay60\lib

x

The following JAR file is needed:

com.ibm.mq.jar

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

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

x

The following platforms are supported by the iWay Application Adapter for mySAP ERP:

• Windows
• Linux/Solaris/OS400
• HP-UX
• AIX

The iWay Application Adapter for mySAP ERP uses the SAP Java Connector (JCo) and the SAP RFC library to communicate with SAP ABAP server targets. To the extent these interfaces and their associated object types are supported, the adapter can function within the established protocols for the following object types:

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

Other connection methods and interface types are not supported. The lowest application server release supported by the iWay Application Adapter for mySAP ERP is 4.6C. For more information about specific applications or servers, please consult your iWay Software Customer Service Representative.

SAP JCo Version 2.x is required for the iWay Application Adapter for mySAP ERP. The SAP JCo files are downloaded from the SAP Service Marketplace. A valid ID is required to access the SAP service marketplace. Please contact your SAP administrator for assistance. For the current release status of the SAP Java Connector (JCo), refer to SAP Note #549268 in the SAP Service Marketplace.

SAP JCo Version 3.0 is not supported for this release of the iWay Application Adapter for mySAP ERP.

For more information on installing, configuring, and verifying the mySAP ERP adapter, see the iWay Application Adapter for mySAP ERP User’s Guide.

Note: SAP JCo files must match the JVM mode (32- or 64-bit). Strictly mixed mode JVM is not supported. It is possible to run the entire 32-bit stack on a 64-bit machine, but 64-bit can only be run on 64-bit machine types.

Windows DLL search rules:

1. Directory for the executable.
2. Current directory.
3. The Windows system directory.
4. The Windows directory.
5. In the PATH environment variable.

The iWay Application Adapter for mySAP ERP is not the owner of the process handle for the JCo or RFC DLL modules. During adapter startup, ownership of the process for the JCo passes to the container (for example, iWay Service Manager) that is running the adapter. When any changes are made to a listener or client, stopping and starting the adapter will not reset the connection handles. iWay Service Manager must be restarted to release the connections.

Since the iWay Service Manager container controls the JCo lifecycle, any conflicts of invocation because of execution order in client libraries must be avoided. The JCo JAR file (sapjco.jar) and its associated JNI library must be copied to the iWay lib directory to avoid conflicts of DLL invocation, for example:

C:\Program Files\iWay60\lib

The SAP RFC library must reside in the %WINDIR% (usually c:\windows) system directory, as there may be multiple users of this DLL on a system (for example, adapter and SAP GUI). Version incompatibility issues are avoided if there is one library located in a central directory.

If you are going to name the library, then the correct name is Librfc32.dll on Windows platforms and Librfccm.so on Linux/UNIX platforms.

On other operating systems, there is no default execution order for the RFC library. It is located by the use of the appropriate variable by system (see list below). The SAP JCo installation in the \lib directory guideline is applicable on these platforms as well.

Windows

• sapjco.jar
• sapjcorfc.dll
• librfc32.dll

Linux/Solaris/OS400

• sapjco.jar
• libsapjcorfc.so
• librfccm.so

HP-UX

• sapjco.jar
• libsapjcorfc.sl
• librfccm.sl

AIX

• sapjco.jar
• libsapjcorfc.so
• librfccm.so

The following is a list of platforms and associated variables:

AIX

LIBPATH

HP-UX

SHLIB_PATH

Other UNIX platforms

LD_LIBRARY_PATH

x

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

x

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\iWay60\lib

x

The Oracle JDBC driver is required:

ojdbc14.jar

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

C:\Program Files\iWay60\lib

You can download this driver from the Oracle Web site 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

x

The PeopleSoft Java Object Adapter is required. This file provides a low level interface between client applications and PeopleSoft. It is normally installed with PeopleSoft under:

PS_HOME\web\PSJOA\psjoa.jar

where:

PS_HOME

Is the PeopleSoft home directory.

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

C:\Program Files\iWay60\lib

The psjoa.jar file is different for every version of PeopleSoft. When you upgrade your Peopletools release, ensure you copy the psjoa.jar file for the new release into the iWay55 lib directory and restart all components.

For PeopleSoft 8.1, the following file also must be copied into the iWay lib directory:

PS_HOME\web\jmac\pstools.properties

For more information, see the iWay Adapter for PeopleSoft User's Guide.

x

See requirements in for specific target data sources. For example, DB2, Oracle, SQL Server, and so forth.

x

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.

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

x

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\iWay60\lib

You can download the driver free of charge from:

http://microsoft.com

x

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's client components on a Windows system. This enables you to use the Telnet Designer, which is supported on Windows only.

The iWay Emulation Adapter requires client components, including the Telnet Designer, that are configured when you install iWay 6.0.1 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.

x

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

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

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\iWay60\lib

x

The following file is required.

tibrvj.jar

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

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