Configuring a clustered server environment for IBM Mashup Center (V1.0)

This topic describes how to set up a cluster configuration for IBM Mashup Center using two or more server nodes and a WebSphere Application Server (WAS) Deployment Manager server.

Do the following steps:

Step 1: Preparing the primary node

In this step, you will prepare the primary node in the cluster. This step includes installing IBM Mashup Center and configuring the database.

Install IBM Mashup Center. For installation instructions, see the IBM Mashup Center Quick Start Guide.

Configure DB2 for Lotus Mashups. See Confguring DB2 for IBM Lotus Mashups for steps to create the database, the Lotus Mashups resources, and the data source.

To configure DB2 or Informix for MashupHub, see Chapter 6 in the IBM MashupHub User and Administrator Guide, and then do the following steps:

Create a new database, for example MashupDB.

Migrate the existing database instance on the primary node to DB2. The instructions for migrating to another database are listed under the Settings option in MashupHub.

Provide the details about the database and complete the configuration steps.

Locate server.config.ini in the MashupCenter_install_root\Hub\installedApps\Mashup Hub.ear\mashuphub-enterprise.war\META-INF\config directory. Then change the app.server.ssl.port to 443, and the app.server.http.port to 80. Also change the base.url parameter to reflect the main IBM HTTP Server name. You will install IBM HTTP Server in a later step.

Step 2: Preparing the secondary nodes

In this step, you will prepare the first secondary node in the cluster. You can repeat these steps for all other nodes in the cluster. This step includes installing IBM Mashup Center and configuring the database.

Install IBM Mashup Center. For installation instructions, see the IBM Mashup Center Quick Start Guide.

Create a Lotus Mashups data source for DB2. See the third step in either the local or remote sections of Confguring DB2 for IBM Lotus Mashups for details.

Stop the secondary node server.

In the MashupCenter_install_root\Hub\installedApps\Mashup Hub.ear\mashuphub-enterprise.war\META-INF\config directory, delete the server.config.ini and mmms.config.ini files.

Repeat these steps for each secondary node in the cluster.

Step 3: Installing and configuring WAS Network Deployment

In this step, you will install WAS Network Deployment 6.1.0.1 and its associated fixpacks on the Deployment Manager server.

Go to the IBM Passport site and download WAS Network Deployment 6.1.0.1.

During the installation process, do the following steps:

DO NOT install the sample application.

Set an installation location, for example C:\IBM\WebSphere\AppServer.

Select the Deployment Manager as the WAS environment.

When enabling administrative security, set both a user name and password, for example admin/admin.

Go to the IBM Support site and install the WAS Update Installer V6.1.0.13. Be sure to set an installation location, for example C:\IBM\WebSphere\UpdateInstaller.

Install WAS 61013 fixpack (6.1.0-WS-WAS-WinX32-FP0000013.pak) using the Update Installer.

If necessary, back up WAS by copying the AppServer folder to another location.

To configure LDAP on the Deployment Manager machine, see Configuring LDAP for IBM Mashup Center.

Step 4: Installing IBM HTTP Server

In this step, you will install IBM HTTP Server (IHS) Version 6.1 and its associated fixpacks. This enables the Web server that you will add in the next step to work with WAS. For more information about installing IBM HTTP Server, see the Installing IBM HTTP Server topic in the WAS Information Center.

Install IBM HTTP Server 6.1 from the WAS Network Deployment 6.1 download CD.

During the installation process, do the following steps:

Set the installation location, for example C:\IBM\HTTPServer.

Select Run HTTP server as the Windows server and IBM HTTP Administration as the Windows Service. Log on using the specified user account, and type the system administrator's user name and password.

Specify the HTTP adminstrator's user ID and password. Click Next.

Select to install the IHS plug-in for WAS, and specify the Web server definition and the hostname for WAS. Click Next to finish.

Step 5: Federating nodes

In this step, you will federate the nodes in the cluster.

Start and open the WAS Deployment Manager administrative console by running the following command: startManager.bat. Log in using the adminstrator's user ID and password.

To update the Deployment Manager adminstrative console preferences, do the following steps:

Navigate to System administration > Console Preferences, and select Synchronize changes with Nodes.

Modify the maximum heap size by selecting System administrator > Deployment manager > Java and Process Management > Process Definition > Java Virtual Machine.

Enable the WAS Deployment Manager application security.

Click Secure administration, applications, and infrastructure > Web security > General settings, and select Use available authentication data when an unprotected URI is accessed.

Stop and start the WAS Deployment Manager.

To add the Mashup Center servers as managed nodes to the cell, do the following steps:

Start server1 on WAS by running the following command: startServer.bat server1.

Add the first (primary) node by changing to the MashupCenter_install_root > mm_profile > bin directory and running the following command:

run addNode.bat DM_HOST SOAP_PORT -username admin -password admin -includeapps

where the default SOAP_PORT is 8879.

Add the second node by changing to the MashupCenter_install_root > mm_profile > bin directory and running the following command:

run addNode.bat DM_HOST SOAP_PORT -username admin -password admin 

where the default SOAP_PORT is 8879.

Repeat the last step for each additional node in the cluster.

Stop and start the WAS Deployment Manager as well as the nodes using stopNode and startNode. This step is needed only if the Deployment Manager administrative console does not list the node agents under System administration > Node agents.

Step 6: Setting up the cluster

In this step, you will use the WAS Deployment Manager set up the cluster.

Click Servers > Clusters > New. Type the cluster name and click Next.

To create the first cluster member, type the member name, select the primary node, and select Create the member by converting an existing application server. Then click Next.

Type the secondary member name, select the node, add the member, and click Next. Finish the remaining cluster setup.

For each cluster member, open MashupCenter_install_root\mm\eclipse\configuration\config.properties, uncomment the com.ibm.mashups.cluster property, and set it to the cluster name.

To add a new Web server and a new node, do the following steps:

To add an unmanaged node for the Web server, navigate to System administration > Add node.

Select Unmanaged node, and then click Next.

Type the name and host name, and then click OK.

To create a new Web server for the cluster environment, log in to the Deployment Manager administrative console, and navigate to Servers > Web servers.

Select to create a new Web server, select the node, and then type the server name. Click Next and then Next again.

Specify the Web server installation location, plug-in installation location, user name, and password.

Click Next to confirm the new server, and then finish adding the Web server.

Step 7: Configuring two MashupHub servers to point to the same database

In this step, you will copy over the necessary files to ensure that two MashupHub servers in the cluster point to the same database.

Copy server.config.ini and mmms.config.ini from the primary node to the same location on the secondary node. This file is located in the MashupCenter_install_root\Hub\installedApps\Mashup Hub.ear\mashuphub-enterprise.war\META-INF\config directory.

Copy key.jck from the primary node to the secondary node. Be sure to delete the key.jck file from the secondary node first. This file is located in the MashupCenter_install_root\Hub\installedApps\Mashup Hub.ear\mashuphub-enterprise.war\META-INF directory.

Copy the hubsample database from the primary node to the secondary node. This file is located in MashupCenter_install_root\\Hub\installedApps\Mashup Hub.ear\mashuphub-enterprise.war. This enables the sample relational feeds to work, such as Policy Holders and Policy Holders Mashup, to work when the secondary node requests them.

Repeat these steps for additional nodes in the cluster.

Step 8: Enabling SSL on IBM HTTP Server

This steps describes how to locate and edit the configuration files necessary to enable SSL on IHS.

1. Locate kdb used by IHS in the plug-in.xml file, and do the following steps:
   
   
   
   
   1. Open the configuration file HTTPServer_install_root\Plugins\config\webserver1\plugin-cfg.xml.
   
   
   
   2. Find the following section, and take note of where the plugin-key.kdb and plugin-key.sth files are located:
      
      

      <Transport Hostname="MUMIVT1.ibm.com" Port="9080" Protocol="http"/
        
      
      <Transport Hostname="MUMIVT1.ibm.com" Port="9443" Protocol="https"
        
      
      <Property Name="keyring" Value="c:\IBM\HTTPServer\Plugins\config\webserver1\plugin-key.kdb"/
        
      
      <Property Name="stashfile" Value="c:\IBM\HTTPServer\Plugins\config\webserver1\plugin-key.sth"/
        
      
      </Transport
       
      

   
   
   



2. Locate HTTPServer_install_root\conf\httpd.conf, and add the following lines of code:
   
   

    
   
   LoadModule ibm_ssl_module modules/mod_ibm_ssl.so 
   
   <IfModule mod_ibm_ssl.c
     
   
   Listen 0.0.0.0:443 
   
   <VirtualHost *:443
     
   
   ServerName  your_Web_server_IP_address 
   
   SSLEnable 
   
   </VirtualHost
     
   
   </IfModule
     
   
   SSLDisable 
   
   Keyfile "C:\Program Files\IBM\HTTPServer\Plugins\config\webserver1\plugin-key.kdb" 
   
   SSLStashFile "C:\Program Files\IBM\HTTPServer\Plugins\config\webserver1\plugin-key.sth" 

Save httpd.conf and exit.

Restart IHS and confirm that no errors exist.

Step 9: Enable SSL between IHS and WAS servers

In this step, you will enable SSL between the IHS and WAS servers first by extracting the certificates from the Deployment Manager and two node servers and then adding the certificates to the IHS key database.

To extract the certificates, do the following steps:

1. Locate kdb used by IHS in the plug-in.xml file, and do the following steps:
   
   
   
   
   1. Open the configuration file HTTPServer_install_root\Plugins\config\webserver1\plugin-cfg.xml.
   
   
   
   2. Find the following section, and take note of the plugin-key.kdb and plugin-key.sth files:
      

      <Transport Hostname="MUMIVT1.ibm.com" Port="9080" Protocol="http"/
        
      
      <Transport Hostname="MUMIVT1.ibm.com" Port="9443" Protocol="https"
        
      
      <Property Name="keyring" Value="c:\IBM\HTTPServer\Plugins\config\webserver1\plugin-key.kdb"/
        
      
      <Property Name="stashfile" Value="c:\IBM\HTTPServer\Plugins\config\webserver1\plugin-key.sth"/
        
      
      </Transport
       
      
      

   
   
   



2. Locate the plugin-key.kdb that IHS uses as default.



3. Find the kdb used by each server, and then do steps D and E to export the certificates. For each node, the key.p12 file is typically located in C:\Program Files\IBM Mashup Center\mm_profile\config\cells\Cell01\nodes\Node01. For the Deployment Manager server, the file is typically located in C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\Cell01.

Do the following steps to open the WAS ikeyman file to export the certificate:

Run the ikeyman.bat file. For each node, this file is typically located in C:\Program Files\IBM Mashup Center\AppServer\bin\ikeyman.bat. For the Deployment Manager server, this file is typically located in C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\ikeyman.bat .

To open the NodeDefaultKeyStore file, do the following steps:

1. Click Key Database File > Open.



2. In the File Select dialog, select PKCS12 in the Key database type field.



3. Click Browse and open the appropriate file for each of the servers in the cluster. For each node, the appropriate file is MashupCenter_install_root\mm_profile\config\cells\Cell01\nodes\Node01\key.p12. For the Deployment Manager server, the appropriate file is WAS_install_root\AppServer\profiles\Dmgr01\config\cells\Cell01\key.p12.



4. Click OK.



5. When prompted for the password, type WebAS.

Select the default certificate under Personal Certificates.

Click Extract Certificate.

Type the name of the certificate file WASKeyP12cert.arm and specify the location for each of the servers in the cluster. The location for the primary node is C:\prim\. The location for all other nodes is C:\sec\. The location for the Deployment Manager server is C:\dm\ .

Copy the WASKeyP12cert.arm files from C:\prim\ and C:\sec\ from the primary and secondary nodes so that they are available for configuring the IHS in the WAS Deployment Manager server.

To add the certificates to the IHS key database, do the following steps:

1. Select Start->All Programs > IBM HTTP Server V6.1 > Start Key Managerment Utility to open Ikeyman.



2. Open the file, select CMS in the Key database type field, and locate plugin-key.kdb under HTTPServer_install_root\Plugins\config\webserver1\, When prompted, type WebAS as the password.



3. Under Key database content, Select Signer Certificates and click Add. Then click Browse to open the location for the WASKeyP12cert.arm file from the primary node. When prompted to specify a label, type WASKeyP12_prim Cert.



4. Click OK.



5. Close Ikeyman.



6. Repeat the steps above for WASKeyP12cert.arm files from the non-primary and Deployment Manager servers.

Restart IBM HTTP Server to make the changes effective.

Step 10: Install the fixpack (if necessary)

To install the fixpack, go to this wiki article. It provides the readme as well as a link to the FixCentral site where you can download the fixpack.

Step 11: Set the cluster name

In this step, you will set the cluster name in in the PROPERTIES file.

1. On each node, open MashupCenter_install_root\mm\eclipse\configuration\config.properties.



2. Add the following line:

com.ibm.mashups.cluster=cluster_name

where cluster_name is the name of the cluster that you specified in Step 6 above..

Restart the cluster environment.

Step 12: Verifying the cluster

Now that the cluster is set up, confirm that it is working properly by logging in to the Deployment Manager admininstrative console and starting the cluster. Now users should be able to access the Mashup Center server by clicking http://WEBserver.domain/mum/enabler.

Note: After configuring a MashupHub cluster, if you make additional configuration changes, you must manually copy the server.config,ini file from the primary node to each secondary node in the cluster. This is because each node in the cluster has its own copy of the file, and any changes you make in the primary node need to be carried over to the other nodes. You should perform this step any time you change the value of the deployIWidgetPackagesettings setting.