Installation Types
The following three installation types are available:
| • | Install or upgrade schema and files |
If you are an iProcess Files-install Owner as well as an iProcess Schema-install Owner, you can install or upgrade schema and files simultaneously.
| • | Install or upgrade schema only |
If you are only an iProcess Schema-install Owner, you can only install or upgrade schema during the installation.
| • | Install or upgrade files only |
If you are only an iProcess Files-install Owner, you can only install or upgrade files during the installation.
For an iProcess Files-install Owner, two installation types are available when installing iProcess files, Full Installation and Partial Installation.
| • | Full Installation |
If you want to install iProcess Engine in a single automated operation, you can perform a full installation.
To complete a full installation:
| — | you must run the installer as the root user, and |
| — | the root user must have DBA-level access to the database. |
|
Note |
If granting this level of access (for the duration of the installation process) is compatible with your site’s security policies, TIBCO strongly recommends doing so, as this considerably simplifies the installation task. |
| • | Partial Installation |
If you want to split the installation into separate tasks according to its component roles (as discussed on iProcess Engine Architecture), you can perform a partial installation. The users acting in the different roles will need to run further commands to complete the installation after the installer has finished.
If a partial installation is performed, the installer creates a $SWDIR/logs/TODO file, which lists the tasks that must be performed manually, the order in which they must be done, and who needs to do them. See The $SWDIR/logs/TODO File for more information.
|
If You Run The Installer As |
And |
||
|
You Have DBA-level Access And |
You Do Not Have DBA Access, Or You Want To Create Or Upgrade The Database Later |
||
|
You Want The Installer To Create The Database |
You Want The Installer To Use An Existing Database |
||
|
|
The installer performs a full installation. It creates the database and sets all necessary file permissions. |
The installer performs a full installation. It uses the specified database and sets all necessary file permissions. |
The installer performs a full installation. The DBA will need to create or upgrade the database to complete the installation, as specified in the |
|
the iProcess Engine |
The installer performs a partial installation.
|
The installer performs a partial installation.
|
The installer performs a partial installation. To complete the installation: The DBA will need to create or upgrade the database.
|
|
Note |
For DB2 database users If you run the installer as a
You can proceed with the installation, provided that your version of DB2 is one of the required versions listed on IBM DB2 Database. However, to be absolutely certain that the version of DB2 you are using is correct, run the following command as the
|
For example, suppose that you want to install a new iProcess Engine, and the iProcess Files-install Owner, iProcess Schema-install Owner, DBA, and root user roles are each performed by different users. In this case, the following sequence is required to perform the installation:
| 1. | The iProcess Files-install Owner: |
-
logs in as the iProcess Engine background user and runs the installer.
-
enters all the necessary configuration information except for the database details.
-
accepts the prompt to perform a partial installation.
The installer installs iProcess Engine files, performs basic configuration tasks, and creates a $SWDIR/logs/TODO file.
| 2. | The iProcess Schema-install Owner runs the $SWDIR/util/swinitora script to supply the database configuration information and create the iProcess Engine database schema. |
| 3. | The DBA runs the $SWDIR/util/swpostinst script to populate the database with the appropriate initial values. |
| 4. | The root user runs the $SWDIR/logs/rootscript script, to set file permissions and perform any other configuration activities that require root access. |