Server Installation, Configuration, and Deployment > JBoss > Configuration
  

Configuration

The topics in the section provide information on pages within the Configuration Wizard.

Engine Configuration

This panel provides information required for Process Server to access your database server. Choices on this panel change the settings in the configuration of the aeEngineConfig.xml file which is contained in the activevos.war file.
Field Name
Default Value
Descripton
Database
MySQL
This setting is used internally by Process Server to handle communication for the supported database.
Select Next to save your value and continue

JNDI Configuration

The Server JNDI Configuration panel allows configuration of the various files that contain JNDI references.
In general, if you have not preconfigured resources on your application server, it is not necessary to change the default values. If you have already configured resources you must match the field to your corresponding resource.
You should configure JNDI resources before completing this configuration. Refer to Configuration for guidelines on configuring a JDBC Data Source and a Work Manager.
You should preconfigure a work manager and timer manager on your application server prior to completing this configuration. However, you can configure them later and rerun the configuration. If you have already configured resources you must match the field to your corresponding resource.
Field Name
Default Value
Description
Database JNDI
jdbc/ActiveVOS
The Process Server Database resource must be assigned a JNDI name for location at run-time. Enter this JNDI name in the text box provided.
Work Manager JNDI
wm/ActiveVOS (suggested name)
Name that is used to connect to a WebLogic Work Manager that you have created in the WebLogic Application Server's Process Console.
Note: If you do not configure a WebLogic Work Manager, Process Server ignores this name and instead use its own internal Work Manager. Enter your WebLogic JNDI name if it differs from the suggested name.
Work Manager JNDI
wm/ActiveVOS (suggested name)
Name that is used to connect to a WebSphere Work Manager that you have created in the WebSphere Application Server using the Process Console.
Note: If you do not specify a Work Manager JNDI name then ActiveVOS will ignore this name and instead use its own internal Work Manager. Enter your WebSphere JNDI name if it differs from the suggested name.
Timer Manager JNDI
tm/ActiveVOS (suggested name)
Name that is used to connect to a WebSphere Timer Manager that you have created in the WebSphere Application Server using the Administration Console. Note: If you do not specify a Timer Manager JNDI name then ActiveVOS will ignore this name and instead use its own internal Timer Manager. Enter this JNDI name if it differs from the suggested name.
Select Next to save your value and continue.

Process Central Configuration

The Process Central Communications Configuration panel allows setting of the connection information to be used when Process Central communicates with the Process Server. This panel allows the configuration of the following:
Parameter
Default Value
Description
Session Timeout
30 seconds
The session timeout sets the duration that an inactive session will remain connected to the Process Central database.
Process Central AeTaskService URL
http://[hostname.domainname]:[port]/active-bpel/services/AeB4PTaskClient-taskOperations
(Required) Process Server can run on the same or a different server than the Process Central. Modify this URL to specify the host and port where Process Server runs. Modify the protocol, to add security, if needed. The URL displayed is the default URL of the Web service that Process Central needs to call Process Server.
After entering this information, click Next to save your values and to continue.

Database Configuration

Note: It is highly recommended that these panels only be used for development servers. Refer to your application server user guide and your database administrators guide for configuring data sources for production installations.
The panels that follow provide the ability to configure a data source file. The information that is entered here is only a subset of the options that can be configured for a data source. Ensure that you have completed the configuration of a JNDI data source prior to completing this step. For details, see Configuration.
Setting
Default Value
Description
Driver Class
None
(Required.) The name of your JDBC driver's implementation of java.sql.driver. Some driver examples are shown here:
  • - MySQL: com.mysql.jdbc.Driver
  • - MS SQL SERVER: com.microsoft.sqlserver.jdbc.SQLServerDriver
  • - ORACLE: oracle.jdbc.OracleDriver
  • - DB2: com.ibm.db2.jcc.DB2Driver
Driver url
None
(Required.) Used to connect to your database. Typical URLS are shown here; however, refer to your database and JDBC driver documentation for further information.
  • - MySQL: jdbc:mysql://[host]:[port]/[database_name]?useUnicode=true&characterEncoding=UTF-8&characterSetResults=utf8
  • (Default port is 3306) UTF-8 encoding is required.
  • - MS SQL SERVER: jdbc:sqlserver://[host]:[port];databaseName=[database_name]
  • (Default port is 1433) UTF-8 encoding is highly recommended.
  • - Oracle: jdbc:oracle:thin:@//[host]:[port]/[database_name]
  • (Default port is 1521) UTF-8 encoding is highly recommended.
  • - DB2: jdbc:db2://[host]:[port]/[database_name]
  • DB2 = (Default port is 50000) UTF-8 encoding is highly recommended.
Example: jdbc:mysql://localhost:3306/ActiveVOS?useUnicode=true&characterEncoding=UTF-8&characterSetResults=utf8
Database name
ActiveVOS
(Required.) The name of your database. It must match the database_name provided in the Driver URL.
Driver jar
None
Driver .jar file must be selected using the Select File button to the right of this field. Select your driver file so that is can be copied to the correct location.
Some driver file examples are shown here, but we strongly recommend you check the Prerequisites details before making your selection.
  • - MySQL: mysql-connector-java-5.0.7-bin.jar
  • - MS SQL SERVER: sqljdbc.jar
  • - Oracle: ojdbc14.jar
  • - DB2: db2jcc.jar and db2jcc_license_cu.jar
Username
bpeluser
(Required by default.) The name associated with the privileges to access your database. Unless you modified this name, it is described in the DDL schema.
Password
bpel
(Required by default.) The password of the above Username. Unless you modified this name, it is described in the DDL schema.
Connection Timeout
1000
The maximum time to wait in milliseconds for a database connection to become available.
Minimum Connections
10
The maximum number of idle connections in the database pool.
Maximum Connections
100
The maximum number of connections in the database pool.
Validate Connection
Checked
Checking this entry will cause the configuration wizard to attempt to connect to your database with the supplied information
Validate Connection. After you enter all required database connection information and click Next, the utility checks that your driver jar and URL are valid and that the database name matches the name in the URL. The utility does not check the username and password of the database. If the server cannot make a connection because these are in error, you can re-run the configure-deploy utility and enter new names. All other values are preserved.
After entering this information, click Next to save your values and to continue.

Configuration and Deployment

Please review the important information in Prerequisites and Installation Checklist before running Process Server configuration.
This panel allows you to select what operations you would like to perform. Subsequent panels show the details of each option. The selections and the results are described in the table below.
The configuration wizard collects details for Process Server to communicate with a selected database, a work manager, and Process Central. It can deploy applications and install the database schema. Select the options you want to execute
Note: Many of the options presented in the configuration wizard are only used within development servers. The availability of these options on production servers may be limited or unavailable due to security restrictions or other limitations imposed by the administrators of the target server, or by your particular configuration and situation.
Select the options you would like to perform and click Next to continue.
Selection
Description
Configure Process Server
Allows the setting of the parameters required to start and run the Process Server and set the security options for the application.
Configure Process Central
When enabled, allows setting of configuration parameters for Process Central application.
Configure Application Resources
Allows configuration of your work manager4, timer manager, JAAS logins, and database resource.
Configure Database
Configuration of an application server's native data source files or wizards.
Deploy Applications and Resources
Deployment of Process Server and datasource.
Deploy Applications
Select deployment of Process Server and Process Central. It also allows you install the database schema. Note that you can run the config-deploy tool more than once on separate servers, to deploy Process Central to different machines.

Security Configuration

Process Server can be deployed in a secured manner. The Security Configuration panel allows you to configure the security parameters that will be applied to the Process Server Console, and deployed BPEL process services. Select the security options you want to enable
After completing configuration, you must assign security roles to users and groups. You can find details on configuring security in the Process Server Guide elsewhere in this help
If you have a license for the multi-tenant feature, you must enable security
After entering this information, click Next to save your values and to continue.

Administrative Functions

These functions add security parameters to the Process Consoles and services by setting the following roles:
abAdmin
Users associated with this role have full administrative rights to Process Server.
abBusinessManager
Users associated with this role have access to process instance details (but cannot operate on them). They can monitor active processes and tasks, and work queues. They have a read-only view of process instance details.
abDeployer
Users associated with this role have rights restricted to deploying business process archive files to Process Server.
abDeveloper
Users associated with this role have rights restricted to service artifacts, endpoint information, and sample messages for the services they consume and expose (that is, processes) after they are deployed. Developers need the ability to deploy process deployment archives, initiate process execution and analyze them. Developers also need to configure global function contexts for custom functions, URN mappings, and the ability to schedule process execution. Specifically, this user has access to the Active Process list, the Process Instance View, the Active Task and Work Queues lists, the Server Log, the Dashboard and all reports, and the catalog's content.
abOperator
Users associated with this role have rights restricted to operating the system. These include observing the functionality of processes, managing process instances using the process instance detail view, running reports, logging, viewing exceptions, acquiring information on service operations, adding and removing tenants, and managing the scheduled database delete schedule.
abTaskClient
Required. You must configure permission to access Process Central for all users. In addition, users who interact with the Human Task (WS-HT) API must have this role.
Process Central presents a login page to users.

Process Services

The process services adds security parameters to the Web Services handler for all deployed BPEL services with a role. The services listed at http://[host]:[port]/active-bpel/services are secured. The process services (roles) are:
abRestrictedServiceConsumer
Users associated with this role cannot access a service unless it is deployed with allowed roles specified in the pdd and the user belongs to at least of these roles. If no roles are specified in the pdd, access to services with no roles specified in the pdd are also denied. Users in this role can view the wsdl files for other services like abServiceConsumer; however, they are blocked at runtime.
abServiceConsumer
Users associated with this role have rights restricted to start process instances of deployed processes, including from Process Central, the Eclipse Web Tools Project, or other client application,such as SOAPUI.
abTenantAdmin
(For a Multi-Tenant licensed server only.) Users associated with this role have rights to deploy and manage contributions into a configured tenant on the server.
Based on a Tenant Definition configured by the Process Server administrator (with the abAdmin role), a tenant administrator user can log into the tenant context on the server. A service consumer user can create process instances for processes deployed to the tenant context.

Identity Service Consumer

The identity service consumer adds security parameters to the Web Services handler for Process Identity service used by the Process Central application using the following roles:
abIdentityListConsumer
Only users associated with this role or abAdmin have rights to submit Web Service requests to the identity service from Process Developer.

Deployment Options

The Deployment Options panel allows the selection of deployment items. The check boxes on this panel are as follows:
Install database schema (New Installation Only)
This option controls whether or not the configuration wizard will install the Process database schema to your database.
Note: This option requires that the user information and database name entered in the Database Configuration Panel have already been created. Additionally, this option should not be selected by users wishing to update from a previous database version. For upgrade instructions please see the Configuration Wizard document.
Install database schema
This option controls whether or not the configuration utility installs the ActiveVOS database schema to your database. Selecting this option will present a Database Configuration panel on the next wizard page
Note: Do not select this option if you are updating from a previous database version. For upgrade instructions please see the Configuration section of your documentation
Install database descriptor
Checking this option installs the application server specific database descriptor file to your application server. Selecting this options eliminates the need to create the descriptor file through application server management consoles.
Install Application Resources
Checking this option installs the Process Server resources to your application server, including settings for work manager, timer manager, JAAS login and database resource.
Deploy Process Server
Checking this option installs the Process Server to your application server.
Note: If you plan to enable clustering, you must re-run this configuration utility and, on the last page, select a different directory for deployment.
Deploy Process Central
Checking this option installs Process Central to your application server.
If you want to install Process Central to a different server, re-run the config-deploy utility on that server.
After entering this information, click Next to save your values and to continue.

Application Server Path

For each node in a cluster, provide a new Directory for deployment; for example, jboss\[your server]\deployments.
After entering this information, click Next to save your values and to continue.