Scenario 1: Connecting the MashupHub server on the secondary node to a database: imc3Added by IBM on November 23, 2010 | Version 1 (Original)
|In this step, you will connect MashupHub on the secondary node to the database that you created earlier for the MashupHub server on the primary node. After completing this step, both servers will connect to a common database.
In this step, you will connect MashupHub on the secondary node to the database that you created earlier for the MashupHub server on the primary node. After completing this step, both servers will connect to a common database.
Before you begin
If the configuration database is Oracle or Microsoft SQL Server, copy the respective JDBC driver JAR file to the .../Hub/installedApps/Mashup Hub.ear/mashuphub-enterprise.war/WEB-INF/lib
directory of each node before completing the following steps.
- On the primary node, modify the following properties in the server.config.ini file:
On the secondary node, locate the .../Hub/installedApps/Mashup Hub.ear/mashuphub-enterprise.war/META-INF/config directory, and delete the following two files:
- Change app.server.ssl.port to 443.
- Change app.server.http.port to 80.
- Set base.url to the main IBM® HTTP Server name, for example https://webserver.cn.ibm.com/mashuphub/client.
- Set the MashupBuilderURL property with IBM HTTP Server host name and port number.
Copy the server.config.ini and mmms.config.ini files from the primary node to the secondary node.
Locate key.jck in the \\Hub\\installedApps\\Mashup Hub.ear\\mashuphub-enterprise.war\\META-INF directory on the secondary node, and delete it. Locate the same file on the primary node and copy it over to the secondary node.
Locate the hubsample database in the MashupCenter_install_root\\Hub\\installedApps\\Mashup Hub.ear\\mashuphub-enterprise.war directory and copy it from the primary node to the secondary node. This step is required so that the sample relational feeds work properly.
Now that both servers are pointing to the same database, start both servers on the primary and secondary nodes.
Parent topic: Scenario 1: Configuring a clustered environment in which Lotus Mashups and MashupHub are installed on the same servers: imc3
Previous topic: Scenario 1: Setting up the cluster: imc3
Next topic: Scenario 1: Enabling SSL on IBM HTTP Server: imc3