1. Configure AIX
Note: Perform this procedure on both translator servers.
Regardless of how much physical memory a server has, the amount of memory
that each process can address is limited by the operating system. On many
operating systems, each 32-bit process can address 4 GB of memory. By default,
the operating system reserves some of the 4 GB for kernel usage and some
for application usage. However, you can configure some operating systems
so more memory is reserved for application usage and less for kernel usage.
Note: The Translator runs as a 32-bit process, regardless of the underlying
server architecture or operating system.
By default, AIX® reserves 1.75 GB for kernel usage and 2.25 GB for application
usage. Using the very large address-space model, AIX reserves 0.75 GB for
kernel usage and 3.25 GB for application usage. This results in a very
slight decrease in operating system performance, but will allow you to
maximize the number of simultaneous users that the translator can host
at maximum performance.
For this scenario, configure AIX to use the very large address-space model.
For more information on AIX‘s very large address-space model, see Large
Program Support in the pSeries®
and AIX information center.
2. Install WebSphere Application Server Network Deployment
Install WebSphere® Application Server Network Deployment on
both translator servers.
For detailed installation instructions,
see Installing
the product and additional software
in the WebSphere
Application Server information center.
3. Enable secure communications
The Secure Sockets Layer (SSL) protocol provides secure
communications between a client and the Translator. You can either:
- Enable SSL within WebSphere® Application Server, or
- Configure WebSphere Application Server to work with an external HTTP
server that uses SSL.
Note: Enable secure communications on both translator servers.
For detailed instructions, see Configuring
Secure Sockets Layer (SSL) in
the WebSphere
Application Server information center.
4. Create a managed node
Note: Perform this procedure on both translator servers.
To create a managed node:
1. Create a profile for the managed node.
* Profile Management Tool – Run /usr/IBM/WebSphere/AppServer/bin/ProfileManagement/pmt.sh
to launch the Profile Management Tool, then create a Custom Profile.
* Command line – Run /usr/IBM/WebSphere/AppServer/bin/manageprofiles.sh
-create -templatePath /usr/IBM/WebSphere/AppServer/profileTemplates/default
-profileName cslpar2Node1
2. Go to the bin of the profile you just created:
/usr/IBM/WebSphere/AppServer/profiles/cslpar2Node1/bin
and federate the profile specifying the server that is running Deployment
Manager. For example, if cslpar1 is running the Deployment Manager process
and cslpar2 is the node that you just created, then run the following command:
addNode.sh cslpar1
5. Install the Webform Server Translator
Note: Perform this procedure on both translator
servers.
To install the Translator:
1. Reboot the server immediately before installation.
2. Copy the db2jcc.jar DB2® driver from the Access Control Database server
to the Translator server.
3. Insert the Lotus® Forms Server for AIX® CD.
4. Run the installer LFServer_30x_WebformServer_AIX.bin.
5. Click Next to accept the default installation directory.
6. Select only Translator and make sure all other options are not selected.
7. Click Next.
8. Select Managed Node installation and click Next.
9. Select Deploy to WebSphere Application Server and click Next. Make sure
Deploy Sample Servlet is not selected.
10. Select DB2 and enter the database information:
* Database name
* Host IP and port
* Username and password
* Location of the db2jcc.jar DB2 driver on the Translator
server
Then click Next.
11. Enter the location of WebSphere® Application Server on the Translator
server and click Next.
12. Enter the Translator deployment details:
* Profile – Ensure that the profile name is correct
for your WebSphere Application Server configuration on the Translator server.
* Cell – Ensure that the cell name is correct for
your WebSphere Application Server configuration on the Translator server.
* Node – Ensure that the node name is correct for
your WebSphere Application Server configuration on the Translator server.
* Server Name – Enter the name that you want to use
for the Translator server (for example, Translator_Server_1 and Translator_Server_2).
* Application Name – Enter the name that you want
to use for the Translator application.
Then click Next.
13. Click Install.
For more information on installing Lotus Forms Server - Webform Server,
see Installing
Webform Server in the Lotus
Forms information center.
6. Configure the Translator
Note: Perform this procedure on both translator servers.
To configure the Translator:
1. Open the translator.properties file in a text editor.
2. Set the fileCacheLocation to the path to the Shared File Cache.
3. Set the fcCacheSize to 250. This represents the maximum number of simultaneous
users that each Translator instance can host at maximum performance.
4. Set logServerHostname to the host running the Log Server.
5. Use the default settings for all other properties.
6. Save the file.
The fcCacheSize setting was calculated as follows:
1. Each Translator server has 8.5 GB of RAM and hosts two instances of
the Translator, so there is 4.25 GB available for each Translator instance.
Under the very large address-space model, AIX® allows 3.25 GB for application
usage. The JVM uses approximately 0.5 GB of memory, but this may vary up
to 0.75 GB, leaving 2.5 GB of memory for each Translator instance to cache
form instances.
2. The maximum form size is 10 MB in memory (including any attachments):
2.5 GB / 10 MB = 250. To allow a margin of safety, set the fcCacheSize
to a slightly smaller value, for example, 200. This means that each Translator
instance can host up to 200 simultaneous users at maximum performance.
The overall system consisting of four Translator instances can host up
to 800 simultaneous users at maximum performance. This is greater than
the expected 250 to 300 simultaneous users.
For more information on configuring the Translator, see Translator
Properties in the Lotus®
Forms information center.
7. Setup the Translator cluster
a. Create the Translator cluster
1. On the Deployment Manager system, login to
the Deployment Manager console.
2. Click System Administration > Nodes and
verify that the Translator nodes are visible.
3. Click Servers > Clusters.
4. Click Add and define the cluster name (for
example, Translator_Cluster).
5. Define a new cluster member for the managed
node you setup on the first Translator server.
6. Define a second cluster member for the managed
node you setup on the first Translator server.
7. Define a third cluster member for the managed
node you setup on the second Translator server.
8. Define a fourth cluster member for the managed
node you setup on the second Translator server.
9. Click Finish and save your changes.
b. Associate the Translator to the cluster
1. On the Deployment Manager system, within WebSphere® Application Server
click Enterprise Applications > TranslatorApp Manage
Modules.
2. Click the check box for module IBM_Webform_Server_Translator_3.0.1.73.
3. Select the cluster (Translator_Cluster) and servers (Translator_Server_1
and Translator_Server_2) you want to associate with the Translator.
4. Click OK and save your changes.
Parent topic: 3.0
Setting up the servers
Previous topic: 3.6
Set up the Deployment Manager system
Next topic: 3.8
Set up the load balancer
|