Installing the Process Server on Nodes in the Cluster
Installing the Process Server on Nodes in the Cluster
If you have a clustered environment, install the Process Server on all nodes of the cluster to which you must deploy the Process Server application. Complete the installation on one node of a cluster before you proceed to install on another node of a cluster. You must ensure that the path for the Process Server installation is the same on all the cluster nodes.
When you install the
Process Server
on RedHat Linux, do not use the root user. The root user does not have a
.profile
, which InstallAnywhere requires. Instead, create and use a separate user profile to install the
Process Server
.
Start the WebSphere deployment manager, and then start the nodes of the WebServer cluster on which you want to run the Process Server.
Start the WebServer cluster.
Open a command prompt, and navigate to the following directory:
<
MDM Hub distribution directory
>/<
operating system name
>/mrmcleanse
To start the Process Server installer on a cluster node, run the following command:
Select the language for the installation, and then click
OK
.
The
Introduction
window appears.
Click
Next
.
The
License Agreement
window appears.
Select the
I accept the terms of the License Agreement
option, and then click
Next
.
The
Choose Install Folder
window appears.
Choose the default location to install the Process Server, or browse to choose a different location.
Click
Next
.
Process Server
fails to load if the total length of the path exceeds 256 characters or includes spaces in the directory or folder names.
On UNIX, the
Choose Link Folder
window appears.
On Windows, the
Choose Shortcut
Folder window appears.
Select a location for the product icons, and click
Next
.
The
Enter Location of License File
window appears.
Click
Choose
to select a license file, and click
Next
.
The
Application Server
window appears.
Select WebSphere, and then click
Next
.
The
WebSphere Application Server Home
window appears.
Configure the following WebSphere settings:
Choose a path to the WebSphere application server, and click
Next
.
The
WebSphere Security Selection
window appears.
Select whether WebSphere is security enabled or not.
If you select
No
, and then click
Next
, the
WebSphere Application Server
window appears. Default is
No
.
You do not need to provide values for the server name, port, and profile name. After the installation, you will set the values in the
cmxcleanse.properties
file.
You do not need to modify default values for the cluster server name, SOAP port, and profile name for the WebSphere application server cluster. You will later set the values in the
cmxcleanse.properties
file.
If you select
Yes
, and then click
Next
, the
WebSphere Application Server and User Credentials
window appears.
Specify the WebSphere user name and the WebSphere password.
Configure cleanse engine settings for the cleanse engine you use.
If you use
Informatica Address Verification
, specify the Configuration file and Parameters file locations and the Correction Type parameter.
If you use Business Objects DQ XI, specify the Host, Port, and Sub File parameters for the Business Objects DQ XI cleanse engine.
Click
Next
.
On the Product Usage Toolkit page, select the
Environment Type
.
If you have a proxy server, select
Yes
, and enter the proxy server details. Otherwise, select
No
, and click
Next
.
You can enter the following proxy server details:
Proxy server name/IP
Proxy server port
Proxy server domain name. Leave blank if not applicable.
Proxy server user name. Leave blank if not applicable.
Proxy server password. Leave blank if not applicable.
Select the
No, I will run it later
post installation setup script option.
The
No, I will run it later
option allows you to manually run the post installation script later.
Click
Next
.
The
Pre-Installation Summary
window appears.
After the summary window displays the options you want, click