Before You Begin

 

The following sections describe the preparatory procedures for BEA eLink Business Process Option Server installation.

• Verifying System Requirements

• Gathering Your Installation Information

• Creating the icadmin User and inconcrt Group

• Creating the eLink Business Process Engine Home Directory

• Creating the Default Business Process Engine Repository Directory

• Configuring the Oracle Database for the eLink Business Process Engine

These procedures are described in detail in the following sections.

Verifying System Requirements

Verify that your system meets the following hardware and software requirements.

Hardware Requirements

• At least 256 MB of RAM

• At least 150 MB of free disk space ( depending on how much database space you want to allot-the default installation uses about 50 MB and creates a database of 100 MB)

Software Requirements

• HP-UX 11.00 (32- or 64- bit) or Solaris 2.6 with patch 105591-06 or higher

• Oracle 8.0.5, with XA

• BEA eLink Platform v1.2

• BEA Foundation 1.1

Gathering Your Installation Information

Gather the information you need to complete the installation. Use the following checklist:

• Base directory of your existing BEA eLink Platform installation

• Base directory where the BEA eLink Business Process Engine components will be installed

• Base directory in which the BEA eLink Business Process Engine Repository will be created

• Your BEA eLink Business Process Option License token and serial number

• Unique identifier for your BEA eLink Business Process Option Server

  Note: The formula for determining a unique server ID is as follows:

  ((serial# - 1,000,000,000) x 10) + 900,000,000

  where serial# is the serial number in the BEA eLink Business Process Engine section of your license file.

• UNIX hostname for the installation machine as known to the UNIX kernel

• TCP/IP port number to be used to connect to the BEA eLink Business Process Engine Repository

• Database user's user ID and password

• Name of the tablespace to be dedicated to the BEA eLink Business Process Engine

• SQL*Net identifier for your database instance

• Absolute pathname for the Oracle installation directory

• Directory containing the SQL*Net configuration files

• Your Oracle site ID

• Your new or existing BEA eLink Platform domain ID

• Your unique identifier for interprocess communications for your eLink Platform domain

• Directory to which eLink Platform transaction logs should be written

• TCP port number to be used by client applications to connect to your eLink Platform domain

Creating the icadmin User and inconcrt Group

BEA eLink Business Process Engine requires a UNIX user ID of icadmin. All BEA eLink Business Process Engine software is run under this user ID, and it owns all BEA eLink Business Process Engine directories. In addition, you must create the UNIX user group inconcrt, with icadmin as a member.

Creating the eLink Business Process Engine Home Directory

You must create the BEA eLink Business Process Engine home directory (known as IC_HOME), which is where the eLink Business Process Engine software will be installed.

Note: The Business Process Engine home directory must be owned by the icadmin user, but must not be that user's home directory. It must also belong to the inconcrt group.

To create the eLink Business Process Engine home directory:

1. Identify a file system with at least 50 MB of free disk space and log in as icadmin.

2. Create the eLink Business Process Engine home directory by entering:

   mkdir directory

   where directory is the complete path name of the eLink Business Process Engine home directory. This directory cannot be the icadmin user's home directory.

3. Use the chgrp command with the -R option to make sure that the group of the eLink Business Process Engine home directory is inconcrt:

   chgrp -R inconcrt directory

4. Use the chmod command to change the permissions on the eLink Business Process Engine home directory to provide inconcrt group members with read access:

   chmod 755 directory

Creating the Default Business Process Engine Repository Directory

One function of the BEA eLink Business Process Engine repository is storing the user interface data for the eLink Business Process window of the eLink Process Design Assistant. This repository is known as the document repository; and the directory for this repository must be created before installation. The icadmin user must have read/write access to the repository directory during installation.

Note: Before you use the eLink Business Process Repository Server, make sure that you select the port number that the document repository server will listen on. Use the netstat command to list ports that are already in use.

To create the default Repository directory:

1. Log in as icadmin.

2. Enter the following command:

   mkdir -p directory

   where directory is the complete path name of the eLink Business Process Engine Repository home directory. (This step creates the directory for the InConcert Document Repository.)

   Warning: Do not create the Repository directory as a subdirectory of the eLink Business Process Engine home directory. This will prevent the extract.sh installation script from executing correctly.

3. Use the chown and chgrp commands to ensure that icadmin is the owner of the Repository directory, as follows:

   chown -R icadmin directory

   chgrp -R inconcrt directory

4. Change the permissions on the Repository directory to provide only icadmin with read/write access:

   chmod -R 700 directory

Configuring the Oracle Database for the eLink Business Process Engine

To run the eLink Business Process Engine, you must create an Oracle user and tablespace. In addition, you must change the Oracle configuration parameter OPEN_CURSORS.

Note: Before you install the eLink Business Process Engine, you must already have an Oracle instance installed and operating. Refer to your Oracle product documentation for information about installing the Oracle database.

Changing the OPEN_CURSORS Configuration Parameter

The BEA eLink Business Process Engine performs many SQL operations. To improve efficiency, it does not close explicit cursors between operations, thus allowing the Oracle database to keep information about the cursor in a cache. However, if you use the default setting for the OPEN_CURSORS parameter, it will result in an ORA-01000 runtime error.

To change the default setting for the OPEN_CURSORS parameter:

1. Shut down the Oracle instance.

2. Open the instance configuration file in a text editor.

   This file is typically found in the directory $ORACLE_HOME/dbs, and is named initSID.ora (where SID is the Oracle system identifier for the instance).

3. Perform a case-insensitive search for the line containing open_cursors. Although Oracle configuration parameters are not case-sensitive, they are typically specified in lowercase.

4. Edit this line to set the value to 255. If it does not exist, create a new line as follows:

   open_cursors = 255

5. Save your changes and exit the text editor.

6. Restart the Oracle instance.

Creating the eLink Business Process Tablespace and Database User

The eLink Business Process Engine database user owns all tables, views, and other database objects that support the operation of the eLink Business Process Engine. The procedure described here creates the user and a tablespace needed to run the eLink Business Process Option.

Note: To create the eLink Business Process Engine database user, you must have administrator access to the Oracle instance.

This procedure is appropriate for those sites without a full-time DBA. If your site does have a DBA, the DBA should create the tablespace in order to ensure that it meets the standards set by your organization.

To create the eLink Business Process Engine tablespace and database user:

1. Log in as the oracle user.

   This login should set the ORACLE_HOME, ORACLE_SID, and PATH environment variables. If it does not, refer to your Oracle documentation for appropriate settings.

2. Identify a file system that contains sufficient space for the eLink Business Process Engine tablespace.

   The required space depends on your expected usage of the eLink Business Process Engine. For a pilot installation, 100 MB is sufficient; for a production installation, you might want to reserve 200 MB or more. For our example, we will use the directory /local/manda/ORACLE/godzilla to store the tablespace.

3. Run the Oracle Server Manager utility by entering:

   svrmgrl

4. Connect to the database instance by entering:

   connect internal

5. Create the eLink Business Process Engine tablespace.

   This example creates a 100 MB tablespace named ICDB. The default storage parameters in this database represent a trade-off between efficient storage of small tables and minimal fragmentation of large tables.

   CREATE TABLESPACE ICDB
   DATAFILE
       '/local/manda/ORACLE/godzilla/icdb.dbf'
       SIZE 100 M
   DEFAULT STORAGE (
       INITIAL 256k
       NEXT 256
       PCTINCREASE 0
       MAXEXTENTS unlimited
       );

6. Create the eLink Business Process Engine user.

   This example creates the user icdbown, with the password icdbown and associates the user with the ICDB tablespace just created.

   Note: The icdbown username and password are used the the examples throughout the rest of this document.

   This example also sets the user's temporary tablespace to ICDB. Many sites have a TEMP tablespace for temporary storage. Determine whether your site has a TEMP tablespace, and use it if available.

   CREATE USER icdbown
   IDENTIFIED BY icdbown
   DEFAULT TABLESPACE ICDB
   TEMPORARY TABLESPACE ICDB;

7. Grant connection access to the eLink Business Process Engine database user.

   GRANT RESOURCE, CONNECT TO icdbown;

8. Grant access to the Oracle system view DBA_PENDING_TRANSACTIONS.

   This step is required by the BEA eLink Platform; if omitted, you will get connection errors when attempting to start the eLink Business Process Engine.

   GRANT SELECT ON DBA_PENDING_TRANSACTIONS TO icdbown;

9. Exit the Oracle Server Manager utility.