Server Installation, Configuration, and Deployment > Apache Tomcat > General Information
  

General Information

The Process Server Setup Wizard lets you install a new server or update an existing one.
  1. 1. Download and obtain a license for Process Server.
  2. 2. Download and run the Process Server installation.
  3. 3. To configure and deploy a server, open quickstart_server.html, which directs you to the file you are reading now.
  4. 4. Review the Prerequisites and Release Notes for Process Server by selecting the links in the navigation bar on the right.
Note: If the Setup Wizard detects an existing installation, it lets you either update the existing installation or install the server in a different directory. When you update an existing installation, the Wizard replaces any file that a previous Wizard had installed. All other files in your server's install directory remain as they were.
This is the start of the concept.

Quick Start

Preconfiguration

  1. 1. Create a database (or tablespace) for Process Server. Select the Configuration link in the navigation bar for details.
  2. 2. Process Server needs to be granted the following permissions on your schema:
  3. 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.
  4. 3. Collect the following information that you will be prompted for during configuration:
  5. 4. For an upgrade installation of Process Server, manually install the database schema. For a new installation, you can automatically install the database schema during configuration.
  6. 5. Ensure that the JAVA_HOME environment variable is set.
  7. Note for Tomcat and JBoss: To avoid issues with multiple JDKs, we recommend that you set JAVA_HOME in the application server startup file instead of in the system environment.
  8. 6. Ensure that your JVM memory settings in your application server match the recommendations described in Prerequisites.
  9. 7. MultiSite Installations Only: To configure MultiSite clustering, be sure to review the instructions in Process Server MultiSite Configuration. Access the instructions from the Configuration link in the navigation bar on the right.
  10. 8. Unix Platform Only: After installing any version of the Process Server on any UNIX OS, you may receive an error when starting the server such as cannot write to temp location [/temp]. This is due to an OS restriction on the number of files that can be created. To avoid this error, before installing the server edit your UNIX security configuration file directly to allow a larger number of files to be opened. In UNIX the parameter NOFILE sets the maximum number of files that can be opened by a single process. For example, in the file /etc/security/limits.conf you could add the line - nofile 10240 to raise the limit from the default 1024 value. 10240 should be large enough. If you are unsure, setting "unlimited" can be considered.

Configuration and Deployment

  1. 1. In your ActiveVOS installation folder, locate the [server]-config>bin folder, and select the config-deploy utility.
  2. 2. Complete the configuration and deployment. Use the online Help as needed.
  3. 3. Use your server container's documentation for help in starting the Process Server.
Note: When you are deploying Process Server to a Tomcat server, activebpel-cert.war is not deployed. You must copy it from {installation_directory}\server-enterprise\tomcat_config\webapps to {Tomcat_Home}\webapps directory when deploying an SSO configuration

Add Your License

  1. 1. You will need access to your Process Server license.
  2. 2. Open the Process Console in a browser:
  3. http://[host]:[port]/activevos
  4. 3. Add your license on the License page. Select the Admin menu item of the Process Console and then select License. Select Add and copy and paste all of the Process Server license into the dialog. Then select the Server Status navigation menu item and select Start Server to start the Process Server.

Prerequisites

Process Server relies on a valid license and third party software components. Ensure that your application server environment meets the requirements before beginning the configuration procedure.

Process Server Licensing

A valid license is required to run Process Server. You enter the license information after you've configured Process Server. Do this as follows:
  1. 1. Start Process Console.
  2. 2. Select Admin | License. (Admin is in the toolbar; License is about a third of the way down on the left.)
  3. 3. Press the Add License button, copy and paste all of the Process Server license into the dialog, and then press the Add License button.
  4. 4. Select the Server Status link near the ver top of the left area press the Start Server button to start the Process Server
Obtaining a License Key
If you did not receive your license prior to receiving the software, contact the Informatica sales department.
Our sales support staff can assist you with licensing questions.

Hardware Requirements

Application Server Hardware
Process Server runs within different server containers, and the hardware requirements of the server are superseded by the requirements of the container.
Database Hardware
Process Server application supports multiple database servers and has no additional requirements besides those of your selected database server.
Note: For maximum performance, we recommend that you run Process Server and its database schema on separate servers.
JVM Memory Requirements
We strongly recommend that you run your application server with at least the following memory settings:
-Xms256m -Xmx1024m -XX:MaxPermSize=384m
where Xms is starting memory, Xmx is maximum memory, and MaxPermSize is the amount of memory set aside for loading class files.
Disk Space Requirements
At least 1 GB of disk space is required to install the Process Server application.
Note: Considerably more disk space is required to run your applications. The amount is dependent on several factors including logging levels you select, number of processes you run, and size of processes.

Software Requirements

Specific versions of Eclipse, client and server operating systems, application and database servers are supported. Support means that Informatica will assist customers with the installation and operation of Business Process Manager products on these 3rd party product versions.
Also certified are specific combinations of 3rd party products. Use of Certified Systems described here will reduce the risk of problems as a result of extensive testing of Business Process Manager with these specific versions. Database connectivity is required for Process Server persistence and version control of deployed processes. It is recommended that the database resides on a dedicated server.
The following software is supported for use with Process Server:
Operating Systems
Web Browser
Application Servers
Note: Other releases of these servers should work. However, they have not been tested.
JAVA Environment
If you are running a Linux distribution and you are using the US ASCII codeset, you will need to add the following startup parameter to your JVM:
-Dfile.encoding=UTF-8 encoding
Application Server
JVM
Comment
Tomcat
Sun JDK 1.7
To avoid issues with multiple JDKs, we recommend that you set JAVA_HOME in the application server startup file instead of in the system environment.
JBoss
Sun JDK 1.7
To avoid issues with multiple JDKs, we recommend that you set JAVA_HOME in the application server startup file instead of in the system environment.
WebLogic
Sun JDK 1.7
WebSphere
IBM J9 VM build 2.4, J2RE 1.6.0
Setting JAVA_OPTS for DOM Processing
If you are using a Java server and the DOM being produced is incorrect, you should add the following definitions to the definition of JAVA_OPTS in your server startup script
set JAVA_OPTS=%JAVA_OPTS%
-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
Note: If this is not set, the classloader must search through the classpath to locate the appropriate class. Depending on the size of the classpath, this operation can degrade performance.
Database Servers
Process Server uses standard database servers as the persistent storage mechanism. You must have access to one of the supported database servers with the proper privileges to create databases and tables as well as privileges to update, insert and delete into those tables.
Supported Databases
Certified JDBC Database Drivers
A JDBC database driver is required. For certain configurations, you will be asked to provide the location of driver during configuration. For other configurations, you will be instructed to use your application server administration console to configure the database.
Note: For a clustered environment, you must install the driver to each node in the cluster.
Database Server
JDBC Driver
MySQL
mysql-connector-java-5.1.6-bin.jar
Microsoft SQL Server
sqljdbc.jar (1.2), sqljdbc4.jar. JBoss 7.x requires sqljdbc4.jar
Oracle
ojdbc6.jar
DB2 9.7
db2jcc_license_cu.jar, db2jcc.jar.JBoss 7.x requires db2jcc4.jar
Process Server
Process Server supports 32-bit and 64-bit Java Virtual Machines (JVM) for the Windows and Linux systems listed above. When installing Process Server on a 64-bit server, the 64-bit JVM supported for a given application server is required.
Process Developer
Process Developer embeds Eclipse 3.7.2 and a 32-bit version of JRE 7 for Windows systems allowing it to run on both 32-bit and 64-bit Windows operating systems and hardware environments. The Linux distribution of Process Developer does not embed the required 32-bit version of JRE 7. Users must install JRE 7 separately. Users wishing to use a 64-bit version of Eclipse must download the 64-bit version of Eclipse for RCP and RAP Developers, and then use the Process Developer Plugin installation.

Before You Configure and Deploy Process Server

Third party software components are required to be installed prior to configuring and deploying Process Server.
Application Server must be Installed
An application server provides Process Server a framework within which to run. Install the appropriate supported server container according to software vendor's documentation on each machine intended to run Process Server.
Note: Set up clustering according to your software vendor's documentation. Once clustering is set up on the application server, follow our documentation for configuring clustering.
Database Server must be Installed
Process Server requires only one database server per any number of application servers running in a cluster.
All databases require a user with administrative rights to the computer in order to install them. Process Server also requires a connection to your database server. This user needs the proper privileges to connect to the Process Server database, update, insert and delete records within that database.
MySQL Configuration Note
A BPEL process can send and receive variables with attachments such as images or documents. Attachments may be large or numerous, causing database connection errors.
To avoid connection errors to MySQL Server, you may need to configure MySQL with more allocated memory than the default of 1MB.
To configure MySQL:
  1. 1. Open MySQL Administrator. (If unavailable, see the note below.)
  2. 2. Select Startup Variables.
  3. 3. Select Advanced Networking.
  4. 4. In the Data/Memory Size panel, enable Max Packet Size.
  5. 5. Set the packet size higher than the default of 1MB. The size depends on the attachment sizes you expect.
  6. 6. Apply changes.
Note: If MySQL Administrator is not available, refer to the MySQL documentation regarding how to set the max_allowed_packet setting for your environment.
About the Process Server Database Schema
Process Server provides database schema definition files for all supported databases. Before you start the configuration and deploy utility, refer to Configuration topic in this help for specific recommendations on how to install the schema for your database.

Installation Folders

Download and extract the installation folders as described in Quick Start. The following describes the contents of the Process Server installation:
{install_dir}/server-enterprise
quickstart_server.html. Open this file for quick start and complete details for configuration and deployment.
{install_dir}/server-enterprise/tomcat_config/bin
Configuration and deployment tool
{install_dir}/server-enterprise/tomcat_config/conf
Configuration files needed by the configuration and deploy utility
{install_dir}/server-enterprise/tomcat_config/ddls
Database schema to be installed automatically (recommended) or manually, as described in Configuration
{install_dir}/server-enterprise/tomcat_config/doc/html/config
Copies of the Configuration utility's online help files. These files are accessible from the Help button within the utility.
{install_dir}/server-enterprise/tomcat_config/shared
Files that will be automatically copied to your deployed Process Server
{install_dir}/server-enterprise/tomcat_config/webapps
Files that will be automatically copied to your deployed Process Server

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

Note: You will need to manually alter the install.properties file in you are using JBoss AS 7 (EAP 6) and up. for information, see Apache Tomcat Pocess Server and Resource Configuration.
Before running the Configuration utility, perform the following pre-configuration steps:

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:
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.
Install a new database schema
  1. 1. Identify your DDL. Use the information provided in the table below to locate the correct DDL file.
  2. 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
  3. 2. Copy the DDL file from above, and rename it.
  4. Note: The original files must remain unchanged for the Configuration utility to work properly
  5. 3. (Optional) Modify the database name. Be sure to see the notes above.
  6. 4. Execute the DDL script.
  7. 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
  8. 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. 1. Shutdown Process Server before executing a database upgrade.
  2. 2. Make a backup copy of your database.
  3. 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. 4. For each upgrade that needs to be applied perform the following:
    1. a. 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.
    2. MYSQL
      {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-MYSQL-PATCH-{patch number}.SQL
      {install_dir}/server/jboss_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-MYSQL-PATCH-{patch number}.SQL
      MS SQL SERVER
      {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-SQLSERVER-PATCH-{patch number}.SQL
      {install_dir}/server/jboss_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-SQLSERVER-PATCH-{patch number}.SQL
      ORACLE
      {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-ORACLE-PATCH-{patch number}.SQL
      {install_dir}/server/jboss_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-ORACLE-PATCH-{patch number}.SQL
      DB2
      {install_dir}/server/tomcat_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-DB2-PATCH-{patch number}.SQL
      {install_dir}/server/jboss_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-DB2-PATCH-{patch number}.SQL
    3. b. Execute the DDL script.
    4. 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.

Deploying Process Server to a JBoss Domain Using the jboss-cli Utility

You can now deploy Process Server using the JBoss domain deployment features if you are using JBoss AS 7 (EAP 6) and up. Using this features requires that you manually edit the install.properties file, which is located within the jboss_config subdirectory of your Process Server installation.
When you are deploying to a domain, the config_deploy utility calls jboss-cli, which will:
The scripts used with jboss-cli are saved in the config_deploy deploy directory so that, if necessary, you can reuse them.
When running Process Server unsecured on JBoss 7/EAP6, a security domain is still required and one is set up for you. However, this domain is not automatically created when you are deploying JBoss as described in this section and you will have to create it. While what you create will be unique to your environment, it will take the following form:
<security-domain name="ActiveVOS">
<authentication>
<login-module code="org.jboss.security.auth.spi.IdentityLoginModule" flag="required">
<module-option name="principal" value="aeadmin"/>
<module-option name="roles" value="abAdmin,abTaskClient"/>
</login-module>
</authentication>
</security-domain>

Multisite Configuration

For details, see Process Server MultiSite Configuration.

JBoss Application Server Requirements and Considerations

Installation of the JDBC Driver
Process Server requires that you provide a JDBC driver to connect to your database. You must install the database driver into each server in the cluster, if you are making server clustering available. Refer to your application server's user guide for information on installing the appropriate JDBC driver
Note: 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. For DB2, JBoss 7.x requires db2jcc4.jar.
High Availability and Clustering
The default JBoss server configuration is not configured for high availability or clustering. The standalone server that is provided with JBoss has standalone-ha.xml and standalone-full-ha.xml configuration files that enables these features.
Configuring Security
You can find details on configuring security roles in Process Develoepr Help or in the Infocenter

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:
Use one of the following techniques to correct errors:

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

Installation Checklist

This section provides a list of most of the items that you should either have completed or information noted prior to attempting to install Process Server.
Hardware
Software
License Information
Database Information
Server Container Information

Glossary

API
Application Program Interface, a set of routines, protocols, and tools for building software applications.
Application Server
Also called an appserver. A program that handles all application operations between users and an organization's backend business applications or databases. Application servers are typically used for complex transaction-based applications. To support high-end needs, an application server has to have built-in redundancy, monitors for high-availability, high-performance distributed application services and support for complex database access.
DDL
Data Definition Language is used to specify a database scheme as a set of definitions expressed in a DDL script. The basic idea is to hide implementation details of the database schemes from the users.
EAR
J2EE modules that comprise an application are assembled into a single application Enterprise Archive (EAR) file.
J2EE
Java 2 Platform Enterprise Edition, a platform-independent, Java-centric environment from Sun for developing, building and deploying Web-based enterprise applications online.
Java
A high-level programming language developed by Sun Microsystems. Java is an object-oriented language similar to C++, but simplified to eliminate language features that cause common programming errors. Java source code files (files with a .java extension) are compiled into a format called bytecode (files with a .class extension), which can then be executed by a Java interpreter.
JAR
Java Archive, a file format used to bundle all components required by a Java applet. JAR files simplify the downloading of applets since all the components (.class files, images, sounds, and the like) can be packaged into a single file. In addition, JAR supports data compression, which further decreases download times.
JNDI
Java Naming and Directory Interface (JNDI). Allows Java-enabled applications to use a unified interface to multiple naming and directory services in the enterprise. Part of the Java Enterprise API set. JNDI works with other J2EE technologies to organize and locate components in a distributed computing environment.
JVM
Java Virtual Machine. An abstract computing machine, or virtual machine, JVM is a platform-independent programming language that converts Java bytecode into machine language and executes it.
URL
Uniform Resource Locator, the global address of documents and other resources on the World Wide Web.
WAR
Java modules that comprise an application are assembled into a single application Web Archive (WAR) file.
Web Server
A Web Server a computer that delivers (serves up) Web pages. Every Web server has an IP address and possibly a domain name. For example, if you enter the URL http://www.pcwebopedia.com/index.html in your browser, this sends a request to the server whose domain name is pcwebopedia.com. The server then fetches the page named index.html and sends it to your browser. That request can also cause complex logic to be executed and manage database access.
XML
Extensible Markup Language, a specification developed by the W3C. XML is a pared-down version of SGML, designed especially for Web documents. It allows designers to create their own customized tags, enabling the definition, transmission, validation, and interpretation of data between applications and between organizations.