Adapter environment

Before installing, configuring, and using the adapter, you must understand its environment requirements.

Broker compatibility

The adapter framework that an adapter uses must be compatible with the version of the integration broker (or brokers) with which the adapter is communicating. Version 1.2.x of the adapter for CORBA is supported on the following versions of the adapter framework and with the following integration brokers:

See Release Notes for any exceptions.

Note:
For instructions on installing the integration broker and its prerequisites, see the following documentation.

For WebSphere InterChange Server (ICS), see the System Installation Guide for UNIX or for Windows.

For message brokers (WebSphere MQ Integrator Broker, WebSphere MQ Integrator, and WebSphere Business Integration Message Broker), see Implementing Adapters with WebSphere Message Brokers, and the installation documentation for the message broker. Some of this can be found at the following Web site:

http://www.ibm.com/software/integration/mqfamily/library/manualsa/

For WebSphere Application Server, see Implementing Adapters with WebSphere Application Server and the documentation at

http://www.ibm.com/software/webservers/appserv/library.html

Adapter standards

The adapter is written to the CORBA 2.3.1 specification and as such is compatible with CORBA applications designed to this standard.

Adapter platforms

The adapter runs on the following platforms:

Adapter dependencies

The connector for CORBA has the following dependencies, each with unique installation requirements, depending on your adapter platform.

JDK software

The Java Development Kit (JDK), Version 1.3.1, is a prerequisite of installing the adapter for CORBA.

Windows 2000

WebSphere Business Integration Adapter Framework, Version 2.4.0 provides a separate installation of IBM JDK, Version 1.3.1 SR5. Note that the IBM JDK, Version 1.3.1 SR5 is not installed as part of the WebSphere Business Integration Adapter Framework installation. You must run a separate installation to install the JDK. For details about how to install the JDK from WebSphere Business Integration Adapter Framework, refer to that software package.

Solaris

Install the Sun JDK 1.3.1 that is specified by the WebSphere Business Integration Adapter Framework, Version 2.4.0 installation. The JDK is not installed as part of the WebSphere Business Integration Adapter Framework installation. You must run separate installation software, provided by Sun Microsystems, to install the JDK.

AIX

Install the IBM JDK, Version 1.3.1 SR5. For details about obtaining the installation software, contact IBM Technical Support.

HP-UX

Install the HP JDK 1.3.1 that is specified by the WebSphere Business Integration Adapter Framework, Version 2.4.0 installation. The JDK is not installed as part of the WebSphere Business Integration Adapter Framework installation. You must run separate installation software, provided by HP, to install the JDK.

Object Request Broker (ORB)

The adapter for CORBA assumes an object request broker environment that supports the IBM Java Object Request Broker (ORB).

Windows 2000

The required IBM Java ORB is provided in the IBM JDK 1.3.1 SR5. For instructions about installing the ORB, see the JDK installation package.

Solaris

WebSphere Business Integration Adapter Framework, Version 2.4.0 provides the necessary IBM Java ORB software. The ORB is installed as part of the Adapter Framework installation.

AIX

The required IBM Java ORB is provided in the IBM JDK 1.3.1 SR5. For instructions about installing the ORB, see the JDK installation package.

HP-UX

WebSphere Business Integration Adapter Framework, Version 2.4.0 provides the necessary IBM Java ORB software. The ORB is installed as part of the Adapter Framework installation.

IDLJ to Java compiler tool

The Object Discovery Agent (ODA) component of the connector for CORBA uses the IDLJ compiler tool. This tool is a compiler that the ODA uses to generate the Java proxy class definitions that allow the connector to act as a CORBA client or server.

CORBA structs, interfaces, methods, and other programmatic entities are defined in an IDL (Interface Definition Language) file. The IDLJ compiler tool run by the ODA converts the CORBA programmatic entities defined in the IDL file into proxy classes. At runtime, the connector creates a proxy object from a proxy class and uses the proxy object to invoke the methods of that object's corresponding CORBA class that is defined in the IDL file.

Users of the adapter for CORBA, version 1.0.x, must recompile their IDL files to regenerate Java proxy class definitions that are compatible with the ODA of version 1.2.x. For details about this migration step, see IDL file compatibility.

Note:
Certain application providers of CORBA servers supply the .jar file that defines the proxy classes, thus bypassing the need for the object definitions generated (compiled) by the connector's ODA (using the IDLJ compiler tool). If the CORBA server application provider supplies a .jar file of proxy class definitions, then be sure to copy the file to the ProductDir\connectors\CORBA\ext directory, or whatever directory you designate as the directory for storing the proxy class .jar files, where ProductDir represents the directory where the connector product is installed. Using Business Object Designer, you specify the appropriate directory name, in the OutputFileDir configure agent property. For details about this property and how to set it, see Configure the agent. For details about defining properties in the ODA, see Creating and modifying business objects.

Windows 2000

The required IDLJ compiler tool is provided in the IBM JDK 1.3.1 SR5. For instructions about installing IDLJ, see the JDK installation package.

Solaris

WebSphere Business Integration Adapter Framework, Version 2.4.0 provides the necessary IDLJ software. The IDLJ is installed as part of the Adapter Framework installation.

AIX

The required IDLJ compiler tool is provided in the IBM JDK 1.3.1 SR5. For instructions about installing IDLJ, see the JDK installation package.

HP-UX

WebSphere Business Integration Adapter Framework, Version 2.4.0 provides the necessary IBM IDLJ software. The IDLJ is installed as part of the Adapter Framework installation.

JavaC

JavaC, the Java programming language compiler, is a prerequisite of the Adapter for CORBA. JavaC is part of the JDK 1.3.1 and as such is installed as a part of any JDK installation. For details about the JDK prerequisite, see JDK software

IBM ORB Transient Naming Server

The IBM ORB Transient Naming Server is a prerequisite of the connector for CORBA. This service provides the necessary CORBA naming services that allow CORBA objects to be named by means of binding a name to an object reference. When running as a client, the connector is able to connect with CORBA servers that use the IBM Java Object Request Broker (ORB) only. When running as a server, CORBA clients that use ORBs of other ORB vendors are able to connect with the connector. For details about the IBM Java ORB, see Object Request Broker (ORB).

WebSphere Business Integration Adapter Framework, Version 2.4.0 provides the necessary IBM ORB Transient Naming Server software. This software is installed as part of the Adapter Framework installation. To launch the IBM ORB Transient Naming Server, run one of the following commands, depending on your platform, from the \connectors\CORBA\ directory.


Windows 2000 Solaris, AIX, HP-UX
NamingService.bat NamingService.sh

This command requires a user-defined port number. For example, the following command, run in a Windows 2000 environment, starts an instance of the IBM ORB Transient Naming Server at port 1100:

NamingService.bat 1100

Note that to use the required IBM ORB Transient Naming Server software provided by WebSphere Business Integration Adapter Framework, you may need to re-register your existing CORBA services with the service that is launched by the NamingService.bat/NamingService.sh command.

Locale-dependent data

The connector has been internationalized so that it can support delivery of double-byte character sets going into a CORBA interface that also supports double-byte character sets, and deliver message text in the specified language. When the connector transfers data from a location that uses one character code to a location that uses a different code set, it performs character conversion to preserve the meaning of the data.

The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encodings for characters in most known character code sets (both single-byte and multibyte). Most components in the WebSphere business integration system are written in Java. Therefore, when data is transferred between most integration components, there is no need for character conversion.

Copyright IBM Corp. 1997, 2004