Integration Architect 8.12.0 on Solaris - Readme
Release - September 2006

Contents

Solaris uses the standard pkgadd installation utility to install Integration Engine. This document leads you through Solaris system requirements, prerequisites, installation procedures, verification, and post-installation steps.

System Requirements

The following hardware and software is needed for a minimum and preferred installation:

Pre-Installation Checklist

Review the following checklist before installing Integration Engine:

To Install from a CD

  1. Log onto the Solaris machine using your root user name and password.
  2. Mount the CD. Substitute your CD device name for /dev/cddevice:

    3. mount -F cdfs /dev/cddevice /cdrom

  3. Run the Solaris pkgadd utility:

    4. pkgadd -d /cdrom Engine<version>

    Note  The archive file name on the installation CD will contain the actual version value to type in place of <version>.

What to Do Next

After installing, you must install the license file. See To Apply the License File.

To Install from a Downloaded Archive

  1. Log onto the Solaris machine using your root user name and password.
  2. Create a temporary directory (called mytmp in the example, or any other name you wish):

    3. mkdir /mytmp

  3. Copy the archive into the mytmp directory:

    4. cp dje800-solaris-<version>.tar.gz /mytmp

    Note  The archive file name on the installation CD will contain the actual version value to type in place of <version>.

  4. Change directories to the temporary directory:

    5. cd /mytmp

  5. Uncompress and untar the archive:

    6. gunzip dje800-solaris-<version>.tar.gz tar xvf

    dje800-solaris-<version>.tar

  6. Run the Solaris pkgadd utility:

    7. pkgadd -d /mytmp Engine<version>

What to Do Next

After installing, you must apply the license file. See To Apply the License File.

To Apply the License File

The following are instructions for applying a license file. If you do not have a license file, see Obtain a license file.

  1. After you have installed Integration Engine, copy your license dj800.slc file to the following location:

    2. cd /opt/PervasiveSoftware/IntegrationEngine<version>/license

  2. Change the file access permissions as follows:

    3. chmod 644 /opt/PervasiveSoftware/IntegrationEngine<version>/license/dj800.slc

  3. Next, you may want to verify the installation. See Post-Installation Steps.

To Update the License File

The following are instructions for updating an existing license. If you do not have an update license file, see Obtain a license file.

To update your license file, copy the update license (.slu file) to the following default location: /opt/PervasiveSoftware/IntegrationEngine<version>/license. If you are using a location other than the default, copy the update license file to that directory location instead.

Note  When copying the update .slu file, do not delete the initial license .slc file (leave the .slc file in the license directory).

Post-Installation Steps

To ensure that Integration Engine is set up correctly, perform the following post-installation steps:

  1. Check for the existence of installed versions. You can determine the Integration Engine versions installed on your Solaris box with the following command:

    2. pkginfo -l Engine<version>

  2. Set the appropriate environment variables for all Integration Engine users as follows:

    3. export PATH=$PATH:/opt/PervasiveSoftware/IntegrationEngine<version>

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/PervasiveSoftware/IntegrationEngine<version>

  3. Ensure all users running Integration Engine have read and execute permissions on the install directory and on all the files and subdirectories located within the install directory. One exception to this is the lookup temporary directory, which is located in the following location:

    4. /opt/PervsiveSoftware/IntegrationEngine<version>/lookup

    Users must have write permissions in the above directory if they plan to use lookup tables.

  4. If you need to uninstall Integration Engine, run the following command as root:

    5. pkgadd -u IntegrationEngine<version>

New Features and Enhancements

This release of Integration Engine for Solaris provides improvements made in the following areas:

Java Runtime Environment

Connectors

Documentation

Known Issues and Resolutions

This section lists the most noteworthy known issues for Solaris as of the release date. If you encounter an issue not found here, contact Pervasive Support.

Issue: A Java Virtual Machine (JVM) is not detected on the machine.

Solution: Install JVM version 1.4.2_06 or higher, or Java 5, and then perform the integration platform installation again. For more information, see the topic “Installing Java Before the Integration Platform” in the Getting Started Guide.

Issue: The Java version currently installed on the machine is not one of the following: 1.4.2_06 or higher, or Java 5

Solution: Install JVM version 1.4.2_06 or higher, or Java 5. For more information, see the topic “Installing Java Before the Integration Platform” in the Getting Started Guide.

Issue: You do not have administrative privileges for the machine (a root user ID and password is required to install the product).

Solution: Contact your support organization and request that your privileges be modified to Administrative for the affected machine.

Issue: While performing a maintenance installation, your subscription is determined to be expired.

Solution: Contact your support organization to have the subscription renewed and obtain an updated licence. After implementing the new license, attempt to install again.

Issue: You encounter a loading of shared libraries error after attempting to run Integration Engine.

Solution: Put the Integration Engine installation directory at the beginning of your PATH and LD_LIBRARY_PATH environment variables. In rare cases, customers have reported problems with having an existing incompatible version of one of the third-party components that are used, such as ACE, ICU, or Xerces C. Place Integration Engine at the front of search paths to insure the component version in the Integration Engine install directory is loaded first at runtime.

Important Notes

Oracle8 Connectors

Two versions of the Oracle8 connector are included to support two versions of Oracle8. The dj800oci8.8.0.5.so connector works with all Oracle 8.0.x client installations; the dj800oci8.8.1.5.so connector works with all Oracle 8.1.x client installations. The user has to either copy or make a symbolic link from the versioned shared library to the dj800oci8.so shared library in the Integration Engine installation directory.

By default, the 8.1.x version of the Oracle8 connector is installed. To enable Oracle 8.0.x support, type the following command in the Integration Engine installation directory:

cp dj800oci8.8.0.5.so dj800oci8.so

To enable Oracle 8.1.x support, type the following command in the Integration Engine installation directory:

cp dj800oci8.8.1.5.so dj800oci8.so

ODBC Drivers

Support is included for both the Data Direct Technologies ODBC driver manager and the IODBC driver manager. By default the ODBC 3.x connector named dj800odbc3.so is built for the Data Direct Technologies ODBC driver manager.

The IODBC version of the ODBC 3.x connector can be used in situations where the default ODBC 3.x connector does not work with other vendor's ODBC drivers. The IODBC enabled shared library is named dj800odbc3.iodbc.so and the Data Direct Technologies shared library is named dj800odbc3.datad.so. To change the default supported ODBC driver manager, the user has to either copy or make a symbolic link from the versioned shared library to the dj800odbc3.so shared library in the Integration Engine installation directory. To enable IODBC driver manager support, type the following command in the Integration Engine installation directory:

cp dj800odbc3.iodbc.so dj800odbc3.so

To re-enable Data Direct driver manager support, type the following command in the Integration Engine installation directory:

cp dj800odbc3.datad.so dj800odbc3.so

Multi-Threaded Engine

In some rare cases, if you are using a multi-threaded license of Integration Engine on a multi-processor machine and receive a random TOC error followed by a core dump, try using an alternate Solaris threads library as outlined below:

Sample error messages:

### Cannot allocate space for TOC object entry for container "ActionParameter1"

### ID seed value missing in TOC object 1 in container "Structure2"

### Total container size value missing in TOC object 1 in container "AppField14"

The environment variable LD_LIBRARY_PATH can be set as follows to bind Integration Engine at runtime to the alternate threads library:

export LD_LIBRARY_PATH=/opt/lib/lwp:$LD_LIBRARY_PATH

For more information, see the Solaris "libthread" manpage.

Useful Links

Technical Support

Pervasive Software strives to ensure easy and successful product installation and operation.

If you encounter problems not covered in this document, call Pervasive Support at 1-800-287-4383.

Disclaimer

PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT.

PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS.

© Copyright 2006 Pervasive Software Inc.

All Rights Reserved.

Pervasive Software Inc.
http://www.pervasive.com
12365 Riata Trace Pkwy, Bldg B
Austin, TX 78727 USA
Voice: (512) 231-6000
Fax: (512) 231-6010
Online Pervasive Contacts

*** END OF README ***