Start the Process Task Manager and set upgrade configuration
parameters for an upgrade from version 3.5. After providing input
to the wizard screen, you will execute the vwupgrade tool using those
parameters.
Use the procedures in this task to run Process Task Manager
to configure upgrade parameters for an upgrade from version 3.5. 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 and Port, 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.
- You should not now see the screen prompting for database
tablespaces or filegroups. If you see that screen now, you have been
able to connect to the database but the database user entered in the
database connection information does not have the correct database
permissions. Verify that the database run time user is the Process Engine database user from Process Engine 3.5.
- 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
- Enter the Fnsw Local Directory and Server Host Names. Verify
that the host name is the name of the server where Process Engine 5.0 software is installed.
This value might be pre-populated based on the version 3.5 configuration. If this is a SQL Server or DB2 database, provide the Database
Column Size Factor.
- Click Finish to save the information
to the vwupgrade.properties file.
- As instructed on the summary screen, you must run vwupgrade to
upgrade the Process Engine database from version 3.5.