Ult Studio Config 71

Ultimus®

Profit from the ProcessTM

Ultimus BPM Configuration Help

Version 7.1

Table of Contents

Table of Contents....................................................................................................................2 Ultimus BPM Studio Configuration Manual ..........................................................................3

Copyright Information ........................................................................................................3 Rules and Guidelines ..........................................................................................................5 Configuring Ultimus BPM Studio Server...........................................................................6 The Main Interface..............................................................................................................7 Configuring Repositories ....................................................................................................8 Configuring Ultimus BPM Servers...................................................................................11 Configuring Access Rights ...............................................................................................13 Viewing Ultimus BPM Studio User Activity ...................................................................17

Ultimus BPM Configuration Help Page 3 of 18

Ultimus BPM Studio Configuration Manual

Version 7.1

BPM Studio is designed on a 3-tier architecture, which consists of the following components:

• The BPM Studio client resides on every designer’s computer. This module serves as the primary interface that developers will use for designing and modeling processes.

• The Ultimus BPM Studio Server is a component that controls access to process repositories. Designers who are working collaboratively on process maps in the BPM Studio client will each have a connection to the particular Ultimus BPM Studio Server that manages access for those repositories. All processes managed by BPM Studio servers are kept in a SQL Server or in an Oracle database.

The contents of this Help file describe how to configure the Ultimus BPM Studio Server for access by BPM Studio client users.

Copyright Information

No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose, without the express written consent of Ultimus, Inc. The software described in this manual is furnished under a license agreement or non-disclosure agreement and may be used or copied only in accordance with the terms of the agreement. The information contained in this manual is subject to change without notice and does not represent a commitment on the part of Ultimus, Inc. Copyright © 1999-2005 Ultimus, Inc. All rights reserved. Companies, names, and data used in examples herein are fictitious unless otherwise noted. Ultimus™, Adaptive Discovery™, Flobot™, FloPort™, FloStation™, Maplet™, U2Net™, and Unruly Event™ are trademarks of Ultimus, Inc. Windows, MS-DOS, Word, Excel, InfoPath and SQL Server are registered trademarks of Microsoft Corp. All other names may be trademarks of their respective owners and are used for reference only. All Ultimus specifications contained in documentation and literature are subject to change without notice.


Reader's responsibilities and expectations

After reading this online Help the reader should be able to know how to use the Ultimus BPM Studio Configuration module.

Ultimus expects the reader to:

• Be proficient with the operating system(s) on which Ultimus BPM Suite and its related components operate.

• Understand the hardware requirements to operate Ultimus BPM Suite and each component there of.

Conventions used in this online Help

The following conventions are used throughout this online Help:

Convention Description

bold Bold text denotes items that you must select or click on in an application, such as menu items, dialog box options, and dialog box output. Bold text is also used to designate labels within table columns.

italic Italic text denotes variables, emphasis, and document, chapter, and section titles. This also denotes text that is a place holder for a word or value that you must supply.

monospace

Text in this font denotes text or characters that you should input to an application, application output, sections of code, programming examples, and syntax examples. This is also used for the proper names of disk drives, paths, directories, device names, file names, file extensions, code excerpts, and URLs.

Underlined blue text

Underlined blue text represents a link to a different section in this document. Clicking the underlined blue text will display that topic.

<> Text within these brackets denotes text that is a placeholder for text or value(s) that the user must supply.

»

The » symbol leads you through nested Start menu items, application menu items, and dialog box options to a final action. For example, the sequence File»Page Setup»Printer... directs you to pull down the File menu, select the Page Setup item, then select Printer... from the dialog box.

This icon denotes a tip, which alerts you to advisory information.

This icon denotes a note, which alerts you to important information.

This icon denotes a caution, which advises you of precautions to take to avoid specific application errors, data loss, or system crash.


Rules and Guidelines

Below are the rules and guidelines for configuring BPM Studio servers:

• A single Ultimus BPM Studio Server is capable of housing multiple process repositories. As an example, the user could have separate process repositories for Human Resource, Finance and Sales departments.

• Each process repository is capable of housing multiple processes. Instructions on how to add processes to process repositories is described in the BPM Studio client Help.

• Ultimus BPM Studio Server leverages either a SQL Server or an Oracle database to store process definitions.

• Each process repository must point to a different physical database in SQL Server or Oracle. The same physical database and table definitions cannot be shared for multiple process repositories. As an example, if the user has two process repositories (one for Finance, the other for Sales), the user should set up two separate database definitions in SQL Server, and have two different System OLE DB database definitions each pointing to a database.

Note:

If the connection to Ultimus BPM Database is utilizing a SQL trusted connection, please refer to the Ultimus BPM Suite Configuration Guide for a detailed explanation of the necessary configurations to make.


Configuring Ultimus BPM Studio Server

The Ultimus BPM Studio Server is configured through a Microsoft MMC-based application that is installed on the same computer as the Ultimus BPM Studio server. To access this MMC application, choose Programs>>Ultimus BPM Suite 7.1>>Ultimus BPM Studio Configuration from the Windows Start Menu. This will launch the MMC application.


The Main Interface

The Ultimus BPM Studio configuration interface is shown below:

Following is a description of each node and its associated function:

• Repositories: This node allows the user to set up multiple process repositories for the particular Ultimus BPM Studio Server the user is configuring.

• Servers: Ultimus BPM Studio provides the ability to publish processes from the BPM Studio clients to Ultimus BPM Servers. This node allows the user to set up Ultimus BPM Server definitions that BPM Studio client users, with the appropriate security rights, will be permitted to publish to when building business processes.

• Access Rights: This node allows administrators to add users, and configure which process repositories they are able to access, and which Ultimus BPM Servers they are permitted to publish processes to.


Configuring Repositories

Ultimus BPM Studio Server maintains process repository definitions (and all associated process information) in a SQL Server or Oracle database. Thus, before users can access process repositories from the BPM Studio clients, Repository definitions need to be set up through the BPM Studio configuration application. To do so:

1. Right-click the Repository node, and select Add:

2. A dialog box appears where repository information is to be specified:

• Name: The logical name of the process repository


In the Database Settings enter the following information:

• Database Server Selection: Select either SQL Server radio button or Oracle radio button as required.

Note:While selecting the Oracle radio button, the client must have Oracle service configured on the system.

• Server Name: Enter the name of the database server in the Server Name field.

Notes:

• Server Name can be any of the following values: computer Name, IP address of the database computer or the local host values.

• In the case of Oracle database server, the Oracle Service name should be specified in the Service Name field.

• Catalog Name: Name of the database.

Note:In the case of Oracle database server, a catalog name is not required.


• User: Enter the name of the user for the database. • Password: Enter the password for the database

Note:

In the case of Oracle database server, in the User field, the schema name and in the Password field, the password for the schema should be entered.

3. Click OK.

Using this mechanism, multiple process repositories can be added for a BPM Studio server.

To edit an existing repository definition, simply right-click the repository and select Edit.

To delete a repository, simply select Delete from the menu.


Configuring Ultimus BPM Servers

In order to add Ultimus BPM Server definitions, right click on the Servers node, and select Add from the menu.

A dialog box appears where the user will be able to enter Ultimus BPM Server definitions:

These Ultimus BPM Server definitions will be used by BPM Studio client users when publishing processes. The user will need to ensure that the Ultimus BPM Servers are visible to the BPM Studio client computers, since publishing of processes occurs directly from the BPM Studio client computer to the BPM Studio servers. Since BPM Studio client supports publishing over DCOM or HTTP/HTTPS, the user will need to ensure the following:

• When DCOM is being used, enter the Windows Server Name of Ultimus BPM Server computer. This computer must be on the same domain as the BPM Studio client.

• When HTTP/HTTPS is being used, enter the fully qualified domain name or IP address of Ultimus BPM Server computer for example computer.yourdomain.com, or 127.0.0.1.


To delete an Ultimus BPM Server definition, right click the server and select Delete from the pop-up menu:


Configuring Access Rights

Access Rights allow the user to control which process repositories BPM Studio client users are able to access, and which Ultimus BPM Servers these users are permitted to publish to.

Before configuring specific Access Rights, the user will need to add users for the user's BPM Studio server. This is done by right-clicking the Access Rights node, and selecting New User:

This will open the User dialog box.

The user can add users through two mechanisms:

• Type the windows short name of the user and click OK. The short user name must be defined in the domain where the BPM Studio client is installed, since the client will use this short name for windows authentication when logging BPM Studio client users onto an Ultimus BPM Studio Server process repository.

• Click the … button and select the user from a list of Windows domain users.


Once the user has added all the user's users, the user can right-click the Repositories node below the user, and select which repositories they are allowed to access through BPM Studio client:

The Repositories dialog box appears:

Following the same mechanism, Ultimus BPM Servers can be added for the user allowing the user to publish from BPM Studio client. By right clicking the Servers node for the user, and selecting Ultimus BPM Server, Ultimus BPM Server definitions can be added:


Repository and Ultimus BPM Server definitions can then be deleted for a user simply by right clicking the definition, and selecting Delete:

Users can also be deleted by right-clicking the user definition and selecting Delete:


In the pop-up menu above, the user will notice there is also an Administrative Rights option in the pop-up menu. This is a very important property that can be assigned to individual users, and provides that user with the following capabilities:

• In BPM Studio client, the user will be able to define Security Rights for all other users with access to the particular process repository. These security rights can be applied to the process or object level and include the ability to Edit, Lock, Delete and Publish processes and objects.

• The user will also be able to perform Check-In, Check-Out, Lock, Delete and Publish functions on behalf of any other user. This is useful in the case where a user checks an object out, goes on vacation, and forgets to check the process back in. The Administrative User can then check the object in on his behalf.

At least one user in a process repository should be assigned this privilege. However due to the powerful nature of this control, it is recommended that only selected individuals be privy to this privilege.


Viewing Ultimus BPM Studio User Activity

Each Ultimus BPM Studio Server supports a concurrent user-licensing model in terms of controlling how many users are permitted to log on to Ultimus BPM Studio Server simultaneously. Concurrent users are those who are logged on to Ultimus BPM Studio client and are accessing Ultimus BPM Studio Server. When the users close their Ultimus BPM Studio client, they are logged off and no longer considered as concurrent users.

The Ultimus BPM Studio Server allows administrators to view which users are logged onto that server. This can be done by right clicking on the Ultimus BPM Studio node, and selecting Properties:

The administrator is then presented with a window where they can view the users that are currently logged onto the Ultimus BPM Studio Server, and the maximum number of allowed concurrent users:


Note:To terminate a user's session right click on a user and select Disconnect.

Documents

Ult Studio Config 71