Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Search   |   PDF Files   |   Contact   |
eLink Business Process Option Doc Home   |   BEA eLink Business Process Option Server Installation Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

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

• Verifying System Requirements

• Gathering Your Installation Information

• Creating the UNIX User and 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.

Verify that your system meets the following hardware and software 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 105591-07 (See Note below for more information on the necessity of this patch.)

• Oracle 8.0.5, with XA

• BEA eLink Foundation v1.2

  Note: It is very important to have only the -06 or -07 patch level installed for Solaris. The file /usr/lib/libCrun.so.1 is required in LD_LIBRARY_PATH. It comes with Solaris patch 105591-06 or -07. If the wrong version of this file is encountered, IcBatRegSA will core dump with a Bus Error during the "install/IcTuxInstall" process. For example, Solaris 2.6 patch 105591-08 will cause a core dump.

  Use the following command to check your patch level:

  >showrev -p|grep 105591
  Patch: 105591-06 Obsoletes: 101242-13 Requires: Incompatibles: Packages: SUNWlibC.2

  If for some reason, you are not able to install these patches immediately, the workaround is to acquire the file libCrun.so.1 from the -06 or -07 patch version. The file must be copied into the directory where IcCliMgr , IcWorker, IcTMS, IcEvtAct, and IcEvtSched live. In the case of this installation example, we chose to /app/elink/bpo_sw/tuxapp. This directory is set as our $APPDIR in the installation guide examples. Those programs use the libCrun.so.1 library.

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

The BEA eLink Business Process Engine requires a UNIX user ID and group be available for use in installing and configuring the BEA eLink Business Process Option. The examples in this guide employ a user ID called elink and a group called elink. The command and response shown in Listing 2-1 demonstrates a method for determining user and group ids. In this example, the user ID (uid) is elink and the group ID (gid) is elink.

>id
uid=1016(elink)gid=4000(elink)

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. The examples provided in the remainder of this installation guide will use an IC_HOME of /app/elink/bpo_sw, so the example in this section will create a directory called bpo_sw in the /app/elink directory.

Note: The Business Process Engine home directory must be owned by the elink user, but must not be that user's home directory. It must also belong to the elink 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 elink.

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

   mkdir directory

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

   Example:

   cd to the /app/elink directory, then enter the following command to make the IC_HOME directory:

   /app/elink> mkdir bpo_sw

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

   chgrp -R elink directory

   Example:

   /app/elink> chgrp -R elink bpo_sw

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

   chmod 755 directory

   Example:

   /app/elink> chmod 755 bpo_sw

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 elink user must have read/write access to the repository directory during installation. The examples provided in the remainder of this installation guide will use a repository directory of /app/elink/bpo_rep, so the example in this section will create a directory called bpo_rep in the /app/elink directory.

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 elink.

2. Enter the following command:

   mkdir -p directory

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

   Example:

   cd to the /app/elink directory, then enter the following command to make the repository directory:

   /app/elink> mkdir -p bpo_rep

   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 elink is the owner of the Repository directory, as follows:

   chown -R elink directory

   chgrp -R elink directory

   Example:

   /app/elink> chown -R elink bpo_rep

   /app/elink> chgrp -R elink bpo_rep

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

   chmod -R 700 directory

   Example:

   /app/elink> chmod -R 700 bpo_rep

5. Add an entry to your environment login file (.kshrc) or command file (setenv) that sets your IC_HOME environment variable.

   Example:

   IC_HOME=/app/elink/bpo_sw

   Note: If you ever have to reinstall the Business Process Engine, it is imperative that you delete all the contents of this repository directory. If you do not, you will have problems with the PDA client later. You will not be able to log into the Process Designer and may see messages like "Local Repository Mismatch".

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.

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.

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 in 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.