High availability deployment scenario for WebSphere Information Integrator Content Edition

Transcription

1 High availability deployment scenario for WebSphere Information Integrator Content Edition This article explains how to install and configure an IBM WebSphere Information Integrator Content Edition in a horizontal cluster. Introduction: WebSphere Information Integrator Content Edition (IICE or content integration server) provides the capability for enterprise content integration. Global organizations use the content integration server to enable portals, collaborative applications, customer relationship management, and other key applications to work with distributed content and work processes throughout the extended enterprise. WebSphere Information Integrator Content Edition is based on Java technology and designed to run in a J2EE environment, such as IBM WebSphere Application Server. Businesses today are faced with the critical need to ensure the availability and continuous operation of their business systems in spite of potential failures ranging from disk crashes, CPU or network failures, or planned downtime for upgrades and maintenance. The ability to provide a service that has little downtime is high availability. This does not mean that a service is guaranteed to be available. The goal of high availability is to continue to provide a user with a working system as seamlessly as possible in the event of a component failure. If a system component fails for any reason, the high availability solution ensures that another component takes over for the failed component, minimizing the disruption to the user. Typically, high availability is achieved by leveraging server clusters. Server clusters come in three varieties: vertical, horizontal and vertical combined with horizontal. Vertical clustering refers to the practice of defining multiple clones of an application server on the same physical machine. Vertical clustering is mostly used to fully utilize the CPU power of a large machine by creating multiple JVM processes and also to provide process level failover. Horizontal clustering refers to the more traditional practice of defining clones of an application server on multiple physical machines, thereby allowing a single WebSphere application to span several machines while presenting a single system image. Horizontal clustering can provide both increased throughput and hardware failover. Horizontal and vertical clustering configurations can be combined to provide a high availability environment. This article provides detailed instructions on the steps involved to design and deploy IICE on a horizontal cluster with WebSphere Application Server. For additional details on clustering with WebSphere Application Server, consult the WebSphere Application Server documentation.

2 WebSphere Application Server horizontal cluster with IICE deployed: Install a deployment manager in the application server node and a Web server on one machine, and one managed application server node on a second machine. This scenario could be easily extended to have multiple managed application server nodes on additional machines, and also have Application server on a separate machine. Figure 1 depicts the environment that you configure by walking through the sample below. The managed nodes in this scenario communicate with the same Web server. However, the preferred strategy is to have a dedicated Web server for each managed node. IMPORTANT: node1.svl.ibm.com and node2.svl.ibm.com are not real addresses. They are examples only. You must change this address according to your configuration. Client Machine Machine A (hr-node1.svl.ibm.com) Client Application ConfigServer:rmi://hr-node1.svl.ibm.com:1250/ConfigurationServer rmi://hr-node2.svl.ibm.com:1250/configurationserver SessionPool: rmi://hr-node1.svl.ibm.com:1250/sessionpool rmi://hr-node2.svl.ibm.com:1250/sessionpool SSO: rmi://hr-node1.svl.ibm.com:1250/ssoserver rmi://hr-node2.svl.ibm.com:1250/ssoserver Dmgr (deployment mgr) Node agent iiceserver (managed node) VeniceBridge.ear WebServer Plugin Config.xml IICE datastore synced Machine B (hr-node2.svl.ibm.com) Node agent iiceserver2 (managed node) VeniceBridge.ear Config.xml IICE datastore Figure 1: IICE deployed on horizontal cluster Steps for installation, deployment and configuration: 1. Install WebSphere Application Server Network Deployment on Machine A. 2. Create a deployment manager profile using the Profile creation wizard on Machine A. 3. Start the deployment manager using the WebSphere Application Server First Steps Console or the startmanager command on Machine A. 4. Create the first Application Server profile using the Profile creation wizard on Machine A. 5. Create a new Application Server iiceserver for the newly created application server profile on Machine A. 6. Install WebSphere Application Server Network Deployment on Machine B. 7. Create the second application server profile using the Profile creation wizard on Machine B.

3 8. Create a new application server iiceserver2 for the newly created application server profile on Machine B. 9. Add both application server nodes to the cell using the administrative console of the WebSphere Application Server Deployment Manager on Machine A. Click System Administration > Nodes to add the nodes. 10. Install IICE on Machine A and Machine B. 11. Create a new cluster iicecluster using the administrative console of the WebSphere Application Server Deployment Manager on Machine A. Click Servers > Clusters to create a new cluster. 12. Deploy the VeniceBridge.ear file to the newly created iicecluster cluster using the administrative console of the WebSphere Application Server Deployment Manager on Machine A. Click Applications > Install New Application to install the VeniceBridge.ear file to the cluster. The VeniceBridge.ear file is located in IICE home install directory. 13. Create a new shared library for content integration server dependencies in WebSphere Application Server Administrative Console: a. Go to Environment > Shared Libraries. b. Ensure that the scope is set to Node. If it is not, select the Node radio button and click Apply. c. Click New. d. Name the new shared library: iicedependencies e. Set the class path to include IICE_HOME/datastore/datastore.jar. f. Set the Native Library Path to include IICE_HOME/datastore. g. Click OK. h. Click Save at the top of the page to save the changes. 14. Create a new class loader: a. Select Servers > Application Servers > iiceserver > Server Infrastructure > Java and Process Management > Class loader. b. Click New. c. Select Parent First for the Class loader mode. d. Click OK. e. Click the Additional Properties > Libraries link. f. Click Add. g. Choose the iicedependencies library you created in the previous step and click OK. h. Select iicedependencies for the Library name. i. Click Save at the top of the page to save the changes. 15. Repeat Step 14 for the iiceserver2 application server to define a new class loader. 16. Add the home directory for the content integration server and the headless option to the property set of the application server Java Virtual Machine: a. Select Servers > Application Servers > iiceserver > Server Infrastructure > Java and Process Management > Process Definition > Additional Properties > Java Virtual Machine > Additional Properties > Custom Properties. b. Click New. c. Enter the following properties: d. Click OK. e. Click New. Name: vbr.home Value: IICE_HOME Description: content integration server installation root directory.

4 f. Enter the following properties: Name: java.awt.headless Value: true g. Click OK. h. Click Save at the top of the page to save the changes. 17. Repeat Step 16 for the iiceserver2 application server to add the home directory for the content integration server. 18. Restart the iicecluster cluster. This restarts iiceserver and iiceserver2 application servers. 19. Change the content integration server configuration for the JNDI property. a. Open the content integration server administration console and connect to: rmi://hr-node1.svl.ibm.com:1250/configurationserver IMPORTANT: node1.svl.ibm.com is not a real address. It is an example only. You must change this address according to your configuration. b. From the menu, go to Edit > Options. Select WebSphere from the drop-down list and click on Properties. c. Update the value of property the java.naming.provider.url field to: corbaloc:hr-node1.svl.ibm.com:9811 IMPORTANT: node1.svl.ibm.com is not a real address. It is an example only. You must change this address according to your configuration. d. Click OK. e. Save the configuration. 20. Test the connection to validate the setup: a. Open the content integration server Administration Tool. b. Right-click on Access Services. c. Click test connection to test the connection to Access Services in the content integration server. d. The connection should succeed. 21. Create a new File System connector. Right-click Connectors and select New Sample File System Connector. Test connection with empty credentials. This connector is used during the verification steps. 22. Save the configuration and close the Administration Tool. 23. Stop the iicecluster cluster. This stops iiceserver and iiceserver2 application servers. 24. On Windows : Open the config.bat file from IICE_HOME\bin directory. On UNIX systems: Open the config.sh file from IICE_HOME/bin directory. Update the JNDI property to:

5 set JNDI_CLIENT_PROVIDER=corbaloc::hr-node1.svl.ibm.com:9811 IMPORTANT: node1.svl.ibm.com is not a real address. It is only an example. You must change this address according to your configuration. 25. Copy the IICE_HOME\config.xml file from Machine A to Machine B to sync the content integration server configuration information. 26. Copy the IICE_HOME\datastore\relate_store directory from Machine A to Machine B to sync the content integration server datastore. 27. UNIX systems only: Run the IICE_HOME/bin/config.sh file to set the content integration server environment variables. 28. UNIX systems only: Using a command line, start each node instance that belongs to the iicecluster. 29. Windows only: Restart the iicecluster cluster. This restarts the iiceserver and iiceserver2 application servers. Verification Step: 1. Modify the IICE_HOME\run_sample.bat file to make it work for Direct mode. The instructions to make the batch file work in Direct mode are in batch file itself. 2. Update the vbr.as.direct.rmi.urls property to create a comma separated list of configuration server RMI URLs. These URLs map to the two content integration servers created for the iicecluster cluster: -Dvbr.as.direct.rmi.urls=rmi://hrnode2.svl.ibm.com:1250/ConfigurationServer,rmi://hrnode1.svl.ibm.com:1250/ConfigurationServer ^ IMPORTANT: node1.svl.ibm.com and node2.svl.ibm.com are not real addresses. They are examples only. You must change this address according to your configuration. 3. Execute RepoTest sample. Run the run_sample.bat file from a command line: run_sample commandline.repotest FileSystemConnector xxx xxx 4. Stop the iiceserver application server using the administrative console of the WebSphere Application Server Deployment Manager on Machine A. Click Servers > Application Servers, check the box for iiceserver and click Stop. 5. Repeat step 3 to execute the RepoTest sample. WebLogic Application Server 9.2 (Platform Edition) horizontal cluster with IICE deployed:

6 Refer to the WebLogic Application Server (Platform Edition) product documentation for details on the cluster install and setup. If you want IICE to be in a high availability environment, then the WebLogic plug-in or a WebLogic supported external load balancer is required. 1. Create two nodes on the WebLogic 9.2 cluster (Node 1 and Node 2). 2. Create a cluster for IICE called iicecluster. 3. Create managed servers on Node 1 and Node 2 and assign them to cluster. 4. Start the managed servers on both the nodes. 5. Install IICE on both nodes. Refer to the installation section of the IICE Information Center. 6. Deploy the VeniceBridge.ear file to the new iicecluster using the administrative console of the WebLogic Application Server. The VeniceBridge.ear file is located in the IICE home installation directory. See IICE documentation on deploying on WebLogic. a. Select the iicecluster as the available target when you deploy the VeniceBridge application. 7. Modify the config.sh file located in the IICE_HOME/bin directory, where IICE_HOME is the root directory of the IICE installation. a. Change the JNDI_CLIENT_FACTORY and JNDI_CLIENT_PROVIDER parameters values to: JNDI_CLIENT_FACTORY=weblogic.jndi.T3InitialContextFactory JNDI_CLIENT_PROVIDER=t3://localhost:7001 b. Add the WebLogic 9.2 client JAR file and the weblogic.jar file in the WL_HOME/weblogic92/server/lib directory to the environment variable: EJB_CLIENT_CLASSPATH. 8. Repeat step 7 on the second IICE node in the cluster. 9. Start the IICE Administration Tool and try test connection for AccessServices. 10. Configure IICE with connectors, data maps and session pools as needed. a. If modifying the FileNet P8 Content Manager connector to work with a Content Engine in a cluster, modify the following settings: i. Remote Server URL: cemp:t3://hr-node1.svl.ibm.com: <Port>, hrnode2.svl.ibm.com: <Port>/FileNet/Engine ii. Remote Server Upload URL: cemp:t3://hr-node1.svl.ibm.com: <Port>, hr-node2.svl.ibm.com: <Port>/ FileNet/Engine iii. Remote Server Download URL: cemp:t3://hrnode1.svl.ibm.com:<port>, hr-node2.svl.ibm.com: <Port>/ FileNet/Engine Note: Port refers to the bootstrap port defined when creating the managed servers in step 3. The above machine address examples (hr-node1.svl.ibm.com) should be modified to your machine or IP address 11. After configuring the IICE connectors, data maps, and session pools on node 1, copy the IICE_HOME\config.xml file from node 1 to node 2 to sync the IICE configuration. 12. Optional: If you want IICE to be in a high availability scenario and you are running an RMIBridge, set the RMIBridge port to be the same port number on both cluster nodes. 13. Optional: If using HTTPAccess, configure HTTP access based on the instructions in the IICE information center. 14. Synchronize the data store database: a. Stop the data store service (FastObjects Server) on both nodes. b. Copy the IICE_HOME\datastore\relate_store directory on Node2 to a backup location. c. Copy the entire IICE_HOME\datastore\relate_store directory from Node1 to Node2. d. Restart the Data Store Service on both nodes. 15. Restart the iicecluster.

7 Note: these instructions are not tested with IICE Subscription Event Services.