TIBCO iProcess Technology Plug-ins Installation

TIBCO iProcess Technology Plug-ins Installation
TIBCO iProcess® Technology
Plug-ins
Installation
Software Release 11.3
December 2011
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, The Power of Now, TIBCO Runtime Agent, TIBCO Administrator, TIBCO Hawk, TIBCO Rendezvous,
TIBCO Adapter, TIBCO Enterprise Message Service, TIBCO SmartSockets, TIBCO Designer, TIBCO
BusinessWorks, and TIBCO iProcess Engine are either registered trademarks or trademarks of TIBCO Software
Inc. in the United States and/or other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 2007-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Changes From the Previous Issue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Release Notes and Readme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
TIBCO iProcess User Documentation Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiii
xiii
xiii
xiii
Chapter 1 Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Pre-Installation Tasks Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Check For Any Late Breaking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Install your Database Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Set Up SQL Server Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Set Up Character Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Export Existing JMS Provider Configuration if Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Back up Your System if Re-installing or Repairing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Choose Your Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2 Introduction to the Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Product Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installation with More Than One iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Preparing to Run the Setup Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
TIBCO iProcess Technology Plug-ins Installation
iv
| Contents
Chapter 3 Using the GUI Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About the GUI Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Running the GUI Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 4 Using the Console Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Installing Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 5 Using the Silent Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Installing Using Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating a Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Password Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing the Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Response File Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
50
51
52
53
54
Chapter 6 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring JNDI Password Encryption (Upgrade Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Using the $SWDIR/eaijava/scripts/env.sh Script (UNIX Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Run the SQL Server Surface Area Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Manually Remove the ISMP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configure the XML Step Definitions Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Chapter 7 Un-installing the TIBCO iProcess Technology Plug-ins . . . . . . . . . . . . . . . . . . . . . . 67
Un-installing TIBCO iProcess Technology Plug-ins From Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Un-installing the iProcess Engine-Based Plug-ins from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Un-installing the BusinessWorks iProcess Plug-in from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Un-installing TIBCO iProcess Technology Plug-ins From UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Un-installing the iProcess Engine-Based Plug-ins from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Un-installing the BusinessWorks iProcess Plug-in from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Appendix A Installation Data Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
General Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Database Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Database Configuration Dialog (continued) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configure the JMS Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
iProcess BusinessWorks Server Plug-in Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Web Application Server Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
JMS Environment Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
TIBCO iProcess Technology Plug-ins Installation
Contents v
|
Appendix B Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Database Connection Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
iProcess Engine Process Sentinels Fail to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
91
92
93
Background Core Dumps on AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
The Setup Program Hangs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Oracle Services May Be Required in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Missing frameworkconfig.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
EAI Java Server Plug-in Fails to Load Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
CPU Usage is Too High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
JMS Connection Test Returns Fail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Console Mode Installation Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
JMS Provider Configuration is Lost in an Upgrade Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Appendix C Java Character Encoding Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Which Java Version/Encoding Set Combination Do I Need?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Obtaining an Appropriate Java Version/Encoding Set Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Java Version/Encoding Set Combinations Supplied by the iProcess Engine . . . . . . . . . . . . . . . . . . . . . . .
Using a Java Version/Encoding Set Combination That is Already Installed . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Required Java Version/Encoding Set Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
105
106
106
Using the Required Java Version/Encoding Set Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Solaris or Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
TIBCO iProcess Technology Plug-ins Installation
vi
| Contents
TIBCO iProcess Technology Plug-ins Installation
| vii
Preface
This software is available on multiple operating systems. However, not all
operating system platforms for a specific software version are released at the
same time. Please see the readme.txt file for the availability of this software
version on a specific operating system platform.
Topics
•
Changes From the Previous Issue, page viii
•
Related Documentation, page ix
•
Documentation Conventions, page xi
•
Connecting with TIBCO Resources, page xiii
TIBCO iProcess Technology Plug-ins Installation
viii
| Changes From the Previous Issue
Changes From the Previous Issue
Major changes from the information presented in the previous issue of this
manual are as follows:
•
In previous releases, database drivers were provided as part of the TIBCO
iProcess Technology Plug-ins product. From this version, database drivers are
no longer provided and must be installed separately. See Install your Database
Driver on page 4.
•
The database drivers that you can use with this product are now explicitly
specified. See Databases and Database Drivers on page 22.
•
This release of TIBCO iProcess Technology Plug-ins supports Windows 7
Professional. See Operating System on page 20.
•
This release of TIBCO iProcess Technology Plug-ins is validated against
TIBCO iProcess Engine versions 11.1.3 and 11.3. See TIBCO iProcess Engine on
page 23.
•
Only Java 6 is supported in this release. Support for Java 5 has been
discontinued. See Java Runtime Environment and Java Virtual Machine on
page 24.
•
References to unsupported platforms and operating systems have been
removed from this manual.
•
The database configuration information is now split over two screens in the
GUI and Console installers. See Database Configuration Dialog on page 77
and Database Configuration Dialog (continued) on page 79.
•
The process of specifying configuration information for the JMS provider has
changed. See Configure the JMS Provider on page 82.
•
Using unencrypted database passwords in the silent installer is no longer
supported. See Password Encryption on page 51.
•
The XML step definitions for iProcess BusinessWorks Connector invocations
are cached, and you can edit the cache size. See Configure the XML Step
Definitions Cache on page 66.
TIBCO iProcess Technology Plug-ins Installation
Preface ix
|
Related Documentation
You can find more information about TIBCO iProcess Technology Plug-ins from
the following sources:
Release Notes and Readme
Before you install the TIBCO iProcess Technology Plug-ins you should read the
Release Notes and Readme supplied with the software. The Release Notes
contain the following version and platform-specific information:
•
any restrictions or known issues that apply.
•
any fixes that have been made.
•
any other information that was not available when this guide was published.
If you are installing from physical media, you can find the Release Notes and
Readme in the Docs folder.
If you are installing from CD-ROM on UNIX, you can find the Release Notes and
Readme in the mount_point/docs/ directory, where mount_point is the location at
which your CD-ROM is mounted.
If you are installing from a network server, you should ask your network
administrator where the Release Notes and Readme are stored.
TIBCO iProcess User Documentation Library
TIBCO iProcess Suite® user documentation is supplied as Adobe Acrobat files in
the TIBCO iProcess Suite User Documentation Library. This provides the entire
documentation set for TIBCO iProcess products. The documentation can also be
accessed from TIBCOmmunity. See Connecting with TIBCO Resources on
page xiii for details.
See the following guides for more information concerning the TIBCO iProcess
Technology Plug-ins:
•
TIBCO iProcess® Java Plug-in User’s Guide, which explains how to define and
use EAI Java steps in your iProcess procedures. EAI Java steps can be
customized to perform the necessary business actions you require in your
procedure (such as calling methods in Enterprise Java Beans or simply
manipulating data via a Java object). The TIBCO iProcess Java Plug-in
software consists of a client plug-in (which is part of the iProcess Workspace
Plug-ins), a server plug-in (which is part of the iProcess Technology Plug-ins),
and an SDK.
TIBCO iProcess Technology Plug-ins Installation
x
| Related Documentation
•
TIBCO iProcess® BusinessWorks™ Connector User’s Guide, which explains how
to use the iProcess BusinessWorks Connector plug-ins, an efficient and easy to
use interface between TIBCO BusinessWorks™ and the TIBCO iProcess®
Engine. The iProcess BusinessWorks Connector consists of a client plug-in
(which is part of the iProcess Workspace Plug-ins) and a server plug-in (which
is part of the iProcess Technology Plug-ins).
•
TIBCO iProcess® Conductor User’s Guide, which provides instructions on using
the TIBCO iProcess Conductor user interface to orchestrate execution plans,
create process components, amend orders, and so on.
•
TIBCO Business Studio® iProcess Developer’s Guide, which provides information
on configuring and using the EAI POJO Plug-in.
•
TIBCO iProcess® Modeler - Integration Techniques guide, which explains how to
use EAI steps in your procedures to control updates to external systems and
iProcess case data under transaction control.
TIBCO iProcess Technology Plug-ins Installation
Preface xi
|
Documentation Conventions
Although this guide covers installing on both Windows and UNIX systems, the
Windows convention of using a back slash in directory paths is used in some
examples (for example, d:\swserver\liberty). UNIX path names are
occasionally shown explicitly, using forward slashes as separators, where a
UNIX-specific example or syntax is required.
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
ENV_NAME
TIBCO products are installed into an installation environment. A product
installed into an installation environment does not access components in other
installation environments. Incompatible products and multiple instances of the
same product must be installed into different installation environments.
TIBCO_HOME
An installation environment consists of the following properties:
•
Name Identifies the installation environment. This name is referenced in
documentation as ENV_NAME. On Microsoft Windows, the name is
appended to the name of Windows services created by the installer and is a
component of the path to the product shortcut in the Windows Start > All
Programs menu.
•
code font
Path The folder into which the product is installed. This folder is referenced
in documentation as TIBCO_HOME.
Code font identifies commands, code examples, filenames, pathnames, and
output displayed in a command window. For example:
Use MyCommand to start the foo process.
bold code
font
Bold code font is used in the following ways:
•
In procedures, to indicate what a user types. For example: Type admin.
•
In large code samples, to indicate the parts of the sample that are of
particular interest.
•
In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
TIBCO iProcess Technology Plug-ins Installation
xii
| Documentation Conventions
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
italic font
Italic font is used in the following ways:
Key
combinations
•
To indicate a document title. For example: See TIBCO ActiveMatrix
BusinessWorks Concepts.
•
To introduce new terms For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
•
To indicate a variable in a command or code syntax that you must replace.
For example: MyCommand PathName
Key name separated by a plus sign indicate keys pressed simultaneously. For
example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after the
other. For example: Esc, Ctrl+Q.
The note icon indicates information that is of special interest or importance, for
example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply
the information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for example,
data loss or corruption if certain steps are taken or not taken.
TIBCO iProcess Technology Plug-ins Installation
Preface xiii
|
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts, a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to http://www.tibcommunity.com.
How to Access All TIBCO Documentation
After you join TIBCOmmunity, you can access the documentation for all
supported product versions here:
http://docs.tibco.com/TibcoDoc
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, please
contact TIBCO Support as follows.
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
TIBCO iProcess Technology Plug-ins Installation
xiv
| Connecting with TIBCO Resources
TIBCO iProcess Technology Plug-ins Installation
|1
Chapter 1
Pre-Installation Tasks
This chapter describes the tasks that you need to perform before you run one of
the installers to install TIBCO iProcess Technology Plug-ins. Some of these tasks
are database-specific.
Topics
•
Pre-Installation Tasks Checklist, page 2
•
Check For Any Late Breaking Information, page 3
•
Set Up SQL Server Authentication, page 5
•
Set Up Character Encoding, page 7
•
Export Existing JMS Provider Configuration if Upgrading, page 8
•
Back up Your System if Re-installing or Repairing, page 9
•
Choose Your Installer, page 10
TIBCO iProcess Technology Plug-ins Installation
2
| Chapter 1
Pre-Installation Tasks
Pre-Installation Tasks Checklist
The following table provides a checklist of the different tasks that you must or
may need to do before installing. The table shows:
•
affected plug-in(s)
•
the section to refer to for more detailed information about a particular task.
You may want to print this table as a useful quick reference when carrying out the
pre-installation tasks. The Done? column in the table provides a place for you to
tick off tasks that have been done.
Task
Plug-in
See
All
page 3
2. Install your Database Driver
All
page 4
3. Set Up SQL Server Authentication
•
iProcess Java Server Plug-in
•
iProcess BusinessWorks
Server Plug-in
•
iProcess Java Server Plug-in
•
iProcess BusinessWorks
Server Plug-in
5. Export Existing JMS Provider
Configuration if Upgrading
•
iProcess BusinessWorks
Server Plug-in
6. Choose Your Installer
All
1. Check For Any Late Breaking
Information
4. Set Up Character Encoding
TIBCO iProcess Technology Plug-ins Installation
page 5
page 7
page 8
page 10
Done?
Check For Any Late Breaking Information 3
|
Check For Any Late Breaking Information
Status
Description
Procedure
If you are...
This task is...
Installing a new plug-in
Required
Upgrading an existing plug-in
Required
Re-installing or repairing an existing plug-in
Required
Re-configuring an existing plug-in
N/A
Before you install a plug-in you should check if there are any restrictions, known
issues or other late-breaking information that may affect your installation, but
that was not known about when this installation guide was published.
To check for late-breaking information:
1. Read the Release Notes and Readme documents that are supplied with the
plug-in software.
If you are installing from physical media, you can find these files in the docs
directory on the media.
If you are installing from a network server, you should ask your network
administrator where these files are stored.
2. Consult the “Late Breaking News” section of the TIBCO Support Web, at
(http://www.tibco.com/services/support/support_web.jsp).
TIBCO iProcess Technology Plug-ins Installation
4
| Chapter 1
Pre-Installation Tasks
Install your Database Driver
Status
Description
If you are...
This task is...
Installing a new plug-in
Required
Upgrading an existing plug-in
Required
Re-installing or repairing an existing plug-in
N/A
Re-configuring an existing plug-in
N/A
This pre-installation task applies only if:
•
you are installing TIBCO iProcess Technology Plug-ins for the first time, or
•
you are upgrading TIBCO iProcess Technology Plug-ins and you have been
using a database driver other than those referred to in Databases and
Database Drivers on page 22, or of an older version.
Procedure
1. Checkthe table in Databases and Database Drivers on page 22 to confirm what
database driver that you need.
2. Install it, following the instructions supplied with the product.
3. Keep a record of the location where you have installed the driver, and the
authentication information required, because you will need to specify this
later. See Database Configuration Dialog on page 77 and Database
Configuration Dialog (continued) on page 79 for the information you will
need.
TIBCO iProcess Technology Plug-ins Installation
Set Up SQL Server Authentication 5
|
Set Up SQL Server Authentication
Status
Description
If you are...
This task is...
Installing a new plug-in
Required
Upgrading an existing plug-in
Required
Re-installing or repairing an existing plug-in
N/A
Re-configuring an existing plug-in
N/A
This pre-installation task applies only if:
•
you are installing an iProcess Java Server Plug-in or an iProcess
BusinessWorks Server Plug-in, and
•
you are using SQL Server and your usernames authenticate using Windows
authentication. The iProcess Java Server Plug-in and iProcess BusinessWorks
Server Plug-ins will only install with a username that authenticates with SQL
Server authentication. This means that if you are using Windows
authentication, you must do the following:
Procedure
1. Create a new username. This must either have system administrator status, or
else must have Execute permission for the master database and also for the
following SQL Server Extended Stored Procedures:
SP_OACreate
SP_OASetProperty
SP_OAMethod
SP_OAGetProperty
SP_OADestroy
2. Set this username to use SQL Server authentication.
3. Set the default database for this username to the iProcess Engine Database.
TIBCO iProcess Technology Plug-ins Installation
6
| Chapter 1
Pre-Installation Tasks
4. When running the Setup program, remember to:
a. From the Database Configuration Dialog, select SQL Server (SQL
Authentication) from the Database Type drop-down list.
b. From the Database Configuration Dialog, enter the following:
— in the User ID and Password boxes, enter the username and password of
the user you have created that uses SQL Server authentication.
— in the Schema Owner box, enter the username of the iProcess Engine
Tables Owner. By default, this is swpro.
TIBCO iProcess Technology Plug-ins Installation
Set Up Character Encoding 7
|
Set Up Character Encoding
Status
Description
If you are...
This task is...
Installing a new plug-in
Required
Upgrading an existing plug-in
Required
Re-installing or repairing an existing plug-in
N/A
Re-configuring an existing plug-in
N/A
This pre-installation task applies only if you are installing an iProcess Java Server
Plug-in or an iProcess BusinessWorks Server Plug-in.
You need to find out your encoding details for the TIBCO iProcess Java Server
Plug-in or iProcess BusinessWorks Server Plug-in so that you can specify the right
character encoding on the Server Plug-in General Configuration Dialog.
From iProcess Engine version 11.1, the iProcess Suite supports Unicode UTF-8,
and using this is recommended in most cases. However, if you have not
configured iProcess Engine to support UTF-8 (for example if upgrading an
existing installation), the TIBCO iProcess Workspace (Windows) sends data to
iProcess Engine in the default encoding used by the host operating system. On
International English versions of Windows this is typically Cp1252.
The TIBCO iProcess Java Server Plug-in and iProcess BusinessWorks Server
Plug-in need the character encoding specification to correctly translate data
formatting to and from Unicode. Please note the following:
•
It is not possible to set the encoding to more than one encoding set — support
for multiple encoding sets across TIBCO iProcess clients connected to a single
iProcess Engine is not permitted in this release.
•
When passing XML data, including for example the Euro symbol, care must
be taken with respect to the encoding used within the XML document and the
XML editor used. (The Euro symbol in UTF-8 is represented as “€” when
viewed in a non Unicode-compliant editor.)
To configure the iProcess Java Server Plug-in to use UTF-8 encoding, set
defaultEncoding=UTF-8 in the $SWDIR/eaijava/encoding.properties file.
For more information about iProcess Engine’s support for Unicode UTF-8 and
other globalization options, see the chapter "Using the TIBCO iProcess Suite in a
Multilingual Environment" in the TIBCO iProcess Engine Architecture Guide.
TIBCO iProcess Technology Plug-ins Installation
8
| Chapter 1
Pre-Installation Tasks
Export Existing JMS Provider Configuration if Upgrading
Status
Description
If you are...
This task is...
Installing a new plug-in
Not required
Upgrading an existing plug-in
Recommended
Re-installing or repairing an existing plug-in
Recommended
Re-configuring an existing plug-in
Recommended
If you are upgrading the iProcess BusinessWorks Server Plug-in, you should
export your existing JMS provider configuration information. This is
recommended in all cases as a backup measure.
However, the information is preserved as part of the upgrade process. Therefore,
you only need to re-import the JMS provider configuration in the case of
something going wrong with the upgrade.
The import procedure is described in the troubleshooting instructions — see JMS
Provider Configuration is Lost in an Upgrade Error on page 102.)
Procedure
To export your existing JMS provider configuration:
1. Make sure the iProcess Engine is running.
2. Start the JMS Administration Utility:
— From UNIX, navigate to the $SWDIR/jmsadmin directory and enter the
following command:
./jmsadmin.sh
— From Windows, click Start > Programs > TIBCO iProcess Server
(Windows) > JMS Administration Utility.
3. Click Export. The Open dialog is displayed.
4. In the File Name box, type the name of the file where you want to save the
JMS provider configuration information. The file can be saved in any location.
5. Click Save. The JMS provider configuration information is exported.
For more information about managing JMS, see the TIBCO iProcess BusinessWorks
Connector User’s Guide.
TIBCO iProcess Technology Plug-ins Installation
Back up Your System if Re-installing or Repairing 9
|
Back up Your System if Re-installing or Repairing
Status
Description
If you are...
This task is...
Installing a new plug-in
Not required
Upgrading an existing plug-in
Not required
Re-installing or repairing an existing plug-in
Recommended
Re-configuring an existing plug-in
Recommended
If you are performing a “Re-install, repair,...” type of installation, and you have
installed any patches or hot fixes since the previous major version was installed,
the updates installed by those patches or hot fixes will be lost. TIBCO therefore
recommends that you backup your system before performing this type of
installation and re-apply the patches or hot fixes after the installation is complete..
In addition any changes that you have made to the log4j.properties file will also
be lost unless you back up that file and restore it after installation is complete.
TIBCO iProcess Technology Plug-ins Installation
10
| Chapter 1
Pre-Installation Tasks
Choose Your Installer
Status
Description
Procedure
If you are...
This task is...
Installing a new component
Required
Upgrading an existing component
Required
Re-installing or repairing an existing component
Required
Re-configuring an existing component
Required
The TIBCO iProcess Technology Plug-ins can be installed in any of the following
ways:
•
Graphical User Interface (GUI)
•
Console
•
Silent
For a description of each of these methods, see Installation Modes on page 19.
After deciding which of these methods to use, refer to the appropriate chapter, as
follows:
— Using the GUI Installer on page 29
— Using the Console Installer on page 39
— Using the Silent Installer on page 49
TIBCO iProcess Technology Plug-ins Installation
| 11
Chapter 2
Introduction to the Installation Process
This chapter provides an overview of the installation program for the TIBCO
iProcess Technology Plug-ins.
Topics
•
Product Overview, page 12
•
Installer Overview, page 17
•
System Requirements, page 20
•
Installation with More Than One iProcess Engine, page 27
•
Preparing to Run the Setup Program, page 28
TIBCO iProcess Technology Plug-ins Installation
12
| Chapter 2
Introduction to the Installation Process
Product Overview
The TIBCO iProcess Technology Plug-ins include the following individual
plug-ins:
You can display a list of the plug ins that are registered on your TIBCO iProcess
Engine by running sweaireg LIST. (See the TIBCO iProcess Administrator's Guide
for more details about sweaireg.) However, note that the iProcess BusinessWorks
Plug-in is not displayed in this list.
•
iProcess® Java Server Plug-in- This plug-in enables the iProcess Engine to
process EAI Java steps that have been added to the iProcess procedure.
When installing this plug-in, you must install it on the same machine as the
TIBCO iProcess Engine.
Also note that when you install the iProcess Java Server Plug-in, the EAI POJO
(Plain Old Java Object) plug-in is installed at the same time. This plug-in can
be configured with a properties file supplied with the iProcess Technology
Plug-ins, but is used only via TIBCO Business Studio™. For more information
about configuring and using the EAI POJO plug-in, see the TIBCO Business
Studio™ Process Developer's Guide.
•
iProcess BusinessWorks™ Server Plug-in - This plug-in provides the
communication mechanism that allows the engine to make calls to TIBCO
BusinessWorks.
When installing this plug-in, you must install it on the same machine as the
TIBCO iProcess Engine.
Note that the iProcess BusinessWorks Plug-in is dependent on the iProcess
Java Server Plug-in — that is, if you install the TIBCO iProcess BusinessWorks
Plug-in, you must also install the TIBCO iProcess Java Server Plug-in. Note
also that the iProcess BusinessWorks Plug-in is not displayed in the list of
plug-ins registered on your TIBCO iProcess Engine.
•
BusinessWorks™ iProcess® Plug-in - This plug-in provides a set of resources
that allow a TIBCO BusinessWorks process definition to communicate with
the TIBCO iProcess Engine.
The BusinessWorks iProcess Plug-in includes facilities that enable you to
create a form using TIBCO BusinessWorks™ FormBuilder, and then to
associate that form with a step in an iProcess procedure. Resources and
activities connected with forms design, which in previous versions of this
TIBCO iProcess Technology Plug-ins Installation
Product Overview 13
|
product were supplied on the iProcessForms palette, are included on the
iProcess palette.
Note that from version 11.3, FormBuilder forms are no longer supported. The
functionality is still included in this guide for the convenience of existing
users.
When installing this plug-in, you must install it on the same machine as
TIBCO BusinessWorks.
Also note that this plug-in cannot be installed at the same time as any of the
other plug-ins in the TIBCO iProcess Technology Plug-ins installer. That is, it
must be installed separately — if you want to install the BusinessWorks
iProcess Plug-in and one or more of the other plug-ins, you must run the
installer twice.
•
iProcess® Conductor Server Plug-ins - These consist of the following
plug-ins:
— TIBCO iProcess® Conductor Order Server Plug-in - This plug-in provides
an interface that notifies the TIBCO iProcess Conductor of the status of the
order. It also enables you to update order data from the TIBCO iProcess
Conductor in the TIBCO iProcess Engine and vice versa.
When installing this plug-in, you must install it on the same machine as the
TIBCO iProcess Engine.
Also note that there are separate versions of iProcess Conductor Order
Server Plug-in, depending on the Web Application Server you are using:
one for Oracle WebLogic (formerly BEA WebLogic) and one for JBoss.
Therefore, there are different dialogs displayed requesting configuration
information depending on which Web Application Server you specify.
— TIBCO iProcess® Conductor Orchestration Server Plug-in - This plug-in
processes the messages you define in the Orchestration step.
When installing this plug-in, you must install it on the same machine as the
TIBCO iProcess Engine.
Note that the iProcess Conductor Orchestration Server Plug-in is
dependent on the iProcess Java Server Plug-in — that is, if you install the
TIBCO iProcess Conductor Orchestration Server Plug-in, you must also
install the TIBCO iProcess Java Server Plug-in.
Also note that there are separate versions of iProcess Conductor
Orchestration Server Plug-in, depending the Web Application Server you
are using: one for Oracle WebLogic and one for JBoss. Therefore, there are
different dialogs displayed requesting configuration information
depending on which Web Application Server you specify.
TIBCO iProcess Technology Plug-ins Installation
14
| Chapter 2
Introduction to the Installation Process
•
TIBCO iProcess® XML Transform Server Plug-in - This plug-in performs
transformations on XML data.
When installing this plug-in, you must install it on the same machine as the
TIBCO iProcess Engine.
Note that the iProcess XML Transform Server Plug-in is dependent on the
iProcess Java Server Plug-in — that is, if you install the TIBCO iProcess XML
Transform Server Plug-in, you must also install the TIBCO iProcess Java
Server Plug-in.
TIBCO iProcess Technology Plug-ins Installation
Product Overview 15
|
Logging
Log files are created in the following directory when you install the TIBCO
iProcess Technology Plug-ins:
—
SWDIR\logs
where SWDIR in the directory in which the iProcess Engine was installed.
When the TIBCO iProcess Technology Plug-ins are initially installed, multiple log
files are created. These files are:
•
On UNIX systems:
— eaireg.log
— eairegerror.log
— eaiunreg.log
— eaiunregerror.log
— eaijava.identifier.log
(identifier is a unique string, for example
"eaijavaabf6c85c3ea1f88d0000004100de6f34.log")
— jmsadmin.log
— jmsadminerror.log
— TIBCOiProcessPluginsInstaller.log
And a file for each plug-in installed, for example:
— TIBCOiProcessJavaPlugInInstall.log
— TIBCOiProcessBusinessWorksPlugInInstall.log
TIBCO iProcess Technology Plug-ins Installation
16
| Chapter 2
Introduction to the Installation Process
•
On Windows systems:
— eaireg.log
— eairegerror.log
— eaiunreg.log
— eaiunregerror.log
— eaijava.identifier.log
(identifier is a unique string, for example
"eaijavaabf6c85c3ea1f88d0000004100de6f34.log")
— jmsadmin.log
— jmsadminerror.log
— swadmBGPREDICTreg.log
— swadmBGPREDICTregerror.log
— swadmBGPREDICTunreg.log
— swadmBGPREDICTunregerror.log
— swadmBGreg.log
— swadmBGregerror.log
— swadmBGunreg.log
— swadmBGunregerror.log
— swadmRPCBGreg.log
— swadmRPCBGregerror.log
— swadmRPCBGunreg.log
— swadmRPCBGunregerror.log
— TIBCOiProcessPluginsInstaller.log
And a file for each plug-in installed, for example:
— TIBCOiProcessJavaPlugInInstall.log
— TIBCOiProcessBusinessWorksPlugInInstall.log
TIBCO iProcess Technology Plug-ins Installation
Installer Overview 17
|
Installer Overview
The TIBCO iProcess Technology Plug-ins installer can be used to perform tasks
other than just to install new plug-ins on your system. When you invoke the
installer program, you are presented with the following choices for the
installation:
These choices are used to perform the following types of installation:
•
New Installation - This is used to install new TIBCO iProcess Technology
Plug-ins on your system.
Note that you can install multiple instances of the TIBCO iProcess Technology
Plug-ins. Each of the multiple plug-ins would be associated with a different
instance of the TIBCO iProcess Engine. (One of the first steps in the
installation procedure is to specify the TIBCO iProcess Engine the new plug-in
is to be associated.)
•
Re-install/Repair/Upgrade Installation - This type of installation would be
used in two scenarios:
— To “re-install/repair” an existing installation. This returns all of the
configuration settings to their original values, i.e., the values that were
specified when the plug-ins were originally installed.
Note that a consequence of this selection is that if you had installed any
patches/hot fixes since the previous major version was installed, the
updates installed by the patches/hot fixes will be lost.
— To “upgrade” the existing installation of TIBCO iProcess Technology
Plug-ins. This is used if you had previously installed version 10.7, for
instance, then want to upgrade to version 11.3. This type of installation will
present the same dialogs as a new installation (when performing a GUI
TIBCO iProcess Technology Plug-ins Installation
18
| Chapter 2
Introduction to the Installation Process
installation), although settings on the dialogs will show the settings that
were specified when the plug-ins were originally installed.
Note that if you are upgrading from a previous version you need to specify
the path to the tibjmsadmin.jar file manually. See Configure the JMS
Provider on page 82.
•
Re-configure Existing Installation - This type of installation allows you to
change some of the configuration settings that were specified in an earlier
installation. It basically presents the same dialogs as a new installation (when
performing a GUI installation), allowing you to make changes.
Note that the re-configure option does not migrate the data contained in the
iProcess database, nor does it reset nor recreate such data.
If you are installing the iProcess Java Server Plug-in, and you select either
“Re-install/Repair/Upgrade Installation” or “Re-configure Existing Installation”,
you may be asked to un-install your existing iProcess Java Server Plug-in before
proceeding.
If this situation arises, and you also have the iProcess BusinessWorks Server
Plug-in and/or the iProcess Decisions Plug-in installed, they must also be
un-installed, and, they must be un-installed in a specific order.
Make sure that you un-install these products in the following order:
1. Un-install the TIBCO iProcess Decisions Plug-in. See the TIBCO iProcess
Decisions Plug-in Installation Guide for more information.
2. Un-install the TIBCO iProcess BusinessWorks Server Plug-in and the TIBCO
iProcess Java Server Plug-in.
Run the iProcess Technology Plug-ins installation process to install the upgraded
versions of the TIBCO iProcess BusinessWorks Server Plug-in and the TIBCO
iProcess Java Server Plug-in. After upgrading, re-install the iProcess Decisions
Plug-in.
If you also have the iProcess Conductor Server Plug-ins and/or the iProcess XML
Transform Server Plug-in installed, they must also be un-installed, and, they must
be un-installed in a specific order.
Make sure that you un-install these products in the following order:
1. Un-install the TIBCO iProcess XML Transform Server Plug-in.
2. Un-install the TIBCO iProcess Conductor Server Plug-ins.
Run the iProcess Technology Plug-ins installation process to install the upgraded
versions of the TIBCO iProcess Conductor Server Plug-ins and the TIBCO XML
Transform Server Plug-in.
TIBCO iProcess Technology Plug-ins Installation
Installer Overview 19
|
Installation Modes
The TIBCO iProcess Technology Plug-ins can be installed using the following
installation modes:
•
GUI Mode - The GUI (graphical user interface) mode causes the installer to
present dialogs that allow you to make choices about product selection,
product location, and so on.
For information about installing in GUI mode, see Using the GUI Installer on
page 29.
•
Console Mode - Console mode allows you to run the installer from the
command prompt or terminal window. This is useful if your machine does not
have a graphical display environment.
For information about installing in Console mode, see Using the Console
Installer on page 39.
•
Silent Mode - Silent mode installs the plug-ins without prompting you for
information — all the information the installer needs is passed to the installer
in the form of a response file that was saved during an earlier installation.
For information about installing in Silent mode, see Using the Silent Installer
on page 49.
TIBCO iProcess Technology Plug-ins Installation
20
| Chapter 2
Introduction to the Installation Process
System Requirements
Disk Space Requirements
The following table provides the amount of disk space required for each plug-in.
Component
Minimum Disk Space
iProcess Java Server Plug-in
35 MB
iProcess BusinessWorks™ Server Plug-in
15 MB
BusinessWorks iProcess Plug-in
20 MB
iProcess Conductor Server Plug-in
15 MB
iProcess XML Transform Server Plug-in
5 MB
Software Requirements
The following subsections provide information about software requirements for
the TIBCO iProcess Technology Plug-ins.
See the TIBCO iProcess® Conductor Installation guide for further software
requirements if you are installing the iProcess Conductor Server Plug-ins.
Operating System
The TIBCO iProcess Technology Plug-ins can be installed on machines running
the following operating systems:
•
Windows XP Professional
•
Windows Vista
•
Windows 7 Professional
•
Windows Server 2003 32-bit or 64-bit
•
Windows Server 2008 32-bit or 64-bit
•
Windows Server 2008 R2
•
Sun SPARC: Solaris 8, 9, and 10
•
Sun x86: Solaris 10
TIBCO iProcess Technology Plug-ins Installation
System Requirements 21
|
•
AIX 5L (5.3), 6.1 and 7.1
•
HP Itanium: HP-UX 11i Version 2 (B.11.23) or Version 3 (B.11.31)
•
Redhat Linux 4.x ES (32-bit or 64-bit)
•
RedHat Linux 4.x AS (32-bit or 64-bit)
•
RedHat Linux Enterprise Server 5.x (32-bit or 64-bit)
•
RedHat Linux Advanced Platform 5.x (32-bit or 64-bit)
•
Novell SUSE Linux Enterprise 10.0 with Service Pack 1, 64 bit version
•
Novell SUSE Linux Enterprise 11.x, 64 bit version
See the readme.txt file for this product for applicable Service Pack levels and for
any further supported operating systems.
Also, ensure that the relevant operating system patches and fixes have been
installed for your chosen copy of Java.
Note that the installation and use of iProcess Conductor Server Plug-ins and the
iProcess XML Transform Server Plug-in is not supported on HP-UX systems.
Microsoft have discontinued standard support for Windows XP and Windows
Server 2003. (Extended support is still available, but must be purchased from
Microsoft.) TIBCO will continue to support iProcess Technology Plug-ins on these
platforms. However, if a problem with iProcess Technology Plug-ins is reported to
TIBCO Support, and the problem is traced to an unsupported operating system,
TIBCO Support will be unable to assist further with the resolution of that
problem.
TIBCO therefore recommend that you use Windows Server 2008, Windows Vista
or Windows 7 instead of Windows XP or Windows Server 2003 on any system
that runs iProcess Technology Plug-ins.
TIBCO iProcess Technology Plug-ins Installation
22
| Chapter 2
Introduction to the Installation Process
Databases and Database Drivers
You must install a suitable database driver for your database before installing
iProcess Technology Plug-ins. TIBCO iProcess Technology Plug-ins supports the
following databases:
Note that DB2 databases are not supported at version 11.3.0.
Database
Database Driver
Oracle 10g R2 release 10.2.0.4
For all Oracle versions, use the
database driver supplied with your
database.
Oracle 11g release 11.1.0.6
Oracle 11g R2 release 11.2.0.2
SQL Server 2005
SQL Server 2008
Use Microsoft SQL Server JDBC
Driver 3.0. Within that product, select
the sqljdbc4.jar file.
SQL Server 2008 R2
Microsoft have discontinued standard support for SQL Server 2005. (Extended
support is still available, but must be purchased from Microsoft.) TIBCO will
continue to support SQL Server 2005. However, if a problem with iProcess
Technology Plug-ins is reported to TIBCO Support, and the problem is traced to
the SQL Server 2005, TIBCO Support will be unable to assist further with the
resolution of that problem.
TIBCO therefore recommend that you use SQL Server 2008 instead of SQL Server
2005 on any system that runs iProcess Technology Plug-ins.
You will need to specify the driver’s location and connection parameters as part
of iProcess Technology Plug-ins installation. See Database Configuration Dialog
on page 77 and Database Configuration Dialog (continued) on page 79 for details
of the information that you will need to supply.
TIBCO iProcess Technology Plug-ins Installation
System Requirements 23
|
TIBCO iProcess Engine
The following versions of the TIBCO iProcess Engine are supported for this
version of iProcess Technology Plug-ins:
iProcess Engine Version
Validated
Compatible
11.0, 11.0.1
No
Yes
11.0.2, 11.1.x
No
Yes
11.1.3
Yes
Yes
11.3
Yes
Yes
Validated versions have been successfully tested by TIBCO for compatibility with
this version of TIBCO iProcess Technology Plug-ins. Compatible versions have not
been formally validated, but have no known incompatibilities with this version of
the product.
If you are installing either the iProcess Java Server Plug-in or the iProcess
BusinessWorks™ Server Plug-in, they must be installed on the same machine on
which a TIBCO iProcess Engine version 11.0 or newer is installed.
If you are using SQL Server and your usernames authenticate using Windows
authentication, you must have created a new username as described in Set Up
SQL Server Authentication on page 5.
If you are not using Windows authentication, you should install using the TIBCO
iProcess Engine Database owner. This username must also have the permissions
listed in Set Up SQL Server Authentication on page 5.
If you are installing the BusinessWorks iProcess Plug-in, you can connect to a
version 11.x iProcess Engine at design time.
The iProcess BusinessWorks™ Server Plug-in requires TIBCO EMS as its JMS
provider. All TIBCO iProcess Engine customers are provided with EMS licenses
enabling them to connect iProcess to other TIBCO software. However, TIBCO
EMS must be purchased separately if you want to use it to communicate with
non-TIBCO products.
TIBCO BusinessWorks
If you are installing the BusinessWorks iProcess Plug-in, it must be installed on
the same machine on which TIBCO BusinessWorks is installed. The minimum
version of BusinessWorks required is version 5.8.
TIBCO iProcess Technology Plug-ins Installation
24
| Chapter 2
Introduction to the Installation Process
Note that to install the BusinessWorks iProcess Plug-in you must be logged in
using a BusinessWorks account.
JMS Providers
The following JMS providers are supported:
JMS Provider
Validated
TIBCO EMS
6.0.1
6.1
Java Runtime Environment and Java Virtual Machine
The iProcess Java Server Plug-in and iProcess BusinessWorks Server Plug-in
require specific versions of the Java Runtime Environment (JRE) and Java Virtual
Machine (JVM). This release of the iProcess Technology Plug-ins supports Java 6
only.
TIBCO strongly recommends that you use one of the following JREs (in order of
preference) to provide the necessary Java functionality when using these plug-ins:
1. ONLY if you are using iProcess Engine Version 11.0 or later: The JRE version that
is distributed with the iProcess Engine and installed in the SWDIR\java
directory.
2. A 32-bit JRE version that TIBCO has validated for compatibility with the
iProcess Engine. For information about versions that are compatible with
Version 11.0 (or later) of the iProcess Engine, see the section entitled “Java
Runtime Environment (JRE)”, in the appropriate TIBCO iProcess Engine
Installation guide.
64-bit JRE versions are not supported.
In addition, because different JRE implementations can contain multiple JVM
libraries, you must select the correct library when you run Setup to install the
iProcess Java Server Plug-in.
If you need to use a different version of the JRE and/or JVM for any reason,
TIBCO strongly recommends that you contact TIBCO Support before doing so to
determine if the JRE you want to use is fully compatible with your version of the
iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
System Requirements 25
|
Choosing the Correct JVM
This section provides information about choosing the correct Java Virtual
Machine (JVM) when completing the Java Environment field and Java
Environment (Alternate Location) fields on the General Configuration dialog see page 75.
Different JRE implementations can contain multiple JVM libraries. You must
select the correct library required by the iProcess Java Server Plug-in, as shown in
the following table.
JRE_HOME is the directory containing the JRE that you intend to use. This JRE
must be either the version that is installed on the iProcess Engine or a version that
is compatible with it — see Java Runtime Environment and Java Virtual Machine
on page 24.
Platform
JVM
Required JVM Location
Windows
jvm.dll
JRE_HOME\bin\server
or, if this JVM is not available:
JRE_HOME\bin\client
AIX
libjvm.a
JRE_HOME/bin/classic
Sun SPARC Solaris
libjvm.so
JRE_HOME/lib/sparc/server
Sun x86 Solaris
libjvm.so
JRE_HOME/lib/i386/server
HP-UX Itanium
libjvm.so
JRE_HOME/lib/IA64N/server
Linux
libjvm.so
JRE_HOME/lib/i386/server
For example, suppose you are installing the iProcess BusinessWorks Server
Plug-in on a Version 11.0 iProcess Engine on Windows, which is installed in
C:\swserver\staffw_nod1. If you want to use a 1.6.x JRE that is compatible with
the iProcess Engine, you might specify the Java Environment directory as:
C:\j2sdk1.6.0\jre\bin\server
Choosing the Correct Java Character Encoding Set
You must ensure that you use a version of Java that provides the necessary
character encoding set support with the iProcess Technology Plug-ins.
See Appendix C, Java Character Encoding Sets, on page 103 for more information
about how to do this.
TIBCO iProcess Technology Plug-ins Installation
26
| Chapter 2
Introduction to the Installation Process
Appendix C is only relevant to installations on Windows, Solaris and Linux.
Contact Hewlett-Packard for information about character encoding set support
on HP-UX.
Contact IBM for information about character encoding set support on AIX.
TIBCO iProcess Technology Plug-ins Installation
Installation with More Than One iProcess Engine 27
|
Installation with More Than One iProcess Engine
The assumption is that the iProcess BusinessWorks Client Plug-in (delivered and
installed as part of the iProcess Workspace Plug-ins) will be used with one
instance of the iProcess Engine and iProcess BusinessWorks Server Plug-in.
This is because the introspection of the definition of a BusinessWorks step created
using the iProcess BusinessWorks Client Plug-in comes from the server, via JMX.
Therefore, the same server needs to be running for the JMX Server to be active in
order to support the client introspection requests.
The JMX Server is identified by the client_install/jmsdb.properties file, where
client_install is the location where you installed the iProcess Workspace Plug-ins.
Therefore if the client is required to connect to a different server, you must
manually amend jmsdb.properties to specify the new server, or else run the
installer selecting the Reconfigure An Existing Installation option (see page 18
for details of this option).
TIBCO iProcess Technology Plug-ins Installation
28
| Chapter 2
Introduction to the Installation Process
Preparing to Run the Setup Program
This section describes preparing to run the setup program on UNIX systems.
Before you install the iProcess Technology Plug-ins:
1. Make sure that the iProcess Background User (see Running the GUI Installer
on page 31) has:
— write permissions to the $SWDIR directory,
— a home directory.
Otherwise, the installation will fail.
2. In some UNIX systems, installation will fail if you include \u in the prompt
PS1. Normally \u would cause the username to be displayed, but some
command shells interpret it as indicating a Unicode sequence. Modify the PS1
prompt to not include \u.
3. Make sure that your JAVA_HOME and PATH environment variables point to
the location of your JRE so that the installer can locate a suitable JVM. For
example, if you installed the JRE in the /opt/java folder set JAVA_HOME to
/opt/java and ensure PATH includes /opt/java/bin.
TIBCO are defining Java runtime environment (JRE) as the path to the
directory that contains the following file:
— If you are using HP-Itanium, Solaris, or Linux, libjvm.so
— If you are using AIX, libjvm.a
During installation, if you have more than one installation of JRE then make
sure that the JAVA_HOME and PATH environment variables are pointing to
the location of the correct JRE installation otherwise the installation may fail.
TIBCO iProcess Technology Plug-ins Installation
| 29
Chapter 3
Using the GUI Installer
This chapter provides the steps necessary to perform a GUI installation.
Topics
•
About the GUI Installer, page 30
•
Running the GUI Installer, page 31
TIBCO iProcess Technology Plug-ins Installation
30
| Chapter 3
Using the GUI Installer
About the GUI Installer
The GUI (graphical user interface) installation mode causes the installer to
present dialogs that allow you to make choices about product selection, product
location, and so on.
Details about the information you need to enter in the installer dialogs is
provided in the Installation Data Reference appendix on page 73. This prevents
duplication of information in this manual since the same information is needed
for the console and silent installation methods.
TIBCO iProcess Technology Plug-ins Installation
Running the GUI Installer 31
|
Running the GUI Installer
To install the TIBCO iProcess Technology Plug-ins, perform the following steps:
1. Log in with a suitable username. To install the BusinessWorks iProcess
plug-in, you must be logged in as a BusinessWorks user. To install the other
components of TIBCO iProcess Technology Plug-ins, you must be logged in as
the iProcess Engine administrator (IPEADMIN).
— in UNIX, this defaults to pro (also referred to as the “Background” user in
UNIX).
— in Windows, this is specified when the iProcess Engine is installed (it
defaults to the user installing the iProcess Engine).
For more information, see the appropriate TIBCO iProcess Engine Installation
guide.
2. Run the appropriate TIBCO iProcess Technology Plug-ins setup program for
your operating system.
The following table lists the setup programs for the available operating
systems:
Platform
Setup Program Name
Windows
setupwindows32.exe
Sun SPARC: Solaris
setupSolaris.bin
Sun x86: Solaris
setupSolarisx86.bin
AIX
setupaix
HP Itanium
setupHPIA64.bin
Linux
setupLinux.bin
Enter the appropriate command, followed by the Installshield parameter:
-is:javahome javahome
where javahome defines the location of the version of Java that the installer is
to use. For example:
./setupSolaris.bin -is:javahome /opt/java1.6
or:
TIBCO iProcess Technology Plug-ins Installation
32
| Chapter 3
Using the GUI Installer
setupwindows32.exe -is:javahome d:\program files\java
This parameter may not be necessary if the required version of Java is in the
default location expected by the system.
The Welcome dialog is displayed.
3. Review the information on the Welcome dialog, then click Next to proceed.
The TIBCO Software Inc. End User License Agreement is displayed.
Note that you can cancel the installation at any point by clicking on the Cancel
button on any dialog.
4. Review the terms of the license agreement:
— If you agree to the terms, click I accept the terms of the license agreement
to continue with the installation, then click Next.
— If you do not agree to the terms of the license agreement, click I do not
accept the terms of the license agreement and exit from the installation
process by clicking on the Cancel button.
The Installation Mode dialog is displayed.
5. Choose the type of installation you are performing by clicking the appropriate
radio button, then click the Next button. The available types are:
— New installation
— Re-install, repair, or upgrade existing installation
— Reconfigure existing installation
For information about these types of installations, see Installer Overview on
page 17.
TIBCO iProcess Technology Plug-ins Installation
Running the GUI Installer 33
|
If you select the “Re-install, repair,...” type of installation, the following
dialog is displayed, warning you that configuration settings will be reset to
their original values in this type of installation.
Note that a consequence of performing a “Re-install, repair,...” type of
installation is that if you had installed any patches/hot fixes since the previous
major version was installed, the updates installed by the patches/hot fixes will be
lost. TIBCO recommends that you backup your system before performing this
type of installation. See Back up Your System if Re-installing or Repairing, page 9.
6. If you are sure you want to re-install the original files, click OK to continue, or
No to return to the Installation Mode dialog.
The Destination dialog is displayed:
The installer will determine the location of the TIBCO iProcess Engines
(Nodes) on your system (at least one must be installed prior to installing the
plug-ins — see System Requirements on page 20) and enter them in the
iProcess Node field drop-down list.
7. Complete the Destination dialog as follows:
a. Leave the Specify SWDIR check box checked if you are installing any
plug-in other than the BusinessWorks iProcess Plug-in. All of the TIBCO
iProcess Technology Plug-ins (with the exception of the BusinessWorks
iProcess Plug-in) are associated with a specific iProcess Engine, and need
SWDIR specified.
The Specify SWDIR check box must be unchecked in order to install the
BusinessWorks iProcess Plug-in - this is not associated with an iProcess
TIBCO iProcess Technology Plug-ins Installation
34
| Chapter 3
Using the GUI Installer
Engine and does not need SWDIR setting. Note that when you uncheck the
box, the iProcess Node field becomes disabled (because you don’t need to
select an iProcess Node (Engine) if you are only installing a BusinessWorks
iProcess Plug-in). Unchecking the Specify SWDIR check box also prevents
you from choosing to install any of the TIBCO iProcess Technology
Plug-ins other than the BusinessWorks iProcess Plug-in.
b. If you are installing only a BusinessWorks iProcess Plug-in, proceed to
step 8.
If you are installing any plug-in other than the BusinessWorks iProcess
Plug-in, select the iProcess Engine to which you want to associate this
installation of the TIBCO iProcess Technology Plug-ins from the iProcess
Node field drop-down list.
Or, you can use the iProcess Node (Alternate Location) field to specify the
iProcess Node if the desired node is not listed in the iProcess Node field
drop-down list. To specify an alternate, you must select “Alternate
location” from the iProcess Node field drop down list, then enter the
desired node in the iProcess Node (Alternate location) field (or use the
Browse button to locate it). Enter the path to the desired iProcess Engine
(for example: “c:\swserver\eastbranch”).
There is a known issue on UNIX systems that when you use the Browse button to
specify the “Alternate Location”, the final directory you select is duplicated. You
must manually delete one of the duplicated directory names from the path after
using the Browse button.
8. Click Next.
TIBCO iProcess Technology Plug-ins Installation
Running the GUI Installer 35
|
The Features dialog is displayed:
This dialog allows you to select the plug-in(s) you would like to install. The
plug-in(s) you select will determine which dialogs are displayed beyond this
point, because each plug-in requires specific types of data.
If you have selected the “Re-install, repair,...” type of installation (see
page 32), this dialog will display version numbers for those plug-ins which
are already installed on your system. Note that these will be the numbers of
the versions already installed - for example, 10.7.0.0 - not the version 11.3 that
you are now installing.
Note that the installation and use of iProcess Conductor Server Plug-ins and
the iProcess XML Transform Server Plug-in is not supported on HP-UX
systems.
Also note that there is a dependency on the iProcess Java Server Plug-in for all
of the TIBCO iProcess Technology Plug-ins, with the exception of the
BusinessWorks iProcess Plug-in. That is, if you install any of the plug-ins
TIBCO iProcess Technology Plug-ins Installation
36
| Chapter 3
Using the GUI Installer
(except the BusinessWorks iProcess Plug-in), you must also install the iProcess
Java Server Plug-in.
9. Use the subsections in Appendix A, Installation Data Reference on page 73,
for information about the data that can be specified in each of the dialogs
displayed by the TIBCO iProcess Technology Plug-ins installer, depending on
the plug-in(s) you are installing.
The following table lists the dialogs displayed for each plug-in, as well as the
page to reference for information about that dialog:
Plug-in
Dialogs Displayed
See...
TIBCO iProcess Java
Server Plug-in
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Authentication Dialog
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Authentication Dialog
page 79
•
BusinessWorks Server Plug-in Configuration Dialog
page 83
•
None — installing this plug-in does not require you to
enter any configuration parameters.
n/a
TIBCO iProcess
BusinessWorks Server
Plug-in
TIBCO BusinessWorks
iProcess Plug-in
page 79
page 79
TIBCO iProcess
Conductor Server
Plug-in
•
Web Application Server Configuration Dialog
page 85
•
JMS Environment Configuration Dialog
page 86
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Authentication Dialog
page 79
TIBCO iProcess Technology Plug-ins Installation
Running the GUI Installer 37
|
Plug-in
Dialogs Displayed
See...
TIBCO iProcess XML
Transform Server
Plug-in
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Authentication Dialog
page 79
10. After completing each necessary dialog, click the Next button to proceed in
the installation process.
When all of the necessary dialogs have been completed for the selected
plug-in(s), the Pre-Installation Summary is displayed. This screen provides a
summary of the plug-ins you are installing.
11. If you are satisfied with the summary, click Install. (You can also click the
Back button to return to any dialog to make changes.)
The installer copies the necessary files to your system and informs you when
it is finished.
12. Click Finish to complete the installation.
TIBCO iProcess Technology Plug-ins Installation
38
| Chapter 3
Using the GUI Installer
TIBCO iProcess Technology Plug-ins Installation
| 39
Chapter 4
Using the Console Installer
This chapter describes how to install the TIBCO iProcess Technology Plug-ins
using console mode.
Topics
•
Installing Using Console Mode, page 40
TIBCO iProcess Technology Plug-ins Installation
40
| Chapter 4
Using the Console Installer
Installing Using Console Mode
Console mode allows you to install the TIBCO iProcess Technology Plug-ins from
a non-graphical display environment. This mode presents a series of prompts that
request the same information that you would enter on the dialogs presented in
the GUI installation mode.
The basic command to run a console installation is:
<Installer> -console
where <Installer> is the name of the installer .exe file (on Windows) or .bin file (on
UNIX; except for AIX, which does not have an extension). For a list of the installer
names, see the table on page 31.
To perform a console mode installation, follow these steps:
1. Log in with a suitable username. To install the BusinessWorks iProcess
plug-in, you must be logged in as a BusinessWorks user. To install the other
components of TIBCO iProcess Technology Plug-ins, you must be logged in as
the iProcess Engine administrator (IPEADMIN).
— in UNIX, this defaults to pro (also referred to as the “Background” user in
UNIX).
— in Windows, this is specified when the iProcess Engine is installed (it
defaults to the user installing the iProcess Engine).
For more information, see the TIBCO iProcess Engine Installation guide.
2. Enter the TIBCO iProcess Technology Plug-ins setup program name at a
command prompt or in a terminal window, followed by the -console switch.
For a list of the setup program names, see the table on page 31.
For example:
setupwindows32.exe -console
TIBCO iProcess Technology Plug-ins Installation
Installing Using Console Mode 41
|
A welcome message is displayed.
Generally, the prompts in console mode expect you to enter a number to indicate
your selection, then press 0 (zero) to submit the selection made and then type 1 to
proceed to the next prompt (or 3 to cancel and 5 to redisplay). You always have
the combination of pressing zero and then 1 to proceed for all screens
If a value is shown in square brackets at the end of the prompt (for example, [0]),
it signifies a default. Pressing Enter submits that value.
3. Enter 1 to proceed, then press Enter.
The TIBCO Software Inc. End User License Agreement is displayed.
4. Read the license agreement by pressing Enter to step through the multiple
pages. At the end of the agreement, the following is displayed:
TIBCO iProcess Technology Plug-ins Installation
42
| Chapter 4
Using the Console Installer
5. Choose to accept or not accept the license agreement.
— If you do not accept the agreement, the installation is cancelled.
— If you accept the agreement, the following is displayed:
6. Select the type of installation you want to perform.
For a description of the types of installation you can perform, see Installer
Overview on page 17.
A prompt is displayed that shows your selection:
The prompt shown above is displayed a number of times in console mode. This
prompt allows you to:
— Press 1 to proceed to the next prompt,
— press 2 to go back to the previous prompt (the license agreement in this
particular case),
— press 3 to cancel the installation, or
— press 5 to redisplay the current prompt (the Installation Mode prompt in
this particular case).
7. When you are satisfied, press 1 to proceed to the next prompt.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Console Mode 43
|
The following is displayed:
8. Indicate whether or not you want SWDIR specified, as follows:
a. Specify SWDIR if you are installing any plug-in other than the
BusinessWorks iProcess Plug-in. All of the TIBCO iProcess Technology
Plug-ins (with the exception of the BusinessWorks iProcess Plug-in) are
associated with a specific iProcess Engine, and need SWDIR specified.
b. Do not specify SWDIR if you are installing only a BusinessWorks iProcess
Plug-in which is not associated with an iProcess Engine and does not need
SWDIR. (Note that if you do not specify SWDIR, the installer will allow
you to install only a BusinessWorks iProcess Plug-in.)
Your response to the Specify SWDIR prompt will determine the next prompt
that is displayed, as follows:
— If you do not specify SWDIR, the Features prompt is displayed when you
complete the Destination prompt — proceed to step 10.
— If you specify SWDIR, the iProcess Node prompt is displayed when you
complete the Destination prompt:
This prompt is used to specify the TIBCO iProcess Node (Engine) to which
you would like to associate the plug-ins you are installing.
9. Select the appropriate iProcess Engine.
If the iProcess Engine on which you want to install the TIBCO iProcess
Technology Plug-ins is not listed, choose the “Alternate Location” selection.
TIBCO iProcess Technology Plug-ins Installation
44
| Chapter 4
Using the Console Installer
This will cause an additional prompt to display, in which you can specify the
path to the desired iProcess Engine. For example: “D:\swserver\myengine”.
The Features prompt is displayed:
This prompt is used to specify which of the TIBCO iProcess Technology
Plug-ins you want to install.
10. Specify the plug-ins you want to install by entering the appropriate number.
You can select multiple plug-ins by entering multiple numbers before
proceeding by entering a 0 (zero).
You can also un-select a plug-in by re-entering that plug-in’s number, then
pressing Enter — that is, it works as a toggle.
Note that there is a dependency on the iProcess Java Server Plug-in for all of the
TIBCO iProcess Technology Plug-ins, with the exception of the BusinessWorks
iProcess Plug-in. That is, if you select any of the plug-ins (except the
BusinessWorks iProcess Plug-in), the iProcess Java Server Plug-in will be
automatically selected.
Also note that the BusinessWorks iProcess Plug-in cannot be installed at the same
time as any of the other plug-ins in the TIBCO iProcess Technology Plug-ins
installer. That is, it must be installed separately — if you want to install the
BusinessWorks iProcess Plug-in and one or more of the other plug-ins, you must
run the installer twice.
After entering 0 (zero), the installer will indicate which plug-ins have been
selected to be installed. For example:
11. Enter 1 to proceed to the next prompt.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Console Mode 45
|
The prompts that are displayed from this point on are dependent on which
plug-ins you are installing.
The following table lists the prompts that are displayed for each plug-in, as
well as the page to reference for details about the information that needs to be
entered at the prompt:
Plug-in
Dialogs Displayed
See...
TIBCO iProcess Java
Server Plug-in
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Authentication Dialog
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Connection Dialog
page 79
•
BusinessWorks Server Plug-in Configuration Dialog
page 83
•
None — installing this plug-in does not require you to
enter any configuration parameters.
n/a
TIBCO iProcess
BusinessWorks Server
Plug-in
TIBCO BusinessWorks
iProcess Plug-in
page 79
page 79
TIBCO iProcess
Conductor Server
Plug-in
TIBCO iProcess XML
Transform Server
Plug-in
•
Web Application Server Configuration Dialog
page 85
•
JMS Environment Configuration Dialog
page 86
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Authentication Dialog
page 79
•
General Configuration Dialog
page 74
•
Database Configuration Dialog
page 77
•
Database Authentication Dialog
page 79
12. Enter the appropriate information at each prompt, then proceed.
TIBCO iProcess Technology Plug-ins Installation
46
| Chapter 4
Using the Console Installer
The Pre-Installation Summary is displayed:
13. Review the information on the Pre-Installation Summary, then when you are
satisfied, enter 1 to proceed.
The installer program will copy the necessary files to your system and display
messages similar to the following when it is finished:
14. Enter 3, then press Enter to complete the installation of the TIBCO iProcess
Technology Plug-ins.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Console Mode 47
|
TIBCO iProcess Technology Plug-ins Installation
48
| Chapter 4
Using the Console Installer
TIBCO iProcess Technology Plug-ins Installation
| 49
Chapter 5
Using the Silent Installer
This chapter describes how to install the iProcess Technology Plug-ins using silent
mode.
Topics
•
Generating a Response File, page 50
•
Password Encryption, page 51
•
Performing a Silent Installation, page 52
•
Response File Details, page 54
TIBCO iProcess Technology Plug-ins Installation
50
| Chapter 5
Using the Silent Installer
Installing Using Silent Mode
A silent-mode installation installs the iProcess Technology Plug-ins without
prompting you for information. The installer uses a provided response file to
determine values for all required settings (for example, the iProcess Engine to
associate the plug-ins, user names, port numbers, and so on).
Generating a Response File
Response files are generated by including the -options-record switch (note that
there no space between -options and -record) when performing a GUI or
console installation from the command line or terminal. It must be in one of the
following forms:
<Installer> -options-record <responseFileName>
or
<Installer> -console
-options-record
<responseFileName>
where <Installer> is the name of the installer .exe file (on Windows) or .bin file (on
UNIX; except for AIX, which does not have an extension), and <responseFileName>
is the path/name of the response file you want to generate. For a list of the
installer names, see the table on page 31.
All parameter values that are entered during the GUI or console installation are
recorded in the response file, which can then be used in a silent installation.
•
Make sure that the machine you use to create the response file is in the same
state as the machines where you want to perform the silent installations.
Otherwise you may have a problem with extra dialogs. For example, if you
create the response file on a machine that has a previous installation of
iProcess Technology Plug-ins then an extra dialog is displayed asking if you
want to upgrade this installation. If you then try and perform a silent
installation with this response file on a machine that does not have a previous
installation of iProcess Technology Plug-ins then the responses in the response
file will not match the dialogs displayed in the installation program.
•
If you are performing an upgrade from an earlier version, note that you
cannot use a response file created with a previous version of iProcess
Technology Plug-ins to install this version. You must carry out an initial
installation with the current version of iProcess Technology Plug-ins to
generate a valid response file which you can then use for silent installations.
For more information about the response file, see Response File Details on
page 54.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 51
|
Password Encryption
If you use the output of the GUI installer to generate a response file, as described
in Generating a Response File on page 50, that response file will include the
encrypted form of the database password. However, it is also possible to produce
an encrypted password for entry into the response file without using the GUI.
To carry out an encryption in console mode, you must:
1. Ensure that the dependent jar files log4j-1.2.13.jar, crypto.jar and
common_utils_library.jar are on the classpath.
2. Invoke the main method in class
com.staffware.integration.utils.java.library.encrypt.DESEncrypterEx
You can achieve this by creating and using a wrapper script. This is an
example script for a Windows environment:
setlocal
rem Set the following two variables to suite the system
set swdir=C:\swserver\staffw_nod1
set java=%SWDIR%\java\bin\java
set cp=%swdir%\eaijava\libs\bootstrap\log4j-1.2.13.jar
set cp=%cp%;%swdir%\eaijava\libs\repository\system\crypto.jar
set
cp=%cp%;%swdir%\eaijava\libs\repository\plugin\common_utils_librar
y.jar
%java% -cp %cp%
com.staffware.integration.utils.java.library.encrypt.DESEncrypterE
x %*
This is an example script for a UNIX environment:
#!/bin/ksh
# Set the following two variables to suit the system
swdir=/opt/swserver/staffw_nod1
java=$SWDIR/java/bin/java
cp=$SWDIR/eaijava/libs/bootstrap/log4j-1.2.13.jar
cp=$cp:$SWDIR/eaijava/libs/repository/system/crypto.jar
cp=$cp:$SWDIR/eaijava/libs/repository/plugin/common_utils_libra
ry.jar
$java -cp $cp
com.staffware.integration.utils.java.library.encrypt.DESEncrypterE
x $
3. Invoke your script, by typing the name you have given it at the command
prompt.
4. Type in the database password. The password is not echoed to the screen; the
characters that you type are replaced by asterisks.
TIBCO iProcess Technology Plug-ins Installation
52
| Chapter 5
Using the Silent Installer
5. The encrypted password is then displayed. You can copy this into your
response file as the value of the SWDatabasePasswordEncrypted keyword.
See Response File Example on page 59 for an example of this keyword.
Performing a Silent Installation
The basic command to run a silent installation is:
<Installer> -options <responseFileName> -silent
where <Installer> is the name of the installer .exe file (on Windows) or .bin file (on
UNIX), and <responseFileName> is the path/name of the response file that was
generated during an earlier GUI or console installation (see Generating a
Response File on page 50).
To perform a silent mode installation, follow these steps:
1. Log in with a suitable username.
To install the BusinessWorks iProcess plug-in, you must be logged in as a
BusinessWorks user. To install the other components of TIBCO iProcess
Technology Plug-ins, you must be logged in as the iProcess Engine
administrator (IPEADMIN):
— in UNIX, this defaults to pro (also referred to as the “Background” user in
UNIX).
— in Windows, this is specified when the iProcess Engine is installed (it
defaults to the user installing the iProcess Engine).
For more information, see the TIBCO iProcess Engine Installation guide.
2. Generate a response file — see Generating a Response File on page 50. For
example:
setupwindows32.exe -options-record C:\temp\ipc.rsp
3. Using the generated response file, perform an installation using the -silent
switch. For example:
setupwindows32.exe -options C:\temp\ipc.rsp -silent
The installation will be performed silently, with no dialogs/prompts
displayed.
The command-line / terminal prompt will return when the installation is
finished — be patient; it may take a few minutes.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 53
|
Viewing the Log File
You can determine the result of the silent installation by looking at the log file.
By default, Setup.log is created in the same folder as Setup.exe unless you use
the -f2 parameter when performing the installation.
The log file contains three sections:
• [InstallShield Silent] identifies the version of InstallShield Silent used in the
silent installation. It also identifies the file as a log file.
• [Application] identifies which application and version have been installed.
This section is only created if the [ResponseResult] section contains the result
code 0, indicating that the installation was successful.
• [ResponseResult] contains one of the following result codes, indicating
whether or not the silent installation succeeded.
Value
Description
0
Success.
-1
General error.
-2
Invalid mode.
-3
Required data not found in the response file.
-4
Not enough memory available.
-5
File does not exist.
-6
Cannot write to the response file.
-7
Unable to write to the log file.
-8
Invalid path to the response file.
-9
Not a valid list type (string or number).
-10
Data type is invalid.
-11
Unknown error during setup.
-12
Dialogs are out of order.
-51
Cannot create the specified folder.
-52
Cannot access the specified file or folder.
TIBCO iProcess Technology Plug-ins Installation
54
| Chapter 5
Using the Silent Installer
Value
Description
-53
Invalid option selected.
Response File Details
Although a response file could be manually created, TIBCO recommends that you
generate one using a GUI or console installation as instructed in Generating a
Response File on page 50.
Once generated, a response file can be manually edited as required. However,
care must be taken when editing the response file. If one or more of the
parameters specified in the response file are incorrect, the plug-ins may not install
properly.
Each line in the response file consists of a keyword/value pair in the following
format:
Keyword="Value"
where:
—
Keyword
—
Value is a valid value for that keyword. All values are specified as strings.
An empty string signifies no entry for that parameter. (Note that the value
string currently cannot contain the ’=’ character. This is a restriction of
Installshield that may be lifted in a later release.)
is one of the keywords listed in the table on page 54.
All of the keywords are stored as variables, and must be set with a -V in the
response file. For example:
-V SWInstallJavaServerPlugIn="True"
The response file can also contain comment lines, which must start with a hash (#)
character in the first column.
Response File Keywords
The following table lists all the keywords that can appear in the response file. The
Description column provides either:
•
a description of the parameter defined by the keyword, or
•
a link to a description of the parameter in the Installation Data Reference
appendix.
Note that some of the keyword descriptions in the table are grouped together
because they are related to one another in some way.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 55
|
All keyword values must be specified as a string — an empty string signifies no
value.
Keyword
Description
LICENSE_ACCEPT_BUTTON
These keywords are automatically created by
Installshield, and should not be edited. The “accept”
keyword should always be “true” and the “reject”
keyword should always be “false”.
LICENSE_REJECT_BUTTON
SWNewInstall
SWRepairInstall
SWReconfigureInstall
SW_DESTINATION
The type of installation to perform: new, re-install /
repair / upgrade, or reconfigure. These are mutually
exclusive — one must be set to “true”; the other two
must be set to “false”.
For more information, see Installer Overview on
page 17.
The path to the TIBCO iProcess Node (Engine) to which
you would like to associate the plug-ins you are
installing. For example: “D:\swserver\myengine”
For BusinessWorks iProcess Plug-in, this value should
not be set.
SWInstallJavaServerPlugIn
SWInstalliPEBWServerPlugIn
These identify the individual plug-ins you want to
install.
Valid entries: “true” or “false”
SWInstallBWiPEServerPlugIn
SWInstalliPConductorServerPlugIn
SWInstalliPXMLTransformServerPlugIn
TIBCO iProcess Technology Plug-ins Installation
56
| Chapter 5
Using the Silent Installer
Keyword
Description
SWWebLogic92RadioButton
These represent the radio buttons on the Web
Application Server Configuration dialog. They
identify which WAS you are using when you are
installing the TIBCO iProcess Conductor Server Plug-in.
Valid entries are“true” or “false”; only one may be set to
"true".
SWJBoss40RadioButton
SWJboss32RadioButton
Note that specifying SWJBoss40RadioButton as true
selects JBoss 4.2.1, and specifying
SWJBoss32RadioButton as true selects JBoss EAP 4.3
For more information, see Web Application Server
Configuration Dialog on page 85
SWWLSJAR
The location of the WebLogic JAR file.
This is applicable only if you are using a WebLogic
WAS.
For more information, see JMS Environment
Configuration Dialog on page 86.
SWCOM_SERVER_URL_Weblogic
The URL to the iProcess Conductor JMS Server.
This is applicable only if you are using a WebLogic
WAS.
For more information, see JMS Environment
Configuration Dialog on page 86.
SWconfigLocation
The path to the JBoss security configuration file.
This is applicable only if you are using a JBoss WAS.
For more information, see JMS Environment
Configuration Dialog on page 86.
SWJBOSSCLIENTJAR
The path to the JBoss client JAR file.
This is applicable only if you are using a JBoss WAS.
For more information, see JMS Environment
Configuration Dialog on page 86.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 57
|
Keyword
Description
SWCOM_SERVER_URL_JBOSS
The URL to the iProcess Conductor JMS Server.
This is applicable only if you are using a JBoss WAS.
For more information, see JMS Environment
Configuration Dialog on page 86.
SWPath
See Update System Path on page 74.
Valid entries: “true” or “false”
Note: (This applies to Windows only.) SWPATH must be
set to true so that your system PATH environment
variable will be updated to include a reference to the
Java Runtime Environment (JRE) location otherwise the
TIBCO iProcess Technology Plug-ins will not install
correctly.
SWServerProxy
See Use HTTP Proxy Server on page 75.
Valid entries: “true” or “false”
SWServerProxyServer
See Proxy Server on page 75.
SWServerProxyPort
See Port Number on page 76.
SWEncoding
See Character Encoding on page 76.
SWJavaLocation
See Java Environment on page 75.
SWAuditUser
These identify the audit user and audit message.
SWAuditMessage
SWDatabaseType
This must be one of the following strings:
— “Oracle”
— “SQL Server (SQL Server Authentication)”
— “SQL Server (Windows Authentication)”
— “Oracle Real Application Cluster (RAC)”
For more information, see Database Type on page 78.
TIBCO iProcess Technology Plug-ins Installation
58
| Chapter 5
Using the Silent Installer
Keyword
Description
SWDatabaseTypeEnc
This must be one of the following strings:
— “Oracle”
— “SQLServer”
SWDatabaseHost
See Host on page 79.
SWDatabasePort
See Port on page 80.
SWDatabaseUser
See User ID on page 80.
SWDatabasePasswordEncrypted
The encrypted database password. Using unencrypted
passwords is not supported. A password can be
encrypted either as output from the GUI installer, or as
described on Password Encryption on page 51.
See Password on page 80.
SWDatabaseSchema
See Schema Owner on page 81.
SWJDBC
See JDBC URL on page 81.
SWComms
See Enable Client Plug-in Connections on page 83.
Valid entries: “true” or “false”
SWJMXPort
See Port Number on page 83.
jdbc_0_alias
Mandatory. The only value accepted is "internal":
jdbc_0_alias="internal"
See Database Configuration Dialog on page 77.
jdbc_0_classpath
Mandatory.
There is no default value.
See Database Configuration Dialog on page 77.
ems_0_alias
Mandatory. Note that if a different mnemonic to ems is
used, (for example, other_0_alias=example) then the
specified test.jar will get copied to a folder called the
$SWDIR/jmslib/other/.
Default entry: ems_0_alias="internal"
See Configure the JMS Provider on page 82.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 59
|
Keyword
Description
ems_0_classpath
Mandatory. Note that if a different mnemonic to ems is
used, (for example, on a Windows system,
other_0_classpath=/opt/test.jar ) then the specified
test.jar will get copied to a folder called the
$SWDIR/jmslib/other/.
There is no default value.
See Configure the JMS Provider on page 82.
Response File Example
The following is an example response file, without the comments (i.e., only the
keywords are shown):
-V LICENSE_ACCEPT_BUTTON=”true”
-V LICENSE_REJECT_BUTTON=”false”
-V SWNewInstall=”true”
-V SWRepairInstall=”false”
-V SWReconfigureInstall=”false”
-V SW_DESTINATION=”C:/swserver/dana106”
-V SWInstallJavaServerPlugIn=”true”
-V SWInstalliPEBWServerPlugIn=”true”
-V SWInstallBWiPEServerPlugIn=”false”
-V SWInstalliPConductorServerPlugIn=”false”
-V SWInstalliPXMLTransformServerPlugIn=”false”
-V SWWeblogic92RadioButton=”false”
-V SWJboss40RadioButton=”true”
-V SWJboss32RadioButton=”false”
-V SWconfigLocation=”C:/jboss/auth.conf”
-V SWJBOSSCLIENTJAR=”C:/jboss/jbossall-client.jar”
-V SWCOM_SERVER_URL_JBOSS=”jnp://liberty:1099”
-V SWPath=”true”
-V SWServerProxy=”false”
-V SWServerProxyServer=””
TIBCO iProcess Technology Plug-ins Installation
60
| Chapter 5
Using the Silent Installer
-V SWServerProxyPort=””
-V SWEncoding=”Cp1252”
-V SWJavaLocation=”C:/jdk1.6.0_26/jre/bin/client”
-V SWAuditUser="swadmin"
-V SWAuditMessage="EAIJava"
-V SWDatabaseType=”SQL Server (Windows Authentication)”
-V SWDatabaseTypeEnc=”SQLServer”
-V jdbc_0_alias="internal"
-V jdbc_0_classpath="C:/install/sqljdbc4.jar"
-V SWDatabaseHost=”127.0.0.1”
-V SWDatabasePort=”1433”
-V SWDatabaseInstance=””
-V SWDatabaseUser=”swpro”
-V SWDatabasePasswordEncrypted="075cbb67f695318cf37fed064b79f840"
-V SWDatabaseSchema=”swpro”
-V SWJDBC=”jdbc:sqlserver://127.0.0.1:1433;SelectMethod=cursor”
-V ems_0_alias="internal"
-V ems_0_classpath="C:/tibco/ems/6.0/lib/tibjms.jar;
C:/tibco/ems/6.0/lib/tibjmsadmin.jar
-V SWComms="true"
-V SWJMXPort="10021"
TIBCO iProcess Technology Plug-ins Installation
| 61
Chapter 6
Post-Installation Tasks
This chapter describes the tasks that you need to perform after you install the
TIBCO iProcess Technology Plug-ins. Some of these tasks apply only if you are
installing on particular databases or operating systems.
Topics
•
Configuring JNDI Password Encryption (Upgrade Only), page 62
•
Using the $SWDIR/eaijava/scripts/env.sh Script (UNIX Only), page 63
•
Run the SQL Server Surface Area Configuration Utility, page 64
•
Manually Remove the ISMP Directories, page 65
•
Configure the XML Step Definitions Cache, page 66
TIBCO iProcess Technology Plug-ins Installation
62
| Chapter 6
Post-Installation Tasks
Configuring JNDI Password Encryption (Upgrade Only)
Follow the instructions in this section if you have upgraded from a previous
version and want to configure your environment to use encrypted JNDI
passwords (both in the database and when exported).
1. Ensure that the iProcess Engine has been shut down.
2. Run the JMS Administration Utility from the command line as follows:
— From UNIX, navigate to the SWDIR/jmsadmin directory and enter the
following command:
jmsadmin.sh eaijava.jmx_listener=enable upgrade
— From Windows, navigate to the SWDIR\jmsadmin directory and enter the
following command:
jmsadmin.bat eaijava.jmx_listener=enable upgrade
This generates a database-specific drop/create SQL scripts (Oracle.sql or
SQLServer.sql)
3. Execute the appropriate SQL script as the iProcess Schema Owner.
Running the script deletes from the database the existing schema and data
relating to iProcess Technology Plug-ins. It then recreates the schema and the
data in secure form.
4. Restart the iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
Using the $SWDIR/eaijava/scripts/env.sh Script (UNIX Only) 63
|
Using the $SWDIR/eaijava/scripts/env.sh Script (UNIX Only)
If you are installing on UNIX, there are some environment variables that you
must set up before you start the Process Sentinels. To do this, you must run the
$SWDIR/eaijava/scripts/env.sh script:
1. Log in as user root or the background user (default is pro).
2. Enter the command:
. $SWDIR/eaijava/scripts/env.sh
You must run this script every time before you start the Process Sentinels.
You could modify the .profile for the user that starts the Process Sentinels so
that it calls the $SWDIR/eaijava/scripts/env.sh script every time the
Process Sentinels are started.
Alternatively, you could add a call to env.sh into the $SWDIR/etc/swstart_env.
For example:
. $SWDIR/eaijava/scripts/env.sh
This will be automatically picked up by swstart -p.
TIBCO iProcess Technology Plug-ins Installation
64
| Chapter 6
Post-Installation Tasks
Run the SQL Server Surface Area Configuration Utility
This post-installation task needs to be performed only if:
•
you are installing or upgrading the TIBCO iProcess Technology Plug-ins, and
•
you are using SQL Server 2005 with Service Pack 2.
If you are performing a new installation under SQL Server 2005 with Service Pack
2, or upgrading to Service Pack 2, you may encounter an error at runtime. When
you use the BusinessWorks iProcess Plug-in from TIBCO Designer and execute a
Start Case on the iProcess Engine, a SQL Server error message is generated
warning you to enable OLE using the Server Surface Area Configuration utility.
1. Stop the iProcess Engine.
2. Select Microsoft SQL Server -> Surface Area Configuration from the
Programs menu.
3. Select Surface Area Configuration For Features.
4. Select OLE Automation, and ensure that the Enable OLE Automation
checkbox is selected.
5. Press OK.
6. When the utility has finished running, restart SQL Server and restart the
iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
Manually Remove the ISMP Directories 65
|
Manually Remove the ISMP Directories
This task is optional.
As part of the installation, the setup program creates ismp* directories, which
contain files, in the home directory of the user you are logged in as when you
perform the install. TIBCO recommend that you remove these directories and the
files they contain once you have installed TIBCO iProcess Technology Plug-ins.
On some UNIX platforms, the directories are called istemp* and these can also be
removed.
TIBCO iProcess Technology Plug-ins Installation
66
| Chapter 6
Post-Installation Tasks
Configure the XML Step Definitions Cache
This step applies only if you have chosen to install the iProcess BusinessWorks
Connector.
In order to improve runtime performance and reduce CPU load, the XML step
definitions for iProcess BusinessWorks Connector invocations are cached. The
cache.properties file is set up for you automatically as part of the installation
process. However you can edit the values set in this file in order to switch caching
off or to change the cache size of the XML data.
To do this, locate the cache.properties file in your $SWDIR/eaijava/properties/bw
folder and edit the following properties as required:
•
bw.xml.request.payload.cacheSize=
•
bw.xslt.request.payload.cacheSize=
•
bw.xslt.response.payload.cacheSize=
•
bw.transport.jmsTimeout.cacheSize=
•
bw.transport.payload.cacheSize=
For all of these properties:
•
The default value is 10.
•
Setting the value to 0 disables the cache.
TIBCO iProcess Technology Plug-ins Installation
| 67
Chapter 7
Un-installing the TIBCO iProcess
Technology Plug-ins
This chapter describes how to un-install the plug-ins included in the TIBCO
iProcess Technology Plug-ins.
Topics
•
Un-installing TIBCO iProcess Technology Plug-ins From Windows, page 68
•
Un-installing TIBCO iProcess Technology Plug-ins From UNIX, page 70
TIBCO iProcess Technology Plug-ins Installation
68
| Chapter 7
Un-installing the TIBCO iProcess Technology Plug-ins
Un-installing TIBCO iProcess Technology Plug-ins From Windows
The following subsections describe un-installing the TIBCO iProcess Technology
Plug-ins from Windows systems.
Un-installing the iProcess Engine-Based Plug-ins from Windows
The TIBCO iProcess Technology Plug-ins should be un-installed using the
un-install program supplied with the software and not via the Add or Remove
Programs in the Control Panel.
Complete the following steps to safely un-install the appropriate instance of the
plug-in:
1. Log in as a user who has administrative privileges.
2. Stop the TIBCO iProcess Engine to which the plug-in you are un-installing is
associated.
3. Via Windows Explorer, navigate to the “un-installer” folder that was created
when the TIBCO iProcess Technology Plug-ins were installed. This folder was
added to the TIBCO iProcess Engine directory when the plug-ins were
installed:
— SWDIR\_uninstCombinedInstaller
where SWDIR is the home directory for the iProcess Engine to which the
TIBCO iProcess Technology Plug-ins you want to un-install are associated.
4. Execute the uninstall.exe program from the uninstaller folder.
The Welcome dialog is displayed.
5. Review the information on the Welcome dialog, then click Next to proceed.
A dialog is displayed that allows you to choose which of the TIBCO iProcess
Technology Plug-ins you want to un-install.
The TIBCO BusinessWorks iProcess Plug-in has its own uninstaller and must
be un-installed in a separate session to the other Technology Plug-ins.
Select the appropriate plug-in(s) you want to un-install, then click Next.
The Summary dialog is displayed.
6. Review the information about the plug-in(s) that will be un-installed, then
click Uninstall.
The un-installer will inform you when it is finished.
TIBCO iProcess Technology Plug-ins Installation
Un-installing TIBCO iProcess Technology Plug-ins From Windows 69
|
7. Click Finish to complete the removal.
Un-installing the BusinessWorks iProcess Plug-in from Windows
To un-install the BusinessWorks iProcess Plug-in from Windows systems:
1. Navigate to the following directory:
<BWHome>\plugins\iprocess\_uninst
where <BWHome> is the TIBCO BusinessWorks home directory, which
defaults to \tibco\bw.
2. Run the Tibuninstall.exe un-install program.
The un-install program will step you through a series of dialogs that will
un-install the plug-in.
TIBCO iProcess Technology Plug-ins Installation
70
| Chapter 7
Un-installing the TIBCO iProcess Technology Plug-ins
Un-installing TIBCO iProcess Technology Plug-ins From UNIX
The following subsections describe un-installing the TIBCO iProcess Technology
Plug-ins from UNIX systems.
Un-installing the iProcess Engine-Based Plug-ins from UNIX
This section describes how to un-install any of the TIBCO iProcess Technology
Plug-ins that are “iProcess Engine-based”, that is, the plug-ins that are installed in
SWDIR (the iProcess Engine installation directory). This includes all of the TIBCO
iProcess Technology Plug-ins except the BusinessWorks iProcess Plug-in (for
information about un-installing the BusinessWorks iProcess Plug-in, see
Un-installing the BusinessWorks iProcess Plug-in from UNIX on page 71).
1. Log in as the iProcess Engine background user (typically pro on UNIX).
2. Stop the TIBCO iProcess Engine to which the plug-in you are un-installing is
associated.
3. Un-install the plug-in by executing the uninstall command located in the
“uninstall” directory, which was added to the TIBCO iProcess Engine
directory when the plug-in was installed.
The table below lists the uninstall command/directory for the supported
UNIX platforms.
Platform
Uninstall Command
AIX
$SWDIR/_uninstCombinedInstaller/uninstall
HP-UX Itanium
$SWDIR/_uninstCombinedInstaller/uninstallHPIA64.bin
HP-UX PA-RISC,
Solaris,
Linux
$SWDIR/_uninstCombinedInstaller/uninstall.bin
The TIBCO iProcess Technology Plug-ins Uninstaller is displayed.
4. Click Next.
The Uninstall Feature dialog is displayed. By default, all features are selected
to be removed.
5. De-select any that you want to keep and click Next.
6. Read the summary information, then click Uninstall to un-install the plug-in.
TIBCO iProcess Technology Plug-ins Installation
Un-installing TIBCO iProcess Technology Plug-ins From UNIX 71
|
7. Click Finish to complete the un-install process.
Un-installing the BusinessWorks iProcess Plug-in from UNIX
To un-install the BusinessWorks iProcess Plug-in from UNIX systems:
1. Navigate to the following directory:
<BWHome>/plugins/iprocess/_uninst
where <BWHome> is the TIBCO BusinessWorks home directory, which
defaults to /tibco/bw.
2. Run the Tibuninstall.bin un-install program.
If you are removing the BusinessWorks iProcess Plug-in from an HP-UX 11.23
64-bit system, the Tibuninstall.bin program may be missing from the
.../_uninst directory. In this case, use the following command to invoke the
un-install program:
java -cp uninstaller.jar run
The un-install program will step you through a series of dialogs that will
un-install the plug-in.
TIBCO iProcess Technology Plug-ins Installation
72
| Chapter 7
Un-installing the TIBCO iProcess Technology Plug-ins
TIBCO iProcess Technology Plug-ins Installation
| 73
Appendix A
Installation Data Reference
This appendix provides reference information about all the configuration items in
the dialogs displayed by the TIBCO iProcess Technology Plug-ins installer.
Topics
•
General Configuration Dialog, page 74
•
Database Configuration Dialog, page 77
•
Database Configuration Dialog (continued), page 79
•
Configure the JMS Provider, page 82
•
iProcess BusinessWorks Server Plug-in Configuration Dialog, page 83
•
Web Application Server Configuration Dialog, page 85
•
JMS Environment Configuration Dialog, page 86
TIBCO iProcess Technology Plug-ins Installation
74
| Appendix A
Installation Data Reference
General Configuration Dialog
The General Configuration dialog is used to specify information about the Java
Runtime Environment, proxy server (if applicable), and character encoding:
The following table describes the information that is specified on the General
Configuration dialog.
Field
Description
Update System Path
Note: This applies to Windows only.
Check the Update System Path box if you want your system
PATH environment variable to be updated to include a reference
to the Java Runtime Environment (JRE) location.
Note: If you do not have the path to the Java DLL (jvm.dll) in
your system PATH environment variable, you must select this
box, otherwise the TIBCO iProcess Technology Plug-ins will not
install correctly.
TIBCO iProcess Technology Plug-ins Installation
General Configuration Dialog 75
|
Field
Description
Java Environment
Select the directory of the Java Runtime Environment you want to
use. The drop-down list will list the available JREs on your
system. If the JRE you want to use is not in the list, select
Alternate location from the drop-down list. This causes the Java
Environment (Alternate Location) field to become active (see
below).
Note: The directory that is displayed must point to the library
folder underneath the JRE installation directory. For example, if
the JRE is installed in C:\Program Files\Java\j2re1.6.0_06,
the Java Environment field must contain C:\Program
Files\Java\j2re1.1.6.0_06\bin\server or
C:\Program Files\Java\j2re1.1.6.0_06\bin\client.
For more information about choosing the correct JVM location,
see Choosing the Correct JVM on page 25.
Java Environment (Alternate
Location)
This field allows you to specify an alternate JRE path if the one
you want to use is not listed in the Java Environment field
drop-down list.
To activate this field, select Alternate location from the Java
Environment field drop-down list, then enter the desired path, or
click on the Browse button to browse to the desired path.
Note - There is a known issue on UNIX systems that when you
use the Browse button to specify the “Alternate Location”, the
final directory you selected is duplicated. You must manually
delete one of the duplicated directory names from the path after
using the Browse button.
Use HTTP Proxy Server
Check this box if you use a proxy server to connect to the Internet
for HTTP requests. If you do not use a proxy server, leave this box
unchecked. If you check this box, the Proxy Server and Port
Number fields become enabled (see below).
Proxy Server
Enter the path to the proxy server you are using for HTTP
connections (if applicable).
(You must check the Use HTTP Proxy Server check box to enable
this field — see above.)
TIBCO iProcess Technology Plug-ins Installation
76
| Appendix A
Installation Data Reference
Field
Description
Port Number
Enter the port number used by the proxy server you are using for
HTTP connections (if applicable).
(You must check the Use HTTP Proxy Server check box to enable
this field — see above.)
Character Encoding
Enter the encoding property that matches the encoding used on
the iProcess Engine. From iProcess Engine version 11.1 this is
typically UTF-8. However, if you have not configured iProcess
Engine to support UTF-8, it will be a different value (for example
Cp1252 for a Windows machine).
For more information about the encoding property, see Set Up
Character Encoding on page 7. For more information about
iProcess Engine’s support for Unicode UTF-8 and other
globalization options, see the chapter "Using the TIBCO iProcess
Suite in a Multilingual Environment" in the TIBCO iProcess Engine
Architecture Guide.
Audit User
Enter the iProcess username (such as swadmin) that will be
displayed in the audit entry.
Audit Message
Enter the message that will be displayed in the audit entry.
TIBCO iProcess Technology Plug-ins Installation
Database Configuration Dialog 77
|
Database Configuration Dialog
The Database Configuration dialog is used to specify database connection
information:
The following table describes the information that is specified on the Database
Configuration dialog.
TIBCO iProcess Technology Plug-ins Installation
78
| Appendix A
Installation Data Reference
Field
Description
Database Type
Select the type of database that your iProcess Engine is using. You can
select:
•
Oracle
•
SQL Server (SQL Server Authenticated)
•
SQL Server (Windows Authenticated)
•
Oracle Real Application Cluster (RAC)
If you are using SQL Server and your usernames authenticate using
Windows authentication, you must select SQL Server (SQL
Authentication). For more information, see Set Up SQL Server
Authentication on page 5.
Note that if you are reconfiguring, you can switch between Oracle and
Oracle RAC because they use the same database driver. But you cannot
switch between other database types when reconfiguring.
Note - The TIBCO iProcess Technology Plug-ins installation may fail if a
basic installation of the iProcess Engine was performed without first
setting up a database (that is, you allowed the engine installation program
to set up everything). If this occurs, the following message is displayed:
“Cannot open user default database.” Set up a default database for the
background user, then re-attempt the plug-ins installation.
Configure Classpath for Provider
Specify JAR files to
add to classpath
Current Provider
Classpath
Browse for and select the provider’s JAR file. Add all the JAR files that you
want to add to the classpath using one of the following methods:
•
Click Browse, locate a specific JAR file and click Add Jar.
•
Specify a directory and click Add all Jars in this directory.
If the values shown in this field are correct for your installation, click Next
to continue past this dialog. If it is necessary to change the classpath, you
can delete the current values by clicking Delete Classpath Entry.
TIBCO iProcess Technology Plug-ins Installation
Database Configuration Dialog (continued) 79
|
Database Configuration Dialog (continued)
The second Database Configuration dialog is used to specify authentication
details for the database connection:
The following table describes the information that is specified on the second
Database Configuration dialog:
Field
Description
Database Physical Details
Host
Enter the IP address of the machine that is hosting the database to which
you are connecting. For example, 10.10.41.28.
You can specify 127.0.0.1 if the database is on the local computer.
TIBCO iProcess Technology Plug-ins Installation
80
| Appendix A
Installation Data Reference
Field
Description
Port
Enter the port number the database is using. This field automatically
displays the default port numbers for the database type you select, as
follows:
— Oracle: 1521
— SQL Server: 1433
If you have selected SQL Server (SQL Server Authenticated) or SQL Server
(Windows Authenticated) from the Database Type field drop-down list,
and you have multiple database instances under SQL Server 2005, find out
the port number used by the SQL instance to which you wish to connect,
and specify it here.
Instance
Note: This field is visible only if you have selected Oracle from the
Database Type field drop-down list.
Enter the instance name of the Oracle database to which you want to
connect.
Service
Note: This field is visible only if you have selected Oracle Real Application
Cluster (RAC) from the Database Type field drop-down list.
Enter the service name for the Oracle database to which you want to
connect.
Authentication Details
User ID
Enter the iProcess Engine database username.
Password
This field contains the password for the iProcess Engine database user.
If you need to set or change this password, click the Modify button and the
Modify Password dialog appears.
Enter the correct password and click OK to be returned to the Database
Configuration dialog.
TIBCO iProcess Technology Plug-ins Installation
Database Configuration Dialog (continued) 81
|
Field
Description
Schema Owner
Enter the username of the iProcess Engine tables owner. By default, this is
swpro — for more information, see Set Up SQL Server Authentication on
page 5.
JDBC URL
This field will contain the connection string used in the JDBC connection.
This should be modified only if you are told to do so by TIBCO Support.
Note that if Oracle RAC is used, it is the cluster details that are included in
the connection string rather than the host and port numbers from the Host
and Port fields.
Cluster Details
Note: This field is applicable only if you have selected Oracle Real
Application Cluster (RAC) from the Database Type field drop-down list.
The cluster details consists of one or more entries, each identifying the
appropriate host and port on which the database is being hosted.
Use the Add to Cluster button to add an entry to this field; this adds an
entry for the host and port currently identified in the Host and Port fields.
Add additional entries by modifying the Host and Port field, then clicking
the Add to Cluster button again. Each entry must be unique.
Use the Remove from Cluster button to remove entries from the Cluster
Details field. Select the desired entry, then click the Remove from Cluster
button. (Note that if you mistakenly remove the wrong entry, you can
re-enter it by simply clicking on the Add to Cluster button — the Host and
Port fields will contain the host and port information for the removed
entry.)
Note that the installation program validates only the JDBC URL for the
Oracle RAC, not each node listed in the Cluster Details field. This also
means that an instance of the Oracle RAC listed in the Cluster Details field
may be running at installation-time, and no warning will be issued.
TIBCO iProcess Technology Plug-ins Installation
82
| Appendix A
Installation Data Reference
Configure the JMS Provider
1. The following dialog is displayed:
2. The Current Provider Classpath is shown.
If the values shown in this field are correct for your installation, click Next to
continue past this dialog. If it is necessary to change the classpath, you can
delete the current values by clicking Delete Classpath Entry.
3. If you need to change the classpath displayed, you need to specify both the
tibjms and the tibjmsadmin JAR files that you wish to use, in the Specify
JAR files to add to classpath field. Add all the JAR files that you want to add
to the classpath using one of the following methods:
— Click Browse, locate a specific JAR file and click Add Jar.
— Specify a directory and click Add all Jars in this directory.
If you are upgrading from a previous version of TIBCO iProcess Technology
Plug-ins, the existing path to tibjms.jar appears here, but you must add the
tibjmsadmin.jar file manually.
4. Click Next.
TIBCO iProcess Technology Plug-ins Installation
iProcess BusinessWorks Server Plug-in Configuration Dialog 83
|
iProcess BusinessWorks Server Plug-in Configuration Dialog
The iProcess BusinessWorks Server Plug-in Configuration dialog is used to
specify connection information between the BusinessWorks Client and Server
Plug-ins:
The following table describes the information that is specified on the iProcess
BusinessWorks Server Plug-in Configuration dialog.
Field
Description
Enable Client Plug-in
Connections
Check the Enable Client Plug-in Connections check box if you want
your iProcess BusinessWorks Server Plug-in to pass data to your
iProcess BusinessWorks Client Plug-in, and vice versa.
This is typically disabled in a production environment.
Port Number
Specify the port number that the iProcess BusinessWorks Client Plug-in
is using. This port must be free for the exclusive use of the iProcess
BusinessWorks Client Plug-in.
This is because the JMX Server started as part of the iProcess
BusinessWorks Connector is completely separate from other JMX servers
used by iProcess (the JMX Server started by the iProcess Engine for the
TIBCO Business Studio configuration, and the JMX Server used within
the iProcess Web Services Server Plug-in) and requires its own port.
These two servers use the following two configuration files:
•
$SWDIR/etc/swjmx.properties for the TIBCO Business Studio JMX
Server
•
$SWDIR/eaijava/jmxconfig.properties for the iProcess
BusinessWorks Plug-in JMX Server
TIBCO iProcess Technology Plug-ins Installation
84
| Appendix A
Field
Installation Data Reference
Description
The port with the number immediately following the one specified here
- that is, port number 10022 in the example illustrated - is also used. Port
Number is used as the JMX port, Port Number +1 for RMI connection. If
you are communicating through a firewall, this RMI port must be
opened in the firewall to enable communications between the iProcess
Technology Plug-ins server plug-ins and the iProcess Workspace
Plug-ins client plug-ins.
TIBCO iProcess Technology Plug-ins Installation
Web Application Server Configuration Dialog 85
|
Web Application Server Configuration Dialog
The Web Application Server Configuration Dialog is used to identify the Web
Application Server (WAS) you are using:
Click on the appropriate radio button for your type and version of WAS.
TIBCO iProcess Technology Plug-ins Installation
86
| Appendix A
Installation Data Reference
JMS Environment Configuration Dialog
The JMS Environment Configuration dialog is used to specify information about
your JMS environment for the iProcess Conductor plug-ins.
The fields displayed on this dialog will differ depending on whether you had
selected WebLogic or JBoss for the WAS on the Web Application Server
Configuration dialog (see page 85), as follows:
WebLogic
TIBCO iProcess Technology Plug-ins Installation
JMS Environment Configuration Dialog 87
|
JBoss
If you select JBOSS EAP 4.3 on the Web Application Server Configuration
dialog, the following two dialogs are displayed. If you select JBOSS 4.2.1, only the
second dialog is shown.
TIBCO iProcess Technology Plug-ins Installation
88
| Appendix A
Installation Data Reference
The following table describes the information that is specified on the JMS
Environment Configuration dialogs.
Field
Description
WebLogic Jar File
Enter the path or use the Browse button to point to the WebLogic JAR
file. This JAR file provides the JNDI context used for communications
between the plug-in and the WebLogic Web Application Server.
JBoss Home Directory
The dialog containing this field is only displayed if you select JBOSS
EAP 4.3.
Enter the path or use the Browse button to point to the JBoss home
directory.
Security
Configuration File
Enter the path or use the Browse button to point to the JBoss security
configuration file.
JBoss Client Jar File
Enter the path or use the Browse button to point to the JBoss client JAR
file. This JAR file provides the JNDI context used for communications
between the plug-in and the JBoss Web Application Server.
iProcess Conductor
JMS Server URL
Enter the URL to the iProcess Conductor JMS Server. This identifies the
machine hosting the JMS Server, as well as the communications port. It is
preceded by a socket/RMI protocol identifier: t3 (WebLogic), jnp (JBoss).
TIBCO iProcess Technology Plug-ins Installation
| 89
Appendix B
Troubleshooting
This chapter describes problems you might encounter during installation and
recommended courses of action to resolve them.
Topics
•
Database Connection Fails, page 90
•
iProcess Engine Process Sentinels Fail to Start, page 91
•
Background Core Dumps on AIX, page 94
•
The Setup Program Hangs, page 95
•
Oracle Services May Be Required in Console Mode, page 96
•
Missing frameworkconfig.xml file, page 97
•
EAI Java Server Plug-in Fails to Load Correctly, page 98
•
CPU Usage is Too High, page 99
•
JMS Connection Test Returns Fail, page 100
•
Console Mode Installation Fails, page 101
•
JMS Provider Configuration is Lost in an Upgrade Error, page 102
TIBCO iProcess Technology Plug-ins Installation
90
| Appendix B
Troubleshooting
Database Connection Fails
Problem
The database connection fails.
Description
The installer automatically checks the database connection when you fill in the
database information in the Database Configuration Dialog (continued).
What to do
To resolve this:
1. Check that the database is running.
2. Check that you have a connection to the machine hosting the database. Try
pinging the machine.
3. Check that the username and password you are supplying are valid.
4. If you are using a SQL server database, make sure that the schema can be
updated via a username that uses SQL Server authentication (especially if the
iProcess Engine was installed using Windows authentication).
Also see: Oracle Services May Be Required in Console Mode on page 96 and Set
Up SQL Server Authentication on page 5
TIBCO iProcess Technology Plug-ins Installation
iProcess Engine Process Sentinels Fail to Start 91
|
iProcess Engine Process Sentinels Fail to Start
If the iProcess Engine Sentinels fail to start after installing the TIBCO iProcess
Technology Plug-ins, it may be due to one of the problems described in the
following subsections. They are shown on the following pages as Problems 1-3.
Problem 1
This applies to UNIX only.
The iProcess Engine Process Sentinels fail to start and a $SWDIR\logs\sw_warn
file is generated that contains the following message:
2005/11/08 14:56:41(BG:1:2478:2:pro:/proeai.c:1.36:2512):
1867-'EAIJAVA' EAI Run-Time Plug-In failed to initialize, error
EAI_JAVA: EAIRun_Init() - Initialise method failed in Loader!
Description
When installing on UNIX, you must run the Setup program as the iProcess
Background user (by default this is the pro user). If you do not, the files you have
installed will not have the correct owner, which causes the iProcess Java Server
Plug-in to fail to load.
What to do
If you have not run Setup using the Background user, you must do the following:
1. Un-install the iProcess BusinessWorks Server Plug-in. See Un-installing the
BusinessWorks iProcess Plug-in from UNIX on page 71.
2. Un-install the iProcess Java Server Plug-in. See Un-installing the iProcess
Engine-Based Plug-ins from UNIX on page 70.
3. Re-install the TIBCO iProcess Technology Plug-ins as the Background User.
TIBCO iProcess Technology Plug-ins Installation
92
| Appendix B
Troubleshooting
Problem 2
This applies to UNIX only.
The iProcess Engine Process Sentinels fail to start and a $SWDIR\logs\sw_warn
file is generated that contains the following message:
2005/11/08 14:56:41(BG:1:2478:2:pro:/proeai.c:1.36:2512):
1867-'EAIJAVA' EAI Run-Time Plug-In failed to initialize, error
EAI_JAVA: EAIRun_Init() - Initialise method failed in Loader!
Description
To get the iProcess Java Server Plug-in to work correctly, you must remove the
s-bit permissions.
What to do
Remove the s-bit permissions on the following iProcess Engine files:
•
$SWDIR/bin/swstart
•
$SWDIR/etc/procmgr
•
$SWDIR/etc/staffrpcbg
•
$SWDIR/etc/swbgmbd
Note that if you run fixperms or re-install the iProcess Engine on top of your
current installation, or upgrade it, you will need to change the s-bit permissions
on the above files again.
TIBCO iProcess Technology Plug-ins Installation
iProcess Engine Process Sentinels Fail to Start 93
|
Problem 3
This applies to UNIX only.
The iProcess Engine Process Sentinels fail to start and a $SWDIR/logs/sw_error
file is generated that contains the following message:
2005/11/15 12:20:22(BG:2:24914:2:pro:/proeai.c:1.36:2350):
1866-Failed to load 'EAIJAVA' EAI Run-Time Plug-In library
'/staffware/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /staffware/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or directory'
2005/11/15 12:20:23(BG:3:24915:2:pro:/proeai.c:1.36:2350):
1866-Failed to load 'EAIJAVA' EAI Run-Time Plug-In library
'/staffware/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /staffware/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or directory'
2005/11/15 12:20:23(BGPREDICT:1:24917:2:pro:/proeai.c:1.36:2350):
1866-Failed to load 'EAIJAVA' EAI Run-Time Plug-In library
'/staffware/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /staffware/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or directory'
2005/11/15 12:20:24(BG:1:24913:2:pro:/proeai.c:1.36:2350):
1866-Failed to load 'EAIJAVA' EAI Run-Time Plug-In library
'/staffware/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /staffware/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or directory'
2005/11/15 12:20:24(BG:4:24919:2:pro:/proeai.c:1.36:2350):
1866-Failed to load 'EAIJAVA' EAI Run-Time Plug-In library
'/staffware/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /staffware/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or directory'
2005/11/15 12:20:35(RPCBG:1:24946:2:pro:/proeai.c:1.36:2350):
1866-Failed to load 'EAIJAVA' EAI Run-Time Plug-In library
'/staffware/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1:
/staffware/installations/<nodename>/etc/staffrpcbg: fatal:
libjvm.so: open failed: No such file or directory'
Description
The $SWDIR/eaijava/scripts/env.sh script has not been run.
What to do
You must run the $SWDIR/eaijava/scripts/env.sh script. For more information,
see Using the $SWDIR/eaijava/scripts/env.sh Script (UNIX Only) on page 63.
TIBCO iProcess Technology Plug-ins Installation
94
| Appendix B
Troubleshooting
Background Core Dumps on AIX
Problem
After installing the iProcess Java Server Plug-in on AIX 5.3, the background
process fails.
Description
After successfully installing the iProcess Java Server Plug-in on AIX 5.3 and
running the env script from the script directory (see Using the
$SWDIR/eaijava/scripts/env.sh Script (UNIX Only) on page 63), if you start the
iProcess Engine, a core dump occurs and an sw_error log is produced.
What to do
To resolve this:
1. Stop the iProcess Engine.
2. Enable LDR_CNTRL=USERREGS in the $SWDIR/eaijava/scripts/env.sh
script.
3. Enable export LDR_CNTRL in the $SWDIR/eaijava/scripts/env.sh script.
4. Reregister the plug-in by executing unregister.sh followed by register.sh.
5. Restart the iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
The Setup Program Hangs 95
|
The Setup Program Hangs
Problem
This applies to UNIX only.
The TIBCO iProcess Technology Plug-ins Setup program reaches 93% and then
hangs indefinitely.
Description
When running the Setup program for the TIBCO iProcess Technology Plug-ins on
UNIX, you must be logged in as the Background User (which defaults to pro), and
that user must have:
•
write permissions to $SWDIR
•
a home directory
If the Background user does not have these, the Setup program is unable to write
any files to the $SWDIR directory or unpack any files temporarily to the
Background User’s home directory.
What to do
To resolve this:
1. Click Cancel to cancel the Setup program.
2. Log in as the Background User.
3. Run the Setup program again.
TIBCO iProcess Technology Plug-ins Installation
96
| Appendix B
Troubleshooting
Oracle Services May Be Required in Console Mode
If you are installing the TIBCO iProcess Technology Plug-ins on Oracle 10g on
Windows, there are some Oracle services that must be running on the machine
hosting the database. If these services are not running, an “Unable to connect to
the Staffware Database” message will be displayed, as follows:
•
If you don't have the OracleDBConsole[SERVICE_NAME] and
OracleService[SERVICE_NAME] running, the following message is
displayed:
Unable to connect to Staffware Database.
Io exception: Connection
refused(DESCRIPTION=(TMP=)(VSNNUM=169869824)(ERR=12505)
(ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4))))
Database connection failed - do you wish to continue?
1. Yes
2. No
•
If you don't have service Oracle[OraDb10g_home]TNSListener running, the
following message is displayed:
Unable to connect to Staffware Database.
Io exception: The Network Adapter could not establish the
connection
Database connection failed - do you wish to continue?
1. Yes
2. No
Start the appropriate services before proceeding with the installation.
TIBCO iProcess Technology Plug-ins Installation
Missing frameworkconfig.xml file 97
|
Missing frameworkconfig.xml file
Problem
After installation the frameworkconfig.xml file is missing.
Description
After installing the iProcess Java Server Plug-in using Java 1.5 and then installing
the iProcess Decisions Server Plug-in, a message appears that the
frameworkconfig.xml is not in the frameworks directory.
What to do
This is potentially caused by a corrupt InstallShield registry. If this occurs contact
TIBCO Support for further assistance.
TIBCO iProcess Technology Plug-ins Installation
98
| Appendix B
Troubleshooting
EAI Java Server Plug-in Fails to Load Correctly
Problem
This applies to UNIX only.
An error similar to the following upon startup indicates that the s-bit permissions
need to be removed:
2008/09/19 14:26:07(BG:4:21893:2:pro:/proeai.c:1.36:2350): 1866Failed to load 'EAIJAVA' EAI Run-Time Plug-In library
'/opt/tibco/sw/lib/EAI_JAVA_i11_0_0_0.EAR', error 'libjava.so:
cannot open shared object file: No such file or directory'
Description
To get the iProcess Java Server Plug-in to load correctly, you must remove the s-bit
permissions.
What to do
Remove the s-bit permissions on the following iProcess Engine files:
•
$SWDIR/bin/swstart
•
$SWDIR/etc/procmgr
•
$SWDIR/etc/staffrpcbg
•
$SWDIR/etc/swbgmbd
Note that if you run fixperms or re-install the iProcess Engine on top of your
current installation, or upgrade it, you will need to change the s-bit permissions
on the above files again.
TIBCO iProcess Technology Plug-ins Installation
CPU Usage is Too High 99
|
CPU Usage is Too High
Problem
Log files indicate that CPU usage is too high because multiple BG processes are
polling the JMX master Virtual Machine (VM) too frequently.
Description
Each BG process polls the JMX master VM at an interval that defaults to 15000mS
(15 seconds). On large systems with many BG processes, this may consume
resources unnecessarily by having so many processes "wake up" to poll for a
response every 15 seconds.
What to do
If this is a problem on your system, you can set the polling interval to a higher
value, as follows:
1. Create a text file SWDIR/eaijava/jmx/config.properties.
2. Give it the contents:
sleepPeriod=value
where value is the polling interval, in milliseconds.
3. Check the file has the correct permissions. It must be owned by the
background user and the iPE group with read access to owner and group.
This file is detected only when iProcess Engine starts up, hence a re-start will be
required. Until a re-start is performed, the system will continue to use the default
value of 15000.
Note that in the event of the loss of the BG process acting as the JMX Master, it
would be up to <sleepPeriod> milliseconds before a slave took over the role of the
master in a recovery scenario.
TIBCO iProcess Technology Plug-ins Installation
100
| Appendix B
Troubleshooting
JMS Connection Test Returns Fail
On the JMS Administration dialog, you can test whether the JMS connection is
working. The following are some possible steps to take to establish why the JMS
connection is failing:
1. Check that the JMS is running.
2. Check that the users are configured correctly.
3. Ensure that you are using the correct JARs.
The status window in the Configure JMS Providers dialog shows the results of
the connection test. Use this information to troubleshoot the problem. You can
also paste this information into another application to use in communication with
TIBCO Support.
TIBCO iProcess Technology Plug-ins Installation
Console Mode Installation Fails 101
|
Console Mode Installation Fails
Problem
sweaireg fails during console mode installation on Windows.
Description
If you do not have any version of Java on the PATH (an unusual situation)
sweaireg will fail because "Update System Path" defaults to the value of "false"
during the console mode installation.
What to do
In the General Configuration Dialog, you must modify the Update System Path
value to true so that your system PATH environment variable will be updated to
include a reference to the Java Runtime Environment (JRE) location otherwise the
TIBCO iProcess Technology Plug-ins will not install correctly.
In GUI mode, the check box is checked by default but in Console and Silent
modes you must amend the value manually.
Note that if you continually use "Update System Path = true" and run the installer
multiple times, the PATH will keep getting extended and that may impact
performance of the system.
This equally applies to console, GUI and silent modes, however the default value
for the field on console mode is false and on GUI mode it is true. You should
change the value as appropriate and not just default it.
TIBCO iProcess Technology Plug-ins Installation
102
| Appendix B
Troubleshooting
JMS Provider Configuration is Lost in an Upgrade Error
This section describes importing JMS provider configuration information you had
previously exported (as described in Export Existing JMS Provider Configuration
if Upgrading on page 8). The export is a backup measure in the unlikely event of
JMS provider configuration information being lost or corrupted in an upgrade
error.
If after upgrading you find that your JMS configuration is not correctly preserved,
you can import your previously exported configuration as follows:
1. Ensure that the iProcess Engine is running.
2. Start the JMS Administration Tool:
— From UNIX, navigate to the $SWDIR/jmsadmin directory and enter the
following command:
./jmsadmin.sh
— From Windows, click Start > Programs > TIBCO iProcess® Engine
(Windows) > JMS Administration Utility.
3. Click Import.
A message is displayed warning you that the current JMS data will be
destroyed.
4. Click OK to continue importing the JMS provider information or Cancel to
return to the Open dialog.
If you clicked OK, the Open dialog is displayed.
5. From the File Name box, select the file that contains your JMS provider
configuration information, then click Open.
The Report for JMS Destination Import dialog is displayed.
This dialog shows which connections have tested successfully and which have
failed. Click Re-test Selected Destinations to re-test one or more connections.
6. Click OK. The new JMS provider information is imported.
TIBCO iProcess Technology Plug-ins Installation
| 103
Appendix C
Java Character Encoding Sets
This appendix describes how to ensure that you use a version of Java that
provides the necessary character encoding set support with the TIBCO iProcess
Technology Plug-ins.
This appendix is only relevant to installations on Windows, Solaris and Linux.
Contact Hewlett-Packard for information about character encoding set support
on HP-UX.
Contact IBM for information about character encoding set support on AIX.
Topics
•
Which Java Version/Encoding Set Combination Do I Need?, page 104
•
Obtaining an Appropriate Java Version/Encoding Set Combination, page 105
•
Using the Required Java Version/Encoding Set Combination, page 108
TIBCO iProcess Technology Plug-ins Installation
104
| Appendix C
Java Character Encoding Sets
Which Java Version/Encoding Set Combination Do I Need?
Java provides two groups of character encoding sets:
•
Basic - supports European languages only
•
Extended - extends Basic to add support for non-European languages
For a complete list of all character encoding sets supported in Java 1.6, see
http://java.sun.com/javase/6/docs/technotes/guides/intl/encoding.doc.html
Use this reference to determine the minimum Java version/encoding set
combination you need.
You must ensure that you use a Java version/encoding set combination that
supports all the character encoding sets you require.
TIBCO iProcess Technology Plug-ins Installation
Obtaining an Appropriate Java Version/Encoding Set Combination 105
|
Obtaining an Appropriate Java Version/Encoding Set Combination
When you have determined what Java version/encoding set combination you
need, you must ensure that this combination is available on your system before
you install the TIBCO iProcess Engine. You can either:
•
use the Java version installed with the iProcess Engine, if it is appropriate - see
Java Version/Encoding Set Combinations Supplied by the iProcess Engine on
page 105 for more information.
•
use a Java version that is already installed on the machine, if it is appropriate see Using a Java Version/Encoding Set Combination That is Already Installed
on page 106.
•
download and install an appropriate Java version - see Installing the Required
Java Version/Encoding Set Combination on page 106.
Java Version/Encoding Set Combinations Supplied by the iProcess Engine
If you are installing the TIBCO iProcess Engine, you may be able to use the Java
version/encoding set combination that is distributed with the iProcess Engine.
The following table lists the combinations of Java version and encoding set (Basic
or Extended) that are distributed (in SWDIR\java) with different versions of the
iProcess Engine.
iProcess Engine
Version 11.0
iProcess Engine
Version 11.0.2
Windows
1.5 Basic (Do not
use - see below.
1.6 Basic
Solaris, Linux
1.5 Extended (Do
not use - see below.
1.6 Extended
Platform
The 1.5 JREs distributed with some versions of iProcess Engines for Windows are
NOT compatible with the version of the TIBCO iProcess Java Plug-in included in
the TIBCO iProcess Engine. You must use a different, compatible JRE instead—see
Java Runtime Environment and Java Virtual Machine on page 24 for more
information.
If this Java version/encoding set combination meets your requirements, you need
take no further action before installing the TIBCO iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
106
| Appendix C
Java Character Encoding Sets
If you need a different Java version/encoding set combination, you must either
use a Java version that is already installed on the machine (if appropriate), or
download and install a suitable Java version. See the following sections for more
information.
Using a Java Version/Encoding Set Combination That is Already Installed
You may be able to use a Java version/encoding set combination that you have
already installed on the machine where you wish to install the TIBCO iProcess
Engine.
The following table lists the Java version/encoding set combinations that are
supported by the different Java versions.
Platform
Java 1.6
Windows
1.6 Basic (see below)
Solaris, Linux
1.6 Extended
On Windows, the default Java installation only provides support for Basic
character encoding sets unless it detects that the operating system uses
non-European character sets, or if the installing user performed a Custom
installation and explicitly requested support for non-European languages (in
which case it provides Extended support as well).
Installing the Required Java Version/Encoding Set Combination
If you need to install the required Java version/encoding set combination,
perform the following steps:
1. Download the required version of Java from Sun’s web site.
2. Install Java with the appropriate character encoding set support. If you are
using:
— Solaris or Linux, the default installation provides support for both Basic and
Extended character encoding sets.
— Windows, the default installation only provides support for Basic character
encoding sets unless it detects that the operating system uses
non-European character sets (in which case it provides Extended support
as well).
TIBCO iProcess Technology Plug-ins Installation
Obtaining an Appropriate Java Version/Encoding Set Combination 107
|
If you require Extended character encoding set support, you should
perform a Custom installation and request support for non-European
languages. This ensures that a complete international version is installed,
which supports the Extended encodings.
TIBCO iProcess Technology Plug-ins Installation
108
| Appendix C
Java Character Encoding Sets
Using the Required Java Version/Encoding Set Combination
Once you have an appropriate Java version/encoding set combination installed,
you must ensure that your TIBCO iProcess Engine use it. The following sections
explain how to do this, depending on the platform you are installing on.
Solaris or Linux
Before you install the TIBCO iProcess Engine, set the JAVA_HOME variable to
point to the Java version you wish to use.
Windows
When you install the TIBCO iProcess Engine, make sure that the Java
Environment field in the Server Configuration dialog (see page 74) points to the
Java version you wish to use.
If you have already installed the TIBCO iProcess Engine and need to change the
Java Environment, run the setup program again and choose Modify Existing
Installation.
TIBCO iProcess Technology Plug-ins Installation
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement