MDM WebSphere Cluster Install Guide TN · Note: The cluster creation steps are out of this document scope. 1.1 Check that the cluster is up and running In the left pane of the WebSphere

MDM Multidomain Edition for DB2 (Version 9.0.1)

MDM WebSphere Cluster Install Guide

Technical Note

Informatica MDM WAS Cluster Install Guide for DB2 – Technical Note

Page ii

Informatica MDM Multidomain Hub - Version 9.0.1 - March 2011 Copyright (c) 2011 Informatica. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement

containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited.

No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise)

without prior consent of Informatica Corporation. This Software is be protected by U.S. and/or international Patents and other Patents

Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software

license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR

12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or

documentation, please report them to us in writing.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data

Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data

Transformation, Informatica B2B Data Exchange, Informatica On Demand and Siperian are trademarks or registered trademarks of Informatica

Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or

trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright

DataDirect Technologies. All rights reserved. Copyright © Sun Microsystems. All rights reserved.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is

licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/

LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS

IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific

language governing permissions and limitations under the License.

This product includes software which is licensed under the GNU Lesser General Public License Agreement, which may be found at

http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied,

including but not limited to the implied warranties of merchantability and fitness for a particular purpose.

This product includes software which is licensed under the CDDL (the "License"). You may obtain a copy of the License at http://www.sun.com/cddl/cddl.html. The

materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties

of merchantability and fitness for a particular purpose. See the License for the specific language governing permissions and limitations under the License.

This product includes software which is licensed under the BSD License (the "License"). You may obtain a copy of the License at

http://www.opensource.org/licenses/bsd-license.php. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or

implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific language governing

permissions and limitations under the License. This product includes software Copyright (c) 2003-2008, Terence Parr, all rights reserved which is licensed under the BSD License (the "License"). You may obtain a

copy of the License at http://www.antlr.org/license.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express

or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific language governing

permissions and limitations under the License.

This product includes software Copyright (c) 2000 - 2009 The Legion Of The Bouncy Castle (http://www.bouncycastle.org) which is licensed under a form of the MIT

License (the "License"). You may obtain a copy of the License at http://www.bouncycastle.org/licence.html. The materials are provided free of charge by Informatica,

"as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular

purpose. See the License for the specific language governing permissions and limitations under the License.

DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied,

including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica

Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation

may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at

any time without notice.

NOTICES

This Informatica product (the “Software”) may include certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software

Corporation (“DataDirect”) which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOTLIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN

ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE,

STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

http://www.antlr.org/license.html/


Page iii

Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product

information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the

Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Documentation

Center, and access to the Informatica user community.

Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or

ideas about this documentation, contact the Informatica Documentation team through email at [email protected]. We

will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments.

The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to the Informatica

Documentation Center from http://my.informatica.com.

Informatica Web Site You can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its

background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes

important information about technical support, training and education, and implementation services.

Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at http://my.informatica.com. The How-To Library is a

collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations

that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to

search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked

questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the

Informatica Knowledge Base team through email at [email protected].

Informatica Multimedia Knowledge Base As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at

http://my.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about

common concepts and guide you through performing specific tasks. If you have questions, comments, or ideas about the Multimedia

Knowledge Base, contact the Informatica Knowledge Base team through email at [email protected].

http://my.informatica.com/


http://www.informatica.com/





Page iv

Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the WebSupport Service. WebSupport requires a user name and

password. You can request a user name and password at http://my.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America/South America Europe/Middle East/Africa Asia/Australia

Toll Free

North America +1 877 463 2435

Brazil 0800 891 0202

Mexico 001 888 209 8853

Standard Rate

North America +1 650 653 6332

Toll Free

United Kingdom 00800 4632 4357 or

0800 023 4632

France 00800 4632 4357

Netherlands 00800 4632 4357

Germany 00800 4632 4357

Switzerland 00800 4632 4357 or 0800

463 200

Israel 00800 4632 4357

Spain 900 813 166

Portugal 800 208 360

Italy 800 915 985

Standard Rate

France 0805 804632

Germany 01805 702702

Netherlands 030 6022 797

Toll Free

Australia 1 800 151 830

New Zealand 1 800 151 830

Singapore 001 800 4632 4357

Standard Rate

India +91 80 4112 5738


Informatica MDM WebSphere Cluster Install Guide for DB2

Technical Note

Table of Contents 1 Create cluster and check cluster configuration .................................................................................... 6

1.1 Check that the cluster is up and running ...................................................................................... 6

1.2 Check that the cluster members are synchronized ...................................................................... 6

2 Prepare message queues ...................................................................................................................... 7

2.1 Configure the Service Integration Bus .......................................................................................... 7

2.2 Configure the Connection Factory ................................................................................................ 8

2.3 Configure the JMS Queue ............................................................................................................. 9

2.4 Activate the JMS Specification .................................................................................................... 10

3 Create the JDBC provider .................................................................................................................... 11

4 Create Data Sources ............................................................................................................................ 13

4.1 Create a System Data Source ...................................................................................................... 13

4.2 Create the ORS Data Source ....................................................................................................... 17

5 Install the MDM Hub Server ............................................................................................................... 19

5.1 Determine the RMI and SOAP port numbers.............................................................................. 19

5.2 Install the MDM Hub Server ....................................................................................................... 20

Installation steps per physical machine ................................................................................................... 20

5.3 Prepare the Hub Server............................................................................................................... 20

5.4 Deploy the Hub ........................................................................................................................... 21

5.5 Set class loading options ............................................................................................................. 23

5.6 Start the Application ................................................................................................................... 24

5.7 Register the ORS ......................................................................................................................... 24

6 Install the Cleanse Hub Server ............................................................................................................ 24

6.1 Prepare the Cleanse Server ......................................................................................................... 25

6.2 Deploy the Cleanse Server .......................................................................................................... 25


Page 6

1 Create cluster and check cluster configuration Create cluster with a minimum of one node, start and synchronize it before proceeding to the Hub

installation.

Note: The cluster creation steps are out of this document scope.

1.1 Check that the cluster is up and running In the left pane of the WebSphere Solutions console, click Servers > Clusters. Make sure that the

required cluster exists and its status is „Started‟.

1.2 Check that the cluster members are synchronized In the left pane, click System administration > Nodes. Make sure all cluster nodes have a status

of„Synchronized‟.


Page 7

2 Prepare message queues Here is a summary of the steps involved in preparing the message queues:

Create and configure a new bus with the name “SiperianBus” and queue named

“SiperianQueue”

Create a new connection factory named “siperian.mrm.jms.xaconnectionfactory”

Configure a new JMS queue named “siperian.sif.jms.queue

2.1 Configure the Service Integration Bus 1. In the left pane click Service Integration > Buses.

In the right pane, click New.

2. Enter „SiperianBus‟ as the name.

Click Next and then Finish.

3. Save the changes

4. In the right pane, under the Topology menu, select Bus Members.

5. Click Add and select the appropriate cluster from the Cluster drop-down menu.

Click Next.


Page 8

6. Select the proper type of message store and click Next.

7. Provide the store properties, such as JNDI name of the data source, schema name, and

authentication alias (create if needed for user file storage).

Click Next then Finish.

8. Find the bus you just created and click on Destinations under the Destination Resources

menu on the right.

9. Click New > Queue > Next.

Use the name “SiperianQueue” as the identifier.

10. Click Next > Finish > Save.

2.2 Configure the Connection Factory

1. On the left pane, click Resources > JMS > JMS Providers.

Select the appropriate cluster and choose Default Messaging Provider.


Page 9

2. Under Additional Properties, select Queue Connection Factories.

Click New.

3. Enter „siperian.mrm.jms.xaconnectionfactory‟ for both the Name and JNDI Name.

4. Choose SiperianBus as the Bus Name for the connection.

5. Click Next > Save to save the changes.

2.3 Configure the JMS Queue 1. On the left pane, click Resources > JMS > Queues.

Select the appropriate cluster scope.

2. Click New.

3. Select the Default Messaging Provider and click OK.

Use “siperian.sif.jms.queue” for both the name and JNDI name.

Choose “SiperianBus” for the Bus Name and “SiperianQueue” for the queue name.


Page 10

2.4 Activate the JMS Specification

1. On the left pane, click Resources > JMS > Activation Specification.

Select the appropriate cluster and click New.

2. Select the Default Messaging Provider.

3. Under the Administration section, use “SiperianActivation” for both the name and the JNDI

name.

4. Under the Destination section, the Destination Type should be queue.

Use “siperian.sif.jms.queue” as the destination JNDI name.

The bus name should be “SiperianBus”.

5. Save all changes.


Page 11

3 Create the JDBC provider 1. Go to Resources > JDBC > JDBC providers.


2. Click New.

Select the appropriate options.

3. Click Next and set the first path to ${WAS_LIBS_DIR}. Leave the second path empty.


Page 12


Page 13

4 Create Data Sources

4.1 Create a System Data Source 1. Go to JDBC > Data Sources.


2. Click New

Name: siperian-cmx_system-ds

JNDI name: jdbc/siperian-cmx_system-ds

Leave the drop-down list empty for now.


Page 14

3. Click Next and select the JDBC provider created in the previous steps.

4. Click Next and provide the connection details.

5. Click Next > Finish.

Save the configuration.


Page 15

6. Open the created data source.

Open the JAAS – J2C authentication data.

7. Click New.

Use the following information for the authentication data.

Name: siperian-cmx_system

Provide the login and password of the user that created the CMX_SYSTEM schema.


Page 16

8. Click OK and Save the configuration.

9. Open the data source and set the “Component-management authentication alias”.

Also set the “Use component-management authentication alias” option for XA recovery.

10. Open the data source. Navigate to “Custom properties”.


Page 17

Set the custom properties with the appropriate types. Make sure not to create any duplicates

(some of parameters are already set to their defaults).

fullyMaterializeLobData=true(java.lang.Boolean)

fullyMaterializeInputStreams=true(java.lang.Boolean)

progressiveStreaming=2 (java.lang.Integer)

deferPrepares=false (java.lang.Boolean)

currentSchema=cmx_system (java.lang.String)

defaultIsolationLevel=2 (java.lang.Integer)

webSphereDefaultIsolationLevel=2 (java.lang.Integer)

11. Save the the configuration.

Click OK and Save the configuration.

You may need to resynchronize nodes. (System administration > Nodes > Synchronize)

12. Open Resources > JDBC > Data sources.

Choose the data source and click Test connection. Each cluster node must report a

successful testing result. If “Test connection” fails, restart all cluster nodes

Note: Restarting the cluster servers may not help.

4.2 Create the ORS Data Source Use the same steps as for creating the cmx_system data source, with these differences.

The JNDI notation for the JDBC data source : jdbc/siperian-<host_name>-<database_name>-<ors_name>-ds

Note: The JNDI name in the JDBC data source setup WebSphere uses the '-' character in its notation.

If the physical server used in the connection also contains the '-' character, the '~' character must

prefix the “-” in the server name.

For example:

Name: siperian-my~-host-sip901-cmx_ors-ds


Page 18

JNDI name: jdbc/siperian-my~-host-sip901-cmx_ors-ds

Create your own J2C authentication alias, if needed. Make sure the schema is used by the user that

created the ORS schema.

Set the custom properties: deferPrepares=false (java.lang.Boolean)

currentSchema=cmx_ors (java.lang.String) - Put the actual schema name here

defaultIsolationLevel=2 (java.lang.Integer)

webSphereDefaultIsolationLevel=2 (java.lang.Integer)


Page 19

5 Install the MDM Hub Server

5.1 Determine the RMI and SOAP port numbers

1. Go to Servers >Application servers and click on any server that belongs to the cluster.

2. On the right side of the screen, expand Communications > Ports.

3. Use General Properties > Member Name as the server name, Bootstrap_address as the

RMI port, and SOAP_CONNECTOR_ADDRESS as the SOAP port during Hub

installation.


Page 20

5.2 Install the MDM Hub Server The MDM Hub Server should be installed on each physical machine in the cluster. In the case of

vertical clustering (having several nodes on a same physical machine), it is sufficient to have a single

installation of the Hub Server on that particular machine.

Installation steps per physical machine

1. Run the MDM Hub Server installer in console mode, by passing validation with following

option.

./hub_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

Do not execute the postInstallSetup scripts at the end of the install process.

2. Use the server name and ports from section 5.1 during the installation process (any server

from this particular physical machine and the particular cluster may be used).

Server Name (DEFAULT: server1): node2

RMI Port (DEFAULT: 2809): 2812

SOAP Port (DEFAULT: 8880): 8883

Repeat the Hub installation using the same path on each physical machine in the cluster

You may want to use the silent install mode for these additional installations. A sample configuration

file can be found in the distribution:

/silent_install/mrmserver/silentInstallServer_sample.properties

The command line for silent installer is:

./hub_install.bin -f <location_of_silent_properties_file_for_hub_server>

5.3 Prepare the Hub Server

Perform the following changes on each physical machine in the cluster.

1. Grant permissions for shell scripts:

chmod a+x $HUB_SERVER_FOLDER/*.sh

chmod a+x $HUB_SERVER_FOLDER/bin/*.sh

2. Configure the Hub server properties by navigating to:

<$HUB_SERVER_FOLDER>/hub/server/resources/cmxserver.properties.

3. Remove the comment markers (#) for the following items in the properties file.

Add all cluster node host names to cmx.appserver.hostname =

For example: cmx.appserver.hostname=dazarov,dazarov,pbsdevdb2

Add all cluster node RMI port numbers to cmx.appserver.rmi.port =


Page 21

Example: cmx.appserver.rmi.port=2812,2815,2814

Make sure number of host names and ports is exactly the same and their order in the list

corresponds.

4. Change the setting for the drop-down limit from the default of 100 in sip.lookup.dropdown.limit=5000

5. Configure the siperian-console.jnlp file.

Follow these steps:

a. Open the EAR file with WinZip.

b. Drag the siperian_console.war file out of the EAR file.

c. Drag the siperian_console.jnlp file out the WAR file.

d. Modify the servername, port, etc. in the siperian_console.jnlp as follows:

<property name="cmxServerProtocol" value="iiop"/>

<property name="cmxServerName" value="khowks02"/>

<property name="cmxServerPort" value="2813"/>

<property name="cmxServerType" value="websphere"/>

<property name="cmxWebServerPort" value="9083"/>

Save the file.

6. Put the siperian-console.jnlp file back into the WAR file with the correct path (\WEB-

INF\classes\resources).

7. Put the WAR file back into EAR file.

5.4 Deploy the Hub 1. Navigate to the Hub installation folder and execute:

$HUB_SERVER_FOLDER/bin/sip_ant.sh repackage

2. Go to the WebSphere Admin Console.

Navigate to Applications > Install new application.

Choose the siperian-mrm.ear from you Hub installation folder.

3. Click Next, and then Next again

Select the scope (cluster) and all modules. Click Apply.


Page 22

4. Click Next. You may need to fill in the empty JNDI names.

cmx.server.MasterEjb

cmx.server.RequestEjb

5. Click Next.

Set NONE for “authentication methods”.

Provide pickup queue connection provider with lookup page, then select “module”.


Page 23

6. Click Next and then Finish.

Save configuration.

5.5 Set class loading options 1. Navigate to Applications > Enterprise Applications > siperian-mrm.ear and click “Class

loading and update detection” under Detail Properties.

Set the “Class loaded with application class loader first” option for the Class loader order.

2. Click OK and Save.


Page 24

5.6 Start the Application Confirm that all nodes synchronize after a few minutes. If not, you will need to manually

synchronize them.

Start the application. Verify that the application status is „Started‟.

5.7 Register the ORS Start the Hub console and register the ORS (see the Informatica MDM Installation Guide for details).

Configure the ORS so that it will not create a datasource after registration.

6 Install the Cleanse Hub Server It is possible to install Cleanse Hub Server into a cluster, however it only provides the benefit of

having a unified EAR deployment procedure using WebSphere Deployment Manager.

The Hub Server provides its own logical “clustering” of Cleanse Servers out-of-the-box, using a

standard round-robin algorithm.

For a non-cluster installation use the regular installation described in the Informatica MDM

Installation Guide.

The following instructions should be applied to each physical machine in the cluster.

Install the Cleanse Server on each cluster node using exactly the same path, using the same server

name, and SOAP port as you did in the Hub Server installation. Do not execute the postInstallSetup

scripts during installation

It is possible to use the silent install mode for these installations. A sample configuration file for the

silent install can be found in the distribution:

/silent_install/mrmcleanse/silentInstallCleanse_sample.properties

The command to do this is:


Page 25

./hub_cleanse_install.bin -f

<location_of_silent_properties_file_for_cleanse_server>

6.1 Prepare the Cleanse Server Grant these permissions to shell scripts

chmod a+x $HUB_CLEANSE_SERVER_FOLDER/*.sh

chmod a+x $HUB_CLEANSE_SERVER_FOLDER/bin/*.sh

6.2 Deploy the Cleanse Server 1. From any cluster node, navigate to the cleanse installation folder and execute the command:

$<HUB_CLEANSE_SERVER_FOLDER>/bin/sip_ant.bat repackage

2. Select Applications > Install New application.

Choose the EAR file from the cleanse installation directory.

3. Click Next and then Next again.

Choose the scope (cluster) and select the module. Click Apply.

4. Click Next.

Choose “virtual host” (configure this if needed) and “module”.

5. Click Next and Finish.

Save the master configuration.


Page 26

Confirm that all nodes synchronize after a few minutes. If they do not synchronize, you may need to

manually synchronize them.

6. Start the cleanse application from Applications > Enterprise applications. Confirm that the

application status is „Started‟.

7. Go to Servers > Application servers and find the HTTP port for each cluster node.

8. Register all the cleanse servers in the cluster nodes in the ORS schema using Hub console. Use

the node host names and the HTTP ports you found.

9. Set the appropriate Thread Count option for servers (see the Informatica MDM Administrator

Guide for details).

10. Test the connection for each cleanse server using the Hub console.


Page 27

11. Confirm that the WebSphere host has a DB2 client installed.

Verify that the WebSphere user has sufficient privileges.

Information Applicable to all Cluster Nodes

The user that runs the application server should have rights to execute DB2 commands (like:

db2 connect to). Add these lines to the user‟s shell properties file:

if [ -f <db2_instance_owner_home>/db2/sqllib/db2profile ]; then

<db2_instance_owner_home>/db2/sqllib/db2profile fi

The user that runs the Cleanse Match server process should have execute permissions on the

Cleanse Server temporary folders and all sub-folders, and read permissions on the files

contained in that folder: <cleanse_server_home>/tmp

The DB2 database should be a registered node. Launch this command and check the output:

db2 list database directory

Check the following library and environment variable settings (see the Informatica MDM

Installation Guide section„MATCH Process Error: VerifyNeedToStrip‟) for more details.

The library path environment variable should contain the following path for the

Informatica profile:

<infamdm_install_directory>/lib

The library path environment variable depends on the platform:

• AIX: LIBPATH

• HP-UX: SHLIB_PATH

• Solaris, Suse, or RedHat: LD_LIBRARY_PATH

For example HP-UX would be: SHLIB_PATH=/u1/infamdm/hub/cleanse/lib

The SSAPR environment variable should include the following path for all users

(such as the Informatica user):

<infamdm_install_directory>/resources


Page 28

For example:

SSAPR=/u1/infamdm/hub/cleanse/resources

Restart the Deployment manager and node processes, if needed, in order to read these

environment variables.

© copyright 2011 Informatica, Corp.

Documents

MDM WebSphere Cluster Install Guide TN · Note: The cluster creation steps are out of this document scope. 1.1 Check that the cluster is up and running In the left pane of the WebSphere