Process Server needs to be granted the following permissions on your schema:
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
.
Collect the following information that you will be prompted for during configuration:
Host, port number, and database name where you are deploying Process Server
The full path to a supported JDBC database driver
Driver implementation class name
Database username and password
Hints and examples of this information are provided in the appropriate page of the Configuration utility's online Help.
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.
Ensure that the
JAVA_HOME
environment variable is set.
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.
Ensure that your JVM memory settings in your application server match the recommendations described in
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.
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
In your
ActiveVOS
installation folder, locate the
[
server]-config
>bin
folder, and select the
config-deploy
utility.
Complete the configuration and deployment. Use the online Help as needed.
Use your server container's documentation for help in starting the Process Server.
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
You will need access to your Process Server license.
Open the Process Console in a browser:
http://[host]:[port]/activevos
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