Interstage Business Process Manager Installation CentraSite administration This Manual Contains Here...

Interstage Business Process Manager Version 7.4

Installation Guide for the Advanced Edition

Publication Date June 2007

Trademarks Interstage is a registered trademark of Fujitsu Limited. i-Flow is a registered trademark of Fujitsu Computer Systems Corporation.

ARIS is a registered trademark of IDS Scheer AG, Saarbruecken.

Microsoft, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries.

UNIX is a registered trademark of the Open Group in the United States and in other countries.

Java, all Java-based trademarks and Solaris are trademarks of Sun Microsystems, Inc. in the U.S. or other countries.

All other trademarks and trade names mentioned have been registered by their respective manufacturer.

Copyright © FUJITSU LIMITED 2005-2007

All rights reserved, including those of translation into other languages. No part of this manual may be reproduced in any form whatsoever by means of photocopying, microfilming or any other process without the written permission of Fujitsu Limited.

[High Risk Activity]

The Customer acknowledges and agrees that the Product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured as contemplated for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical damage or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. The Customer shall not use the Product without securing the sufficient safety required for the High Safety Required Use. In addition, Fujitsu (or other affiliate's name) shall not be liable against the Customer and/or any third party for any claims or damages arising in connection with the High Safety Required Use of the Product.

All Rights Reserved, Copyright (C) FUJITSU LIMITED 2005-2006

Interstage Business Process Manager Installation Guide for the Advanced Edition iii

About this Manual

This manual describes how to configure the environment and install Interstage Business Process Manager (Interstage BPM).

Intended Audience

This manual is intended for system administrators. It assumes that the reader has a working knowledge of

• Windows® 2000 Server and/or Windows Server™ 2003 administration • Microsoft® SQL Server administration • Oracle administration • Microsoft® Active Directory administration • Sun Java System Directory Server administration • CentraSite administration

This Manual Contains

Here is a list of what is in this manual:

Chapter Title Description

1 System Configurations

Description of the typical system configurations for the installation of Interstage Business Process Manager

2 System Requirements

Hardware and software required to use Interstage Business Process Manager.

3 Installation Steps to install and configure Interstage Business Process Manager.

4 Setting Up a Directory Service

Steps to install and configure a Directory Service for Interstage Business Process Manager.

Appendix A Security Description of security modes and of the configuration of Interstage Business Process Manager in a firewall environment.

Appendix B Silent Mode Installation

Steps to install Interstage Business Process Manager non-interactive with an installation script.

iv Interstage Business Process Manager Installation Guide for the Advanced Edition

Appendix C Troubleshooting Description of the Interstage Business Process Manager log files and specific error situations and troubleshooting information.

Typographical Conventions

The following conventions are used throughout this manual:

Example Meaning

command Text, which you are required to type at a command line, is identified by Arial Narrow font.

screen text Text, which is visible in the user interface, is bold.

Reference Reference material is in italics.

Parameter A command parameter is identified by Arial Narrow font.

Other References

The following references for Interstage Business Process Manager are also available:

Release Notes

Contains an overview of Interstage Business Process Manager, installation tips, and late-breaking information that could not make it into the manuals.

Interstage Business Process Manager Administration Guide

Describes how to configure and administrate Interstage Business Process Manager. This guide contains the descriptions of the parameters of the ibpm.properties file.

Interstage Business Process Manager Developer's Guide

Describes how to use the Interstage Business Process Manager API to customize and extend Interstage BPM to fit the unique needs of your organization.

Interstage Business Process Manager User's Guide

Explains how to use the Interstage Business Process Manager client user interfaces.

Interstage Business Process Manager ARIS Process Performance Manager Integration Guide

Interstage Business Process Manager Installation Guide for the Advanced Edition v

Describes how to install and configure the PPM adapter and the PPM autoConfig tool. With both programs, process data can be transferred from Interstage Business Process Manager to ARIS Process Performance Manager.

API Javadoc Documentation

This HTML documentation provides the API and syntax of the packages, interfaces and classes for developing custom applications or embedding Interstage Business Process Manager into other products.

Abbreviations

The products described in this manual are abbreviated as follows:

• "Interstage Business Process Manager" is abbreviated as "Interstage BPM". • "Microsoft® Windows® 2000 Server" is abbreviated as "Windows 2000® Server". • "Microsoft® Windows Server™ 2003" is abbreviated as "Windows Server™ 2003". • "Microsoft® Active Directory" is abbreviated as "Active Directory". • "Solaris ™ Operating System" is abbreviated as "Solaris".

vi Interstage Business Process Manager Installation Guide for the Advanced Edition

Table of Contents

About this Manual ......................................................................................................... iii Intended Audience...................................................................................................................................... iii This Manual Contains ................................................................................................................................ iii Typographical Conventions.........................................................................................................................iv Other References .........................................................................................................................................iv Abbreviations ...............................................................................................................................................v

Table of Contents............................................................................................................vi

Table of Figures ........................................................................................................... viii

1 System Configurations ............................................................................................1

2 System Requirements ..............................................................................................4 2.1 Minimum Software Requirements for Server on Windows ...........................................................4 2.2 Minimum Software Requirements for Server on Solaris ...............................................................4 2.3 Minimum Software Requirements for Server on Linux.................................................................5 2.4 Minimum Software Requirements for Clients ...............................................................................5 2.5 Minimum Hardware Requirements for Server on Windows or Linux ...........................................6 2.6 Minimum Hardware Requirements for Server on Solaris ..............................................................7 2.7 Minimum Hardware Requirements for Clients ..............................................................................7 2.8 Development Environment ............................................................................................................8

3 Installation................................................................................................................9 3.1 Installation Procedure.....................................................................................................................9 3.2 Installation Worksheet .................................................................................................................10 3.3 Database Server Configuration ....................................................................................................12

3.3.1 Microsoft® SQL Server ..........................................................................................................12 3.3.2 Oracle ......................................................................................................................................14 3.3.3 Sybase .....................................................................................................................................15 3.3.4 Starting the Database Server ...................................................................................................15

3.4 Interstage Business Process Manager Installation........................................................................15 3.4.1 Server Installation....................................................................................................................17 3.4.2 Directory Service Installation..................................................................................................22 3.4.3 External Systems Installation and Authentication...................................................................26 3.4.4 Database Installation ...............................................................................................................30 3.4.5 Database Configuration...........................................................................................................49 3.4.6 Final Installation Steps ............................................................................................................50 3.4.7 Pre-Installation Summary........................................................................................................52

3.5 User Accounts and Roles .............................................................................................................55 3.5.1 Automate Interstage Business Process Manager Account Creation ........................................56 3.5.2 Creating User Accounts for the Template Library ..................................................................58

3.6 Load the Interstage Business Process Manager Clients ...............................................................59 3.7 Uninstalling Interstage Business Process Manager......................................................................60 3.8 Upgrading Interstage Business Process Manager from Previous Versions..................................61

4 Setting Up a Directory Service .............................................................................63 4.1 Setting Up Microsoft® Active Directory .....................................................................................63

4.1.1 Granting Schema Update Permission on Windows® 2000 Server..........................................64 4.1.2 Importing the iFlowADAdd.ldif File............................................................................................65

Interstage Business Process Manager Installation Guide for the Advanced Edition vii

4.1.3 Using Existing Active Directory Users and Groups................................................................66 4.1.4 Add New Users .......................................................................................................................67 4.1.5 Add New Groups.....................................................................................................................71 4.1.6 Add Members to a User Group ...............................................................................................73 4.1.7 Active Directory Group Caching.............................................................................................76

4.2 Setting Up Sun Java System Directory Server .............................................................................77 4.2.1 Starting the Sun Java System Directory Server.......................................................................78 4.2.2 Importing the iFlowLDAPAdd.ldif File ........................................................................................78 4.2.3 Using Existing Sun Java System Directory Server Users and Groups ....................................81 4.2.4 Add New Users .......................................................................................................................81 4.2.5 Add New Groups and Members to a Group ............................................................................84 4.2.6 Set User Permissions for Interstage Business Process Manager’s Login Name......................87 4.2.7 iPlanet Group Caching ............................................................................................................90

4.3 Setting Up CentraSite...................................................................................................................91 4.3.1 Automate Account Creation ....................................................................................................93 4.3.2 Add New Users .......................................................................................................................96 4.3.3 Set User Permissions ...............................................................................................................98 4.3.4 Add New Groups...................................................................................................................100

Appendix A Security ...................................................................................................102 Demo Mode..............................................................................................................................................102 Security Mode ..........................................................................................................................................102 Setting Up Security Mode ........................................................................................................................102 Deploying Interstage Business Process Manager in a Firewall Environment ..........................................103 Configuring SMTP Authentication for Use with Interstage Business Process Manager..........................103 Password Encryption................................................................................................................................104

Appendix B Silent Mode Installation.........................................................................107 How It Works ...........................................................................................................................................107 Setting Up an Interstage Business Process Manager Silent Mode Installation.........................................107 Installing Interstage Business Process Manager in Silent Mode ..............................................................109

Appendix C Troubleshooting .....................................................................................111 Log File Information ................................................................................................................................111 Resolving Specific Error Situations .........................................................................................................111

Interstage BPM Server Fails to Start ...................................................................................................111 Error in IBPMServer.log .....................................................................................................................112

Errors During Installation and Configuration...........................................................................................112 Errors during Starting the Interstage BPM Server....................................................................................114 Errors during Using the Administration Facility ......................................................................................114 Contacting Your Local Fujitsu Support Organization..............................................................................115

Index .............................................................................................................................116

Interstage Business Process Manager Installation Guide for the Advanced Edition viii

Table of Figures

Figure 1-1: All systems are installed on the same machine ..........................................................................1 Figure 1-2: Interstage BPM and the database are installed on remote machines........................................2 Figure 1-3: Interstage BPM Server and Interstage BPM Clients are installed on different machines.........3

Figure 3-1: Interstage Business Process Manager Installation Directory Screen .....................................17 Figure 3-2: Installation Action Screen........................................................................................................18 Figure 3-3: Interstage Business Process Manager Components Screen ....................................................19 Figure 3-4: Interstage Business Process Manager Host Information Screen.............................................20 Figure 3-5: Mail Server (SMTP) Host Information Screen ........................................................................21 Figure 3-6: Directory Service Screen .........................................................................................................22 Figure 3-7: LDAP Configuration Settings Screen ......................................................................................23 Figure 3-8: Active Directory Configuration Settings Screen......................................................................24 Figure 3-9: URM Configuration Settings Screen........................................................................................25 Figure 3-10: Login Information Screen ......................................................................................................26 Figure 3-11: Document Management System (DMS) Directory Screen .....................................................27 Figure 3-12: Repository and Registry Integration Settings Screen ............................................................28 Figure 3-13: Database Type Screen ...........................................................................................................30 Figure 3-14: Microsoft SQL Server JDBC Driver Screen ..........................................................................31 Figure 3-15: Microsoft SQL Server 2005 JDBC Driver Screen .................................................................31 Figure 3-16: Microsoft SQL Server Driver Cannot Be Found Screen........................................................32 Figure 3-17: Microsoft SQL Server Instance Screen ..................................................................................33 Figure 3-18: Microsoft SQL Server Non-Administrative Account Screen ..................................................34 Figure 3-19: Microsoft SQL Server Administrative Account Screen ..........................................................35 Figure 3-20: MS SQL Server Data Directory Screen .................................................................................36 Figure 3-21: Oracle JDBC Driver Screen ..................................................................................................37 Figure 3-22: Database Driver Cannot Be Found Screen ...........................................................................38 Figure 3-23: Oracle Instance Screen..........................................................................................................39 Figure 3-24: Oracle Non-Administrative Account Screen..........................................................................40 Figure 3-25: Oracle Administrator Information Screen .............................................................................41 Figure 3-26: Oracle Installation Directory Screen ....................................................................................42 Figure 3-27: Sybase JDBC Driver Screen ..................................................................................................43 Figure 3-28: Database Driver Cannot Be Found Screen ...........................................................................44 Figure 3-29: Sybase Server Information Screen.........................................................................................45 Figure 3-30: Sybase Non-Administrative Account Screen..........................................................................46 Figure 3-31: Sybase Database Server Administrative Account Screen ......................................................47

Interstage Business Process Manager Installation Guide for the Advanced Edition ix

Figure 3-32: Sybase Installation Directory Screen ....................................................................................48 Figure 3-33: Database Configuration Screen.............................................................................................49 Figure 3-34: Java Development Kit (JDK) Location Screen ......................................................................50 Figure 3-35: Interstage Business Process Manger Administrator’s E- mail Address Screen.....................51 Figure 3-36: Pre-Installation Summary Screen..........................................................................................52 Figure 3-37: Start Interstage Business Process Manager Services Screen ................................................53 Figure 3-38: Please read the summary information below Screen.............................................................54

Figure 4-1: New Object – User window.....................................................................................................69 Figure 4-2: New Object – User dialog........................................................................................................70 Figure 4-3: New Object – User dialog........................................................................................................71 Figure 4-4: New Object – Group window ..................................................................................................72 Figure 4-5: Role Properties window ..........................................................................................................74 Figure 4-6: Select Users, Contacts, Computers, or Groups box ................................................................75 Figure 4-7: Select Users, Contacts, or Computers box ..............................................................................75 Figure 4-8: Role Properties box .................................................................................................................76 Figure 4-9: Servers and Applications tab ...................................................................................................79 Figure 4-10: Tasks tab ................................................................................................................................80 Figure 4-11: Import Databases dialog........................................................................................................80 Figure 4-12: Directory tab..........................................................................................................................82 Figure 4-13: New Object dialog .................................................................................................................83 Figure 4-14: Create New User dialog.........................................................................................................83 Figure 4-15: Directory tab..........................................................................................................................85 Figure 4-16: Create New Group dialog......................................................................................................85 Figure 4-17: Static Group tab.....................................................................................................................86 Figure 4-18: Search users and groups dialog.............................................................................................87 Figure 4-19: Directory tab..........................................................................................................................88 Figure 4-20: Set Permission dialog ............................................................................................................88 Figure 4-21: Search users and groups dialog.............................................................................................89 Figure 4-22: Set Permission dialog ............................................................................................................90 Figure 4-23: Create User dialog.................................................................................................................97 Figure 4-24: Role Management dialog .......................................................................................................98 Figure 4-25: Create Role dialog .................................................................................................................99 Figure 4-26: Group Management dialog ..................................................................................................100 Figure 4-27: Create Group dialog ............................................................................................................101

Interstage Business Process Manager Installation Guide for the Advanced Edition 1


Interstage Business Process Manager (Interstage BPM) is a server-based workflow engine with APIs (Application Programming Interfaces) for workflow application development. The Interstage BPM Server operates with a database and a Directory Service. For Interstage BPM are two clients available: the Interstage BPM Console and the Administration Facility.

Three system configurations are typically used. The decision, which configuration is to be used, depends on the desired performance of the employed systems.

Minimum Configuration: All systems are installed on the same machine

It is possible to install the Interstage BPM Server, the Interstage BPM Clients, the database and the Directory Service on the same machine. With the Web Browser you can load the Interstage BPM Console or the Administration Facility and work with the Interstage BPM Server.

Customer applications can be built with the Model API .The Model API is an abstraction over the server and provides a single unified API to the server. It runs in the client process, and handles all the communications to the server. For more information about the architecture of Interstage BPM refer to the Interstage Business Process Manager Administration Guide.

Figure 1-1: All systems are installed on the same machine



System configuration 2: Database and Directory Service are installed on remote machines

The Interstage BPM Server and the Interstage BPM Clients are installed on a machine; the database and the Directory Service are installed on remote machines. With the Web Browser you can load the Interstage BPM Clients and work with the Interstage BPM Server. Refer to the Interstage Business Process Manager Components Screen for more information about the installation of the Interstage BPM Server and the Interstage BPM Clients on the same machine.

Figure 1-2: Interstage BPM and the database are installed on remote machines


3 Interstage Business Process Manager Installation Guide for the Advanced Edition

System configuration 3: Interstage BPM Server and Interstage BPM Clients are installed on different machnines

The Interstage BPM Server and the Interstage BPM Clients are installed on different machines; the database and the Directory Service are installed on remote machines. With the Web Browser you can load the Interstage BPM Clients and work with the Interstage BPM Server. Refer to the Interstage Business Process Manager Components Screen for more information about the installation of the Interstage BPM Server and the Interstage BPM Clients on the same machine.

Figure 1-3: Interstage BPM Server and Interstage BPM Clients are installed on different machines



2.1 Minimum Software Requirements for Server on Windows

Operating System

Microsoft® Windows Server™ 2003 Standard Edition / Enterprise Edition SP1

Microsoft® Windows® 2000 Server / Advanced Server SP4

Database

Microsoft® SQL Server 2000 Standard Edition / Enterprise Edition SP4

Oracle 9i R9.2.0 Standard Edition / Enterprise Edition

Sybase 12.5.3

DB2 V8.2

Directory

Microsoft® Windows® 2000/2003 Native Directory

Microsoft® Active Directory (bundled in Windows® 2000 Server or Windows Server™ 2003)

CentraSite 1.2

Sun One V5.1

Java Environment

J2SE Development Kit (JDK) 1.4.2_10 / 5.0 Update 5

2.2 Minimum Software Requirements for Server on Solaris

Operating System

Solaris ™ Operating System 9 on SPARC based systems

Database


Sybase 12.5.3



DB2 V8.2

Directory

Sun Java System Directory Server 5.1

CentraSite 1.2

Sun One V5.1

Java Environment


2.3 Minimum Software Requirements for Server on Linux

Operating System

RedHat Linux ES 4.0

Database


Sybase 12.5.3

DB2 V8.2

Directory

Sun Java System Directory Server 5.1

CentraSite 1.2

Sun One V5.1

Java Environment


2.4 Minimum Software Requirements for Clients

Web Browser

Microsoft® Internet Explorer 6.1 SP1

Operating System

Microsoft® Windows XP Professional SP2



Microsoft® Windows Server™ 2003 Standard Edition / Enterprise Edition SP1

Microsoft® Windows® 2000 Professional / Server / Advanced Server SP4

Note: If you want to use Netscape 8.x on UNIX or Linux, please contact your local Fujitsu support organization.

2.5 Minimum Hardware Requirements for Server on Windows or Linux

Machine

Fujitsu PRIMERGY or other Intel Architecture server

Processor

Pentium III, 1 GHz, 1 CPU (recommended: Pentium III, 2 GHz, 2 CPU or greater)

Memory

1 GB (recommended: 2 GB or more)

Hard Drive

Recommended: 8 GB of free space during runtime (Please refer the calculation method below)

Interstage BPM installation: 200 MB

Log file space: You need sufficient disk space for log files.

Microsoft® SQL Server installation: Please refer to the product documentation.

Oracle installation: Please refer to the product documentation.

Database space: As a rule of thumb, 1000 instances of a process definition with 10 nodes require about 5 MB. During Interstage BPM runtime, the processing of work items, history entries in the database, etc., require additional space besides the initial database size. This additional space depends on 1) the number of process instances 2) the number of active nodes 3) the number of users who are assigned to work items. For example, if you have 1000 instances of a process with 10 nodes, 50% of the nodes require parallel processing (e.g. OR nodes), 10 users are accessing the process instances, you need the following disk space at runtime: 1500 active nodes multiplied with 10 users: 15.000 KB or 15 MB



2.6 Minimum Hardware Requirements for Server on Solaris

Machine

Fujitsu PRIMEPOWER or other SPARC server

Processor

Ultra SPARC or SPARC64 V (kernel arch: sun4u/sun4us/sun4d) 1 GHz, 1 CPU (recommended: Ultra SPARC/SPARC64V 1.2GHz, 2CPU or greater)

Memory

1 GB (recommended: 2 GB or more)

Hard Drive

Recommended: 8 GB of free space during runtime. (Please refer the calculation method in the previous section.)

2.7 Minimum Hardware Requirements for Clients

Machine

Fujitsu DESKPOWER, ESPRIMO, SCENIC, SCALEO, Stylistic, Lifebook, AMILO, CELCIUS, PRIMERGY or other Windows PC / Intel Architecture server

Processor

Pentium III 500 MHz or greater

Memory

512 MB or more



2.8 Development Environment

Development Environment



3 Installation

The Interstage BPM installer automates the installation process and creates the configuration file ibpm.properties. When you want to change an Interstage BPM configuration parameter, you do not necessarily have to go through the entire installation process again. You can change your configuration by following the instructions described in the Interstage Business Process Manager Administration Guide.

Refer to Chapter 2, "System Requirements", on page 4 for details on the required components mentioned in the procedures described in this chapter.

3.1 Installation Procedure

Note: Installation of Interstage BPM is a short, smooth process if you know all of the values for the parameters that the installer needs. It is recommended that you take the time to fill out the Installation Worksheet on page 10 before starting the installation process.

In order to install Interstage BPM, complete the following steps in the recommended order:

1. Make sure that the database server is running. Refer to section "Database Server Configuration" on page 12.

2. Install Interstage BPM. Refer to section "Interstage Business Process Manager Installation" on page 15.

Note: The Apache Tomcat Web Server 5.0 is installed and used as the Interstage BPM Web Server when you choose the Interstage Business Process Manager Clients option in the Interstage Business Process Manager Components screen.

3. Set up Interstage BPM user accounts and Roles. Refer to section "User Accounts and Roles" on page 55.

4. Load the Interstage BPM Console. Refer to section "Load the Interstage Business Process Manager Clients" on page 59.

Note: To connect to a Directory Server (except for the default Interstage BPM user created during installation), you must configure the Directory Server before you start running Interstage BPM services. Refer to Chapter 4 "Setting Up a Directory Service" on page 63 for details.

3 Installation


3.2 Installation Worksheet

During the course of the installation you will be asked to enter values for a number of parameters. To ensure a smooth and easy installation, it is recommended that you fill out the following worksheet before beginning the installation.

Database Parameters

Database Server host name or IP address of the server that hosts the database instance

Database SID (Instance name on Microsoft® SQL Server, DB2, or Sybase)

Database Name

Database Port # Oracle default: 1521 Microsoft® SQL Server default: 1433 DB2 default: 50000 Sybase default : 5000

Database Top-Level Directory*

Database Directory*

Database Non-Administrative user name Database Non-Administrative password

Database Administrator user name * Oracle default: system Microsoft® SQL Server, Sybase, and DB2 default: sa

Database Administrator password*

Database JDBC Driver Location (Oracle Default (localhost): C:\Oracle\jjdbc\bin Microsoft SQL Server Default (localhost): C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib Sybase Default (localhost): C:\Sybase\Connect-5_5\classes\jconn2.jar DB2 Default (localhost): C:\IBM\SQLLIB\java (Windows) /opt/IBM/java (Solaris) db2java.zip, db2jcc.jar, and db2jcc_license_cu.jar

* Information is not needed if the database has already been installed remotely.

Directory Server Configuration (Only Needed if installing LDAP, Active Directory or CentraSite)

Directory Server host name or IP address

3 Installation


Directory Server Configuration (Only Needed if installing LDAP, Active Directory or CentraSite)

(local or remote)

Directory Server port number Default is 389 (not the admin port #)*

Directory Server directory search string* (Example: dc=mycompany, dc=com) This is the directory search string.

URM Configuration File URM Admin User Name URM Admin Password

URM Domain Name

*Information is not needed if the directory service has already been installed remotely.

Interstage BPM Server Configuration

Interstage BPM Server directory Default is C:\Fujitsu\InterstageBPM on Windows, /opt/FJSVibpm on UNIX or Linux.

Location of the J2SE Development Kit (JDK) Installation (top-level) directory.

SMTP server host name

Interstage BPM Administrator’s email address (can be any active email address )

Note: Consult your system Administrator and your email Administrator for the correct host names, since the Interstage BPM Server will not start if the SMTP server host name is incorrect. If you are in doubt, leave this field blank and edit the ibpm.properties file later. Refer to the Interstage Business Process Manager Administration Guide for details. If you do not enter a SMTP server host name, Interstage BPM’s email notification feature will be disabled.

Interstage BPM Clients Configuration

Location of the J2SE Development Kit (JDK) Installation (top-level) directory.

3 Installation


Interstage BPM Server host name. Interstage BPM Clients directory.

UDDI and WebDAV Server Configuration

URL for UDDI Registry.

URL for WebDAV Repository. Publish URL. Business Entity.

3.3 Database Server Configuration

This section provides instructions in configuring your database software for use by Interstage BPM.

You must create a new database instance for Interstage BPM. During installation, you will specify this instance. These installation instructions use the default database instance for the purpose of providing an example. For example, the default database instance for Microsoft® SQL Server is represented by a <blank>. The default database instance for Oracle is orcl.

3.3.1 Microsoft® SQL Server

Microsoft® SQL Server 2000 or 2005 Standard Edition or Enterprise Edition can be used as the database with Interstage BPM.

Observe the Following:

1. Confirm that TCP/IP is selected under Network Operations.

2. Make sure that you install Microsoft® SQL Server in Mixed Mode. Microsoft® SQL Server in Mixed Mode allows Windows Authentication, i.e. a Windows user can log in to the database, and Microsoft® SQL Server Authentication, i.e. a user needs a user name and a password for the database.

Note: If Microsoft® SQL Server is already installed, you may have to run the setup program again if the default selection from the prior installation enabled Named Pipes. Run the Microsoft® SQL Server setup again and add TCP/IP. However, do not disable Named Pipes. Both must be selected.

3 Installation


3. Confirm that the port number for TCP/IP is set to 1433.

4. If you are using Microsoft SQL Server 2000, install the SQL Server 2000 Driver for JDBC. If you are using Microsoft SQL Server 2005, install the SQL Server 2005 Driver for JDBC.

Microsoft does not provide a JDBC driver with Microsoft SQL Server, so you must obtain the latest service pack of the SQL Server Driver for JDBC from the Microsoft Web Site and install it using the instructions provided on the download page.

NOTE: There are different driver installation instructions for UNIX or Linux than there are for Windows.

For Microsoft SQL Server 2000: The default installation location on Windows is:

C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib If you performed a default installation of the JDBC Driver, this is the location (PATH) that you should enter in the text field. On UNIX or Linux, you designate a location to which the driver will be installed when you install the driver. The location that you designate during the installation of Interstage BPM will be the following:

<location specified during driver installation>/lib. Enter the path to the lib directory of the database driver in the MSSQL JDBC Driver Path field or click Browse and navigate to it. The lib directory should have the following three files in it: msbase.jar, mssqlserver.jar, and msutil.jar. These are the actual driver.

If you are an advanced user of Interstage BPM and want to move these files to a different location, you may. However, all three of these files must be in the same directory, and you must specify that directory in the MSSQL JDBC Driver Path field.

For Microsoft SQL Server 2005: The Microsoft SQL Server 2005 JDBC Driver is installed using a self-extracting zip file. It is recommended that you unzip this file to a root directory on your machine, typically your C drive. If unzip the file to your C drive, you will know that sqljdbc.jar, the JDBC Driver file, will be located in the C:\sqljdbc_1.1\enu directory.

Enter the path to the sqljdbc.jar file in the MSSQL JDBC Driver Path field or click Browse and navigate to it. This JAR file is the actual driver.

If you are an advanced user of Interstage BPM and want to move this file to a different location, you may. However, you must specify that directory in the MSSQL JDBC Driver Path field.

3 Installation


Running Your Database on a Remote Host

To configure your database to run on a remote host, run the Interstage BPM installer on the remote database host before installing Interstage BPM on the Interstage BPM host. Choose the Configure Interstage Business Process Manager Database Server option in the Installation Action screen. This procedure creates the Interstage BPM tables in the remote database.

Next, you need to install Interstage BPM on the local machine and copy the Microsoft SQL Server JDBC driver, msbase.jar, mssqlserver.jar, and msutil.jar located in the C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib directory, to your local machine. It is suggested that you create a directory with an identifiable name because you must specify the location of the driver during the installation of Interstage BPM.

3.3.2 Oracle

Observe the Following:

• Create a new database instance for Interstage BPM. During installation, you will specify this instance. These installation instructions use the default database instance for the purpose of providing an example. The default database instance for Oracle is orcl.

• See the Oracle documentation for instructions on how to install it.

• The Oracle JDBC driver requires a TCP/IP version of Oracle's SQL*Net. This is the default for a standard installation. The port number for TCP/IP must be 1521.

• If you need to uninstall Oracle or require recovery from a failed installation, contact Oracle Technical Support for instructions before reinstalling.


To configure Oracle to run on a remote host, run the Interstage BPM installer on the remote database host before installing Interstage BPM on the Interstage BPM host. Choose the Configure Interstage Business Process Manager Database Server option in the Installation Action screen. This procedure creates the Interstage BPM tables in the remote database.

Next, you need to install Interstage BPM on the local machine. Copy the Oracle JDBC driver (the classes12.zip file, typically located in the <ORACLE_ROOT>\jdbc\lib directory) to the local machine into the <Interstage BPM installation directory>/lib directory (and to the <Interstage BPM installation directory>/taskmanager/iflowreport/WEB-INF/lib directory if are using the Interstage Business Process Manager Clients). If you are installing Interstage BPM on a UNIX or Linux platform, you must also change the file permission of classes12.zip to 110110110 in both directories into which you copied the driver file.

3 Installation


3.3.3 Sybase

The user performing the installation must have full administration privileges on the computer upon which you are installing Interstage BPM.

For any other purpose than demonstration of the software, Fujitsu Computer Systems Corporation recommends that you configure the database to grow automatically. For instructions, see the Sybase Adaptive Server Administration documentation. The procedure is called the sp_dbextend procedure for "Automation database expansion." It involves the running of a script file.


To configure Sybase to run on a remote host, run the Interstage BPM installer on the remote database host before installing Interstage BPM on the Interstage BPM host. Choose the Configure Interstage Business Process Manager Database Server option in the Installation Action screen. This procedure creates the Interstage BPM tables in the remote database.

Next, you need to install Interstage BPM on the local machine and copy the Sybase JDBC driver (jconn2.jar located in the <SYBASE_ROOT>\jConnect-5_5\classes directory on Windows, $SYBASE_ROOT/jConnect-5_5/classes on UNIX or Linux to your local machine. It is suggested that you create a directory with an identifiable name because you must specify the location of the driver during the installation of Interstage BPM.

3.3.4 Starting the Database Server

Since configuration information must be written to the database during installation, ensure that the database server is running prior to installing Interstage BPM. Start the database server according to the documentation provided with your database server.

3.4 Interstage Business Process Manager Installation

It is recommended that you close all other applications prior to installation.

To connect to the Directory Service and log into Interstage BPM, you must configure and start the Directory Service before starting Interstage BPM. The best time for configuration is after installing Interstage BPM and before you start the Interstage BPM Server, because the Interstage BPM installer installs an Interstage BPM LDIF file that you need to import into the Directory Server.

Note: If you install Interstage BPM on a laptop that is periodically disconnected from the network, your laptop’s DHCP lease may expire while you are off line. If this happens, TCP/IP (and therefore Interstage BPM) will cease functioning. Therefore, you should use a static IP address for the laptop.

Database and/or Directory Server on Remote Machines

3 Installation


To increase performance, you may wish to install certain Interstage BPM components like the database and/or the Directory Server on remote machines (i.e., not on the Interstage BPM Server machine). If you install the database server on a remote machine, you need to run the Interstage BPM installer twice:

1. After the remote database has been installed and started, you must run the Interstage BPM installer on the remote database server machine and configure the Interstage BPM Database Server. You need to select in the Installation Action screen the Configure Interstage Business Process Manager Database Server option.

Next, you need to install Interstage BPM on the local machine. If you are using a remote database, copy the database JDBC driver to the local machine. See the Database Server Configuration section for instructions. Select the Install Interstage Business Process Manager Software Components option in the Installation Action screen.

Proceed as follows to install Interstage BPM:

For installing Interstage BPM on UNIX or Linux, log in as root.

Note: If you have a previous version of Interstage BPM on your machine, refer to section "Upgrading Interstage Business Process Manager from Previous Versions" on page 61.

1. Read the Release Notes located in the top directory of the CD-ROM.

2. Run setupwin32.exe in the top directory on the CD-ROM to install Interstage BPM on Windows. Run setupSolaris.bin in the top directory on the CD-ROM to install Interstage BPM on Solaris. Run setupLinux.bin in the top directory on the CD-ROM to install Interstage BPM on Linux.

3. Read the Welcome screen and click Next.

4. Read the license agreement and click the Accept radio button if you accept the agreement. Then, click Next. You must accept the license agreement to continue with the installation.

3 Installation


3.4.1 Server Installation

Figure 3-1: Interstage Business Process Manager Installation Directory Screen

Accept the default or click Browse and navigate to the directory where the Interstage BPM Server components are to be installed.

On UNIX and Linux, the default installation directory is opt/FJSVibpm.

Click Next to continue.

3 Installation


Figure 3-2: Installation Action Screen

You have two options:

A. Select Configure Interstage Business Process Manager Database Server, if you are installing the Interstage BPM database on a remote server (i.e., not on the Interstage BPM Server machine) and skip to the Database Installation section of these instructions. In this case, you must run the Interstage BPM installer using this option on the remote database server before installing Interstage BPM on the local machine. This creates the tables that Interstage BPM needs. When you finish configuring the remote Interstage BPM database server, return to the local host and run the Interstage BPM Server installation. When you get to this step (on the second pass through), proceed with sub-step B instead.

If your database is running on a remote host, the installation program will skip the database steps involved with configuring the database because it doesn’t need to install the database. These two skipped steps are marked with a special note in the Database Installation section.

B. If your database is running on the local machine (i.e., the Interstage BPM Server), or if the database is running on a remote host and you have already configured that database using the Interstage BPM installer as described in sub-step A above, select Install Interstage Business Process Manager Software Components to install Interstage BPM. Click Next to continue.

3 Installation


Figure 3-3: Interstage Business Process Manager Components Screen

You can install the Interstage BPM Server and the Interstage BPM Clients by selecting both the Interstage Business Process Manager Server and the Interstage Business Process Manager Clients checkboxes. Selecting both checkboxes is recommended because in this way the complete Interstage BPM package will be installed and it is ensured that you will have the complete Interstage BPM functionality.

If you want to install only the Interstage BPM Server, select only the Interstage Business Process Manager Server checkbox. If you choose this option, the Interstage BPM Console, Administration Facility and Client Listener will be unavailable. The step where you specify your top-level JDK directory will be skipped.

If you want to install only the Interstage BPM Clients, select only the Interstage Business Process Manager Clients checkbox. If you choose this option, only the Interstage BPM Console with the Administration Facility and Client Listeners will be available. The installation of the Interstage BPM Server will be skipped. Proceed directly to the Database Installation section. Also, the installation program will skip the database steps involved with configuring the database because it doesn’t need to install the database. These two steps are marked with notes in the database section.

Click Next to advance to the next screen.

3 Installation


Figure 3-4: Interstage Business Process Manager Host Information Screen

Note: This screen will appear if you are installing Interstage BPM on the UNIX or Linux operating systems. It will also appear if you are installing only the Interstage BPM Client.

Enter the name of the computer on which you installed the Interstage BPM Server.

Click Next to proceed to the next screen.

3 Installation


Figure 3-5: Mail Server (SMTP) Host Information Screen

Enter your site’s SMTP mail delivery service in the Mail Server (SMTP) Host field.

Click Next to proceed to the next screen.

3 Installation


3.4.2 Directory Service Installation

Figure 3-6: Directory Service Screen

Note: Like the database, the Directory Server can be installed on a remote host. The NT Native Directory Service Adapter, however, must be installed on the local Interstage BPM Server host. Also, the NT Native Directory Service Adapter is not available on UNIX or Linux.

If you selected NT Native Directory Service Adapter the installation program uses special utilities to create a user, a Group and a Role. Refer to section "Directory Service Modification During Installation" on page 56 for details. If you selected the NT Native Directory Service Adapter, proceed with the External Systems Installation and Authentication section.

Select LDAP Directory Service Adapter if you use as Directory Service Sun Java System Directory Server 5.1 on UNIX or Linux. Select Microsoft Active Directory Service Adapter if you use Active Directory as your directory service. Note that Active Directory runs only on Windows.

Select Centrasite User Role Management Directory Adapter if you use Centrasite as your directory management service.

Select the type of Directory Service adapter you wish to use. The next appearing screen depends on the selected option. Click Next to continue.

3 Installation


Figure 3-7: LDAP Configuration Settings Screen

You will see this screen next if you selected the LDAP Directory Service Adapter option the LDAP Configuration Settings screen appears.

To properly complete this screen, you must know the installation and configuration information for your Directory Service. You must specify the name of the LDAP Host, the LDAP Key and the LDAP Organizational Unit (OU) used by your organization. Consult your Directory Server Administrator to obtain the correct keys for the hierarchy search string. Refer to section "Using Existing Active Directory Users and Groups" on page 66 for more information how to configure the LDAP Server.

Click Next to continue. You will proceed with the External Systems Installation and Authentication section.

3 Installation


Figure 3-8: Active Directory Configuration Settings Screen

You will see this screen next if you selected the Microsoft Active Directory Service Adapter option, the Active Directory Configuration Settings screen appears.

Enter the Active Directory Host, Active Directory Key, and Active Directory Organizational Unit (OU) of the LDAP-based Directory Server for Interstage BPM. Consult your Directory Server Administrator to obtain the correct keys for the hierarchy search string. Refer to section "Using Existing Active Directory Users and Groups" on page 66 for more information how to configure the Active Directory Server.


3 Installation


Figure 3-9: URM Configuration Settings Screen

You will see this screen next if you selected the CentraSite User Role Management Directory Adapter option the URM Configuration Settings screen appears.

Enter the path and name of the URM Configuration File or click Browse to select it. Then, enter the URM Admin Username, URM Admin Password and URM Domain Name in their respective fields. (URM is the abbreviation of User Role Management). Consult your CentraSite Administrator to obtain the correct keys login information.

If you selected CentraSite User Role Management Directory Adapter the installation program uses special utilities to create a user, a Group and a Role. Refer to section "Directory Service Modification During Installation" on page 56 for details.

In addition there is a client program available to add users and Groups in the underlying Directory Server that this component is using. Refer to section "Setting Up CentraSite" on page 91 for details.


3 Installation


3.4.3 External Systems Installation and Authentication

Figure 3-10: Login Information Screen

Note: If you are installing Interstage BPM on UNIX or Linux, the Interstage BPM Administrative User specified on this screen should already be a UNIX or Linux user in the Administrative Group.

Enter a user name and password to specify an Interstage BPM Administrator account∗. The Interstage BPM Directory Service Adapter will use this account to log into the Directory Service.

By default, the user specified in this screen is also used to access the Directory Server. If you are using LDAP, Active Directory, or CentraSite and want to use a different user, you must change the Interstage BPM configuration manually by changing the LDAPAccessUserID and LDAPAccessUserPassword parameters in the ibpm.properties file. Refer to the Interstage Business Process Manager Administration Guide for more information about the parameters in the ibpm.properties file. Click Next to continue.

∗ If the name of an existing user account is specified on this screen, be sure to enter the correct existing password for this account. If you enter a wrong password, the password for the account is changed to the wrong one during the setup of Interstage BPM, and you must use the wrong password. Alternatively you can specify a user name that does not yet exist in the directory. In this case, you can set the password arbitrarily.

3 Installation


Figure 3-11: Document Management System (DMS) Directory Screen

Select a Document Management System (DMS) root directory on the Interstage BPM Server host. This is the directory for attachments and optionally for other documents. The default DMS root directory is C:\Fujitsu\InterstageBPM\attachments. The default DMS root directory on UNIX or Linux is /opt/FJSVibpm/attachments.

Note: The Forms Repository, where Interstage BPM stores all of its HTML forms, is also a DMS root directory. The Forms Repository is automatically created under the Interstage BPM client directory. The path to the Forms Repository is defined in the DMSRoot parameter of the ibpm.properties file. Refer to the Interstage Business Process Manager Administration Guide for more information about the ibpm.properties file.

You can also specify additional DMS root directories after installation by creating the directories and then adding them to the DMSRoot parameter of the ibpm.properties file and adding an entry to the DMSCollections.xml file. This file can be found in the Interstage BPM bin directory. Detailed instructions for adding a DMS Directory can be found in the Interstage Business Process Manager Administration Guide.


3 Installation


Figure 3-12: Repository and Registry Integration Settings Screen

This screen prompts for repository and registry integration settings. Interstage BPM can be integrated with any WebDAV-compliant repository or UDDI-compliant registry. However, the examples used below are for CentraSite.

If you do not know the settings for your particular WebDAV-compliant repository or UDDI-compliant registry, see your System Administrator and the instructions for using your WebDAV or UDDI software.

Note: You must have a WebDAV-compliant repository installed and configured for use with Interstage BPM to publish metadata to it. The same requirement applies to a UDDI-compliant registry to which you want to publish information or search. Also, you must check the checkbox for a particular integration type to activate that integration feature.

If you want to publish metadata to a WebDAV repository, check the Publish Metadata to a WebDAV Repository checkbox and enter the following information on this screen:

• Publish Metadata URL (WebDAV): This is the URL to which metadata will be published when an Interstage BPM process definition is published. For CentraSite use the following URL:

3 Installation


http://hostname:80/tamino/IntegrationMetadataRepository/ino:dav/ino:dav/ documents

If you want to publish to a UDDI Registry, check the Publish to UDDI Registry checkbox and enter the following information on this screen:

• UDDI Business Name: This is the name of the business that is publishing process definition information to the UDDI Registry. It is an identifier that helps you to categorize the process definition information added to the UDDI Registry. It makes it easier to search and retrieve the process definitions for Web Services. The business name must be added as a category in order to be able to publish process definitions for example in CentraSite. For CentraSite use your company name.

• UDDI Publish URL: This is the URL to which UDDI Registry information will be published when an Interstage BPM process definition is published. For CentraSite use the following URL: http://hostname:49940/TaminoUddiRegistry/publish

If you want to search a UDDI Registry, check the Search UDDI Registry checkbox and enter the following information on this screen:

• UDDI Search URL: This URL is the UDDI search location. It allows you to search the UDDI Registry using the search registry dialog box that is part of the Web Services Java Action. For CentraSite use the following URL: http://hostname:49940/TaminoUddiRegistry/inquiry


3 Installation


3.4.4 Database Installation

Figure 3-13: Database Type Screen

Select the database adapter type that matches the database server type you wish to use.


3 Installation


Figure 3-14: Microsoft SQL Server JDBC Driver Screen

Figure 3-15: Microsoft SQL Server 2005 JDBC Driver Screen

This set of database screens will appear if you selected the MS SQL 2000 Database Adapter or the MS SQL 2005 Database Adapter on the Database Type screen.

3 Installation


You must provide the location of your database JDBC driver file(s) on this screen. For more information about the drivers to be used, see the 3Microsoft® SQL Server section of this manual.

Note: The actual installation screen for Microsoft SQL Server 2005 notes the version of the Microsoft SQL Server adapter in the title. Different JDBC drivers are used for Microsoft SQL Server 2005 and Microsoft SQL Server 2000.

Figure 3-16: Microsoft SQL Server Driver Cannot Be Found Screen

Note: The actual installation screen for Microsoft SQL Server 2005 notes the version of the Microsoft SQL Server adapter in the title.

If you see this screen, it is either because you have not installed the Database Server JDBC Driver files to your machine as instructed, or you have not specified the correct location of the driver files. If the installation program cannot find these driver files, it will not be able to update or create your database properly. You can obtain these driver files from your software vendor as instructed in the section on setting up your database.

3 Installation


Figure 3-17: Microsoft SQL Server Instance Screen

Note: The actual installation screen notes the version of the Microsoft SQL Server adapter in the title.

To properly complete this screen, you must know the following information (this information can be provided by the Microsoft® SQL Server Administrator):

• Microsoft SQL Server Host: Enter the name of the computer on which you installed Microsoft SQL Server. If this computer does not have a name use its IP address. This information is mandatory. This setting defaults to the name of the local machine. If you are using a remote database, change this setting to the name of the machine containing the remote database, so the database is not installed on this machine.

• Microsoft SQL Server Instance: The default database instance for Microsoft SQL Server is represented by a <blank>.

• Microsoft SQL Server Port: The port number is set to 1433 if you are using the default database instance.

3 Installation


Figure 3-18: Microsoft SQL Server Non-Administrative Account Screen

To properly complete this screen, you must know the following information:

• Microsoft SQL Server Username: Enter the user name for a non-administrative database user account. Interstage BPM will use this account to log into the database.

• Microsoft SQL Server Password: Enter the password for the non-administrative database user account.

• Confirm Microsoft SQL Server Password: Re-enter the password for the non-administrative database user account.

The password that you enter in the Microsoft SQL Server Password field must match the password that you enter in the Confirm Microsoft SQL Server Password field. If they do not match, you will receive a message informing you of this and upon clicking OK, you are returned to this screen, then you can re-enter your password.

When your Microsoft® SQL Server login information is correct, click Next.

If you are configuring a remote database, skip to the Error! Reference source not found. section.

3 Installation


Figure 3-19: Microsoft SQL Server Administrative Account Screen

Note: This screen will not appear if your database does not reside on the local computer. Therefore, it should never appear when installing on UNIX.


• Microsoft SQL Server AdminUser: Enter the user name of the Microsoft® SQL Server Administrator user account.

• Microsoft SQL Server Admin Password: Enter the password for the Microsoft® SQL Server Administrator user account.

When your Microsoft® SQL Server login information is correct, click Next.

3 Installation


Figure 3-20: MS SQL Server Data Directory Screen

In most cases, you can accept the default that appears on this screen. You will need to change this default location only if you are upgrading from a previous version of Interstage BPM, and your Interstage BPM Data Files are in a location other than the location used as a default for Microsoft SQL Server Data Files.

If your Microsoft SQL Server Data Files are in a location other than the default location, you must specify that location in the MS SQL Server Data Directory Path field.

Skip to the 3Database Configuration section.

3 Installation


Figure 3-21: Oracle JDBC Driver Screen

This set of database screens will appear if you selected Oracle 9i or later Database Adapter on the Database Type screen.

You must provide the location of your database JDBC driver on this screen. For more information about the driver, see the 3Oracle section of this manual.

When your JDBC Driver Path is correct, click Next.

3 Installation


Figure 3-22: Database Driver Cannot Be Found Screen


3 Installation


Figure 3-23: Oracle Instance Screen


• Oracle Host: Enter the name of the computer on which you installed Oracle. If this computer does not have a name, use its IP address. This information is mandatory. This setting defaults to the name of the local machine. If you are using a remote database, change this setting to the name of the machine containing the remote database, so the database is not installed on this machine.

• Oracle SID: Enter the SID of the Oracle instance that you are using. The default is orcl. This is the usual value for SID unless you are running multiple instances of Oracle.

• Oracle DB Name: Enter the name of the database instance. You can find the database name in the init.ora file. In Oracle 10g1, the file can be found int the following directory: C:\oracle\product\10.1.0\admin\OraDB\pfile

In Oracle 9, the file can be found int the following directory:

C:\oracle\ora90\admin\OraDB\pfile • Oracle Port: Enter the Oracle port number that you are using. The default is 1521.

This is the usual value for the port number unless you are using this port for another program.

When your Oracle configuration information is complete and correct, click Next.

3 Installation


Figure 3-24: Oracle Non-Administrative Account Screen

To properly complete this screen, you must know the following information (this information can be provided by the Oracle Administrator):

• Oracle Username: Enter the user name for a non-administrative database user account. Interstage BPM will use this account to log into the database.

• Oracle Password: Enter the password for the non-administrative database user account.

• Oracle Confirm Password: Re-enter the password.

The password that you enter in the Oracle Password field must match the password that you enter in the Oracle Confirm Password field. If they do not match, you will receive a message informing you of this and upon clicking OK, you are returned to this screen, then you can re-enter your password.

When your Oracle login information is correct, click Next.

If you are configuring a remote database, skip to the Final Installation Steps section.

3 Installation


Figure 3-25: Oracle Administrator Information Screen

Note: This screen will not appear if your database does not reside on the local computer.


Oracle Admin Username: Enter the user name of the Oracle Administrator user account.

Oracle Admin Password: Enter the password for the Oracle Administrator user account.

When your Oracle login information is correct, click Next.

3 Installation


Figure 3-26: Oracle Installation Directory Screen


Enter the Oracle Root directory and the Oracle DBPath, i.e. the directory in which you want the Interstage BPM database to reside.

Click Next to continue. Skip to the Database Configuration section if your database software is installed on the local machine.


3 Installation


Figure 3-27: Sybase JDBC Driver Screen

This set of database screens will appear if you selected Sybase 12.5.1 Database Adapter on the Database Type screen.

You must provide the location of your database JDBC driver on this screen. For more information about the driver, see the 3Oracle section of this manual.

When your JDBC Driver Path is correct, click Next.

3 Installation


Figure 3-28: Database Driver Cannot Be Found Screen


3 Installation


Figure 3-29: Sybase Server Information Screen

This set of database screens will appear if you selected Sybase 12.5.1 or later Database Adapter on the Database Type screen.


• Sybase Host: Enter the name of the computer on which you installed Sybase. If this computer does not have a name, use its IP address. This information is mandatory. This setting defaults to the name of the local machine. If you are using a remote database, change this setting to the name of the machine containing the remote database, so the database is not installed on this machine.

• Sybase Port: Enter the Sybase port number that you are using. The default is 5000. This is the usual value for the port number unless you are using this port for another program.

When your Sybase configuration information is complete and correct, click Next.

3 Installation


Figure 3-30: Sybase Non-Administrative Account Screen

To properly complete this screen, you must know the following information (this information can be provided by the Sybase Administrator):

• Sybase Username: Enter the user name for a non-administrative database user account. Interstage BPM will use this account to log into the database.

• Sybase Password: Enter the password for the non-administrative database user account.

• Sybase Confirm Password: Re-enter the password.

The password that you enter in the Sybase Password field must match the password that you enter in the Sybase Confirm Password field. If they do not match, you will receive a message informing you of this and upon clicking OK, you are returned to this screen, then you can re-enter your password.

When your Sybase login information is correct, click Next.

3 Installation


Figure 3-31: Sybase Database Server Administrative Account Screen


• Sybase Server Admin User: Enter the user name of the Sybase Server Administrator user account.

• Sybase Server Admin Password: Enter the password for the Sybase Server Administrator user account.

When your Sybase Server login information is correct, click Next.

3 Installation


Figure 3-32: Sybase Installation Directory Screen

Enter the Sybase Root directory.

Click Next to continue. Skip to the Database Configuration section if your database software is installed on the local machine.


3 Installation


3.4.5 Database Configuration

Figure 3-33: Database Configuration Screen

Warning: If you want to reconfigure the database, select Create New Interstage Business Process Manager Database. Be aware that by choosing this option, you will lose all previous data stored in the database. No matter which of these options you choose, it is strongly recommended that you backup the database and the attachments directories before installation. The installation process automatically migrates (and therefore overwrites) process definitions to the current release’s formats. Use the default functionalities of Oracle and Microsoft® SQL Server for backing up your database.

• Select Update Interstage Business Process Manager Database, if you have already installed and used Interstage BPM Advanced Edition and have process definitions, process instances or work items that you want to keep.

• Select Create New Interstage Business Process Manager Database, if you want to start with a completely new Interstage BPM Database.



3 Installation


3.4.6 Final Installation Steps

Figure 3-34: Java Development Kit (JDK) Location Screen

In the Java Development Kit (JDK) Location screen, the top-level folder of your J2SE Development Kit (JDK) installation must be specified. If the destination folder specified on this screen is not the top-level folder of your JDK installation, click Browse and navigate to it. You must install the correct JDK and specify the path to its top-level folder on this screen. See the System Requirements in Chapter 2 for version information.

On UNIX and Linux, the default JDK top-level directory is /usr/java.


3 Installation


Figure 3-35: Interstage Business Process Manger Administrator’s E- mail Address Screen

Note: This screen only appears if you chose to enter the host name of your site’s SMTP mail delivery service.

Specify the email address (or alias email address) of the Interstage BPM Administrator that manages the email server used by Interstage BPM. This address will appear in the "From:" field on all email messages sent from the Interstage BPM Server. This includes all email notifications, work item escalations, timer resolution messages, etc.


3 Installation


3.4.7 Pre-Installation Summary

Figure 3-36: Pre-Installation Summary Screen

Make sure that all the information displayed on the Pre-Installation Summary screen is correct, then click Next to start the Interstage BPM installation.

3 Installation


Figure 3-37: Start Interstage Business Process Manager Services Screen

Make sure that the Start Interstage Business Process Manager Services checkbox is checked if you want the Interstage BPM Server to be started after you click Finish. Make sure that the Use Process Template Library checkbox is checked if you want the Interstage BPM Server to import the Interstage BPM Template Library, so that sample process definitions are available when you start to use Interstage BPM. For some process definitions of the Template Library you must create special users. Refer to section "Creating User Accounts for the Template Library" on page 58 for details. If you choose not to import the Template Library, you can import it at another time.

3 Installation


Figure 3-38: Please read the summary information below Screen

Check the <install_directory>/logs/IBPMServer.log file to see if the server is running. If the server is running, you will see a message similar to the following: "Interstage BPM Server Version x.x Build xxxxx is ready." at the end of the file.

Note: Be prepared for a delay of about a minute to get the Internet BPM Server and the services for the different adapters started because there are some sleep statements in the script.

Tip: In order to examine whether the Interstage BPM services are running check the Interstage BPM log files. For more information about using the log files, refer to section "Errors during Starting the Interstage BPM Server" on page 114.

Load the Interstage BPM Console into your Browser and log in to verify that the Interstage BPM Server is fully functional.

Refer to section "Load the Interstage Business Process Manager Clients" on page 59 for information how to start the Interstage BPM Console.

3 Installation


3.5 User Accounts and Roles

Define User Access to Interstage BPM

The first step in setting up Interstage BPM user accounts is to set up normal user login accounts on the Directory Server. For specific details about creating user login accounts for users who will have access to Interstage BPM, consult Chapter 4 "Setting Up a Directory Service" on page 63 and the documentation supplied with your Directory Server.

Assign Users to Roles

You create user login accounts on the machine where the Interstage BPM Server resides; Roles, however, must be created as Groups in the Directory Service. Because of this, the scope of the Role definitions varies. They can apply to the local system or to several systems or to the domain, depending on how the Directory Service is set up.

When defining the activities for a process in the process definition, the activities are assigned to Roles according to who is responsible for carrying out the activity. The advantage of assigning activities to Roles (rather than individuals) is that if personnel changes occur, only the Role definition needs to be updated, and not all the processes that use the Role.

Roles are logical groupings of people. For example, a Manager Role might contain the first-line managers in an organization. Any Interstage BPM user may be made a member of any Role. But you must make sure that the user names for the Interstage BPM users and the Group members are identical.

Note: To create a valid Group in Interstage BPM, you must use only alphanumeric characters, hyphens, and underscore characters ("_"). The default group used by Interstage BPM is Role.

Before Roles can be assigned to users, you must create Groups, which are the logical equivalent of Roles in the Directory Service. Consult Chapter 4 "Setting Up a Directory Service" on page 63, and the documentation for the Directory Service for details.

Interstage BPM Administrator login account names must be members of the special Group named by default AdminRole.

3 Installation


Directory Service Modification During Installation

When using the NT Directory Service or CentraSite the installation program uses special utilities to perform the following actions with respect to the Directory Service:

• It creates the default Interstage BPM user. This is the user specified on the Login Information screen during installation. This is the primary Interstage BPM administrative user. If you accepted the default user presented during installation, this user is ibpm_server1.

• It creates the Role Group. The Role Group is the default Interstage BPM Group. Interstage BPM activities are assigned to the Role Group by default.

• It creates the AdminRole Group. The AdminRole Group is the Interstage BPM Administrative Group. A user must be a member of this Group to perform administrative functions using the Administration Facility. For more information on the Administration Facility refer to the Interstage Business Process Manager Administration Guide.

• It adds the default Interstage BPM user to the Role Group.

• It adds the Interstage BPM user to the AdminRole Group.

Note for CentraSite

If you are using CentraSite, you don’t need to create any special users or Groups. You can use the users and Groups already defined in CentraSite.

For example, say that you already have a Group called Managers defined in CentraSite. Simply assign the activities that you want the Managers to perform to the Managers Group.

3.5.1 Automate Interstage Business Process Manager Account Creation

For Interstage BPM installations that use the Windows NT Directory Service, the creation of Interstage BPM login accounts from the command line, complete with the necessary assignment of user rights, can be automated with the iflownetadd utility, typically located in the <Interstage BPM installation directory>\bin directory.

Iflownetadd

The parameters are as follows:

- user The user name to be added to the Windows NT Directory Service. - password The logon password for this user. - group The Group name associated with this user. - domainname (or \\machinename) .The Directory Server that stores the user and

3 Installation


Group profiles. To create an account on the local domain, use domainname. To create an account on a different machine, use \\machinename. Note that machine name must be preceded by two backward slashes.

Use the following syntax for iflownetadd:

iflownetadd user password group domainname|\\machinename

To get online help for this command, type the command name iflownetadd with no parameters. Here is a sample batch file that creates entries for four users and their associated Groups in a Windows environment on an Interstage BPM server named PERFORMA:

iflownetadd Perf1 Perf1 Group1 \\PERFORMA iflownetadd Perf2 Perf2 Group2 \\PERFORMA iflownetadd Perf3 Perf3 Group3 \\PERFORMA iflownetadd Perf4 Perf4 Group4 \\PERFORMA

User rights with NT Directory Service

With Windows NT Directory Services, an additional user right must be added to user login account definitions. The provided utility iflownetadd automates this process.

All Interstage BPM users must have the advanced user right "Log on as a batch job." You can grant this right to a Group containing the users or to each user individually.

When Windows 2000® Server is used as the platform for the Interstage BPM Server, the login account for this server must also have the advanced user right. The login account must also have Administrator privileges to successfully start the Interstage BPM Server, or install the Interstage BPM Server.

Note: When you use StartAll.bat to start the Interstage BPM Server and the components, the user that you used to log in to Windows must have the user right mentioned above.

The Interstage BPM Server is responsible for Interstage BPM user login, but it cannot validate all required user rights at the time of login. Thus, users without all the necessary user rights may successfully login, but fail later when attempting a function requiring a specific user right.

Note for Windows 2000® Server

If you are using the native Microsoft Windows NT Directory Service on Windows 2000® Server, add users by opening the Administrative Tools folder on the Start Programs menu, and clicking the Computer Management option, then the Local Users and Groups option, and finally, the Users option. On the Action menu, click New User and add the user name, password, and password options in the dialog that appears.

3 Installation


You must then set the user rights by clicking the Administrative Tools icon on the Control Panel. Select the Local Security Policy icon, then the Local Policy option, and finally, the User Rights Assignment option. On the Action menu, select Security… to invoke the Local Security Policy Setting dialog. Select the user rights listed above, and click the Add button to add the users you have just created.

For all Interstage BPM users, the user password must be set to "Password never expires". Deselect the other password properties in the Password Properties tab.

Note for Windows Server™ 2003

If you are using the native Microsoft Windows NT Directory Service on Windows Server™ 2003, add users by opening the Administrative Tools folder on the Start>Settings>Control Panel menu, and double-clicking the Computer Management option. Then, open the Local Users and Groups option, and finally, the Users option. On the Action menu, click New User and add the user name, password, and password options in the dialog that appears.

You must then set the user rights by clicking the Administrative Tools icon on the Control Panel. Select the Local Security Policy icon, then the Local Policy option, and finally, the User Rights Assignment option. On the Action menu, select Security… to invoke the Local Security Policy Setting dialog. Select the user rights listed above, and click the Add button to add the users you have just created.

For all Interstage BPM users, the user password must be set to "Password never expires". Deselect the other password properties in the Password Properties tab.

3.5.2 Creating User Accounts for the Template Library

Interstage BPM comes with ten standard business process definitions that are enclosed in packages, which you can install during the installation of Interstage BPM. Refer to Creating User Accounts for the Template Library section for details on installing the Template Library.

Some of the process definitions in the Template Library might require some minor configuration depending on how Interstage BPM is set up on your system. Use the following instructions to perform this configuration:

1. If you checked the Use Template Library checkbox when you installed Interstage BPM, the Template Library has already been imported into your Interstage BPM Server. Refer to installation Step Error! Reference source not found. in section "Interstage Business Process Manager Installation" for details for installing the Template Library. If you did not, you can import these packages individually using the instructions for importing packages in the Interstage Business Process Manager User’s Guide. You also you can import the Template Library by running the DeployTemplate.bat /DeployTemplate.sh file. The batch file is typically located in

3 Installation


the C:\Fujitsu\InterstageBPM\bin directory on Windows and in the /opt/FJSVibpm/bin directory on UNIX or Linux.

Use the DeployTemplate.bat file on Windows as follows:

DeployTemplate.bat <username> <PW> C:\Fujitsu\InterstageBPM\bin\packager.conf

2. Create the users and Groups needed by the Template Library. If you are using Microsoft® Active Directory or Sun Java System Directory Server you can import the template_library.ldif file for creating the users and the Groups. The template_library.ldif file is typically located in the C:\Fujitsu\InterstageBPM\samples\TemplateLibrary\ldap directory. Refer to section "Importing the iFlowADAdd.ldif File" on page 65 for importing an ldif file into Microsoft® Active Directory. Refer to section "Importing the iFlowLDAPAdd.ldif File" on page 78 for importing an ldif file into Sun Java System Directory Server.

If you are using the Microsoft® Windows® 2000/2003 Native Directory, you can create the users and Groups for a particular process definition by running a special batch file. These batch files are typically located in the C:\Fujitsu\InterstageBPM\bin\TemplateUsers directory. To run these files, you will need to replace 'machine-name' with your actual machine name, in these files.

3.6 Load the Interstage Business Process Manager Clients

Once the Interstage BPM server is running, any machine satisfying the minimum client requirements may access it. However, when the Interstage BPM Server starts after installation, you might have to wait two or three minutes before reloading the clients.

Prior to using the Interstage BPM Browser-based clients for the first time, ensure that you have the correct Browser version, that the Browser is configured to allow the Interstage BPM Java applet access to local resources, and that the Java Virtual Machine is enabled (see below).

Check the Browser version:

In the Microsoft Internet Explorer menu bar, select Help > About.

See Minimum Requirements beginning on page 4 to determine the correct Browser version.

Allow the Interstage BPM Java applet access to local resources as follows:

1. In the Microsoft Internet Explorer menu bar, select Tools > Internet Options.

2. In the Internet Options dialog, select the Security tab, set the Security Level for the Local intranet zone to Medium.

3 Installation


Interstage Business Process Manager Client Configuration

Perform the following configuration steps on every computer that will be running Interstage BPM clients:

Note: You can run Interstage BPM clients on any machine configured using the following steps as long as the machine meets the minimum system requirements.

Interstage BPM has three clients. Access to these clients is through the Interstage BPM Client index page. To load the index page, enter the following URL in the browser:

http://<Interstage BPM Machine Name or FQDN>:49950/ibpm/

For example, the index page on an intranet might have the following URL: http://myServer:49950/ibpm/

Click the client’s button to open its login page.

• BPM Console – use this JSP Client to start processes, respond to work items, create process definitions, and edit process definitions and process instances. This client also includes email capability. For information about using the Interstage BPM Console refer to the Interstage Business Process manager User's Guide.

• Administration Facility – use to import, export or delete process definitions, delete process instances, and modify and delete user profiles. For information about using the Administration Facility refer to the Interstage Business Process Manager Administration Guide.

• Reports – Use this JSP Client to generate reports.

3.7 Uninstalling Interstage Business Process Manager

You can uninstall Interstage BPM with the Interstage BPM uninstall program (Start>Programs>Interstage Business Process Manager>Uninstall) or with the Microsoft Windows 2000 control panel Add or Remove Programs (Start>Settings> Add or Remove Programs). On UNIX or Linux, run /_uninst/uninstall.sh. When you uninstall with Interstage BPM’s uninstall program, Interstage BPM removes everything except

• the FormsRepository and other DMS root directories (unless they are empty, in which case the directories are deleted),

• the ibpm.properties file,

• log files from the Interstage BPM \logs\ directory,

• the iflowserver user,

3 Installation


• the AdminRole Group,

• the Interstage BPM database.

The uninstall program automatically saves your configuration files with the suffix Previous appended to their file names. For example, ibpm.properties file is saved as ibpmprevious.properties. This preserves a record of any tuning changes you may have made to the configuration of your previous version of Interstage BPM. After installing Interstage BPM again, you can manually copy any custom configuration settings from your Previous files to your current configuration files.

To uninstall Interstage BPM, perform the following steps:

1. Log out of all Interstage BPM clients and close all Browser windows.

2. Select Uninstall from the Interstage BPM Program Group (Start > Programs> Interstage Business Process Manager > Uninstall). An alternative uninstallation method is to run setup.exe from the Interstage BPM CD, the same as if you were installing Interstage BPM. On Unix, run uninstall.sh which is located in <Interstage BPM installation directory> /_uninst.

3. Make sure that the Uninstall Interstage BPM Advanced Edition radio button is selected, then click Next.

4. Click OK when asked Do you want to completely remove the selected application and all of its components?

After uninstalling Interstage BPM restart your machine.

3.8 Upgrading Interstage Business Process Manager from Previous Versions

Warning: Always back up your Interstage BPM database before upgrading to a new version of Interstage BPM. This is the only way to ensure the retention of your current Interstage BPM data.

To upgrade:

1. Uninstall the previous version of Interstage BPM according to the instructions for that version.

2. Install Interstage BPM according to the installation instructions in this Guide. During the installation of Interstage BPM when given a choice between keeping your existing database and creating a new one or overwriting the old one, be sure to keep your existing database.

3 Installation


Warning: If you overwrite the old database, you will lose all of the previous work that is stored in the database.



There are the following of Directory Services available for Interstage BPM:

• Microsoft® Windows® 2000/2003 Native Directory

• Microsoft® Active Directory

• Sun Java System Directory Server

• CentraSite

This chapter provides instructions for setting up the Sun Java System Directory Server, the Microsoft® Active Directory and CentraSite.

The Microsoft® Windows® 2000/2003 Native Directory is a component of the Windows® 2000 Server/Windows Server 2003™ operating systems. For the Microsoft Windows 2000/2003 Native Directory no setup is required aside from the setup preformed automatically by the Interstage BPM installer with the iflownetadd utility. Refer to section "Automate Interstage Business Process Manager Account Creation" on page 56 for details on the iflownetadd utility.

Note: Use the instructions in this chapter only if you are using the Sun Java System Directory Server, Microsoft® Active Directory or CentraSite with Interstage BPM. Do not use these instructions if you are using the Microsoft Windows 2000/2003 Native Directory with Interstage BPM

Sun Java System Directory Server, Microsoft® Active Directory and CentraSite use a form of the Lightweight Directory Access Protocol (LDAP). Like all LDAP-type Directory Services, they organize people into Groups or Roles, and maintain a user profile with the appropriate permissions for each user. They maintain a user profile for each person and with the appropriate permissions.

4.1 Setting Up Microsoft® Active Directory

This section provides instructions for setting up Microsoft® Active Directory. Active Directory uses a form of the Lightweight Directory Access Protocol (LDAP). Like all LDAP-type Directory Services, Active Directory organizes people into Groups or Roles, and maintains a user profile with the appropriate permissions for each user.

The Active Directory setup procedure must be performed on the master domain controller for your network by an Administrator who has permission to modify the master domain schema. Note that this procedure involves the addition of attributes to Active Directory and that the addition of these attributes is permanent.



Note: There may be several sub domains in your network, but this set up procedure will only be successful if it is performed on the master domain controller as it contains the master domain schema. This schema affects the entire network. Changes made to the schema of a sub domain will have no effect.

To install Interstage BPM with Active Directory, you must customize your Active Directory Server installation as follows:

• On Windows 2000® Server, grant schema update permissions so that you are allowed to modify the master domain schema.

• Import the iFlowLDAPAdd.ldif file into your Directory Server. The iFlowLDAPAdd.ldif file contains the default Interstage BPM LDAP object class for Active Directory, users and Groups.

• Add users and Groups to the Directory Service.

4.1.1 Granting Schema Update Permission on Windows® 2000 Server

By default, schema modification is disabled on all Windows® 2000 Server domain controllers. To enable schema modification for a particular domain controller (DC), perform the following steps.

1. At the command prompt, type: regsvr32 schmmgmt.dll

RegSvr32 has been successfully registered if the "llRegisterServer in schmmgmt.dll succeeded dialog box is displayed.

2. Click Start to open a new management console.

Then click Run and type: mmc

3. On the Console menu, click Add/Remove Snap-in.

4. Click Add to open the Add Standalone Snap-in dialog box.

5. Select Active Directory Schema, then click Add.

6. The Active Directory Schema is displayed in the Add/Remove Snap-in. Click Close, then click OK to return to the Console.

7. Click Active Directory Schema. From the Action menu, select Operations Master.

8. Select the Schema may be modified on this Domain Controller check box.

9. Confirm your settings by clicking OK.



4.1.2 Importing the iFlowADAdd.ldif File

WARNING If you effectively import the iFlowADAdd.ldif file, you will be adding four attributes to the Active Directory master schema. These attributes are listed below.

Be aware that updating the master schema cannot be undone.

If you attempt to import the iFlowADAdd.ldif file on a machine other than the machine containing the Active Directory master schema, it will attempt to add these attributes to Active Directory and fail for lack of the necessary permissions. The script will stop at this point leaving Active Directory unchanged. Thus, no users or Groups will be added to Active Directory.

To effectively import the iFlowADAdd.ldif file so that you can use the Interstage BPM User Profile, you must have permission to modify the Active Directory master schema and import the file on the machine containing the Active Directory master schema. The batch file importAD.bat imports the iFlowADAdd.ldif file, but it must be moved to the master schema machine with the iFlowADAdd.ldif file.

Importing the LDIF file generated by the Interstage BPM installation program results in the following:

• Attributes used by Interstage BPM are added to Active Directory. Attributes and their functionality are described in the table on page 67.

• The IflowGroups and IflowUsers Groups are added to the Organizational Unit (ou) specified during the installation of Interstage BPM.

• The default Interstage BPM Roles Role and AdminRole are added to Active Directory Group.

• The default user (typically ibpm_server1) is added to the Organizational Unit.

• The default Groups Role and AdminRole are added to the members of IflowGroups.

• The default user (typically ibpm_server1) is added to the members of IflowUsers.

Proceed as follows to import the iFlowADAdd.ldif file:

1. Log on as an Administrator to the machine containing the Active Directory master schema.

2. Ensure that the Password Policies of the Domain Security Policy are set as follows. The Domain Security Policy is an administrative tool provided by Microsoft®, Password Policy is an option in the respective tree view (Windows Settings > Security Settings > Account Policies).



• Minimum password length: 0 characters

• Password must meet complexity requirements: Disabled

Make sure to remember the current settings to restore them in Step 6.

3. If the Active Directory server is installed on a machine different from the Interstage BPM Server, copy the iFlowADAdd.ldif file and the importAD.bat file to the Active Directory Server.

4. Ensure that the iFlowADAdd.ldif file is in your current directory.

5. Execute importAD.bat.

6. Restore the Password Policies (if you changed them in Step 2).

4.1.3 Using Existing Active Directory Users and Groups

If you are new to Interstage BPM and are already using Active Directory as the Directory Service to maintain your organization’s Users and Groups, you can use your existing directory structure with Interstage BPM. You can do this by designating your LDAP Users as Interstage BPM users and your LDAP Groups as Interstage BPM Roles. This involves the modification of two special LDAP Groups, IflowUsers and IflowGroups.

When you imported the iFlowADAdd.ldif file (see section "Importing the iFlowADAdd.ldif File" on page 64), you created two LDAP Groups under your main Organizational Unit (ou) called IflowUsers and IflowGroups. Of course, this assumes that you specified your main organizational unit when you installed Interstage BPM. These two special LDAP Groups can be used to allow your LDAP Users and Groups access to Interstage BPM.

To give your LDAP Users access to Interstage BPM as Interstage BPM users, add them as members of the IflowUsers group. You can add each user individually or add a group that contains the users. Users in the Group sub-levels are also given access. To give your LDAP Groups access to Interstage BPM as Interstage BPM Roles, add them as members of the IflowGroups Group.

Note: Because users added as members of the IflowUsers Group, do not have certain Interstage BPM attributes, they will not be able to use the Interstage BPM User Profile or the Interstage BPM features associated with it.

If you want your users to be able to use these Interstage BPM User Profile features, you must add certain attributes to the Active Directory master schema. To add these attributes, you must have permission to modify the Active Directory schema.

The attributes and the functionality are described in the table in the next section.



Active Directory Attributes Used by Interstage BPM

The following table lists the Active Directory attributes used by Interstage BPM for functionality associated with the DirectoryService class of the Model API.

If users are not using any of this functionality, there is no need to add these attributes to the Active Directory master schema. In addition, comment out the RequiredAttributes parameter in the ibpm.properties file to prevent errors if the DirectoryService class of the Model API is used inadvertently.

For example, if you do not have these attributes in Active Directory and RequiredAttributes is not commented out, entering an email address using the DirectoryService class of the Model API will cause an error.

Attribute Functionality That Needs It

Email This attribute allows you to specify an email address in the DirectoryService class of the Model API.

iflownotification This attribute enables Interstage BPM to notify users by email of work items to which they have been assigned. This notification is made using the email functionality. Your users must have this attribute if they want to use the email functionality.

Uid Allows Interstage BPM to uniquely identify the user to which this attribute is assigned. Users must have this attribute if they want to use the email functionality.

Dmsdir This attribute allows users to have their own DMS directory, so they may keep their forms separate from the forms used by other Interstage BPM users.

4.1.4 Add New Users

You can add new users to Active Directory by manually editing the LDIF file or by using the GUI.

Importing the .ldif File

The batch file createADUser.bat imports the createADUser.ldif file. Proceed as follows:

1. Log on as an Administrator to the machine where the Active Directory master schema is located.

2. Ensure that the Password Policies of the Domain Security Policy are set as follows. The Domain Security Policy is an administrative tool provided by Microsoft®, Password Policy is an option in the respective tree view (Windows Settings > Security Settings > Account Policies).



• Minimum password length: 0 characters

• Password must meet complexity requirements : Disabled

Make sure to remember the current settings to restore them in Step 7.

3. If the Active Directory Server is different from the Interstage BPM Server, copy the createADUser.ldif and createADUser.bat files to the Active Directory Server.

4. To create a new user, update the createADUser.ldif and createADUser.bat files. See the instructions in the files for details.

5. Ensure that the createADUser.ldif file is located in your current directory.

6. Execute the createADUser.bat batch file.

7. Restore the Password Policies if you changed them in Step 2.

Using the GUI to Add New Users

1. Launch the Active Directory Console if you haven’t already done so by selecting Start > Settings > Control Panel > Administrative Tools > Active Directory Users and Computers. Expand the host name and the domain name to find the People category.

2. Right click People.

3. From the popup menu, select New, and then select User to open the New Object - User dialog.



Figure 4-1: New Object – User window

4. Enter the new user’s information and click Next.

For each user, Active Directory requires you to provide a first name, last name, full name, and user login name.

Interstage BPM requires both a user login name and password to log in. The default user name and password for Interstage BPM administration are ibpm_server1.

5. Enter the user’s password, and then click Next.



Figure 4-2: New Object – User dialog

6. Confirm the adding of the new user by clicking Finish in the confirmation dialog box:



Figure 4-3: New Object – User dialog

Use the New Object - User dialog to create as many new user profiles as you want.

Note: To create valid users in Interstage BPM, use only alphanumeric characters, hyphens, and underscore characters ("_").

4.1.5 Add New Groups

You can add new Groups to Active Directory by importing the LDIF file or by using the GUI.


The batch file createADGroup.bat imports the createADGroup.ldif file. Proceed as follows:


2. If the Active Directory Server is different from the Interstage BPM Server, copy the createADGroup.ldif and createADGroup.bat files to the Active Directory Server.

3. To create a new Group, update the createADGroup.ldif file. See the instructions in this file for details.

4. Ensure that the createADGroup.ldif file is located in your current directory.



5. Execute the createADGroup.bat batch file.

Using the GUI to Add New Groups

1. Launch the Active Directory Console if you haven’t already done so by selecting Start > Settings > Control Panel > Administrative Tools > Active Directory Users and Computers. Expand the host name and the domain name to find the Groups category.

2. Right click Groups. From the popup menu that appears, select New, and then select Groups to open the New Object - Groups dialog.

3. Add the new Group’s information, and then click OK to add your new Group. In the example below, the Group "Role" is added:

Figure 4-4: New Object – Group window

Use the New Object - Groups dialog to create as many new Groups as you want.

Note: To create valid Groups in Interstage BPM, use only alphanumeric characters, hyphens, and underscore characters ("_").

For each Group, Active Directory requires you to provide a unique name for your Group.



4.1.6 Add Members to a User Group

You can add members to a Group by manually editing the addADGrMember.ldif file or by using the GUI.


The batch file addADGrMember.bat imports the addADGrMember.ldif file. The file must be moved to the Active Directory master schema machine. Proceed as follows:


2. If the Active Directory Server is different from the Interstage BPM Server, copy the addADGrMember.ldif and addADGrMember.bat files to the Active Directory Server.

3. To add a member to a Group, update the addADGrMember.ldif file. See the instructions in this file for details.

4. Ensure that the addADGrMember.ldif file is located in your current directory.

5. Execute the addADGrMember.bat batch file.

Using the GUI to Add Members to a Group

1. Launch the Active Directory Console if you haven’t already done so by selecting Start > Settings > Control Panel > Administrative Tools > Active Directory Users and Computers. Expand the host name and the domain name to find the Groups category.

2. Right click the Group to which you want to add members. From the popup menu that appears select Properties, and then select the Members tab to invoke the Group’s properties dialog.

The Properties dialog for the Role Group is used in the following example. ibpm_example is already a member of the Role Group.



Figure 4-5: Role Properties window

3. The default Group named Role is installed when you import the iFlowADAdd.ldif file. You can maintain all of your users if you like. In the Role Properties dialog, click Add.

4. (Windows® 2000 Server) The Select Users, Contacts, Computers, or Groups dialog appears. Select a user or Group that you want to add as a member of the Group. Then click Add.



The user or Group appears in the bottom text area of the dialog box.

Figure 4-6: Select Users, Contacts, Computers, or Groups box

5. (For Windows Server™ 2003) The Select Users, Contacts, Computers, or Groups dialog appears. Search a user or Group that you want to add as a member of the Group.

The user or Group appears in the bottom text area of the dialog box.

Figure 4-7: Select Users, Contacts, or Computers box

6. Click OK.



The user appears with the existing users in the text area of the properties dialog box.

Figure 4-8: Role Properties box

Note: After normal installation using Active Directory, the default Administrator Role is a Group called AdminRole. You can change this default name by modifying the AdminRole parameter in the ibpm.properties file.

To this Group, add the IDs of all Interstage BPM users who will create WFAdminSession objects through Java. This Group should at least include the default ibpm_server1 user ID.

4.1.7 Active Directory Group Caching

When the Interstage BPM Server starts up (whether you start Interstage BPM by rebooting your machine or by running startservices.bat), Interstage BPM connects to your LDAP Directory Service and copies all of the user and Group information defined in LDAPUsersDN and LDAPGroupsDN to a cache on your Interstage BPM Server machine. This increases Interstage BPM performance because user and Group information no longer has to be retrieved from the LDAP Server that might be running on a separate



Network machine. It retrieves it from the LDAP Cache that is on the local machine in memory.

If the cache is not updated, users added since the start of the Interstage BPM Server would not be able to login to or use Interstage BPM. To avoid this, the cache has to be updated periodically.

The LDAPGroupCacheAgeSec parameter specifies how often the LDAP Cache is updated. LDAP Groups that have been in service for longer than the period of time specified in the LDAPGroupCacheAgeSec parameter are checked, and new user and Group information is retrieved from the LDAP Directory Service. The default value for this parameter is 3600 seconds, so if you don't add this parameter to the ibpm.properties file, the LDAP Cache will be checked every hour. If this parameter is set to -1, new user and Group information is retrieved from the LDAP Directory Service every time it is needed.

Each entry in the cache has a timestamp on it that is set to the last time that Group was read from the Directory Service. Whenever someone calls the Directory Adapter to fetch a Group, the Directory Adapter looks to see if that Group is in the cache:

• If the Group requested is NOT in the cache, then it is read in and timestamped with the current time.

• If the Group requested is already in the cache, then the timestamp is checked. If the Group was timestamped before the previous cache check (it is at a time before LDAPGroupCacheAgeSec seconds ago), then just that Group is deleted from the LDAP Cache and read back in from the Directory Service. All other Groups in the cache are unaffected.

4.2 Setting Up Sun Java System Directory Server

To install Interstage BPM with Sun Java System Directory Server (formerly know an iPlanet Server), you must customize your Sun Java System Directory Server installation as follows:

• Start the Sun Java System Directory Server.

• Import the iFlowLDAPAdd.ldif file into your Sun Java System Directory Server. The iFlowLDAPAdd.ldif file contains the default Interstage BPM LDAP object class for Sun Java System Directory Server, users and Groups.

• Add users and Groups to the Directory Service.

• Set the Sun Java System Directory Server access permissions.



4.2.1 Starting the Sun Java System Directory Server

After a standard installation of the Sun Java System Directory Server, it starts automatically on UNIX or Linux when the computer boots. If for any reason the Sun Java System Directory Server does not start when the computer boots, you can start the Sun Java System Directory Server manually.

The easiest way to start a fully installed UNIX or Linux daemon (like the Sun Java System Directory Server) is to locate the master startup file in the /etc/init.d directory and give it the appropriate argument. The Directory Server master startup file (typically located in /etc/init.d/) is linked to the startup and shutdown images of the file (typically located in /etc/rc2.d/). Therefore, enter the following command:

/etc/init.d/slapd start

However, the slapd daemon will start only if it is first shut down properly. If the K* files (or kill files) are installed correctly in the /etc/rc2.d/ directory, the daemons should automatically be stopped when the system shuts down. To do this, enter the following on the command line:

/etc/init.d/slapd stop

If you don’t have wrappers installed for the start-admin and start-slapd programs, follow these instructions:

1. Navigate to the start-admin program in the product directory of the Sun Java System Directory Server.

2. Enter the following command: start-admin

3. Navigate to the start-slapd program in the server directory of the Sun Java System Directory Server.

4. Enter the following command: start-slapd

Note: If wrappers have not been installed for stopping the daemons, navigate to the same directories then type stop-admin and stop-slapd at the command line.

Once you are certain that the Sun Java System Directory Server is running, you can start the Sun Java System Directory Server Console. Navigate to the product directory of the Sun Java System Directory Server.

Enter the following command: ./startconsole

4.2.2 Importing the iFlowLDAPAdd.ldif File

The iFlowLDAPAdd.ldif file contains the default Interstage BPM LDAP object class for Sun Java System Directory Server, users and Groups.



Proceed as follows to import the iFlowLDAPAdd.ldif file:

1. Make sure that you have the iFlowLDAPAdd.ldif file in your Interstage BPM \bin directory, typically <Interstage BPM installation directory>\bin\iFlowLDAPAdd.ldif.

2. Start the Sun Java System Directory Server Console.

3. In the Servers and Applications tab, expand the Directory Server Name tree. It shows the host name of the machine upon which the Directory Server is running.

4. Expand the Server Group tree.

Figure 4-9: Servers and Applications tab

5. Double-click Directory Server. The iPlanet Directory Server dialog appears.



Figure 4-10: Tasks tab

6. In the Tasks tab, select the Import Database menu item. The Import Databases dialog appears.

Figure 4-11: Import Databases dialog



7. Specify the fully qualified path to the iFlowLDAPAdd.ldif file in the LDIF file field. This file typically located in <Interstage BPM installation directory>\bin\iFlowLDAPAdd.ldif.

Note: Do not change the defaults in the Import Databases dialog.

8. Confirm your settings by clicking OK.

Note: The import function will not overwrite existing settings. If you have imported an iFlowLDAPAdd.ldif file previously, duplicate settings will be detected and rejected. An appropriate message will appear.

4.2.3 Using Existing Sun Java System Directory Server Users and Groups

If you are new to Interstage BPM and are already using Sun Java System Directory Server as the Directory Service to maintain your organization’s users and Groups, you can use your existing directory structure with Interstage BPM. You can do this by designating your LDAP Users as Interstage BPM users and your LDAP Groups as Interstage BPM Roles. This involves the modification of two special LDAP Groups, IflowUsers and IflowGroups.

When you imported the iFlowLDAPAdd.ldif file, you created two LDAP Groups under your main Organizational Unit (ou) called IflowUsers and IflowGroups. Of course, this assumes that you specified your main organizational unit when you installed Interstage BPM. These two special LDAP Groups can be used to allow your LDAP Users and Groups access to Interstage BPM.

To give your LDAP Users access to Interstage BPM as Interstage BPM users, add them as members of the IflowUsers Group. You can add each user individually or add a Group that contains the users. Users in the Group sub-levels are also given access. To give your LDAP Groups access to Interstage BPM as Interstage BPM Roles, add them as members of the IflowGroups Group.

Note: Because users added as members of the IflowUsers Group, do not have certain Interstage BPM attributes, they will not be able to use the Interstage BPM User Profile or the Interstage BPM features associated with it.

If you want your users to be able to use these Interstage BPM features, you must add them as new iflowpersons instead of as new users.

4.2.4 Add New Users

You can add new people to the default Interstage BPM class iflowperson by manually editing the iFlowLDAPAdd.ldif file or by using the Sun Java System Directory Server Console.



Using the Sun Java System Directory Server Console to Add New Users

1. Start the Sun Java System Directory Server Console

2. In the Servers and Applications tab, expand the Directory Server Name tree. It shows the host name of the machine upon which the directory server is running.



5. Select the Directory tab.

6. Right-click People for the specified server.

Figure 4-12: Directory tab

7. Select New and then select Other… to open the New Object dialog.



Figure 4-13: New Object dialog

8. Select iflowperson and click OK. The Create New User dialog appears.

Figure 4-14: Create New User dialog

9. Use the Create New User dialog to create as many new user profiles as you want.



Note: To create valid users in Interstage BPM, only use alphanumeric characters, hyphens, and underscore characters ("_").

For each user, Sun Java System Directory Server requires you to provide a first name, last name and common name(s). In addition, Interstage BPM requires a User ID.

Although filling in a password and confirming it are optional for Sun Java System Directory Server, Interstage BPM requires a password to log in. The default user name and password for Interstage BPM administration are iflow.

The fields “E-Mail”, “Phone” and “Fax” are not used by Interstage BPM.

9. Confirm your setting by clicking OK.

4.2.5 Add New Groups and Members to a Group

You can add new Groups to Sun Java System Directory Server by importing the iFlowLDAPAdd.ldif file or by using the Sun Java System Directory Server Console.





5. Select the Directory tab.

6. Right-click Group for the specified server.




7. Select New and then select Group… to open the Create New Group dialog.

Note: To create a valid Group in Interstage BPM, only use alphanumeric characters, hyphens, and underscore characters ("_").

Figure 4-16: Create New Group dialog



8. Enter the name of the new Group that you will be using. Groups are known as "Roles" in Interstage BPM: There is a default Group named "Role" installed by the Interstage BPM installer when you import the iFlowLDAPAdd.ldif file. The next step is to add members to the Group.

9. Click on the left side of the Create New Group dialog on Members.

Figure 4-17: Static Group tab

10. Keep the default Static Group tab, and click Add…. to display the Search users and groups dialog.

11. In the Search drop-down list, select Users. If desired, use an asterisk (*) in the for text box as a search wild card. Select the Search button.



Figure 4-18: Search users and groups dialog

12. Select the users that you wish to add to the Role you have created, and click OK. Repeat this procedure to create and populate every Role that you will need in Interstage BPM.

Note: After a normal installation using the Sun Java System Directory Server, the default Administrator Role is a Group called "AdminRole". You can change this default name by modifying the AdminRole parameter in the ibpm.properties file.

To this Group, add the IDs of all Interstage BPM users who will log into the Administration Facility or create WFAdminSession objects through Java. This Group should at least include the default iflow user ID.

4.2.6 Set User Permissions for Interstage Business Process Manager’s Login Name

It is recommended to use the Interstage BPM user specified during installation for logging in to the Directory Service. The following instructions use the user iflow as example.



3. Right click Directory Server.




4. Select Set Access Permissions… from the context menu to open the Set Permission dialog.

Figure 4-20: Set Permission dialog



Note: If a user is already listed in the Set Permission dialog, there is no need to continue with this procedure. Only one admin user is needed.

5. Click Add… to open the Search users and groups dialog.

6. In the Search drop-down list, select Users and Groups. If desired, use an asterisk (*) in the for text box as a search wild card.

7. Click Search.

Figure 4-21: Search users and groups dialog

8. Select the user iflow and click OK. The Set Permission Dialog reappears with iflow in the user list text box.



Figure 4-22: Set Permission dialog

Sun Java System Directory Server is now ready to work with Interstage BPM.

Note: The user iflow is used for example purposes only. The suggested user to set as the Sun Java System Directory Server administrative user is the user specified on the Login Information screen as the Interstage BPM administrative user during the installation of Interstage BPM. If you accepted the default, that user is ibpm_server1.

4.2.7 iPlanet Group Caching

When the Interstage BPM Server starts up, Interstage BPM connects to the LDAP Directory Service and copies all of the user and Group information defined in LDAPUsersDN and LDAPGroupsDN to a cache on the Interstage BPM Server. This increases Interstage BPM performance because user and Group information no longer has to be retrieved from the LDAP Server that might be running on a separate network machine. It retrieves it from the LDAP Cache that is on the local machine in memory.

If the cache is not updated, users added since the start of the Interstage BPM Server would not be able to login to or use Interstage BPM. To avoid this, the cache has to be updated periodically.

The LDAPGroupCacheAgeSec parameter specifies how often the LDAP Cache is updated. LDAP Groups that have been in service for longer than the period of time specified in the LDAPGroupCacheAgeSec parameter are checked, and new user and Group information is retrieved from the LDAP Directory Service. The default value for this



parameter is 3600 seconds, so if you don't add this parameter to the ibpm.properties file, the LDAP Cache will be checked every hour. If this parameter is set to -1, new user and Group information is retrieved from the LDAP Directory Service every time it is needed. Refer to the Interstage Business Process Manger Administration Guide for more information about the parameters of the ibpm.properties file.

Each entry in the cache has a timestamp that is set to the last time that group was read from the Directory Service. Whenever someone calls the Directory Adapter to fetch a Group, the Directory Adapter checks if that Group is in the cache:

• If the Group requested is not in the cache, it is read in and timestamped with the current time.

• If the Group requested is already in the cache, the timestamp is checked. If the Group was timestamped before the previous cache check (it is at a time before LDAPGroupCacheAgeSec seconds ago), then just that Group is deleted from the LDAP Cache and read back in from the Directory Service. All other Groups in the cache are unaffected.

4.3 Setting Up CentraSite

To install Interstage BPM with Active CentraSite, you must customize your CentraSite installation as follows:

• Synchronize CentraSite with Interstage BPM: Start the Administration Facility and logon as Administrator. Click in the Process Definitions section the Synchronize button. For more details refer to the Interstage Business Process Manager Administration Guide.

• Enable UDDI and metadata publishing: Set the following parameters in the ibpm.properties file: UddiPublisherUserName=<the user who installed IMR> UddiPublisherPassword=<password> MetaDataRepositoryUserName=<the user who installed IMR> MetaDataRepositoryPassword=<password> For more details about the ibpm.properties file refer to the Interstage Business Process Manager Administration Guide.

• Add user properties to the urm_config.xml file, which can be found in the installation directory of CentraSite, for example ...\Program Files\Software AG\Integration Metadata Repository\tomcat\conf\urm_config.xml. Edit the urm_config.xml file as follows:

1. Find the element <MetadataProperties>.

This element has an attribute Class whose value is a string similar to the example below:



<MetadataProperties Class="org.apache.slide.urm.authenticator.userdb.impl.tamino.URMMetadataPropsSpiTamino"> There is no need to alter this attribute.

2. The element <MetadataProperties> contains an element <User>.

Add to the existing entries within the element <User> the following properties: <Property name="uid" writeable="true" description="IBPM user property to identify a user" /> <Property name="iflownotification" writeable="true" description="IBPM user property for email notification" /> <Property name="email" writeable="true" description="Property to store IBPM user email" /> <Property name="dmsdir" writeable="true" description="Property to store the individual attachment directory for IBPM users" /> <Property name="sms" writeable="true" description="Property to store the IBPM user sms address" /> <Property name="pin" writeable="true" description="Property to store the IBPM user sms pin" /> The location of the new property elements within the <User> element is not critical.

You can use the Interstage BPM IBPMSSXAdd utility to automate the creation of users from the command line. The CentraSite Integration Manager is a GUI tool, with which you can create user and Groups and assign users the appropriate access rights.



4.3.1 Automate Account Creation

For Interstage BPM installations that use CentraSite, you can use the Interstage BPM IBPMSSXAdd utility to automate the creation and management of Interstage BPM login accounts from the command line, complete with the necessary assignment of user rights.

IBPMSSXAdd

Use the following syntax for IBPMSSXAdd:

java IBPMSSXAdd {-c|-d|-a|-r} targets The following options are available:

-c Creates the specified user and the specified Group and puts the user in that Group.

-d Deletes the specified user and the specified Group. -a Adds a user to an existing Group. -r Removes the specified user from the specified Group.

For the targets the following options are available:

-u Specifies the user name to be added. -g Specifies the Group name associated with this user.

The following shows two examples of using IBPMSSXAdd:

java IBPMSSXAdd -c {-u username password [-g groupname] | -g groupname}

Creates a user with the user name "username" and the password "password" and adds the user to the specified Group "goupname".

java IBPMSSXAdd -d {-u username [-g groupname] | -g groupname}

Deletes a user with the user name "username" from the specified Group "groupname".

IBPMSSXAdd.bat

The IBPMSSXAdd.bat batch file, typically located in the <Interstage BPM installation directory>\bin directory, uses the IBPMSSXAdd Java Utility program to automatically manage Interstage BPM users in CentraSite. It simplifies the addition of a user to the CentraSite. The Interstage BPM installer will use this batch file to create the default user ibpm_server1. The CentraSite Administrator can use this utility to create more users and Groups for Interstage BPM.

The following example is run during the installation.



The IBPMSSXAdd.bat batch file contains the following parameters:

• IFLOWROOT: The top-level directory of the Interstage BPM installation. The value that you entered during the Interstage BPM installation is used automatically.

• URM_CONFIG_FILEPATH: The fully qualified name of the URM (User Role Management). The value that you entered during the Interstage BPM installation for the Repository Configuration File (URM) is used automatically.

• ADMIN_USER: The URM Admin User Name. The value that you entered during the Interstage BPM installation is used automatically.

• ADMIN_PASSWORD: The URM Admin Password. The value that you entered during the Interstage BPM installation is used automatically.

• ADMIN_DOMAIN: The URM Admin Domain. The value that you entered during the Interstage BPM installation is used automatically.

• IBPM_USER: The name of the user that you want to add as an Interstage BPM user to the URM Directory Service. The purpose of this batch file is to add this user to the URM Directory Service.

• IBPM_PASSWORD: The password of the user that you want to add as an Interstage BPM user to the URM Directory Service. The purpose of this batch file is to add this user to the URM Directory Service.

The following example shows the setting for the IBPMSSXAdd.bat batch file:

set IFLOWROOT=C:\Fujitsu\InterstageBPM set URM_CONFIG_FILEPATH="C:\Program Files\CentraSite\tomcat\conf\urm_config.xml" set ADMIN_USER=Administrator set ADMIN_PASSWORD=admin4u set ADMIN_DOMAIN=NETADMIN set IBPM_USER=ibpm_server1 set IBPM_PASSWORD=ibpm_server1 echo calling 0.IBPMInit.bat call %IFLOWROOT%\bin\0.IBPMInit.bat

The following run of the utility adds the user whose name is %IBPM_USER% and password is %IBPM_PASSWORD%:

java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -c -u %IBPM_USER% %IBPM_PASSWORD% > IBPMSSXAdd.log



The following run of the utility creates the AdminRole Group:

java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -c -g AdminRole >> IBPMSSXAdd.log

The following run of the utility creates the Role Group:

java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -c -g Role >> IBPMSSXAdd.log

The following run of the utility adds the user whose name is %IBPM_USER% and password is %IBPM_PASSWORD% to the AdminRole Group:

java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -a -u %IBPM_USER% -g AdminRole >> IBPMSSXAdd.log

The following run of the utility adds the user whose name is %IBPM_USER% and password is %IBPM_PASSWORD% to the Role Group:

java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -a -u %IBPM_USER% -g Role >> IBPMSSXAdd.log

The following run of the utility removes the user whose name is %IBPM_USER% and password is %IBPM_PASSWORD% from the Role Group:

java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -r -u %IBPM_USER% -g Role >> IBPMSSXAdd.log

The following run of the utility removes the user whose name is %IBPM_USER% and password is %IBPM_PASSWORD% from the AdminRole Group:

java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -r -u %IBPM_USER% -g AdminRole >> IBPMSSXAdd.log

The following run of the utility deletes the user whose name is %IBPM_USER%:



java -DURM_CONFIGFILE_PATH=%URM_CONFIG_FILEPATH% -DIMR_DOMAIN=%ADMIN_DOMAIN% -DIMR_ADMIN_USER=%ADMIN_USER% -DIMR_ADMIN_PWD=%ADMIN_PASSWORD% com.fujitsu.iflow.utilities.IBPMSSXAdd -d -u %IBPM_USER% >> IBPMSSXAdd.log

4.3.2 Add New Users

You can add new users to CentraSite by using the CentraSite Metadata Manager. This section provides instructions for adding new users to CentraSite. For more detailed information refer to the User Management and Role Management instructions in the CentraSite Online Help.

1. Start the CentraSite Metadata Manager.

On Windows select Start > Programs > CentraSite > Metadata Manager.

On UNIX or Linux start a browser and enter the following URL:

http://<hostname>:49940/gateway/index.jsp

Or use the following shell command:

imrmanager.sh

2. Select Start > Programs > CentraSite > Metadata Manager.

3. Logon as Administrator to the CentraSite Metadata Manager.

4. Choose the entry User Management in the CentraSite Metadata Manager main menu.

5. Select the link Create User on the User Management dialog.



Figure 4-23: Create User dialog

6. Enter the name of the new user in the field User ID.

7. Enter the password in the first Password field.

8. Re-enter the password in the second Password field.

One or more Roles can be assigned to a user. For more information about creating a Role refer to section "Creating a User Role" on page 98.

9. Select a Role from the box marked All Roles and choose the double-right arrow button to assign a Role to the user.

One or more Groups can be assigned to the user. For information about creating a Group refer to section "Add New Groups" on page 100.

10. Select a Group from the box marked All Groups and choose the double-right arrow button to assign a Group to the user.

11. Scroll down the page and click Save to confirm your settings.



4.3.3 Set User Permissions

You can create new Roles by using the CentraSite Metadata Manager. To every Role you can assign users and access rights.

4.3.3.1 Creating a User Role






imrmanager.sh



4. Select the link Role Management.

Figure 4-24: Role Management dialog

5. Select the link Create Role.



Figure 4-25: Create Role dialog

6. Enter a name for the user Role in the text field Role Name.

7. Select one or more of the access rights you wish to assign to the user role.

8. Scroll down the page and choose Save.

4.3.3.2 Editing a User Role

Use this feature to assign users and access rights to a user Role.

1. Make sure that the Role Management dialog is open.

2. Select the edit icon that is located in the same row as the user Role.

This opens the Edit Role dialog, which allows you to assign one or more users and one or more rights to the role you have chosen. If you are logged on locally, the list shows all users who are registered locally to use the computer. If you are using a Windows domain, all IDs of users who are registered in the domain are shown. Depending on the size of your Windows domain, it can take some time to retrieve the IDs of all registered users from the domain registry.

3. Select one or more user IDs from the list displayed.

4. Select one or more access rights that you wish to assign to the user Role.

5. Scroll down the page and choose Save.



4.3.4 Add New Groups

You can add new Groups to CentraSite by using the CentraSite Metadata Manager. This section provides instructions for adding new Groups to CentraSite. For more detailed information refer to the User Management and Role Management instructions in the CentraSite Online Help.






imrmanager.sh

2. Select Start > Programs > CentraSite > Metadata Manager.



5. Select the link Group Management.

Figure 4-26: Group Management dialog



6. Select the link Create Group.

Figure 4-27: Create Group dialog

7. Enter the name of the Group.

8. Scroll down the page and choose Create.


Appendix A Security

Interstage BPM can be set to two security levels: Demo Mode and Security Mode. Demo Mode is useful while key members of your work team learn the features of the software. Later, Security Mode provides a stable and controlled environment for implementing Interstage BPM across your company.

Demo Mode

Demo Mode restricts access to Interstage BPM in two ways:

1. Only the person who is assigned a work item may make choices about it, thus advancing the process to the next work item - or completing it.

2. Only members of the AdminRole can access the Administration Facility.

All Interstage BPM users can experiment with all of Interstage BPM functions, including creating and editing process definitions and process instances.

Security Mode

In Security Mode, access to process definitions, process instances, and work items are restricted to the specific people who need to use them.

• Only members of the Role specified for TemplatePublishers key in the ibpm.properties file can create new process definitions.

• Only the process instance owners, current assignees, and Interstage BPM Administrators can view any specific process instances. ("Current assignees" are those who have active task assignments. This does not include people who will have task assignments later in the process.)

• Only the process instance owners, current assignees, and Interstage BPM Administrative Users can edit their specific process instances. This means they can change User Defined Attributes and add or delete attachments. However, they are not allowed to edit the process structure.

Setting Up Security Mode

To turn on Security Mode, you must make two changes in the ibpm.properties file, which is typically located in <Interstage BPM installation directory>\bin\.:

Appendix A: Security


1. Locate and load the ibpm.properties file. You may use Notepad.exe, since the file must be saved as a plain text file.

2. In the "#Server" section, add a line that reads: SecuritySwitch=true to enable Security Mode.

3. In the "Common parameters" section, add the TemplatePublishers =<registered role> parameter. This registered Role must be registered in your Directory Service. For example, if you have defined a Role of "pubRole" in your Directory Service, you would type TemplatePublishers=pubRole.

Be aware that this key takes effect only if the Security Mode is switched on.

Deploying Interstage Business Process Manager in a Firewall Environment

The following configuration steps are necessary to operate Interstage BPM in a Firewall environment:

1. Open an inbound and outbound port on the firewall. This operation has to be performed by your Firewall Administrator. The recommended port is 49954 because this is the RMI default port.

2. If you used Port 49954 in Step 1, add the RMIExport parameter to your ibpm.properties file as follows:

RMIExPort=49954

If you used a different port in Step 1 (say port number 49955), you need to add two parameters to the ibpm.properties file as follows:

RMIPort=49955 RMIExPort=49955

The reason for this extra parameter is that the RMIPort value defaults to port number 49954. If you use port number 49954, there is no need to add it to the ibpm.properties file. Refer to the Interstage Business Process Manager Administration Guide for more details.

Configuring SMTP Authentication for Use with Interstage Business Process Manager

Note: Only a System Administrator should perform these instructions.

If you required SMTP Authentication for logging in to Interstage BPM, use the following instructions:

1. Set up an email server and enable SMTP Authentication.



2. Set the following parameters in the Interstage BPM configuration file ibpm.properties:

SMTPServerHost= /*this is the email server host name*/

SMTPUserName= /*user name for SMTP authentication*/

SMTPPassword= /*password for SMTP authentication*/

3. Restart the Interstage BPM Server and design a process definition to test the email feature. Refer to the Interstage Business Process Manager User's Guide for information how to design process definitions.

If the SMTPUserName or SMTPPassword are set correctly, the email will be accepted by the email server. If neither the SMTPUserName nor SMTPPassword values are blank, Interstage BPM will use the SMTP authentication feature.

Password Encryption

The Interstage BPM installation program encrypts the passwords entered during installation using a predefined encryption key. The Interstage BPM Server will use this key to decrypt the passwords. If you need to change the user/passwords after installation, a utility application is provided so that you can encrypt the passwords and overwrite them in the ibpm.properties configuration file.

It is assumed that the default key is used to encrypt and decrypt the passwords. In case, a different key is used for security reasons, this key must be provided as a configuration parameter. The default key is not published; it is hardcoded in the Interstage BPM Server code. The utility application does not provide for decryption of passwords. It can only be used for encryption.

The Interstage BPM Server decrypts all passwords at startup. If decryption fails, a warning message will be printed in the IBPMServer.log file.

The utility provided is:

com.fujitsu.iflow.utilities.TextEncrypter.class

Usage:

To encrypt a password with the default key:

java com.fujitsu.iflow.utilities.TextEncrypter.class –e textPassword

To encrypt a password with a new key:

java com.fujitsu.iflow.utilities.TextEncrypter.class –e textPassword [EncryptionKey]



Note: If a key other than the default key is used, it should contain more than 24 characters.

During startup, the key needs to be provided in the configuration file during startup. The property name in the ibpm.properties file is "EncryptionKey".

For security reasons, the key can be removed again from the configuration file after server startup. It has to be provided, however, for any subsequent start of the server.

The Interstage BPM installer has encrypted each password in the configuration file using the default key. It recommended encrypting your password with your own key. Each password can be encrypted using the above mentioned tool.

Alternatively, all passwords in the ibpm.properties file can be encrypted at the same time. To do this, substitute all passwords in the ibpm.properties file with actual text passwords and run the ibpm.properties file in the utility as follows:

java com.fujitsu.iflow.utilities.TextEncrypter.class -f iniFileWithPath [EncryptionKey] Example:

java com.fujitsu.iflow.utilities.TextEncrypter.class -f C:\Fujitsu\InterstagBPM\bin\ibpm.properties EWAERJQ23FIQ0J22


Appendix B Silent Mode Installation

A Silent Mode installation is a non-interactive type of installation, i.e. you start the installation program and Interstage BPM is installed. If you have to perform multiple installations of Interstage BPM, and the installations are essentially the same, you might want to consider installing Interstage BPM in Silent Mode as you can save a significant amount of time.

How It Works

Silent Mode installations involve the use of an installation script. You perform the first installation interactively using a special installation option that records the installation into an installation script in ASCII (text) format called record-install.txt. You then run subsequent installations in silent mode using this script. Minor installation variations can be handled by editing the script.

Setting Up an Interstage Business Process Manager Silent Mode Installation

1. Create a new directory on your computer.

2. Copy the following files from the install directory on your CD-ROM to the directory that you created on your computer:

• ibpmedinfo.dat

• setup.jar

• setupwin32.exe on Windows

• setupLinux.bin on Linux

• setupSolaris.bin on Solaris

• setupAIX.bin on AIX

3. Open a Command Prompt window and navigate to the directory on your machine containing the copied files.

Appendix B: Silent Mode Installation


4. Start the Interstage BPM installation program by entering the following command:

On Windows:

setupwin32.exe -options-record <Installation Script>

In the following example, RMI is the directory containing the copied files and record-install.txt is the name of the installation script to be recorded:

C:\RMI> setupwin32.exe -options-record record-install.txt This command starts a normal mode installation of Interstage BPM and records the installation choices that you make. As the installation program runs, use the instructions written earlier in this manual.

At the end of installation, the installation choices are written to the installation script. In the example, the installation script record-install.txt is created in the RMI directory. You can now use the installation script to install Interstage BPM on other computers in Silent Mode.



Installing Interstage Business Process Manager in Silent Mode

Install Interstage BPM using Silent Mode as follows:

1. Create a directory on the computer where you want to install Interstage BPM in Silent Mode. In the example below, RMI is used as the directory's name.

2. Copy the following files from the computer where you recorded the installation script to the directory that you created in the previous step:

• ibpmedinfo.dat

• the installation script that you recorded, e.g. record-install.txt

• setup.jar

• setupwin32.exe on Windows

• setupLinux.bin on Linux

• setupSolaris.bin on Solaris

• setupAIX.bin on AIX

3. Take note of the drive and directory to which you copied the files.

4. Open the installation script in a text editor and make any changes necessary to make it run properly in the different environment.

5. Save the changes made to your installation script.

6. Open a Command Prompt window and navigate to the directory that contains the installation script.

7. Install Interstage BPM in Silent Mode with the following command:

C:\RMI> <Absolute Path>\setupwin32.exe -options "<Absolute Path>\record-install.txt" -silent Interstage BPM will be installed in Silent Mode. There will be no screen response at all except for some Command Prompt windows that will appear near the end of your installation. Interstage BPM has now been installed in Silent Mode.

This procedure can be repeated for all of your Interstage BPM installations.


Appendix C Troubleshooting

Log File Information

If Interstage BPM does not seem to be working properly, check the following log file:

• IBPMServer.log in the \logs directory of your Interstage BPM installation (typically <Interstage BPM installation directory>\logs) on the Interstage BPM Server host. This log file is often very helpful in troubleshooting. For example, it may indicate that the database server is down.

Resolving Specific Error Situations

Interstage BPM Server Fails to Start

Check the IBPMServer.log file in the <Interstage BPM installation directory>\logs directory.

Look for What to do

DbService : setConnection: Connection to database server failed. Is the database server running and reachable through the network? {ORA-01089: immediate shutdown in progress - no operations are permitted.

Check if the database is running. Also check that you can access the database from the machine where the Interstage BPM Server is installed in case the database is running on a different machine. You can use "telnet <databaseServerHostName> <port>" from the server host machine to check that the connection to the database host/port can be established.

LdapBroker : getContext: Could not create the directory services. {[LDAP: error code 49 - Invalid Credentials]}

LdapBroker : getGroupMembersByDN: Could not retrieve the user groups. {Could not create the directory services. {[LDAP: error code 49 - Invalid Credentials]}}

LdapBroker : Could not retrieve the user groups. {Could not create the directory services. {[LDAP: error code 49 - Invalid Credentials]}}

Ensure that the user name/password as specified in LDAPAccessUserID / LDAPAccessUserPassword (ibpm.properties parameters) are correct and you can login to your Directory Server using the above user name/password.

getContext: Could not create the directory services.

Ensure that the LDAP Server is running on the port as specified in LDAPServer (ibpm.properties

Appendix C: Troubleshooting


Look for What to do

LdapBroker : getGroupMembersByDN: Could not retrieve the user groups. {Could not create the directory services.

LdapBroker : Could not retrieve the user groups. {Could not create the directory services.

parameter). You can use "telnet ldapServerHostName port" from the server host machine to check that the connection to the host/port can be established.

Error in IBPMServer.log

Check the IBPMServer.log in the <Interstage BPM installation directory>\logs directory.

Look for What to do

getGroupMembersByDN: Could not retrieve the user groups. {[LDAP: error code 32 - No Such Object]}

One possibility of this error could be that a user has been deleted from the Directory Server (LDAP Server) but the reference of it is still there in one of the groups which is causing this error in the log file.

Errors During Installation and Configuration

This section lists several errors that could occur during the installation and configuration of Interstage BPM and describes the required action(s) to take:

A. An error occurred during Interstage BPM database creation/update

I Cause One of the following values provided during the installation were wrong:

- Oracle Administrator name - Oracle Administrator password

Action Restore the database from the backup of the database made before installing Interstage BPM.

Run the installer again and select Configure Interstage Business Process Manager Database Server on the Installation Action screen. In this way, the database is configured without installing Interstage BPM again.

II Cause One of the following values provided during the installation were wrong.



- Oracle Hostname - Oracle SID - Oracle Port

Action Restore the database from the backup of the database made before installing Interstage BPM.

Uninstall Interstage BPM and install it again.

III Cause Database server is not running

Action Start the database server.

Run the installer again and select Configure Interstage Business Process Manager Database Server on the Installation Action screen. In this way, the database is configured without installing Interstage BPM again.

B. An error occurred during the execution of importAD.bat for importing the iFlowLDAPAdd.ldif file.

I Cause One of the following values provided during the installation were wrong:

- LDAP Key - Organization Unit

These values are described in the ibpm.properties file as follows:

LDAPUsersDN = cn=IflowGroups, < Organization Unit >, <LDAP Key>

Action Uninstall Interstage BPM and install it again.



Errors during Starting the Interstage BPM Server

The following table explains the possible causes of errors during server startup and the appropriate action(s) to take:

I Cause The Active Directory Server is remote and Active Directory is not running.

Action Start the Active Directory Server, then start the Interstage BPM Server.

II Cause One of the following values provided during the installation was wrong.

- User name for the Directory Service Login account - Password for the Directory Service Login account

These values are described in the importAD.bat file as arguments of the "net user" command.

Action Uninstall Interstage BPM and install it again.

III Cause The Database Server is not running.

Action Start the Database Server, then start the Interstage BPM Server.

Errors during Using the Administration Facility

This section lists an error that could occur during using the Administration Facility.

I Cause Clicking on the Help button in the Administration Facility doesn't bring up a window with the online help.

Action The Pop-up-Blocker of the Web Browser prevents the appearance of the window with the online help.

For the Internet Explorer select Tools > Internet Options… and then the Privacy tab. Deselect Block pops-ups or choose Settings for adding the URL of the Administration Facility, typically http://<Interstage BPM server host name>:49950/ibpm, to the list of Web sites from which pop-ups are allowed.



Contacting Your Local Fujitsu Support Organization

If you are unable to troubleshoot your problem, proceed as follows:

1. In the ibpm.properties file, set the DebugLevel parameter to 2 and restart Interstage BPM via the Interstage Management Console. Your ibpm.properties file can be found in the <Interstage BPM installation directory>\bin directory.

2. Replicate the actions that caused the error.

3. Contact your local Fujitsu Support organization and provide the following information:

• Description of the steps you performed and, if possible, the application program and its source code that caused the error.

• Console output which contains the return value(s) and/or exceptions of the Model API.

• IBPMServer.log file

Proceed as follows to store this information:

Windows® 2000 Server: o Start > Settings > Control Panel o Administrative Tools > Event Viewer > Application Log or System

Log o From the Action menu, select Save Log File As.

Windows Server™ 2003: o Start > Control Panel o Administrative Tools > Event Viewer > Application or System o From the Action menu, select Save Log File As.

• ibpm.properties file

• Windows System Information

Proceed as follows to store this information:

Windows® 2000 Server: o Start > Programs > Accessories > System Tools > System

Information o From the Action menu, select Save As Text File

Windows Server™ 2003: o Start > Programs > Accessories > System Tools > System

Information o From the File menu, select Export.


Index

A about this manual................................ iii Active Directory .................................67 Administration Facility.......................60 ARIS PPM

documentation list .............................iv Assigning

User access to Roles.........................56 Users to LDAP groups .....................81

B browser configuration.........................59

C CentraSite ...........................................93

Add new Groups ............................100 Add new users ..................................96 Automate account creation...............93 Creating a Role.................................98 IBPMSSXAdd..................................93 Metadata Manager............................96 Set user permissions.........................98

D database

server ................................................15 Database

Adapter.............................................30 Server ...............................................12 server configuration

Microsoft Windows 2000 ...........12 Demo Mode ......................................102 DeployTemplate.bat ...............................58 Directory Service

Active Directory attributes...............67 Add Members to groups...................73 Add new Groups ..............................71 Add new users ..................................67 iFlowLDAPAdd.ldif.........................65 Schema update permission...............64 Setup.................................................63 Users and Groups .............................66

Directory Service Adapter Selecting .......................................... 22

E Email

Server Administrator ....................... 51

G Group

Add .................................................. 71 Add member .................................... 73

I IBPMSSXAdd.bat.................................. 93 Interstage BPM

documentation list ............................ iv Installation

on a laptop.................................. 15 Installation on Windows 2000......... 15 Overview ........................................... 1 Server Files...................................... 17 Uninstalling ..................................... 60

iPlanet Group Caching....................... 90

L

LDAP Active Directory attributes .............. 67 Add members to groups .................. 73 Add new groups............................... 71 Add new users ................................. 67 iFlowLDAPAdd.ldif........................ 65 Schema update permission .............. 64 Setup................................................ 63 Users and Groups ...................... 66, 81

M Microsoft® Active Directory............See

Directory Service Model API............................................ 1

P password properties ........................... 58

Index


S Schema update permission .................64 Security Features ..............................102 Security Mode ..................................102 Silent Mode installation....................107 SMTP

Host ..................................................21 Sun Java System Directory Server

Add new users ..................................81 Import iFlowLDAPAdd.ldif.............79 Set user permissions.........................87 Start ..................................................78

System Requirements Database .........................................4, 5 Directory Server .........................4, 5, 8

Operating system........................... 4, 5

T TCP/IP ............................................... 12 Template Library ............................... 53

Creating Users and Groups.............. 58 template_library.ldif ............................... 59 Troubleshooting ............................... 112

Interstage BPM Server startup ...... 114

U URM Admin ...................................... 25 User

Add .................................................. 67 Assign to LDAP Group ................... 66

Date post:	17-Mar-2018
Category:	Documents
Upload:	duongtuyen
View:	213 times
Download:	0 times

Interstage Business Process Manager Installation CentraSite administration This Manual Contains Here...

Documents