Download - EMC IT Process Centre Installation Guide · BPM Studio This is the primary application development tool for ITPC, which provides an Eclipse-based integrated development environment

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® IT Process Centre

Installation GuideP/N 300-004-621

REV A02

IT Process Centre Installation Guide2

Copyright © 2006 - 2007 Savvion Corporation. All rights reserved.

Published November, 2007

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to the Document/Whitepaper Library on EMC Powerlink.

Table of Contents

PrefaceAudience.......................................................................................................................................................6Information on ITPC Documentation ............................................................................................................7Conventions Used in this Manual .................................................................................................................8Product Support Contact Information ...........................................................................................................8Where to Get Help........................................................................................................................................8Your Comments ............................................................................................................................................9

Chapter 1—An Overview of ITPCITPC Components ...................................................................................................................................... 11How ITPC Works ........................................................................................................................................12ITPC User Types ........................................................................................................................................14

Chapter 2—Installation CD Contents & Pre-installation TasksITPC Installation CD Contents....................................................................................................................15ITPC Supported Platforms..........................................................................................................................16System Requirements ................................................................................................................................16Software Requirements ..............................................................................................................................17Supported Configurations...........................................................................................................................18Preparing Your Database for ITPC .............................................................................................................18

Preparing Your Database: Oracle 9i/10g.................................................................................................19Resizing the Oracle 9i/10g Tablespace.............................................................................................20

Preparing Your Database: Microsoft SQL 2000 ......................................................................................21Installing the MS SQL Server SP3 Driver .........................................................................................22Preparing the Microsoft SQL Server for XA Compliance ..................................................................22

Before You Begin........................................................................................................................................23

Chapter 3—Installing ITPCPrerequisites for ITPC Installation ..............................................................................................................24

System Information Required for Installation ..........................................................................................25Installing ITPC ............................................................................................................................................26

Indicating an Application Server..............................................................................................................31

3

Entering Email Server Information ..........................................................................................................33Selecting the User Management Interface ..............................................................................................34Defining the Database.............................................................................................................................36

Selecting the Database.....................................................................................................................36Entering Database Information .........................................................................................................38

Completing the Installer Wizard ..............................................................................................................38

Chapter 4—After Installing ITPCDatabase Cleaning Utility: setupSBM.........................................................................................................42

Using setupSBM for All Components ......................................................................................................42Using setupSBM for One Component .....................................................................................................43

JDBCRealm Utility: populateJDBCRealm ..................................................................................................44Using the Silent Installation Utility ..............................................................................................................45

Chapter 5—Getting Started with ITPCStarting the Servers in Windows.................................................................................................................46

Starting Servers in Windows on Pramati .................................................................................................46Starting Servers in UNIX.............................................................................................................................47

Starting Servers in UNIX on Pramati .......................................................................................................47Installing ITPC as a Windows Service........................................................................................................47

Installing ITPC as a Windows Service on Pramati ..................................................................................47Logging in to ITPC......................................................................................................................................50Using the ITPC AppServer Console ...........................................................................................................51Starting ITPC Modules on Windows ...........................................................................................................52Testing the ITPC Installation.......................................................................................................................53Testing the BizLogic Server and the BizLogic Mail Listener .......................................................................54

Testing the BizLogic Server.....................................................................................................................54Windows ...........................................................................................................................................54UNIX .................................................................................................................................................55

Stopping the Servers ..................................................................................................................................55Stopping the Servers in Windows............................................................................................................55

Pramati .............................................................................................................................................55Stopping Servers in UNIX........................................................................................................................55

Pramati .............................................................................................................................................56

Chapter 6—Using the Database Configuration ToolBefore Configuration...................................................................................................................................57Configuring the New Database...................................................................................................................58After Configuration......................................................................................................................................62Reverting to the Old Database ...................................................................................................................62

Chapter 7—Using the patchDeployer UtilityAbout the patchDeployer Utility ..................................................................................................................64

Installing a Patch .....................................................................................................................................64Removing a Patch ...................................................................................................................................65

Installation Guide 4 Contents

Chapter 8—Uninstalling ITPCUninstalling with the Uninstaller Wizard......................................................................................................66Additional Uninstalling Procedures.............................................................................................................68

Additional Uninstalling Procedures for Pramati Application Server.........................................................68

Appendix A—Frequently Asked Questions during Installation

Appendix B—Configuring Database Resource ParametersDatabase Resource Configuration for Pramati ...........................................................................................70

Datasource List .......................................................................................................................................70Connection Pool Properties for Ejb Server..............................................................................................71

jdbc/BizLogicDB................................................................................................................................71jdbc/BizPulseDB ...............................................................................................................................71jdbc/BizStoreDB................................................................................................................................72jdbc/JMSAdapterDBXA.....................................................................................................................72jdbc/SBMCommonDB.......................................................................................................................73jdbc/SBMCommonDBXA ..................................................................................................................73jdbc/jmsdb.........................................................................................................................................74jdbc/qrulesDB ...................................................................................................................................74jdbc/XMLDocRepositoryDB ..............................................................................................................75

Connection Pool Properties for Portal Server .........................................................................................75jdbc/jmsdb for Portal Server..............................................................................................................75jdbc/XMLDocRepositoryDB for Portal Server ...................................................................................76jdbc/SBMCommonDB for Portal Server............................................................................................76jdbc/SBMPortalsDB for Portal Server ...............................................................................................77

Appendix C—Improving BPM Portal PerformancePramati .......................................................................................................................................................78

Glossary

Index

Installation Guide 5 Contents

Preface

This guide is part of the documentation set for IT Process Centre (ITPC).

AudienceThe range of ITPC modules creates the opportunity for four types of users, summarized in the following table:

Table 1 ITPC User Types and Responsibilities

User Type ResponsibilitiesITPC User Responsible for carrying out specific business tasks using ITPC applications.

Examples include:

• An office administrator submitting an online purchase request.

• HR personnel scheduling interviews for a potential hire.

• A sales representative responding to a customer request.

• An engineer reviewing a trouble ticket reported by a customer.

ITPC Manager Responsible for automating business processes in a particular business domain. BPM Portal’s Management module serves as the primary interface to ITPC for the ITPC Manager, enabling the manager to monitor, analyze, and control business processes. Also uses the Process Modeler for modeling and simulation.

Application Developer Responsible for creating customized applications for implementing business processes and developing interfaces associated with tasks. ITPC application developers may work closely with ITPC business managers to define the requirements of an application, and determine the business processes.

ITPC Administrator Responsible for configuring ITPC components, managing user/group profiles, and administering ITPC applications and utilities.

6

Information on ITPC DocumentationIT Process Centre (ITPC) documentation contains information for the entire range of ITPC users. In the following table, we recommend the guides that are most relevant to each type of user.

Table 2 ITPC Documentation

If you are the… Read the…ITPC User BPM Portal User’s Guide

Quick Start GuideTerminology GuideTutorial Guide

ITPC Manager BPM Portal Manager’s Guide BPM Portal User’s GuideTerminology GuideTutorial Guide

Application Developer API Reference Guide Application Developer’s GuideBizLogic Developer’s GuideBizPulse User’s GuideBizSolo User’s GuideBPM Portal Manager’s GuideBPM Portal User’s Guidea

BPM Studio User’s GuideClustering GuideCustomization GuideManaged Adapters GuideQuick Start GuideTerminology GuideTutorial GuideWeb Services Developer’s Guide

a. Demonstrates how to thoroughly test ITPC applications.

ITPC Administrator BizPulse User’s Guideb

BPM Portal Administrator’s GuideBPM Portal Manager’s GuideBPM Portal User’s GuideInstallation GuideManaged Adapters GuideTerminology GuideTroubleshooting Guide for Administrators

b. Refer to the sections detailing BizPulse Admin.

Preface 7 Information on ITPC Documentation

Conventions Used in this ManualThis document uses the following conventions and terminology notations.

Product Support Contact InformationIf the product documentation does not provide a solution to your specific issue, or if you need clarification on the issue, please contact the EMC Product Support Team. You can contact the team through the Internet, e-mail, telephone, or by postal mail.

To enable us to quickly answer your questions, please have the following information available:

• Your name, installation site address and the license key for EMC software.

• Your ITPC version and build number.

• Your operating system, application server and browser, with version and service pack details, if any.

• Your database management system and version, and information on JVM and JDBC used.

Where to Get HelpEMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Table 3 Conventions in this Manual

Convention Purposebold Indicates titles of command buttons, check boxes, options, lists, dialog

boxes and portal page names.

bold italic Represents notes that alert you on specific ITPC elements and similar advisory information.

italic Indicates directory paths, file names and book titles.

monospace Represents code segments or examples.

backward slash “\” Indicates the path in Windows environment. For UNIX environment, replace with forward slash “/”

ITPC_HOME or %ITPC_HOME% Represents the installation directory of ITPC.

Preface 8 Conventions Used in this Manual

http://powerlink.emc.com

Your CommentsComments and suggestions about our product documentation are always welcome.

To provide feedback:

1 Go to: http://Powerlink.EMC.com

2 Click the Feedback link.

Preface 9 Your Comments

http://softwaresupport.EMC.com

Chapter 1

An Overview of ITPC

IT Process Centre (ITPC) is a comprehensive business process management platform, that enables companies to quickly transform their business processes into flexible and manageable Web applications, distributed over intranets, extranets, and the Internet.

Figure 1 ITPC Overview

ITPC addresses every stage in the business life cycle: Define, Integrate, Deploy, Monitor, Analyze, Improve, and Control. By adopting an end-to-end approach, ITPC incorporates all the key elements required to meet the ever-changing demands of e-business while providing customers with confidence for e-business success. Providing integrated management tools, ITPC lets customers monitor operations proactively, modifying automated processes on the fly based on changing external operations online.

10

ITPC ComponentsITPC is a suite of integrated components that enables you to easily build intranet, extranet, and Internet applications and manage your e-business. ITPC consists of the following components:

Figure 2 ITPC Components

Table 4 ITPC Components

Component DescriptionBPM PortalHome

The Home module of BPM Portal is the primary interface for ITPC Users, enabling them to interact with ITPC applications. Users can complete entries to various tasks and applications, and link to the support infrastructure required to achieve these tasks.

BPM Portal Management

The Management module enables ITPC Managers to query, report on, and control processes and resources, and is only visible to ITPC Managers.

BPM Portal Administration

The Administration module enables ITPC Administrators to modify configuration parameters, manage user/group access control, and install/uninstall ITPC applications.

Web Services This component allows ITPC application developers to; a) publish their applications as Web services, and b) find and convert other available Web services on the Internet into ITPC applications.

BizSolo This component provides a framework for developing and implementing Web-enabled workflow applications.

BPM Studio This is the primary application development tool for ITPC, which provides an Eclipse-based integrated development environment in which users can create ITPC applications, processes, Web applications, and rule files.

Process Modeler

This tool is used to design templates for basic business processes, and to run simulations of processes and individual worksteps. Users can also save or retrieve processes from the ITPC process repository.

An Overview of ITPC 11 ITPC Components

How ITPC WorksThe following figure provides an overview of the interaction between ITPC components.

Figure 3 How ITPC Works

BizLogic This is a flexible, lightweight, scalable workflow process engine for intranets, extranets, and the Internet.

BizPulse This open, event-driven rule engine is used to formulate and enforce policies in business applications.

Table 4 ITPC Components

Component Description

An Overview of ITPC 12 How ITPC Works

The following explanations correspond with the labels shown in Figure 3, and describe how the components operate.

A. BPM Studio and/or Process Modeler provide an integrated development environment (IDE) for ITPC, where you can design and deploy business processes. The application developer designs a process template in the IDE that reflects the business flow and other business process requirements. ITPC then generates an *.spt or *.swt file for the process template. If desired, business rules for the process template can be defined using the Rule Editor, a BizPulse component that is launched with BPM Studio.

B. The Web Container specifies a run time environment for servlet-based portals that include the BPM Portal, BizSolo and Web Services. The BPM Portal provides user interfaces for the Home, Management, and Administration modules.

C. Once the process template is defined, ITPC Administrators use the Administration module to install the process on the BizLogic server. ITPC Administrators can also configure ITPC components, manage user/group access control, and publish ITPC applications as Web services. Once installed, users access applications through servlets that pass the requests over an RMI/IIOP connection to the BizLogic server within an EJB Container.

D. The EJB Container provides a run time environment that executes and manages Java-based program components that run on the server side of a client/server network. Within the EJB Container are the BizLogic server and BizPulse server.

E. The BizLogic server writes events to event tables in the database. Each BizLogic process uses JDBC to connect to database server as well as store events in the database. Within the BizLogic server, BizStore uses JDBC to connect to the database server process and retrieve the events deposited by the BizLogic process. BizStore interprets the events and populates the process tables. These populated tables are used by BPM Portal modules.

F. Once the process template is installed as an ITPC application, ITPC Users use the Home module to access applications, obtain information to perform their tasks, and launch the application to start process instances from the BizLogic server.

G. Once the process template is installed as an ITPC application, ITPC Managers use the Management module to (depending on access privileges) launch the application to start process instances, monitor execution of process instances, and create reports. Servlets receive manager requests and pass them onto the BizLogic server over an RMI/IIOP connection. ITPC Managers use the Report Builder to define management reports that retrieve information through JDBC to the database server.

H. BizPulse is a rule-based event/message processing server that loads application rules and executes them against the BizLogic and/or external events/messages. This server persists data in the database for recovery and with the help of JDBC connects to the database.

I. Managed Adapters exchange information between ITPC applications and external applications by converting ITPC-specific protocol to the protocol of an external system such as a database or ERP system. When users add a Managed Adapter to a workstep, they can define complex mapping between ITPC dataslots and adapter inputs/outputs of the external application. At run time when the workstep is executed, the Managed Adapter sets the adapter inputs and configuration, and maps the outputs to the appropriate output dataslots.

J. BizSolo is a run-time component that executes the presentation flows. This component provides a Model, View, Controller (MVC) paradigm for developing presentation flow-based applications and executing them in a Web container.

An Overview of ITPC 13 How ITPC Works

K. ITPC’s Web Services component allows BizLogic and BizSolo applications to be published as Web services.

L. The relational database management system serves as a persistent store for all ITPC data storage needs. The BPM Portals and servers connect to DBMS using the JDBC driver.

ITPC User TypesThere are four user types within ITPC:

• ITPC Users. ITPC Users use ITPC applications to coordinate specific business tasks with another department within their company, with another company within their organization, and/or with a business partner in another organization. The Home module in BPM Portal serves as the primary interface in which ITPC Users run ITPC applications.

• ITPC Managers. ITPC Managers are typically experts in a particular business domain, such as Quality Assurance or Human Resources. They might need to work with managerial personnel from other groups in automating some of the business procedures that these groups share. The Management module in BPM Portal serves as the primary ITPC interface for business managers to coordinate and integrate business processes, enabling them to exchange information with each other, and to share functionality over such standard communication protocols as the Internet or e-mail.

• ITPC Application Developers. ITPC Application Developers are responsible for analyzing business processes and developing interfaces associated with tasks or processes creation. Application Developers are often not domain experts themselves, but work closely with ITPC Managers to define the business process and determine the requirements of an application. Application Developers use BPM Studio or Process Modeler to define the business process; the resulting process template file is tested, simulated, deployed and run as an ITPC application.

• ITPC Administrators. ITPC Administrators are responsible for configuring ITPC components, managing user/group profiles and access control, and installing/uninstalling ITPC applications. The Administration module in BPM Portal serves as the primary ITPC interface for ITPC Administrators to administer ITPC applications.

All ITPC user types can communicate by using one or more ITPC applications and/or by communicating between ITPC applications and external applications. Examples include:

• A QA Department manager requesting the Human Resources Department to approve the hiring of a QA Engineer.

• HR personnel coordinating interview scheduling with a regional office in another state.

• Engineers collaborating with a business partner’s Engineering Department to develop specifications for an application.

An Overview of ITPC 14 ITPC User Types

Chapter 2

Installation CD Contents & Pre-installation Tasks

This chapter reviews the contents of the ITPC Installation CD, details pre-installation tasks relating to database setup, and describes the ITPC licensing policy.

ITPC Installation CD ContentsITPC is delivered on a CD-ROM containing documentation and software (listed in Table 5) that you may access from the CD-ROM prior to installing ITPC. User guides are in PDF format and are found under the ITPC_HOME\docs\ directory, and JavaDocs are in HTML format and can be found under the ITPC_HOME\docs\ITPC APIs\ directory. Responses to Frequently Asked Questions (FAQs) are found in the sbminfo directory, as well as animated demonstrations in Flash that illustrate procedures for creating an application and other commonly used process definition tasks.

Table 5 ITPC Installation CD Contents

Directory/Item ContentsInstaller For Windows (2000, Server 2003 and XP), Redhat Linux 3.0, and Sun

Solaris 9/10 installations.

Install.cmd and Install.sh Install.cmd for Windows installation and Install.sh for UNIX installationa.

a. UNIX installation procedures apply to Solaris, and Linux operating systems.

LicenseAgreement.txt License Agreement

Release_Notes.htm, images Release Notes files and images folder

docs The ITPC documentation set includes a range of user guides in PDF format and JavaDocs that contain HTML files describing ITPC APIs. This documentation enables you to discover how to use ITPC. For a complete listing, see ITPC Documentation in the Preface.

patches Contains patch and readme file for specific issues.

sbminfo Contains two folders: faqs and flashdemos. The faqs folder contains responses to frequently asked questions; and the flashdemos folder contains animations of common used ITPC procedures.

15

ITPC Supported PlatformsThe following table lists the platforms supported by ITPC 2.1.

System RequirementsTable 7 describes the minimum and recommended requirements for installing and running ITPC 2.1 on Windows and UNIX (Procedures described under the UNIX heading apply to Solaris, and Linux operating systems).

Table 6 ITPC-Supported Platforms

Category SoftwareApplication servers Pramati Server 4.1 SP4 (embedded in ITPC)

Operating systems Microsoft Windows 2000 Professional/Advanced with SP 4 Microsoft Windows Server 2003 Standard/Enterprise Microsoft Windows XP SP2 (for Browser, Process Modeler and BPM Studio only)

Sun Solaris 9/10 (Solaris SPARC only supported for ITPC servers. BPM Studio and Process Modeler only supported on Windows)

Browsers Internet Explorer (IE) 6.0 SP1 (Requires Java plugin JDK 1.4.2; only supported on Windows; Needs to disable MS JVM)

Mozilla FireFox 1.0.7 (Requires Java plugin JDK 1.4.2)

Java Technology (J2EE) Java Development Kit J2SDK 1.4

J2EE 1.3/1.4 (including JDBC 2.0, EJB 2.0, JCA 1.0, JSP 1.2, Servlet 2.3, JTA 1.0.1, JMS 1.0.1/1.0.2, JNDI 1.2, Java RMI 1.0, RMI/IIOP 1.0, JAAS 1.0, JavaMail 1.2, JAXP 1.1). Specific service information depends on your application server.

Database / JDBC Driver Oracle 9i and 10g, with Oracle JDBC thin driver.

Microsoft SQL Server 2000 SP3

Compatible mail servers Sendmail (UNIX)

Exchange or IMAP compatible (Windows)

User management ITPC Realm (File-based) and ITPC Realm (DB-based)

JDBC (Database based) authentication on all platforms

Microsoft Active directory, on Windows 2000 and Windows Server 2003

Sun Java System Directory Server 5.2, on Windows 2000 or Solaris 9/10

External Realm support, on Windows 2000.

Table 7 System Requirements

Equipment Minimum RecommendedProcessor Pentium IV 1GHz or

UltraSPARC-III 900 MHzDual CPU Pentium IV 1GHz & up orDual CPU UltraSPARC-III 900 MHz and up

Memorya 2 GB RAM 2 GB of RAM

Free disk spaceb 1GB 1 GB and up. Depending on the application server you are using, you may need additional free disk space.

Peripherals CD-ROM CD-ROM

Installation Guide 16 ITPC Supported Platforms

Software RequirementsThe following table lists software that must be installed on your system before you install ITPC 2.1. If the required software is not already installed on your system, install it in the order listed.

IMPORTANT! You may encounter problems with ITPC archiving utilities when using old JDBC drivers.

a. Please set your virtual memory setting to at least twice the recommended memory setting. You must restart your ma-chine to set the virtual memory. Please see your System Administrator if you require more assistance in setting virtual memory.b. For installing ITPC on a FAT partition, we recommend you have at least 2000MB of free disk space. On NTFS or FAT 32, we recommend at least 1000MB of free disk space.

Table 8 Software Requirements

Software NotesApplication server Pramati Server 4.1 SP4 (embedded in ITPC)

Microsoft Internet Explorer 6.0+orMozilla FireFox 1.0.7

Microsoft Internet Explorer only supported on Windows. You need to disable MS JVM. Both browsers require Java plugin (JDK 1.4.2).On Mozilla, use the contributed build by SUN for Solaris.

Oracle 9i and 10g

or

Microsoft SQL Server 2000 SP3

Before you install ITPC, have the database up and running.If you are running an OCI driver, you must install the Oracle client on the machine where ITPC is installed. For the thin driver, the Oracle client is not required.

Use MS Windows 2000 Professional/Advanced with SP3 or MS Windows Server 2003 Standard/Enterprise. Both case-sensitive and case-insensitive instances are supported..

Java Development Kit J2SDK 1.4 and J2EE 1.3/1.4.

JDBC Driver For Oracle 9i/10g: JDBC thin driver in classes12_01.zip and classes12_9i.zip files.For MS SQL Server 2000: MS JDBC Driver

Installation Guide 17 Software Requirements

Supported ConfigurationsITPC has been extensively tested on the platforms, tools and systems listed in the following table.

Preparing Your Database for ITPCBefore installing ITPC, the Database Administrator must perform a series of actions to prepare the database. These actions are described in the following sections for Preparing Your Database: Oracle 9i/10g, and Preparing Your Database: Microsoft SQL 2000.

Table 9 Tested and Supported Configurations

Server Operating System Browser Application Server

DatabaseMgt.

SystemJ2SDK User

Management

MS Windows 2000 with Service Pack 4+

IE 6.0 SP1orMozilla FireFox 1.0.7

Pramati Server 4.1 SP4 (embedded in ITPC)

Oracle 9i/10gMS SQL Server 2000 SP3

J2SDK 1.4 ITPC File-based (PAK)ITPC DB-based (JDBC)LDAP Realm:• Microsoft Active

Directory

MS Windows Server 2003 Standard/Enterprise

as above Pramati Oracle 9i/10gMS SQL Server 2000 SP3

J2SDK 1.4 ITPC File-based (PAK)ITPC DB-based (JDBC)LDAP Realm:• Sun Java System

Directory Server 5.2

Sun Solaris 9/10 as above as above Oracle 9i/10g

J2SDK 1.4 as above

Redhat Enterprise Linux AS 3.0

as above Pramati Oracle 9i J2SDK 1.4 ITPC File-based (PAK)ITPC DB-based (JDBC)LDAP Realm:

Win XPa Prof. SP2

a. For Browser and BPM Studio only.

IE 6.0 SP1 N/A N/A J2SDK 1.4 N/A

Installation Guide 18 Supported Configurations

Preparing Your Database: Oracle 9i/10g

Before installing ITPC 2.1, the Database Administrator must perform a series of actions to prepare the Oracle 9i/10g database for ITPC. The following scripts show how to manage (create and drop) User and Tablespace for Oracle 9i. To use these scripts for Oracle 10g, substitute 10g for 9i throughout.

• createTableSpace_9i.sql

• createUser_9i.sql

• dropUser_9i.sql

• dropTableSpace_9i.sql

To resize an Oracle 9i/10g database, see Resizing the Oracle 9i/10g Tablespace on page 20.

1. Create a tablespace by executing createTableSpace_9i.sql, as shown in the following SQL statements. The following script also creates a temporary tablespace:

CREATE TABLESPACE ebms_USER_DATADATAFILE 'ebms_USER_DATA.ORA' SIZE 256MDEFAULT STORAGE( INITIAL 16K NEXT 16K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 50)ONLINE;

CREATE TEMPORARY TABLESPACE ebms_TEMPORARY_DATATEMPFILE 'ebms_TEMPORARY_DATA.ORA' SIZE 64MEXTENT MANAGEMENT LOCAL;

-- Make sure that the tablespaces have been created correctly --

SELECT TABLESPACE_NAME, STATUS FROM DBA_TABLESPACES;

EXIT

2. Create a database user in the system and grant privileges by executing createUser_9i.sql, as shown in the following SQL statements:

CREATE USER ebms IDENTIFIED BY ebms DEFAULT TABLESPACE ebms_USER_DATA;

GRANT create session, create table, create sequence, create view To ebms;

ALTER USER ebms

Installation Guide 19 Preparing Your Database for ITPC

QUOTA UNLIMITED ON ebms_USER_DATA;

-- -- Make sure that the user has been created correctly --

SELECT USERNAME FROM sys.dba_users;

EXIT

3. Drop a tablespace from the system by executing dropTableSpace_9i.sql, as shown in the following SQL statements:

-- -- Drop tablespaces and rollback segment. -- Note: Make sure you remove ebms data files explicitly. --

DROP TABLESPACE ebms_USER_DATA INCLUDING CONTENTS CASCADE CONSTRAINTS;

SELECT TABLESPACE_NAME, STATUS FROM DBA_TABLESPACES;

4. Drop a database user from the system by executing dropUser_9i.sql, as shown in the following SQL statements:

DROP USER ebms CASCADE;

-- -- Make sure that the user has been dropped correctly --

SELECT USERNAME FROM sys.dba_users;

IMPORTANT! ITPC with Oracle 9i needs at least 50 open_cursors. Set this parameter in init.ora or the initorcl.ora file in the $ORACLE_HOME/Database directory. For your convenience, a script is provided in ITPC_HOME/dbscripts/oracle/createUser_9i.sql that contains the required SQL statements specific to Oracle 9i.

Resizing the Oracle 9i/10g Tablespace

The following procedures describe how to resize Oracle 9i to a user’s tablespace (datafile). To use these procedures for Oracle 10g, substitute 10g for 9i throughout.

1. To coalesce (or defragment) the free space in a user’s tablespace, enter the following command:ALTER TABLESPACE <tablespace_name> COALESCE;

2. To resize the datafile, enter the following command:ALTER DATABASE DATAFILE <data_file_name> RESIZE <n> K|M;

For example:

ALTER DATABASE DATAFILE D:\oracle\ora2\database\ITPC_USER_ORA RESIZE 256M;


Note: You can only decrease the size of the datafile with the space that is free between the highest used block of the datafile and the last block of the datafile. If the tablespace is fragmented, the free spaces between these blocks cannot be deallocated in this way.

To resize a temporary tablespace (or tempfile), we recommend creating a new temporary tablespace and dropping the existing one, since it is difficult to reduce the size of the TEMP table while it is online.

1. Create a new temporary tablespace, by entering the following command:CREATE TEMPORARY TABLESPACE <tablespace_name> TEMPFILE <datafile_name> SIZE <n> K|MEXTENT MANAGEMENT LOCAL;

For example:

CREATE TEMPORARY TABLESPACE ebmsNEW_TEMPORARY_DATATEMPFILE ebmsNEW_TEMPORARY_DATA.ORA SIZE 64MEXTENT MANAGEMENT LOCAL;

2. Alter the existing user (in ITPC) to have the new temporary tablespace as its temporary tablespace, by entering the following command:ALTER USER <user_name> TEMPORARY TABLESPACE <tablespace_name>;

For example:

ALTER USER ebms TEMPORARY TABLESPACE ebmsNEW_TEMPORARY_DATA;

3. Drop the old temporary tablespace by entering the following command:DROP TABLESPACE <old_tablespace_name>;

For example:

DROP TABLESPACE ebms_TEMPORARY_DATA;

Preparing Your Database: Microsoft SQL 2000

To prepare the Microsoft SQL Server for ITPC, complete the following steps:

1. Create a database, such as the following:CREATE DATABASE sbm ON PRIMARY( NAME = sbm_6_1_dat,FILENAME = 'c:\mssql2000\data\sbm_6.mdf',SIZE=256MB,FILEGROWTH=10% ),( NAME = sbm_6_2_dat,FILENAME = 'c:\mssql2000\data\sbm_6.ndf',SIZE=64MB,FILEGROWTH=10% )LOG ON( NAME = sbm_6_log,FILENAME = 'c:\mssql2000\data\sbm_6.log',SIZE=5MB,FILEGROWTH=10% )COLLATE SQL_Latin1_General_CP1_CS_AS;


COLLATE specifies the name of the default collation for the database. The collation name can either be a Windows collation name or an SQL collation name. If not specified while creating the database, the database is assigned the default collation of the SQL Server instance.You can also determine the case sensitivity|case insensitivity setting in the Collation name field of the General tab. SQL_Latin1_General_CP1_CI_AS is the Case Insensitive (CI) setting and is the default setting. As shown in the last line above, SQL_Latin1_General_CP1_CS_AS is the Case Sensitive (CS) setting.

Note: ITPC 2.1 supports both Case Insensitive and Case Sensitive databases for Microsoft SQL 2000. Applications developed with Case Insensitive databases in earlier releases should be used with Case Insensitive databases in this current release.

2. Create a database user in the system and grant privileges by executing the following SQL statements:USE sbm;

EXEC sp_addlogin 'sbm','sbm','sbm';EXEC sp_grantdbaccess 'sbm';EXEC sp_addrolemember 'db_owner','sbm';EXEC sp_adduser 'login_name','schema_name';

3. Set the database options according to the following:EXEC sp_dboption @dbname='sbm',@optname='ANSI null default',@optvalue='on';

Installing the MS SQL Server SP3 Driver

Install the Microsoft SQL Server 2000 Driver for JDBC Service, Service Pack 3 by performing the following steps:

1. Navigate to the Microsoft Website (http://www.microsoft.com/downloads/) and download the SQL Server 2000 for JDBC SP3.

2. By default, this download is installed in C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC. This installation contains the following:

• msbase.jar, mssqlserver.jar and msutil.jar drivers in the MSSql\drivers\sqlserver2000-jdbc-sp3 directory.

• sqljdbc.dll and instjdbc.sql files in the MSSql\dlls_for_MSSqlServer2000_Sp3 directory.

3. Copy the msbase.jar, mssqlserver.jar and msutil.jar drivers in the MSSql\drivers\sqlserver2000-jdbc-sp3 directory to the ITPC_HOME/lib directory.

Preparing the Microsoft SQL Server for XA Compliance

To add XA compliance to your Microsoft SQL Server:

1. You can either manually perform procedures to add XA compliance or use a ITPC-provided script to facilitate the addition of XA compliance.

The following steps describe how to manually add XA compliance (For an alternative procedure that uses a script to add XA compliance, see Step 2 below.):


http://www.microsoft.com/downloads/

a. Copy the sqljdbc.dll file from Microsoft SQL Server 2000 Driver for JDBC to the SQL_Server_Root/binn directory of the database server for SQL server.

b. From the server, use the ISQL utility to run the instjdbc.sql script. Before running this script, the System Administrator should back up the master database.

c. At a command prompt, use the following syntax to run instjdbc.sql:

d. ISQL -Usa -P sa_password -S server_name -i location\instjdbc.sql

e. where: sa_password is the password of the system administrator; server_name is the name of the server on which SQL server resides; and location is the full path to instjdbc.sql.

f. The instjdbc.sql script generates many messages. In general, you can ignore these messages, but scan the output for any messages that indicate an execution error. The final message should indicate that instjdbc.sql ran successfully. The script may fail if there is not enough space available in the master database to store the JDBC XA procedures or to log the changes to existing procedures.

g. Start the Distributed Transaction Coordinator service on the machine where the SQL server is running. The Distributed Transaction Coordinator service can be started from Control Panel > Administrative Tools > Services.

2. You can alternatively use a script to add XA compliance:

a. Navigate to the ITPC_HOME\bin directory and open the setupmssqlxa.bat file.

b. Edit the file to enter values in the listed parameters (e.g., user name, password, etc.)

c. Copy this file to your database machine and execute it.

Before You Begin

IMPORTANT! The initial ITPC 2.1 installation is a fresh install.

Complete the following tasks before beginning the installation process:

1. Verify the ITPC Installation CD contains the items listed in Table 5 on page 15.

2. Review the list of ITPC-supported platforms, as shown in Table 6 on page 16.

3. Review the system and software requirements, as listed in Table 7 and Table 8, respectively.

4. Review the tested and supported configurations for ITPC, as listed in Table 9.

5. Read the Release Notes available on the ITPC Installation CD.

Installation Guide 23 Before You Begin

Chapter 3

Installing ITPC

EMC provides an intuitive Installer wizard that enables you to easily install ITPC 2.1. The Installer wizard uses InstallShield® MultiPlatform 5.0.1 for all supported operating systems. Insert the ITPC Installation CD into the CD drive to start the installation process.

Consult with your local system administrator for specific information concerning certain Windows and UNIX operating system settings and database issues including those related to user management policy, Web server configuration, and TCP port numbers. You will need administration privileges on your machine to install ITPC.

Prerequisites for ITPC InstallationBefore installing ITPC, verify that the prerequisite software has been installed correctly. Consult the following table to verify proper installation:

Note: Before installing, check the patches directory on the Installation CD for information on patches for specific issues. Open the patches directory, select an issue and review the readMe file.

Table 10 Software Prerequisites Checklist

Software Verify that...J2SDK ... the JDK\bin directory is in the system environment path.

Application server ... the selected application server is installed properly and that you are able to run it.

Database and JDBC driver

... you have an account and can access the database server. See Database Cleaning Utility: setupSBM on page 42 for information on how to clean the database.

24

To ensure a smooth installation, check the following before installing ITPC:

• For Windows, make sure that no active Java tasks (java.exe) are present in the Task Manager. After shutting down the application server, check if any Java tasks in the Task Manager are active. If so, make sure they are shut down.

• Ensure that the database is up and running on a local or remote machine, or ensure that the database connection is established if using client/server.

System Information Required for Installation

Although the Installer wizard guides you through the installation, you will need to enter system information into the Installer dialogs, as summarized in Table 11. Collect the system information needed by the ITPC installer before starting the ITPC installation.

Table 11 System Information Prerequisites

Information NotesITPC destination foldera

By default, the installer uses C:\ITPC. Ensure the drive is not a network drive. See Selecting the Destination Location on page 28 for additional recommendations.

Mail server address ITPC uses e-mail to notify the administrator and users when certain events occur.

Mail server address format: MyMailServer.MyDomain

Example: mail.company.com

BizLogic system administrator's e-mail address

An e-mail address in the following format: [email protected]. This person is responsible for administrating ITPC.

BizLogic e-mail address

ITPC maintains a special user account for use by BizLogic via e-mail, i.e., a company’s time card notification can be sent via e-mail notifying the recipient of a task to perform in ITPC.

BizLogic e-mail address format: [email protected]

User Managementb Select the user management realm you plan to use for your installation:

• ITPC File-based (PAK) Realm. A text-based system that reads user, password, and other ITPC user-specific information from the ums_users.txt file. Also reads general and specific group information from ums_groups.txt file.

• ITPC DB-based (JDBC) Realm. User management system built on a database that can be modified using the Administration module after installation. Reads user, password, group and ITPC specific information from the database.

• LDAP-Sun Java System Directory Server or

• LDAP-MS Active Directory Realm. Employs the LDAP directory service to retrieve user, password and group information.LDAP Server Name: The name of the LDAP server.LDAP Port: The number of the LDAP port.LDAP DIT Information: Directory Information Tree (DIT) information.LDAP Login Information: Directory-specific login information.

See User Management Interface Setup for LDAP on page 35 for more information.

Language The installer selects the correct language determined by your operating system. Currently, English (United States) is the only supported language.

Installation Guide 25 Prerequisites for ITPC Installation

IMPORTANT! If you get a message indicating that there is not sufficient space in your default temporary directory, we recommend that you use a temporary directory, of 1 GB of available space, for ITPC before launching the installer. To use a non-default temporary directory during installation at the command line, enter: on Windows: setupwin32.exe -is:tempdir <directory_name>on Solaris: setupsolarisSparc.bin -is:tempdir <directory_name>on Linux: setuplinux.bin -is:tempdir <directory_name>

Installing ITPCInsert the Installation CD in the CD-ROM drive to begin the installation process. Make sure that a Windows or UNIX operating system (Procedures described under the UNIX heading apply to Solaris, and Linux operating systems) is already running.

Inserting the ITPC Installation CD launches the Installer wizard, which presents options in a series of dialog windows that enable you to install ITPC on your machine. Most of the dialog windows provide default values, which, if you accept them, result in a standard installation. Where appropriate, the Installer wizard prompts you for confirmation before initiating important actions.

Web Server Port Number

The HTTP port number used by your application server. The default application server is Pramati 4.1 SP4, with the Portal Server HTTP Port of 8181; and the EJB Lookup Port of 9292.

Note: Changing the port number during installations is for ITPC configuration purposes only and does not change the Web server port number. The Web server port number should remain fixed.

Protocol for Application server

The two supported protocols are: HTTP and HTTPS for SSL enabled Web servers.

Application Server By default, Pramati 4.1 SP4 is the application server. Before installing ITPC to Pramati, note where the Pramati home directory is, e.g., C:\ITPC.

JDBC Driver This driver depends on the type of database used. See Table 8.

Database URL Consult with your local database administrator.

If you use the default Oracle database management system, an example format for the host alias is jdbc:oracle:thin:@DB_Server_Name:port #:SID

Other default values for Oracle are:

• server name: localhost

• port number: 1521

• SID: orcl

DB User Name & Password

Ask the database administrator at your site to create an account with a user name and password to access the database. You are prompted during the installation to enter the user name and password your database administrator has set up for you. A user name and password are required to run ITPC applications.

ITPC program folder The default name is ITPC.

a. We strongly suggest installing to the recommended directory. If you decide to install in another directory, long path names may cause problems in the automatic configuration, due to string length limitations with InstallShield.b. See the BPM Portal Administrator’s Guide for additional information about case sensitivity in user names and passwords for user management.

Table 11 System Information Prerequisites

Information Notes

Installation Guide 26 Installing ITPC

Note: In addition to the automated installation start or if the installation options do not display, you may start the installation process from your browser. Open the browser, navigate to the CD-ROM drive and open the Install.cmd for Windows or the Install.sh for UNIX.

To begin the installation of ITPC:

1. Insert the ITPC Installation CD into the CD-ROM drive.

Open the Installer directory. For Windows, run Install.cmd. For UNIX, run Install.sh.

The Installer wizard opens, providing options that enable you to install ITPC on your machine. After selecting an installation option, you must enter data in a series of dialog windows to correctly install and configure ITPC.

2. After the process of extracting files has completed, the Welcome page opens (see the following figure). Review the text, then click Next.

Figure 4 Welcome to the Installer Wizard


3. The End User License Agreement dialog box appears. Review the agreement. If you accept the terms of the agreement, select the I accept... option, as shown in the following figure. Click Next.

Figure 5 License Agreement

Note: If you want to change any of the settings at any point during the installation, click Back to return to a previous page and make the necessary changes. Click Cancel at any point during the installation to cancel the installation and exit the Installer wizard. Click Next to accept the displayed information and continue with the installation of EMC IT Process Centre 2.1.

Selecting the Destination Location

The Installer wizard next detects and selects the destination location. For Windows, it selects the bootup drive as the default directory for ITPC installation. As shown in the following figure, C:\ITPC is the default directory and folder destination for ITPC. For UNIX, the default is /opt/ITPC.

1. Accept the default destination or click Browse to locate the destination folder you prefer.


Note: Due to certain InstallShield™ limitations, we recommend you use no more than five characters for your destination folder name.

Figure 6 Choosing the Destination Location

2. If you are installing ITPC on a FAT partition, we recommend you have at least 2000 MB of free space. On NTFS or FAT 32, we recommend at least 1000 MB. If you must use a drive formatted as FAT and you are having installation problems, free up some disk space and attempt the installation again. For more information, please see the Release Notes included on the ITPC Installation CD.

3. Click Next to continue. You may experience a delay after clicking Next, because the installer is running background checks during this step.

Note: Regardless of how you launch the ITPC installation, the information needed by the Installer wizard for the ITPC installation and configuration are the same. To avoid installation errors, carefully review the information entered in the various dialogs before proceeding to the next dialog.

Selecting the Installation Features

Select installation features for ITPC 2.1 from the following options:

• EMC IT Process Centre

• ITPC Documentation


We recommend you accept the defaults, as shown in the following figure, and click Next.

Figure 7 Selecting Features for Installation

Entering Host and Domain Names Information

Enter your Host name and Domain name, as shown in the following figure. The value, Iss.emc.com, is provided as a default for the Domain name. Whether installing in Windows or UNIX, make sure you enter a value in the Domain field, since the EJB Server will not start correctly if the field is left blank. When finished, click Next to continue.

Figure 8 Defining Host Name and Domain Name


Indicating an Application Server

The Application Server page (see the following figure) enables you to indicate the application server you use to deploy the ITPC application.

Figure 9 Indicating the Application Server

1. Select one of the following options:

• Embedded Appserver (Pramati 4.1 SP4). Provided with the installation CD.

2. After selecting the application server, click Next.

If you selected Pramati as you application server, the Specifying Server Ports page (see Figure 10 on page 32) appears.

Specifying Server Ports

The Specifying Server Ports page appears, where you can specify the configurable ports that are assigned to your application server.


1. For Pramati application servers, the page shown in the following figure appears. Accept the default settings or enter specific and unique port numbers. Select the Advanced check box to open a window where you can review advanced port settings the include various EJB Server or Port Server ports.

Figure 10 Selecting Server Ports for Pramati Application Server

2. Click Next to continue.

Selecting the Host Portal URL

The Host Portal URL page appears next. Review the text displayed. If necessary, revise the default Host Portal URL to a URL that can access your BPM Portals.

1. If Pramati is your application server, the default Host Portal URL is <machine_name>.domain_name:8181, as shown in the following figure.

Figure 11 Choosing the Host Portal URL for Pramati Application Servers



Entering Email Server Information

The Mail Server Information page appears for all application servers, enabling you to configure your Mail Server.

1. To properly configure the Email server, enter the following information:

a. Mail Server. The server name and domain name of your Email server, if different from the default values shown in the following figure. For example, mail.company_name.com

Figure 12 Configuring the Outgoing Mail Server

b. ITPC Administrator E-Mail. The email address of the ITPC administrator who receives BizLogic mail. For example, ITPCadmin@company_name.com.

c. BizLogic E-Mail. BizLogic e-mail ID for sending BizLogic information to the ITPC administrator. For example, blemail@company_name.com

Select the check box tospecify the

BizLogicMail Login andIncoming Mail Server


2. If you select the check box in Figure 12 above stating “Check here if you want to specify your BizLogic Mail Login and Incoming Mail Server.” and click Next, the Incoming Mail Server and BizLogicMail User Account dialog box appears (see the following figure).

Figure 13 Defining the Incoming Mail Server and BizLogicMail User Account

a. Specify the Incoming Mail Server. If desired, select “User Name for BizLogic Mail” or “User Name and Password for BizLogic Mail” in the Incoming Mail Server and BizLogicMail User Account dialog box and click Next.

b. In the following BizLogic Mail Login window, enter your BizLogic Mail user name and/or password and click Next.

c. If a user name or a user name and password is supplied for BizLogic Mail, you are prompted to enter the information each time the BizLogic Mail Server is used while you are running ITPC.

d. Click Next, and the installation continues to the User Management Interface dialog box.

Note: The BizLogic Mail user name and/or password appear in parameters in the ITPC_HOME\conf\ITPCemail.properties file.

Selecting the User Management Interface

Select from the following available user management options: ITPC: FILE BASED (PAK), ITPC: DB BASED (JDBC), LDAP-Sun Java System Directory Server or LDAP-MS Active Directory. ITPC supports the Sun Java System Directory and Microsoft Active Directory servers.


The User Management Interface page appears for all application servers. As shown in the following figure, the default is ITPC: FILE BASED. Select a user management system. Click Next to continue.

Figure 14 Choosing the User Management Interface

Note: For additional information about the user management options, see “User Management” in the BPM Portal Administrator’s Guide.

User Management Interface Setup for LDAP

If you selected LDAP for your user management, you are prompted to enter additional information. Review the examples provided by the installer for entering the requested information.

Information needed for LDAP-Sun Java System Directory Server or LDAP-MS Active Directory:

1. Enter the LDAP server and LDAP port information, as shown in the following figure. It is not mandatory to enter LDAP domain information. Click Next to continue.

Figure 15 Entering LDAP Server Information


2. Enter information on the Directory Information Tree in the DIT-User-Root and DIT-Group-Root boxes. Click Next to continue.

3. Enter your User name and Password for the LDAP server. Click Next to continue.

Note: After completing ITPC installation, configure the MS Active Directory and the Sun Java System Directory LDAP servers manually in BPM Portal Administration. For further information on how to configure the LDAP servers after completing the ITPC installation, see the BPM Portal Administrator’s Guide.

Defining the Database

The next several pages enable you to indicate your database management system and define the database.

Selecting the Database

1. Select either Oracle 9i Oracle 10g, or Microsoft SQL Server 2000 as your database management system.

Figure 16 Indicating a Database

Note: You can change the database or database parameters after you have installed ITPC by using the Database Configuration Tool. For more information, see Chapter 6, Using the Database Configuration Tool.

2. If you selected Oracle as your database management system, the following figure appears.

a. Accept the defaults or enter new data for the database URL Prefix, Server Name, and Port Number.


b. In the last field, enter the SID (the server ID default is orcl).

Figure 17 Defining the Database for Oracle

3. If you selected MS SQL Server 2000 as your database management system, a prompt appears (see following figure) that informs you of steps to take to deploy MS SQL.

Figure 18 MSSQL Prompt

a. Click OK and the following page appears. Figure 19 Defining the Database for MS SQL Server

b. Accept the defaults in URL Prefix, Server Name and Port Number or enter specific values. Enter the correct database name and server name in the URL Properties box.



Entering Database Information

You must next enter login information to connect to your database.

1. Enter a user name and password for the database in the appropriate boxes of the database login information page, as shown in the following figure that appears for all server/database setups.

Figure 20 Entering Database Login Installation Information


Completing the Installer Wizard

Perform the following procedures to complete the Installer wizard.


Verifying the Connection to the Database

The Database Connection page appears (see the following figure), enabling you to verify the connection to your database, or to bypass the verification of the database connection.

Figure 21 Verifying the Database Connection Page

1. Click the Yes, I want to verify... option to verify that your database has a valid connection.

2. Click the No, I do not want to verify option to continue the Installation wizard without verifying your database connection.



Selecting the Program Group

By default, all installation shortcuts are in the ITPC 2.1 folder, under Start > Programs > EMC. The window in the following figure appears for all application servers and enables you to change the program group folder in which the installation shortcuts are kept.

Figure 22 Selecting the Program Group Page

1. Accept the default or enter a new folder name in the text box.


Reviewing the Installation Summary

The Installation Summary page enables you to review the choices you made during the ITPC Installation.

Figure 23 Installation Summary Page


1. If you want to change any of the settings, click Back to return to the appropriate page and make the necessary changes.

2. Click Cancel to cancel the installation and exit the Installer wizard.

3. If you accept the displayed information, click Next.

Installing ITPC

As shown below, the Installer wizard displays the progress of the installation of ITPC.

Figure 24 Installing ITPC

Successful Completion of the Installer Wizard

A Success message is displayed after the Installer wizard has successfully completed (see below). Click Finish to exit the Installer wizard and continue with the installation of ITPC 2.1 on your machine.

Figure 25 Installing Success Message


Chapter 4

After Installing ITPC

After you have initially installed ITPC by using the Installer wizard (see Installing ITPC on page 26), perform the following additional settings or configurations to ensure that your ITPC installation is set up correctly.

Database Cleaning Utility: setupSBMThe setupSBM utility creates ITPC system tables (database tables), and removes and redefines all previous database tables.

BizPulse, BizLogic, User Management, Event and Access Control List (ACL) Management maintain database repositories in different locations, depending on the configuration setup. The failure of one component can cause inconsistency in application data. Using the setupSBM utility deletes information in these databases, cleans up ITPC application data and resets ITPC.

Note: Close ITPC and your application server before running the setupSBM utility. Not doing so may render ITPC inoperable or cause a JDBC exception. For more information, see Stopping the Servers on page 55.

Using setupSBM for All Components

To apply the setupSBM utility to all components, run the following command from the ITPC_HOME\bin directory:

CAUTION! We recommend backing up data you want to save before executing this command.

setupSBM -c ALL -u [UserName]-p [password]

42

Since UNIX is case-sensitive, enter the setupSBM utility in the case shown above. You may use either upper case or lower case in Windows 2000. If you are using an MS SQL 2000 database, you can add -s [schemaname] to the above command to specify the schema name. If the schema name is not specified, then it will be assumed to be the same as the user name.

Note: For BizLogic stand-alone servers, apply the setupBizLogic utility by running the following command: setupBizLogic -u [UserName] -p [password]

If your system is unable to find the setupSBM command, enter the following directory path: D:\SBM\bin setupSBM -c.

ALL includes all of the following components: BizPulse, BizLogic, User Management, Event and Access Control Management (ACL Manager).

For UserName and password, enter a user name and password (the default is “ebms” for both user name and password). A user with a valid user name and password is granted all the default permissions of ITPC. A new user is created with a specified password for JDBC Realm. Because ITPC does not modify the LDAP repository, verify that the user exists in the LDAP before assigning a user name.

After entering the user name and password, you are asked to confirm your decision to proceed with the cleanup operation.

Do you really want to initialize database tables of SBM? (y/n):

To continue, enter “y” and press Enter to proceed with the cleanup operation.

The setupSBM utility is completed when the following message appears:

SBM database setup has been completed successfully.

Note: ITPC also provides Load and Unload utilities that guard against the unchecked growth of database tables during installation and allow easy movement of data between database servers. For more information, see Unloading and Loading from the Database Tables in Chapter 9 of the BPM Portal Administrator’s Guide.

Using setupSBM for One Component

To use the setupSBM utility for an individual component, run the following command from the ITPC_HOME\bin directory and enter one of the following component names: BizPulse, BizLogic, User Management, Event or Access Control Management (ACL Manager). In the example below, the setupSBM utility is used for ACL.

setupSBM -c ACL

See Table 12 for a listing of user name and password requirements for each component.

After entering the user name and password, you are asked to confirm your decision to proceed with the cleanup operation.

Do you really want to initialize database tables of SBM? (y/n):

Installation Guide 43 Database Cleaning Utility: setupSBM

To continue, enter “y” and press Enter to proceed with the cleanup operation.

Note: If you run the setupSBM utility for one component, be aware that data pertaining to other components may remain in the system, causing application data inconsistency.

Table 12 provides the user name and password requirements for the various ITPC components.

Note: BizLogic Designer and BizSolo Designer are deprecated, and we recommend using BPM Studio or Process Modeler to design applications. You can, however, open BizLogic Designer or BizSolo Designer by entering the following command from the ITPC_HOME\bin directory: designer or designer -bizsolo.

JDBCRealm Utility: populateJDBCRealmThis utility imports user information from previous realms into the ITPC DB-Based Realm (JDBCRealm). To run this utility, enter the following: populateJDBCRealm <realmName>

<realmName> represents the previously used realm (SBMRealm, NISRealm or LDAPRealm) that the user wants to import data from.

If you want to run the utility and take information from SBMRealm (also referred to as PAKRealm), you must use PAKRealm as the parameter, as in the following: populateJDBCRealm <PAKRealm>

Parameters for other realms require proper setup in the umacl.conf file before running this utility. For example, if you want to run the utility and take information from NISRealm, enter as shown below:populateJDBCRealm NISRealm

Then set the NISServer and NISDomain parameters in the umacl.conf file to the correct values.

Table 12 User Name and Password Requirements for ITPC Component

Component RequirementsALL or User Management Requires both user name and password.

Access Control Management (ACL Manager)

Requires user name.

BizPulse User name and password not required. Recreates all BizPulse tables except those of the Database Event Channel.

BizLogic User name and password not required. Recreates all BizLogic tables except those of the Database Event Channel.

Event User name and password not required. Recreates all BizEvent, BizStoreEvent and BizPulseEvent tables, but does not change BizLogic or BizPulse tables.

Installation Guide 44 JDBCRealm Utility: populateJDBCRealm

Using the Silent Installation UtilityAfter initially installing ITPC through the Installer wizard, you can create a template response file that contains all the commands you used in your initial installation. You can then use this response file to install ITPC without going through the Installer wizard. This “silent” installation mode can be used to install ITPC on multiple and/or remote systems.

1. To generate the response file:

• For Windows: setupwin32.exe -options-record <response file name>

• For UNIX: setupsolarisSparc.bin -options-record <response file name>

Note: Make sure the response file name includes the complete path information.

2. To use the silent installation mode:]

• For Windows: setupwin32.exe -silent -options <response file name>

• For UNIX: setupsolarisSparc.bin -silent -options <response file name>

Installation Guide 45 Using the Silent Installation Utility

Chapter 5

Getting Started with ITPC

After installing ITPC, we recommend testing several modules of the system. This chapter describes how to start the servers, perform the ITPC installation tests, and stop the servers in case you need to restart the system or perform an upgrade.

Starting the Servers in WindowsTo start ITPC in a Windows operating system, you must first start the servers that are associated with your selected application server. Procedures for starting servers in Windows for each application server supported by ITPC are presented in the following sections.

Starting Servers in Windows on Pramati

To start ITPC while using Pramati as your application servers, start the EJB server and the Portal server before you start the ITPC servers, as shown in the following steps:

1. To start the EJB server:

Start > Programs > EMC > ITPC 2.1 > Start Servers > EJB Server

Wait until the server has started (approximately 1-2 minutes) before proceeding to the next step. Please wait until the starting process has been completed. Starting ITPC before allowing the starting of application servers to be completed can result in errors.

2. To start the Portal (or application) server:

Start > Programs > EMC > ITPC 2.1 > Start Servers > Portal Server

Wait until the server has started (approximately 1-2 minutes) before proceeding to the next step. Please wait until the starting process has been completed. Starting ITPC before allowing the starting of application servers to be completed can result in errors.

3. To start the ITPC servers (after starting the EJB and Portal servers):

Start > Programs > EMC > ITPC 2.1 > Start Servers > Start ITPC Servers

46

4. By default, the Connect to BizLogic Server dialog box appears. You must enter your User Name and Password.

5. When finished entering your data, click OK to complete starting the servers.

Starting Servers in UNIXTo start ITPC in a UNIX operating system, you must first start the servers that are associated with your selected application server. Procedures described under the UNIX heading apply to Solaris, and Linux operating systems.

To start ITPC in UNIX with Pramati 4.1, start the Portal server first, then the EJB server, and finally the ITPC servers.

If your system supports X-Windows server, then make sure that the DISPLAY environment variable is set properly in the shell where the portal server starts from. Enter setenv DISPLAY <machine_name>:<number> to set the environment variable before starting the servers. However, if your system does not support X-Windows server, and if the DISPLAY variable is not set for it, then you should modify the startPortalServer.sh and add the property -Djava.awt.headless=true, as shown in the following example, to start the portal server in headless mode.

VM_ARGS=$JAVA_OPTIONS" -Djava.awt.headless=true ..."

IMPORTANT! Complete each command before you execute the next one.

Note: Make sure the server processes do not exit when you log out or disconnect.

Starting Servers in UNIX on Pramati

Start the servers for Pramati by entering the following commands:

cd pramati/server/bin./startEjbServer.sh ./startPortalServer.shcd <SBM_HOME>/bin./startSBM.sh

Installing ITPC as a Windows ServiceYou may install ITPC as a Windows service on Pramati application servers.

Installing ITPC as a Windows Service on Pramati

This section explains how to install ITPC as a Windows service on Pramati 4.1 SP4 (assuming a single server). We provide shortcuts to the scripts to install or uninstall ITPC EJB Server or ITPC Portal Server as a Windows Service. In the following steps, the ITPC home directory is referred to as “ITPC_HOME”.

Installation Guide 47 Starting Servers in UNIX

1. To install ITPC EJB Server as a Windows Service: go to the Start menu and choose Programs > EMC > ITPC 2.1 > ITPC Windows Services > Install ITPC EJB Service;or, open a command window and go toSBM_HOME\pramati\services\jsw\j2eeserver and execute install_server_ejbServer.bat.

2. To install ITPC Portal Server as a Windows Service: go to the Start menu and choose Programs > EMC > ITPC 2.1 > ITPC Windows Services > Install ITPC Portal Service;or open a command window and go to:SBM_HOME\pramati\services\jsw\j2eeserver and execute install_server_portalServer.bat.

3. To install a user defined Windows Service named ‘sbmservice’, go to: ITPC_HOME\bin

and execute: instsrv sbmservice SBM_HOME\bin\srvany.exe.

4. To configure sbmservice, complete the following:

a. From the Start menu, open the Windows Registry Editor by selecting Run and entering regedt32. Click OK.

b. Locate the following key: HKEY_LOCAL_MACHINE\SYSTEM > CurrentControlSet > Services > sbmservice.

c. From the Edit menu, select Add Key. Enter “Parameters” in the Key Name box. Click OK.

d. Highlight the Parameters key in the left pane. From the Edit menu, select Add Value. Enter “Application” in the Value Name box and select REG_SZ from the Data Type list. Click OK.

e. The String Editor window appears. Enter “%winnt%\system32\cmd.exe” as the String data for the “Application” value.

f. Create another value by entering “AppParameters” in the Value Name box and selecting REG_SZ from the Data Type list. Click OK and enter “/k ITPC_HOME\bin\startsbm.bat” as the String data for the “AppParameters” value.

g. Create a third value by entering “AppDirectory” in the Value Name box and selecting REG_SZ from the Data Type list. Click OK and enter “ITPC_HOME\bin” as the String data for the “AppDirectory” value.

h. Locate the key “sbmservice” once again in the left pane. To create a value, enter “DependOnService”. Select REG_MULTI_SZ from the Data Type drop-down list. Click OK. In the Multi String Editor, enter “PramatiServerejbServer”. Click OK.

i. Go to the startsbm.bat file. Edit the file and add your user name and password information; e.g.,%ITPC_HOME%\bin\startBizLogicServer.bat -u <user_name> -p <password>

Installation Guide 48 Installing ITPC as a Windows Service

5. Optionally, if you want to make sure that Pramati ejbServer is completely started before the sbmservice is started, confirm that the following changes are made in startSBM.bat.

Add:set initialdelay=240set retryinterval=10call %ITPC_HOME%\bin\setblclientenv.batjava -classpath %CPATH% com.tdiinc.common.util.ServiceManager -i %initialdelay% -f %retryinterval% -appServer pramati

beforestart call %ITPC_HOME%\bin\startBizLogicServer.bat -u ebms -p ebms

where initialdelay is the time in seconds after which the utility tries to see whether the ejbServer has started and retryinterval is the time in seconds after which it retries to see whether the server has started.

A sample startSBM.bat with these changes follows:@echo offset ITPC_HOME=C:\ITPCprset initialdelay=240set retryinterval=10call %ITPC_HOME%\bin\setblclientenv.batjava -classpath %CPATH% com.tdiinc.common.util.ServiceManager -i %initialdelay% -f %retryinterval% -appServer pramati

start call %ITPC_HOME%\bin\startBizLogicServer.bat -u ebms -p ebmsstart call %ITPC_HOME%\bin\startBizPulseServer.batexit

6. Optionally, if you want to ensure that “PramatiJ2eeServer” and “sbmservice” are functioning correctly, test them as follows:

a. From the Windows Control Panel, open Administrative Tools and then open Services. Select Pramati J2eeServer ejbServer or Pramati J2eeServer portalServer. Open the Properties dialog window for each service and, with the General tab open, change the Startup type to Manual for each service. Open the Log On tab and select the Allow service to interact with desktop check box for each service. Clear this option for production mode.

b. Reboot the machine to allow the registry manager changes to take effect.

c. To start “sbmservice,” open the Windows Control Panel. Select Services. A command window pops up. Here is your opportunity to fix any problems shown in the window.

d. Login, logout, and reboot your machine to test the “sbmservice” automatic start up and the newly created services.

7. To uninstall all servers as a Windows service:

• Go to ITPC_HOME\pramati\services\jsw\j2eeserver, and execute remove_server_ejbServer.bat and remove_server_portalServer.bat. This removes Pramati as a service.

• Go to ITPC_HOME\bin and run: instsrv sbmservice removeThis command uninstalls ITPC as a service.

Installation Guide 49 Installing ITPC as a Windows Service

Note: Stopping sbmservice will not stop the ITPC servers. The ITPC servers must be stopped manually.

Logging in to ITPCAfter starting the servers, log in to ITPC by performing the following procedures.

1. Log in to BPM Portal, where you need to log in only once to gain access to ITPC modules (that include Home, Management and Administration) and applications for which you have permissions.

To log in to BPM Portal, select:

Start > Programs > EMC > ITPC 2.1 > Login to BPM Portal

Note: If you are using a client machine, login to ITPC by entering http://machine_name.domain_name:port_number/sbm/bpmportal/login.jsp in your browser.

2. If you logged in to BPM Portal, the BPM Portal Login page appears (see the following figure).

Figure 26 BPM Portal Login Page

a. Enter your User name and Password (‘ebms’ and ‘ebms’ are the default values), and click Login.

Installation Guide 50 Logging in to ITPC

b. The BPM Portal opens to the Home Task List page (see the following figure). From this page, you can navigate to other portals, assuming you have the corresponding privileges and permissions. For more information, see the BPM Portal Administrator’s Guide.

Figure 27 BPM Portal Home Page

c. If you have Manager’s permissions, click the Management tab to open the Management module. For more detailed information, see Chapter 4 in the BPM Portal Manager’s Guide.

Using the ITPC AppServer ConsoleThe ITPC AppServer Console enables users with the required permissions to install, configure, monitor, manage and deploy one or more application servers that, for ITPC 2.1, include Pramati.

1. To access the ITPC AppServer Console for Pramati, you can use the following shortcut: Start > Programs > EMC > ITPC 2.1 > ITPC AppServer Console, opening the Server Management Console GUI for the application server.

2. Enter a user name and password. The user name and password required to access the ITPC AppServer Console differs according to your application server. For example:

• If Pramati is your application server, log in to the ITPC AppServer Console with the user name “root” and the password “pramati”.

Installation Guide 51 Using the ITPC AppServer Console

3. Use the functions in the Management Console to:

• Create views on multiple servers.

• Perform remote and unified management of application servers and applications deployed on them.

• Seamlessly deploy applications on servers and clusters.

• Remotely deploy applications across firewalls.

• Create special alert messages that can be received on any device.

• Maintain a high level of security that supports JAAS framework.

Starting ITPC Modules on WindowsThis section assumes that you started the servers and that you have the required permissions to start the following ITPC modules.

Table 13 Starting ITPC Modules on Windows

To start... Perform the following...BPM Portal To open BPM Portal on the host (installation) machine:

From the Start menu, select Programs > EMC > ITPC 2.1 > Login to BPM Portal. The BPM Portal Login page opens.You must enter your user name and password to access BPM Portal.

If you are accessing BPM Portal from a client machine, enter the following in your browser:

http://machine_name.domain.com:port_number/sbm/bpmportal/login.jspBPM Portal Administration

To open the Administration module of BPM Portal on the host (installation) machine:

From the single sign-on BPM Portal page, click the Administration module tab, select System and then the Status submenu option. The status of the servers is displayed.

If you are accessing the Administration module from a client machine, enter the following in your browser:

http://machine_name.domain.com:port_number/sbm/bpmportal/administration/system_status.jspFor example:

http://oxygen.yourcompany.com:18793/sbm/bpmportal/administration/system_status.jspNote: Use the predefined values of “ebms” and “ebms” for the user name and password only if you are using the ITPC Realm (file-based user management).

BPM Portal Home To open the BPM Portal User’s Home on the host machine:

From the single sign-on BPM Portal page, click the Home module tab, and select one of the links displayed in the Home menu bar;

If you are accessing BPM Portal User’s Home from a client machine, enter the following in your browser:

http://machine_name.domain.com:port_number/sbm//bpmportal/myhome/tasks.jspNote: Use the predefined values of “ebms” and “ebms” for the user name and password only if you are using the ITPC Realm (file-based user management).

If you installed applications in BPM Portal Administration, you will see Applications listed in the ITPC Applications page.

Installation Guide 52 Starting ITPC Modules on Windows

Testing the ITPC InstallationBefore testing, review the information contained in Table 13.

To test the ITPC installation, complete the following steps:

BPM Portal Management

To open BPM Portal Management on the host machine:

From the single sign-on BPM Portal page, click Management, and select one of the links displayed in the menu bar;If you are accessing the Management module in BPM Portal from a client machine, enter the following in your browser:http://machine_name.domain.com:port_number/sbm/bpmportal/management/loverview.jspNote: Use the pre-defined values of “ebms” and “ebms” for the user name and password only if you are using the ITPC Realm (file-based user management).

BizLogic Admin If you would like to install or remove applications, you can use BizLogic Admin as an alternate to the Administration module in BPM Portal. In addition to installing or removing applications, there are multiple ITPC commands available in BizLogic Admin.

Note: Start the BizLogic server before starting BizLogic Admin.

To access BizLogic Admin choose:

Start > Programs > EMC > ITPC 2.1 > ITPC Servers > BizLogic > Start BizLogic Admin

Or in Windows go to:ITPC_HOME\bin\StartBizLogicAdminTo get a list of commands available in BizLogic Admin, enter the following:connect <user name> <password>help

Type exit to close the window.

Or in UNIX to access BizLogic Admin, enter in a UNIX shell:startBizLogicAdmin.sh

To get a list of commands available in BizLogic Admin, enter:connect <user name> <password>help

Type exit to close the window.

BizPulse Admin As an alternate to the Administration module in BPM Portal, you can use BizPulse Admin to monitor the state of the BizPulse server, or administer the rules, events, infopads or other internal application objects of the BizPulse server.

To access BizPulse choose:Start > Programs > EMC > ITPC 2.1 > ITPC Servers > BizPulse > Start BizPulse Admin

Or in UNIX to access BizPulse Admin, enter in a UNIX shell:startBizPulseAdmin.sh

and view the list of commands available in BizPulse Admin.

Note: Start the ITPC servers before starting BizPulse.

Table 13 Starting ITPC Modules on Windows

To start... Perform the following...

Installation Guide 53 Testing the ITPC Installation

1. For Pramati application servers: start the servers in the following sequence: the Portal server, the EJB managed server and the ITPC servers.

2. Click Login to BPM Portal, opening the BPM Portal Login page. Enter a valid user name and password. You can use “ebms” for both if you are using ITPC Realm (file-based user management).

Note: If you are using LDAP authentication, you will need to create the manager account (for example, “ITPC”) and a password before logging into the Management module of BPM Portal.

3. Assuming that the Administrator has installed the required applications and provided you with the appropriate permissions (see the BPM Portal Administrator’s Guide for more information), navigate to your Home in the BPM Portal and create one or more instances of the sample application(s).

Successfully starting the sample application(s) demonstrates that BizLogic and BPM Portal are functioning properly. To test BizPulse, start the sample application Assign_A_Task_Ver5 in BPM Portal, which contains rules.

4. Navigate to the Management module from the BPM Portal page and select the menu links within Management. Successful navigation through the Management module while testing links indicates Management and BizLogic are functioning properly.

Testing the BizLogic Server and the BizLogic Mail Listener

The BizLogic mail listener (Incoming Mail Server) enables you to use the E-mail Support option to get mail from other worksteps and processes to complete a task. The Outgoing Mail Server sends mail notifications.

Note: Depending on your individual setup, the Incoming Mail Server and the Outgoing Mail Server may reside on the same machine, or may reside on different machines. The configuration settings for these servers are contained in different configuration files. The BizLogic mail server configuration is contained in ITPC_HOME\conf\.

Testing the BizLogic Server

After reviewing the sbmemail.properties file, start the BizLogic server. The BizLogic server starts automatically when a ITPC session is started. Run the BizLogic server in order to run the BizLogic MailServer.

To check if the BizLogic server is running without starting a ITPC session, perform one of the following:

Windows

Navigate to the ITPC_HOME\bin directory and open startBizLogicAdmin.bat.

If BizLogic server is running, a command window is launched where you can access the available commands.

Installation Guide 54 Testing the BizLogic Server and the BizLogic Mail Listener

UNIX

Open a shell. Navigate to the ITPC_HOME\bin directory and open startBizLogicAdmin.sh.

If BizLogic server is running, a command window is launched where you can access the available commands.

Stopping the Servers To stop ITPC in Windows and UNIX operating systems, you must first stop the servers that are associated with your selected application server.

Stopping the Servers in Windows

Procedures for stopping servers in Windows for each application server supported by ITPC are presented in the following sections.

Note: When stopping the servers, you must use the reverse sequence in stopping that you did when starting the servers.

Pramati

If Pramati is your application server, stop the servers by the following methods:

1. In the BPM Portal, click the Logout link in the Navigation bar, which returns you to the Login page. Click the Close button or select File > Close to exit BPM Portal.

2. Stop the ITPC servers by selecting: Start > Programs > EMC > ITPC 2.1 > Stop Servers > Stop ITPC Servers; or run the stopSBM from the command line.

3. Stop the Portal (or application) server by selecting: Start > Programs > EMC > ITPC 2.1 > Stop Servers > Portal Server.

4. Stop the EJB server by selecting: Start > Programs > EMC > ITPC 2.1 > Stop Servers > EJB Server.

You are prompted to press a key to initiate the stopping process. Open the Start Portal Server command window and wait until another key prompt appears, completing the stopping process. This procedure may take some time (depending on the number of applications you have installed and your machine’s configuration).

Stopping Servers in UNIX

To stop ITPC in UNIX, perform the following procedures.

Note: Complete each command before you execute the next one.

Note: Make sure the server processes do not exit when you log out or disconnect.

Installation Guide 55 Stopping the Servers

Pramati

Stop the servers for Pramati by entering the following commands:

cd <ITPC_HOME>/bin./stopSBM.shcd <ITPC_HOME>/pramati/server/bin./stopPortalServer.sh./stopEjbServer.sh

Installation Guide 56 Stopping the Servers

Chapter 6EMC

Using the Database Configuration Tool

While working with the existing installation of EMC, you can choose to use another database and point EMC setup to it. You can configure the new database with EMC using the Database Configuration Tool. This is a special EMC Tool and can be accessed from the Start menu. The Database Configuration Tool changes the database-related properties in all EMC *.conf and *.properties files, and uses appserver MBeans to delete and recreate the appserver data sources with the new properties.

Note: The DB Configuration tool is not supported for EMC clustering.

Before ConfigurationBefore you configure the new database, carry out the following procedures.

1. Ensure that the new database is correctly installed and a valid user is created.

2. Stop the servers in the correct sequence, according to the application server you are using.

3. If you are changing to a different database management system (DBMS), copy the new driver jars to the EMC_HOME\lib folder and restart the Database Configuration tool. Depending on the database you are using, you need to rename its corresponding driver file(s) as follows, and copy it/them in the EMC_HOME\lib directory.

• Oracle: classes12_01.zip

• MSSQL: msbase.jar, msutil.jar, and mssql.jar

4. Start only the EJB Server and the Portal Server. If you are using a Pramati application server, give “nobody” group ALLPermission. You can do this through the Admin console: Go to:

• localhost:8282/admin

57

• user: root

• password: pramati

a. Click on Security on the left pane.

b. Click on system realm on the right pane.

c. Click on “nobody” group on the right pane and check ALLPermission.

d. Repeat for the Portal Server in the Admin console, with localhost:8181/admin.

Configuring the New DatabaseTo open the Database Configuration Tool:

1. Select Start > Programs > EMC > EMC 2.1 > Tools > DB Configuration Tool. An Instructions window is displayed as shown in the following figure. The information displayed in this window contains instructions to be followed before and after using the Tool and is specific to the application server with which EMC is installed.

Figure 28 Database Configuration Tool, Instructions Window

Installation Guide 58 Configuring the New Database

2. Click Next, displaying the Current Database Configuration window, as shown below.

Figure 29 Database Configuration Tool, Summary of Current Database Configuration

3. Click Next. The Database Selection window is displayed as shown in the following figure.

Figure 30 Database Configuration Tool, Select Database

4. Select the DBMS you want to configure. Options supported for the current 2.1 release are: Oracle 9i/10g and Microsoft SQL Server 2000.


5. Click Next. The Database Properties window for Oracle 9i is displayed, as shown in the following figure. The window for other database management systems are slightly different.

Figure 31 Database Configuration Tool, Database Properties

6. Enter the database properties to construct the database URL.

7. Click Next. The Database User Details window is displayed as shown in the following figure.

Figure 32 Database Configuration Tool, Database User Details

a. Enter a valid User Name and Password.

b. For Encrypt Password option, select Yes if you want to keep the password encrypted.

c. Click Test DB Connection to validate the database details entered. On successful validation, a confirmation message is displayed. If you enter invalid details, an error message is displayed.


8. Click Next. The Host Details window for Oracle is displayed, as shown in the following figure. The window for MS SQL Server is slightly different.

Figure 33 Database Configuration Tool, Host Details

9. Enter the details. Ensure that your port specification is valid, and does not conflict with the other servers.

10. Click Next. A prompt appears, asking you to make sure that the Portal and EJB servers (for Pramati application servers) are running. Click OK.

Figure 34 Server Prompt

11. The Server URL window for a Pramati server opens, displaying the details of the currently running servers. For Pramati, only EJB and Portal Server details are displayed.

Figure 35 Database Configuration Tool, Server URL Window

12. Verify the server URLs and click Next. If the servers are running, and validated, the Database Configuration Tool prompts, as shown in the following figure.


Figure 36 Configuration Prompt

13. Click Yes. The New Database Configuration window is displayed, as shown in the following figure.

Figure 37 Database Configuration Tool, Summary of New Database Configuration

14. Click the Test to validate... button to validate the new Data sources. When they are validated, a confirmation message is displayed. The new database is now correctly configured. If the database connection is not successful, a message appears that directs you to the DBConfigTool.log file.

15. Click Finish. A Message appears, prompting you to perform the actions covered in the next section.

After ConfigurationAfter you have successfully configured the new database and tested the data sources, carry out the following steps.

1. Stop the servers with stopServer command. Do not use Ctrl + C.

2. Run updateSBM.bat|sh.

3. Run setupSBM.bat|sh.

4. Start the servers again in the required sequence.

EMC is now ready with the new database.

Reverting to the Old DatabaseIn case you need to revert to your original setting, follow these instructions.

Installation Guide 62 After Configuration

1. Stop all the servers.

2. Rename the following files to their original names:

• sbmdb.properties.orig

• sbm.conf.orig

• sbm/adapters/db/conf/db.properties.orig

3. For Pramati, rename resource-config.xml.orig to resource-config.xml in the server/nodes/ejbServer/config and server/nodes/portalServer/config directories.

Note: To configure your database to the application server’s default settings, see Appendix B, Configuring Database Resource Parameters.

Installation Guide 63 Reverting to the Old Database

Chapter 7

Using the patchDeployer Utility

EMC provides the patchDeployer utility, enabling users to deploy patches on an existing installation. This tool applies the patch, copies the patch files in all the required locations, redeploys and updates the ear and war files, and keeps track of the patches given to a customer.

About the patchDeployer UtilityThe patchDeployer utility is based on Apache ANT, and uses customized ANT tasks to apply the patches. This utility contains an xml file, ITPC_HOME/conf/sbm-files.xml, that lists ITPC files and specifies their type and location. Based on this xml file, the patchDeployer utility applies the patch. The utility generates and updates another xml file, ITPC_HOME/patches/sbm-patches.xml, that lists all the patches applied on the installation and the order in which they were applied. The patchDeployer utility also backs up files during patch deployment and stores them in the ITPC_HOME/patches/bkup/b4_<patchID> directory.

Technical Support provides each customer with a *.zip file that typically contains all the files in one directory that is identified with a specific patch ID; e.g., PATCH3234.zip may contain all the files needed to fix BUG 1234 AND BUG 1235. The Patch zip file contains two subdirectories: ejbapps and webapp. The ejbapps subdirectory contains all the ears that are required; the webapp subdirectory holds all the files that need to be updated under the webapp.

The patchDeployer utility provides Pramati cluster support. It uses the sbm-cluster.xml file as the cluster configuration file, reading information regarding the cluster.

Installing a Patch

Upon receiving the Patch zip file, extract the contents to the ITPC_HOME/patches directory. Open the command line to ITPC_HOME/bin, and run applyPatch.bat|sh PATCH<ID>. To use our example from the previous paragraph, run ITPC_HOME\bin\applyPatch.bat PATCH3234.

64

The patchDeployer utility deploys all the files under the ITPC_HOME/patches/PATCH3234 directory and, based on the sbm-files.xml, decides whether to copy the file in various locations or to copy/redeploy the ear if that particular file is an ear.

The patchDeployer utility also backs up all original files that are affected under the ITPC_HOME/patches/bkup directory. It also automatically provides details of the patch and keeps track of the order in which patches were installed. For example, the directory structure after successfully installing three patches will be as follows:

ITPC_HOME/patches/PATCH3234ITPC_HOME/patches/PATCH3235ITPC_HOME/patches/PATCH3236

ITPC_HOME/bkup/b4_PATCH3234ITPC_HOME/bkup/b4_PATCH3235ITPC_HOME/bkup/b4_PATCH3236

After patch installation, the sbm-patches.xml file is also updated, and includes patch details and patch order information. For example, if it is the first patch, the patch order is 1; if it is the second patch, it is assigned patch order 2, and so on.

Note: Make sure that the webapp directory under ITPC_HOME/patches/<patchID> is not empty.

Removing a Patch

If you want to remove a patch, or want to return to a ITPC installation state that existed before a patch was applied, run the following: ITPC_HOME\bin\removePatch.bat PATCH3236.

The utility checks with the sbm-patches.xml file to verify the patch order and ensures that the intended patch removal corresponds with Last In - First Out criteria. If you try to remove a previous patch before the one last installed; e.g., removing PATCH3235 before removing PATCH3236, the patchDeployer utility prompts you to remove the last-installed patch before proceeding.

Installation Guide 65 About the patchDeployer Utility

Chapter 8

Uninstalling ITPC

To uninstall EMC IT Process Centre (ITPC), go to Start > Programs > EMC > ITPC 2.1 > Uninstall ITPC and use the Uninstaller Wizard to manually remove ITPC. The Uninstaller wizard does not provide support for module level uninstalling. The Uninstaller uninstalls all modules, regardless of the initial Setup Type of installation. In ITPC 2.1 installation, nothing is removed from pre-existing software programs.

Uninstalling with the Uninstaller WizardPerform the following procedures to uninstall ITPC:

1. To uninstall ITPC on Windows: Select Start > Programs > EMC > ITPC 2.1 > Uninstall ITPC.

2. To uninstall ITPC on UNIX, run <ITPC_HOME>/_uninst/uninstaller.bin.

3. The Uninstaller wizard opens to the Welcome page (see the following figure). Review the text and click Next.

Figure 38 Welcome to the Uninstaller Wizard

66

4. As shown in the figure below, verify that the correct features are selected. Click OK to confirm deletion of the indicated features and continue with the uninstallation.

Figure 39 Selecting Features to Uninstall

5. An Uninstaller Summary page appears. (see the following figure). Verify the summary is correct. Click Next if it is correct.

Click Back if you wish to return to previous windows and change any information. Click Cancel to end the uninstallation process and exit the Uninstaller wizard.

Figure 40 Uninstaller Summary Page

Installation Guide 67 Uninstalling with the Uninstaller Wizard

6. The Remove Existing Files dialog box appears. Click Yes to all.

The layout of this dialog box depends on the application server you are using. The Remove Existing Files dialog box is shown in the figure below.

Figure 41 Remove Existing Files Prompt

7. The Uninstaller Successful page appears (see the following figure). Click Finish to complete uninstalling ITPC.

Figure 42 Uninstaller Success Message

Additional Uninstalling ProceduresThe Uninstall procedure does not completely remove all previously installed ITPC data. You may have to manually remove certain files and folders to ensure that all previously installed ITPC data is removed.

To complete the uninstallation of ITPC, perform the following steps:

Additional Uninstalling Procedures for Pramati Application Server

If you do not want to save any applications you have created or modified, you can select the <ITPC_HOME> folder (in this case, the ITPC folder in the C drive) and delete it from the directory. The pramati directory is contained within the ITPC folder. If you want to save any applications, move them to another folder before you delete the ITPC folder.

Installation Guide 68 Additional Uninstalling Procedures

69

Appendix A

Frequently Asked Questions during Installation

Occasionally, users encounter problems during installation. Below are some frequently asked installation questions and answers you can use to resolve problems. If you have further questions, review the EMC Product Support Team Website or contact the EMC Product Support Team at [email protected].

Table 14 Windows Troubleshooting

Problem SolutionMy ITPC session ends or an exception is thrown.

When a problem occurs with ITPC, such as a system, server or servlet crash, then check the ITPC log files. If you can, access the Log Viewer in the Systems tab of the Administration module or open the log file located in the directory folder where ITPC is installed.

Installed applications on ITPC do not appear in the Management module in BPM Portal.

Application names and associated access privileges are not added to the BizManageUsers.properties file in the ITPC_HOME\BizManage\reports directory. You can manually modify this file or log into the Administration module to assign these applications to a user.

The following error appears:

"sbm.domain.com cannot be resolved by the DNS server"

This error may occur if your computer is not connected to the network (DNS server) for Windows 2000.

Modify your "hosts" file under%Winnt%\system32\drivers\etc. You need to add your machine name in front of "localhost", as shown in the following:

127.0.0.1 localhost MyMachine MyMachine.MyDomain.com

And/Or

Machine IP address YourMachineName.

Appendix B

Configuring Database Resource Parameters

This appendix presents the default parameters of database resources for the application servers supported in ITPC 2.1. If you have changed database resource parameters and want to tune these parameters back to the default values, please refer to the default settings provided in the following sections.

Database Resource Configuration for PramatiTo tune the database parameters for Pramati Portal Server, log in to the Portal Server Admin Console (localhost:8181/admn user: root, password: pramati). Open Configure in the left pane and click Resources.

To tune the database parameters for Pramati EJB Server, log in to the EJB Server Admin Console (localhost:8282/admn user: root, password: pramati or click Start > Programs > EMC > ITPC 2.1 > ITPC AppServer Console). Open Configure in the left pane and click Resources.

Datasource List

Table 15 Datasource List for Ejb ServerDatasource Name Connection Factory

Namejdbc/BizLogicDB SBMDB_CF

jdbc/BizPulseDB SBMDB_CF

jdbc/BizStoreDB SBMDB_CF

jdbc/JMSAdapterDBXA SBMDB_CF

jdbc/SBMCommonDB SBMDB_CF

jdbc/SBMCommonDBXA SBMDB_CF

jdbc/jmsdb SBMDB_CF

70

Connection Pool Properties for Ejb Server

jdbc/BizLogicDB

jdbc/BizPulseDB

jdbc/qrulesDB SBMDB_CF

jdbc/XMLDocRepositoryDB SBMDB_CF

Table 16 Datasource List for Portal ServerDatasource Name Connection Factory

Namejdbc/SBMCommonDB for Portal Server SBMDB_CF

jdbc/jmsdb for Portal Server SBMDB_CF

jdbc/SBMPortalsDB for Portal Server SBMDB_CF

jdbc/XMLDocRepositoryDB for Portal Server SBMDB_CF

Table 17 Connection Pool Properties for jdbc/BizLogicDBName jdbc/BizLogicDB

Driver Class (driver class needs to be specified at the connection factory level and will be the same for all datasources using the same connections factory)

Oracle oracle.jdbc.driver.OracleDriver

MSsql com.microsoft.jdbc.sqlserver.SQLServerDriver

Connection Pool PropertiesMaximum Size 40

Minimum Size 1

Initial Size 1

Refresh Interval 300

Idle Time out 300

Connection Req Timeout 10

Prepared Statement Cache Size 150

Transaction Participation True (XA_enabled)

Table 18 Connection Pool Properties for jdbc/BizPulseDBName jdbc/BizPulseDB




Connection Pool Properties

Table 15 Datasource List for Ejb Server

Installation Guide 71 Database Resource Configuration for Pramati

jdbc/BizStoreDB

jdbc/JMSAdapterDBXA

Maximum Size 20

Minimum Size 1

Initial Size 1


Idle Time out 300



Transaction Participation True

Table 19 Connection Pool Properties for jdbc/BizStoreDBName jdbc/BizStoreDB





Minimum Size 1

Initial Size 1


Idle Time out 300



Transaction Participation False

Table 20 Connection Pool Properties for jdbc/JMSAdapterDBXAName jdbc/JMSAdapterDBXA





Minimum Size 1

Initial Size 1

Table 18 Connection Pool Properties for jdbc/BizPulseDB


jdbc/SBMCommonDB

jdbc/SBMCommonDBXA


Idle Time out 300




Table 21 Connection Pool Properties for jdbc/SBMCommonDBName jdbc/SBMCommonDB





Minimum Size 1

Initial Size 1


Idle Time out 300




Table 22 Connection Pool Properties for jdbc/SBMCommonDBXAName jdbc/SBMCommonDBXA





Minimum Size 1

Initial Size 1


Idle Time out 300




Table 20 Connection Pool Properties for jdbc/JMSAdapterDBXA


jdbc/jmsdb

jdbc/qrulesDB

Table 23 Connection Pool Properties for jdbc/jmsdbName jdbc/jmsdb





Minimum Size 1

Initial Size 1


Idle Time out 300




Table 24 Connection Pool Properties for jdbc/qrulesDBName jdbc/qrulesDB





Minimum Size 1

Initial Size 1


Idle Time out 300





jdbc/XMLDocRepositoryDB

Connection Pool Properties for Portal Server

jdbc/jmsdb for Portal Server

Table 25 Connection Pool Properties for jdbc/XMLDocRepositoryDBName jdbc/XMLDocRepositoryDB





Minimum Size 1

Initial Size 1


Idle Time out 300




Table 26 Connection Pool Properties for jdbc/jmsdbName jdbc/jmsdb





Minimum Size 1

Initial Size 1


Idle Time out 300





jdbc/XMLDocRepositoryDB for Portal Server

jdbc/SBMCommonDB for Portal Server

Table 27 Connection Pool Properties for jdbc/XMLDocRepositoryDBName jdbc/XMLDocRepositoryDB





Minimum Size 1

Initial Size 1


Idle Time out 300




Table 28 Connection Pool Properties for jdbc/SBMCommonDBName jdbc/SBMCommonDB





Minimum Size 1

Initial Size 1


Idle Time out 300





jdbc/SBMPortalsDB for Portal Server

Table 29 Connection Pool Properties for jdbc/SBMPortalsDBName jdbc/SBMPortalsDB





Minimum Size 1

Initial Size 1


Idle Time out 300





78

Appendix C

Improving BPM Portal Performance

The following sections provide procedures to improve performance of BPM Portal on Pramati application server.

Pramati To improve the performance of BPM Portal on a Pramati application server, perform the following procedures.

Note: For information on tuning a cluster of Pramati application servers to improve performance, see the Clustering Guide.

In the out-of-the-box installation, there are two copies of web-config.xml; namely, web-config.xml.dev and web-config.xml.prod under ITPC_HOME\pramati\server\nodes\portalServer\config. The web-config.xml.prod file is tuned for a production environment with the update-check-interval-seconds value set to -1. This disables the check the server performs for changes in JSP files. Rename this file to web-config.xml and restart the server.

Note: Once the update-check-interval-seconds value is set to -1, the Portal server will no longer compile JSPs. If you want to deploy new JSPs or need the server to recompile modified JSPs, the update-check-interval-seconds value should be a positive value.

Glossary

This is a listing of common ITPC terminology. For a full version of terms used in IT Process Centre (ITPC) documentation, refer to the Terminology Guide in the ITPC_HOME\docs folder.

A | B | C | D | E | G | H | I | K | M | P | R | S | T | U | W

ACL ManagerIn EMC BusinessManager (EBM), Access Control List Manager provides a finer, more precise control over user access rights for resources and actions.

Activity WorkstepIn ITPC, the basic unit of work; must be performed by one or more human performers (valid individual user, multiple users or user group).

AdapterA Java class that integrates remote, third party classes and actions with ITPC. An adapter can automate certain functions and tasks performed by a remote server or other external systems.

AdministrationA module in BPM Portal enabling the administrator to perform such tasks as installing/uninstalling applications, modifying configuration parameters controlling ITPC operations, and manage ITPCITPC users, groups and access control.The Administration module is visible only to ITPC users who have permissions to access it.

ApplicationIn ITPC, an application is an installed, executable business process that automates a business flow.

A Go to Top

79

Balanced ScorecardA management application in the Management module that measures performance by analyzing how an organization’s business activities help it achieve its strategic goals. The Balanced Scorecard provides an analysis from a range of perspectives.

BAMBusiness Activity Management combines Business Process Management with strategic and analytical information on specific business performance indicators, providing real-time status information and identifying critical events to assist senior management in making informed business decisions.

BizLogicAn ITPC component that provides a flexible, lightweight, scalable workflow process engine for intranets, extranets, and the Internet.

BizPulsean ITPC component that provides an open event-driven rule engine to formulate and enforce policies in business applications.

BizSolo an ITPC component that enables users to develop customizable, sophisticated presentation flows for business processes, install them as Web applications, and execute them on their Web browsers.

BizStoreAn open repository of rich e-business information collected from different ITPC modules.

BPELBPEL (Business Process Execution Language) for Web services is an XML-based language designed to enable task-sharing for a distributed computing or grid computing environment - including across multiple organizations - using a combination of Web services.

BPMNBPMN (Business Process Modelling Notation) provides businesses with the capability of defining and understanding their internal and external business procedures through a Business Process Diagram giving organizations the ability to communicate these procedures in a standard manner.

BPM Portalan ITPC component that offers users, managers, administrators and developers a unified, customizable portal for single sign-on access to all ITPC functionalities to which they are granted permission.

BPM Studioan ITPC component that is an Integrated Development Environment for ITPC and enables ITPC users to develop and deploy an ITPC application without leaving the development environment.

Business Calendaran ITPC feature that accurately calculates the Due Date of tasks, and provides support for multiple business calendars across different time zones.

B Go to Top

Glossary 80 Glossary

Business FlowThe logical sequence of process activities, related to one another by a triggering activity, to achieve an outcome. It represents a business process that begins with a commitment and ends with the termination of that commitment. In ITPC, business flow includes workflow (the flow of all human-performed activities), integration flow (the flow of activities performed by systems) and presentation flow (from a user’s viewpoint, the flow of data from one Web page to the next).

Business LogicThe control flow and information flow among worksteps that define a business process.

Business ObjectA representation of an activity in the business domain, including its name, definition, attributes, behavior, relationships and constraints.

Business ProcessA process involving multiple worksteps in the form of operations, interactions and notifications performed by a user, group of users, an external adapter, or a script. Examples of internal business processes are purchasing, expense reporting, help desk, and time card. External processes may include order processing, sales, and customer service.

Business Process ManagementThe concept of guiding work activities through a multi-step business process in order to improve performance and reduce costs within and across functional business units.

Business RuleA combination of elements, including validation edits, logon verifications, database lookups, policies and transformations, that represent an enterprise’s way of doing business.

ClusterIn ITPC, an integrated set of multiple, electronically connected but physically separated servers. This loosely coupled group of nodes collaborate to provide shared access to the services that each node hosts. To other systems, the cluster appears as a single system.

Control FlowThe sequences of worksteps and workstep conditions, as defined in a process template in BPM Studio or Process Modeler.

Dashboardan ITPC feature that provides a graphic overview of the status of several business processes on a single Web page, enabling users to monitor the progress of each process. Users can view business processes across all applications or for a selected application.

DataslotA data placeholder that persists through the entire process and defines the information flow of the business process. Dataslots are associated with processes, where they can add information into (Input type) or out of (Output type) worksteps, and appear as editable or read-only fields on a user’s interface.

Expression Editoran ITPC tool that enables users to define complex conditional expressions within a Decision workstep to support their business requirements.

C Go to Top

D Go to Top

E Go to Top


GroupIn ITPC, an entity that has as members valid users or other groups who perform related work and have authorized access to specific components.

Heatmapan ITPC feature that provides a convenient, graphical tool for managers to visually locate the bottlenecks in the process execution. It helps managers to get an overview of the status of the currently active instances, identify suspended instances, and analyze the history of the completed instances.

HomeA module in BPM Portal through which users interact with ITPC. Using the Home module, users complete entries to various tasks and applications, update profile, set preferences, and link to the support infrastructure required to achieve these tasks. The Home module is the primary interface for ITPC application users.

Infopad In ITPC, a data structure used to capture business metrics, typically displayed as a table with one or two dimensions.

InstanceAn individual object within a specific class. In ITPC, a self-contained unit that is created each time you use a process template to run an ITPC application.

ITPC ApplicationAn application is an implementation of a business process. It can contain one or more process templates, performers, adapters, customized forms or rules. An application can be deployed, installed and run on BizLogic servers. In ITPC, an application is an installed, executable business process that automates a workflow.

ITPC Web Servicesan ITPC component that allows ITPC application developers to; a) publish their applications as Web Services, and b) find and convert other available Web Services on the Internet into ITPC applications.

KPIKey Performance Indicator, used in the Balanced Scorecard system, that provides the data translating enterprise goals into a set of measurable objectives.

Management A module in BPM Portal enabling the managers to query, report, and control processes and resources for users of ITPC. The Management module is visible only to ITPC users who have permissions to access it.

Managed Adapter In ITPC, a Managed Adapter is an implementation of an adapter interface that facilitates data exchange between ITPC processes and external applications.

Migration

G Go to Top

H Go to Top

I Go to Top

K Go to Top

M Go to Top


The process of moving from the use of one operating environment to another operating environment that is typically seen as improvement. Migration can involve moving to new hardware, new software, or both. It may involve a new application, another type of database, or a redesigned network. Migration is also used to refer simply to the process of moving data from one storage device to another. ITPC supports data migration as well as application migration.

PAMProcess Asset Management recognizes that a company’s processes are a unique asset and provides a structure that organizes, stores, and secures process data, enabling users to retrieve information on any of the company’s processes.

PerformerAn entity that executes a workstep. Depending on the workstep type, the performer can be a human user, a group of users, an adapter or other external performer, or a script.

Presentation FlowThe flow of information and user input from one interface to the next. Typically related to a single Activity workstep in the process and generated in a BizSolo environment.

Process EngineOrchestrates the execution of business processes and also coordinates conversations among process engines based on public processes, which forms the backbone of global business collaboration.

Process ModelerA stand-alone component that enables users to design templates for basic business processes and store or retrieve them from the EMC central process repository, and to design and run simulations of processes.

Process Refreshan ITPC feature for replacing the installed process without versioning, facilitating the running process instances to refresh and seamlessly adapt to the new workflow.

Process RepositoryA central place (can contain several databases) in which a group of processes is stored and maintained in an organized way, and can be accessed to retrieve information.

Process TemplateIn ITPC, a model of business flow that includes worksteps, connectors and dataslots. After users deploy and install it as an application in the ITPC directory structure, they can use the application to create process instances.

RollbackIn ITPC, a feature that restarts the workflow from a workstep previously selected as the rollback point in the process, performed automatically in the event of a failure.

RoleThe actions and activities assigned to a valid ITPC user who is a member of a group. In ITPC, only members of a group can be assigned a role. A role indicates the relationships of the user in a group context.

Rule WizardAn interactive utility that enables ITPC users to quickly develop rules that can be applied to a business process.

Swim Lanes

P Go to Top

R Go to Top

S Go to Top


Used in workflow diagrams to organize complex processes across functional boundaries. For example, seen as horizontal lines on a process map, swim lanes can be used to place individual task steps into different categories that depend on task ownership.

TaskIn ITPC, a performer is assigned one or more workitems that the performer sees as tasks. There are two types of tasks: Assigned, which are assigned specifically to you; and Available, which are available to be performed by you or other members of your user group.

UserIn ITPC, a valid human performer with authorized access to specific modules.

WorkflowThe logical sequence of activities performed by human performers, typically in a BPM Studio or Process Modeler environment. Workflow includes the tasks, procedural steps, organizations or people involved, required input and output information, and tools needed for each activity in a business process.

T Go to Top

U Go to Top

W Go to Top


Index

AAccess Control List Management 42application servers

managing through appserver consoles 51ports 31selecting 31starting 46stopping 55supported by ITPC 16, 17

AppServer Console 51

BBizLogic E-Mail ID 33BPM Portal, logging in 50browsers, supported by ITPC 16

Ccleaning databases with setupSBM 42configurations

for a new database 57supported for ITPC 18

contents of Installation CD 15Conventions in ITPC documentation 8Customer support 8

Ddatabase

cleaning utility 42login information 38

preparing for MS SQL server 21preparing for Oracle 9i/10g 19selecting 36supported by ITPC 16tuning for Pramati 70URL default settings 26

Database Configuration Tool 57Configuring the New Database 58Reverting to the Old Database 62

Database usercreating in MS SQL 2000 22creating in Oracle 9i 19removing from Oracle 9i 20

destination location, selecting 28disk space required 16DISPLAY environment variable 47Domain name 30

EEJB servers

starting 46stopping 55

Email server information 33

FFAT partition 29

HHost name, for ITPC installation 30

Host Portal URL, selecting 32

Iimporting user information 44Incoming Mail, specifying server 34Install wizard 24Installation CD, contents 15installing

ITPC 27ITPC as Windows Service 47ITPC on a FAT partition 29MS SQL Server 2000 Driver for JDBC Service 22prerequisites for 24silent installation 45software requirements 17tasks before beginning 23troubleshooting 27

ITPCAppServer Console 51conventions in documentation 8documentation list 7installation 27starting modules 52supported platforms 16, 18uninstalling 66user types 6

ITPC serversstarting 46stopping 55

JJava Technology, supported 16JDBC driver requirements 17JDBCRealm utility 44

Llanguages, supported 25LDAP

realm 25server information 35

License Agreement 28

MMail server, specifying 33Management Console GUI 51memory required 16

MS SQL serverdatabase cleaning procedures 43preparing database for 21XA compliance 22

OOCI driver 17operating systems, supported 16Oracle 9i/10g database, preparing for 19

Ppassword, default 50platforms, supported by ITPC 16, 18populateJDBCRealm utility 44port numbers

default 26selecting 31

Portal serversstarting 46stopping 55

Pramati application serverinstalling ITPC as Windows Service with 47tuning database parameters 70

prerequisites, for ITPC installation 25Product Support Team 8protocols, supported 26

RRemove Existing Files dialog 68

SServer Management Console 51setupBizLogic utility 43setupSBM utility 42Silent Installation 45software prerequisites 24software requirements 17starting

all servers in ITPC 46EJB server 46ITPC modules 52ITPC servers 46Portal server 46

stoppingall servers in ITPC 55

Installation Guide 86 Index

EJB servers 55ITPC servers 55Portal servers 55

system information prerequisites 25system requirements for installation 16

Ttesting

BizLogic mail server 54ITPC installations 53

troubleshooting in Windows 69tuning database parameters

Pramati 70

Uuninstalling

additional steps for 68ITPC 66

UNIXstarting servers in 47supported configurations 18

user managementprerequisites 25selecting 34supported by ITPC 16

user name, default 50User types 14utilities

populateJDBCRealm 44setupBizLogic 43setupSBM 42

WWeb server port number 26Windows

prerequisites for ITPC installation 25starting servers in 46supported configurations 18troubleshooting 69

Windows Service, installing ITPC as 47

XXA compliance

for MS SQL Server 22X-Windows server 47

Installation Guide 87 Index

Download - EMC IT Process Centre Installation Guide · BPM Studio This is the primary application development tool for ITPC, which provides an Eclipse-based integrated development environment

Top Related