TIBCO iProcess Engine for Windows Installation

TIBCO iProcess Engine for Windows Installation
TIBCO iProcess® Engine
for Windows
Installation
Software Release 11.5
April 2015
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 Business Studio, TIBCO
Enterprise Message Service, TIBCO Hawk, TIBCO iProcess, TIBCO iProcess Suite, and TIBCO Rendezvous are
either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition
(J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation
in the U.S. and 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 © 1994-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
TIBCO iProcess Engine Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Third-party Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvi
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Organization Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installer Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
iProcess Engine Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Basic System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Additional System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Supported Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Upgrade Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
sw_error.log and sw_warn.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
init2Kora_tok.sql_UserName_TimeStamp.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
init2Ksql.sql_UserName_TimeStamp.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
ScriptName.sql_UserName_TimeStamp.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
upgrFromtoTo.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
PostChecks_UserName_TimeStamp.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
TIBCO iProcess Engine for Windows Installation
iv
| Contents
Chapter 2 Installing TIBCO iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing TIBCO iProcess Engine in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Custom Installation - New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Custom Installation - Upgrade Existing Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
35
44
55
Installing TIBCO iProcess Engine in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Generating a Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Performing an Installation in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Upgrading TIBCO iProcess Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Upgrade Performance and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Installing or Upgrading TIBCO iProcess Engine to Version 11.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Chapter 3 Uninstalling TIBCO iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Pre-removal Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Uninstalling iProcess Engine from a Windows Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Uninstalling iProcess Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Removing the ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Removing the iProcess Events COM+ Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Removing the iProcess Engine Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Appendix A Pre-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Checking for Any Late-breaking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Backing Up the TIBCO iProcess Engine File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Backing Up the TIBCO iProcess Engine Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Checking for the Database Codepage Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Upgrading the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Upgrading the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Stopping Any Other iProcess Engines on the Same Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Setting Up DCOM Permissions for the iProcess Objects Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Setting Up DCOM Permissions for a Node Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Configuring the Oracle Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Setting Up Oracle Transparent Application Failover (TAF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring Oracle OPEN_CURSORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Disabling Oracle Authentication Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
TIBCO iProcess Engine for Windows Installation
Contents v
|
Configuring Oracle Character Set Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Disabling Oracle Flashback Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Creating an Oracle UNDO Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating the SQL Server Database and Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Creating the ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Removing All User-defined Constraints (or Triggers), Indexes, and Statistics From the iProcess Engine Schema
Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Configuring the Microsoft Windows Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Appendix B Post-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Re-implementing Changes to Upgraded Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configuring Firewall Port Ranges on Slave Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Configuring TIBCO iProcess Objects Server and TIBCO iProcess Objects Director . . . . . . . . . . . . . . . . . . . . . 119
Enabling COM+ Network Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Configuring the Microsoft Windows Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Enabling Oracle Function-based Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Installing the IBM Client for JMS on J2SE with IBM WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . 127
Configuring IAPJMS Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Configuring the Default iProcess Engine Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Recreating Prediction Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Configuring Access to SSOLite Stored Procedures for TIBCO iProcess Plug-ins. . . . . . . . . . . . . . . . . . . . . . . . 132
Granting Permissions on Stored Procedures in EAI Database Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Recreating All User-defined Constraints (Or Triggers), Indexes and Statistics on the iProcess Engine Schema
Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Updating the Domain Group Policy for the Log On As A Service Right. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Enabling OLE Automation on SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Disabling or Re-enabling Write Access to WebDav . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Configuring JMX Ports to Run Through a Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Setting Up iProcess Engine with an IPv6 Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Starting TIBCO iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Appendix C Configuration Options for TIBCO iProcess Engine Installation . . . . . . . . . . . . .145
Upgrade or New Install Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Group & User Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
SQL/ODBC Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Database Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
TIBCO iProcess Engine for Windows Installation
vi
| Contents
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Select Components To Configure Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
SMTP Server Parameters Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
SMTP Backup Servers Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
TIBCO iProcess Web Server Configuration Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Default Java Message Service Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Appendix D Usage Profiles for Tablesizes Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
tablesizes.med File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
tablesizes.large File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Appendix E Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Does the iProcess Engine Database Support UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
How Do I Create the SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Is It Necessary to Use TIBCO iProcess COM Server Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
How Long Will an Upgrade Take . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
How Do I Upgrade TIBCO EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Updating EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Appendix F Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
The Installer Fails with an Unable to Open the File Warning Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
The Installer Exits Because You Are Not a Local Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Installer Cannot Continue Because Another iPE is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Installation Encounters an Error Trying to Locate pthread.dll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Connecting to the Oracle Database Fails During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Installing with an Unsupported Database Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
The Installer Cannot Locate an Oracle UNDO Tablespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Oracle TAF Is Not Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Oracle Advanced Queuing Is Not Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Oracle Client and Database NLS_LANG Settings Do Not Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Oracle OPEN_CURSORS Value Is Less Than 200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
The Installer Cannot Initialize the iProcess Engine Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Errors Occur on Validating the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
License File Cannot Be Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Upgrading Fails Because It Cannot Create the Process Sentinels Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Recovering iProcess Engine if an Upgrade Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
TIBCO iProcess Engine for Windows Installation
Contents vii
|
mscluster Command Reports Error in \etc\services File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Process Sentinels Do Not Start Due to Logon Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
iProcess Engine Processes Do Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Distributed Transaction Errors Occur When You Start iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Failed to Start TIBCO iProcess Engine Using a Domain User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
TIBCO iProcess Engine for Windows Installation
viii
| Contents
TIBCO iProcess Engine for Windows Installation
Figures ix
|
Figures
Figure 1
Direct Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 2
TNS Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 3
Setup Type Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 4
Choose Destination Location Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 5
Group & User Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 6
SQL/ODBC Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 7
The Database Dialog for Configuring an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 8
Select Tablesizes profile Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 9
Confirm Tablespace Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 10
The Database Dialog for Configuring a SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 11
Select Components to Configure Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 12
TIBCO iProcess Objects - Server Configuration Utility Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 13
Setup Complete Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 14
Upgrade or New Install Dialog - New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 15
Choose Destination Location Dialog - New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 16
Configuration Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 17
Group & User Configuration Dialog - Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 18
SQL/ODBC Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 19
The Database Dialog for Configuring an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 20
Select Tablesizes profile Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 21
Confirm Tablespace Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 22
The Database Dialog for Configuring a SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 23
Select Components to Configure Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 24
TIBCO iProcess Objects - Server Configuration Utility Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 25
Setup Complete Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 26
Upgrade or New Install Dialog - Upgrade Existing Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 27
Question Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 28
Configuration Dialog - Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
TIBCO iProcess Engine for Windows Installation
x
| Figures
Figure 29
Group & User Configuration Dialog - Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 30
Select Components to Configure Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 31
TIBCO iProcess Objects - Server Configuration Utility Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 32
Setup Complete Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 33
Default Java Message Service Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
TIBCO iProcess Engine for Windows Installation
Tables xi
|
Tables
Table 1
General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Table 2
Syntax Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Table 3
Organization Roles During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 4
Upgrading iProcess Engine on a Node Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 5
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Table 6
Windows Cluster Management Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 7
Additional Runtime Disk Space Requirements for TIBCO iProcess Objects . . . . . . . . . . . . . . . . . 13
Table 8
JMS Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 9
IRE Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 10
Required Database Versions When Using a Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 11
Required Oracle Database and Client Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 12
ODBC Driver Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 13
Pre-Installation Tasks Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 14
Post-Installation Tasks Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Table 15
SIZE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 16
Configuration Options in the Upgrade or New Install Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Table 17
Configuration Options in the Group & User Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . 148
Table 18
Configuration Options in the SQL/ODBC Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Table 19
Configuration Options in the Database Details Dialog - SQL Server . . . . . . . . . . . . . . . . . . . . . . 154
Table 20
Configuration Options in the Database Details Dialog - Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table 21
Configuration Options in the Select Components to Configure Dialog. . . . . . . . . . . . . . . . . . . . . 158
Table 22
Configuration Options in the Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 23
Configuration Options in the SMTP Server Parameters Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Table 24
Configuration Options in the SMTP Backup Servers Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 25
Configuration Options in the TIBCO iProcess Web Server Configuration Dialog . . . . . . . . . . . . 168
Table 26
Configuration Options in the JAR Files For JMS Connectivity Dialog . . . . . . . . . . . . . . . . . . . . . 172
Table 27
Configuration Options in IAPJMS Properties Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
TIBCO iProcess Engine for Windows Installation
xii
| Tables
TIBCO iProcess Engine for Windows Installation
| xiii
Preface
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 manual describes how to install TIBCO iProcess Engine on Microsoft
Windows platforms.
Topics
•
Related Documentation, page xiv
•
Typographical Conventions, page xvi
•
Connecting with TIBCO Resources, page xix
TIBCO iProcess Engine for Windows Installation
xiv
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
TIBCO iProcess Engine Documentation
The following documents form the TIBCO iProcess Engine documentation set:
•
TIBCO iProcess Engine Installation Read this manual for instructions on site
preparation and installation.
•
TIBCO iProcess Engine Release Notes Read the release notes for a list of new
and changed features. This document also contains lists of known issues and
closed issues for this release.
•
TIBCO iProcess Suite Documentation This documentation set contains all the
manuals for TIBCO iProcess Engine and other TIBCO products in TIBCO
iProcess® Suite. The manuals for TIBCO iProcess Engine are as follows:
— TIBCO iProcess Engine Architecture Guide
— TIBCO iProcess Engine Administrator’s Guides:
TIBCO iProcess Engine Administrator’s Guide
TIBCO iProcess Objects Director Administrator’s Guide
TIBCO iProcess Objects Server Administrator’s Guide
— TIBCO iProcess Engine Database Administrator's Guides:
TIBCO iProcess Engine (DB2) Administrator's Guide
TIBCO iProcess Engine (Oracle) Administrator's Guide
TIBCO iProcess Engine (SQL) Administrator's Guide
— TIBCO iProcess swutil and swbatch Reference Guide
— TIBCO iProcess Engine System Messages Guide
— TIBCO iProcess User Validation API User's Guide
— LDAPCONF Utility User’s Guide
Other TIBCO Product Documentation
You may find it useful to read the documentation for the following TIBCO
products:
•
TIBCO ActiveMatrix BusinessWorks™
TIBCO iProcess Engine for Windows Installation
Preface xv
|
•
TIBCO Business Studio™
•
TIBCO Enterprise Message Service™
•
TIBCO Hawk®
•
TIBCO Rendezvous®
Third-party Documentation
You may find it useful to read the documentation for the following third-party
products:
•
Microsoft® Windows®
•
Oracle® Database
•
Microsoft SQL Server®
•
IBM® WebSphere®
•
Oracle WebLogic Server®
TIBCO iProcess Engine for Windows Installation
xvi
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
SWDIR
TIBCO iProcess Engine installs into a directory. This directory is referenced in
documentation as SWDIR.
For example, if SWDIR is set to C:\swerver\staffw_nod1 on a Windows server
(on the C: drive), then the full path to the swutil command is
C:\swerver\staffw_nod1\bin\swutil.
IPEINSTALL
user
Indicates the Windows account that is used to run the Setup installation
program. See IPEINSTALL on page 4 for details.
IPEADMIN user
Indicates the Windows account that is used to administer iProcess Engine. See
IPEADMIN on page 5 for details.
IPESERVICE
Indicates the Windows account that is used to run iProcess Engine. See
IPESERVICE on page 5 for details.
user
code font
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 Engine for Windows Installation
Preface xvii
|
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 names 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.
Table 2 Syntax Typographical Conventions
Convention
Use
[ ]
An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
|
A logical OR that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
TIBCO iProcess Engine for Windows Installation
xviii Typographical Conventions
|
Table 2 Syntax Typographical Conventions (Cont’d)
Convention
Use
{ }
A logical group of items in a command. Other syntax notations may appear
within each logical group.
For example, the following command requires two parameters, which can be
either the pair param1 and param2, or the pair param3 and param4.
MyCommand {param1 param2} | {param3 param4}
In the next example, the command requires two parameters. The first parameter
can be either param1 or param2, and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters.
The first parameter must be param1. You can optionally include param2 as the
second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
TIBCO iProcess Engine for Windows Installation
Preface xix
|
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
You can access TIBCO documentation here:
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 Engine for Windows Installation
xx
| Connecting with TIBCO Resources
TIBCO iProcess Engine for Windows Installation
|1
Chapter 1
Introduction
This chapter explains installation modes, requirements, and other options you
need to be aware of before starting the installation.
Topics
•
Installation Overview, page 2
•
Installation Requirements, page 8
•
Upgrade Requirements, page 24
•
Log Files, page 25
TIBCO iProcess Engine for Windows Installation
2
| Chapter 1
Introduction
Installation Overview
This section provides an overview of the TIBCO iProcess Engine installer.
•
Installation Modes, page 2
•
Installation Types, page 3
•
Organization Roles, page 3
•
Installer Accounts, page 4
•
iProcess Engine Architecture, page 6
Installation Modes
The installer can run in the following modes on Microsoft Windows platforms.
•
GUI Mode
•
Silent Mode
GUI Mode
In GUI mode, the installer presents panels that allow you to make choices about
product selection, product location, and so on.
To invoke the installer in GUI mode, double-click the executable.
For detailed information, see Installing TIBCO iProcess Engine in GUI Mode on
page 34.
Silent Mode
In Silent mode, the installer uses a response file that was saved during an earlier
installation. Silent mode installs without prompting you for information.
For detailed information, see Installing TIBCO iProcess Engine in Silent Mode on
page 63.
TIBCO iProcess Engine for Windows Installation
Installation Overview 3
|
Installation Types
Two installation types are available, Basic and Custom.
•
Basic
Choosing the Basic installation type is recommended for new users.
The Basic installation type installs a new iProcess Engine using default
components and configuration options whenever possible.
•
Custom
The Custom installation type is recommended for advanced users.
The Custom installation type allows you to install iProcess Engine under the
following circumstances:
— If you want to install a new iProcess Engine, making your own choices for
all available configuration options.
— If you want to install a new slave server in a node-cluster iProcess Engine.
A slave server must use the same node name as the master server, but you
cannot choose the node name when you perform a Basic installation. The
Basic installation assigns it automatically.
— If you want to upgrade an existing iProcess Engine installation.
Organization Roles
To install TIBCO iProcess Engine, you will need to perform a number of
pre-installation tasks, then run the installer, and finally complete a number of
post-installation tasks.
Each of these stages requires the involvement of one or both of the organizational
roles described in Table 3.
Table 3 Organization Roles During Installation
Role
Knowledge Required
Permissions Required
iProcess
Files-install
Owner
iProcess Engine configuration (including all
optional iProcess Engine components)
To install and configure iProcess
Engine files and directories
iProcess
Schema-install
Owner
Database configuration
Database configuration
To create and configure the iProcess
Engine database schema
TIBCO iProcess Engine for Windows Installation
4
| Chapter 1
Introduction
Table 3 Organization Roles During Installation (Cont’d)
Role
Knowledge Required
Permissions Required
DBA
Database configuration
To create table spaces and users for
iProcess Engine
Depending on your operational and security environment, these roles can be
performed either by the same person or by different departments or individuals.
For Oracle users:
When you run the installer, you must have access to an Oracle DBA account that
has the necessary permissions to create tables and users, for example, either with
the DBA role assigned or with access to the Oracle Data Dictionary. See Table 20,
Configuration Options in the Database Details Dialog - Oracle, on page 156 for
details.
If you do not have DBA-level access, the installer will not be able to create the
iProcess Engine schema and users in the Oracle database.
For SQL Server users:
TIBCO recommends that you have the name and password of a SQL Server DB
Administrator (DBA) account available when you run the installer. This allows
the installer to perform all necessary installation tasks.
If you run the installer without DBA-level access, additional manual
pre-installation or post-installation tasks will be required in order to perform the
installation. See Appendix A, Pre-installation Tasks, on page 81 and Appendix B,
Post-installation Tasks, on page 115 for details.
Installer Accounts
The following installer accounts will be used during the TIBCO iProcess Engine
installation:
•
IPEINSTALL
•
IPEADMIN
•
IPESERVICE
IPEINSTALL
IPEINSTALL is a Windows user account used to install TIBCO iProcess Engine.
•
The IPEINSTALL user account must be a member of the Administrators
group on the computer where you are installing iProcess Engine. If you use an
TIBCO iProcess Engine for Windows Installation
Installation Overview 5
|
account that does not meet this requirement, the installer will immediately
exit with an error. See The Installer Exits Because You Are Not a Local
Administrator on page 190 for details.
•
The IPEINSTALL user account also determines which Windows accounts you
will be able to use as the IPEADMIN and IPESERVICE users:
— If you perform a Basic installation, the IPEINSTALL user account will also
be used as the IPEADMIN and IPESERVICE users. You cannot choose a
different account for these users.
— If you perform a Custom installation, the location of the IPEINSTALL user
account will determine the accounts that are available for you to choose as
the IPEADMIN and IPESERVICE users. You can only choose accounts for
these users from the same location (local machine, domain or trusted
domain) as the IPEINSTALL user.
•
The location of the IPEINSTALL user account also determines the default
value of the OS_USER_LOCATIONS process attribute, which defines where
iProcess Engine obtains the list of users when it populates the O/S User List
in the TIBCO iProcess Administrator User Manager tool. See TIBCO iProcess
Engine Administrator’s Guide for more information about this attribute.
IPEADMIN
IPEADMIN is a Windows user account used to administer TIBCO iProcess
Engine.
IPEADMIN permissions are required to perform tasks such as:
•
starting, stopping, and configuring iProcess Engine.
•
running various utilities, such as SWDIR\bin\swutil or
SWDIR\util\LDAPCONF.
IPESERVICE
IPESERVICE is a Windows user account used to run TIBCO iProcess Engine,
specifically:
•
the iProcess nodeName
Engine processes.
Process Sentinels
service, which runs all iProcess
TIBCO iProcess Engine for Windows Installation
6
| Chapter 1
Introduction
•
the iProcess Events COM+ application, which provides the publish or
subscribe event mechanism used for inter-process communication by
iProcess Engine processes.
By default, the Windows user account that is used as the IPEADMIN user will
also be used as the IPESERVICE user.
However, depending on your site’s operational policies, this may not be
acceptable. For example, if a user types an incorrect password of the IPEADMIN
user account, the account may be locked out. If this also locks out the
IPESERVICE account, you will not be able to start the iProcess nodeName
Process Sentinels service and the iProcess Events COM+ application. In this
situation, separate accounts would probably be more suitable.
When you run the installer, you can choose to use separate Windows accounts for
the IPEADMIN and IPESERVICE users, but to do so, you must perform a Custom
installation, rather than a Basic one.
iProcess Engine Architecture
iProcess Engine can be installed using either of the following architectures:
•
Single Server—The iProcess Engine node is installed and run on a single
server.
•
Node Cluster—The iProcess Engine node is distributed across multiple
servers, each of which runs iProcess Engine processes. One server acts as the
master server, while all other servers in the cluster are slave servers.
If you decide to use a node cluster architecture:
•
the computers hosting the iProcess Engine master and slave servers must all
be members of the same domain.
•
the IPEADMIN and IPESERVICE users must be domain accounts.
The master server and all slave servers use the same iProcess Engine database
schema. The schema can be hosted on an Oracle instance or on a SQL Server
database that is either local (to one of the servers in the iProcess node cluster) or
remote.
The iProcess Engine architecture is scalable. You can convert from a single server
to a node cluster at any time simply by adding another server to the installation.
See TIBCO iProcess Engine Architecture Guide for more information about the
iProcess Engine architecture.
TIBCO iProcess Engine for Windows Installation
Installation Overview 7
|
Installing the iProcess Engine on a Node Cluster
If you want to install a new iProcess Engine using a node cluster architecture, you
must:
1. Install iProcess Engine on the master server (to create the iProcess Engine
database schema).
2. Install iProcess Engine on each slave server (to add the server to the node
cluster, using the same database schema).
Each slave server must use the same installation parameters as the master server
(for example, node name, database name, RPC numbers, and Windows account
names).
Any specific differences in the installation process for a slave server are noted at
the appropriate points in the rest of this documentation.
Upgrading iProcess Engine on a Node Cluster
If you want to upgrade an existing iProcess Engine, either from or to a node
cluster architecture, follow the appropriate instructions shown in Table 4.
Table 4 Upgrading iProcess Engine on a Node Cluster
To Upgrade...
Do this...
From
To
single server
single server
Upgrade the iProcess Engine on the single (master) server,
using the instructions in this documentation.
node cluster
node cluster
Upgrade the iProcess Engine on the master server, using the
instructions in this documentation.
Upgrade the iProcess Engine on each slave server, using the
instructions in this documentation.
single server
node cluster
Upgrade the iProcess Engine on the single (master) server,
using the instructions in this documentation.
Install the iProcess Engine on each slave server that you want
to add to the node, using the instructions in this
documentation.
node cluster
single server
Remove the iProcess Engine on each slave server, using the
instructions in the Installation guide for that version.
Upgrade the iProcess Engine on the master server, using the
instructions in this documentation.
TIBCO iProcess Engine for Windows Installation
8
| Chapter 1
Introduction
Installation Requirements
This section describes the installation requirements for this product.
•
Supported Platforms, page 8
•
Basic System Requirements, page 8
•
Additional System Requirements, page 9
•
Supported Databases, page 18
Supported Platforms
The following Microsoft Windows (x86) platforms are supported:
•
Microsoft Windows 7 (32-bit and 64-bit)
•
Microsoft Windows 8 (32-bit and 64-bit)
•
Microsoft Windows 8.1 (32-bit and64-bit)
•
Microsoft Windows Server 2008 (32-bit and 64-bit)
•
Microsoft Windows Server 2008 R2 (64-bit)
•
Microsoft Windows Server 2012 (64-bit)
•
Microsoft Windows Server 2012 R2 (64-bit)
Basic System Requirements
Before installing TIBCO iProcess Engine, make sure your system meets the system
requirements listed in Table 5.
Table 5 System Requirements
Component
Requirement
Processor
Minimum: single x86-based, 800Mhz
Recommended: x86-based, Dual or Quad 2.5 GHz
Memory
Minimum: 512 MB
Recommended: 2 GB
This value does not include database server memory requirements if the database is
installed on the same computer as iProcess Engine.
TIBCO iProcess Engine for Windows Installation
Installation Requirements 9
|
Table 5 System Requirements
Component
Requirement
Disk space
10 MB for the iProcess Engine distribution set during installation
250 MB for the contents of the SWDIR directory structure after installation
File system
Oracle
The amount of Oracle tablespace needed for iProcess Engine data. See
Configuring the Oracle Schema on page 93 for more information about
how to calculate this figure.
SQL Server
The amount of SQL Server disk space needed for iProcess Engine data.
NTFS
FAT partitions are not supported by iProcess Engine.
Additional System Requirements
Additional system requirements are described below:
•
POSIX Threads (pthreads), page 9
•
Windows Clustering, page 12
•
TIBCO iProcess Objects, page 12
•
iProcess Server Manager, page 13
•
Activity Publishing and Work Queue Delta Publication, page 14
•
Java Runtime Environment (JRE), page 16
•
LDAP Directory Service, page 17
POSIX Threads (pthreads)
On a Windows system, version 2.7.0 of the POSIX Threads (pthreads) library must
be available on the system PATH of the computer where you intend to install
TIBCO iProcess Engine, before installation begins.
TIBCO has validated Version 2.7.0 with iProcess Engine. If you want to use a later
version of the library, contact TIBCO Support to confirm whether or not that
version is supported by your iProcess Engine version.
When you install or upgrade TIBCO iProcess Engine to version 11.5, you have to
use the latest version of the pthreads library. See Installing or Upgrading TIBCO
iProcess Engine to Version 11.5 on page 70.
TIBCO iProcess Engine for Windows Installation
10
| Chapter 1
Introduction
Downloading the pthreads Library
If you do not already have a POSIX Threads (pthreads) library, you can obtain the
POSIX Threads (pthreads) for Windows distribution set from TIBCO Software
Inc. by downloading it as follows:
1. Go to the TIBCO Software Product Download Site
(https://edelivery.tibco.com) website.
Entry to this site requires a username and password. If you do not have a
username, you can request one.
2. To navigate to the product, , you can find the product in one of the following
ways:
— Search the product name in the search field.
— Click All PRODUCTS A-Z.
— Click AUTOMATION.
TIBCO iProcess Engine for Windows Installation
Installation Requirements 11
|
3. If you navigate to the product by clicking AUTOMATION, click Business
Process Management (BPM) in the following page.
4. Click Download under TIBCO iProcess Engine and then click the product
version you want to download.
5. Download the pthread.dll file.
6. Copy the pthread.dll file to the following folder:
— For Windows (32-bit), copy the pthread.dll file from the POSIX Threads
(pthreads) for Win32 distribution set to the %systemroot%\system32
folder on the computer where you intend to install iProcess Engine and
make sure that the computer’s PATH system environment variable includes
the %systemroot%\system32 folder.
— For Windows (64-bit), copy the pthread.dll file from the POSIX Threads
(pthreads) for Win32 distribution set to the %systemroot%\SysWOW64
folder on the computer where you intend to install iProcess Engine and
make sure that the computer’s PATH system environment variable includes
the %systemroot%\SysWOW64 folder.
If a supported version of the pthread.dll library is not available on the system
PATH when you run the installer, the installer immediately exits with an error
message. See Installation Encounters an Error Trying to Locate pthread.dll on
page 192 for details.
TIBCO iProcess Engine for Windows Installation
12
| Chapter 1
Introduction
Additional pthread Requirements for the SAL SDK
If you intend to build any applications using the iProcess Engine’s SAL SDK
(installed in SWDIR\sdks\swsalsdk), those applications must include the
following files from the POSIX Threads (pthreads) for Win32 distribution set:
•
include\pthread.h
•
include\sched.h
•
include\semaphore.h
•
lib\pthreadVC2.lib
Errors occur if you build applications without including these files.
Windows Clustering
If you want to install the iProcess Engine on a Microsoft Windows cluster, make
sure that the necessary cluster management software (listed in Table 6) is installed
on each machine in the cluster.
Table 6 Windows Cluster Management Software
Operating System
Requirement
Windows Server 2008
Supplied as part of the basic operating system.
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows 7
Windows 8
Windows 8.1
Windows XP
Not supported.
Windows Server 2003
TIBCO iProcess Objects
The iProcess Objects Server receives requests for services or data from TIBCO
iProcess Objects (COM, JAVA, or C++) or TIBCO iProcess Server Objects (JAVA or
.NET). The iProcess Objects Server processes the request, then makes the
appropriate call to an iProcess Engine to initiate the desired service or obtain the
desired information.
TIBCO iProcess Engine for Windows Installation
Installation Requirements 13
|
The iProcess Objects Director is a stand-alone program that maintains a list of
iProcess Objects Servers that are configured in a node cluster. When a client needs
access to an iProcess Objects Server, it first establishes a connection to the iProcess
Objects Director. The iProcess Objects Director then decides, based on a pick
method, which iProcess Objects Server the client should connect to.
If you want to enable the iProcess Objects Server or iProcess Objects Director, you
need to take account of additional runtime disk space requirements listed in
Table 7. For detailed information about how to enable iProcess Objects Server or
iProcess Objects Director, see Select Components To Configure Dialog on
page 158.
Table 7 Additional Runtime Disk Space Requirements for TIBCO iProcess Objects
Component
Runtime Disk Space Requirement
iProcess Objects Server
5 MB + Log file
By default, the maximum size of the iProcess Objects Server log file is 15 MB.
This can be configured after installation. See TIBCO iProcess Objects Server
Administrator’s Guide for more information. The log file is not created during
installation. It is created the first time the iProcess Objects Server is used.
iProcess Objects Director
500 KB + Log file
By default, the maximum size of the iProcess Objects Director log file is 15
MB. This can be configured after installation using the
LOG_FILE_MAX_SIZE process attribute. (See TIBCO iProcess Objects Director
Administrator’s Guide for more information.) The log file is not created during
installation. It is created the first time the iProcess Objects Director is used.
iProcess Server Manager
The iProcess Server Manager is a JSP web client application that you can use to
start, stop, restart, and pause iProcess Engine server processes. It utilizes the
iProcess Web Server service and TIBCO Hawk to provide a graphical view of
iProcess Engine server processes on a machine or a node cluster.
If you are planning to use the iProcess Server Manager, you must have:
•
TIBCO Hawk Version 4.9.0 installed on the machine where you intend to
install iProcess Engine.
TIBCO iProcess Engine for Windows Installation
14
| Chapter 1
Introduction
•
TIBCO Rendezvous Version 8.4.2 installed on the machine where you intend
to install iProcess Engine. (This is the minimum version required to run
TIBCO Hawk Version 4.9.0.)
If you have a version of TIBCO Rendezvous earlier than 8.4.2 already installed,
you should either remove TIBCO Rendezvous or upgrade it to Version 8.4.2
before installing iProcess Engine. The reason for this is the installer cannot
upgrade an earlier version of TIBCO Rendezvous.
•
TIBCO Hawk Version 4.9.0 installed on the machines on which you want to
administer iProcess Engine processes.
Activity Publishing and Work Queue Delta Publication
If activity publishing is enabled, activity information about auditable objects (for
example, procedures and steps) can be published to an external application. (The
BG process publishes monitored activities to the IAPJMS process.) This enables
real-time monitoring of auditable objects so that mission critical or important
business events can be easily monitored.
Enabling activity publishing also enables Work Queue Delta publication via JMS.
This allows an external application to monitor a work queue and to retrieve only
those work items in a given work queue that have changed. In this case the WIS
process publishes messages about the monitored queue to the IAPJMS process,
and IAPJMS in turn publishes messages to a JMS topic which can be monitored by
the external application. See iProcess Engine Administrator’s Guide for configuring
activity publishing and work queue delta publication once they are enabled.
If you plan to enable activity publishing, you must ensure that the computer
hosting iProcess Engine has access to the Java Message Service (JMS) provider
that you want to use. This must be one of the following JMS providers listed in
Table 8.
Table 8 JMS Providers
JMS Provider
TIBCO Enterprise Message
Service (EMS)
Supported
Versions
6.3
7.0
7.0.1
8.0
8.1
TIBCO iProcess Engine for Windows Installation
Additional Requirements
If you are upgrading iProcess Engine and you are using EMS,
you must ensure that your version of EMS is updated. See
How Do I Upgrade TIBCO EMS on page 184 for details.
Installation Requirements 15
|
Table 8 JMS Providers
Supported
Versions
JMS Provider
IBM WebSphere
Application Server
8.5.5
Additional Requirements
The IBM Client for JMS on J2SE with WebSphere Application
Server must be installed on the machine hosting the iProcess
Engine.
See Installing the IBM Client for JMS on J2SE with IBM
WebSphere Application Server on page 127 for more
information.
Oracle WebLogic Server
12.1.1
If the WebLogic Server is hosted remotely, one of the
following WebLogic client types must be installed on the
machine hosting iProcess Engine:
WebLogic T3 client (weblogic.jar), or
WebLogic JMS Thin Client (wljmsclient.jar and
wlclient.jar)
These JAR files are located in the WL_HOME\server\lib
subdirectory of the WebLogic Server installation directory,
where WL_HOME is the top-level installation directory for the
entire WebLogic Platform (for example,
c:\bea\weblogic90\server\lib).
See Default Java Message Service Dialog on page 170 for
more information.
JBoss EAP
6.1.0
None
Other
The JMS provider can be hosted either on the local machine or on a remote
machine. If the JMS provider is hosted remotely, appropriate client application
JAR files must be installed on the machine hosting the iProcess Engine. See
your JMS provider documentation for more information about required client
JAR files. You specify the location of these JAR files when you run the installer.
See Default Java Message Service Dialog on page 170 for more
information.
The JMS provider must support Java Virtual Machine (JVM) 1.5.0_11, 1.6, or
1.7. JVM 1.7 is distributed with this version of iProcess Engine, and installed
into the SWDIR\java directory.
For detailed information about how to enable activity publishing, see Select
Components To Configure Dialog on page 158.
TIBCO iProcess Engine for Windows Installation
16
| Chapter 1
Introduction
Java Runtime Environment (JRE)
The following information is listed in Table 9:
•
the iProcess Engine components and other dependant iProcess products that
use Java, and therefore need access to a Java Virtual Machine (JVM) or other
JRE libraries on the computer hosting the iProcess Engine.
•
the default JRE that each component or product uses to locate the libraries that
it needs.
•
the configuration tool provided to allow you to configure the location of the
JRE used by each component or product (if applicable).
Table 9 IRE Information
Component or Product
Default JRE
Location
Configuration Tool
IAPJMS process
SWDIR\java
SWLIB_PATH
process attribute value
See “Administering Process Attributes” in TIBCO
iProcess Engine Administrator’s Guide for more
information.
iProcess Server Manager
SWDIR\java
None
JMX engine
SWDIR\java
None
TIBCO EMS
SWDIR\java
None
TIBCO Hawk
SWDIR\java
None
TIBCO iProcess
BusinessWorks Connector
Server Plug-in
Selectable when
you install the
plug-in
TIBCO iProcess Technology Plug-ins installer
TIBCO iProcess Java Server
Plug-in
Selectable when
you install the
plug-in
See TIBCO iProcess Technology Plug-ins Installation for
more information.
TIBCO iProcess Technology Plug-ins installer
See TIBCO iProcess Technology Plug-ins Installation for
more information.
Note:
On some platforms, if you are installing iProcess Java
Server Plug-in to use with this version of iProcess
Engine, you cannot run the installer with Java 1.6, you
must use an earlier version such as Java 1.5. However,
you can use Java 1.6 at runtime.
TIBCO iProcess Engine Web
Service Server Plug-in
Selectable when
you install the
plug-in
TIBCO iProcess Engine for Windows Installation
TIBCO iProcess Engine Web Services Plug-in installer
See TIBCO iProcess Engine Web Services Plug-in
Installation for more information.
Installation Requirements 17
|
TIBCO strongly recommends that you use the following JRE to provide the
necessary Java functionality when using the components and products listed in
Table 9.
JRE 1.7.0_75,
which is distributed with this version of the iProcess Engine and
installed into the SWDIR\java directory.
You can identify this JRE by running the SWDIR\java\bin\java
command, which will display output similar to the following:
-version
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) Server VM (build 24.75-b04, mixed mode, sharing)
If you need to use a different version of the JRE for any reason, TIBCO strongly
recommends that you contact TIBCO Support before doing so, to determine if the
JRE you want to use is fully compatible with this version of iProcess Engine.
LDAP Directory Service
You can manage iProcess user, group, role, and attribute data via any LDAP
compliant directory service.
TIBCO iProcess Engine for Windows Installation
18
| Chapter 1
Introduction
Supported Databases
The following database types are supported for TIBCO iProcess Engine on
Windows platforms:
•
Oracle Database
•
SQL Server Database
Oracle Database
TIBCO iProcess Engine requires one of the following Oracle database versions:
•
Oracle 11g release 11.1.0.6 (server) with 12.1.0.1 (client)
•
Oracle 11g release 11.2.0.3 (server) with 12.1.0.1 (client)
•
Oracle 12c release 12.1 (server) with 12.1.0.1 (client)
You must install TIBCO iProcess Engine with 32-bit Oracle 12c client.
The exact Oracle version requirements depend on which of the following two
types of database connections you intend to use:
•
a direct connection to the default database hosted on the computer where you
will install or upgrade TIBCO iProcess Engine. For detailed information, see
Direct Connection Requirements for Oracle on page 18.
•
a Transparent Network Substrate (TNS) connection, connected to either:
— the default database hosted on the computer where you will install or
upgrade TIBCO iProcess Engine, or to
— a remote database, meaning a database that is either hosted on a remote
computer, or a non-default database on the computer where you will install
or upgrade iProcess Engine.
For detailed information, see TNS Connection Requirements for Oracle on
page 19.
Direct Connection Requirements for Oracle
Figure 1 illustrates an example of a direct connection from TIBCO iProcess Engine
to the default Oracle database:
TIBCO iProcess Engine for Windows Installation
Installation Requirements 19
|
Figure 1 Direct Connection
Table 10 shows the required Oracle database versions when using a direct
connection to the default database.
Table 10 Required Database Versions When Using a Direct Connection
Database
Release
Additional Requirements
11.1.0.6
Oracle Services for Microsoft Transaction Server (ORAMTS)
11.2.0.3
To see if ORAMTS is installed on your system, run the Oracle Universal Installer and click
the Installed Products button. If you need to install this component, perform a Custom
installation and select the appropriate product from the list.
12.1
TNS Connection Requirements for Oracle
When using a TNS connection, you must:
•
ensure that the remote Oracle database uses one of the Oracle Database
releases specified in Table 11.
•
ensure that the correct Oracle Client release is installed on the computer
where you will install or upgrade the iProcess Engine, as described in
Table 11.
Figure 2 illustrates an example of a TNS connection from TIBCO iProcess
Engine to the default database:
TIBCO iProcess Engine for Windows Installation
20
| Chapter 1
Introduction
Figure 2 TNS Connection
•
have the indicated Oracle Client release (and any specified additional patches
or components) installed on:
— the computer where you will install or upgrade the iProcess Engine, and
— if you are using a Windows cluster, on each machine in the cluster.
Each Oracle Client must be pointing to the same Oracle Database.
•
use the TNS name to connect the iProcess Engine to the Oracle Database. See
Database Details Dialog on page 154 for details.
Table 11 shows the required Oracle database and client versions when you use a
TNS connection connecting to the default database or to a remote database.
Table 11 Required Oracle Database and Client Versions
Certified
Database
Release
Compatible
Database
Release
11.1.0.6
11.1.0.x where
x is 6 or higher
Oracle Services for
Microsoft
Transaction Server
(ORAMTS)
11.2.0.3
11.2.0.x where
x is 3 or higher
12.1
12.1.0.x where
x is 1or higher
Additional
Requirements
Client
Release
Additional
Requirements
with
12.1.0.1
Oracle Services for
Microsoft Transaction
Server (ORAMTS)
Oracle Services for
Microsoft
Transaction Server
(ORAMTS)
with
12.1.0.1
Oracle Services for
Microsoft Transaction
Server (ORAMTS)
Oracle Services for
Microsoft
Transaction Server
(ORAMTS)
with
12.1.0.1
Oracle Services for
Microsoft Transaction
Server (ORAMTS)
To see if ORAMTS is installed on your system, run the Oracle Universal Installer
and select Installed Products. If you need to install this component, perform a
Custom installation and select the product from the list.
TIBCO iProcess Engine for Windows Installation
Installation Requirements 21
|
If you are using an Oracle version (Database or Client) that is:
•
earlier than the releases explicitly mentioned in the table above, you must
upgrade to one of the specified releases.
•
later than the releases explicitly mentioned in the table above, contact TIBCO
Support to confirm whether or not that release is supported by your iProcess
Engine version.
You will need access to an Oracle Metalink account to be able to access the
required patches and patch sets.
TIBCO iProcess Engine uses Oracle Call Interface (OCI) to access data in the
Oracle database. For reasons of stability, TIBCO iProcess Engine is statically
linked with the Oracle client libraries that provide the required OCI routines.
Oracle only supports products that run against the same set of libraries they were
built with. This means you must use particular Oracle Client versions, depending
on the method you use to connect to the database.
If you are using Oracle Real Application Clusters (RAC), TIBCO recommends that
you install the iProcess Engine on a machine that is not part of the RAC, and use a
TNS connection to connect to the remote database.
SQL Server Database
TIBCO iProcess Engine requires one of the following SQL Server database
versions:
— SQL Server 2005 with Service Pack 3
— SQL Server 2008
— SQL Server 2008 R2
— SQL Server 2012
— SQL Server 2014
If you are using a SQL Server version that is:
•
earlier than the releases explicitly mentioned above, you must upgrade to one
of the specified releases.
•
later than the releases explicitly mentioned above, contact TIBCO Support to
confirm whether or not that release is supported by your iProcess Engine
version.
The SQL Server must be installed either:
•
on the computer where you intend to install the iProcess Engine, or
TIBCO iProcess Engine for Windows Installation
22
| Chapter 1
Introduction
•
on a computer which is in the same domain or workgroup as the computer
where you intend to install the iProcess Engine.
When you install iProcess Engine with SQL Server 2008, but without the DBA
role, the following error message appears:
The User does not have permissions to add the linked server.
You can ignore this message and continue to install iProcess Engine. To make sure
that SSOLITE works correctly, you need to use the DBA role to run the following
script after the installation:
$SWDIR/util/sql_check_linkedserver.sql
Authentication Requirements
TIBCO strongly recommends that you install iProcess Engine against a SQL
Server instance that uses Mixed Mode authentication (where database connections
can be authenticated using either SQL Server login IDs or passwords, or Windows
accounts). The installer normally creates or uses SQL Server logins to enable the
iProcess Engine to connect to the SQL Server instance.
Although iProcess Engine can use Windows-authenticated accounts to access the
SQL Server database, there are currently some restrictions associated with this
mode of operation that require changes to the installation procedures described in
this documentation.
If you want to install the iProcess Engine against a SQL Server instance that uses
Windows Only authentication, see “Installing iProcess Engine Against a SQL
Server Instance That Uses Windows Only Authentication” in TIBCO iProcess
Engine (SQL Server) Release Notes for more information before proceeding further.
ODBC Driver Requirements
This version of iProcess Engine requires an ODBC driver to allow iProcess Engine
to connect to the SQL Server database. The driver required depends on the type of
database you are using, as shown in Table 12.
Table 12 ODBC Driver Requirements
Database
Required ODBC Driver
SQL Server 2005
SQL Native Client
SQL Server 2008
SQL Native Client
TIBCO iProcess Engine for Windows Installation
Installation Requirements 23
|
The SQL Native Client driver is not automatically provided on the Windows
operating systems supported by this version of the iProcess Engine. It is installed
as part of SQL Server.
If you do not have SQL Server installed on the computer where you intend to
install iProcess Engine, and you intend to use a SQL Server that is installed on a
remote computer, you will need to download the SQL Native Client driver
from the Microsoft Download Center:
•
Download Feature Pack for Microsoft SQL Server 2005 - April
version 1.0 from
http://www.microsoft.com/download/en/details.aspx?DisplayLang=en&i
d=17943
2006,
•
Download Microsoft SQL Server 2008 Feature Pack, April
version 10.00.2531.00 from
http://www.microsoft.com/download/en/details.aspx?id=3522
2009,
Additional Requirements
If the computer where you are running SQL Server is using Windows Server 2008,
Windows Server 2008 R2, Windows 7, Windows 2012, Windows Server 2012,
Windows Server 2012 R2, Windows 8, or Windows 8.1, and you intend to enable
the TIBCO iProcess COM Server Plug-in, you must enable network DTC access.
If it is not enabled, database transactions are limited to the local server.
For more information about how to enable network
DTC access:
•
For Windows Server 2003, see article 817064 in Microsoft’s Knowledge Base at
http://support.microsoft.com.
•
For Windows Server 2008 or Windows 7, see the article “Enable Network DTC
Access” in the Windows Server TechCenter section of Microsoft TechNet at
http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx.
TIBCO iProcess Engine for Windows Installation
24
| Chapter 1
Introduction
Upgrade Requirements
If you are using TIBCO iProcess Engine version 11.0 or higher, or TIBCO Process Engine
9.0, you can upgrade to version 11.5.0 directly without upgrading through an intermediate
version.
If you are upgrading iProcess Engine, you must ensure that EMS is also updated. See How
Do I Upgrade TIBCO EMS on page 184.
TIBCO iProcess Engine Version 11.5.0 requires specific operating system and
database versions. See Installation Requirements on page 8 for more information.
If your current iProcess Engine/Process Engine is running against an operating
system or a database version that does not meet these requirements, you will need
to upgrade your operating system or database to a supported version before you
can upgrade iProcess Engine.
TIBCO iProcess Engine for Windows Installation
Log Files 25
|
Log Files
This section describes the different log files that the installer may write to the
SWDIR\logs directory during the course of an installation or upgrade.
•
sw_error.log and sw_warn.log, page 25
•
init2Kora_tok.sql_UserName_TimeStamp.log, page 25
•
init2Ksql.sql_UserName_TimeStamp.log, page 25
•
ScriptName.sql_UserName_TimeStamp.log, page 26
•
upgrFromtoTo.log, page 26
•
PostChecks_UserName_TimeStamp.log, page 26
sw_error.log and sw_warn.log
sw_error and sw_warn are system log files used to record information, as well as
error and warning messages. The sw_error.log and sw_warn.log files only
record information received on the current date. When the date changes, if new
information needs to be recorded to the log files, the previously generated
sw_error.log and sw_warn.log files will be archived with the new file names,
sw_errortimestamp.log and sw_warntimestamp.log.
For example, if the original sw_error.log file is generated on July 1, 2012, the
new error messages need to be written in the new error log file on July 5, 2012,
then the original log file will be archived with the new file name
sw_error20120701.log.
Errors or warnings can be written to these files during installation or upgrade.
For a full description of the sw_error.log and sw_warn.log files and their
contents, see TIBCO iProcess Engine System Messages Guide.
init2Kora_tok.sql_UserName_TimeStamp.log
This file logs the progress of the init2Kora.sql SQL script used to create the
iProcess Engine database schema in Oracle.
The log file is always created when the script is run, whether the script runs
successfully or not.
init2Ksql.sql_UserName_TimeStamp.log
This file logs the progress of the
init2Ksql.sql
SQL script used to create the
TIBCO iProcess Engine for Windows Installation
26
| Chapter 1
Introduction
iProcess Engine database schema in SQL Server.
The log file is always created when the script is run, whether the script runs
successfully or not.
ScriptName.sql_UserName_TimeStamp.log
This file logs the progress of the ScriptName.sql SQL script used to upgrade the
iProcess Engine database schema from one version to another. Multiple upgrade
scripts can be run during an upgrade, depending on the version being upgraded
from.
A log file is always created for each upgrade script that is run, whether the script
runs successfully or not.
upgrFromtoTo.log
This file logs errors that occurred during an upgrade stage, where From indicates
the version being upgraded from, and To indicates the version being upgraded to.
An upgrFromtoTo.log file is only created if an error occurs (whether fatal or not).
Multiple upgrFromtoTo.log files may be created.
PostChecks_UserName_TimeStamp.log
This file logs the progress of various post-installation checks that the installer runs
to validate that the installation or upgrade has succeeded.
This file is always created when you run the installer, and always contains some
initial debug information, like the following example.
070130153435.774993:A001: fil_pattr_register_callback : Added callback(0/1)
MBOXSET_MSG to attribute(19) MBSET_WRITE_BG
070130153435.820335:i001: iqlDbQueueRead : idl_select_uni failed..Returned 100
070130153435.820497:i001: iqlQueueInit(): failed to get information about
DEADQUEUE: 0
070130153435.823555:i001: iqlDbQueueRead : idl_select_uni failed..Returned 100
070130153435.823658:i001: iqlQueueInit(): failed to get information about
DEADQUEUE: 0
This debug information does not indicate that a validation error has occurred, and
can be ignored.
TIBCO iProcess Engine for Windows Installation
Log Files 27
|
If the installer displays one of the following error messages when it performs its
post-validation checks, this file also contains additional information about the
error.
Failed to subscribe, publish, or receive a COM+ event.
ErrorDescription
Failed to access the database and validate the nodename.
ErrorDescription
TIBCO iProcess Engine for Windows Installation
28
| Chapter 1
Introduction
TIBCO iProcess Engine for Windows Installation
| 29
Chapter 2
Installing TIBCO iProcess Engine
This chapter describes how to install TIBCO iProcess Engine on Windows.
Topics
•
Pre-installation, page 30
•
Installing TIBCO iProcess Engine in GUI Mode, page 34
•
Installing TIBCO iProcess Engine in Silent Mode, page 63
•
Upgrading TIBCO iProcess Engine, page 65
•
Post-installation, page 66
•
Installing or Upgrading TIBCO iProcess Engine to Version 11.5, page 70
TIBCO iProcess Engine for Windows Installation
30
| Chapter 2
Installing TIBCO iProcess Engine
Pre-installation
The most time-consuming part of a TIBCO iProcess Engine installation is the
collection of environment information and parameters. This section helps you
complete this process.
Table 13 provides a checklist of the tasks that you must or may need to perform
before installing the iProcess Engine. The table shows:
•
whether the iProcess Files-install Owner, iProcess Schema-install Owner, or
DBA user needs to perform the task. See Organization Roles on page 3 for
more information about iProcess Files-install Owner, iProcess Schema-install
Owner, and DBA.
•
the status of a task, depending on whether you are installing a new iProcess
Engine or upgrading an existing one. There are four possible task statuses:
— Required —You must perform this task before installing iProcess Engine.
— Check — You may need to perform this task before installing iProcess
Engine, depending on your installation scenario.
— Optional — You may wish to perform this task before installing iProcess
Engine, but it is not essential.
— N/A — You can install iProcess Engine. without performing this task.
For detailed information about each task, see Appendix A, Pre-installation
Tasks, on page 81.
You may want to print this table as a useful quick reference when performing the
pre-installation tasks. The Done? column in the table provides a place for you to
tick off tasks that have been done.
Table 13 Pre-Installation Tasks Checklist
Task
Checking for Any
Late-breaking
Information
Database
Type
Oracle
SQL Server
To be done by
iProcess Files-install
Owner
Install
Status
Upgrade
Status
Required
Required
N/A
Required
iProcess Schema-install
Owner
DBA
Backing Up the
TIBCO iProcess
Engine File System
Oracle
SQL Server
iProcess Files-install
Owner
TIBCO iProcess Engine for Windows Installation
Done?
Pre-installation 31
|
Table 13 Pre-Installation Tasks Checklist
Task
Database
Type
Backing Up the
TIBCO iProcess
Engine Database
Schema
Oracle
Checking for the
Database Codepage
Setting
Oracle
Upgrading the
Operating System
Oracle
SQL Server
SQL Server
Install
Status
Upgrade
Status
iProcess Schema-install
Owner
N/A
Required
iProcess Schema-install
Owner
Required
Check
Check
Check
Check
Check
Check
Check
Check
N/A
Check
N/A
To be done by
Done?
DBA
SQL Server
iProcess Files-install
Owner
iProcess Schema-install
Owner
Upgrading the
Database
Oracle
SQL Server
iProcess Schema-install
Owner
DBA
Stopping Any Other
iProcess Engines on
the Same Machine
Oracle
Setting Up DCOM
Permissions for the
iProcess Objects
Server
Oracle
Setting Up DCOM
Permissions for a
Node Cluster
Oracle
Configuring the
Oracle Schema
Oracle
iProcess Schema-install
Owner
Optional
N/A
Setting Up Oracle
Transparent
Application Failover
(TAF)
Oracle
iProcess Schema-install
Owner
Check
Check
SQL Server
iProcess Files-install
Owner
iProcess Schema-install
Owner
SQL Server
iProcess Files-install
Owner
iProcess Schema-install
Owner
SQL Server
iProcess Files-install
Owner
iProcess Schema-install
Owner
DBA
TIBCO iProcess Engine for Windows Installation
32
| Chapter 2
Installing TIBCO iProcess Engine
Table 13 Pre-Installation Tasks Checklist
Task
Configuring Oracle
OPEN_CURSORS
Database
Type
Oracle
To be done by
iProcess Schema-install
Owner
Install
Status
Upgrade
Status
Required
Check
Check
Check
Check
Check
Check
Check
N/A
Check
Required
Required
Check
N/A
Check
N/A
N/A
Check
DBA
Disabling Oracle
Authentication
Services
Oracle
Disabling Oracle
Authentication
Services
Oracle
Configuring Oracle
Character Set Support
Oracle
iProcess Schema-install
Owner
DBA
iProcess Schema-install
Owner
DBA
iProcess Schema-install
Owner
DBA
Disabling Oracle
Flashback Query
Oracle
iProcess Schema-install
Owner
DBA
Creating an Oracle
UNDO Tablespace
Oracle
iProcess Schema-install
Owner
DBA
Creating the SQL
Server Database and
Logins
SQL Server
Creating the ODBC
Data Source
SQL Server
iProcess Schema-install
Owner
DBA
iProcess Schema-install
Owner
DBA
Removing All
User-defined
Constraints (or
Triggers), Indexes,
and Statistics From
the iProcess Engine
Schema Tables
Oracle
SQL Server
iProcess Schema-install
Owner
DBA
TIBCO iProcess Engine for Windows Installation
Done?
Pre-installation 33
|
Table 13 Pre-Installation Tasks Checklist
Task
Database
Type
Configuring the
Microsoft Windows
Cluster
Oracle
Configuring the
Microsoft Windows
Cluster
Oracle
SQL Server
To be done by
iProcess Schema-install
Owner
Install
Status
Upgrade
Status
Optional
Check
Check
Check
Done?
iProcess Schema-install
Owner
SQL Server
iProcess Schema-install
Owner
iProcess Schema-install
Owner
TIBCO iProcess Engine for Windows Installation
34
| Chapter 2
Installing TIBCO iProcess Engine
Installing TIBCO iProcess Engine in GUI Mode
Before running the installer, make sure that iProcess Files-install Owner and
iProcess Schema-install Owner have known the following information:
•
node name
•
SWDIR
•
the account of background user. iProcess Schema-install Owner needs to use
this account if iProcess Schema-install Owner can not use the root account
during installation.
To install TIBCO iProcess Engine in GUI mode, complete the following steps:
1. Use the IPEINSTALL user account to log on to Windows.
2. Open the physical media or download the TIBCO iProcess Engine installation
package from a network server.
3. Extract the product’s file to a temporary directory and navigate to the
temporary directory.
Check if you have already copy the pthread.dll file to the appropriate
directory. For detailed information, see POSIX Threads (pthreads) on page 9.
4. Run setup.exe. The Welcome dialog appears.
5. Review the information in the Welcome dialog and click the Next button. The
Software License Agreement dialog appears.
6. Review the entire TIBCO Software Inc. End User License Agreement.
— Click the No button if you do not agree to the terms of the license
agreement, and then exit from the installation process.
— Click the Yes button if you agree to the terms of the license agreement. The
Setup Type dialog appears, as shown in Figure 3.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 35
|
Figure 3 Setup Type Dialog
7. Select the Basic or Custom installation type in the Setup Type dialog.
— Select the Basic radio button to continue with the Basic Installation.
— Select the Custom radio button to continue with the Custom Installation New Installation or Custom Installation - Upgrade Existing Installation.
Basic Installation
For TIBCO iProcess Engine Basic Installation, complete the following steps:
1. Select the Basic radio button in the Setup Type dialog, then click the Next
button. The Choose Destination Location dialog appears, as shown in
Figure 4.
TIBCO iProcess Engine for Windows Installation
36
| Chapter 2
Installing TIBCO iProcess Engine
Figure 4 Choose Destination Location Dialog
2. Click the Browse... button to specify a Destination Folder where you want to
install iProcess Engine.
The Destination Folder is referred to as SWDIR.
The length of the SWDIR full pathname must not exceed 64 characters.
If you are installing iProcess Engine on a computer that is part of a Windows
cluster, SWDIR must be located on a cluster storage device that is accessible to all
nodes in the cluster.
3. Click the Next button. The Group & User Configuration dialog appears, as
shown in Figure 5.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 37
|
Figure 5 Group & User Configuration Dialog
4. Review the information in the Group & User Configuration dialog and enter
the password for your iProcess Engine administrator account. For detailed
information about configuration options in this dialog, see Group & User
Configuration Dialog on page 148.
5. Click the Next button.
If you are using an Oracle database with iProcess Engine, skip this step.
If you are using a SQL Server database with iProcess Engine, the SQL/ODBC
Details dialog appears, as shown in Figure 6. For detailed information about
configuration options in this dialog, see SQL/ODBC Details Dialog on
page 151.
TIBCO iProcess Engine for Windows Installation
38
| Chapter 2
Installing TIBCO iProcess Engine
Figure 6 SQL/ODBC Details Dialog
a. Select the Choose An Existing ODBC Data Source or Enter A New
ODBC Data Source radio button in the dialog.
b. Check or uncheck the You Have DBA Privileges (To Create A Database
And Users) checkbox.
c. Click the Next button.
If you entered a new ODBC Data Source name, the ODBC Source Not
Found dialog appears and the following prompt is displayed in it:
ODBC Source does not exist. Do you want to create it?
Click the Yes button to open the Database Details dialog. Click the No
button to return to the SQL/ODBC Details dialog, and choose a different
ODBC Data Source name.
6. Configure the database that iProcess Engine will connect to in the Database
Details dialog. For detailed information about configuration options in this
dialog, see Database Details Dialog on page 154.
If you are using an Oracle database with iProcess Engine, the configuration
options are listed in Table 20, Configuration Options in the Database Details
Dialog - Oracle, on page 156. The Database Details dialog is shown in
Figure 7.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 39
|
Figure 7 The Database Dialog for Configuring an Oracle Database
— Enter the Oracle database service (TNS) name.
— Enter the Database Admin Username and password.
— Check or uncheck the Support Unicode Encoding checkbox.
— Click the Change button to change the database users, if needed.
If you are using Oracle 12c, you must specify the owner name and user
name of iProcess Engine database with the prefix, c##. For example,
c##ipepro and c##ipeuser.
— Click the Next button. The installer now tries to connect to the Oracle
database using your specified settings and performs a number of checks
against your Oracle configuration. See Table 20, Configuration Options in
the Database Details Dialog - Oracle, on page 156 for detailed information.
The Select Tablesizes Profile dialog appears, as shown in Figure 8.
TIBCO iProcess Engine for Windows Installation
40
| Chapter 2
Installing TIBCO iProcess Engine
Figure 8 Select Tablesizes profile Dialog
— Click the Next button. The Confirm Tablespace dialog appears. Select
whether you want to create all objects in IPEDATA tablespace or use
tablespace names exactly as specified in tablesizes file in the dialog.
Figure 9 Confirm Tablespace Dialog
— Click the Next button. the Select Components to Configure dialog appears.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 41
|
If you are using a SQL Server database with iProcess Engine, the configuration
options are listed in Table 19, Configuration Options in the Database Details
Dialog - SQL Server, on page 154. The Database Details dialog is shown in
Figure 10.
Figure 10 The Database Dialog for Configuring a SQL Server Database
— Enter the iPE DB Owner login name and password.
— Enter the iPE DB User login name and password.
— Check or uncheck the Support Unicode Encoding checkbox.
— Click the Next button. If the database users that you entered in the dialog
do not exist, the installer can create them for you. The Select Components
To Configure dialog appears, as shown in Figure 11.
7. Select components that you want to configure during the installation in the
Select Components To Configure dialog, as shown in Figure 11. For detailed
information about configuration options in this dialog, see Select Components
To Configure Dialog on page 158.
TIBCO iProcess Engine for Windows Installation
42
| Chapter 2
Installing TIBCO iProcess Engine
Figure 11 Select Components to Configure Dialog
8. Click the Next button. In step 7., if you check
— the Configure Email Plug-in checkbox, the SMTP Server Parameters dialog
appears. Configure the parameters that the iProcess Email Server Plug-in
will use to connect to an SMTP server. For detailed information about
configuration options in this dialog, see SMTP Server Parameters Dialog on
page 166.
— the Install iProcess ‘Web Server’ Service checkbox, the TIBCO iProcess Web
Server Configuration dialog appears. Specify the location of TIBCO Hawk
and TIBCO Rendezvous that are used by the iProcess Web Server service.
For detailed information about configuration options in this dialog, see
Select Components To Configure Dialog on page 158.
— the Enable IAP checkbox, the Default Java Message Service dialog appears.
Configure the necessary Java Message Service (JMS) parameters to enable
Activity Monitoring and Work Queue Delta publication on TIBCO iProcess
Engine. For detailed information about configuration options in this
dialog, see TIBCO iProcess Web Server Configuration Dialog on page 168.
— any other checkbox, the Start Copying Files dialog appears. Review the
current settings in this dialog.
9. Click the Next button to proceed with the installation. If you checked the
Configure iProcess Objects Server checkbox in Figure 11, The TIBCO iProcess
Objects - Server Configuration Utility dialog appears, as shown in Figure 12.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 43
|
Figure 12 TIBCO iProcess Objects - Server Configuration Utility Dialog
— Set your desired configuration parameters for iProcess Objects Server. See
TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Objects Server
Administrator’s Guide for more information about the available parameters.
— If you are installing to a Microsoft Windows Cluster, you must specify that
iProcess Objects Server uses a static port (using the TCP tab).
10. Complete the installation. After completing the installation, the Setup
Complete dialog appears, as shown in Figure 13. You can choose to restart
your computer right now or later.
TIBCO iProcess Engine for Windows Installation
44
| Chapter 2
Installing TIBCO iProcess Engine
Figure 13 Setup Complete Dialog
11. Click the Finish button to exit the installation program.
Custom Installation - New Installation
For TIBCO iProcess Engine Custom Installation, complete the following steps:
1. Select the Custom radio button in the Setup Type dialog, and then click the
Next button. The Upgrade or New Install dialog appears, as shown in
Figure 14.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 45
|
Figure 14 Upgrade or New Install Dialog - New Installation
2. Select the New Installation radio button and specify the iProcess node name
you want to use for the new installation in the Upgrade Or New Install dialog,
and check both the Install Files and Install Schema checkboxes to install
iProcess Engine files and schema tables simultaneously.
— iProcess Files-install Owner can install files.
— iProcess Schema-install Owner can install schema tables.
For detailed information about configuration options in this dialog, see
Upgrade or New Install Dialog on page 146.
You must install iProcess Engine files and schema tables for a new installation,
but you can choose to install them separately. In this situation, you must
choose to install iProcess Engine schema tables first.
To install iProcess Engine schema tables separately, follow steps 3., 6., 7.,10.,
11. and 12.
To install iProcess Engine files separately, follow steps 3., 4., 5., 8., 9., 10., 11.
and 12.
TIBCO iProcess Engine for Windows Installation
46
| Chapter 2
Installing TIBCO iProcess Engine
3. Click the Next Button. The Choose Destination Location dialog appears, as
shown in Figure 15. Click the Browse... button to specify a Destination Folder
where you want to install iProcess Engine.
The Destination Folder is referred to as SWDIR.
The length of the SWDIR full pathname must not exceed 64 characters.
If you are installing iProcess Engine on a computer that is part of a Windows
cluster, SWDIR must be located on a cluster storage device that is accessible to
all nodes in the cluster.
Figure 15 Choose Destination Location Dialog - New Installation
4. (For Install Files Only) Click the Next button. The Configuration dialog
appears, as shown in Figure 16. For detailed information about configuration
options in this dialog, see Configuration Dialog on page 161
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 47
|
Figure 16 Configuration Dialog
5. (For Install Files Only) Click the Next button. The Group & User
Configuration dialog appears, as shown in Figure 17. Configure information
in the Group & User Configuration dialog. For detailed information about
configuration options in this dialog, see Group & User Configuration Dialog
on page 148.
TIBCO iProcess Engine for Windows Installation
48
| Chapter 2
Installing TIBCO iProcess Engine
Figure 17 Group & User Configuration Dialog - Custom Installation
6. (For Install Schema Only) Click the Next button.
If you are using an Oracle database with iProcess Engine, skip this step.
If you are using a SQL Server database with iProcess Engine, the SQL/ODBC
Details dialog appears, as shown in Figure 6. For detailed information about
configuration options in this dialog, see SQL/ODBC Details Dialog on
page 151.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 49
|
Figure 18 SQL/ODBC Details Dialog
a. Select the Choose An Existing ODBC Data Source or Enter A New
ODBC Data Source radio button in the dialog.
b. Check or uncheck the You Have DBA Privileges (To Create A Database
And Users) checkbox.
c. Click the Next button.
If you entered a new ODBC Data Source name, the ODBC Source Not
Found dialog appears and the following prompt is displayed in it:
ODBC Source does not exist. Do you want to create it?
Click the Yes button to open the Database Details dialog. Click the No
button to return to the SQL/ODBC Details dialog, and choose a different
ODBC Data Source name.
7. (For Install Schema Only) Configure the database that iProcess Engine will
connect to in the Database Details dialog. For detailed information about
configuration options in this dialog, see Database Details Dialog on page 154.
If you are using an Oracle database with iProcess Engine, the configuration
options are listed in Table 20, Configuration Options in the Database Details
Dialog - Oracle, on page 156. The Database Details dialog is shown in
Figure 19.
TIBCO iProcess Engine for Windows Installation
50
| Chapter 2
Installing TIBCO iProcess Engine
Figure 19 The Database Dialog for Configuring an Oracle Database
— Enter the Oracle database service (TNS) name.
— Enter the Database Admin Username and password.
— Check or uncheck the Support Unicode Encoding checkbox.
— Click the Change button to change the database users, if needed.
If you are using Oracle 12c, you must specify the owner name and user
name of iProcess Engine database with the prefix, c##. For example,
c##ipepro and c##ipeuser.
— Click the Next button. The installer now tries to connect to the Oracle
database using your specified settings and performs a number of checks
against your Oracle configuration. See Table 20, Configuration Options in
the Database Details Dialog - Oracle, on page 156 for detailed information.
The Select Tablesizes Profile dialog appears, as shown in Figure 20.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 51
|
Figure 20 Select Tablesizes profile Dialog
— Click the Next button. The Confirm Tablespace dialog appears. Select
whether you want to create all objects in IPEDATA tablespace or use
tablespace names exactly as specified in tablesizes file in the dialog.
Figure 21 Confirm Tablespace Dialog
— Click the Next button. The Select Components to Configure dialog appears,
as shown in Figure 23.
If you are using a SQL Server database with iProcess Engine, the configuration
options are listed in Table 19, Configuration Options in the Database Details
Dialog - SQL Server, on page 154. The Database Details dialog is shown in
Figure 22.
TIBCO iProcess Engine for Windows Installation
52
| Chapter 2
Installing TIBCO iProcess Engine
Figure 22 The Database Dialog for Configuring a SQL Server Database
— Enter the iPE DB Owner login name and password.
— Enter the iPE DB User login name and password.
— Check or uncheck the Support Unicode Encoding checkbox.
— Click the Next button. If the database users that you entered you entered in
the dialog do not exist, the installer can create them for you. The Select
Components To Configure dialog appears.
8. (For Install Files Only) Select components that you want to configure during
the installation in the Select Components To Configure dialog, as shown in
Figure 23. For detailed information about configuration options in this dialog,
see Select Components To Configure Dialog on page 158.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 53
|
Figure 23 Select Components to Configure Dialog
9. (For Install Files Only) Click the Next button. In step 8., if you check
— the Configure Email Plug-in checkbox, the SMTP Server Parameters dialog
appears. Configure the parameters that the iProcess Email Server Plug-in
will use to connect to an SMTP server. For detailed information about
configuration options in this dialog, see SMTP Server Parameters Dialog on
page 166.
— the Install iProcess ‘Web Server’ Service checkbox, the TIBCO iProcess Web
Server Configuration dialog appears. Specify the location of TIBCO Hawk
and TIBCO Rendezvous that are used by the iProcess Web Server service.
For detailed information about configuration options in this dialog, see
Select Components To Configure Dialog on page 158.
— the Enable IAP checkbox, the Default Java Message Service dialog appears.
Configure the necessary Java Message Service (JMS) parameters to enable
Activity Monitoring and Work Queue Delta publication on TIBCO iProcess
Engine. For detailed information about configuration options in this
dialog, see TIBCO iProcess Web Server Configuration Dialog on page 168.
— any other checkbox, the Start Copying Files dialog appears. Review the
current settings in this dialog.
10. Click the Next button to proceed with the installation. If you checked the
Configure iProcess Objects Server checkbox in Figure 23, The TIBCO iProcess
Objects - Server Configuration Utility dialog appears, as shown in Figure 24.
TIBCO iProcess Engine for Windows Installation
54
| Chapter 2
Installing TIBCO iProcess Engine
Figure 24 TIBCO iProcess Objects - Server Configuration Utility Dialog
— Set your desired configuration parameters for iProcess Objects Server. See
TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Objects Server
Administrator’s Guide for more information about the available parameters.
— If you are installing to a Microsoft Windows Cluster, you must specify that
iProcess Objects Server uses a static port (using the TCP tab).
11. Complete the installation. After completing the installation, the Setup
Complete dialog appears, as shown in Figure 25. You can choose to restart
your computer right now or later.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 55
|
Figure 25 Setup Complete Dialog
12. Click the Finish button to exit the installation program.
Custom Installation - Upgrade Existing Installation
For TIBCO iProcess Engine Custom Installation, complete the following steps:
1. Select the Custom radio button in the Setup Type dialog, then click the Next
button. The Upgrade or New Install dialog appears, as shown in Figure 26.
TIBCO iProcess Engine for Windows Installation
56
| Chapter 2
Installing TIBCO iProcess Engine
Figure 26 Upgrade or New Install Dialog - Upgrade Existing Installation
2. Select the Upgrade Existing Installation radio button, then select the iProcess
node name you want to upgrade in the Upgrade or New Install dialog.
— iProcess Files-install Owner can upgrade files.
— iProcess Schema-install Owner can upgrade schema tables.
You can either upgrade iProcess Engine files and schema tables
simultaneously, or upgrade them separately. If there are no schema changes
between the current version and the upgrade, the Upgrade Schema checkbox
is unchecked and disabled. If you need to upgrade schema tables, you must
upgrade iProcess Engine files also. For detailed information about
configuration options in this dialog, see Upgrade or New Install Dialog on
page 146.
To upgrade iProcess Engine schema tables separately, follow steps 3., 6., 7.,10.,
11. and 12.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 57
|
To upgrade iProcess Engine files separately, follow steps 3., 4., 5., 8., 9., 10., 11.
and 12.
Since iProcess Engine 11.5, all the new case memo data is stored in the nmemo
table and pack_nmemo table. You can choose to migrate old case memo data
when upgrading to iProcess Engine 11.5 by checking the Migrate live cases or
Migrate all cases checkbox.
The migration for the case memo data might take a long time depending on
the volume of the memos in the pack_memo and memo tables. You can also
migrate the memo data by using the swutil MIGRATEMEMOS command after
the upgrades.
3. Click the Next Button. The Question dialog appears, as shown in Figure 27.
Figure 27 Question Dialog
It informs you that the installer needs to delete the contents of the
SWDIR\tsys and SWDIR\sysinfo folders before continuing. It also reminds
you that you must have removed any user-defined constraints, indexes, or
statistics that you have added to iProcess Engine schema tables before
continuing with the upgrade. For more information, see Recreating All
User-defined Constraints (Or Triggers), Indexes and Statistics on the iProcess
Engine Schema Tables on page 135.
4. (For Upgrade Files Only) Click the Yes button when you are ready to continue
with the upgrade. The Configuration dialog appears, as shown in Figure 28.
For detailed information about configuration options in this dialog, see
Configuration Dialog on page 161
TIBCO iProcess Engine for Windows Installation
58
| Chapter 2
Installing TIBCO iProcess Engine
Figure 28 Configuration Dialog - Upgrade
5. (For Upgrade Files Only) Click the Next button. The Group & User
Configuration dialog appears, as shown in Figure 29. Configure information
in the Group & User Configuration dialog. For detailed information about
configuration options in this dialog, see Group & User Configuration Dialog
on page 148.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 59
|
Figure 29 Group & User Configuration Dialog - Upgrade
6. (For Upgrade Schema Only) Click the Next button.
If you are using an Oracle database with iProcess Engine, skip this step.
If you are using a SQL Server database with iProcess Engine, the SQL/ODBC
Details dialog appears. For detailed information about configuration options
in this dialog, see SQL/ODBC Details Dialog on page 151. Click the Next
button.
7. (For Upgrade Schema Only) Configure the database that iProcess Engine will
connect to in the Database Details dialog. For detailed information about
configuration options in this dialog, see Database Details Dialog on page 154.
If you are using an Oracle database with iProcess Engine, the configuration
options are listed in Table 20, Configuration Options in the Database Details
Dialog - Oracle, on page 156.
If you are using a SQL Server database with iProcess Engine, the configuration
options are listed in Table 19, Configuration Options in the Database Details
Dialog - SQL Server, on page 154.
TIBCO iProcess Engine for Windows Installation
60
| Chapter 2
Installing TIBCO iProcess Engine
8. (For Upgrade Files Only) Click the Next button. The Select Components to
Configure dialog appears. Select the components that you want to configure
during the upgrade in this dialog, as shown in Figure 30. For detailed
information about configuration options in this dialog, see Select Components
To Configure Dialog on page 158.
Figure 30 Select Components to Configure Dialog
9. (For Upgrade Files Only) Click the Next button. The Start Copying Files
dialog appears. Review the current settings in this dialog.
10. Click the Next button to proceed with the installation.
If you checked the Configure iProcess Objects Server checkbox in Figure 30,
The TIBCO iProcess Objects - Server Configuration Utility dialog appears, as
shown in Figure 31.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in GUI Mode 61
|
Figure 31 TIBCO iProcess Objects - Server Configuration Utility Dialog
— Set your desired configuration parameters for iProcess Objects Server. See
TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Objects Server
Administrator’s Guide for more information about the available parameters.
— If you are installing to a Microsoft Windows Cluster, you must specify that
iProcess Objects Server uses a static port (using the TCP tab).
11. Complete the installation. After completing the installation, the Setup
Complete dialog appears, as shown in Figure 32. You can choose to restart
your computer right now or later.
TIBCO iProcess Engine for Windows Installation
62
| Chapter 2
Installing TIBCO iProcess Engine
Figure 32 Setup Complete Dialog
12. Click the Finish button to exit the installation program.
TIBCO iProcess Engine for Windows Installation
Installing TIBCO iProcess Engine in Silent Mode 63
|
Installing TIBCO iProcess Engine in Silent Mode
If you want to install TIBCO iProcess Engine in silent mode, you must have
installed it in GUI mode on a computer and generated a response file that
provides all the configuration information. You can subsequently use this
response file as a script to run a similar installation automatically, without having
to manually enter values in the dialogs. You may want to do this if you are
installing a master server and multiple slave servers: you can run the installer in
GUI mode for the master server, and run it in silent mode using the resulting
response file on each slave server.
The following procedure explains how to install TIBCO iProcess Engine in silent
mode.
•
Generating a Response File, page 63
•
Performing an Installation in Silent Mode, page 64
Generating a Response File
To generate a response file, complete the following steps:
1. Perform all the necessary pre-installation tasks. See Pre-installation on page 30
for detailed information.
2. Open a command-line window and type the following command:
setupDir\setup.exe -bC:\spoinfo.reg -r -f1responseFileName.rst
where:
— setupDir is the directory from which you run the installer in GUI mode.
— responseFileName.rst is the full path of the response file in which you want
to record your responses to the installation prompts.
For example:
E:\TIBCO\setup.exe -bC:\spoinfo.reg -r -f1C:\ipe113.rst
3. Run setup.exe, entering the required values to all the prompts as normal. See
Installing TIBCO iProcess Engine in GUI Mode on page 34.
4. Perform the post-installation tasks. See Post-installation on page 66 for
detailed information.
5. Start iProcess Engine to make sure that it has been correctly installed.
TIBCO iProcess Engine for Windows Installation
64
| Chapter 2
Installing TIBCO iProcess Engine
Performing an Installation in Silent Mode
To perform an installation in silent mode, complete the following steps:
1. Prepare a response file responseFileName.rst. For detailed information, see
Generating a Response File on page 63.
2. Perform all the necessary pre-installation tasks on each machine where you
want to install iProcess Engine. See Pre-installation on page 30 for detailed
information.
3. Log in as a user who is a member of the Administrators group. See
IPEINSTALL on page 4 for more information.
4. Open a command-line window and type the following command:
setupDir\setup.exe -bC:\spoinfo.reg -s -f1responseFileName.rst
where:
— setupDir is the directory from which you run the installer in GUI mode.
— responseFileName.rst is the full path of the response file in which you want
to record your responses to the installation prompts.
5. Press the Enter key on the keyboard. The installer installs iProcess Engine,
automatically getting the necessary information from the response file.
6. Perform the post-installation tasks. See Post-installation on page 66 for
detailed information.
7. Start iProcess Engine to make sure that it has been correctly installed.
TIBCO iProcess Engine for Windows Installation
Upgrading TIBCO iProcess Engine 65
|
Upgrading TIBCO iProcess Engine
If you are using TIBCO iProcess Engine version 11.0 or higher, or TIBCO Process Engine
9.0, you can upgrade to version 11.5.0 directly without upgrading through an intermediate
version. For detailed information of upgrade, see Custom Installation - Upgrade Existing
Installation on page 55.
Upgrade Performance and Timing
Upgrading to Version 11.5.0 can involve significant changes to iProcess data and
data structures. The upgrade process is therefore complex, and can take a
significant amount of time to complete if the system being upgraded has a large
amount of case data.
TIBCO cannot provide an estimate of how long the upgrade will take because of
the number of customer-specific factors that can have an impact, and the
complexity of their interaction, for example, the amount of data in your existing
system, the configuration of your database, and the hardware setup you are
running.
TIBCO therefore strongly recommends that you test the upgrade before
performing it on your target system, either in a representative production
environment, or using a copy of your production system. This will allow you to
determine how long the upgrade is likely to take, and to identify any specific
factors that may affect the success or duration of the upgrade.
Upgrade Steps
To upgrade an existing iProcess Engine to Version 11.5.0, see Custom Installation Upgrade Existing Installation on page 55 for detailed information.
TIBCO iProcess Engine for Windows Installation
66
| Chapter 2
Installing TIBCO iProcess Engine
Post-installation
This section describes the tasks you need to perform after you have installed
TIBCO iProcess Engine according to the instructions in Installing TIBCO iProcess
Engine in GUI Mode on page 34.
Table 14 provides a checklist of the tasks that you must or may need to perform
before starting iProcess Engine. The table shows:
•
whether the iProcess Files-install Owner, iProcess Schema-install Owner, or
DBA user needs to perform the task. See Organization Roles on page 3 for
more information about iProcess Files-install Owner, iProcess Schema-install
Owner and DBA.
•
the status of a task, depending on whether you are installing a new iProcess
Engine or upgrading an existing one. There are four possible task statuses:
— Required —You must perform this task before starting the iProcess Engine.
— Check — You may need to perform this task before starting the iProcess
Engine, depending on your installation scenario.
— Optional — You may wish to perform this task before starting the iProcess
Engine, but it is not essential.
— N/A — You can start iProcess Engine without performing this task.
For detailed information about each task, see Post-installation Tasks on
page 115.
You may want to print this table as a useful quick reference when performing the
post-installation tasks. The Done? column in the table provides a place for you to
check off tasks that have been done.
Table 14 Post-Installation Tasks Checklist
Task
Re-implementing
Changes to Upgraded
Configuration Files
Database
Type
Oracle
SQL Server
To be done by
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
TIBCO iProcess Engine for Windows Installation
Install
Status
Upgrade
Status
See
N/A
Optional
page 117
Done?
Post-installation 67
|
Table 14 Post-Installation Tasks Checklist (Cont’d)
Task
Configuring Firewall
Port Ranges on Slave
Servers
Database
Type
Oracle
SQL Server
To be done by
iProcess
Files-install
Owner
Install
Status
Upgrade
Status
See
Check
Check
page 118
Optional
Optional
page 119
Check
Check
page 121
Check
Check
page 122
Check
Check
page 126
Check
Check
page 127
Done?
iProcess
Schema-install
Owner
Configuring TIBCO
iProcess Objects Server
and TIBCO iProcess
Objects Director
Oracle
Enabling COM+
Network Access
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
Configuring the
Microsoft Windows
Cluster
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
Enabling Oracle
Function-based Indexes
Oracle
iProcess
Schema-install
Owner
DBA
Installing the IBM
Client for JMS on J2SE
with IBM WebSphere
Application Server
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
TIBCO iProcess Engine for Windows Installation
68
| Chapter 2
Installing TIBCO iProcess Engine
Table 14 Post-Installation Tasks Checklist (Cont’d)
Task
Configuring IAPJMS
Security Settings
Database
Type
Oracle
SQL Server
To be done by
iProcess
Files-install
Owner
Install
Status
Upgrade
Status
See
Optional
Optional
page 129
Optional
Optional
page 130
N/A
Optional
page 131
Check
Check
page 132
Check
Check
page 134
N/A
Check
page 135
iProcess
Schema-install
Owner
Configuring the Default
iProcess Engine Installer
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
Recreating Prediction
Data
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
Configuring Access to
SSOLite Stored
Procedures for TIBCO
iProcess Plug-ins
SQL Server
Granting Permissions
on Stored Procedures in
EAI Database Steps
Oracle
iProcess
Schema-install
Owner
DBA
SQL Server
iProcess
Schema-install
Owner
DBA
Recreating All
User-defined
Constraints (Or
Triggers), Indexes and
Statistics on the iProcess
Engine Schema Tables
Oracle
SQL Server
TIBCO iProcess Engine for Windows Installation
iProcess
Schema-install
Owner
DBA
Done?
Post-installation 69
|
Table 14 Post-Installation Tasks Checklist (Cont’d)
Task
Database
Type
Updating the Domain
Group Policy for the
Log On As A Service
Right
Oracle
Enabling OLE
Automation on SQL
Server
SQL Server
SQL Server
To be done by
iProcess
Files-install
Owner
Install
Status
Upgrade
Status
See
Check
Check
page 137
N/A
Check
page 137
Optional
Optional
page 138
Optional
Optional
page 139
Optional
Optional
page 140
Optional
Optional
page 142
Done?
iProcess
Schema-install
Owner
iProcess
Schema-install
Owner
DBA
Disabling or
Re-enabling Write
Access to WebDav
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
Configuring JMX Ports
to Run Through a
Firewall
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
Setting Up iProcess
Engine with an IPv6
Address
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
Starting TIBCO iProcess
Engine
Oracle
SQL Server
iProcess
Files-install
Owner
iProcess
Schema-install
Owner
TIBCO iProcess Engine for Windows Installation
70
| Chapter 2
Installing TIBCO iProcess Engine
Installing or Upgrading TIBCO iProcess Engine to Version 11.5
If you want to install or upgrade TIBCO iProcess Engine to version 11.5, the WIS
and WQS processes might consume extremely high levels of CPU resources
because you use an older version of the pthreads library with TIBCO iProcess
Engine 11.5.0. For TIBCO iProcess Suite version 11.5, the pthread.dll library has
been rebuilt; versions that were provided with previous releases of TIBCO
iProcess Engine are incompatible with TIBCO iProcess Engine 11.5.
To install or upgrade TIBCO iProcess Engine to version 11.5, perform the
following steps:
1. Check whether you have the pthread.dll file in your local directory.
— For Windows (32-bit), the pthread.dll file is located in the
%systemroot%\system32 directory.
— For Windows (64-bit), the pthread.dll file is located in the
%systemroot%\SysWOW64 directory.
2. If the pthread.dll file is not saved in your local directory, download the
latest version of the pthread.dll file and save it in the directory that is
specified in the first step.
See Downloading the pthreads Library on page 10 for details on how to
download the pthread.dll file.
3. Install or upgrade TIBCO iProcess Engine.
For more details on how to install TIBCO iProcess Engine in GUI mode, see
Installing TIBCO iProcess Engine in GUI Mode on page 34. For more details
on how to install TIBCO iProcess Engine in silent mode, see Installing TIBCO
iProcess Engine in Silent Mode on page 63. For more details on how to
upgrade TIBCO iProcess Engine, see Upgrading TIBCO iProcess Engine on
page 65.
4. After installing or upgrading TIBCO iProcess Engine to version 11.5.
5. Copy the latest version of the pthread.dll file to the following folder. See
step 2 on how to download the latest version of this file.
— $SWDIR\bin
— $SWDIR\util
— $SWDIR\rpc
— $SWDIR\etc
— $SWDIR\uninstall
TIBCO iProcess Engine for Windows Installation
Installing or Upgrading TIBCO iProcess Engine to Version 11.5 71
|
After performing the previous steps, you can run TIBCO iProcess Engine 11.5
successfully.
TIBCO iProcess Engine for Windows Installation
72
| Chapter 2
Installing TIBCO iProcess Engine
TIBCO iProcess Engine for Windows Installation
| 73
Chapter 3
Uninstalling TIBCO iProcess Engine
This chapter describes how to uninstall TIBCO iProcess Engine on Windows.
Topics
•
Pre-removal Considerations, page 74
•
Uninstalling iProcess Engine from a Windows Cluster, page 75
•
Uninstalling iProcess Engine, page 76
•
Removing the ODBC Data Source, page 77
•
Removing the iProcess Events COM+ Application, page 78
•
Removing the iProcess Engine Database, page 79
TIBCO iProcess Engine for Windows Installation
74
| Chapter 3
Uninstalling TIBCO iProcess Engine
Pre-removal Considerations
Before uninstalling your iProcess Engine, TIBCO recommends that you:
•
Do not attempt to delete iProcess Engine files directly, as some may remain on
the system, causing problems if you want to reinstall iProcess Engine later.
•
Back up your database schema and any other files if you want to keep your
existing iProcess Engine data. Otherwise it will be lost when you uninstall the
iProcess Engine.
Configuration changes that were made prior to installation are not automatically
removed. Any such changes made must be manually changed back to their
original values.
•
If you uninstall an iProcess Engine that uses a node cluster architecture, you
must remove things in the following sequence:
a. Remove iProcess Engine from each slave server.
b. Remove iProcess Engine from the master server.
c. Remove iProcess Engine database schema and Oracle users or SQL logins
from the Oracle or SQL Server instance.
When you are ready to uninstall iProcess Engine, work through the instructions in
the following sections in sequence.
It is essential that if you have TIBCO iProcess Technology Plug-ins installed, you
uninstall these before uninstalling iProcess Engine. See TIBCO iProcess Technology
Plug-ins Installation for detailed information.
TIBCO iProcess Engine for Windows Installation
Uninstalling iProcess Engine from a Windows Cluster 75
|
Uninstalling iProcess Engine from a Windows Cluster
If you have installed iProcess Engine in a Windows cluster:
1. Run the following command on each secondary machine in the cluster:
SWDIR\mscluster\mscluster -r
Do not run this command on the machine where iProcess Engine is installed.
If you do so, you will not be able to uninstall iProcess Engine from that machine.
This command removes the following iProcess Engine shared resources and
services:
—
iProcess
nodeName Process Sentinels service
—
iProcess
nodename Web Server service
—
NobleNet Portmapper for TCP
—
iProcess Events
—
iProcess COM+ Bridge
service
COM+ application
COM+ application
where nodename is the node name of this iProcess Engine.
It also removes the port numbers used by the iProcess Engine watcher and
worker process sentinels in the
%systemroot%\system32\drivers\etc\services file.
2. Remove the Generic
Service resources for the NobleNet Portmapper and
services for this iProcess Engine using Cluster
Administrator, see Configuring the Microsoft Windows Cluster on page 122
for details.
Process Sentinels
See Microsoft documentation for more information about the Cluster
tool.
Administrator
3. Remove the ODBC data source for this iProcess Engine from each secondary
machine in the cluster if you are using a SQL Server database.
4. Uninstall iProcess Engine itself. See Uninstalling iProcess Engine on page 76
for details.
TIBCO iProcess Engine for Windows Installation
76
| Chapter 3
Uninstalling TIBCO iProcess Engine
Uninstalling iProcess Engine
To remove iProcess Engine from your computer, complete the following steps:
1. Log in to Windows using the IPEADMIN user account and also make sure that
all users are logged out from iProcess Engine.
2. Open the Control Panel window.
a. Stop the following services:
iProcess
nodeName Process Sentinels
iProcess
NodeName Web Server (if it exists)
b. Double-click the Add or Remove Programs button and select the TIBCO
iProcess Engine nodeName item from the list, where nodeName is the name
of iProcess Engine installation that you want to uninstall. Then click the
Remove button to perform the uninstallation process.
If any messages are displayed during the uninstallation, follow the on-screen
instructions.
3. Remove the ODBC data source used by this iProcess Engine if you are using a
SQL Server database. See Removing the ODBC Data Source on page 77 for
details.
4. Remove the iProcess Events COM+ application. See Removing the iProcess
Events COM+ Application on page 78 for details.
TIBCO iProcess Engine for Windows Installation
Removing the ODBC Data Source 77
|
Removing the ODBC Data Source
If you are using a SQL Server database, the steps listed below are required.
To remove the ODBC data source used by this iProcess Engine, complete the
following steps:
1. Open the Control Panel window.
2. Click the Administrative Tools button, then double-click the Data Sources
(ODBC) button.
3. Select the SQL Server data source used by this iProcess Engine database on
the System DSN tab and click the Remove button.
4. Click the Yes button to confirm that you want to remove the ODBC data
source in the ODBC Administrator dialog.
5. Close the Data Sources (ODBC) and Administrative Tools windows.
6. Remove the iProcess Events COM+ application. See Removing the iProcess
Events COM+ Application on page 78 for details.
TIBCO iProcess Engine for Windows Installation
78
| Chapter 3
Uninstalling TIBCO iProcess Engine
Removing the iProcess Events COM+ Application
Removing the iProcess Events COM+ application means that any other iProcess
Engine installed on this computer will no longer work.
Do not remove this application if there are other iProcess Engine installations on
this computer.
To remove the iProcess Events COM+ application, complete the following steps:
1. Open the Control Panel window.
2. Click the Administrative Tools button, then double-click the Component
Services button. The Component Services console appears.
3. Select Component Services > Computers > My Computer > COM+
Application in the left pane.
4. Right-click the iProcess Events item and select Delete from the pop-up menu.
5. Click the Yes button to confirm that you want to delete the iProcess
COM+ application in the Confirm Item Delete dialog.
Events
6. Close the Control Panel window.
7. Delete the following two files from your system:
—
winnt\system32\SWEventClass.dll
—
winnt\system32\SWEventClassSubscriber.dll
8. Remove the iProcess Engine database. See Removing the iProcess Engine
Database on page 79 for details.
TIBCO iProcess Engine for Windows Installation
Removing the iProcess Engine Database 79
|
Removing the iProcess Engine Database
You need to follow a specific procedure to remove your iProcess Engine database:
•
Oracle
•
SQL Server
Oracle
Do not remove the iProcess Engine schema and Oracle users until you have
removed the iProcess Engine files from the master server and all slave servers.
Delete the iProcess schema and the iProcess background user and foreground
user accounts from the Oracle database. See Oracle documentation for more
information about how to do this.
SQL Server
Do not remove the iProcess Engine schema and SQL Server users until you have
removed the iProcess Engine files from the master server and all slave servers.
To delete the iProcess Engine database and SQL logins:
1. Start SQL Server Management Studio.
You must install SQL Tools to get the SQL Server Management Studio utility.
2. Delete the iProcess Engine database:
a. Expand Databases to the iProcess Engine database you want to delete.
b. Right-click the iProcess Engine database and select Delete from the
pop-up menu.
c. Click the Yes button to confirm that you want to delete this database.
3. Delete the IPE
DB Owner
and IPE
DB User
SQL Server login IDs:
a. Expand Security and click Logins.
b. Right-click the IPE DB Owner login and select Delete from the pop-up
menu. Click the Yes button to confirm that you want to delete this
database.
TIBCO iProcess Engine for Windows Installation
80
| Chapter 3
Uninstalling TIBCO iProcess Engine
c. Right-click the IPE DB User login and select Delete from the pop-up
menu. Click the Yes button to confirm that you want to delete this
database.
See SQL Server documentation for more information about this procedure.
TIBCO iProcess Engine for Windows Installation
| 81
Appendix A
Pre-installation Tasks
This appendix lists the pre-installation tasks.
Topics
•
Checking for Any Late-breaking Information, page 82
•
Backing Up the TIBCO iProcess Engine File System, page 83
•
Backing Up the TIBCO iProcess Engine Database Schema, page 85
•
Checking for the Database Codepage Setting, page 86
•
Upgrading the Operating System, page 87
•
Upgrading the Database, page 88
•
Stopping Any Other iProcess Engines on the Same Machine, page 89
•
Setting Up DCOM Permissions for the iProcess Objects Server, page 91
•
Setting Up DCOM Permissions for a Node Cluster, page 92
•
Configuring the Oracle Schema, page 93
•
Setting Up Oracle Transparent Application Failover (TAF), page 98
•
Configuring Oracle OPEN_CURSORS, page 100
•
Disabling Oracle Authentication Services, page 101
•
Configuring Oracle Character Set Support, page 102
•
Disabling Oracle Flashback Query, page 104
•
Creating an Oracle UNDO Tablespace, page 105
•
Creating the SQL Server Database and Logins, page 106
•
Creating the ODBC Data Source, page 110
•
Removing All User-defined Constraints (or Triggers), Indexes, and Statistics
From the iProcess Engine Schema Tables, page 112
•
Configuring the Microsoft Windows Cluster, page 113
TIBCO iProcess Engine for Windows Installation
82
| Appendix A
Pre-installation Tasks
Checking for Any Late-breaking Information
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required
Upgrading from an iProcess Engine Version 11.0 or later
Required
Oracle, SQL Server
Before installing TIBCO iProcess Engine, you need to check if there any
restrictions, known issues, or other late-breaking information that may affect your
installation.
See TIBCO iProcess Engine Release Notes for detailed information.
Procedure
To check for late-breaking information:
1. Read TIBCO iProcess Engine Release Notes and TIBCO iProcess Engine Readme
that are supplied with the iProcess Engine software.
2. Visit the TIBCO Support Web, at http://www.tibco.com/services/support.
TIBCO iProcess Engine for Windows Installation
Backing Up the TIBCO iProcess Engine File System 83
|
Backing Up the TIBCO iProcess Engine File System
Status
Database
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
N/A
Upgrading from an iProcess Engine Version 11.0 or later
Required
Oracle, SQL Server
Description
You must back up your iProcess Engine system before an upgrade.
Make sure that you back up the entire SWDIR directory structure, and any other
files you want to restore if a failure occurs during upgrade. The upgrade process
has no UNDO capability. If it fails for any reason, you will require a full backup of
your SWDIR file system to be able to restore your original iProcess Engine system.
You must also back up your database schema — For detailed information, see Backing
Up the TIBCO iProcess Engine Database Schema on page 85.
Procedure
Complete the following steps to back up an existing iProcess Engine:
1. Get all users to log out of the iProcess Engine.
2. Stop the iProcess nodeName Process Sentinels service from the Control
Panel window to stop the iProcess Engine.
3. Make a secure offline copy of the entire SWDIR directory structure and any
other files you want to restore if a failure occurs during upgrade using your
operating system backup utility.
If you have made any changes to the following files since they were installed, you
need to manually re-implement those changes after upgrading the iProcess
Engine:
•
SWDIR\etc\language.lng\staffico
•
SWDIR\etc\language.lng\auditusr.mes
This is because the files are overwritten during the upgrade and any changes to
the original files are not automatically merged into the new files. See
Re-implementing Changes to Upgraded Configuration Files on page 117 for more
information.
TIBCO iProcess Engine for Windows Installation
84
| Appendix A
Pre-installation Tasks
See Also
For more information about the procedures, see TIBCO iProcess Engine
Administrator's Guide and your operating system documentation.
TIBCO iProcess Engine for Windows Installation
Backing Up the TIBCO iProcess Engine Database Schema 85
|
Backing Up the TIBCO iProcess Engine Database Schema
Status
Database
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
N/A
Upgrading from an iProcess Engine Version 11.0 or later
Required
Oracle, SQL Server
Description
You must back up your iProcess Engine database schema before an upgrade.
In some circumstances, an upgrade may fail and leave iProcess Engine in an
unusable condition. If this happens, you need to back up your database schema to
restore the system to its previous condition before you can either use it or attempt
to upgrade it again.
Procedure
See your database documentation for more information about how to back up the
iProcess Engine database schema.
TIBCO iProcess Engine for Windows Installation
86
| Appendix A
Pre-installation Tasks
Checking for the Database Codepage Setting
Status
Database
Description
Node Cluster
Procedure
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
Before installing TIBCO iProcess Engine, check that the database codepage setting
and the codepage setting of your system environment variable used to start up
iProcess Engine are consistent.
The codepage setting of your database must be consistent with the system
environment variable in both master server and slave servers.
For detailed information about how to configure the codepage setting of the
system environment variable and databases, see your operating system
documentation and your database documentation.
For example, if you want to use UTF-8 codepage for Oracle database and your
system environment variable, you need to do the following settings:
export NLS_LANG=AMERICAN_AMERICA.AL32UTF8
TIBCO iProcess Engine for Windows Installation
Upgrading the Operating System 87
|
Upgrading the Operating System
Status
Database
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Required
Oracle, SQL Server
Description
TIBCO iProcess Engine requires a specific release version of an operating system.
For supported operation systems information, see Supported Platforms on
page 8.
Node Cluster
The operating system version used must be the same on the master server and on
each slave server.
Procedure
See Also
If you are using an operating system version that does not meet the specified
requirements, you must upgrade it.
See your operating system documentation for more information about how to
upgrade your operation system.
TIBCO iProcess Engine for Windows Installation
88
| Appendix A
Pre-installation Tasks
Upgrading the Database
Status
Database
Description
Node Cluster
Procedure
See Also
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
TIBCO iProcess Engine requires a specific release version of a database. For
supported database information, see Supported Databases on page 18.
The database version used must be the same on the master server and on each
slave server.
If you are using a version of database that does not meet the specified
requirements, you must upgrade it.
See your database documentation for more information about how to upgrade a
database.
TIBCO iProcess Engine for Windows Installation
Stopping Any Other iProcess Engines on the Same Machine 89
|
Stopping Any Other iProcess Engines on the Same Machine
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required for the first
installation
Upgrading from an iProcess Engine Version 11.0 or later
Required for the first
upgrade
Oracle, SQL Server
Before installing TIBCO iProcess Engine on a machine, you need to stop any other
iProcess Engines running on the same machine. If you do not do this when it is
required, the installer will display an error dialog and fail when you run it. See
Installer Cannot Continue Because Another iPE is Running on page 191 for more
information.
After stopping iProcess Engines running on a machine, the installer can stop and
replace components (for example, the iProcess Events COM+ application) that are
also used by other iProcess Engine installations. The installer checks whether the
latest versions of these components are currently installed, and only replaces
them where the version delivered with this iProcess Engine is more recent than
the installed version of the component.
Therefore, it is only necessary to stop other iProcess Engines for the first
installation of iProcess 11.3 on a given machine. When you install a second or
subsequent instance of iProcess, these components will already be at the latest
versions, and will not need to be replaced.
Procedure
To stop any other iProcess Engines running on the same machine, complete the
following steps:
1. Open the Control Panel window.
2. Double-click the Administrative Tools item.
3. Double-click the Services item.
4. Search for any running services with the following names:
—
iProcess
nodeName Process Sentinels
—
iProcess
NodeName Web Server
5. If there are any, right-click each service and select Stop from the pop-up
menu.
TIBCO iProcess Engine for Windows Installation
90
| Appendix A
Pre-installation Tasks
See Also
For more information about how to stop an iProcess Engine, see “Stopping
iProcess Engine” in Chapter 1, TIBCO iProcess Engine Administrator’s Guide.
TIBCO iProcess Engine for Windows Installation
Setting Up DCOM Permissions for the iProcess Objects Server 91
|
Setting Up DCOM Permissions for the iProcess Objects Server
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required
Upgrading from an iProcess Engine Version 11.0 or later
Required
Oracle, SQL Server
If the Windows Distributed Component Object Model (DCOM) facility is enabled
on this machine and you intend to enable the iProcess Objects Server during the
installation (see Select Components To Configure Dialog on page 158 for detailed
information), you must ensure that the IPEADMIN user has DCOM Access
Permissions and Launch Permissions.
If you have chosen to use separate accounts for the IPEADMIN and IPESERVICE
users, you must give the IPESERVICE user the same DCOM permissions as the
IPEADMIN user.
You may have DCOM enabled without having explicitly set it. For example,
Microsoft Web Server enables it as part of its setup.
Procedure
To set up DCOM permissions, complete the following steps:
1. Log on to Windows as an administrator user.
2. Run dcomcnfg in the command-line window. The Component Services
window appears.
3. Double-click the Computers icon to locate the My Computer icon.
4. Right-click the My Computer icon and select Properties from the pop-up
menu. The My Computer Properties dialog appears.
5. Click the Default Properties tab.
— If the Enable Distributed COM On This Computer checkbox is checked,
you must set the necessary permissions for the IPEADMIN user. See your
operating system documentation for detailed information.
— If the Enable Distributed COM On This Computer checkbox is unchecked,
DCOM is not enabled and you can proceed with other pre-installation
tasks.
6. If you have chosen to use separate accounts for the IPEADMIN and
IPESERVICE users, repeat the above procedure for the IPESERVICE user.
TIBCO iProcess Engine for Windows Installation
92
| Appendix A
Pre-installation Tasks
Setting Up DCOM Permissions for a Node Cluster
This only applies to Windows XP and Windows Server 2003.
Status
Database
Description
Procedure
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
In a node cluster, iProcess Engine machines communicate by publishing and
subscribing to events using the iProcess Engine event mechanism. This means
that all machines in a node cluster must have permission to instantiate events. To
allow this, you must configure the Windows Distributed Component Module
(DCOM) facility to allow ANONYMOUS LOGON permissions on each machine.
To set up DCOM permissions, complete the following steps:
1. Log on to Windows as an administrator user.
2. Run dcomcnfg in the command line window. The Component Services
window appears.
3. Double-click the Computers icon to locate the My Computer icon.
4. Right-click the My Computer icon and select Properties from the pop-up
menu. The My Computer Properties dialog appears.
5. Click the COM Security tab. Follow theses steps to set up Access Permissions:
a. Click the Edit Limits... button in the Access Permissions area. The Access
Permission dialog appears.
b. Select the ANONYMOUS LOGIN option from the Group Or User Names
list and check the Allow checkbox for Remote Access in the Permissions
for ANONYMOUS LOGON area.
c. Click the OK button to return to the My Computer Properties dialog.
d. Click the OK button to return to the Component Services dialog.
e. Exit the Component Services window.
TIBCO iProcess Engine for Windows Installation
Configuring the Oracle Schema 93
|
Configuring the Oracle Schema
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
N/A
Oracle
When running the installer, it creates a small database by default (approximately
50Mb) that is suitable for benchmarking or development purposes.
You can modify this default database configuration if you want to optimize it for
your Oracle environment, taking into account factors specific to your installation,
such as the number of cases, the amount of case data, the life of cases, and so on.
The Default iProcess Engine Schema Configuration
By default, the installer performs the following operations when it creates the
iProcess Engine schema:
•
It creates the following tablespaces for the Oracle instance. In the non- RAC
environment, the default tablespaces location is ORACLE_HOME\database. In
a RAC environment, the installer does not specify the datefile value, and
RAC determines the tablespaces location automatically.
— a data tablespace (with the default name staffwar). By default, all iProcess
Engine tables, indexes, and Oracle AQ queues are stored in this tablespace.
— a temporary tablespace (with the default name temp), which is used for
sorting.
•
It creates the following Oracle users:
— iProcess Engine DB Schema Owner User (with the default name swpro).
— iProcess Engine DB User (with the default name swuser).
The staffwar and temp tablespaces are allocated to these users as their
default tablespaces.
•
It creates the iProcess Engine schema tables, indexes, and Oracle AQ queues
in the default staffwar tablespace.
The use of the staffwar tablespace is defined in the tablesizes file. See
How the Installer Sets Up the Default Configuration on page 94 for details.
TIBCO iProcess Engine for Windows Installation
94
| Appendix A
Pre-installation Tasks
How the Installer Sets Up the Default Configuration
The installer uses the init2Kora_tok.sql file and the tablesizes file
as the template files to create the iProcess Engine schema:
•
the init2Kora_tok.sql file
The init2Kora_tok.sql file defines the following configuration macros for
each iProcess Engine table and index that is to be created:
— SIZETABLESIZE—the initial size (in extents) of a table.
— SIZETABLEPCTINCREASE—the percentage increase to be applied when
growing a table.
— SIZETABLESPACE—the tablespace to be used by a table.
— SIZEINDEXSPACE—the tablespace to be used by an index.
where SIZE is one of seven different categories, as shown in Table 15.
Table 15 SIZE Categories
Category
Used For
Example
TINY
Small tables that do not grow.
flag_table
procedure_lock
SMALL
Generally static tables that contain small
amounts of data.
list_names
MEDIUM
Generally static tables that contain more data.
user_names user_values
BIG
Slightly larger tables that typically hold values
for references held in SMALL and MEDIUM
tables.
user_values
Most of the tables that contain case-related
information, typically ones that only have one or
two rows per case.
case_information
Tables that hold multiple rows per case, but not
for all cases.
pack_data
Tables that hold multiple rows per case for all
cases.
audit_trail
LARGE
HUGE
MASSIVE
dbs_names
db_str_values
outstanding_addr
staffo
pack_memo
case_data
See TIBCO iProcess Engine (Oracle) Administrator’s Guide to see which macros are
defined for each table and index in the iProcess Engine database.
TIBCO iProcess Engine for Windows Installation
Configuring the Oracle Schema 95
|
•
the tablesizes file
The tablesizes file defines a real value for each configuration macro in the
file. The default values for the different TABLESIZE
macros are shown below:
init2Kora_tok.sql
#
# Initial size (in extents) for each
# category of table.
#
TINYTABLESIZE=1K
SMALLTABLESIZE=2K
MEDIUMTABLESIZE=40K
BIGTABLESIZE=200K
LARGETABLESIZE=500K
HUGETABLESIZE=500K
MASSIVETABLESIZE=1M
When running the installer, it:
1. copies the following files to the installing user’s temporary folder (as defined
by the %TEMP% user environment variable):
—
init2Kora_tok.sql
— the tablesizes file specified in the Select Tablesizes Profile dialog.
2. updates the init2Kora_tok.sql script to:
a. replace the configuration macros with the actual values from the
tablesizes file.
b. replace occurrences of the default data tablespace name (staffwar) with
the name specified in the Confirm Tablespace dialog.
3. runs the init2Kora_tok.sql script to create the iProcess database schema.
How to Change the Default Configuration
You can change the default configuration of the iProcess Engine schema to match
your particular requirements. Depending on the level of configuration control
you need, you can use any combination of the following methods:
TIBCO iProcess Engine for Windows Installation
96
| Appendix A
Pre-installation Tasks
•
Change the Default Data Tablespace
There are two ways in which you can change the default data tablespace to be
used:
— The installer can automatically create the default data tablespace for you,
using the name you specify in the Database Details dialog. See Database
Details Dialog on page 154 for details.
— Alternatively, you can create the default data tablespaces manually before
running the installer. You may want to do this if, for example, you want to
spread the larger iProcess tables across multiple tablespaces.
If you are using Oracle Real Application Clusters (RAC) you must create all
required tablespaces on the RAC shared storage device or devices before running
the installer. If you do not do this, the installer creates the data file or files for the
tablespace in the ORACLE_HOME\database directory.
To do this:
— Manually create a tablespace you want to use as the default data
tablespace. If you have created multiple tablespaces, simply specify the
name of one of these tablespaces.
— When running the installer, specify that you want to use this tablespace
in the Database Details dialog, then specify that all database objects should
be created in this tablespace in the Confirm Tablespace dialog. See
Database Details Dialog on page 154 for details.
•
Use an Alternative tablesizes File
When you run the installer, you can use the Select Tablesizes Profile dialog to
choose one of the following alternative tablesizes file:
—
tablesizes.med—Using this file will create a medium-sized database,
requiring at least 2.5 GB of disk space.
—
tablesizes.large—Using this file will create a large-sized database,
requiring at least 65 GB of disk space.
See Appendix D, Usage Profiles for Tablesizes Files, on page 175 for more
information about the intended usage profiles of these files.
•
Customize Specific Configuration Macros in the Tablesizes File
If you require more specific configuration control, you can edit the
tablesizes file to change the values assigned to specific configuration
macros. For example, you may want to:
TIBCO iProcess Engine for Windows Installation
Configuring the Oracle Schema 97
|
— increase the initial size of tables that use the LARGETABLESIZE macro.
— spread the larger iProcess tables across multiple tablespaces or file systems
(to aid I/O performance and reduce contention) by modifying individual
SIZETABLESPACE or SIZEINDEXSPACE entries.
Remember to create any additional tablespaces before you run the installer.
You can edit the tablesizes file when you run the installer.
•
Customize the init2Kora_tok.sql File to Assign Different Configuration Macros or
Values to Specific Tables or Indexes
Finally, you can edit the init2Kora_tok.sql file to assign different
configuration macros (or hard code specific values) to specific tables and
indexes. You can do this when you run the installer.
By default, the predict and predict_lock tables use the SMALL macro values. If
you intend to enable background case prediction on your system (using the
ENABLE_CASE_PREDICTION process attribute), TIBCO recommends that you
change these tables to use a larger value in line with the level of background
prediction activity you expect. See “Administering Process Attributes” in TIBCO
iProcess Engine Administrator’s Guide for more information.
See Also
For more information about how to estimate the size and layout requirements of
your iProcess Engine schema, consult the following sources:
•
TIBCO iProcess Engine (Oracle) Administrator’s Guide—this documentation
defines the structure of each table, and provides guidance on the number of
records a table should contain depending on the iProcess data.
•
your TIBCO representative, who can work with you to prepare a detailed
sizing and configuration estimate.
TIBCO iProcess Engine for Windows Installation
98
| Appendix A
Pre-installation Tasks
Setting Up Oracle Transparent Application Failover (TAF)
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional or Required (see below)
Upgrading from an iProcess Engine Version 11.0
or later
Optional or Required (see below)
Oracle
Oracle TAF enables an application user (such as the iProcess Engine) to
automatically reconnect to a database if the connection fails. If you are running
parallel servers, using TAF can allow the iProcess Engine to switch to an
alternative instance if the one that it is using fails. Even if you are not using
parallel servers, using TAF still means that although the iProcess Engine will not
function while the database is down, it can recover immediately and
automatically when the database is recovered.
•
TIBCO strongly recommends the use of Oracle TAF with iProcess Engine to
provide 24*7 resilient operation. If you are deploying iProcess Engine for user
acceptance testing (UAT) or to a production environment, you must enable
TAF.
For more information about how the iProcess Engine supports database
failover, see TIBCO iProcess Engine Architecture Guide.
•
You should not use TAF to protect the iProcess Engine from a scheduled
Oracle shutdown.
•
The standard Oracle client connection is not protected by TAF. Therefore, if a
failover occurs, iProcess Engine Workspace users may need to log in again.
To enable the use of TAF with the iProcess Engine, you need to configure TAF
support for the service name that you intend to use to connect to the Oracle
database.
Procedure
The procedure you use to set up TAF depends on whether you are using Oracle
RAC:
•
If you are not using Oracle RAC, you must manually configure a net service
name that includes the FAILOVER_MODE parameter included in the
CONNECT_DATA section of the connect descriptor.
TIBCO iProcess Engine for Windows Installation
Setting Up Oracle Transparent Application Failover (TAF) 99
|
You must specify at least the TYPE and METHOD sub-parameters for the
FAILOVER_MODE parameter.
•
See Also
If you are installing iProcess Engine on one of the nodes of an Oracle RAC,
you can use Oracle's Database Configuration Assistant (DBCA) to create a
new service that will use TAF. DBCA will update all the tnsnames.ora files
for the instances you choose to be in the Oracle RAC. If your iProcess Engine
is connected via an Oracle client to the Oracle RAC, you can copy the changes
that DBCA makes to the Oracle database tnsnames.ora file to the client's
tnsnames.ora file.
For more information about how to set up TAF, see the following documents in
the Oracle documentation set:
•
Oracle Net Services Administrator’s Guide
•
Oracle Clusterware and Oracle Real Application Clusters Administration and
Deployment Guide (if you are using Oracle RAC)
TIBCO iProcess Engine for Windows Installation
100
| Appendix A
Pre-installation Tasks
Configuring Oracle OPEN_CURSORS
Status
Database
Description
Procedure
See Also
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required
Upgrading from an iProcess Engine Version 11.0 or later
N/A
Oracle
The Oracle OPEN_CURSORS parameter is defined in the initialization parameter
file for the Oracle instance. It defines the limit on the maximum number of cursors
(active SQL statements) for each session on this Oracle instance.
Make sure that the Oracle
200.
OPEN_CURSORS
parameter is set to a value of at least
See the Oracle documentation for more information about the initialization
parameter file and the OPEN_CURSORS parameter.
TIBCO iProcess Engine for Windows Installation
Disabling Oracle Authentication Services 101
|
Disabling Oracle Authentication Services
Status
Database
Description
If you are...
This task ...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle
If you are installing the iProcess Engine in an Active Directory environment, you
must disable Oracle authentication services. If you do not do this, the following
error occurs when it attempts to connect to the Oracle database:
TNS-12638 Credential retrieval failed
If you are not using Active Directory you do not need to do this.
Procedure
To disable authentication services, set the following parameter in the Oracle
sqlnet.ora configuration file:
SQLNET.AUTHENTICATION_SERVICES=none
By default, the sqlnet.ora file is located in the ORACLE_HOME\network\admin
directory, or in the directory specified by the TNS_ADMIN environment variable.
TIBCO iProcess Engine for Windows Installation
102
| Appendix A
Pre-installation Tasks
Configuring Oracle Character Set Support
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle
Oracle’s NLS_LANG parameter sets the language, territory, and character set that
the iProcess Engine uses to communicate with the Oracle database. The iProcess
Engine requires that NLS_LANG uses an 8-bit character set.
NLS_LANG
is defined in the following Windows registry subkey:
Oracle
Version
Key
Oracle 11g
RegistryLocation\ORACLE\KEY_ORAHOME
where ORAHOME is the Oracle home name.
where RegistryLocation is either \HKEY_LOCAL_MACHINE\Software, if you are
running the iProcess Engine on a 32-bit machine, or
\HKEY_LOCAL_MACHINE\Software\Wow6432Node, if you are using a 64-bit
machine.
You can also set NLS_LANG as a System or User environment variable (using
System in the Control Panel window). However, if you do this the environment
variable setting is used for ALL Oracle homes and takes precedence over any
parameters set in the Windows registry.
Oracle recommends that you use the Windows registry to set NLS_LANG unless
you have a specific requirement to use an environment variable.
Node Cluster
NLS_LANG
must be set to the same value on the master server and on each slave
server.
Procedure
To set NLS_LANG, complete the following steps:
1. Set the NLS_LANG value to use an 8-bit character set component (charset).
TIBCO iProcess Engine for Windows Installation
Configuring Oracle Character Set Support 103
|
2. If you are using a TNS connection, make sure that the character set component
(charset) of the NLS_LANG value for the Oracle client matches the character
set component of the NLS_LANG setting on the Oracle database.
The format of the NLS_LANG string is:
NLS_LANG =
language_territory.charset
Example
NLS_LANG=American_America.WE8ISO8859P1
See Also
For more information about using NLS_LANG, see Oracle Database Globalization
Support Guide.
TIBCO iProcess Engine for Windows Installation
104
| Appendix A
Pre-installation Tasks
Disabling Oracle Flashback Query
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
N/A
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle
Oracle has a flashback query feature, which lets you view and repair historical data.
(The initialization parameter, UNDO_RETENTION, provides a means of explicitly
specifying the amount of UNDO information to retain.)
If flashback query is enabled, the amount of UNDO tablespace required while
you are upgrading (see Creating an Oracle UNDO Tablespace on page 105 for
details) will increase significantly. You may therefore want to disable this feature
while you are upgrading the iProcess Engine or Process Engine.
However, this may not be possible if there are other applications that use the same
database and that may require a flashback query while the upgrade is taking
place. If that is the case, you must leave the feature enabled and make sure you
have sufficient UNDO tablespace available.
Procedure
•
It is possible for UNDO to reach 100%, as the flashback query UNDO will still
be allocated. This will make it difficult to monitor the UNDO tablespace.
•
If UNDO is set to autoextend, it may grow extremely large, as all UNDO
transactions for the entire upgrade will be stored.
To disable flashback query, use the Oracle command:
alter system set UNDO_RETENTION=0
See Also
See your Oracle documentation for more information about flashback query.
TIBCO iProcess Engine for Windows Installation
Creating an Oracle UNDO Tablespace 105
|
Creating an Oracle UNDO Tablespace
Status
Database
Description
Procedure
See Also
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required
Upgrading from an iProcess Engine Version 11.0 or later
Required
Oracle
Oracle uses UNDO tablespaces to rollback transactions. Previous versions of Oracle
used rollback segments.
Create an Oracle UNDO tablespace for the iProcess Engine database.
See:
•
your Oracle documentation, for more information on how to create and
manage UNDO tablespaces.
•
Disabling Oracle Flashback Query on page 104 for more information about
Oracle’s flashback query feature and its impact on the amount of UNDO
tablespace you require.
TIBCO iProcess Engine for Windows Installation
106
| Appendix A
Pre-installation Tasks
Creating the SQL Server Database and Logins
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
N/A
SQL Server
The iProcess Engine stores its data in a SQL Server database, and requires two
SQL Server logins to access this database:
•
iPE DB Owner—owns the iProcess Engine database
•
iPE DB User—used for read access to the iProcess Engine database
The installer can automatically create the iProcess Engine database and these
logins for you, but only if you know the system administrator SQL login name
(default sa) and password for the SQL Server instance that you want to use. See
SQL/ODBC Details Dialog on page 151 for details.
If you do not know the system administrator SQL login name and password,
the installer cannot do this. In this case, you must use the following procedure to
manually create the SQL Server database and logins before you run the installer.
Depending on the authentication method used by the SQL Server instance
(Windows or SQL Server), you must use a Windows account or SQL Server login
that has been assigned the System Administrators server role. If you do not
have access to such an account or login, contact your SQL Server database
administrator for assistance.
TIBCO iProcess Engine for Windows Installation
Creating the SQL Server Database and Logins 107
|
Procedure
To manually create the iProcess Engine database and SQL Server logins, complete
the following steps:
1. Start SQL Server Management Studio.
You must install SQL Tools to get the SQL Server Management Studio utility.
2. If necessary, connect to or register the server where you intend to create the
iProcess Engine database.
3. Right-click the server you want to use, then select Properties from the pop-up
menu.
4. Set the value of the Maximum number of concurrent connections field on the
Connections page for this server.
Set this value to either 0 (unlimited), or a value that is equal to or greater than
the following calculation:
9
+ wiscount + bgcount + ((users/maxusers_per_process) x maxpoolsize)
where:
—
9 is the number of connections to the database required by iProcess Engine
server processes. This number is fixed.
— wiscount is the number of Work Item Server (WIS) processes configured for
this iProcess Engine. The default is 2.
— bgcount is the number of background (BG) processes configured for this
iProcess Engine. The default is 4.
— users is the maximum number of TIBCO iProcess Workspace (Windows)
users expected to concurrently use the iProcess Engine database.
— max_users_per_process is the maximum number of iProcess Engine users per
RPC pool server process (RPC_POOL). The default value is 20. You can
reduce this value by changing the MAX_USERS_PER_PROCESS parameter in
the STAFF section of the SWDIR\etc\staffcfg file.
Changing the MAX_USERS_PER_PROCESS parameter may increase the number of
RPC processes, and therefore impact performance.
— maxpoolsize is the maximum number of database connections a single RPC
pool server process will create, if required. This value is defined by the
MAXPOOLSIZE parameter in the BPOOL section of the SWDIR\etc\staffcfg
file. The default value is 10. In the calculation above maxpoolsize is used to
represent the maximum possible number of connections. Under normal
TIBCO iProcess Engine for Windows Installation
108
| Appendix A
Pre-installation Tasks
runtime conditions, the number of connections per server is unlikely to
exceed 2 or 3.
5. Click the OK button.
6. Create a new database on this SQL server to hold iProcess Engine data. To do
this:
a. Right-click Databases, then select New Database.
b. Enter a name for the iProcess Engine database on the General tab.
c. Enter a suitable Initial
size (MB)
value on the General page.
TIBCO recommends a minimum database size of 20Mb.
Certain iProcess operations (for example, purging cases and restores) may
generate large numbers of database transactions. You should configure the
SQL Server and iProcess Engine database so that it has sufficient resources
to handle the expected transaction load. For more information about how
to estimate the size and layout requirements of your iProcess Engine
database, consult the following sources:
•
TIBCO iProcess Engine (SQL Server) Administrator’s Guide. this
documentation defines the structure of each table, and provides
guidance on the number of records a table should contain depending
on the iProcess data.
•
Your TIBCO representative, who can work with you to prepare a
detailed sizing and configuration estimate.
d. Make sure that the Autogrowth checkbox for the data and log files on the
General tab has been checked.
If these options are not selected and the SQL Server runs out of resource when
trying to process an iProcess Engine operation, iProcess Engine will fail and a
SWDIR\logs\sw_error file will be created.
e. Click the OK button.
7. Right-click the iProcess Engine database, then select Properties from the
pop-up menu.
8. On the Options tab, Select the database Recovery Model (Simple, Full, or
Bulk-Logged) that is most appropriate for your database backup/recovery
environment.
9. Click the OK button.
TIBCO iProcess Engine for Windows Installation
Creating the SQL Server Database and Logins 109
|
10. Create the IPE DB Owner and IPE DB User SQL Server login IDs. To do this
(for each login):
a. Expand Security, right-click Logins, then click New Login.
b. Enter a Name for the login. You can use any name you want to, but the
suggested ones are swpro for the IPE DB Owner and swuser for the
IPE DB User.
c. Click the User Mapping tab.
d. In the list of databases, select the iProcess Engine database that you just
created, then check the Map checkbox to allow this login to access the
database.
e. In the Database roles section, check the db_owner checkbox for the IPE DB
Owner login, or the db_datareader checkbox for the IPE DB User login.
f.
Click the OK button.
11. Right-click the iProcess Engine database, then select Properties from the
pop-up menu.
12. Click the Permissions tab. Make sure that the IPE DB Owner and IPE DB User
logins are listed. Check the Grant checkbox for each permission listed against
each login.
13. Click the OK button.
14. Create a default schema for the IPE DB Owner and IPE DB User. To do this
(for each login):
a. Expand the iProcess Engine database, expand Security, right-click Schema
then select New Schema.
b. Enter the login ID as the Schema
owner
and as the Schema
name.
c. Click the OK button.
15. Ensure that the SQL Server collation setting specifies the correct character set
for TIBCO iProcess Engine.
If both TIBCO iProcess Engine and SQL Server have been installed on a native
operating system and you plan to run TIBCO iProcess Engine on the native
operating system, you will not have to change the collation settings.
For more information about collation settings, see SQL Server Database Engine
Guide.
TIBCO iProcess Engine for Windows Installation
110
| Appendix A
Pre-installation Tasks
Creating the ODBC Data Source
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine
Optional
Upgrading from any Version i9, i10, 10, or 11 iProcess Engine
N/A
SQL Server
TIBCO iProcess Engine uses an ODBC data source to connect to the SQL Server.
The installer can automatically create an ODBC data source for you. However,
you can use the following procedure to manually create it before you run
setup.exe.
If you are installing the iProcess Engine into a Microsoft Windows Cluster, the
mscluster command automatically creates an ODBC data source with the same
name and details on each secondary machine in the cluster.
Procedure
To manually create an ODBC data source, complete the following steps:
1. Perform one of the following operations to open the ODBC Data Source
Administrator dialog on Windows:
— On the 64-bit Windows platform, run the following utility:
\windows\syswow64\odbcad32.exe
You must use this utility to create an ODBC data source because the
iProcess Engine installer is a 32-bit application. If you do not do so, the
ODBC data source will not appear in the SQL/ODBC Details dialog. For
detailed configuration information in the SQL/ODBC Details dialog, see
SQL/ODBC Details Dialog on page 151.
— On the 32-bit Windows platform, double-click the Administrative Tools
icon in the Control Panel window, then double-click the Data Sources
(ODBC) item.
2. Click the Add button under the System DSN tab. The Create New Data Source
dialog appears.
TIBCO iProcess Engine for Windows Installation
Creating the ODBC Data Source 111
|
3. Select SQL Native Client as the driver for which you want to set up a data
source.
If SQL Native Client is not shown in the list of available drivers, you will need
to download it from the Microsoft Download Center at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=DF0BA5AA
-B4BD-4705-AA0A-B477BA72A9CB&DisplayLang=en
4. Click the Finish button. The Create A New Data Source To SQL Server wizard
appears.
5. Specify the information listed in the Create A New Data Source To SQL Server
wizard to complete the operation. For detailed information about the Create a
New Data Source to SQL Server wizard, see Microsoft documentation.
The layout of this wizard depends on the version of the SQL Server driver
installed on the computer. The required information may be on different pages.
TIBCO iProcess Engine for Windows Installation
112
| Appendix A
Pre-installation Tasks
Removing All User-defined Constraints (or Triggers), Indexes, and
Statistics From the iProcess Engine Schema Tables
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
N/A
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
For an existing iProcess Engine, you have created constraints (or triggers),
indexes, and statistics in the iProcess Engine schema tables. As part of an
upgrade, the installer needs to modify certain columns in the iProcess Engine
schema tables, then recreate constraints (or triggers), indexes, and statistics after
the necessary columns has been changed in the upgrade process.
To successfully upgrade an existing iProcess Engine, you need to remove any
user-defined constraints (or triggers), indexes, and statistics from the iProcess
Engine schema tables manually before running the upgrade installer. The installer
cannot automatically remove them.
Procedure
Using an appropriate SQL utility, remove all user-defined constraints (or
triggers), indexes, or statistics that you have added to iProcess Engine schema
tables.
You can manually recreate them after completing the upgrade. See Recreating All
User-defined Constraints (Or Triggers), Indexes and Statistics on the iProcess
Engine Schema Tables on page 135 for more information.
TIBCO iProcess Engine for Windows Installation
Configuring the Microsoft Windows Cluster 113
|
Configuring the Microsoft Windows Cluster
Status
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required if you use a
Windows Cluster
Upgrading from an iProcess Engine Version 11.0 or later
Required if you use a
Windows Cluster
If you are installing iProcess Engine into a Microsoft Windows Cluster, you must
perform some preliminary tasks to enable iProcess Engine to operate in the
Microsoft Windows Cluster environment.
Microsoft Windows Clustering is not supported on Windows XP.
Procedure
Perform the following steps:
1. If you are upgrading an iProcess Engine that is part of a Windows cluster, run
the following command on each secondary machine in the cluster:
SWDIR\mscluster\mscluster -r
Do not run this command on the machine where the iProcess Engine is installed. If you
do you will not be able to start or upgrade the iProcess Engine.
This command removes the iProcess Engine shared resources and services,
and the port numbers used by the iProcess Engine watcher and worker
process sentinels in the %systemroot%\system32\drivers\etc\services file.
You will need to create the shared resources and services used by the
upgraded iProcess Engine after you have run the installer.
2. Enable network DTC access on the cluster. If network DTC access is not
enabled, database transactions are limited to the local server.
For more information about how to enable network DTC access, see article
817064 in Microsoft’s Knowledge Base at http://support.microsoft.com.
3. Using Cluster Administrator, install a Distributed Transaction Coordinator
resource. If this resource is not available, the installer will not be able to add
TIBCO iProcess Engine for Windows Installation
114
| Appendix A
Pre-installation Tasks
the iProcess Events and (optional) iProcess COM+ Bridge COM+ applications
to Component Services during installation.
For more information about how to do this, see “Installing a Distributed
Transaction Coordinator resource” in the Microsoft Cluster Administrator
Help.
See Also
See Microsoft documentation for more information about the Cluster
Administrator tool.
TIBCO iProcess Engine for Windows Installation
| 115
Appendix B
Post-installation Tasks
This appendix lists the post-installation tasks.
Topics
•
Re-implementing Changes to Upgraded Configuration Files, page 117
•
Configuring Firewall Port Ranges on Slave Servers, page 118
•
Configuring TIBCO iProcess Objects Server and TIBCO iProcess Objects
Director, page 119
•
Enabling COM+ Network Access, page 121
•
Configuring the Microsoft Windows Cluster, page 122
•
Enabling Oracle Function-based Indexes, page 126
•
Installing the IBM Client for JMS on J2SE with IBM WebSphere Application
Server, page 127
•
Configuring IAPJMS Security Settings, page 129
•
Configuring the Default iProcess Engine Installer, page 130
•
Recreating Prediction Data, page 131
•
Configuring Access to SSOLite Stored Procedures for TIBCO iProcess
Plug-ins, page 132
•
Granting Permissions on Stored Procedures in EAI Database Steps, page 134
•
Recreating All User-defined Constraints (Or Triggers), Indexes and Statistics
on the iProcess Engine Schema Tables, page 135
•
Updating the Domain Group Policy for the Log On As A Service Right,
page 136
•
Enabling OLE Automation on SQL Server, page 137
•
Disabling or Re-enabling Write Access to WebDav, page 138
•
Configuring JMX Ports to Run Through a Firewall, page 139
•
Setting Up iProcess Engine with an IPv6 Address, page 140
TIBCO iProcess Engine for Windows Installation
116
| Appendix B
Post-installation Tasks
•
Starting TIBCO iProcess Engine, page 142
TIBCO iProcess Engine for Windows Installation
Re-implementing Changes to Upgraded Configuration Files 117
|
Re-implementing Changes to Upgraded Configuration Files
Status
Database
Description
See Also
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
N/A
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
If you made any changes to the default values in the following files on your
original system, you should now manually re-implement any of those changes
that you want to keep in the upgraded files:
•
SWDIR\etc\language.lng\staffico
•
SWDIR\etc\language.lng\auditusr.mes
For more information about the default contents of these files, and how to edit
them, see the following:
For Information About
See
SWDIR\etc\language.lng\staffico
Using iProcess Engine Configuration
Files in TIBCO iProcess Engine
Administrator’s Guide
SWDIR\etc\language.lng\auditusr.mes
Defining Audit Trail Entries in TIBCO
iProcess swutil and swbatch Reference
Guide.
TIBCO iProcess Engine for Windows Installation
118
| Appendix B
Post-installation Tasks
Configuring Firewall Port Ranges on Slave Servers
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required
Upgrading from an iProcess Engine Version 11.0 or later
Required
Oracle, SQL Server
Onward firewall port range configuration data in TIBCO iProcess Engine Version
11.5.0 is stored in the port_range database tables, and can be configured by using
the SWDIR\util\swadm utility.
If you are installing or upgrading an iProcess Engine as:
Procedure
•
a slave server in a Node Cluster, you must now manually configure any
required firewall port range data.
•
a master server or single server, you do not need to do anything. The installer
automatically creates the necessary port range configuration data in this case,
either using default values (for a new installation), or using the existing values
for an upgrade.
If you are either:
•
installing a new slave server, or
•
upgrading an existing slave server,
you should use the swadm utility to create the necessary port range configuration
data for your firewall configuration.
See Also
See Chapter 9, Administering Firewall Port Ranges in TIBCO iProcess Engine
Administrator’s Guide for more information about using the iProcess Engine with a
firewall, and how to use the SWDIR\util\swadm utility to configure firewall port
ranges.
TIBCO iProcess Engine for Windows Installation
Configuring TIBCO iProcess Objects Server and TIBCO iProcess Objects Director 119
|
Configuring TIBCO iProcess Objects Server and TIBCO iProcess
Objects Director
Status
Database
Description
Node Cluster
Procedure
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
If you chose to enable the iProcess Objects Server and/or iProcess Objects
Director during the installation process (see Select Components To Configure
Dialog on page 158), you can now configure them according to your requirements
before starting iProcess Engine.
The iProcess Objects Server and/or iProcess Objects Director must communicate
using the same Client-Server RPC port number (see Configuration Dialog on
page 161) used by the node on which the iProcess Engine foreground processes
(WIS, WQS, and so on) are running. If they do not match, errors will be written to
the iProcess Objects Server and/or iProcess Objects Director log file on startup.
To configure iProcess Objects Server, run the iProcess Objects Server
Configuration Utility. To start this utility, select Start > Settings > Control Panel >
TIBCO iProcess Objects Server.
You do not need to run this utility again if you choose to run iProcess Objects
as part of the installation process, see Select
Components To Configure Dialog on page 158 for details.
Server Configuration Utility
For more information about this utility, and how to use it, see Configuring the
TIBCO iProcess Objects Server in TIBCO iProcess Objects Server Administrator’s
Guide.
To configure iProcess Objects Director, set the iProcess Engine process attributes
that control the iProcess Objects Director to your required values.
For more information about these attributes and their possible values, see
“Configuring the TIBCO iProcess Objects Director“ in the TIBCO iProcess Objects
Director Administrator’s Guide.
TIBCO iProcess Engine for Windows Installation
120
| Appendix B
Post-installation Tasks
If the iProcess Objects Server or iProcess Objects Director is installed on a master
or slave server (in a node cluster) that is not running any iProcess Engine
foreground processes (WIS, WQS, and so on):
1. Determine the client or server RPC port being used by the node on which the
foreground processes are running by looking at line 11 of the SWDIR\swdefs
file on that node’s machine.
2. Compare the client or server RPC port specified in the SWDIR\swdefs file of
the machine on which you are installing the iProcess Objects Server and
iProcess Objects Director with the port number you determined in the
previous step. If the RPC numbers match, no further action is required. If they
do not match:
a. Change the client or server RPC port specified in the SWDIR\swdefs file of
the machine on which you are performing the installation so it is the same
as on the machine running the foreground processes.
b. Change the RPC number in the following registry location on the machine
on which you are installing so it matches the number in the
SWDIR\swdefs file:
RegistryLocation\Staffware plc\Staffware
Server\Nodes\MyNode\RPC_CLTSRV
where RegistryLocation is either \HKEY_LOCAL_MACHINE\Software, if you are
running iProcess Engine on a 32-bit machine, or
\HKEY_LOCAL_MACHINE\Software\Wow6432Node, if you are using a 64-bit
machine.
TIBCO iProcess Engine for Windows Installation
Enabling COM+ Network Access 121
|
Enabling COM+ Network Access
Status
Database
Description
Procedure
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
COM+ network access is disabled by default when you install the iProcess
Engine. You must enable it in either of the following circumstances:
•
the iProcess Engine is installed on Windows Server 2003 and uses the node
cluster architecture (see Windows Clustering on page 12). You must enable
COM+ network access on the master server and on each slave server.
•
the iProcess Engine is installed on a Microsoft Windows Cluster. You must
enable COM+ network access on each machine in the cluster.
To enable COM+ network access:
1. Open the Control Panel window and click Add or Remove Programs.
2. Click the Add/Remove Windows Components button. The Windows
Components Wizard is displayed.
3. Select Application Server and click Details.
4. Check the Enable network COM+ access checkbox.
5. Click the OK button.
6. Click the Next button to complete the Windows Components Wizard.
7. Click the Finish button to close the wizard.
TIBCO iProcess Engine for Windows Installation
122
| Appendix B
Post-installation Tasks
Configuring the Microsoft Windows Cluster
Status
Database
Description
Procedure
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required if you use a
Windows Cluster
Upgrading from an iProcess Engine Version 11.0 or later
Required if you use a
Windows Cluster
Oracle, SQL Server
If you are installing the iProcess Engine into a Microsoft Windows Cluster, you
must perform some additional tasks to enable the iProcess Engine to operate in
the Microsoft Windows Cluster environment.
Perform the following steps:
1. If you did not check the Auto Start Processes On Service Startup checkbox
when you ran the installer (see Configuration Dialog on page 161), set the
iProcess Engine PM_AUTO_BOOT process attribute value to 1 (so that iProcess
Engine processes automatically start after the Process Sentinels have started).
2. If you did not check the Use Cluster Network Name checkbox when you ran
the installer (see Select Components To Configure Dialog on page 158),
configure the iProcess Engine to use a virtual server in a Microsoft Windows
cluster. To do this:
a. Use the SWDIR\util\swadm SHOW_SERVERS command to determine the
machine ID of the physical server where the iProcess Engine is currently
installed (as stored in the node_cluster table). For example:
C:\swserver\staffw_nod1\util>swadm show_servers
----------------------------------------------------------------------------Machine ID
Machine Name
Master
Check Error Files
Machine Comment
-----------------------------------------------------------------------------
1
PCANUSER00355
TIBCO iProcess Engine for Windows Installation
Y
Y
PCANUSER00355
Configuring the Microsoft Windows Cluster 123
|
where:
— MachineID is the ID of the physical server where the iProcess Engine is
currently installed.
— Machine Name is the name of the Microsoft Distributed Transaction
Coordinator resource (MSDTC). See "What is MSDTC" in TIBCO
iProcess Engine Architecture Guide for more information.
3. If you are using EMS, you must now:
a. install the same EMS Version on each secondary machine in the cluster. See
TIBCO Enterprise Message Service Installation for more information about
how to install EMS.
b. configure EMS to work as part of the cluster. For more information about
how to do this, see EMS documentation.
If you are upgrading your version of TIBCO EMS, you must follow the
instructions in How Do I Upgrade TIBCO EMS on page 184. Failure to do
so will result in the loss of work queue data.
4. If you are using Hawk, you must now:
a. install the same Hawk Version on each secondary machine in the cluster.
You can find the Hawk Version distribution set and documentation in the
SWDIR\hawk folder. See TIBCO Hawk Installation and Configuration for
more information about how to install Hawk.
b. configure Hawk to work as part of the cluster. For more information about
how to do this, see Hawk documentation.
5. If your Microsoft Windows Cluster is not running software to ensure that
services, components, and shared DLLs are replicated between machines, and
therefore identical between the machines in the cluster, run the following
command on each secondary machine in the cluster:
SWDIR\mscluster\mscluster
TIBCO iProcess Engine for Windows Installation
124
| Appendix B
Post-installation Tasks
This command creates the following shared resources and services that are
required by iProcess Engine:
—
iProcess
nodeName Process Sentinels service
—
iProcess
nodeName Web Server service
—
NobleNet Portmapper for TCP
—
iProcess Events
—
iProcess COM+ Bridge
service
COM+ application
COM+ application
where nodeName is the node name of this iProcess Engine.
It also replicates the port numbers used by the iProcess Engine watcher and
worker process sentinels in the
%systemroot%\system32\drivers\etc\services file.
6. Open the Control Panel window, and select Administrative Tools > Cluster
Administrator.
7. Install a new Generic Service resource for the iProcess Engine NobleNet
Portmapper service. This resource must have the following properties:
Property
Description
Resource name
Any suitable descriptive name you choose.
Service name
NobleNet Portmapper for TCP
For more information about how to install this resource, see “Installing a
Generic Service Resource” in the Microsoft Cluster Administrator help.
TIBCO iProcess Engine for Windows Installation
Configuring the Microsoft Windows Cluster 125
|
8. Install a new Generic Service resource for the iProcess Engine Process
Sentinels service. This resource must have the following properties:
Property
Description
Resource name
Any suitable descriptive name you choose.
Dependencies
The NobleNet Portmapper resource you created in the
previous step.
Service name
iProcessnodeNameProcessSentinels
where nodeName is the node name of this iProcess Engine.
There must be no spaces anywhere in the name or at the
end of the string.
Registry Replication
> Root Registry Key
Add both of the following entries:
•
RegistryLocation\Staffware plc\Staffware
Server\Nodes\nodeName
•
RegistryLocation\Staffware plc\iProcess
EntObj Server\Nodes\nodeName
where:
RegistryLocation is either SOFTWARE, if you are running
iProcess Engine on a 32-bit machine, or
SOFTWARE\Wow6432Node, if you are using a 64-bit
machine.
nodeName is the node name of this iProcess Engine.
See Also
See Microsoft documentation for more information about the Cluster
Administrator tool.
TIBCO iProcess Engine for Windows Installation
126
| Appendix B
Post-installation Tasks
Enabling Oracle Function-based Indexes
Status
Database
Description
Procedure
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required
Upgrading from an iProcess Engine Version 11.0 or later
N/A
Oracle
The case_information table contains an Oracle function-based index,
idx_ci_casedesc_UC, which allows iProcess Engine to perform
non-case-sensitive searches on the table.
To enable the use of the idx_ci_casedesc_UC index in Oracle, you must:
1. Set the following Oracle initialization parameters:
QUERY_REWRITE_INTEGRITY=TRUSTED;
QUERY_REWRITE_ENABLED=TRUE;
2. Ensure that the following SQL command is run at regular intervals (for
example, as a scheduled job in the database or as part of your maintenance
activities).
analyze table case_information compute statistics;
On systems with large amounts of data, this command can take a long time to
complete. TIBCO recommends that you run the command when there are not
many users logged in, for example, overnight.
This command computes the necessary statistics on the case_information
table which the Oracle query optimizer uses to perform Cost-Based
Optimization (CBO). If there is no cost-based information, or if CBO is
disabled, searches involving the case_information table will require a full
table scan, which can take a long time to complete.
See Also
See Oracle documentation for more information about function-based indexes
and CBO.
TIBCO iProcess Engine for Windows Installation
Installing the IBM Client for JMS on J2SE with IBM WebSphere Application Server 127
|
Installing the IBM Client for JMS on J2SE with IBM WebSphere
Application Server
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Required if you use
Websphere 6.x
Upgrading from an iProcess Engine Version 11.0 or later
Required if you use
Websphere 6.x
Oracle, SQL Server
If you intend to use Websphere 6.x as your JMS provider for Activity Publication,
and you do not already have the IBM Client for JMS on J2SE with WebSphere
Application Server installed on your system, you must install it now.
You must install the IBM JMS Client into the directory you specified for it when
you ran the installer, see Default Java Message Service Dialog on page 170 for
details.
The IBM JMS Client is an embeddable technology that provides JMS V1.1
connections to a service integration bus messaging engine in WebSphere
Application Server V6.0.2 (or above). It is available from the following IBM URL:
http://www-1.ibm.com/support/docview.wss?uid=swg24012804
Procedure
To do this:
1. Download the IBM JMS Client download file (sibc_install-build.jar) from
the above URL.
2. Use the following command to install the IBM JMS Client:
java –jar sibc_install-build.jar jms_jndi_sun
directory
where:
—
jms_jndi_sun is the installation option for JMS + JNDI for Sun JREs. You
must use this installation option to ensure that the IBM JMS Client uses a
Sun JRE, which it must do to work with iProcess Engine IAPJMS process.
TIBCO iProcess Engine for Windows Installation
128
| Appendix B
Post-installation Tasks
— directory is the same pathname that you entered in the Base field of the
Default Java Message Service dialog (see Default Java Message Service
Dialog on page 170). You must install to this directory because that is where
the iProcess Engine will look for the client JAR files.
TIBCO iProcess Engine for Windows Installation
Configuring IAPJMS Security Settings 129
|
Configuring IAPJMS Security Settings
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
If you chose to enable Activity Publication when you run the installer (see Select
Components To Configure Dialog on page 158), default values for the JNDI/JMS
username and password are written to the SecurityPrinciple and
SecurityCredentials properties (respectively) in the
SWDIR\etc\iapjms.properties file. This file contains all the configuration
information for the IAPJMS library.
If you want to change these values for security reasons, you should do so now.
Enabling activity publishing does not result in events being automatically
published by the iProcess Engine. See Select Components To Configure Dialog on
page 158 for more information.
See Also
For more information about how to change the default values for the JNDI/JMS
username and password, see “Updating the IAP Security Principle and
Credentials” in TIBCO iProcess Engine Administrator’s Guide.
TIBCO iProcess Engine for Windows Installation
130
| Appendix B
Post-installation Tasks
Configuring the Default iProcess Engine Installer
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
The installer creates a default set of server processes, process attributes, message
queues, and Mbox sets for the iProcess Engine. You can, if you wish, change this
default installer to suit your particular requirements.
Node Cluster
The default processes are all set up on the master server. When a slave server is
added, no processes are initially configured to run on it.
Procedure
Use the SWDIR\util\swsvrmgr or SWDIR\util\swadm utility to set up server
processes, process attributes, message queues, and Mbox sets according to your
requirements.
See Also
See the following in TIBCO iProcess Engine Administrator's Guide for more
information.
For Information About
Configuring
See This Chapter
processes
Administering iProcess Engine Server Processes
process attributes
Administering Process Attributes
message queues and Mbox sets
Administering Message Queues and Mbox Sets
TIBCO iProcess Engine for Windows Installation
Recreating Prediction Data 131
|
Recreating Prediction Data
Status
Database
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
N/A
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
Description
During the upgrade process the predict and predict_lock tables are dropped
and then recreated. Accordingly, any prediction data contained in those tables is
lost.
Procedure
You can recreate the data in these tables (for any procedures that you want to) by
using the following command:
SWDIR\bin\swutil PREDICT procname ALL_CASES
where procname is the name of the procedure that you want to recreate prediction
data for.
See Also
For more information about:
•
case prediction, see Using Case Prediction to Forecast Outstanding Work
Items in TIBCO iProcess Modeler Advanced Design.
•
the swutil PREDICT command, see Updating Prediction for Cases in TIBCO
iProcess swutil and swbatch Reference.
TIBCO iProcess Engine for Windows Installation
132
| Appendix B
Post-installation Tasks
Configuring Access to SSOLite Stored Procedures for TIBCO
iProcess Plug-ins
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
SSOLite is a set of stored procedures, available in the iProcess Engine database,
that provide applications with direct access to a limited subset of iProcess Engine
functionality.
The following TIBCO iProcess Plug-ins require access to the SSOLite stored
procedures:
•
TIBCO iProcess Web Services Plug-in
•
TIBCO iProcess Java Plug-in
•
TIBCO iProcess BusinessWorks Connector
If you want to use any of these plug-ins with SQL Server 2005, you must assign
the SQL Server System Administrators server role to the IPE DB Owner SQL
Server login ID. If you do not do this, these plug-ins will not be able to access the
SSOLite stored procedures and so will not function.
If you want to use any of these plug-ins with SQL Server 2008, you do not need to
assign the SQL Server System Administrators server role to the IPE DB Owner
SQL Server login ID.
Procedure
To assign the SQL Server System
SQL Server login ID:
Administrators
server role to the IPE
DB
Owner
1. Start SQL Server Management Studio.
You must install SQL Tools to get the SQL Server Management Studio utility.
2. Expand Security and click Logins.
3. Right-click the IPE DB Owner SQL Server login ID, see Database Details
Dialog on page 154, then select Properties from the pop-up menu.
TIBCO iProcess Engine for Windows Installation
Configuring Access to SSOLite Stored Procedures for TIBCO iProcess Plug-ins 133
|
4. Click the Server Roles tab.
5. Select System Administrators, then click the OK button.
See Also
For more information about SSOLite stored procedures, see TIBCO iProcess Engine
(SQL Server) Administrator’s Guide.
TIBCO iProcess Engine for Windows Installation
134
| Appendix B
Post-installation Tasks
Granting Permissions on Stored Procedures in EAI Database Steps
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
The EAI steps are used to communicate with database stored procedures. You
must grant execute permission to swuser on all custom stored procedures used
by EAI Database steps if you are using TIBCO iProcess Engine version 11.4.0 or
later.
If you are using TIBCO iProcess Engine earlier version than 11.4.0, the foreground
processes connect to the database using the Oracle foreground user (swuser),
whereas the Oracle background user (swpro), is used for the background
processes. For example, the WIS processes connect to the Oracle database as the
swuser user whereas the BG processes connected to the Oracle database as the
swpro user.
If you are using TIBCO iProcess Engine version 11.4.0 or later, all the processes,
regardless of whether they are background or foreground processes, connect to
the Oracle database as the Oracle foreground user, which by default is the swuser
user.
Procedure
See related database documentation on how to grant execute permission.
TIBCO iProcess Engine for Windows Installation
Recreating All User-defined Constraints (Or Triggers), Indexes and Statistics on the iProcess Engine Schema Tables 135
|
Recreating All User-defined Constraints (Or Triggers), Indexes and
Statistics on the iProcess Engine Schema Tables
Status
Database
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
N/A
Upgrading from an iProcess Engine 11.1 or later
Possibly required
Oracle, SQL Server
Description
After the upgrade has finished you need to recreate any user-defined constraints
(or triggers), indexes, or statistics that you deleted before upgrading the iProcess
Engine. See Removing All User-defined Constraints (or Triggers), Indexes, and
Statistics From the iProcess Engine Schema Tables on page 112 for more
information.
Procedure
Using an appropriate SQL utility, recreate all user-defined constraints (or
triggers), indexes, or statistics on iProcess Engine schema tables that you deleted
before you upgraded.
TIBCO iProcess Engine for Windows Installation
136
| Appendix B
Post-installation Tasks
Updating the Domain Group Policy for the Log On As A Service
Right
Status
Database
Description
If You Are
This task
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
When you install iProcess Engine, the installer assigns the Log on as a service
right to the user account you have chosen to use to run the iProcess nodeName
Process Sentinels service (the IPESERVICE user). The right is assigned on the
computer where you have installed the iProcess Engine.
If you have installed the iProcess Engine in a domain, using domain users, and the
domain uses a group policy for the Log on as a service right, you must now
also update that group policy to include the IPESERVICE user.
If you do not do this, the IPESERVICE user’s locally-assigned right will be
overwritten when the domain controller propagates the group policy to the
member machines in the domain (which happens, by default, every 90 minutes).
The account will therefore lose the Log on as a service right, and so be unable
to start the iProcess nodeName Process Sentinels service.
Procedure
Change the group policy on the domain controller for the Log
right to include the IPESERVICE user.
You must have access to an account that has Domain
be able to change the group policy.
See Also
on as a service
Administrator privileges to
There are a number of ways to change group policies, depending on how the
domain is configured. See your Microsoft documentation for more information
about group policies and how to change them.
TIBCO iProcess Engine for Windows Installation
Enabling OLE Automation on SQL Server 137
|
Enabling OLE Automation on SQL Server
Status
Database
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
SQL Server
Description
The OLE Automation option on SQL Server is disabled by default on SQL Server
2005 Service Pack2 or later. You must enable it before calling the SSOLite stored
procedure from any client, such as SQL session, Java JDBC code, TIBCO
BusinessWorks iProcess Plug-in, and so on.
Procedure:
This post-installation task needs to be performed only if:
•
you are installing or upgrading the TIBCO iProcess Engine, and
•
you are using SQL Server 2005 with Service Pack 3.
To enable the OLE Automation option with the SQL Server Surface Area
Configuration utility on SQL Server 2005 with Service Pack 3, perform the
following steps:
1. Stop iProcess Engine.
2. Select Programs > Microsoft SQL Server > Surface Area Configuration from
the Start menu.
3. Select Surface Area Configuration For Features.
4. Select OLE Automation, and check the Enable OLE Automation checkbox.
5. Press the OK button.
6. Restart SQL Server and iProcess Engine.
TIBCO iProcess Engine for Windows Installation
138
| Appendix B
Post-installation Tasks
Disabling or Re-enabling Write Access to WebDav
Status
Database
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
Description
You may find, once you have installed or upgraded the iProcess Engine, that you
want to disable or re-enable write access to WebDav on the Apache Tomcat
Application Server installed with the iProcess Engine. To do this, you must edit
the SWDIR\tomcat\webdav\WEB-INF\web.xml file.
Procedure
To disable or re-enable write access to WebDav on the Apache Tomcat Application
Server installed with the iProcess Engine, do the following:
1. In a text editor, open the SWDIR\tomcat\webdav\WEB-INF\web.xml file.
2. Depending on your requirements, either uncomment or comment out the
following section:
<init-param>
<param-name>readonly</param-name>
<param-value>false</param-value>
</init-param>
3. Save the file.
TIBCO iProcess Engine for Windows Installation
Configuring JMX Ports to Run Through a Firewall 139
|
Configuring JMX Ports to Run Through a Firewall
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
JMX relies on JAVA technology called RMI, which uses dynamic ports to be able
to communicate between a client and a server. Firewalls cannot handle dynamic
ports, as they need to know the port number. iProcess overcomes this problem by
statically assigning a listening port for the RMI server.
To do this you need to configure the %SWDIR%/etc/swjmx.properties file.
Procedure
To configure the swjmxproperties file, complete the following steps:
1. Open the SWDIR/etc/swjmx.properties file. You can see the following
lines:
SWJMXConfig.location=C:/swserver/staffw_nod1/etc/swjmx_config.xml
SWJMXConfig.port=10025
2. Change the SWJMXConfig.port property to a port of your choosing.
The RMI server port number will then be automatically set to the value of
+1.
SWJMXConfig.port
3. Save the file.
TIBCO iProcess Engine for Windows Installation
140
| Appendix B
Post-installation Tasks
Setting Up iProcess Engine with an IPv6 Address
Status
Database
Description
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Possibly required
Upgrading from an iProcess Engine Version 11.0 or later
Possibly required
Oracle, SQL Server
If you want to use iProcess Engine with an IPv6 Address, you need to set up your
iProcess Engine. The IPv4 address is used for iProcess Engine by default.
To use LDAP server with an IPv6 address, you need to add an IPv6 address as a
host name when setting up the LDAP server connection. See "Setting Up the
Connection" in LDAPCONF Utility User’s Guide.
Procedure
Perform the following steps to set up IPv6 in iProcess Engine:
The network and machines that host iProcess Engine servers or clients must support IPv6.
1. Configure your database to support IPv6.
— Oracle To configure IP addresses for Oracle, edit the tnsnames.ora file,
which is located in the ORACLE_HOME\network\admin directory. Set the
value of the HOST parameter to the IPv6 address. The ORACLE_HOME
directory specifies where your Oracle database installs into. For more
information about how to edit the tnsnames.ora file, see Oracle
documentation.
— SQL Server To configure IP addresses for SQL Server, create an ODBC Data
Source. Add the IPv6 address in the Server field when selecting a server
that SQL Server connects to. For more information about how to create an
ODBC data source, see Creating the ODBC Data Source on page 110.
2. Stop iProcess Engine by running the following commands:
a. $SWDIR\bin\swstop
b. $SWDIR\bin\swstop
-p
3. Configure the STAFFCFG file, which is located in the $SWDIR\etc directory.
Change the value of the IPPROPTOCOL parameter to 6:
IPPROTOCOL, 6; 4 is IPV4, 6 is IPV6
TIBCO iProcess Engine for Windows Installation
Setting Up iProcess Engine with an IPv6 Address 141
|
For more information about the IPPROTOCOL parameter see "Tuning the
iProcess Engine Using SWDIR\etc\staffcfg Parameters" in TIBCO iProcess
Engine Administrator’s Guide.
4. Restart iProcess Engine.
TIBCO iProcess Engine for Windows Installation
142
| Appendix B
Post-installation Tasks
Starting TIBCO iProcess Engine
Status
Database
Description
Node Cluster
Procedure
If you are...
This task is...
Installing a new iProcess Engine Version 11.5.0
Optional
Upgrading from an iProcess Engine Version 11.0 or later
Optional
Oracle, SQL Server
The iProcess Engine is now properly installed, configured, and ready to start up
Install each node in the cluster before trying to start the iProcess Engine.
To start the iProcess Engine:
When you install iProcess Engine with the Oracle database 11g, if the Oracle
server and client have been installed on an x86 platform and a non-x86 platform
respectively, you must run the following steps before starting iProcess Engine:
1. Log in to SQLPlus using the system account.
2. Run the following statement:
alter system set events='10867 trace name context forever, level
1';
1. If you were prompted to reboot your computer when the installer finished,
but you have not yet done so, you must reboot now.
2. Log in as the iProcess Engine IPEADMIN user.
3. If you have installed the iProcess Engine to a Windows cluster, use the Bring
online service in the Microsoft Cluster Administrator to start the iProcess
Engine.
Do not start iProcess Engine on a Windows cluster using Control Panel >
Services or the SWDIR\bin\swstart command.
4. Copy the msvcr100.dll file from the $SWDIR\java\bin directory to the
win_systemroot\System32 (Microsoft Windows 32-bit) or
win_systemroot\SysWOW64 (Microsoft Windows 64-bit) folder. The win_systemroot
directory specifies where your Windows system is installed.
TIBCO iProcess Engine for Windows Installation
Starting TIBCO iProcess Engine 143
|
5. If you are not using a Windows Cluster:
a. Open a command prompt window.
b. Enter the following command to start the iProcess Engine process
sentinels:
SWDIR\bin\swstart -p
If you did not check the Auto start processes on service startup checkbox
when you ran the installer, enter the following command to start the
iProcess Engine processes:
SWDIR\bin\swstart
If you did check the Auto start processes on service startup checkbox, the
process sentinels will automatically start all of the iProcess Engine
processes.
Quick Starting and Restarting iProcess Engine
You can also use the following command to quick start the iProcess Engine
processes:
SWDIR\bin\swstart -q
You can use the RESTART_SPO_CACHE_PROC process attribute to define how many
latest versions of procedure definition to be cached by the iProcess Objects
Server processes when restarting the iProcess Objects Server processes or
quick starting iProcess Engine; use the RESTART_WIS_CACHE_THRESHOLD process
attribute to define the threshold number of work items in a work queue to be
cached by the WIS processes when restarting the WIS processes or quick starting
iProcess Engine.
For more information about the swstart -q command, see "Controlling the
iProcess Engine" in TIBCO iProcess Engine Administrator's Guide. For more
information about the RESTART_SPO_CACHE_PROC and
RESTART_WIS_CACHE_THRESHOLD process attributes, see "Administering Process
Attributes" in TIBCO iProcess Engine Administrator's Guide.
See Also
See "Controlling the iProcess Engine" in TIBCO iProcess Engine Administrator's
Guide for more information about how to start the iProcess Engine.
TIBCO iProcess Engine for Windows Installation
144
| Appendix B
Post-installation Tasks
TIBCO iProcess Engine for Windows Installation
| 145
Appendix C
Configuration Options for TIBCO iProcess
Engine Installation
This appendix lists the configuration options for TIBCO iProcess Engine
installation.
Topicst
•
Upgrade or New Install Dialog, page 146
•
Group & User Configuration Dialog, page 148
•
SQL/ODBC Details Dialog, page 151
•
Database Details Dialog, page 154
•
Select Components To Configure Dialog, page 158
•
Configuration Dialog, page 161
•
SMTP Server Parameters Dialog, page 166
•
SMTP Backup Servers Dialog, page 167
•
TIBCO iProcess Web Server Configuration Dialog, page 168
•
Default Java Message Service Dialog, page 170
TIBCO iProcess Engine for Windows Installation
146
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Upgrade or New Install Dialog
The Upgrade or New Install dialog allows you to choose whether to install a new
iProcess Engine or upgrade an existing one using the Custom installation type.
•
For information about a new installation, see Custom Installation - New
Installation on page 44.
•
For information about upgrading an existing iProcess Engine, see Custom
Installation - Upgrade Existing Installation on page 55.
The following table contains detailed information for configuration options
available in the Upgrade Or New Install dialog.
Table 16 Configuration Options in the Upgrade or New Install Dialog
Configuration
Option
New Installation
Description
Select the New Installation radio button to install a new iProcess Engine.
You need to specify an iProcess node name for the new installation. You
can either accept the default entry or enter a new name in the text field.
Default
Value
Selected
Note: If you want to install a master server, the node name must be 24
characters or less using letters or digits, which can be separated by an
underscore character.
If you want to install a slave server, the node name must be exactly the
same as the one used on the master server.
Upgrade Existing
Installation
Select the Upgrading Existing Installation radio button to upgrade an
existing iProcess Engine. You need to select the iProcess Engine that you
want to upgrade in the list of node names.
When you select a node name in the list, the related information of the
selected iProcess Engine is displayed in the Details area, for example,
Version, Language, Client-Server RPC port number, and so on.
Note: If you cannot directly upgrade the selected iProcess Engine node
name to this version, an error message is displayed in the Details area.
Click the Cancel button to exit the installation.
For detailed information of iProcess Engine upgrade requirements, see
Upgrade Requirements on page 24.
TIBCO iProcess Engine for Windows Installation
Unselected
Upgrade or New Install Dialog 147
|
Table 16 Configuration Options in the Upgrade or New Install Dialog (Cont’d)
Configuration
Option
Install Files
(Upgrade Files)
Custom
Installation
- New
Installation
Custom
Installation
- Upgrade
Existing
Installation
Install Schema
(Upgrade Schema)
Default
Value
Description
Custom
Installation
- New
Installation
Custom
Installation
- Upgrade
Existing
Installation
Check the Install Files
or Upgrade Files
checkbox to install
iProcess Engine files.
Note: Generally, the
administrator of your
operating system has
access to install files.
Check the Install
Schema or Upgrade
Schema checkbox to
install iProcess Engine
schema tables.
Note: Generally, the
database administrator
(DBA) has access to
install schema tables.
When performing an
upgrade, you can
choose whether to
migrate memo data by
clicking the following
radio buttons: Not
migrate, Migrate live
cases, and Migrate all
cases.
When performing a new
installation, if you want to
install both iProcess Engine
files and schema tables
simultaneously, check both
checkboxes. If you want to
install them separately, you
must install schema tables
first. After successfully
installing the schema tables,
restart the installer to install
files.
Note: If you check the Install
Files checkbox first, you will
be prompted to install schema
tables before installing files in
the following installation
steps.
Checked
Checked
Checked
N/A
When performing an
upgrade, if there are no
schema changes between
the current version and the
upgrade, the Upgrade
Schema checkbox is
unchecked and disabled. If
you need to upgrade
schema tables, you must
upgrade iProcess Engine
files also.
You can migrate the
memo data by using the
memo migration utility
after the upgrades. See
TIBCO iProcess Engine
Administrator’s Guide
for more information
about using the
swutil
MIGRATEMEMOS
command to migrate
memo data.
TIBCO iProcess Engine for Windows Installation
148
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Group & User Configuration Dialog
The Group & User Configuration dialog allows you to specify iProcess Engine
group names, the administrator account, the services account, and whether
iProcess Workspace users need a password to log in.
The following table contains detailed information for configuration options
available in the Group & User Configuration dialog
Table 17 Configuration Options in the Group & User Configuration Dialog
Configuration
Option
Description
Default Value
Please Select The iPE User And Administration Groups
Administrators
Group
Specify the local Windows group, for example, a group on the
computer where you are installing the iProcess Engine. This group
will be used to contain iProcess Engine administrators.
Basic Installation
You cannot change the default value.
Custom Installation New Installation
You can either select an existing group from
the drop-down list or enter a new group
name. The installer will create this group for
you.
Custom Installation Upgrade Existing
Installation
Users Group
Specify the local Windows group, for example, a group on the
computer where you are installing the iProcess Engine. This group
will be used to contain iProcess Engine users.
Basic Installation
You cannot change the default value.
Custom Installation New Installation
You can either select an existing group from
the drop-down list or enter a new group
name. The installer will create this group for
you.
Custom Installation Upgrade Existing
Installation
TIBCO iProcess Engine for Windows Installation
iProcess
Administrators
iProcess Users
Group & User Configuration Dialog 149
|
Table 17 Configuration Options in the Group & User Configuration Dialog (Cont’d)
Configuration
Option
Description
Default Value
Please Select The iPE Administrator Account
Select Account
From List
This checkbox is only enabled when performing the Custom
Installation.
Unchecked
Check this checkbox to populate the field with a drop-down list of user
accounts that are available from the location you specified in the
Operating System Users Location dialog.
Username
Specify the Windows account you want to use to administer the
iProcess Engine, for example, the IPEADMIN user.
Basic Installation
You cannot change the default account
shown.
Note: If you do not want to use the default
account as the IPEADMIN account, you must
click the Cancel button to exit the installation
and run setup.exe again using the desired
account as the IPEADMIN account.
Custom Installation New Installation
Custom Installation Upgrade Existing
Installation
You can either enter the name of the Windows
account you want to use directly or check the
Select Account From List checkbox to
populate the field with a drop-down list of
user accounts that are available from the
location you specified in the Operating
System Users Location dialog.
Note: If you have a large number of Windows
operating system users across a domain and
trusted domains, this can take a long time. To
avoid this, enter the name of the Windows
account you want to use directly.
Password
Enter the password for the selected iProcess Engine administrator
account user.
The
IPEINSTALL
user
The
IPEINSTALL
user
The existing
IPEADMIN
account that is
defined on line 3
of the
SWDIR\swdefs
file.
None
Please Select The iPE services Account
Use Separate
Account For iPE
Services
This checkbox is only enabled when performing the Custom
Installation.
Unchecked
Check this checkbox to use different Windows accounts for the
IPESERVICE users.
TIBCO iProcess Engine for Windows Installation
150
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Table 17 Configuration Options in the Group & User Configuration Dialog (Cont’d)
Configuration
Option
User Name
Description
Default Value
Specify the Windows account you want to use to run the iProcess
Engine, for example, the IPESERVICE user.
Basic Installation
You cannot change the default account
shown.
Note: If you do not want to use the default
account as the IPEADMIN account, you must
click the Cancel button to exit the installation
and run setup.exe again using the desired
account as the IPEADMIN account.
Custom Installation New Installation
Custom Installation Upgrade Existing
Installation
You can either enter the name of the Windows
account you want to use directly or check the
Select account from list checkbox to populate
the field with a drop-down list of user
accounts that are available from the location
you specified in the Operating System Users
Location dialog.
Note: If you have a large number of Windows
operating system users across a domain and
trusted domains, this can take a long time. To
avoid this, enter the name of the Windows
account you want to use directly.
The
IPEINSTALL
user
The
IPEINSTALL
user
The existing
IPEADMIN
account that is
defined on line 3
of the
SWDIR\swdes
file.
Password
Enter the password for the selected iProcess Engine services account
user.
N/A
Users Are
Required To
Login with A
Password
This checkbox is only enabled when performing the Custom
Installation.
Checked
Check this checkbox if you require iProcess Workspace users to supply
a password to log in to this iProcess Engine.
Uncheck this checkbox if you want to allow iProcess Workspace users
to be able to log in to this iProcess Engine without a password.
TIBCO iProcess Engine for Windows Installation
SQL/ODBC Details Dialog 151
|
SQL/ODBC Details Dialog
The SQL/ODBC Details dialog allows you to configure the ODBC data source
that is used to connect to SQL Server through iProcess Engine.
The following table contains detailed information for configuration options
available in the SQL/ODBC Details dialog.
Table 18 Configuration Options in the SQL/ODBC Dialog
Default
Value
Configuration Options
Description
Choose An Existing
ODBC Data Source
Select this radio button if you want to use an existing ODBC data
source, then select the ODBC data source you want to use from the
drop-down list.
Cleared
Note: When installing the iProcess Engine on a 64-bit Windows
system, only ODBC data sources created for 32-bit applications
will appear in the drop-down list. See Creating the ODBC Data
Source on page 110 for detailed information.
Enter ANew ODBC Data
Source
Select this radio button if you want to create a new ODBC data
source, and then enter a name in the field for the new ODBC data
source.
Selected
Note: This name must not be the same as any existing ODBC data
source name on the computer where you are installing the iProcess
Engine.
If you intend to use the TIBCO iProcess BusinessWorks Connector
with this iProcess Engine, this name must be the same as the name
of the database you want to use.
If you are installing the iProcess Engine into a Microsoft Windows
Cluster, the mscluster command automatically creates an
ODBC data source with the same name and details on each
secondary machine in the cluster. See Configuring the Microsoft
Windows Cluster on page 113 for detailed information.
TIBCO iProcess Engine for Windows Installation
152
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Table 18 Configuration Options in the SQL/ODBC Dialog (Cont’d)
Configuration Options
Description
Default
Value
SQL Server
Choose The SQL
Server To
Connect To
Select the name of the SQL Server that you want your new ODBC
Data Source to connect to in the drop-down list or enter its name in
the field directly.
N/A
Note: If the SQL Server you want to connect to is not listed in the
drop-down list, make sure that the SQL Server Browser
service is running. This service runs automatically, but if it is not
running for any reason, the SQL Server will not be shown in this
list.
Use Integrated
Windows
Authentication
This setting determines the authentication method that the ODBC
data source will use when connecting to the SQL Server.
Checked
Check this checkbox if you want the ODBC data source to connect
to the SQL Server using Windows authentication.
Uncheck this checkbox if you want the ODBC data source to
connect to the SQL Server using SQL Server authentication (SQL
Server login ID and password).
You Have DBA Privileges
Check this checkbox if you have the name and password of a SQL
Administrator login. This SQL Server login must be a member of
the sysadmin fixed server role.
Note: You must check this checkbox if you want the installer to
create the iProcess Engine database and iPE DB Owner and iPE DB
User logins for you. For detailed information about iPE DB Owner
and iPE DB User, see Database Details Dialog on page 154.
Uncheck this checkbox if you do not have the name and password
of a SQL Administrator login. In this situation, the installer will
not be able to create the iProcess Engine database and iPE DB
Owner and iPE DB User logins. To continue with the installation,
you must have created the iProcess Engine database and iPE DB
Owner and iPE DB User logins before running the installer. For
detailed information, see Creating the SQL Server Database and
Logins on page 106.
TIBCO iProcess Engine for Windows Installation
Checked
SQL/ODBC Details Dialog 153
|
Table 18 Configuration Options in the SQL/ODBC Dialog (Cont’d)
Configuration Options
SQL Server Login
Name
Default
Value
Description
This field is only available if you check the You Have DBA
Privileges checkbox.
sa
Specify the username of the SQL Administrator login that you
want the installer to use to connect to this SQL Server.
SQL Server Login
Password
This field is only available if you check the You have DBA
privileges checkbox.
N/A
Enter the password for the specified SQL Administrator login.
TIBCO iProcess Engine for Windows Installation
154
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Database Details Dialog
The Database Details dialog allows you to configure the database that the iProcess
Engine will connect to.
The following two databases can be used with the iProcess Engine on Windows:
•
SQL Server, page 154
•
Oracle, page 156
SQL Server
If you are using a SQL Server database, the following table contains detailed
information for configuration options available in the Database Details dialog.
Table 19 Configuration Options in the Database Details Dialog - SQL Server
Configuration Option
ODBC Source
Description
Default Value
The ODBC Data Source being used appears in this field.
The ODBC
Source that is
defined in
You cannot change this value. If it is not the ODBC Data
Source you want to use, click the Back button to return to the
SQL/ODBC Details Dialog and select a different ODBC
Data Source.
SQL/ODBC
Details Dialog
on page 151
Database Details
Database Name
Specify the name of the database that you want to create.
Note: If you chose to use an existing ODBC Data Source, you
cannot change the value shown, which is the name of the
database associated with that ODBC data source. If this is not
the database you want to use, click the Back button to return
to the SQL/ODBC Details Dialog and choose a different
ODBC Data Source.
In the SQL/ODBC Details Dialog, if you do not check the You
Have DBA Privileges checkbox, you must specify the name of
an existing database here.
If you intend to use the TIBCO iProcess BusinessWorks
Connector with this iProcess Engine, this name must be the
same as the name of the ODBC Source.
See Microsoft SQL Server documentation for information
regarding applicable naming conventions.
TIBCO iProcess Engine for Windows Installation
The name of the
database
associated with
the selected
ODBC data
source
Database Details Dialog 155
|
Table 19 Configuration Options in the Database Details Dialog - SQL Server (Cont’d)
Configuration Option
Description
Default Value
iPE DB Owner Login
Specify the name of the SQL Server login that owns the
iProcess Engine database.
N/A
Note: In the SQL/ODBC Details Dialog on page 151, if you do
not check the You Have DBA Privileges checkbox, you must
specify the name of an existing SQL Server login here.
If you are using Windows-authenticated accounts, you must
enter the simple username not the fully qualified name, for
example, swpro rather than EMEA\swpro. For more
information, see Authentication Requirements on page 22.
See Microsoft SQL Server documentation for information
regarding applicable Naming Conventions.
iPE DB Owner Password
Specify the password for the iPE DB owner.
N/A
Note: When entering a password, you must ensure that the
password conform to the password complexity requirements
of your site. If you are unsure of the password complexity
requirements, contact your system administrator.
iPE DB User Login
Specify the name of the SQL Server login that the iProcess
Engine will use for read access to the iProcess Engine
database.
N/A
Note: See Microsoft SQL Server documentation for
information regarding applicable Naming Conventions.
In the SQL/ODBC Details Dialog, if you do not check the You
Have DBA Privileges checkbox, you must specify the name of
an existing SQL Server login here.
iPE DB User Password
Enter the password for the specified iPE DB User Login.
N/A
Note: When entering a password, you must ensure that the
password conforms to the password complexity requirements
of your site. If you are unsure of the password complexity
requirements, contact your system administrator.
Support Unicode
Encoding
Check this checkbox if you want the iProcess database to
support unicode (UTF-8) encoding. For more information, see
Does the iProcess Engine Database Support UTF-8 on
page 180
Unchecked
Uncheck it to disable this function.
TIBCO iProcess Engine for Windows Installation
156
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Oracle
If you are using an Oracle database, the following table contains detailed
information for configuration options available in the Database Details dialog.
Table 20 Configuration Options in the Database Details Dialog - Oracle
Configuration Option
Description
Enter The Oracle Database
Service (TNS) Name
Specify the service name of the Oracle database in which
you want to create the iProcess Engine schema.
Default
Value
N/A
Note: If you are using a direct connection to the default
database hosted on the computer where you are installing
the iProcess Engine, you can leave this field blank. For
more information, see Direct Connection Requirements for
Oracle on page 18.
TIBCO strongly recommends the use of an Oracle
TAF-enabled service name to provide 24*7 resilient
operation. If you are deploying the iProcess Engine for
user acceptance testing (UAT) or to a production
environment, you must enable TAF. For detailed
information, see Setting Up Oracle Transparent
Application Failover (TAF) on page 98.
You cannot change this value if you are upgrading the
iProcess Engine.
See Oracle Database documentation for information
regarding applicable naming conventions.
Database
Admin User
(e.g. system)
Username
Specify the name of the Oracle user that the iProcess
Engine will use when it needs to connect to the database as
a database administrator (DBA).
system
This must be an account which has the necessary
permissions to create tables and users, for example, either
with the DBA role assigned or with access to the Oracle
Data Dictionary.
Note: See Oracle Database documentation for information
regarding applicable naming conventions.
Password
Specify the password for the Oracle DBA user.
Note: When entering a password, you must ensure that the
password conform to the password complexity
requirements of your site. If you are unsure of the
password complexity requirements, contact your system
administrator.
TIBCO iProcess Engine for Windows Installation
N/A
Database Details Dialog 157
|
Table 20 Configuration Options in the Database Details Dialog - Oracle (Cont’d)
Default
Value
Configuration Option
Description
Support Unicode Encoding
Check this checkbox if you want the iProcess database to
support unicode (UTF-8) encoding.
Unchecked
Uncheck it to disable this function.
Database
Users
Change
If you want to use different users, click the Change
button to open the Database Users dialog. You can define
the iPE DB Owner and password, the iPE User and
password, and Tablespace in the dialog.
N/A
Note: When entering a password, you must ensure that the
password conforms to the password complexity
requirements of your site. If you are unsure of the
password complexity requirements, contact your system
administrator.
TIBCO iProcess Engine for Windows Installation
158
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Select Components To Configure Dialog
The Select Components to Configure dialog allows you to choose whether you
want to install, enable, or configure various optional iProcess Engine components.
The following table contains detailed information for configuration options
available in the Select Components To Configure dialog.
Table 21 Configuration Options in the Select Components to Configure Dialog
Configuration
Option
Description
Upgrade NobleNet
Portmapper
This checkbox is only enabled if the installer detects that the NobleNet Portmapper
service is installed on your system.
Check this checkbox if you want to upgrade this service. The upgrade will replace the
existing service with a new version with the name NobleNet Portmapper for
TCP.
TIBCO advises you to perform this upgrade, unless you have other services on your
computer which have a hardcoded dependency on the NobleNet Portmapper
service.
Uncheck this checkbox if you do not want to upgrade the NobleNet Portmapper
service.
Upgrade COM+
Component
Check this checkbox if you want to upgrade the COM+ Component.
Register EAICOM
Server Plug-in
Check this checkbox to enable TIBCO iProcess COM Server Plug-in.
Uncheck this checkbox if you do not want to upgrade the COM+ Component.
TIBCO recommends that you do this only if you need to use this plug-in, and if you
have ensured that your iProcess environment fully supports distributed transactions.
See Is It Necessary to Use TIBCO iProcess COM Server Plug-in on page 182 for more
information.
Uncheck the checkbox to disable this plug-in.
Configure E-Mail
Plug-in
Check this checkbox if you want to configure SMTP server parameters for the TIBCO
iProcess EMail Server Plug-in as part of the installation. You will be able to configure
these parameters in a later installation dialog.
You cannot change this setting if you are upgrading from Version 10.5 or later, or from
an earlier version that already has the TIBCO iProcess EMail Server Plug-in installed.
The checkbox is disabled.
Alternatively, you can configure SMTP server parameters after you have installed the
iProcess Engine. See TIBCO iProcess Email Plug-in User’s Guide for more information.
Uncheck this checkbox if you want to do this.
TIBCO iProcess Engine for Windows Installation
Select Components To Configure Dialog 159
|
Table 21 Configuration Options in the Select Components to Configure Dialog (Cont’d)
Configuration
Option
Description
Install iProcess Web
Server Service
Check this checkbox if you want to install the iProcess nodename Web Server service.
You should install this service if you want to use the iProcess Server Manager.
The iProcess Server Manager is a JSP web client application that you can use to start,
stop, restart, and pause iProcess Engine server processes. It utilizes TIBCO Hawk and
TIBCO Rendezvous (see Additional System Requirements on page 9 for more
information) to provide a graphical view of the iProcess Engine server processes on a
machine or a node cluster.
You will need to specify the location of the TIBCO Hawk and TIBCO Rendezvous
applications in a later dialog. See TIBCO iProcess Web Server Configuration Dialog on
page 168.
Alternatively, you can use the SWDIR\bin\smstart.bat file to install this service
after you have installed the iProcess Engine. See "Using the iProcess Server Manager to
Administer Server Processes" in TIBCO iProcess Engine Administrator’s Guide for more
information. Uncheck this checkbox if you want to do this, or if you do not want to
install this service.
Enable IAP
Check this checkbox to enable activity publishing (both IAPJMS and Work Queue
Delta publishing). Uncheck this checkbox to disable it.
If you are upgrading from Version 10.3 or later you cannot change this setting. The
checkbox is disabled.
If activity publishing is enabled, activity information about auditable objects (for
example, procedures and steps) can be published to an external application. (The BG
process publishes monitored activities to the IAPJMS process.) This enables real-time
monitoring of auditable objects so that mission critical or important business events
can be easily monitored.
Similarly, details of a work item are provided whenever the work item changes on a
queue that the subscribing application is subscribed to.
Note: If you enable activity publishing on the master server, you must also enable it on
each slave server.
Selecting this checkbox sets the value of the iProcess Engine IAPJMS_PUBLISH process
attribute to 1 (enabled). Clearing it sets it to 0 (disabled). See TIBCO iProcess Engine
Administrator’s Guide for more information about this process attribute.
Enabling activity publishing does not result in activities being automatically published by the
iProcess Engine. To get the iProcess Engine to actually monitor and publish events, you
must also:
•
configure the activities and events that you want to monitor and publish. See
“Configuring Activity Monitoring” in TIBCO iProcess Modeler - Integration
Techniques for more information.
•
configure how iProcess Engine will handle and publish monitored events. See
“Administering Activity Monitoring” in TIBCO iProcess Engine Administrator’s
Guide for more information.
TIBCO iProcess Engine for Windows Installation
160
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Table 21 Configuration Options in the Select Components to Configure Dialog (Cont’d)
Configuration
Option
Use Cluster
Network Name
Description
Check this checkbox if you want to install the iProcess Engine to a virtual server in a
Microsoft Windows cluster. (The indicated Microsoft Windows cluster Network Name
will be written to the iProcess Engine database node_cluster table at the end of the
installation process.)
You must do this if you wish to run the iProcess Engine in an interference-free failover
configuration on a Microsoft Windows cluster.
Uncheck this checkbox if you want to install the iProcess Engine on the physical
computer instead.
Note: This checkbox is only displayed if a Microsoft Windows cluster Network Name
can be found for the machine on which the installation is being performed. The Cluster
Network Name is also displayed for information.
If you are upgrading from Version 10.5 or later you cannot change this setting. The
checkbox is disabled.
You can update the node_cluster table with a Microsoft Windows cluster Network
Name after installation if you prefer.
You will need to perform some additional post-installation tasks to configure the
iProcess Engine to run in a cluster.
Enable iProcess
Objects Server
Check this checkbox if you want to enable the iProcess Objects Server process (SPO).
Uncheck it to disable the process.
The iProcess Objects Server receives requests for services or data from TIBCO iProcess
Objects (COM, JAVA, or C++) or TIBCO iProcess Server Objects (JAVA or .NET). The
iProcess Objects Server processes the request, then makes the appropriate call to an
iProcess Engine to initiate the desired service or obtain the desired information.
For more information, see TIBCO iProcess Objects Server Administrator’s Guide.
Configure iProcess
Objects Server
Check this checkbox if you want to run the iProcess Objects Server Configuration
Utility later in the installation process. This utility allows you to set configuration
parameters for the iProcess Objects Server.
Uncheck this checkbox if you do not want to run the configuration utility.
For information about the parameters available in this utility, see TIBCO iProcess
Objects Programmer’s Guide or TIBCO iProcess Objects Server Administrator’s Guide.
Enable iProcess
Objects Director
Check this checkbox if you want to enable the iProcess Objects Director process
(DIRECTOR).
The iProcess Objects Director is a standalone program that maintains a list of iProcess
Objects Servers that are configured in a node cluster. When a client needs access to an
iProcess Objects Server, it first establishes a connection to the iProcess Objects Director.
The iProcess Objects Director then decides, based on a “pick method”, which iProcess
Objects Server the client should connect to.
For more information, see TIBCO iProcess Objects Director Administrator’s Guide.
TIBCO iProcess Engine for Windows Installation
Configuration Dialog 161
|
Configuration Dialog
The Configuration dialog allows you to define a number of basic iProcess Engine
configuration options.
The following table contains detailed information for configuration options
available in the Configuration dialog.
Table 22 Configuration Options in the Configuration Dialog (Sheet 1 of 5)
Configuration
Options
Description
Default
Value
Licensee
Specify a name to identify the installing iProcess Engine.
TIBCO
Note: The length of the name must be between 4 and 32 characters.
JMX Port
Number
TIBCO iProcess Engine includes a Java Management Extensions (JMX)
engine that enables TIBCO Business Studio to deploy procedures to the
iProcess Engine.
10025
Specify the port number on which the JMX engine should run.
The port number must be:
—an integer value between 0 and 65535.
—unique across all iProcess Engine installations on this computer.
If you do not specify a number, the default port 10025 will be used.
In Business Studio, a Deployment Server can use this port number to
deploy processes to this iProcess Engine using the JMX Remote Method
Invocation (RMI) interface. See TIBCO Business Studio Process Developer’s
Guide for more information.
The port number will be written to the SWJMXConfig.port entry in the
SWDIR\etc\swjmx.properties file, and can be changed after
installation if needed. See TIBCO iProcess Engine Administrator’s Guide for
more information.
TIBCO iProcess Engine for Windows Installation
162
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Table 22 Configuration Options in the Configuration Dialog (Sheet 2 of 5)
Configuration
Options
Client-Server
RPC Port
Number
Description
Specify the RPC service number that the TIBCO iProcess Workspace
(Windows) clients use to communicate with this iProcess Engine:
Default
Value
391877
- Select a new value from the drop-down list.
- Click the
button to open the RPC Port Numbers dialog. Enter the
RPC port numbers in the Client-Server RPC Port Number field.
Note: You cannot change this value when upgrading an existing iProcess
Engine.
391875 to 391879
are reserved for iProcess Engine client-server RPC
program numbers. Using a number in this range should prevent any
clash with other applications using the same number, provided that other
applications also use legitimate RPC numbers.
The RPC service number must be unique across all iProcess Engine
installations on this computer.
Process
Sentinels Service
Startup
Select the startup mode you want to use for the iProcess Process
Sentinels service from the drop-down list:
Automatic
Automatic - The iProcess Process Sentinels service starts
automatically when the computer starts up.
Manual - You must manually start the Process Process Sentinels
service either locating the service from Control Panel > Services or using
the SWDIR\bin\swstart command.
Disabled - You cannot start the iProcess Process Sentinels service.
After the installation, you can change this setting by using the Services
Console on Windows.
Auto-start
Processes On
Service Startup
Check this checkbox to automatically start the iProcess Engine processes
after the iProcess Process Sentinels service has started and set the
value of the iProcess Engine PM_AUTO_BOOT process attribute to 1
(enabled).
Uncheck this checkbox to disable automatic process startup and set the
value of the iProcess Engine PM_AUTO_BOOT process attribute to 0
(disabled). You will need to manually start the iProcess Engine processes
after the iProcess Process Sentinels service has started.
For an existing iProcess Engine, if the automatic process startup is
currently enabled (PM_AUTO_BOOT=1), you cannot disable it during the
upgrade. The checkbox is disabled.
See TIBCO iProcess Engine Administrator’s Guide for more information
about the PM_AUTO_BOOT process attribute.
Note: You must check this checkbox if you are installing the iProcess
Engine to a Microsoft Windows Cluster.
TIBCO iProcess Engine for Windows Installation
Checked
Configuration Dialog 163
|
Table 22 Configuration Options in the Configuration Dialog (Sheet 3 of 5)
Configuration
Options
Enable Case
Prediction
Default
Value
Description
Check this checkbox to enable the case prediction server process
(BGPREDICT) and set the value of the iProcess Engine
ENABLE_CASE_PREDICTION process attribute to 1 (enabled).
Unchecked
Uncheck this checkbox to disable the case prediction server process
(BGPREDICT) and set the value of the iProcess Engine
ENABLE_CASE_PREDICTION process attribute to 0 (disabled).
For an existing iProcess Engine, if the case prediction server process
is currently enabled (ENABLE_CASE_PREDICTION=1), you cannot
disable it during the upgrade. The checkbox is disabled.
See TIBCO iProcess Engine Administrator’s Guide for more information
about the iProcess Engine ENABLE_CASE_PREDICTION process
attribute.
Note: The case prediction server process only affects background
case prediction. It has no effect on live case prediction or case simulation.
For more information about the usage of case prediction, see the
Using Case Prediction to Forecast Outstanding Work Items chapter in TIBCO
iProcess Modeler Advanced Design.
TIBCO iProcess Engine for Windows Installation
164
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Table 22 Configuration Options in the Configuration Dialog (Sheet 4 of 5)
Configuration
Options
Enable Case
Data
Normalization
Description
Case data normalization is a feature used to make case data searching
more efficient and therefore faster. It uses the field_value_N column
in the case_data table in the iProcess Engine database. This column
provides a normalized value of the value in the field_value column,
allowing the database to do simple string comparisons, instead of having
to do type conversions.
Check this checkbox to enable case data normalization and set the value
of the iProcess Engine NORMALISE_CASE_DATA process attribute to 1
(enabled).
Uncheck this checkbox to disable case data normalization and set the
value of the iProcess Engine NORMALISE_CASE_DATA process attribute
to 0 (disabled).
For an existing iProcess Engine, if case data normalization is currently
enabled (NORMALISE_CASE_DATA=1), you cannot disable it during the
upgrade. The checkbox is disabled.
See TIBCO iProcess Engine Administrator’s Guide for more information
about the NORMALISE_CASE_DATA process attribute.
Note: If you intend to use iProcess Objects to perform case data searches,
TIBCO strongly recommends that you enable case data normalization. If
you do not do this, you will be able to view and start procedures, but you
will not be able to view the cases until you normalize the data.
You can enable or disable case data normalization after installation by
using the Case Data Normalization Utility. See the
Administering Case Data Normalization chapter in the TIBCO iProcess
Engine Administrator's Guide for more information about this utility.
When upgrading an existing iProcess Engine, you should also note the
following before choosing to enable case data normalization:
The installer will need to populate the field_value_N column for
every row in the case_data table, using the values from the
field_value column. This can significantly impact the duration of the
upgrade process if there are large numbers of cases on the system. See
How Long Will an Upgrade Take on page 183 for more information.
TIBCO iProcess Engine for Windows Installation
Default
Value
Checked
Configuration Dialog 165
|
Table 22 Configuration Options in the Configuration Dialog (Sheet 5 of 5)
Configuration
Options
Enable system
event logging
Default
Value
Description
The system event logging records system events like logins, login
failures, movesysinfos, and so on. The recorded system events are saved
in the system_event table. You can change the configuration in the
system_event_conf table to decide which system events are audited
and published. See TIBCO iProcess Engine (DB2, SQL, and Oracle)
Administrator’s Guide for more information.
Checked
Check this checkbox to enable the system event logging and set the value
of the iProcess Engine SYSTEM_EVENT_LOGGING process attribute to 1
(enabled).
Uncheck this checkbox to disable the system event logging and set the
value of the iProcess Engine SYSTEM_EVENT_LOGGING process attribute
to 0 (disabled).
See TIBCO iProcess Engine Administrator’s Guide for more information
about the iProcess Engine
SYSTEM_EVENT_LOGGING,PUBLISH_SYS_EVENT_METHOD, and
SEJMS_TOPICNAME process attributes.
TIBCO iProcess Engine for Windows Installation
166
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
SMTP Server Parameters Dialog
The SMTP Server Parameters dialog allows you to configure the parameters that
the iProcess EMail Server Plug-in will use to connect to an SMTP server.
The values you specify in the SMTP Server Parameters dialog are written as
parameters to the SWDIR\libs\eai_mail.cfg file. For more information about
these parameters, see TIBCO iProcess Email Plug-in User’s Guide.
If you are upgrading a system that already has the iProcess Email Plug-in
installed, the default values shown in this dialog are taken from the existing
SWDIR\libs\eai_mail.cfg file.
The following table contains detailed information for configuration options
available in the SMTP Server Parameters dialog.
Table 23 Configuration Options in the SMTP Server Parameters Dialog
Configuration Option
Description
Default Value
Mail From
Specify the default email address that you want to use to
send EAI Mail messages from.
N/A
Host
Specify the name or IP address of the machine hosting
the SMTP server that you want to use.
N/A
Port
Specify the TCP port number on which the SMTP server
is running.
25
Test
Connection
Click this button if you want to test the connection to the
SMTP server using the specified Host and Port
parameters.
N/A
Check this checkbox if you want to specify SMTP
backup hosts.
Unchecked
SMTP Server
Parameters
Specify SMTP Backup Hosts
Click the Next button, the SMTP Backup Servers dialog
appears. Configure the parameters for your SMTP
backup servers in this dialog. For detailed information,
see SMTP Backup Servers Dialog on page 167.
Specify Mail Message
Headers
Check this checkbox if you want to specify the header
information to be used with all EAI Mail messages.
Click the Next button, enter the information in the Enter
Message Header field.
TIBCO iProcess Engine for Windows Installation
Unchecked
SMTP Backup Servers Dialog 167
|
SMTP Backup Servers Dialog
The SMTP Backup Servers dialog allows you to configure parameters that the
iProcess Email Plug-in will use to locate backup servers in case of a failure in the
primary SMTP server. For more information about backup servers, see TIBCO
iProcess Email Plug-in User’s Guide.
The values you specify in this dialog are written as parameters to the
SWDIR\libs\eai_mail.cfg file. For more information about these parameters,
see TIBCO iProcess Email Plug-in User’s Guide.
The following table contains detailed information for configuration options
available in the SMTP Backup Servers dialog.
Table 24 Configuration Options in the SMTP Backup Servers Dialog
Configuration
Option
Description
Default Value
SMTP Backup Servers
Host
For each backup server in turn, you can specify the machine name or
the IP address of the machine hosting the backup SMTP server. There
can be as many backup host entries as there are SMTP servers available
for failover.
N/A
Port
The port number on which the preceding backup host is running. There
must be one backup port entry for each backup host server.
25
Retry Count
Specify how many times the iProcess Email plug-in will use a backup
server before retrying the primary host.
50
Enter a non-zero numeric value in this field.
Note:
—If a negative value is entered, it is interpreted as the default value.
—If zero or a non-numeric value is entered, the configuration of backup
servers has no effect and the plug-in reverts to the primary host.
If a successful connection is made on retrying the primary host, the
plug-in reverts to using that host. If not, the plug-in continues with the
backup server that is currently in use.
TIBCO iProcess Engine for Windows Installation
168
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
TIBCO iProcess Web Server Configuration Dialog
The TIBCO iProcess Web Server Configuration dialog allows you to specify the
location of TIBCO Hawk and TIBCO Rendezvous that are used by the iProcess
Web Server service.
The following table contains detailed information for configuration options
available in the TIBCO iProcess Web Server Configuration dialog.
Table 25 Configuration Options in the TIBCO iProcess Web Server Configuration Dialog
Configuration
Option
Description
Default Value
TIBCO Software Location
Please Enter The
Directory Where
TIBCO HAWK
Is Installed
Specify the full pathname of the directory where the TIBCO Hawk
software is installed.
Please Enter The
Directory Where
TIBCO
Rendezvous Is
Installed
Specify the full pathname of the directory where the TIBCO
Rendezvous software is installed.
C:\tibco\hawk
—Enter the full pathname of the directory in the field.
—Click the
button. The Locate TIBCO Hawk dialog appears.
Select the appropriate directory, then click the OK button.
—Enter the full pathname of the directory in the field.
—Click the
button. The Locate TIBCO Rendezvous dialog
appears. Select the appropriate directory, then click the OK button.
TIBCO iProcess Engine for Windows Installation
C:\tibco\tibrv
TIBCO iProcess Web Server Configuration Dialog 169
|
Table 25 Configuration Options in the TIBCO iProcess Web Server Configuration Dialog (Cont’d)
Configuration
Option
Description
Default Value
Enable The
Webdav Server
For Write Access
Check this check box if you want write access to WebDav enabled
on the Apache Tomcat application server that is installed with
iProcess Engine.
Unchecked
Selecting this option enables you to easily deploy your TIBCO
Forms using TIBCO Business Studio. If you want to use TIBCO
Forms and do not want to enable this option, then you must install
the forms manually on this or your own web server.
There are security issues around enabling WebDav and if you select
this option, the following warning message is displayed:
You have enabled write access to WebDAV, which
allows you to make your own deployed forms for the
browser client. This may cause your server
potential security issues and/or cause your
deployed forms for the browser client to fail.
TIBCO Software Inc. is not responsible for these
or any other consequences caused by your use of
the write access to WebDAV.
If you do not want to use TIBCO Forms, then TIBCO recommends
that you do not enable write access to WebDav. See Apache Tomcat
Application Server Documentation for more information about
security.
TIBCO iProcess Engine for Windows Installation
170
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Default Java Message Service Dialog
The Default Java Message Service dialog, along with two subsequent dialogs,
allows you to configure the necessary Java Message Service (JMS) parameters to
enable Activity Monitoring and Work Queue Delta publication on the iProcess
Engine.
For more information about the use of these parameters, see Administering
Activity Monitoring in TIBCO iProcess Engine Administrator’s Guide.
To configure the default JMS parameters, complete the following steps:
1. Select one JMS provider that the iProcess Engine will publish messages to in
the Default Java Message Service dialog, as shown in Figure 33.
If you want to use TIBCO EMS, select TIBCO EMS 8.0 if you are using TIBCO
EMS version 8.0, otherwise select TIBCO EMS if you are using TIBCO EMS other
supported versions.
If you want to use JBoss 4.0.0, you need to select the JBoss radio button. If you
want to use any other version of JBoss or JBoss Messaging, you need to select the
Other radio button instead.
If you want to use IBM Websphere 7.x, you need to select the IBM Websphere 8.x
button. If you are using IBM Websphere 8.x, SSL will be enabled by default. Since
SSL is disabled by default in TIBCO iProcess Engine, you should either disable
SSL in IBM Websphere 8.x or enable SSL in TIBCO iProcess Engine.
Similarly, if you want to use Oracle WebLogic Server Version, you should select
the Oracle WebLogic Server radio button. If you want to use any other version of
WebLogic Server, you select the Other radio button instead.
TIBCO iProcess Engine for Windows Installation
Default Java Message Service Dialog 171
|
Figure 33 Default Java Message Service Dialog
2. Click the Next button. The JAR Files For JMS Connectivity dialog appears.
Configure the items listed in Table 26.
TIBCO iProcess Engine for Windows Installation
172
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Table 26 Configuration Options in the JAR Files For JMS Connectivity Dialog
Configuration
Option
Description
Base
In the Default Java Message Service dialog shown in Figure 33, if you select:
IBM Websphere 6.x
Specify the full path of the directory containing the IBM Client for JMS on J2SE with
WebSphere Application Server. The iProcess Engine IAPJMS process must use this client
to communicate with the WebSphere 6.x Application Server.
If you do not already have this client installed on this computer, TIBCO recommends that
you use the default location (SWDIR\jmsclient). You must then install this client into
the specified directory after you have installed iProcess Engine. See Installing the IBM
Client for JMS on J2SE with IBM WebSphere Application Server, page 127 for more
information about how to do this.
IBM Websphere 8.x
You must specify the websphere_home directory where IBM Websphere 8.x is installed
and make sure the following files are saved in the websphere_home\runtimes
directory:
•
com.ibm.ws.sib.client.thin.jms_versionnumber.jar
•
com.ibm.ws.ejb.thinclient_versionnumber.jar
•
com.ibm.ws.orb_versionnumber.jar
JBoss 6.x
Specify the full path of the directory containing the following files:
•
jboss-jms-api_1.1_spec.jar
•
jnp-client.jar
•
hornetq-core-client.jar
•
hornetq-jms-client.jar
•
netty.jar
•
jboss-logging.jar
Note: In JBosss 6.x, JMS service is provided by HornetQ. So you need to install HornetQ.
On the other hand, you can find the listed .jar files either in HornetQ or in JBoss 6.x final
installation directory.
TIBCO iProcess Engine for Windows Installation
Default Java Message Service Dialog 173
|
Table 26 Configuration Options in the JAR Files For JMS Connectivity Dialog (Cont’d)
Configuration
Option
Description
Base
anything else
Specify the full path (or comma-separated paths) of the JAR files required by this JMS
provider.
When specifying the path, make sure that you use the forward slash character (/) as the
path separator, rather than the backslash character (\). For example, specify
e:/tibco/ems/clients/java/jms.jar not
e:\tibco\ems\clients\java\jms.jar.
The installer writes this value to the IAPJMS configuration file:
SWDIR\etc\iapjms_classpath.properties.
Additional
Specify the full path (or comma-separated paths) of any additional JAR files that are
required for your JMS configuration.
When specifying the path, make sure that you use the forward slash character (/) as the
path separator, rather than the backslash character (\).
The installer writes this value to the IAPJMS configuration file:
SWDIR\etc\iapjms_classpath.properties.
If you are using a Microsoft Windows Cluster, the Base and Additional paths
must be accessible to every physical machine in the cluster.
3. Click the Next button. The IAPJMS Properties dialog appears. Configure the
items listed in Table 27.
Table 27 Configuration Options in IAPJMS Properties Dialog
Configuration
Option
Context
Description
Specify the name of the context factory that produces context instances for the selected JMS
Provider.
The installer writes this value to the IAPJMSConnect.InitialContextFactory
property in the IAPJMS configuration file:
SWDIR\etc\iapjms_classpath.properties.
URL
Specify the URL that the iProcess Engine uses to connect to the selected JMS Provider.
The installer writes this value to the IAPJMSConnect.InitialURL property in the
IAPJMS configuration file: SWDIR\etc\iapjms_classpath.properties.
TIBCO iProcess Engine for Windows Installation
174
| Appendix C
Configuration Options for TIBCO iProcess Engine Installation
Table 27 Configuration Options in IAPJMS Properties Dialog (Cont’d)
Configuration
Option
Connection
Description
Specify the name of the object that iProcess Engine uses to create a connection to the
selected JMS Provider.
The installer writes this value to the IAPJMSConnect.TopicConnectionFactory
property in the IAPJMS configuration file:
SWDIR\etc\iapjms_classpath.properties.
4. Click the Next button to continue with the installation.
TIBCO iProcess Engine for Windows Installation
| 175
Appendix D
Usage Profiles for Tablesizes Files
This appendix shows the usage profiles that have been used to calculate the
values used in the alternative tablesizes files tablesizes.med and
tablesizes.large.
In each file, the sizing of the initial extent is 10% of the maximum estimated
tablesize. This means that as the table grows it will expand to fill 10 database
extents.
Topics
•
tablesizes.med File, page 176
•
tablesizes.large File, page 177
TIBCO iProcess Engine for Windows Installation
176
| Appendix D
Usage Profiles for Tablesizes Files
tablesizes.med File
This file defines tablesizes for a medium-sized installation. If you use this file, you
must reserve at least 2.5 GB of disk space for the database.
Statistic
Value
Number of registered iProcess Engine users
200
Number of iProcess Engine groups
10
Number of user-defined attributes
4
Average number of groups a user belongs to
5
Average number of case starts per day
2000
Average number of days before a case is purged
90
Average number of days before a case is closed
30
Average percentage of steps processed via queues
90%
Average number of assigned fields per case
50
Average number of steps processed per case
10
Average number of CustAudits per case
20
Average number of sub-procedure calls per case
3
Average size of field name
10
Average size of field value
50
TIBCO iProcess Engine for Windows Installation
tablesizes.large File 177
|
tablesizes.large File
This file defines tablesizes for a large-sized installation. If you use this file, you
must reserve at least 65 GB of disk space for the database.
Statistic
Value
Number of registered iProcess Engine users
9500
Number of iProcess Engine groups
500
Number of user-defined attributes
12
Average number of groups a user belongs to
15
Average number of case starts per day
20000
Average number of days before a case is purged
90
Average number of days before a case is closed
30
Average percentage of steps processed via queues
90%
Average number of assigned fields per case
150
Average number of steps processed per case
25
Average number of CustAudits per case
50
Average number of sub-procedure calls per case
8
Average size of field name
12
Average size of field value
50
TIBCO iProcess Engine for Windows Installation
178
| Appendix D
Usage Profiles for Tablesizes Files
TIBCO iProcess Engine for Windows Installation
| 179
Appendix E
Frequently Asked Questions
This appendix lists some frequently asked questions.
Topics
•
Does the iProcess Engine Database Support UTF-8, page 180
•
How Do I Create the SQL Server Database, page 181
•
Is It Necessary to Use TIBCO iProcess COM Server Plug-in, page 182
•
How Long Will an Upgrade Take, page 183
•
How Do I Upgrade TIBCO EMS, page 184
TIBCO iProcess Engine for Windows Installation
180
| Appendix E
Frequently Asked Questions
Does the iProcess Engine Database Support UTF-8
TIBCO iProcess Suite supports Unicode (UTF-8) character encoding natively
within its component products. When you install TIBCO iProcess Engine, you
have the option to specify whether or not you want your iProcess database to
support UTF-8, see the option listed in Database Details Dialog on page 154.
Determining whether or not to support UTF-8 is a major decision. Before you start
the installation process, TIBCO recommends that you consult “Using the TIBCO
iProcess Suite in a Multilingual Environment" in TIBCO iProcess Engine
Architecture Guide. This sets out the advantages and costs of using UTF-8, both in
new installations, and when upgrading existing iProcess installations.
TIBCO iProcess Engine for Windows Installation
How Do I Create the SQL Server Database 181
|
How Do I Create the SQL Server Database
When you install a new iProcess Engine, you can use one of the following two
methods to create iProcess Engine users and schema in the SQL Server database:
•
Let the installer create the iProcess Engine users and schema. TIBCO
recommends using this method wherever possible. However, to do this, you
must have access to a SQL Server DB Administrator (DBA) account when you
run the installer.
•
Get a SQL Server DB Administrator to create the iProcess Engine users and
schema before you run the installer, as a pre-installation task, see Creating the
SQL Server Database and Logins on page 106. Using this method allows you
to run the installer without access to a SQL Server DB Administrator account.
You can choose the method which best suits the operational, organizational, and
security requirements of your particular installation scenario.
TIBCO iProcess Engine for Windows Installation
182
| Appendix E
Frequently Asked Questions
Is It Necessary to Use TIBCO iProcess COM Server Plug-in
The iProcess COM Server Plug-in is a component of the iProcess Engine that you
can optionally choose to register when you run the installer, see Select
Components To Configure Dialog on page 158 for details. You need to register
this plug-in if the iProcess Engine will handle procedures that use EAI COM steps
to call external COM applications.
The iProcess COM Server Plug-in can have a significant impact on iProcess
Engine performance. TIBCO recommends that you register it only if you need to
use EAI COM steps.
The iProcess COM Server Plug-in uses the transaction infrastructure provided by
the Microsoft Distributed Transaction Coordinator service (MSDTC). This
infrastructure imposes security and authentication requirements which can cause
permissions problems if the iProcess environment is not set up correctly to
support distributed transactions. If such problems occur, the iProcess COM Server
Plug-in will not work, see Distributed Transaction Errors Occur When You Start
iProcess Engine on page 213 for details.
Consequently, TIBCO recommends that if you intend to use the iProcess COM
Server Plug-in, you make sure that you adhere to the following requirements
when installing the iProcess Engine:
•
The following entities must all be located either on the same machine or in the
same domain:
— the iProcess Engine
— the Windows iProcess Engine administrator account (IPEADMIN), which
runs the iProcess nodeName Process Sentinels service
— the Oracle or SQL Server database
— the Windows account that is running the Oracle or SQL Server database
— the Windows account that is running the Distributed
Coordinator service.
•
Transaction
In a domain, the Distributed Transaction Coordinator service must be
running on every machine that is running an iProcess Engine master or slave
server, or the Oracle or SQL Server database.
See TIBCO iProcess COM Plug-in User’s Guide for more information.
TIBCO iProcess Engine for Windows Installation
How Long Will an Upgrade Take 183
|
How Long Will an Upgrade Take
Upgrading to TIBCO iProcess Engine Version 11.5.0 can involve significant
changes to iProcess Engine data and data structures. The upgrade process is
therefore complex, and can take a significant amount of time to complete if the
system being upgraded has a large amount of case data.
TIBCO cannot provide an estimate of how long the upgrade will take because of
the number of customer-specific factors that could have an impact, and the
complexity of their interaction, such as the amount of data in your system, the
configuration of your Oracle or SQL Server system, and the hardware setup you
are running.
TIBCO therefore strongly recommends that you test the upgrade before
performing it on your target system, either on a representative production
environment, or using a copy of your production system. This will allow you to
determine how long the upgrade is likely to take, and to identify any specific
factors that may affect the success or duration of the upgrade. If you require
further advice or assistance on this, contact TIBCO Support.
TIBCO iProcess Engine for Windows Installation
184
| Appendix E
Frequently Asked Questions
How Do I Upgrade TIBCO EMS
TIBCO iProcess Engine version 10.6.x was shipped with a version of TIBCO EMS
that contains a security vulnerability (EMS 4.4.1 or earlier). See the following link
for more information:
http://www.tibco.com/resources/mk/ems_security_advisory_20080115.txt
In order to fix the vulnerability EMS must be updated to version 6.0 or later. It is
therefore fixed by upgrading EMS to the version required for TIBCO iProcess
Engine Version 11.5.0.
Updating EMS
The EMS installer does not currently offer an upgrade option. The install process
removes any queues, topics, factories, or other configurations that have been
applied to the EMS server and restores to the default configurations.
In order to backup and restore all your existing EMS queues, factories, topics,
queue messages, topic messages and configuration use the following process:
1. Stop your EMS applications.
2. Stop tibemsd and tibemsadmin.
3. Make a copy of all .conf files and .db files found under the ems/bin
directory and its sub-directories.
4. Uninstall the old EMS version.
5. Install the new EMS version.
6. Replace your .conf files and .db files from step 3.
For more detailed instructions on how to install and uninstall EMS, see TIBCO
Enterprise Message Service Installation.
It is important that this configuration is maintained because iProcess features,
such as IAPJMS, Technology Plug-ins, and Web Services Plug-in, rely on various
EMS queues and topics to function correctly.
TIBCO iProcess Engine for Windows Installation
How Do I Upgrade TIBCO EMS 185
|
IAPJMS Specific Procedure
With a basic iProcess Engine installation, EMS can be used by the IAPJMS process
for activity publication.
After the upgrade IAPJMS will continue to function. IAPJMS uses client jar files
found in the EMS install directory to connect to EMS. As long as the configuration
is correct no other update should be needed.
TIBCO iProcess Web Services Plug-in Specific Procedure
TIBCO iProcess Web Services Plug-in can be configured to use EMS as the JMS
provider. In this case an additional step is required after the EMS upgrade.
Update the tibjms.jar file stored under the SWDIR\jetty-6.1.1\jms\tibco
directory to the new version supplied with the updated EMS server.
TIBCO iProcess Technology Plug-in Specific Procedure
The TIBCO iProcess Technology Plug-in uses EMS to communicate with the
BusinessWorks Engine when iProcess Engine > BusinessWorks EAI steps are
being defined. The following additional step is required after EMS has been
updated:
Update the tibjms.jar file stored under the SWDIR\jmslib\ems directory to the
new version supplied with the updated EMS server.
TIBCO iProcess Engine for Windows Installation
186
| Appendix E
Frequently Asked Questions
TIBCO iProcess Engine for Windows Installation
| 187
Appendix F
Troubleshooting
This appendix describes how to deal with errors that you may encounter when
installing the iProcess Engine.
If the information in this appendix does not help you to resolve the problem, or if
you are in any way unsure as to how to proceed, contact TIBCO Support for
further assistance.
Topics
•
The Installer Fails with an Unable to Open the File Warning Dialog, page 189
•
The Installer Exits Because You Are Not a Local Administrator, page 190
•
Installer Cannot Continue Because Another iPE is Running, page 191
•
Installation Encounters an Error Trying to Locate pthread.dll, page 192
•
Installation Encounters an Error Trying to Locate pthread.dll, page 192
•
Installing with an Unsupported Database Version, page 194
•
The Installer Cannot Locate an Oracle UNDO Tablespace, page 196
•
Oracle TAF Is Not Enabled, page 197
•
Oracle Advanced Queuing Is Not Enabled, page 198
•
Oracle Client and Database NLS_LANG Settings Do Not Match, page 199
•
Oracle OPEN_CURSORS Value Is Less Than 200, page 200
•
The Installer Cannot Initialize the iProcess Engine Database, page 201
•
Errors Occur on Validating the Installation, page 202
•
License File Cannot Be Found, page 203
•
Upgrading Fails Because It Cannot Create the Process Sentinels Process,
page 204
•
Recovering iProcess Engine if an Upgrade Fails, page 205
•
mscluster Command Reports Error in \etc\services File, page 207
TIBCO iProcess Engine for Windows Installation
188
| Appendix F
Troubleshooting
•
Process Sentinels Do Not Start Due to Logon Failure, page 209
•
iProcess Engine Processes Do Not Start, page 211
•
Distributed Transaction Errors Occur When You Start iProcess Engine,
page 213
•
Failed to Start TIBCO iProcess Engine Using a Domain User, page 214
TIBCO iProcess Engine for Windows Installation
The Installer Fails with an Unable to Open the File Warning Dialog 189
|
The Installer Fails with an Unable to Open the File Warning Dialog
Problem
Description
When you run the installer a Warning dialog is displayed with the following
message:
Unable to open the file: fil.dll
You can only click the OK button to this dialog, and when you do so, the installer
exits.
This error occurs if you do not have the correct Oracle database and/or client
releases (along with any additionally required patches or components) installed
on the computer where you are trying to install the iProcess Engine.
The fil.dll file requires the Oracle client .dll files to be able to connect to the
Oracle database. When the installer starts, it tries to load the fil.dll file, which
in turn attempts to load the required Oracle .dll files. If these files cannot be
found, the error occurs.
What to Do
Install the required Oracle database and/or client release on the computer where
you are trying to install iProcess Engine. See Oracle Database on page 18 for more
information.
Make sure that you have also installed any additional patches or components that
are required.
TIBCO iProcess Engine for Windows Installation
190
| Appendix F
Troubleshooting
The Installer Exits Because You Are Not a Local Administrator
Problem
Description
When you run the installer it exits immediately with the following error message:
You are not a local machine Administrator.
Setup cannot continue
To be able to run the installer, you must be logged in as a user that is a member of
the Windows Administrators group on the computer where you are trying to
run the installer.
What to Do
To resolve this problem:
1. Either:
— Log out, then log in as a user who is already a member of the local
Administrators group.
— Add the user you are logged in as to the local Administrators group.
To access the Administrators group, select Control Panel > Administrative
Tools > Computer Management > System Tools > Local Users and Groups >
Groups > Administrators. See your Windows documentation if you need more
information.
2. Run the installer again.
TIBCO iProcess Engine for Windows Installation
Installer Cannot Continue Because Another iPE is Running 191
|
Installer Cannot Continue Because Another iPE is Running
Problem
Description
The installer displays an error when you click the Next button on the Setup Type
dialog, see Upgrade or New Install Dialog on page 146. For example:
The following iPE services have been found to be running:
rocess
staffw_nod1 Process Sentinels
The installation process cannot continue until all installations
have been shutdown.
Please see the iPE server document for more information.
The installer has detected that the indicated iProcess nodeName Process
Sentinels service is running, where NodeName is the nodename of the iProcess
Engine that is running the service.
The installer may need to stop and replace components (such as the iProcess
COM+ application) that are also used by other iProcess Engine
installations, if those components need updating. If so, it cannot perform the
installation if another iProcess Engine is running on the same machine.
Events
What to Do
To resolve this problem:
1. Stop the indicated iProcess nodeName
this:
Process Sentinels
service. To do
a. Open the Control Panel window.
b. Double-click the Administrative Tools icon.
c. Double-click the Services icon.
d. Right-click the iProcess nodeName
choose Stop.
Process Sentinels
service and
2. Click the Next button on the Setup Type dialog again. If you have chosen:
— a Basic installation, the Choose Destination Location dialog is displayed.
— a Custom installation, the Upgrade or New Install dialog is displayed.
See Also
See “Stopping the TIBCO iProcess Engine” in TIBCO iProcess Engine
Administrator’s Guide for more information.
TIBCO iProcess Engine for Windows Installation
192
| Appendix F
Troubleshooting
Installation Encounters an Error Trying to Locate pthread.dll
Problem
Description
When you run the installer, the installer exits immediately with one of the
following error messages:
•
Failed to locate the 'pthread.dll' component
•
The minimum 'pthread.dll' component version required is 2.7.0.
The version available on the system is 2.6.0
•
Failed to load the 'pthread.dll' component as no version
information could be found in it
•
Failed to determine the version of the 'pthread.dll'
component.
accompanied by the following message:
POSIX Threads (pthreads) for Win32 is required in order for the
software to run correctly. Please refer to the Installation
Guide for information on where to get hold of this component and
how to install it.
What to Do
To resolve this problem:
1. Obtain the POSIX Threads (pthreads) library for Windows distribution set
library from TIBCO Software Inc. and make it available on your system PATH.
For detailed information, see POSIX Threads (pthreads) on page 9.
2. Run the installer again.
TIBCO iProcess Engine for Windows Installation
Connecting to the Oracle Database Fails During Installation 193
|
Connecting to the Oracle Database Fails During Installation
Problem
Description
The installer displays the following error when you click the Next button from the
Database Details dialog:
Failed to connect to database with username, password and
connection supplied.
Do you wish to continue with this setup?
The installer cannot connect to the Oracle database.
What to Do
To resolve this problem:
1. Check the following:
— You have specified the correct information in the Database Details dialog.
— The Oracle database is running and your computer has a network
connection to it.
2. If you want to continue with the installation, click the Yes button. If you do
not want to continue with the installation, click the No button. The installer
exits.
TIBCO iProcess Engine for Windows Installation
194
| Appendix F
Troubleshooting
Installing with an Unsupported Database Version
Problem
Description
If you try to install or upgrade the iProcess Engine using a database version that
does not meet the minimum requirements for this version of the iProcess Engine,
the installer displays the following error messages when you click the Next
button from the Database Details dialog. For example,
•
for the Oracle database:
WARNING: the version of Oracle you are using is not supported.
See the Installation Guide for full details of supported
Oracle versions.
Minimum versions required are
10g (10.2.0.4)
11g (11.2.0.3)
Do you wish to continue with this installation?
•
for the SQL Server database:
Failed to determine the version of SQL server.
Do you wish to continue with this installation?
or
WARNING: the version of SQL server you are using is not
supported.
Minimum versions required are:
SQL Server 2005 Service Pack 3 (9.0.4035)
SQL Server 2008 (10.0.1600)
Continue with installation?
Although you can continue, TIBCO recommends that you only install the iProcess
Engine using a supported database version.
TIBCO iProcess Engine for Windows Installation
Installing with an Unsupported Database Version 195
|
What To Do
If you want to continue with the installation, click the Yes button.
If you do not want to continue with the installation:
1. Click the No button. The installer exits.
2. Upgrade your operating system and/or database to a supported version and
then restart the installer.
TIBCO iProcess Engine for Windows Installation
196
| Appendix F
Troubleshooting
The Installer Cannot Locate an Oracle UNDO Tablespace
Problem
Description
The installer displays one of the following error messages when you click the
Next button from the Database Details dialog:
Error Message
Meaning
This Oracle instance does not
have an UNDO tablespace
defined.
The installer has connected to the Oracle database
and determined that an UNDO tablespace does not
exist.
You cannot continue the
installation without an UNDO
tablespace.
Failed to determine if there is an
UNDO tablespace present.
The installer has attempted to connect to the Oracle
database to determine if an UNDO tablespace
exists, but has been unable to do so.
The installer cannot create the iProcess Engine database schema without an
UNDO tablespace.
What To Do
To resolve this problem:
1. Click the OK button. The Database Details dialog is displayed.
2. Make sure that the Oracle database is running and that your computer has a
network connection to it.
3. Make sure that an Oracle UNDO tablespace exists for the iProcess Engine
database. Create one if it does not. See Oracle documentation for more
information on how to create and manage UNDO tablespaces.
4. Click the Next button on the Database Details dialog.
TIBCO iProcess Engine for Windows Installation
Oracle TAF Is Not Enabled 197
|
Oracle TAF Is Not Enabled
Problem
Description
The installer displays one of the following error messages when you click the
Next button from the Database Details dialog:
Error Message
Meaning
This Oracle connection does
NOT have TAF enabled, you can
still continue, but if this
installation is to be used in a
UAT or Production environment
you MUST enable TAF
(Failover).
The installer has connected to the Oracle database
and determined that Oracle TAF is not enabled for
the specified Oracle database service (TNS) name.
Continue without TAF enabled?
Failed to determine whether
TAF is configured for the Oracle
connection.
The installer has attempted to connect to the Oracle
database to determine if Oracle TAF is enabled, but
has been unable to do so.
TIBCO strongly recommends the use of Oracle TAF with the iProcess Engine to
provide 24*7 resilient operation.
If you are deploying iProcess Engine for user acceptance testing (UAT) or to a
production environment, you must enable TAF.
What To Do
If you want to enable TAF before continuing with the installation:
1. Click the No button to return to the Database Details dialog.
2. Make sure that the Oracle database is running and that your computer has a
network connection to it.
3. Enable Oracle TAF on your chosen service name.
4. Click the Next button on the Database Details dialog.
If you want to continue with the installation without enabling TAF, click the Yes
button.
TIBCO iProcess Engine for Windows Installation
198
| Appendix F
Troubleshooting
Oracle Advanced Queuing Is Not Enabled
Problem
Description
The installer displays one of the following error messages when you click the
Next button from the Database Details dialog:
Error Message
Meaning
This Oracle connection does
NOT have Advanced Queuing
installed.
The installer has connected to the Oracle database
and determined that Oracle Advanced Queuing is
not installed for the specified Oracle database
service (TNS) name.
Oracle Advanced Queuing (AQ)
is required for iPE.
Failed to determine whether
Oracle AQ is correctly installed.
The installer has attempted to connect to the Oracle
database to determine if Oracle TAF is installed, but
has been unable to do so.
Oracle Advanced Queuing provides the message queuing and event handling
systems used by the iProcess Engine. The iProcess Engine will not work if Oracle
Advanced Queuing is not installed.
What To Do
To resolve this problem:
1. Click the No button to return to the Database Details dialog.
2. Make sure that the Oracle database is running and that your computer has a
network connection to it.
3. Make sure that Oracle Advanced Queuing is installed. See your Oracle
documentation for more information about installing Advanced Queuing.
4. Click the Next button on the Database Details dialog.
TIBCO iProcess Engine for Windows Installation
Oracle Client and Database NLS_LANG Settings Do Not Match 199
|
Oracle Client and Database NLS_LANG Settings Do Not Match
Problem
Description
What To Do
The installer displays one of the following error messages when you click the
Next button from the Database Details dialog:
Error
Meaning
The NLS_LANG environment
setting doesn't match the
database's setting.
The installer has connected to the Oracle database
and determined that its NLS_LANG setting does not
match the NLS_LANG setting on the Oracle client.
Failed to check the NLS
environment settings with that
of the database.
The installer has attempted to connect to the Oracle
database to check its NLS_LANG setting, but has
been unable to do so.
To resolve this problem:
1. Click the No button to return to the Database Details dialog.
2. Make sure that the Oracle database is running and that your computer has a
network connection to it.
3. Change the NLS_LANG setting for the Oracle client so that it matches the
NLS_LANG setting on the Oracle database.
4. Click the Next button on the Database Details dialog.
TIBCO iProcess Engine for Windows Installation
200
| Appendix F
Troubleshooting
Oracle OPEN_CURSORS Value Is Less Than 200
Problem
Description
What To Do
The installer displays one of the following error messages when you click the
Next button from the Database Details dialog:
Error
Meaning
WARNING: This Oracle instance
has the OPEN_CURSORS
parameter configured to a value
less than 200. It should be set to
200 or greater.
The installer has connected to the Oracle database
and determined that its OPEN_CURSORS parameter
is configured to a value less than 200.
Failed to get the current value of
the Oracle OPEN_CURSORS
parameter.
The installer has attempted to connect to the Oracle
database to check its OPEN_CURSORS parameter
value, but has been unable to do so.
To resolve this problem:
1. Click the No button to return to the Database Details dialog.
2. Make sure that the Oracle database is running and that your computer has a
network connection to it.
3. Increase the OPEN_CURSORS parameter to a value of 200 or more.
4. Click the Next button on the Database Details dialog.
TIBCO iProcess Engine for Windows Installation
The Installer Cannot Initialize the iProcess Engine Database 201
|
The Installer Cannot Initialize the iProcess Engine Database
Problem
Description
The installer displays the following error when it tries to run the SQL script to
initialize the iProcess Engine database schema:
The database initialization script has failed to run
successfully.
Setup cannot continue.
What To Do
To resolve this problem:
1. Click the Exit button to exit from the installer.
2. Examine the following log file to determine the cause of the error:
— For Oracle users
SWDIR\logs\init2Kora_tok.sql_UserName_TimeStamp.log
— For SQL Server users
SWDIR\logs\init2Ksql.sql_UserName_TimeStamp.log
where:
— UserName is the name of the account being used to run the installer (for
example, the IPEINSTALL user).
— TimeStamp is the time that the log file was created, in the form
DDMMYYYY_HHMM.
3. If the cause of the error is obvious, correct it and restart the installer. If not,
contact TIBCO Support for further assistance.
TIBCO iProcess Engine for Windows Installation
202
| Appendix F
Troubleshooting
Errors Occur on Validating the Installation
Problem
Description
The installer displays one or more of the following error messages when it
attempts to validate that the installation has succeeded:
Error Message
Failed to start the NobleNet Portmapper for TCP service or
contact it once it had been started. ErrorDescription
Failed to start the iPE COM+ component.
ErrorDescription
Some or all of the iPE registry entries haven't been created or
updated correctly. ErrorDescription
Failed to subscribe, publish or receive a COM+ event.
ErrorDescription
Failed to access the database and validate the nodename.
ErrorDescription
Failed to enqueue message to the BG.
ErrorDescription
In each case, ErrorDescription provides more detailed information about the
specific error that has occurred. There may also be further information in the
Windows System and/or Application event logs (which you can view by
selecting Control Panel > Administrative Tools > Event Viewer.)
In the case of the COM+, database access and enqueuing message errors, the
following log file also provides further information about the error:
SWDIR\logs\PostChecks_UserName_TimeStamp.log
where:
•
UserName is the name of the account being used to run the installer (for
example, the IPEINSTALL user).
•
What To Do
TimeStamp is the time that the log file was created, in the form DDMMYYYY_HHMM.
Examine the ErrorDescription and, if applicable, the log file to try and determine
the cause of the error and its possible resolution.
TIBCO recommends that you contact TIBCO Support for further assistance with
any of these errors unless the cause and resolution are immediately obvious.
TIBCO iProcess Engine for Windows Installation
License File Cannot Be Found 203
|
License File Cannot Be Found
Problem
Description
When the installer attempts to generate configuration files, it displays an error
message stating that the license file cannot be found. When you click the OK
button to acknowledge this message, a Dr. Watson error is generated.
When running the installer, in the Choose Destination Location dialog, the
Destination Folder for the iProcess system directory (SWDIR) had a full pathname
of more than 64 characters.
What to Do
To resolve this problem:
1. Run the installer again.
2. In the Choose Destination Location dialog, specify a Destination Folder
pathname that has a length 64 characters or less.
TIBCO iProcess Engine for Windows Installation
204
| Appendix F
Troubleshooting
Upgrading Fails Because It Cannot Create the Process Sentinels
Process
Problem
Description
The installer displays the following fatal error:
InstallService(): CreateService (iProcess staffw_nod1 iProcess Sentinels)
The specified service has been marked for deletion.
The Services dialog was open when you ran the installer.
If the Services dialog is open when the installer runs, the installer cannot upgrade
the indicated iProcess Engine service.
What to Do
To correct this error:
1. Close the Services dialog.
2. Run the installer again.
TIBCO iProcess Engine for Windows Installation
Recovering iProcess Engine if an Upgrade Fails 205
|
Recovering iProcess Engine if an Upgrade Fails
Problem
Description
In some circumstances, it is possible that an upgrade can fail and leave the
iProcess Engine system in an unusable condition. If this happens:
1. You must restore your original system to its previous condition before you can
either use it or attempt to upgrade it again.
2. If you suspect that:
— the error was caused by an external factor (for example, a system hardware
failure while the upgrade was in progress), you can, if you wish, attempt to
upgrade the system again.
— the error was connected with the upgrade process itself (for example, the
installer crashes for unknown reasons), TIBCO recommends that you do
not attempt to upgrade again. Instead, you should contact TIBCO Support
for further assistance.
What to Do
If you are using iProcess Engine with the Oracle database, follow these steps to
restore your original system:
1. Log in as the background user, for example, the IPEADMIN user.
2. Delete the SWDIR directory structure.
3. Restore your backup of the SWDIR directory structure. See your operating
system documentation for more information about how to do this.
4. Run the SWDIR\bin\fixperms program, to grant appropriate permissions on
all files in and under SWDIR. Use the command:
SWDIR\bin\fixperms -r -y SWDIR
The system should now be restored to the same state it was in before you
attempted to upgrade it.
If you are using iProcess Engine with the SQL Server database, follow these steps to
restore your original system:
1. Re-install the version of the iProcess Engine or Process Engine that you were
attempting to upgrade from. Make sure that you install it in the same folder.
Do not start iProcess Engine or Process Engine at the end of installation.
2. Restore the backup of your iProcess system directory (SWDIR) which you
made before attempting the upgrade.
TIBCO iProcess Engine for Windows Installation
206
| Appendix F
Troubleshooting
3. From the SQL Server, restore the backup of the iProcess database which you
made before attempting the upgrade. See the SQL Server documentation for
more information about how to do this.
4. Restore default file permissions to all iProcess server files. (This may be
necessary if any file permissions were changed during the backup or restore
operation.) To do this:
a. Log in as the IPEADMIN user.
b. Take ownership of all files in and below the SWDIR folder.
c. Give Full Control to Everyone for all files in and below the SWDIR folder.
d. Run the SWDIR\bin\fixperms utility.
The system should now be restored to the same state it was in before you
attempted to upgrade it.
TIBCO iProcess Engine for Windows Installation
mscluster Command Reports Error in \etc\services File 207
|
mscluster Command Reports Error in \etc\services File
Problem
Description
When you install the iProcess Engine, the installer writes the port numbers used
by the iProcess Engine watcher and worker process sentinels to the
%systemroot%\system32\drivers\etc\services file.
The SWDIR\mscluster\mscluster utility attempts to replicate these entries to
the %systemroot%\system32\drivers\etc\services file on the Windows
cluster node. If it encounters an error, the utility displays this message:
Checking entries in 'etc\services'
followed by one of the errors listed below.:
Error
Meaning
Error: watcher port number
Number already in use by process
mscluster cannot create the required entry for the
watcher process because the allocated port Number
is already in use on this machine by the indicated
process.
You will need to either change the port number
used by the indicated process, or use a different port
number for the watcher process.
Error: port mismatch for watcher
entry nodename_watcher entry currently uses
CurrentNumber rather than
NewNumber
mscluster cannot create the required entry for the
watcher process because an entry already exists for
it. The current entry uses port CurrentNumber but
mscluster needs to allocate port NewNumber to it.
You will need to manually update the existing
entry.
The error messages are shown for the watcher process. The same errors can also
occur for the worker process.
What to Do
To resolve this problem:
1. Using a suitable text editor, open the
%systemroot%\system32\drivers\etc\services
file.
2. If necessary, change the port number allocated to the other process indicated in
the error message.
3. Add the required entry for the watcher (or worker) process, in the format:
nodename_SentinelType
Number/tcp
[# Comment]
TIBCO iProcess Engine for Windows Installation
208
| Appendix F
Troubleshooting
where:
— nodename is the iProcess Engine nodename.
— SentinelType is either watcher or worker, as shown in the error message.
— Number is the port number you want to use, either the original number that
mscluster tried to use (as reported in the error message) or a different
number, as required.
The port number must be a unique entry in this file (for example, not used by
any other entry).
There must be a blank line left at the bottom of the services file, otherwise
the last line is ignored.
— Comment (optional) is any descriptive text you want to add.
4. Save the file.
If you have used a different port number than the one that mscluster tried to use,
you must replicate this change to the other machines in the iProcess Engine
system. Repeat steps 1 to 4 on the iProcess Engine master server, any iProcess
Engine slave servers, and each other machine in the Windows cluster.
TIBCO iProcess Engine for Windows Installation
Process Sentinels Do Not Start Due to Logon Failure 209
|
Process Sentinels Do Not Start Due to Logon Failure
Problem
Description
When you try to start the iProcess Engine for the first time, the iProcess
nodeName Process Sentinels service fails to start and displays the following
error message (system error 1069):
.
The service did not start due to a logon failure.
See TIBCO iProcess Engine Administrator’s Guide for more information about how
to start the iProcess Engine.
When you install the iProcess Engine, the installer assigns the Log on as a
right to the user account you have chosen to use to run the iProcess
nodeName Process Sentinels service (the IPESERVICE user). The right is
assigned on the computer where you have installed the iProcess Engine.
service
However, a conflict can occur if:
•
you have installed the iProcess Engine in a domain, using domain users, and
•
the domain uses a group policy for the Log on
policy does not include the IPESERVICE user.
as a service
right, but the
The domain controller propagates the group policy to the member machines in
the domain at regular intervals (by default, every 90 minutes). When this
happens, the IPESERVICE user’s locally-assigned right will be overwritten by the
group policy. The account therefore loses the Log on as a service right, and so
cannot start the iProcess nodeName Process Sentinels service.
What to Do
To resolve this problem:
1. Change the group policy on the domain controller for the Log
service right to include the IPESERVICE user.
You must have access to an account that has Domain
privileges to be able to change the group policy.
on as a
Administrator
2. On the computer running the iProcess Engine, either wait for the domain
controller to refresh the group policy, or use the Microsoft gpupdate tool to
update the policy immediately.
3. Start the iProcess Engine. The iProcess nodeName
service should start correctly.
Process Sentinels
TIBCO iProcess Engine for Windows Installation
210
| Appendix F
Troubleshooting
See Also
See your Microsoft documentation for more information about group policies,
how to change them, and the gpupdate tool.
TIBCO iProcess Engine for Windows Installation
iProcess Engine Processes Do Not Start 211
|
iProcess Engine Processes Do Not Start
Problem
Description
When you try to start iProcess Engine for the first time, the iProcess nodeName
Process Sentinels service starts but the remaining iProcess server processes do
not appear.
See TIBCO iProcess Engine Administrator’s Guide for more information about how
to start the iProcess Engine and the processes that should appear when you start
it.
iProcess Engine processes communicate by publishing and subscribing to events.
When the iProcess Engine starts, a START event is issued. The Process Sentinels
subscribe to that event, which causes them to start the necessary iProcess Engine
server processes.
The iProcess Events COM+ application provides event handling functionality for
the iProcess Engine. If there is a problem with this application, events cannot be
processed, so the Process Sentinels do not receive the START event and therefore
do not start the iProcess Engine server processes.
The iProcess Events application runs using the IPESERVICE Windows account.
When the application starts up, it authenticates the IPESERVICE user, either:
•
on the local machine, if local accounts are being used, or
•
on the appropriate domain controller, if domain or trusted domain accounts
are being used, or if the iProcess Engine is installed in an Active Directory
environment.
If authentication fails, the iProcess Events COM+ application fails to start.
Possible reasons for authentication failure are:
What to Do
•
The application cannot contact the domain controller for some reason - for
example, transient network problems.
•
Incorrect username, the wrong IPESERVICE user is being used.
•
Incorrect password for the IPESERVICE user. This can occur if the
IPESERVICE user account has been deleted and recreated for any reason. An
encrypted identifier is associated with each instance of a username/password
combination. Although the recreated username and password are the same,
this identifier is different, so authentication fails. The password must be
manually re-entered.
To try and correct any problems with the iProcess Events application:
1. Open the Control Panel window, click Administrative Tools, and then click
Component Services. The Component Services console is displayed.
TIBCO iProcess Engine for Windows Installation
212
| Appendix F
Troubleshooting
2. In the left pane, select Component Services > Computers > My Computer >
COM+ Applications.
3. Right-click COM+ Applications and select View > Status View. The
right-hand pane shows whether or not the iProcess Events application is
currently running.
On Windows Server 2003, the iProcess Events application does not run all the
time. It shuts down automatically when it is idle, and restarts automatically
when an event occurs.
4. Right-click iProcess Events and select Properties from the pop-up menu.
5. On the Identity tab (which specifies the account that the iProcess Events
application runs under):
a. Select the This user radio button, and make sure that the specified User is
the correct IPESERVICE user for this installation.
b. Enter the password for this user again in both the Password and Confirm
Password fields.
6. Click the OK button.
7. If the iProcess Events application is currently running, right-click it and shut it
down.
8. Right-click the iProcess Events application and start it. Make sure that the
application is running.
You should now be able to start iProcess Engine server processes. To do this:
1. Log in as the IPEADMIN user.
2. Make sure that the iProcess nodeName
running.
Process Sentinels
service is
3. Use the command:
SWDIR\bin\swstart
4. Check that the appropriate server processes start (using either
SWDIR\util\swadm or Task Manager).
TIBCO iProcess Engine for Windows Installation
Distributed Transaction Errors Occur When You Start iProcess Engine 213
|
Distributed Transaction Errors Occur When You Start iProcess
Engine
Problem
Description
When you start the iProcess Engine for the first time, the following error message
is repeatedly written to the SWDIR\logs error file.
2007/01/26 12:02:36(BG:1:6088:1:pro:idl.c:7.148:5826):
1945-Database error: idl_SQL_allocate_connection_from_pool()
idl_SQL_enlist_connection() Failed
This error indicates that the TIBCO iProcess COM Server Plug-in has been
registered, but is unable to successfully complete a distributed transaction due to
permissions problems.
These problems are most likely caused by using an iProcess environment that
does not properly support distributed transactions. See Is It Necessary to Use
TIBCO iProcess COM Server Plug-in on page 182 for more information.
What to Do
To stop the error being written to the SWDIR\logs error file, unregister the
iProcess COM Server Plug-in using the following command:
SWDIR\util\sweaireg UNREG eaicom
The iProcess Engine will not be able to process any EAI COM steps after you have
done this.
If you need to be able to process EAI COM steps, you will need to either re-install
and/or re-configure the iProcess Engine to use an environment that supports
distributed transactions, or investigate the particular permissions problems to see
if any workarounds are available. Contact TIBCO Support for further assistance.
TIBCO iProcess Engine for Windows Installation
214
| Appendix F
Troubleshooting
Failed to Start TIBCO iProcess Engine Using a Domain User
Problem
Description
(Only for Microsoft Windows Server 2012 R2) If you install TIBCO iProcess
Engine as Administrator and specify another domain user as the TIBCO iProcess
Engine administrator account in the Group & User Configuration dialog, the
following error occurred when you run the swstart -p command to start TIBCO
iProcess Engine:
Could Not Find C:\swserver\lipelw1\pmstop
System error 5 has occurred
Access is denied.
What to Do
To resolve this problem, perform the following tasks:
•
User Account Control Setting
•
Security Policy Setting
Task A User Account Control Setting
Perform the following steps to change user account control setting:
1. Click or tap Start in Microsoft Windows. In the search box, type Change User
Account Control settings. The User Account Control Settings dialog is
displayed.
2. Move the slider to Never notify.
3. Click OK.
Task B Security Policy Setting
Perform the following steps to set security policy for user account:
1. Open the Control Panel window.
2. Double-click the Administrative Tools icon.
3. Double-click the Local Security Policy icon. The Local Security Policy
window is displayed.
4. Expand Local Policies > Security Options in the left panel and then
double-click the User Account Control: Run all administrators in Admin
Approval Mode item in the right panel.
5. Select Disabled in the Local Security Setting tab.
6. Restart your machine.
TIBCO iProcess Engine for Windows Installation
| 215
Index
A
G
Access permissions
Windows 2003, XP 92
Activity Publishing and Work Queue Delta
Publication 14
Additional pthread Requirements for the SAL SDK 12
Additional System Requirements 9
Authentication Requirements 22
Generating a Response File 63
I
DBA 4
Direct Connection Requirements for Oracle 18
init2Kora_tok.sql_UserName_TimeStamp.log 25
init2Ksql.sql_UserName_TimeStamp.log 25
Installation Mode
GUI Mode 2
Silent Mode 2
Installation Modes 2
Installation Overview 2
Installation Requirements 8
Installation Types 3
Basic 3
Custom 3
Installer Accounts 4
Installing TIBCO iProcess Engine 29
Installing TIBCO iProcess Engine in GUI Mode 34
Installing TIBCO iProcess Engine in Silent Mode 63
IPEADMIN 4
IPEINSTALL 4
IPESERVICE 4
iProcess Engine Architecture 6
Node Cluster 6
Single Server 6
iProcess Files-install Owner 3
iProcess Schema-install Owner 3
iProcess Server Manager 13
F
J
Foreground processes 119
Java Runtime Environment (JRE) 16
B
Basic Installation 35
Basic System Requirements 8
C
connecting with TIBCO resources xix
Custom Installation - New Installation 44
Custom Installation - Upgrade Existing Installation 55
customer support xix
D
TIBCO iProcess Engine for Windows Installation
216
| Index
L
Log Files 25
support, contacting xix
Supported Databases 18
Supported Platforms 8
sw_error 25
sw_warn 25
swdefs file 120
O
ODBC Driver Requirements 22
Oracle Database 18
Organization Roles 3
Other TIBCO Product Documentation xiv
P
Performing an Installation in Silent Mode 64
POSIX Threads (pthreads) 9
Post-installation 66
Pre-installation 30
Pre-Installation Tasks 81
Pre-removal Considerations 74
Q
T
technical support xix
Third-Party Documentation xv
TIBCO iProcess Engine Documentation xiv
TIBCO_HOME xvi
TNS Connection Requirements for Oracle 19
Typographical Conventions xvi
U
Uninstalling iProcess Engine 76
Uninstalling TIBCO iProcess Engine 73
Upgrade Performance and Timing 65
Upgrade Requirements 24
Upgrading TIBCO iProcess Engine 65
quick start 143
W
R
Related Documentation xiv
Removing the iProcess Engine Database 79
Removing the iProcess Events COM+ Application 78
Removing the ODBC Data Source 77
S
ScriptName.sql_UserName_TimeStamp.log 26
SQL Server Database 21
TIBCO iProcess Engine for Windows Installation
Windows Clustering 12
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