Start the Process Task Manager and set initial configuration
parameters on the Process Engine server
virtual server.
Use the procedures in this task to configure and start the
default virtual server instance for Process Engine. Complete these procedures
on only one node in a Process Engine farm.
If you are in a Microsoft cluster server environment, configure all
additional Process Engines to
use the same database as the initial Process Engine.
- Open
your completed Installation and Upgrade Worksheet file.
Tip: In the worksheet file, verify that the command is enabled. To view only Process
Task Manager values, filter by Process Task
Manager in the Installation or Configuration
Program column.
- Log on to the Process Engine server
as pe_install_user .
- Start the Process Task Manager,
as follows:
Option |
Description |
Windows® creating
the virtual server with a name of default |
Select . |
Windows assigning
a specific name to the virtual server |
At a command prompt, change to the installation directory,
by default C:\Program Files\IBM\FileNet\ProcessEngine,
and enter vwtaskman virtual_server_name where virtual_server_name is
the virtual server name. |
UNIX® creating the
virtual server with a name of default |
Enter ./vwtaskman at the command prompt.
The terminal should support X Windows and
the DISPLAY environment variable should be set. |
UNIX assigning a
specific name to the virtual server |
Enter ./vwtaskman virtual_server_name where virtual_server_name is
the virtual server name at the command prompt. The terminal should
support X Windows and the
DISPLAY environment variable should be set. |
- In the Database subtab, enter the
Database Type, Database version (for DB2 only), Database Name, Database
User Name and password, Database Host and Database Port from the installation
worksheet. If you are using DB2® for z/OS®,
enter DB2 for z/OS instance
name in Database Name field. As an alternative to entering the Database
Host, Port, and Database Name, the JDBC Driver URL can be manually
configured.
Important: If the Process Engine is using Oracle RAC, you
must enter the JDBC URL manually in the JDBC Driver URL field to connect
to the Process Engine database.
- Click Next. Process Task Manager
will connect to the database. If you cannot connect to the database
with the information provided here, or the JDBC driver cannot be accessed,
you will get an error and must resolve it before continuing.
- Enter the tablespace information for DB2 or Oracle databases
or the filegroup information for SQL Server databases using the values
from your installation worksheet. If you are using DB2 for z/OS, enter the real DB2 for z/OS database name in the Data
Tablespace field. Click Next to proceed.
- Accept or change the default Process Engine Main Port and Process Engine Naming Service Port and
click Next to proceed with configuration. These
port numbers must be unique for each virtual server on a machine.
- Provide the Content Engine URI,
Service Username and password, Administrator Group, and optional Configuration
Group names identified on your installation worksheet. The
value for the Content Engine URI
defaults using information entered when the Content Engine client software was installed.
If there is no value in this field you might need to reinstall and
configure the Content Engine client
software.
- Click Test connection to verify
that all information entered in this screen is correct and that you
can connect to the Content Engine using
the provided authentication information. If there are
errors returned they must be resolved before proceeding. After testing
the connection returns a message indicating success, click Next
- Click Finish to save the security
and database information to the Process Engine database. Information is written to the database and an initial set of
tables are created in the database. If there are errors trying to
create the tables or write to the database they must be resolved before
proceeding.
- In a farmed configuration, return to the General tab
and enter the load balancer virtual name in the Process
Engine Server Virtual Host field.
- After all parameters have been entered, click OK.
- When prompted by Process Task Manager to restart the software,
click Yes. Process Task Manager will restart
the software automatically on all servers in the farm.
- Check Automatically Restart to have
the Process Engine software automatically
restart when the server is restarted.