You are on page 1of 87

S s

Guide

®

BusinessManager 6.5

Clustering

End User License Agreement
IMPORTANT! PLEASE READ CAREFULLY. This License Agreement is a legal agreement between you and Savvion for Savvion Software Product(s) purchased hereby which include computer software and may include associated media, printed materials, and online or electronic documentation. Before installing any Savvion Software Product (the “Software”), you should carefully read the following terms and conditions. If you do not accept the terms and conditions of this License Agreement, please do not install the Software. BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE, YOU ARE CONSENTING TO BE BOUND BY AND ARE BECOMING A PARTY TO THIS AGREEMENT. REDISTRIBUTION OR RENTAL NOT PERMITTED. Software Product License. The Software is protected by copyright laws and international copyright treaties, as well as other intellectual property laws. A patent for Savvion BusinessManager (SBM) is pending. The Software is licensed, not sold. This Agreement sets forth the terms and conditions of your use of the Software. License Grant. Savvion (“the Licensor”) grants you (“the Licensee”) a non-exclusive license to use the Software. Disclaimer Of Warranty. The Software is provided on an “AS IS” basis, without warranty of any kind, including without limitation the warranties that the Software is free of defects, merchantable, fit for a particular purpose, or non-infringing. This disclaimer of warranty constitutes an essential part of this License Agreement. Scope Of License Grant. The Licensee may use the Software on any single computer or server, or on a network as defined under the terms of the specific Software License(s) acquired by the Licensee for each Savvion Software Product. The Licensee may not permit other individuals to use the Software except under the terms listed above. The Licensee shall not modify, translate, reverse engineer, decompile, disassemble, or remove any proprietary notices or labels on the Software. Title. Title, ownership rights, and intellectual property rights in the Software shall remain in Savvion. Permissions. No part of this publication may be stored in a retrieval system, transmitted, translated, or reproduced in any way onto any medium, including but not limited to photocopy, photograph, microfilm, magnetic or other record, without the prior agreement and written consent of Savvion. Termination. This License Agreement and the license granted hereunder will terminate automatically if you fail to comply with the limitations described herein. Upon termination, you must destroy all copies of the Software and Documentation. Export Restriction. The Licensee acknowledges that the Software hereunder shall be subject to the Export Restriction Regulations of USA. The licensee agrees not to export the Licensed Software nor knowingly provide the same to any third party who exports or re-exports the Licensed Software, in whole or in part, directly or indirectly, to countries which are subject to Export Restrictions. Disclaimer. IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES WHETHER IN AN ACTION OF CONTRACT, TORT, INCLUDING NEGLIGENCE, OR OTHERWISE, OR LOSS OF DATA, USE, REVENUE OR PROFIT WHETHER OR NOT THE PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LIABILITY LIMITATION.

General. This Agreement represents the complete agreement concerning the License granted hereunder and may be amended only, in whole or in part, by an addendum in writing executed by duly authorized representatives of Savvion. If any provision of this Agreement is held to be unenforceable, such provision shall be removed only to the extent necessary to make it enforceable. This Agreement shall be governed by the laws of the State of California.
Third Party Software. SBM provides a modified PNGencoder from http://www.keypoint.com/. Original com.keypoint.PngEncoder is a Java class that converts Image objects to PNG byte arrays. Copyright (C) 1999 J. David Eisenberg. This library is free. You can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This library is distributed for your use, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. You should receive a copy of the GNU Library General Public License along with this library. If not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. SBM includes software developed by the jfor project (http://www.jfor.org). Copyright (c) 2002 by the jfor project. All rights reserved. For more information, go to http://www.jfor.org/jfor-license.html. SBM includes a JDBC driver from Oracle for Oracle database 9i/10g. (c) Copyright 2004, Oracle Corporation. All rights reserved. Review the license terms and agreements for the JDBC driver at http://otn.oracle.com/software/tech/java/sqlj_jdbc/htdocs/jdbc9201.html. Oracle is a trademark of the Oracle Corporation. SBM includes a jConnect 5.5 driver from Sybase. Review the license terms and agreements for the driver at http://www.sybase.com. (c) Copyright 2004 Sybase Inc. SBM provides an embedded application server, evaluation version, from Pramati. Copyright © 2004 Pramati Technologies. All rights reserved. Review the copyright for Pramati app server at http://www.pramati.com/. Contact Savvion, Inc. to obtain full licenses for this application server. The source code, object code, and documentation in the com.oreilly.servlet package are copyrighted and owned by Jason Hunter. Binary code of some servlets in this package is included in SBM. Copyright (c) 1998-2004 Jason Hunter. All rights reserved. Review the copyright and agreements at http://www.servlets.com/copyright.html. SBM includes software developed by the Apache Software Foundation (http://www.apache.org/) and therefore is subject to the terms of the Apache Software License, Version 1.1 (http://www.apache.org/LICENSE). SBM includes Mozilla Rhino JavaScript implementation in Java. See Mozilla Public License at http://www.mozilla.org/MPL/MPL-1.1.html. Copyright (c) 1999-2006 by Savvion Incorporated, 5104 Old Ironsides Drive, Suite 205, Santa Clara, California 95054, USA.

Table of Contents

Preface
Audience....................................................................................................................................................... 7 Information on SBM Documentation.............................................................................................................8 Conventions Used in this Manual ................................................................................................................. 9 Product Support Contact Information ........................................................................................................... 9

Chapter 1—Introduction
Clustering Terminology ...............................................................................................................................10 Designing Server Clusters.......................................................................................................................... 11

Chapter 2—Clustering in SBM
What’s New ................................................................................................................................................ 13 Clustering Features .................................................................................................................................... 13 Clustering SBM Servers ............................................................................................................................. 14 Load Balancing........................................................................................................................................ 14 Failover.................................................................................................................................................... 14 Vertical Clustering ................................................................................................................................... 15 Installing Applications in Clustered Environment........................................................................................ 15 BPM Portal Clustering ................................................................................................................................ 15 Using BPM Studio in Clustered Environment ............................................................................................. 16 Using Managed Adapters in Clustered Environment.................................................................................. 16

Chapter 3—Using the Cluster Configuration Tool
Starting the Cluster Configuration Tool ....................................................................................................... 19 Configuration Panel................................................................................................................................. 20 Cluster Panel........................................................................................................................................... 20 Server Panel............................................................................................................................................ 21 Setting Up the Cluster ................................................................................................................................ 21 EJB Cluster ............................................................................................................................................. 21 JMS Cluster............................................................................................................................................. 23
3 CLUST-DG-6502

Web Cluster............................................................................................................................................. 24 Standalone Servers ................................................................................................................................. 26 Proxy Server............................................................................................................................................ 27 Document Server .................................................................................................................................... 28 URL for the Document Server .......................................................................................................... 28 Viewing the XML File...............................................................................................................................29 Running modifyprop Utility ...................................................................................................................... 29 Updating the JNDI Properties File...........................................................................................................29 Running the Cluster.................................................................................................................................... 29 Adding New and Recovered Nodes ...........................................................................................................30 Editing and Deleting Nodes ........................................................................................................................ 30

Chapter 4—Editing the Cluster Configuration File
Understanding the Tags.............................................................................................................................. 33 General Tags ........................................................................................................................................... 33 <cluster-configuration> ..................................................................................................................... 33 <domain-name>................................................................................................................................ 33 <protocol> ......................................................................................................................................... 33 <synchronize-time> .......................................................................................................................... 33 <authentication> ...............................................................................................................................34 <multicast> ....................................................................................................................................... 34 <cluster> ........................................................................................................................................... 34 <node>.............................................................................................................................................. 34 JMS Cluster Tags .................................................................................................................................... 35 <file-store> ........................................................................................................................................ 35 <persistence> ................................................................................................................................... 35 Single Server Tags .................................................................................................................................. 36 Order of Tags........................................................................................................................................... 36 Configuring the Cluster...............................................................................................................................37 EJB Setup ............................................................................................................................................... 37 Single EJB Server............................................................................................................................. 37 EJB Cluster ....................................................................................................................................... 37 JMS Setup............................................................................................................................................... 38 Single JMS Server ............................................................................................................................ 38 JMS Cluster ...................................................................................................................................... 38 JMS Cluster Persistence .................................................................................................................. 38 Portal Setup............................................................................................................................................. 39 Single Portal Server .......................................................................................................................... 39 Web Cluster ...................................................................................................................................... 39 Proxy Server............................................................................................................................................ 39 Document Server .................................................................................................................................... 39 URL for the Document Server .......................................................................................................... 40 Setting the Cluster in Stages ...................................................................................................................... 40 EJB Cluster ............................................................................................................................................. 40 JMS Cluster............................................................................................................................................. 41 Web Cluster............................................................................................................................................. 41 Running the Cluster Setup ......................................................................................................................... 41 Cluster Setup Log File............................................................................................................................. 41 Adding New and Recovered Nodes ...........................................................................................................41
Clustering Guide 4

........................................................................................................................................................... 47 Configuring BizPulse for Failover ................................................................................................................................................................ 53 Using Ports...................................................................................................................................................................................... 59 Configuring BizPulse for Failover ........ 55 Specifying Environment Variables ........................................................................................................................................................................................................................................................................................................................................................................................... 49 Starting the BizPulse Server ............................................ 50 Performance Tuning ................... 47 Restoring Original Configuration ..................................................................................... 68 Clustering Guide 5 .................................................................................................................................................................................................................................................. 48 Working with the Cluster........................................................................................................................................................................................................................................................................................................................... 58 Restoring Original Configuration .......................................................................................................... 48 Starting the Cluster......................................................................................................................................................................... 62 Chapter 7—Configuring WebSphere Application Server Before Clustering....... 48 BizPulse Application Loading in a Cluster.................................................... 49 Starting the BizLogic Server...................................................................................................................................................... 49 Starting the Servers............................................................................................................................................................................................................................................................................................................................................................................... 44 Configuring Clusters ........................................ 62 Performance Tuning ................................................................................... 61 JMS Migration in a JMS Cluster .................................................................................................................................................................................. 46 Modifying SBM Properties .............................................................................................. 67 Configuring Clusters .............................................................................................................................................................................................. 56 JMS Cluster with Standalone EJB Server................................................................................................. 42 Chapter 5—Configuring Pramati Application Server Before Clustering... 59 Working with the Cluster............ 58 Modifying SBM Properties ................................................................... 50 Stopping the Cluster .................................................................................................................................. 60 Stopping the Cluster .......................................................................................................................................................................................................................................................................................................................................................... 65 Using Ports......................................................................................................................Database Storage of Cluster Files.................................... 46 Setting up Web Cluster ............................................. 43 Using Ports............ 56 JMS Cluster with EJB Cluster ............................................................57 Setting up Web Cluster ...............................................................56 Setting up JMS Cluster................. 57 Setting Up the Cluster .... 68 Setting up EJB and Portal Clusters ...................................................................... 59 BizPulse Application Loading in a Cluster......................................... 46 Setting Up the Cluster .. 60 Starting the Cluster...................................................................................................................... 45 Setting up EJB Cluster ........................................................................................................................................................................................................................................... 50 Chapter 6—Configuring WebLogic Application Server Before Clustering.......................................... 46 Setting up High Availability JMS Cluster ............................................................................................................................................................................................................................................................................ 53 Configuring Clusters .................................................................................................................................................

............................................... 69 Setting Up the Cluster ............................................................................. 79 Glossary Index Clustering Guide 6 ............................................................................... 72 Starting the BizPulse Server...................................................................................................................................................................................................................... 74 Appendix A—BizLogic Server Commands Starting BizLogic Server Instances..... 69 Configuring Portal Load Balancing....................................................................................... 69 Modifying SBM Properties ........................................................................................... 70 Configuring BizPulse for Failover ....................................... 71 Starting IBM HTTP Server ................................................... 71 BizPulse Application Loading in a Cluster........................................................................................................................ 72 Starting the BizLogic Server .................................................................................................................................................. 71 Starting EJB and Portal Clusters .................................................................................................................77 Appendix B—BizPulse Server Commands Starting and Stopping BizPulse Server.................................................................................................................................................................................................................................................................................................................................................................................. 73 Restoring Original Configuration ................................................................. 73 Working with Two-Node Clusters .............................................................................................................. 78 Starting and Stopping BizPulse Monitoring................. 71 Working with the Cluster...................................................................................................................................... 76 Stopping BizLogic Server Instances ...........................................................................Configuring for QuickRules Support........................................................................................ 72 Stopping the Cluster ....................................................................................

Preface This guide is part of the documentation set for Savvion BusinessManager. and determine the business processes. analyze. Responsible for creating customized applications for implementing business processes and developing interfaces associated with tasks.5 SP2. Audience The range of Savvion BusinessManager (SBM) modules creates the opportunity for four types of users. SBM application developers may work closely with SBM business managers to define the requirements of an application. and administering SBM applications and utilities. Responsible for configuring SBM components. BPM Portal’s Management module serves as the primary interface to SBM for the SBM Manager. and control business processes. A sales representative responding to a customer request. version 6. HR personnel scheduling interviews for a potential hire. An engineer reviewing a trouble ticket reported by a customer. managing user/group profiles. Examples include: • • • • SBM Manager An office administrator submitting an online purchase request. summarized in the following table: Table 1 SBM User Types and Responsibilities User Type SBM User Responsibilities Responsible for carrying out specific business tasks using SBM applications. enabling the manager to monitor. Application Developer SBM Administrator 7 . Responsible for automating business processes in a particular business domain. Also uses the Process Modeler for modeling and simulation.

8 Information on SBM Documentation . Table 2 SBM Documentation If you are the… SBM User Read the… BPM Portal User’s Guide Quick Start Guide Terminology Guide SBM Manager Tutorial Guide BPM Portal Manager’s Guide BPM Portal User’s Guide Terminology Guide Application Developer Tutorial Guide API Reference Guide Application Developer’s Guide BizLogic Developer’s Guide BizPulse User’s Guide BizSolo User’s Guide BPM Portal Manager’s Guide BPM Portal User’s Guidea BPM Studio User’s Guide Clustering Guide Customization Guide Managed Adapters Guide Quick Start Guide Terminology Guide Tutorial Guide SBM Administrator Web Services Developer’s Guide BizPulse User’s Guideb BPM Portal Administrator’s Guide BPM Portal Manager’s Guide BPM Portal User’s Guide Installation Guide Managed Adapters Guide Terminology Guide Troubleshooting Guide for Administrators a.Information on SBM Documentation SBM documentation contains information for the entire range of SBM users. b. Refer to the sections detailing BizPulse Admin. we recommend the guides that are most relevant to each type of user. Demonstrates how to thoroughly test SBM applications. In the following table.

http://www. file names and book titles.savvion. If you are already a customer. • Your database management system and version. 9 Conventions Used in this Manual .com 1-877-SAVVION in the United States or 1-408-330-3000 for local calls 408-330-3111 for international calls 1-408-330-3444 for the Product Support Fax Line Postal Address Savvion BusinessManager Product Support Team 5104 Old Ironsides Drive. or if you need clarification on the issue. • Your SBM version and build number. Represents code segments or examples. You can contact the team through the Internet.. options.. please contact the Savvion Product Support Team. or by postal mail. you can send an e-mail to Product Support and request them to provide you with a user name and password to access this site. Table 3 Conventions in this Manual Convention bold bold italic italic Purpose Indicates titles of command buttons. as provided in Table 4. please have the following information available: • Your name. Indicates the path in Windows environment. Indicates directory paths. check boxes. • Your operating system. Suite 205 Santa Clara. dialog boxes and portal page names. lists. To enable us to quickly answer your questions..Conventions Used in this Manual This document uses the following conventions and terminology notations.. you can also access SBM discussion groups at: http://www. application server and browser. installation site address and the license key for Savvion software. For UNIX environment.com/support/tsgsupport/discus/ E-mail Telephone support@savvion. and information on JVM and JDBC used.savvion. e-mail. telephone. Represents notes that alert you on specific SBM elements and similar advisory information.com/support/ If you are a first time user. with version and service pack details. Web Site Use. CA 95054 USA This contact information is for customer support ONLY. monospace backward slash “\” SBM_HOME or %SBM_HOME% Product Support Contact Information If the product documentation does not provide a solution to your specific issue. if any. Table 4 Savvion BusinessManager Product Support Team Contact Information To contact by. replace with forward slash “/” Represents the installation directory of SBM.

Is the ability to switch between the locations where similar requests are handled.Chapter 1 Introduction Clustering involves grouping independent nodes together to work as a single system that allows shared processing. Clustering Terminology Some important clustering terminology is explained below. Node. • Offering scalability by allowing dynamic addition of resources to improve performance. such as a common data storage. For example. and then routed to another server that is still operational. However. Load Balancing. denoting the amount of time that an application or system is available to perform work. Each node in the cluster will have its own local resources. a clustered system provides higher availability. Deciding which server handles the request depends on the load-balancing logic. 10 . the cluster appears as a single system. A system with high availability uses load balancing so that all requests are routed to one or more preferred servers until one of the servers becomes unavailable. and greater scalability than each node can provide independently. High Availability. Availability. These common resources are accessible to each node in the cluster. • Ensuring reliability through reduced system failure. Refers to the individual system that is part of a cluster. by managing failover. A cluster is a loosely coupled group of nodes collaborating to provide shared access to the services that each node hosts. a request for a database connection might be handled on any one of four different servers in a cluster. the cluster also has common resources. The objectives of clustering are: • Providing high availability by balancing resource requests. Is defined as support to backup services in case of a system or node failure. Availability is typically measured in percentage uptime. To the other systems. or to the other components of the same system. Together. increased reliability. Refers to the quality of the system's response to process a request.

This refers to multiple installations of SBM. For more definitions. Horizontal Cluster. each hosting a cluster node. then more servers are required to be available for failover. a cluster having three nodes could have two nodes running in the same machine (vertical cluster) and the third node in a different machine (horizontal cluster). A successful failover means to transfer the service without any intervention by client or manual process. Is the ability for a request that is being serviced.Failover. This refers to a single installation of SBM hosting multple cluster nodes. Designing Server Clusters The cluster design depends on several factors such as: • Extent of high availability needs • Users. For a fuller listing of SBM terminology. Clustering Guide 11 Designing Server Clusters . Reliability. Vertical Cluster. if the risk of failure is high. along with the possibility of multiple failures. The increase in load could be due to increase in the number of users accessing the application. running in the same physical machine. running in the same physical machine or multiple machines. but are part of the same cluster and runs homogeneously. without unacceptable degradation under increase in load. On the other hand. more servers are needed in the configuration to ensure high availability and good performance at all times. Denotes capability of a system to scale up to provide sustained system availability and throughput. to have a high availability switchover to another node without disruption of the service. A vertical cluster could be part of a horizontal cluster that is. Is the ability of a system to perform its required functions and sustain a requested service under stated conditions for a specified period of time. or in the volume or size of user transactions or actions. and the volume of the user transactions • Network design and capacity • Database design and dependencies • Systems management If the load requirements are unpredictable. see the Glossary on page 80 of this guide. Scalability. see the Terminology Guide in the SBM_HOME\docs folder.

Figure 1 Cluster Design Clustering Guide 12 Designing Server Clusters .The design process is explained in the following diagram.

and describes the basic Clustering features. • Support to different application server: o o o Pramati WebLogic WebSphere For more information.Chapter 2 Clustering in SBM This chapter lists the new Clustering functions introduced in SBM 6. SBM Server as a Windows service is not supported. refer to Configuring Pramati Application Server on page 43.5 SP2. and Configuring WebSphere Application Server on page 64. Configuring WebLogic Application Server on page 52. 13 . For more information. NOTE: On cluster. refer to Editing the Cluster Configuration File on page 32. What’s New SBM provides the following new features for clustering: • Support for High Availability JMS with Pramati Cluster • Ability to refresh configuration parameters across all nodes • Support for Vertical Clustering Clustering Features SBM continues to support the following clustering features: • Load balancing and Failover • Automatic clustering o XML based cluster configuring.

The following figure shows a setup with three nodes in a cluster. SBM employs load balancing to meet these demands. where only one node is always active. In Figure 2. assuring failover. In case of BizLogic server load balancing. a group of application server clusters work as a single system sharing the load. Clustering Guide 14 Clustering SBM Servers . server clustering is used for Load Balancing and for Failover. Note: BizLogic/BizPulse Web Services API and Process Repository are not supported in the clustered environment. When the active node fails.Clustering SBM Servers In SBM. The setup shown in Figure 2 represents three nodes. BizPulse is clustered for failover to ensure high availability. All three nodes have a common database. The requests sent by the client are shared by the three nodes. where the system must be configurable to support backup services in case of infrastructure component failure. This section describes how the servers are configured. Figure 2 Clustering SBM Servers Load Balancing Large-scale business solutions require that the system is scalable to meet the performance and throughput demands with increase in workload. one of the remaining nodes takes over. Failover Large organizations focus on high availability of their systems. the client sees the cluster as a single SBM setup.

Installing Applications in Clustered Environment For installing applications in a clustered environment. the users from different browser instances log in to the SBM using a single URL that actually points to the proxy Portal server. Clustering Guide 15 Installing Applications in Clustered Environment . a physical copy of the installed SBM applications must be available in all the nodes. The proxy server then directs the request to any node in the cluster. when the request is served by any one of the nodes. first you need to copy the Hiring directory to SBM_HOME\ebmsapps and SBM_HOME\pramati\server\nodes\portalServer\archives\public_html\sbm\ebmsapps (in case of Pramati application server). When you install an application in the clustered environment. a single proxy server provides the load balancing and failover. Log information for individual nodes is recorded in separate log files. see Using BPM Studio in Clustered Environment on page 16. if you want to install the Hiring application. it creates the application files on any one node in the cluster. Note: In the clustered environment. go to the Administration module. BPM Portal clustering refers to configuring the Portal servers in a cluster for load balancing and for failover. BPM Portal Clustering In SBM architecture.log and bizlogic_node2. This is achieved transparently and without any parameter or configuration changes. For example.log. to all the other nodes in the cluster. we recommend user management realms other than PAKRealm. Hence. In this configuration. if the nodes in vertical cluster are node1 and node2 then. the Web container. For example. JSPs. After the application is copied to all the nodes. and servlets. and install the application Hiring. where a single SBM installation may host more than one node. You need to copy them from the node where it got installed. Each component log file name would be appended with “_<nodeName>”.Vertical Clustering SBM also provides support for vertical clustering. or the Portal server is a run-time environment for SBM. it is available in the BizLogic/BizSolo Applications list. Note: You can avoid copying the files manually by using the BPM Studio. we recommend that you use BPM Studio. first you need to manually copy the application directory to the SBM directory and the application server web directory of each node in the cluster. If you want to use the BPM Portal to install applications. For more information. SBM Portal servers (Web containers). Then you can login to the BPM Portal. This proxy server is referred as the Web Load Balancer Node. Then you can install single or multiple applications from the BPM Portal Administration module. The BPM Studio will automatically deploy applications to every node in the cluster. are clustered mainly for load balancing to obtain high scalability and required performance. Typically.log would be bizlogic_node1. bizlogic. Refer to Using BPM Studio in Clustered Environment on page 16 for more information.

the actual design is carried out from the BPM Portal. you need to copy the installed application from the node where it got installed. You must ensure that the physical copies of the application are available in all the nodes before installing the application. If you have added other Target elements to the Deployment element. or performs its own function of data transformation. Part of the functions related to the operation of the managed adapters (such as adapter configuration. and the new application may get saved in any one node in the cluster. When you actually install the new Balanced Scorecard application. Navigate to BPM Studio and click Project > Deploy. If. simplifying the development process of such adapters. input/ output mapping) are handled by standardized SBM components. You need to copy these files to all nodes to make web services run in the clustered environment.savvion. Edit the Deployment element by adding a Target element. which is now in the Server drop-down list of available deployment targets. 5. Deploy as usual (see the steps in the “Deploying an Application on an SBM Server” section in the BPM Studio User’s Guide) and the application will be available on each machine in the Cluster. for example.com:8181/sbm/deployment"/> <Server url="http://server3. Similarly. as shown in the following example. you have a cluster of three machines—server1. Using BPM Studio in Clustered Environment You can use BPM Studio to deploy an application to a cluster of machines.savvion. Using Managed Adapters in Clustered Environment Savvion's Managed Adapters act as a translating module that converts the SBM-specific protocol to another application-specific protocol. you can add multiple Target elements to the Deployment element.savvion. deploy an application to this cluster by performing the following steps: 1. 4. similar to other BizLogic/ BizSolo applications. 2. publishing applications/worksteps as web services generates WSDL files on one of the nodes. to all the other nodes in the cluster.com:8181/sbm/deployment"/> <Server url="http://server2. server2 and server3. 3. Navigate to the file BPMStudio_HOME\conf\DesignerDeployment. Select Cluster (the Label in the code sample in Step 2).In case of Balanced Scorecard Designer. <Deployment> <Target> <Label>Cluster</Label> <Description>Clustered SBM environment</Description> <Server url="http://server1. In SBM. Clustering Guide 16 Using BPM Studio in Clustered Environment .com:8181/sbm/deployment"/> </Target> </Deployment> If required. a Managed Adapter is a pluggable component that connects SBM to an external system such as database and ERP system. see the BPM Studio User’s Guide). opening the Deployment Wizard (for more information.xml. the label of these targets will also appear in the Server drop-down list.

jar and any related database drivers in the server classpath on all the nodes. make sure the Workbook is present at the same location on all the cluster nodes. Savvion offers nine Managed Adapters: J-Integra Excel Adapter. see Chapter 3 in the Managed Adapters Guide). JMS Adapter. • A J-Integra Excel Adapter requires a temporary directory to store its work files. FTP Adapter . These issues are described for the various managed adapters in the following section. QuickRules Adapter and Web Service Adapter. This temporary directory must be present on all the cluster nodes. You can specify this directory through the Excel Adapter Configurator (for more information. File Adapter. • For iWay Adapters. must be in the server classpath for each node in the cluster. Database Adapter. iWay Adapter. Email Adapter. the SBM_HOME\Schema directory and the Dictionary file must be available on each of the cluster nodes at the same location.Currently. For example. When using a managed adapter in a clustered environment. you must ensure that all the files required for the work of the adapter are present in all the cluster nodes. if you are using the iWay RDBMS Adapter. Clustering Guide 17 Using Managed Adapters in Clustered Environment . include the iwrdbms. • If you configured the J-Integra Excel Adapter to use a static Workbook file (as opposed to obtaining the Workbook from a Document dataslot). • The adapter jar and other jar files that the iWay Adapter needs.

and procedures for using this tool are covered in this chapter. JMS cluster. and you may require to refer to them. The remaining chapters of this guide describe procedures for individual application servers providing advanced information. the file sbm-cluster. Web cluster. 18 . or any combination of these. The cluster configuration is specified for the EJB cluster.xml can be edited manually as described in Editing the Cluster Configuration File on page 32. The Cluster Configuration Tool works in environments that support graphics.Chapter 3 Using the Cluster Configuration Tool The Cluster Configuration Tool is a quick way of configuring the SBM cluster by providing the required system details and running the cluster setup directly from the Tool after it validates the settings. For environments that do not support graphics.

If the application server is WebLogic.The Cluster Configuration Tool automatically detects and displays the application server and its relevant details. • View XML: This tab displays the generated XML file after the setup configuration is verified. and Server panel. For example. Depending on the selection in the left pane. Cluster panel. and the Server panel. the tool will additionally display WebLogic domain and location. Figure 3 Cluster Configuration Tool Interface In the left pane. the above figure shows the application server as pramati.Configuration panel. Clustering Guide 19 Starting the Cluster Configuration Tool . The following figure shows the Cluster Configuration Tool screen for a fresh SBM installation. go to SBM_HOME\cluster\bin and run setupcluster. These are described in detail in the following sections. the top node SBM Cluster Configuration displays the application server details. the right pane displays different panels . and displays its version and protocol.bat|sh. The Cluster Configuration Tool has the following tabs: • Setup: This tab shows the configuration panel.Starting the Cluster Configuration Tool To start the Cluster Configuration Tool. Cluster panel. • Run: This tab displays the log messages when the cluster is being deployed.

The Configuration panel is displayed in the right pane as shown in the following figure. click the Clusters node or the Standalone Servers node. Figure 4 Configuration Panel The Configuration panel displays links to the clusters or servers available as an alternative way of navigation.Configuration Panel In the left pane. Click any existing node. click the Clusters node. or click Add Node to display the Cluster panel in the right pane as shown in the following figure. Figure 5 Cluster Panel The Cluster panel displays information about the selected cluster. and then click any cluster. Cluster Panel In the left pane. Clustering Guide 20 Starting the Cluster Configuration Tool .

click on the Standalone Servers node. To set up the EJB cluster. you can have either a single EJB server. JMS and Portal (Web) servers can be standalone or in cluster. EJB Cluster In your SBM setup. and Web clusters. Figure 6 Server Panel The Server panel displays information about the selected server. Note that EJB. If you have chosen a cluster for any of them. In the left pane. under the node SBM Cluster Configuration. then the standalone server is disabled. Clustering Guide 21 Setting Up the Cluster . Note: The document server is required in case of Web cluster. JMS. or a cluster of EJB servers.Server Panel In the left pane. and then click any server. Setting Up the Cluster This section describes setting up the EJB. click Clusters. carry out the following steps: 1. The Server panel is displayed in the right pane as shown in the following figure.

Enter the location of SBM Home. Specify Name for the node. Figure 8 EJB Cluster.” in the node name to avoid any cluster start problems. click Add Node to display the node information as shown in the following figure. We recommend that you do not use the character “. which should be unique. 6. Figure 7 Setting EJB Cluster 3.2.Adding node 4. In the Cluster panel. Specify the IP Address. 5. HTTP Port and JNDI Port on which the node listens. Clustering Guide 22 Setting Up the Cluster . which is the installation directory of SBM. click EJB to display the EJB cluster setup as shown in the following figure. Under the Clusters node.

To set up the JMS cluster. Click Save to save the configuration. click JMS to display the JMS cluster setup as shown in the following figure. Under the Clusters node. or a cluster of JMS servers. carry out the following steps: 1. JMS Cluster In your SBM setup. Click Add to add the node to the EJB cluster. you can have either a single JMS server. Figure 9 Setting JMS Cluster Clustering Guide 23 Setting Up the Cluster . 8. click Clusters. under the node SBM Cluster Configuration. In the left pane. Click Add & Continue to add more nodes. 2. Click Cancel to go back to the previous screen.7.

6. 9. under the node SBM Cluster Configuration. Web Cluster In your SBM setup. click Clusters. which is the installation directory of SBM. or a Web cluster of Portal servers.Adding node 4. which should be unique. Figure 10 JMS Cluster.3.” in the node name to avoid any cluster start problems. We recommend that you do not use the character “. Click Cancel to go back to the previous screen. Enter the location of SBM Home. Specify Name for the node. To set up the Web cluster carry out the following steps: 1. Clustering Guide 24 Setting Up the Cluster . 5. Click Add to add the node to the JMS cluster. you can have either a single Portal server. 7. Click Save to save the configuration. Name the Target Node. click Add Node to display node information as shown in the following figure. In the left pane. Click Add & Continue to add more nodes. 8. In the Cluster panel. Specify the IP Address and JNDI Port on which the node listens.

7. HTTP Port and JNDI Port on which the node listens. Click Add to add the node to the Web cluster. Under the Clusters node. 6. Figure 12 Web Cluster. Click Cancel to go back to the previous screen. Specify the IP Address. In the Cluster panel. click Add Node to display node information as shown in the following figure. Figure 11 Setting Web Cluster 3.2. Clustering Guide 25 Setting Up the Cluster . We recommend that you do not use the character “. Specify Name for the node. Enter the location of SBM Home. which is the installation directory of SBM.Adding node 4. Click Add & Continue to add more nodes.” in the node name to avoid any cluster start problems. which should be unique. click Web to display the Web cluster setup as shown in the following figure. 5.

The names of the Standalone EJB and Portal servers must be ejbServer and 5. you can have either clusters of EJB/JMS/Portal servers. and jndi-port number. In the Server panel. and an additional JMS server should not be created.8. SBM validates that the EJB server and JMS server are identical in name. Note: For Pramati Web cluster. or standalone single servers. Figure 13 Setting Standalone Servers 3. In the left pane. Standalone Servers In your SBM setup.xml with the port numbers specified in the file sbm-cluster. Click Save to save the configuration. under the node SBM Cluster Configuration. to display its information as shown in the following figure. 4. NOTE: portalServer respectively. 1. Note: If a single EJB server is specified. Specify other information. Specify Name for the server. 2. For Pramati Web cluster vertical clustering is not supported. click the server you want to configure. address. click Standalone Servers. The following procedure describes the configuration of the standalone servers. you need to manually update the files <SBM_HOME>\pramati\server\nodes\portalServer\config\server-config. which should be unique. Click Save to save the configuration.xml and <SBM_HOME>\pramati\server\nodes\portalServer\config\qos-config. Clustering Guide 26 Setting Up the Cluster .xml. then it uses the embedded JMS server.

The proxy server is provided as a plugin by the application server vendor and is different for different Web servers. it is the proxy server that routes the request to one of the servers in the Web cluster. Figure 14 Setting Proxy Server 3. click Proxy Server to display its information as shown in the following figure. If you are using WebLogic as httpserver. 2. When a Web cluster is set up. then it already includes the plugin and the cluster setup utility configures the proxy server. 4. In case of WebSphere. Specify the IP Address and HTTP Port on which the server listens. For installation of plugin in Web servers. 1. Then. 5. Clustering Guide 27 Setting Up the Cluster . Specify Name for the server. which should be unique. In case of Pramati and WebLogic.Proxy Server A proxy server is required with a Web cluster. under the node SBM Cluster Configuration. Therefore the proxy server configuration is essential with the Web cluster. a new server instance is created. the IBM HTTP Server is used as a proxy server. Click Save to save the configuration. refer to the vendor specific documentation. The following procedure describes the configuration of the Proxy server. click Standalone Servers. A proxy server need not always be a new server instance. the external clients send their request to the proxy server. In the Server panel. In the left pane.

4. the Document server URL is the same as the URL of the single Portal server. Note: The document server is required in case of Web cluster. 5. The following procedure describes the configuration of the Document server. Clustering Guide 28 Setting Up the Cluster . under the node SBM Cluster Configuration.bat utility is run. which should be unique. Click Browse to search the location. For a single Portal server. In case of the Web cluster.conf when the modifyprop.Document Server The Document server in SBM that deals with the documents related to the Document dataslots also needs to be configured. Click Save to save the configuration. 1. 2.conf and designer. In the left pane. Specify the URL and the Document Location of the server. Specify Name for the server. The document location properties are also modified in the files sbm. Figure 15 Setting Document Server 3. the documents must be stored on a shared drive so that all nodes can access this location. click Document Server to display its information as shown in the following figure. In the Server panel. URL for the Document Server The URL for the Document server depends on whether a single Portal server has been configured or a Web cluster. click Standalone Servers.

you need not go through the remaining chapters of this guide. SBM validates if the Document server URL is same as the Proxy server URL and also if the document location is specified for the Document server.war\WEB-INF Running the Cluster Click the Run tab. If validation fails. The trace messages are displayed. when you see the cluster setup completed message.extdocserver to True in the file SBM_HOME\cluster\conf\sbmclusterprops. You can modify the SBM configuration files appropriately using the modifyprop utility. then the document server URL can be specified as the proxy server URL. Running modifyprop Utility Verify that SBM is installed on all machines.war\WEB-INF WEBSPHERE_HOME\AppServer\profiles\%PROFILE%\config\cells\%CELL%\applications\quick rules_war. Updating the JNDI Properties File After setting up the cluster. This file is located in the following directories • Pramati application server: SBM_HOME\pramati\server\nodes\portalServer\archives\public_html\quickrules-bui\WEB-INF • WebLogic application server: BEA_HOME\user_projects\domains\%SBMDOMAIN%\applications\quickrules-bui\WEB-INF • WebSphere application server: WEBSPHERE_HOME\AppServer\profiles\%PROFILE%\installedApps\%CELL%\quickrules_war. Refer to the section. and click Run Setup.For a Web cluster.log file. you need to manually update the property java. Modifying SBM Properties for individual application servers. you can exit the Cluster Configuration Tool.e ar\quickrules. After clicking Run Setup. Viewing the XML File Click the View XML tab to view the saved XML file.xml.properties with the EJB cluster URL. You can click Clear Messages to remove the trace messages.provider. refer to the <SBM_HOME>\cluster\logs\clustersetup. and the individual application servers are set up. This file needs to be updated in all the nodes of the portal cluster. Clustering Guide 29 Running the Cluster .cluster.url in the file JNDIProperties. The validation can be disabled by setting the system property sbm.ear\deployments\quickrules_war\quickrules. Note: Once you have set up cluster using the Cluster Tool.naming. if there is a drive controller in Windows using RAID controller or a shared drive on UNIX. an exception is thrown. This will provide failover.

1. 2. Start the application server node as required for the individual application server and verify that it is started properly. you need not stop the existing cluster. 1. For BizPulse.Adding New and Recovered Nodes In case of failure of any cluster node or addition of new nodes to the existing cluster. Editing and Deleting Nodes You can modify node configuration to accommodate system changes after the cluster configuration. Note that while reconfiguring. you will need to reconfigure the cluster and synchronize it with the cluster already running. run the command: addBizLogicNodes -u <user> -p <password> -nc <count> Where count is the number of new nodes to be added. 3. From SBM_HOME\bin. Click any node to display its configuration as shown in the following figure. Refer to Starting and Stopping BizPulse Monitoring on page 79 for related procedures. when you add a new node. This will synchronize the BizLogic server on the new node. Fix the problem on the crashed node and restart the machine. you need to start BizPulse monitoring on that node for failover. Note: BizPulse runs in a failover configuration and need not be re-synchronized. if it is a new node. Alternately. Figure 16 Editing Node Configuration Clustering Guide 30 Adding New and Recovered Nodes . Refer to the section. Modifying SBM Properties of the individual application server. 4. verify that SBM is installed on that machine. and the configuration files are appropriately modified using the modifyprop utility.

click Delete to remove the node from the cluster. Clustering Guide 31 Editing and Deleting Nodes . the cluster no longer exists.2. 5. 4. Make changes as necessary. Figure 17 Updating Node Configuration 3. In Figure 16. When the last node in a cluster is deleted. Click Update to save the changes. Click Cancel to go back to the previous screen. Click Edit to modify the contents as shown in the following figure.

refer to Configuring WebLogic Application Server on page 52. The remaining chapters of this guide describe procedures for individual application servers providing advanced information. and you may require to refer to them. Using this configuration file. refer to Configuring WebSphere Application Server on page 64. For clustering with WebSphere application servers. For environments that do not support graphics. we recommend you use the Cluster Configuration Tool for configuration as described in Using the Cluster Configuration Tool on page 18.Chapter 4 Editing the Cluster Configuration File The Cluster Configuration Tool works in environments that support graphics. The cluster configuration is specified in an XML file placed in SBM_HOME\cluster\conf. • Standalone EJB and Portal servers must not be running. For clustering with WebLogic application servers. For clustering with Pramati application servers. the default name sbm-cluster. you can specify the EJB cluster.xml to provide the cluster details.dtd. Web cluster. Clustering in SBM has the following common prerequisites: • Each node should have a static IP address. refer to Configuring Pramati Application Server on page 43.xml is used.xml while ensuring that the file conforms to sbm-cluster. 32 . If you are using an environment that supports graphics. you can manually edit the cluster configuration file sbm-cluster. If no custom file name is specified. JMS cluster. • Machines and port numbers must be selected after proper planning. or any combination of these. Note: You can specify a custom file name to the cluster configuration file other than sbm-cluster.

This tag is optional.xml are explained in the following sections. The protocol can be overridden for an individual <cluster> by defining it within the cluster. which is the absolute path of the directory under which your SBM is installed in WebLogic. For example. <domain-name> This is an optional tag for Pramati. in case of a Web cluster which uses HTTPS connection. For example. For example t3:// for WebLogic. This is a mandatory tag for WebLogic. the node attribute should have the name of the node. Attributes: • appserver: This is the name of the application server. In this tag. Specify the domain name with which SBM is installed under WebLogic in the file SBM_HOME\cluster\conf\sbm-cluster. Pramati. it will look as follows: <cluster name="WebCluster" type="web"> <protocol>https://</protocol> . Clustering Guide 33 Understanding the Tags . which is taken as the reference and all the other nodes’ time is synchronized with the reference node.. Note: The domain name is case sensitive. Along with the domain-name.. • appversion: This is the version of the application server.xml. <synchronize-time> A <cluster-configuration> has a <synchronize-time> tag that is required for synchronizing the time of all the node machines in the cluster.Understanding the Tags The different tags used in the configuration file sbm-cluster. you need to specify the location. General Tags The configuration file uses the following general tags. For example. <cluster-configuration> This is the main tag in the configuration file. <domain-name location="C:\bea\user_projects\domains\sbm50">sbm50 </domain-name> <protocol> A <cluster-configuration> has a protocol that is required to communicate to the application server and create the URLs for lookup.

JMS cluster and Web cluster types. Note: This tag is supported only for Windows and Solaris operating systems.0. one for EJB cluster. An Application cluster may include EJB cluster. for example.255. The user name and password should have administration rights. NOTE: Cluster name should not contain spaces or special characters that are not allowed by the underlying operating system. one for JMS cluster and one for Web cluster. It has a single attribute: • name: The unique name of the node. This is important if more than one application cluster runs in the same intranet. The <nodes> tag has as many <node> tags as the number of nodes in the cluster. The cluster requires a <multicast> tag for WebLogic that corresponds to the multicast address. • type: This is the type of cluster. Any exception during the synchronization of node time will be ignored and the cluster setup will continue. It has a port attribute that has the multicast port number. Attributes: • name: This is the unique name of the cluster.255. A multicast address is an IP address in the range from 224. It may be same as the host name. system/wlsysadmin can be used for WebLogic and root/pramati can be used for Pramati. Valid types are ejb. Clustering Guide 34 Understanding the Tags . <node> This represents a node in the cluster. <multicast> IP multicast is a simple broadcast technology that enables multiple applications to "subscribe" to a given IP address and port number and listen for messages. or different from the host name.The cluster nodes are synchronized with the target node time only during the cluster setup. <authentication> A <cluster-configuration> has an <authentication> tag that provides the user name and password to connect to the application server for the cluster setup.255.0. Any errors during synchronization are ignored and the cluster setup is continued. There could be only one cluster defined for a type. jms and web. Note: The multicast address or port should be different for each application cluster. Note that the utility does not log any errors outside its control. You can also use third-party tools for synchronizing time. Each cluster will have more than one node defined under the <nodes> tag. <cluster> A <cluster-configuration> can have multiple <cluster> tags corresponding to each cluster to be set up.0 to 239. For example.

For example. in case of WebLogic. This tag is valid for EJB. Normally the naming service runs on this port. different tags need to be defined. JMS and WEB nodes. This tag is valid for EJB.A node is characterized by the following: • <address>: This is the IP address of the node or its host name. Persistence is characterized by the following: • <url>: The database URL. two servers will be created with the name ejb1 and ejb2 for the following configuration: <cluster name="ejb_cluster" type="ejb" > <nodes> <node name="ejb1"> . . JMS Cluster Tags The JMS cluster can have either file store or the database store for persistence. Application servers such as Pramati also require persistence for all clusters. </node> </nodes> </cluster> Note: We recommend that you do not use the character “. WEB and PROXY server. Depending on the store.” in the node name to avoid any cluster start problems. . if one node of the JMS cluster goes down. In case of file store. Clustering Guide 35 Understanding the Tags . a <file-store> tag needs to be defined for each node in the JMS cluster. • <user>: Database user name. <persistence> This tag is used for the JMS cluster setup if the cluster uses database store. then the migration of messages has to be done manually. The cluster utility creates a server instance for each node with the server name as the node name. . • <jndi-port>: This is the JNDI port on which the node listens. . • <sbm-home>: This is the location where SBM is installed in the cluster nodes. </node> <node name="ejb2"> . This will have the absolute path of the file to be used as the store. <file-store> In case of file store. • <driver>: The fully qualified class name of the database driver. • <http-port>: This is the HTTP port on which the node listens.

if all the clusters (EJB. the JMS and EJB clusters might use different databases.protocol?. For application servers like Pramati. • <databasename>: Name of the database: for example.jmsserver?. Note: For a particular type (JMS/Web) there can either be a single server or a cluster. db2. and portalServer should be valid active server instances which should already exist before the cluster setup is started.cluster+. Order of Tags Ensure that the order of tags in the file sbm-cluster. • <connection-pool-name>: Name of the connection pool defined in the appserver.io.xml is the same as defined in the file sbm-cluster. But keeping the persistence with each cluster provides the flexibility to have a different database or the same database but different users for different clusters.authentication?. it should not conflict with any of the running servers’ ports in the cluster. required only for WebLogic JMS cluster database persistence. both single server and cluster for the same type cannot exist together. • <provider>: The database used: for example.synchronize-time?. In this scenario.dtd. <jndi-port>. For example. then while starting the cluster setup. ejbServer.IOException: IO error: The content of element type "cluster-configuration" must match "(domain-name?. however. that is. While using a single server. The port specified for proxyServer should be unique.documentserver?.proxyserver?. Single Server Tags You may have to set up an EJB cluster. db2. If the sequence is not the same as defined in the DTD file. and <http-port> for the IP address/host name and the port on which the server listens. you will get the following exception: java. oracle.multicas t?. the single servers can be defined in the configuration file as <jmsserver> and <portalserver> respectively for JMS and Portal single server.adminserver?.po rtalserver?. then similar persistence information needs to be replicated for each cluster. but not JMS cluster and Web cluster. The proxyServer is a server instance created by the cluster utility.deploy?)" Clustering Guide 36 Understanding the Tags . Both of them have a name attribute that is the unique name for the server. They also have the elements <address>.ejbserver?.• <password>: The password for the above user. Also note that jmsServer and documentServer are the logical references pointing to a valid active WebLogic server instance. JMS and Web) use the same database. the name of the server should be as follows: • For JMS server: jmsServer • For Portal server: portalServer • For Admin server: adminServer Note that adminServer.

adminserver?. or a cluster of EJB servers. SBM validates that the EJB server and JMS server are identical in name. and jndi-port number. jmsserver?. synchronize-time?. The name attribute holds the unique name of the EJB server. Single EJB Server Single EJB server is specified with the help of the <ejbserver> element. authentication?. then it uses the embedded JMS server. EJB Cluster For an EJB cluster. specify a <node> element under the <nodes> in <cluster>. documentserver?. • The type attribute of the <cluster> element should be "ejb". multicast?. you need to provide the following information: • The name attribute of <cluster> element should contain a unique name for the EJB cluster. Note: For any validation related to the EJB cluster. The IP address of the EJB node and the port on which it listens are specified with the <address> and <jndi-port> elements under the <node>. proxyserver?. Note: If a single EJB server is specified.xml. SBM refers to the attribute if-cluster-type in the file SBM_HOME\cluster\conf\sbm-properties. Note: If a single EJB server is specified.portalserver?. • The name attribute of the <node> will contain the unique name of the ejb node. • For each ejb node in the cluster. EJB Setup In your SBM setup. you can have either a single EJB server. The IP address and the port on which the server listens are specified with the help of the <address> and <jndi-port> elements under the <ejbserver>. address. then definitions of both the clusters should come at the top after the multicast element. and an additional JMS server should not be created. then an EJB cluster cannot be specified and vice versa. deploy?)> If you want to set up both EJB and JMS clusters. protocol?. Clustering Guide 37 Configuring the Cluster . cluster+. Configuring the Cluster This section lists information needed for different cluster setups.The order of the elements as defined in the DTD file is as follows: <!ELEMENT cluster-configuration (domain-name?. ejbserver?.

The tag <target-node> is required only for WebLogic JMS cluster. The IP address of the JMS server and the port on which it listens have to be specified with the <address> and <jndi-port> elements under the <node>. driver. • The type attribute of the <cluster> element should be "jms". then it uses the embedded JMS server. and jndi-port number. The name attribute holds the unique name of the JMS server. Clustering Guide 38 Configuring the Cluster . The IP address and the port on which the server listens are specified with the help of the <address> and <jndi-port> elements under the <jmsserver>. Note: If a single JMS server is specified. • The target of the JMS server specified under <target-node> should be any server instance. password and name of the connection pool such as SBMCommonDBPool. you can have either a single JMS server. • If database persistence is used.JMS Setup In your SBM setup. Note: If a single EJB server is specified. • If file persistence is used. • For each JMS server in the cluster. then a single <persistence> tag needs to be defined under the <cluster>. user name. then a <file-store> is to be specified under each <node> that will contain the absolute path to the file that is to be used as the store. • The name attribute of the <node> will contain the unique name of the JMS server. address. Single JMS Server Single JMS server is specified with the help of the <jmsserver> element. then a JMS cluster cannot be specified and vice versa. You need to provide the values for the provider. JMS Cluster Persistence The persistence properties are defined with the help of <persistence> element under the <cluster> element. url. and an additional JMS server should not be created. or a cluster of JMS servers. JMS Cluster For a JMS cluster. SBM validates that the EJB server and JMS server are identical in name. specify a <node> element under the <nodes> in <cluster>. you need to provide the following information: • The name attribute of <cluster> element should contain a unique name for the JMS cluster. • The store attribute of the <cluster> element should be "db" for database persistence or "file" for file persistence.

When a Web cluster is set up. Clustering Guide 39 Configuring the Cluster . The <documentserver> element has a name attribute that is the unique name of the document server. then a Web cluster cannot be specified and vice versa. The values for the <address> tag under <proxyserver> tag should be of the server where you installed the plugin. you need to provide the following information: • The name attribute of <cluster> element should hold a unique name for the Web cluster. In case of Pramati and WebLogic. This can be done with the help of the <documentserver> element under <cluster-configuration>. A proxy server is specified with the help of the <proxyserver> element. are specified with the help of the <address> and <http-port> elements under the <proxyserver>. the IBM HTTP Server is used as a proxy server. it is the proxy server that routes the request to one of the servers in the Web cluster. The proxy server is provided as a plugin by the appserver vendor and is different for different Web servers. • The name attribute of the <node> will contain the unique name of the Web server. Web Cluster For a Web cluster. refer to the vendor specific documentation. The name attribute holds the unique name of the Portal server. Document Server The Document server in SBM that deals with the documents related to the Document dataslots also needs to be configured in the configuration file. Single Portal Server A single Portal server is specified with the help of the <portalserver> element. In case of WebSphere. If you are using WebLogic as httpserver. or a Web cluster of Portal servers. the external clients have to send their request to the proxy server only.Portal Setup In your SBM setup. specify a <node> element under the <nodes> in <cluster>. The IP address of the Web server and the port on which it listens have to be specified with the <address> and <http-port> elements under the <node>. then it already includes the plugin and the cluster setup utility configures the proxy server. For installation of plugin in Web servers. • The type attribute of the <cluster> element should be "web". The IP address and the port on which the server listens. A proxy server need not be a new server instance. Note: If a single Portal server is specified. Therefore the proxy server is essential with the Web cluster. Then. a new server instance is created. The name attribute holds the unique name of the proxy server. Proxy Server A proxy server is required with a Web cluster. It consists of the elements: <doc-location> and <url>. you can have either a single Portal server. • For each Web server in the cluster. The IP address and the port on which the server listens are specified with the help of the <address> and <http-port> elements under the <portalserver>.

This will provide failover. then the document server URL can be specified as the proxy server URL. In this case.xml: • <cluster name="sbm_cluster" type="ejb" create="true"> • <adminserver name="wladmin"> • <documentserver name="docServer"> • <portalserver name="portalServer"> • <jmsserver name="sys97"> Clustering Guide 40 Setting the Cluster in Stages . The <doc-location> element specifies the exact location of the documents directory used for storing the document dataslot contents.The <documentserver> element is mandatory for the Web cluster. you must comment out the corresponding single server. For a Web cluster. SBM validates if the Document server URL is same as the Proxy server URL and also if the document location is specified for the Document server. When the cluster setup is run.bat | sh utility is run.xml.conf when the modifyprop.conf and designer. the cluster is set up only for those configurations for which the create attribute is set to true. That is. the <doc-location> element need not be specified. URL for the Document Server The URL for the Document server depends on whether a single Portal server has been configured or a Web cluster. EJB Cluster For an EJB cluster. Note: The element <documentserver> is required with the Web cluster. If validation fails. an exception is thrown. This can be achieved with the help of the create attribute for the <cluster> element. The validation can be disabled by setting the system property sbm. you can set up the EJB cluster first. This element is optional.cluster. the following tags should be included in the file sbm-cluster. and then the JMS cluster and/or the Web cluster. Note: While setting up a cluster. the Document server URL is the same as the URL of the single Portal server. The document location properties can also be modified in the files sbm. as the single server and the cluster cannot exist together. The documents must be stored on a shared drive so that all nodes can access this location. Setting the Cluster in Stages You can also carry out the cluster setup in stages. For a single Portal server.extdocserver to True in the file SBM_HOME\cluster\conf\sbmclusterprops. if there is a drive controller in Windows using RAID controller or a shared drive on UNIX.

JMS Cluster Once the EJB cluster setup is done. Note that while reconfiguring. verify that SBM is installed on that machine. Fix the problem on the crashed node and restart the machine. Cluster Setup Log File The file SBM_HOME\cluster\logs\clustersetup. Adding New and Recovered Nodes In case of failure of any cluster node or addition of new nodes to the existing cluster. the XML file should have the following tags for the Web cluster setup: • <cluster name="sbm_cluster" type="ejb" create="false"> • <cluster name="sbmjmscluster" type="jms" store="db/file" create="false"> • <cluster name="web_cluster" type="web" create="true"> • <adminserver name="wladmin"> • <documentserver name="docServer"> • <proxyserver name="proxy" type="pramati"> Running the Cluster Setup To start the Cluster Setup. Clustering Guide 41 Running the Cluster Setup . and the configuration files are appropriately modified using the modifyprop utility. and [-f clusterFile] denotes the application server-specific configuration file. Alternately. you will need to reconfigure the cluster and synchronize it with the cluster already running.log contains all the logged messages and exceptions during the setup. go to SBM_HOME\cluster\bin and run setupcluster. if it is a new node. Refer to the section. 1. you need not stop the existing cluster.bat|sh [-cmd] [-f clusterFile] where [-cmd] specifies that this is a command line operation. Modifying SBM Properties for individual application servers. the XML file should have the following tags for the JMS cluster setup: • <cluster name="sbm_cluster" type="ejb" create="false"> • <cluster name="sbmjmscluster" type="jms" store="db/file" create="true"> • <adminserver name="wladmin"> Web Cluster Once the EJB and JMS cluster setup is done.

xml For WebLogic Application Server.xml is read from the file system by default. then the cluster utility assumes that the files are already stored in the database. • Cluster configuration file sbm-cluster. • You can check in and check out the cluster files using the script SBM_HOME\cluster\bin\DBFileManager. • The file SBM_HOME\cluster\conf\sbmclusterprops. For BizPulse. Database Storage of Cluster Files The following files can be read from the database or from the file system. the file will be read from the database. • If the database storage is enabled. run the command: addBizLogicNodes -u <user> -p <password> -nc <count> Where count is the number of new nodes to be added. It contains the property propertyfilestorage which is used to specify if database storage is required. Refer to Starting and Stopping BizPulse Monitoring on page 79 for related procedures. sbm-resources-weblogic. 4. Clustering Guide 42 Database Storage of Cluster Files . These files are directly read from the database without checkout. the following files must be present in database: o o sbm-cluster. you need to start BizPulse monitoring on that node for failover.2. when you add a new node.xml specifies properties for the cluster utility itself. If the property propertyfilestorage is set to True. From SBM_HOME\bin. 3. Start the application server node and verify that it is started properly. NOTE: If the database file storage is enabled.xml must also be present in the database. Note: BizPulse runs in a failover configuration and need not be re-synchronized. This will synchronize the BizLogic server on the new node.xml sbm-properties.

Refer to Using BPM Studio in Clustered Environment on page 16 for more information. Make changes in the file sbm-cluster. to all the other nodes in the cluster.txt for quick reference. You need to copy them from the node where it got installed. You can avoid copying the files manually by using the BPM Studio. Before Clustering Before clustering.xml as described in the section Configuring Clusters on page 45.bat • Copy the file SBM_HOME\cluster\conf\sbm-cluster-pramati.xml.xml. If you plan to use the Cluster Configuration Tool instead. You can also use the file SBM_HOME\cluster\docs\readme_pramati. refer to the chapter Editing the Cluster Configuration File on page 32. ensure that: • Pramati Admin Service must be running on all intended nodes before starting the cluster setup. This can be done by running the following command: SBM_HOME\pramati\server\bin\runstartupsvc. it creates the application files on any one node in the cluster. When you install a BizLogic/BizSolo application in a clustered environment.xml to sbm-cluster. For basic reference information on manual cluster configuration.Chapter 5 Configuring Pramati Application Server This chapter describes the details of Pramati application server required for manual editing of the file sbm-cluster. refer to the chapter Using the Cluster Configuration Tool on page 18. Note: Portal cluster is not supported in vertical clustering using Pramati application server. This will be your cluster configuration file. 43 .

1. then you need to delete it manually before running the utility.129</address> <jndi-port>9295</jndi-port> <source-node>ejbServer</source-node> </node> Clustering Guide 44 Before Clustering . Copy the file SBM_HOME\cluster\conf\pramati-web-lbconfig.32. If such a table already exists. Modify the nodes section in this file with the Web cluster node information present in the file sbm-cluster.32. Modify the hostname attribute to the IP address of the load balancer as shown below: <node-choser name="url-mapping-node-choser" … <host name="10. then you need to delete it manually before running the utility.seconds="60000" socket-idle-timeout-millis="60000" /> </node> <node type="J2EE" host="10.1. b.xml as shown below: <nodes self-name="null"> <node type="J2EE" host="10. note the following points: • All EJB nodes should have the same port number. a.• For Web Clustering on UNIX. • Verify that the table with name of the EJB cluster does not already exist in the database specified in the persistence properties.118" web-port="8181" name="sys80WA"> <naming-port /> <socket-pool enabled="true" min="20" max="50" pool-idle-time-out. If such a table already exists.bat | sh before starting the cluster. if you choose port 9295. For example. a table by this name is already created in the database specified in the <persistence> section of this cluster.xml.129" web-port="8181" name="sys91WA"> <naming-port /> <socket-pool enabled="true" min="20" max="50" pool-idle-time-out. For example.129"> • On each node of the cluster. a table by this name is already created in the database specified in the <persistence> section of this cluster. if the cluster name is “sbmjmsCluster”. Using Ports While specifying the port numbers in the cluster configuration file. if the cluster name is “sbmejbCluster”.32. • Verify that the table with name of the JMS cluster does not already exist in the database specified in the persistence properties.xml as web-lbconfig. For example. then <cluster name="sbmejbCluster" type="ejb"> <nodes> <node name="sys91"> <address>10.32.1. run the utility SBM_HOME\bin\setupSBM.seconds="60000" socket-idle-timeout-millis="60000" /> </node> … c.1.

Configuring Clusters Note the following points: • The <source-node> tag is mandatory. "ejbServer" is the default node of an SBM standalone installation.1.32.) on the portal server nodes.bat | sh is being run. then proxy server should be created on the same node as the machine where the utility setupcluster. Specify the "ejbServer" node as source node.32. • In case of vertical clustering. <cluster name="sbmwebCluster" type="web" create="false"> <nodes> <node name="sys91WA"> <address>10.118</address> <jndi-port>9191</jndi-port> <http-port>8181</http-port> </node> </nodes> </cluster> The tag <jndi-port> needs to be specified for portal server nodes for query service to access the JNDI resources (JDBC. etc. This port will be different than <http-port> for Pramati server.129</address> <jndi-port>9191</jndi-port> <http-port>8181</http-port> </node> <node name="sys80WA"> <address>10. This tag is optional.32.1.<node name="sys74"> <address>10. sys91jms) must be different from any other node name.112</address> <jndi-port>9295</jndi-port> </node> </nodes> … The tag <http-port> can also be specified to access the HTTP port (if available) on this EJB node. • If the Web cluster option is used. • The standalone JMS server name (for example.then since Web cluster uses existing Portal servers. Clustering Guide 45 Configuring Clusters . the port numbers will be the port numbers of the individual port numbers of the Portal servers. This is used to set the required SBM configuration on the cluster nodes. For example.1. nodes are on the same machine. • All Web nodes should have the same port number. • The <persistence> tag is mandatory for EJB cluster. and port numbers need to be different. if you choose port 8181.

Since the Portal server nodes already exist. 6. When you set up the HA JMS using the Cluster Configuration Tool. 4. it enters the values for these tags. Set up the JMS cluster using the Cluster Configuration Tool as explained in the Chapter 3. Click the Run tab and click Run Setup to run the cluster. To set up the HA JMS with Pramati cluster. Clustering Guide 46 Setting Up the Cluster . one of the other passive nodes becomes active. Setting Up the Cluster To run the cluster setup: • Execute setupcluster. The <nodes> tag contains the list of nodes for the cluster. Similarly. Using the Cluster Configuration Tool. <address>. Locate the <persistent-store> tag. open the jms-config. Pramati creates a table with the same name as the cluster name and hence the cluster name must be unique. The value for the <http-port> tag must be different than the <http-port> of any nodes defined in the cluster with type "web". Setting up Web Cluster The Web cluster in the template XML assumes the usage of the existing Portal servers in a load-balancing mode. <jndi port> and <sbm home> tags. 3. From the machine on which the Cluster Configuration Tool is run. one of the JMS nodes is in active state and all other JMS nodes are in passive state. carry out the following steps: 1. The first <node> element must contain the <node name>. the create attribute is set to false. Change the <persistence-type> tag value from file-store to db-store. 5. refer to Pramati documentation for Pramati Web LoadBalancer. When the active JMS node fails. The first <node> element must contain the <source-node> tag. Setting up High Availability JMS Cluster When a High Availability (HA) JMS is set up with a Pramati Application Server. The node specified in this tag (ejbServer by default) must be present on the same machine as this node.xml file from <SBM_HOME>\pramati\server\nodes\<JMS_NODE_NAME>\config folder. Entry for the <proxyserver> tag must be present. add EJB and Portal nodes as desired. If required to install the proxy server in other webservers or servlet engines. 2. The <nodes> tag contains the list of JMS nodes for the cluster.bat|sh -cmd in SBM_HOME\cluster\bin on one of the cluster nodes.Setting up EJB Cluster The EJB cluster configuration is provided by default. The <persistence> tag will contain the database connection parameters used by Pramati to persist the EJB cluster configuration.

bat [-f clusterFileName] where clusterFileName is the name of the cluster configuration file to use. In case the cluster configuration file is other than sbm-cluster. To modify the SBM configuration files for the cluster configuration. To ensure that you always have the original files for restoration. then sbm-cluster.bat |sh file with the option -f with the configuration file name. SBM side configuration will have to be modified for the standalone server to run. Save this file. new nodes are created for the cluster in addition to the existing standalone node.bat is run multiple times. After this. you need to run the modifyprop.orig". Note: If the utility modifyprop.bat -node <JMS_NODE_NAME> -uploadconfig This will save the changes to the database.orig) will be overwritten.bat to update the SBM property files in the jar and ear files. It internally calls SBM_HOME\bin\updateSBM.orig extensions to the respective conf files.xml. 9. 10.bat to complete the restoration. and restoration of Pramati side configuration will not be required. modifyprop. Modifying SBM Properties Ensure that all nodes in the cluster have the same cluster configuration file. run SBM_HOME\cluster\bin\modifyprop. Continue with the rest of the cluster setup procedure explained in the following sections. From the machine on which the Cluster Configuration Tool is run.bat maintains a copy of the original files with the extension ". execute following command from <SBM_HOME>\pramati\server\bin folder: startJMSServer.xml. sbm-cluster. manually back up the conf directory before running the utility. However. Stop the JMS Server by using the shutdown command in JMS Cluster’s shell. the original files (. It is also possible to easily restore the original configuration because modifyprop. Clustering Guide 47 Modifying SBM Properties . 8.xml is used Restoring Original Configuration In case of Pramati.bat on each node in the cluster to update the properties in the SBM conf files for the cluster. This will back up the affected configuration files under SBM_HOME\conf directory by appending .7. run SBM_HOME\bin\updateSBM. If no file is specified. These files can be renamed to their original name.

the word "Monitoring" is used here almost synonymously as "Failover".Configuring BizPulse for Failover Some of the important parameters in bizpulse.cluster.cluster. BizPulse server starts up on any one of the nodes. On the node.cluster.interval=30 When BizPulse monitoring is “on”. make sure that you copy all the relevant applications.server. a monitoring process will start on each of the nodes. Note: You must first start the EJB Server on the node where the cluster utility was executed. • bizpulse.monitor.failover. and the process writes the last BizPulse alive time to the database. where the BizPulse server is active.server. This indicates that there are more than one nodes working in cluster mode. and then run the BizLogic / BizPulse servers. Ensure that the same copy of the applications exists on all the nodes and there is no version mismatch on different nodes.server.cluster.monitor. BizPulse Application Loading in a Cluster For application loading. otherwise the servers may hang or take more time to start. This parameter should be set to “on” to enable failover.interval=120 When the difference between the last BizPulse alive time and the current time exceeds the specified bizpulse. You can use either BizPulseAdmin or BPM Portal to load the applications.interval in seconds.monitor=on Failover is achieved by monitoring the active BizPulse server. Clustering Guide 48 Configuring BizPulse for Failover .interval.failover. the monitoring takes place every 30 seconds. On all the other nodes. monitoring process checks the state of the BizPulse at the interval specified by bizpulse.cluster. whenever BizPulse is started.server. • bizpulse. Therefore. and initiating the failover action in case the server fails. Ensure that you do not start the EJB Server simultaneously on all the cluster nodes. • bizpulse. the monitoring process will try to start the BizPulse server on a node other than the one on which BizPulse was last active. and their compiled rules on all the nodes in the cluster. monitoring process checks and compares the last BizPulse alive time with the current time.server.conf which affect BizPulse failover functionality are discussed below: • bizpulse. Working with the Cluster You need to first start the clusters and/or individual servers.cluster=on This parameter should be set to “on”. In this particular example.server.

start it with the command: startEJBServer Starting the Servers You can start the BizLogic and BizPulse servers through the Administration module of BPM Portal. If the EJB cluster is not set up. then start with the command: startBizLogicServer Clustering Guide 49 Working with the Cluster . If the EJB cluster is not set up.bat|sh [nodename] You must run the command for each node. then start with the command startBizLogicServer -u <user name> -p <password> -nc <nodes in cluster> 2.bat|sh. Start the Portal servers in the cluster with the command: the SBM_HOME\pramati\server\bin\startPortalServer. If the EJB cluster is set up. and there is a single EJB server. If the Web cluster is set up. 4. start the Portal server with the command: SBM_HOME\pramati\server\bin\startPortalServer. NOTE: You need to run this command on all the nodes individually. start the EJB servers of the cluster with the command: SBM_HOME\pramati\server\bin\startEjbServer. a. Always start JMS server / cluster before starting EJB server / cluster. If the Web cluster is not set up. If the EJB cluster is set up. Note: You need to run this command on all the nodes individually. 2. and there is a single EJB server. and there is a single Portal server.bat|sh <JmsServer> In this example.Starting the Cluster 1. Start the Portal proxy server with the command: SBM_HOME\pramati\server\bin\startPortalServer. the proxy server name is “proxyserver”. <proxyserver> In this example. In this example.bat|sh. The following sections describe how to start the BizLogic and BizPulse servers through the command line. the JmsServer name is “sys91jms”. Start the JMS server with the command: SBM_HOME\pramati\server\bin\startJMSServer. b. 3. the nodename is “sys91” and “sys74”. Starting the BizLogic Server Go to SBM_HOME\bin and start the BizLogic servers a follows: 1.bat|sh. 5.

web-config. then start with the command startBizPulseServer -nodes <nodes in cluster> 2. by using the shutdown command for individual servers.prod under SBM_HOME\pramati\server\nodes\portalServer\config. For each of the backend nodes in SBM_HOME\pramati\server\nodes\portalServer\config\web-config. Note: Once the update-check-interval-seconds value is set to -1. The web-config. there are two copies of web-config.xml. Starting the BizPulse Server Go to SBM_HOME\bin and start the BizPulse server as follows: 1. This ensures that the socket connections between the Loadbalancer and the backend nodes does not get timed out for a long period of time. The values of keep-alive-timeout (millis) and socket-idle-time-out (millis) should be changed to a high value in the web-config.dev and web-config. then start with the command startBizPulseServer For more information on BizPulse server commands. If you want to deploy new JSPs or need the server to recompile modified JSPs.xml. Performance Tuning To improve the performance. the Portal server will no longer compile JSPs. In the out-of-the-box installation. This disables the check the server performs for changes in JSP files. <idle-timeout-millis>10000</idle-timeout-millis> <keepalive-timeout-millis>30001</keepalive-timeout-millis> Clustering Guide 50 Performance Tuning . namely. refer to BizPulse Server Commands on page 78.xml.xml and restart the server. the update-check-interval-seconds value should be a positive value. If the EJB Cluster is not set up. If the EJB Cluster is set up. and frequent creation of sockets. and hence does not result in unnecessary. 2. Stopping the Cluster You need to stop the cluster in the exact reverse order of starting the cluster as described in Starting the Cluster on page 49. rename this file to web-config.xml.xml of the backend nodes. you can carry out the following tuning: 1. In the production environment. refer to BizLogic Server Commands on page 76.xml change the idle-timeout-millis to 10000.prod file is tuned for a production environment with the update-check-interval-seconds value set to -1. and there is a single EJB server. (preferably to more than five minutes for keep-alive-timeout and 10-60 seconds for idle-timeout).For more information on BizLogic server commands.

a.SessionStickinessNodeChoo ser" enabled="true"> <props time-out-minutes="6" cleanup-interval-minutes="2" /> </node-chooser> to <node-chooser name="session-stickiness-node-chooser" class="com.xml.SessionStickinessNodeChoo ser" enabled="true"> <props time-out-minutes="45" cleanup-interval-minutes="2" /> </node-chooser> Note: The sample values used in this example should be changed to the appropriate values in your system.lb. For example. thereby improving performance. in SBM_HOME\pramati\server\nodes\proxy\config\web-lbconfig.savvion. The proxyServer\loadbalancer node is configured for a session timeout of 6 min by default.web.web.savvion.nodechooser.pramati. This can be done by setting the “denial-of-service enabled” to false. It is okay to turn off the DOS (Denial of Service attack) protection on the backend nodes in a cluster. Since the DOS protection is turned on in the proxyServer/loadbalancer by default. Clustering Guide 51 Performance Tuning . <node type="J2EE" host="jerusalem. make sure that the socket-idle-timeout-millis="10000" for both the nodes.3. For the proxy node.pramati. This can be updated to a desirable value by modifying the code as follows: <node-chooser name="session-stickiness-node-chooser" class="com.nodechooser. in the nodes section.com" web-port="8181" name="web_kuba"> <naming-port /> <socket-pool enabled="true" min="20" max="50" pool-idle-time-out-seconds="1000" socket-idle-timeout-millis="10000"/> </node> b. turning it off in the backend nodes will avoid DOS attack checks from happening twice (in the loadbalancer and the backend node).com" web-port="8181" name="web_jerusalem"> <naming-port /> <socket-pool enabled="true" min="20" max="50" pool-idle-time-out-seconds="1000" socket-idle-timeout-millis="10000" /> </node> <node type="J2EE" host="kuba.lb.

it creates the application files on any one node in the cluster. You need to copy them from the node where it got installed.1. C:\bea\user_projects\domains\sbm50. Clustering in SBM uses the following terminology: • SBM_HOME: Refers to the installation directory of SBM. for WebLogic 8. You can avoid copying the files manually by using the BPM Studio. If you plan to use the Cluster Configuration Tool instead. to all the other nodes in the cluster.txt for quick reference. Refer to Using BPM Studio in Clustered Environment on page 16 for more information. You can also use the file SBM_HOME\cluster\docs\readme_weblogic. refer to the chapter Editing the Cluster Configuration File on page 32.xml. • WL_HOME: Refers to the WebLogic installation directory • WL_SBM_DOMAIN: Refers to the absolute location where SBM is installed under WebLogic. For basic reference information on manual cluster configuration. Note: When you install a BizLogic/BizSolo application in a clustered environment. refer to the chapter Using the Cluster Configuration Tool on page 18.Chapter 6 Configuring WebLogic Application Server This chapter describes the details of WebLogic application server required for manual editing of the file sbm-cluster. 52 . For example.

log files WL_SBM_DOMAIN\adminServer\*. You are required to use the same directory for each node.32.tlog files The jar and ear files included with default installation must not be clustered.129 and EJB nodes are 10. run the utility SBM_HOME\bin\setupSBM.1.168. ensure that: • If a single JMS server is configured for the cluster. and the same WebLogic domain name for each node.32.wlnotdelete WL_SBM_DOMAIN\adminServer\ldap WL_SBM_DOMAIN\adminServer\logs WL_SBM_DOMAIN\adminServer\*.32</address> <jndi-port>18785</jndi-port> Clustering Guide 53 Before Clustering . For more information. • Make sure that the Admin Server is running on one of the machines in the cluster before starting the cluster setup. For example.168.32. see the Installation Guide.129 and 10. then the JMS server should always be targeted on 10.bat |sh.1.Before Clustering Before clustering. then <cluster name="sbmejbCluster" type="ejb"> <nodes> <node name="sys97"> <address>192.32. then this server should be targeted to the EJB server that is at the same location as the Administration server. • On each node in the cluster.179.28</address> <jndi-port>18785</jndi-port> </node> <node name="sys98"> <address>192.xml.1. • Copy the file SBM_HOME\cluster\conf\sbm-cluster-weblogic. For example. note the following points: • All EJB nodes should have the same port number.0. Make changes in the file sbm-cluster. • Remove the following temporary files and directories: • • • • • • Note: WL_SBM_DOMAIN\adminServer\.xml as per the cluster configuration. if the Administration server is at node1 IP=10. Using Ports While specifying the port numbers in the cluster configuration file. if you choose 18785.129.xml as sbm-cluster. and all nodes should use the same database account. This will be your cluster configuration file.0.internal WL_SBM_DOMAIN\adminServer\. • Ensure that SBM is installed on all nodes before proceeding.1. • Each node should be installed on a separate machine.

<cluster name="sbmwebCluster" type="web"> <nodes> <node name="sys97_web"> <address>192. For example. For example. 18785. • All JMS nodes should have the same port number as EJB nodes.0.28</address> <http-port>18795</http-port> </node> <node name="sys98_web"> <address>192. Clustering Guide 54 Before Clustering .) on the portal server nodes. etc. and hence can be omitted. <cluster name="sbmjmsCluster" type="jms" store="db"> <nodes> <node name="sys97_jms"> <address>192. This port is the same as the <http-port> for WebLogic server.168. then since the Web cluster uses existing Portal servers.168.32</address> <http-port>18795</http-port> </node> </nodes> </cluster> The tag <jndi-port> can be specified for portal server nodes for query service to access the JNDI resources (JDBC. if you choose 18795.0.32</address> <jndi-port>18785</jndi-port> <target-node>sys98</target-node> </node> </nodes> … NOTE: The tag <http-port> is not valid for JMS server or JMS cluster nodes.168. the IP address and target of JMS nodes should be the same as the IP address and node name of the corresponding EJB nodes respectively. • All Web nodes should have the same port number.</node> </nodes> </cluster> The tag <http-port> can also be specified after <jndi-port> tag to access the HTTP port (if available) on this EJB node. Also.28</address> <jndi-port>18785</jndi-port> <target-node>sys97</target-node> </node> <node name="sys98_jms"> <address>192. This tag is optional.168. the port numbers will be the port numbers of the individual port numbers of the Portal servers.0.0.

<node name="sys113"> <address>10. Configuring Clusters Note the following points: • The <domain-name> tag is mandatory for WebLogic. We recommend to install WebLogic in the same location on all the machines in the cluster.• You must use the same port number specified while installing SBM. <adminserver name="adminServer"> <address>192.xml manually as described below: • If SBM is installed in different directories on different nodes during the cluster setup with WebLogic.172</address> <jndi-port>18785</jndi-port> <sbm-home>D:/SBM_HOME</sbm-home> </node> Where.ear from \u4\bea\user_projects\domains\SBM\applications\bizlogic.1. Specify the absolute path of the directory under which SBM is installed in WebLogic. then the file config.\applications\bizlogic. change the path of the file bizlogic. You need to make the paths relative to the domain directory. For example. In case WebLogic is installed at different locations. The domain name is case sensitive. Specify the domain name with which SBM is installed under WebLogic in the file SBM_HOME\cluster\conf\sbm-cluster.0. <domain-name location= "C:/bea/user_projects/domains/sbm50">sbm50 </domain-name> • The adminSever and proxyServer name must not be changed. (nodes on same machine). For example.28</address> <jndi-port>18791</jndi-port> </adminserver> … • In case of vertical clustering. For example. port numbers need to be different. then the property sbm-home needs to be added for all the nodes in the file sbm-cluster.ear • If SBM is installed in different locations on the cluster nodes. and then edit the file as follows: The paths of the applications in the file config. sbm-home is the location of SBM installation on that specific node.xml on the Admin server needs to be changed manually. then shut down the Admin sever.32. Clustering Guide 55 Configuring Clusters . you need to modify the file config. and a single JMS server is to be configured. • The location attribute is mandatory for WebLogic.168.xml.xml.xml are absolute by default. You need to first run the cluster setup utility. 18791.ear to .

the target-node of the JMS server will not be validated.28</address> <jndi-port>18792</jndi-port> <target-node>ejbServer</target-node> </node> Clustering Guide 56 Configuring Clusters .168.0.sbm.cluster.cluster. Specifying Environment Variables You can specify whether the JMS server is an external server or not by using the environment variable sbm.extjmsserver. Setting up JMS Cluster The JMS servers can be configured in two ways. if the SBM_HOME property is different for at least one node.168. <ejbserver name="ejbServer"> <address>192.0. indicating that the JMS server is not an external server and its target should be either the name of the EJB Server (single server) or the name of any of the nodes of the EJB Cluster (cluster). Similarly. this property is ignored.savvion. then the value of the <target-node> should be the name of the EJB Server with which you want to cluster the JMS Servers. either with a standalone EJB Server or with an EJB Cluster. the JMS store for a standalone installation is a file on the local file system. Hence a JDBC store is set as the JMS store to avoid this problem. the address and port of the JMS Servers should be the same as that of the EJB Server. For example. In such a case.weblogic. JMS Cluster with Standalone EJB Server If you configure the JMS Servers with a standalone EJB Server. The value true indicates that the JMS server is an external server.extjmsserver=false com. You can change its value in the file SBM_HOME\cluster\bin\setupcluster.• In case of a single JMS server. The JMS server (and hence the EJB node) will not start in such case. By default. then the file store path of an assigned JMS server may not be valid on all the machines.32</address> <jndi-port>18792</jndi-port> <target-node>ejbServer</target-node> </node> <node name="jmsNode2"> <address>192. then the utility sets a pre-configured JDBC store (BizLogic_JDBC_Store.32</address> <jndi-port>18792</jndi-port> <ejbserver> <cluster name="sbmjmscluster" type="jms" store="db"> <nodes> <node name="jmsNode1"> <address>192. If SBM is installed in different locations on different nodes.168.0. BizPulse_JDBC_Store) for BizLogic and BizPulse.ClusterSetup The default value is false.bat|sh in the following command: java -Dsbm. In case of JMS cluster.

If you want to choose a different proxyServer name (for example. . The name of the JMS Servers in the JMS Cluster should not exceed 16 characters. Similarly. </cluster> Setting up Web Cluster Entry for <proxyserver> should be made in the file SBM_HOME\cluster\conf\sbm-cluster. change the value of portal proxy server port when the web cluster setup is done. .168.28</address> <jndi-port>9000</jndi-port> </node> <node name="sys98"> <address>192. sys55_proxyServer).</nodes> .0. </cluster> JMS Cluster with EJB Cluster If you configure the JMS Servers with an EJB Cluster.168. then the value of <target-node> should be set to the EJB Cluster node names. Clustering Guide 57 Configuring Clusters .cmd|sh file in the WL_SBM_DOMAIN folder.32</address> <jndi-port>9001</jndi-port> <target-node>sys98</target-node> </node> </nodes> . then you must change the proxyServer name in the startPortalProxyServer. An example of this is given below: <cluster name="ejb_cluster" type="ejb"> <nodes> <node name="sys97"> <address>192. .0.28</address> <jndi-port>9000</jndi-port> <target-node>sys97</target-node> </node> <node name="jmsNode2"> <address>192.168. In the file WL_SBM_DOMAIN\ stopPortalProxyServer.168. . the address and port of the JMS servers in the JMS Cluster should be the same as that of the EJB Servers in the EJB Cluster.0. The value for the <http-port> tag must be different than the <http-port> of any nodes defined in the cluster with type "web".xml.32</address> <jndi-port>9001</jndi-port> </node> </nodes> </cluster> <cluster name="sbmjmscluster" type="jms" store="db"> <nodes> <node name="jmsNode1"> <address>192.0.cmd | sh.

xml and provide the value for the location attribute of <property-files> element to point to the location of the conf directory of the SBM_HOME.war is uploaded by the cluster utility in the upload folder of the WL_SBM_DOMAIN\adminServer folder. This can be seen under the SBM_HOME\cluster\webapps folder. then the cluster setup remains incomplete.bat on each node in the cluster to update the properties in the SBM conf files for the cluster. then the property files are located from the CLASSPATH. Refer to the WebLogic documentation for downloading. then it is required to download and install the WebLogic plugins. and any application server specific resource files like sbm-resources-weblogic. the utility does not get any exception from the server and continues to show that the setup is okay. Run SBM_HOME\cluster\bin\setupcluster. 2. Setting Up the Cluster To run the cluster setup: 1.cmd|sh. check the application server log file WL_SBM_DOMAIN\adminServer\logs\adminServer. Clustering Guide 58 Setting Up the Cluster . It internally calls SBM_HOME\bin\updateSBM. After the setup is completed.xml file. After the setup is complete. To modify the SBM configuration files for the cluster configuration. run SBM_HOME\cluster\bin\modifyprop. In some cases.bat to update the SBM property files in the jar and ear files. Note: The cluster utility must be run from the same machine on which the WebLogic Server is installed.xml. you need to shut down the Admin server and then restart it. This will back up the affected configuration files under SBM_HOME\conf directory by appending .bat|sh.xml. So. Ensure that the AdminServer is running on one node. • Open the file SBM_HOME\cluster\conf\sbm-properties. installing and configuring the proxy server for IIS and Netscape’s iPlanet. Modifying SBM Properties Before modifying the properties. Note: If this value is not specified or specified incorrectly. ensure the following: • All the nodes of the cluster have identical files sbm-cluster. then properties of the incorrect SBM installation will be updated. If not. if some other SBM_HOME than the one on which the cluster setup is done. is in the CLASSPATH. an application with name WLProxyApp. you can start the AdminServer by running WL_SBM_DOMAIN\startAdminServer. This may happen for various reasons such as an incorrect domain name. Note: If you need to install a proxy server in other webservers/servlet engines.orig extensions to the respective conf files. If the server does not start properly. and results in a corrupted config.While the Portal server is made clusterable.log for any errors in setup. sbm-properties.xml.

since every time the file is backed up with a unique name.xml should be replaced with the requisite backup copy.conf affect BizPulse failover functionality significantly. Clustering Guide 59 Configuring BizPulse for Failover .In case the cluster configuration file is other than sbm-cluster. the cluster utility creates a backup of your original file config. modifyprop. make sure that you copy all the relevant applications. even after multiple runs of the cluster setup utility. Note: WebLogic JMS cluster assumes that the server clocks of all the nodes in the cluster need to be synchronized at all times. refer to Configuring BizPulse for Failover on page 48. then sbm-cluster. you need to run the modifyprop. Irrespective of whether the setup was completed successfully or not.xml. You can use either BizPulseAdmin. and their compiled rules on all the nodes in the cluster. the file config.xml is used Restoring Original Configuration For WebLogic.orig extensions. This will enable users to retain the original configuration file and also the subsequent ones.xml. Rename the backed up configuration files from the SBM_HOME\conf directory by removing the . before restoring the file config. do the following: • Shut down the Admin server if it is running. or BPM Portal to load the applications. Consult your system administrator for a time management program to handle this. the existing file config. BizPulse Application Loading in a Cluster For application loading.xml. • Remove the temporary files as mentioned in Before Clustering on page 53. The above method can also be used to restore the configuration if any exception is encountered in the cluster setup or the cluster setup process is aborted.bat [-f clusterFileName] where clusterFileName is the name of the cluster configuration file to use. For more information about these parameters.<n1> where n1 is the least value.xml. Ensure that the same copy of the applications exists on all the nodes and there is no version mismatch on different nodes.xml. Configuring BizPulse for Failover Some parameters in bizpulse.xml.bat |sh file with the option -f with the configuration file name. will give the original file config.<number>. For example. If no file is specified. The backup file is created as config. To restore the original configuration. where the <number> is the current time in long number format.

startEjbClusterInstance sys97 192.0. If EJB cluster is not set up. If the Web Cluster is not set up. Start the Admin server with the command: startAdminServer 2.bat | sh from the SBM_HOME\bin directory. and <admin url> is the URL of the AdminServer specified in the cluster configuration. and then run the BizLogic / BizPulse servers. a.0. start it with the following command: startEjbServer 4.168. startPortalClusterInstance sys97_web 192. For example. Clustering Guide 60 Working with the Cluster . use startBizLogicNodes. start the EJB Servers of the clusters with the following command: startEjbClusterInstance <server name> <admin url> where <server name> is the EJB node name. refer to BizLogic Server Commands on page 76. go to WL_SBM_DOMAIN: 1. If the Web Cluster is set up.28:18791 5. and there is a single EJB server.28:18791 3. and there is a single Portal server. and <admin url> is the URL of the AdminServer specified in the cluster configuration. NOTE: To start BizLogic server on all nodes. then start with the command: startBizLogicServer For more information on BizLogic server commands. go to SBM_HOME\bin. and there is a single EJB Server. Starting the Cluster To start the cluster. then start with the command startBizLogicServer -u <user name> -p <password> -nc <nodes in cluster> b. If the EJB cluster is not set up. To start the BizLogic server. Start the Portal proxy server with the following command: startPortalProxyServer Start the Portal servers in the cluster with the command startPortalClusterInstance <server name> <admin url> where <server name> is the Portal node name. For example. start the Portal server with the following command: startPortalServer 6. If EJB cluster is set up.168.Working with the Cluster You need to first start the clusters and/or individual servers. If the EJB cluster is set up.

For stopping the EJB. stopBizLogicServer [options] [-u [username]] [-p [password]] [-nc [count]] For more information on BizLogic server commands. refer to BizPulse Server Commands on page 78. stopEjbClusterInstance <server name> <admin url> Clustering Guide 61 Working with the Cluster . stopPortalClusterInstance <server name> <admin url> where <server name> is the Portal node name. Note: BizLogic and BizPulse servers can also be started using BPM Portal. and there is a single EJB server. To stop the BizPulse server. Portal. stop the EJB cluster instance on each node. stopPortalProxyServer 5. stop the server with the following command: stopPortalServer 6. go to SBM_HOME\bin.bat -nodes <nodes in cluster> For more information on BizPulse server commands. 3. To stop the BizLogic server. then start with the command startBizPulseServer For more information on BizPulse server commands. and <admin url> is the URL of the AdminServer specified in the cluster configuration. stopBizPulseServer. go to WL_SBM_DOMAIN.0. To start the BizPulse server. In case of a Web cluster. Stop the cluster instances on each node. 4. go to SBM_HOME\bin.168.28:18791 Stop the Portal proxy server. refer to BizPulse Server Commands on page 78. Stopping the Cluster You need to stop the cluster in the exact reverse order of starting the cluster as described in Starting the Cluster on page 60. In case of an EJB cluster. stopPortalClusterInstance sys97_web 192. and Admin servers. In case of a single Portal server. If the EJB Cluster is set up. 2.7. To stop the cluster: 1. refer to BizLogic Server Commands on page 76. go to SBM_HOME\bin. a. For example. then start with the command startBizPulseServer -nodes <nodes in cluster> b. If the EJB Cluster is not set up.

If node1 fails. implement the remigration from node2 to node1 by using the following command: migrateJMS node1 node1 restorenode Note that the repetition of node1 is correct. stopEjbClusterInstance sys97 192.28:18791 7. stopAdminServer Note: BizLogic and BizPulse servers can also be stopped using BPM Portal.where <server name> is the EJB node name.168. For example. you can carry out the following tuning: Set the value of PageCheckSeconds and <servlet-reload-check-secs> to -1 in the weblogic. You can use WL_SBM_DOMAIN\migrateJMS. Once the remigration succeeds.0. When node1 is repaired and ready to be used. Stop the Admin server. Performance Tuning To improve the performance. and that restorenode is case sensitive.bat| sh is set to the correct URL of the cluster. migrateJMS node1 node2 migratenode In this example. and <admin url> is the URL of the AdminServer specified in the cluster configuration. node1 can be restarted using the startClusterInstance scripts.xml file (This procedure makes sure that WebLogic does not check for JSP changes which takes considerable time on Solaris operating system). see BizLogic Server Commands on page 76 and BizPulse Server Commands on page 78. For more information on how to start the BizLogic and BizPulse server in a recovered WebLogic instance that is a node in a cluster. node1 is the source node and node2 is the target node.xml file is located under bea_home\user_projects\domains\sbm_domain\applications\sbm\WEB-INF Clustering Guide 62 JMS Migration in a JMS Cluster . the JMS server needs to be manually migrated to the other node for failover. Make sure that the ADMIN_URL of the migrateJMS. This will migrate the JMS server from node1 to node2 and provide failover. The weblogic. then the batch file can be invoked as: migrateJMS node1 node2 Or.bat| sh script file to migrate the JMS server. stop the server with the following command: stopEjbServer 8. JMS Migration in a JMS Cluster When one node of the JMS cluster fails. In case of a single EJB server. Consider two nodes node1 and node2 in the cluster (EJB cluster + JMS cluster).

dev and weblogic. weblogic.xml.xml. The original copy of weblogic.prod. Rename the file to weblogic.xml. The weblogic. namely. click on descriptors -> weblogic. In the right pane. Login to Admin console and on the left pane go to deployments -> Web Application Modules -> sbm.xml. 1. under bea_home\user_projects\domain\sbm_domain\applications\sbm\WEB-INF.prod file already has the PageCheckSeconds and <servlet-reload-check-secs> values set to -1.xml Clustering Guide 63 Performance Tuning .xml is the same as weblogic.The out-of-the-box installation comes with two versions of WebLogic.xml and restart the Portal server instance. 2.xml. You can also check the parameter values through the admin console.dev and is tuned for the development environment.

2. For basic reference information on manual cluster configuration. D:\WebSphere\DeploymentManager. If you plan to use the Cluster Tool instead.Chapter 7 Configuring WebSphere Application Server This chapter describes the details of WebSphere application server required for manual editing of the file sbm-cluster. For example.txt for quick reference. • PROFILE: The profile defines the run-time environment and includes all of the files that the ‘server processes’ in the run-time environment can change. Refer to SOAP_CONNECTOR_ADDRESS::port parameter value in serverindex.5 is installed. refer to the chapter Editing the Cluster Configuration File on page 32. You can also use the file SBM_HOME\cluster\docs\readme_websphere. Clustering in SBM uses the following terminology: • SBM_HOME: Refers to the installation directory of SBM. • CONNTYPE: This determines what connector WebSphere uses. • ADMINSERVER_HOME: The location where Deployment Manager is installed. A profile in WebSphere is similar to a domain in WebLogic. The valid values are RMI and SOAP. Currently the value given for "-startingPort" is 4000. The default is SOAP. The default SOAP port for a cell manager is 8879. This may change based on the value provided for the parameter "-startingPort" during creation of the Deployment Manager profile.0. • PORT: This is the port used when for connecting to wsadmin. refer to the chapter Using the Cluster Configuration Tool on page 18. This is the physical path where the WASND 6. This may change if you have both WebSphere base and WebSphere ND installed in the same machine providing the co-exist option.xml at WebSphere_Install_root\AppServer\profiles\dmgr\config\cells\sys90Cell\nodes\sys90Manager.xml. 64 .

You can avoid copying the files manually by using the BPM Studio. If an SBM cluster has to be setup. to all the other nodes in the cluster. refer WebSphere documentation. it creates the application files on any one node in the cluster. and sys90. then WAS ND is needs to be installed. Refer toWorking with Two-Node Clusters on page 74. This version of Websphere ND also supports creation of WAS Base type of profiles to be created on it. Therefore. Figure 18 WebSphere . But for installing SBM.1). This installation creates a default profile with a server "server1". sys114. you need to create a deployment manager profile.Three-node Cluster It is also possible to set up cluster with only two nodes. for standalone SBM to be installed. From version WAS ND 6. Refer to Using BPM Studio in Clustered Environment on page 16 for more information.0 onwards. In the previous version (WAS ND 5. and understanding WebSphere terminology. installing WebSphere ND used to create a Deployment Manager. WAS Base needs to be installed. Before Clustering This example refers to a cluster setup of three machines. Clustering Guide 65 Before Clustering .• WEBSPHERE BASE: Websphere Application Server Base (WAS Base) is used in the case of standalone applications. sys76. Note: When you install a BizLogic/BizSolo application in a clustered environment. once Websphere ND is installed. we need to create a new profile on which the SBM applications can be deployed. For additional information. The following figure illustrates the architecture of the cluster. • WEBSPHERE ND: Websphere application server Network Deployment (WAS ND) is used in the case of WebSphere clusters. You need to copy them from the node where it got installed.

2.bat/sh and createSbmPortalServer.5 SP2 on sys114.0.2.net. c.ibm. The messaging engine folder name follows the following convention: <nodeName>.xml as per the cluster configuration. Execute createprofile. These folders are created in the APPSERVER_HOME\AppServer\profiles\<profileName>\databases\com. (Do not execute the scripts createSbmEjbServer. and not from the machine where Deployment Manager is installed. Make changes in the file sbm-cluster. e.client. Install WebSphere 6. cell name.2. Federate both the nodes.props file in the WEBSPHERE_HOME\appserver\profiles\<profile_name>\properties directory to avoid the java. Please note that each time the cluster is removed and re. and the node name must be unique on all the three nodes.installed. d. required for the management of the cluster.SocketTimeoutException: Read timed out exception. Note: For the ejb and web cluster. h.0. j.0. k. that is. • Copy the file SBM_HOME\cluster\conf\sbm-cluster-was. The cluster scripts should be run from any of the cluster nodes.bat/sh from the SBM_HOME\cluster\bin folder on sys90.<clusterMemberName>-<busName>. Install WebSphere 6.requestTimeout property from 180 to 0 in the soap. This will be your cluster configuration file. This would create the Deployment Manager profile. Install IBM HTTP Server 6. This has to be done in all the cluster member machines. sys114 and sys76 to the Deployment Manager. Change the value of the com. sys90.• Before proceeding to clustering.) g. that is.SOAP. that is. ensure that the database name specified in the "<databasename>" tag under the "presistance" tag is valid. f.sib folder. b. Install Web server plugins.bat/sh from the SBM_HOME\bin folder on sys76 and sys114.ibm. i.5 Standard Edition on sys76 and on sys114. Execute createadminprofile.0. Clustering Guide 66 Before Clustering . When the cluster is started for the first time after setup. (part of WebSphere 6. the messaging engine folder which is created inside the above-mentioned folder has to be removed. the messaging engine creates folders in each of the nodes where the cluster members are running.5 Standard Edition). Install SBM 6.xml as sbm-cluster. carry out the following steps: a. sys76 or sys114.xml. Please note that the profile name.0 on sys90 (part of WebSphere 6. sys90.5 Network Deployment on sys90. that is.5 Standard Edition).2.bat/sh.ws. sys76 and sys90. Currently the cluster setup is configured to use the cloudscape database.

You can find this node name from the sbm.websphere.tdiinc. For example.32. which is hosting the jmsserver.name parameter in the SBM_HOME\conf\sbmjndi. if the EJB cluster is described as below: <cluster name="sbmejbCluster" type="ejb" create="true"> <nodes> <node name="sys114sbm65node"> <address>sys114.node.properties file.tdiinc. Also all the EJB cluster nodes have the same <jndi-port> number. </persistence> </cluster> then. • All the Web cluster nodes should have the same <http-port> value. The <http-port> of cluster nodes of the Web cluster should be same as the <http-port> of the proxyserver. This tag is optional.com</address> <jndi-port>9811</jndi-port> <sbm-home>D:/SBM65_WS60</sbm-home> </node> <node name="sys76sbm65node"> <address>sys76. The <jndi-port> number of the jmsserver should be the same as the <jndi-port> of the EJB cluster node.com</address> <jndi-port>9811</jndi-port> </jmsserver> Note that the address and the <jndi-port> number of the jmsserver are the same as the address and <jndi-port> of the EJB cluster node. For example.128</address> <http-port>9448</http-port> </proxyserver> Clustering Guide 67 Before Clustering . which host the jmsserver.Using Ports While specifying the port numbers in the cluster configuration file.1. and not valid for JMS server. NOTE: The node name should be same as the one you specified while installing SBM. . note the following points: • The entire EJB cluster node should have the same <jndi-port> value.tdiinc. the jmsserver should have the following values: <jmsserver name="sys76sbm65node"> <address>sys76.com</address> <jndi-port>9811</jndi-port> <sbm-home>D:/SBM65_WS60</sbm-home> </node> </nodes> <persistence> . if the proxyserver is described as below: <proxyserver name="sys90" type="websphere"> <address>10. The tag <http-port> can also be specified after <jndi-port> tag for EJB server or EJB cluster to access the HTTP port (if available) on this EJB node.

bat Clustering Guide 68 Configuring Clusters . All the Web cluster nodes have the same <http-port> number. Configuring Clusters Configuring a cluster in WebSphere involves federating the installations with WebSphere ND. etc. . To check that the node agents for sys76 and sys114 are running. In case of a cluster. setting up EJB and Portal clusters. Start WebSphere Deployment Manager. Setting up EJB and Portal Clusters 1.1.173</address> <http-port>9448</http-port> <sbm-home>D:/SBM_WS60</sbm-home> </node> <node name="sys76sbm65node"> <address>10.name parameter in the SBM_HOME\conf\sbmjndi.32.properties file. You can find this node name from the sbm.websphere. by executing startManager. use System Administration > Node Agent from the WebSphere Administrative Console of Deployment Manager. </persistence> </cluster> Note that the <http-port> for all the Web cluster nodes is the same as the proxyserver <http-port>. the Web cluster should be as shown below: <cluster name="sbmwebCluster" type="web" create="true"> <nodes> <node name="sys114sbm65node"> <address>10.114</address> <http-port>9448</http-port> <sbm-home>D:/SBM65_WS60</sbm-home> </node> </nodes> <persistence> . The node agent should still be running from when the addNode command was executed previously. NOTE: The node name should be same as the one you specified while installing SBM.then. and configuring Portal load balancing.1. Then look at the status for the nodes sys76 and sys114. If the node agent is unavailable on one of the computers.) on the portal server nodes.bat in D:\WebSphere\DeploymentManager\bin (on sys90). the JNDI tree for all nodes is present at the cell level and hence the <jndi-port> value will be the same as the EJB <jndi-port> value. D:\WebSphere\AppServer\bin\startNode. start it from the command line of that computer.32. 2.node. Start the node agent on sys76 and sys114. The <jndi-port> value will be different than the <http-port> in case of a standalone portal server. The tag <jndi-port> can be specified for portal server nodes for query service to access the JNDI resources (JDBC.

conf" 9448 MAP_ALL "C:\\IBM\\WebSphere\\Plugins" unmanaged aruba.bat|sh -cmd in SBM_HOME\cluster\bin on one of the cluster nodes.war" ules-ps41" target="ejb">quickrules-ps41.bat -f C:\\IBM\\WebSphere\\AppServer\\bin\\configureWebserverDefinition.jacl webserver1 IHS "C:\\IBM\\IBMHTTPServer" "C:\\IBM\\IBMHTTPServer\\conf\\httpd.bat|sh on all the nodes to verify WebSphere parameters.ear</application> 2.ear</application> Setting Up the Cluster To run the cluster setup: • Execute setupcluster.3. restart DMgr.xml.ear</application> to <application name="QuickRules3.jacl webserver1 IHS Clustering Guide 69 Setting Up the Cluster . For example. Edit SBM_HOME\cluster\bin\setenv. Create and initialize the SBM tables in the database. wsadmin.1" target="ejb">quickrules-was60. add the ND installation path before the wsadmin script and configureWebserverDefinition. In SBM_HOME\bin on sys76 and sys114. Change the following entry from the deploy section of the file sbm-cluster. the following changes need to be done manually to configure QuickRules in the cluster mode. Add the following entry in the deploy section of the file sbm-cluster.xml.war.com aruba. <application name="quickrname="quickrules-was.bat located under the bin directory of the Plugins installation directory. Configuring Portal Load Balancing Configure IBM HTTP Server to perform SBM Portals load-balancing. Ensure the location specified for the ADMINSERVER_HOME does not contain backward slash (“\”).bat -f configureWebserverDefinition.savvion.savvion. <application location="%SBM_HOME%\webapps" name="quickrules.war" target="web">quickrules. 1. 4.com windows modify it to: C:\\IBM\\WebSphere\\AppServer\\bin\\wsadmin. 1. Edit the configurewebserver1. In this file. execute: setupSBM.jacl.bat -c all -u ebms -p ebms -yes Note: After setting up the cluster. Configuring for QuickRules Support After configuring the cluster.

For more information.war\WEB-INF\lib\commons-digester. In the left panel. and then in the right panel. Copy this value to the value for the property Port in httpd. go to Servers > Web Server.properties file. Clustering Guide 70 Modifying SBM Properties .jasper.savvion.war\WEB-INF\lib\commons-digester.jasper.xml from the SBM_HOME\cluster\conf directory and check the value for <http-port> under the tag <proxyserver>. select webserver1 and click Generate Plugin-in.properties files and set the sbm."C:\\IBM\\IBMHTTPServer" "C:\\IBM\\IBMHTTPServer\\conf\\httpd.jar| where jasper is the profile name of an individual node and aruba is the profile name of an ND node.websphere.com windows 2.war\WEB-INF\lib\jasperreports.conf file and modify the bpmportal.conf in the IBM Http Server installation location.ear\sbm.webappdir parameter in the sbm.savvion. To modify the properties: 1. For example.ear\sbm.name parameter in the sbmjndi.conf" 9448 MAP_ALL "C:\\IBM\\WebSphere\\Plugins" unmanaged aruba.jar| D:\IBM\WebSphere\AppServer\profiles\sys79\installedApps\aruba\sbm_ war. 3. bpmportal. After confirmation click Propogate Plugin-in.ear\sbm.classpath= D:\IBM\WebSphere\AppServer\profiles\sys79\installedApps\aruba\sbm_ war."Using WebSphere Application Server V5 for load balancing and failover". Please note down the current values because you will need them while restoring the original configuration.conf and sbm.jar| D:\IBM\WebSphere\AppServer\profiles\sys79\installedApps\jasper\sbm _war.compiler. The cellname should be the cell name of the “dmgr” of the ND installation.xml.compiler.conf and SBM_HOME\conf\sbmjndi. Open the file sbm-cluster.com aruba.jasper. Edit the SBM_HOME\conf\bpmportal. Log in into the WebSphere Admin Console. sbm-cluster. refer to WebSphere documentation .classpath= D:\IBM\WebSphere\AppServer\profiles\sys79\installedApps\jasper\sbm _war. Please note down the current values because you will need them while restoring the original configuration. The cellname should be the cell name of the “dmgr” of the ND installation.ear\sbm.classpath parameter.jar| should be changed to: bpmportal. Edit the SBM_HOME\conf\sbm.compiler.cell.war\WEB-INF\lib\jasperreports. Modifying SBM Properties Ensure that all nodes in the cluster have the same cluster configuration file. 2.

In the example above. If no file is specified. refer to Configuring BizPulse for Failover on page 48. http:// jaguar.0. Run SBM_HOME\cluster\bin\modifyprop.savvion. Configuring BizPulse for Failover Some parameters in bizpulse. you need to run the modifyprop.bat on both sys76 and sys114. • • In D:\WebSphere\AppServer\bin on sys76. Run SBM_HOME\bin\setupSbmPortalServer.orig extensions to the respective conf files. You can use either BizPulseAdmin. then sbm-cluster. Edit the SBM_HOME\conf\webservices. and their compiled rules on all the nodes in the cluster.publishURL=http://jaguar.3. Starting EJB and Portal Clusters 1.xml is used 5. In case the cluster configuration file is other than sbm-cluster. modifyprop.xml. Working with the Cluster You need to first start the clusters and / or individual servers.bat on each node in the cluster to update the properties in the SBM conf files for the cluster. 4. execute: startNode. Ensure that the same copy of the applications exists on all the nodes and there is no version mismatch on different nodes. or BPM Portal to load the applications. BizPulse Application Loading in a Cluster For application loading.savvion.inquiryURL=http://jaguar.bat |sh file with the option -f with the configuration file name. This will back up the affected configuration files under SBM_HOME\conf directory by appending .com:9448/sbm/uddi uddi.bat Clustering Guide 71 Configuring BizPulse for Failover .conf file and update the following properties: uddi. and then run the BizLogic / BizPulse servers. For more information about these parameters. make sure that you copy all the relevant applications.conf affect BizPulse failover functionality significantly.bat In D:\WebSphere\AppServer\bin on sys114.com:9448/sbm/uddi Both the URLs should point to the individual portal server URL. Start the node agents on each node if not already started.savvion.0.bat [-f clusterFileName] where clusterFileName is the name of the cluster configuration file to use. execute: startNode.com:9448 is the portal server URL of the individual node on jaguar.

then start with the command startBizPulseServer -nodes <nodes in cluster> Clustering Guide 72 Working with the Cluster . refer to BizLogic Server Commands on page 76. Execute startCluster. the soap.jsp Starting the BizLogic Server Go to SBM_HOME\bin and start the BizLogic servers a follows: 1.bat|sh sbm_sys114sbm65node • startServer. you can individually start the servers as follows: a. then start with the command startBizLogicServer -u <user name> -p <password> -nc <nodes in cluster> 2. If the EJB cluster is set up.jar under SBM_HOME/lib should be renamed (e. The wsadmin tool exits after ensuring the Start command to individual servers.tdiinc.2.g.com:9448/sbm/bpmportal/login.bat|sh sbm_sys76sbm65node • startServer. If the EJB Cluster is set up. • startServer.jar.orig) before starting BizLogic and BizPulse servers.jar.jar distributed with SBM is different from the WebSphere’s soap.. in D:\IBMHttpServer. soap.exe You can now log in into SBM cluster using the common BPM Portal URL: http://sys90. so make sure that all the servers are started by checking the logs before proceeding (the portal server may take several minutes to start).bat|sh sbm_web_sys114sbm65node Starting IBM HTTP Server From the Deployment Manager Machine.bat|sh sbm_web_sys76sbm65node b. execute: Apache. Alternatively. On the sys76 node. and there is a single EJB server. then start with the command: startBizLogicServer For more information on BizLogic server commands. (APPSERVER_HOME\AppServer\profiles\<profileName>\bin): • startServer. Note: Since the version of soap. On the sys114 node.bat from SBM_HOME\cluster\bin. Starting the BizPulse Server Go to SBM_HOME\bin and start the BizPulse server as follows: 1. If the EJB cluster is not set up.

bat 3.properties files and set the sbm. execute: stopNode. Edit the SBM_HOME\conf\sbm.bat from SBM_HOME\cluster\bin. you should get a message that the node has been successfully removed.bat Note that the command must not be issued on two nodes at the same time. with CTRL+C in the terminal where IBM HTTP Server has started. 4.bat In D:\WebSphere\AppServer\bin on sys114. Note: BizLogic and BizPulse servers can also be started using BPM Portal. Remove EJB and Portal Cluster by executing removeSBMClusterFromWS. 2. and there is a single EJB server.properties file to their original values which you had noted down in the step 1 of the Modifying SBM Properties on page 70.name parameter in the sbmjndi. execute: removeNode.bat In D:\WebSphere\AppServer\bin on sys114. 6. refer to BizPulse Server Commands on page 78. wait for the command to complete.cell.orig extensions. After the command completes. execute: stopNode. Restoring Original Configuration 1. Convert the setup to stand-alone SBM installations by removing the nodes that were federated to the Deployment Manager: • • In D:\WebSphere\AppServer\bin on sys76. Stopping the Cluster You need to stop the cluster in the exact reverse order of starting the cluster as described in Starting EJB and Portal Clusters on page 71. Execute stopCluster. Stop IBM HTTP Server. execute: removeNode.conf and sbm. Stop EJB and Portal cluster: a. Rename the backed up configuration files from the SBM_HOME\conf directory by removing the . Stop the node agents on each node: • • In D:\WebSphere\AppServer\bin on sys76. b.conf and SBM_HOME\conf\sbmjndi. Clustering Guide 73 Restoring Original Configuration .webappdir parameter in the sbm. then start with the command startBizPulseServer For more information on BizPulse server commands. and then execute it on computer sys114.bat from SBM_HOME\cluster\bin.websphere. by using the shutdown command for individual servers. 5. Execute removeNode on computer sys76 first. If the EJB Cluster is not set up.2.

If you need to federate the nodes after installing SBM. for example.ibm. the parameter SBM. the cluster may not work.0. Install WebSphere 6. sys90 and sys76.<clusterMemberName>-<busName>.2.5 Standard Edition on sys76 and sys90. Install SBM on sys90 and sys76. The following figure illustrates the architecture of the cluster. The messaging engine folder name follows the following convention: <nodeName>. This is a very important step and if not done properly. Remove the messaging engine datastore created inside the folder APPSERVER_HOME\AppServer\profiles\<profileName>\databases\com. Clustering Guide 74 Working with Two-Node Clusters . using the following steps: a. This has to be done in all the cluster member machines. During the installation. 3. 1. 5. Find out the node name where Deployment Manager is installed. 2. Figure 19 WebSphere . Federate both the nodes (sys90 and sys76) to the Deployment Manager (sys90).ws. when a screen prompts "Modify ports for coexistence".conf needs to be manually changed on each node.5 Network Deployment on sys90. select the check box. Install WebSphere 6.0. sys90 in this case.7.2.Two-node Cluster You can compare it with the architecture of the three-node cluster illustrated in Figure 18 on page 65. Working with Two-Node Clusters The configuration explained in the sample setup above can also be achieved using two machines instead of three machines.WebAppDir in sbm. 4.sib.

war to D:\WebSphere\AppServer\installedApps\sys90Network\sbm. from D:\WebSphere\AppServer\installedApps\sys76\sbm.5 is installed on sys90.ear\sbm. for example. in sys76. on both sys76 and sys114 in this case. Refer to the IBM HttpServer Installation document for more details.0.ear\sbm. make sure that IBM HttpServer is installed as a Windows service.b. Note: When WebSphere 6.war. c.2. Change the value of SBM. Clustering Guide 75 Working with Two-Node Clusters .WebAppDir from individual machine name to the Deployment Manager machine name.war.war. For example. Make sure that the change is carried out on all the nodes.

It also starts the BizStore. [options]: -help [count]: number of BizLogic Server Instances [username]: optional. for a cluster with two nodes: startBizLogicServer –u ebms -p ebms -nc 2 The above command starts the BizLogic server on all instances in the cluster. You can also start BizLogic Server from the BPM Portal Administration tab. startBizLogicServer [options] [-u [username]] [-p [password]] [-nc [count]] Where. Emailer. MConsole. Go to System > Status. valid password For example. valid username [password]: optional. ResumeWS.Appendix A BizLogic Server Commands This appendix describes the BizLogic commands you need to use for all the supported application servers. and Session services. CheckDue. Use this command only if you want to start all the servers in a cluster. 76 . Starting BizLogic Server Instances Start the BizLogic servers on all the cluster instances by running the following batch script in SBM_HOME\bin. select BizLogic Server and click Start.

use: addBizLogicNodes –u ebms -p ebms -nc 2. One node in the cluster is shut down or crashes.common. After the node is restarted.jms. [options]: -help [count]: number of BizLogic Server Instances [username]: optional. valid username [password]: optional.Use the following commands to start one or several of all the servers. invoke the following command for Archiver or EventPublisher: startArchiver. valid password For example. Assume a cluster with three nodes.bat|sh startEventPublisher.bat|sh If you see a warning message indicating that the Archiver or EventPublisher is already started. If a node has crashed or a new node is added. If you need to restart two nodes.JMSException. where 1 indicates the number of nodes to restart. Clustering Guide 77 Stopping BizLogic Server Instances . you can disregard it. stopBizLogicServer –u ebms -p ebms -nc 2 Note: The startBizLogicServer and stopBizLogicServer scripts occasionally throw a weblogic. use the following command to start only the BizLogic server on that node: addBizLogicNodes –u ebms -p ebms -nc 1. You can ignore the message and run the script again. stopBizLogicServer [options] [-u [username]] [-p [password]] [-nc [count]] Where. Stopping BizLogic Server Instances You may drop the BizLogic servers on the cluster instances by running the following batch script in SBM_HOME\bin.

and start the server again. Windows: startBizPulseServer. Go to System > Status.You can also start BizPulse Server from the BPM Portal Administration tab.server.cluster.Appendix B BizPulse Server Commands This section describes the BizPulse commands you will need to use for all the supported application servers. you need to stop the server. However.sh -nodes <nodes in cluster> This command starts the BizPulse server on one node.monitor to “on”. 2.monitor is set to “on” in the bizpulse. the monitoring will not start. select BizPulse Server and click Start.bat -nodes <nodes in cluster> UNIX: stopBizPulseServer. and monitoring on all the nodes in the cluster.server. if the parameter bizpulse. Starting and Stopping BizPulse Server 1.sh -nodes <nodes in cluster> This command stops the BizPulse server.conf file.cluster.cluster. Start the BizPulse server by running startBizPulseServer on one of the nodes in the cluster. If the parameter bizpulse.monitor is set to “off” in the bizpulse. and stops monitoring on all the nodes in the cluster. set the parameter bizpulse. if you want to start monitoring after you have started the BizPulse server. 78 .bat -nodes <nodes in cluster> UNIX: startBizPulseServer.server.conf file. Stop BizPulse server by running: Windows: stopBizPulseServer.

cluster.server.sh -nodes <nodes in cluster> Note: To use the startBizPulseMonitor.sh -nodes <nodes in cluster> Clustering Guide 79 Starting and Stopping BizPulse Monitoring .cluster. you can start the BizPulse monitor on that node by running: Windows: startBizPulseMonitor. In this setup. you can stop BizPulse monitor by running: Windows: stopBizPulseMonitor.bat|sh command on a new node.conf file.server.monitor set to “on” in the bizpulse.bat -nodes <nodes in cluster> UNIX: startBizPulseMonitor. If you want to stop BizPulse monitoring without stopping the BizPulse server.bat -nodes <nodes in cluster> UNIX: stopBizPulseMonitor.monitor set to “on” in the bizpulse.conf file.Starting and Stopping BizPulse Monitoring If you start the BizPulse server with the parameter bizpulse. you must have started the server with the parameter bizpulse. monitoring will start on all the nodes in the server. if you add a new node to the cluster.

the basic unit of work. must be performed by one or more human performers (valid individual user. An adapter can automate certain functions and tasks performed by a remote server or other external systems. For a full version of terms used in SBM documentation. and manage SBM users. groups and access control.Glossary This is a listing of common SBM terminology. Adapter A Java class that integrates remote. refer to the Terminology Guide in the SBM_HOME\docs folder. multiple users or user group). third party classes and actions with SBM.The Administration module is visible only to SBM users who have permissions to access it. Application In SBM. Activity Workstep In SBM. A|B|C|D|E|G|H|I|K|M|P|R|S|T|U|W A ACL Manager Go to Top In Savvion BusinessManager (SBM). 80 . Administration A module in BPM Portal enabling the administrator to perform such tasks as installing/uninstalling applications. an application is an installed. more precise control over user access rights for resources and actions. Access Control List Manager provides a finer. modifying configuration parameters controlling SBM operations. executable business process that automates a business flow.

administrators and developers a unified. lightweight. BPMN BPMN (Business Process Modelling Notation) provides businesses with the capability of defining and understanding their internal and external business procedures through a Business Process Diagram giving organizations the ability to communicate these procedures in a standard manner. BPM Studio An SBM component that is an Integrated Development Environment for SBM and enables SBM users to develop and deploy an SBM application without leaving the development environment. providing real-time status information and identifying critical events to assist senior management in making informed business decisions. and provides support for multiple business calendars across different time zones. customizable portal for single sign-on access to all SBM functionalities to which they are granted permission. 81 . BAM Business Activity Management combines Business Process Management with strategic and analytical information on specific business performance indicators. managers. Business Calendar An SBM feature that accurately calculates the Due Date of tasks.including across multiple organizations using a combination of Web services. and the Internet. BPM Portal An SBM component that offers users. BizLogic An SBM component that provides a flexible. sophisticated presentation flows for business processes. extranets. BizStore An open repository of rich e-business information collected from different SBM modules. install them as Web applications. BizPulse An SBM component that provides an open event-driven rule engine to formulate and enforce policies in business applications. The Balanced Scorecard provides an analysis from a range of perspectives. and execute them on their Web browsers. BizSolo An SBM component that enables users to develop customizable.B Balanced Scorecard Go to Top A management application in the Management module that measures performance by analyzing how an organization’s business activities help it achieve its strategic goals. scalable workflow process engine for intranets. BPEL BPEL (Business Process Execution Language) for Web services is an XML-based language designed to enable task-sharing for a distributed computing or grid computing environment .

Business Flow
The logical sequence of process activities, related to one another by a triggering activity, to achieve an outcome. It represents a business process that begins with a commitment and ends with the termination of that commitment. In SBM, business flow includes workflow (the flow of all human-performed activities), integration flow (the flow of activities performed by systems) and presentation flow (from a user’s viewpoint, the flow of data from one Web page to the next).

Business Logic
The control flow and information flow among worksteps that define a business process.

Business Object
A representation of an activity in the business domain, including its name, definition, attributes, behavior, relationships and constraints.

Business Process
A process involving multiple worksteps in the form of operations, interactions and notifications performed by a user, group of users, an external adapter, or a script. Examples of internal business processes are purchasing, expense reporting, help desk, and time card. External processes may include order processing, sales, and customer service.

Business Process Management
The concept of guiding work activities through a multi-step business process in order to improve performance and reduce costs within and across functional business units.

Business Rule
A combination of elements, including validation edits, logon verifications, database lookups, policies and transformations, that represent an enterprise’s way of doing business.

C
Cluster

Go to Top

In SBM, an integrated set of multiple, electronically connected but physically separated servers. This loosely coupled group of nodes collaborate to provide shared access to the services that each node hosts. To other systems, the cluster appears as a single system.

Control Flow
The sequences of worksteps and workstep conditions, as defined in a process template in BPM Studio or Process Modeler.

D
Dashboard

Go to Top

An SBM feature that provides a graphic overview of the status of several business processes on a single Web page, enabling users to monitor the progress of each process. Users can view business processes across all applications or for a selected application.

Dataslot
A data placeholder that persists through the entire process and defines the information flow of the business process. Dataslots are associated with processes, where they can add information into (Input type) or out of (Output type) worksteps, and appear as editable or read-only fields on a user’s interface.

E
Expression Editor

Go to Top

An SBM tool that enables users to define complex conditional expressions within a Decision workstep to support their business requirements.
82

G
Group

Go to Top

In SBM, an entity that has as members valid users or other groups who perform related work and have authorized access to specific components.

H
Heatmap

Go to Top

An SBM feature that provides a convenient, graphical tool for managers to visually locate the bottlenecks in the process execution. It helps managers to get an overview of the status of the currently active instances, identify suspended instances, and analyze the history of the completed instances.

Home
A module in BPM Portal through which users interact with SBM. Using the Home module, users complete entries to various tasks and applications, update profile, set preferences, and link to the support infrastructure required to achieve these tasks. The Home module is the primary interface for SBM application users.

I
Infopad

Go to Top

In SBM, a data structure used to capture business metrics, typically displayed as a table with one or two dimensions.

Instance
An individual object within a specific class. In SBM, a self-contained unit that is created each time you use a process template to run an SBM application.

K
KPI

Go to Top

Key Performance Indicator, used in the Balanced Scorecard system, that provides the data translating enterprise goals into a set of measurable objectives.

M
Management

Go to Top

A module in BPM Portal enabling the managers to query, report, and control processes and resources for users of SBM. The Management module is visible only to SBM users who have permissions to access it.

Managed Adapter
In SBM, a Managed Adapter is an implementation of an adapter interface that facilitates data exchange between SBM processes and external applications.

Migration
The process of moving from the use of one operating environment to another operating environment that is typically seen as improvement. Migration can involve moving to new hardware, new software, or both. It may involve a new application, another type of database, or a redesigned network. Migration is also used to refer simply to the process of moving data from one storage device to another. SBM supports data migration as well as application migration.

P
PAM

Go to Top

Process Asset Management recognizes that a company’s processes are a unique asset and provides a structure that organizes, stores, and secures process data, enabling users to retrieve information on any of the company’s processes.
83

Performer
An entity that executes a workstep. Depending on the workstep type, the performer can be a human user, a group of users, an adapter or other external performer, or a script.

Presentation Flow
The flow of information and user input from one interface to the next. Typically related to a single Activity workstep in the process and generated in a BizSolo environment.

Process Engine
Orchestrates the execution of business processes and also coordinates conversations among process engines based on public processes, which forms the backbone of global business collaboration.

Process Modeler
A stand-alone component that enables users to design templates for basic business processes and store or retrieve them from the Savvion central process repository, and to design and run simulations of processes.

Process Refresh
An SBM feature for replacing the installed process without versioning, facilitating the running process instances to refresh and seamlessly adapt to the new workflow.

Process Repository
A central place (can contain several databases) in which a group of processes is stored and maintained in an organized way, and can be accessed to retrieve information.

Process Template
In SBM, a model of business flow that includes worksteps, connectors and dataslots. After users deploy and install it as an application in the SBM directory structure, they can use the application to create process instances.

R
Rollback

Go to Top

In SBM, a feature that restarts the workflow from a workstep previously selected as the rollback point in the process, performed automatically in the event of a failure.

Role
The actions and activities assigned to a valid SBM user who is a member of a group. In SBM, only members of a group can be assigned a role. A role indicates the relationships of the user in a group context.

Rule Wizard
An interactive utility that enables SBM users to quickly develop rules that can be applied to a business process.

S
SBM Application

Go to Top

An application is an implementation of a business process. It can contain one or more process templates, performers, adapters, customized forms or rules. An application can be deployed, installed and run on BizLogic servers. In SBM, an application is an installed, executable business process that automates a workflow.

SBM Web Services
An SBM component that allows SBM application developers to; a) publish their applications as Web Services, and b) find and convert other available Web Services on the Internet into SBM applications.

Swim Lanes
Used in workflow diagrams to organize complex processes across functional boundaries. For example, seen as horizontal lines on a process map, swim lanes can be used to place individual task steps into different categories that depend on task ownership.
84

T
Task

Go to Top

In SBM, a performer is assigned one or more workitems that the performer sees as tasks. There are two types of tasks: Assigned, which are assigned specifically to you; and Available, which are available to be performed by you or other members of your user group.

U
User
In SBM, a valid human performer with authorized access to specific modules.

Go to Top

W
Workflow

Go to Top

The logical sequence of activities performed by human performers, typically in a BPM Studio or Process Modeler environment. Workflow includes the tasks, procedural steps, organizations or people involved, required input and output information, and tools needed for each activity in a business process.

85

71 BPM Portal Clustering 15 BPM Studio Clustering 16 E EJB Cluster 56 EJB server 56 Environment Variables Setting up 56 EventPublisher 77 Excel Adapter. issues in clustering 17 C Cluster Tool 18 Cluster Panel 20 Configuration Panel 20 Server Panel 21 Setting up 21 Starting 19 Clustering 10 Adding New and Recovered Nodes 30. 77 BizPulse Clustering Failover Configuration 48. 32 Cluster Information 21. deploying in a 16 Conventions in SBM documentation 9 Customer support 9 D deploying applications on a cluster 16 Designing Server Clusters 11 B batch script 76. 14 Terminology 10 Clustering Framework 18. 59.Index A applications deploying on a cluster 16 Archiver 77 clusters. 37 Cluster Setup in Stages 40 F Failover BizPulse on Pramati 48 BizPulse on WebLogic 59 BizPulse on WebSphere 71 I installing SBM as Windows Service 13 iWay Adapters. 41 Designing 11 for Failover 14 for Load Balancing 14 in SBM 12. issues in clustering 17 86 .

installing SBM as 13 Clustering Guide 87 . 40 Using Ports Pramati 44 WebLogic 53 WebSphere 67 W WebSphere Three-node Cluster 65 Two-node Cluster 74 Windows Service.J JMS server 56 L License Agreement 2 M managed adapters in clustering 16 P Product Support Team 9 R Restoring Original Configuration Pramati 47 WebLogic 59 WebSphere 73 S SBM conventions in documentation 9 documentation list 8 user types 7 Setting up EJB Cluster Pramati 46 WebSphere 68 Setting up JMS Cluster WebLogic 56 Setting up Web Cluster Pramati 46 WebLogic 57 WebSphere 68 U URL Document Server 28.