Table of Contents

Search

  1. Preface
  2. Apache Tomcat
  3. WebLogic
  4. IBM Websphere
  5. JBoss

Server Installation, Configuration, and Deployment

Server Installation, Configuration, and Deployment

Process Server and Resource Configuration

Process Server and Resource Configuration

This topic leads you through configuration of the resources required for Process Server. You must configure your database, Apache Tomcat Server and Process Server before deploying and running Process Server. The sections below provide information for completing the configuration.

Configuration Instructions

Before running the Configuration utility, perform the following pre-configuration steps:
  • Create a database (or tablespace) where Process Server persistence information will be stored
  • Create a default user with administrative rights to the computer and database for use by Process Server
  • Note both the database name and port number, which you will be asked for during configuration.
  • Process Server requires a JDBC driver to connect to your database. During configuration, you will be prompted for:
    • The full path to a supported JDBC database driver
    • The driver implementation class name
    Note that the Microsoft SQL Server 2005 JDBC Driver 1.2 driver, or the JDTS-1.2.jar drivers are supported. Version 1.1 of the Microsoft SQL Server will not function as it does not include all required functionality.

First Time or New Install

If you are performing a clean installation, that is, a first-time install or a new database, you can use the Configuration utility to automatically install the database schema.

Manual Install or Update of Database Schema

It is strongly recommended that you automatically install the database schema; however, you can manually install it. Customers migrating from an earlier version should follow the instructions below.
Migrating from ActiveVOS to Process Developer
If you are migrating from ActiveVOS, perform the following steps:
  • Manually update the Process Server database schema using the DDL patches provided in
    {install_dir}/server/tomcat_config/ddls/updates
  • Run the
    Configuration utility
  • Review the Release Notes for late breaking migration information
  • Review the Process Developer help topic, Migrating from Earlier Versions
Process Server can be configured to use an RDBMS database.
Relational Database Schemas
These instructions are generalized to make sure they can be followed for each database. When creating the database schema for Process Server, you can either create a new database definition or upgrade an existing definition.
  • Refer to the install a new database schema section for a new installation.
  • Refer to upgrade a database schema when performing a version upgrade.
Install a new database schema
  1. Identify your DDL. Use the information provided in the table below to locate the correct DDL file.
    Database Server
    DDL File Name and Location
    Notes
    MYSQL
    {install_dir}/server/tomcat_config/ddls/ActiveBPEL_Enterprise-MYSQL.SQL
    The default database name, ActiveVOS is defined within the DDL file. If you edit this name, ensure that you do not replace ActiveVOS Enterprise, a name that is inserted into the
    AeMetaInfo
    table.
    MS SQL SERVER
    {install_dir}/server /tomcat_config/ddls/ActiveBPEL_Enterprise-MYSQL.SQL
    The default database name, ActiveVOS is defined within the DDL file. If you edit this name, ensure that you do not replace ActiveVOS Enterprise, a name that is inserted into the
    AeMetaInfo
    table.
    ORACLE
    {install_dir}/server/ tomcat_config/ddls/ ActiveBPEL_Enterprise- ORACLE.SQL
    Create a tablespace prior to running the DDL.
    DB2
    {install_dir}/server/ tomcat_config/ddls/ ActiveBPEL_Enterprise- DB2.SQL
  2. Copy the DDL file from above, and rename it.
    Note:
    The original files must remain unchanged for the Configuration utility to work properly
  3. (Optional) Modify the database name. Be sure to see the notes above.
  4. Execute the DDL script.
  5. Permissions must be set for Process Server to access your schema. For example,
    GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE
    If Process Server does not have the permissions it needs, you will see an error message that begins as follows:
    Failed to get version info from the AeMetaInfo table
    .
Each database server provides its own mechanism or utility for executing a DDL script file. Execute the DDL script file using the appropriate utility. For example, if you are using Oracle, the utility to execute the DDL script file would be SQL Plus.
Upgrade an existing database schema
To upgrade your existing Process Server database to be compatible with the new version of software, follow the instructions below:
  1. Shutdown Process Server before executing a database upgrade.
  2. Make a backup copy of your database.
  3. Identify your current running version of Process Server. Database upgrades are provided to upgrade from one version back at a time. This means that more than one upgrade script may need to be applied to your database. For example, if you are running ActiveVOS version 8.0.x, you must go to the
    updates
    folder, and apply all patch scripts with higher numbers, starting with
    [database name]-Patch-9.0.sql
    . Be sure to run the patch scripts in
    ascending
    order. Do not run any upgrade script with a version number equal to or less than your current running version.
  4. For each upgrade that needs to be applied perform the following:
    1. Identify your DDL. Use the information provided in the table below to locate the correct DDL file. Note: The updates must be applied in ascending order.
      MYSQL
      Tomcat: {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-MYSQL-PATCH-{patch number}.SQL
      MS SQL SERVER
      Tomcat: {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-SQLSERVER-PATCH-{patch number}.SQL
      ORACLE
      Tomcat: {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-ORACLE-PATCH-{patch number}.SQL
      DB2
      Tomcat: {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-DB2-PATCH-{patch number}.SQL
    2. Execute the DDL script.
      Each database server provides its own mechanism or utility for executing a DDL script file. Execute the DDL upgrade script file using the appropriate utility. For example, if you are using Oracle, the utility to execute the DDL script file would be SQL Plus.

Multisite Configuration

For details, see
Process Server MultiSite Configuration
.

Tomcat Security Configuration

You can find details on configuring Process Server security roles in Process Developer Help or in the Infocenter.

Configuration for Headless Mode

Process Server relies on GUI components from the Java's SWT package, such as fonts. If you are running on a headless server (that is, the server does not have a graphic subsystem), you may see one of the following errors in the stack trace:
  • java.lang.NoClassDefFoundError: sun/awt/X11GraphicsEnvironment
  • Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable
  • org.eclipse.birt.report.service.api.ReportServiceException
Use one of the following techniques to correct the errors:
  • Configure the JVM system property
    java.awt.headless=true
    and at the command line, start the JVM with the argument:
    -Djava.awt.headless=true
  • Run a X-windows virtual frame buffer (Xvfb)
In a Linux environment that uses Azul Zulu JDK, when you run the ActiveVOS installer, the following error appears:
java.lang.Error: Probable fatal error:No fonts found...
Workaround: To install the missing fonts, run the following command:
sudo yum install fontconfig dejavu-sans-fonts dejavu-serif-fonts

Using the Configuration Utility

The Configuration utility walks through the steps required to provide the property values for Process Server and selected resources.
Note:
Before running the utility, ensure that your server container is stopped.
Starting the Configuration Utility
Execute one of the following utilities based on your operating system:
Windows
{install_dir}/server/tomcat_config/bin/config_deploy.bat
Linux
{install_dir}/server/tomcat_config/bin/config_deploy.sh
If You Have Manually Installed or Updated the Database Schema
If you have manually installed or updated the database schema, when prompted, you must not select the "Install Database Schema" checkbox.
Running the Configuration Utility in Different Modes
The Configuration utility can be run with a graphical interface (default), in console mode or silently. When you run the utility your configuration options are automatically written to the
install.properties
file and they will be used as the defaults the next time the application is configured. One of the following parameters is accepted by the Configuration utility:
Help:
help
This option displays the usage for console and silent modes.
Console mode:
console
Runs the Configuration utility in text mode within a command window.
Silent mode:
silent
Silent mode:
silent
. Runs in the background requiring no user interaction. This option requires that you have already run the Configuration utility in default mode, which sets configuration options in the i
nstall.properties
file.
An example of running the Configuration utility from the command line is
config_deploy help
Configuration Help
The Configuration utility contains online help for each panel of the utility. Access Help by clicking the
Help
button in each panel. Additionally you can access the help from
{install_dir}/server/tomcat_config/doc/html/config
.

0 COMMENTS

We’d like to hear from you!