gettingstarted with wps&esb part3

8/9/2019 Gettingstarted With WPS&ESB Part3

1/256

ibm.com/redbooks

Draft Document for Review June 3, 2008 1:55 pm SG24-7643-00

Getting Started with WebSphereProcessServer and WebSphereEnterprise Service Bus

Part 3: Runtime

Carla Sadtler

Srinivasa R Borusu

Sergiy Fastovets

Thalia Hooker

Ernese Norelus

Fabio Paone

Dong Yu

Install WebSphere Process Server

Build topologies based on

patterns

Prepare for deployment

Front cover
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


2/256


3/256

Getting Started with WebSphere Process Serverand WebSphere ESB Part 3: Runtime

June 2008

International Technical Support Organization

Draft Document for Review June 3, 2008 1:55 pm 7643edno.fm

SG24-7643-00


4/256

7643edno.fm Draft Document for Review June 3, 2008 1:55 pm

Copyright International Business Machines Corporation 2008. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

First Edition (June 2008)

This edition applies to WebSphere Process Server V6.1 and WebSphere Enterprise Service BusV6.1.

This document created or updated on June 3, 2008.

Note: Before using this information and the product it supports, read the information inNotices on page vii.


5/256

Copyright IBM Corp. 2008. All rights reserved. iii

Draft Document for Review June 3, 2008 1:55 pm 7643TOC.fm

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1. Planning for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 WebSphere Application Server concepts . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1.1 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1.2 Application server environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.3 WebSphere Application Server for z/OS. . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Selecting a topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2.1 Stand-alone server topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2.2 Deployment environment patterns . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2.3 Single cluster pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.2.4 Remote messaging pattern. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.5 Remote messaging and remote support pattern. . . . . . . . . . . . . . . . 141.2.6 Web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.3 Planning for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.3.2 User ID authorities for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.3.3 Installation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.3.4 Installation type (distributed and i5/OS) . . . . . . . . . . . . . . . . . . . . . . 211.3.5 Selecting additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1.3.6 Root directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.3.7 Creating profiles during installation. . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.3.8 Installing recommended maintenance . . . . . . . . . . . . . . . . . . . . . . . 231.4 Planning for profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.4.1 Planning for databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.4.2 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.4.3 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

1.5 Planning for the Profile Management Tool . . . . . . . . . . . . . . . . . . . . . . . . 33

1.5.1 Profile environment and type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


6/256

7643TOC.fm Draft Document for Review June 3, 2008 1:55 pm

iv Getting Started with WebSphere Process Server and WebSphere ESB Part 3: Runtime

Chapter 2. Installation on distributed and i5/OS systems . . . . . . . . . . . . . 372.1 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2 Typical installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.3 Installation on i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2.3.1 Installing remotely from a Windows workstation . . . . . . . . . . . . . . . . 432.3.2 Installing WebSphere Process Server on i5/OS silently . . . . . . . . . . 472.4 Install the IBM Update Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.5 Download and install maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 3. Creating profiles on distributed and i5/OS systems . . . . . . . . 513.1 Methods used to build the profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.1.1 Profile Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.1.2 The manageprofiles command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2 Standalone WebSphere Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . 563.3 Building a deployment environment using a pattern . . . . . . . . . . . . . . . . . 663.3.1 Summary of steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.3.2 Build the Web server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.3.3 Building the deployment manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 71

3.3.4 Building Node1 and the first process server of the cluster . . . . . . . . 753.3.5 Building Node2 and the second process server of the cluster . . . . . 793.3.6 Creating the cluster for mediation modules. . . . . . . . . . . . . . . . . . . . 81

3.3.7 Define the Web server to the cell . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

3.4 Augmenting a WebSphere ESB profile to WebSphere Process Server . . 90

Chapter 4. Creating and managing profiles on z/OS . . . . . . . . . . . . . . . . . 934.1 Methods of creating profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.2 Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954.3 Creating a deployment manager node . . . . . . . . . . . . . . . . . . . . . . . . . . . 964.4 Creating a custom node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104.5 Configuring the deployment manager node . . . . . . . . . . . . . . . . . . . . . . 127

4.5.1 Run the zSMPInstall.sh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

4.5.2 Preparing DmgrDB2.rsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.5.3 Run the zWPSConfig.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.5.4 Creating DB2 database objects using the createDB.sh script . . . . 1314.5.5 Back up the WebSphere configuration HFS datasets. . . . . . . . . . . 133

4.6 Configuring a custom node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.6.1 Running the zSMPInstall script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.6.2 Preparing ManagedDB2.rsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

4.6.3 Running zWPSConfig.sh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

4.6.4 Federating a custom node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374.6.5 Configure and federate secondary custom node . . . . . . . . . . . . . . 1394.6.6 Back up the WebSphere configuration HFS datasets. . . . . . . . . . . 139


7/256

Contents v

Draft Document for Review June 3, 2008 1:55 pm 7643TOC.fm

4.7 Creating a WebSphere Process Server cluster. . . . . . . . . . . . . . . . . . . . 1394.7.1 Add DB2 libraries to the Servant and Adjunct JCL . . . . . . . . . . . . . 140

4.7.2 creating a cluster/server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.7.3 Configure Service Component Architecture . . . . . . . . . . . . . . . . . . 145

4.7.4 Configure Common Event Infrastructure. . . . . . . . . . . . . . . . . . . . . 1494.7.5 Configuring the Business Flow and Human Task Managers . . . . . 152

Chapter 5. Managing the runtime environment . . . . . . . . . . . . . . . . . . . . 1575.1 Administrative tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

5.1.1 Using commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595.1.2 Using the administrative console . . . . . . . . . . . . . . . . . . . . . . . . . . 1615.1.3 Using IBM Web Administration for i5/OS . . . . . . . . . . . . . . . . . . . . 1645.1.4 WebSphere scripting client (wsadmin) . . . . . . . . . . . . . . . . . . . . . . 168

5.2 Managing stand-alone server environments . . . . . . . . . . . . . . . . . . . . . . 1695.2.1 Managing application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

5.3 Managing distributed environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715.3.1 Managing the deployment manager . . . . . . . . . . . . . . . . . . . . . . . . 1715.3.2 Managing nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735.3.3 Managing servers and clusters from the administrative console . . 175

5.4 Managing the Web server plug-in configuration . . . . . . . . . . . . . . . . . . . 1775.4.1 Generating the plug-in with administrative console. . . . . . . . . . . . . 1775.4.2 Enabling automated plug-in regeneration . . . . . . . . . . . . . . . . . . . . 178

5.4.3 Propagating the plug-in configuration file . . . . . . . . . . . . . . . . . . . . 1785.4.4 Activating the new plug-in configuration . . . . . . . . . . . . . . . . . . . . . 1795.4.5 Enable automated plug-in propagation . . . . . . . . . . . . . . . . . . . . . . 180

5.5 Viewing the JVM logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Chapter 6. Managing applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1836.1 Scenario: Order Management System . . . . . . . . . . . . . . . . . . . . . . . . . . 1846.2 Planning for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

6.2.1 Setting up the prerequisites for Order Management System . . . . . 189

6.3 Defining application resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916.3.1 Setting the resource scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916.3.2 Defining security credentials to access a resource. . . . . . . . . . . . . 1926.3.3 Defining JDBC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1936.3.4 Defining users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2006.3.5 JMS resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

6.4 Deploying applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086.4.1 Exporting applications for deployment . . . . . . . . . . . . . . . . . . . . . . 209

6.4.2 Installing applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2106.4.3 Configure and test Web service URLs . . . . . . . . . . . . . . . . . . . . . . 2126.4.4 Updating endpoint URLs in Web service bindings . . . . . . . . . . . . . 2146.4.5 Example: installing the Order Management System applications. . 215


8/256

7643TOC.fm Draft Document for Review June 3, 2008 1:55 pm

vi Getting Started with WebSphere Process Server and WebSphere ESB Part 3: Runtime

6.5 Generate the Web server plug-in configuration. . . . . . . . . . . . . . . . . . . . 2206.6 Testing the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

6.6.1 Starting and preparing your test clients. . . . . . . . . . . . . . . . . . . . . . 2216.6.2 Testing the mediation modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

6.6.3 Test the business integration modules . . . . . . . . . . . . . . . . . . . . . . 225

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233How to get Redbooks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235


9/256

Draft Document for Review June 3, 2008 1:55 pm 7643spec.fm

Copyright IBM Corp. 2008. All rights reserved. vii

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area.Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send license

inquiries, in writing, to:IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may

make improvements and/or changes in the product(s) and/or the program(s) described in this publication atany time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm

the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs in

any form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which thesample programs are written. These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.


10/256

7643spec.fm Draft Document for Review June 3, 2008 1:55 pm

viii Getting Started with WebSphere Process Server and WebSphere ESB Part 3: Runtime

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

Redbooks (logo) iSeriesi5/OSz/OSDB2

InformixIBMMVSOS/390Rational

RedbooksRACFSystem zWebSphere

The following terms are trademarks of other companies:

Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporationand/or its affiliates.

EJB, Java, JDBC, JMX, JVM, J2EE, and all Java-based trademarks are trademarks of Sun Microsystems,Inc. in the United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.


11/256

Copyright IBM Corp. 2008. All rights reserved. ix

Draft Document for Review June 3, 2008 1:55 pm 7643pref.fm

Preface

This book provides new users with information on installing and configuring aWebSphere Process Server and WebSphere Enterprise Service Bus runtimeenvironment. It includes installation examples on distributed, i5/OS, and z/OSplatforms. It also provides basic configuration information for deployingapplications.

Some knowledge of WebSphere Application Server Network Deployment isassumed.

This is the third book of a three-part series:

Getting Started with WebSphere Process Server and WebSphere EnterpriseService Bus:

Part 1: Development, SG24-7608

Part 2: Scenario, SG24-7642

Part 3: Runtime, SG24-7643

The team that wrote this book

This book was produced by a team of specialists from around the world workingat the International Technical Support Organization, Raleigh Center.

Carla Sadtler is a Consulting IT Specialist at the ITSO, Raleigh Center. Shewrites extensively about WebSphere and Patterns for e-business areas. Before

joining the ITSO in 1985, Carla worked in the Raleigh branch office as a ProgramSupport Representative, supporting MVS customers. She holds a degree inmathematics from the University of North Carolina at Greensboro.

Srinivasa Borusu is a Senior IT Specialist at IBM IndiaSoftware Labs, Bangalore. He is currently working as aWebSphere Consultant with IBM Business Partner TechnicalStrategy and Enablement (BPTSE) Developer Services team,enabling and supporting worldwide business partners on

WebSphere products. Since he joined IBM in 2000, he hasplayed various roles, including Tech Lead for the IBM JavaVirtual Machine Support, during his tenure at OS/2 worldwide

support center. His technical portfolio also includes one FILE rated patent, 4 IBM


12/256

7643pref.fm Draft Document for Review June 3, 2008 1:55 pm

x Getting Started with WebSphere Process Server and WebSphere ESB Part 3: Runtime

SOA and WebSphere product certifications and several published articles. Heholds a masters degree in Computer Applications from the Andhra University,Visakhapatnam, India.

Sergiy Fastovets joined IBM in 1996 in the Research Triangle

Park. He has ten years experience in design, development, andsales support in the Host Integration area. In 2006 Sergiytransferred to the IBM UK where he is an IT Consultant forWebSphere Software Services. He holds a degree inmathematics from the University of Saint Petersburg, Russia.His native town is Poltava, Ukraine.

Thalia Hooker Ph.D., is a Consulting IT Specialist andmember of the WebSphere Americas iPoC Team. She

executes proof-of-concepts using the WebSphere platform toshow customers how IBM solutions and products can helpthem meet their integration requirements. These solutions andproducts include Service Oriented Architecture (SOA) andWebSphere Business Process Management products such as,WebSphere Process Server and WebSphere EnterpriseService Bus.

Ernese Norelus is an IBM Certified Consulting IT Specialist

with the ASEAN Software Services team in Singapore. He hasbeen in IT for ten years, with eight years of experiencepresenting, teaching, and proposing solution architectures tocustomers using the WebSphere business integration portfolio.He is also a well-known conference speaker, and he holdscertifications in IM/DB2, Lotus, Rational, Tivoli andWebSphere. He holds degrees in Biochemistry and Computer

Science and Information Technology Management from the Universit duQubec Montral, (Qubec, Canada).

Fabio Paone is WebSphere technical sales supporting theChannel (Business Partners) in Italy. He has four yearsexperience as a developer in the Rome Tivoli Lab, primarily inJ2EE development. He is certified as a WebSphere ApplicationServer Administrator (versions 5, 6, and 6.1), and hasparticipated in WebSphere Application Server certification testreviews.


13/256

Preface xi

Draft Document for Review June 3, 2008 1:55 pm 7643pref.fm

Dong Yu is a Staff Software Engineer at IBM ChinaDevelopment Lab. He has four years of experience in theWebSphere Business Integration Field.His areas of expertiseinclude WebSphere Process Server installation andConfiguration.Dong holds a master degree in Software

Engineering from Northwestern Polytechnical University.

Thanks to the following people for their contributions to this project:

Rich ConwayInternational Technical Support Organization, Raleigh Center

Margaret TicknorInternational Technical Support Organization, Raleigh Center

Stephen CocksIBM UK

Andrew MeadIBM UK

Sharuff MorsaIBM UK

Dean BarkerIBM UK

Become a published author

Join us for a two- to six-week residency program! Help write a book dealing withspecific products or solutions, while getting hands-on experience with

leading-edge technologies. You will have the opportunity to team with IBMtechnical professionals, Business Partners, and Clients.

Your efforts will help increase product acceptance and customer satisfaction. Asa bonus, you will develop a network of contacts in IBM development labs, andincrease your productivity and marketability.

Find out more about the residency program, browse the residency index, andapply online at:

ibm.com/redbooks/residencies.html
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html


14/256

7643pref.fm Draft Document for Review June 3, 2008 1:55 pm

xii Getting Started with WebSphere Process Server and WebSphere ESB Part 3: Runtime

Comments welcome

Your comments are important to us!

We want our books to be as helpful as possible. Send us your comments aboutthis book or other IBM Redbooks in one of the following ways:

Use the online Contact us review Redbooks form found at:

ibm.com/redbooks

Send your comments in an e-mail to:

[email protected]

Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


15/256

Copyright IBM Corp. 2008. All rights reserved. 1

Draft Document for Review June 3, 2008 1:55 pm 7643RunPlan.fm

Chapter 1. Planning for installation

This chapter discusses installation planning for WebSphere Process Serverinstallations. This chapter is intended to provide the you with the concepts and

primary considerations for installation.

Although it is possible to install WebSphere Process Server on a WebSphereApplication Server base, this chapter will assume WebSphere Application ServerNetwork Deployment as a base product.

This chapter will also provide concepts for WebSphere ESB within the context ofa WebSphere Process Server installation.

1


16/256

7643RunPlan.fm Draft Document for Review June 3, 2008 1:55 pm

2 Getting Started with WebSphere Process Server and WebSphere ESB Part 3: Runtime

1.1 WebSphere Application Server concepts

WebSphere Process Server and WebSphere ESB are built on top of WebSphereApplication Server technology and inherit its runtime structure and configuration

characteristics. The concepts associated with WebSphere Application Server arecommon for all of these products and are important to understand in order to planfor a WebSphere Process Server or WebSphere ESB environment.

WebSphere Application Server is organized based on the concept of cells,nodes, and servers. While all of these elements are present in eachconfiguration, cells and nodes do not play an important role until you takeadvantage of the features provided with Network Deployment.

The following concepts are key to understanding topologies based onWebSphere Application Server.

The application serveris the primary runtime component in all configurationsand is where an application executes. Application servers have levels ofcapability tailored to the applications they will host. These levels are:

WebSphere Application Server and WebSphere Application ServerNetwork Deployment - designed to run J2EE applications.

WebSphere ESB - includes the functionality of WebSphere Application

Server and can host mediation modules.

WebSphere Process Server - includes the functionality of WebSphereESB servers and can host business integration modules.

In a WebSphere Process Server installation, which includes WebSphereESB, it is common to create all application servers with the WebSphereProcess Server template.

A node is a grouping of application servers for configuration and operationalmanagement on one machine. Nodes are generally associated with aphysical machine. It is possible to have multiple nodes on a single machinebut nodes cannot span machines. A node agent in the node is the contactpoint for the deployment manager during cell administration.

As with application servers, nodes also have levels of capability that supporttheir environment.

Acellis a grouping of nodes into a single administrative domain. A cell canconsist of multiple nodes, which are all administered from a single point (thedeployment manager).

f f 7643R Pl f


17/256

Chapter 1. Planning for installation 3


1.1.1 Profiles

Runtime environments are built by creatingprofiles. Each profile contains filesspecific to that runtime such as logs and configuration files. Profiles can becreated during installation and after. After a profile is created, further

configuration to the runtime environment is done using WebSphereadministrative tools that include scripting, commands, and the administrativeconsole.

Each profile is stored in a unique directory path selected at profile creation time.The default is for the profiles to be stored in a subdirectory of the installationdirectory, but they can be located anywhere. All profiles share the productbinaries.

A profile is created with one of the following levels of function: WebSphere Application Server Network Deployment

WebSphere Enterprise Service Bus

WebSphere Process Server

Profiles for WebSphere Process Server and WebSphere Enterprise Bus areactually profiles built for WebSphere Application Server Network Deployment andaugmented with the process server or ESB function.

Profile typesThere are three profile types used to define server environments:

Stand-alone server: This type of profile creates an application server that ismanaged from its own administrative console. It functions independently fromall other servers and deployment managers.

When the tool your are using to create profiles offers the choice of creating aprofile for multiple environments, the stand-alone server option is associated

with a WebSphere Application Server Network Deployment profile. Theprofiles augmented for additional function are referred to as:

Stand-alone process server profile: A stand-alone server profile thathas been augmented for WebSphere Process Server.

Stand-alone enterprise service bus profile: A stand-alone service busprofile that has been augmented for WebSphere ESB.

Deployment manager: This type of profile creates a deployment managerthat is used to administer nodes that are federated into its cell.

Custom: A custom profile contains an empty node. No application server ordeployment manager is defined by this profile. The typical use for a customprofile is to federate its node to a deployment manager. After federating the

7643RunPlan fm Draft Doc ment for Re ie J ne 3 2008 1 55 pm


18/256



node, use the deployment manager to create a server or a cluster of serverswithin the node.

Augmenting profiles

WebSphere Application Server profiles (both base and Network Deployment)can be augmented to have WebSphere ESB or WebSphere Process Serverfunction. Likewise, WebSphere ESB profiles can be augmented to haveWebSphere Process Server function. However, the profile to be augmented mustexist on a system with a WebSphere Process Server installation.

On distributed and i5/OS systems, augmentation to stand-alone servers orunfederated custom nodes can be done using the Profile Management Tool orthe manageprofiles command.

Custom profiles that have been federated to a cell must be augmented manually.A federated profile must be removed from the deployment manager first, thenaugmented. Removing the node from the deployment manager will restore thenode to the configuration saved prior to using addNode command. Data might belost. The deployment manager profile must also be federated. Then the customprofile can be federated back to the cell. The deployment manager must also beaugmented before federating the node back to the cell. For more information,see:

Augmenting existing profiles (distributed and i5/OS platforms)http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/tins_aug_profiles.html

For information on augmenting profiles on z/OS systems, see

zWPSConfig.sh and zWESBConfig.sh (z/OS platforms)

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/rins_zos_configscript.html

1.1.2 Application server environments

There are two basic topology types for WebSphere environments.

Stand-alone application serversIn astand-alone serverenvironment, each application server acts as a uniqueentity. The cell consists of one node and one application server. The

administration is managed through the application server.

Multiple stand-alone application servers can exist on a machine, either throughindependent installations of the WebSphere Process Server code or by creating

Draft Document for Review June 3 2008 1:55 pm 7643RunPlan fm
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/tins_aug_profiles.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/tins_aug_profiles.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/rins_zos_configscript.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/rins_zos_configscript.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/rins_zos_configscript.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/tins_aug_profiles.html


19/256



multiple application server profiles within one installation. However, WebSphereProcess Server does not provide centralized management or administration formultiple stand-alone application servers. Stand-alone application servers do notprovide workload management or failover capabilities.

Standalone servers are most often used for test environment and fornon-production applications.

Profiles

A stand-alone server for WebSphere Process Server is created by defining anstand-alone process server profile. A stand-alone server for WebSphere ESB iscreated by defining an stand-alone enterprise service bus profile.

Distributed application serversA distributed serverconfiguration enables central administration, workloadmanagement, and failover. In this environment, you integrate one or more nodesinto a cell that is managed by a deployment manager. Administration andmanagement is handled centrally from the deployment manager.

Each node has one or more application servers. The nodes can reside on thesame machine as the deployment manager or on multiple separate machines.Each node has a node agentthat works with the deployment manager to manageadministration processes.

Figure 1-1 on page 6 shows a runtime environment that consists of a single cell,a deployment manager that manages that cell, and two nodes each with twoapplication servers.

7643RunPlan fm Draft Document for Review June 3 2008 1:55 pm


20/256



Figure 1-1 Distributed servers

With a distributed server configuration, you can create multiple applicationservers to run unique sets of applications and then manage those applicationsfrom a central location. However, more importantly, you can clusterapplication

servers to allow for workload management and failover capabilities. Applicationsthat you install in the cluster are replicated across the application servers. Whenone server fails, another server in the cluster continues processing. Workload isdistributed among Web and EJB containers in a cluster using a weightedround-robin scheme.

Profiles

A distributed server environment consists of one deployment manager profileand one or more custom node profiles.

The easiest way to build a new WebSphere Process Server distributedenvironment is to use the deployment environment patterns. Each cell can havemultiple deployment environments configured.

A typical process for creating a new non-productionWebSphere Process Serverenvironment would be:

1. Select a topology based on one of the available deployment environments.

2. Install WebSphere Process Server on the deployment manager host,selecting the deployment environment you want to build and the deploymentmanager option. This will build a deployment manager profile and will prepare

Cell

Server B

DeploymentManager

Server A

Node

Application

ServerApplication

Server

NodeAgent

Server C

Node

Application

ServerApplication

Server

NodeAgent



21/256


a ocu e o e e Ju e 3, 008 55 p 7643RunPlan.fm

the environment, including creating the databases required for WebSphereProcess Server.

3. Install WebSphere Process Server on additional hosts (nodes), selecting thedeployment environment and the custom profile option. This will create acustom profile for each node, federate it to the cell, define the applicationservers on the node, and add the application servers to the appropriatecluster.

The result will be fully functional WebSphere Process Server environment,however, this process gives you limited control over the database configuration.

In a production environment, it is recommended that you create the deploymentmanager first, then use the administrative console to create the deploymentenvironment. This gives you the ability to use multiple databases for the

WebSphere Process Server components.

A typical process for creating a new productionWebSphere Process Serverenvironment would be:

1. Install WebSphere Process Server on the deployment manager host andcreate a deployment manager profile.

2. Install WebSphere Process Server and create a custom profile on each node,allowing the federation to the deployment mangaer to occur during profile

creation.3. Use the administrative console to create a deployment environment. This

allows you to select the nodes to add to each cluster and provides greatercontrol over the database configuration options.

Examples of building topologies based on deployment environment patterns canbe found in Chapter 3, Creating profiles on distributed and i5/OS systems onpage 51.

1.1.3 WebSphere Application Server for z/OS

While WebSphere Application Server for z/OS has the same basic conceptspreviously discussed, it contains a unique process model that enables theproduct to manage many z/OS unique services and provides Quality of Service(QoS). On z/OS, an application server is built using a federation of JVMs, each ina different process that together represents a single server instance. A server iscomposed of address spaces that actually run the code. WebSphere Process

Server is built on this environment and takes advantage of this structure.

Figure 1-2 illustrates how WebSphere processes are structured in a z/OSenvironment.



22/256

p


Figure 1-2 One cell, deployment manager, node on same LPAR, node separated

To understand how WebSphere on z/OS is unique from the distributed platforms,we briefly discuss some of the z/OS-specific concepts.

Address spaceAn address space is the area of successive virtual addresses that z/OS assignsto a user (or separately running program) for executing instructions and storingdata. It is equivalent to a process on distributed platforms.

Control regionThe control region (CR) is basically the only public interface to this collection ofJVMs that, all together, represent a single application server. All requests go

through the CR and the CR forwards them to one of the potentially many servantcontrollers for processing. In short, a CR is like a router or even an addressspace that binds the TCP ports used by the server. A CR does have anembedded JVM, which is the only JVM allowed to receive connections fromthe outside world. Each server has only one CR that is started through a JCLstart procedure.

The requests arrive in the CR process, which then works with the z/OS workloadmanager (WLM) to dispatch the work to the servant regions (Figure 1-3).

MVS ITSO SYS B

Daemon

CR

Node Agent

CR

DMGR

CR A

Daemon

CR

Node Agent

CR

AppServer

CR SR

AppServer

CR SR

MVS ITSO SYS A



23/256


Figure 1-3 Inside the application server

Control region adjunctThe control region adjunct is a specialized servant that interfaces with newservice integration buses to provide messaging services.

Servant regionThe servant region (SR) is where the requests are actually processed and isequivalent to the application server on a distributed environment platform. All theSRs are identical and have the same J2EE level. The SR depends on the CR formany services such as communication, security and transaction control.

When multiple SRs are created, a copy of each application is found in each SRand the CR will forward the requests to the appropriate SR.

zWLMThe z/OS workload manager manages resources to ensure that performancegoals are met. It is a part of z/OS. To differentiate this from the workloadmanagement of WebSphere, we refer to this as zWLM. As the CR receivesincoming requests, it works with zWLM to ensure that these requests areclassified according to organization-defined rules and dispatched appropriatelyto servant regions that can handle the load. zWLM can alter factors to ensurethat performance goals are met, for example, by updating importance levels ofservices classes and starting additional servant regions.

JCL startprocedure

System console

Controllerregion

zWLM

Servant region #1

JVM

Application

Servant region #n

JVM

Application

JCL start

procedure

J2EE application server



24/256


DaemonA daemon server provides the location name service for external clients. There isone daemon per cell per MVS image. If your cell consists of multiple MVSimages, a daemon will be created for each MVS image where your cell exists. Ifthere are two cells on the same MVS image, two daemons will be created. Each

daemon server consists of a single CR.

Daemon servers are started automatically when the first server for the cell onthat MVS image is started. If you kill a daemon, all the servers for that cell on thatMVS image come down.

1.2 Selecting a topology

In order to plan an installation, you need to design the topology you want to build.Choosing the right topology is important regarding future requirements for highavailability, scalability, and performance. The topology selected will determine thenumber of systems you need to install the product on, the profiles you will needto create, and your path through the installation and profile creation process.

This section will describe common topologies, starting with a simple stand-aloneserver topology, and progressing to more complex topologies that have been

identified as common deployment patterns.

1.2.1 Stand-alone server topology

The simplest topology is one that consists of a stand-alone server forWebSphere Process Server and WebSphere Enterprise Service Bus. Allcomponents run on a single server and both modules and mediation modulesrun in the application server.

With this topology, there is no central configuration management. The applicationserver has its own administrative console. There are no workload managementor high availability features with this topology.

Note: For a more in-depth discussion of topologies for WebSphere ProcessServer and WebSphere Enterprise Service Bus topologies, see:

Production Topologies for WebSphere Process Server and WebSphereESB V6, SG24-7413

z/OS Getting Started: WebSphere Process Server and WebSphereEnterprise Service Bus V6, SG24-7378



25/256


This topology is most often seen for non-critical applications and in testenvironments.

Figure 1-4 Stand-alone server topology

1.2.2 Deployment environment patterns

A set of deployment environment patterns have been identified that representcommon deployment scenarios. WebSphere Process Server provides built-insupport for these patterns in the installation process, the profile creation tools,and administrative console. These patterns assist in creating the profiles andconfiguration settings that define complex deployment environments, includingthe creation of the supporting databases and clusters.

The three patterns are:

Single cluster pattern

Remote messaging pattern

Remote messaging and remote support pattern

Using this support is recommended on distributed and i5/OS systems. Thepatterns defined by this support are also legitimate patterns for a z/OSenvironment, but at the time of this publication, the use of the deployment

Example: For an example of this topology, see 3.2, Standalone WebSphereProcess Server on page 56.

Node1

WebSphere Process Server

Application

Modules

Mediation modules

Support

Messaging



26/256


environment options in the profile creation tool and the administrative consolewere not recommended.

Cluster pattern componentsThe patterns use application server clustering to provide failover and loadbalancing for components in the topology. The support for these components hasbeen broken down into the following categories:

Messaging components that support the WebSphere Process Server andWebSphere ESB environment:

Service Component Architecture (SCA) application bus. This bus exists asa default location for the queues that are used by JMS export components.

SCA system bus

Business Process Choreographer bus

Common Event Interface (CEI) bus

Support components for the WebSphere Process Server and WebSphereESB environment:

CEI server

Business Rules Manager

BPC Explorer and BPC Observer

Application components

Application deployment target

1.2.3 Single cluster pattern

The single cluster pattern is the simplest of the clustering patterns. It defines onecluster that supports applications, messaging, and the support components.

Using patterns for WebSphere Process Server and WebSphere ESB:

When used to create a WebSphere Process Server environment, theapplication deployment target can host modules, mediation modules or both.When used to create a WebSphere ESB environment, the application

deployment target can host mediation modules only.

For examples of combining these patterns to create more complexdeployment environments, see Chapter 3, Creating profiles on distributedand i5/OS systems on page 51



27/256


This pattern is recommended for the scenarios where most invocations aresynchronous. Messaging use should be minimal and applications role shoulddominate the use cases.

The cluster can consist of multiple nodes and multiple servers on each node. A

cluster consisting of WebSphere Process Server nodes and servers can hostboth business integration and mediation applications. Applications are installedto the cluster.

Figure 1-5 Single cluster pattern

1.2.4 Remote messaging pattern

The remote messaging pattern defines one cluster for application deploymentand one remote cluster for the messaging infrastructure. The common eventinfrastructure and other support applications are configured on the applicationdeployment cluster. This pattern is recommended for scenarios involving heavyasynchronous invocations. However, this is not ideal when other supportingruntime components are actively involved.

Applications are installed to the application deployment cluster.

Example: For an example of this topology, see 3.3, Building a deploymentenvironment using a pattern on page 66.

Node1

WebSphere

ProcessServer

Node2

WebSphere

ProcessServer

WebSphereProcessServer


Cluster1

Application

Modules

Mediation modules

Support

Messaging



28/256


In this pattern, the messaging cluster is assigned as a member of the serviceintegration buses that provide support for the WebSphere Process Server andWebSphere ESB infrastructure. The SCA.Application bus has one bus member(the messaging cluster) by default.

Figure 1-6 Remote messaging pattern

1.2.5 Remote messaging and remote support pattern

The Remote messaging and remote support pattern defines one cluster for

application deployment, one remote cluster for the messaging infrastructure, andone remote cluster for the common event infrastructure and other supportapplications.This pattern performs well, providing the most scalable, flexible andversatile topology pattern. If in doubt, select this pattern.

Node1


Node2


Cluster1



Cluster2

Messaging

Application

Modules

Mediation modules

Support



29/256


Figure 1-7 Remote messaging and remote support pattern

1.2.6 Web servers

WebSphere Application Server provides Web server plug-ins that work with aWeb server to route requests from the Web server to the proper applicationserver. A Web server plug-in is specific to the type of Web server. It is installedon the Web server machine and configured in the Web server configuration.

A plug-in configuration file generated on the application server and placed on theWeb server is used for routing information. In order to manage the generationand propagation of these plug-in configuration files, Web servers are defined to

the WebSphere configuration repository. In some cases, Web serverconfiguration and management features are also available from the WebSphereadministrative tools.

Example: For an example of this topology, see 3.3, Building a deploymentenvironment using a pattern on page 66.

Node1


Node2




Cluster1

Cluster2



Cluster3

Messaging

Support

Application

Modules

Mediation modules



30/256


Figure 1-8 Remote messaging and remote support pattern

Managed Web servers versus unmanagedA supported Web server can be on a managed node or an unmanaged node,depending on the environment on which you are running the Web server.

Basic administrative functions are provided in the WebSphere administrativetools for all supported Web servers. For example, generation of a plug-inconfiguration can be performed for all Web servers. If the Web server is definedon a managed node, automatic propagation of the plug-in configuration can beperformed using node synchronization. If the Web server is defined on an

unmanaged node, automatic propagation of a plug-in configuration is onlysupported for IBM HTTP Servers.

Some additional administrative console tasks are supported for IBM HTTPServers on managed and unmanaged nodes. For example, you can start IBMHTTP Servers, stop them, terminate them, display their log files, and edit theirconfiguration files.

Unmanaged nodes

An unmanaged node does not have a node agent to manage its servers. In astand-alone server environment, you can define one Web server and it, bynecessity, resides on an unmanaged node. In a distributed server environment,Web servers defined to an unmanaged node are typically remote Web servers.

Node1

WebSphere

ProcessServer

WebServer

Node2

WebSphere

ProcessServer



Cluster1

Cluster2



Cluster3

Messaging

Support

ApplicationModules

Mediation modules



31/256


If the Web server is defined to an unmanaged node, you can do the following:

1. Check the status of the Web server.

2. Generate a plug-in configuration file for that Web server.

If the Web server is an IBM HTTP Server and the IHS Administration server is

installed and properly configured, you can also:

a. Display the IBM HTTP Server Error log (error.log) and Access log(access.log) files.

b. Start and stop the server.

c. Display and edit the IBM HTTP Server configuration file (httpd.conf).

d. Propagate the plug-in configuration file after it is generated.

You cannot propagate an updated plug-in configuration file to a non-IHS Webserver that is defined to an unmanaged node. You must install an updated plug-inconfiguration file manually to a Web server that is defined to an unmanagednode.

Managed nodes

In a distributed server environment, you can define multiple Web servers. TheseWeb servers can be defined on managed or unmanaged nodes. A managed nodehas a node agent. If the Web server is defined to a managed node, you can do

the following:1. Check the status of the Web server.

2. Generate a plug-in configuration file for that Web server.

3. Propagate the plug-in configuration file after it is generated.

If the Web server is an IBM HTTP Server (IHS) and the IHS Administrationserver is installed and properly configured, you can also:

a. Display the IBM HTTP Server Error log (error.log) and Access log

(access.log) files.b. Start and stop the server.

c. Display and edit the IBM HTTP Server configuration file (httpd.conf).

How are nodes and servers defined?During the installation of the plug-in, the Plug-ins installation wizard creates aWeb server configuration script named configure. Thisconfiguration script is used to define the Web server definition and, if necessary,

the node definition to WebSphere.

If a Web server definition already exists for a stand-alone application server,running the script does not add a new Web server definition. Each stand-alone



32/256


application server can have only one Web server definition. A distributed serverenvironment, on the other hand, can have multiple Web server definitions. Thescript creates a new Web server definition unless the Web server name is thesame.

The Plug-ins installation wizard stores the script in the /bindirectory on the Web server machine. If the plug-in is installed locally (on thesame machine as the application server), the configuration script will be runautomatically.

For remote installations, you must copy the script from the Web server machineto the WPS_install_root/bin directory on the application server machine forexecution. The script runs against the default profile. If one machine is runningunder Linux or UNIX and the other machine is running under Windows, use

the script created in the /bin/crossPlatformScripts directory.

If you are federating a stand-alone application server into a cell, any Web serverdefinitions created for a stand-alone application server will be lost when they arefederated. If you are creating a distributed server environment this way, wait untilafter federating your application servers to create Web server definitions.

For more information about the installation of Web server plug-ins and how theWeb server definitions scripts are generated and executed, see WebSphereApplication Server V6.1: Planning and Design, SG24-7305.

1.3 Planning for installation

In this book, we will show examples of various installation and profile creationscenarios. However, this is not intended to be a comprehensive planning guide.

Please refer to the WebSphere Process Server V6.1.0 information center formore in-depth planning and installation topics:

Planning for WebSphere Process Server (distributed and i5/OS)

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cpln_plancons.html

Note: Always open a new command window in which to execute theconfigurescript. There is a potential conflict between ashell environment variable, the WAS_USER_SCRIPT variable, and the realdefault profile. The script always works against the default profile. However, ifthe WAS_USER_SCRIPT environment variable is set, a conflict arises as thescript attempts to work on the profile identified by the variable.


Pl i f W bS h P S ( /OS)
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cpln_plancons.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cpln_plancons.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cpln_plancons.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cpln_plancons.html


33/256


Planning for WebSphere Process Server (z/OS)

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cpln_plancons.html

In addition, the following document provides valuable guidance in planning for a

WebSphere for z/OS installation

WebSphere z/OS V6 -- WSC Sample ND Configuration

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100653

1.3.1 Prerequisites

Before starting the installation process, check the following Web site to makesure you have met the prerequisites:

WebSphere Process Server detailed system requirements

http://www-1.ibm.com/support/docview.wss?uid=swg27006205

1.3.2 User ID authorities for installation

The user ID used for installation is preferably one with Administrator authorities.

However, it is possible to use a non-root user ID. Non-root installation allowsyou to perform the install as a non-root user on Linux or UNIX operating systems,or as a non-administrator on Windows.

If you decide to use a non-root user ID to perform the installation, be sure toreview the following information center articles:

Limitations of non-root installers

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.

websphere.nd.multiplatform.doc/info/ae/ae/rins_nonroot.html Granting write permission of files and directories to a non-root user for profile

creation

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/iins_nonrootprofile.html

To install on an i5/OS system, you must use a valid i5/OS user profile for thatsystem. The user profile must have *ALLOBJ and *SECADM authorities. Without

these authorities, the installation will fail.To install on z/OS, you must have administrator authority.


1 3 3 Installation methods
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cpln_plancons.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cpln_plancons.htmlhttp://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100653http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100653http://www-1.ibm.com/support/docview.wss?uid=swg2700620http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rins_nonroot.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rins_nonroot.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/iins_nonrootprofile.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/iins_nonrootprofile.htmlhttp://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100653http://www-1.ibm.com/support/docview.wss?uid=swg2700620http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cpln_plancons.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/iins_nonrootprofile.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rins_nonroot.html


34/256


1.3.3 Installation methods

Before starting the install, you should be aware of the options you have for themethod of installation.

Distributed systemsInstallation on distributed systems can be done interactively or silently. Interactiveinstallation is initiated by executing the launchpad interface and selecting theoption to install WebSphere Process Server. An example of this can be found inChapter 2, Installation on distributed and i5/OS systems on page 37.

To perform a silent install, you build a response file and execute the installcommand.

Both installation methods install the binary files and (optionally) allow you tocreate one profile. Additional profiles can be created after installation using thePMT ormanageprofiles command.

For more information about installation, see:

Installing and configuring WebSphere Process Server (distributed and i5/OS)

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.html

i5/OSInstallation on i5/OS can be done using one of the following methods:

Interactively from a Windows workstation

Silently from a Windows workstation

Silently on the i5/OS system

Examples of an interactive installation and a silent installation on i5/OS can beChapter 2, Installation on distributed and i5/OS systems on page 37.

The installation installs the binary files and optionally, allows you to create oneprofile. Additional profiles can be created after installation using the PMT on aWindows workstation or themanageprofiles command on i5/OS.

For more information about installation, see:

Installing and configuring WebSphere Process Server (distributed and i5/OS)

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.html


z/OS
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/welcome_wps_ins.html


35/256


z/OSInstallation on z/OS is done in phases.

1. Use SMPE to install and configure WebSphere Application Server for z/OS.

2. Use SMP/E to install the WebSphere Process Server product binaries into an

HFS or zFS file system.3. Create the WebSphere Application Server profiles required for the topology

you select using the customization dialog or zPMT.

4. Run the zSMPInstall.sh script to install WebSphere Process Server to eachWebSphere Application Server profile directory.

5. Create the appropriate databases and storage groups required byWebSphere Process Server.

6. Run the zWPSConfig.sh to configure the server as a process server, enablingthe server to handle business processes and mediations.

For information on these steps, see the information center, starting with thisarticle:

Installing and configuring WebSphere Process Server (z/OS)

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/iins_zos_welcome.html

1.3.4 Installation type (distributed and i5/OS)

On distributed and i5/OS systems, you have three options for installation.

Typical Installation: A full installation of WebSphere Process Server. Thisinstallation path allows you to define a WebSphere Enterprise Service Bus orWebSphere Process Server environment consisting of one stand-aloneserver, a deployment manager, or a custom profile during the installation

process. The common database is created using the default for the operatingsystem. You may also elect to create no profiles during installation.

Note: When you order WebSphere Process Server for z/OS you get theWebSphere ESB runtime that allows you to run mediations in aWebSphere Process Server configured server. You can't build an ESB-onlyserver. There is a zWESBConfig.sh script shipped with WebSphereProcess Server, but it doesn't work.

In order to build an ESB-only server you have to order, SMP/E install andconfigure the WebSphere ESB for z/OS product separately.


Deployment Environment Installation: A full installation of WebSphere
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/iins_zos_welcome.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/iins_zos_welcome.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/iins_zos_welcome.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/iins_zos_welcome.html


36/256


Deployment Environment Installation: A full installation of WebSphereProcess Server. This installation choice guides you through the process ofsetting up a deployment environment. You can choose a deployment managerbased on a deployment environment pattern or continue to define adeployment environment that you have already created. This option allows

you to select from a limited list of database providers for the commondatabase. After installation, you create additional profiles using the ProfileManagement Tool or manageprofiles command.

Client Installation: A partial installation of WebSphere Process Server thatallows you to run a client application that interacts with a WebSphereEnterprise Server Bus and WebSphere Process Server within the same cell.

1.3.5 Selecting additional features

During the install, you will have the option of selecting the following features thatare not installed by default:

Business rule beans (deprecated)

This option is available on all platforms with the exception of i5/OS.

This function has been carried forward from WebSphere Business IntegrationServer Foundation, version 5.1.1. It will not be supported in future versions ofWebSphere Process Server.

Business rule beans has been replaced by business rules.

For more information, see:

Overview of business rules

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cadm_busiru_overview.html

Deprecated features

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.html

Extended messaging service (deprecated)

This option is available on all platforms with the exception of i5/OS.

This function has been carried forward from WebSphere Business IntegrationServer Foundation, version 5.1.1. It will not be supported in future versions ofWebSphere Process Server. Instead of using the Extended MessagingService and its associated tools, the standard JMS APIs, or equivalent

messaging technologies should be used.


Deprecated features


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/co
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cadm_busiru_overview.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cadm_busiru_overview.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cadm_busiru_overview.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.html


37/256


p //p / / p/ / p /m.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.html

WebSphere Process Server samples

The Samples Gallery contains sample that demonstrate WebSphere

technology. They are appropriate for demonstration and developmentenvironments, but are not recommended for production environments.

For more information on educational material, see:

Samples and tutorials

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/covw_sample_tutorial.html

1.3.6 Root directoryYou will need to specify a location for the installation. The default root directoriescan be found in:

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/rins_installation_paths.html

1.3.7 Creating profiles during installation

Determining the profiles you will need will depend on the topology you plan torun. With the exception of stand-alone topologies, every topology will needmultiple profiles. With distributed and i5/OS installations, you have the option ofcreating a profile during installation. After installation, you can create additionalprofiles using the manageprofiles command or the Profile Management Tool.

Creating the first profile during installation is simply a shortcut to get you started.

1.3.8 Installing recommended maintenance

After installation, you should install the Update Installer for WebSphere Softwareand install all recommended fixes. The Update Installer can be installed from thelaunchpad.

Recommended fixes can be found at:

Recommended Fixes for WebSphere Process Server

http://www-1.ibm.com/support/docview.wss?rs=2307&uid=swg27006649

Mandatory critical fixes for WebSphere Process Server for z/OS V6.1


http://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&q1=P
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/covw_sample_tutorial.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/covw_sample_tutorial.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/rins_installation_paths.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/rins_installation_paths.htmlhttp://www-1.ibm.com/support/docview.wss?rs=2307&uid=swg27006649http://www-1.ibm.com/support/docview.wss?rs=2307&uid=swg27006649http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/rins_installation_paths.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/rins_installation_paths.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/gmig_deprecationlist.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/covw_sample_tutorial.htmlhttp://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&q1=PK59140&uid=swg27011675&loc=en_US&cs=utf-8&lang=enhttp://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&q1=PK59140&uid=swg27011675&loc=en_US&cs=utf-8&lang=en


38/256


K59140&uid=swg27011675&loc=en_US&cs=utf-8&lang=en

1.4 Planning for profiles

Decisions to be made before creating a profile are related to the topology andruntime environment. These decisions are logically separate from those made forinstallation. However, since you can create profiles during installation, thesetopics should be considered during your initial planning.

Profiles on distributed and i5/OS systems can be created in one of the followingways:

Using the Profile Management Tool (a wizard-driven tool) During installation

Using the manageprofiles command

On z/OS systems, the following path is recommended for creating:

1. Use the zPMT to build JCL required to create the WebSphere NetworkDeployment profiles.

2. Augment the profiles for WebSphere Process Server or WebSphere ESB.

Configuring WebSphere Application Server for z/OS requires a fair amount ofplanning and coordination. For example, when defining multiple deploymentmanagers or application servers on a single machine or LPAR, you need toensure that the ports and names you select for each are unique and the z/OSenvironment variables, generated jobs, and so on, were all set up properly. Westrongly recommend you spend time planning the installation and if possible,practice by configuring a stand-alone application server using the default options.

1.4.1 Planning for databases

WebSphere Process Server uses databases during runtime to support theexecution of business processes and mediations. The set of tables that make upeach database can be stored in a separate physical database, or can be acombined with others in a larger common database. The database configurationyou choose will depend on the features that you use and performanceconsiderations. The databases can be created as part of the profile creation, or

you can choose to delay creating them until after the profile is created but beforeit is started.

The following is the list of logical databases:


WebSphere Process Server components and the enterprise service bus use
http://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&q1=PK59140&uid=swg27011675&loc=en_US&cs=utf-8&lang=enhttp://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&q1=PK59140&uid=swg27011675&loc=en_US&cs=utf-8&lang=enhttp://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&q1=PK59140&uid=swg27011675&loc=en_US&cs=utf-8&lang=en


39/256


a common database. The default name for this database is WPRCSDB.

A Common Event Infrastructure database, referred to as the CEI database.The default name for this database is EVENT.

A Business Process Choreographer database, referred to as the BusinessProcess Execution database. The default name for this database is BPEDB.

A Business Process Execution Observer database, referred to as theobserver database. The default name for this database is OBSRVDB.

A database for the messaging engines. The default name for this database isMEDB.

Detailed requirements for database products can be found in:

WebSphere Process Server detailed system requirements

http://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&uid=swg27006205

Deciding when and how to create the databasesThe minimal configuration for a WebSphere Process Server or WebSphere ESB

configuration is the common database that contains all the database tables. Thisis not recommended for a production system. This is the configuration you willget if you use the Profile Management Tool to create the databases. In this seriesof books, we will use this configuration.

For production systems, it is recommended that you create the databases andupdate the appropriate data sources manually. This gives you maximum controlover the location and grouping of database tables. To do this, you choose theoption to delay the creation of the databases when you create the profiles. This

will cause scripts to be generated to help you create the common and eventdatabases, and will create the data sources based on information you provideduring profile creation. Create the databases using the scripts or your owncommands and update the appropriate data sources.

i5/OS: On series, there is a single global database in which you define all

schemas for all functional components. You must make sure that all schemanames are unique within the logical partition (LPAR).

There are also unique considerations for selecting the driver needed toconnect remotely to an i5/OS database server. For more information, see:

Database specifications

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_db_specs.html


Finding the database scripts and specifications
http://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&uid=swg27006205http://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&uid=swg27006205http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_db_specs.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_db_specs.htmlhttp://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&uid=swg27006205http://www-1.ibm.com/support/docview.wss?rs=2307&context=SSQH9M&uid=swg27006205http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_db_specs.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_db_specs.html


40/256


You can find scripts for the common database, the BPEDB and the OBSRVDB inWPS_install_root/dbscripts. These scripts are available after install.

During the profile creation with the Profile Management Tool, a new set of scripts

is generated into profile_root/dbscripts. These scripts create the commondatabase with the attributes you specified during profile creation.

Scripts to create the Business Process Choreographer tables and schema aregenerated when you configure BPC. This can be during or after profile creationor as part of the deployment environment configuration. These are also stored inprofile_root/dbscripts. You will need to create the BPEDB database and then runthese scripts.

For the messaging engines you can use the sibDDLGenerator script to generatethe database scripts. Information about the messaging engine databases can befound at:

Messaging engine database specifications

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_messaging_engine_db_specs.html

Messaging engine database specifications (z/OS)

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.i

bm.websphere.wps.z.610.doc/doc/cins_messaging_engine_db_specs.html

Common database (WPRCSDB)WebSphere Process Server components and the enterprise service bus use acommon database. The default name for this database is WPRCSDB.

The common database is used by the following product components:

Recovery

Relationship service Mediation Application scheduler Customization (selector and business rule group) EventSequencing (LockManager) WebSphere ESB Message Logger primitive

Depending on the database provider you select, you have the option to have thedatabase created automatically during profile creation. The option to create a

new database is disabled for the following database types: DB2 for z/OS and OS/390 v7 DB2 for z/OS v8


DB2 for z/OS v9 Oracle 9i and 10g
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_messaging_engine_db_specs.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_messaging_engine_db_specs.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cins_messaging_engine_db_specs.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cins_messaging_engine_db_specs.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cins_messaging_engine_db_specs.htmlhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_messaging_engine_db_specs.html


41/256


Oracle 9i and 10g

If you elect to defer the database creation, scripts will be created for your use indefining the database. The information you enter for the existing database(whether it actually exists yet or not) must be correct since it will be used tocreate the data source and the scripts. The scripts are located inprofile_root/dbscripts/CommonDB/dbType/dbName.


Common database specifications

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.610.doc/doc/cins_common_db_specs.html

Common database specifications (z/OS)http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.z.610.doc/doc/cins_common_db_specs.html

Table 1-1 shows the database provider options for the Common database.

Table 1-1 Options for common database on distributed systems

Database

product

DerbyEmbedded

Install (typical) - standalone profile (the default - no option) PMT (typical)- standalone profile (the default - no option) PMT (advanced)- standalone profile Administrative console (deployment environment)

Derby Network Install (typical) - deployment manager (the default - no option) Install (Deployment Environment) - deployment manager

PMT (advanced)- all profiles Administrative console (

gettingstarted with wps&esb part3

Documents