Oracle BPASuite Installation Guide

Oracle BPA Suite 11g

Oracle BPA Suite Installation and Administration Guide

May 2009

Copyright © 2008, 2009 Oracle and/or IDS Scheer AG. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Portions of this software copyright © 2009, IDS Scheer AG.


I

Contents

1 Manual conventions..............................................................................................1

2 Installation..........................................................................................................2 2.1 Installation options .....................................................................................3 2.2 Client installation - Windows operating system................................................5 2.3 Client install and uninstall - Linux operating system.........................................7 2.4 Oracle Business Process Repository installations (Windows operating system) .....8

2.4.1 Default (recommended for up to 50 users) ...............................................12 2.4.1.1 Initial installation ........................................................................12 2.4.1.2 Subsequent installation ................................................................14 2.4.1.3 Update installation.......................................................................15

2.4.2 User-defined (advanced installation)........................................................17 2.4.2.1 Oracle Business Process Repository................................................18 2.4.2.2 Oracle BPA Suite Site Administrator ...............................................20 2.4.2.3 Oracle Business Process Repository Site Manager.............................21

2.4.2.3.1 Step-by-step instructions - Use existing Oracle database (prepared for Oracle BPA Suite) ................................................21

2.4.2.3.2 Step-by-step - Configure and connect existing Oracle database instance ................................................................................23

2.4.2.3.3 Step-by-step - Create new Oracle database instance....................25 2.4.2.3.4 Step-by-step - Microsoft SQL Server ..........................................27 2.4.2.3.5 Step-by-step - IBM DB2...........................................................28

2.4.2.4 Oracle BPA Suite Web Client Components .......................................30 2.5 Oracle Business Process Repository installations (Unix operating system) .........34

2.5.1 Oracle Business Process Repository .........................................................37 2.5.2 Oracle Business Process Repository Site Manager ......................................38 2.5.3 Oracle Business Process Repository and Oracle Business Process

Repository Site Manager ........................................................................39 2.5.4 Oracle BPA Suite Web Client Components.................................................41 2.5.5 Uninstall ..............................................................................................43

2.6 Oracle Business Process Publisher Server installations....................................44 2.6.1 Apache Tomcat Web Application Server under Windows..............................44

2.6.1.1 Step-by-step instructions (standard database) ................................45 2.6.1.2 Step-by-step instructions (Oracle database)....................................47 2.6.1.3 Step-by-step instructions (existing Oracle database)_tomcat .............51 2.6.1.4 Step-by-step instructions (new Oracle database)_tomcat ..................56 2.6.1.5 Step-by-step instructions (MS SQL Server 2005 database) ................61

2.6.2 Apache Tomcat Web Application Server under Solaris/Linux........................66 2.6.2.1 Step-by-step instructions (Oracle database)....................................69 2.6.2.2 Step-by-step instructions (MS SQL Server 2005 database) ................72

2.6.3 IBM WebSphere Application Server (WAS 6.1.0.15) under Windows .............74 2.6.3.1 Step-by-step instructions (Oracle database)....................................75 2.6.3.2 Step-by-step instructions (MS SQL Server 2005 database) ................97

2.6.4 IBM WebSphere Application Server (WAS 6.1.0.15) under RHELx64 ........... 121 2.6.4.1 Step-by-step instructions (Oracle database).................................. 122 2.6.4.2 Step-by-step instructions (MS SQL Server 2005 database) .............. 143 2.6.4.3 Deployment of a new WAR file .................................................... 166


II

2.6.5 Oracle WebLogic Server, version 11g under Windows............................... 170 2.6.5.1 Step-by-step instructions (Oracle database)_WebLogic11g.............. 171 2.6.5.2 Step-by-step instructions (MS SQL Server 2005

database)_WebLogic.................................................................. 183 2.6.6 Oracle Business Process Publisher Report Server installations.................... 194

2.6.6.1 Apache Tomcat Web Application Server under Windows .................. 195 2.6.6.1.1 Step-by-step instructions (standard database) .......................... 195 2.6.6.1.2 Step-by-step instructions (Oracle database configured)_tomcat... 197 2.6.6.1.3 Step-by-step instructions (existing Oracle database)_tomcat....... 201 2.6.6.1.4 Step-by-step instructions (new Oracle database)_tomcat............ 206 2.6.6.1.5 Step-by-step instructions (MS SQL Server 2005 database).......... 211

2.7 Acrobat Reader ...................................................................................... 214 2.8 Java Runtime Environment....................................................................... 215 2.9 System add-ons ..................................................................................... 216

2.9.1 Oracle BPA Suite Process Generator....................................................... 216 2.10 Additional installation information and principles ......................................... 217

2.10.1 Oracle BPA Suite - System architecture ................................................ 217 2.10.2 Oracle Business Process Architect installations....................................... 217 2.10.3 Oracle Business Process Repository - Exit a service ................................ 217 2.10.4 Automatic backup ............................................................................. 218 2.10.5 Particular issues - Oracle BPA Suite client and Oracle Business Process

Repository on the same computer ...................................................... 219 2.10.5.1 Installation............................................................................... 219 2.10.5.2 Uninstall .................................................................................. 220

3 Administration ................................................................................................. 221 3.1 Database management systems................................................................ 221

3.1.1 Oracle Business Process Repository ....................................................... 221 3.1.1.1 Oracle database management system for Oracle Business Process

Repository................................................................................ 221 3.1.1.1.1 Set up the database .............................................................. 221

3.1.1.1.1.1 Install Oracle BPA Suite database objects.......................... 222 3.1.1.1.1.2 Use SQL*Plus scripts...................................................... 222

3.1.1.1.1.2.1 Available SQL*Plus scripts....................................... 223 3.1.1.1.1.2.2 Run batch files install.bat/install.sh .......................... 224

3.1.1.1.1.3 Configure the installation scripts ...................................... 224 3.1.1.1.1.3.1 Connection data..................................................... 224 3.1.1.1.1.3.2 Change tablespace names....................................... 224 3.1.1.1.1.3.3 Change the password for Oracle user ARIS71............. 225 3.1.1.1.1.3.4 Change the password for Oracle user arisadm71 ........ 226 3.1.1.1.1.3.5 Change user names................................................ 226

3.1.1.1.2 Configure Oracle Business Process Repository URL..................... 226 3.1.1.2 MS SQL database management system for Oracle Business Process

Repository................................................................................ 227 3.1.1.2.1 Required programs, drivers, and scripts ................................... 227 3.1.1.2.2 Notes on installing SQL Server ................................................ 228 3.1.1.2.3 Set up the database .............................................................. 228

3.1.1.2.3.1 Configure the installation scripts ...................................... 229


III

3.1.1.2.3.1.1 Change the name of the database ............................ 229 3.1.1.2.3.1.2 Change the password for the login user ARIS71 ......... 229 3.1.1.2.3.1.3 Change the user name ARIS71 ................................ 230

3.1.1.2.3.2 Configure Oracle Business Process Repository URL ............. 231 3.1.1.3 IBM DB2 database management system for Oracle Business

Process Repository .................................................................... 231 3.1.2 Oracle Business Process Publisher Server ............................................... 233

3.1.2.1 Manage a system with an MS SQL database .................................. 234 3.1.2.1.1 Sample script create_db.sql.................................................... 237

3.1.2.2 Manage a system with an Oracle database .................................... 239 3.2 Oracle Business Process Repository ........................................................... 242

3.2.1 Oracle Business Process Repository - Operating system and database system platforms ................................................................................ 246

3.2.2 Recommended user-related server dimensioning ..................................... 248 3.2.3 Protocols used.................................................................................... 249

3.2.3.1 Oracle BPA Suite on the Internet/SSL........................................... 249 3.2.3.2 Oracle BPA Suite on the intranet/VPN........................................... 249

3.2.4 Configure Oracle Business Process Repository ......................................... 249 3.2.4.1 Log logins ................................................................................ 251 3.2.4.2 Log messages........................................................................... 251 3.2.4.3 SSL encryption of data transmission via Secure Socket Layer .......... 251 3.2.4.4 Update SSL certificates .............................................................. 252 3.2.4.5 Configure Oracle Business Process Repository/Oracle Business

Process Repository Site Manager connection.................................. 253 3.2.4.6 Configure client/Oracle Business Process Repository connection ....... 254 3.2.4.7 Deactivate Report Server............................................................ 254 3.2.4.8 Deactivate simulation server ....................................................... 255 3.2.4.9 HTML Generator - Current database lists....................................... 255 3.2.4.10 Activate Oracle BPA Suite Notify Service ....................................... 256 3.2.4.11 Restrict number of index_backup files .......................................... 258 3.2.4.12 Provide additional memory ......................................................... 259 3.2.4.13 New database - Additional languages ........................................... 259

3.2.5 Oracle BPA Suite Converter .................................................................. 260 3.2.6 When are placed symbols displayed (server)? ......................................... 261 3.2.7 Add custom icons for macros ................................................................ 262 3.2.8 Server log directory ............................................................................ 262

3.3 Oracle BPA Suite agent............................................................................ 263 3.3.1 What are Oracle BPA Suite agents for?................................................... 263 3.3.2 What tasks does an Oracle BPA Suite agent handle? ................................ 263 3.3.3 How to exit Oracle BPA Suite agents...................................................... 263 3.3.4 Activate Oracle BPA Suite Notify Service ................................................ 264

3.4 Java clients (application) ......................................................................... 265 3.4.1 Oracle Business Process Simulator ........................................................ 269 3.4.2 Client log directory.............................................................................. 270

3.5 Oracle Business Process Publisher ............................................................. 271 3.5.1 Oracle Business Process Publisher Server ............................................... 273

3.5.1.1 Approved platforms, servers, applications, and databases ............... 275 3.5.2 Context path ...................................................................................... 279 3.5.3 Modify configuration files ..................................................................... 279


IV

3.5.3.1 Show all groups in the Explorer tree (Publisher Server)................... 279 3.5.3.2 Change the DAO of an Oracle database (Tomcat)........................... 280 3.5.3.3 E-mail settings.......................................................................... 281 3.5.3.4 Free port to Web server ............................................................. 281 3.5.3.5 Change IP address .................................................................... 282 3.5.3.6 LDAP user management ............................................................. 282 3.5.3.7 Use Microsoft SQL database........................................................ 283 3.5.3.8 Encrypt LDAP password.............................................................. 286 3.5.3.9 Configure navigation carousel ..................................................... 286 3.5.3.10 Display news ............................................................................ 287 3.5.3.11 Configure OIS user management (Oracle Business Process

Publisher Server) ...................................................................... 288 3.5.3.12 Use an Oracle database (Tomcat) ................................................ 288 3.5.3.13 Oracle restart ........................................................................... 291

3.5.4 Manage reports .................................................................................. 292 3.6 Java clients (browser mode)..................................................................... 293

3.6.1 Set up Java clients for browser use........................................................ 295 3.6.1.1 Installed files of Oracle BPA Suite ................................................ 295 3.6.1.2 Language update and character sets ............................................ 298 3.6.1.3 Execution as application or applet................................................ 298 3.6.1.4 Provide additional memory ......................................................... 299 3.6.1.5 Installation by software distribution ............................................. 299

3.6.1.5.1 Possible settings for user.cfg .................................................. 300 3.6.1.5.2 Preconfigured user.cfg ........................................................... 300 3.6.1.5.3 Configure user.cfg................................................................. 300

3.6.2 Start a second Java-based product in the browser ................................... 300 3.6.3 Automatically update installed Web clients.............................................. 301

3.6.3.1 Preparations for the automatic update.......................................... 301 3.6.3.2 Set up web clients for automatic update ....................................... 301

3.7 Central user login using LDAP................................................................... 302 3.7.1 Configure LDAP server operation........................................................... 303 3.7.2 Set Oracle Business Process Repository for LDAP server operation with

SSL .............................................................................................. 304 3.8 Data backup .......................................................................................... 305

3.8.1 Transfer data from earlier Oracle BPA Suite versions................................ 307 3.8.1.1 Configuration............................................................................ 309

3.8.1.1.1 Transfer item groups of the configuration ................................. 309 3.8.1.1.2 Transfer exported filters, font formats, languages, and

templates ............................................................................ 310 3.8.1.2 Transfer custom or modified scripts of previous Oracle BPA Suite

versions................................................................................... 310 3.8.2 Back up users and configuration ........................................................... 311 3.8.3 Automatic backup of current configuration files ....................................... 312 3.8.4 Save method changes ......................................................................... 312

3.9 Data management with Oracle BPA Suite Admintool .................................... 312 3.9.1 Start Oracle BPA Suite Admintool .......................................................... 313 3.9.2 Oracle BPA Suite Admintool commands .................................................. 313


V

3.9.2.1 Backup .................................................................................... 316 3.9.2.1.1 Example .............................................................................. 317 3.9.2.1.2 Data backup using a batch program (batch file) ........................ 318

3.9.2.2 Backupasn ............................................................................... 318 3.9.2.3 Backupconfig ............................................................................ 319 3.9.2.4 Configadminpassword ................................................................ 320 3.9.2.5 Copy ....................................................................................... 320 3.9.2.6 Createdb.................................................................................. 321 3.9.2.7 Dbmspassword ......................................................................... 321 3.9.2.8 Download................................................................................. 321 3.9.2.9 Delete ..................................................................................... 322 3.9.2.10 Exit ......................................................................................... 322 3.9.2.11 Help ........................................................................................ 322 3.9.2.12 Interactive ............................................................................... 323 3.9.2.13 Kill .......................................................................................... 323 3.9.2.14 List ......................................................................................... 324 3.9.2.15 Maintain................................................................................... 324 3.9.2.16 Monitor .................................................................................... 324 3.9.2.17 Password ................................................................................. 325 3.9.2.18 Rename ................................................................................... 325 3.9.2.19 Reorg ...................................................................................... 325 3.9.2.20 Restore.................................................................................... 326 3.9.2.21 Restoreversioned ...................................................................... 327 3.9.2.22 Restoreasn ............................................................................... 327 3.9.2.23 Restoreconfig............................................................................ 328 3.9.2.24 Server ..................................................................................... 328 3.9.2.25 Sessions .................................................................................. 329 3.9.2.26 Siteadminpassword ................................................................... 330 3.9.2.27 Statistic ................................................................................... 330 3.9.2.28 Status ..................................................................................... 331 3.9.2.29 Version .................................................................................... 331

3.10 Evaluation (scripting) .............................................................................. 331 3.10.1 Optimize memory requirements .......................................................... 332 3.10.2 Report formats and report files............................................................ 333 3.10.3 Windows API functions....................................................................... 334 3.10.4 Dialog variables ................................................................................ 335 3.10.5 Nested dialogs .................................................................................. 335 3.10.6 Icons for placed attributes .................................................................. 336 3.10.7 Add custom icons for macros .............................................................. 336

3.11 Known restrictions .................................................................................. 337 3.11.1 When do links work?.......................................................................... 339 3.11.2 Calendar .......................................................................................... 342

3.12 Glossary................................................................................................ 342 3.13 Appendix ............................................................................................... 346

3.13.1 System language and locale IDs.......................................................... 346 3.13.2 Port numbers.................................................................................... 350


1

1 Manual conventions

This chapter describes the manual conventions.

Note

This manual describes the settings and features as they were at the time

of print. Since manual and software are subject to different production

cycles, the description of settings and features may differ from actual

settings and features. Information about discrepancies is provided in the

Readme file that accompanies the product. Please read this file and take

the information into account when installing, setting up, and using the

product.

When you combine various technologies, please observe the

manufacturers' instructions, particularly announcements concerning

releases on their Internet pages. We cannot guarantee proper

functioning of supported third-party systems. Always follow the

instructions provided in the installation manuals of the relevant

manufacturer, or contact Oracle Corporation support.

In the Installation and Administration Guide, the following notational and

formatting conventions are used for menu items, file names, etc.

Notation/Formatting Example

Menu items, shortcut keys, dialog boxes, file

names, keyboard entries, etc. are written in

bold.

Click on OK.

Enter the path in the

sample.txt file.

Sequences of menus and menu items are

separated by forward slashes.

Click on Help/Help

topics.

User-defined entries are highlighted in bold

and enclosed in angle brackets.

Enter the path

<directory>\server.


2

2 Installation

This chapter describes the requirements for individual installations. Each

installation is explained step-by-step. It is assumed that you perform the

installations for the first time using the OracleBPA.exe startup file.

You can also start individual installation programs via the corresponding

Setup.exe.

If system files are changed during installation, you are prompted to

reboot your computer after installation.

Please refer to the chapter Administration (Page 221) to obtain

information on additional settings required for using Oracle BPA Suite

products.

If you re-run an installation for installed programs, the following options

are provided:

Modify Program

Use this option to add more components and/or languages.

Repair program

This option repeats an installation with the current settings. This is

useful if a program file was deleted by accident, for example. Any

subsequently installed hotfixes will be deleted!

Remove

This option uninstalls the component for which the installation

program was launched.

Note

When you perform an update, add a language (Modify Program

option), or repeat an installation (Repair Program option), the system

checks if a CFG file was changed manually. If so, a backup copy of that

file is generated before the new CFG file is installed. For example, if you

have modified the arisclient.cfg file manually, it is backed up (Page

218) in the <Oracle BPA Suite installation

directory>\javaclient\backup\config directory. The settings from

the previous installation are retained, for example the installation path,

the program group, and the languages you installed.

If you run an update installation for Oracle Business Process Repository,

all configuration changes are applied.


3

Warning

Please only use the file userServerSettings.cfg to change the

configuration. This ensures that your changes are preserved in future

update installations. The other Oracle Business Process Repository

configuration files are overwritten for each installation.

2.1 Installation options

If you insert an Oracle BPA Suite installation media in your drive, the

start page opens automatically. If it is not displayed automatically, click

on the name of your drive in Windows Explorer and run the program

OracleBPA.exe.

Important documents are automatically created in English (always,

except in an exclusively German installation) when you install Oracle

BPA Suite products. You can access these documents via

Start/Programs/Oracle BPA Suite/Documents.


4

Installation media

Installation program

Content/Components installed

Install Oracle

BPA Suite

Install products of the Oracle BPA Suite.

Additional

installations

Provides access to the server installation

programs and to the installation of JRE and

Adobe Acrobat Reader.

Installation and

Administration

Guide

Opens the Installation and Administration

Guide in PDF format. This requires Adobe

Acrobat Reader.

Quick Start Guide Opens the Quick Start Guide.

Delta paper Opens the description of differences between

earlier Oracle BPA Suite versions and the

current Oracle BPA Suite version.

Oracle BPA Suite

news

Opens the Oracle BPA Suite news page on the

IDS Scheer home page in your Web browser.

IDS Scheer

Academy

Opens the IDS Scheer Academy catalog with

the latest information on training, workshops,

and consulting services.

Additional installations

Installation program

Content/Components installed

Install Oracle

Business Process

Repository

Install Oracle Business Process Repository.

Install Oracle

Business Process

Publisher Server

Install Oracle Business Process Publisher

Server.

Adobe Acrobat

Reader

Install the viewer for displaying PDF

documents, such as the Oracle BPA Suite

Methods Manual.

Java Runtime

Environment

(JRE)

To use Java-based Oracle BPA Suite products

and start them via a Web browser, install SUN

Java Runtime Environment (JRE) if you have

not yet done so.


5

2.2 Client installation - Windows operating system

This chapter describes the installation of Oracle BPA Suite clients on

Windows operating systems.

Important documents are automatically created in English (always,

except in an exclusively German installation) when you install Oracle

BPA Suite products. You can access these documents via

Start/Programs/Oracle BPA Suite/Documents. If additional

languages are installed, the documents and help files of those languages

(Windows operating system) are automatically installed.

The installation Oracle BPA Suite WITH LOCAL STANDARD

DATABASE SYSTEM also installs the standard database system. This

allows you to create databases on your computer and work with them

without other users being able to access them. You can also connect to

an Oracle Business Process Repository to create databases there and

work with them.

The installation Oracle BPA Suite WITHOUT LOCAL STANDARD

DATABASE SYSTEM does not provide the standard database system.

This means that you can only create databases and work with them if

you connect to Oracle Business Process Repository. To be able to work

locally, select Oracle BPA Suite WITH LOCAL STANDARD

DATABASE SYSTEM.

Procedure

1. Ensure that the system requirements for all products and

functionalities are met.

2. Insert the Oracle BPA Suite installation media into your drive. If the

start page is not displayed automatically, click on the name of your

drive in Windows Explorer and run the OracleBPA.exe program.

3. Click on Install Oracle BPA Suite. The installation program's

Welcome page opens.

4. Click on Next.

5. Once you have read the license agreements and accept them, click

on Yes. The Select target path page opens.

If other Oracle BPA Suite products are already installed on the

computer, this step is skipped and the directory in which the other

products are installed is used. The Select program folder page

opens.


6

6. Select the installation directory. To use the installation directory

suggested in the Target folder box, click on Next. To install the

products in a directory different from the one suggested, click on

Change. Enter the relevant path in the Path box or navigate to the

relevant directory in the Directories box, and then click on OK. Click

on Next.

7. Select the program directory in which to place the program shortcut.



products are installed is used. The program directory for Oracle BPA

Suite is created.

To use a different name, enter a name in the Program folder box or

select the program folder in the Existing folders box, and then click

on Next.

8. Click on Next. The Local Standard Database System dialog box

opens.

9. You have the following options:

If you want to use Oracle BPA Suite with a local standard database

system on your computer, click on Next. The corresponding option

button Oracle BPA Suite WITH LOCAL STANDARD DATABASE

SYSTEM is already enabled by default.

If you have previously selected Oracle BPA Suite products that

cannot access local databases, the system notifies you accordingly.

Click on OK and select Next. Continue with the following step.

If you use the Oracle BPA Suite products exclusively in a server/client

environment and do not require a separate database system on your

computer:

Activate the option field Oracle BPA Suite WITHOUT LOCAL

STANDARD DATABASE SYSTEM, and click on Next.

The Select language dialog box opens.

10. Enable the check boxes for the desired interface and method

languages. Click on Next. The Start Copy Operation page opens.

11. Check the settings in the Start Copy Operation dialog box. If these

are correct, click on Next. The products will now be installed. The

system notifies you when the installation is complete.

12. If you do not want to create a desktop shortcut to launch Oracle BPA

Suite products, disable the Create Desktop Shortcut check box.

Click on Finish.

13. The installation is complete, and the installation program closes.


7

Tip

You can use Oracle BPA Suite Converter to transfer databases that were

created with previous Oracle BPA Suite versions (for further information,

please refer to the chapter entitled Transfer data from earlier

versions of Oracle BPA Suite in the Administration Guide).

A subsequent installation or update installation is similar to the server

installation.

To install an additional language later, you must run setup again.

2.3 Client install and uninstall - Linux operating system

This chapter describes the installation of Oracle Business Process

Architect on a Linux operating system.

Procedure



2. Copy the file install_bpa11gR1.xxxxxx.sh to the directory in which

you would like to install an Oracle BPA Suite product.

3. When you are in the directory to which you copied the file, enter

./install_bpa11gR1.xxxxxx.sh to install an Oracle BPA Suite

product.

You can start the install_bpa11gR1.xxxxxx.sh file from any

directory of your choice. To do so, you need to enter the full path in

front of the file name.

Configuration is performed automatically with the installation.

You can reconfigure the software at any time after installation with

the configure.sh script in the directory

JavaClient.xxxxxx/setup/. The software is ready to run

immediately. Use the appropriate Launcher.exe file in the directory

JavaClient.xxxxxx/ to start an Oracle BPA Suite product.

The path of the Java Runtime Environment is stored in the YYYMMDD-

HHMMDD.data.conf file in the directory

./JavaClient.xxxxxx/setup/backup.


8

Uninstall

To uninstall a client, you first have to exit the application and then

delete the installation folder.

Procedure

1. Close the application.

2. Delete the folder <installation directory>/JavaClientxxxxxx:

rm –r <installation directory>/JavaClient.xxxxxx

2.4 Oracle Business Process Repository installations (Windows operating system)

This chapter describes installations related to Oracle Business Process

Repository that can be performed under a Windows operating system.

All Oracle BPA Suite clients use Oracle Business Process Repository to

access the database server and thus work with a common data basis.

To ensure optimum load distribution and better protection against

failure, more than one Oracle Business Process Repository can be used.

The default server includes:

Oracle Business Process Repository

Oracle Business Process Repository Site Manager

Oracle BPA Suite Converter

This section describes processor, memory, system configuration, and

software requirements of the various server and client computers for

Oracle BPA Suite. For simultaneous use of other applications, a faster

processor, additional memory, or system extension may be required.

Depending on the application scenario (e.g. Merge or Simulation), large

databases can involve extended runtimes. Use of report, backup and

restore functions may require more RAM. On the other hand, if more

RAM is available than listed below, runtime behavior might improve.

In some cases, minimum and recommended system requirements are

specified. The minimum system requirements must be met in order for

the Oracle BPA Suite products to work properly. Meeting the

recommended system requirements will assure good performance even

with large data volumes. In general, it is advisable to use up-to-date

hardware taking into account the number of users who will be accessing

the same Oracle Business Process Repository.


9

Note







product.

Oracle Business Process Repository saves configuration data at the

operating system level. We strongly recommend protection at the

operating system level to minimize the risk of data misuse.

Hardware Recommended Minimum

Processor Intel Pentium IV 3.4 GHz Intel Pentium IV 2.4

GHz

RAM 64-bit system

2 GB RAM

32-bit system

1 GB RAM In 32-bit

systems, the maximum

size of a Virtual Machine

(VM) is 1 GB.

512 MB

The system requirements depend on the number of users (1 GB main

memory for 50 users) and use of certain features.

The RAM required for JavaScript reports varies greatly. If you want to

run report scripts that process large quantities of database items, we

recommend a 64-bit Windows installation or a Unix installation due to

the upper memory limit of 1.2 GB main memory for Oracle Business

Process Repository. Please also note the information on script

development (Page 331).

If you create a Publisher export and use links to large files (>15 MB),

you may need more memory for your Oracle Business Process

Repository. If the memory is insufficient, the export process is

canceled.


10

Software Details

Operating

systems

Depends on the database systems used.

Network High-speed network (>=100 Mbit) between database server and Oracle

Business Process Repository.

JRE Windows

If you have Oracle Business Process Repository installed and start Oracle

BPA Suite products as programs, an internal JRE version is automatically

used. You do not need to install JRE separately. If you have already installed

JRE, your installation is not used by Oracle BPA Suite.

Your JRE installation is only used if you start Oracle BPA Suite products from

your browser.

The following are approved: Java Runtime Environment (JRE) 1.6.0_04 and

subsequent patches that are in the public domain (Java SE on the SUN home

page except Java SE for Business) and generally released by SUN.

To display different character sets (Japanese, Arabic, Cyrillic, etc.), the

corresponding file in directory <JRE installation

directory>\<version>\lib must be named font.properties. For example,

if you wish to display Japanese characters, you must rename the

font.properties.ja file to font.properties.

Note

SUN renamed the JRE versions. JRE 1.6.0_04 is now called JRE 6.0, Update

4. Approvals are also valid for subsequent updates.

Oracle BPA Suite products are tested using the JRE that is current at the

time of release.

If JRE 1.6.0_04 and subsequent patches are approved for an Oracle BPA

Suite product, the approval is valid for both JRE 1.6.0_04 and JRE

1.6.0_05 and for any subsequent patch from the public domain Java SE

of the SUN home page (except for Java SE for Business). SUN

Microsystems guarantees compatibility between the JRE patch levels.

Therefore, the Oracle BPA Suite approvals for JREs are valid for all patch

levels of a version.

If you are using JRE 1.6 update 3 or an older version, copy the file jaxb-

api.jar from the directory <Web Client Components>\lib to the

directory <Java JRE installation directory>/endorsed, e.g.

C:\Program Files\Java\jre1.6.0_01\lib\endorsed.

If the directory endorsed does not exist, you must create it. Please


11

Software Details

note that you must repeat this procedure for every update of version 3 or

older. We therefore recommend installation of version 4 or higher.

If you have Java 6 update 10 installed, problems may occur despite

better performance. Depending on your graphics card and driver

configuration, installation of Java 6 update 10 may cause delays in the

Designer and Matrices modules.

In this case, use the following command line entry to start the program:

-Dsun.java2d.d3d=false

Protocols

(Page 249)

Data exchange between browser-capable Oracle BPA Suite clients and Oracle

Business Process Repository can be encrypted with SSL (1024-bit RSA).

SSL capability is already integrated into Oracle BPA Suite and only needs to

be activated when needed.

If Oracle BPA Suite clients within the intranet or in a VPN environment

(Virtual Private Network) access Oracle Business Process Repository, no

firewall is required. Communication between clients and Oracle Business

Process Repository takes place via the CORBA protocol IIOP (Internet Inter

Object Request Broker Protocol).

Output If, for example, you want to output documents in PDF format using Microsoft

Word or Microsoft Excel, you must have Adobe Reader and Microsoft Office

version 2000, 2002, 2003, or 2007 installed. If you use reports to import

data from Excel tables, please ensure that the tables have been saved in

XLS format. If pop-up blockers are activated for the domain, it may not

always be possible to open report output in PDF format from a Publisher

export.

In addition, all applications that are linked in your models should be

installed.

Note

Oracle Business Process Repository does not support NAT (Network

Address Translation) by default. However, Oracle Corporation offers

customized solutions. Additional information is available from our

support.


12

2.4.1 Default (recommended for up to 50 users)

Use the following procedures to install:

Oracle BPA Suite Site Administrator



Standard database system

Oracle BPA Suite Web Client Components

Procedure

1. Ensure that the system requirements (Page 242) for all components

are met.

2. Perform the default server installation (Page 12). The standard

database system is installed automatically at the same time.

3. If you want to use Java-based Oracle BPA Suite products via a

browser, please ensure that a Web server is installed on the

computer and that the Web server default path points to <Oracle

BPA Suite installation directory>\Server\HTML.

Install the relevant clients on the workstations.

2.4.1.1 Initial installation

The detailed description below explains the steps that the installation

program performs when you run the standard installation of Oracle

Business Process Repository on your system for the first time.

Procedure



2. Insert the Oracle BPA Suite installation media into your drive. If

the start page is not displayed automatically, click on the name of

your drive in Windows Explorer and run the OracleBPA.exe

program.

3. Click on Additional Installations.

4. Click on Install Oracle Business Process Repository.

5. The installation program's Welcome page opens. Click on Next.


13

6. The license agreement is displayed. Please read it carefully. To

accept the license agreement, click on Yes. The Select target path

page opens.

7. If other Oracle BPA Suite products are already installed on the


products are installed is used.






on Next.

Note

Note that the name of the installation directory must not contain any

spaces or country-specific special characters.





Suite is created.



on Next.

10. Enable the check boxes for the languages in which you want to install

the program. Ensure that all languages you want to provide to the

Oracle BPA Suite clients are installed. Click on Next.

11. Click on Default (recommended for up to 50 users). The Select

target path page opens.

12. Select the installation directory for your Oracle BPA Suite Web Client

Components files. To use the suggested installation directory, click

on Next and continue with the next step. Note that the name of the

installation directory must not contain any country-specific special

characters.

To install the program in a directory different from the one

suggested, e.g. on your active Web server, click on Browse. Enter

the desired path in the Path box, or navigate to the desired directory

in the Directories box. Click on OK. Click on Next.


14

13. Decide whether or not the program is to be installed as a Windows

service by enabling the relevant check box. If you install it as a

Windows service, it will be launched automatically with the operating

system. Otherwise, you need to click on the program icon to run the

program. Click on Next.

14. Check the settings in the Installation Overview dialog box. If these

are correct, click on Next. The products will now be installed.

15. Confirm the Welcome dialog and, once the driver is installed,

completion of the installation. Click on Finish.

The installation is complete, and the installation program closes.

2.4.1.2 Subsequent installation


program performs when you have Oracle Business Process Repository

installed and call the same Oracle Business Process Repository

installation program again.

Previously used databases and filters are not affected by the subsequent

installation. If you want to use the supplied demo database rather than

the current one, you can copy it to your server using the Restore

function.

Report scripts supplied by default are reinstalled. If you changed

existing reports but did not rename them, we recommend that you

create backup copies and add them with modified names once the

installation is complete.

If files have to be reinstalled during setup, the old files are saved in a

backup directory. Therefore, they are still available after installation. The

contents of the HTML directories are examples of such files.

The configuration changes that you made in the file

userServerSettings.cfg are applied.

Procedure

1. Ensure that the system requirements are met for all components.







15

5. The Note dialog box asks you to terminate any running Oracle

Business Process Repository or the corresponding Windows service

(Page 217) before you continue with the installation. Click on OK

after having done so or if no Oracle Business Process Repository is

running.

6. The installation program's Welcome page opens. The Modify

Program option button is already enabled. Click on Next.

7. Enable the check boxes for the languages you want to add. Click on

Next. Please ensure that all languages you selected for the installed

Oracle BPA Suite products are installed.





program.

9. Check your settings in the summary. If your settings are correct,

click on Next. The components will now be installed.

10. Click on Finish.

The installation is complete and the installation program closes.

Tip


2.4.1.3 Update installation


program performs when you have Oracle Business Process Repository

installed and call the Oracle Business Process Repository installation

program with an Oracle BPA Suite installation media of a higher version.

Previously used databases and filters are not affected by the installation.

If you want to use the supplied demo database rather than the current

one, you can copy it to your server using the Restore function.

Report scripts supplied by default are reinstalled. If you changed

existing reports but did not rename them, we recommend that you

create backup copies and add them with modified names once the

installation is complete.

If files have to be reinstalled during setup, the old files are saved in a

backup directory. Therefore, they are still available after installation. The

contents of the HTML directories are examples of such files.


16

The configuration changes that you made in the file

userServerSettings.cfg are applied.

In older program versions, configuration changes were entered in

different files. If you run an update installation of the current version,

the configuration files are converted when Oracle Business Process

Repository is started. All configuration changes are entered in the file

userServerSettings.cfg. The configuration files are deleted. They are

backed up in the backup directory.

Procedure

1. Ensure that the system requirements are met for all components.






5. A message informs you that the currently installed Oracle Business

Process Repository version is older than the version of the Oracle

BPA Suite installation media and that an update will be performed.

Click on OK to confirm the message.

6. The Note dialog box asks you to terminate any running Oracle

Business Process Repository or the corresponding Windows service

before you continue with the installation. Click on OK after having

done so or if no Oracle Business Process Repository is running.



8. Click on Finish.


Tip



17

2.4.2 User-defined (advanced installation)

This installation option allows you to install Oracle Business Process

Repository Site Manager, Oracle Business Process Repository, and Oracle

BPA Suite Web Client Components separately or together.

Thus, a scenario can be set up in which Oracle Business Process

Repository and the database system (Oracle Business Process

Repository Site Manager) are installed on different computers.

For scenarios in which 200 or more users work simultaneously with

Oracle BPA Suite, we recommend that you install Oracle Business

Process Repository and the database system on different computers. It

is advisable that only Oracle Corporation employees perform this

type of installation (see chapter Support in the Administration

Guide).

Procedure

1. Ensure that the system requirements are met for all components

(see chapter Hardware and software requirements in the

Administration Guide).

2. Install a database system, or set up an existing database for work

with Oracle BPA Suite.

3. Install Oracle Business Process Repository Site Manager with the

appropriate option (see chapter Step-by-step instructions (Page 21))

on the server computer on which you installed your database.

Continue with step 5.

4. Install Oracle Business Process Repository on every computer you

want to use as Oracle Business Process Repository.

If you want to use Java-based Oracle BPA Suite products via a

browser, install Oracle BPA Suite Web Client Components and set up

your Web server for use with Oracle BPA Suite Web Client

Components (see chapter Oracle BPA Suite Web Client Components)

or

5. You can import the demo database into your database system.

a. Start Oracle BPA Suite Site Administrator.

b. Right-click on the name of the server, and select Restore.


18

c. Select the ADB file of the demo database in the directory

Databases and Filters\Databases on the installation media,

and click on Open.

Once the database is registered with Oracle BPA Suite, you receive a

corresponding message.

For the following procedures, it is assumed that there are no previous

installations on the computer. Unlike the installations described above,

user-defined options allow you to install any combination of components

from Oracle Business Process Repository, Oracle BPA Suite Site

Administrator, Oracle Business Process Repository Site Manager,

and Oracle BPA Suite Web Client Components.

The instructions describe the installation sequence if you select one of

the components provided. If you select more than one component, the

installation sequences are combined according to your selection.

Tip

To install an Oracle BPA Suite Site, perform the installation on every

computer you intend to use as an Oracle Business Process Repository in

the Oracle BPA Suite Site.

2.4.2.1 Oracle Business Process Repository

This section describes in detail the steps that the installation program

performs when you install an Oracle Business Process Repository.

Tip




Procedure


functionalities are met (see chapter Administration (Page 221)).







19



on Yes. The Select target path page opens. If other Oracle BPA

Suite products are already installed on the computer, this step is

skipped and the directory in which the other products are installed is

used. The Select program folder page opens.





Suite is created.



on Next. Enable the check boxes for the languages in which you

want to install the program. Ensure that all languages you want to

provide are installed. Click on Next. Click on USER-DEFINED

(ADVANCED INSTALLATION).

8. Either enter your license key or enable the Dongle Version

(Hardware Key) check box if you use a hardware key instead of a

license key. Click on Next. The Select target path page opens.

9. Disable all check boxes except the Oracle Business Process

Repository check box.

10. Enter the name of the computer on which Oracle Business Process

Repository Site Manager has been installed. Click on Next.





program.






20

2.4.2.2 Oracle BPA Suite Site Administrator


program performs when you install Oracle BPA Suite Site Administrator.

Procedure














7. The Select program folder page opens. Select the program

directory in which to place the program shortcut. If other Oracle BPA

Suite products are already installed on the computer, this step is

skipped and the directory in which the other products are installed is

used. The program directory for Oracle BPA Suite is created.



on Next.


the program. Ensure that all languages you want to provide are

installed. Click on Next. Click on USER-DEFINED (ADVANCED

INSTALLATION), recommended for 50 or more users.

9. Ensure that the Install ARIS Governance Engine check box is

cleared. Click on Next.

10. Either enter your license key or enable the Dongle Version

(Hardware Key) check box if you use a hardware key instead of a

license key. Click on Next.

11. Disable all check boxes except for the Oracle BPA Suite Site

Administrator check box.


21

12. Click on Next.

13. Check the settings in the Start Copy Operation dialog box. If these

are correct, click on Next. The products will now be installed.



2.4.2.3 Oracle Business Process Repository Site Manager

This section describes in detail the steps that the installation program

performs when you install Oracle Business Process Repository Site

Manager.

Warning

You may install Oracle Business Process Repository Site Manager only

once for each Oracle BPA Suite Site.

2.4.2.3.1 Step-by-step instructions - Use existing Oracle database (prepared for Oracle BPA Suite)

The database objects required for operating Oracle BPA Suite have

already been created (Page 221) (for example, using the SQL*PLUS

scripts).

Procedure




installation media start page is not displayed automatically, double-

click on the OracleBPA.exe file.



The installation program's Welcome page opens. Click on Next.



page opens.





22






on Next.

Note







Suite is created.



on Next.

8. The Select Language page opens. Enable the check boxes for the

languages in which you want to install the program. Ensure that all

languages you want to provide are installed. Click on Next. The

Select Components page opens.


Repository Site Manager check box. Click on Next.

10. Activate Oracle. Click on Next.

11. Click on Connect to already configured Oracle database

instance. The database may be installed locally or on a different

computer.

12. Click on Next. The Connect to already configured Oracle

database instance page opens.

13. Enter the server, port, and service name for the database. The

default name of the database is BPA. Click on Next.


service by enabling the relevant option button. If you install it as a





23





2.4.2.3.2 Step-by-step - Configure and connect existing Oracle database instance

You already have an Oracle database, but the database objects required

for operating Oracle BPA Suite have not been created (Page 221) there

yet. If you use Oracle Business Process Publisher, we recommend that

you work with two separate Oracle databases for Oracle Business

Process Repository and Oracle Business Process Publisher. This keeps

the two systems from competing for resources, and you achieve better

performance and higher availability.

You should set the tablespaces for automatic, unlimited growth.

Otherwise, you run the risk of completely exhausting the memory in the

tablespaces, which may cause important functions of Oracle Business

Process Repository and Oracle Business Process Publisher to fail. If the

option for automatic growth is not set, regular monitoring (e.g. weekly)

of the Oracle instance is required to ensure that the tablespaces are

manually increased on time.

Procedure



Ensure that Oracle SQLPlus is installed.









page opens. If other Oracle BPA Suite products are already installed

on the computer, this step is skipped and the directory in which the

other products are installed is used.


24






on Next.

Note







Suite is created.



on Next.

9. The Select Language page opens. Enable the check boxes for the

languages in which you want to install the program. Ensure that all

languages you want to provide are installed. Click on Next.

10. Click on User-defined (recommended for 50 or more users). The





13. Click on Configure and Connect Existing Oracle Database

Instance. The database may be installed locally or on a different

computer.

14. Click on Next.

15. The installation program checks whether an sqlplus command is

installed and whether a link can be established to it. If the check is

not successful, an error message is output. If the check is successful,

the dialog box Configure and Connect Existing Oracle Database

Instance opens.

16. If this happens, verify and correct the server name, port number,

service name for the database, and the password of the SYSTEM

user. Click on Next.


25

17. Select the data tablespace and the index tablespace in the dialog

box. Click on Next.










2.4.2.3.3 Step-by-step - Create new Oracle database instance

You set up (Page 221) a new Oracle database instance and prepare it for

use with Oracle Business Process Analysis Suite.

Procedure



Ensure that Oracle SQLPlus is installed.









page opens.






on Next.


26

Note







Suite is created.



on Next. The Select Language page opens.



installed. Click on Next.






13. Click on Create New Oracle Database Instance. The database

may be installed locally or on a different computer. Click on Next.

The Create New Oracle Database dialog box opens.

a. Select the Oracle database installation to be used.

b. Select the directory for the database files of the database being

created. To install the database in a different directory than the

one suggested, click on the Browse button.

c. Enter the relevant path in the Path box or navigate to the

relevant directory in the Directories box, and then click on OK.

Note that the name of the directory must not contain any

country-specific special characters.

d. The name of the new database is BPA.

e. Enter the password for the system users in the Password for

SYS, SYSTEM, etc. box, and confirm your entry.

f. Enter the port number of the new Oracle Listener. It must be a

port that is not used. This is checked in the next step. Port 1521

is the default.

14. Click on Next.


27





program.





2.4.2.3.4 Step-by-step - Microsoft SQL Server

You set up (Page 227) a new Microsoft SQL Server and prepare it for use

with Oracle Business Process Analysis Suite.

Procedure











page opens.









on Next.


28

Note







Suite is created.











12. Enable the Microsoft SQL Server option, and click on Next.










2.4.2.3.5 Step-by-step - IBM DB2

You set up (Page 231) a new DB2 server and prepare it for use with

Oracle Business Process Analysis Suite.

Procedure




29









page opens.









on Next.

Note







Suite is created.











12. Enable IBM DB2, and click on Next.


30










2.4.2.4 Oracle BPA Suite Web Client Components

If you want to use Oracle BPA Suite via a browser, you need to install

Oracle BPA Suite Web Client Components.

Oracle BPA Suite Web Client Components consist of passive Web server

components (e.g. HTML files) only.

Oracle BPA Suite Web Client Components and Web server

Before your Web server can use Oracle BPA Suite Web Client

Components, you need to specify one of the following settings:

Map a drive to the WWW root of the Web server.

Run Oracle Business Process Repository setup on the computer

where your Web server is installed. Enter the path to the WWW root,

e.g. <C:\inetpub\tomcat\>.

Oracle BPA Suite Web Client Components and HTML Generator

The index.html and aris_database.html files are updated by the

HTML Generator during system operation (for further information, please

refer to the chapter on HTML Generator - Current database lists in

the Administration Guide). The HTML Generator is configured using the

files defaultServerSettings.cfg and userServerSettings.cfg of

Oracle Business Process Repository, and it uses the templates located in

the directory Oracle Business Process

Repository/templates/htmlgen. It is launched every time a database

is created, deleted, or renamed.

The following directories are created:

/lan


31

This is the start directory commonly used. It runs the Java-based Oracle

BPA Suite products as an applet and enables direct access to the Oracle


/ssl

If you select this directory for launching Java-based Oracle BPA Suite

products, the data exchange is encrypted (for further information,

please refer to the chapter on SSL encryption of data transmission

via Secure Socket Layer in the Administration Guide).

/app


products, they are run as an application, not as an applet (for further

information, please refer to the chapter on Execution as application

or applet in the Administration Guide).

Note

To enable SSL encryption, open the file userServerSettings.cfg and

add the following entry:

<profiles>

<public ssl="443" />

</profiles>

Please note that the output and backup paths must be modified

accordingly in the userServerSettings.cfg file. If your work is not

limited to the use of only one Oracle Business Process Repository, you

need to adjust the paths on the computer on which Oracle Business

Process Repository Site Manager is installed. Insert the following entry:

<htmlgen>

path="e:/inetpub/wwwroot/bpa11"/><backuppath

path="e:/inetpub/wwwroot/bpa11/backup"/>

</htmlgen>


32

You make other changes in the same way:

<htmlgen>

<appserver name=“myspecialhost" />

<genlist>

<genfile target_dir="ssl"

target_name="dblist.html"

database_template="aris_database_ssl.html"/>

</genlist>

</htmlgen>

Warning





Procedure










on Yes.


suggested in the Target folder box, click on Next.





8. Click on USER-DEFINED (ADVANCED INSTALLATION), recommended

for 50 or more users.

9. Disable all check boxes except Oracle BPA Suite Web client

components. Click on Next. The Select target path page opens.


33

10. Select the installation directory for your Oracle BPA Suite Web Client

Components files. To use the suggested installation directory, click

on Next and continue with the next step. Note that the name of the

installation directory must not contain any country-specific special

characters.






click on Next. The components will now be installed. The installation

process generates the \html directory in the specified path. A path

is relative within the directory so that you can change the name of

the path specified during installation without any negative impact.

For multilingual pages, the start pages index_app.html,

index_lan.html, and index_ssl.html are located in the directory

\html. For monolingual pages, they reside in the directory

\html\<languageid>. These pages contain the database lists that

are generated by the HTML Generator whenever Oracle BPA Suite

deletes or adds databases or changes their names.



Note

If you install Oracle Business Process Repository Site Manager and

Oracle BPA Suite Web Client Components in one step, the installation

program enters the path to the HTML Generator in the file

setupServerSettings.cfg of the Oracle Business Process Repository

Site Manager computer.

Warning






34

2.5 Oracle Business Process Repository installations (Unix operating system)

This chapter describes installations related to Oracle Business Process

Repository that can be performed under a Unix operating system.
























Note







product.


35

Oracle Business Process Repository saves configuration data at the

operating system level. We strongly recommend protection at the

operating system level to minimize the risk of data misuse.



GHz

RAM 64-bit system

2 GB RAM

32-bit system

1 GB RAM In 32-bit



(VM) is 1 GB.

512 MB












canceled.


36

Software Details

Operating

systems




JRE Oracle Business Process Repository requires JRE 1.6. Please first install the

appropriate JRE 1.6 for your operating system.

Protocols

(Page 249)

Data exchange between browser-capable Oracle BPA Suite clients and Oracle

Business Process Repository can be encrypted with SSL (1024-bit RSA).

SSL capability is already integrated into Oracle BPA Suite and only needs to

be activated when needed.




Process Repository takes place via the CORBA protocol IIOP (Internet Inter

Object Request Broker Protocol).

Output If, for example, you want to output documents in PDF format using Microsoft

Word or Microsoft Excel, you must have Adobe Reader and Microsoft Office

version 2000, 2002, 2003, or 2007 installed. If you use reports to import

data from Excel tables, please ensure that the tables have been saved in

XLS format. If pop-up blockers are activated for the domain, it may not

always be possible to open report output in PDF format from a Publisher

export.


installed.

Note




support.

The following installation options exist:

Oracle Business Process Repository and Oracle Business Process

Repository Site Manager

Only Oracle Business Process Repository

Only Oracle Business Process Repository Site Manager


37

2.5.1 Oracle Business Process Repository

This section describes in detail the steps that must be performed when

you install Oracle Business Process Repository.

Tip




Step-by-step instructions

Prerequisite

A database instance for Oracle BPA Suite must have been created on the

database server.

Procedure

1. Ensure that the system requirements are met for all products and

features (please refer to chapter Administration, Hardware and

software requirements).

2. Insert the installation media, and navigate to the directory

Setups/Unix Linux/Oracle Business Process Repository. Copy

the file install_bpr11gR1.xxxxxx.sh to your hard drive.

3. Switch to the directory in which the Oracle Business Process

Repository installation script is located, and enter

./install_bpr11gR1.xxxxxx.sh [business_server_options] to

install Oracle Business Process Repository.

Specify the following options for the installation of Oracle Business

Process Repository:

-bpr_type BS

-jvm <Path of the Java Runtime Environment>

-sitemanager <Host Name of Oracle Business Process Repository

Site Manager>

4. You must enter a fully qualified name for the computer on which

Oracle Business Process Repository Site Manager is installed, for

example computerxyz.domainxyz.com. You can start the file

install_bpr11gR1.xxxxxx.sh from any directory. To do so, you

need to enter the full path in front of the file name.

To change the installation path, specify the additional option -

installdir <absolute path of the desired installation

directory>.


38

The parameters are stored in the file YYYMMDD-HHMMDD.data.conf

in the directory ./install_bpa11.xxxxxx.sh/setup/backup.

The script extracts itself and stores the files in the

/install_bpa11.xxxxxx.sh subdirectory.

Configuration is performed automatically with the installation. You can

reconfigure the software at any time after installation with the

configure.sh script in the install_bpa11.xxxxxx.sh/setup folder. The

software is ready to run immediately. To start Oracle Business Process

Repository, use the launcher y-serverlauncher.sh in the directory

install_bpa11.xxxxxx.sh.

Note

The Oracle BPA Suite Web Client Components (Page 41) are installed

automatically at the same time.

2.5.2 Oracle Business Process Repository Site Manager


you install Oracle Business Process Repository Site Manager.

Warning

You may install Oracle Business Process Repository Site Manager only

once for each Oracle BPA Suite Site.


Procedure






Switch to the directory in which the Oracle Business Process

Repository installation script is located, and enter sh

install_bpr11gR1.xxxxxx.sh [site_manager_options] to install Oracle

Business Process Repository Site Manager.


Process Repository Site Manager:

-bpr_type SM


-dbserver <Host name of the database server>


39

-dbport <Port of the database server>

-dbinstance <Name of the database instance>

You must enter a fully qualified name for the database server, that

is, computerxyz.domainxyz.com, for example. You can start the

file install_bpr11gR1.xxxxxx.sh from any directory. To do so, you

need to enter the full path in front of the file name.



directory>.






reconfigure the software at any time after installation with the script

configure.sh in the directory install_bpa11.xxxxxx.sh/setup. The




2.5.3 Oracle Business Process Repository and Oracle Business Process Repository Site Manager


you install Oracle Business Process Repository and Oracle Business

Process Repository Site Manager simultaneously.

Tip





Prerequisite

A database instance for Oracle BPA Suite must have been created on the

database server.


40

Procedure






Switch to the directory in which the Oracle Business Process

Repository installation script is located, and enter sh

install_bpr11gR1.xxxxxx.sh [site_manager_options] to install Oracle

Business Process Repository and Oracle Business Process

Repository Site Manager.


Process Repository and Oracle Business Process Repository Site

Manager:

-bpr_type BS_SM


-dbserver <Host name of the database server>

-dbport <Port of the database server>

-dbinstance <Name of the database instance>

You must enter a fully qualified name for the database server, that

is, computerxyz.domainxyz.com, for example. You can start the

file install_bpr11gR1.xxxxxx.sh from any directory. To do so, you

need to enter the full path in front of the file name. If



directory>.






reconfigure the software at any time after installation with the script

configure.sh in the directory install_bpa11.xxxxxx.sh/setup. The





41

Note

The Oracle BPA Suite Web Client Components (Page 41) are installed

automatically at the same time.

2.5.4 Oracle BPA Suite Web Client Components

When you install Oracle Business Process Repository on a computer with

a Unix operating system, the Oracle BPA Suite Web Client Components

are installed automatically at the same time.

Oracle BPA Suite Web Client Components consist of passive Web server

components (e.g. HTML files) only.

For multilingual pages, the start pages index_app.html,

index_lan.html, and index_ssl.html are located in the directory

\html. The respective language page is located in the directory

\html\<languageid>. These pages contain the database lists that are

generated by the HTML Generator whenever Oracle BPA Suite deletes or

adds databases or changes their names.

Oracle BPA Suite Web Client Components and Web server

Before your Web server can use Oracle BPA Suite Web Client

Components, you need to specify one of the following settings:

Map a drive to the WWW root of the Web server.

Run Oracle Business Process Repository setup on the computer

where your Web server is installed. Enter the path to the WWW root,

e.g. <C:\inetpub\tomcat\>.

Oracle BPA Suite Web Client Components and HTML Generator

The index.html and aris_database.html files are updated by the

HTML Generator during system operation (for further information, please

refer to the chapter on HTML Generator - Current database lists in

the Administration Guide). The HTML Generator is configured using the

files defaultServerSettings.cfg and userServerSettings.cfg of

Oracle Business Process Repository, and it uses the templates located in

the directory Oracle Business Process

Repository/templates/htmlgen. It is launched every time a database

is created, deleted, or renamed.

The following directories are created:

/lan


42

This is the start directory commonly used. It runs the Java-based Oracle

BPA Suite products as an applet and enables direct access to the Oracle


/ssl


products, the data exchange is encrypted (for further information,

please refer to the chapter on SSL encryption of data transmission

via Secure Socket Layer in the Administration Guide).

/app


products, they are run as an application, not as an applet (for further

information, please refer to the chapter on Execution as application

or applet in the Administration Guide).

Note

To enable SSL encryption, open the file userServerSettings.cfg and

add the following entry:

<profiles>

<public ssl="443" />

</profiles>

Please note that the output and backup paths must be modified

accordingly in the userServerSettings.cfg file. If your work is not

limited to the use of only one Oracle Business Process Repository, you

need to adjust the paths on the computer on which Oracle Business

Process Repository Site Manager is installed. Insert the following entry:

<htmlgen>

path="e:/inetpub/wwwroot/bpa11"/><backuppath

path="e:/inetpub/wwwroot/bpa11/backup"/>

</htmlgen>


43

You make other changes in the same way:

<htmlgen>

<appserver name=“myspecialhost" />

<genlist>

<genfile target_dir="ssl"

target_name="dblist.html"

database_template="aris_database_ssl.html"/>

</genlist>

</htmlgen>

Warning





2.5.5 Uninstall

To uninstall one or more of the following components, you first have to

exit Oracle Business Process Repository and then delete the component.

Procedure

1. Use the script y-serverstopper.sh in the folder <installation

directory>/server.xxxxxx to exit Oracle Business Process

Repository.

2. Delete the folder <installation directory>/server.xxxxxx:

rm –r <installation directory>/server.xxxxxx


44

2.6 Oracle Business Process Publisher Server installations

This chapter describes the Oracle Business Process Publisher Server

installations for the approved Web Application Servers.

Oracle Business Process Publisher Servers manage every Publisher

export. A Publisher export is a Web application based on J2EE. Java

Servlets and Java Server Pages (JSP) are used, which, in addition to a

Java environment (JDK), require a Web application server (for example

Apache Tomcat) as runtime environment. The data is held in a

relational database system and is exchanged with the program via a

JDBC interface.

The standard database system and Apache Tomcat Web Application

Server are automatically installed if you select the standard installation

for Oracle Business Process Publisher Server. With this database system,

up to 10 users can access a Publisher export simultaneously. Swimlane

models cannot be exported optimally using a Derby database. For a

larger number of users, you require an external database system.

Depending on the Oracle Business Process Publisher Server license

purchased, these systems enable all users to simultaneously work on a

Publisher export.

After the standard installation, reports are run by Oracle Business

Process Publisher Server. You can additionally install a Report Server

(Page 194) to optimize system performance when running reports

Note

Due to methodological and functional changes, you may no longer be

able to open an existing Publisher export. If this happens, you must

perform exports again. The browser caches should be cleared after an

update installation.

2.6.1 Apache Tomcat Web Application Server under Windows

This chapter describes the installation of Apache Tomcat Web Application

Server under Microsoft Windows.

Note





45




2.6.1.1 Step-by-step instructions (standard database)

This procedure describes the standard installation of Apache Tomcat

Web Application Server. With this database system, up to 10 users can

access exports simultaneously. For a larger number of users, you need

the Oracle (Page 288) database system or MS SQL Server 2005.


purchased, these systems enable all users to simultaneously work on

exports.

Procedure



2. Insert the Oracle BPA Suite installation media into the appropriate

drive. If the start page is not displayed automatically, click on the

name of your drive in Windows Explorer and run the OracleBPA.exe

program.


4. Click on Install Oracle Business Process Publisher Server.












on Next.

Note



The Select program folder page opens.


46





Suite is created.



on Next.

9. Select the Oracle Business Process Publisher Server option. The

Enter port number page opens.

10. Enter the port number for accessing Oracle Business Process

Publisher Server via a browser. The port number you entered must

not be used by another application (e.g. Web server). Click on Next.

11. Enable the Standard Database System check box if you want to

use the standard database. Click on Next.



13. Click on Finish. The installation is complete and the installation

program closes.

14. If you want to use another database instead of the Derby database,

ensure that the appropriate database is installed and adjust the

database management system for use with Oracle Business Process

Publisher Server (Page 233).

15. Communicate the URL (<root directory of Oracle Business

Process Publisher Server>/<context>) that allows users to

access every Publisher export and administrators to manage exports.

After the standard installation of Oracle Business Process Publisher

Server, the URL is http://<server

name>:9090/businesspublisher if you did not change the default

settings during installation.

16. If you have installed Oracle Business Process Publisher Server on an

external computer, change the IP address in the configuration file.

To create a Publisher export and enable users to work with it, you must

start Oracle Business Process Publisher Server and communicate the

URL. After the standard installation of Oracle Business Process Publisher

Server, the URL is http://<server name>:9090/businesspublisher

if you did not change the default settings during installation.


47

2.6.1.2 Step-by-step instructions (Oracle database)

Please adjust your system as required to run Oracle Business Process

Publisher in combination with Apache Tomcat Web application server and

an Oracle database. If you use this database, all enabled users can work

simultaneously with a Publisher export. This description assumes you

are using Apache Tomcat.

Prerequisite

You have created an Oracle database and configured it as follows. If

you install a database yourself, always follow the instructions

provided in the Oracle Installation Guide. We recommend that you

use two separate Oracle databases for Oracle Business Process

Repository and Oracle Business Process Publisher. This keeps the two

systems from competing for resources, and you achieve better


Use of the database character set AL32UTF8 is mandatory.

We recommend a block size of 8K.

query_rewrite_enabled=true

query_rewrite_integrity=trusted

You have created two tablespaces: ARISBPDATA (for table data)

and ARISBPINDEX (for index data). To use other names or

existing tablespaces, you must customize the configuration file

webappserver.cfg (see below). We recommend that you set the

tablespaces for automatic, unlimited growth. Otherwise, you run

the risk of completely exhausting the memory in the tablespaces,

which may cause important functions of Oracle Business Process

Repository and Oracle Business Process Publisher to fail. If the

option for automatic growth is not set, regular monitoring (e.g.

weekly) of the Oracle instance is required to ensure that the

tablespaces are manually increased on time.

You have created an Oracle user that Oracle Business Process

Publisher can use to connect to the database. The name of the

Oracle user is assumed to be ARISBP. You can select any

password. Enter it in the configuration file

businesspublisher.xml (see below). If you prefer another

name, change the name there as well:

CREATE USER ARISBP IDENTIFIED BY ARISBP;

The Oracle user must have the following privileges

GRANT CREATE SESSION TO ARISBP;

GRANT ALTER SESSION TO ARISBP;


48

GRANT CREATE TABLE TO ARISBP;

GRANT CREATE VIEW TO ARISBP;

GRANT QUERY REWRITE TO ARISBP;

ALTER USER ARISBP QUOTA UNLIMITED ON ARISBPDATA;

ALTER USER ARISBP QUOTA UNLIMITED ON ARISBPINDEX;

We recommend that you turn off the Oracle recycle bin because

large quantities of tables accumulate there when exports are

deleted.

Procedure

1. Open the file businesspublisher.xml in the Oracle Business Process

Publisher Server installation directory

..\BPServer\tomcat\conf\catalina\localhost\ with a text

editor.

2. Ensure that the following entries are maintained:

<Context path="/businesspublisher" docBase="C:\Program

Files\Oracle BPA

Suite11\BPServer\tomcat\webapps\businesspublisher\" debug="0"

reloadable="false" crossContxt="true">

<Resource name="jdbc/businesspublisherdb" auth="Container"

type="javax.sql.DataSource"

maxActive="30" maxIdle="30" maxWait="1000"

initialSize="10"



username="ARISBP" password="ARISBP" 

driverClassName="oracle.jdbc.driver.OracleDriver"

url="jdbc:oracle:thin:@localhost:1521:ARISBP" 

connectionProperties="SetBigStringTryClob=true"/>

</Context>

3. Open the file webappserver.cfg in the Oracle Business Process


..\BPServer\tomcat\webapps\businesspublisher\config\ with

a text editor.



49

a. Ensure that the following entries are correctly maintained:

<bp-oracle tablespace-data="ARISBPDATA" tablespace-

index="ARISBPINDEX" />

If you have decided to use other tablespace names (see

Prerequisites), please maintain them here.

b. Ensure that you have adjusted the entries for

DatabaseDAOClass as follows:

<env-entry>

<description>The IDatabaseDAO Implementation

Class</description>

<env-entry-name>DatabaseDAOClass</env-entry-name>

<env-entry-type>java.lang.String</env-entry-type>

<env-entry-value>

com.idsscheer.aris.businesspublisher.application.dao.database.A

OracleDAO</env-entry-

value>

</env-entry>

4. Ensure that the JDBC driver ojdbc5.jar exists in the Oracle Business

Process Publisher Server installation directory

..\BPServer\tomcat\common\lib. We assume that you are using

version 10.2.0.3. You find the file on the installation media.

Note







Install Oracle Business Process Publisher Server

Procedure






program.


50














on Next.

Note








Suite is created.



on Next.






11. To use an Oracle database, enable the Oracle Database check box.

12. Click on Connect to already configured Oracle database

instance. The database may be installed locally or on a different

computer.

13. Click on Next. The Connect to already configured Oracle

database instance page opens.


51

14. Enter the name or IP address of the computer on which your Oracle

Business Process Publisher Server is installed. Enter the port number

(1521 is set as default), service name of your database (BUPU1020

is set as default), and database user (ARISBP is set as default). Click

on Next.




program closes.

2.6.1.3 Step-by-step instructions (existing Oracle database)_tomcat






Prerequisite






















52




















deleted.

Procedure




editor.



Files\Oracle BPA






initialSize="10"


53












</Context>




a text editor.








<env-entry>


Class</description>



<env-entry-value>



value>

</env-entry>



54





Note








Procedure






program.














on Next.


55

Note








Suite is created.



on Next.








computer. Click on Next.





Instance opens.

13. If this happens, verify and correct the server name, port number,

service name for the database, and the password of the SYSTEM

user. Click on Next.


box. Click on Next.




program closes.


56

2.6.1.4 Step-by-step instructions (new Oracle database)_tomcat






Prerequisite

































57









deleted.

Procedure




editor.



Files\Oracle BPA






initialSize="10"












</Context>



58




a text editor.








<env-entry>


Class</description>



<env-entry-value>



value>

</env-entry>





Note








59


Procedure






program.














on Next.

Note








Suite is created.



on Next.




60







The Create New Oracle Database Instance dialog box opens.














is the default.

13. Click on Next.





on Next.




program closes.


61

2.6.1.5 Step-by-step instructions (MS SQL Server 2005 database)

Please adjust the system as required to manage Oracle Business Process

Publisher in combination with an MS SQL Server 2005 database. If you

use the MS SQL Server 2005 database, all users covered by the license

can simultaneously work with a Publisher export, which is not possible

with the standard database.

Prerequisite

Copy the file create_db.sql (installation media/Setups/All OS/Oracle

Business Process Publisher Server) to a directory of your choice.

You have installed Microsoft SQL Server 2005 under MS Windows.

Microsoft SQL Server 2005 is not included in the package.

Procedure

1. Open the Server properties dialog box.

2. On the Security tab, select the SQL Server and Windows

authentication mode option.

3. Create a database using the script create_db.sql.

a. Open the script for editing.

b. Adjust the path to the database file. Ensure that the path has

been created before you run the script.

If you specify the ARISBP11 database name, user name, and

password according to your choice, you must also change them in

the configuration files businesspublisher.xml and

webappserver.cfg.

c. Ensure that Latin1_General_CI_AI sorting is selected for the

COLLATE statement.

The script creates the specified data groups. If you have changed

the names in the script, you must also change them in the

configuration file businesspublisher.xml.

ARISBPDATA: contains all database objects

ARISBPINDEX: contains all index data

d. Copy the JDBC driver jTDS.jar (installation media/Setups/All

OS/Oracle Business Process Publisher Server) to the Tomcat

installation directory under common/lib.


62

4. Customize the configuration file

..\BPServer\tomcat\conf\catalina\localhost\businesspublisher.xml:

a. Ensure that the driverClassName property is set to

net.sourceforge.jtds.jdbc.Driver.

b. Ensure that the URL has been adjusted correctly, for example as

follows:

jdbc:jtds:sqlserver://hostname:<Port>/ARISBP11

If you have specified a database name of your choice, use it

instead of ARISBP11.

If you are using named instances, complete the URL with the

following entry:

;instance=<name of instance>, for example,

jdbc:jtds:sqlserver://hostname:1433/ARISBP11;instance

=MSSQLSRV.

c. Change the user name and password.


..\BPServer\tomcat\webapps\businesspublisher\config\webappserv

er.cfg.

a. Ensure that the entries in the following line are correct:

<bp-mssql schema="ARISBPDATA" filegroup-

data="ARISBPDATA" filegroup-index="ARISBPINDEX" />

If you have changed the names in the script, you must adjust

them here.

6. Ensure that the database connection is set for MSSQL.

<env-entry>


Class</description>



<env-entry-

value>com.idsscheer.aris.businesspublisher.application.dao.database

.AMSSQLDAO</env-entry-value>

</env-entry>

Tip

For additional information about Microsoft SQL Server 2005, visit

http://support.microsoft.com/kb/914277/en-us

(http://support.microsoft.com/kb/914277/en-us).



63

Note








Procedure






program.














on Next.

Note









64

Suite is created.



on Next.






11. To use an MS SQL Server, enable the MS SQL Server check box.





on Next.




program closes.

Sample script create_db.sql USE master GO CREATE DATABASE [ARISBP11] ON PRIMARY (NAME = N'ARISBPPRIM', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPPRIM.mdf' , SIZE = 10MB , FILEGROWTH = 10MB), FILEGROUP [ARISBPDATA] (NAME = N'ARISBPDATA', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPDATA.ndf' , SIZE = 100MB , FILEGROWTH = 100MB), FILEGROUP [ARISBPINDEX] (NAME = N'ARISBPINDEX', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPINDEX.ndf' , SIZE = 100MB , FILEGROWTH = 100MB) LOG ON (NAME = N'ARISBPLOG', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPLOG.ldf' , SIZE = 10MB , FILEGROWTH = 10MB) COLLATE Latin1_General_CI_AI GO EXEC dbo.sp_dbcmptlevel @dbname=N'ARISBP11', @new_cmptlevel=90 GO BEGIN TRY EXEC [ARISBP11].[dbo].[sp_fulltext_database] @action = 'disable' END TRY BEGIN CATCH END CATCH


65

GO ALTER DATABASE [ARISBP11] SET ANSI_NULL_DEFAULT OFF GO ALTER DATABASE [ARISBP11] SET ANSI_NULLS OFF GO ALTER DATABASE [ARISBP11] SET ANSI_PADDING OFF GO ALTER DATABASE [ARISBP11] SET ANSI_WARNINGS OFF GO ALTER DATABASE [ARISBP11] SET ARITHABORT OFF GO ALTER DATABASE [ARISBP11] SET AUTO_CLOSE OFF GO ALTER DATABASE [ARISBP11] SET AUTO_CREATE_STATISTICS ON GO ALTER DATABASE [ARISBP11] SET AUTO_SHRINK OFF GO ALTER DATABASE [ARISBP11] SET AUTO_UPDATE_STATISTICS ON GO ALTER DATABASE [ARISBP11] SET CURSOR_CLOSE_ON_COMMIT OFF GO ALTER DATABASE [ARISBP11] SET CURSOR_DEFAULT GLOBAL GO ALTER DATABASE [ARISBP11] SET CONCAT_NULL_YIELDS_NULL OFF GO ALTER DATABASE [ARISBP11] SET NUMERIC_ROUNDABORT OFF GO ALTER DATABASE [ARISBP11] SET QUOTED_IDENTIFIER OFF GO ALTER DATABASE [ARISBP11] SET RECURSIVE_TRIGGERS ON GO ALTER DATABASE [ARISBP11] SET RECOVERY FULL GO ALTER DATABASE [ARISBP11] SET MULTI_USER GO ALTER DATABASE [ARISBP11] SET PAGE_VERIFY CHECKSUM GO CREATE LOGIN ARISBP11 WITH PASSWORD=N'ARISBP', DEFAULT_DATABASE=[ARISBP11] GO USE [ARISBP11] GO CREATE USER [ARISBP11] FOR LOGIN [ARISBP11] GO CREATE SCHEMA [ARISBPDATA] GO ALTER USER ARISBP11 WITH DEFAULT_SCHEMA = ARISBPDATA; GO GRANT CONTROL ON SCHEMA :: [ARISBPDATA] TO [ARISBP11] GO GRANT CREATE TABLE TO [ARISBP11] GO GRANT CREATE VIEW TO [ARISBP11] GO GRANT CREATE FUNCTION TO [ARISBP11] GO


66

2.6.2 Apache Tomcat Web Application Server under Solaris/Linux


Server on Solaris or Linux systems.

Note







Step-by-step instructions (MS SQL Server 2005 database)

This procedure describes the adjustments to an Apache Tomcat Web

Application Server 5.5.25 under Solaris 5.20 en if you are using an MS

SQL Server 2005 database.

Prerequisite

Copy the file jtds.jar (installation media/Setups/All OS/Oracle

Business Process Publisher Server/MSSQL) to a directory of

your choice.

You need the file businesspublisher.war for WAR deployment. You

find this file on the installation media, or you can download it from

www.oracle.com.

You have created and configured an MS SQL Server 2005 database

(Page 234). If you install a database yourself, always follow the

instructions provided in the MS SQL Installation Guide.

Procedure

1. Download (http://tomcat.apache.org) the file apache-tomcat-

5.5.25.tar.gz, and unzip the contents to a directory, such as tmp,

for which you have all privileges.

This provides you with the standard configuration, which you now

adjust.

2. Open the subdirectory ..tomcat/bin, and create the file setenv.sh

there.

3. Adjust the following variables as shown in the example:

CATALINA_HOME="/tmp/apache-tomcat-5.5.25"

JAVA_HOME="/usr/jre/jre1.5.0_10"

http://tomcat.apache.org/


67

CATALINA_OPTS="$CATALINA_OPTS -

Daris.businesspublisher.home=$CATALINA_HOME/webapps/

businesspublisher -

Djava.security.auth.login.config="$CATALINA_HOME/webapp

s/businesspublisher\config\BPLogin.cfg" -

Xbootclasspath/p:/tmp/orbacus.4.3.2.jar -Xms128m -

Xmx1024m-XX:MaxPermSize=128m"

4. Copy the file businesspublisher.war to the installation directory

.../apache-tomcat-5.5.25/webapps. You find the file on the

installation media or on our ftp server (ftp://ftp.ids-

scheer.de/pub/ARIS/HELPDESK/).

5. Test the configuration by starting Tomcat. To do this, run the file

startup.sh in the installation directory apache-tomcat-5.5.25/bin.

The businesspublisher.war file is automatically extracted and

integrated in the system (deployment).

ftp://ftp.ids-scheer.de/pub/ARIS/HELPDESK/



68

6. Stop Tomcat by running the file shutdown.sh in the installation

directory .../apache-tomcat-5.5.25/bin.

7. Open the file webappserver.cfg in the installation directory

.../apache-tomcat-

5.5.25/tomcat/webapps/businesspublisher/config/.

8. Enter the new license key in the License key line, e.g.

<license key="C99999-XXX_Business_Publisher-

V71LdeLenPdU250-XXXX..."/>

9. In the bpservicehost value line, change the value for the IP

address of the computer on which Tomcat is installed, e.g.

<bpservicehost value="172.30.111.123"/>


<env-entry>


Class</description>



<env-entry-



</env-entry>

11. Save the change and close the file.


69

12. Create the file businesspublisher.xml in the installation directory

.../apache-tomcat-5.5.25/conf/catalina/localhost.

13. Insert the following lines at the end of this file:



<Context path="/businesspublisher" docBase="/tmp/apache-tomcat-

5.5.20/webapps/businesspublisher/" debug="1" reloadable="true"

crossContxt="true">

Rescource name="jdbc/businesspublisherdb" auth="Container"

type="javax.sql.DataSource" maxActive="30" maxIdle="30"

maxWait="1000" initialSize="10" username="<enter the user

name>" password="<enter the password of the user>"

driverClassName="net.sourceforge.jtds.jdbc.Driver"

url="jdbc:jtds:sqlserver://<Hostname>:<Port>/ARISBP71"

</Context>

</Host>

</Engine>

</Server>


15. Customize the configuration file batchserver.cfg. You find more

information about this in the file.

Ensure that the value of the key name value is maintained with the

name of the batch server and the key host value with the IP

address or the fully qualified name.

16. Copy the file jtds.jar (installation media/Setups/All OS/Oracle

Business Process Publisher Server) to the installation directory

.../apache-tomcat-5.5.25/common/lib.

17. Start Tomcat.

The system is configured.



Application Server 5.5.25 under Solaris/Linux.


5.5.25.tar.gz, and unzip the contents to a directory for which you

have all privileges.



70

The following folder structure is created.


adjust.

2. Copy the file orbacus<version number>.jar (installation

media/Setups/All OS/Oracle Business Process Publisher Server) to a

local directory. The version number may have changed since

completion of this document. In this example, the file name is

orbacus.4.3.2.jar.

3. Open the bin subdirectory, and create the file setenv.sh with the

following content:

CATALINA_HOME="/<directory>/apache-tomcat-5.5.25"

JAVA_HOME="/usr/jre/jre1.6.0_4



businesspublisher -

Djava.security.auth.login.config=$CATALINA_HOME/webapps

/businesspublisher/config/bplogin.cfg -

Xbootclasspath/p:/<path>/orbacus.4.3.2.jar -Xms128m -

Xmx1024m"

Adapt the paths and file names to the relevant system.

4. Copy the file businesspublisher.war (installation media/Setups/All

OS/Oracle Business Process Publisher Server or IDS ftp server

(ftp://ftp.ids-scheer.de/pub/ARIS/HELPDESK/)) to the installation

directory .../apache-tomcat-5.5.25/webapps.



The file businesspublisher.war is automatically extracted and the

structure .../apache-tomcat-

5.5.25/tomcat/webapps/businesspublisher/config is created.





71

7. Open the file .../apache-tomcat-

5.5.25/tomcat/webapps/businesspublisher/config/webappserver.cf

g.

a. In the bpservicehost value line, change the value for the IP



8. Ensure that the database connection is set for Oracle here:

<env-entry>


Class</description>



<env-entry-value>

com.idsscheer.aris.businesspublisher.application.dao.database.AOra

cleDAO</env-entry-

value>

</env-entry>



.../apache-tomcat-5.5.25/tomcat/conf/catalina/localhost

with the following content:

<Context path="/businesspublisher" docBase="/opt/apache-

tomcat-5.5.25/webapps/businesspublisher" debug="0"


<Resource name="jdbc/businesspublisherdb"

auth="Container" type="javax.sql.DataSource"


username="ARISBP" password="ARISBP"


url="jdbc:oracle:thin:@DBSERVER:PORT:INSTANCE"


</Context>


12. Customize the configuration file batchserver.cfg, and save your

changes. You find more information about this in the file.


72

13. Copy the file ojdbc5.jar (installation media/Setups/All

OS/Oracle Business Process Publisher Server) to the installation

directory .../apache-tomcat-5.5.25/common/lib.

14. Start Tomcat.

Users can now create Web exports.

Note

1. When you combine various technologies, please observe the








Application Server 5.5.25 under Solaris/Linux.


5.5.25.tar.gz, and unzip the contents to a directory for which you

have all privileges.

The following folder structure is created.


adjust.

2. Copy the file orbacus<version number>.jar (installation

media/Setups/All OS/Oracle Business Process Publisher Server) to a

local directory. The version number may have changed since

completion of this document. In this example, the file name is

orbacus.4.3.2.jar.

3. Open the bin subdirectory, and create the file setenv.sh with the

following content:



73

CATALINA_HOME="/<directory>/apache-tomcat-5.5.25"

JAVA_HOME="/usr/jre/jre1.6.0_4



businesspublisher -

Djava.security.auth.login.config=$CATALINA_HOME/webapps

/businesspublisher/config/bplogin.cfg -

Xbootclasspath/p:/<path>/orbacus.4.3.2.jar -Xms128m -

Xmx1024m"

Adapt the paths and file names to the relevant system.

4. Copy the file businesspublisher.war (installation media/Setups/All

OS/Oracle Business Process Publisher Server or IDS ftp server

(ftp://ftp.ids-scheer.de/pub/ARIS/HELPDESK/)) to the installation

directory .../apache-tomcat-5.5.25/webapps.



The file businesspublisher.war is automatically extracted and the

structure .../apache-tomcat-

5.5.25/tomcat/webapps/businesspublisher/config is created.



7. Open the file .../apache-tomcat-

5.5.25/tomcat/webapps/businesspublisher/config/webappserver.cf

g.

a. In the bpservicehost value line, change the value for the IP




<env-entry>


Class</description>



<env-entry-



</env-entry>




74


.../apache-tomcat-5.5.25/tomcat/conf/catalina/localhost

with the following content:

<Context path="/businesspublisher" docBase="/opt/apache-tomcat-

5.5.25/webapps/businesspublisher" debug="0" reloadable="false"

crossContxt="true">




username="ARISBP" password="ARISBP"


url="jdbc:oracle:thin:@DBSERVER:PORT:INSTANCE"


</Context>


12. Customize the configuration file batchserver.cfg, and save your

changes. You find more information about this in the file.

13. Copy the file jtds.jar (installation media/Setups/All OS/Oracle

Business Process Publisher Server) to the installation directory

.../apache-tomcat-5.5.25/common/lib.

14. Start Tomcat.

Users can now create Web exports.

Note







2.6.3 IBM WebSphere Application Server (WAS 6.1.0.15) under Windows


Publisher Server in combination with IBM WebSphere Application Server

(WAS 6.1.0.15) and approved databases.

If you select this procedure, you must make some settings in the

administration console of IBM WebSphere.


75

Note








This procedure describes the adjustments to an IBM WAS 6.1.0.15 (en)

if you are using an Oracle database 10g.

Prerequisite

Copy the file from the directory installation media/Setups/All

OS/Oracle Business Process Publisher Server/Oracle/IBM

Websphere to a directory of your choice.



www.oracle.com.






















76




















deleted.

Procedure

1. After the installation, click on Start/Programs/IBM

Websphere/Application Server

V6.1/Profile/<Appsrv01>/Start Server.

2. Open the administration console of your IBM WebSphere Application

Server in the browser (http://localhost:9060/ibm/console), and

create a JDBC provider.

3. Click on Resources/JDBC/JDBC Provider in the views.


77

4. In the Scope box, select the Cell entry and click on New.

5. Select the Oracle entry in the Database type box.

6. Select the Oracle JDBC Driver entry in the Provider type box.

7. In the Implementation type box, select the Connection pool

data source entry.

8. Enter the name in the Name box and a description in the

Description box. Then click on Next.


78

9. Click on Next, and enter the path to the ojdbc file in the Class path

box (see Prerequisites). If the value has not been correctly

transferred, correct the path on the page JDBC providers/Oracle

JDBC Driver.

10. Click on Next, and check your settings in the summary.

11. Click on Finish, and save the configuration.

The new JDBC provider is created.


79

12. Click on Resources/JDBC/Data source in the views, select the

entry Cell in the Scope box, and click on New.

13. In the Data source name and JNDI name box, enter the entries

shown in the graphic, and click on Next.


80

14. Select the option Select an existing JDBC provider, select Oracle

JDBC Driver, and click on Next.

15. Enter the URL for the Oracle database server using the following

syntax: jdbc:oracle:thin:@<Servername>:<Port>:<Instance>,

and select the settings shown.

16. Click on Next, and check the settings in the summary. Click on

Finish.

17. You must save the master configuration.


81

18. Click on the link Oracle JDBC Driver DataSource, on Custom

Properties, and on New to create a user with access privileges.

Configure database access on the page Data sources/Oracle JDBC

Driver DataSource/Custom properties.


82

19. Enter user in the Name box and the value ARISBP in the Value

box.

20. Click on OK, and save your changes. You find the new entry at the

end of the list.


83

21. Then, enter a password for the ARISBP user, and click on OK.

22. Save your changes, and test the database connection by clicking on

Test connection on the Data sources page. If you do not receive a

confirmation message, please check the settings and the path to the

file ojdbc5.jar.


84

23. Run the War deployment by clicking on Applications/Enterprise

Applications/Install New Application in the views.

24. Select the Local file system option, click on Browse, and select the

path to the WAR file (businesspublisher.war). You find this file on

the installation media, or you can download it from www.oracle.com.

25. In the Context root box, enter /businesspublisher.


85

26. Click on Next, and on the following pages, select the settings as

shown.


86

27. Click on Browse.


87

28. Enable the option Oracle JDBC Driver Data Source, and click on

Apply.

29. Check your entries, click on Next and then on Finish. The

installation starts. A progress bar is displayed during installation.


88

30. Save the changes when the master installation has been completed

succesfully.

31. Configure the system by defining the Home directory

aris.businesspublisher.home and generic JVM variables.

Depending on the number of users with simultaneous access to the

system, we recommend that you make more memory available to

the server process. If about 100 users have simultaneous access,

allocate 2048 MB.

Please note the selected settings in the illustrations.


89

32. Open the page Application servers/<server>/Process

Definition/Java Virtual Machine


90

33. Enter the value -Xmx2048m in the Generic JVM arguments box,

and click on Custom Properties.


91

34. Click on New, and enter the name aris.businesspublisher.home in

the Name box. Please note the lower-case spelling.

35. In the Value box, enter the path to the directory

businesspublisher.war. You find it in the installation directory of

IBM Websphere Application Server under the directory

Profiles/<name of the profile>/installedApps/<server

name><node>cell.

36. Click on Apply, and save the changes.

The Home directory is defined.


92

37. Enable Name Service by disabling all check boxes on the page

Security/Secure administration, applications, and

infrastructure and by adjusting the settings as shown. To disable,

you first have to enable the Enable administrative security check

box.

You can later use the file dumpNameSpace.bat to check whether

the settings are correct.


39. Click on Java Authentication and Authorization

Service/Application logins/New.

40. Enter the value NativeLogin in the Alias box.



93

42. Open the file <installation

directory>/IBM/WebSphere/AppServer/profiles/<AppSrv01

>/installedApps/<ids-

ID>/businesspublisher.ear/businesspublisher.war/config/bpl

ogin.cfg, and copy the entry marked in the following graphic.

43. Click on Security/Secure administration, applications, and

infrastructure/Java Authentication and Authentication

Service/Application logins.

44. Click on NativeLogin/JAAS login modules/New.

45. Paste the copied entry into the Module class name box.


47. Click on Environment/Naming/CORBA Naming Service Groups.

48. Enable the Select from special subjects option, select all roles for

Everyone, click on Apply, and save the changes.


94

49. Click on Add, enable the Select from special subjects option,

select all roles for All Authenticated, and click on Apply.

50. Save your changes.

51. Run the file <installation

directory>/IBM/WebSphere/AppServer/profiles/<Appsrv01

>/bin/dumpNameSpace.bat.


95

52. Copy the value that is highlighted green to the clipboard.




ID>/businesspublisher.ear/businesspublisher.war/config/we

bappserver.cfg.

54. Customize the file as follows:

a. <bpserviceport value="9100"

b. usenameservice="true"

c. nameserviceprefix="/nodes/<node>/servers/<server

name>"/>

Paste the content of the clipboard here.

d. <bpservicehost value="<fully qualified name> or <IP

address>"/>

e. Ensure that these values are also transferred to the files Oracle

BPA Suite installation directory>\Oracle BPA

Suite<Version>\Server\config\defaultServerSettings.cfg

and userSettings.cfg.


56. Restart the server.

57. Check the settings by starting the file <installation


>/bin/dumpNameSpace.bat. Here, you also find the entry

/nodes/ids-5dke28k3adwNode01/servers/server1, which you

use as nameserviceprefix (see above).


96

If the installation was successful, you also find the marked entries in

the file <installation


>/installedApps/<CellName>/businesspublisher.ear/busines

spublisher.war/config/webappserver.cfg.


<env-entry>


Class</description>



<env-entry-value>


cleDAO</env-entry-

value>

</env-entry>


60. Customize the configuration file <installation



spublisher.war/config/batchserver.cfg. You find more



97




61. Save the changes, and restart IBM Websphere Application Server and

Oracle Business Process Publisher.

The system is now running with IBM WAS 6.1.0.15 in combination with

an Oracle database 10g.

Note









if you are using an MS SQL Server 2005 database.

Prerequisite



your choice.



www.oracle.com.




Procedure


Websphere/Application Server V6.1/Profile/Appsrv01/Start

Server.






98


5. Select the SQL Server entry in the Database type box.

6. In the Provider type box, select the entry WebSphere embedded

ConnectJDBC driver for MS SQL Server.


data source entry.




99

9. Click on Next, and, in the Class path box, enter the path to the files

sqlserver.jar, base.jar, util.jar, and spy.jar.



100






101

13. Enter the names in the Data source name and JNDI name box,

and click on Next.

14. Select the option Select an existing JDBC provider, select SQL



102

15. Enter the database name, server name, and port numbers, and

select the settings shown.


Finish.



103

18. Select the following settings on the page Data

sources/businesspublisherdb:


104

19. Configure database access on the page Data

sources/businesspublisherdb/Custom properties.


105

20. Enter user in the Name box, for example, and the value ARISBP in

the Value box.


end of the list.


106



107

23. To test the database connection, click on Test connection. If you do

not receive a corresponding message, please check the settings.

24. Run the War deployment by clicking on Applications/Install New

Application in the views.


108






109

27. Click on Next, and, on the following pages, select the settings as

shown.


110



111

29. Enable the businesspublisherdb option, and click on Apply.


installation starts.


112


succesfully.






allocate 2048 MB.



113




114




115







name><node>cell.




116





box.









117
















118




52. Run the file <installation


>/bin/dumpNameSpace.bat.

53. Copy the value that is highlighted green to the clipboard.


119





bappserver.cfg.





name>"/>



address>"/>






57. Restart the server.

58. Check the settings by starting the file <installation


>/bin/dumpNameSpace.bat. Here, you also find the entry

/nodes/ids-5dke28k3adwNode01/servers/server1, which you

use as nameserviceprefix (see above).


120

If the installation was successful, you also find the marked entries in

the file <installation



spublisher.war/config/webappserver.cfg.

59.


<env-entry>


Class</description>



<env-entry-



</env-entry>








121




63. Restart IBM Websphere Application Server and Oracle Business

Process Publisher.


an MS SQL Server 2005 database.

Tip




Note







2.6.4 IBM WebSphere Application Server (WAS 6.1.0.15) under RHELx64


Publisher Server in combination with IBM WebSphere Application Server

(WAS 6.1.0.15) and approved databases under RedHat ES 5 x64.


administration console of IBM WebSphere.

Note









122



if you are using an Oracle database 10g.

Prerequisite

Copy the file from the directory installation media/Setups/All

OS/Oracle Business Process Publisher Server/Oracle/IBM

Websphere to a directory of your choice.



www.oracle.com.































123











deleted.

Procedure


Websphere/Application Server

V6.1/Profile/<Appsrv01>/Start Server.






5. Select the Oracle entry in the Database type box.

6. Select the Oracle JDBC Driver entry in the Provider type box.


data source entry.


124




125

9. Click on Next, and enter the path to the ojdbc file in the Class path

box (see Prerequisites). If the value has not been correctly

transferred, correct the path on the page JDBC providers/Oracle

JDBC Driver.





126



13. In the Data source name and JNDI name box, enter the entries

shown in the graphic, and click on Next.


127

14. Select the option Select an existing JDBC provider, select Oracle


15. Enter the URL for the Oracle database server using the following

syntax: jdbc:oracle:thin:@<Servername>:<Port>:<Instance>,

and select the settings shown.


Finish.



128

18. Click on the link Oracle JDBC Driver DataSource, on Custom

Properties, and on New to create a user with access privileges.

Configure database access on the page Data sources/Oracle JDBC

Driver DataSource/Custom properties.


129

19. Enter user in the Name box and the value ARISBP in the Value

box.


end of the list.


130


22. Save your changes, and test the database connection by clicking on

Test connection on the Data sources page. If you do not receive a

confirmation message, please check the settings and the path to the

file ojdbc5.jar.


131

23. Run the War deployment by clicking on Applications/Enterprise

Applications/Install New Application in the views.






132

26. Click on Next, and on the following pages, select the settings as

shown.


133



134

28. Enable the option Oracle JDBC Driver Data Source, and click on

Apply.


installation starts. A progress bar is displayed during installation.


135


succesfully.






allocate 2048 MB.



136




137




138







name><node>cell.




139





box.









140
















141








bappserver.cfg.





142


name>"/>



address>"/>





Save your changes.


<env-entry>


Class</description>



<env-entry-value>


cleDAO</env-entry-

value>

</env-entry>










56. Save the changes, and restart IBM Websphere Application Server and



an Oracle database 10g.


143

Note










Prerequisite



your choice.



www.oracle.com.




Procedure


Websphere/Application Server V6.1/Profile/Appsrv01/Start

Server.






144


5. Select the SQL Server entry in the Database type box.

6. In the Provider type box, select the entry WebSphere embedded

ConnectJDBC driver for MS SQL Server.


data source entry.




145

9. Click on Next, and, in the Class path box, enter the path to the files

sqlserver.jar, base.jar, util.jar, and spy.jar.



146






147

13. Enter the names in the Data source name and JNDI name box,

and click on Next.

14. Select the option Select an existing JDBC provider, select SQL



148

15. Enter the database name, server name, and port numbers, and

select the settings shown.


Finish.



149

18. Select the following settings on the page Data

sources/businesspublisherdb:


150

19. Configure database access on the page Data

sources/businesspublisherdb/Custom properties.


151

20. Enter user in the Name box, for example, and the value ARISBP in

the Value box.


end of the list.


152



153

23. To test the database connection, click on Test connection. If you do

not receive a corresponding message, please check the settings.




154






155


shown.


156



157

29. Enable the businesspublisherdb option, and click on Apply.




158


succesfully.






allocate 2048 MB.



159




160




161







name><node>cell.




162





box.









163
















164








bappserver.cfg.





165


name>"/>



address>"/>







<env-entry>


Class</description>



<env-entry-



</env-entry>










58. Restart IBM Websphere Application Server and Oracle Business

Process Publisher.


an MS SQL Server 2005 database.

Tip






166

Note







2.6.4.3 Deployment of a new WAR file

If you have installed Oracle Business Process Publisher Server in

combination with IBM WebSphere Application Server (WAS 6.1.0.15)

and one of the approved databases under RedHat ES 5 x64, you can

update the system by using the new file businesspublisher.war.

Afterward, you must perform all exports again.

Prerequisite



www.oracle.com.

Procedure

1. Exit Oracle Business Process Publisher Server.

2. Back up the configuration files webappserver.cfg and

batchserver.cfg (<installation

directory>/IBM/WebSphere/AppServer/profiles/<AppSrv01>/installe

dApps/<ids-

ID>/businesspublisher.ear/businesspublisher.war/config/) to a

secure directory located outside this installation directory.


167



uninstall businesspublisher.

4. Ensure that the directory is deleted. The directory structure should

look as follows:

<Installation


dApps/<ids-ID>.








168


shown.


169

9. Click on Browse.




170


succesfully.

12. Move the previously backed up configuration files

webappserver.cfg and batchserver.cfg back into their original

directory (<installation


dApps/<ids-

ID>/businesspublisher.ear/businesspublisher.war/config/).

13. Clear the corresponding database of the Oracle or MS SQL server.

14. Restart <ARIS_Business_Publisher_Server>, and perform the

exports.

2.6.5 Oracle WebLogic Server, version 11g under Windows


Publisher Server in combination with Oracle WebLogic Server version

11g and approved databases.


administration console of Oracle WebLogic Server 11g.

Note








171

2.6.5.1 Step-by-step instructions (Oracle database)_WebLogic11g

This procedure describes the adjustments to an Oracle WebLogic Server

11g (en) if you are using an Oracle database 11g.

Prerequisite

Copy the file ojdbc5.jar (installation media/Setups/All

OS/Oracle Business Process Publisher Server) to a directory of

your choice.



www.oracle.com.


























password. If you prefer another name, change the name there as

well:


172












deleted.

Procedure

1. After installation, open the administration console of WebLogic

Server in your browser at http://<server

name>:<port>/console.

The port number depends on your current configuration. The Login

dialog box is displayed.


173

2. Log in to Oracle WebLogic Server. An overview page is displayed.

3. Select the Deployment node in the navigation bar on the left.

4. Select the file businesspublisher.war from your hard drive, and

upload it.


174

5. Define how the war file is to be installed. Select Install this

deployment as an application.

6. Select an existing cluster on which the application will be available.


175

7. Select the general application properties and a security model. Define

businesspublisher as the default application name.

8. Specify access to the source. Select Copy this application onto

every target for me. This means that the source is available via file

access and is not saved in a database.


176

9. Select Yes, take me to the deployment's configuration screen

to test the configuration.


177

10. Test the configuration.


178

11. Configure the data source. Select the Services/JDBC/Data

Sources node in the navigation on the left. Click on New.

12. Define the database type and the JNDI address to be used by Oracle

Business Process Publisher. Define jdbc/businesspublisherdb as

the JNDI name.


179

13. Select the database type and the associated database driver.

14. Configure Supports Global Transactions and One-Phase

Commit.


180

15. Define the database name (instance name), the host on which the

database server runs, the port, the user name, and the password to

be used to log in to the database.


181

16. Test the database connection.

17. Specify the cluster on which the new data source is available.


182

18. Display a summary of the data sources.

19. Adjust the settings for the Java Virtual Machine. To do this, open the

file setDomainEnf.cmd in the directory

%beahome%\user_projects\domains\%YourDomain%\bin.

20. Add the following configuration entries for Oracle Business Process

Publisher Server at the end of the file to extend the JVM options of

the J2EE server.

Define the root directory of the Web application for the

aris.businesspublisher.home option:

set BP_INSTALL=AdminServer/tmp/_WL_user/businesspublisher/1xhsau/war set JAVA_OPTIONS=%JAVA_OPTIONS% -Daris.businesspublisher.home=%DOMAIN_HOME%/servers/%BP_INSTALL%

21. Set the correct Corba server for Oracle Business Process Publisher.

You must specify the library to be used by the server. Ensure that

each Web application server uses its specific Corba library. Java has

a mechanism that can be used to define external libraries:

set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.endorsed.dirs=%DOMAIN_HOME%/servers/%BP_INSTALL%/WEB-INF/lib/endorsed


183

This directory must contain a copy of the file orbacus.4.3.2.jar. You

find this file in directory WEB-INF/lib/endorsed of Oracle Business

Process Publisher.

22. Specify the Java variable java.security.auth.login.config, which

must point to a configuration file in which the login modules are

defined. The configuration file bplogin.cfg for Oracle Business

Process Publisher is located in the configuration directory of the

application:

set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.security.auth.login.config=%DOMAIN_HOME%/servers/%BP_INSTALL%/config/bplogin.cfg

23. Allocate memory to the server process, assuming that 1024 MB are

required for every 100 simultaneous users. Make the setting you

want in file setDomainEnf.cmd.

24. Open file webappserver.cfg in the directory

%BP_INSTALL%\config\webappserver.cfg.

25. Search for the string bpservicehost, and set the value for the IP

address to a fully qualified computer name (e.g. <bpservicehost

value="172.30.252.3"/>).

2.6.5.2 Step-by-step instructions (MS SQL Server 2005 database)_WebLogic



Prerequisite



your choice.



www.oracle.com.





184

Procedure

1. After installation, open the administration console of WebLogic

Server in your browser at http://<server

name>:<port>/console.

The port number depends on your current configuration. The Login

dialog box is displayed.

2. Log in to Oracle WebLogic Server. An overview page is displayed.


185

3. Select the Deployment node in the navigation bar on the left.

4. Select the file businesspublisher.war from your hard drive, and

upload it.

5. Define how the war file is to be installed. Select Install this

deployment as an application.


186

6. Select an existing cluster on which the application will be available.

7. Select the general application properties and a security model. Define

businesspublisher as the default application name.


187

8. Specify access to the source. Select Copy this application onto

every target for me. This means that the source is available via file

access and is not saved in a database.

9. Select Yes, take me to the deployment's configuration screen

to test the configuration.


188

10. Test the configuration.


189

11. Configure the data source. Select the Services/JDBC/Data

Sources node in the navigation on the left. Click on New.

12. Define the database type and the JNDI address to be used by Oracle

Business Process Publisher. Define jdbc/businesspublisherdb as

the JNDI name.


190

13. Select the database type and the associated database driver.

14. Configure Supports Global Transactions and One-Phase

Commit.


191

15. Define the database name (instance name), the host on which the

database server runs, the port, the user name, and the password to

be used to log in to the database.


192

16. Test the database connection.

17. Specify the cluster on which the new data source is available.


193

18. Display a summary of the data sources.

19. Adjust the settings for the Java Virtual Machine. To do this, open the

file setDomainEnf.cmd in the directory

%beahome%\user_projects\domains\%YourDomain%\bin.

20. Add the following configuration entries for Oracle Business Process

Publisher Server at the end of the file to extend the JVM options of

the J2EE server.

Define the root directory of the Web application for the

aris.businesspublisher.home option:

set BP_INSTALL=AdminServer/tmp/_WL_user/businesspublisher/1xhsau/war set JAVA_OPTIONS=%JAVA_OPTIONS% -Daris.businesspublisher.home=%DOMAIN_HOME%/servers/%BP_INSTALL%

21. Set the correct Corba server for Oracle Business Process Publisher.

You must specify the library to be used by the server. Ensure that

each Web application server uses its specific Corba library. Java has

a mechanism that can be used to define external libraries:

set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.endorsed.dirs=%DOMAIN_HOME%/servers/%BP_INSTALL%/WEB-INF/lib/endorsed


194

This directory must contain a copy of the file orbacus.4.3.2.jar. You

find this file in directory WEB-INF/lib/endorsed of Oracle Business

Process Publisher.

22. Specify the Java variable java.security.auth.login.config, which

must point to a configuration file in which the login modules are

defined. The configuration file bplogin.cfg for Oracle Business

Process Publisher is located in the configuration directory of the

application:

set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.security.auth.login.config=%DOMAIN_HOME%/servers/%BP_INSTALL%/config/bplogin.cfg

23. Allocate memory to the server process, assuming that 1024 MB are

required for every 100 simultaneous users. Make the setting you

want in file setDomainEnf.cmd.

24. Open file webappserver.cfg in the directory

%BP_INSTALL%\config\webappserver.cfg.

25. Search for the string bpservicehost, and set the value for the IP

address to a fully qualified computer name (e.g. <bpservicehost

value="172.30.252.3"/>).

2.6.6 Oracle Business Process Publisher Report Server installations

This chapter describes the Oracle Business Process Publisher Report

Server installations for the approved Web Application Servers.



(Page 194) to optimize system performance when running reports.

After you install Oracle Business Process Publisher Report Server,

exports are managed by Oracle Business Process Publisher Server and

reports are run by Oracle Business Process Publisher Report Server.

To be able to work with Oracle Business Process Publisher Report

Server, the same database and database server must be used as for the

Oracle Business Process Publisher Server installation.

Note

If you do not install the server with the setup program, you must adjust

the configuration file batchserver.cfg.


195

2.6.6.1 Apache Tomcat Web Application Server under Windows


Server under Microsoft Windows.

Note







2.6.6.1.1 Step-by-step instructions (standard database)

This procedure describes the standard installation of Apache Tomcat

Web Application Server if you are using a Derby database. With this

database system, up to 10 users can access exports simultaneously. For

a larger number of users, you need the Oracle (Page 288) database

system or MS SQL Server 2005. Depending on the Oracle Business

Process Publisher Server license purchased, these systems enable all

users to simultaneously work on exports.

Procedure






program.












196



on Next.

Note








Suite is created.



on Next.

8. Select the option Oracle Business Process Publisher Report

Server. The page Oracle Business Process Publisher Server

opens.

9. Enter the computer name or IP address of the computer on which

Oracle Business Process Publisher Server is installed.

10. Enable the Standard Database System check box if you want to

use the standard database.




program closes.

13. If you want to use another database instead of the Derby database,

ensure that the appropriate database is installed and adjust the

database management system for use with Oracle Business Process

Publisher Server (Page 233).

14. Communicate the URL (<root directory of Oracle Business

Process Publisher Server>/<context>) that allows users to

access every Publisher export and administrators to manage exports.

After the standard installation of Oracle Business Process Publisher

Server, the URL is http://<server

name>:9090/businesspublisher if you did not change the default

settings during installation.


197

15. If you have installed Oracle Business Process Publisher Server on an

external computer, change the IP address in the configuration file.

To create a Publisher export and enable users to work with it, you must

start Oracle Business Process Publisher Server and communicate the

URL. After the standard installation of Oracle Business Process Publisher

Server, the URL is http://<server name>:9090/businesspublisher

if you did not change the default settings during installation.

2.6.6.1.2 Step-by-step instructions (Oracle database configured)_tomcat






Prerequisite
























198


















deleted.

Procedure




editor.



Files\Oracle BPA






initialSize="10"


199












</Context>




a text editor.








<env-entry>


Class</description>



<env-entry-value>



value>

</env-entry>



200





Note







Install Oracle Business Process Publisher Report Server

Procedure






program.













on Next.

Note





201





Suite is created.



on Next.



opens.


Oracle Business Process Publisher Server is installed. Click on Next.






on Next.




program closes.

2.6.6.1.3 Step-by-step instructions (existing Oracle database)_tomcat






Prerequisite







202



































deleted.


203

Procedure




editor.



Files\Oracle BPA






initialSize="10"












</Context>




a text editor.








204



<env-entry>


Class</description>



<env-entry-value>



value>

</env-entry>





Note








Procedure






program.




205











on Next.

Note








Suite is created.



on Next.



opens.






computer. Click on Next.





Instance opens.


206





on Next.


box. Click on Next.




program closes.

2.6.6.1.4 Step-by-step instructions (new Oracle database)_tomcat






Prerequisite





















207





















deleted.

Procedure




editor.



Files\Oracle BPA






initialSize="10"




208










</Context>




a text editor.








<env-entry>


Class</description>



<env-entry-value>



value>

</env-entry>







209

Note








Procedure






program.













on Next.

Note








Suite is created.


210



on Next.



opens.






The Create New Oracle Database Instance dialog box opens.














is the default.

12. Click on Next.





on Next.




program closes.


211

2.6.6.1.5 Step-by-step instructions (MS SQL Server 2005 database)



use the MS SQL Server 2005 database, all users covered by the license

can simultaneously work with a Publisher export, which is not possible

with the standard database.

Prerequisite





Procedure











webappserver.cfg.


COLLATE statement.










212






follows:





following entry:



=MSSQLSRV.




er.cfg.





them here.


<env-entry>


Class</description>



<env-entry-



</env-entry>

Tip






213

Note








Procedure






program.








products are installed is used. The Select program folder page

opens.





Suite is created.



on Next.



opens.




214

10. To use an MS SQL Server, enable the MS SQL Server check box.





on Next.




program closes.

2.7 Acrobat Reader

Here, you install the viewer for displaying PDF documents such as the

Methods Manual.

Procedure

1. If the start page is not displayed automatically, click on the name of


program.


3. Click on Acrobat Reader <Version>.


The page Default application for viewing PDF opens.

5. Enable the option button for the required viewer version, and click on

Next.

6. To use the suggested installation directory, click on Next and

continue with the next step. Note that the name of the installation

directory must not contain any country-specific special characters.

To install the program in a different directory than the one

suggested, click on Browse. Enter the desired path in the Path box

or navigate to the desired directory in the Directories box. Click on

OK. Click on Next.

7. Click on Install.


215

2.8 Java Runtime Environment

To use Oracle BPA Suite via a browser, install SUN Java Runtime

Environment (JRE) if you have not yet done so. This section describes

the standard installation process. To perform a different installation,

enable the Adapted option button during JRE installation.

Procedure

1. If the start page is not displayed automatically, click on the name of


program.

2. Click on Java Runtime Environment to start the JRE setup.

3. Once you have read the license agreements and accept them, enable

the relevant check box and click on Next.

4. Enable the Default option and click on Next.

5. The installation is performed and a message is displayed when it is

complete. Click on Finish to exit the JRE installation program.

Note

Install JRE in a path whose directory name does not include any spaces.

Otherwise, JRE cannot be executed.

If you are using software systems that install their own JRE: Please

make sure that in the environment variables the path of the SUN JRE is

entered before the ones of software systems having their own JRE.

Otherwise, it may not be possible to run Oracle Business Process

Architect via a browser.


216

2.9 System add-ons

This chapter describes the installation of system add-ons.

2.9.1 Oracle BPA Suite Process Generator

Oracle Process Generator enables you to transfer objects and models to

Excel, to edit them there, and to return them to Oracle BPA Suite again.

In addition, you can easily define new objects or process models of the

EPC type in an Excel table and transfer them to Oracle BPA Suite

databases.

In this way, even without Oracle BPA Suite installed, you can define

processes and transfer them to an Oracle BPA Suite database later. After

having transferred the new models you can prepare them graphically by

means of automatic layout generation. In addition, you can quickly enter

large quantities of data using object tables. Thus, attributes are entered

and edited independently of an installed Oracle BPA Suite.

For further information please refer to the online help.


217

2.10 Additional installation information and principles

This chapter provides installation information and basics.

2.10.1 Oracle BPA Suite - System architecture

Oracle BPA Suite has the following components:


Oracle Business Process Publisher Server

Database server (standard database system or other database

system)

Oracle BPA Suite client products

Oracle Business Process Repository Site Manager (includes HTML

Generator and Oracle BPA Suite Web Report Server)

Web server (Oracle BPA Suite Web Client Components)

2.10.2 Oracle Business Process Architect installations

Oracle Business Process Architect installations (option Oracle BPA

Suite WITH LOCAL STANDARD DATABASE SYSTEM) are suitable for

users who only work with local databases or who want to access local

databases and databases on the network.

The standard database system is also installed with this installation. This

allows you to create databases on your computer and work with them

without other users being able to access them. You can also connect to

an Oracle Business Process Repository to create databases there and

work with them.

2.10.3 Oracle Business Process Repository - Exit a service

Prerequisite

Ensure on your computer that you have the privilege to exit Windows

services that have been started.

Procedure

1. Open the Windows Start menu, and select Settings/Control Panel.

The Control Panel of your operating system opens.

2. Open the list item Management.


218

3. Then open the list item Services.

4. In the Status column, check whether the service Oracle BPA Suite

Server 11g has been started.

5. If so, right-click on the service Oracle BPA Suite Server 7.1 and

select Exit.

The service Oracle BPA Suite Server 11g is now exited.

2.10.4 Automatic backup

When you perform an update, make changes to a program, add

languages, or uninstall a component, the relevant files and directories

are backed up. A selection of files is listed here to provide examples:

In a client installation in directory <Oracle BPA Suite installation directory>\backup<date>: Files from <Oracle BPA Suite installation

directory>\LocalServer\data (user databases, when uninstalling)

Directory <Oracle BPA Suite installation

directory>\LocalServer\sysconfig

Directory <Oracle BPA Suite installation directory>\html

Directory <Oracle BPA Suite installation directory>\script

In a server installation in directory <Oracle BPA Suite installation directory>\server\backup

Files from <Oracle BPA Suite installation

directory>\server\data (user databases, when uninstalling)


directory>\server\sysconfig


directory>\server\templates


219

2.10.5 Particular issues - Oracle BPA Suite client and Oracle Business Process Repository on the same computer

Oracle BPA Suite clients and Oracle Business Process Repository use

shared components that can only be installed once per computer.

Therefore, you have to consider these particular issues when an Oracle

BPA Suite client and Oracle Business Process Repository are installed on

the same computer.

If you make any changes to the Oracle BPA Suite client or Oracle

Business Process Repository, you need to ensure that both have the

same version and are installed with the same languages after the

changes:

Therefore, when you perform a version update, you need to ensure

that both Oracle Business Process Repository and the Oracle BPA

Suite client are included.

When you install additional languages, you need to install them for

both Oracle Business Process Repository and the Oracle BPA Suite

client.

2.10.5.1 Installation

The Oracle BPA Suite client is already installed on the computer.

If you install Oracle Business Process Repository afterward, its

installation directory will automatically be inserted into the directory

structure (<Oracle BPA Suite installation directory>\server). In this

case, there is no need for you to add the installation directory for Oracle

Business Process Repository. During the installation of Oracle Business

Process Repository, you must select the same languages as for the

previous installation of the Oracle BPA Suite client.

To find out which languages have been installed for Oracle BPA Suite,

run the Oracle BPA Suite setup again and select the Modify Program

option. Installed languages are enabled on the Select Language page

of the Oracle BPA Suite setup. Once you have determined which

languages are installed, click on Cancel.


220

Oracle Business Process Repository is already installed on the computer.

If you then install the Oracle BPA Suite client, its files and directories are

automatically integrated into the Oracle Business Process Repository

directory structure. In this case, there is no need for you to add the

installation directory for the Oracle BPA Suite client.

During the installation of the Oracle BPA Suite client, you must select

the same languages as for the previous installation of Oracle Business

Process Repository.

To find out which languages have been installed for Oracle Business

Process Repository, run the Oracle Business Process Repository setup

again and select the Modify program option. Installed languages are

enabled on the Select Language page of the Oracle Business Process

Repository setup. Once you have determined which languages are

installed, click on Cancel.

2.10.5.2 Uninstall

You can uninstall Oracle Business Process Repository and Oracle BPA

Suite clients individually without affecting the operability of the

remaining component. The order in which they were installed is

irrelevant.

Under Windows, you uninstall programs using the Setup or from

Start/Control Panel/Software.

Under Unix/Linux, you uninstall Oracle Business Process Repository

(Page 43) or Oracle BPA Suite clients by deleting the relevant directories

in the installation directory.


221

3 Administration

3.1 Database management systems

This chapter describes how to set up and manage databases on different

database management systems.

3.1.1 Oracle Business Process Repository

3.1.1.1 Oracle database management system for Oracle Business Process Repository

If you wish to run Oracle Business Process Repository based on Oracle

as the database management system, please read the following pages.

To set up your database server, we recommend that you make use of

the Oracle Corporation installation support. Please read the information

about Oracle Business Process Repository and database approvals.

Note







3.1.1.1.1 Set up the database

We assume use of database character set AL32UTF8. The block size

should be 8K.

Procedure

Create two permanent tablespaces ARISDATA and ARISINDEX for the

indices.

You can also assign other names for the two tablespaces. In this case,

you must later adapt the configuration.

Note

A relatively small Oracle BPA Suite database occupies on the order of

100 MB per tablespace. The size required for the tablespaces ultimately

depends on the anticipated number of Oracle BPA Suite databases and


222

their size. Since this is difficult to predict, it is best to start with 4 GB per

tablespace and keep an eye on the trend toward exhausting that

capacity.

3.1.1.1.1.1 Install Oracle BPA Suite database objects

To install the database objects that are required to operate Oracle BPA

Suite, you can use the scripts available on the Oracle BPA Suite

installation media in the Setups\DBMS\Oracle directory. Since the

scripts rely on SQL*PLUS, at least the Oracle client software must be

available on the computer on which you intend to run the scripts.

The scripts create the two Oracle users arisadm71 and ARIS71:

arisadm71

This user is only used as a schema for the database objects required by

BPA. Oracle Business Process Repository never connects to this user. For

this reason, it does not require a CREATE SESSION privilege. The

privileges assigned to this user are:

CREATE TABLE

CREATE VIEW

CREATE TRIGGER

ARIS71

This is the user that Oracle Business Process Repository uses to access

the data in the schema arisadm71. The user ARIS71 itself does not have

any database objects. It solely has object privileges for the database

objects in the schema arisadm71. The system privilege assigned to the

user ARIS71 is CREATE SESSION.

3.1.1.1.1.2 Use SQL*Plus scripts

The scripts install the database objects required for operating Oracle

BPA Suite in an existing Oracle database. Since the scripts rely on

SQL*PLUS, at least the Oracle client software must be available on the

computer on which you intend to run the scripts.

Alternatively, you can have the server setup program create the

database objects.


223

3.1.1.1.1.2.1 Available SQL*Plus scripts

Once the Oracle database is created, the scripts for importing the

database objects required for operating Oracle BPA Suite can be run.

The following scripts are available:

install.bat

Windows batch files for running SQL*Plus scripts

envset.bat

Batch files for adjusting settings The file envset.bat is called by the file

install.bat.

Before you run scripts by calling them from install.bat (or install.sh),

you must adjust configurations in the file envset.bat (or envset.sh).

install.sh

Bash script for running SQL*Plus scripts To run this script under Unix,

you need the bash as Shell.

envset.sh

Bash script for adjusting settings The file envset.sh is called by the file

install.sh. To run this script under Unix, you need the bash as Shell.

adminc.sql

SQL*Plus script for creating the user arisadm71

appuserc.sql

SQL*Plus script for creating the connection user ARIS71

schema_aris.sql

SQL*PLUS script for creating a procedure that produces a spreadsheet

set for an Oracle BPA Suite database

basemgr.sql

Procedures for managing Oracle BPA Suite databases.

deinstall.sql

SQL*PLUS script for removing the users arisadm71 and ARIS71.


224

3.1.1.1.1.2.2 Run batch files install.bat/install.sh

If you have adjusted configurations (Page 224) in the envset.bat file

(or envset.sh), you can call the batch file install.bat (or install.sh).

3.1.1.1.1.3 Configure the installation scripts

Before you run the scripts, you must adjust them to your environment.

Adjustments can be made in the file envset.bat or envset.sh, which

you find on the installation media under Setups\DBMS\Oracle.

3.1.1.1.1.3.1 Connection data

You can change connection data. To do this, edit the files envset.bat and

envset.sh, which you find on the installation media under

Setups\DBMS\Oracle. First copy these files to the hard drive of the

computer on which they will be run.

Procedure

1. Open the file envset.bat or envset.sh with a text editor.

2. Find the line SET DL_ORA_BIN_PATH=, and specify the path to

the directory where the Oracle binaries reside. If this path is already

in the system path, you can leave the value empty.

3. In the line SET TARGET_HOST=localhost, enter the host name (or

IP address) on which the Oracle instance is running.

4. Enter the port in the line SET TARGET_PORT=1521.

5. In the line SET TARGET_SERVICE_NAME=BPA, enter the service

name (or Oracle SID).

6. In the line SET INSTALL_USER=system, enter an Oracle user who

has a DBA role, for example the Oracle user SYSTEM. Provide it with

a password in the line SET INSTALL_PWD=manager.

3.1.1.1.1.3.2 Change tablespace names

If you have assigned other names to the tablespaces (Page 221), the

envset.bat and envset.sh file must be adjusted. You find this on the

installation media under Setups\DBMS\Oracle. First copy these files

to the hard drive of the computer on which they will be run.


225

Procedure


2. Find the line SET DL_TS_DATA=ARISDATA, and replace the

tablespace name ARISDATA with the one you selected.

3. Find the line SET DL_TS_INDEX=ARISINDEX, and replace the

tablespace name ARISINDEX with the one you selected.

You can specify another temporary tablespace in the line SET

DL_TS_TEMP=TEMP if needed.

3.1.1.1.1.3.3 Change the password for Oracle user ARIS71

Change the password for the Oracle user ARIS71. The default password

for this user is *ARIS!1dm9n#. You can also change the password

later at any time using the Oracle BPA Suite function DBMS password.

To prevent misuse, you should change it immediately. To select another

password for the Oracle user ARIS71 in advance, edit the envset.bat

and envset.sh file before the scripts are used.

Procedure


2. Find the line SET DLAPP_PWD=*ARIS!1dm9n#, and change the

password.

3. For Oracle Business Process Repository to use the new password, you

must specify it in the file Lockservice.cfg in the config directory of

Oracle Business Process Repository Site Manager.

4. Open the file Lockservice.cfg in the config directory of Oracle

Business Process Repository Site Manager with a text editor.

5. Find the line arisadm_pwd_=*ARIS!1dm9n#, and change the

password.

Note

The password is specified in plain text in the file Lockservice.cfg, but

immediately after Oracle Business Process Repository starts for the first

time, it encrypts the password in the file Lockservice.cfg. The key

arisadm_pwd_ with final underscore identifies the password as a plain

text password, while the key arisadm_pwd without a final underscore

identifies the encrypted password. After Oracle Business Process

Repository starts, the arisadm_pwd_ variant is converted into the

arisadm_pwd variant.


226

3.1.1.1.1.3.4 Change the password for Oracle user arisadm71

The user arisadm71 solely serves as a schema for data required by

Oracle BPA Suite. Oracle Business Process Repository only connects to

the Oracle user ARIS71. The latter has privileges for the schema

arisadm71.

Since Oracle Business Process Repository does not connect directly to

the Oracle user arisadm71, this user does not need a working

password. The scripts give user arisadm71 an impossible password.

3.1.1.1.1.3.5 Change user names

Instead of ARIS71 and arisadm71, you can select other names for the

required Oracle users. This can be useful, for example, if you want to

use the same Oracle database for several installations of Oracle Business

Process Repository. In this case, please select different user names for

each installation.

Procedure


2. Find the line SET DLADM_SCHEMA=arisadm71, and replace the

default value in this line with the user name you want.

3. Find the line SET DLAPP_USER=ARIS71, and replace the default

value in this line with the user name you want.

4. For Oracle Business Process Repository to use the new user names,

you must specify this in the file Lockservice.cfg in the config

directory of Oracle Business Process Repository Site Manager.



6. Find the lines arisadm_schema=BPAadm11 and

arisadm_user=bpa11, and change them to match the user names

you have selected.

3.1.1.1.2 Configure Oracle Business Process Repository URL

For Oracle Business Process Repository to connect to your Oracle

instance, you must specify the URL in the file Lockservice.cfg in the

config directory of Oracle Business Process Repository Site Manager.


227

Procedure



2. Find the line url=jdbc:oracle:thin:@host:1521:ARIS, and replace

host with your computer name, 1521 with your port, and BPA with

the name of your instance.

3.1.1.2 MS SQL database management system for Oracle Business Process Repository

If you wish to run (Page 27) Oracle Business Process Repository based

on Microsoft SQL (MS SQL) as the database management system, please

read the following pages.




Note







3.1.1.2.1 Required programs, drivers, and scripts

To use Oracle BPA Suite with an SQL Server on a 32-bit Windows

platform, you need the following components:

Microsoft SQL Server for installing the SQL Server on a Microsoft

Server

If you want to use this server, you need to purchase it from

Microsoft.

Oracle BPA Suite SQL Server scripts

The scripts are located on the Oracle BPA Suite installation CD in the

Setups\DBMS\MSSQL directory.


228

3.1.1.2.2 Notes on installing SQL Server

Server sorting must be case-insensitive. That is, the sorting name

must contain the character sequence _CI_. Select the server sorting

Latin1_General_CI_AI for example.

Select the option SQL Server and Windows authentication mode

as server authentication.

Set the option Enable triggers to generate additional triggers to

TRUE.

Set the timeout value for remote queries to 0.

3.1.1.2.3 Set up the database

To install the database with the database objects that are required to

operate Oracle BPA Suite, you can use the scripts available on the

installation media in the Setups\DBMS\MSSQL directory.

The scripts create a database ARIS71 and a login ARIS71.

The scripts consist of the following files:

inst.bat: Windows batch file for running scripts

deinstall.sql: SQL script for deleting database objects from the

ARIS71 database and the ARIS71 login

drop_db.sql: Deletes the ARIS71 database.

createdb.sql: SQL script for creating the ARIS71 database

install.sql: SQL script for creating the ARIS71 login and the

database objects in the ARIS71 database

schema_aris.sql: SQL script for creating a procedure that produces

a spreadsheet set for an Oracle BPA Suite database

schema_bo.sql: SQL script for creating a procedure that produces a

spreadsheet set for a BO database.

Before you run the scripts by calling inst.bat, you must configure the

inst.bat file.


229

3.1.1.2.3.1 Configure the installation scripts

Procedure

1. Edit the inst.bat file, and find the line

SET MSSQL_IDS_MSSQL_LOGIN_NAME=localhost\username

2. Replace the expression localhost\username with a user name that

has administrative access to the database server. This user serves to

run the SQL scripts.

3. Find the line

SET MSSQL_IDS_FILEGROUP_FILE_DIR=C:\msqldata\ARIS71

and specify the path in which the database files are to be created for

the database. Ensure that the directory exists.

3.1.1.2.3.1.1 Change the name of the database

You can select another name for the database instead of ARIS71. To do

this, you must edit the inst.bat file. You find this on the installation

media under Setups\DBMS\MSSQL. First copy these files to the hard

drive of the computer on which they will be run.

Procedure

1. Open the file inst.bat with a text editor.

2. Find the line SET MSSQL_IDS_DATABASE_NAME=ARIS71, and

change the name of the database.

3. Adjust (Page 231) the URL in the Lockservice.cfg file of Oracle


3.1.1.2.3.1.2 Change the password for the login user ARIS71

The default password for the login user ARIS71 is *ARIS!1dm9n#. You

can change the password later at any time using the Oracle BPA Suite

function DBMS password. To prevent misuse, you should change it

immediately. To select another password for the login user ARIS71 in

advance, edit the inst.bat file before the scripts are used.

Procedure



230

2. Find the line SET MSSQL_IDS_APP_PWD=*ARIS!1dm9n#, and

change the password.

For Oracle Business Process Repository to use the new password, you

must specify it in the file Lockservice.cfg in the config directory of

Oracle Business Process Repository Site Manager.



4. Find the line arisadm_pwd_=*ARIS!1dm9n#, and change it as

needed.

Note

The password is specified in plain text in the file Lockservice.cfg, but

immediately after Oracle Business Process Repository starts for the first

time, it encrypts the password in the file Lockservice.cfg. The key

arisadm_pwd_ with final underscore identifies the password as a plain

text password, while the key arisadm_pwd without a final underscore

identifies the encrypted password. After Oracle Business Process

Repository starts, the arisadm_pwd_ variant is converted into the

arisadm_pwd variant.

3.1.1.2.3.1.3 Change the user name ARIS71

You can select another name for required SQL Server users instead of

ARIS71.

Procedure


2. Find the line SET MS SQL_IDS_APP_USER=ARIS71, and replace

the default value in this line with the user name you want.

3. For Oracle Business Process Repository to use the new user names,

you must specify these in the file Lockservice.cfg in the config

directory of Oracle Business Process Repository Site Manager.



5. Find the line arisadm_user=ARIS71, and change it to match the

user names you have selected.


231

3.1.1.2.3.2 Configure Oracle Business Process Repository URL

For Oracle Business Process Repository to connect to your MS SQL

instance, you must specify the URL in the file Lockservice.cfg in the

config directory of Oracle Business Process Repository Site Manager.

Procedure



2. Find the line

url=jdbc:jtds:sqlserver://host:1433/ARIS71;instance=MSSQL

SERVER, and replace host with the computer name and ARIS71

with the name of the database (if you selected another database

name when you modified the scripts). If you are using a named

database instance, replace MSSQLSERVER with the name of your

instance.

Note

Sometimes the name MSSQLSERVER does not work, although you are

using a default instance. In this case, remove the expression

;instance=MSSQLSERVER at the end of the URL.

3.1.1.3 IBM DB2 database management system for Oracle Business Process Repository

If you wish to run (Page 28) Oracle Business Process Repository based

on DB2 as the database management system, please read this page.




Note








232

Procedure

1. Create an operating system user with the name db2aris on the DB2

host computer. Oracle Business Process Repository uses a free DB2

database user to connect to the DB2 database.

2. Assign this user to the DB2USERS user group.

3. Enter the password *ARIS!1dm9n# for this user.

To create the DB2 database, you can use the following script after

you have adapted the paths (UTF-8 is absolutely necessary). The

script is located on the Oracle BPA Suite installation media in the

directory Setups\DBMS\DB2.

CREATE DATABASE ARIS AUTOMATIC STORAGE YES ON 'E:\db2data' DBPATH ON 'E:\' USING CODESET UTF-8 TERRITORY EN; UPDATE DB CFG FOR ARIS USING AUTO_MAINT ON; UPDATE DB CFG FOR ARIS USING AUTO_TBL_MAINT ON; UPDATE DB CFG FOR ARIS USING AUTO_RUNSTATS ON; UPDATE ALERT CFG FOR DATABASE ON ARIS USING db.db_backup_req SET THRESHOLDSCHECKED YES; UPDATE ALERT CFG FOR DATABASE ON ARIS USING db.tb_reorg_req SET THRESHOLDSCHECKED YES; UPDATE ALERT CFG FOR DATABASE ON ARIS USING db.tb_runstats_req SET THRESHOLDSCHECKED YES; CONNECT TO ARIS; CREATE BUFFERPOOL ARISBP IMMEDIATE SIZE 20000 AUTOMATIC PAGESIZE 8 K; CREATE REGULAR TABLESPACE ARISDATA PAGESIZE 8 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 8 OVERHEAD 12.67 PREFETCHSIZE 8 TRANSFERRATE 0.18 BUFFERPOOL ARISBP DROPPED TABLE RECOVERY OFF; CREATE REGULAR TABLESPACE ARISINDEX PAGESIZE 8 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 8 OVERHEAD 12.67 PREFETCHSIZE 8 TRANSFERRATE 0.18 BUFFERPOOL ARISBP DROPPED TABLE RECOVERY OFF; CREATE LARGE TABLESPACE ARISLOB PAGESIZE 4 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 8 OVERHEAD 12.67 PREFETCHSIZE 8 TRANSFERRATE 0.18 BUFFERPOOL IBMDEFAULTBP; CREATE SYSTEM TEMPORARY TABLESPACE ARISTEMP PAGESIZE 8 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 8 OVERHEAD 12.67 PREFETCHSIZE 8 TRANSFERRATE 0.18 BUFFERPOOL ARISBP; UPDATE DATABASE CONFIGURATION USING LOGSECOND 40 IMMEDIATE; UPDATE DATABASE CONFIGURATION USING LOGFILSIZ 5000 DEFERRED; GRANT CONNECT ON DATABASE TO USER db2aris; GRANT CREATETAB ON DATABASE TO USER db2aris; GRANT USE OF TABLESPACE ARISDATA TO USER db2aris; GRANT USE OF TABLESPACE ARISINDEX TO USER db2aris; GRANT USE OF TABLESPACE ARISLOB TO USER db2aris;


233

CREATE SCHEMA db2aris AUTHORIZATION db2aris; CONNECT RESET;

Note

The default password for this user is *ARIS!1dm9n#. To prevent

misuse, you should change it immediately.

To use a different database name, user name, or password, you have to

change these entries in the configuration file Lockservice.cfg

(...installation directory/server/config).

To change the entries, replace the following values:

arisadm_user=db2aris

arisadm_schema=db2aris

url=jdbc:db2://myhost:50000/ARIS

arisadm_pwd_=*ARIS!1dm9n#

You can only change the password here. The DBMS password cannot be

changed in the program interface.

Once you have defined the password and started Oracle Business

Process Repository, the password entered in the file is automatically

encrypted to prevent misuse. The key is also renamed from

arisadm_pwd_ (unencrypted) to arisadm_pwd (encrypted).

If you wish to change the password afterward, you first have to rename

the arisadm_pwd key to arisadm_pwd_ again and enter the new

password directly after =. The password is automatically encrypted after

restart.

3.1.2 Oracle Business Process Publisher Server

Please read this section if you performed the standard installation of

Oracle Business Process Publisher Server and want to use an Oracle or

MS SQL database instead of the Derby database. For additional

information, see chapter Oracle Business Process Publisher (Page

44).

Notes

If you install databases yourself, always follow the instructions provided

by their respective manufacturers.


234

3.1.2.1 Manage a system with an MS SQL database



use the MS SQL Server 2005 database, all users provided with a license

key can simultaneously work with a Publisher export, which is not

possible with the Derby database.

Prerequisite





Procedure











webappserver.cfg.


COLLATE statement.










235






follows:





following entry:



=MSSQLSRV.




er.cfg.





them here.


<env-entry>


Class</description>



<env-entry-



</env-entry>

Tip






236

Note







Sample script create_db.sql USE master GO CREATE DATABASE [ARISBP11] ON PRIMARY (NAME = N'ARISBPPRIM', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPPRIM.mdf' , SIZE = 10MB , FILEGROWTH = 10MB), FILEGROUP [ARISBPDATA] (NAME = N'ARISBPDATA', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPDATA.ndf' , SIZE = 100MB , FILEGROWTH = 100MB), FILEGROUP [ARISBPINDEX] (NAME = N'ARISBPINDEX', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPINDEX.ndf' , SIZE = 100MB , FILEGROWTH = 100MB) LOG ON (NAME = N'ARISBPLOG', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPLOG.ldf' , SIZE = 10MB , FILEGROWTH = 10MB) COLLATE Latin1_General_CI_AI GO EXEC dbo.sp_dbcmptlevel @dbname=N'ARISBP11', @new_cmptlevel=90 GO BEGIN TRY EXEC [ARISBP11].[dbo].[sp_fulltext_database] @action = 'disable' END TRY BEGIN CATCH END CATCH GO ALTER DATABASE [ARISBP11] SET ANSI_NULL_DEFAULT OFF GO ALTER DATABASE [ARISBP11] SET ANSI_NULLS OFF GO ALTER DATABASE [ARISBP11] SET ANSI_PADDING OFF GO ALTER DATABASE [ARISBP11] SET ANSI_WARNINGS OFF GO ALTER DATABASE [ARISBP11] SET ARITHABORT OFF GO ALTER DATABASE [ARISBP11] SET AUTO_CLOSE OFF GO ALTER DATABASE [ARISBP11] SET AUTO_CREATE_STATISTICS ON GO ALTER DATABASE [ARISBP11] SET AUTO_SHRINK OFF GO ALTER DATABASE [ARISBP11] SET AUTO_UPDATE_STATISTICS ON GO


237

ALTER DATABASE [ARISBP11] SET CURSOR_CLOSE_ON_COMMIT OFF GO ALTER DATABASE [ARISBP11] SET CURSOR_DEFAULT GLOBAL GO ALTER DATABASE [ARISBP11] SET CONCAT_NULL_YIELDS_NULL OFF GO ALTER DATABASE [ARISBP11] SET NUMERIC_ROUNDABORT OFF GO ALTER DATABASE [ARISBP11] SET QUOTED_IDENTIFIER OFF GO ALTER DATABASE [ARISBP11] SET RECURSIVE_TRIGGERS ON GO ALTER DATABASE [ARISBP11] SET RECOVERY FULL GO ALTER DATABASE [ARISBP11] SET MULTI_USER GO ALTER DATABASE [ARISBP11] SET PAGE_VERIFY CHECKSUM GO CREATE LOGIN ARISBP11 WITH PASSWORD=N'ARISBP', DEFAULT_DATABASE=[ARISBP11] GO USE [ARISBP11] GO CREATE USER [ARISBP11] FOR LOGIN [ARISBP11] GO CREATE SCHEMA [ARISBPDATA] GO ALTER USER ARISBP11 WITH DEFAULT_SCHEMA = ARISBPDATA; GO GRANT CONTROL ON SCHEMA :: [ARISBPDATA] TO [ARISBP11] GO GRANT CREATE TABLE TO [ARISBP11] GO GRANT CREATE VIEW TO [ARISBP11] GO GRANT CREATE FUNCTION TO [ARISBP11] GO

3.1.2.1.1 Sample script create_db.sql

USE master GO CREATE DATABASE [ARISBP11] ON PRIMARY (NAME = N'ARISBPPRIM', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPPRIM.mdf' , SIZE = 10MB , FILEGROWTH = 10MB), FILEGROUP [ARISBPDATA] (NAME = N'ARISBPDATA', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPDATA.ndf' , SIZE = 100MB , FILEGROWTH = 100MB), FILEGROUP [ARISBPINDEX] (NAME = N'ARISBPINDEX', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPINDEX.ndf' , SIZE = 100MB , FILEGROWTH = 100MB) LOG ON (NAME = N'ARISBPLOG', FILENAME = N'C:\mssqldata\ARISBP11\ARISBPLOG.ldf' , SIZE = 10MB , FILEGROWTH = 10MB) COLLATE Latin1_General_CI_AI GO


238

EXEC dbo.sp_dbcmptlevel @dbname=N'ARISBP11', @new_cmptlevel=90 GO BEGIN TRY EXEC [ARISBP11].[dbo].[sp_fulltext_database] @action = 'disable' END TRY BEGIN CATCH END CATCH GO ALTER DATABASE [ARISBP11] SET ANSI_NULL_DEFAULT OFF GO ALTER DATABASE [ARISBP11] SET ANSI_NULLS OFF GO ALTER DATABASE [ARISBP11] SET ANSI_PADDING OFF GO ALTER DATABASE [ARISBP11] SET ANSI_WARNINGS OFF GO ALTER DATABASE [ARISBP11] SET ARITHABORT OFF GO ALTER DATABASE [ARISBP11] SET AUTO_CLOSE OFF GO ALTER DATABASE [ARISBP11] SET AUTO_CREATE_STATISTICS ON GO ALTER DATABASE [ARISBP11] SET AUTO_SHRINK OFF GO ALTER DATABASE [ARISBP11] SET AUTO_UPDATE_STATISTICS ON GO ALTER DATABASE [ARISBP11] SET CURSOR_CLOSE_ON_COMMIT OFF GO ALTER DATABASE [ARISBP11] SET CURSOR_DEFAULT GLOBAL GO ALTER DATABASE [ARISBP11] SET CONCAT_NULL_YIELDS_NULL OFF GO ALTER DATABASE [ARISBP11] SET NUMERIC_ROUNDABORT OFF GO ALTER DATABASE [ARISBP11] SET QUOTED_IDENTIFIER OFF GO ALTER DATABASE [ARISBP11] SET RECURSIVE_TRIGGERS ON GO ALTER DATABASE [ARISBP11] SET RECOVERY FULL GO ALTER DATABASE [ARISBP11] SET MULTI_USER GO ALTER DATABASE [ARISBP11] SET PAGE_VERIFY CHECKSUM GO CREATE LOGIN ARISBP11 WITH PASSWORD=N'ARISBP', DEFAULT_DATABASE=[ARISBP11] GO USE [ARISBP11] GO CREATE USER [ARISBP11] FOR LOGIN [ARISBP11] GO CREATE SCHEMA [ARISBPDATA] GO


239

ALTER USER ARISBP11 WITH DEFAULT_SCHEMA = ARISBPDATA; GO GRANT CONTROL ON SCHEMA :: [ARISBPDATA] TO [ARISBP11] GO GRANT CREATE TABLE TO [ARISBP11] GO GRANT CREATE VIEW TO [ARISBP11] GO GRANT CREATE FUNCTION TO [ARISBP11] GO

3.1.2.2 Manage a system with an Oracle database






Prerequisite
























240


















deleted.

Procedure




editor.


<Context path="/businesspublisher" docBase="C:/Program

Files/ARIS11/BPServer/tomcat/webapps/businesspublisher/"

debug="0" reloadable="false" crossContxt="true">




initialSize="10"










241





</Context>




a text editor.

4. Ensure that the following entries are correctly maintained:





5. Ensure that you have adjusted the entries for DatabaseDAOClass

as follows:

<env-entry>


Class</description>



<env-entry-value>


cleDAO</env-entry-

value>

</env-entry>





Note








242

3.2 Oracle Business Process Repository
























Note







product.


243



GHz

RAM 64-bit system

2 GB RAM

32-bit system

1 GB RAM In 32-bit



(VM) is 1 GB.

512 MB



If you use Oracle BPA Suite Converter, you need an additional 256

MB RAM and 512 MB hard disk space for converting a database.




canceled.

If you use Oracle Business Process Simulator, 30% of main memory

is automatically reserved for simulation. You need at least 1 GB RAM

for a 32-bit system. 64-bit systems need at least 2 GB RAM.

For additional information, please contact Oracle Corporation support.


244

Software

Operating

systems




JRE Windows

If you have Oracle Business Process Repository installed and start

Oracle BPA Suite products as programs, an internal JRE version is

automatically used. You do not need to install JRE separately. If you

have already installed JRE, your installation is not used by Oracle BPA

Suite.

Your JRE installation is only used if you start Oracle BPA Suite products

from your browser.

The following are approved: Java Runtime Environment (JRE) 1.6.0_04

and subsequent patches that are in the public domain (Java SE on the

SUN home page except Java SE for Business) and generally released

by SUN.



directory>\<version>\lib must be named font.properties. For

example, if you wish to display Japanese characters, you must rename

the font.properties.ja file to font.properties.

Note

SUN renamed the JRE versions. JRE 1.6.0_04 is now called JRE 6.0,

Update 4. Approvals are also valid for subsequent updates.

Oracle BPA Suite products are tested using the JRE that is current at

the time of release.

If JRE 1.6.0_04 and subsequent patches are approved for an Oracle

BPA Suite product, the approval is valid for both JRE 1.6.0_04 and

JRE 1.6.0_05 and for any subsequent patch from the public domain

Java SE of the SUN home page (except for Java SE for Business).

SUN Microsystems guarantees compatibility between the JRE patch

levels. Therefore, the Oracle BPA Suite approvals for JREs are valid

for all patch levels of a version.

If you are using JRE 1.6 update 3 or an older version, copy the file

jaxb-api.jar from the directory <Web Client Components>\lib

to the directory <Java JRE installation directory>/endorsed,


245

e.g. C:\Program Files\Java\jre1.6.0_01\lib\endorsed.

If the directory endorsed does not exist, you must create it.

Please note that you must repeat this procedure for every update of

version 3 or older. We therefore recommend installation of version

4 or higher.

If you have Java 6 update 10 installed, problems may occur despite

better performance. Depending on your graphics card and driver

configuration, installation of Java 6 update 10 may cause delays in

the Designer and Matrices modules.

In this case, use the following command line entry to start the

program:


Unix

Oracle Business Process Repository requires JRE 1.6. Please first install

the appropriate JRE 1.6 for your operating system.

Protocols (Page

249)

Data exchange between browser-capable Oracle BPA Suite clients and

Oracle Business Process Repository can be encrypted with SSL (1024-

bit RSA).

SSL capability is already integrated into Oracle BPA Suite and only

needs to be activated when needed.


(Virtual Private Network) access Oracle Business Process Repository,

no firewall is required. Communication between clients and Oracle

Business Process Repository takes place via the CORBA protocol IIOP

(Internet Inter Object Request Broker Protocol).

Output If, for example, you want to output documents in PDF format using

Microsoft Word or Microsoft Excel, you must have Adobe Reader and

Microsoft Office version 2000, 2002, 2003, or 2007 installed. If you use

reports to import data from Excel tables, please ensure that the tables

have been saved in XLS format. If pop-up blockers are activated for

the domain, it may not always be possible to open report output in PDF

format from a Publisher export.


installed.


246

Note




support.

3.2.1 Oracle Business Process Repository - Operating system and database system platforms

Note

We support the integration of databases of the versions listed in the

table below only as long as they are supported by the respective

manufacturer.

This information was current at the time of printing. Therefore,

discrepancies may exist. Please read the release information in the

current Readme file. If other platforms or databases are released after

this guide has gone to press, you will be informed about them in the

Release Notes.

Approved combinations

Standard database system (1.3)

Oracle 10g R 2 (10.2.0.1) Express Edition (Universal) (2.7)

Oracle 10.1, 10.2, and 11.x (2)

MS SQL Enterprise Edition 2005 (2)

IBM DB2 UDB 9.5 (2)

Windows XP

Pro + SP1,2

(32-bit) (6)

Yes Yes Yes Yes Yes

Windows

Server 2003

SP1,2 + R2

SP2 (6)

(32/64-bit)

Yes Yes Yes Yes Yes

Windows

Server 2008

(6) (32/64-

bit)

No Yes Yes No No

HP-UX 11 No Yes Yes No No


247

Standard database system (1.3)

Oracle 10g R 2 (10.2.0.1) Express Edition (Universal) (2.7)

Oracle 10.1, 10.2, and 11.x (2)

MS SQL Enterprise Edition 2005 (2)

IBM DB2 UDB 9.5 (2)

Sun Solaris

9, 10

(4)

No Yes Yes No No

RedHat

Enterprise

Linux 5

(5)

Yes Yes Yes

No No

VMWare ESX No Yes Yes No No

(1)Only with 32-bit Java, Oracle BPA Suite standard platform, database

license included in the Oracle Business Process Repository license.

(2) Database must be provided by the customer.

(3) We recommend a maximum database size of 1 GB.

(4) Tested with SPARC + Intel processors

(5) Tested with RedHat ES5 (32/64-bit)

(6) Itanium processors have not been approved for Oracle BPA Suite

installations on Windows systems.

(7) You can use a maximum of 1 GB RAM and only one processor. You

can only start one instance per computer. The maximum database size

is 4 GB; this size is problematic if Oracle Business Process Repository

and Oracle Business Process Publisher use the database on the same

computer.


248

3.2.2 Recommended user-related server dimensioning

The following table provides an overview of the server configurations

that we recommend depending on the current number of users with

access.

Using the recommended sizes enables good system performance.

The servers must work within a network that runs at a transmission

speed of at least 100 Mbits.

Number of users

Server scenario Business Server Database server

1 - 50 Single server Quantity: 1

CPU(1): 1

Main memory: 2 GB

DBMS: Standard

database system

CPU(1): -.-

Main memory: -.-

51 - 100 Business Server

site

Quantity: 1

CPU: 2

Main memory: 2 GB

DBMS: External

systems

CPU(1): 1

Main memory: 2 GB


site

Quantity: 1

CPU: 2

Main memory: 2 GB

DBMS: External

systems

CPU(1): 2

Main memory: 2 GB


site (2)

Quantity: 2

CPU: 2

Main memory: 2 GB

DBMS: External

systems

CPU(1): 2

Main memory: 2 GB

n(3) *

200

Business Server

site (2)

Quantity: n (3)

CPU: 2

Main memory: 2 GB

DBMS: External

systems

CPU(1): 4

Main memory: 4 GB

(1) Pentium IV, 3.4 GHz

(2) Please contact Oracle Corporation support.


249

(3) n stands for a number of Business Server sites greater than 1. The

RAM required for JavaScript reports varies greatly. Therefore, we

recommend that you run these under UNIX or on a 64-bit system.

3.2.3 Protocols used

Different protocols are used for communication depending on the

equipment level. Oracle BPA Suite requires a fully functional TCP/IP

infrastructure. For the full equipment level, TCP/IP, IIOP (CORBA), and

HTTP are required.

Alternatively, data can be exchanged SSL-encrypted via the IIOP

protocol (see Oracle BPA Suite on the Internet/SSL (Page 249)).

3.2.3.1 Oracle BPA Suite on the Internet/SSL

Data exchange between browser-capable Oracle BPA Suite clients and

Oracle Business Process Repository can be encrypted with SSL (1024-bit

RSA).

SSL capability is already integrated into Oracle BPA Suite and only needs

to be activated when needed.

3.2.3.2 Oracle BPA Suite on the intranet/VPN




Process Repository takes place via the CORBA protocol IIOP (Internet

Inter Object Request Broker Protocol).

3.2.4 Configure Oracle Business Process Repository

During the installation process, the following files are created among

others in the directory <Oracle BPA Suite installation

directory>/server/config:

defaultServerSettings.cfg

Contains all default settings in an XML structure. This file is

overwritten for each subsequent setup.

setupServerSettings.cfg

Contains all settings that you specified during installation, e.g. the

paths. This file is overwritten for each subsequent setup.


250

userServerSettings.cfg

Contains all configuration changes that you have made after

installation. This file is not overwritten. If you run subsequent setups,

your configuration changes are preserved.

In older program versions, configuration changes were entered in

different files. If you run an update installation of the current version,

the configuration files are converted when Oracle Business Process

Repository is started. All configuration changes are entered in the file

userServerSettings.cfg. The configuration files are deleted. They

are backed up in the backup directory.

You enter all configuration changes as XML tags in the file <Oracle BPA

Suite installation directory>\server\config\userServerSettings.cfg.

This allows you to change all default settings according to your

requirements. Ensure that you enter the attributes in the correct XML

structure. You find the XML structure and all default attributes in the file

defaultServerSettings in the same directory. Please only change the

file userServerSettings.cfg. These changes are not overwritten in an

Oracle Business Process Repository update.

Note

If Oracle Business Process Repository does not start properly after the

configuration has been changed, check the XML structure of the file

userServerSettings.cfg. Once you have corrected or deleted incorrect

entries, the related changes are undone when you restart the server,

and the default settings of these attributes are used.

You need to change this configuration file if, for example,

you want to change the behavior of the HTML Generator (Page 255).

you want to configure the connections between the clients, Oracle

Business Process Repository, and Oracle Business Process Repository

Site Manager.

an e-mail is to be sent automatically to an address of your choice

(Page 256) in response to errors and warnings reported by Oracle


you wish to use SSL software.

the computer on which you have installed Oracle Business Process

Repository has two network cards.

you have to change ports as a result of a port conflict with external

software.

you want to enable a detailed, line-by-line debug output for the

Report Server.


251

3.2.4.1 Log logins

Logging is disabled by default. Use this setting to log login procedures

for an Oracle Business Process Repository.

1. Open the file <Oracle BPA Suite installation

directory>\server\config\userServerSettings.cfg with a text editor.

2. Insert the following:

<accounting state="on" />

3. Save the file, and restart Oracle Business Process Repository.

The login and logout times for each user are output in the log file.

3.2.4.2 Log messages

Logging is disabled by default. Use this setting to log information about

Oracle Business Process Repository. Enable logging if the system does

not work properly.




<startmode debugoutput="on" debuglevel="ALL" />


All messages are output in the log file.

Tip

If you enter the following, only information is output:

<startmode debugoutput="on" debuglevel="INFO" />

3.2.4.3 SSL encryption of data transmission via Secure Socket Layer

Using SSL (1024 Bit RSA) you can exchange encrypted data between the

Java-based products and Oracle Business Process Repository. SSL

capability is already integrated in Oracle BPA Suite.

Note

If you have installed Oracle Business Process Repository on a Unix

operating system and have enabled SSL encryption, Oracle Business

Process Repository must run under the root account.


252

Procedure

1. Ensure that the system date matches the current date. This ensures

that the validity of the SSL certificates (Page 252) is checked

correctly. These certificates can only be used to exchange data

between Java-based products and Oracle Business Process

Repository.




<profiles> <public ssl="443" /> </profiles>

If the default port 16070 is already in use, you can use any other

port that is available.

<profiles> <public port="<available port number>" />

</profiles>


5. From now on, use index_ssl.html as the start file for the databases.

This file is located in the directory %BPAHOME11g% server\html.

Warning





3.2.4.4 Update SSL certificates

Ensure that the certificates installed for your Oracle Business Process

Repository are up to date.

Procedure

Automatic installation

The SSL certificates are automatically updated when you use the patch

setup. Besides the patch setup, you continue to use the hotfix package

as a ZIP file. Using this ZIP file, the hotfix package can be installed with

the Silent install option. For additional information, see the Setup

descriptions (ftp://ftp.ids-

scheer.de/pub/ARIS/HELPDESK/ARIS701/hotfix/ARIS_Patch_Setup/).

ftp://ftp.ids-scheer.de/pub/ARIS/HELPDESK/ARIS701/hotfix/ARIS_Patch_Setup/

ftp://ftp.ids-scheer.de/pub/ARIS/HELPDESK/ARIS701/hotfix/ARIS_Patch_Setup/


253

Manual installation

1. Download the SSL certificate upCert_SSL_<program version>

from our server (ftp://ftp.ids-

scheer.de/pub/ARIS/HELPDESK/CERTIFICATES/). Ensure that your

program version matches the one of this certificate.

2. Exit Oracle Business Process Repository.

3. Copy the file ssl.jar to the Endorsed directory of your Oracle

Business Process Repository installation, e.g. ..\server\endorsed.

4. Start Oracle Business Process Repository.

The certificate has been updated.

3.2.4.5 Configure Oracle Business Process Repository/Oracle Business Process Repository Site Manager connection

The following entries specify the intervals at which Oracle Business

Process Repository Site Manager checks whether the license service is

active:

<licenseservice_client timeout_interval="300000" heartbeat_interval="50000" /> </licenseservice_client>

The heartbeat_interval="50000" entry specifies that Oracle Business

Process Repository sends a ping to Oracle Business Process Repository

Site Manager every 50 seconds (= 50,000 milliseconds) and thus

indicates that its licenses are still in use.

The timeout_interval="300000" entry specifies that Oracle Business

Process Repository Site Manager checks every 5 minutes (= 300,000

milliseconds) whether Oracle Business Process Repository is still logged

in with the corresponding licenses. If not, all licenses used via this

Oracle Business Process Repository will be released.

Similarly, the following entries handle the locks in the database:

<lockservice_client timeout_interval="300000" heartbeat_interval="50000" /> </lockservice_client>

The heartbeat_interval="50000" entry specifies that Oracle Business

Process Repository sends a ping to Oracle Business Process Repository

Site Manager every 50 seconds (= 50,000 milliseconds) to indicate that

its locks are still valid.

ftp://ftp.ids-scheer.de/pub/ARIS/HELPDESK/CERTIFICATES/

ftp://ftp.ids-scheer.de/pub/ARIS/HELPDESK/CERTIFICATES/


254

The timeout_interval="300000" entry specifies that Oracle Business

Process Repository Site Manager checks every 5 minutes (= 300,000

milliseconds) whether Oracle Business Process Repository is still logged

in with the corresponding licenses. If not, all locks generated via this

Oracle Business Process Repository will be lifted.

3.2.4.6 Configure client/Oracle Business Process Repository connection

While each client pings Oracle Business Process Repository every 25

seconds, the following setting causes Oracle Business Process Repository

to check every 90 seconds (value in milliseconds) which client is still

connected. This entry determines the period within which a user can

contact Oracle Business Process Repository via the client without having

to log in again.




<appservertimer timeout_interval="60000" /> </appservertimer>


The change has been applied.

3.2.4.7 Deactivate Report Server

The Report Server is running by default. If you do not want to start any

VB scripts on Oracle Business Process Repository, you can deactivate the

Report Server. As a result, fewer system resources are needed and

system performance improves. You can always run VB scripts locally.




<reportserver active="false" />


The Report Server is no longer running. Therefore, more resources are

available for Oracle Business Process Repository.


255

3.2.4.8 Deactivate simulation server

The simulation server is running by default. If you are not using Oracle

Business Process Simulator on an Oracle Business Process Repository,

you can deactivate the simulation server. As a result, fewer system

resources are needed and system performance improves.




<simuserver active="false" />


The simulation server is no longer running. Therefore, more resources

are available for Oracle Business Process Repository.

3.2.4.9 HTML Generator - Current database lists

HTML Generator creates all index files and the file aris_database.html

for the Web Client Components. It updates the access files whenever

databases are created, renamed, or deleted. You can use the file

userServerSettings.cfg (server\config directory) to control its

behavior.

In a default server installation, the HTML Generator is switched on and

generates the index.html files in the directory C:\<default

directory>\Oracle BPA Suite11g\server\html. If you accept all

default values during installation, this directory will always contain a

current, executable Web Client Components directory that you can copy

directly to your Web server.

A dialog box prompts you to specify where the HTML Generator is to be

installed.

The htmlgen section of the file defaultServerSettings.cfg contains

the path in which the created files are saved. A language ID is entered in

this section for each of the interface languages installed on the Oracle

Business Process Repository. For each of these IDs, HTML Generator

creates an index_lan.html file in the Web Client Components structure:


256

<htmlgen> <languagelist default="de"> <language tag="de"/> <language tag="en"/> <language tag="ja"/> </languagelist>  <outputpath path="C:/wwwroot/Oracle BPA Suite11g"/> </htmlgen>

Please note that you must insert the output and backup paths in the file

userServerSettings.cfg. If your work is not limited to the use of only

one Oracle Business Process Repository, you need to adjust the paths on

the computer on which Oracle Business Process Repository Site Manager

is installed. Insert the following entry:

<htmlgen> path="e:/inetpub/wwwroot/bpa11"/><backuppath path="e:/inetpub/wwwroot/bpa11/backup"/> </htmlgen> You make other changes in the same way: <htmlgen> <appserver name="myspecialhost" /> <genlist> <genfile target_dir="ssl" target_name="dblist.html" database_template="aris_database_ssl.html"/> </genlist> </htmlgen>

You can run the HTML Generator manually at any time by executing the

htmlgen.bat file in the Oracle Business Process Repository directory.

Warning





3.2.4.10 Activate Oracle BPA Suite Notify Service

Administrators of Oracle BPA Suite sites can have messages sent by the

Oracle BPA Suite notify service when problems arise. It is possible to

notify (Page 256) several administrators at the same time.

In the file userServerSettings.cfg, you can specify that an e-mail be

sent to an e-mail address of your choice when the behavior of the Oracle

BPA Suite site triggers warnings or error messages. The e-mail contains


257

the zipped files of the log and config directories. You can toggle the

notification mode by setting the state value.

Prerequisite

The username account (see the following example) must exist on your

e-mail server.

Procedure




Example

<adminagent> <mailing state="on" language ="en" warnings ="on" username="adminservice" address="[email protected]"> <recipient address="[email protected]" /> </mailing> </adminagent>


4. Warnings or error messages are sent by e-mail to the administrators.

Please refer to the table for possible values.

Entry Value Meaning

state on

off

The mail function is

switched on.


switched off.

language

en

Contains the relevant

language code.

In this example, the

language code is set to

English.

warnings on

off

E-mails will be sent for

warnings and errors.

E-mails will be sent only

for errors.


258

Entry Value Meaning

username adminservice Name of the e-mail

sender.

In this example:

adminservice

address adminservice@your

company.com

Address of the e-mail

sender.

recipient address adminservice@your

company.com


recipients.

You can insert a list of

addresses here.

3.2.4.11 Restrict number of index_backup files

When HTML Generator creates a new index_lan.html file, the existing

index.html file is saved as index_backup (<date time>).zip under

the specified backup path. The backup path is specified in the

<htmlgen> section. You can decide how frequently the backup files

(except the current ones) are to be deleted. The interval is defined in

days. In the following example, the entry specifies that index_backup

files are deleted after seven days.




<htmlgen> <backupperiod period="7"/> </htmlgen>

If you want to change the path, enter the following, for example:

<backuppath path="e:/wwwroot/bpa11/backup"/>


The index_backup files are deleted after seven days.


259

3.2.4.12 Provide additional memory

If you use memory-intensive applications, such as an XML import or Fast

Merge, we recommend that you provide additional memory to the local

server LOCAL and Oracle Business Process Repository.

To provide additional memory, you need to ensure that the hardware

requirements are met.

LocalServer

You can increase memory usage by specifying the following entry in the

file local.cfg in the directory <Oracle BPA Suite installation

directory>/LocalServer/config:

maxMem=1024m

Just change the value shown in bold. The entry in the example above

specifies that the local server LOCAL may use a maximum of 1024

megabytes of memory.

Server

You can increase memory usage by inserting the following entries in the

file userServerSettings.cfg in the directory <Oracle BPA Suite

installation directory>/Server/config:

<jre> <maxMem server="1024m" /> </jre>

The entry in the example specifies that Oracle Business Process

Repository may use a (maximum) memory of 1024 megabytes.

3.2.4.13 New database - Additional languages

Using the readonly_properties.xml file, you can specify which

database languages are automatically created when creating databases.

Find the file

for the local database system in the <Oracle BPA Suite

installation directory>\LocalServer\property directory.

for the Oracle BPA Suite Server in the <Oracle BPA Suite

installation directory>\server\property directory.

Procedure

1. Open the file readonly_properties.xml of the corresponding

directory in a text editor.


260

2. Select a language text block, e.g. the Spanish block:

1. <property key="dbinitlanguages.es.commonfontbold" datatype="BOOL">false</property> 2. <property key="dbinitlanguages.es.stdfontstylename" datatype="STRING">Standard</property> 3. <property key="dbinitlanguages.es.maingroupname" datatype="STRING">Main group</property> 4. <property key="dbinitlanguages.es.dialogfontsize" datatype="LONG">8</property> 5. <property key="dbinitlanguages.es.commonfontsize" datatype="LONG">10</property> 6. <property key="dbinitlanguages.es.codepage" datatype="LONG">1252</property> 7. <property key="dbinitlanguages.es.charset" datatype="LONG">0</property> 8. <property key="dbinitlanguages.es.commonfontname" datatype="STRING">Arial</property> 9. <property key="dbinitlanguages.es.lcid" datatype="LONG">1033</property>

3. Copy the text block to the clipboard and paste it at the end of the

file.

4. If required, change the name of the default language font in row 2

(Standard is the default value in the Spanish language text block).

5. Change the name of the main group in row 3, if necessary (Main

group is the default value in the Spanish language text block).

6. Modify the codepage entry in row 6, if necessary (codepage 1252 is

the default value in the Spanish language text block).

7. Change the general font name in row 8, if necessary (Arial is the

default value in the Spanish language text block).

8. Modify the locale ID in row 9, if necessary (locale ID 1034 is the

default value in the Spanish language text block).

Note

If you want to use country-specific special characters, they must be

entered with UTF-8 encoding. Please use an UTF-8-enabled editor to

encode country-specific special characters.

3.2.5 Oracle BPA Suite Converter

Oracle BPA Suite Converter is the program for converting data from

older Oracle BPA Suite versions to work with Oracle BPA Suite 11g,

regardless of the server platform and database management system

used. The conversion enables you to transfer databases of a different

product version. If, for example, you created a user database under an

Oracle database for Oracle BPA Suite 10.1.3.1, you can use Oracle


261

BPA Suite Converter to specify that this database be transferred to

your local Oracle BPA Suite.

You can convert databases directly from the relevant server.

If you have disk space problems when converting large databases (see

file serverout.log in directory <Oracle BPA Suite installation

directory>\LocalServer\log\ or <Oracle BPA Suite installation

directory>\server\log\), you can specify that more memory (Page

299) is allocated for database conversion in the file

userServerSettings.cfg (in directory <Oracle BPA Suite installation

directory>\LocalServer\config\) or in the file local.cfg (in directory

<Oracle BPA Suite installation directory>\server\config\).

As a rule, all applications from which COM objects are used in Oracle

BPA Suite databases must be installed on the computer you use for

converting databases. Databases containing links to Microsoft Word and

Microsoft Excel documents can be converted only if Microsoft Word and

Microsoft Excel version 2000 or higher are installed.

The system requirements depend on the relevant usage scenario.

In case of doubt, please contact Oracle Corporation support.

3.2.6 When are placed symbols displayed (server)?

For example, if you run reports or create a Publisher export, the icons

that are saved in the icons subdirectory in the installation directory of

your Oracle Business Process Repository are used for linked files. Icons

of Microsoft Office products are automatically displayed. For these

applications, you do not need any icons in the directory noted above

unless you want to use your own icons.

You can change icons or add new ones. To create and edit icons in ICO

format, you need a suitable application. Assign file names that conform

with the extension of the relevant application.

To create icons that represent bitmap graphics or text files, for example,

save the graphics under the names bmp.ico and txt.ico.

Added icons are immediately available. Once you have changed icons,

you must restart Oracle Business Process Repository.

Note

If icons displayed in models are different from those in the report output

or in Publisher export, ensure that you have saved the corresponding

icons in the installation directory of your Oracle Business Process

Repository, in the icons subdirectory.


262

If icons for placed attributes are missing there, they will not be displayed

in the Publisher export or report output.

3.2.7 Add custom icons for macros

For users to be able to add frequently used macros as icons to the

toolbar, administrators must provide these icons.

Prerequisite

You have administration privileges for the Oracle Business Process

Repository installation directory.

Procedure

1. Open the installation directory of the relevant Oracle Business

Process Repository ..server/templates/scriptservice/internal/,

and create the images subdirectory.

2. This is where you save the icon files in PNG format.

The graphics must be (n*16) x 16 pixels in size.

3. Create an images.lst file and save it in UTF-8 format.

The file specifies the sequence in which the icons are displayed in the

user interface.

The file must have the following structure:

<Name of the first icon>.png

<Name of the second icon>.png

...

The new icons are available to users in the Configure macros dialog

box after restarting the program. If the file images.lst is missing, no

icons from the images directory are displayed.

3.2.8 Server log directory

The activities of the Oracle Business Process Repository are recorded in

the log directory of the server installation directory. If problems occur

during operation, you can use the log files to find and resolve errors. If

you cannot resolve the problems, please send an error description and

the entire contents of the log and config directories to Oracle

Corporation support.


263

3.3 Oracle BPA Suite agent

The following section describes how the agent-based system in Oracle

BPA Suite supports you in diagnosing and restoring Oracle BPA Suite

services.

3.3.1 What are Oracle BPA Suite agents for?

The Oracle BPA Suite agent system autonomously monitors and, in

particular, starts and stops Oracle Business Process Repository

processes and all dependent services.

Within the system, an Oracle BPA Suite agent monitors and manages all

Oracle Business Process Repository processes (and the associated Oracle

BPA Suite services) that are installed on one computer.









3.3.2 What tasks does an Oracle BPA Suite agent handle?

An Oracle BPA Suite agent mainly performs the following tasks:

Determining and providing Oracle BPA Suite service information

Monitoring Oracle BPA Suite services by querying them at regular

intervals (ping)

Shutting down or rebooting Oracle BPA Suite services (automatically

or after prompting)

3.3.3 How to exit Oracle BPA Suite agents

Shutting down Oracle Business Process Repository correctly will also

shut down the Oracle BPA Suite agent and all Oracle BPA Suite services.

To do so, either open the DOS window for Oracle Business Process

Repository and press Ctrl + C, or shut down the service.


264

3.3.4 Activate Oracle BPA Suite Notify Service









Prerequisite

The username account (see the following example) must exist on your

e-mail server.

Procedure




Example

<adminagent> <mailing state="on" language ="en" warnings ="on" username="adminservice" address="[email protected]"> <recipient address="[email protected]" /> </mailing> </adminagent>


4. Warnings or error messages are sent by e-mail to the administrators.

Please refer to the table for possible values.

Entry Value Meaning

state on

off


switched on.


switched off.


265

Entry Value Meaning

language

en

Contains the relevant

language code.

In this example, the

language code is set to

English.

warnings on

off

E-mails will be sent for

warnings and errors.

E-mails will be sent only

for errors.

username adminservice Name of the e-mail

sender.

In this example:

adminservice

address adminservice@your

company.com


sender.

recipient address adminservice@your

company.com


recipients.

You can insert a list of

addresses here.

3.4 Java clients (application)

Oracle Business Process Architect is a Java client that you start as an

application. All clients use Oracle Business Process Repository to access

the database server and thus work with a common data basis.

This section describes the processor, memory, system configuration, and

software requirements of the various client computers. For simultaneous

use of other applications, a faster processor, additional memory, or

system extension may be required.




RAM is available than listed below, runtime behavior might improve. In

some cases, minimum and recommended system requirements are


266







The table shows the requirements that apply for many of the Java-based

programs. Additional requirements must be met for some programs.

Find out about specific requirements in the relevant sections.

Note







product.


267


Processor Intel Pentium IV 2.4 GHz Intel Pentium IV 2.0 GHz

RAM Client installation with and

without local database

system: 1 GB RAM

Client installation without local

database system: 256 MB RAM

Client installation with local

database system: 512 MB RAM

Bandwidth 128 k 56 k. Lower bandwidths are

possible. However, lower

bandwidths can result in reduced

performance.

Hard disk 375 MB

For single-user installation:

sufficient disk space for each

user database.

375 MB

For single-user installation:

sufficient disk space for each user

database.

Network

communication

TCP/IP (Page 249) TCP/IP

Software Details

Operating

systems

Windows XP Professional + Service Packs

Windows Vista (Business, Ultimate; 32-bit)

Windows Vista + Service Pack 1 (32-bit)

Citrix Metaframe Presentation Server 4.0

Only in combination with Windows Server 2003 Standard

Edition + Service Pack 2 (32/64-bit).

For any patches/security patches that may be needed, see the

Oracle BPA Suite release notes in the file Readme.txt on the

Oracle BPA Suite installation media.

RedHat ES5-Linux

Without local server LOCAL


268

Software Details

Browser Microsoft Internet Explorer, version 6.0

Microsoft Internet Explorer, version 7.0

Security settings (Microsoft Internet Explorer)

If Java Runtime Environment (JRE) is not yet installed and needs

to be downloaded, you need to specify settings in the

Tools/Internet Options/Security/Custom Level menu in

Microsoft Internet Explorer.

Adjust your browser settings to ensure that the following actions

are permitted:

Running ActiveX controls and plug-ins

Downloading signed ActiveX controls

Executing JavaScript

Pop-ups are permitted in the domain in which the Oracle

Business Process Publisher is running.

If pop-ups are blocked, report output cannot be displayed in

PDF format.

JRE If you have Oracle Business Process Repository installed and start

Oracle BPA Suite products as programs, an internal JRE version is

automatically used. You do not need to install JRE separately. If

you have already installed JRE, your installation is not used by

Oracle BPA Suite.

Your JRE installation is only used if you start Oracle BPA Suite

products from your browser.

To display different character sets (Japanese, Arabic, Cyrillic,

etc.), the corresponding file in directory <JRE installation

directory>\<version>\lib must be named font.properties.

For example, if you wish to display Japanese characters, you must

rename the font.properties.ja file to font.properties.

Output If, for example, you want to output documents in PDF format

using Microsoft Word or Microsoft Excel, you must have Adobe

Reader and Microsoft Office version 2000, 2002, 2003, or 2007

installed. If you use reports to import data from Excel tables,

please ensure that the tables have been saved in XLS format. If

pop-up blockers are activated for the domain, it may not always

be possible to open report output in PDF format from a Publisher


269

Software Details

export.

In addition, all applications that are linked in your models should

be installed.

LDAP Oracle BPA Suite supports LDAP. Windows Server 2003 Active

Directory has been tested; therefore, the documentation refers to

this system.

Multi-monitor

operation

Oracle BPA Suite products are approved for multi-monitor

operation.

3.4.1 Oracle Business Process Simulator

Oracle Business Process Simulator is integrated into Oracle Business

Process Architect.

Oracle Business Process Simulator is used for process analysis and

process optimization. Based on process models and organizational

structures, the simulation enables a comparison of actual and target

processes in respect of practicability and efficiency. The focus can also

be laid on costs, execution time or resource usage. This answers

questions on throughput times, weak points, bottlenecks, resource

requirements, etc.

Oracle Business Process Simulator includes the following model types:

EPC

EPC (material flow)

EPC (column display)

EPC (row display)

EPC (table display)

EPC (horizontal table display)

PCD

PCD (material flow)

Office process

Industrial process

Schedule/Composite schedule


270

Business process diagram (BPMN)

BPMN allocation diagram

The following model types are included without having to be explicitly

selected.

Event diagrams that have been assigned to events,

Function allocation diagrams that have been assigned to functions,

and

Organizational charts that have been assigned to human resources.

Oracle Business Process Simulator supports the same platforms as

Oracle Business Process Repository (see Administration Guide). If you

use Oracle Light as a database, Oracle Business Process Simulator

accesses the Oracle Light instance.

If you use Oracle Business Process Simulator, you need at least 1 GB

RAM for a 32-bit system. 64-bit systems need at least 2 GB RAM.

If you use Oracle Business Process Simulator, 30% of main memory

is automatically reserved for simulation. You need at least 1 GB RAM

for a 32-bit system. 64-bit systems need at least 2 GB RAM.

3.4.2 Client log directory

The program activities are logged in the directory <system

drive>:\Documents and Settings\<user>\Oracle BPA Suite11\log. If

problems occur during operation, you can use the log files to find and

resolve errors. If you cannot resolve the problems, please send an error

description and the entire contents of the log and config directories to

Oracle Corporation support.


271

3.5 Oracle Business Process Publisher

This chapter describes the system requirements and configuration of


Oracle Business Process Publisher Server

For 100

simultaneous

users

Up to 100

simultaneous

users

Up to 50

simultaneous

users

Processor Dual Intel Xeon

2.8 GHz with 1

MB of level 2

cache

Intel Xeon 3.4 GHz

with 1 MB of level 2

cache

Intel Pentium IV,

3.0 GHz with 1 MB

of level 2 cache

RAM 4 GB DDR2

SDRAM RAM,

400 MHz (2 x 2

GB) Dual Rank

2 GB DDR2 SDRAM

RAM

2 GB DDR2 SDRAM

RAM

Controller SCSI with RAID1

option

SCSI with RAID1

option

SCSI with RAID1

option

Hard disk RAID1, 2 x 73

GB SCSI hard

drive, 15,000

rpm in RAID

array

SATA-RAID1, 2 x 73

GB SCSI hard drive,

10,000 rpm in RAID

array

SATA-RAID1, 2 x

73 GB SCSI hard

drive, 10,000 rpm

in RAID array

Operating

systems

Depends on the database systems (Page 275) used.

Network

connection

Web application server to database server: Integration in a

1000 MBit network

Client connection: Internet connection



Repository. If the memory is insufficient, the export process is canceled.





272

Computers of the Publisher export users

Browser Microsoft Internet Explorer, version 6.0

Microsoft Internet Explorer, version 7.0

Firefox 1.x

Firefox 2.x

While Oracle Corporation has not approved the use of later versions, it

is highly unlikely that they cannot be used. However, we cannot

guarantee that links will work correctly (Page 339).

Security settings (Microsoft Internet Explorer)

If Java Runtime Environment (JRE) is not yet installed and needs to be

downloaded, you need to specify settings in the Tools/Internet

Options/Security/Custom Level menu in Microsoft Internet

Explorer.

Adjust your browser settings to ensure that the following actions are

permitted:

Running ActiveX controls and plug-ins

Downloading signed ActiveX controls

Executing JavaScript

Pop-ups are permitted in the domain in which the Oracle Business

Process Publisher is running.

If pop-ups are blocked, report output cannot be displayed in PDF

format.

JRE The following are approved: (Page 275) Java Runtime Environment

(JRE) 1.6.0X and patches that are in the public domain (Java SE on

the SUN home page except Java SE for Business) and generally

released by SUN.




example, if you wish to display Japanese characters, you must rename

the font.properties.ja file to font.properties.

Output If, for example, you want to output documents in PDF format using


Microsoft Office version 2000, 2002, 2003, or 2007 installed. If you use

reports to import data from Excel tables, please ensure that the tables

have been saved in XLS format. If pop-up blockers are activated for


273

the domain, it may not always be possible to open report output in PDF

format from a Publisher export.


installed.

Note







3.5.1 Oracle Business Process Publisher Server

Oracle Business Process Publisher is integrated in the Administration

module of Oracle Business Process Architect. With these products,

administrators can create exports of your Oracle BPA Suite databases

after you have installed Oracle Business Process Publisher Server.

Oracle Business Process Publisher Servers manage every Publisher

export. A Publisher export is a Web application based on J2EE. Java

Servlets and Java Server Pages (JSP) are used, which, in addition to a

Java environment (JDK), require a Web application server (for example

Apache Tomcat) as runtime environment. The data is held in a

relational database system and is exchanged with the program via a

JDBC interface.

The standard database system and Apache Tomcat Web Application

Server are automatically installed if you select the standard installation

for Oracle Business Process Publisher Server. With this database system,

up to 10 users can access a Publisher export simultaneously. Swimlane

models cannot be exported optimally using a Derby database. For a

larger number of users, you require an external database system.


purchased, these systems enable all users to simultaneously work on a

Publisher export.





274

If you retain the settings of the installation program when you use the

standard installation of Oracle Business Process Publisher Server, the

context path and the free port to the Web server are entered

automatically.

To use a server other than Apache Tomcat Web Application Server,

please follow the Installation instructions (Page 44).

Note








275

3.5.1.1 Approved platforms, servers, applications, and databases

Tested and approved combinations are listed in the tables below.

Note

When you combine various technologies, please observe the manufacturers' instructions, particularly announcements

concerning releases on their Internet pages. We cannot guarantee proper functioning of supported third-party systems.

Always follow the instructions provided in the installation manuals of the relevant manufacturer, or contact Oracle

Corporation support.

This information was current at the time of printing. Therefore, discrepancies may exist in Service Releases. Please read

the current release information and the Readme file.

Tested Web application servers

Platform Web server

IBM WebSphere

6.1.0.15 or

higher

TomCat 5.5.x

(32/64 bit)

Oracle WebLogic

11g R 1

Windows Server 2003 SP1, SP2

(32/64-bit)

Yes Yes Yes

Windows Server 2003 SP2, R2

SP2

(32/64-bit)

Yes Yes Yes

Windows Server 2008 (32/64-

bit)

No Yes Yes


276

Platform Web server

Sun Solaris 9, 10 (1, 2, 3) No Yes No

Red Hat Enterprise (4)

Linux 5

Yes Yes Yes

VMWare ESX Yes Yes No

(1) Installation only by Oracle Corporation Support.

(2) Tested with Sparc processors

(3) Tested with Intel Xeon processors

(4) Tested with RedHat ES 5

Tested Web servers

Platform Web server

Apache 2.0.x Apache 2.2.x


(32/64-bit)

Yes Yes


SP2

(32/64-bit)

Yes Yes


277

Tested database systems

Platform Database system

Standard

database

system

(10 users

max.) (1)

Oracle

10.1/10.2/

11.x (2)

Oracle

10g R 2

(10.2.0.1

)

Express

Edition

(Univers

al) (2.6)

MS SQL Server

2005 (2)


(32/64-bit)

Yes Yes Yes Yes


SP2

(32/64-bit)

Yes Yes Yes Yes

Windows Server 2008 (32/64-

bit)

No Yes No No

Sun Solaris 9, 10 (2, 3, 4) No Yes No No

Red Hat Enterprise (5)

Linux 5

Yes Yes No No

VMWare ESX No Yes No No


278

(1)Only with 32-bit Java

(2) Installation only by Oracle Corporation Support.

(3) Tested with Sparc processors

(4) Tested with Intel Xeon processors

(5) Tested with RedHat ES 5

(6) You can use a maximum of 1 GB RAM and only one processor. You can only start one instance per computer. The

maximum database size is 4 GB; this size is problematic if Oracle Business Process Repository and Oracle Business

Process Publisher use the database on the same computer.


279

3.5.2 Context path

The context path is the path to the directory where the index.html

start page for Oracle Business Process Publisher is located. If you

want to place the start page in another directory, you need to change

the path accordingly.

3.5.3 Modify configuration files

Free port to Web server (Page 281)

Change IP address (Page 282)

LDAP user management (Page 282)

OIS user management (Page 288)

E-mail settings (Page 281)

Use an Oracle database (Page 288)

MS SQL Server 2005 under MS Windows

3.5.3.1 Show all groups in the Explorer tree (Publisher Server)

By default, only groups containing at least one item are displayed in

exports. To display empty groups as well in the Explorer tree, change

the corresponding setting in the configuration file.

Prerequisite

You have access privileges for the Publisher Server installation

directory.

Procedure

1. Open the file webappserver.cfg in the Publisher Server

installation directory

..\BPServer\tomcat\webapps\businesspublisher\config\

with a text editor.

2. In the <switch value="off"/> line, change the default value

from off to on.

<show_all_groups>

<switch value="on"/>

</show_all_groups>



280

4. Restart Publisher Server.

In each Publisher export, the Explorer tree displays all groups of the

relevant databases.

Tip

You can undo this setting at any time by entering the default value

and restarting Oracle Business Process Publisher.

3.5.3.2 Change the DAO of an Oracle database (Tomcat)

Procedure

1. In case of deployment in a Tomcat Web application server

environment, open the configuration file ..\

BPServer\tomcat\webapps\businesspublisher\config\webappserv

er.cfg from the Oracle Business Process Publisher Server

installation directory in a text editor.

In case of deployment on an Oracle Application Server, open the

configuration file

..\j2ee\home\applications\BusinessPublisher\businesspublisher\co

nfig\webappserver.cfg from the Oracle Business Process

Publisher Server installation directory in a text editor.

2. Ensure that the entry for DatabaseDAOClass refers to a valid DOA

value and is specified as follows:

<env-entry> <description>The IDatabaseDAO Implementation Class</description> <env-entry-name>DatabaseDAOClass</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>com.idsscheer.aris.businesspublisher.application.dao.database.AOracleDAO</env-entry-value> </env-entry>

If you are using a Tomcat environment, ensure that the

ojdbc5.jar JDBC driver is available in the installation directory

(..\BPServer\tomcat\common\lib) of Oracle Business Process

Publisher Server. It is assumed that version 10.2.0.3 is installed.

The file is located on the installation media under /Setups/All

OS/Oracle Business Process Publisher Server.


281

3.5.3.3 E-mail settings

If you reset passwords, for example, automatic e-mails containing the

initial passwords are sent to the appropriate users.

Prerequisite

You have access privileges for the Oracle Business Process Publisher

Server installation directory.

Procedure




with a text editor.

2. Find the <bpadmin> tag. In this section, configure the mail

server settings.

3. Specify the required settings. Information about settings is

provided in the <bpadmin> section.

Save the changes and restart Oracle Business Process Publisher

Server.

3.5.3.4 Free port to Web server

The installation program automatically enters 9090 as the port. To

use another free port on your Web server, you need to enter the

required port in the Tomcat Server Port box.

Prerequisite



Procedure

1. Open the file businesspublisher.xml in the Oracle Business



editor.

2. In the following line, change the value for the port number:

<Connector port="9090" />.



282

The change takes effect only after you have restarted Oracle

Business Process Publisher Server.

3.5.3.5 Change IP address

If you have installed Oracle Business Process Publisher Server on an

external computer rather than locally, you must enter the IP address

of the external computer in the configuration file.

Prerequisite



Procedure




with a text editor.

2. In the bpservicehost value line, change the value for the IP

address of the computer on which Oracle Business Process

Publisher Server is installed, e.g. <bpservicehost

value="172.30.111.123"/>


The change takes effect only after you have restarted Oracle


3.5.3.6 LDAP user management

If you manage users via an LDAP system, authentication is performed

using this system. To enable the Oracle Business Process Publisher

administrator to map LDAP user groups to Oracle BPA Suite user

groups, you need to customize the configuration file.

Prerequisite



Procedure




with a text editor.


283

2. Find the <ldap> tag. In this section, configure the login using an

LDAP system.

3. Specify the required settings. Information about settings is

provided in the <ldap> section.

4. Save the changes and restart Oracle Business Process Publisher

Server.

The Oracle Business Process Publisher administrator can now map

Oracle BPA Suite user groups to LDAP user groups.

Warning

If your LDAP server is set up so that it allows anonymous

authentication (unauthenticated bind mechanism), users may be able

to log in without a password.

Note

You can use the administration interface for exports to encrypt (Page

286) the password of the LDAP user maintained here. Copy the

encrypted password to this file and restart the server.

3.5.3.7 Use Microsoft SQL database

Please adjust the system as required to manage Oracle Business

Process Publisher in combination with an MS SQL Server 2005

database. If you use the MS SQL Server 2005 database, all users

covered by the license can simultaneously work with a Publisher

export, which is not possible with the standard database.

Prerequisite

Copy the file create_db.sql (installation media/Setups/All

OS/Oracle Business Process Publisher Server) to a directory of

your choice.

You have installed Microsoft SQL Server 2005 under MS

Windows. Microsoft SQL Server 2005 is not included in the

package.

Procedure





284






password according to your choice, you must also change them

in the configuration files businesspublisher.xml and

webappserver.cfg.


COLLATE statement.

The script creates the specified data groups. If you have

changed the names in the script, you must also change them

in the configuration file businesspublisher.xml.



d. Copy the JDBC driver jTDS.jar (installation

media/Setups/All OS/Oracle Business Process Publisher

Server) to the Tomcat installation directory under

common/lib.


..\BPServer\tomcat\conf\catalina\localhost\businesspublisher.x

ml:



b. Ensure that the URL has been adjusted correctly, for example

as follows:





following entry:


jdbc:jtds:sqlserver://hostname:1433/ARISBP11;instanc

e=MSSQLSRV.



285


..\BPServer\tomcat\webapps\businesspublisher\config\webappse

rver.cfg.





them here.


<env-entry>


Class</description>



<env-entry-

value>com.idsscheer.aris.businesspublisher.application.dao.datab

ase.AMSSQLDAO</env-entry-value>

</env-entry>

Tip




Note









286

3.5.3.8 Encrypt LDAP password

If users are authenticated via LDAP, a default user and the related

password must be entered in the configuration file

webappserver.cfg. To prevent misuse, you can encrypt this

password and enter it in the configuration file.

1. Log in as administrator to the Publisher export.

2. Click on Information and then on the Encrypt LDAP

password link in the Other box.

3. Enter the password to be encrypted, and then click on Encrypt

LDAP password.

4. Copy the encrypted password to the clipboard.



(..\BPServer\tomcat\webapps\businesspublisher\config\) with a

text editor.

6. Search for the tag <ldapdefaultpwd value="password"/>,

and paste the copied password as a value between the quotation

marks.

7. Search for the tag <ldappwdcrypted value="false"/>, and

change the value from false to true.

8. Save the change and restart Oracle Business Process Publisher

Server.

The password is now encrypted.

3.5.3.9 Configure navigation carousel

To display the navigation carousel in exports, a structuring model

must be modeled in the database.

Ensure that the configuration file <Oracle Business Process Publisher

Server installation

directory>\tomcat\webapps\businesspublisher\layouts\default\config\

aspectOrientedEntry.cfg.xml is configured for evaluation of the

modeled structuring model. This setting is selected by default. You do

not have to adjust this file unless it has been changed after

installation.


287

Procedure

1. Open the file in an editor.

2. Ensure that the values of the keys are maintained as follows:

<aoeDefinition exportName="*"

isVisible="true"

and

<aoeDefinition exportName="no export"

isVisible="true"

Changes to this file take effect immediately without restarting Oracle


3.5.3.10 Display news

The News section in the Home module is used in the standard

export as an example. If you have knowledge of RSS feed and XML

programming, you can insert links in this area.

Prerequisite



Procedure

1. Open the file

\BPServer\tomcat\webapps\businesspublisher\layouts\default\conf

ig\layout.cfg.xml with your editor.

2. Find the <news basename="news"> area, and enter the URL

for your RSS feed.

<news basename="news">  <url proto="http" location="http://www.ids-scheer.com/ids-upload/products/aris_news/aris_news.xml" proxyAdress="hades.ids-scheer.de" proxyPort="3103" refresh="600"/> </news>


Tip

The News area can be customized to meet your requirements. For

example, you can keep a list of links to the models or objects that

have been changed or created since a specific date.


288

3.5.3.11 Configure OIS user management (Oracle Business Process Publisher Server)

If you manage users via an OIS system, authentication is performed

using this system. To authenticate via the OIS system, you must

adapt the configuration file.

Prerequisite



Procedure




with a text editor.

2. Find the <LoginModuleSection> tag. Set the value OISLogin,

i.e. <LoginModuleSection value="OISLogin"/>.

3. Open the file oisconfig.cfg in the Oracle Business Process



with a text editor.

4. Find the <oisproviderurl> tag. Specify the URL for the OIS

system and the correct port number in the form of

http://192.168.3.4:7001. The default port is 7001, e.g.

<oisproviderurl value="http://192.168.3.4:7001">.

5. Save the changes and restart Oracle Business Process Publisher

Server.

The Oracle Business Process Publisher administrator can now map

Oracle BPA Suite user groups to OIS user groups.

3.5.3.12 Use an Oracle database (Tomcat)


Publisher in combination with Apache Tomcat Web application server

and an Oracle database. If you use this database, all enabled users

can work simultaneously with a Publisher export. This description

assumes you are using Apache Tomcat.


289

Prerequisite

You have created an Oracle database and configured it as follows.

If you install a database yourself, always follow the instructions



Repository and Oracle Business Process Publisher. This keeps the

two systems from competing for resources, and you achieve

better performance and higher availability.





You have created two tablespaces: ARISBPDATA (for table

data) and ARISBPINDEX (for index data). To use other

names or existing tablespaces, you must customize the

configuration file webappserver.cfg (see below). We

recommend that you set the tablespaces for automatic,

unlimited growth. Otherwise, you run the risk of completely

exhausting the memory in the tablespaces, which may cause

important functions of Oracle Business Process Repository and

Oracle Business Process Publisher to fail. If the option for

automatic growth is not set, regular monitoring (e.g. weekly)

of the Oracle instance is required to ensure that the


















290

We recommend that you turn off the Oracle recycle bin

because large quantities of tables accumulate there when

exports are deleted.

Procedure




editor.



Files\Oracle BPA

Suite11\BPServer\tomcat\webapps\businesspublisher\"

debug="0" reloadable="false" crossContxt="true">




initialSize="10"





username="ARISBP" password="ARISBP" <!-- Use the

Oracle user name and password here (see Prerequisites> --

>






</Context>




with a text editor.






291





<env-entry>


Class</description>

<env-entry-name>DatabaseDAOClass</env-entry-

name>


<env-entry-value>

com.idsscheer.aris.businesspublisher.application.dao.database.

AOracleDAO</env-entry-

value>

</env-entry>

4. Ensure that the JDBC driver ojdbc5.jar exists in the Oracle

Business Process Publisher Server installation directory

..\BPServer\tomcat\common\lib. We assume that you are

using version 10.2.0.3. You find the file on the installation media.

Note







3.5.3.13 Oracle restart

After restarting the ORACLE server, links to the database may no

longer function, which will lead to errors when used by Oracle

Business Process Publisher. You can exclude this source of error

by testing the connections of the connection pool via query in

advance. The query is already commented out and included in the file

businesspublisher.xml. You need to insert the query as a value.


292

Procedure




editor.

2. Locate the <Resource name= tag.

3. Add the following value after the last value:

validationQuery="select 'Y' from dual.


As of now, the connections to the database will be tested. If they are

no longer correct, a new connection is established.

3.5.4 Manage reports

Administrators can manage reports in the administration interface of

exports.

Prerequisite

You have exported report scripts and observed the following:

The reports only evaluate the contexts Database, Group, Model,

or Object.

The reports do not call any dialog boxes.

The reports only require read access to items.

If you use a report template to create the reports in design view,

the prerequisites mentioned above are automatically met.

The reports only contain methods allowed for Oracle Business

Process Publisher.

Note

Normally, you cannot use the report scripts provided with Oracle BPA

Suite. Some of these reports are interactive and use methods that are

not supported by Oracle Business Process Publisher. If the

prerequisites for Oracle Business Process Publisher reports are not

met, an error message is output during report execution.

Procedure

Add report

1. Log in as a system administrator or administrator. The export

administration opens.


293

2. In the Reports module, click on Add.

3. Click on Browse, and select the report export file (*.arx) of the

relevant report.

Export files are created when you export a report script from

Oracle Business Process Architect, for example. Reports provided

here must meet the prerequisites.

4. Click on Upload.

Report name, description, and context are displayed in the table.

Users can run newly added reports only after they log in again.

Tip

If you need additional evaluation scripts, you can create report

outputs based on a report script template in design view. If you are

familiar with the JavaScript and Oracle BPA Suite Script

programming languages, you can create user-defined evaluation

scripts or adapt existing scripts.

Delete report

Click on Delete .

The report is removed from the list.

3.6 Java clients (browser mode)

This section describes the requirements and the setup, setting

options, and execution modes for starting Oracle BPA Suite products

via your browser (as Web clients) rather than starting them as

applications.

Make sure that one of the approved JRE versions is installed on all

computers and the specific system requirements (Page 265) are met.

JRE

The following are approved: Java Runtime Environment (JRE)

1.6.0_04 and subsequent patches that are in the public domain (Java

SE on the SUN home page except Java SE for Business) and generally

released by SUN.

To display different character sets (Japanese, Arabic, Cyrillic, etc.),

the corresponding file in directory <JRE installation


example, if you wish to display Japanese characters, you must



294

Note

SUN renamed the JRE versions. JRE 1.6.0_04 is now called JRE 6.0,

Update 4. Approvals are also valid for subsequent updates.

Oracle BPA Suite products are tested using the JRE that is current at

the time of release.

If JRE 1.6.0_04 and subsequent patches are approved for an

Oracle BPA Suite product, the approval is valid for both JRE

1.6.0_04 and JRE 1.6.0_05 and for any subsequent patch from

the public domain Java SE of the SUN home page (except for

Java SE for Business). SUN Microsystems guarantees compatibility

between the JRE patch levels. Therefore, the Oracle BPA Suite

approvals for JREs are valid for all patch levels of a version.

If you are using JRE 1.6 update 3 or an older version, copy the file

jaxb-api.jar from the directory <Web Client Components>\lib

to the directory <Java JRE installation directory>/endorsed,

e.g. C:\Program Files\Java\jre1.6.0_01\lib\endorsed.

If the directory endorsed does not exist, you must create it.

Please note that you must repeat this procedure for every update

of version 3 or older. We therefore recommend installation of

version 4 or higher.

If you have Java 6 update 10 installed, problems may occur

despite better performance. Depending on your graphics card and

driver configuration, installation of Java 6 update 10 may cause

delays in the Designer and Matrices modules.

In this case, use the following command line entry to start the

program:


IIS 6.0 on Windows Server 2003

If you installed Internet Information Server 6.0 (IIS 6.0) with default

settings, please proceed as follows to display the files listed below.

Procedure

Oracle Business Process Architect: Register the cfg MIME type

with the Web server. Only then can the arisloader.cfg file be

used.

Web Publisher exports: For the Web site on which the Web

Publisher exports will run, enter the text/html MIME type for the

properties file type. This allows Web Publisher export files to be

identified.


295

3.6.1 Set up Java clients for browser use

This section provides you with information on the setup, setting

options, and execution modes that are important for using Oracle BPA

Suite products in a browser environment.

Procedure

1. Ensure that the system requirements are met.

2. Install the Web Client Components (see Installation Guide).

3. Install a JRE approved for Oracle BPA Suite. Ensure that the

directory name of the path does not contain any spaces or special

characters, or otherwise the JRE cannot be run.

Navigate to the Web Client Components installation directory

using your browser. If the Web Client Components are set up, you

will find the link to the HTML test page at the end of the

multilingual index page.

When you navigate back to the Web Client Components

installation directory using your browser, the database list of the

linked Oracle BPA Suite Site is displayed.

4. Pass the link on to users who want to work with Oracle Business

Process Architect, for example, the link to the index_lan.html file.

3.6.1.1 Installed files of Oracle BPA Suite

By default, the files you need to download the Java-based products to

your computer are installed in the directory

%BPAHOME11g%server/html/lib. You need the downloaded JAR

files to run Java-based products. The file arisloader.cfg is saved in

the directory %BPAHOME11g%server/html/config. This file

controls the download of Java-based products if you click on a

database shortcut on the home page.

Here are some examples of entries in the arisloader.cfg file:

# Versioninfo # ARIS_Version=11g.0.260956 # File_Version=1 # Use variable DownloadClientPath to override the default directory where the files # of the ARIS Download Client are stored # Sample: # DownloadClientPath=C:Download Client DownloadClientPath=


296

# DO NOT EDIT THIS SECTION! # Main Start Class jvmOptions=-Xms64m -Xmx256m -XX:NewSize=32m -XX:MaxNewSize=64m # External Libraries jar=CcConfig.jar jar=CcLicense.jar jar=CcSaxpath-1.0.jar jar=ChartDirector.jar jar=CnvConnect.jar jar=CorticonFoundationAPI.jar jar=JimiProClasses.jar jar=activation.jar jar=ant-launcher.jar jar=ant.jar jar=antlr.jar jar=bsscjhrs.jar jar=castor-1.0.5.jar jar=commons-collections-3.2.jar jar=commons-configuration-1.3.jar jar=commons-dbcp-1.2.1.jar jar=commons-discovery.jar jar=commons-lang-2.2.jar jar=commons-logging.jar jar=commons-pool-1.3.jar jar=ejb20.jar:ignore jar=iText-2.0.7.jar jar=iTextAsian.jar jar=jaxb.jar jar=jdo2-api-2.0.jar jar=jdom.jar jar=jh.jar jar=jide-develop.jar jar=js.jar jar=log4j-1.2.14.jar jar=lucene-analyzers-2.2.0.jar jar=lucene-core-2.2.0.jar jar=lucene-highlighter-2.2.0.jar jar=mail.jar jar=ociplugins.1.0.0.jar jar=orbacus.4.3.2.jar jar=org.eclipse.core.resources_3.2.2.R32x_v20061218.jar jar=org.eclipse.core.runtime_3.2.0.v20060603.jar jar=org.eclipse.emf.common_2.2.1.v200705141058.jar jar=org.eclipse.emf.ecore.change_2.2.1.v200705141058.jar jar=org.eclipse.emf.ecore.xmi_2.2.3.v200705141058.jar jar=org.eclipse.emf.ecore_2.2.3.v200705141058.jar jar=org.eclipse.emf.edit_2.2.2.v200705141058.jar jar=org.eclipse.equinox.common_3.2.0.v20060603.jar jar=org.eclipse.osgi_3.2.2.R32x_v20070118.jar jar=poi-3.0.2.jar jar=qname.jar jar=simulationstepcache-1.0.0.jar jar=tools.jar jar=wsdl4j.jar jar=xercesImpl.jar


297

jar=xml-apis.jar jar=y-annotations-1.jar jar=y-graphics-3.jar jar=y-graphlayout-2.jar jar=y-guiframework-6.jar jar=y-lipo-1.jar jar=y-reportdesigner-client-2.jar jar=y-reportdesigner-common-2.jar jar=y-reportexecution-2.jar jar=y-utils-2.jar jar=y.jar # ARIS Client jars jar=arismethod.jar jar=cl_locale.jar jar=cl_locale_de.jar jar=cl_locale_en.jar jar=client.jar

Use the DownloadClientPath= entry or the BPAHOME11g=

environment variables to specify the directory on your computer to

which the files of the Java-based products are copied after startup.

The setup of ARIS Toolset enters for variable BPAHOME11g= the

path to the installation directory of ARIS Toolset. BPAHOME11g= is

an environment variable of the client computer and not an entry in

the file arisloader.cfg.

Note

Please do not use any country-specific special characters in the path

for BPAHOME11g= or DownloadClientPath=.

The entry and environment variables are queried in the following

sequence:

1. The DownloadClientPath entry in the file arisloader.cfg is

checked. If a directory is assigned to this entry, the JAR files are

copied to that directory.

2. If no directory is assigned to this entry, the system searches for

the BPAHOME11g environment variable. If the system finds it,

the JAR files are copied to the directory specified there.

3. If the environment variable is not found, the JAR files are copied

to the directory <installation directory>\Oracle BPA

Suite<Version>\DownloadClient.

The BPAHOME11g= environment variable allows you to copy the

JAR files to any directory on any client computer.


298

3.6.1.2 Language update and character sets

A language update for the Web Client Components and Oracle BPA

Suite Server enters the language resource files in the arisloader.cfg

file in the installation directory. As a result, a language update is

performed automatically when a Java-based product opens a

database.

To display different character sets (Japanese, Arabic, Cyrillic, etc.),

the corresponding file in the installation directory must be called

font.properties.

For example, if you wish to display Japanese characters, you must


3.6.1.3 Execution as application or applet

We recommend that you run Java-based products as an application to

prevent errors caused by your browser. You can install Java-based

products as a client or launch them as an application via a browser as

described below.

During installation, the directory \template\htmlgen is created in

which the files aris_database_lan.html (index_lan.html) and

aris_database_app.html (index_app.html) are stored.

The lines for starting Java-based clients differ as follows:

File aris_database_lan.html (index_lan.html) for starting Java-

based clients as applets:

var appletmode = (args['appletmode'] ? args['appletmode'] : "applet");

File aris_database_app.html (index_app.html) for starting Java-based

clients as an application:

var appletmode = (args['appletmode'] ? args['appletmode'] : "javaapp");

Warning

If you start a Web client via Internet Explorer, for example Oracle

Business Process Architect, the Java call remains open in the

background. As a result, you may not be able to start a second Web

client.

Even if you are able to start multiple Web clients, we recommend that


299

you start only one Web client at a time because simultaneous access

of multiple Web clients to one Java instance may lead to loss of data

and program crashes.

3.6.1.4 Provide additional memory

If you use Java-based products as applets, you can provide them with

additional memory. This is recommended if you use memory-

intensive, user-defined symbols in your databases, for example.

Tip

This setting affects all Java-based programs.

Go to the control panel, open the Java control panel, and change the

Java applet runtime settings by entering the required Java runtime

parameters for the JRE version you are using. To provide 256 MB of

memory (recommended), enter -Xmx256m.

3.6.1.5 Installation by software distribution

Warning

As a consequence of changing the standard installation as described

in this section, updates or other changes by the Oracle BPA Suite

installation program are no longer possible. They would have to be

made manually.

Generally, the following applies: The cid.bin file must not be

distributed because all clients will otherwise be identified as one and

the same client. Since the file is newly created when the client is

started, there is no need to distribute it.

After starting the Oracle BPA Suite products, you will find the cid.bin

file in the BPA11 subdirectory of the user profile (%userprofile%).

You can copy the JAR files of a Java-based product from the directory

Oracle BPA Suite11g/DownloadClient to a directory on the client

computer via software distribution. In the file arisloader.cfg, you

can then assign the BPAHOME11g environment variable to the

DownloadClientPath= entry for this path.


300

3.6.1.5.1 Possible settings for user.cfg

You can specify the following settings in the user.cfg file:

You can specify configuration settings, such as the default filter or

grid width, for example.

You can set up sample Java-based products and copy the

generated user.cfg file to the directory <installation

directory>\server\html\config\oem02. You must delete the

session ID in that case.

3.6.1.5.2 Preconfigured user.cfg

When Oracle Business Process Architect is installed for the first time

(Page 295), the internal user.cfg file is used when the application is

first started.

3.6.1.5.3 Configure user.cfg

If Oracle Business Process Architect finds the user.cfg or user.tmp

file in the config directory of your Web Client Components

installation, it uses this file instead of the preconfigured file (Page

300) user.cfg.

Procedure

1. Switch to the config directory of your Web Client Components

installation.

2. Open the file user.cfg with a text editor, enter your data (Page

300), and save the file under the name user.cfg. You can update

these files simultaneously via software distribution.

3.6.2 Start a second Java-based product in the browser

If you start Oracle Business Process Architect in the browser, for

example, the Java applet runs in the background in Internet Explorer.

But if you try to start a second Java-based product, such as ARIS

Business Optimizer, in the same manner, the Java applet that is still

active prevents it.

To open the second Java-based product, you must close the browser,

which terminates the Java applet, and open the browser again. You

can then start ARIS Business Optimizer in the browser.


301

3.6.3 Automatically update installed Web clients

You can set up a virtual directory on your Web server that the

installed Web clients can access to download newer versions. If you

update the virtual directory on your Web server by running a patch

setup, the Web clients will automatically download the current files

when the setup is run.

The automatic update is only performed for Java-based products.

Local standard database system installations are not updated.

3.6.3.1 Preparations for the automatic update

To perform an automatic update, create a virtual directory on your

Web server for which you enable client access.

Procedure

1. Install the Web Client Components (see user-defined installation

of Oracle Business Process Repository in the Installation Guide) on

your Web server.

2. Create a virtual directory that is mapped to the installation

directory of the installed Web Client Components. Assign a name

to the Web directory, e.g. ARIS_autoupdate.

3. Test the auto-update URL, such as

http://WebServer/BPA_autoupdate, by entering

http://WebServer/BPA_autoupdate/config/arisloader.cfg

in any Web browser. If the content of the arisloader.cfg file is

displayed, continue with the next step.

Communicate the URL; in our example http://WebServer/

BPA_autoupdate.

If you update the ARIS Web Client Components of your Web server

using a patch setup, the Web clients you set up will automatically

download the updated files at the next startup.

3.6.3.2 Set up web clients for automatic update

For installed Web clients, you can configure the system to search a

URL for current program files at startup. If current files are available,

they will be downloaded.


302

Procedure

1. Start the Web client and click on View/Options.

2. In the tree view, click on Automatic updates.

3. Enable the Enable automatic updates check box.

4. Enter the URL for the automatic Oracle BPA Suite update, in our

example http://WebServer/BPA_autoupdate.

5. Enable the Test connection check box.

Click on OK to close the options. If a connection cannot be

established, you receive a corresponding message. In this case,

correct the URL.

Every time the Web client is started, the specified URL is checked for

updated program files. If any are available, they can be downloaded.

3.7 Central user login using LDAP

The security level of this user authentication system meets the

highest standards. If you want the user login to fulfill higher security

requirements than the standard user management, we recommend

that you use LDAP authentication. If users are authenticated by an

LDAP server rather than the Oracle BPA Suite database,

administration is simplified since you only create user groups in the

database and assign access and function privileges to them. With this

'single point of login', the user names and passwords only need to be

maintained in the LDAP system, which avoids redundant passwords.

Moreover, if you delete an LDAP user or change his password, you

can prevent that user from accessing any of the Oracle BPA Suite

databases that use the LDAP login process.

Note

If LDAP authentication is enabled, users that have been created in the

database can no longer log in. The system user system is an

exception. Unlike all other users, the system user system is never

authenticated via the LDAP system. If the LDAP servers are down and

databases cannot be accessed, you can still log in as the user

system.

Make sure that user names in the LDAP system contain only valid

characters and that users use secure passwords. Alphanumeric

characters, spaces, and the following characters are allowed in user

names: . - _ ! " § $ % & / ( ) = ? * + # < > , ; :


303

Due to significant differences in the various LDAP systems, no general

configuration and connection description can be provided. Applicable

restrictions and parameters depend on the particular system used. To

connect LDAP, comprehensive knowledge of the relevant system is

required.

We therefore cannot guarantee proper functioning of Oracle BPA Suite

in combination with different LDAP systems. Windows Server 2003

Active Directory has been tested and approved; therefore, the

documentation refers to this system. All other LDAP system

connections required for specific projects are available from our Field

Support on request. Please note that any customization required by

manufacture or customer is not covered by the standard software

maintenance and maintenance contract of IDS Scheer AG.

To authenticate users via LDAP, you need to install an LDAP server

and adjust your databases. The LDAP server software can be

downloaded free of charge from the Internet or purchased.

You find general descriptions on the following pages.

3.7.1 Configure LDAP server operation

To enable user authentication via your LDAP system, you must

change database properties.

Prerequisite

You have the Database management function privilege.

You have installed an LDAP server.

You have created user groups in the databases and assigned

function and access privileges to them.

Procedure

1. Click on Administration in the Modules bar, and log in to the

database.

2. Click on the Properties button, and correctly maintain all data on

the Properties - Database/Authentication system/LDAP

settings pages. The program is unable to verify whether your

entries are correct. Follow the instructions in the dialog boxes.

Help on using wizards and dialog boxes is available directly in the

user interface.


304

3. On the Filter and import properties page, enable the

Automatically import users at login check box and, if

necessary, select a user group. As a result, authenticated LDAP

users are automatically created as users in the database during

their first login.

If you do not select this option, you need to import LDAP users in

the database.

4. Map LDAP user groups to Oracle BPA Suite user groups.

From now on, the user is authenticated via the LDAP server.

3.7.2 Set Oracle Business Process Repository for LDAP server operation with SSL

Procedure

1. Install the LDAP server you want to use. Always refer to your

LDAP system documentation because installation varies from

system to system.

2. Obtain the SSL certificate for your LDAP system. To do so, consult

your LDAP system documentation.

3. Import the certificate using the program Keytool.exe. The

program is located in the Oracle BPA Suite server installation

directory>\server\jre\bin directory.

4. Enter the path to the Oracle BPA Suite server installation directory

as the keystore parameter. Example: You have installed Oracle

BPA Suite Server in the directory C:\Program Files\Oracle BPA

Suite 11\server\. The program could be called as follows:

Please note that you need to replace the terms in angle brackets

(< >) with the actual terms without angle brackets:

keytool.exe -keystore C:\Program Files\Oracle BPA Suite

11\server\jre\lib\security\cacerts -storepass changeit -import -

alias <dc> -file <path>\<certificate file>

Now you need to specify the following settings for each database

whose users are to log in using the LDAP server.

5. In Oracle BPA Suite, log in to the database that is managed on

this Oracle Business Process Repository.

6. Right-click on the name of the database, and select

Properties/Authentication system/LDAP

settings/Connection.


305

7. Enable the Use SSL check box and ensure that the correct value

is maintained in the Port box.

The connection to the LDAP system is established via SSL.

3.8 Data backup

Administrators have various options for backing up your data that is

managed on an Oracle Business Process Repository.

Every time Oracle Business Process Repository is launched, the

configuration files are backed up in the file backup_sysconfig.zip.

This file is saved in the sysconfig directory. If required, you can open

this file using an extraction program and restore the files of the

sysconfig directory.

Database

In Oracle Business Process Architect, using the Backup

functionality in the pop-up menu of a database.

In Oracle BPA Suite Admintool (Page 312), using the Backup

(Page 316) command.

In Oracle BPA Suite Site Administrator, using the Backup

functionality in the pop-up menu of a database.

Filters

In Oracle Business Process Architect, using the Export

functionality in the pop-up menu for a filter (individual backup).

In Oracle BPA Suite Admintool (Page 312), using the

Backupconfig (Page 319) command.

Method, configuration, and queries In Oracle BPA Suite Admintool (Page 312), using the

Backupconfig (Page 319) command.

Scripts In Oracle Business Process Architect, using the Export

functionality in the pop-up menu for a script (individual backup).

To back up all scripts and macros for an Oracle Business Process

Repository, save the directory <Oracle BPA Suite installation

directory>\server\templates with all its subdirectories.


306

When you perform an update, make changes to a program, add

languages, or uninstall a component, the relevant files and directories

are backed up. A selection of files is listed here to provide examples:

In a client installation in directory <Oracle BPA Suite installation directory>\backup<date>: Files from <Oracle BPA Suite installation

directory>\LocalServer\data (user databases, when

uninstalling)


directory>\LocalServer\sysconfig

Directory <Oracle BPA Suite installation directory>\html

Directory <Oracle BPA Suite installation directory>\script

In a server installation in directory <Oracle BPA Suite installation directory>\server\backup

Files from <Oracle BPA Suite installation

directory>\server\data (user databases, when uninstalling)


directory>\server\sysconfig


directory>\server\templates

Note

User attributes of the Free attributes attribute type group from

previous Oracle BPA Suite versions are no longer used as of version

11g. You can now customize attribute type groups and attribute

types.

To be able to apply user attributes from previous versions, you must

import the filters of the previous version containing all user attributes

of the database. These user attributes are only created and thus

visible once the filters have been imported. Subsequently, restore the

database of the previous version on your current Oracle Business

Process Repository.

Alternatively, you can also use Oracle BPA Suite Converter. Please

note that you can only view user attributes in the current Oracle BPA

Suite version if you have imported the corresponding filters from the

previous version.


307

3.8.1 Transfer data from earlier Oracle BPA Suite versions

This chapter provides information on data transfers from databases of

Oracle BPA Suite 10.1.3.1 and higher.

What data will be transferred?

You can continue to use data from Oracle BPA Suite 10.1.3.1 and

higher. Using Oracle BPA Suite Converter, you can transfer user

databases and configuration databases.

Transfer databases

User databases contain the structural and process-oriented

organization of your company, for example. The contents of user

databases can be transferred in their entirety using Oracle BPA Suite

Converter.

Procedure

1. Create a backup copy of your databases.

2. Ensure that the Oracle Business Process Repository has been

launched with access to the databases. The data to be transferred

can exist locally within an Oracle BPA Suite installation or on the

network.

3. Click on Start/Programs/Oracle BPA

Suite/Administration/Oracle BPA Suite Converter 11g if you

installed Oracle BPA Suite in the program group suggested by the

installation program. The Oracle BPA Suite Converter Wizard

opens.

4. Select the Oracle BPA Suite Server on which the converted

database is to be saved. To add a server to the list, click on Add.

Enter the server name and click on OK.

5. Click on Next.

6. Enable the option button for the Oracle BPA Suite version to be

used as the source for conversion.

7. Click on Next.

8. Select the source containing the Oracle BPA Suite user database

that you want to transfer to your new Oracle BPA Suite

installation.


308

Based on your settings you now have one or several of the following

options.

Oracle BPA Suite Network server

Select an Oracle BPA Suite server in the Network server box. To

add a server to the list, click on Add. Enter the server name and click

on OK.

Local system

Local database directory: Enable the Local option button.

Note

To convert databases locally (LOCAL server), you need to launch the

LOCAL server of the appropriate Oracle BPA Suite version before

starting Oracle BPA Suite Converter. To start LOCAL, click on LOCAL

in the tree view in the Explorer module.

Procedure

1. Click on Next.

2. Select the user database you would like to transfer.

3. Click on Next.

a. Enable the check boxes for the configuration database items

you wish to transfer. Enabling all check boxes has the

following effects:

b. Items and method extensions in the configuration database on

the source server will be transferred, if they do not exist on the

target server.

c. Existing items and user-defined symbols in the configuration

database on the target server will be overwritten with items

and user-defined symbols having identical GUIDs.

d. Names of user-defined symbols, free attributes and units of

free attributes that already exist in a certain language in the

configuration database on the target server will be overwritten.

e. Assignments of attributes to attribute type groups that already

exist in the configuration database on the target server will be

overwritten.

f. Items and method extensions in the configuration database on

the target server remain unchanged if they do not exist on the

source server.


309

User-defined symbols are always transferred. You cannot

disable this check box.

4. Click on Next.

5. Enter the database administrator password and the password for

the configuration database of the source server.

6. Click on Next.

7. Enter the database administrator password and the password for

the configuration database of the target server.

8. Click on Next.

9. Check the settings you specified in the wizard. To start data

transfer, click on Finish. The converted database is saved. If the

name of the converted database already exists on the target

server, a number is added to the name of the converted database.

Once the data transfer has been completed successfully a

message appears.

10. Click on OK.

Oracle BPA Suite Converter closes.

3.8.1.1 Configuration

Method and evaluation filters, templates, font formats, and chart

definitions are managed in the configuration. The contents of the

configuration are available to all user databases on a given server.

You can transfer individual configuration items.

3.8.1.1.1 Transfer item groups of the configuration

You can use Oracle BPA Suite Converter to transfer all or individual

item groups, such as filters or model templates, from the

configuration of Oracle BPA Suite 10.1.3.1 and higher.

Tip

The procedure description and the Select configuration data wizard

page of the online help for Oracle BPA Suite Converter include

instructions for selecting individual item groups.

When you transfer item groups with Oracle BPA Suite Converter,

the reference to the respective database is not affected. In other

words, the assignment of user-defined symbols to objects in the

databases still exists, for example.


310

3.8.1.1.2 Transfer exported filters, font formats, languages, and templates

You can transfer filters, templates, and chart definitions that you have

exported in XML format (ACC, AMC, and ATC files).

The following description refers to Oracle Business Process Architect.

Procedure

1. Run Oracle Business Process Architect.

2. Activate the Administration module.

3. In the navigation bar, click on the plus sign (+) next to the server

into whose configuration you wish to import the filter, font format,

language, or template.

4. Open the Configuration/Conventions database item.

5. Right-click on Filter, Font formats, Languages or Templates and

select Import. The Import dialog box opens.

6. Select the import file and, if required, decide how conflicts are to

be solved during import by enabling the relevant check boxes.

7. Click on OK.

3.8.1.2 Transfer custom or modified scripts of previous Oracle BPA Suite versions

You can import user-generated or modified scripts and semantic

checks that you wrote in JavaScript in previous Oracle BPA Suite

versions. Use Oracle BPA Suite Script Converter to transfer VB scripts

and import converted scripts to the required Oracle Business Process

Repository.

Procedure

1. Copy the VB scripts to the appropriate script directories of the

directory Oracle BPA Suite <installation directory>\script.

2. Run Oracle BPA Suite Script Converter (Start/Programs/Oracle

BPA Suite/Administration/Oracle BPA Suite Script

Converter 7.1).

3. Click on Select scripts. The Select scripts to be converted

dialog box opens.


311

4. Navigate to the appropriate script directory, select the scripts to

be converted, and click on Open.

5. Repeat the script selection for all relevant directories. The selected

scripts are listed in the Oracle BPA Suite Script Converter output

window.

Click on Convert. Oracle BPA Suite Script Converter updates all

scripts in the list and removes them from the output window. A

message is displayed when the update is complete.

Note

If not all scripts have been updated, you are informed which scripts

are affected and why Oracle BPA Suite Script Converter did not

update them.

For example, write-protected scripts cannot be updated. Scripts that

are not updated remain on the list.

3.8.2 Back up users and configuration

To back up the entire content of a database server, you proceed as

follows.

Procedure

1. Use Oracle BPA Suite Admintool to back up all user databases.

Use the BPAadm11 backup all <directory> command if you

use the Oracle BPA Suite Admintool in interactive mode.

2. Use Oracle BPA Suite Admintool to back up configuration data.

Use the BPAadm11 backupconfig <directory> command if you

use the Oracle BPA Suite Admintool in interactive mode.

Tip

It is also possible to back up user databases online. The Oracle BPA

Suite System Maintenance and Administration training session

provides instructions on backup procedures and concepts. For

additional information, please contact Oracle Corporation support.


312

3.8.3 Automatic backup of current configuration files

Every time Oracle Business Process Repository is launched, the

configuration files are backed up in the file backup_sysconfig.zip.

This file is saved in the sysconfig directory. If required, you can open

this file using an extraction program and restore the files of the

sysconfig directory.

3.8.4 Save method changes

Running the Backupconfig (Page 319) command in Oracle BPA Suite

Admintool (Page 312) backs up all data for the configuration and

method of an Oracle Business Process Repository. You can restore it

using the Restoreconfig command.

3.9 Data management with Oracle BPA Suite Admintool

You can use Oracle BPA Suite Admintool commands (Page 313) to

manage the Oracle BPA Suite databases of a server and to change

administrator passwords, for example. The program is a console

application and runs in the MS DOS input window. The individual

commands of the program are supplied as command line parameters.

The program provides information on the success and effect of each

command executed.

Warning

As a basic rule, Oracle BPA Suite databases should not be edited

using Windows Explorer. If you rename database folders or copy files,

this may result in program malfunction.

For example, if you use scripts for daily backups, we strongly

recommend that you protect these scripts at the operating system

level because passwords are unencrypted.

You can start Oracle BPA Suite Admintool from any client computer

and access the databases on the server:

Click on Start/Programs/Oracle BPA

Suite/Administration/Oracle BPA Suite Admintool 11g if you

accepted the program group suggested by the installation program.

The MS DOS input window opens and Oracle BPA Suite Admintool is

launched in interactive mode.


313

3.9.1 Start Oracle BPA Suite Admintool

You can start Oracle BPA Suite Admintool from any client computer

and access the databases on the server:

Click on Start/Programs/Oracle BPA

Suite/Administration/Oracle BPA Suite Admintool 11g if you

accepted the program group suggested by the installation program.

The MS DOS input window opens and Oracle BPA Suite Admintool is

launched in interactive mode.

3.9.2 Oracle BPA Suite Admintool commands

In this section, all program commands are listed with their syntax

both in interactive mode (Start/Programs/Oracle BPA

Suite/Administration/Oracle BPA Suite Admintool 11g) and

outside of interactive mode.

To work outside of interactive mode, you need to enter a command to

navigate to the Oracle BPA Suite installation directory (for example,

to the directory C:\Program Files\Oracle BPA Suite).

Note

To use Oracle BPA Suite Admintool outside of interactive mode, you

must enter the parameter Oracle Business Process Repository, as well

as passwords.




Parts of commands that are enclosed in angle brackets must be

replaced with the appropriate designations or names. Example: In the

Backup all <directory> command, you replace <directory> with

the name of an existing directory. For example, this command could

be: backup all e:\backup

Parts of commands that are enclosed in square brackets are optional,

i.e., you can use these if you need to.

Example: delete [<database name>] [all]

After the command, you can either enter a database name or use all

to specify that all databases be deleted.

If parameters include spaces you need to enclose the parameter in

quotation marks.


314

If you want to create the Sales data database with the name Sales

data 2005, for example, enter the following:

Interactive mode copy Sales data "Sales data 2005"

Outside of interactive mode BPAadm11 copy Sales data "Sales data 2005"

Syntax

A command line in Oracle BPA Suite Admintool has the following

syntax:

BPAadm11 [<option>] <command> [<command argument 1>] ...

The following options can be used in Oracle BPA Suite Admintool:


315

Option Description

-s <server name> Indicates the server on which the

command is to be performed. In

interactive mode, the server can be

changed via the server command.

-p <password> Indicates the database administrator

password for the specified server. If the

password is not correct, the program will

prompt you to enter the correct password

before the selected command can be

performed. The default password is

DBADMIN (uppercase).

-pc <password> Indicates the configuration administrator

password for the specified server. If the

password is not correct, the program will

prompt you to enter the correct password

before the selected command can be

performed. The default password is

CFGADMIN (uppercase).

-pa <password> Indicates the Site Administrator password.

The default password is SITEADMIN

(uppercase).

-l <file name> Activates logging of all program

operations. The log file indicates which

operation was performed at what time and

with what result.

-cf <command file> Specifies the command file with

executable commands that is to be

started.

-sc <schema context> Indicates the context of the schema.

Oracle BPA Suite is set as the default.

-u <user> <password> Specifies the alternative password for the

system user.


316

Notes

When working with Oracle BPA Suite Admintool, please observe the

following:

If you are working with Oracle BPA Suite Admintool on the server

computer, use the -s localhost parameter.

If you have not entered a password, you will be prompted to

supply the Database Administrator password before each

command is executed.

If you use values with special characters (e.g. '&' in the

password), you need to enclose the value in quotes. For additional

information, please refer to the help and support center for your

operating system.

On the server, system messages in Oracle BPA Suite Admintool

are always output in the Oracle BPA Suite installation language.




3.9.2.1 Backup

Backs up a database as a compressed file with the ADB (Oracle BPA

Suite database) file extension to a folder of your choice.

Oracle BPA Suite databases may contain your company's

organizational structure and business processes, for example. The

contents of these databases are subject to constant development.

Every time a user opens a database and supplements a model for

example, important information is added. To avoid the risk of losing

this data, it is recommended that you back up your user databases

every day.

To back up a database as an ADB file, enter the following command

call and press Enter:

backup <database name> <backup directory>

The name of the backup file consists of the name of the database

and the appended file extension, ADB.


317

Warning

If a file of the same name already exists in the backup directory, it

will be overwritten.




You can use the following switch:

All: Backs up all databases on the selected database server.

To back up all databases on a server as ADB files, enter the following

command call and press Enter.

Interactive mode backup [<database name>] [all] <backup directory> [<new database name>]

Outside of interactive mode BPAadm11 backup [<database name>] [all] <backup directory> [<new database name>]

Using the Restore (Page 326) command, databases that have been

backed up as ADB files can be imported into and registered on a

server.

3.9.2.1.1 Example

The Project database to be backed up is located on the LOCAL

server. The database administrator password is DBADMIN. The

backup file is to be saved to the Backup folder on a data carrier.

Procedure

1. Run Oracle BPA Suite Admintool (Start/Programs/Oracle BPA

Suite/Administration/Oracle BPA Suite Admintool 11g). Oracle BPA

Suite Admintool is launched directly in interactive mode and you

can enter the desired command.

2. Enter the following command line and press Enter:

backup project e:\backup

Once you have identified yourself as the database administrator, the



318

3.9.2.1.2 Data backup using a batch program (batch file)

If you want to back up data automatically at a particular time every

day, Oracle BPA Suite provides support with the backup.cmd batch

program in the addons\ServerBackup directory on the Oracle BPA

Suite installation media. This program can be run regularly using time

control software.

To perform time-controlled data backups, copy the file backup.cmd

to <Oracle BPA Suite installation directory>\JavaClient. Then

use the time control software to specify the times at which the data

backup is to be performed. All registered databases will be backed up

at the specified time to the directory you previously entered in the

backup.cmd file.

Warning




3.9.2.2 Backupasn

Saves a database as a compressed file with the file extension ADB.

Extracts the status of the specified change list number <asn> from a

versioned database <dbname> to an ADB file of the <archivedir>

directory. Instead of <asn>, <head> or <work> can be used.

<head> stands for the last versioned state and <work> for the

current state that is not versioned yet.

Databases may contain your company's organizational structure and

business processes, for example. The contents of these databases are

subject to constant development. Every time a user opens a database

and supplements a model for example, important information is

added. To avoid the risk of losing this data, it is recommended that

you back up your user databases every day.

To back up the state of a specific change list number of a versioned

database as an ADB file, enter the following command call and press

Enter:

backupasn <database name> <backup directory> <change list

number>


319

To back up the current state of a versioned database as an ADB file,

enter the following command call and press Enter:

backupasn <database name> <backup directory> head

To back up the state of a versioned database that is not versioned yet

as an ADB file, enter the following command call and press Enter:

backupasn <database name> <backup directory> work

The name of the backup file consists of the name of the database

and the appended file extension ADB.

Warning

If a file of the same name already exists in the backup directory, it

will be overwritten.

Using the Restore (Page 326), Restoreasn (Page 327), and

Restoreversioned (Page 327) command, databases that have been

backed up as ADB files can be imported in and registered on a server.

3.9.2.3 Backupconfig

Saves the Oracle BPA Suite configuration data (filters, templates, and

charts) to the specified directory in the appropriate file format.

To save the Oracle BPA Suite configuration data, enter the following

command call and press Enter:

Interactive mode backupconfig <backup directory> <new file name>

Outside of interactive mode BPAadm11 backupconfig <backup directory> <new file name>

To restore (Page 328) configuration files, use the Restoreconfig

command.


320

3.9.2.4 Configadminpassword

Changes the configuration administrator password.

To change the configuration administrator password, enter the

following command call and press Enter:

Interactive mode (the new password must not be entered in interactive mode, you will be prompted for it by the system) configadminpassword <current password>

Outside of interactive mode BPAadm11 configadminpassword <new password> <current password>

3.9.2.5 Copy

Copies databases to a server. To copy a database, enter the following


Interactive mode copy <source database name> [all] <target database name>

Outside of interactive mode BPAadm11 copy <source database name> [all] <target database name>

Optionally, you can specify the server to which you want to copy the

database by typing a colon behind the target database name and

adding the server name.

In batch mode, you can also enter the database administrator

password and specify that all databases are to be copied:

copy <source database name> <target database name> [all] [:<server>] [/<server password>]

Note

Database names must be unique. If a database already exists with

the name specified in the second parameter, the database cannot be

copied.

Example

The SalesDB database is to be duplicated on the LOCAL server. The

database administrator password is DBADMIN. The copy of the

database is to be named New salesDB.


321

Procedure

1. Run Oracle BPA Suite Admintool (Start/Programs/Oracle BPA

Suite/Administration/Oracle BPA Suite Admintool 11g).

Oracle BPA Suite Admintool is launched directly in interactive

mode and you can enter the desired command.

2. Enter the following command line and press Enter:

copy SalesDB "New salesDB"

If you have identified yourself as the database administrator, the


3.9.2.6 Createdb

Creates a new database.

Interactive mode createdb SalesDB

Outside of interactive mode BPAadm11 createdb SalesDB

3.9.2.7 Dbmspassword

Changes the password of the DBMS user. This change is helpful if the

DBMS (Database Management System) in use is also used by

applications other than Oracle BPA Suite. This may be the case with

the Oracle DBMS. The Oracle DBMS user is called ARIS71. The

default password is arisadmin (lower case).

To change the password of the DBMS user:

Interactive mode (the new password must not be entered in interactive mode, you will be prompted for it by the system) dbmspassword <current password>

Outside of interactive mode BPAadm11 dbmspassword <new password> <current password>.

3.9.2.8 Download

Saves log files, configurations or user login information from the

Oracle BPA Suite site to a selected directory.

Interactive mode download [logs] [configs] [accounting] <target directory> all


322

Logs stands for log files, configs for configurations and accounting

for user information.

Outside of interactive mode BPAadm11 download [logs] [configs] [accounting] <target directory>

3.9.2.9 Delete

Removes databases from the database server and deregisters them.

You can use the following switches:

All: Deletes all databases on the selected database server.

Force: Deletes the relevant databases even though users are still

logged in.

To delete a database from the selected database server, enter the

following command call and press Enter:

Interactive mode delete [<database name>] [all] [force]

Outside of interactive mode BPAadm11 delete [<database name>] [all] [force]

3.9.2.10 Exit

Exits interactive mode and closes the Oracle BPA Suite Admintool

window. The Exit command can only be executed in interactive mode.

To exit interactive mode as well as the program, enter the following

command call and then press Enter: exit

3.9.2.11 Help

Displays a help text for every available command. The help text

describes the actions that will be performed as a consequence of the

command, as well as the parameters that must be entered with the

command.

To call help for a specific command, enter the following command call

and press Enter:

Interactive mode help <command>


323

Outside of interactive mode BPAadm11 help <command>

To see an overview of help, enter the following command call and

press Enter. By pressing the Enter key, you can navigate through the

Help.

3.9.2.12 Interactive

Switches to interactive mode, in which you can enter several

commands in a prompt sequence without having to exit the program.

You need to log in to each server only once.

To enter a sequence of commands within the program, enter the

following command call outside of interactive mode and press Enter:

BPAadm11 interactive

3.9.2.13 Kill

Terminates a user's connection to databases on the selected database

server. This connection is identified by the connection ID that you can

display using the Sessions command.

Warning

All users whose connection to databases on the specified server was

terminated with the Kill function cannot properly exit Oracle BPA

Suite. Changes which have not yet been saved are lost and must be

made again after Oracle BPA Suite has been restarted.


all: Terminates all connections with databases on the selected

database server.

To terminate a user's connection to databases on the specified server,

enter the following command call and press Enter.

Interactive mode kill [<session ID>] [all]

Outside of interactive mode BPAadm11 kill [<session ID>] [all]


324

3.9.2.14 List

Displays all databases that are registered on a database server and

that can be opened by Oracle BPA Suite.


all: Lists all databases regardless of context. In this way, all

databases of the Oracle BPA Suite and Business Optimizer context are

output.

To display all databases that can be opened by Oracle BPA Suite,


Interactive mode list [all]

Outside of interactive mode BPAadm11 list [all]

3.9.2.15 Maintain

Starts maintenance for the specified database. Maintenance is

database system-specific, which means that a set number of

maintenance tasks is performed depending on the database. Refer to

your database management system documentation for information

regarding specific maintenance tasks.


all: Starts maintenance for all databases on the database server.

To perform maintenance for a database, enter the following command

call and press Enter.

Interactive mode maintain [<database name>] [all]

Outside of interactive mode BPAadm11 maintain [<database name>] [all]

3.9.2.16 Monitor

Shows all current server activities, such as backup or XML export, for

example.

To display the server activities, enter the following command call and

press Enter.


325

Interactive mode monitor

Outside of interactive mode BPAadm11 monitor

3.9.2.17 Password

Changes the database administrator password for the selected server.

First, the current password must be entered.

To change the database administrator password, enter the following

command call and press Enter.

Interactive mode password <new password> <current password>

Outside of interactive mode BPAadm11 password <new password> <current password>

3.9.2.18 Rename

Renames a database.


force: Renames the database even if users are connected to it.

To rename a database, enter the following command call and press

Enter.

Interactive mode rename <old database name> <new database name> [force]

Outside of interactive mode BPAadm11 rename <previous database name> <new database name> [force]

3.9.2.19 Reorg

Reorganizes a database.

Oracle BPA Suite searches the database for object and connection

definitions that do no longer have occurrences in models. These are

deleted.

If you are using an object library, you should not enable this option

since it may be possible and intended for certain definitions to exist

without having any occurrences.


326

A database can only be reorganized if no user is logged in to the

database.


all: Reorganizes all databases on the selected database server.

To reorganize a database, enter the following command call and press

Enter.

Interactive mode reorg [<database name>] [all]

Outside of interactive mode BPAadm11 reorg [<database name>] [all]

3.9.2.20 Restore

Imports individual databases that were backed up as ADB files, or

imports all ADB files of a directory to the current database server.

The database directory must not contain a database that has the

same name as the one to be imported. You are therefore given the

opportunity to rename the database when importing.


overwrite: Overwrites a database on the database server that has

the same name as the one imported.

To import one or more ADB files in a directory to a server and register

them there, enter the following command call and press Enter.

Interactive mode restore <backup file> [overwrite]

Directory with multiple ADB files:

restore <backup directory> [overwrite]

Outside of interactive mode BPAadm11 restore <backup file> [overwrite]


BPAadm11 restore <backup directory> [<new database name>] [overwrite]

To import an ADB file and rename the database at the same time,



327

Interactive mode restore <backup file> [<new database name>] [overwrite]

Outside of interactive mode BPAadm11 restore <backup file> [<new database name>] [overwrite]

3.9.2.21 Restoreversioned

Creates a versionable database <dbname> from an ADB file

<archive> of an unversioned database. Can also back up all adb/bdb

files of a directory. The overwrite option can only be used for backup

files of the current program version.

The database directory must not contain a database that has the

same name as the one to be imported. You are therefore given the

opportunity to rename the database when importing.






Interactive mode restoreversioned <backup file> [<database name>] [overwrite]


restoreversioned <backup directory> [overwrite]

Outside of interactive mode BPAadm11 restoreversioned <backup file> <database name> [overwrite]


BPAadm11 restoreversioned <backup directory> [overwrite]

3.9.2.22 Restoreasn

Creates a versionable database <dbname> of a specific state from

an ADB file <archive> of an unversioned database. Either a change

list number <asn> or head can be selected as the state. head

stands for the last versioned state. Can also back up all adb/bdb files

of a directory. The overwrite option can only be used for backup files

of the current program version.


328






Interactive mode restoreasn <ADB file> <change list numberasn> <database name> [overwrite] or restoreasn <archive> head <dbname> [overwrite]


restoreasn <backup directory> [overwrite]

Outside of interactive mode BPAadm11 <ADB file> <change list numberasn> <database name> [overwrite] or BPAadm11 restoreasn head <archive> <dbname>[overwrite]

3.9.2.23 Restoreconfig

Saves the Oracle BPA Suite configuration data (filters, templates, and

charts) to the specified directory in the appropriate file format.

To save the Oracle BPA Suite configuration data, enter the following


Interactive mode restoreconfig <path\file name>

Outside of interactive mode BPAadm11 restoreconfig <path\file name>

To back up ACB files, use the Backupconfig (Page 319) command.

3.9.2.24 Server

Can be run in interactive mode only. It terminates the current

connection to the server and permits connecting to another server. All

commands that are entered thereafter relate to the new server.

To terminate the current server connection and create a new one,

enter the following command call and press Enter:

server <server> [<password>]

You can enter the Site administrator password now or wait for it to be

requested later.


329

3.9.2.25 Sessions

Displays all users who are logged in to a database on the specified

server.

The following information is displayed:

TCP/IP host name of the computer that the user used when

logging in to the database

User name

Connection ID

Name of the application that established the connection

The user name displayed is based on the value specified in the

Username environmental variable of the computer from which the

user logged in to the database.

The information displayed can be sorted either by user name or

database name.

The following options are available for displaying information about all

current users of databases on the specified server.

Users sorted by user name:

Interactive mode sessions byuser

Outside of interactive mode BPAadm11 sessions byuser

Users sorted by process identifier:

Interactive mode sessions bypid

Outside of interactive mode BPAadm11 sessions bypid

Users sorted by database name:

Interactive mode sessions bydatabase

Outside of interactive mode BPAadm11 sessions bydatabase


330

3.9.2.26 Siteadminpassword

Changes the password of Oracle BPA Suite Site Administrator. The

default password after installation is SITEADMIN. This is case

sensitive.

To change the Site administrator password:

Interactive mode (the new password must not be entered in interactive mode, you will be prompted for it by the system) siteadminpassword <current password>

Outside of interactive mode BPAadm11 siteadminpassword <new password> <current password>

3.9.2.27 Statistic

Displays the following information for the evaluated database:

All models

All users

All font formats


all: Outputs all information about the database.

To display this information for one or all databases, enter the

following command calls and press Enter:

Interactive mode

Information about a database:

statistic <database name>

Information about all databases:

statistic all

Outside of interactive mode

Information about a database:

BPAadm11 statistic <database name>

Information about all databases:

BPAadm11 statistic all


331

3.9.2.28 Status

Displays the status of a client-server connection.

To display the status of a client-server connection, enter the following


Interactive mode status <server>

Outside of interactive mode BPAadm11 status <server>

3.9.2.29 Version

Outputs the version number of the Oracle BPA Suite Admintool

program.

To display version numbers, enter the following command call and

press Enter.

Interactive mode: Version

Outside of interactive mode BPAadm11 version

Tip

To output the version number of an Oracle Business Process

Repository, please use the Status (Page 331) command.

3.10 Evaluation (scripting)

The VB report execution environment enables you to run Visual Basic

reports when you work with Java-based products. The VB report

execution environment runs under Windows. It is installed with the

Oracle BPA Suite Site Administrator installation. Ensure that the

Report Server is enabled.

With Oracle Business Process Architect you can also create and run

JavaScript reports, provided the necessary system requirements are

met.


332

Visual Basic reports

You need about 10 MB RAM plus about 25 MB RAM for each

simultaneously run Visual Basic report. For example, to create four

reports at the same time, you need 10 MB plus four times 25 MB

RAM, that is, a total of 110 MB RAM.

JavaScript reports







Note

If you observe certain requirements (Page 332) when creating report

scripts, you ensure that memory requirements are optimized when

the reports are run. This reduces the execution time of your reports

and the risk of reaching the memory limits of your system.

3.10.1 Optimize memory requirements

If you observe certain requirements (Page 332) when creating report

scripts, you ensure that memory requirements are optimized when

the reports are run. This reduces the execution time of your reports

and the risk of reaching the memory limits of your system.

Only use database objects within the report for as long as is

necessary. Afterward, the database objects should no longer be kept

in memory. To achieve this, you can take the following steps, for

example:

Avoid storing lists of Oracle BPA Suite objects in global variables if

possible.

Use "short" functions to keep data only as long as it is required.

If lists containing a large number of objects are no longer needed,

it is advisable to clear them. This helps enable Java's garbage

collection to delete these objects from the memory. This measure

provides additional memory for report execution in the long term

even if the memory requirements in Java and using JavaScripts

cannot be controlled directly.


333

3.10.2 Report formats and report files

Visual Basic reports

To generate DOC and XLS output formats, Microsoft Office version

2000, 2002, 2003, or 2007 must be installed on the computer on

which Oracle Business Process Repository Site Manager is installed. If

you use reports to import data from Excel tables, please ensure that

the tables have been saved in XLS format.







Note

The Report Server is running by default. If you do not want to start

any VB scripts on an Oracle Business Process Repository, you can

shut down (Page 254) the Report Server to avoid unnecessary use of

system resources. You can always run these locally. To shut down the

Report Server, you must configure the file userServerSettings.cfg

as follows.

All reports

If, for example, you want to output documents in PDF format using


Microsoft Office version 2000, 2002, 2003, or 2007 installed. If you

use reports to import data from Excel tables, please ensure that the

tables have been saved in XLS format. If pop-up blockers are

activated for the domain, it may not always be possible to open

report output in PDF format from a Publisher export.


installed.

The reports are saved in your Temp directory. To save them in a

different directory, use the Save As functionality in the output

program.

In Oracle Business Process Architect, you can manage evaluation

scripts (reports, macros, transformations, and semantic checks) in

the Administration module.


334

3.10.3 Windows API functions

Since reports are run on the server, dialogs that are called from a

script via Windows API functions cannot be displayed on the client, for

example. The same applies to running Shell and ShellExecute. The

relevant programs and files are run or opened via the default

methods on the server.

For this reason, Oracle BPA Suite Script has special methods for

displaying, running, or opening dialog boxes, programs, and files on

the client. You find the parameters for these methods in the

corresponding help files. Replace the default methods as shown in the

following table:

Default Oracle BPA Suite Script

GetOpenFileName

(Win API)

BrowseForFiles

Option parameter e.g. = 0. Multiple files can be

selected if you increase this parameter by + 8.

GetSaveFileName

(Win API)

BrowseForFiles

Option parameter e.g. = 3

GetFilePath

(Sax Basic)

BrowseForFiles

SHBrowseForFolder

(Win API)

BrowseForFolders

ShellExecute

(Win API)

Shell


335

3.10.4 Dialog variables

When you use dialog variables in a report, this differs from use in the

local report because you must declare the scope of the dialog

variables.

Example of a local report:

bIsOk = False If bIsOk Then Begin Dialog UserDialog 440,112,"ARIS Report" ' %GRID:10,7,1,1 OptionGroup.options OptionButton 20,14,380,14,"Option1" OptionButton 20,35,380,14,"Option2" OKButton 210,77,100,21 CancelButton 320,77,100,21 End Dialog Dim Dlg As UserDialog End If If Dlg.options = 0 Then ...

If this report is run on a server, an error occurs here because the

Dlg.options variable is not globally valid.

The following change makes the Dlg.options variable globally valid

and allows you to run the report as a Web report:

Dim nDlg_Options As Long bIsOk = False If bIsOk Then Begin Dialog UserDialog 440,112,"ARIS Report" ' %GRID:10,7,1,1 OptionGroup.options OptionButton 20,14,380,14,"Option1" OptionButton 20,35,380,14,"Option2" OKButton 210,77,100,21 CancelButton 320,77,100,21 End Dialog Dim Dlg As UserDialog nDlg_Options = Dlg.options End If If nDlg_Options = 0 Then ...

3.10.5 Nested dialogs

Nested dialogs are not permitted in Web reports. Such nested dialogs

occur, for example, when a message box (MsgBox) is used in the

DialogFunc to output an error message. To have the Web report

output this message box, you need to integrate it in such a way that

it appears only after the dialog box generated with DialogFunc is

closed.


336

3.10.6 Icons for placed attributes

For example, if you run reports or create a Publisher export, the icons

that are saved in the icons subdirectory in the installation directory

of your Oracle Business Process Repository are used for linked files.

Icons of Microsoft Office products are automatically displayed. For

these applications, you do not need any icons in the directory noted

above unless you want to use your own icons.

You can change icons or add new ones. To create and edit icons in

ICO format, you need a suitable application. Assign file names that

conform with the extension of the relevant application.

To create icons that represent bitmap graphics or text files, for

example, save the graphics under the names bmp.ico and txt.ico.

Added icons are immediately available. Once you have changed icons,

you must restart Oracle Business Process Repository.

Note

If icons displayed in models are different from those in the report

output or in Publisher export, ensure that you have saved the

corresponding icons in the installation directory of your Oracle

Business Process Repository, in the icons subdirectory.

If icons for placed attributes are missing there, they will not be

displayed in the Publisher export or report output.

3.10.7 Add custom icons for macros

For users to be able to add frequently used macros as icons to the

toolbar, administrators must provide these icons.

Prerequisite

You have administration privileges for the Oracle Business Process

Repository installation directory.

Procedure

1. Open the installation directory of the relevant Oracle Business

Process Repository

..server/templates/scriptservice/internal/, and create the

images subdirectory.


337

2. This is where you save the icon files in PNG format.

The graphics must be (n*16) x 16 pixels in size.

3. Create an images.lst file and save it in UTF-8 format.

The file specifies the sequence in which the icons are displayed in

the user interface.

The file must have the following structure:

<Name of the first icon>.png

<Name of the second icon>.png

...

The new icons are available to users in the Configure macros dialog

box after restarting the program. If the file images.lst is missing, no

icons from the images directory are displayed.

3.11 Known restrictions

Knowing how the system is going to be used is essential to

determining an optimal technical configuration.

For specific cases, please contact Oracle Corporation support.

Versions more recent than those listed below have not been tested or

approved for use.

Note

Despite the approval of our software for operation with the listed

operating system versions and other software and hardware

requirements, we cannot exclude the possibility of problems arising

from unpredictable incompatibility issues with certain

hardware/software combinations.

This applies, for example, to the use of certain printers/printer drivers

or graphic cards/graphic card drivers under certain operating system

versions. In some cases, operational faults may occur when you

display graphics in Oracle BPA Suite, create reports, use other Office

applications, or export from Web Publisher. When a hardware key is

used for copy protection of software programs, poor performance of

the parallel interface may lead to delays or even errors.


338







Printers/plotters

Oracle BPA Suite printouts are not generated correctly with the HP

Design Jet 800 plotter driver and compatible drivers in HPGL mode.

Links




canceled. Please also note the error sources described (Page 339).

Reports in PDF format

Windows operating systems

If you select PDF as the output format and create the report script in

design view, only the character sets of the computer

(C:\Windows\Fonts) on which Oracle Business Process Repository

is installed are used. If you have formatted a text with the Algerian

character set, for example, and this is not in the specified directory,

the default character set is used to output this text.

Additional character sets that you install in C:\Windows\Fonts are

automatically considered.

Unix operating systems

There is no default directory for character sets under Unix operating

systems. If you install additional character sets in a directory of your

choice, the file userServerSettings.cfg in the directory

install_bpa11.xxxxxx.sh/config must be adjusted.

To do this, add the following expression to the file:

<reportdir font_location="/Fonts/" >

</reportdir>


339

Characters

Because of a known error in JVM (Sun)

(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5040856),

you should use only Western European characters in computer

names.

If you publish OLE objects whose file names are written in Japanese

characters in another language, e.g. de or en, the names will not be

displayed correctly. These files cannot be opened. To be able to open

the files, replace the Japanese (or other) file names with English

ones.

3.11.1 When do links work?

A link is a connection between resources. When you click on a link in

a browser, the linked file is displayed. Many factors play a role in this

process, which can sometimes lead to errors. Ensure that all system

requirements are met and only the approved browsers are used. If,

for example, you install a security update for your browser that is not

approved by IDS Scheer, links may no longer work.




canceled.

Using file servers is one way to exclude the possibility of faulty links.

All files that have been linked in databases are managed on a file

server.

Type of file (MIME type)

Not every browser can display all files. Some systems do not return

files without an extension, since the MIME type cannot be determined

directly. Access can also be limited to files of a specific type. Your

system administrator may have defined these restrictions in various

places:

Server

Operating system of the server

Client

Operating system of the client

Central settings (with Active Directory, etc.)

Proxy and its operating system

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5040856


340

Correct notation

Depending on your system configuration, the notation of the link may

also cause errors. Generally, a URL is processed in 8-bit

representation. Unicode coding must be handled separately.

No problems should be expected if you:

Maintain links in English and without any spaces and special

characters

If you maintain links in languages such as Japanese, or with

spaces and special characters, etc., you must place these links in

quotation marks.

Links are no longer than 1024 characters.

Many systems cannot process more characters than that.

Type of link

Depending on the domain from which a link is started or to which a

link leads, a distinction must be made between local and external

links. Different errors may also occur depending on system and

security settings.

External links

Correctly written and absolute links pose no problems. All links to

files that were copied from Oracle Business Process Publisher to

the Oracle Business Process Publisher Server also work correctly.

The browser handles these as external links.

Local links

All links to local files are subject to strict security restrictions.

These restrictions are not at all uniform and differ between various

browsers and different versions and patches. If, for example, you

install a security update for your browser that is not approved by

IDS Scheer, links may no longer work.

Syntax

Local link without drive link

The link file:///C:/Program Files/Internet

Explorer/readme.txt opens a file in the local directory structure

C:\Program Files\Internet Explorer\readme.txt

Local link with local drive link


341

The link file:///U:/ARIS/businesspublisher/tomcat

5.5.16/RUNNING.txt opens a file in the local directory structure

U:\ARIS\\businesspublisher\tomcat 5.5.16\RUNNING.txt,

with U representing a direct link to a local directory.

External link with network drive link

The link file:///V:/External/Version.txt opens a file in the

network structure V:\External\Version.txt, with V representing

a direct connection to a network drive.

UNC link (Universal Naming Convention)

UNC path

The link with a different syntax, for example,

file://SERVER/www/trace.txt,

file:///\\SERVER\www\trace.txt, or

file://///SERVER/www/trace.txt, opens a file in the drive

structure \\SERVER\www\trace.txt.

Direct access (i.e. without a drive link) to any resource in the

network is possible with a UNC path.

Security risks

Not every browser always makes interactive reference to possible

security risks. More frequently, functional links are blocked.

Firefox generates a message in the error console in these cases

(Tools/Error console), but does not distinguish between local and

external links. All local access is blocked automatically. You can

remove blocking of specific sites by adjusting or creating the file

<drive>:\Documents and Settings\<USER>\Application

data\Mozilla\Firefox\Profiles\<GENERATED_NAME>.default\

users.js:

user_pref("capability.policy.policynames", "localfilelinks"); user_pref("capability.policy.localfilelinks.sites", "http://pcsomeone"); user_pref("capability.policy.localfilelinks.checkloaduri.enabled", "allAccess");

Authorizations

Missing authorizations and the storage location of linked files may be

reasons for faulty links.

If locally saved files are linked in a database, these links cannot be

resolved if you use an Oracle Business Process Repository. These

links only work if you manage the database on the local server

local.


342

If you have enabled the Copy documents check box on the

Include links page of the Profile Wizard

(View/Options/Publisher export profiles) and started Oracle

Business Process Repository as a service, ensure that your

authorization concept permits access to linked documents.

3.11.2 Calendar

Oracle BPA Suite supports the Gregorian calendar. Other calendars,

such as the Islamic and traditional Japanese calendar, are not

supported.

3.12 Glossary

Please select a subentry.

A

Application server Computer on which applications are run. It is a component of a 3-tier

architecture.

Oracle BPA Suite agent Program that autonomously monitors and manages Oracle Business

Process Repository processes.

Oracle Business Process Architect Modeling tool of the Oracle BPA Suite product family that runs within

a browser or as an application (Page 298) and that can be used in a

LAN and a WAN. Oracle Business Process Architect thus enables so to

speak Internet modeling of business processes.

Oracle Business Process Repository Oracle BPA Suite application server (see Application server)

Oracle BPA Suite Converter Conversion component of Oracle BPA Suite. It converts Oracle BPA

Suite data of previous Oracle BPA Suite versions to the current Oracle

BPA Suite format.


343

Oracle BPA Suite HTML Generator Program module that automatically generates the HTML files needed

by Java-based clients when they are launched via a browser.

Oracle BPA Suite Site At least one Oracle Business Process Repository, one database server

and one Oracle Business Process Repository Site Manager.

Oracle BPA Suite Site Administrator Central management component with which administrative accesses

can be provided to all Oracle BPA Suite sites simultaneously.

Oracle Business Process Repository Site Manager Central component of Oracle BPA Suite Site that, for instance,

coordinates access to programs and data by means of a license and

lock service.

D

Database server Computer on which the Oracle BPA Suite Repository is installed.

Oracle BPA Suite Clients access the database server on which the

Oracle BPA Suite Repository containing the Oracle BPA Suite

databases resides via the Oracle Business Process Repository.

F

Firewall Technology (hardware and/or software) that controls the data flow

between internal and external (unprotected) networks and provides

protective mechanisms to combat unauthorized access.

J

JRE Java Runtime Environment. System that is used to run Java

programs. The main components are the Java Virtual Machine, the

Java Interpreter, and the host operating system.


344

L

LAN Local Area Network. Network within a company. This network has

broad bandwidth.

LDAP Lightweight Directory Access Protocol. Protocol that provides access

to centrally managed libraries of information and directories. It saves

having to search the whole network for data. The access data for user

login to Oracle BPA Suite is stored centrally on the LDAP server so it

does not have to be managed separately for each database.

O

Oracle Relational database system that can be used for Oracle BPA Suite

installations.

R

RAID Redundant Array of Independent Disks. Method of linking several

hard drives and accessing these as if accessing a single hard drive.

This means that data storage and data access is 'spread' across these

hard drives, which improves access time and avoids complete loss of

data should a drive fail.

S

SSL Secure Socket Layer. Security software for encrypting data that is

exchanged between programs.

System user Users who have all function and access privileges in a database.

System users can be created by the system manager (user system)

or by another system user. The system system user is created

automatically for every database. The name system cannot be


345

changed. A system user should immediately change the password

manager to prevent unauthorized access. The function and access

privileges of system users cannot be changed. To withdraw privileges

from a system user, another system user must disable the System

user check box on the former user's Function privileges properties

page. As a result, the user's privileges can be changed. After this, the

user has no access privileges.

'system' user

Enter the user name system if you log in for the first time after you

have installed the program or created a new database. The system

system user is created automatically for every database. This user

has all function and access privileges. Authorized persons can use this

emergency user to log in to any database, even if you use an LDAP

system or an OIS system. The name system cannot be changed. You

should immediately change the password manager to prevent

unauthorized access. To avoid problems, you can create additional

system users.

W

WAN Wide Area Network. Network that transports data both within the

company network and via the Internet. This network has low

bandwidth.

Web Client Components WWW components that are accessed by Web clients, e.g. Oracle

Business Process Architect when they are started via a Web browser.

Web server A server containing the HTML pages, images, documents and other

files and folders that users or programs within a network can access.


346

3.13 Appendix

3.13.1 System language and locale IDs

The locale ID designates a language within a language group.

The language groups and code page are also represented by a

number, e.g. code page=1252. The language group is preceded by a

minus sign (-), e.g. -1252.

System language Locale ID

Afrikaans - South Africa 1078

Albanian - Albania 1052

Arabic - Algeria 5121

Arabic - Bahrain 15361

Arabic - Egypt 3073

Arabic - Iraq 2049

Arabic - Jordan 11265

Arabic - Kuwait 13313

Arabic - Lebanon 12289

Arabic - Libya 4097

Arabic - Morocco 6145

Arabic - Oman 8193

Arabic - Qatar 16385

Arabic - Saudi Arabia 1025

Arabic - Syria 10241

Arabic - Tunisia 7169

Arabic - U.A.E. 14337

Arabic - Yemen 9217

Basque - Spain 1069

Belarussian - Belarus 1059

Bulgarian - Bulgaria 1026

Catalan - Spain 1027


347


Chinese - Hong Kong 3076

Chinese - PRC 2052

Chinese - Singapore 4100

Chinese - Taiwan 1028

Croatian - Croatia 1050

Czech - Czech Republic 1029

Danish - Denmark 1030

Dutch - Belgium 2067

Dutch - Netherlands 1043

English - Australia 3081

English - Belize 10249

English - Canada 4105

English - Caribbean 9225

English - Ireland 6153

English - Jamaica 8201

English - New Zealand 5129

English - South Africa 7177

English - Trinidad 11273

English - United Kingdom 2057

English - United States 1033

Estonian - Estonia 1061

Faeroese - Faeroe Islands 1080

Farsi - Iran 1065

Finnish - Finland 1035

French - Belgium 2060

French - Canada 3084

French - France 1036

French - Luxembourg 5132

French - Switzerland 4108


348


German - Austria 3079

German - Germany 1031

German - Liechtenstein 5127

German - Luxembourg 4103

German - Switzerland 2055

Greek - Greece 1032

Hebrew - Israel 1037

Hungarian - Hungary 1038

Icelandic - Iceland 1039

Indonesian - Indonesia 1057

Italian - Italy 1040

Italian - Switzerland 2064

Japanese - Japan 1041

Korean - Korea 1042

Latvian - Latvia 1062

Lithuanian - Lithuania 1063

Norwegian - Norway (Bokmal) 1044

Norwegian - Norway (Nynorsk) 2068

Polish - Poland 1045

Portuguese - Brazil 1046

Portuguese - Portugal 2070

Romanian - Romania 1048

Russian - Russia 1049

Serbian - Serbia (Cyrillic) 3098

Serbian - Serbia (Latin) 2074

Slovak - Slovakia 1051

Slovene - Slovenia 1060

Spanish - Argentina 11274

Spanish - Bolivia 16394


349


Spanish - Chile 13322

Spanish - Colombia 9226

Spanish - Costa Rica 5130

Spanish - Dominican Republic 7178

Spanish - Ecuador 12298

Spanish - El Salvador 17418

Spanish - Guatemala 4106

Spanish - Honduras 18442

Spanish - Mexico 2058

Spanish - Nicaragua 19466

Spanish - Panama 6154

Spanish - Paraguay 15370

Spanish - Peru 10250

Spanish - Puerto Rico 20490

Spanish - Spain (Modern Sort) 3082

Spanish - Spain (Traditional Sort) 1034

Spanish - Uruguay 14346

Spanish - Venezuela 8202

Swedish - Finland 2077

Swedish - Sweden 1053

Thai - Thailand 1054

Turkish - Turkey 1055

Ukrainian - Ukraine 1058

Vietnamese - Vietnam 1066


350

3.13.2 Port numbers

The following port numbers are entered in the Services file of your

Windows installation. This file is located in the

system32/drivers/etc/ Windows directory.

Port Name For

16070 aris71_name_public Public Name Service

16071 aris71_name_private Private Name Service

16072 aris71_admin Admin Service

16073 aris71_admin_agent Agent Service

16074 aris71_Olite Standard database system

16075 aris71_local_public Public Name Service local

16076 aris71_local_Olite Standard database system

local

16077 aris71_local_private Private Name Service local

16078 aris71_local_admin Admin Service local

16079 aris71_bp_service Business Publisher Service

16080 aris71_simuserver Simulation Service

16081 aris71_local_simuserver Simulation Service local

16083 aris71_bp_report Business Publisher Report

Service


i

Index

A Acrobat Reader - 214

Administration Browser use (Java-based products) - 295 Language update and character sets - 298 Software distribution - 299

Applet - 298

Application - 298

Approved platforms Oracle Business Process Repository - 242

Automatic backup - 218

B Backup - 316

Backupasn - 318

Backupconfig - 319

Browser use (Java-based products) - 295

C Character set - 298

Citrix - 265

Client log - 270

Configadminpassword - 320

Configuration database - 309

Configure client connection - 254

Copy - 320

Createdb - 321

D Dbmspassword - 321

Deactivate Report Server - 254

Deactivate simulation server - 255

Delete - 322

Download - 321

E Evaluation - 331

Exit - 322

Expand memory - 259

H Help - 322

I Install an Oracle BPA Suite

client (Linux) - 7

Install an Oracle BPA Suite client (Windows) - 5

Install Oracle Business Process Publisher Report Server - 194

Install Oracle Business Process Publisher Server - 44

Install Oracle Business Process Repository (Windows) - default - 12

Install Oracle Business Process Repository (Windows) - user-defined - 17

Installation Automatic backup - 218 Install an Oracle BPA Suite

client (Linux) - 7 Install an Oracle BPA Suite

client (Windows) - 5 Install Oracle Business

Process Publisher Server - 44

Install Oracle Business Process Repository (Windows) - default - 12

Install Oracle Business Process Repository (Windows) - user-defined - 17

Oracle BPA Suite Site Administrator - 20

Oracle BPA Suite Web Client Components - 41

Oracle Business Process Repository Site Manager - 21


ii

Software distribution - 299 System add-ons - 216

Interactive - 323

J Java Runtime Environment -

215

Java-based products - 295

K Kill - 323

L Language update - 298

Language update and character sets - 298

LDAP - 344

List - 324

Locale ID - 346

Log login - 251

Log messages (debugging) - 251

M Maintain - 324

Memory-optimized scripts - 332

Monitor - 324

Multi-monitor operation - 265

O Oracle BPA Suite Admintool

Backup - 316 Backupasn - 318 Backupconfig - 319 Configadminpassword - 320 Copy - 320 Createdb - 321 Dbmspassword - 321 Delete - 322 Download - 321 Exit - 322 Help - 322 Interactive - 323 Kill - 323 List - 324 Maintain - 324 Monitor - 324 Password - 325

Rename - 325 Reorg - 325 Restore - 326 Restoreasn - 327 Restoreconfig - 328 Restoreversioned - 327 Server - 328 Sessions - 329 Siteadminpassword - 330 Statistic - 330 Status - 331 Version - 331

Oracle BPA Suite agent - 263

Oracle BPA Suite Notify Service - 256

Oracle Business Process Publisher Server - 273 IBM WebSphere Application

Server (WAS 6.0.X) (Windows) - 74

Install Apache Tomcat Web Application Server (Solaris/Linux) - 66

Install Apache Tomcat Web Application Server (Windows) - 44

Install Oracle Business Process Publisher Report Server - 194

Oracle Business Process Repository Configure client connection -

254 Configure Oracle Business

Process Repository Site Manager connection - 253

Deactivate Report Server - 254

Deactivate simulation server - 255

Enable SSL - 251 Expand memory - 299 IBM DB2 database - 231 Log login - 251 Log messages (debugging) -

251 MS SQL database - 227 Oracle database - 221 Standard installation - 12 User-defined installation -

17


iii

Oracle Business Process Repository Site Manager Configure Oracle Business

Process Repository Site Manager connection - 253

Installation with configured Oracle database instance - 21

Installation with existing Oracle database instance - 23

Installation with IBM DB2 - 28

Installation with MS SQL Server - 27

Installation with newly created Oracle database instance - 25

P Password - 325

R Rename - 325

Reorg - 325

Restore - 326

Restoreasn - 327

Restoreconfig - 328

Restoreversioned - 327

S Server - 328

Server LOG - 262

Sessions - 329

Siteadminpassword - 330

Software distribution - 299

Software requirements Additional memory - 259 Oracle BPA Suite Converter

- 260 Oracle BPA Suite UML

Designer - 265 Oracle Business Process

Architect - 265 Oracle Business Process

Publisher - 271 Oracle Business Process

Repository - 242

Oracle Business Process

Simulator - 265 Web Client Components -

265

SQL*Plus scripts Import - 222

SSL encryption - 251

Start a program as an Applet - 298

Start a program as an application - 298

Start a program in the browser - 295

Start Oracle BPA Suite Admintool - 313

Statistic - 330

Status - 331

System add-ons - 216

System language - 346

T Transfer data from earlier

Oracle BPA Suite versions - 307

V Version - 331