You can install Process Engine in a Veritas cluster server on a UNIX platform.
Install and configure Process Engine software, and configure and use the FileNet custom agents on Veritas Cluster Server; all steps are applicable for Solaris, AIX, and HP-UX platforms.
Symantec uses Service Groups of resources to provide highly available services to users. The instructions specify how to add resources to a pre-existing service group to provide a highly available Process Engine Service.
Symantec provides a framework to create custom agents that can control and monitor particular resources. FileNet has created custom agents by using the Veritas framework to allow users to create, monitor, and control a Process Engine resource. The agents have been certified by Symantec for use with their Veritas Cluster Server product on Solaris, AIX, and HP-UX platforms.
Important: In a Veritas Cluster Environment the user accounts, by design, must be local and not Network Information Services (NIS and NIS+) users if they are to be used by an agent. This requirement includes the account specified as the Oracle Owner in the Veritas Oracle agent, and the fnsw user account that is used in the Process Engine agent. For more information, see the Veritas Cluster Server and Veritas Agent documentation.
From time to time it can become necessary to recompile the Process Engine Veritas Agent to accommodate a change in the operating system (if the agent is to be used on an operating system on which the agent was not compiled) or a change in the startup and shutdown behavior of the agent (for example to increase the level of
|
monitoring). To recompile the Process Engine Veritas Agent or to produce a new agent binary if needed, follow the instructions in “Recompiling the FileNet Process Engine Veritas agent” on page 85.
“Installing Process Engine in a Veritas cluster server (UNIX)”
You can install and configure Process Engine servers in a Veritas cluster
“Installing the FileNet P8 4.5.1 Process Engine Agent” on page 83 You can install the FileNet P8 4.5.1 Process Engine Agent.
“Verifying Process Engine installation (UNIX)” on page 84
You can verify your Process Engine installation by using Application Engine (Workplace).
“Recompiling the FileNet Process Engine Veritas agent” on page 85 You can recompile the FileNet Process Engine Veritas agent if needed.
Installing Process Engine in a Veritas cluster server (UNIX)
You can install and configure Process Engine servers in a Veritas cluster To install the Process Engine in a Veritas cluster server:
1. Verify that you have performed the required preparation tasks as shown in
“Performing required preparation tasks” on page 35.
2. Install Process Engine in the cluster.
a. Install the Process Engine software and the Content Engine client software on the first node as documented in the platform specific Process Engine installation tasks found in the IBM FileNet P8 Platform Installation and Upgrade Guide.
b. When the cluster group comes online on the next node, remove all files and directories underneath /fnsw/local. Repeat the installation procedure, installing Process Engine software and Content Engine client software.
Repeat, one server at a time, for all Process Engine nodes.
3. Configure Process Task Manager to display on all nodes when Process Engine service starts running under the cluster virtual name.
a. Start Process Task Manager (vwtaskman), on the first Process Engine node if it is not already running.
b. Select the root node in the navigation tree.
c. In the Local Host field enter in a comma separated list of the physical node names of the cluster.
d. Close and reopen Process Task Manager.
4. Follow the instructions for configuring Process Task Manager in the IBM FileNet P8 Platform Installation and Upgrade Guide and skip the last step involving the configuration of the vworbbroker.endPoint property. Instead, return to this task to resume configuration specific to your network protocol and farmed
environment. When configuring security, use the highly available Content Engine URL. For more information, see “Connecting by using Content Engine Web Service Transport (CEWS)” on page 71.
5. From Process Task Manager, add the cluster virtual name registered in DNS for the Process Engine cluster:
Important: This configuration is only required for the first Process Engine.
These are steps that should be performed in connection with the steps for configuring Process Task Manager in the IBM FileNet P8 Platform Installation and Upgrade Guide.
a. Start Process Task Manager (vwtaskman), on the first Process Engine node.
c. On the Advanced page, add the vworbbroker.endPoint property:
Internet protocol version Property entry
IPv4 vworbbroker.endPoint = iiop:
//cluster_virtual_name:port#
/hostname_in_ior
=cluster_virtual_name
Where cluster_virtual_name is the name of the cluster, used by the clients with the Process Engine server.
where:
v cluster_virtual_name is the cluster variable name. For example, in the following table showing example host file entries, the cluster_virtual_name is pe_farm. When configuring isolated region connections points, use the cluster_virtual_name as the DNS name.
v port# is the port on the Process Engine server used for the vworbbroker process handling RPCs from the Process Engine API clients. The default value is 32777.
For example, add iiop://pe_cluster:32777/hostname_in_ior=pe_cluster, where pe_cluster is virtual name of the Process Engine cluster. In this case the hosts file on one of the nodes in the Process Engine cluster might look like this:
Table 20. Example of hosts file on the Process Engine cluster nodes.
Node name Hosts file entry
PE_node1 1.2.3.4 cluster_virtual_namelocal_node_server1 PE_node2 1.2.3.4 cluster_virtual_namelocal_node_server2
where:
v 1.2.3.4 is the network address for the cluster.
v cluster_virtual_name is the name of the cluster
v local_node_server1 and local_node_server2 are the network names for the Process Engine servers.
d. Restart the software when prompted after applying the setting for the vworbbroker.endPoint.
6. Complete the installation and configuration of the Process Engine and verifying the database connection. Do not install any software updates until the entire cluster is installed and configured.
7. Enable automatic start of Process Engine services from the Process Task Manager.
a. Fail over to each node and start the Process Task Manager.
b. Check the box to enable automatic startup of Process Engine Processes.
8. After the cluster has been installed and configured, install any software updates for the Process Engine.
Related tasks
Installing Process Engine
You can install Process Engine software either interactively or silently. A number of configuration steps follow the execution of the Process Engine installation program.
Installing the latest Content Engine client files on Process Engine servers Installing the Content Engine Client files on all Process Engine enables communication between the Content Engine and the Process Engine. You can install these files interactively by using the installation wizard or silently by using the command line and a silent input file.
Configuring Process Task Manager
Start the Process Task Manager and set initial configuration parameters on the Process Engine.
Verifying connection to the Process Engine database
To verify the connection to the Process Engine database, issue the vwcemp command.
Completing post-installation Process Engine configuration (Windows only) You must enable Process Engine to use the largest available contiguous free memory area for shared memory allocations. Otherwise, at some point during normal execution, the system fails to allocate shared memory and ceases to function correctly.
Installing Process Engine software updates
You can install software updates such as modified releases, fix packs, or interim fixes to Process Engine.