Integration Manager 2.0 - Readme
General Release - June 2008

Contents

Welcome to Integration Manager 2.0. This document contains the most up-to-date information about the product and may supersede that in the product documentation. It covers the following topics:

This document may be updated after the product release. Download the latest version from Product Updates under Support at the Pervasive web site.

Introduction

Version 2.0 delivers improved features over the previous release. Your license enables the features that you can use, so you may find documentation for features that you have not purchased.

The Integration Manager 2.0 server is supported on Windows XP, 2003 Server, and Red Hat Enterprise Linux 5. The Integration Manager 2.0 client is supported on Windows XP and 2003 Server. Supported browsers include Internet Explorer 6 and 7.

New Features and Enhancements

This release of Integration Manager provides improvements in the following areas:

Quality Improvements

This release includes the following features and enhancements:

Documentation

The following documents have been significantly revised:

Upgrading and Installing Integration Manager

If you do not have Integration Manager installed, skip to Installing Integration Manager 2.0.

These release notes cover the following Integration Manager and database combinations. If yours is not listed, contact Pervasive Support.

Integration Manager Version
Database Version
1.4
Pervasive Postgres 8.0.3
1.6
Pervasive Postgres 8.0.3
1.6
PostgreSQL 8.0.14

The upgrade of Integration Manager to version 2.0 consists of several tasks which must be performed in sequence:

  1. Removing Integration Manager 1.4 or 1.6
  2. Installing Integration Manager 2.0
  3. Migrating Your Data

Removing Integration Manager 1.4 or 1.6

Before installing Integration Manager 2.0, you must first remove 1.6. This applies to Windows only.

To remove Integration Manager 1.4 or 1.6

  1. Shut down the Pervasive Postgres or PostgreSQL, Integration Server, and Integration Manager services.
  2. From Windows Add or Remove Programs, select Pervasive Integration Manager and click Remove.
  3. Remove any remaining directories or files in C:\Pervasive\IntegrationManager.

Installing Integration Manager 2.0

To install Integration Manager 2.0 on Windows

  1. Log on to the machine as a user with local administrator rights.
  2. If you have not already done so, do one of the following:
    • Insert the installation CD into the appropriate drive and click Integration Manager. If the splash screen does not appear when you insert the CD, select Start 4 Run, enter drive:\IntegrationManager.exe (where drive is the letter of your CD-ROM), and click OK.
    • Download the Integration Manager 2.0 executable file from Pervasive, then double-click the file icon.
  3. Once the splash screen appears, click Integration Manager.
  4. Read the Important Notice and close the window.
  5. In the installation wizard Welcome window, click Next.
  6. Read the license agreement and click Yes if you agree.
  7. Accept the default installation location or browse for another.
  8. When the installation process ends, click Finish to close the window and exit.

    9. Note  The path and file name for Integration Manager cannot contain any spaces. Therefore, if you decide to change the installation path or folder name, do not insert any spaces or the program will not work properly.

To install Integration Manager on Linux

  1. Log on to the machine as root.
  2. If you have not already done so, do one of the following:
    • Insert your installation CD into the appropriate drive. Mount the CD and run the installer. Use your own CD device name instead of /dev/cdrom.

      • mount /dev/cdrom/ /mnt/cdrom

      cd /mnt/cdrom

      IntegrationManager-linux-<version>-<date>.sh

    • Download the Integration Manager 2.0 installation file from Pervasive and copy it into a temporary directory. From the temporary directory, run the following command:

      • IntegrationManager-<version>-<date>.sh

  3. Read the license agreement and type Yes to accept. The software is installed.
  4. After installation, add any user who will start and stop Integration Manager on Linux to the pvsw group. The pvsw group was created on installation.

    5. gpasswd -a <username> pvsw

    Note  Users who work with the Integration Manager server on Linux must have read and write permission for all Integration Manager files and subdirectories. They must also have execute permissions for the scripts in the Integration Manager /bin directory.

Migrating Your Data

After installing or upgrading Integration Manager, migrate your data. If you are using Postgres 8.0.3 or PostgreSQL 8.0.14 on Windows or Linux, you must run a script to carry your data forward.

The following arguments are required when running the script.

Argument
Description
Host
Host name or IP address of the PostgreSQL or Postgres server
Port
Port where the PostgreSQL or Postgres server listens
Database name
Name of Integration Manager database
User name
User name (you must have read access to PostgreSQLor Postgres)
Password
Password corresponding to specified user name

To upgrade from Postgres 8.0.3 or PostgreSQL 8.0.14

  1. Log on to the machine as a user with local administrator rights.
  2. Start the Postgres or PostgreSQL service.
  3. From a command prompt, navigate to the following directory:

    4. Windows—C:\Pervasive\IntegrationManager\im\bin

    Linux—/opt/PervasiveSoftware/IntegrationManager/im/bin

  4. Type migrateData.bat or migrateData.sh followed by the argument values. For example:

    5. migrateData.bat dbhost 5432 IMDatabase tester 1234

    A message appears telling you whether the migration was succesful.

  5. Continue setting up Integration Manager. See “Configuring Integration Manager” in the Integration Manager Installation and Configuration Guide.

After you complete the configuration steps, log on to Integration Manager and verify your data is there by browsing the various tabs.

Note  When using Integration Manager 2.0 , you can use the same service name and password, superuser password, and port that you used with your previous database.

Known Issues

The following items describe known issues in the current release:

Error When Shutting Down the Integration Manager Service on Linux

Issue: On Red Hat, the following error displays when a user shuts down the Integration Manager service: “INFO: Failed shutdown of Apache Portable Runtime”. CR 35540.

Workaround: None.

Integration Manager Hangs When Server Quits While Running a Scheduled Process

Issue: Integration Manager hangs instead of displaying an accurate error message when Integration Server quits while running a scheduled process. CR 35473

Workaround: None.

Integration Manager Incorrectly Reports Status of Deployment to Read-only Repository

Issue: When a user attempts to deploy a package to a read-only repository, Integration Manager states that the deployment is successful when it is not. CR 35543.

Workaround: Ensure that the repository is writable before attempting to deploy packages to it.

Unable to Change a Recurring Event to a One-time Event

Issue: When a user attempts to change a recurring event to a one-time event, the change is not saved. CR 35549.

Workaround: The user must create a new one-time event.

Inetgration Manager Monitor Shows Incorrect Information for Integration Server on Solaris

Issue: When monitoring a running Integration Server on Solaris, Integration Manager shows the status as idle. CR 35677.

Workaround: None.

Integration Manager Does Not Provide Status Details on Home Page

Issue: The View Status link on the Home page in Integration Manager does not show the details of the process that is running. CR 35476.

Workaround: None.

Database Migration Script Error is Misleading

Issue: The script, migrateData.bat or migrateData.sh, to migrate data from PostgreSQL may return the following error: Migration from PostgreSQL to a new Derby database was not successful. Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. CR 35372.

Workaround: Ensure that the PostgreSQL database is started, then run the script again.

Deployed Package Does Not Show Up in Scheduling Tab

Issue: When using two instances of Integration Manager to schedule a package to run on one Integration Server, one instance of Integration Manager may not list the package on the Scheduling tab. The user may have to deploy the package again, even if the Deploy tab states that the package already exists. CR 35531.

Workaround: None.

Deleted Scheduled Event May Still Appear in a Separate Integration Manager Instance

Issue: When a user deletes a scheduled event, the event may still appear to a different user running another instance of Integration Manager. CR 35488.

Workaround: None.

Execution of .djar Files Does Not Require Specific Role

Issue: Any user can execute packages. CR 35385.

Workaround: None.

Execution of .djar Files Does Not Require Specific Role

Issue: Any user can execute packages. CR 35385.

Workaround: None.

Integration Manager Opens in Help Window

Issue: When a user logs out of Integration Manager while running the help, the Integration Manager log in page opens in the help window. CR 35496.

Workaround: None.

Integration Manager Launches Multiple Browser Windows

Issue: When monitoring multiple servers with multiple browsers, Integration Manager launches additional browsers instead of refreshing an open one. CR 35721.

Workaround: None.

Overlapping Schedules Cause Some Processes to Not Start

Issue: If the number of processes scheduled to run simultaneously exceeds the number of engines available, the additional processes are marked as “Not Started” and are never run. CR 35775.

Workaround: Ensure more engines are configured to run than processes. Consider each instance of Integration Manager that may be sending processes to a server. A user can edit the number of engines in the Max Engine Count field under the Manage tab.

Documentation Notes

This section provides information regarding the documentation included with Integration Manager.

Documentation is provided in two formats:

PDF and JavaHelp files are installed with the product.

Frequently Asked Questions

How do I install a license file for Integration Manager?

To install a license file

  1. Copy your license file to a directory on your system.
  2. Start Integration Manager.
  3. Open a supported browser and log on to Integration Manager.
  4. Click the Configure tab, then the Properties tab.
  5. Enter the full path to the license file in the LICENSE_PATH box and save it.

What to Do Next

Once you have successfully installed Pervasive Integration Manager using Integration Manager Installation and Configuration Guide, read the Integration Manager User’s Guide.

Useful Links

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