Welcome to Data Integrator 9.0.3. This document contains the most up-to-date information for running this product on Solaris systems and may supersede that in the product documentation. It covers the following topics:
The following hardware and software is needed for a minimum and preferred installation:
Note The above are recommended system requirements for satisfactory operation. For maximum performance, make sure that physical memory meets the requirements of the local system and all applications.
The installation creates a Groupid called pvsw, under which djengine runs. The pvsw Groupid permissions are 644. Transformations and resulting files run by a user are owned by the user who created them.
Review the following checklist before installing Integration Engine:
java -version
pkgrm Engineversion
The license file to use for your solution is provided by your Pervasive sales representative. This license .slc file determines which integration products can be used. If you need to update features for your existing installation, contact your sales representative.
mount -F cdfs /dev/cddevice /cdrom
For /dev/cddevice, use your CD device name.
gunzip dje900-solaris-version.tar.gz
tar xvf dje900-solaris-version.tar
dje900-solaris-version.sh
After installing, apply the license. See “To Apply the License File.”
mkdir /mytmp
cp dje900-solaris-version.tar.gz /mytmp
For version, use the values from the .tar.gz file name.
cd /mytmp
gunzip dje900-solaris-version.tar.gz
tar xvf dje900-solaris-version.tar
dje900-solaris-version.sh
After installing, apply the license. See “To Apply the License File.”
Use these steps to apply the default license file. If you do not have one, see “Obtain a license file.”
/opt/PervasiveSoftware/IntegrationEngineversion/license
chmod 644 /opt/PervasiveSoftware/IntegrationEngineversion/license/cosmos.slc
Note For information on how to use License Manager to access future license files, see “Managing License Files on Unix” in the Getting Started Guide.
To ensure that Integration Engine is set up correctly, follow these steps after installation:
If the security settings applied during installation are not appropriate for your environment, you can revert to your previous permissions by executing the following commands as root:
chmod 755 /opt/PervasiveSoftware/IntegrationEngineversion/djengine
chmod 777 /opt/PervasiveSoftware/IntegrationEngineversion/Plug-Ins
chmod 777 /opt/PervasiveSoftware/IntegrationEngineversion/lookup
chmod 777 /opt/PervasiveSoftware/IntegrationEngineversion/eaa
chmod 777 /opt/PervasiveSoftware/IntegrationEngineversion/jars
chmod 777 /opt/PervasiveSoftware/IntegrationEngineversion/license
The Unix security feature for the integration platform is now disabled.
This section lists 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 Java, 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: You do not have administrative privileges for the machine. A root user ID and password are 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 obtain an updated license. After implementing the new license, attempt to install again. For information on how to use License Manager to access your new license file, see “Managing License Files on Unix” in the Getting Started Guide.
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 environment variable. 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 run time.
Two versions of the Oracle8 connector are included to support two versions of Oracle8. The djoci8.8.0.5.so connector works with all Oracle 8.0.x client installations; the djoci8.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 djoci8.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 djoci8.8.0.5.so djoci8.so
To enable Oracle 8.1.x support, type the following command in the Integration Engine installation directory:
cp djoci8.8.1.5.so djoci8.so
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 djodbc3.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 ODBC drivers from other vendors. The IODBC enabled shared library is named djodbc3.iodbc.so and the Data Direct Technologies shared library is named djodbc3.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 djodbc3.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 djodbc3.iodbc.so djodbc3.so
To reenable Data Direct driver manager support, type the following command in the Integration Engine installation directory:
cp djodbc3.datad.so djodbc3.so
In some rare cases, if you are using a multithreaded license of Integration Engine on a multiprocessor machine and receive a random TOC error followed by a core dump, try using an alternate Solaris threads library by running the following command:
/usr/bin/crle -u -l /opt/PervasiveSoftware/IntegrationServerSDKversion/
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"
For more information, see the Solaris "libthread" man page.
Integration Engine does not currently support Solaris 10 containers.
If you encounter problems not covered in this document, see the file contact.htm with the product documentation under /help/pdf.
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 2008 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 ***