TIBCO iProcess Technology Plug-ins Installation
TIBCO iProcess® Technology
Plug-ins
Installation
Software Release 11.6
January 2016
Two-Second Advantage®
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, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer,
TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Rendezvous, TIBCO Adapter, TIBCO iProcess
Connector for ActiveMatrix BusinessWorks, TIBCO iProcess, and TIBCO Runtime Agent 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 © 2003-2016 TIBCO Software Inc. All rights reserved.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
TIBCO iProcess Technology Plug-ins Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
TIBCO iProcess User Documentation Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii
xii
xii
xii
Chapter 1 Preinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Preinstallation Tasks Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Checking for Any Late Breaking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installing Your Database Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Setting Up SQL Server Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Before Running the Setup Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
When Running the Setup Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Setting Up SQL Server Windows Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Before Running the Setup Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
When Running the Setup Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Setting Up Character Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Exporting Existing JMS Provider Configuration if Upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Backing Up Your System if Re-installing or Repairing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Choosing Your Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2 Introduction to the Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Product Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Installation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Supported Databases and Database Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
TIBCO iProcess Technology Plug-ins Installation
iv
| Contents
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installation with More Than One iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Preparing to Run the Setup Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 3 Using the GUI Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
About the GUI Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Running the GUI Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 4 Using the Console Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Installing Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 5 Using the Silent Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Installing Using Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating a Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Password Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing the Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Response File Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
48
50
51
52
53
Chapter 6 Postinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Running BWC Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuring JNDI Password Encryption (Upgrade Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Using the $SWDIR/eaijava/scripts/env.sh Script (UNIX Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Run the SQL Server Surface Area Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Manually Remove the ISMP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configure the XML Step Definitions Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Replace the 32-bit Library with the 64-bit Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 7 Uninstalling TIBCO iProcess Technology Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Uninstalling TIBCO iProcess Technology Plug-ins From Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Uninstalling the iProcess Engine-Based Plug-ins from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Uninstalling the BusinessWorks Plug-in for iProcess from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Uninstalling TIBCO iProcess Technology Plug-ins From UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Uninstalling the iProcess Engine-Based Plug-ins from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Uninstalling the BusinessWorks Plug-in for iProcess from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Appendix A Installation Data Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
General Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Database Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
TIBCO iProcess Technology Plug-ins Installation
Contents v
|
Database Configuration Dialog (Continued) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
JMS Provider Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
iProcess Server Plug-in for ActiveMatrix BusinessWorks Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Appendix B Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Database Connection Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
iProcess Engine Process Sentinels Fail to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Problem 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Problem 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Problem 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Background Core Dumps on AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
The Setup Program Hangs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Oracle Services May Be Required in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Missing frameworkconfig.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
EAI Java Server Plug-in Fails to Load Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
CPU Usage is Too High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
JMS Connection Test Returns Fail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Console Mode Installation Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
JMS Provider Configuration is Lost in an Upgrade Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Appendix C Java Character Encoding Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Which Java Version/Encoding Set Combination Do I Need. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Obtaining an Appropriate Java Version/Encoding Set Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Java Version/Encoding Set Combinations Supplied by iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Using a Java Version/Encoding Set Combination That Is Already Installed . . . . . . . . . . . . . . . . . . . . . . . . . 110
Installing the Required Java Version/Encoding Set Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Using the Required Java Version/Encoding Set Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Solaris or Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
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 file for the availability of this software
version on a specific operating system platform.
This manual describes how to install TIBCO iProcess® Technology Plug-ins.
Topics
•
Related Documentation, page viii
•
Typographical Conventions, page x
•
Connecting with TIBCO Resources, page xii
TIBCO iProcess Technology Plug-ins Installation
viii
| Related Documentation
Related Documentation
This section lists documentation resources about TIBCO iProcess Technology
Plug-ins you might find useful.
TIBCO iProcess Technology Plug-ins Documentation
•
TIBCO iProcess Technology Plug-ins Installation Read this manual for
instructions on site preparation and installation.
•
TIBCO iProcess Technology Plug-ins Release Notes Read the release notes for a
list of new and changed features for TIBCO iProcess Technology Plug-ins.
This document also contains lists of known issues and closed issues for this
release.
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
See the following guides for more information concerning 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® Connector for ActiveMatrix BusinessWorks™ User’s Guide,
which explains how to use the TIBCO iProcess Connector for ActiveMatrix
BusinessWorks plug-ins, an efficient and easy to use interface between TIBCO
ActiveMatrix BusinessWorks™ and the iProcess Engine. The Process
Connector for ActiveMatrix BusinessWorks consists of a client plug-in (which
is part of the iProcess Workspace Plug-ins), a server plug-in (which is part of
TIBCO iProcess Technology Plug-ins Installation
Preface ix
|
the iProcess Technology Plug-ins), and a BusinessWorks plug-in (which is also
part of the iProcess Technology Plug-ins).
•
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
x
| Typographical Conventions
Typographical Conventions
Although this guide covers installing on both Windows and UNIX systems, the
Windows convention of using a back slash in folder 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
Preface xi
|
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
xii
| Connecting with TIBCO Resources
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts. It is 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 TIBCO Documentation
Documentation for this and other TIBCO products is available on the TIBCO
Documentation site:
https://docs.tibco.com
Documentation on the TIBCO Documentation site is updated more frequently
than any documentation that might be included with the product. To ensure that
you are accessing the latest available help topics, please visit us at
https://docs.tibco.com.
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, 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
|1
Chapter 1
Preinstallation Tasks
This chapter describes the tasks that you have to perform before you run one of the
installers to install TIBCO iProcess Technology Plug-ins. Some of these tasks are
database-specific.
Topics
•
Preinstallation Tasks Checklist, page 2
•
Checking for Any Late Breaking Information, page 3
•
Setting Up SQL Server Authentication, page 5
•
Setting Up SQL Server Windows Authentication on page 6
•
Setting Up Character Encoding, page 8
•
Exporting Existing JMS Provider Configuration if Upgrading, page 9
•
Backing Up Your System if Re-installing or Repairing, page 10
•
Choosing Your Installer, page 11
TIBCO iProcess Technology Plug-ins Installation
2
| Chapter 1
Preinstallation Tasks
Preinstallation Tasks Checklist
The following table provides a checklist of the different tasks that you must or
might do before installing. The table shows:
•
affected plug-in(s)
•
the section to refer to for more detailed information about a particular task.
You might want to print this table as a useful quick reference when carrying out
the preinstallation 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. Installing Your Database Driver
All
page 4
3. Setting Up SQL Server
Authentication
•
iProcess Java Server Plug-in
•
iProcess Server Plug-in for
ActiveMatrix BusinessWorks
4. Setting Up SQL Server Windows
Authentication
•
iProcess Java Server Plug-in
•
iProcess Server Plug-in for
ActiveMatrix BusinessWorks
5. Setting Up Character Encoding
•
iProcess Java Server Plug-in
•
iProcess Server Plug-in for
ActiveMatrix BusinessWorks
6. Exporting Existing JMS Provider
Configuration if Upgrading
•
iProcess Server Plug-in for
ActiveMatrix BusinessWorks
7. Backing Up Your System if
Re-installing or Repairing
All
page 10
8. Choosing Your Installer
All
page 11
1. Checking for Any Late Breaking
Information
TIBCO iProcess Technology Plug-ins Installation
page 5
page 6
page 8
page 9
Done?
Checking for Any Late Breaking Information 3
|
Checking 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 have to check if there are any restrictions, known
issues or other late-breaking information that might 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
folder of 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
Preinstallation Tasks
Installing 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 preinstallation 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 Supported Databases
and Database Drivers on page 23, or of an older version.
Procedure
1. Check the table in Supported Databases and Database Drivers on page 23 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 have to specify this later.
See Database Configuration Dialog on page 79 and Database Configuration
Dialog (Continued) on page 81 for the information you need.
TIBCO iProcess Technology Plug-ins Installation
Setting Up SQL Server Authentication 5
|
Setting 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 preinstallation task applies only if you are using Windows authentication
mode for SQL Server identity authentication and you want to install TIBCO
iProcess Java Server Plug-in and TIBCO iProcess Server Plug-in for ActiveMatrix
BusinessWorks with SQL Server (SQL Server Authentication) database types.
Before Running the Setup Program
Perform the following steps before running the setup program:
1. Create a new user for logging into SQL Server, including the user name and
password.
2. Set the SQL Server to use Windows authentication mode for identity
authentication.
3. Set the iProcess Engine Database as the default database for this user name.
When Running the Setup Program
Perform the following steps when running the setup program:
1. In the Database Configuration Dialog, select SQL Server (SQL Server
Authentication) from the Database Type list.
2. In the Database Configuration Dialog (Continued), do the following:
— In the User ID and Password fields, enter the user name and password of
the user which you created.
— In the Schema Owner field, enter the user name of the iProcess Engine
Tables Owner. By default, the user name is swpro.
TIBCO iProcess Technology Plug-ins Installation
6
| Chapter 1
Preinstallation Tasks
Setting Up SQL Server Windows 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 preinstallation task applies only if you are using Windows authentication
mode for SQL Server identity authentication and you want to install TIBCO
iProcess Java Server Plug-in and TIBCO iProcess Server Plug-in for ActiveMatrix
BusinessWorks with SQL Server (Windows Authentication) database type.
Before Running the Setup Program
Perform the following steps before running the setup program:
1. Set SQL Server to use Windows authentication mode for identity
authentication.
2. Copy the sqljdbc_auth.dll file:
— If you want to install TIBCO iProcess Technology Plug-ins on a machine of
which operating system is Windows (32-bit), copy the sqljdbc_auth.dll
file to the %systemroot%\System32 directory of the machine and make
sure that the PATH system environment variable of the machine includes
the %systemroot%\System32 directory.
— If you want to install TIBCO iProcess Technology Plug-ins on a machine of
which operating system is Windows (64-bit), copy the sqljdbc_auth.dll
file to the C:\WINDOWS\SysWOW64 directory and make sure that the PATH
system environment variable of the machine includes the
C:\WINDOWS\SysWOW64 directory.
You can download the sqljdbc_auth.dll file at
http://www.microsoft.com/en-us/download/details.aspx?id=11774.
TIBCO iProcess Technology Plug-ins Installation
Setting Up SQL Server Windows Authentication 7
|
When Running the Setup Program
Perform the following steps when running the setup program:
1. In the Database Configuration Dialog, select SQL Server (Windows
Authentication) from the Database Type list and click the Browse button to
select the sqljdbc4.jar file as the file to be added to the Specify JAR files
to add to classpath field.
2. In the Database Configuration Dialog (Continued), leave the User ID field,
Password field, and the Schema Owner field empty.
TIBCO iProcess Technology Plug-ins Installation
8
| Chapter 1
Preinstallation Tasks
Setting 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 preinstallation task applies only if you are installing an iProcess Java Server
Plug-in or an iProcess Server Plug-in for ActiveMatrix BusinessWorks.
You have to find out your encoding details for TIBCO iProcess Java Server Plug-in
or iProcess Server Plug-in for ActiveMatrix BusinessWorks 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 it is good practice to use Unicode UTF-8 in most cases. However, if you have
not configured iProcess Engine to support UTF-8 (for example, if upgrading an
existing installation), 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.
Ensure that you have set up the character encoding specification of TIBCO
iProcess Java Server Plug-in and iProcess Server Plug-in for ActiveMatrix
BusinessWorks so that they can correctly translate data formatting to and from
Unicode. Note the following points:
•
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 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 TIBCO iProcess Engine Architecture Guide.
TIBCO iProcess Technology Plug-ins Installation
Exporting Existing JMS Provider Configuration if Upgrading 9
|
Exporting 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 iProcess Server Plug-in for ActiveMatrix BusinessWorks,
you must export your existing JMS provider configuration information as a
backup. It is a mandatory task.
After the upgrade process is finished, you have to re-import the backup JMS
provider configuration information.
The import procedure is described in the troubleshooting instructions — see JMS
Provider Configuration is Lost in an Upgrade Error on page 106.)
Procedure
To export your existing JMS provider configuration:
1. Make sure iProcess Engine is running.
2. Start the JMS Administration Utility:
— From UNIX, navigate to the $SWDIR/jmsadmin folder and type 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 TIBCO iProcess Connector for
ActiveMatrix BusinessWorks User’s Guide.
TIBCO iProcess Technology Plug-ins Installation
10
| Chapter 1
Preinstallation Tasks
Backing 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 are lost. It is good practice to
back up your system before performing this type of installation and re-apply the
patches or hot fixes after the installation is completed.
In addition any changes that you have made to the log4j.properties file are
lost unless you back up that file and restore it after installation is completed.
TIBCO iProcess Technology Plug-ins Installation
Choosing Your Installer 11
|
Choosing 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 17.
After deciding which of these methods to use, refer to the appropriate chapter, as
follows:
— Using the GUI Installer on page 31
— Using the Console Installer on page 39
— Using the Silent Installer on page 47
TIBCO iProcess Technology Plug-ins Installation
12
| Chapter 1
Preinstallation Tasks
TIBCO iProcess Technology Plug-ins Installation
| 13
Chapter 2
Introduction to the Installation Process
This chapter provides an overview of the installation program for TIBCO iProcess
Technology Plug-ins.
Topics
•
Product Overview, page 14
•
Installation Overview, page 16
•
Installation Requirements, page 21
•
Installation with More Than One iProcess Engine, page 28
•
Preparing to Run the Setup Program, page 29
TIBCO iProcess Technology Plug-ins Installation
14
| Chapter 2
Introduction to the Installation Process
Product Overview
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 TIBCO iProcess Engine Administrator's
Guide for more details about sweaireg.) However, note that TIBCO ActiveMatrix
BusinessWorks Plug-in for iProcess is not displayed in this list.
•
TIBCO iProcess Java Server Plug-in - This plug-in enables 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
TIBCO iProcess Engine.
Also note that when you install 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 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 TIBCO Business
Studio™ Process Developer's Guide.
•
TIBCO iProcess Server Plug-in for ActiveMatrix BusinessWorks- This plug-in
provides the communication mechanism that allows the engine to make calls
to TIBCO ActiveMatrix BusinessWorks™ .
When installing this plug-in, you must install it on the same machine as
TIBCO iProcess Engine.
Note that TIBCO iProcess Server Plug-in for ActiveMatrix BusinessWorksis
dependent on the iProcess Java Server Plug-in — that is, if you install TIBCO
iProcess Server Plug-in for ActiveMatrix BusinessWorks, you must also install
TIBCO iProcess Java Server Plug-in. Note also that TIBCO iProcess Server
Plug-in for ActiveMatrix BusinessWorks is not displayed in the list of plug-ins
registered on your TIBCO iProcess Engine.
•
TIBCO ActiveMatrix BusinessWorks™ Plug-in for iProcess - This plug-in
provides a set of resources that allow a TIBCO ActiveMatrix BusinessWorks
process definition to communicate with TIBCO iProcess Engine.
When installing this plug-in, you must install it on the same machine as
TIBCO ActiveMatrix 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 TIBCO ActiveMatrix
TIBCO iProcess Technology Plug-ins Installation
Product Overview 15
|
BusinessWorks Plug-in for iProcess and one or more of the other plug-ins, you
must run the installer twice.
•
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
TIBCO iProcess Engine.
Note that iProcess XML Transform Server Plug-in is dependent on the
iProcess Java Server Plug-in — that is, if you install TIBCO iProcess XML
Transform Server Plug-in, you must also install TIBCO iProcess Java Server
Plug-in.
TIBCO iProcess Technology Plug-ins Installation
16
| Chapter 2
Introduction to the Installation Process
Installation 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:
Figure 1 Installation Types
•
New Installation - This is used to install new TIBCO iProcess Technology
Plug-ins on your system.
Note that you can install multiple instances of TIBCO iProcess Technology
Plug-ins. Each of the multiple plug-ins is associated with a different instance
of TIBCO iProcess Engine. (One of the first steps in the installation procedure
is to specify the TIBCO iProcess Engine that the new plug-in is to be
associated.)
•
Re-install/Repair/Upgrade An Existing Installation - This type of installation
is used in the following two scenarios:
— To “re-install/repair” an existing installation. This returns all of the
configuration settings to their original values, for example, 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 are 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 the current release. This type of
installation presents the same dialogs as a new installation (when
TIBCO iProcess Technology Plug-ins Installation
Installation Overview 17
|
performing a GUI installation), although settings on the dialogs show the
settings that were specified when the plug-ins were originally installed.
Note that if you are upgrading from a previous version you have to specify
the path to the tibjmsadmin.jar file manually. See JMS Provider Details
Dialog on page 89.
•
Re-configure An 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 iProcess Java Server Plug-in, and you select either
“Re-install/Repair/Upgrade An Existing Installation” or “Re-configure An
Existing Installation”, you might be asked to uninstall your existing iProcess Java
Server Plug-in before proceeding.
If this situation arises, and you also have iProcess Server Plug-in for ActiveMatrix
BusinessWorks and/or iProcess Decisions Plug-in installed, they must also be
uninstalled, and, they must be uninstalled in a specific order.
Make sure that you uninstall these products in the following order:
1. Uninstall TIBCO iProcess Decisions Plug-in. See TIBCO iProcess Decisions
Plug-in Installation for more information.
2. Uninstall TIBCO iProcess Server Plug-in for ActiveMatrix BusinessWorks and
TIBCO iProcess Java Server Plug-in.
Run the iProcess Technology Plug-ins installation process to install the upgraded
versions of TIBCO iProcess Server Plug-in for ActiveMatrix BusinessWorks and
TIBCO iProcess Java Server Plug-in. After upgrading, re-install iProcess Decisions
Plug-in.
Installation Modes
TIBCO iProcess Technology Plug-ins can be installed using the following
installation modes:
•
GUI Mode - In GUI mode, the installer displays panels where you can select a
product, product location, and so on. To invoke the installer in GUI mode,
double-click the executable file.
For information about installing in GUI mode, see Using the GUI Installer on
page 31.
TIBCO iProcess Technology Plug-ins Installation
18
| Chapter 2
Introduction to the Installation Process
•
Console Mode - In console mode, you can run the installer on a command
line. This is useful if your machine does not have a GUI environment.
For information about installing in the console mode, see Using the Console
Installer on page 39.
•
Silent Mode - In silent mode, the installer installs the product without
prompting you for information. The installer uses either default or custom
settings that are saved in a response file.
For information about installing in the silent mode, see Using the Silent
Installer on page 47.
•
TIBCO iProcess BusinessEvents Server Plug-in - This plug-in provides an
execution environment for business rules expressed as decision tables in
TIBCO Business Studio. It interfaces the TIBCO Business Events engine with
TIBCO iProcess Engine.
Use TIBCO Business Studio to model, simulate and implement business
processes. Within the business process, services might be invoked to execute
procedures or test conditions. These supported services mi be expressed as
business rules that can be executed by the Business Events runtime engine.
Version 2.0 introduced Concept Models and Decision Tables into Business
Studio as a means of expressing Business Rules.
Install TIBCO iProcess BusinessEvents Server Plug-in to allow execution of
Decision Tables under iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
Installation Overview 19
|
Logging
When you install TIBCO iProcess Technology Plug-ins, log files are created in the
SWDIR\logs folder, where SWDIR is the folder in which iProcess Engine was
installed.
When 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
•
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
TIBCO iProcess Technology Plug-ins Installation
20
| Chapter 2
Introduction to the Installation Process
— swadmBGregerror.log
— swadmBGunreg.log
— swadmBGunregerror.log
— swadmRPCBGreg.log
— swadmRPCBGregerror.log
— swadmRPCBGunreg.log
— swadmRPCBGunregerror.log
— TIBCOiProcessPluginsInstaller.log
TIBCO iProcess Technology Plug-ins Installation
Installation Requirements 21
|
Installation Requirements
This section describes the installation requirements for this product:
•
Disk Space Requirements
•
Supported Systems
•
Supported Databases and Database Drivers
•
Software 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 Server Plug-in for ActiveMatrix
BusinessWorks
15 MB
TIBCO ActiveMatrix BusinessWorks
Plug-in for iProcess
20 MB
iProcess BusinessEvents Server Plug-in
15 MB
iProcess XML Transform Server Plug-in
5 MB
Supported Systems
TIBCO iProcess Technology Plug-ins is supported on the following operating
systems:
TIBCO iProcess Technology Plug-ins Installation
22
| Chapter 2
Introduction to the Installation Process
•
Microsoft Windows
— Windows 7 Professional (32-bit and 64-bit)
— Windows 8 (32-bit and 64-bit)
— Windows 8.1 (32-bit and 64-bit)
— Windows 10 (64-bit)
— Windows Server 2008 (32-bit and 64-bit)
— Windows Server 2008 R2 (64-bit)
— Windows Server 2012 (64-bit)
— Windows Server 2012 R2 (64-bit)
•
Oracle SPARC
— Solaris 11 (64-bit)
— Solaris 10 (64-bit)
•
IBM AIX
— AIX 6.1 (64-bit)
— AIX 7.1 (64-bit)
•
HP Itanium
— HP-UX 11i Version 3 (B.11.31) (64-bit)
•
Linux (64-bit)
— Red Hat Enterprise Linux Server 6.6
— Red Hat Enterprise Linux Server 7.0
— Red Hat Enterprise Linux Server 7.1
— Novell SUSE Linux Enterprise 11 SP3
See the readme 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.
TIBCO iProcess Technology Plug-ins Installation
Installation Requirements 23
|
Microsoft has discontinued standard support for Windows Server 2008 and
Microsoft Windows Server 2008 R2. Extended support is still available, but must
be purchased from Microsoft.
TIBCO will continue to support iProcess Engine on Windows Server 2008 and
Microsoft Windows Server 2008 R2. However, if a problem with iProcess Engine
is reported to TIBCO Support, and the problem is traced to Windows Server 2008
or Microsoft Windows Server 2008 R2 , TIBCO Support will not be able to assist
further with the resolution of that problem.
TIBCO therefore recommends that you install iProcess Engine on Microsoft
Windows Server 2012, Microsoft Windows Server 2012 R2, Windows 7, Windows
8, Windows 8.1, or Windows 10 instead of Windows Server 2008 and Microsoft
Windows Server 2008 R2.
Supported 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:
Database
Database Driver
Oracle 11g release 11.2.0.4
For all Oracle versions, use the
database driver supplied with your
database.
Oracle 12c release 12.1.0.2
DB2 Universal Database 9.7
DB2 Universal Database 10.1
DB2 Universal Database 10.5
SQL Server 2008 R2 SP1
SQL Server 2012
For DB2, use the database driver
supplied with your database. See
https://www-304.ibm.com/support
/docview.wss?uid=swg21363866 if
you need further guidance.
Use Microsoft SQL Server JDBC
Driver 3.0. Within that product, select
the sqljdbc4.jar file.
SQL Server 2014
SQL Server 2016
You must specify the driver location and connection parameters as part of the
iProcess Technology Plug-ins installation. See Database Configuration Dialog on
page 79 and Database Configuration Dialog (Continued) on page 81 for details of
the information that you will need to supply.
TIBCO iProcess Technology Plug-ins Installation
24
| Chapter 2
Introduction to the Installation Process
Microsoft has discontinued standard support for SQL Server 2008 and SQL Server
2008 R2. Extended support is still available, but must be purchased from
Microsoft.
TIBCO will continue to support SQL Server 2008 R2 SP1. However, if a problem
with iProcess Engine is reported to TIBCO Support, and the problem is traced to
SQL Server 2008 R2 SP1, TIBCO Support will not be able to assist further with the
resolution of that problem.
TIBCO therefore recommends that you use SQL Server 2012.
Software Requirements
The following subsections provide information about software requirements for
TIBCO iProcess Technology Plug-ins:
•
TIBCO iProcess Engine
•
TIBCO ActiveMatrix BusinessWorks
•
JMS Providers
•
Java Runtime Environment
•
Java Character Encoding
TIBCO iProcess Engine
The following versions of TIBCO iProcess Engine are supported for this version of
iProcess Technology Plug-ins:
iProcess Engine Version
Validated?
Compatible?
11.6.0
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.
TIBCO iProcess Technology Plug-ins Installation
Installation Requirements 25
|
If you are installing either iProcess Java Server Plug-in or iProcess Server Plug-in
for ActiveMatrix BusinessWorks, they must be installed on the same machine on
which a TIBCO iProcess Engine version 11.6 or higher is installed.
If you are using SQL Server and your user name authentication use Windows
authentication, you must have created a new user name as described in Setting
Up SQL Server Authentication on page 5.
If you are not using Windows authentication, you must install the software using
the TIBCO iProcess Engine Database owner. This user name must also have the
permissions listed in Setting Up SQL Server Authentication on page 5.
iProcess Server Plug-in for ActiveMatrix BusinessWorks 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 ActiveMatrix BusinessWorks
If you are installing TIBCO ActiveMatrix BusinessWorks Plug-in for iProcess, it
must be installed on the same machine on which TIBCO ActiveMatrix
BusinessWorks is installed. Three versions of TIBCO ActiveMatrix BusinessWorks
are supported: 5.9.3, 5.10, 5.11, 5.12, and 5.13.
Note: When installing TIBCO ActiveMatrix BusinessWorks Plug-in for iProcess,
you must log in using a BusinessWorks account.
JMS Providers
The following JMS providers are supported:
JMS Provider
Validated
TIBCO EMS
8.2.1
8.1
8.0
7.0.1
7.0
TIBCO iProcess Technology Plug-ins Installation
26
| Chapter 2
Introduction to the Installation Process
Java Runtime Environment
iProcess Java Server Plug-in and iProcess Server Plug-in for ActiveMatrix
BusinessWorks require specific versions of the Java Runtime Environment (JRE)
and Java Virtual Machine (JVM). This release of iProcess Technology Plug-ins
supports Java 8.
When you install the product on AIX platforms, JRE 1.8.x is supported when
installing TIBCO iProcess Technology Plug-ins version 11.6.0.
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 have to use a different version of the JRE and/or JVM for any reason, it is
good practice to contact TIBCO Support before doing so to determine if the JRE
you want to use is fully compatible with your version of iProcess Engine.
Choosing Correct Java Virtual Machine
This section provides information about choosing the correct Java Virtual
Machine (JVM) when completing the Java Environment field and Java
Environment (Alternate Location) fields in the General Configuration dialog, as
show in figure page 77.
Different JRE implementations can contain multiple JVM libraries. You must
select the correct library required by iProcess Java Server Plug-in, as shown in the
following table.
JRE_HOME is the folder containing the JRE that you want to use. This JRE must
be either the version that is installed on iProcess Engine or a version that is
compatible with it — see Java Runtime Environment on page 26.
Platform
JVM
Required JVM Location
Windows
jvm.dll
JRE_HOME\bin\client or
JRE_HOME\bin\server
Note: If you want to use jvm.dll located in
JRE_HOME\bin\server on Windows
platforms, you need to set the SWJVM_OPTIONS
environment variable. For example:
SWJVM_OPTIONS = -Xms64m -Xmx256m
AIX
TIBCO iProcess Technology Plug-ins Installation
libjvm.a
JRE_HOME/lib/ppc64/classic
Installation Requirements 27
|
Platform
JVM
Required JVM Location
Oracle SPARC
Solaris
libjvm.so
JRE_HOME/lib/sparcv9/server
HP-UX IA64
Itanium
libjvm.so
JRE_HOME/lib/IA64N/server
Linux
libjvm.so
JRE_HOME/lib/amd64/server
For example, suppose you are installing iProcess Server Plug-in for ActiveMatrix
BusinessWorks on one iProcess Engine Version 11.6 on Windows, which is
installed in C:\swserver\staffw_nod1. If you want to use a JRE Version 1.8.0
that is compatible with iProcess Engine, you have to specify the Java Environment
folder as:
C:\j2sdk1.8.0\jre\bin\client
Java Character Encoding
You must ensure that you use a version of Java that provides the necessary
character encoding set support with iProcess Technology Plug-ins.
See Appendix C, Java Character Encoding Sets, on page 107 for more information
about how to do this.
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
28
| Chapter 2
Introduction to the Installation Process
Installation with More Than One iProcess Engine
The assumption is that iProcess Client Plug-in for ActiveMatrix BusinessWorks
(delivered and installed as part of iProcess Workspace Plug-ins) are used with one
instance of iProcess Engine and iProcess Server Plug-in for ActiveMatrix
BusinessWorks.
This is because the introspection of the definition of a BusinessWorks step created
using iProcess Client Plug-in for ActiveMatrix BusinessWorks comes from the
server, via JMX. Therefore, the same server is required 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 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 17
for details of this option.
TIBCO iProcess Technology Plug-ins Installation
Preparing to Run the Setup Program 29
|
Preparing to Run the Setup Program
This section describes preparations you have to do to run the setup program on
UNIX systems.
Before you install iProcess Technology Plug-ins:
1. Make sure that the iProcess Background User (see Running the GUI Installer
on page 33) has write permissions to the $SWDIR folder and a home folder.
Otherwise, the installation fails.
2. In some UNIX systems, installation fails if you include \u in the prompt PS1.
Normally \u causes the user name 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 folder
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 might
fail.
TIBCO iProcess Technology Plug-ins Installation
30
| Chapter 2
Introduction to the Installation Process
TIBCO iProcess Technology Plug-ins Installation
| 31
Chapter 3
Using the GUI Installer
This chapter introduces how to perform a GUI installation.
Topics
•
About the GUI Installer, page 32
•
Running the GUI Installer, page 33
TIBCO iProcess Technology Plug-ins Installation
32
| Chapter 3
Using the GUI Installer
About the GUI Installer
In GUI mode, the installer displays panels where you can select a product,
product location, and so on. To invoke the installer in GUI mode, double-click the
executable file.
Details about the information in the installer dialogs is provided in the
Installation Data Reference appendix on page 75. This prevents duplication of
information in this manual because the same information is needed for the
console and silent installation methods.
TIBCO iProcess Technology Plug-ins Installation
Running the GUI Installer 33
|
Running the GUI Installer
To install TIBCO iProcess Technology Plug-ins, perform the following steps:
1. Log in with a suitable user name. To install ActiveMatrix BusinessWorks
Plug-in for iProcess, 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).
— on UNIX, this is pro by default (also referred to as the “Background” user
on UNIX).
— on Windows, this is specified when iProcess Engine is installed (it is the
user installing the iProcess Engine by default).
For more information, see the Installation guide for TIBCO iProcess Engine.
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
Oracle SPARC: Solaris
setupSolaris.bin
AIX
setupaix
HP Itanium
setupHPIA64.bin
Linux
setupLinux.bin
Type 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.8
or:
setupwindows32.exe -is:javahome d:\program files\java
TIBCO iProcess Technology Plug-ins Installation
34
| Chapter 3
Using the GUI Installer
This parameter might 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 in 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 the Cancel
button in any dialog.
4. Review the terms of the license agreement:
— If you agree to the terms, select 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, select I do not
accept the terms of the license agreement and exit from the installation
process by clicking 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 Next. The following installation types are available.
— New installation
— Re-install, repair, or upgrade an existing 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. It is good practice to back up your system before performing this type of
installation. See Backing Up Your System if Re-installing or Repairing, page 10.
— Reconfigure an existing installation
For information about these types of installations, see Installation Overview
on page 16.
6. If you select the “Re-install, repair,...” type of installation, the following
dialog is displayed, warning you that configuration settings are reset to their
original values in this type of installation. If you are sure you want to re-install
the original files, click Yes to continue, or No to return to the Installation Mode
dialog.
TIBCO iProcess Technology Plug-ins Installation
Running the GUI Installer 35
|
Figure 2 The Re-install or Repair Installation Warning Dialog.
7. If you select New Installation in step 5, the Destination dialog is displayed:
Figure 3 The Destination Dialog
The installer selects the location of the TIBCO iProcess Engines (Nodes) on
your system (at least one must be installed prior to installing the plug-ins —
see Supported Systems on page 21) and enter them in the iProcess Node field.
8. Complete the Destination dialog as follows:
a. Leave the Specify SWDIR check box selected if you are installing any
plug-in other than the ActiveMatrix BusinessWorks Plug-in for iProcess.
All of the TIBCO iProcess Technology Plug-ins (with the exception of the
ActiveMatrix BusinessWorks Plug-in for iProcess) are associated with a
specific iProcess Engine, and need SWDIR specified.
The Specify SWDIR check box must be cleared to install the ActiveMatrix
BusinessWorks Plug-in for iProcess, which is not associated with an
iProcess Engine and does not need SWDIR setting. Note that when you clear
the check box, the iProcess Node field becomes disabled (because you don’t
need to select an iProcess Node (Engine) if you are only installing a
ActiveMatrix BusinessWorks Plug-in for iProcess). Clearing the Specify
SWDIR check box also prevents you from choosing to install any of TIBCO
TIBCO iProcess Technology Plug-ins Installation
36
| Chapter 3
Using the GUI Installer
iProcess Technology Plug-ins other than ActiveMatrix BusinessWorks
Plug-in for iProcess.
b. If you are installing only an ActiveMatrix BusinessWorks Plug-in for
iProcess, proceed to step 9.
If you are installing any plug-in other than ActiveMatrix BusinessWorks
Plug-in for iProcess, select the iProcess Engine to which you want to
associate this installation of TIBCO iProcess Technology Plug-ins from the
iProcess Node field.
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; 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 folder you select is duplicated. You
must manually delete one of the duplicated folder names from the path after
using the Browse button.
9. Click Next, the Features dialog is displayed.
Figure 4 The Features Dialog
TIBCO iProcess Technology Plug-ins Installation
Running the GUI Installer 37
|
On this dialog, you can select the plug-ins that you want to install. The plug-in
you select determines 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 34), this dialog displays version numbers for those plug-ins which are
already installed on your system. Note that these are the numbers of the
versions already installed - for example, 10.7.0.0 - not the current release that
you are now installing.
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
ActiveMatrix BusinessWorks Plug-in for iProcess. That is, if you install any of
the plug-ins (except the ActiveMatrix BusinessWorks Plug-in for iProcess),
you must also install the iProcess Java Server Plug-in.
10. Use the subsections in Appendix A, Installation Data Reference on page 75,
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 you are installing.
The following table lists the dialogs displayed for each plug-in, and the page
to reference for information about that dialog:
Plug-in
Dialogs Displayed
See...
TIBCO iProcess Java
Server Plug-in
•
General Configuration Dialog
page 76
•
Database Configuration Dialog
page 79
•
Database Authentication Dialog
page 81
•
General Configuration Dialog
page 76
•
Database Configuration Dialog
page 79
•
Database Authentication Dialog
page 81
•
iProcess Server Plug-in for ActiveMatrix
page 90
TIBCO iProcess Server
Plug-in for
ActiveMatrix
BusinessWorks
BusinessWorks Configuration Dialog
TIBCO ActiveMatrix
BusinessWorks Plug-in
for iProcess
•
None — installing this plug-in does not require you to
enter any configuration parameters.
n/a
TIBCO iProcess Technology Plug-ins Installation
38
| Chapter 3
Using the GUI Installer
Plug-in
Dialogs Displayed
See...
TIBCO iProcess
BusinessEvents Server
Plug-in
•
General Configuration Dialog
page 76
•
Database Configuration Dialog
page 79
•
Database Connection Dialog
page 81
•
General Configuration Dialog
page 76
•
Database Configuration Dialog
page 79
•
Database Authentication Dialog
page 81
TIBCO iProcess XML
Transform Server
Plug-in
11. After completing each necessary dialog, click Next to proceed in the
installation process.
When all of the necessary dialogs have been completed for the selected
plug-ins, the Pre-Installation Summary is displayed. This screen provides a
summary of the plug-ins you are installing.
12. If you are satisfied with the summary, click Install. (You can also click Back to
return to any dialog to make changes.)
The installer copies the necessary files to your system and informs you when
it is finished.
13. Click Finish to complete the installation.
TIBCO iProcess Technology Plug-ins Installation
| 39
Chapter 4
Using the Console Installer
This chapter describes how to install 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
In console mode, you can run the installer on a command line. This is useful if
your machine does not have a GUI environment. This mode presents a series of
prompts that request the same information that you enter in the dialogs presented
in GUI 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 33.
To install the software in console mode, follow these steps:
1. Log in with a suitable user name. To install ActiveMatrix BusinessWorks
Plug-in for iProcess, 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).
— on UNIX, this is pro by default (also referred to as the “Background” user
on UNIX).
— on Windows, this is specified when the iProcess Engine is installed, which
is the user installing the iProcess Engine by default.
For more information, see the Installation guide for TIBCO iProcess Engine.
2. Type 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 33.
For example:
setupwindows32.exe -console
A welcome message is displayed.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Console Mode 41
|
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 press 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. Press ENTER submits that value.
3. Type 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 information is displayed:
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 information is displayed:
6. Select the type of installation you want to perform.
For a description of the types of installation you can perform, see Appendix
on page 16.
A prompt is displayed that shows your selection:
TIBCO iProcess Technology Plug-ins Installation
42
| Chapter 4
Using the Console Installer
The prompt shown above appears a number of times in the console mode. Press
the number to perform the corresponding operation.
— 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.
— Press 5 to redisplay the current prompt (the Installation Mode prompt in
this particular case).
7. When you are satisfied, type 1 to proceed to the next prompt.
The following information 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 ActiveMatrix
BusinessWorks Plug-in for iProcess. All of the TIBCO iProcess Technology
Plug-ins with the exception of ActiveMatrix BusinessWorks Plug-in for
iProcess are associated with a specific iProcess Engine, and need SWDIR
specified.
b. Do not specify SWDIR if you are installing only ActiveMatrix
BusinessWorks Plug-in for iProcess that is not associated with an iProcess
Engine and does not need SWDIR. Note that if you do not specify SWDIR,
the installer installs only ActiveMatrix BusinessWorks Plug-in for iProcess.
Your response to the Specify SWDIR prompt determines 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:
TIBCO iProcess Technology Plug-ins Installation
Installing Using Console Mode 43
|
This prompt is used to specify the TIBCO iProcess Node (Engine) to which
you want 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.
An an additional prompt is displayed, 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 typing the appropriate number.
You can select multiple plug-ins by typing multiple numbers before
proceeding by typing 0 (zero).
You can also deselect a plug-in by re-typing the number of the plug-in; 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 ActiveMatrix
BusinessWorks Plug-in for iProcess. That is, if you select any of the plug-ins
except the ActiveMatrix BusinessWorks Plug-in for iProcess, the iProcess Java
Server Plug-in is automatically selected.
Also note that the ActiveMatrix BusinessWorks Plug-in for iProcess 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 ActiveMatrix BusinessWorks Plug-in for iProcess and one or
more of the other plug-ins, you must run the installer twice.
After typing 0 (zero), the installer prompts which plug-ins have been selected
to be installed.
11. Type 1 to proceed to the next prompt.
TIBCO iProcess Technology Plug-ins Installation
44
| Chapter 4
Using the Console Installer
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 76
•
Database Configuration Dialog
page 79
•
Database Authentication Dialog
•
General Configuration Dialog
page 76
•
Database Configuration Dialog
page 79
•
Database Connection Dialog
page 81
•
iProcess Server Plug-in for ActiveMatrix
page 90
TIBCO iProcess Server
Plug-in for
ActiveMatrix
BusinessWorks
page 81
BusinessWorks Configuration Dialog
TIBCO ActiveMatrix
BusinessWorks Plug-in
for iProcess
•
None — installing this plug-in does not require you to
enter any configuration parameters.
n/a
TIBCO iProcess
BusinessEvents Server
Plug-in
•
General Configuration Dialog
page 76
•
Database Configuration Dialog
page 79
•
Database Authentication Dialog
•
General Configuration Dialog
page 76
•
Database Configuration Dialog
page 79
•
Database Authentication Dialog
TIBCO iProcess XML
Transform Server
Plug-in
page 81
page 81
12. Enter the appropriate information at each prompt; then proceed.
The Pre-Installation Summary is displayed.
13. Review the information in the Pre-Installation Summary; then when you are
satisfied, type 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:
TIBCO iProcess Technology Plug-ins Installation
Installing Using Console Mode 45
|
14. Type 3; then press ENTER to complete the installation of the TIBCO iProcess
Technology Plug-ins.
TIBCO iProcess Technology Plug-ins Installation
46
| Chapter 4
Using the Console Installer
TIBCO iProcess Technology Plug-ins Installation
| 47
Chapter 5
Using the Silent Installer
This chapter describes how to install iProcess Technology Plug-ins using silent
mode.
Topics
•
Generating a Response File, page 48
•
Password Encryption, page 50
•
Performing a Silent Installation, page 51
•
Response File Details, page 53
TIBCO iProcess Technology Plug-ins Installation
48
| Chapter 5
Using the Silent Installer
Installing Using Silent Mode
In silent mode, the installer installs the product 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 when
performing a GUI or console installation from the command line or terminal. It
must be in one of the following forms:
Note that there is no space between -options and -record.
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 33.
All parameter values that are entered during GUI or console mode 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.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 49
|
For more information about the response file, see Response File Details on
page 53.
TIBCO iProcess Technology Plug-ins Installation
50
| Chapter 5
Using the Silent Installer
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 48, the response file includes 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 added in the classpath.
2. Invoke the main method in class
com.staffware.integration.utils.java.library.encrypt.DESEncrypt
erEx
You can achieve this by creating and using a wrapper script. The following
example shows how to create a script in the Windows environment to invoke
the method.
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 $
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 51
|
3. Invoke your script by typing the name you have given it at the command
prompt.
4. Type the database password. The password is not echoed to the screen; the
characters that you type are replaced by asterisks.
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 57 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 48).
To install the software in silent mode, follow these steps:
1. Log in with a suitable user name.
To install ActiveMatrix BusinessWorks Plug-in for iProcess, 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):
— on UNIX, this is pro by default (also referred to as the “Background” user
on UNIX).
— on Windows, this is specified when the iProcess Engine is installed (it is the
user installing the iProcess Engine by default).
For more information, see the Installation guide for TIBCO iProcess Engine.
2. Generate a response file — see Generating a Response File on page 48. 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 is performed silently, with no dialogs/prompts displayed.
The command line returns when the installation is finished — be patient; it
might take a few minutes.
TIBCO iProcess Technology Plug-ins Installation
52
| Chapter 5
Using the Silent Installer
Viewing the Log File
You can check 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
Installing Using Silent Mode 53
|
Value
Description
-53
Invalid option selected.
Response File Details
Although a response file could be manually created, it is good practice to generate
one using a GUI or console installation as instructed in Generating a Response
File on page 48.
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 might 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 might be lifted in a later release.
is one of the keywords listed in the table on page 53.
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
54
| Chapter 5
Using the Silent Installer
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 is always be “true” and the “reject” keyword is
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 Installation Overview on
page 16.
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 ActiveMatrix BusinessWorks Plug-in for iProcess,
this value is empty.
SWInstallJavaServerPlugIn
SWInstalliPEBWServerPlugIn
These identify the individual plug-ins you want to
install.
Valid entries: “true” or “false”
SWInstallBWiPEServerPlugIn
SWInstallBEServerPlugIn
SWInstalliPXMLTransformServerPlugIn
SWPath
See Update System Path on page 76.
Valid entries: “true” or “false”
Note: (This applies to Windows only.) SWPATH must be
set to true so that your system PATH environment
variable is updated to include a reference to the Java
Runtime Environment (JRE) location otherwise TIBCO
iProcess Technology Plug-ins is not installed correctly.
SWServerProxy
See Use HTTP Proxy Server on page 77.
Valid entries: “true” or “false”
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 55
|
Keyword
Description
SWServerProxyServer
See Proxy Server on page 77.
SWServerProxyPort
See Port Number on page 77.
SWEncoding
See Character Encoding on page 78.
SWJavaLocation
See Java Environment on page 77.
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)”
— “DB2”
— “Oracle Real Application Cluster (RAC)”
For more information, see Database Type on page 80.
SWDatabaseTypeEnc
This must be one of the following strings:
— “Oracle”
— “SQLServer”
— “DB2”
SWDatabaseHost
See Host on page 85.
SWDatabasePort
See Port on page 86.
SWDatabaseInstance
This keyword is used for the Instance field in Oracle
systems and the DB Name field in DB2 systems. See
Instance on page 86 and DB Name on page 86.
SWDatabaseUser
See User ID on page 86.
TIBCO iProcess Technology Plug-ins Installation
56
| Chapter 5
Using the Silent Installer
Keyword
Description
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 50.
See Password on page 87.
SWDatabaseSchema
See Schema Owner on page 87.
SWJDBC
See JDBC URL on page 88.
SWComms
See Enable Client Plug-in Connections on page 90.
Valid entries: “true” or “false”
SWJMXPort
See Port Number on page 91.
jdbc_0_alias
Mandatory. The only value accepted is "internal":
jdbc_0_alias="internal"
See Database Configuration Dialog on page 79.
jdbc_0_classpath
Mandatory.
There is no default value.
See Database Configuration Dialog on page 79.
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 JMS Provider Details Dialog on page 89.
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 JMS Provider Details Dialog on page 89.
TIBCO iProcess Technology Plug-ins Installation
Installing Using Silent Mode 57
|
Response File Example
The following is an example response file, without the comments (for example,
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 SWInstalliPXMLTransformServerPlugIn=”false”
-V SWWeblogic92RadioButton=”false”
-V SWWeblogic81RadioButton="false"
-V SWWeblogic1034RadioButton="false"
-V SWJboss40RadioButton=”true”
-V SWJboss32RadioButton=”false”
-V SWJboss51RadioButton="false"
-V SWconfigLocation=”C:/jboss/auth.conf”
-V SWJBOSSCLIENTJAR=”C:/jboss/jbossall-client.jar”
-V SWCOM_SERVER_URL_JBOSS=”jnp://liberty:1099”
-V SWJBossHome="D:\tools\jboss-eap-4.3\jboss-as"
-V SWPath=”true”
-V SWServerProxy=”false”
-V SWServerProxyServer=””
-V SWServerProxyPort=””
-V SWEncoding=”Cp1252”
-V SWJavaLocation=”C:/jdk1.8.0_66/jre/bin/client”
-V SWAuditUser="swadmin"
-V SWAuditMessage="EAIJava"
TIBCO iProcess Technology Plug-ins Installation
58
| Chapter 5
Using the Silent Installer
-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
| 59
Chapter 6
Postinstallation Tasks
This chapter describes the tasks that you need to perform after you install TIBCO
iProcess Technology Plug-ins. Some of these tasks apply only if you are installing
on particular databases or operating systems.
After installing TIBCO iProcess Technology Plug-ins, you have to add the IP
address and the corresponding computer name of the machines where TIBCO
ActiveMatrix BusinessWorks, TIBCO iProcess Workspace, and TIBCO iProcess
Technology Plug-ins are installed in the host file respectively.
Topics
•
Running BWC Tool, page 60
•
Configuring JNDI Password Encryption (Upgrade Only), page 63
•
Using the $SWDIR/eaijava/scripts/env.sh Script (UNIX Only), page 64
•
Run the SQL Server Surface Area Configuration Utility, page 65
•
Manually Remove the ISMP Directories, page 66
•
Configure the XML Step Definitions Cache, page 67
•
Replace the 32-bit Library with the 64-bit Library, page 68
TIBCO iProcess Technology Plug-ins Installation
60
| Chapter 6
Postinstallation Tasks
Running BWC Tool
From this release, ActiveMatrix BusinessWorks Service Agent can connect to the
database that the iProcess engine is used by running the BWC tool.
After installing TIBCO iProcess Technology Plug-ins, the following two options
are added in the eaijavaplugin.properties file located in the SWDIR/eaijava
directory:
—
eaijava.db_use_new_mechanism=true
—
eaijava.db_use_bw_config=true
If the value of the eaijava.db_use_new_mechanism option is any value not true
or empty, the plug-in takes the value as false.
By default, these two options are set to true. After running the BWC tool, a
BWCTool.cfg file is generated, which is used by BusinessWorks Service Agent to
access the IPE database. Therefore, when a delayed release error occurs, TIBCO
ActiveMatrix BusinessWorks Plug-in for iProcess calls the
SW_DELAYED_RELEASE_ERR stored procedure in the iProcess database to send the
error message to iProcess engine.
•
If you want to use the old mechanism of the 11.4 release for the Delayed
Release function, you have to set the eaijava.db_use_new_mechanism
option to false.
•
If you want to use the mechanism of the 11.5 release for the Delayed Release
function, you have to set the eaijava.db_use_new_mechanism option to
true and the eaijava.db_use_new_mechanism option to false.
Before running the tool, make sure the JDK path in the BWCTool.tra file that
currently in use is correct.
To run the BWC tool, follow these steps:
1. Copy the JDBC driver of the iProcess Engine database to the
TIBCO_HOME/bw/version/lib folder.
TIBCO iProcess Technology Plug-ins Installation
Running BWC Tool 61
|
2. Add the JDBC path to TIBCO class path in the BWCTool.tra file located in
the the TIBCO_HOME/bw/plugins/iprocess/bin folder:
— On Windows, add
tibco.class.path.extended=%TIBCO_BW_PLUGIN_HOME%/lib/palette
s; JDBC path
— On UNIX, add
tibco.class.path.extended=%TIBCO_BW_PLUGIN_HOME%/lib/palette
s: JDBC path
If you are using Windows authentication mode for SQL Server identity
authentication, you also have to copy the sqljdbc_auth.dll file to the system
path:
— If you want to run the BWC tool on a machine of which operating system
is Windows (32-bit), copy the sqljdbc_auth.dll file to the
%systemroot%\System32 directory of the machine and make sure that the
PATH system environment variable of the machine includes the
%systemroot%\System32 directory.
— If you want to the BWC tool on a machine on a machine of which operating
system is Windows (64-bit), copy the sqljdbc_auth.dll file to the
C:\WINDOWS\SysWOW64 directory and make sure that the PATH system
environment variable of the machine includes the C:\WINDOWS\SysWOW64
directory.
You can download the sqljdbc_auth.dll file at
http://www.microsoft.com/en-us/download/details.aspx?id=11774.
3. Open the TIBCO_HOME/bw/plugins/iprocess/bin folder and run BWCTool.
A command prompt is displayed.
TIBCO iProcess Technology Plug-ins Installation
62
| Chapter 6
Postinstallation Tasks
4. Enter 1 to add a new configuration; then press Enter.
5. Provide the iProcess engine and database information accordingly when you
are prompted.
6. Press 0 (zero) to exit the command prompt.
After running the BWC tool, a BWCTool.cfg file is generated with provided
database information in the TIBCO_HOME/bw/plugins/lib/palettes directory,
which is used by BusinessWorks Service Agent to connect to the database.
TIBCO iProcess Technology Plug-ins Installation
Configuring JNDI Password Encryption (Upgrade Only) 63
|
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. Shut down Ensure iProcess Engine.
2. Run the JMS Administration Utility from the command line as follows:
— From UNIX, navigate to the SWDIR/jmsadmin folder and type the
following command:
jmsadmin.sh eaijava.jmx_listener=enable upgrade
— From Windows, navigate to the SWDIR\jmsadmin folder and type the
following command:
jmsadmin.bat eaijava.jmx_listener=enable upgrade
This generates a database-specific drop/create SQL scripts (Oracle.sql or
SQLServer.sql or DB2.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 iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
64
| Chapter 6
Postinstallation Tasks
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. Type the command:
. $SWDIR/eaijava/scripts/env.sh
You must run this script every time before you start the Process Sentinels.
You can 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 can add a call to env.sh into the
$SWDIR/etc/swstart_env. For example:
. $SWDIR/eaijava/scripts/env.sh
This is automatically picked up by swstart
TIBCO iProcess Technology Plug-ins Installation
-p.
Run the SQL Server Surface Area Configuration Utility 65
|
Run the SQL Server Surface Area Configuration Utility
This postinstallation task is required only if you are installing or upgrading
TIBCO iProcess Technology Plug-ins, and using SQL Server 2008 R2 with Service
Pack 1.
If you are performing a new installation under SQL Server 2008 R2 with Service
Pack 1, or upgrading to Service Pack 1, you might encounter an error at run time.
When you use ActiveMatrix BusinessWorks Plug-in for iProcess from TIBCO
Designer and execute a Start Case on iProcess Engine, a SQL Server error message
is generated warning you to enable OLE using the Server Surface Area
Configuration utility.
To run the Server Surface Area Configuration utility, complete these steps:
1. Stop 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 iProcess
Engine.
TIBCO iProcess Technology Plug-ins Installation
66
| Chapter 6
Postinstallation Tasks
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 folder of the user you are logged in as when you
perform the install. It is good practice to 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
Configure the XML Step Definitions Cache 67
|
Configure the XML Step Definitions Cache
This step applies only if you have chosen to install the iProcess Connector for
ActiveMatrix BusinessWorks.
To improve runtime performance and reduce CPU load, the XML step definitions
for iProcess Connector for ActiveMatrix BusinessWorks 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 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
68
| Chapter 6
Postinstallation Tasks
Replace the 32-bit Library with the 64-bit Library
•
This task is only required if you install the TIBCO ActiveMatrix
BusinessWorks Plug-in version 11.5.0 or previous for iProcess into a 64-bit
TIBCO Runtime Agent (TRA).
•
For Process Technology Plug-in 11.5, the correct iProcess Server Objects (Java)
version is 11.4.1.
To replace the 32-bit library with the 64-bit library from the appropriate TIBCO
iProcess Server Objects (Java) release, complete the following stepsOn UNIX:
1. From TIBCO Support, obtain the correct iProcess Server Objects (Java) release
for the version of the plug-in and the platform type.
2. Extract the install software to a temporary folder.
3. Go to the temporary folder and locate the lib64 folder. This folder contains
the 64-bit library libssoJNI.so.
4. Copy the libssoJNI library from the lib64 folder and overwrite the file
under TIBCO_HOME/bw/plugins/lib.
On Windows:
1. From TIBCO Support, obtain the correct iProcess Server Objects (Java) release
for the version of the plug-in and the platform type.
2. Install the software to a temporary folder.
3. Go to the temporary folder and locate the x64 folder. This folder contains the
following 64-bit libraries:
•
ssoJNI.dll
•
icudt36.dll
•
icuuc36.dll
4. Copy these libraries from the x64 folder and overwrite the files under
TIBCO_HOME\bw\plugins\bin.
TIBCO iProcess Technology Plug-ins Installation
| 69
Chapter 7
Uninstalling TIBCO iProcess Technology
Plug-ins
This chapter describes how to uninstall the plug-ins included in TIBCO iProcess
Technology Plug-ins.
Topics
•
Uninstalling TIBCO iProcess Technology Plug-ins From Windows, page 70
•
Uninstalling TIBCO iProcess Technology Plug-ins From UNIX, page 72
TIBCO iProcess Technology Plug-ins Installation
70
| Chapter 7
Uninstalling TIBCO iProcess Technology Plug-ins
Uninstalling TIBCO iProcess Technology Plug-ins From Windows
The following subsections describe how to uninstall TIBCO iProcess Technology
Plug-ins from Windows systems.
Uninstalling the iProcess Engine-Based Plug-ins from Windows
TIBCO iProcess Technology Plug-ins must be uninstalled using the uninstall
program supplied with the software and not via the Add or Remove Programs in
the Control Panel.
Complete the following steps to safely uninstall the appropriate instance of the
plug-in:
1. Log in as a user who has administrative privileges.
2. Stop TIBCO iProcess Engine to which the plug-in you are uninstalling is
associated.
3. With Windows Explorer, navigate to the “uninstaller” folder that was created
when the TIBCO iProcess Technology Plug-ins were installed. This folder was
added to the TIBCO iProcess Engine folder when the plug-ins were installed:
— SWDIR\_uninstCombinedInstaller
where SWDIR is the home folder for iProcess Engine to which the TIBCO
iProcess Technology Plug-ins you want to uninstall are associated.
4. Execute the uninstall.exe program from the uninstaller folder.
The Welcome dialog is displayed.
5. Review the information in 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 to uninstall.
ActiveMatrix BusinessWorks Plug-in for iProcess has its own uninstaller and
must be uninstalled in a separate session to the other Technology Plug-ins.
Select the appropriate plug-in that you want to uninstall; then click Next.
The Summary dialog is displayed.
6. Review the information about the plug-in to be uninstalled; then click
Uninstall.
The uninstaller informs you when it is finished.
TIBCO iProcess Technology Plug-ins Installation
Uninstalling TIBCO iProcess Technology Plug-ins From Windows 71
|
7. Click Finish to complete the uninstallation.
Uninstalling the BusinessWorks Plug-in for iProcess from Windows
To uninstall ActiveMatrix BusinessWorks Plug-in for iProcess from Windows
systems:
1. Navigate to the following folder:
BWHome\tools\universal_installer
where BWHome is the TIBCO ActiveMatrix BusinessWorks home folder.
2. Run TIBCOUniversalInstaller.exe uninstall program.
The uninstall program step you through a series of dialogs to uninstall the
plug-in.
TIBCO iProcess Technology Plug-ins Installation
72
| Chapter 7
Uninstalling TIBCO iProcess Technology Plug-ins
Uninstalling TIBCO iProcess Technology Plug-ins From UNIX
The following subsections describe how to uninstall the TIBCO iProcess
Technology Plug-ins from UNIX systems.
Uninstalling the iProcess Engine-Based Plug-ins from UNIX
This section describes how to uninstall 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 folder). This includes all of the TIBCO
iProcess Technology Plug-ins except ActiveMatrix BusinessWorks Plug-in for
iProcess. For more information about uninstalling ActiveMatrix BusinessWorks
Plug-in for iProcess, see Uninstalling the BusinessWorks Plug-in for iProcess from
UNIX on page 73).
1. Log in as the iProcess Engine background user (typically pro on UNIX).
2. Stop TIBCO iProcess Engine to which the plug-in you are uninstalling is
associated.
3. Uninstall the plug-in by executing the uninstall command located in the
“uninstall” folder, which was added to the TIBCO iProcess Engine folder
when the plug-in was installed.
The table below lists the uninstall command/folder for the supported UNIX
platforms.
Platform
Uninstall Command
AIX
$SWDIR/_uninstCombinedInstaller/uninstall
HP-UX Itanium
$SWDIR/_uninstCombinedInstaller/uninstallHPIA64.b
in
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. Deselect any that you want to keep and click Next.
6. Read the summary information, then click Uninstall to uninstall the plug-in.
TIBCO iProcess Technology Plug-ins Installation
Uninstalling TIBCO iProcess Technology Plug-ins From UNIX 73
|
7. Click Finish to complete the uninstall process.
Uninstalling the BusinessWorks Plug-in for iProcess from UNIX
To uninstall the ActiveMatrix BusinessWorks Plug-in for iProcess from UNIX
systems:
1. Navigate to the following folder:
BWHome/tools/universal_installer
where BWHome is the TIBCO ActiveMatrix BusinessWorks home folder.
2. Run the TIBCOUniversalInstaller.bin uninstall program.
If you are removing the ActiveMatrix BusinessWorks Plug-in for iProcess from an
HP-UX 11.23 64-bit system, the TIBCOUniversalInstaller.bin program may be
missing from the .../universal_installer folder. In this case, use the
following command to invoke the uninstall program:
java -cp uninstaller.jar run
The uninstall program step you through a series of dialogs to uninstall the
plug-in.
TIBCO iProcess Technology Plug-ins Installation
74
| Chapter 7
Uninstalling TIBCO iProcess Technology Plug-ins
TIBCO iProcess Technology Plug-ins Installation
| 75
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 76
•
Database Configuration Dialog, page 79
•
Database Configuration Dialog (Continued), page 81
•
JMS Provider Details Dialog, page 89
•
iProcess Server Plug-in for ActiveMatrix BusinessWorks Configuration
Dialog, page 90
TIBCO iProcess Technology Plug-ins Installation
76
| 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.
Figure 5 The General Configuration Dialog
The following table describes the information that is specified in the General
Configuration dialog.
Field
Description
Update System Path
Note: This applies to Windows only.
Select the Update System Path check 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
check box, otherwise TIBCO iProcess Technology Plug-ins is not
installed correctly.
TIBCO iProcess Technology Plug-ins Installation
General Configuration Dialog 77
|
Field
Description
Java Environment
Select the directory of the Java Runtime Environment you want to
use. The drop-down list lists the available JREs on your system. If
the JRE you want to use is not on the list, select Alternate location
from the drop-down list; then the Java Environment (Alternate
Location) field is enabled.
Note: The directory that appears must point to the library
directory underneath the JRE installation directory. For example, if
the JRE is installed in C:\Program Files\Java\j2re1.8.0_66,
the Java Environment field must contain C:\Program
Files\Java\j2re1.8.0_66\bin\client.
See Java Runtime Environment on page 26 for more information.
For more information about choosing the correct JVM location, see
Choosing Correct Java Virtual Machine on page 26.
Java Environment (Alternate
Location)
Use this field 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 Browse to browse to the desired path.
Note: A known issue is detected 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
Select this check box if you use a proxy server to connect to the
Internet for HTTP requests. The Proxy Server and Port Number
fields are enabled. If you do not use a proxy server, leave this
check box cleared.
Proxy Server
Enter the path to the proxy server you are using for HTTP
connections if applicable.
You must select the Use HTTP Proxy Server check box to enable
this field.
Port Number
Enter the port number used by the proxy server you are using for
HTTP connections (if applicable).
You must select the Use HTTP Proxy Server check box to enable
this field.
TIBCO iProcess Technology Plug-ins Installation
78
| Appendix A
Installation Data Reference
Field
Description
Character Encoding
Enter the encoding property that matches the encoding used on
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 is a different value (for example
Cp1252 for a Windows machine).
For more information about the encoding property, see Setting Up
Character Encoding on page 8. 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 TIBCO iProcess Engine
Architecture Guide.
Audit User
Enter the iProcess user name such as swadmin that is displayed in
the audit entry.
Audit Message
Enter the message that is displayed in the audit entry.
TIBCO iProcess Technology Plug-ins Installation
Database Configuration Dialog 79
|
Database Configuration Dialog
The Database Configuration dialog is used to specify database connection
information.
Figure 6 The Database Configuration Dialog
The following table describes the information that is specified in the Database
Configuration dialog.
TIBCO iProcess Technology Plug-ins Installation
80
| Appendix A
Installation Data Reference
Field
Description
Database Type
Select the type of database that your iProcess Engine is using. You can
select the following database type:
•
Oracle
•
SQL Server (SQL Server Authentication)
•
SQL Server (Windows Authentication)
•
Oracle Real Application Cluster (RAC)
•
DB2
If you are using Windows authentication mode for SQL Server identity
authentication and select SQL Server (SQL Server Authentication) from
the Database Type list, see Setting Up SQL Server Authentication on
page 5 for more information.
If you are using Windows authentication mode for SQL Server identity
authentication and select SQL Server (Windows Authentication) from the
Database Type list, see Setting Up SQL Server Windows Authentication on
page 6 for more information.
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 might fail if a
basic installation of iProcess Engine was performed without first setting up
a database that is, you let the engine installation program 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 reinstall the plug-ins.
Configure Classpath for Provider
Specify JAR files to
add to classpath
Current Provider
Classpath
Browse for and select the JAR file of the provider. 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. 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) 81
|
Database Configuration Dialog (Continued)
The second Database Configuration dialog is used to specify authentication
details for the database connection.
The configuration items displayed on the second Database Configuration dialog
differ depending on which database type is selected from the Database Type list
in the Database Configuration Dialog.
The following figures show the specific fields displayed on the second Database
Configuration dialog when a different database type is selected.
Figure 7 Select the SQL Server (Windows Authentication) Database Type
TIBCO iProcess Technology Plug-ins Installation
82
| Appendix A
Installation Data Reference
Figure 8 Select the SQL Server (SQL Server Authentication) Database Type
Figure 9 Select the Oracle Database Type
TIBCO iProcess Technology Plug-ins Installation
Database Configuration Dialog (Continued) 83
|
Figure 10 Select the DB2 Database Type
TIBCO iProcess Technology Plug-ins Installation
84
| Appendix A
Installation Data Reference
Figure 11 Select the Oracle Real Application Cluster(RAC) Database Type
The following table describes the information that is specified in the second
Database Configuration dialog:
Field
Description
Database Physical Details
TIBCO iProcess Technology Plug-ins Installation
Database Configuration Dialog (Continued) 85
|
Field
Description
The path of the tnsnames.ora
file
This field is displayed when you select Oracle or Oracle Real
Application Cluster (RAC) from the Database Type list in the
Database Configuration Dialog.
The tnsnames.ora file is generated automatically by the Oracle
Configuration tool when installing the Oracle client. You can
find the tnsnames.ora file in the
%systemroot%/product/version/NETWORK/ADMIN directory of
the machine on which the Oracle client is installed. The
systemroot variable is the location of the system disk and the
version variable is the version number of the Oracle client.
The SID in the tnsnames.ora file records the host, port, and
instance information of the Oracle database which you want to
connect to.
Note: If the The path of the tnsnames.ora file check box is
selected, the SID in the tnsnames.ora file will be used. You do
not need to specify the Host field and Port field.
Host
Enter the IP address or the host name of the machine that is
hosting the database. For example, 10.10.41.28.
You can specify 127.0.0.1 if the database is on a local machine.
Note: The field is unavailable when the The path of the
tnsnames.ora file check box is selected for the Oracle and Oracle
Real Application Cluster (RAC) database types. Besides, when
you select SQL Server (Windows Authentication) from the
Database Type list, you have to specify the host name rather
than the IP address of the machine.
TIBCO iProcess Technology Plug-ins Installation
86
| Appendix A
Installation Data Reference
Field
Description
Port
Enter the port number that the database is using. This field
automatically displays the default port number for the database
type you selected, as follows:
•
Oracle: 1521
•
SQL Server: 1433
•
DB2: 50000
If you select SQL Server (SQL Server Authentication) or SQL
Server (Windows Authentication) from the Database Type list,
and you have multiple database instances under SQL Server,
find out the port number used by the SQL instance to which you
want to connect, and specify it here.
Note: The field is inapplicable when the The path of the
tnsnames.ora file check box is selected for the Oracle and Oracle
Real Application Cluster (RAC) database types.
Instance
Enter the instance name of the Oracle database to which you
want to connect.
Note: This field is available only when you select Oracle from
the Database Type list.
DB Name
Enter the name of the DB2 database to which you want to
connect.
Note: This field is available only when you select DB2 from the
Database Type list.
Note: You must enter the DB2 database name rather than the
DB2 database alias name.
Service
Enter the service name for the Oracle database to which you
want to connect.
Note: This field is available only when you select Oracle Real
Application Cluster (RAC) from the Database Type list.
Authentication Details
User ID
Enter the user name of the iProcess Engine database.
Note: You do not have to specify this field if SQL Server
(Windows Authentication) is selected from the Database Type
list.
TIBCO iProcess Technology Plug-ins Installation
Database Configuration Dialog (Continued) 87
|
Field
Description
Password
This field contains the password for the iProcess Engine
database user.
If you have to set or change this password, click Modify and the
Modify Password dialog is displayed.
Enter the correct password and click OK and the Database
Configuration dialog (Continued) is returned.
Note: You do not have to specify this field if SQL Server
(Windows Authentication) is selected from the Database Type
list.
Schema Owner
Enter the user name of the iProcess Engine tables owner. The
default value of this field is swpro.
For more information, see Setting Up SQL Server Authentication
on page 5.
Note: You do not have to specify this field if SQL Server
(Windows Authentication) is selected from the Database Type
list.
TIBCO iProcess Technology Plug-ins Installation
88
| Appendix A
Installation Data Reference
Field
Description
JDBC URL
This field contains the connection string used in the JDBC
connection.
If you select Oracle or Oracle Real Application Cluster (RAC)
from the Database Type list and select the The path of the
tnsnames.ora file check box, the @SID (for example,
jdbc:oracle:thin:@SID), rather than the IP address, port
number, and instance name (for example,
jdbc:oracle:thin:@host:port:instance), is included in the JDBC
URL field.
This is modified only if you are instructed to do so by TIBCO
Support.
Note: If the tnsnames.ora file is used, the connection string in
the JDBC URL field, that is jdbc:oracle:thin:@SID, is
recorded in the eaijavaplugin.properties file, which is
located in the SWDIR/eaijava directory of the machine on
which TIBCO iProcess Engine is installed.
Cluster Details
Note: This field is applicable only when you select Oracle Real
Application Cluster (RAC) from the Database Type list.
The cluster details consists of one or more entries, each
identifying the appropriate host and port on which the database
is being hosted.
Click Add to Cluster to add an entry to this field, an entry for
the host and port currently identified in the Host and Port fields
is added. Add additional entries by modifying the Host and
Port field, then click Add to Cluster again. Each entry must be
unique.
Select the desired entry, then click Remove from Cluster to
remove the entry from the Cluster Details field. (Note that if
you mistakenly remove the wrong entry, you can re-enter it by
simply clicking Add to Cluster — the Host and Port fields will
contain the host and port information for the removed entry.)
Note: The installation program only validates 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 might be running at installation-time, and
no warning is issued.
TIBCO iProcess Technology Plug-ins Installation
JMS Provider Details Dialog 89
|
JMS Provider Details Dialog
The JMS Provider Details dialog is used to configure the JMS provider details.
Figure 12 The JMS Provider Details Dialog
1. The Current Provider Classpath is shown.
If the values shown in this field are correct for your installation, click the Next
button to continue past this dialog. If it is necessary to change the classpath,
you can delete the current values by clicking Delete Classpath Entry.
2. If you need to change the classpath displayed, you need to specify the tibjms,
tibjmsadmin, and jms-2.0 (Only need to be specified when you use TIBCO
EMS version 8.x or above as the JMS provider) 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 the Browse button, 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 and jms-2.0.jar (Only when you use TIBCO EMS version
8.x or above as the JMS provider) files manually.
3. Click the Next button.
TIBCO iProcess Technology Plug-ins Installation
90
| Appendix A
Installation Data Reference
iProcess Server Plug-in for ActiveMatrix BusinessWorks
Configuration Dialog
The iProcess Server Plug-in for ActiveMatrix BusinessWorks dialog is used to
specify connection information between the BusinessWorks Client and Server
Plug-ins:
Figure 13 The iProcess Server Plug-in for ActiveMatrix BusinessWorksConfiguration
Dialog
The following table describes the information that is specified in the iProcess
Server Plug-in for ActiveMatrix BusinessWorks Configuration dialog.
Field
Description
Enable Client Plug-in
Connections
Select the Enable Client Plug-in Connections check box if you want
your iProcess Server Plug-in for ActiveMatrix BusinessWorks to pass
data to your iProcess Client Plug-in for ActiveMatrix BusinessWorks,
and vice versa.
This is typically disabled in a production environment.
TIBCO iProcess Technology Plug-ins Installation
iProcess Server Plug-in for ActiveMatrix BusinessWorks Configuration Dialog 91
|
Field
Description
Port Number
Specify the port number that the iProcess Client Plug-in for ActiveMatrix
BusinessWorks is using. This port must be free for the exclusive use of
the iProcess Client Plug-in for ActiveMatrix BusinessWorks.
This is because the JMX Server started as part of TIBCO iProcess
Connector for ActiveMatrix BusinessWorks is completely separate from
other JMX servers used by iProcess (the JMX Server started by 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
Note: 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
92
| Appendix A
Installation Data Reference
TIBCO iProcess Technology Plug-ins Installation
| 93
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 94
•
iProcess Engine Process Sentinels Fail to Start, page 95
•
Background Core Dumps on AIX, page 98
•
The Setup Program Hangs, page 99
•
Oracle Services May Be Required in Console Mode, page 100
•
Missing frameworkconfig.xml file, page 101
•
EAI Java Server Plug-in Fails to Load Correctly, page 102
•
CPU Usage is Too High, page 103
•
JMS Connection Test Returns Fail, page 104
•
Console Mode Installation Fails, page 105
•
JMS Provider Configuration is Lost in an Upgrade Error, page 106
TIBCO iProcess Technology Plug-ins Installation
94
| 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, do the following checks:
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 user name 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 user name that uses SQL Server authentication especially if
iProcess Engine was installed using Windows authentication.
5. If you are using DB2, make sure that you have entered the database name not
the database alias in the Database Name field.
Also see: Oracle Services May Be Required in Console Mode on page 100 and
Setting Up SQL Server Authentication on page 5
TIBCO iProcess Technology Plug-ins Installation
iProcess Engine Process Sentinels Fail to Start 95
|
iProcess Engine Process Sentinels Fail to Start
If the iProcess Engine Sentinels fail to start after installing the TIBCO iProcess
Technology Plug-ins, it might 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 does 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. Uninstall the iProcess Server Plug-in for ActiveMatrix BusinessWorks. See
Uninstalling the BusinessWorks Plug-in for iProcess from UNIX on page 73.
2. Uninstall the iProcess Java Server Plug-in. See Uninstalling the iProcess
Engine-Based Plug-ins from UNIX on page 72.
3. Reinstall the TIBCO iProcess Technology Plug-ins as the Background User.
TIBCO iProcess Technology Plug-ins Installation
96
| 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 in 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 have to change the s-bit permissions on the
above files again.
TIBCO iProcess Technology Plug-ins Installation
iProcess Engine Process Sentinels Fail to Start 97
|
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
'/iProcess/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /iProcess/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or folder'
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
'/iProcess/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /iProcess/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or folder'
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
'/iProcess/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /iProcess/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or folder'
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
'/iProcess/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /iProcess/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or folder'
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
'/iProcess/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /iProcess/installations/<nodename>/etc/swbgmbd:
fatal: libjvm.so: open failed: No such file or folder'
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
'/iProcess/installations/<nodename>/lib/EAI_JAVA_i10_3_0_0.EAR',
error 'ld.so.1: /iProcess/installations/<nodename>/etc/staffrpcbg:
fatal: libjvm.so: open failed: No such file or folder'
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 64.
TIBCO iProcess Technology Plug-ins Installation
98
| 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 folder (see Using the
$SWDIR/eaijava/scripts/env.sh Script (UNIX Only) on page 64), if you start
iProcess Engine, a core dump occurs and an sw_error log is produced.
What to do
To resolve this:
1. Stop 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 iProcess Engine.
TIBCO iProcess Technology Plug-ins Installation
The Setup Program Hangs 99
|
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 folder
If the Background user does not have these, the Setup program is unable to write
any files to the $SWDIR folder or unpack any files temporarily to the Background
User’s home folder.
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
100
| 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 iProcess Database” message will be displayed, as follows:
•
If you don't have the OracleDBConsole[SERVICE_NAME] and
OracleService[SERVICE_NAME] running, the following message appears:
Unable to connect to iProcess 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 appears:
Unable to connect to iProcess 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 101
|
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 folder.
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
102
| 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 folder'
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 in 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 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 103
|
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
104
| 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 105
|
Console Mode Installation Fails
Problem
sweaireg fails during the 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
TIBCO iProcess Technology Plug-ins will not install correctly.
In the GUI mode, the checkbox is checked by default but in the 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 the GUI, console, and silent modes, however the default
value for the field in the console mode is false and in the GUI mode it is true. You
should change the value as appropriate and not just default it.
TIBCO iProcess Technology Plug-ins Installation
106
| 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 Exporting Existing JMS Provider
Configuration if Upgrading on page 9). 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 iProcess Engine is running.
2. Start the JMS Administration Tool:
— From UNIX, navigate to the $SWDIR/jmsadmin folder and type the
following command:
./jmsadmin.sh
— From Windows, click Start > Programs > TIBCO iProcess® Engine
(Windows) > JMS Administration Utility.
3. Click Import.
A message appears 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 appears.
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 appears.
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
| 107
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 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 108
•
Obtaining an Appropriate Java Version/Encoding Set Combination, page 109
•
Using the Required Java Version/Encoding Set Combination, page 111
TIBCO iProcess Technology Plug-ins Installation
108
| 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.8, see
http://docs.oracle.com/javase/7/docs/technotes/guides/intl/encoding.doc.ht
ml
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 109
|
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 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 iProcess Engine on
page 109 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 110.
•
download and install an appropriate Java version - see Installing the Required
Java Version/Encoding Set Combination on page 110.
Java Version/Encoding Set Combinations Supplied by iProcess Engine
If you are installing TIBCO iProcess Engine, you may be able to use the Java
version/encoding set combination that is distributed with 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.
Platform
iProcess Engine
Version 11.6.0
Windows
1.8 Basic
Solaris, Linux
1.8 Extended
If this Java version/encoding set combination meets your requirements, you need
take no further action before installing TIBCO iProcess Engine.
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.
TIBCO iProcess Technology Plug-ins Installation
110
| Appendix C
Java Character Encoding Sets
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 TIBCO iProcess
Engine.
The following table lists the Java version/encoding set combinations that are
supported by the different Java versions.
Platform
Java 1.8
Windows
1.8 Basic (see below)
Solaris, Linux
1.8 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 Oracle’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).
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
Using the Required Java Version/Encoding Set Combination 111
|
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 76) 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
112
| Appendix C
Java Character Encoding Sets
TIBCO iProcess Technology Plug-ins Installation
| 113
Index
B
I
BusinessWorks Plug-in for iProcess 14
BWCTool 60
installation mode
console 18
GUI 17
silent 18
iProcess BusinessEvents Server Plug-in 18
iProcess Java Server Plug-in 14
iProcess Server Plug-in for ActiveMatrix
BusinessWorks 14
iProcess XML Transform Server Plug-in 15
C
character encoding 8
connecting with TIBCO resources xii
console installer 40
console mode 18
customer support xii
J
D
JMS Administration Utility 9, 106
JMS provide details dialog 89
JMS provider details dialog 89
database configuration dialog 79, 81, 81, 81
database driver 4
disk space requirements 21
L
log 19
E
export JMS provider configuration 9
P
G
general configuration dialog 76
GUI installer 33
GUI mode 17
post-installation tasks 59
configure the XML step definitions cache 67
configuring JNDI password encryption 63
remove the ISMP directories 66
run the SQL Server surface area configuration
utility 65
using the $SWDIR/eaijava/scripts/env.sh script 64
pre-installation tasks 2
TIBCO iProcess Technology Plug-ins Installation
114
| Index
R
response file 48
S
silent installer 48
silent mode 18
software requirements 24
BusinessWorks 25
database and database drivers 23
iProcess Engine 24
Java character encoding 27
JMS provider 25
JRE 26
JVM 26
supported system 21
SQL server authentication 5, 6
support, contacting xii
T
technical support xii
TIBCO_HOME x
U
uninstall from UNIX 72
BusinessWorks Plug-in for iProcess 73
iProcess Engine-based plug-ins 72
uninstall from Windows 70
BusinessWorks Plug-in for iProcess 71
iProcess Engine-based plug-ins 70
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