Setting up WebSphere Process Server 6.

1 Cluster using Deployment Environment feature and Oracle10g database-Lab Exercise

Shahfazal Mohammed, Kiran Kumar Munnanoor Part 1 of 3 Contents

ABOUT THIS DOCUMENT ......................................................................................................................2 CONFIGURING ORACLE JVM ................................................................................................................2 CONFIGURING XA FOR ORACLE ..........................................................................................................2 DATABASE USERS/PRIVILEGES CONSIDERATIONS ..........................................................................3 Common database User (WPSDB).................................................................................................. 3 Business Process Container User (BPCDB) .................................................................................... 3 Business Process Container Observer User (BPCOBS)................................................................... 4 Common Event Infrastructure User.................................................................................................. 4 ESB Message Logger User (ESBLOG)............................................................................................ 4 Messaging engines datastores ........................................................................................................ 4 INSTALLING WEBSPHERE PROCESS SERVER 6.1 .............................................................................5 UPDATING YOUR WPS 6.1.0.0 INSTALLATION TO WPS 6.1.0.1 ........................................................14

About this Document

This document can be used to set up WebSphere Process Server 6.1.0.1 Clustered environment using the Deployment Environment feature of the WebSphere Process Server Deployment Manager Administrative Console. The database used for this exercise is Oracle 10g. The objective of this document is to separate the WebSphere Process Server installation and configuration part from the database interaction part (where scripts are run to create the required tables and table spaces). This will allow the WebSphere Process Server install user to finish Installation and Configuration and hand off the scripts to the DBA who will set up the database tables for the WebSphere Process Server installation. Also note that this document does not discuss Administrative and Application Security, nor does it discuss Database or Performance tuning. The main objective of this document is to be a lab exercise in setting up a Clustered topology using the WebSphere Process Server administrative console. Refer to the WebSphere Process Server Information Center for additional information about Security and Database performance considerations: http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp?topic=/com.ibm.websphere.wps.610.doc/wel come_top_wps.htm

Configuring Oracle Java Virtual Machine (JVM)

The Oracle Database needs to have the Oracle JVM (or JServer in 9i terms) enabled. To enable this, you can use the Oracle Database Configuration Assistant or specific SQL scripts. See the Oracle documentation for details. You can check whether the Oracle JVM/JServer component is installed by invoking the following query from SQL*Plus, as SYS: 1. (Oracle 9i) describe dbms_java 2. (Oracle 10g) select version, status from dba_registry where comp_id='JAVAVM'; In addition, the correct privilege to run Java needs to be granted to each of our users (you will receive XA errors if you do not do this). For each user, the Oracle DBA needs to run the following command: grant javauserpriv to <user>; This is done later in this article for each database user.

Configuring XA for Oracle

XA is a two-phase commit protocol defined by the X/Open DTP group. The database used by WebSphere Process Server needs to be XA enabled. To do this, two tasks need to be carried out by your DBA: The <ORACLE_HOME>/javavm/install/initxa.sql script needs to be run on the WPSDB database. This script configures the database for XA. More information on this requirement is available from Configuring and using XA distributed transactions in WebSphere Studio, see the Resources section. 1. The following queries need to be executed: grant select on pending_trans$ to public; grant select on dba_2pc_pending to public; grant select on dba_pending_transactions to public; grant select on V$XATRANS$ TO PUBLIC; Note: If the last query fails, it means that the V$XATRANS$ view does not exist. You need to prepare the Oracle database for XA transactions recovery by executing the xaview.sql script located under <ORACLE_HOME>/RDBMS/ADMIN.

sqlplus SYS/xxxxxx@WPSDB @xaview.sql Additionally, for each user, you will need to grant access to dbms_system (this is done later for each user).

Database Users/Privileges Considerations

For the purposes of this article, we configured everything in a single Oracle database. This is an initial configuration, and would probably be modified after reviewing the performance of the databases. Since we are using the Deployment Environment feature from the administrative console, and will be delaying the execution of database scripts, we do not need any database access during the WebSphere Process Server installation. You may have your DBA create the required users/schemas according to the following table and privileges (with the exception of Common Event Infrastructure (CEI). Table 1 lists the database schemas that are required for WebSphere Process Server, along with the names used for the user IDs (schemas) in the configuration presented in this article. Table Database Tables Schema/Userid used in this article WPSDB EVENT SCASYSME SCAAPPME CEIME ESBLOG BPCME BPCDB BPCOBS

Usual name or default name WPRCSDB CEI First 3 letters of instance SID + SS00 First 3 letters of instance SID + SA00 First 3 letters of instance SID + CM00 ESBLOG First 3 letters of instance SID + BM00 First 3 letters of instance SID + BE00 First 3 letters of instance SID + BC00

Purpose of this user Main Process Server configuration CommonDB Common Event Infrastructure configuration SCA System Bus messaging engine data store configuration SCA Application Bus messaging engine data store configuration CEI messaging engine data store configuration ESB Messaging Mediation data store configuration Business Process Container Bus data store configuration Business Process Container configuration Business Process Observer

Have your DBA create the above users according to the privileges below. Note that the CREATE/GRANT commands below assume it is the DBA that is running these commands.

Common database User (WPSDB)

The Process Server configuration database user, WPCDB, has no special requirements other than it must exist. To create it, your DBA needs to run a command equivalent to the following: create user WPSDB identified by passw0rd; grant connect, resource, unlimited tablespace to WPSDB; grant execute on dbms_system to WPSDB; grant javauserpriv to WPSDB; The above commands use the systems default tablespace; your DBA may wish to specify a different tablespace and this is fine.

Business Process Container User (BPCDB)

To create the Business Process Container database user, the DBA needs to run a command similar to: create user BPCDB identified by passw0rd; grant connect, resource, create tablespace, drop tablespace, create view, unlimited tablespace to BPCDB; grant execute on dbms_system to BPCDB; grant javauserpriv to BPCDB;

Business Process Container Observer User (BPCOBS)

create user BPCOBS identified by passw0rd; grant connect, resource, create tablespace, drop tablespace, create view, unlimited tablespace to BPCOBS; grant execute on dbms_system to BPCOBS; grant javauserpriv to BPCOBS;

Common Event Infrastructure (CEI) User

Configuring CEI generates a whole set of scripts that include actions to create tablespaces, roles and a CEI user based on the database information provided during configuration. These scripts may be handed off to the DBA for execution as some of the scripts need DBA-like privileges for creating the user and linking the roles and tablespaces to this user.

ESB Message Logger User (ESBLOG)

The ESBLOG.MSGLOG table is used by the Message Logger ESB primitive to log messages. create user ESBLOG identified by passw0rd; grant connect, resource, unlimited tablespace to ESBLOG; grant execute on dbms_system to ESBLOG; grant javauserpriv to ESBLOG;

Messaging engines Datastores

The same table names (SIB000, SIB001, etc.) are used by each messaging engine; therefore, you need to use a specific schema (user) for each messaging engine. create user SCASYSME identified by passw0rd; grant connect, resource, unlimited tablespace to SCASYSME; grant execute on dbms_system to SCASYSME; grant javauserpriv to SCASYSME; create user SCAAPPME identified by passw0rd; grant connect, resource, unlimited tablespace to SCAAPPME; grant execute on dbms_system to SCAAPPME; grant javauserpriv to SCAAPPME; create user CEIME identified by passw0rd; grant connect, resource, unlimited tablespace to CEIME; grant execute on dbms_system to CEIME; grant javauserpriv to CEIME; create user BPCME identified by passw0rd; grant connect, resource, unlimited tablespace to BPCME; grant execute on dbms_system to BPCME; grant javauserpriv to BPCME;

Installing WebSphere Process Server 6.1

____ 1. Once the database users are set up, we will install WebSphere Process Server 6.1.0.0, upgrade to WebSphere Process Server 6.1.0.1 and create a Deployment manager (DMGR) and a Custom node, federate the Custom node to the DMGR and use the administrative console to set up the Clustered topology.

Important Note: At the time of writing this document, WebSphere Process Server 6.1.0.1 was released and it is highly suggested that users upgrade to the latest fix pack available and install the latest critical fixes available, as well. ____ 2. Select the I accept the terms in the license agreement option button and click Next.

____ 3.

After the System Prerequisites check passes, hit Next.

____ 4.

Select Install a new copy of WebSphere Process Server and click Next.

____ 5.

Select Typical Installation and click Next.

____ 6.

Type a directory to install WebSphere Process Server 6.1. Make sure that the path name is short and contains no spaces. For the rest of this lab, we will assume our installation location is C:\WPS61.

____ 7.

In the WebSphere Process Server Environments window, select None.

____ 8.

Click Next. A warning window will pop up and inform you WebSphere Process Server requires at least one profile to be function. Click Yes to continue the installation.

Note: What we want to do is install the WebSphere Process Server binaries first and then go about creating the DMGR and other profiles later.

10

____ 9.

Review the summary information and click Next.

11

____ 10. The Websphere Application Sever and WebSphere Process Server will begin installing. Please be patient, this installation can take between 15-45 minutes.

12

____ 11. When the installation finishes, review the installation results and click Finish.

13

Updating your WebSphere Process Server 6.1.0.0 installation to WebSphere Process Server 6.1.0.1
At the time of writing this document WebSphere Process Server fix pack 6.1.0.1 has been released. For more information, refer to: http://www.ibm.com/support/docview.wss?rs=2307&uid=swg24018733 For the purpose of this document, we will update our WebSphere Process Server 6.1.0.0 installations to WebSphere Process Server 6.1.0.1 ____ 1. Download the latest WebSphere Process Server V6.1.0 Fix Pack 1 (6.1.0.1) from: http://www.ibm.com/support/docview.wss?rs=2307&uid=swg24018733 Unzip this to a temporary location. Make a note of this temporary location. You should see 3 .pak files after you unzip the Fix Pack. Download the latest Update Installer for WebSphere Application Server V6.0.2.21 (onward) and V6.1 from: http://www.ibm.com/support/docview.wss?rs=180&uid=swg24012718 Make sure you scroll down until you see the Download Package table for the different platforms and download the correct version. Unzip this to a temporary location and install the Update Installer program by running the install.exe program. Install this to a folder location of your choice. Start the Update Installer program by running update.bat from under the folder you installed the Update Installer program to. Make sure the version in the title bar says 6.1.0.15

____ 2.

____ 3.

14

____ 4.

Click Next and select the WPS installation that you want to update (C:\WPS61 for this document)

15

____ 5.

Click Next and select the Install Maintenance Packages option

16

____ 6.

Click Next and then select the top level folder location of where you unzipped the Fix Pack files into from Step 1 above (F:\dwnloads\6.1.0-WS-WPS-ESB-WinX32-FP0000001 in this case. This folder has 3 .pak files)

17

____ 7.

Click Next and by default all the maintenance packages in the Fix Pack should have been selected for installation. You will need to install all of these packages.

18

____ 8.

Click Next and after Prerequisite check, you should see an Installation Summary screen

19

____ 9.

Click next to start off the updates installation process.

20

21

____ 10. Once the Installation is complete, you should see the above screen if the update process was successful. Click Finish to exit the Update Installer.

22

____ 11. Go to the bin directory of the WPS product (C:\WPS61\bin) in this case and run versionInfo.bat to make sure the version information shows up correctly.

____ 12. At this point you have the latest fix pack applied to your WebSphere Process Server installation.

23