Business Process Manager for z/OS V8.0.1: Process …...Stack Environment including WAS FPs & BPM Advanced: PS V8 –Create BPM V8 DMGR-Import Spreadsheet Response file (DMGR)-Review

© 2012, 2013 IBM Corporation

IBM Business Process Management

1

Business Process Manager for z/OS V8.0.1: Process ServerUnit 3 - Network Deployment Configuration

Single Cluster Topology

John Hutchinson, IBM Advanced Technical [email protected]

To retrieve the latest copy of this slide set, go to the following url: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS5030

Updated Mar. 01, 2013

B#CELLB#NODEA

ServerB#SR01A

DaemonB#DEMN

Node AgentB#AGNTA

Deployment ManagerB#DMGR

839 DB2Tables

B#CELLB#NODEA

ServerB#SR01A

DaemonB#DEMN

Node AgentB#AGNTA

Deployment ManagerB#DMGR

839 DB2Tables

What you Will build 891 DB2

Tables

mailto:[email protected]



2

BPM Integration Configurations – Wildfire Class

Team 1: 192.168.17.201 = wg31

Team 2: 192.168.17.202 = wg31

Team 3: 192.168.17.203 = wg31

Team 4: 192.168.17.204 = wg31

Team 5: 192.168.17.205 = wg31

. . .

z/OSB1SR01ProcessServer

DB2


DB2


DB2


DB2

pcsr01aProcessCenterServer

zLinux – 192.168.17.232wpspctr.wsclab.washington.ibm.com

Repository

DB2 z/OS

Process Servers on z/OS in WSLPLEXTeam 1 Team 2 Team 3 Team 4

Process Center: WAS AppServer run time

where Process Designer & Integration Designer share assets to develop business

processes interactively.

PD = graphical tool to create

business processes

IID = graphical tool to configure

business processes with resources like

DB2, CICS (WID)

Process Servers are WAS Servers with

Business Integration Services

BPM Repository = DB2 Database Similar to

BPM Database on z/OS192.168.17.215

Deploy

Publish

Top-Down

Process Center

Bottom-Up

Save



3

Configuration Outline1. Planning & Prep: use the Spreadsheet to create response files

– Use Installation Manager to lay down the WAS, WCT & BPM code.

2. Use WCT/zPMT to create Configuration Jobs

3. Configure Security Profiles (TSO)

4. Create & Augment Deployment Manager (TSO)

5. Create Database & DB2 Tables (USS Telnet)

6. Create, Augment & Federate Empty Node (TSO)

7. Create Cluster w/ Deployment Environment (Browser: ISC Wizard)

8. Update Variables & Bootstrap ProcessServer Database (USS Telnet)

9. Validate Configuration & Run Sample Jobs (Browser: ISC, BPE)

(There’s a reason for this order. i.e., can't do #5 before #4 or after #6...)



4

IBM Process Server Components

Cluster (1) Database (15 data sources)

– Common WPS & ESB (2)– Business Process Container – Business Space (2)– Process Server (2)– Data Warehouse (2)– Messaging Engines (6)

SI Buses & MEs (6)– SCA System & Application bus– CEI bus, BPC bus– Process Server, Data Warehouse

IBM BPM Applications (30+)– Business Flow Manager, Human Task

Manager, BPE Container, ...– BPC Explorer & Observer, Business Rules

Manager– Business Space, IBM BPM Teamworks– Process Portal, Process Admin, Performance

Data Warehouse – Hiring Sample, WPS Echo, WPS Human Task

One WebSphere z/OS Server

Controller RegionServant Regions

Adjunct Region

Messaging Engines

Embe

dded

HTT

P Se

rver

Mes

sagi

ng

zWLM

HTTP

SIB

Web container EJB containerServlets JSPs EJBs

Web Services Engine

WebSphere PlatformMessaging dispatch

Data replication

Name server

Dynamic cache

Security

Business Process Container

Human Task Container

DB2 or Cloudscape

Messaging EnginesMessaging

EnginesMessaging Engines

Servant Regions


Web Services Engine


Data replication

Name server

Dynamic cache

Security



Servant Regions


Web Services Engine


Data replication

Name server

Dynamic cache

Security



Servant Regions (JVM each)


Web Services Engine


Data replication

Name server

Dynamic cache

Security



BPC

Bus

SCA

.APPLIC

ATIO

N B

us

SCA

.SYSTEM B

us

CEI B

us

Fabric Bus

Monitor B

us

One WebSphere z/OS Server

Controller RegionServant Regions

Adjunct Region

Messaging Engines

Embe

dded

HTT

P Se

rver

Mes

sagi

ng

zWLM

HTTP

SIB


Web Services Engine


Data replication

Name server

Dynamic cache

Security




Web Services Engine


Data replication

Name server

Dynamic cache

Security



DB2 or Cloudscape

DB2 or Cloudscape

Messaging EnginesMessaging

EnginesMessaging Engines

Servant Regions


Web Services Engine


Data replication

Name server

Dynamic cache

Security




Web Services Engine


Data replication

Name server

Dynamic cache

Security



Servant Regions


Web Services Engine


Data replication

Name server

Dynamic cache

Security




Web Services Engine


Data replication

Name server

Dynamic cache

Security



Servant Regions (JVM each)


Web Services Engine


Data replication

Name server

Dynamic cache

Security




Web Services Engine


Data replication

Name server

Dynamic cache

Security



BPC

Bus

SCA

.APPLIC

ATIO

N B

us

SCA

.SYSTEM B

us

CEI B

us

Fabric Bus

Monitor B

us

BPC

Bus

SCA

.APPLIC

ATIO

N B

us

SCA

.SYSTEM B

us

CEI B

us

Fabric Bus

Monitor B

us



5

1. Planning cannot be over-emphasized Configuration topologies

– # of Clusters, # of cluster members (Systems) Hardware requirements

– CPUs, Memory, (64 bit JVM)– Disk storage (14,000 cyl = 1.4 x 3390-9)

- 1500 cyl. for each Node HFS/zFS(Additional 1500+ for each back-up)

- 7700 cyl. for DB2 Tablespaces Names for

– Cells, Nodes, Servers, Clusters, – User & Group IDs, etc.– z/OS Dataset Aliases, & Space allocations

UNIX file systems (use zFS)– Directories & files (ownerships & permissions)

DB2 components & Names for . . .– Databases, Storage groups, Schemas, BPs, ..

Security Identities, – User Ids, GroupIDs, Auth. Aliases– EJBROLEs– Use Federated Repository w/RACF Bridge

(We will make these decisions for you, but when you get home...)

LPAR A LPAR B

Cluster

Mobile DMGR

CFShared Data

OSA OSA OSA OSA

VIPA VIPA

Appl Appl

RRS - Res. Recovery Svcs. RRS - Res. Recovery Svcs.

SAF, WLM, IRD, JES, etc. SAF, WLM, IRD, JES, etc.

DVIPA + Sysplex Distributor

CICS IMS MQ DB2 CICS IMS MQ DB2

WOLA

LPAR A LPAR B

Cluster

Mobile DMGR

CFShared Data

OSA OSAOSAOSA OSAOSA OSA OSAOSAOSA OSAOSA

VIPAVIPA VIPAVIPA

ApplAppl ApplAppl

RRS - Res. Recovery Svcs.RRS - Res. Recovery Svcs. RRS - Res. Recovery Svcs.RRS - Res. Recovery Svcs.

SAF, WLM, IRD, JES, etc.SAF, WLM, IRD, JES, etc. SAF, WLM, IRD, JES, etc.SAF, WLM, IRD, JES, etc.

DVIPA + Sysplex DistributorDVIPA + Sysplex Distributor

CICS IMS MQ DB2 CICS IMS MQ DB2CICS IMS MQ DB2CICSCICS IMSIMS MQMQ DB2DB2 CICS IMS MQ DB2CICSCICS IMSIMS MQMQ DB2DB2

WOLA



6

Process Server Configuration Spreadsheet (Techdoc WP102075)

Each team has a unique IP host Addr which will use as its host name to identify it to the Process Center:

Note: Each team will have a unique Cell Prefix: B1, B2, B3, …



7

Spreadsheet Creates 5 Documents:

zPMT: Response file for Deployment Manager

Schema defsFor DBA

zPMT: Response File forEmpty Node

Click on Tabs, and Buttons to save the Response files

ISC: Deployment Environment Wizard

dbDesign file forDbDesignGenerator

and DE Wizard

Save these files in the C:\wpswork\ Directory andFTP the dbdesign file to z/OS.



8

Spreadsheet Modified to create only one Cluster Member



9

2. Create Configuration Jobs for Deployment Manager & Empty Node Stack Environment including WAS FPs & BPM Advanced: PS V8

– Create BPM V8 DMGR- Import Spreadsheet Response file (DMGR)- Review Panels- “Process” when complete to Generate and FTP Jobs

– Create BPM V8 Custom Node- Import Spreadsheet Response file (Empty Nodes)- Review Panels- “Process” when complete to Generate and FTP Jobs



10

3. Setting up Security Profiles● The standard BBO*BRAK jobs do not include the following:

● -- Administrator's userID password not set ● -- STARTED profiles for servers (because created Empty Nodes)

● The DORAC800 exec from Techdoc WP101427 does both, plus the profiles done by the standard BBOSBRAK, BBODBRAK & BBOMBRAK jobs.● – Don't run any of the BBO%BRA% jobs, except for BBODBRAM to create

Home directories.● We provide the following jobs in USER1.WAS.CNTL:

–RUNRC800 – runs the DORAC800 exec in USER1.WAS.DATA

–B#RACUID - Defines the RACF User IDs for BPM

–B#EJBROL – Defines the EJBROLE profiles for BPM



11

4. Create / Configure DMGR

Run Configuration Jobs created by the PMT:– BBOSBRAK – Define RACF Users & Groups

- (You already ran the RUNRC800 job in USER1.WAS.CNTL)– BBOSBRAM – Create Home Directories – BBODBRAK – Create RACF Profiles & Permissions (Replaced with RUNRC800)

– BBODCFS – Create zFS– BBODHFSA – Populate zFS– BBOWWPFD – Create Profiles– BBODPROC – Copy Proclib members– BPZAUGD – Augment profiles with BPM: ProcessServer

Next: Configure the Cell-scoped Database tables.



12

5. Create DB2 Database Tables Generate sql templates with the .dbDesign file from the Spreadsheeet:

– cd /wasv8config/b0cell/b0dmnode/DeploymentManager/util/dbUtils– Run DbDesignGenerator.sh -g /u/user1/wpswork/b0Cell.dbdesign r) for

createDB2.sh

Run this command in USS (with leading period & space): . db2setup.sh

Create DB2 StoGroup & databases & GRANTs– Use the b0cell.sql file from the Spreadsheet

Create Cell-scoped Database Tables (before starting Dmgr) cd <Profile_Root>/dbscripts/<Cell_Name>DBcreateDB2.sh -DBAlias b0ADMIN -RunSQL

Create Cluster-scoped database tables (before starting bootstrapProcessSvr)cd <Profile_Root>/dbscripts/<Cluster_Name>DB– createDB2.sh -DBAlias b0ADMIN -RunSQL



13

6. Create Empty (Custom) Node

Run Custom Node Configuration Jobs– BBOSBRAK & BBOMBRAK – BBOSBRAM – Redundant with same job run for the Dmgr– BBOMCFS – Create zFS– BBOMHFSA – Populate zFS– BBOWWPFM – Create Profiles– BBOMPROC – Copy Procs – BPZAUGN – Augment with BPM: PS

< Start DMgr >– BBOWMNAN – Federate Empty Node (Change JOB card to use Administrator’s UserID)

Next: Create a Cluster with the DE Wizard



14

7. Create Deployment Environment Cluster– Use .deploy & .dbDesign files from spreadsheet

for definitions (Cluster, Data sources, etc.).– Next, Next, Next, & Generate the Cluster



15



16

8. Update Deployment EnvironmentUpdate WAS Ports & BPM Configuration with WpsUpdate.py script

cd /wasv8config/B0cell/B0dmnode/DeploymentManager/profiles/default/bin ./wsadmin.sh -conntype SOAP -host wg31.washington.ibm.com -port 7502 \

-lang jython -user b0admin -password b0admin \-f ../../../../wassmpe/zOS-config/samples/WpsUpdate.py \-node b0nodea -server b0sr01a -ports 7540 -cluster b0sr01

Note the order of parameters:• Before the -f is for wsadmin.sh• After the -f is for the py script

BootStrap ProcessServer Databasecd to <DMGR_PROFILE_ROOT>/bin (same as above)bootstrapProcessServerData.sh -clusterName b0sr01

– Full Node Re-synchronization is required (re-cycle Dmgr & NodeAgent)



17

9. Installation Verification Does the Server start, and are all SI Buses active? (See Server Logs.) AdminConsole (ISC) – Validate the Applications, SI Buses & Messaging

Engines & JDBC Resource Data sources Install the WPSHumanTask.ear, Start it and Test it using the url:

http://wg31:7547/WPSHumanTaskWeb Go to the BPC explorer worklist: http://wg31:7547/bpc Select “My To-dos”, then select the work item, and click on “Work on”.



18

Enough Talk – Let's do the lab...