Home

"user manual"

1. E View max HETE E Class Resources information e Page 1 of3 E Smart_Bank WLM Selected Service Class Resources information 8 Teler Managed Service Goal Goal Duration Average Perform Authentification System Class Percentile Importance Value Response Time Inde a E Banking BAPLEX BAOT MVSSYS_ BAT_DISC 1 Diseret ja o cics BAPLEX BAO1 MVSSYS BAT_3V30 1 Velocio O Medium 30 0 0 DB2 BAPLEX BA01 MVSSYS BAT_3V40 1 Velocio 0 Medium 40 Oo 0 MaQSeries BAPLEX BAOLMVSSYS BAT 3V50 1 Velocio 0 0 0 TOR NE ST Webs A Teller Charl 3 7 Views ATM Table Views a Mg Web El MUM Selected Service as zBank GDPS H Managed Service Goal Duration LE PROCESS SO4 System Class Percentile Importance Value Re _ BAPLEX B BAOUMYSSYS BAT_DISC 1 Discret _ 0 nia 0 0 E pao BAPLEX BA01 MYSSYS BAT_3V30 4 Velocio 0 Medium 30 0 efi 4 gt F Query 4 Filters E Thresholds Az Style Filters Service Class 84T_DIsc Managed anen x ee al Data Snapshot nM ry Managed Service G System Class z _ BAPLEX BA01 MV5SYS_ C_ BAPLEX BA01 MVSSYS C BAPLEX BA01 MVSSYS om BAPLEX BA01 MVSSYS BAT_DISC D1 Discret na A m BAT_3V30 1 Velocio O Medium BAT_3V40 Velocio 0 Medium BAT_3V50 1 Velocio 0 Medi
2. Figure 3 44 TEP Router status gt The second attribute group called NETSUMMARY is useful to quickly determine which networks are monitored by the SNMP data provider and get simple information such as the number of nodes detected and the response time statistics When starting the SNMP the data provider reloads the already discovered networks and their attributes from the KUMSNETS file Figure 3 45 shows the network summary Only the production network is managed by the SNMP data provider Im NETSUMMARY blades SYSADMIN BEE File Edit View Help o gt FOHR BRS AF S COV SBSWKHRABEEARY t eo S View Physical 9 255 255 255 0 10 1 1 209 Production Net 255 255 255 0 10 1 1 209 9 212 128 255 255 252 0 of Enterprise 8 UNIX Systems ia Linux Systems cfs Windows Systems Ga BLADE10 EHI BLADE11 aH BLADE12 ER BLADES By Universal Agent Hgg 10 1 1 131 INTERNETOO s 10 1 1 131 SNMP MANAGEROO GH MANAGED NODES G MIBNODATA L eg 10 1 1 131HTTPdp UAGENTOO mgg 10 1 1 131SNMPdp UAGENTOO xi dhh BD munah andinn Mak ORM AeA KLA ODAN Physical Figure 3 45 TEP Network summary The managed system Production Net SNMP MANAGEROO contains an attribute group containing data the others are empty This managed system is created by the Universal Agent based on the information provided in the KUMSNAME file This file is upda
3. Hub Time Tue 03 21 2006 05 46 PM Figure 3 38 DB2 thread details for CBMPLAN Server Available Thread Detail 9 212 128 3141 SYSADMIN 3 4 Multichannel architecture Physical views This section describes the Physical views that can be used in a multichannel architecture 3 4 1 WebSphere Application Server These Physical views are similar to those of the z OS environment Refer to 3 1 1 IBM OMEGAMON for z OS V3 10 on page 125 to obtain a broad view of IBM Tivoli Monitoring capabilities for WebSphere Application Server 170 Infrastructure Solutions Building a Smart Bank Operating Environment 3 4 2 Uniform Resource Locator monitoring The Hypertext Transfer Protocol HTTP data provider available in the Universal Agent enables you to obtain statistics regarding the Uniform Resource Locator URL connections initiated from a single location to miscellaneous Web sites The installation and settings are described in 2 2 The distributed environment on page 84 The content of the attribute groups relates to the settings defined during the configuration of the HTTP data provider The managed system lt hostname gt INTERNETOO contains two attribute groups with data the others are empty The first one called MANAGED_URL contains a set of useful information pertaining to the URL such as availability status and response time gt Status When the remote server replies to the U
4. og Page 1 of3 1B Smart_Bank WLM Selected Service Class Resources information aj Teler Managed Senice Penoa Goal Goal Goal Goal Duration Average Perform Authentication System Class Tyne _ Percentile importance Value Response Time Inde s F Banking BAPLEXBAD1 MVSSY5 BAT_DISC 1 Diseret 0 ra 0 a ol acs BAPLEXBAO1 MVSSYS BAT_3V30 1 Velocio 0 Medium 30 o ol D82 BAPLEX BA01 MYSSYS BAT_3V Velocio 0 Medium 40 0 o MQSeries BAPLEX BA01 MVSSYS BAT_3V Velocio 0 Medium 50 0 o TP BAPLEXBADI MVSSYS BATCH Velocio 0 Medium 25 0 o WebSphere BAPLEXBAD1MVSSYS BATCH Velocio 0 Medium 30 0 o BAPLEXBAD1 MVSSYS BATCHHOT 1 Velocio 0 Highest so o o I Teler Channet BAPLEXBAD1 MVSSYS_ BATCHLOW 1 Diseret 0 nia 0 0 o e s Aam BAPLEXBADTMVSSYS CICS_AOR 1 Velocio D Mediun 30 T ol a Web BAPLEX BAO1 MVSSYS CICS_CPS 1_Velocio 0 Medium 50 0 o E Bi zBank GDPSHyperSwap T PROCESS SOA o 0 BAPLEXBA01 MVSSYS 1 AvgResp 500 0 BAPLEXBA01 MvSSYS PRJOPD 1 AvgResp 500 o 2 BAPLEX BAO1 MVSSYS PR_MDBD 1 AvgResp 500 0 0 BAPLEX BA01 MYSSYS PR_MDBDW 1 AvgResp 500 0 o BAPLEX BA01 MVSSYS PR_TRF 1 AvgResp 600 0 i BAPLEXBAD1 MVSSYS_ PRWEB 1 AvgResp 500 0 o BAPLEXBAD1 MVSSYS_SYSOTHER 1 SysGoal iy o o BAPLEXBADI MVSSYS_ SYSSTC 1 SysGoal 0 o ol BAPLEXBAD1 MVS8Y5 SYSTEM 1 SysGoal 0 0 0 o BAPLEX BAQ1 MVSSYS TRX_ABI 1 AvgResp 0 600 0 29 BAPLEX BAO1 MVSSYS TRX_ABP 1 AvgResp 0
5. Figure 4 13 Web page advice in a situation When used a simple Web page is displayed as shown in Figure 4 14 File Edit View Help e gt THE BRP CAM F OO C SQWRBRERERVOVTSED Figure 4 14 Situation advice in a Web page format Chapter 4 Customizing the Logical views 197 The event attribute variables listed in Table 4 1 are available in a Web page advice Table 4 1 Attributes available in a Web page advice Attribute iain EVENT ATTRIBUTE ISITSTSH SITNAMES Managed system name EVENT ATTRIBUTE ISITSTSH ORIGINNODE Tip To find out the attribute names that can be used as variables edit the situation Select the Show formula option and check the box against Show detailed formula The names that are now displayed are a concatenation of the group name a period and the attribute name You can use it as a variable by surrounding it with two dollar signs Advice that prompts a user The purpose of a Logical view is to display business information when managing alerts The advice function prompts the users to focus on their demands and send back relevant data Example 4 2 shows how to use the INPUT function Example 4 2 INPUT function in a situation advice search INPUT What do you want to reasearch for enter lt BODY BGCOLOR e6e6fa gt Searching database for lt b gt searcht lt b gt lt META HTTP EQUIV refresh CONTENT 1 URL http www mechanicalworks com s
6. Page 4 ot1 Elapsed Package Thread mer intemal Time DERM Status CPU Time SYSLN300 0 0 NOT IN DB2 00 00 27 814 00 00 15 191 997613 108 27 BASQLID BASR011S 03 21 06 al SYSLN100 0 0 NOT IN DB2 00 00 22 387 00 00 14 250 39990 1817 9089 BASGLID BASROMS 03 21 06 o0 5 CORBEP1 0 0 NOT IN DB2 00 00 1 6 00 494653 133815 18515 ARNOULD FABBEP1 03 21 06 00 00 20 709 RRSAF SYSLN300 0 0 NOT IN DB2 00 00 16 722 00 00 09 124 653131 72 18 BASOLID BASR011S 03 21 06 T 00 00 06 924 RRSAF SYSLN300 0 0 NOT IN DB2 00 00 08 814 00 00 04 835 360669 40 10 BAS LID BASRO11S 03 21 06 00 14 57 000 DISTSERV SYSSH200 0 0 WAIT REMREQ 00 00 01 343 00 00 00 707 39008 4l 0 ARNOULD kfwservi 03 21 06 T 00 14 57 000 DISTSERV SYSSH200 0 0 WAIT REMREQ 00 00 00 864 00 00 00 461 36749 4 0 ARNOULD kfwservi 03 21 06 le 00 14 57 000 DISTSERV SYSSH200 0 0 WATT REMREG _00 00 00 860 00 00 00 454 35749 4 O ARNOULD kfwservi 03 21 06 Ea 00 14 57 600 DISTSERV SYSSH200 0 0 WAIT REMREQ 00 00 00 844 00 00 03 967 35911 12 1 ARNOULD kfwservi 03 21 06 00 00 06 925 PRRSAF SYSLN300_ 0 0 NOT IN DB2 00 00 00 844 00 00 00 453 35741 4 1 BASQLID__ BASR0115 03 21 06 4 ri Hub Time Tue 03 21 2006 05 37 PM o Server Available Thread Activity by Plan 9 212 128 31 SYSADMIN Figure 3 36 DB2 threads activity with the
7. 131 3 2 1 IBM Tivoli Composite Application Manager for Service Oriented Architecture 132 3 2 2 IBM OMEGAMON for WebSphere Application Server 139 3 2 3 IBM OMEGAMON for WebSphere MQ 0 000 ccc eee 149 3 3 IBM CICS Business Event Publisher for MQ Series and event processing 154 3 3 1 Overview of CICS Business Event Publisher for MQ Series 154 3 3 2 Using CICS Business Event Publisher to populate the banking data warehouse Gatabase ss je ivace secre aani winch aie grees Ene mates eas dd ot hea paar lad 157 3 3 3 Monitoring a running CICS Business Event Publisher using OMEGAMON XE for MOSES fi nero aaaea As tidcitie Rowdies nial Mod ay dual RR dav E a TER BEAUNE 161 3 4 Multichannel architecture Physical vViewS 2 0000 c eee eee eee 170 3 4 1 WebSphere Application Server 0 0000 eee 170 3 4 2 Uniform Resource Locator monitoring 00 cee ee 171 3 4 3 IBM HTTP Server monitoring 0 000 cee tee 173 3 4 4 Simple network monitoring 0 00 cee 177 Chapter 4 Customizing the Logical views 2 0 00 c ee eeeeee 181 4 1 Introducing the Logical view 0 0 c cette 182 4 1 1 Things to be considered before defining the Logical view 182 4 1 2 Defining a Logical vView 6 000 cet 183 4 2 Assigning managed systems to a Logical view 0 0 0 c eee eee 189 4 2 1 Assigning a managed system to
8. 3 View Smart_Bank x EEx 32 WLM Selected Service Class Resources information Authentification Banking cies DB2 MQSeries TCP WebSphere A Teller Channel PROCESS SOA _WLM Selected Service Class Resources information F Smart_Bank zj Managed Service Period Goal Goal Goal Goal Duration Average Performance Actual Per lg Wm Teller System Class Type _ Percentile Importance Value Response Time Index Host C BAPLEX BAOUMYSSYS BAT_DISC 1 Discret O nia 0 0 0 0 00 0 E ATM Web zBank GDPS HyperSwap BAPLEX BAO2 MVSSYS__ BAT_DISC 1 Discret Figure 4 50 Result of the dynamic link utilization Advanced link Going further the header and the footer With the advanced link that is defined you move from a view called WM All Service Class Resources information to another view called WLM Selected Service Class Resources information It is better to present the target view with a title that includes as a sample the selected Service Class and its description You can perform this task in the advanced link definition Note Set up the text of a header or a footer the same way that you assigned a value to a symbol in a query Click the header or footer you want to set up in the left hand side of the window and an attribute in the right hand side of the window By doing so the original text if any of the header or the footer is disregarded T
9. A 22 Eclipse Help Server HELPSYR No 3 0 1 Tivoli Enterprise Portal Browser Yes NJA NJA NJA 06 10 00 00 localhost Tivoli Enterprise Portal Desktop Yes NJA NJA NJA 06 10 00 00 blades Tivoli Enterprise Portal Sers Started 22 Universal Agent za MS Stopped Manual No Yes 06 10 00 00 5 22 Monitoring Agent For Winde A MS Started Auto LocalSystem Yes Yes 06 10 00 00 Change Startup Change Startup Parms Set Defaults For All Agents Configure Greate Instance Reconfigure Advanced Configure Advanced Unconfigure Remove Instance Configure TEPS Interfaces Edit Trace Parms Licensing gt View Trace Log Edit Variables Edit ENV File Edit EIF Configuration Edit TEC Server Mapping File Set Network Interface Remove TEMS application support Configure SOAP Server Hubs Buld TEPS Database Browse Settings About Services Configure Java App View Running Processes load map FTP attribute and catalog files to mainframe Figure 2 43 File Transfer Protocol FTP catalog and attribute files selection b In the window that opens select the attribute and catalog data for transfer if you select all of them you are presented with the option of either overwriting or not overwriting the files that already exist on z OS Click OK Chapter 2 IT environment of the Smart Bank showcase 103
10. 3 View Physical y 0 E jil by Service Operation Type paroman a 05 390 Unix US Fay Services Manag TranstenWS cashWithdraw R a Message Ar PostingInquiryCounterWS getP ostingListCounter R Bey Services Ma PostingInquiryAtmWS getP ostingListatm R EH Perfor Hello helloFSS R Ts CustomerArrangementListWS getAccountListR pautes ChequeDepositNS deposit R w Storage Subsysl tl p eeepost S F Websphere Apr CashiWithdrawiW S cashWithdraw R g E E Baokww CashDepositWS cashDeposit R BillP aymentWS pay R En BA02 Kd BalancelnquiyWSigetBalance R Py gg O A E E E A E S E A x mm gt o 1000 2000 3000 4000 5000 6000 7000 s000 9000 10000 lt 3 Physical Number of Messages Average Message Size by Service Operation Type EOX Hello helloFSS P Hello helloF SS R 200 300 400 600 600 o 100 Message Size in Bytes S Hub Time Sa 03 18 2006 12 06 PM Server Available Message Count 9 212 128 31 WOLF1 Figure 3 13 The Message Summary workspace Chapter 3 Using Physical views 137 The Fault Summary workspace The Fault Summary workspace provides a general summary of faults by operation Figure 3 14 shows the workspace on the BAO1 system 0 li a pa ke amp File Edt Yiew Favorites I Address http 9 212 128 31 1920 cnpykat bal EJ Go ay 2 Tivoli Enterprise Portal File Edit View Help HHBREA
11. Queue Name a H ts i 5 o 10 20 30 40 50 60 70 80 90 100 Percent Full s Physical a Queue Definition Total Input Output High Depth Name Type Opens Opens Opens Threshold lt Jfeilel S xe Meret a Normal Predefin 0 0 0 No 0 0 80 0 0 No CICBEP QLOCAL2 Normal Predefin 0 0 0 No 0 0 0 0 No CICBEP QLOCAL3 Normal Predefin 0 0 0 No ol o 0 0 No CICS01 INITQ Normal Predefin 3 3 0 nla 0j 0 0 0 No z Yes cIC802 NITQ Normal Predefin 1 1 0 No 0 0 0 0 No Enab Enabl Yes CRB CLTING Normal Predefin 0 0 0 No 0j 0 0 0 No Enabl Enabl No CRB CLTINGALS Normal Predefin __ 0 0 0 No pies 20 0j OO No Enabl Enabl No CRB DEAD LETTER Normal Predefin 0 0 0 No 0j 0 0 0 No tEnabl Enabl No CRB DEAD LETTER A Normal Predefin 0 0 0 No 0 0j 0 0 No Enabl Enabl No cl CRB SRVINQ 2 4 1 No o o 0 0 No Eran Enabl No CRB SRVINQ ALS 2 1 1 No 0 0 0 0 No Enabl Enabl No a ao n A hla T ni al AA Ble TEnaht Enaki Thin gt CSQ1 BA01 MQESA Figure 3 32 Queue statistics 164 Infrastructure Solutions Building a Smart Bank Operating Environment 4 The window shown in Figure 3 33 is displayed The Recent Queue Statistics panel at the bottom shows the latest stat
12. C Hub Time jeu 03 09 2006 09 55 AM ake Server Available CICS_Perf_Summary_Link 9 212 128 33 SYSADMIN Figure 4 29 Relative link Sample source view 212 Infrastructure Solutions Building a Smart Bank Operating Environment 2 If you use this link by clicking the chain that represents the relative link the TEP asks you the specific CICS region you want to focus on Choose the one you want as shown in Figure 4 30 Select Target gx Enterprise E z OS Systems S BAPLEX MYS SYSPLEX Ge Baot cics 5 5 BAM CICSRA10 H DB2 Summary S 5 BAU CICSRA11 EH D52 Summary S 5 Ba0t cicsrai4 H DB2 Summary 5 BAM CICSRT10 EH DB2 Summary 5 BA01 CPSMCMO H DB2 Summary Cay Cre Figure 4 30 The Select Target window when using a relative link Chapter 4 Customizing the Logical views 213 3 The TEP then displays the DB2 Summary workspace for the CICS region that is selected Figure 4 31 Tivoli Enterprise Portal File Edit View Help HHABRet PAO STOO ClSOSWRRBETANRVFSTBE View Physical x HE DB2 Summary System CICS Region Attached DB2 Subsystem 1 ID Name to DB2 Name Fa Bat cicsratt a ER Automatic Initiate Descriptors BA01 CICSRA11 Yes CB01 ER Bottleneck Analysis ER Connections Analysis EK DB2 Summary E DB2 Task Activity E DBCTL Summary 4 EK Dispatcher Summary E Dispatcher TCB
13. COMMAREA DFHMIRS Figure 5 5 Service oriented invocation of the core system step 3 Note There are many integration mechanisms that can be used We chose the CICS Transaction Gateway mechanism Another equally viable and strategic choice is SOAP HTTP direct to CICS Infrastructure Solutions Building a Smart Bank Operating Environment Figure 5 6 shows step 4 described in Table 5 1 which is our full process integration step that uses the Enterprise services created in step 3 but combines them with other services and uses the Process Choreographer provided by the WebSphere Business Integration Server Foundation The run time element of the process is an EJB It is this workload that we monitor as described in 5 1 4 Process integration on page 269 B09 Browser Z OS LPAR client WebSphere Application Server v5 1 CICSPlex CICS v3 1 HTTP Web Container EJB Container action Pgs e 2 O po i COMMAREA DFHMIRS JCA ECI java classes Resource adapter CTG Server v5 1 HTTP Server plug in Workload Injection siepe ysplex HTTP Distributor Choice of binding Direct EJB call RMI IIOP EJB Binding WSDL RMI IIOP SOAP Binding WSDL SOAP HTTP Figure 5 6 Service oriented invocation of a process step 4 Our ser
14. Cancel Delete Back Figure 4 45 Dynamic link functions and operators In summary the advanced link definition window contains the following features The structure of the target workspace Functions to apply on them Operators to build some logic vvvy Attributes gathered by the source workspace Everything that is required to build the filter associations is now available Chapter 4 Customizing the Logical views 227 228 Advanced link Setting up a value for dynamic filtering To set up a value for dynamic filtering in the advanced link perform the following tasks 1 In the right hand side of the window A in Figure 4 46 a Clear button is present Click it to erase all the data in the top right section B 2 In the left side of the window the symbol SERCLASS C is present Click it fl KJRITMOO1I Link Wizard Define New Link WLM Details Properties Symbols y linklsEnabled V contextlsAvailable S Target Workspace FR Query WLM LINK Service Class Symbols Vv NODE v o Ey Table WM he lected Servi V Footer V Header Expression Allowable Terms Test Values Link FQ Selected Row Attributes v Actual Host Y Average Response Time Vv Average Storage Y CSS Priority Y Class Flag v Durstian Figure 4 46 Selecting the SERCLASS symbol 3 In the bottom right section in the Attributes list zone A inside
15. g P ISmart_Bank E Teller WLM All Service Class Resources information Page WLM All Service Class Resources information Managed Service Goal Duration Average Performar Authentification System Percentile Importance Value Response Time Index Banking BAPLEX BA01 MVSSYS BAT_DISC 1 Discret 0 0 CICS BAPLEX BA01 MVSSYS_ BAT_3V30 1 Velocio 0 Medium 30 0j a 0 DB2 BAPLEX BA01 MVSSYS BAT_3V40 1 Velocio 0 Medium 40 0 0 0 MOSeries BAPLEX BAO1 MVSSYS BAT_3V50 1 Velocio 0 Medium 50 0 amg o TCP BAPLEX BA01 MVSSYS BATCH 1 Velocio Ol Medium 25 0 0 o WebSphere BAPLEX BA01 MVSSYS_ BATCH_HI 1 Velocio 0 Medium 30 0 0 0 BAPLEXBA01 MV55YS BATCHHOT 1 Velocio O Highest 50 0 o o E Channel PAPI EY BANIMYSSYS BATCH AAt 14 Discreet O nia n ol ol 0 2 KJRITMOO2I Link Wizard Edit Link WLM Details X z w amp a E Properties Expression o m C a __0 B Symbols aS V contextisAveilable o 0 v am a S Target Workspace 13 o S F Query WLM LINK Service Class L D g Symbols Tear g g SODE Allowable Terms i V SERCLASS p g E Table WLM Selected Servi 5 Values al a a V Footer Link O 0 V Header E peetedRow R p o S Attributes 0 0 V Actual Host 0i 0 v Average Response Time tt 0 v Average Storage 0 0 V CSS Priority 0 0 V Class Flag 0 0 V Duration 0 0 YV Goal Impo
16. All the z OS based agents connect to their local Tivoli Enterprise Management Server Remote by using only SNA No other protocol is configured Because mirroring the Tivoli Enterprise Portal Server is an extremely time consuming task that is difficult to maintain consistently we offer a fourth solution for the clients who want to keep their Tivoli Enterprise Portal Server on systems based on IBM System x Chapter 1 Introducing the technical architecture of the Smart Bank showcase 45 1 4 6 Virtualized IBM System x with Moveable Hub implementation This architecture as depicted in Figure 1 18 shows a way to get a high availability solution where the Tivoli Enterprise Portal Server is located on IBM System x and the Tivoli Enterprise Management Server Hub resides on z OS VMware ESX Server bs VMware ESX Server Windows o Windows Appl Sys Figure 1 18 IBM System x based virtualized Tivoli Enterprise Portal server and z OS based Moveable Hub This solution is similar to that discussed in 1 4 4 IBM System z environment scenario on page 37 The Moveable Hub implementation is exactly the same The only difference here is the virtualization platform under the Tivoli Enterprise Portal Server hardware The components are gt On VMware ESX Server The VMware solution is discussed in detail in VMware at a glance on page 48 On Windows e Tivoli Enterprise Portal Server The Tivoli Enterprise
17. Enterprise H UNIX Systems i L 35 Linux Systems EEE Windows Systems Ga BLADE10 http satss Q080 web app BLADE11 BLADE12 BLADES ey Universal Agent 5 a 10 4 1 131 INTERNETOO MANAGED_URL http Inxc1 production localifss URL_OBJECTS E5 10 1 1 131 SNMP MANAGEROO is 10 1 1 131HTTPdp UAGENTOO a 10 1 1 131SNMPdp UAGENTOO 5 Production Net SNMP MANAGEROO M Curent Response Time E Maximum Response Time Dlaverage Response Time g SmartBank SNMP MANAGEROO Ba Windows OS Blades http blade2 production localifss mf z 0S Systems lt a aes one lt an 80 100 120 140 160 180 200 220 240 HE Report manx v URL Status Status Timestamp Page Title Page Size Current Response Time Maximum Response Time Average Response Time Page Objects Total Object Size httpisafss 9080 web app OK 2006 03 18 18 11 45 020 Siebel Analytics Log In 4096 219 234 224 1 0 http lnx1 production localifss OK 2006 03 18 18 11 45 010 FSS Benchmark Test 1917 31 31 Eil 0 o httpfblade2 production localifss OK 2006 03 18 18 11 45 000 __ FSS Benchmark Test 1917 16 16 10 0 0 Figure 3 41 TEP MANAGED_URL workspace 3 4 3 IBM HTTP Server monitoring The file data provider available in the Universal Agent enables the extraction of useful information from sequential text files In such a situation this feature is used to
18. 9 2 Page 1of3 E Smart_Bank WLM All Service Class Resources information B Teller Managed Gemiea i c Goal Goal Goal Goal Average Perfo Authentification System Class Type _ Percentile Importance Value Response Time Inf 5 3 Banking 2 BAPLEX BAO1 MVSSY BAT_DISC scret O nla 0 0 cles CAEN OOO ADANA a LO Es mar auan ASS tate nin Cy ees an 0 D2 tail X 0 MQSeri 0 TCP Properties Expression 0 Weesp iE Gl Symbols kw TableRow ATTRIBUTE MWLMPR CLSNAMES o Eos contextisAvailable Eal MMM 0 a Teler Chant V linkisEnabled 5 0 a AIM Target Workspace Allowable Terms a a Eg Web F Query WLM LINK Service Class a NN 0 zBank GDPS Hy Symbols Expression Value 0 PROCESS SOA V NODE i v BAT_DISC o E Table WLM Selected Servi B 0 V Footer 0 V Header 0 0 V IO Priority 0 V VO Rate 0 V IFA Service Units 0 V Managed System 0 V Percent CPU 0 V Percent IFA 0 V Percent IFA on CP 0 V Performance Index 0 V Period 0 V Resource Group 0 v 0 Y Service Class Description 0 New o NEN iiaa x 2 0 Coa Come Cae ot 0 z E Physical 8 Smart_Bank TA Rent Amana nnm a eS ANC ana a Kg C Hub Time Wed 03 15 2006 05 44 PM 7 Server Available WLM All Service Class 9 212 128 31 SYSADMIN Figure 4 48 The result of the association Tip To fill the value of a symbol you can also use a specific function called INPUT This prompts the user for a value OMEGAMON XE for MainFrame Netwo
19. http 9 212 128 31 1920 cnpjkdt E EJ Go ay Tivoli Enterprise Portal File Edit View Help HHBACAM SOCO SOHUBZSERRERF ODED 3 View Physical HE Message Arrival Details old Comparison Message Situation Name Operator Threst Service Name Operation Name rejre Curent Message Thresh warmee IP Address w MYS Operating System wi 8 OMEGACENTER Bridge 8 3a 05 390 Unix U55 i Ba Services Management Agent SH Message Arrival By Services Management Agent Env Performance Summary ja E Message Summary Faults Summary E amp Storage Subsystem Ls S F WebSphere Application Server 05 39 coy BaL KWwwA gi MessageArrivalClearing _ 0 Less_Than MessageArrivalCritical i x 0 Greater Than E 5 Physical gt RTI Message Arrival by Service mean x FI Message Arrival by Operation menx Number of Messages Number of Messages S Hub Time Fr 03 17 2006 06 33 PM P Server Available Message Arrival 9 212 128 31 WOLF1 Figure 3 10 The Message Arrival workspace 134 Infrastructure Solutions Building a Smart Bank Operating Environment The Service Management Environment workspace This workspace as shown in Figure 3 11 presents summarized data for all the monitored application servers on that system Information from all the active data collectors are put together in order to provi
20. Key attributes All the key attributes In this case all the numeric attributes defined with SKEY SUM total result count for a summarizing interval To calculate the statistics such as the number of bytes received per second new attributes called derived attributes are created based on the default attribute group provided by the SUMMARY statement For example the new attribute Occurrences is derived from the default attribute Occurrence Moreover derived attributes can be created based on the numeric attribute defined with SKEY SUM in this case BytesSend and BytesReceived attributes The attribute groups HIST_WORKLOAD_BY_DAY and HIST_WORKLOAD_BY_HOUR are based on the concept The difference is only the summarization period defined in the SUMMARY statement set to 86400 seconds 1 day and 3600 seconds 1 hour Infrastructure Solutions Building a Smart Bank Operating Environment Figure 3 43 shows an example of data provided by the WORKLOAD_DETAIL attribute group The default report has been customized a little for a better understanding of the published data m WORKLOAD_DETAIL blades SYSADMIN olx Fie Edt View Help ers GE S View Physical Gia blade2 Linux OS Universal Agent 1000 a 10 1 1 425 1BMHTTPOO EXCEPTION_DETAIL HIST_BROWSER_STAT HIST_CLIENT_PLATFORM_STAT HIST_HTTP_STAT HIST_REFERRAL_BY_LOCATION HIST_REFERRAL_STAT HIST_REQUEST_BY_LOCATION HIST_REQUEST_STAT HIST_STAT
21. Number of Queues 600 MQSERIES a csa Application Debugging Application Statistics Buffer Pool Statistics Channel Definitions Channel Initiator Status Channel Performance Cluster Queue Manager Dead Letter Queue Messages Log Manager Performance Message Manager Performance MOQSeries Events Page Set Statistics a E Queue Definitions Queue Manager Status Queue Statistics E Ea cs 2 E Physical Monitored Queues HLocal Queues GRemote Queues E Aias Queues O Transmit Queues M Fredefined Queues E Permanent Dynamic Queues M Temporary Dynamic Queues ciun Gus Queue Definitions Definition Creation Queue 2 Date amp Time Name lt Moo Queue Descripti CICBEP QLOCAL2 Local Normal Predefined 01 26 05 11 02 11 Yes Enabled O No BEEP i ed BER CICS01 NITQ Local Predefined 5 51 d o CICS RA10 CICS02 INITQ Local Predefined 02 01 06 14 51 54 Enabled 0 CICS RA10 CRB CLTING Local Predefined 03 15 06 13 41 33 Yes Enabled a No COREBANK LOCAL QUEUE FO E CRB CLTINGALS Alias Normal nia Yes Enabled 0 No CRB DEAD LETTER Local Normal Predefined 03 15 06 13 41 33 Yes Enabled 0 No COREBANK DEAD LETTER QU CRB DEAD LETTER ALS Alias Normal n a Yes Enabled 0 No CRB SRVING Local Normal Predefined 03 15 06 13 41 33 Yes Enab
22. 3 To set up the function Properties Symbols V contextisAvailable Y linkisEnabled v Target Workspace F Query WLM LINK Service Class Symbols v NODE V SERCLASS E Table WLM Selected Servi V Footer V Header parameters erase the proposed default Figure 4 56 Expression kfw TableRow ATTRIBUTE MWLMPR C LSNAME Selected we Allowable Terms Functions m Between abe Sub String abe Quote String abe String Scan Compare Date and Time Time abe Index Of abt Last Index Of abe Length abe Format Values abe Get Resource String Get Advice URL String abc Extract Token abe To String ab To Boolean ab To Integer abe To Float abe To Uy abe Trim abe Starts With abc Ends With Back Figure 4 56 Modifying the function parameter 236 Infrastructure Solutions Building a Smart Bank Operating Environment 4 To fill the required parameters for this function in the attribute list select the one containing the Service Class description The top right section of the dynamic link definition is updated Figure 4 57 8 KJRITMOO2I Link Wizard Edit Link WLM Details amp Properties S Symbols V contextisAvailable V linklsEnabled Target Workspace S F Query WLM LINK Service Class Allowable Terns 5 Symbols Y NODE V SERCLASS o E Table WLM Selected Servi V Footer V Header Expres
23. Linux OS Linux OS Linux OS Linux OS a Business Analytics e y UNIX OS we CICSPlex we DB2 z OS Linux utilisation Network E Systems Management Movable Hub address space BA01 Movable Hub address space BA02 MVS Address Space BA01 Enterprise MVS Address Space BA02 a ga UNK os By Windows OS Blade11 amp Windows OS Blades m afl iAiehSnhere ziNS Clustert x Physical Neils view l Hub Time Wed 03 22 2006 02 39 PM JE Server Available Neils view 9 212 128 31 SYSADMIN Figure 4 68 The Smart Bank Logical view tree The Logical view tree is clearly defined in two parts gt The first one is the structure of the Smart Bank Enterprise view It is simple because we want to display the services the Smart Bank clients receive through the different channels offered gt The second one is more detailed The Smart Bank team picked up all the physical environments involved for each channel The categories and subcategories are organized according to the decisions taken by the Smart Bank showcase team The main idea is to create groups of identical involved hardware middleware and software components These subtrees are designed at the time of creating new children or are simply created by copying the adequate parts of the physical tree directly New situations are defined on some levels to complete the set of situations inherited from the copies of the physical tree
24. The installation and customization process can be split into the following multiple tasks The System Modification Program Extended SMP E installation The use of the Installation and Configuration Assistant Tool ICAT The run time environment building Configuring the primary hub Configuring the remote hub vvvvy The System Modification Program Extended installation The IBM Tivoli Monitoring Services V6 1 and Tivoli OMEGAMON XE for z OS V3 1 0 products are delivered using the standard IBM enterprise software fulfillment processes either through electronic delivery or physical delivery The installation is performed using the standard System Modification Program Extended SMP E process This IBM Redbook does not discuss the SMPYE installation For details about the complete SMP E installation refer to IBM Tivoli OMEGAMON XE V3 1 0 Deep Dive on z OS SG24 7155 60 Infrastructure Solutions Building a Smart Bank Operating Environment The use of the Installation and Configuration Assistant Tool The configuration of the IBM Tivoli Monitoring Services and Tivoli OMEGAMON XE products is made by an IBM configuration tool named ICAT This tool allows easy configuration and assists you in defining your run time environment ICAT can be invoked either through the batch mode or the interactive mode This book uses the interactive mode based on a set of Interactive System Productivity Facility ISPF dialogs to collect customization values and
25. Enabl Yes No None E SYST Normal PermDyn 0 0 0 No 0 0 80 0 0 No Enabl Enabl Yes No None KMQ Normal PermDyn 0 0 0 No 0 0 80 0 0 No Enabl Enabl Yes No None ATDIV Normal Predefin 0 0 0 No 0 a 80 0 0 No Enabl Enabl Yes No None ATDIV Normal Predefin 0 0 0 No 0 0 80 0 0 No Enabl Enabl Yes No None Km Normal PermDyn 0 0 0 No 0 0 80 0 0 No Enabl Enabl Yes No None aR ia Rinwwal Pace A A nlna a n an AN hin Faaki Faaki Van hia hiana 4 ae CSQ1 BA01 MQESA je Hub Time Do 03 16 2006 07 57 PM ck Server Available Queue Statistics 9 212 128 31 WOLF1 Figure 3 26 The Queue Statistics workspace Depending on how the application environment is set up the queues may or may not be application specific For the Smart Bank showcase the following rules were implemented gt System focused situations The existence of the monitored queue Monitoring does not help if the monitored object no longer exists The product enables an alarm for all the erased queue objects Once a queue is discovered it monitors the existence of the queue for 24 hours Monitoring the relative queue depth The system s well being requires that no queue gets full A full queue may lead to messages crowding the dead letter queue which may in turn lead to the channels stopping This means that a local problem may spread across system boundaries In order to b
26. Graphic View Text style Font name E im is x Boa 0 taic FN Notepad Hub Time Figure 4 64 Graphics property access Chapter 4 Customizing the Logical views 243 2 To change the current style to the Smart Bank showcase style click Browse Figure 4 65 n f Properties Smart_Bank X Smart_Bank 3 9 Views Notepad Views S Graphic Views 2 Preview Graphic View POORNE h Xx Hoo S Background O Map Image Fitto view user 0 MOP banner fat jpg Style shape_white_label_bottom css Browse image files Graph 0k cance Apply Test Help Figure 4 65 Background and style setup 3 Open the User folder and select the entry created earlier named Smart Bank showcase css and open it Figure 4 66 Look in amp Select Name X HL sample _Jarge_Icon_oottom_Iatel css HE sample_large_icon_no_label css sample_large_icon_right_label css UE sample_small_icon_bottom_label css sample_small_icon_no_label css le sample_small_icon_right_label css Ie SmartBank css File name Files of type SmartBank css All Files Open N Figure 4 66 Opening Smart Bank showcase style 244 Infrastructure Solutions Building a Smart Bank Operating Environment 4 The style window closes Click OK in the backgrou
27. Total Object Size 0 0 ibm com Ok IBM U 10 1000 1000 ebiapp OK 7 Siebel At Iti gin 62 62 http ln productionlocalifss OK 2006 03 20 19 9 54 020 FSS Benchmark Test 1917 16 16 http blade2 production localif OK 2006 03 20 19 49 54 010 FSS Benchmark Test 1917 31 31 31 i oll Figure 3 39 TEP Internet URL response time with ObjCache Figure 3 40 shows the URLs response time for the site www ibm com with the parameter ObjCache 0 all objects are downloaded The response time is around 5 seconds MANAGED_URL blades SYSADMIN of x File Edit View Help ABHA BREA LOOG SBSUBAETANRD e sea O 8 alleen View Physical E blades a Int Ga Inxt aHa Inx4 m pa Inxs spa Inx ra Windows Systems GG BLADE10 http satss 9080Aweb app BLADE11 BLADE12 h BLADES Ba Universal Agent http Anm ibm com M current Response Time E Maximum Response Time Dlaverage Response Time http Inx1 production localitss 10 44 AR SNMP MANAGEROO 10 1 1 431HTTPdp UAGENTOO 10 1 1 131SNMPdp UAGENTOO http blade2 production localitss 5 Production Net SNMP MANAGEROO ene Tester Page Title Page Size Current Response Time Maximum Response ine Average Response Time Page E Total Object Size http ibm com Ok IBM United States 24649 5169 3406 144827 http isafss 9080weblap
28. Unknown 10 1 1 147 0 5 03 14 06 16 01 04 60 nlipgy Servlet org apachejsp _CDOutput _jspService 03 14 06 15 58 10 Unknown 10 1 1 147 0 6 03 14 06 16 01 04 60 S1gWij Servlet org apache jsp _BlOutput _ispService 03 14 06 15 58 22 Unknown 10 1 1 147 0 7 03 14 06 16 01 04 60 Servlet org apache jsp _CDOOutput _jspService 03 14 06 15 58 22 Unknown 10 1 1 147 0 8 03 1 4 06 16 01 04 60 Servlet org apachejsp _BPOutput JspService 03 14 06 15 58 22 Unknown 10 1 1 147 0 9 03 14 06 16 01 05 60 Servlet org apache jsp _TOFOutput _jspService 03 14 06 15 58 18 Unknown 10 1 1 147 0 10 03 14 06 16 01 05 60 Servlet org apachejsp TOFOutput _jspService 03 14 06 15 58 22 Unknown 10 1 1 147 0 03 14 06 16 01 05 60 Servlet org apache jsp_CDTOutput _jspService 03 14 06 15 58 27 Unknown 10 1 1 147 0 Servlet nra anarheisn COTOutaut isnService N31 4iNh ITAR Unknown 11011147 N Oo Hub Time Di 03 1 4 2006 04 01 PM ee Server Available HTTP Sessions 9 212 128 31 WOLF1 Figure 3 19 The HTTP Sessions workspace Infrastructure Solutions Building a Smart Bank Operating Environment The Datasource workspace This workspace shown in Figure 3 20 provides a brief overview of defined data source usage in the WebSphere Application Server One of the useful situations involves testing the existence of all the required data sources Another important rule is to look at the Average
29. afha BLADES bp Banes m z OS Systems Navigator View Identity j Name Smart_Bank Description smart Bank showcase Enterprise view Physical Reaook Cah o e KFWITMOG611 Enter a description of the Navigator view n BLADE12 NT jwailable KB ache KB lommit Limit KB lommitted KB ize Ad Watch kntoma kinconfg somsave sor kinlogs kincontg Topview putty ems putty oo 7 A 20000 40000 60000 Z 800000 1200000 Kilobytes Kilobytes OPrivate KB Ovirtual KB Hub Time Thu 03 02 2006 05 06 PM Server Available Windows NT 10 1 1 131 SYSADMIN Applet cmwApplet started Internet Figure 4 4 Defining the new Logical view Infrastructure Solutions Building a Smart Bank Operating Environment 3 Define the embedded levels that must be a part of this Logical view by using the Create Child Item icon zone A in Figure 4 5 A child is created under the current selected level an outline is displayed around its name It is possible to create a new child at any existing level of the actual Navigator view Enter the name of the new level and a short description zone B in Figure 4 5 The name given to the child item must be meaningful for all those who use this Logical view After creating the new logical tree click Close Note To build a Navigator view provide a name fir
30. gt magan HA Neils view E Smart Bank Enterprise View UNIX Systems Operations a Ea js20 1 A Branch Blade Servers e3 ta safss Linux OS E Linux Systems Linux OS a Ga blade2 Linux OS Eis blades Linux OS a Ey blades Universal Agent a a blades WebSphere Application Server Agent J Ea Int1 WebSphere Application Server Agent Ea Inx1 Branch zivM Servers d Ele Inx4 Linux OS Gla Inxs Linux OS a Ga nx Linux OS E Windows Systems Linux OS a Ga BLADE10 Universal Agent a Ge BLADE11 WebSphere Application Server Agent Ea BLADE12 WebSphere Application Server Agent e3 ta BLADES Business Analytics z OS Systems CICSPlex r BAPLEX MYS SYSPLEX DB2 z OS a Ga Bam Linux utilisation a Ga B402 Natwveork amp amp amp amp amp ct E f amp ooe Figure 5 12 TEP Edit Navigator view We now have a high level view of the infrastructure and know that a potential problem exists We used the link provided in the systems management alert to dig deeper into the problem The same actions are performed throughout the Physical view tree but the business and operations context are not so obvious Chapter 5 Scenarios and use cases 275 5 2 2 Monitoring the monitoring environment Figure 5 13 shows a Logical view of the monitoring environment This is a simplified view of the monitoring infrastructure with alerts superimposed on a JPEG image None of these alerts are links but they show th
31. 1 AvgResp 0 Low 800 FO of BAPLEX BAD1 MVS 1 AvgResp OfLow 100 of o g Physical Tee o pire ee z Ta Hub Time Mon 03 13 2006 08 00 PM Figure 4 34 The target workspace without any filtering WLM Selected Service Class 9 212 128 31 SYSADMIN Server Available Chapter 4 Customizing the Logical views 217 A user query is defined to gather the data This query is another copy of an existing one called WLM Service Class Resource Call this query WLM LINK Service Class Resources and modify it by adding a symbol named SERCLASS in the Service Class column zone A in Figure 4 35 Implement this new symbol in this column because the user request is to make the selection based on the Service Class name Important Never modify an existing symbol in a query Changing the name of an existing symbol results in unpredictable failures and errors An existing symbol may be used for purposes pertaining to the product by other links and so on Note You can define your own queries in the TEP That way you can set up your own symbols and retrieve only the data you require for the views in the workspace W WLM Selected Service Class 9 212 128 31 SYSADMIN File Edit View Help CET gt ABHRBRSFAA F OO C SQOWUHBRERERDF eve 3 View Emart Bank M max Teea Ei teed ee gl ez Page 1of3 E Smart_Bank WLM Selected Service Class Resources information 5 a Teller Managed Service 4 Goal Goal
32. Alias TIVHUBLB Mode CANCTDCS TpName SNASOCKETS KDE1I_ OpenTransportProvider Transport opened com1 sna pipe For the z OS Tivoli Enterprise Monitoring Server Remote on BAO1 a successful SNA initialization message is registered in the RKVLOG as shown in Example 2 3 Example 2 3 z OS Tivoli Enterprise Monitoring Server Remote SNA initialization message on BAO1 BSS1 GetEnv KDCFP_ALIAS KDCFC_ALIAS KLXBS_ALIAS KO1DSLB BSS1 GetEnv KDCFP_TPNAME KDCFC_TPNAME KLXBS_TPNAME SNASOCKETS BSS1 GetEnv KDCFP_MODE KDCFC_MODE KLXBS_MODE CANCTDCS getEnv AF_SNA configuration Alias KO1DSLB Mode CANCTDCS TpName SNASOCKETS eee eeee KDE1I_ OpenTransportProvider Transport opened coml sna pipe Chapter 2 IT environment of the Smart Bank showcase 81 For the z OS Tivoli Enterprise Monitoring Server Remote on BAO2 a successful SNA initialization message is registered in the RKVLOG as shown in Example 2 4 Example 2 4 z OS Tivoli Enterprise MonitoringServer Remote SNA initialization message on BAO2 BSS1 GetEnv KDCFP_ALIAS KDCFC_ALIAS KLXBS_ALIAS KO2DSLB BSS1 GetEnv KDCFP_TPNAME KDCFC_TPNAME KLXBS_TPNAME SNASOCKETS BSS1 GetEnv KDCFP_MODE KDCFC_MODE KLXBS_MODE CANCTDCS getEnv AF_SNA configuration Alias KO2DSLB Mode CANCTDCS TpName SNASOCKETS eee e eee KDE1I_ OpenTransportProvider Transport opened coml sna pipe In these examples gt KDCFC_ALIAS identifies the APPL definition of the indepe
33. In the top left corner of the TEP window navigate and expand the navigator tree to locate the MQSeries queue Note In our example queue CSQ1 is installed on the z OS LPAR named BA01 The activity on CSQ1 is monitored Chapter 3 Using Physical views 161 Figure 3 30 shows the expanded TEP navigator tree and the information provided for the CSQ1 queue This figure shows that several other monitoring agents are installed in our environment These monitor other subsystems such as DB2 CICS mainframe network sysplex and so on The queue manager summary provides the status of the queue manager that is active File Edit View Help E View Physical v O 8 palletes Oe E UNIX Systems E Linux Systems iE fy Windows Systems z OS Systems E BAPLEXCMVS SYSPLEX a Ga Bao acs 0B2 E Mainframe Networks MQSERIES Total Count 600 gt Application Debugging DLG Depth Cl Monitored Queues M Local Queues GRemote Queues H Alias Queues O Transmit Queues M Predefined Queues GPermanent Dynamic Queues Wi temporary Dynamic Queues Bopen Queues M Number Queues with High Depth M Number of Queues Put Inhibited number of Queues Get Inhibited Application Statistics Buffer Pool Statistics Channel Definitions Channel Initiator Status Channel Performance Cluster Queue Manager Dead Letter Queue Messages Log Manager Perfor
34. Infrastructure Solutions Building a Smart Bank Operating Environment As an example a specific situation is defined in the Moveable Hub address space BAO1 level Figure 4 69 i Movable Hub address space BAO1 9 212 128 31 SYSADMIN l a x File Edit View Help gt AEHRRtA SOOWM SSHURBRBETARF OTE a oh Eh Location http 9 212 128 31 1 920 cnp dhilibiclassesicandle fwitesources helpiwkspat Rabe i j BAO1 sy Branch channel dicscnnbabintsil isnot g nternet channel i a BA SOA Model tpg fe Formula Distribution IP Expert Advice EF Action f Urti Processs choreographer Movable Hub address space BA01 SOA Service Management B amp mvs system r Description WebSphere Ma g o check whether Tivoli HUB is active on LPARs a a Operations E Gi Branch Blade Servers Linux OS B ga Linux OS Formula E3 Linux OS ie Linux OS ic WebSphere Application Server Ageri a NebSphere Application Server Ager Ra Branch z V M Servers 7 a Linux OS Ql TIVSHUBT a amp Linux os es a Be Linux os OO Linux OS A Business Analytics 4 a a UNK OS a E cicspiex Job Name The name of the job started task TSO user APPC address sp S E DB2z0S and so on consuming CPU cycles Valid value is a string with a maximy Linux utilisation eight characters E3 Network A 4 Systems Management Job Preemptable Home SRB Service Percent Cum
35. M System CPU Percent E Busy CPU Percent O Total Swap Space MB M Swap Space Free MB D Total Memon MB M Memory Free MB O Total Swap Space MB E Swap Space Free MB Bi Total Memor MB E Memory Free MB blade3 site LZ ht 2000 3000 4000 5000 Figure 5 17 Linux environment Table 5 12 shows the base queries used to create the Logical view from the assigned agents in Figure 5 16 Table 5 12 Linux utilization Assigned agent and situation Assigned managed system Linux OS Linux CPU Query WebSphere Application Server CPU cluster machines on z VM and BladeCenter Linux OS Linux VM Stats Query WebSphere Application Server VM Stats cluster machines on z VM and BladeCenter Neither the BladeCenter nor the z VM machine use virtual memory at this level of workload We injected around 4 6 operations per second over the branch channel to the z990 in our development region when we captured these windows with the other workloads running for ATM Internet and Batch Chapter 5 Scenarios and use cases 283 It is important to monitor memory utilization In the Linux environment the virtual memory can be monitored through Total Swap Space virtual memory defined to the system and Swap Space Free By managing the available system memory both Random Access Memory RAM and virtual memory Swap Space help identify processes that are being constrained not necessarily by th
36. MQSeries J BAPLEXBAOT MVSSYS BAT_3V50 1 Velocio 0 Medium 50 0 0 00 0 0 TCP amp BAPLEX BA01 MVSSYS BATCH 1 Velocio 0 Medium 25 0 0 00 0 0 WebSphere BAPLEX BA01 MVSSYS BATCH_HI 1 velocio 0 Medium 30 0 0 00 0 0 ZOS BAPLEX BA01 MVSSYS BATCHHOT 1 Velocio 0 Highest 50 0 0 00 0 0 8 Teller Channel BAPLEX BAOT MVSSYS BATCHLOW 1 Discret 0 nia 0 0 0 00 0 0 B ATM BAPLEX BAO1 MVSSYS CICS_AOR 1 Velocio 0 Medium 50 0 0 00 0 0 EJ Web BAPLEX BAO1 MVSSYS CICS_CPS 1 Velocio 0 Medium 50 0 0 00 0 0 E zBank GDPS HyperSwap BAPLEX BAOI MVSSYS CICS_TOR 1 Velocio 0 Medium 50 0 0 00 0 0 EJ PROCESS SOA BAPLEX BAO1 MVSSYS OMVSDFLT 1 Velocio 0 Medium 30 0 5 00 0 0 BAPLEX BAO1 MVSSYS PR_DEFLT 1 AvgResp 0 Low 600 0 0 00 0 0 2 BAPLEX BAO1 MVSSYS_ PR_IOPA1 1 AvgResp 0 Low 500 0 0 00 0 0 BAPLEX BA01 MVSSYS_ PR_IOPD 1 AvgResp 0 Low 500 0 0 00 0 0 BAPLEX BA01 MVSSYS_ PR_MDBD 1 AvgResp 0 Low 500 0 0 00 0 0 BAPLEX BA01 MVSSYS_ PR_MDBDW 1 AvgResp 0 Low 500 0 0 00 0 0 BAPLEX BAO1 MVSSYS PR_TRF 1 AvgResp 0 Low 600 0 0 00 0 0 BAPLEX BAO1 MVSSYS PR_WEB 1 AvgResp 0 Low 500 0 0 00 0 0 BAPLEX BA01 MVSSYS_ SYSOTHER 1 SysGoal O nia 0 0 0 00 0 0 gt BAPLEX BA01 MVSSYS_ SYSSTC 1 SysGoal 0 nia 0 0 0 00 0 2 BAPLEX BA01 MVSSYS_ SYSTEM 1 SysGoal 0 nia 0 0 0 00 14 2 BAPLEX BAOI MVSSYS TRX_ABI 1 AvgResp 0 Low 600 0 0 00 0 0 gt BAPLEX BA01 MVSSY
37. SYSADMIN Figure 4 67 The Smart Bank welcome menu The user has the following choices gt To examine the enterprise which is essentially the services that clients actually receive gt To have direct access to the components of the Smart Bank infrastructure The blue chains that surround the two round icons indicate to the users that they can click it to go to another display or workspace In this case the Smart Bank team set up two absolute links one to go to the Enterprise view and another to go to the Operations view Note The Smart Bank showcase Logical view does not use many dynamic links because there are few requirements to extract data from one view to filter on another workspace during the showcase Chapter 4 Customizing the Logical views 247 248 The Smart Bank Logical view tree The structure of the complete Logical view is shown in Figure 4 68 a Neils view 9 212 128 31 SYSADMIN File Edt View Help Oo AOHRRBREAD SOOWM SSHWHhARB View Neils view im max g QQang h x S esve 4 EA Smart Bank Enterprise View ATM Channel Branch channel Internet channel SOA Model Processs choreographer SOA Service Management WebSphere MQ A G operations E i Branch Blade Servers S Bey Linux oS Ba Linux os a Fey Linux os E3 Linux OS E WebSphere Application Server Agent E B Branch z vM Servers
38. Ttegrated Facility m tnx FT WebSphere Ma for Linux IF Ls ZAM Linux General z OS processors CPs i S CSQ1CHIN Dcpu Percent lt gt 00 0 8 0 x E websphere M user CPU Percent E System CPU Percent OBusy CPU Percent E CBOIMSTR CPU Percent Dra Percent Table 5 10 shows the base queries used to create the Logical view from the assigned agents in Figure 5 15 FI zLinux machines Branch Ocpu Percent MIFA Percent 0 2 4 6 8 10 12 14 16 18 Figure 5 15 z9 utilization view Table 5 10 z9 utilization queries Assigned agent query Assigned managed system MVS System System CPU Utilization z OS LPARs BAO1 and BAO2 Query System CPU Utilization MVS System Address space CPU utilization Generic job names that cover the Query started tasks from the various z OS Address space CPU utilization subsystems Linux OS Linux CPU Query CPU Linux guests on z VM Workspace D then shows the WebSphere subsystems and workspace E the DB2 systems running Finally workspace F shows the WebSphere cluster running on z VM completing the picture of our application loads running on IBM System z9 109 Chapter 5 Scenarios and use cases 279 5 2 5 Summary We show the basic CPU activity on our main Enterprise view so that even as we monitor the service level agreements of our client facing channels we can view the CPU utilization as we vary the volumes Thus this
39. WLM LINK Service Class Allowable Terms Siete V VO Priority gB S f Table WLM Selected Servi V Footer V Managed System U Peadar V Percent CPU V Percent IFA V Percent IFA on CP Expression Value BAT_3V30 Selected batch importance 3 vel 30 B Y Workload Description Vid v Name V Type S E Table WLM All Service Class Resources information jea Query WLM Service Class Resources Fs EH workspace E lt Unnamed ca gt 5 Unnamed New E sUnnamed gt IMi Figure 4 58 Validation of the formula A new symbol is defined along with an expression to determine its value A part of this value is filled with some of the attributes coming from the source view Tip You can use the same process functions and operators to fill the value of the symbols defined in any of the target workspace queries Infrastructure Solutions Building a Smart Bank Operating Environment Advanced link Full usage of a newly defined symbol The target window of the dynamic link is the workspace named WLM Selected Service Class Open that workspace and perform the following tasks 1 Select the table view and open Properties 2 In the Style section of properties select Header 3 Check the box against Show 4 In the Text field enter the name of the symbol between the two dollar signs Figure 4 59 a Properties WLM Selected Service Class zOS 0 Views Table Views BAPLEX BA01 MVSSYS BA
40. a am jms BPDUpdateMdbConnectionFactory H Curent Connections OPool Percent Used lt lt v x jms BDWUpdateMdbConnectionF actory ji Jj TRFProcess Reply setbOWUndateReauest SetePDUodateReavest jms BPECFC gt gt o 1 2 3 4 EOWUpdat EPDUpdat eee aisant FI EJE Container statistics manx x J J AfterBOWUpdate AfterEPDUpdate 0 169 BACELLA BAO0C001 BASRO11 O Total Method Invocations BACELLA BADCO01 BASRO11 M Total Instantiates E Total Active Methods ne lt gt 0246810 14 18 22 26 30 Figure 5 10 Process component view Table 5 6 shows the base queries that we used to create the Logical view from the assigned agents in Figure 5 10 Table 5 6 Process view queries Assigned agent Query Assigned managed system J2EE Server WebSphere on z OS DB Connection Pools for OS 390 Query DB Connection Pools J2EE Server WebSphere on z OS J2EE Connector connection pools for OS 390 Query J2EE Connector connection pools J2EE Server WebSphere on z OS EJB Containers for OS 390 Query EJB Containers 270 Infrastructure Solutions Building a Smart Bank Operating Environment Figure 5 10 provides a graphical JPEG view of the process The Transaction Reporting Activity TRF issues the service call to CICS invoking our core system functionality On receiving a response from our core system the process performs the following actions within the same unit of work gt Web Service call update of the analytical database
41. autonomic technologies Infrastructure simplification along with systems management is the proof point that this IBM Redbook helps address It also provides the mechanism through which the other proof points are demonstrated This step involves optimization of IT resources and information life cycle management from the infrastructure perspective This book does not claim to deliver the ultimate solution to all these problems It shows how IBM strategies and infrastructure can be used to address their problems with the appropriate use of technologies and a set of example ISVs performing certain business functions A day at our bank This book uses a storyboard to drive the demonstration and to tackle the proof points clearly This story involves a day s activity in the bank It starts at 06 00 hrs in the morning The bank s clients are either returning home from the night shift leaving the Spanish nightclubs or are starting the day Table 1 5 shows details of the events that we typically run through for the Smart Bank showcase Table 1 5 Story board relating to a day in the life of the Smart Bank 06 00 a m Setting the scene Early We show low channel traffic coming from the automated morning at the bank teller machines ATMs and Internet channels with clients withdrawing cash for the day or accessing the Internet bank We show the injection mechanism perform a business transaction or two from our Internet bank and empha
42. available Earlier Tivoli Enterprise Portal Server was supported only on Windows platforms Therefore a lot of clients have their Tivoli Enterprise Portal Server running on Windows Figure 1 17 shows such a solution approach when using the Moveable Hub on z OS VMware ESX Server Windows Appl Sys Figure 1 17 Windows Tivoli Enterprise Portal Server with Moveable Tivoli Enterprise Management Server Hub on z OS The components are gt On Windows Tivoli Enterprise Portal Server The Tivoli Enterprise Portal Server is placed on Windows However high availability functions and mirroring functions are not supported and the switch in the Hot Standby Tivoli Enterprise Management Server is not recognized Remote Tivoli Enterprise Management Server The Windows based Tivoli Enterprise Management Server Remote acts as the Primary Tivoli Enterprise Management Server for all Windows based agents It also hosts all the distribution packages for the Windows systems 44 Infrastructure Solutions Building a Smart Bank Operating Environment IBM Tivoli Monitoring agents IBM Tivoli Monitoring agents for monitoring the server software such as the operating system and the DB2 Universal Database is installed on the Tivoli Enterprise Portal Server systems too These agents connect to the Windows based Tivoli Enterprise Management Server Remote as their primary server and to the AlX based Tivoli Enterprise Management Serve
43. gt The symbols used in the query in the target workspace extract in A1 are displayed in the dynamic link window A2 gt The table which is the only view in the target workspace B1 is shown in the dynamic link window B2 but as a header and footer only no data shown gt The dynamic link context and enable C1 is used by the TEP internally It uses these values to either offer or not offer the link on that row in that view true or false values shown in C2 gt Data coming from the source workspace is also displayed D1 224 Infrastructure Solutions Building a Smart Bank Operating Environment The structure of the target workspace is completely displayed in the left side of the dynamic link definition window If multiple views are available in this workspace this window displays all of them KJRITMO0 21 Link Wizard Ed Properties P Symbols V contextisAvailable v S Target Workspace S F Query WLM LINK Service Class Resources a Symbols Expression true y Allowable Terms 2 WLM Selected Service Class 9 212 V NODE G Values V SERCLASS Link S Ey Table WLM Selected Service Class Resources information Selected Row V Footer B Attributes V Header Fie Edt View Help z 6 BRean s View Snert Bark v Dax e0459 GA EE S LE EA
44. logical partition See LPAR logical tree 195 259 selected level 195 logical view 16 139 181 258 final objective 182 relative link 211 tree structure 202 LPAR 17 276 M managed system 50 150 181 266 management query 261 MDB 263 Message Driven Bean See MDB message server 155 moveable hub 38 276 MQSeries message queue 154 server 155 multichannel integration 269 multichannel transformation 10 N navigation subtree 126 navigator item 123 view 163 184 275 existing level 187 queue statistics tab 163 O On Off Capacity on Demand 13 Open Infrastructure Offering 272 open standard 271 P physical blade 283 physical tree 122 182 physical view 22 121 195 258 posting table 156 process choreographer 265 process EJB 262 simple RMI IIOP call 271 production network 86 programming model 280 Q quality of service 12 R Random Access Memory RAM 284 real time update 19 reference architecture 14 response time 20 135 258 retail bank 4 260 recognizable view 260 simplified logical view 260 router status 178 S SAN 49 288 Infrastructure Solutions Building a Smart Bank Operating Environment seeding operation 95 SERCLASS symbol 228 dynamic association 230 server list 82 service oriented architecture 9 service oriented architecture See SOA Services Inventory Query 266 Smart Bank client 185 248 demonstration 10 enterprise view 248 environment 180 infrastructure 247 logical view 250 tree 248
45. main menu 247 network workspace 252 node 180 operating environment 2 operations workspace 250 project 22 121 280 goal 22 proof point 8 root 246 server 180 showcase 1 32 148 192 202 258 css 244 architecture 19 demonstration 258 environment 24 image 231 infrastructure 154 logical view 242 menu 203 objective 4 operations workspace 250 proof points 23 rule 128 style 242 system 128 Welcome menu 250 workspace 252 Tivoli Enterprise Portal administrator 188 Welcome menu 247 SMS 131 SNMP data provider 177 SOA 18 131 257 model diagram 20 view 268 response time 136 service 133 Web services 138 STG 4 Storage Area Network See SAN Storage Management Subsystem See SMS systems management 3 250 273 showcase requirements 22 Systems Technology Group See STG T target workspace 201 internal content 223 TCP IP communication 45 technical architecture 1 TEPS 25 Tivoli Data Warehouse 28 Tivoli Enterprise 20 122 Tivoli Enterprise Management Server primary 33 Tivoli Enterprise Management Server Hub 25 26 66 Hot Standby configuration 36 logical gateway 28 move 41 store 26 Tivoli Enterprise Management Server Remote 25 port switching 41 Tivoli Enterprise Managing Agent 25 125 189 Tivoli Enterprise Managing Server 25 26 Tivoli Enterprise Portal 12 182 258 Tivoli Enterprise Portal Client 122 Tivoli Enterprise Portal client 25 Tivoli Enterprise Portal Server See TEPS U Universal Agent 125 171 274 use case 17
46. source workspace and Navigator view If you started the link wizard from a table row or chart point the Attributes are displayed Values Bin 3 setected Row EE Attributes V ProcessiD V Page Faultssec V Page File kBytes When you link to the target worksp H ma tl afiha nunsnnninn fen eer an ca ace Tivoli Enterprise Portal applies the result x Ie tavlenmane ta the tavanit oumbal om unas m rE 2 Delete Figure 4 39 Link Expression Editor panel The window then displays data in the three parts Figure 4 40 Properties Symbols y linklsEnabled V contextisAvailable Target Workspace F Query WLM LINK Service Class Symbols Y NODE v N o EQ Table WiMBelected Servi V Footer V Header KJRITMOO1I Link Wizard Define New Link WLM Details F Expression J Allowable Terms 5 Values E Link o fH Selected Row Attributes V Actual Host Y Average Storage v CSS Priority Y Class Flag V Duration V Goal Importance V Goal Percentile V Goal Type V Goal Value V WO Priority V VO Rate V Managed System V Percent CPU V Percent IFA V Percent IFA on CP V Performance Index V Period V Resource Group 1 Service Clase Y Average Response Time Figure 4 40 The dynamic link definition window Infrastructure Solutions Building a Smart Bank Operating Environment The Advanced Link
47. 0 BAPLEX MVS SYSPLEX 4 SYSGRS2 1 0 BAPLEX MVS SYSPLEX SYSWLM 2 0 BAPLEX MVS SYSPLEX IXCLO012 2 0 BAPLEX MVS SYSPLEX SYSMCS d 0 BAPLEX MVS SYSPLEX SYSDAE 3 2 BAPLEXMVS SYSPLEX SYSMCS2 4 0 BAPLEX MVS SYSPLEX xl 5 Hub Time Fr 03 17 2006 04 30 PM oe Server Available XCF Groups Data for Sysplex 9 212 128 31 WOLF1 Figure 3 3 The z OS navigation subtree For the Smart Bank showcase some applications have their own processes implemented directly in the operating system If these processes are not performing well the dedicated application fails Most of the rules reflect the requirements of the system programmers while a few rules reflect the requirements of the business managers In a large environment the system programmer or those in charge of the operations do not understand the impact of a missing task that is already started and the impact of this on a company s business Infrastructure Solutions Building a Smart Bank Operating Environment 3 1 2 IBM OMEGAMON for UNIX System Services V2 20 8X x a EA ps ke O File Edt View Favorites T Address http 9 212 128 31 1920 cnp kat bal EJ Go ar Tivoli Enterprise Portal File Edit View Help HH BRtAF SOCOWM SBSHUBAEAERVFSTEeE View Physical vi ne PM File Systems with 70 or more used space Z EH User Response Time A 108 WLM Service Class Resource OMEGACENTER Bridge 05 390 Unix U55 a By
48. 128 31 1920 cnpikd E EJ co Ar x a A pe ke E File Edit view Favorites I Tivoli Enterprise Portal File Edit View Help HHABREAD SOCOH SSWRBSBSEHERVOTEOA 3 View Physical oO 8 Z amp amp EDM Utilization O 8 O X amp DF Send Rate EDM Utilization cics DB2 5 CB01 BA01 DB2 E Thread Activity RE B g J Detailed Thread Exception Lock Conflicts Subsystem Management Log Manager Utility Jobs EDM Pool Buffer Pool Management Volume Activity CICS Connections IMS Connections DB2 Connect Server E E DW01 BA01 DB2 Bj amp DB Wait Percent O 8 O X amp OOF Receive Rate DB Wait Percent DDF Receive Rate E Physical System State Information Time Interval Waiting On DDF Global Trace EDM DB Wait Indoubt Threads Waiting Threads Waiting Users Waiting DDF Send DDF Receive ae Time Tape Mount Inactive Active Utilization Percent Threads On Limit On Locks For Threads Rate Rate procedat E NTT Si DB2 System CB01 MYS System BA01 C 5 Hub Time Sa 03 18 2006 02 22 PM ae Server Available System Status 9 212 128 31 WOLF1 ADMIN MODE Figure 3 5 The navigation subtree of IBM OMEGAMON for DB2 OMEGAMON for DB2 offers plenty of information on the DB2 subsystem running on z OS Figure 3 5 shows the navigation tree generated by the IBM Tivoli Monitorin
49. 2000 he joined Candle and focused on IBM WebSphere products and the management of these systems Since 2004 he has been a part of the IBM team in Germany working together with major financial services clients on deploying IBM Tivoli products in their environment He holds a Graduate Engineer Degree in Computer Science from the University of Erlangen Nuernberg Thanks to the following people for their contributions to this project Fred Winegust IBM Canada James Goethals IBM USA Luis Aused L pez IBM Spain Nathalie Defez IBM France Peter Fowler IBM USA Robert Honer IBM USA Sharmela Pattabiraman Editor ITSO Bangalore India Preface xi Become a published author Join us for a two week to six week residency program Help write an IBM Redbook dealing with specific products or solutions while getting hands on experience with leading edge technologies You will team with IBM technical professionals Business Partners and or clients Your efforts will help increase product acceptance and client satisfaction As a bonus you will develop a network of contacts in IBM development labs and increase your productivity and marketability To find out more about the residency program browse the residency index and apply online at ibm com redbooks residencies html Comments welcome xii Your comments are important to us We want our IBM Redbooks to be as helpful as possible Send us your comments about this IBM Red
50. 21 provides an overview of all the servlets and JavaServer Pages executed in the selected Web container This workspace is application focused The response time given is specific to each application This means that no system wide rule can be applied except for a general rule such as no transaction must on an average last for more than xx milliseconds amp x a EA pe se aO amp File Edt yew Favorites I Address http 9 212 128 31 1920 f enpykdk E EJ Go y 2 Tivoli Enterprise Portal File Edit View Help HHBR AM S OO C SQSWURBRBERERYM EA 3 View Physical m MT Ten Worst Average Response Times All Workloads Suspected Memory L FssSerlet Heap Usage x Garbage Collector Ac PlAQutput jsp Pool Utilization BP Output jsp 7 7 R 5 F x 7 F 7 3 3 i A p In flight Workloads o 200 400 600 800 1000 1200 1400 1600 1800 Longest Running Wo HTTP Sessions j lt Datasources Bi Lock Analysis CTG Summary JMS Summary Milliseconds FssProcessServiet k Web Applications j PICU iaai O Sentet Eror Rate Co 6 JSP 1 2 Processor H seriet Request Rate krwrtmozst 52 Navigator updates pending F Physical n khan Servlets JSPs for Selected Web Application InvokerSerlet Servlet Concurrent Requests Response Time Error Rate Request Rate Interval Time SerletJSP Name Sam
51. 257 W Web service 31 monitoring agent 31 Web Services Definition Language See WSDL WebSphere Application Server 17 124 261 282 agent 274 deep dive analysis 31 defined data source 145 IBM OMEGAMON 124 IBM Tivoli Composite Application Manager 139 instance 273 workspace 142 resource use 139 WebSphere Business Integration 125 server foundation 18 WebSphere MQ 18 132 262 activity 269 IBM OMEGAMON 132 logical view 268 monitoring 149 product 150 queue 269 system 150 WLM 21 258 service class resource 218 Work Load Manager See WLM workspace administration mode 182 WSDL 18 262 Index 289 Z z OS LPARs configuration values 125 290 Infrastructure Solutions Building a Smart Bank Operating Environment Infrastructure Solutions Building a Smart Bank Operating Environment Ca Redbooks el 0 5 spine 0 475 lt gt 0 873 250 lt gt 459 pages Infrastructure Solutions Building a Smart Bank Operating Environment Using a live showcase to demonstrate how to deliver key banking projects Building an SOA with IBM System z and IBM BladeCenter with IBM z OS and Linux Using IBM Tivoli Monitoring V6 and Tivoli Composite Application Manager V6 IBM created the Smart Bank showcase to demonstrate to retail banking clients the benefits of IBM products services and solutions in addressing their key business issues The Smart Bank showcase covers different solutions areas such as IT servic
52. 258 Atomic Consistent Isolated and Durable See ACID attribute group 28 122 EXCEPTION_DETAIL 174 WORKLOAD_DETAIL 175 B Banking Data Warehouse See BDW Basel II compliance 13 credit risk reporting 15 report 15 BDW 4 BPEL 19 270 branch server 10 263 280 business continuity 2 21 Business Event Publisher See CICS BEP Business Process Execution Language See BPEL C CBM 14 CICS BEP 20 154 activity 163 component 158 159 Dataspace Server 158 event connecter 158 event connector 156 event monitor 169 for MQSeries 154 key features 154 Messaging Server 158 plan 169 process 161 product 269 setup process 158 CICS region 130 192 213 current affectation 192 CICS Transaction Gateway 262 263 mechanism 264 Component Business Model See CBM core system 4 10 258 262 API 261 proprietary mechanism 261 service oriented invocation 262 transformation 18 257 CRB SRVINQ 269 Copyright IBM Corp 2006 All rights reserved D DB2 55 84 94 265 279 282 demonstration proof points 10 derived attribute 176 dynamic link context 224 definition 215 window 222 240 utilization 231 E Early Support Programme See ESP EJB 22 139 263 report activity level 139 Enterprise JavaBeans See EJB enterprise view 17 203 258 ESP 4 ETL 19 Extract Transform and Load See ETL F Fair Isaac TRIAD 17 Fidelity Corebank 4 application 265 Financial Services Architecture See FSA Financial Services Data Model See FSDM financia
53. 3 1 The current architecture of the Smart Bank showcase 18 The current architecture of the Smart Bank showcase comprises different features which are described in the following sections Core system Our bank s core system is Fidelity Corebank V4 2 which is a modern retail banking application based on real time update principles to a database based on the Financial Services Data Model from Information FrameWork and physically implemented in DB2 for z OS It natively runs on CICS and is predominantly written in Common Business Oriented Language COBOL It is supplied with a comprehensive set of application programming interface APIs that allow banks to interface with its business functionality In V4 2 Corebank natively employes a proprietary interface technique using WebSphere MQ as the transport protocol Figure 1 5 displays the architecture overview diagram from a physical perspective showing where the core system is implemented in relation to the other systems Multichannel architecture Our multichannel architecture uses the Corebank proprietary WebSphere MQ mechanism to interface to Corebank We created a Java application to receive our channel requests and interface them to our core retail banking system This application uses the Struts framework and writes through Java Message Service JMS and the Corebank interface Java classes supplied to WebSphere MQ This application is deployed to the WebSphere Application Server on z OS for
54. 3 8 F S g 3 F S e a a amp a a z 3 z 8 z Al gt j A CB Hub Time Wed 03 22 2006 03 28 PM I Server available Network 9 212 128 31 SYSADMIN Neils view Figure 4 72 The Smart Bank Network workspace Following are some features pertaining to this workspace gt Most of the Smart Bank showcase workspaces contain graphics They are easy to read can offer new links and are easy to use gt Care must be taken while designing a graphic preferably built by using Microsoft PowerPoint gt Pictures are often included in the graphics Resuming the Smart Bank Logical view The Smart Bank showcase Logical view is designed to support the showcase All the features described in this chapter are not used The design and organization of this Logical view can be used as a sample to create the one a user requires Then using the other functions demonstrated in this book situations advice links and so on a Logical view that meets all the supervision requirements of a user is easy to build 4 6 Logical view Lessons learned 252 Following are some of the guidelines to follow when developing a Logical view gt Keep the number of embedded levels small enough three or four because the user can get lost in the depth of a large tree gt Avoid too much information in a graphic view Keep the graphic simple Use the situation advice and their possibilities to allow the user get more information when required In
55. 75 8 In Figure 2 20 on page 73 when the IP communication protocol is set press Enter The SNA Communication Protocol screen Figure 2 24 is displayed Specify the SNA parameters The applid prefix value is used to create all the VTAM APPLIDs required by the Tivoli Enterprise Monitoring Server These applids begin with a prefix and end with a specific value that makes each applid unique These applids are contained in a VTAM Major node Specify the SNA communication values for this TEMS Applid prefix gt TIVHUB Network ID gt PSSCBA NETID value from SYS1 VTAMLST ATCSTRnn Enter Next Fl Help F3 Back F6 Applids COMMAND gt Figure 2 24 ICAT SNA Communication Protocol configuration screen After the SNA communication protocol is set press Enter This takes you to the Tivoli Enterprise Monitoring Server configuration main menu shown in Figure 2 17 on page 70 from where the configuration process continues In this screen perform the following tasks a Select option 4 to create the runtime members These members are created in the runtime libraries for this run time environment b Select option 5 to configure the persistent data store This step is optional However this option is required if you are using the data warehousing function c Finally select option 6 to complete the configuration This generates a list of procedures that must be performed after you exit ICAT in order to finalize the installation and conf
56. A pop up opens Enter the name of the new symbol as shown in Figure 4 52 In our case the name ProcHeader is used Properties Expression 8 Symbols true Y contextisAvailable v finkisEnabled 8 Target Workspace Fe Query WLM LINK Service Class Symbols V NODE Values V SERCLASS Link 2 E Table Wi Selected Servi 5 amp Selected Row V Footer Attributes Y Header V Actual Host Y Average Response Time Allowable Terms ProcHeader E V Goal Type V Goal Value V VO Priority V VO Rate V IFA Service Units Y Managed System V Percent CPU V Percent IFA V Percent IFA on CP V Performance Index V Period Loo U Re irc Groun Figure 4 52 Naming the new symbol Chapter 4 Customizing the Logical views 233 3 The newly defined symbol is then placed in the left hand side of the window A in Figure 4 53 As with the symbol in a query select an attribute B in the bottom right section in order to assign it a value C KIRITMO021 Link Wizard Edit Link WLM Details x Properties Expression Symbols sk w TableRow ATTRIBUTE MULMPR CLSNAME contextlsAvailable y linklsEnabled L v w Gear Test eo Target Workspace Allowable Terms 7 me S F Query WLM LINK Service Class 8 Symbols Y Average Storage V NODE V CSS Priority V SERCLASS Y Class Flag E Table WLM Selected Servi V Duration V Footer V Goal Imp
57. Active Receiver Channels Diinactive Receiver Channels M Active Sender Channels Diinactive Sender Channels M current Requesters Bi inactive Requesters H Active Server Channels Number of Channels Application Statistics Bi 24 Buffer Pool Statistics g Channel Definitions Channel Initiator Status Cluster Queue Manager Dead Letter Queue Message Log Manager Performance Message Manager Performar MQSeries Events 4 FT W inactive Server Channels Page Set Statistics cso H Auto Defined Cluster Channels Queue Definitions Queue Manager Status Queue Statistics ie CsQ2 E WIMA fa MVS Operating System FM Transmit Rates Channel Name CRBOQM C10 a f 05 390 Unix USS _ capaci a E E nM CRBQM C10 __ kFwrtmo2st 12 Navigator updates pending CRBOMICIA q a o 1 oo a Physical KB per Second Channel Performance Channel Channel Connection Channel In Doubt XmitQ Message Transmit Batches Cur CurBatch CurBatch CurMsg Last Send Name Type Name Status Status Depth Count KB Sec Complete Defn LUW ID Messages SeqNo Date amp Time CRBQM C10 SVRCONN 10 1 1 127 Running No 0 0 0 00 0 Yes 0000000000000000 0 O 03 16 06 16 22 CRBQM C10 SVRCONN 10 1 1 127 Running No 0 0 0 00 0 Yes 0000000000000000 0 QO 03 16 06 16 50 CRBQM C10 SVRCONN 10 1 1 127 Running No 0 0 0 00 0 Yes 0000000
58. Attributes in Figure 4 47 click Service Class B This displays a string in the top right section C fl KJRITMOO1I Link Wizard Define New Link WLM Details s Properties 5 Symbols y linklsEnabled Y contextlsAvailable S Target Workspace amp F Query WLM LINK Service Class Symbols Y NODE v o FER Table WLM Selected Servi V Footer V Header Expression kfw TableRow ATTRIBUTE MUJLMPR CLSNAME Allowable Terms Y Class Flag Y Duration V Goal Importance V Goal Percentile V Goal Type V Goal Value V VO Priority V WO Rate Y IFA Service Units Vv Managed System V Percent CPU V Percent IFA V Percent IFA on CP Y Performance Index V Period V Resource Group y Service Class V Service Class Lyscription Vv Workload Vv Workload Description Vid v Name V Type m FA Table JAIM All Service Class Pacoueces information Figure 4 47 Selecting the Resource Class attributes Infrastructure Solutions Building a Smart Bank Operating Environment 4 Click Test in zone A in Figure 4 48 A pop up opens B It contains the name of the Service Class that is displayed in the line you selected C in the view at the beginning of the dynamic link definition a File Edit View Help e n9 B Mc a REA RRE r a EA O 3 View Smart_Bank mM mnax eae EEE
59. BAO2 z OS LPARs DB2 z OS z OS Systems DB2 System Status DW01 and CB01 DB2 systems on BDW and BAO1 and BAO2 z OS LPARs FSDM Chapter 5 Scenarios and use cases 273 Alert Assigned agent Assigned managed system BladeCenter gt Linux Systems Linux OS Blade 2 Linux OS and Universal Branch gt Linux Systems WebSphere Application Agent Servers Server Agent Blade 3 Linux OS Linux Systems Universal Agent Blade 4 and Blade 5 Linux OS and WebSphere Application Server z VM Branch Linux Systems Linux OS Inx1 Linux OS and Universal Servers Linux Systems WebSphere Application Agent Server Agent Inx7 Linux OS Linux Systems Universal Agent Inx4 and Inx5 Linux OS and WebSphere Application Server Siebel UNIX Systems UNIX OS SAFSS POWER4 blade with AIX Analytics UNIX Systems WebSphere Application WebSphere Server Agent Tivoli Link Workspace Monitoring Linux Link Workspace utilization Enterprise Link Workspace view 274 Infrastructure Solutions Building a Smart Bank Operating Environment Figure 5 12 shows the main Edit Navigator view in the TEP that was used to assign the different physical agents to the alerts shown in Figure 5 11 The different physical and logical machines defined to our system and subdivided by the operating system are seen Note The Linux guest machine on z VM Int1 was not used in the context of this book Edit Navigator View Target View Neils view Source View Physical
60. BAQ1 PSSCBA KO1OENC CANCTL Dubbed Address Spaces BPXPRMxx Values 4 Files Fl Kernel Logged on Users Processes 1 Services Management Agent E la aa gt PE Dercent used menpa 08 0 3 Physical CandleHome SERVICE usIppiixm SERVICE IBARA t usi ipp ctg6 BARA7 1 ust ippiixm BARA71 Status Mount Point File System Name la poren VOLSER Mode Security SETUID Status ga DDNAME Seconds F m hororonorooor 0 vorar oeron rene on bace OMVS WAS BACELL HFS BA0810 RDWR SECURITY SETUID Active 102526 Sysoogsa gt IBARA71 OMVS BARA71 ROOT BA0S10 READ SECURITY SETUID Active 102526 SYS00005 1 IBARAT 1lusrilppicicsts CICS USR LPP CICSTS HFS 11 BA0CI RDWR SECURITY SETUID Active 102526 SYS00033 Al IBARAT lustiippicicstsicicsts22 CICSTS22 USR LPP CICSTS CICSTS22 HFS 45 BAOCI RDWR SECURITY SETUID Active 102526 SYS00034 IBARAT Justiippicicstsicicsts23 OMVS USR LPP CICSTS CICSTS23 58 BA0512 RDWR SECURITY SETUID Active 102526 SYS00035 BARA Iiustilppicicstsicicsts23d3 OMVS USR LPP CICSTS CICSTS23 03 EJ 5A0512 RDWR SECURITY SETUID Active 102526 SYS00036 IBARAT ustiippicicstsicicsts23d4 OMVS USR LPP CICSTS CICSTS23 D4 Gy BA0S11 RDWR SECURITY SETUID Active 102526 SYSO0037 IBARAT ustiippicicstsicicsts31 OMVS USR LPP CICSTS CICSTS31 7 BAOSI1 RDWR SECURITY SETUID Active 102526 SyS00038 BARA Hustiippicicstsicicsts32 iter2
61. BFR SF SS 8B BSF SF BB Soe ss es ss es sh ses 8 ss Fs Fs ss s 8 ee C Heure du concentrateur ven 17 03 2006 W Serveur disponible All Region Transaction Overview FLEBE FLEBE Figure 4 73 A graphic navigator approach You can define a Logical view to perform the following functions which are based on customers realizations gt Manage a CICSPlex To manage CICS regions over a sysplex create a Logical view that shows the relationship between the terminal owning region TOR application owning region AOR and the others regions and create a subtree for each collection of regions that manage a set of applications gt Manage well known problems Build a Logical view that includes all the information that indicates that one of your current known problems is starting and add actions inside in order to quickly react and solve it gt Handle the operation team s requirements Interview your operations team and ask them which data they require to have better control over the systems and build Logical views to fulfill their requirements gt Reorganize the physical data Define a graphic that maps the physical emplacements of your systems and then tag and drop each system into its corresponding place from the Physical view This Logical view can be built quickly and the existing alerts definition retained 254 Infrastructure Solutions Building a Smart Bank Operating Environment gt Follow up on applications Build
62. Connection Wait Time which indicates that the request going to this data source is in the queue before it is executed _ A x 0o 9 x 2 pe se ea amp File Edt View Favorites T Address http 9 212 128 31 1920 enp kat E J Go Ar Tivoli Enterprise Portal Fie Edit View Help mEnE ci a o E EAE r E E View Physical g FI Average Datasource Wait and SQL Processing Times g Pool Utilization In flight Workloads Longest Running Wo HTTP Sessions Lock Analysis CTG Summary lt 4 JMS Summary aj Web Applications EJB Containers DB Connection Pools EJ ed ky KFWITMO25I 60 Navigator updates pending a Physical Datasources Current Interval Dlaverage Connection Wait Time Dl Average Query Processing Time E Average Update Processing Time spuosas ii oop A DO jdbo COREBANKds jdbo BDWds java comp envijdbc BPEDB Sample Datasource Date and Time Name 03 406 16 06 05 60 jdbc COREBANKds DB2 DSNO8015 286 13 0 216 0 0 000 0 C 03 14 06 16 06 05 60 jdbc BDWads DB2 DSNO8015 211 67 1 116 0 0 000 03 14 06 16 06 05 60 java comp lenwidbc BPEDB DB2 DSNO08015 52 19 0 316 0 0 000 0 Jl x f 5 Hub Time Di 03 1 4 2006 04 06 PM ca Server Available Datasources 9 212 128 31 WOLF1 Figure 3 20 The data source workspace Chapter 3 Using Physical views 145 The Web Applications workspace This workspace shown in Figure 3
63. Enabled Yes No None 1 O 10 26 04 1 03 21 06 16 36 24 0 19 No 3203 0 80 40 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 21 06 16 35 24 0 19 No 3005 0 80 37 5 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 21 06 16 34 24 0 19 No 2751 0 80 34 3 No Enabled Enabled Yes No None 1 O 10 26 04 03 21 06 16 33 24 0 19 No 2461 0 80 30 7 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 21 06 16 32 24 0 19 No 2219 0 80 27 7 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 21 06 16 31 24 0 19 No 1987 0 80 24 8 No Enabled Enabled Yes No None 1 O 10 26 04 1 4 gt C Hub Time Tue 03 21 2006 04 41 PM ee Server Available Recent Queue Statistics 9 212 128 31 SYSADMIN Figure 3 34 Queue CICBEPQLOCAL1 filling up due to workload generation c Start the FABBEP batch to read all the messages that are currently in the queue The messages will be processed and the DB2 posting table populated as described in 3 3 2 Using CICS Business Event Publisher to populate the banking data warehouse database on page 157 The result on the TEP is shown in Figure 3 35 This figure shows that several new metrics have changed e Output Opens is still at 19 because the CICS Business Event Publisher process is still running e Current Depth is now going from 7233 to O during one interval All the messages present in the queue have been processed immediately after starting the FABBEPbatch e Full decreases and is at 0 e M
64. Figure 4 62 Smart Bank showcase First level 4 5 2 Using the Smart Bank showcase style Using the style features the Smart Bank team designed an alternative to the previous display Figure 4 62 The first level workspace provides access to the data in another way as shown in Figure 4 63 The standard icons have been changed and replaced by pictures BHaRIIr a Ex Hoa eS Building a Smart Bank operating environment PRO OA E p Op O ral gt i nao CE Hub Time Thu 03 16 2006 06 27 PM AP Server Available Smart_Bank 9 212 128 31 SYSADMIN lt 3 Smart Bank _ Figure 4 63 The Smart Bank showcase style 242 Infrastructure Solutions Building a Smart Bank Operating Environment 4 5 3 Setting up a style in a graphic view To set up a style in a graphic view perform the following tasks When the graphic view is displayed right click it to access its property menu Figure 4 64 Click the plot area to access the background and style setup Smart Bank 9 212 128 3171 SYSADMIN ist X File Edt View Help a Sse eee a E ci i Ss Ve a eee X gt ADARROAD SCO SOUBREHAERF S A eA ig Graphic View manx boog ax o ol a 2 Properties Smart_Bank Pe Smart_Bank Preview 53 0 Views E Notepad Views Graphic Views BOSS RAG ah x loo S D Graphic View g all a Options Show Title Text
65. Goal Goal i Average Perform Authentification System Class Peroa Type e value DUration Response Time Indea 3 B Banking BAPLEX BA01 MVSSYS BAT_DISC 1 Discret 0 nia 0 0 0 a acs Sa eae Y ET PN TIAP ce RYOTE A ai DB2 Ml Propertie X MQSer TCP z0S Preview wens C a ins awe E WLM Selected Service Class Resources information g sa EOS chal Ey NU SetecteciSerace cas WLM Selected Service Class Resources information a ag atm Managed service nnal Goal coal coat T Goal Ta es Web Quer ditor X S zBank GDPSH 7 PROCESS S04 a ci cal p Description i w Vape_orives Tal Description ILM Service Class Resources information for this MVS image a Wy Topuser E3 User_Response_Time WLM_Service_Class_Resov SRIWLMLINK Service Class Service cass Data Source TEMS HUB CMS ip pipe 10 1 1 29 2018 F WLM Serv Class for Ser Last Modified F WLM Service Class Rese OMEGACENTER Gateway Last Modified on Mon 03 13 2006 12 16 PM Last Modified by SYSADMIN Specificati 5 OMEGAMON for MVS pecification Query Results Source a OMEGAMON for OPR Specification Y Managed Service i Goal Goal a E E IN Porod a e e raie i v v v F SERCLASS T Physical E Sr Ie a Figure 4 35 Adding a symbol in a query A new workspace is defined It contains the Navigator tree and one view A new query is defined as also a new symbol in it 218 Infrastructure
66. Hoa E a Banking BAPLEX BAOT MVSSYS__ BAT_DISC 1 Discret O nia 0 0 00 acs f BAP I WVSSYS BAT_3V30 O Medium 30 oO o DB2 BAT_3v40 io o 0 o MQSeries BAT_3V50 io 0 Medium 0 oj TCP _ BATCH ocio 0 Medium 0 o WebSphere 3 BATCH_HI 102 0 Medium 0 0 YS BATCHHOT 1 io 0 Highest 0 8 Teller Channel BATCHL 0 oj ATM 0 o D Ed Web S E 0 0 1 5 iE zBank GDPS HyperSwap CICS_TOR 0 0 1 PROCESS SOA BAPLEX BAOUMVSSYS OMVSDFLT 0 4 i BAPLEX BA01 MYSSYS PR_DEFLT 1 AvgResp 0 0 PR_IOPA1 1 AvgResp 0 0 i 1 AvgResp 0 13 1 AvgResp o 0 0 1 AvgResp 0 0 i PR_TRF 1 AvgResp Lov 600 0j 0 00 PR wEB 1 AvoResp Ojlow 500 oj 0 0 00 SYSOTHER 1 SysGoal_ O wa 0 0 0 00 LEX B 1 SysGoal 0 nia 0 0 0 0 00 BAPLEX BA01 MVSSYS_ SYSTEM 1 SysGoal 0 n a 0 0 _ 0 0 00 BAPLEXCBA01 MYSSYS TRX_ABI 1 AvgResp 0 Low 600 0 0 0 00 BAPLEX BA01 MYSSYS TRX_ABP 1 AvgResp 0 Low 800 0 0 0 00 3 TRX_ACAL 1 AvgResp 0 Low 800 0 0 0 00 3 TRX_ACD __ 1 AvgResp 0 Low 800 0 0 0 00 1h _ACDO 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BAO1 MVSSYS TRX_ACDT 1 AvgResp 0 Low 800 0 ol 0 00 BAPLEX BA01 MVSSYS_ TRX_ACW 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BA01 MVYSSYS_ TRX_APIA 1 AvgResp 0 Low 500 0 0 0 00 BAPLEX BA01 MVSSYS_ TRX_APIC 1 AvgResp 0 Low 900 0 0 0 00 BAPLEX BA01 MYSSYS_ TRX_ATOF 1 AvgResp 0 Low 800 0
67. Low Candidate Infrastructure Solutions to Link Customer Imperative amp Business Rationale Increase Business Flexibility To drive growth through new capabilities and enhanced value propositions Optimize IT Environments To enhance efficiency across your IT resources including voice data and network Enhance Business Resilience amp Security To protect and strengthen your financial institution Figure 1 1 Affinity mapping of IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 Systems management Within the IBM infrastructure solutions reference architecture one of the key architectural decisions around optimizing IT environments is systems management which aims to perform the following functions gt Align the IT infrastructure with business goals gt Increase resource utilization gt Improve personnel productivity gt Increase application availability gt Create an infrastructure that is driven by business priorities gt Create a flexible infrastructure that adapts to changing business requirements and gain more control of that infrastructure to provide more business agility Before going into the details of systems management and monitoring let us consider what we are monitoring and what we are trying to show Chapter 1 Introducing the technical architecture of the Smart Bank showcase 3 1 1 2 Objective of the Smart Bank showcase T
68. Memory la La Open Crypto_Service_Unavailable BAPLEX BAQ2 MVSSYS E BH Heap Usage B Ope Crypto_Internal_Error BAPLEX BAO2 MVSSYS Cryptographic Onen ree Space_Pct_Critical TIVSREMT BA02 STOR Ss SMS Storage Gr Running Node_Agent Running Application_Server Running Application_Server C Hub Time Mo 03 13 2006 10 30 AM 7 Server Available WebSphere Application Server OS 390 9 212 128 31 WOLF1 Figure 3 15 WebSphere Application Server z OS default workspace 140 Infrastructure Solutions Building a Smart Bank Operating Environment Figure 3 16 shows the customized workspace It now includes the OMEGAMON WebSphere Application Server on z OS Systems agent log and the WebSphere Application Server error log across all the monitored servers Q Tivoli Fie Edit View Help 5 dae Enterprise Portal e Ste Aa sS View Physical g 08 g i Storage Subsystem a fy TIVSREMT BAO1 STORAGE w EEE sees Fg BAOL KWWA Agent Events Application Server Error Logs Application Trace Files J2EE Server E AACELL BBOCOO1 AASRI 5i BACELLA BAOCOO1 BASF Application Server Ir All Workloads Suspected Memory L Heap Usage u Garbage Collector Ac Pool Utilization In flight Workloads Longest Running Wo HTTP Sessions Datasources HHH 0008 lt gt KFWITMO25I 56 Navigator updates pending E Physical Sphere Application Si e
69. Modes E Dispatcher TCB Pools ER Dump Analysis E Dump Details E Enqueue Analysis v Is m iis a a Physical N TakeAction O 8 O x E Terminal menx 3 A Take Action a 4 Action Name sSelect Action vi Command Destination Systems Hub Time jeu 03 09 2006 10 05 AM ak Server Available DB2 Summary 9 212 128 33 SYSADMIN Figure 4 31 Result of a relative link 4 4 4 Defining an advanced link An advanced link is a powerful tool It allows you to select data from one view in a workspace and use it to dynamically filter the data on the targeted workspace As an example the Smart Bank showcase team wants to apply specific service levels to its VIP clients When alerts come in the team wants to deep dive into the data pertaining to only the VIP clients A jump from one view in a workspace to another view with data selection is the reason behind the dynamic links When an advanced link is used the link takes data from the selected part of the current view source workspace goes to the target workspace and uses the selected data as filters At the end of the link process the target workspace shows only the pertinent data relating to the selected data To filter the data on the target workspace the dynamic link function uses variables These variables called symbols are set up in the queries used in the target workspace 214 Infrastructure Solutions Building a Smart Bank Operating Environment Therefore in or
70. OMVS USR LPP CICSTS CICSTS32 1TER2 74 BA0S14 RDWR SECURITY SETUID Active 102526 SyS00039 IBARA 1ustiippictgs00 OMVS CTG500 8 BAOS12 RDWR SECURITY SETUID Active 102526 8Y800031 BARA Tusrilppictg501 OMVS CTG501 4 BA0S12 RDWR SECURITY SETUID Active 102526 SYS00032 IBARA 1 usrilppictg6 CTG6 HFS l EXE BAOSP1 RDWR SECURITY SETUID Active 102526 SYS00030 BARA t usrippicyanea OMVS BARA 1 CYANEA EEJ BA0S13 READ SECURITY SETUID Active 102526 sysooo09 C Hub Time Sa 03 18 2006 01 58 PM a Server Available Mounted File Systems 9 212 128 31 WOLF1 ADMIN MODE Figure 3 4 The physical tree of OMEGAMON for USS OMEGAMON for USS provides a deep insight into the UNIX System Services running on z OS Because the implementation of the WebSphere Application Server and the TCP IP stack are highly dependent on a healthy USS subsystem under z OS this monitor helps keep the system up and running Figure 3 4 shows that many mount points are affected by lack of free space which may lead to a major system outage For the Smart Bank showcase several situations are created to keep the file system clean in order to have all the required mount points up and running along with all the required USS processes in the system Later these rules are used partly in order to set up the Application Logical views Chapter 3 Using Physical views 127 3 1 3 IBM OMEGAMON for DB2 V3 10 128 fX ddress http 9 212
71. Operating Environment 1 1 3 The banking sector s current key business drivers This strategic input came from the Financial Services Sector FSS and the Global Business Services GBS and its IBM Institute of Business Value The CEOs of retail banks currently face major issues and challenges the most important of which are as follows gt Banks are seeking new revenue growth and client profitability strategies to compete ina competitive environment gt Outdated core systems and poor merger and acquisition M amp A integration are making it difficult for banks to respond to the changing conditions gt New threats and regulations are necessitating investment in compliance measures and new risk management strategies Table 1 2 Table 1 3 and Table 1 4 look at these issues in detail identifying some of the challenges and the key recommendations from IBM GBS to banks Table 1 2 Revenue growth and client profitability Industry issue 1 Revenue growth and client profitability Challenge for banks To be able to exploit client data so that they can increase the profitability of existing clients through targeted product and service offerings Identify untapped revenue sources and be able to develop unique value propositions based on their business intelligence and thereby increase competitive differentiation Recommendations Shift from product focus to client needs Client segmentation profitability focus Multichannel delivery serv
72. Predefined Dynamic Dynarr Name Name Subsys Jobname Date amp Time Status Type Depth Maximum Queues Queues Queues Queues Queues Queues Perm Qs Temp CSQ1 BA01 CSQ1 CSQ1MSTR 03 15 06 13 41 05 Active MVS 0 572 561 1 10 1 32 529 CSQ2 BA01 Not Available Inactive MYS 0 0 0 0 0 0 0 0 WIJMA BA01 Not Available Inactive MVS 0 0 0 0 0 0 0 0 JE DES z 05 Hub Time Do 03 16 2006 04 14 PM IB Server available MQSERIES 9 212 128 31 WOLF1 Figure 3 24 The physical tree of OMEGAMON for WebSphere MQ monitoring Chapter 3 Using Physical views 149 150 The following workspaces exist for z OS only Application statistics Application debugging Buffer pool statistics Channel initiator status Message manager performance Page set statistics vvvvvy The Error Log Workspace is not available on z OS systems That is why it is not displayed in the window shown in Figure 3 20 on page 145 The OMEGAMON for WebSphere MQ product is useful for executing the following tasks gt Collecting and analyzing MQSeries specific data for all your remote and local WebSphere MQ queue managers from a single vantage point gt Providing many useful workspaces that you can use to track trends and understand system problems gt Providing the ability to view information about each WebSphere MQ system you are monitoring This information is useful for Monitoring the performance of each WebSphere MQ managed system and helping iden
73. SPIPE port number gt Secure IP PIPE IP6 SPIPE port number gt Secure IP PIPE for IPV6 IP UDP port number gt Non secure NCS RPC IP6 UDP port number gt IP UDP for IPV6 Enter Next Fl Help F3 Back COMMAND gt Figure 2 29 ICAT Advanced communication configuration screen 5 After the communication is made between the primary Hub and the Remote Tivoli Enterprise Monitoring Server return to the main screen Figure 2 26 and continue with the configuration options To verify the SNA communication between the primary Hub Tivoli Enterprise Monitoring Server the remote Tivoli Enterprise Monitoring Server and the agents use a VTAM display applid as explained earlier and displayed in Figure 2 23 on page 75 The various agents that must be installed must also be configured This is described in the individual installation and customization documentation 80 Infrastructure Solutions Building a Smart Bank Operating Environment 2 1 6 OMEGAMON XE Tivoli enterprise management Initialization checklist for the server and the agent The OMEGAMON Engine Service is a collection of basic z OS and communication service routines built specifically for the z OS environment All OMEGAMON XE Tivoli enterprise management server and Tivoli Enterprise management Agent address spaces that have been started load and use the services of OMEGAMON Engine Service The successful initialization is noted by the message KLVIN408 in the R
74. Smart Bank project goals demonstrate the business proof points through the TEP using the Logical and Physical views in order to show the bank running at full volume and handling the use cases thrown at it during different times in a day gt Measuring the following Operational online and batch throughput Response time across our channels to clients and business units Utilization of our IT resources primarily CPU but also I O and memory Monitoring and managing systems availability and pinpointing problem areas Demonstrating the scalability through TEP and showing how IBM Tivoli Monitoring can assist in this aspect 22 Infrastructure Solutions Building a Smart Bank Operating Environment gt Showing control of the environment from a single point Although automatic processes adjust the system response based on the business parameters there are occasions when direct manual action is required and the environment adjusted as with the On Off Capacity on Demand scenario This is required because this demonstrates how flexible the infrastructure is and despite being virtual is capable of quickly responding to the demands of the business 1 3 3 Use cases this IBM Redbook focuses on The Smart Bank showcase lays out a number of business proof points To demonstrate these we created a number of use cases that simulate events at different times of the day in the bank We deliberately decided to focus on a few of the more impo
75. Solutions Building a Smart Bank Operating Environment Accessing the advanced link definition To access the advanced link definition perform the following tasks 1 Inthe workspace named WLM All Service Class select a line from the table and right click it 2 Select the Link To gt Link Wizard option Figure 4 36 Important Make a note of the Service Class name displayed in the line that you select in order to start the link definition This name is used later in this chapter File Edit View Help gt FABRBRGAA STOO ll SQwWRBSERAERAOTEeS ALM All Service Class Resources information ven brne DX amp og 1 Smart_Bank WLM All Service Class Resources information Teller Managed Service 3 Average i Authentification System Class Percentile Importance Value pratan Response Time Hoa 8 Banking BAPLEX BAO1 MYSSYS BAT_DISC 1 Discret 0 nla 0 0 0 i a CICS BAPLEX BA01 MVSSYS BAT_3V30 1 Velocio 0 Medium 30 0 0 0 00 DB2 BAPLEX BA01 MVSSYS BAT_3V40 1 Velocio 0 Medium 40 0 0 0 00 MQSeries BAPLEX BAO1 MVSSYS BAT_3V50 1 Velocio 0 Medium 50 0 a 0 00 TCP BAPLEX BA01 MVSSYS_ BATCH 1 Velocio 0 Medium 25 0 a 0 25 1 WebSphere BAPLEX BAQ1 MVYSSYS BATCH_HI 1 Velocio 0 Medium 30 0 a 0 00 BAPLEX BAQ1 MYSSYS BA
76. The scope of these functions and the related products are included in the IBM Tivoli Composite Application Manager The following products are used in the Smart Bank project gt IBM Tivoli Composite Application Manager for WebSphere Application Server gt IBM Tivoli Composite Application Manager for SOA gt IBM Tivoli OMEGAMON XE for WebSphere Application Server on z OS IBM Tivoli Composite Application Manager for WebSphere IBM Tivoli Composite Application Manager for WebSphere results from the merger of the following two standalone products into one gt IBM WebSphere Studio Application Monitor gt IBM Tivoli OMEGAMON XE for WebSphere Application Server on z OS These products now share a common data collector to get the required data from the monitored WebSphere Application Server Chapter 1 Introducing the technical architecture of the Smart Bank showcase 29 Figure 1 10 illustrates the components and how they integrate with IBM Tivoli Monitoring V6 IBM Tivoli Composite Application Manager for WebSphere comprises three major components gt IBM Tivoli Composite Application Manager WebSphere Application Server managing server The managing server is the central point of IBM Tivoli Composite Application Manager WebSphere Application Server infrastructure where deep dive analysis for the monitored application can be carried out This component is split up into several subcomponents including a WebSphere Application Server i
77. Time DISC __ Discret_ nia BAT_DISC Managed Performance Actual Perc System BAPLEX BAOT MYVSSYS 8 Teller Channel e a am E Web zBank GDPS HyperSwap PROCESS SOA Figure 4 60 Dynamic link The full sample An advanced link definition can do much more You can build headers footers and the value of the symbol used in queries Thus parts of the attributes values can be concatenated to build a new value that will be assigned to a symbol in a query Advanced link Remarks This section describes some but not all the advanced link features By referring to guides and other relevant documentation you can find more information about all the functions and how to use them You will find that in headers and footers you can mix the string values and symbol values and that when in the dynamic link definition window you can click some of the displayed fields in order to find out the variables that can be used in the definition processes The dynamic link is a powerful tool in which you will discover something new every time Note In the same view you can define as many links as you want If you do so the user will see all the defined links The default link will be presented first but the user can choose another one If the user clicks the link icon directly the default link is used Link anchor In the link anchor window you can perform the following tasks gt Select the d
78. To delete a link select it and click Delete Note Whether you edit define or delete a link save the workspace after finishing with the Link Wizard to make the changes permanent E Physical 3 Smart_Bank Selection Hub Time Sat 03 11 2006 05 24 PM Server Available Smart_Bank 9 212 128 31 SYSADMIN Figure 4 22 Link Wizard access Note If links are already defined the Define New Link window shows the existing definitions 206 Infrastructure Solutions Building a Smart Bank Operating Environment 3 In the next window Figure 4 23 the Link Identity tag provides a name to your new definition We recommend that you use standard and meaningful names blanks are allowed When the user tries to use the link feature these names are displayed If the cursor is positioned on the link symbol a pop up displays the name of this link prefixed with the Link to label For this new link use Branch details When done click Next Smart Bank 9 212 128 31 SYSADMIN Jee File Edit View Help g a Teller Authentification Banking Teller Channel The name and description fields identify the link target ATM 2 m Web Type the link name zBank GDPSiHyperSwap Optional Click inside the Description field and type a description of the link PROCESS S0A Click Next After defining the link you see the name ofthe link in the list of available links when you select Lin
79. UNIX Systems a Linux Systems oa fia BLADES E E Windows Systems aia BLADES 1 z OS Systems E 2 05 Systems ry BLADE12 NT vailable KB ache KB ommit Limit KB Physical RedBook ize Ad Watch kntoma kincontg somsave sor kinlogs mi ae Sa kincontg Topview Close Help putty ems putty sass vsmon re re r r gt oo 10 o 20000 40000 60000 o 400000 800000 1200000 D Privileged Time Kilobytes i Kilobytes Foruns Hais Ees io Hub Time Thu 03 02 2006 05 04 PM ae Server Available Windows NT 10 1 1 131 SYSADMIN En Applet CMWApplet started ei Internet Figure 4 3 Starting the definition of a Logical view Chapter 4 Customizing the Logical views 185 186 2 Anew window opens Figure 4 4 Enter the name of the new Logical View such as Smart_Bank and a meaningful description Click OK The Logical view is now defined O S hbalA zele s B A ae Tivoli Enterprise Portal lil File Edit View Help HHBRSEAD S COCSQSWKHKRARATERT GFE View Physical id max Julies O 8 O x R memory Allocation Ee Edit Navigator View x Source View Physical z Enterprise f UNIX Systems Target View Logical fd Ba Linux Systems 2 a amp a 2 RSI Windows Systems E BLADE11 Enterprise Enterprise BLADE12 UNIX Systems i tt Gy 3 Linux Systems El Windows Systems
80. Up F8 Down Figure 2 16 ICAT Run time Environment screen This displays the screen shown in Figure 2 17 Use option 1 to configure the LU6 2 log mode which generates a batch job you must submit Each RTE can contain only one TEMS To configure Last selected the TEMS for this RTE perform these steps in order Date Time Create LU6 2 logmode 06 03 20 15 12 Specify configuration values 06 03 16 10 26 Specify communication protocols 06 03 20 15 19 Create runtime members 06 03 16 10 30 Configure persistent data store Complete the configuration 06 03 07 16 59 Optional 7 View TEMS list and registration status 06 03 07 8 Generate sample migration JCL Fl Help F3 Back Figure 2 17 ICAT Tivoli Enterprise Monitoring Server configuration screen 70 Infrastructure Solutions Building a Smart Bank Operating Environment 3 Select option 2 to specify the configuration values Define the started task name in this case HUB as shown in Figure 2 18 Set the security parameters for the integrated cryptographic services if necessary Select option 3 to specify the communication protocol To configure a TEMS for your site complete the items on this panel TEMS started task gt TIVSHUBT Hub or Remote gt HUB Security settings Security validation gt N Y N Integrated Cryptographic Service Facility ICSF installed gt N Y N ICSF load library gt CSF SCSFMODO Encryption key gt IBMTivoliMonitoringEncryp
81. V6 after migrating to IBM Tivoli Composite Application Manager for WebSphere This includes the following features gt Workload analysis gt Application trace These functions belong to the deep dive analysis category and are moved to the newly introduced IBM Tivoli Composite Application Manager managing server with its own user interface This user interface addresses the requirements of application developers and deployers more than the operations and line business managers The OMEGAMON WebSphere Application Server agent enables the monitoring of the health and availability of WebSphere Application Server environments as well as the performance of the deployed Java 2 Platform Enterprise Edition J2EE applications inside the server The product is useful to execute the following tasks gt To report current data and monitor performance for multiple platforms operating systems and applications gt To track and report the status of the WebSphere Application Server instances in your enterprise gt To centrally administer WebSphere Application Server in your enterprise including starting and stopping servers and setting instrumentation levels in order to control performance data collection gt To collect and report traffic and resource use within each WebSphere Application Server including the following Pool usage information Java virtual machine JVM state JVM memory Garbage collection Database
82. View Help BHBREtAA S C O0O C SBSNUKRRAERDT 7 amp Oo w Logical Disk Space Ooea80 x FI Memory Allocation Linux Systems Windows Systems BLADE11 BLAI Ge f h BLADES Uha BLADES z OS Systems Primary BLADE12 NT Oavailable KB Dicache KB E Commit Limit KB Bcommitted KB kntema somsave scr kinconfg putty 800000 1200000 Kilobytes i Ovirtual KB O Privileged Time M user Time Hub Time Thu 03 02 2006 01 48 PM GP Server Available Windows NT 10 1 1 131 SYSADMIN Figure 4 1 The default physical tree There are four major areas in the TEP physical display Area A provides access to the administrative functions and the tools used to build the views Area B shows the Navigator toolbar Area C is the physical tree Area D provides the views set up for the selected physical level in the tree Chapter 4 Customizing the Logical views 183 184 2 From the Navigator toolbar B access the Edit Navigator View shown in Figure 4 2 From the same point select one of the Logical views you defined Tivoli Enterprise Portal File Edit View Help mano x a 8000000 6000000 4000000 sapiqo 4 fq BLADEN a BLADE12 fa BLADES Ea BLADES z OS Systems M Free kntema i
83. WAS AIX Siebel E TEMS Remote pa z z z Inx5 blade6 Linux WAS blade11 Windows 2 Fi ND f TEPS F 5 g z 3 3 mo W 3 2 Inx blades 2 ES 8 E F amp 3 3 z 3 v g x lt gt 3 a Figure 5 14 Network view of the operating environment Table 5 9 shows the base queries that we used to create the Logical view from the assigned agents in Figure 5 14 Table 5 9 Network view queries Alert Assigned agent situations queries Assigned managed system Workspace z9 and Blade Situation created with Individual node specified for each nodes alerts Universal Data Provider checking node situation name and node status If offline then critical state event is sent Chapter 5 Scenarios and use cases 277 Alert Assigned agent situations queries Assigned managed system Workspace Universal Data Provider Internet http www ibm com IBM US Managed URL Query Web page Managed URL http safss 9080 web app Siebel Analytics login http Inx1 production local fss branch application http blade2 production local fss branch application Managed Link to Physical view Blade8 amp Nodes Universal Data Provider SNMP Manager Managed Nodes In the left hand side of Figure 5 14 the IBM System z9 109 environment is displayed with the virtual IP address node denoting the sysplex distributor the two z OS LPARs and the Linux guest machines on z VM The names below the alerts indicate the domain na
84. a part of the existing Physical views or Logical views into your new Logical view By doing this you inherit the attached managed system from the existing setup as also the queries views and situations In the Smart Bank showcase Logical view at the ATM Banking Customer Information Control System level CICS level we copied the CICS regions directly from the physical tree With this we inherited the current assignment of the CICS regions see the example for region CICSRA 10 in Figure 4 9 Note A navigator tree works in an hierarchical manner If a managed system is assigned to a specific level of the tree all the other levels that are included up to the root inherit from this managed system assignment Ej Navigator View Properties Navigator Item Identity Name BA01 CICSRA10 Description A v Assigned Available Managed Systems A R s gt amp Available Managed System Lists n gt v is gt Edit Managed System Lists KFVVITM3371 Enter a name for the Navigator item Figure 4 9 Inherited managed system 192 Infrastructure Solutions Building a Smart Bank Operating Environment 4 2 3 Adding views with explicit managed system After adding a view proceed as usual To assign a query select Query Results Source Select the box against Let user assign explicitly Select one or more Available Managed Systems from the list as shown in Figure 4 10 Cont
85. activity are dedicated to a specific SMS group In this case the application context makes sense but the Smart Bank showcase does not 3 2 Physical views from IBM Tivoli Composite Application Manager As described in IBM Tivoli Composite Application Manager on page 29 the Tivoli Composite Application Manager family is divided into the following multiple products gt IBM Tivoli Composite Application Manager for Service Oriented Architecture This is described in 3 2 1 IBM Tivoli Composite Application Manager for Service Oriented Architecture on page 132 gt IBM OMEGAMON for WebSphere Application Server on Distributed Systems and IBM OMEGAMON for WebSphere Application Server on z OS This is described in 3 2 2 IBM OMEGAMON for WebSphere Application Server on page 139 Chapter 3 Using Physical views 131 gt IBM OMEGAMON for WebSphere MQ This is described in 3 2 3 IBM OMEGAMON for WebSphere MQ on page 149 Note In this project OMEGAMON for WebSphere is used instead of IBM Tivoli Composite Application Manager for WebSphere although IBM Tivoli Composite Application Manager for WebSphere is the designated successor of OMEGAMON for WebSphere This is because the Tivoli Enterprise Monitoring Agent for IBM Tivoli Composite Application Manager WebSphere Application Server was not available on z OS at the time of writing this book For further information contact your nearest IBM sales representative For
86. all the distribution packages for the Linux on IBM System z systems Note If there are enough Linux on IBM System z images available place the Tivoli Enterprise Portal Server and the Tivoli Enterprise Management Server on different systems Also a secondary Linux on IBM System z based Tivoli Enterprise Management Server Remote would be helpful to support the two different paths to the Hub Tivoli Enterprise Management Server In our case we add Tivoli Enterprise Management Server to Linux on IBM System z in order to be able to use the HiperSockets for IP communication which are available in System z The Tivoli Enterprise Management Server running on this system can now connect to the infrastructure using only IP communication through the HiperSockets This dramatically increases the performance of the components Chapter 1 Introducing the technical architecture of the Smart Bank showcase 39 The Moveable Hub The Moveable Hub implementation is documented in BM Tivoli OMEGAMON XE V3 1 0 Deep Dive on z OS SG24 7155 In the Smart Bank project similar concepts are used Only the paradigm that all z OS internal communication is performed only through SNA is added Figure 1 15 describes the solution Moveable Hub with VIPA Figure 1 15 The Moveable Hub As described earlier the Tivoli Enterprise Management Server Hub is the core component of IBM Tivoli Monitoring V6 connecting the Tivoli Enterprise Portal Server wit
87. and ATTR files are not sent to the Tivoli Enterprise Monitoring Server Hub and Object Description Identifier ODI files are not sent to the Tivoli Enterprise Portal Server Therefore the Tivoli Enterprise Portal workspaces are unable to show the data In order to work around this problem connect the Universal Agent to the Tivoli Enterprise Monitoring Server Hub where the MDL file is being imported After the Model File Element MDL file is imported the Tivoli Enterprise Portal workspaces show data Thus the Universal Agent can move to any remote Tivoli Enterprise Monitoring Server The reason is that the CAT and ATTR files are created for Tivoli Enterprise Monitoring Server and an ODI file is created on the TEP by the Tivoli Enterprise Monitoring Server Hub which is the only one with the ability to do so Simple network monitoring with the Universal Agent A simple solution must be implemented to monitor the production network in order to periodically check the availability of the Smart Bank servers The Simple Network Management Protocol SNMP data provider available in the Universal Agent is a full function of the SNMP manager which is capable of discovering the network Network monitoring must address the following requirements gt Only the production network must be discovered gt A workspace must display only the network reachability of the participating servers to the Smart Bank environment 116 Infrastructure Solutions B
88. and BA02 If job name is Situation Jobname TIVSHUBT running on not found informational state alert is triggered BAO1 or BAO2 blue 276 Infrastructure Solutions Building a Smart Bank Operating Environment Alert Assigned agent and situations Assigned managed system z OS Tivoli Enterprise MVS System MVS Address Space z OS LPARs BA01 and BA02 If job name is Monitoring Server Situation Jooname TIVSREMT running on not found critical state alert is triggered red Remote BAO1 amp BAO2 To return to the Operations view the Back icon on the toolbar at the top is selected 5 2 3 Monitoring the network From the Operations view the network with the domain names displayed and the actual IP addresses hidden can be seen Figure 5 14 shows this view File Edit View Help gt FORRBRGAF SOOW SSHURBRERALBRFOTBE ei Smart Bank showcase Network View all Remote HTTP response time BoE a hx Hoole S System 29 109 a Remote HTTP response time e CISCO 6509 Switch A Fast Ethernet BladeCenter 8627 E Current Response Time Gigabit Ethernet M maximum Response Time H Average Response Time s Ei MANAGED NODES Le z OS LPAR1 Linux WAS Linux HTTP ba0t wea A blade4 3 ZiOS LPAR2 G blade2 Linux WAS 3 sooo dl 8 ba02 ade amp gt a AIX TEMS rae a Remote inux Ma Linux HTTP 7 ND 9 blade7 O Inx4 na blade3 Linux
89. and Printer Sharing for Microsoft Networks Properties 21x Server Optimization Optimization Minimize memory used C Balance Maximize data throughput for file sharing I Make browser broadcasts to LAN manager 2 x clients Cancel Figure 2 35 Windows network server optimization Tuning the AIX operating system Verify the size of the data area by running the ulimit d command where the d option specifies the size of the data area in kilobytes If the setting returned is less than 256 MB increase the maxfiles limit to at least 256 MB 2 2 8 Database considerations 94 The database implemented for the Tivoli Enterprise Portal Server is IBM DB2 Enterprise Edition 8 1 11 for Windows This database is installed locally on the server where the Tivoli Enterprise Portal Server is installed In our case the default installation process proposed by the DB2 Installer is used without any specific customization A basic tuning of the database is carried out to contribute to the overall performance of the Tivoli Enterprise Portal Server This tuning is based on the recommendations available in the DB2 Administration Guide In particular we tuned the buffer pool The configuration of the buffer pool is the single most important tuning area because the delay caused by slow input output I O can be reduced A buffer pool is the amount of main memory allocated to the cache table and the index data pages when they
90. and application performance information across the entire enterprise and across platforms As described in the introduction to IBM Tivoli Monitoring V6 product in IBM Tivoli Monitoring V6 on page 24 the portal acts as the single point of control for all the activities around Tivoli monitoring IBM Tivoli Monitoring V6 enables the following tasks gt Checking the health of the monitoring infrastructure gt Getting all the monitoring information from a single user interface gt Creating and distributing the monitoring rules that is situations to define specific thresholds that must lead to events gt Viewing events across the entire monitoring environment including the Tivoli Enterprise Console gt Implementing predefined activities that are to be executed manually or automatically in order to manage critical issues in the IT environment gt Interoperating with system automation tools in order to control more complex automation tasks By installing a specific agent on a system and connecting it to the IBM Tivoli Monitoring V6 infrastructure an entry in the physical tree is created Figure 3 1 shows the physical tree for the Smart Bank showcase For each system operating system group platform an agent is installed and an item entry is created Below this level the different physical or logical system names on which the agents are running on are visible For each agent type a subtree is created This subtree contains a
91. applications without looking at outside batch reports or information from other monitors or sources The addition of more than 40 new tables and related attributes provides more detailed information to further reduce the time you spend pin pointing problems affecting performance This monitor addresses the requirements to support system programmers and the operations staff who are in charge of running the CICS system as well as the requirements of the application department to get insight into the performance of the application 130 Infrastructure Solutions Building a Smart Bank Operating Environment 3 1 6 IBM OMEGAMON for Storage on z OS V3 1 0 0 i a ps v O s File Edt View Favorites T Address http blades 1920 enp kdhylbfen bal EJ Go Ay 28 Tivoli Enterprise Portal File Edit View Help HABReAM SOOM SQOUBBAEAERF OTB View Physical ag Oa Fil Sms Storage Groups Performance Hit Rate E o FI sms Storage Groups Performance Resonse T O0 AO x e 5 amp Storage Subsystem Bi Application Summary Channel Path Cache CU Performance Cache CU Status E B E E E Logical Control Unit E Tape Group Virtual Tape Subsystems EH SMS Storage Groups Perform S SMS Storage Groups Space E User DASD Groups Performar E User DASD Groups Space EH HSM Status E Dataset Group Summary EH SMS Configuration a E wahEnhara fnnlicatinn
92. banking database warehouse The process extracts the relevant information from the core system response and writes it as a message to a queue using JMS An MDB is triggered by the presence of a message in the queue and it performs the insert through JDBC to the banking database warehouse DB2 on z OS gt Web Service call update of banking database warehouse for business performance The process extracts the relevant information from the core system response and enriches this data with more information retrieved by a Structured Query Language SQL call to the financial services data model FSDM database DB2 on z OS This information is then written as a message to a different queue using JMS An MDB that is triggered by the message updates our BDW This is a different business reason from our other analytical database update and affects different tables gt Reply to the process or service requestor after the entire process is completed successfully This process can be bound in a number of different ways as already discussed in Table 5 1 For this book we used the simple RMI IIOP call of the process EJB Our Logical view provides the following operational information about this process gt With the JDBC connections information calls to the operational database FSDM and our analytical database for the BDW update and for the business performance dashboard update are seen gt With the J2EE Connector J2C view the CICSSECI
93. connection pool which refers to the CICS Transaction Gateway and our service to invoke our core systems functionality are seen As we write to the queues for asynchronous update of our BDW database the JMS activity is also seen gt Finally in the third view the EJB activity in WebSphere on z OS which represents the method invocations of our process is seen 5 1 5 Summary After the Logical views are constructed our service oriented architecture and our integration mechanisms are seen The use of open standards is the key to allowing such an integration The use of TEP IBM Tivoli Monitoring V6 1 and IBM Tivoli Composite Application Manager for SOA help in monitoring and managing the service oriented environment The choice of WebSphere on z OS as the platform for our Integration Hub and Process Choreographer was taken based on a number of factors some of which are listed here gt Our core systems functionality was already on IBM System z in CICS In our case this meant that we could benefit from the efficiencies and richer integration functionality of being on the same platform gt The underlying quality of service or the IBM System z9 platform Many see SOA as the strategic architectural way forward Many are also of the opinion that in order to truly benefit from this an Enterprise view and scope is required Consequently the integration and provision of these services becomes a mission critical imperative that the IBM Syste
94. create or delete a situation perform the following tasks 1 At the chosen level right click and select the Situations option If this option does not appear it means that no managed system is attached to that level Use the Properties option to do so The Situations for window opens Figure 4 11 If some situations are already associated with this object they are displayed Click the Set Situation Filtering icon located in zone A Select the Eligible for Association box to display all the situations that can be associated Click OK The TEP sends back all the situations assigned to that level and relate to the managed system File Edit View Help ee gt G RBRPF ADS COC SQW RBRBETARFTOtFeE ee View Smart_Ba i x ju e P Smart_Bank Teller i ATM Channel a A A Aushertificetion a af Situation Editor Assistance 8 Banking j a a ccs apa a j OS AA E Web IG Services Management Agent zBank GDPS HyperSwap MessageArrivalClearing s p Mg PROCESS SOA MessageArrivalCritical Situation editor ije S E bal Situations notify you when an event occurs on a managed system Your IBM Tivoli Monitoring ebsphere_Web_Appicationt Product provides a set of predefined situations for your immediate use You can
95. execute the creation of the run time environment Important We recommend that you make a note of the following points gt For IBM Tivoli Composite Application Manager V6 only the IBM Tivoli Composite Application manager for SOA can be configured by ICAT gt Other IBM Tivoli Composite Application Manager components such as Response Time Tracking client Information Control System CICS transaction WebSphere and Common Services cannot be configured through ICAT Refer to the corresponding installation publications for details For IBM Tivoli Composite Application Manager for Response Time Tracking for z OS IBM Tivoli Composite Application Manager for Transaction Tracking Installation and Configuration Guide GC32 9482 For IBM Tivoli Composite Application Manager for WebSphere z OS IBM Tivoli Composite Application Manager for WebSphere Installation and Customization Guide GC32 9506 For IBM Tivoli Composite Application Manager for CICS transactions IBM Tivoli Composite Application Manager for CICS Transactions Product Guide SC32 9510 For IBM Tivoli Composite Application Manager Common Services IBM Tivoli Composite Application Manager for WebSphere Operator s Guide SC32 9508 ICAT performs the following tasks gt Defines and builds a run time environment that is used to run the product and plug the agent gt Configures the system parameters that are used for the product components gt Completes
96. for TIVOLI Smart Bank LPAR BA02 HUB SHARING BASE RTE SHARE for moveable HUB Smart Bank Enter Next Fl Help F3 Back F7 Up F8 Down COMMAND gt F1 HELP F2 SPLIT F3 END F4 RETURN F5 RFIND F6 RCHANGE F7 UP F8 DOWN F9 SWAP F10 LEFT F11 RIGHT F12 RETRIEVE Figure 2 11 ICAT Run time Environment screen for the Smart Bank environment The shared run time environments called BAO1 and BAO2 and the HUB run time environment type are all shared with our base run time environment type called BASE 66 Infrastructure Solutions Building a Smart Bank Operating Environment Working with z OS system variables When defining the run time environment it is possible to use the z OS system variables as shown in Figure 2 12 By utilizing the system variables the components inherit the system values from the z OS system that they are started on UPDATE RUNTIME ENVIRONMENT 2 of 2 Use z OS system variables Y Y N RTE name specification amp SYSNAME RTE base alias specification gt Applid prefix specification gt K amp SYSCLONE Use VTAM model applids gt N Y N TEMS in this RTE gt Y Y N If Y TEMS name gt BA01 TEMS Case sensitive VTAM communications values Applid prefix Network ID gt PSSCBA Logmode table gt KDSMTAB1 LU6 2 logmode gt CANCTDCS TCP IP communications values Required if TCP IP is used in this RTE Hostname gt 10 1 1 20 Address gt 10 1 1 20 Started task gt TCPIP Recommended def
97. four levels This enables users to find their way much more easily Define the views on a workspace that deals with different managed systems on y when their purpose is to combine information in order to fully explain the state of what is monitored at a particular level of the tree Use other product functions to simplify the usage for example you may have many regions that you want to monitor using a Logical view To do so you may develop the same leaf in many places of the Logical view However instead of doing this define only one workspace and use it as a target of dynamic links For more details refer to 4 4 Defining the links on page 201 Build graphics using background maps or pictures A picture can be a simple colored square that is built using a presentation tool and saved as a TEP supported file Note In order to use a newly defined Logical view TEP users who are already connected must log in again 4 2 Assigning managed systems to a Logical view The purpose of a Logical view is to reorganize the data available through the Tivoli Enterprise Monitoring Agents Following are the three ways of setting up managed systems to a level of a Logical view in order to be able to define the views at this level gt Assigning one or more managed systems to a specific level and then building views linked to these managed systems During the Logical view definition process directly attach to the level of the physical tree o
98. internal setup The Define New Link window is divided into the following parts as shown in Figure 4 41 gt The target workspace content A describes the internal content of the target workspace gt The allowed terms B displays values coming from the source workspace and the functions and operators you can apply on these values gt The Expression part C shows the contents of the values or the results of an expression Each of these windows is used during the dynamic link definition f 2 KJRITMO01I Link Wizard Define New Link WLM Details Properties Expression Symbols linklsEnabled V contextlsAvailable lt a S Target Workspace Clear_ _Test_ ea Query WLM LINK Service Class Allowable Terms 3 Symbols Y NODE IE Values A v BERCLASS Link 5 E Servi E Selected Row V Footer S Attributes V Header V Actual Host v Average Response Time V Average Storage v CSS Priority A Y Class Flag V Duration Y Goal Importance V Goal Percentile V Goal Type v Goal Value B V 1 0 Priority V VO Rate V Managed System V Percent CPU V Percent IFA V Percent IFA on CP V Performance Index V Period V Resource Group New u Service Class b Figure 4 41 Parts of the dynamic link definition window Chapter 4 Customizing the Logical views 223 Advanced link The target workspace content The target workspace displa
99. io Hub Time Thu 03 02 2006 07 19 PM re Server Available Windows NT 10 1 1 131 SYSADMIN Applet cmwApplet started fea Internet Figure 4 5 Creating a child in the Logical view Chapter 4 Customizing the Logical views 187 The Logical view is created as shown in Figure 4 6 O 98 AaAG P zele S B Tivoli Enterprise Po E Edit Navigator iew xi Target View Smart_Bank Source View Physical x eH ia e e Smart_Bank Enterprise EA Teller HE UNIX Systems Fie Edt View Help a meteg 3 View Physical ORA Enterprise Authentification m Linux Systems a UNIX Systems Sr Banking ETS Windows Systems fa Linux Systems cics z OS Systems bj fay Windows Systems MQSeries TCP WebSphere z0S E BLADE11 BLADE12 EES EES tifa BLADES mba BLADES gf Teller Channel 7 z OS Systems m at ATM Channel Authentification Banking KFwiTMo2si 88 t C cics a Web ES Physi R Porsa amp reo a Authentification EH Banking fT Top Process CPU Time Pm oc EEE Web Channel L LA Financial Dashboard A IzBank GDPS HyperSwap ES5800 z F20 LEF PROCESS S0A 800000 1200000 CB Hub Time Thu 03 02 2006 07 20 PM Server Available Windows NT 10 1 1 131 SYSADMIN l Applet CMwApplet started ail a Internet Figure 4 6 The completed Logical view As required by the Smar
100. is installed on z OS gt Service management gt Service management environment Details about how this workload is injected is provided at this point of the demonstration for a better understanding of the Logical views described here During a demonstration these explanations form a part of the presentation content 260 Infrastructure Solutions Building a Smart Bank Operating Environment Multichannel workload evolution The workload shown in Figure 5 7 on page 266 is our multichannel workload being injected as individual Web services using the SOAP Hypertext Transfer HTTP protocol This represents the simulation of our ATM and Internet channels by injecting straight into the WebSphere Application Server on z OS Table 5 1 shows the way our core system evolved Note Each step referenced in Table 5 1 is associated with one or more enterprise archive files EAR files deployed to the WebSphere Application Server for the different integration styles to coexist Table 5 1 a ecu Multichannel workload Web service multichannel workload Client Struts based Java 2 Platform Enterprise Edition J2EE architecture where we injected using HTTP and tested using a Struts client through JavaServer Pages Each operation calls an action bean that is specific to the type of application programming interface API on the core system The action bean corresponds one to one with a stateless session bean Integration The session bea
101. is useful Tivoli Enterprise Portal File Edit View Help BHRBROAM SOOC SRQHBZARHANRFOTRE view Physical D TE e lt dull Garbage Collection Rate manx Fi Heap Usage GS J2EE Server Es AACELL BBOCOOL AASRI y 400000 Gs BACELLA BAOCOO1 BASF 5 Application Server Ir 2 200000 All Workloads z F Suspected Memory L Fy a 289 Heap Usage Eg ASID Pool Utilization lt 4 In flight workloads Longest Running i Cl kbytes in Use Kbytes Free HTTP Sessions Datasources Lock Analysis CTG Summary JMS Summary Web Applications iv Real Time Percent Kbytes Real Free Time Objects Total Kbytes Kbytes Kbytes in Moved Freed inUse Use Delta Times Run Sample Interval Date and Time Time SIO 0313 06 19 17 27 60 289 2 1 973 1149 0 487373 140970 140582 246019 273 0 4 Garbage Collection Rate Objects Freed oO Hub Time Mo 03 1 3 2006 07 18 PM je Server Available Garbage Collector Activity 9 212 128 31 WOLF1 i Figure 3 18 The Garbage Collector Activity workspace Chapter 3 Using Physical views 143 144 A useful action based on this data is monitoring the number of HTTP sessions Depending on the underlying system this number may differ but can be set by the system programmer s experience o 0 HAG Ax e es Fle Edt View Favorites T Addre Tivoli Enterprise Portal 8 Kal htt
102. javaw somsave ser 2 kdsmain kinconfg svchost putty kntema putty 0 0 Kilobytes O Privileged Time yt M User Time OPrivate KB Hub Time Thu 03 02 2006 02 59 PM aal Top Process CPU Time manx aall Top Process Private Size maong x all Top Process Virtual Size Server Available Windows NT 10 1 1 131 SYSAL Primary BLADE D Available KE M cache KB D Commit Lim M Committed H 400000 Kiloby Figure 4 2 Accessing the Edit Navigator Tree function Infrastructure Solutions Building a Smart Bank Operating Environment 3 Click the icon named Edit Navigator View in zone A The TEP opens a new window with two frames Building a new Logical view As required by the Smart Bank team a Logical view that displays the status of all the channels used by the Smart Bank clients while dealing with the bank is created 1 Create a new Navigator View Click the Create New Navigator View icon located in zone A as shown in Figure 4 3 LFelG SB ay 2 Qo Hag Tivoli Enterprise Portal Fie Edit View Help HHBRSEAD SS COC SSHWUKRBRAERT BFE View Physical bd Dax IEEE O 8 0 x R memory Allocation manx gl Enterprise Target View Logical Source View Physical z fa UNIX Systems A By Linux Systems gZ g B fy Windows Systems ee BLADE11 Enterpri Create New Navigator View Enterprise a BLADE12 i
103. level A better approach is to hide the Navigator view and create a graphic navigator approach that is in each workspace you create a graphic view always at the same place in the workspace Inside this workspace insert your own icons that represent the different levels the users must go to Then define a link to give access to these levels Chapter 4 Customizing the Logical views 253 Figure 4 73 shows a graphic navigator approach All Region Transaction Overview FLEBE FLEBE m Fichier Editer Afficher Aide e EE T TEE T E ETE State By regions O80 x Navigin O BO x BBSBEQAae E hk x Total transactions per region midwest 46972 AnyBank 68355 77509 Onorth 26765 Qrvest rwes ast n a 3 east C Midwest soun norn SJ East 8 Total Transations per Regions last half hour Oao x Total Transations per Regions last half hour 80000 T 700004 A BEA al le el 60000 i 4 50000 t HEAR 40000 t f lle a ETET e l H AN A bs 2 _ sal ha se Fe Ps foe fa A Vat 20000 SSE SER SERA E O ARAR RN Cee acisi fa o Sof i a gt oe Kad 2 nd 2 Ca 2 8 3 8 8 8 2 8 8 amp S 3S 8 8B Ss FF
104. number 5698 A46 provides a comprehensive monitor for z OS I O subsystem performance and storage availability It also includes the IBM DS6000 and IBM DS8000 device support IBM Tivoli OMEGAMON XE for Mainframe Networks V3 1 0 Product number 5698 A40 provides the ability to monitor and manage the health of the networks It is used for TCP IP Virtual Telecommunications Access Method VTAM File Transfer Protocol FTP TN3270 sessions and OSA IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z OS Product number 5655 P07 provides a tool to monitor analyze optimize and tune the performance of the IBM Universal DataBase UDB and IBM DB2 on z OS It includes performance data and analysis tools for a performance warehouse IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1 1 0 Product number 5698 A587 comprises several components Tivoli OMEGAMON XE for WebSphere Integration Brokers to monitor verify analyze and tune message broker topologies Tivoli OMEGAMON XE for WebSphere MQ Monitoring to monitor collect and analyze the WebSphere MQ specific data on the queue manager Tivoli OMEGAMON XE for WebSphere MQ Configuration to simplify the WebSphere MQ administration IBM Tivoli OMEGAMON XE for UNIX System Services USS V2 2 1 Product number 5608 C15 is a required component to monitor the USS in OS 390 or z OS Chapter 2 IT environment of the Smart Bank showcase 57 58 gt The IBM Tivoli Compos
105. objects only five will be downloaded by the HTTP provider to estimate the response time Generally content such as pictures of a Web site is updated regularly Consequently a part of the objects may change Thereby the calculation of the cache percentage is only an assessment Reflecting this value in the configuration file KUMPURLS using the ObjCache parameter Chapter 3 Using Physical views 171 Figure 3 39 shows the URLs response time for the Web site www ibm com with the parameter ObjCache 100 no object downloaded as in a situation when all of them are already in a cache The response time is around 1 second gt MANAGED_URL blades SYSADMIN BEE File Edit View Help eG i Be wre COV BSWKAARHERDT 2 eA View Physical nea EEE Cea AR OA ee eg mph blades a Int Ga Inxt Ea Inx ea Inx5 Lay Inx e Windows Systems Ga BLADE10 fa BLADE11 mla BLADE12 B BLADES a Universal Agent cH http Ammm ibm com http safss 9080Aweb app E Current Response Time um Response Time http fInxt production local fss 10 14 AM SNMP MANAGEROO 10 1 1 A31HTTPdp UAGENTOO 10 1 1 131SNMPdp UAGENTOO Production Net SNMP MANAGEROO SmartBank SNMP MANAGEROO http blade2 production local tss goaox Status hE Page Title Page ES Current Response ie Maximum Response Time Average Response Time Page Objects
106. on this system the operating system agent connect only to the local Remote Tivoli Enterprise Management Server If the machine is lost which is one of the assumptions refer to 1 4 2 General architectural considerations on page 32 a secondary connection will not help gt OnAIX Remote Tivoli Enterprise Management Server The AIX based Tivoli Enterprise Management Server Remote functions as the primary Tivoli Enterprise Management Server for all AlX based and Linux based agents It also hosts all the distribution packages for the AIX and Linux systems IBM Tivoli Monitoring agents The local agents on this system the operating system agent connect only to the local Remote Tivoli Enterprise Management Server If the machine is lost which is one of the assumptions refer to 1 4 2 General architectural considerations on page 32 a secondary connection will not help gt Onz OS Moveable Hub Tivoli Enterprise Management Server This feature is introduced in 1 4 4 IBM System z environment scenario on page 37 The idea is described in detail in The Moveable Hub on page 40 On z OS each LPAR hosts its own Remote Tivoli Enterprise Management Server The communication with the Tivoli Enterprise Management Server Hub uses only SNA based communication The Tivoli Enterprise Management Server Hub is the only IBM Tivoli Monitoring V6 component on z OS that supports TCP IP communication On z OS eac
107. our ATM and Internet channels and to WebSphere Application Server on Linux z VM and IBM BladeCenter for our branches The key architectural message here is the exact reuse of the same core system APIs for all our channels and the ability to monitor and manage the service level agreements and workload management across these channels at an enterprise level Core system transformation and service oriented architecture Our architecture is then developed using some of the key standards and techniques recommended by IBM for establishing an SOA Fundamentally we automatically create services using tools that leverage the core system functionality previously exposed through proprietary APIs and establish a process integration platform through the use of WebSphere Business Integration Server Foundation WBISF This uses the Web Services Definition Infrastructure Solutions Building a Smart Bank Operating Environment Language WSDL definitions of our services along with Business Process Execution Language BPEL in order to link different business functions together thereby providing a mechanism to transform the use of the core system Figure 1 5 illustrates the Smart Bank showcase architecture with emphasis on the channels that are discussed Internet Customers Intranet Extranet Customers with card Intranet Business Unit Intranet Internet Business U
108. questions gt What can be expected from this agent Each product is represented by a specific agent called Tivoli Enterprise Monitoring Agent The reported data is specific to the application On which system must this specific agent type be installed Not all the agents are installed on every system in the infrastructure Agents are installed only to a specific system with a specific requirement Which attributes does this agent support Each agent type groups its gathered information into attribute groups Which key points must be monitored from a system perspective The different points of view within an IT organization may differ from team to team The system group in charge of delivering a stable IT environment faces specific challenges Which additional application must be covered by specific rules defined to this agent Business unit managers who are in charge of a special part of the business are less interested in single system components because their main focus is the execution of their core business through the entire infrastructure They require designated information about the health of their supporting applications 3 1 1 IBM OMEGAMON for z OS V3 10 This agent provides a deep insight into the z OS operating environment From V3 10 the sysplex monitoring functions are an integral part of the z OS agent Besides the installation is simplified A navigation tree with detailed information about performance and conf
109. response taken time by the operation gt The number of messages by operation gt The fault summary by operation This value is shown because there are multiple servers that are injected with the data collector on this single z OS LPAR Chapter 3 Using Physical views 135 136 The Performance Summary workspace This workspace is available for each application server injected with a data collector As shown in Figure 3 12 it displays information about the response time of each called SOA service within the specific server 9 Tivoli Enterprise Portal Fie Edit View Help HaABREAD FSOCOH SSURBSEHRERVOTEOA View Physical ha g z Tar omesse onnage 05 390 Unix USS a EN Services Management Agent w Message Arrival EN Services Management Agent Env fea Message Summary Faults Summary ir f amp Storage Subsystem i ES WebSphere Application Server 05 39 E G BAOL KWWwA ce Gi BAZ gt E Physical cn i ervices Inventory HAG Arlee Oe lfteerece eae sme cer File Edit View Favorites T d helloFSS helloFSS Average Elapsed 10 20 Response Time in Milliseconds Elapsed Time Service Type Service Name OperationName ocaren Round tin Time Message ngunt Max Elapsed Time Min Elapsed Time lt i RR Requester BalancelnquiniS getBalance 1 0 1 1 a Provider Balancelnguiny NS getBalance 1 0 1 1 Re
110. run time environment libraries after SMP E maintenance or product configuration 3 Note In a sharing run time environment type configuration the master run time environment and all the other run time environments sharing the master run time environment must be loaded Utilities display a selection menu to perform various useful processes for maintaining the run time environment This step is optional However one of this utilities is mandatory if you use the system variable for the hub You can build the run time environment after configuring the product Infrastructure Solutions Building a Smart Bank Operating Environment To configure a product select option 2 Select product to configure in the screen shown in Figure 2 8 The Product Selection Menu screen Figure 2 9 is displayed This screen displays all the products that are installed and available from the installation in the system In our example Tivoli Monitoring Services on z OS V6 1 0 is selected first Depending on your environment you may have a different list from which you can select a different product accordingly Actions S Select product IBM Tivoli Composite Application Manager for SOA V6 0 0 IBM Tivoli Monitoring Services on z OS V6 1 0 IBM Tivoli OMEGAMON DE on z OS V3 1 0 IBM Tivoli OMEGAMON XE for CICS on z OS V3 1 0 IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z OS V3 1 0 IBM Tivoli OMEGAMON XE for Mainframe Networks V3 1 0 IBM Tivoli OMEGAMO
111. the configuration by setting up the required system definitions Creating the started task Virtual Telecommunications Access Method VTAM definitions Authorizing data sets and so on These processes must be performed individually for each of the monitoring agent product that is to be installed A full and complete description of the IBM ICAT is detailed in BM Tivoli OMEGAMON XE V3 1 0 Deep Dive on z OS SG24 7155 Chapter 2 IT environment of the Smart Bank showcase 61 Before using the ICAT perform the following tasks 1 After installing the contents of the product tape into your SMP E environment copy the contents of the KCIINST file into your INSTLIB in order to be able to start the configuration tool 2 Start the configuration tool from an Interactive System Productivity Facility Time Sharing Option ISPF TSO session by invoking the newly created library EXEC your qual INSTLIB Note The INSTLIB library must be created and members must be copied from the TKCIINST to the INSTLIB libraries earlier After the ICAT copyright screen the Main Menu Figure 2 7 that allows you to set up the working environment is displayed Option 1 allows you to specify the allocation for the tool work libraries Option 2 allows you to install the products and their maintenance In our environment we installed the SMP E process instead of this option Option 3 Product to configure allows you to customize
112. to another workspace A link is accessible in the place it is defined that is from the selected view included in that workspace When one or more links are defined on a table row or a graphic view icon a link anchor is visible For links defined on other elements right click the link and then select the link name you want to use To define a link you require a source workspace and a target workspace If you are linking from a data element such as a row or a bar the source workspace must have the data being displayed before the link is defined Some workspaces have data only when something exceptional happens Therefore in order to define a link the target workspace must be built earlier After defining the tree structure of a Logical view the administrator must also decide which link definitions are useful the type of each link the information the target views of the links must show and so on 202 Infrastructure Solutions Building a Smart Bank Operating Environment 4 4 2 Defining an absolute link An absolute link allows you to jump from one workspace to another workspace in one click The Smart Bank showcase team defined a Logical view to match its individual requirements This Logical view shows the different channels that are used by the Smart Bank clients when dealing with the bank In the Smart Bank showcase menu that displays the status of these channels all the views are shown If an alert is visible on one of these bra
113. to automatically recover from critical situations ensuring that your business critical applications are up and running Built on a lightweight highly scalable architecture IBM Tivoli Monitoring is quickly deployed and easily managed for quick time to value and low cost of ownership Simple and centralized control enhanced visualization of information ease of use and historical and real time reporting allow you to quickly access the information you require in customizable formats in order to rapidly identify diagnose and resolve situations By linking IT services to processes data skills and tools through its single user workspace IBM Tivoli Monitoring allows you to view consistent data across technology domains and align IT services with business goals to deliver immediate value IBM Tivoli Monitoring when 24 Infrastructure Solutions Building a Smart Bank Operating Environment combined with IBM Tivolis composite application event network and service level management solutions offers complete and integrated availability management ensuring that your IT resources and staff are operating efficiently and effectively in alignment with your business requirements and priorities TEP Client tees lt lt a Ea TEMS Remote TEMS f TEMA TEMA TEMA TEMA TEMA for TEMA Windows Linux UNIX z OS Databases Universal Figure 1 8 IBM Tivoli Monitoring V6 components IBM Tivoli Monitoring V6 comprises the fo
114. top right hand side are a series of navigational alerts and links that help us navigate between our different Logical views during a demonstration File Edit View Help gt FHHBBROGAA SOOW SSMURBSREAERFOFBE Smart Bank showcase Operations view manx BHARTI h X o olig 4 Enterprise view Channel Actos z OS LPARs N Points f Se internet Intranet ee CICSPlex en 9 seve Linux utilisation bi ff a Network Enterprise Operational he Internet Banking View z 4 5 Re 4 RM ai A Business Analysts Systems Management ki s AIX power 4 blades Muti platform Branch S v E Figure 5 11 The Operational view Table 5 7 shows the base queries that we used to create the Logical view from the assigned agents in Figure 5 11 Table 5 7 Operational view queries Alert Assigned agent Assigned managed system WebSphere z OS Systems WebSphere Application WebSphere for z OS V5 cluster with Cluster WBI Server J2EE Server WBI SF on BA01 and BA02 z OS SF Application Server Instance LPARs WebSphere z OS Systems WebSphere Application WebSphere on z OS V6 on BAO1 Cluster Server J2EE Server and BAO2 z OS LPARs Channel Application Server Instance Applications CICSPlex z OS Systems CICS Region Overview AOR and TOR regions on BAO1 and
115. traffic problem The virtual and physical network must support all the heartbeat signals and data requests the Tivoli Enterprise Management Server Hub handles Over the years z VM has proved its capability to support high network traffic and CPU load The third and the fourth option have a common feature that is the IP address to the communication partners such as Tivoli Enterprise Management Server Remote and Tivoli Enterprise Portal Server will not change This simplifies the configuration Although this book does not provide you with a final answer about where to place your central IBM Tivoli Monitoring V6 infrastructure components because this depends on various factors it provides you with the necessary information that will help you make an informed choice Infrastructure Solutions Building a Smart Bank Operating Environment IT environment of the Smart Bank showcase This chapter describes the Smart Bank showcase operating mainframe environment used to implement the IBM Tivoli Monitoring service products including the following The Smart Bank showcase operating environment The hardware The software The workload vvvy This chapter also describes how to configure the IBM Tivoli Monitoring service components with the Installation and Configuration Automation Tool ICAT for the following IBM Tivoli Enterprise Monitoring Server IBM Tivoli Enterprise Monitoring Agent IBM Tivoli Monitoring Services IBM Tivoli OMEGAMON Cla
116. used the TEP option of displaying the blue chain link symbol on the alert in order to differentiate between alerts with links attached and those without links Enterprise Operations Figure 5 1 Smart Bank showcase The opening window Chapter 5 Scenarios and use cases 259 In order to provide a recognizable view of a typical retail bank we chose to use a simplified Logical view of a retail bank on which we superimposed the alerts for our key proof points and channels Figure 5 2 shows the details of the TEP Enterprise View window On the left the channel alerts representing our multichannel environment are visible When the workload is injected at different volumes during the course of the demonstration these alerts provide a high level view of whether our infrastructure is able to maintain the quality of service we have agreed upon with our business channels Smart Bank sh A HOOI RTE hx o FS Chane Access Points inte met intranet Access htegratbn Entemiise hiegraton Internet Barking 4 a Enterprise View Figure 5 2 The Enterprise view B We added another alert over the Integration Hub box through which we linked to our service oriented architecture view 5 1 2 Service oriented architecture view The agents used in the Logical view Figure 5 7 on page 266 come from the IBM Tivoli Composite Application Manager for Service Oriented Architecture product that
117. view these situations and create others in the Situation editor d Show Situations Click To ae View the situation and its definition in the Show Situations that are Situation name editor Associated wali Montord Appkcation Identify a broader range of situations to show 7 Eligible for Association Initially the tree lists only than only if you do i AET N not see the situation and you opened the v Associated with this object 4 fm Situation editor from the Navigator pop up FSet Situation filter criteria menu OK Cancel Help f 7 ea create new Situation Create a new situation gt ij 5 Make a copy of the selected situation with a Create another Situation new name and description S Delete Situation Delete the selected situation TEE Physical rR tlc The Situation editor shows the situations associated with the selected Navigator item or if you sical lt 2 Smart_Bank opened the editor from the toolbar the situations for all IBM Tivoli Monitoring products When you click a name or create a situation the right frame opens with these tabs Notepad Click To f Formula See add to and edit the formula being tested See and assign the systems on which the Distribution situation is running l Hub Tim lt gt te Figure 4 11 Eligible situations for association Infrastructure Solutions Building a Smart Bank Operating Environment 3 You may then create a new situation create another situ
118. z OS is the most important server The monitoring infrastructure is mostly driven by the requirements and is the responsibility of the people who handle the System z environment Due to this the Tivoli Enterprise Management Server Hub is placed on z OS and the Tivoli Enterprise Portal Server is placed on Linux on IBM System z This implies that most of the maintenance must be performed on z OS and the Linux on IBM System z platform Figure 1 14 shows the suggested configuration Remote TEMS Appl Sys Figure 1 14 IBM System z centric configuration Chapter 1 Introducing the technical architecture of the Smart Bank showcase 37 38 The components are gt On Windows Remote Tivoli Enterprise Management Server The Windows based Tivoli Enterprise Management Server Remote acts as the Primary Tivoli Enterprise Management Server for all Windows based agents It also hosts all the distribution packages for the Windows systems IBM Tivoli Monitoring agents The local agents on this system the operating system agent connect only to the local Remote Tivoli Enterprise Management Server If we lose the machine which is one of the assumptions a secondary connection will not help gt OnAIxX Remote Tivoli Enterprise Management Server The AlX based Tivoli Enterprise Management Server Remote serves as the Primary Tivoli Enterprise Management Server for all AlX based and Linux based agents It also ho
119. 0 By BA0LKWWA ot Agent Events 0B Hub Time Fr 03 1 7 2006 02 02 PM I Serer Available Enterprise Status 9 212 128 31 WOLF1 Figure 3 1 The physical tree for the Smart Bank showcase Each entry in the tree is called a navigator item Each navigator item has at least one workspace By default it is named as the navigator item entry itself A workspace may contain several views Figure 3 2 shows an example from the Windows Server navigator subtree Multiple workspaces are available with each of them detailing different values in different views on the process information gathered by the Windows Server agent A single view may contain different methods of presentation but only one can be used at a time Following are the presentation types that are available Circular Gauge Linear Gauge Bar Chart Table Pie Chart Plot Chart Notepad Situation Event Console Universal Message Console Graphic View Take Action Terminal Browser vvvvvvvvvvvviy Chapter 3 Using Physical views 123 We recommend that you consult the user manual about how to use the different options that are available Tivoli Enterprise Portal File Edit View Help HHSBRE AF SOOC SQSWRABRAARDV S sea 3 View Physical ga ona WEA 8 O x E Time Distribution Ee 5j Windows Systems Al a a BLADE10 _Total _Total E BLADE11 a BLADE12 Pe 5 8 Windows os WmiProviderSubSy
120. 0 0 00 BAPLEX BAD1 MVSSYS_ TRX_ATWF 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BA01 MYSSYS_ TRX_BBI 1 AvgResp 0 Low 100 0 0 0 00 amp Physical g Smart_Bank call ian a annn MUE a E a ee AUT S 2 a aioe A Hub Time Mon 03 13 2006 01 19 PM Server Available WLM All Service Class 9 212 128 31 SYSADMIN Figure 4 32 Source workspace for dynamic link definition Chapter 4 Customizing the Logical views 215 Objective of the advanced link definition Because the WLM definitions are numerous three pages are returned A user usually selects only one WLM service class and gets back a display showing only the activity for that WLM service class that is active on the two systems at the same time BAO1 and BAO2 Target workspace expected The content of the target workspace that is expected after the selection is the same as the one called WLM All Service Class The expected target workspace can be called WLM Selected Service Class In fact there is another simple way in which to achieve this objective Simply filter the contents of the view Figure 4 33 However in our case instead of using this repetitive approach a new filter to focus on each service class we use the dynamic link function which performs the filtering function by itself dynamically after a selection H WLM Selected Service Class 9 212 128 31 SYSADMIN X Fie Edt View Help eee E CE e
121. 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 17 06 14 33 24 0 0 No 0 0 80 0 0 No Enabled Enabled Yes No None i 0 10 26 04 03 1 7 06 14 32 24 1 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 17 06 14 31 24 1 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 1 7 06 14 30 24 1 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 IM FING 1 AINA 4 no Kile n n on nn hie Crahiod Crahiod Van Ma Mana 4 n AMORINA 4 gt Queue CICBEP QLOCAL1 QMgr CSQ1 Host BA01 Figure 3 33 Queue CICBEPQLOCAL1 statistics To demonstrate the activity on the MQ queue perform the following tasks a Start the CICS Business Event Publisher started tasks b Using a workload generator create banking transactions on the banking infrastructure As stated earlier for each money transaction carried out which records a change in the DB2 posting table the DB2 change is tracked and a message is written to the queue To see how the MQ queue is filling up the batch FABBEP to process messages in the queue is not started Figure 3 34 shows that the following new metrics have changed e Output Opens is at 19 according to the CICS Business Event Publisher process that is running e Current Depth increases The rate is about 300 messages inserted in the queue every minute When this is compared to the transaction rate as seen from the workload generator it matches our rate of 5 3 transactio
122. 00 00 I IBM Tivoli OMEGAMON XE for Storage on z OS 03 10 00 00 xl a7 InstallShield Back Next gt Cancel Figure 2 41 z OS application support selection Chapter 2 IT environment of the Smart Bank showcase 101 102 e When the operation is completed you must receive the messages displayed in the window as shown in Figure 2 42 Ie Installer A iolxi Please wait while application support is added KQ EAAACATAANANAANNANANNANNAANAANMAANNAARAA AAA s Installation completed successfully Installation details topping the Tivoli Enterprise Portal Server TEPS Performing initial TEPS configuration dding TEPS support for IBM Tivoli OMEGAMON DE on z 05 Version dding TEPS support for IBM Tivoli OMEGAMON XE for CICS on z 0 dding TEPS support for IBM Tivoli OMEGAMON XE for Cryptograph dding TEPS support for IBM Tivoli OMEGAMON XE for DB2 Version dding TEPS support for IBM Tivoli OMEGAMON XE for Mainframe Ne dding TEPS support for IBM Tivoli OMEGAMON XE for 05 390 Unix dding TEPS support for IBM Tivoli OMEGAMON XE for Storage on dding TEPS support for IBM Tivoli OMEGAMON XE for 2 05 Versior Performing final TEPS configuration can take up to 20 minute Starting the Tivoli Enterprise Portal Server TEPS Installation completed successfully e log file for this installation is located at C DOCUME 1 ADMINI 1 LOCALS 1 Temp 1 ITM_AppSupport_I InstallShield Figure 2 42 z OS
123. 000 IST2061 SESSIONS IST6341 NAME STATUS SID SEND RECV VR TP NETID IST635I KOIWWNC ACTIV S CDD3C505D133D2B5 016B 0001 PSSCBA IST635I KOIOENC ACTIV S CDD3C505D133D2B2 0061 0001 PSSCBA IST635I KOIMCNC ACTIV S CDD3C505D133D2AF 0351 0001 PSSCBA IST635I KOIN3NC ACTIV S CDD3C505D133D2AC 0061 0001 PSSCBA IST635I KOIMVNC ACTIV S CDD3C505D133D2A6 00B2 0001 PSSCBA IST635I KOIM2EQ ACTIV S CDD3C505D133D2A2 0022 0001 PSSCBA IST635I TIVHUBLB ACTIV S CDD3C505D133D29E 1CE6 0001 PSSCBA IST635I TIVHUBLB ACTIV SV S CDD3C505D133D29D 0001 0001 PSSCBA IST635I KOIWWNC ACTIV P CDD3C505D133D2B4 0001 O9AF PSSCBA IST635I KOIWWNC ACTIV SV P CDD3C505D133D2B3 0001 0001 PSSCBA IST635I KOIOENC ACTIV P CDD3C505D133D2B1 0001 0152 PSSCBA IST635I KOIOENC ACTIV SV P CDD3C505D133D2B0 0001 0001 PSSCBA IST6351 KOIMCNC ACTIV P CDD3C505D133D2AE 0001 OA6D PSSCBA IST635I KOIMCNC ACTIV SV P CDD3C505D133D2AD 0001 0001 PSSCBA IST6351 KOIN3NC ACTIV P CDD3C505D133D2AB 0001 0045 PSSCBA IST635I KOIN3NC ACTIV SV P CDD3C505D133D2AA 0001 0001 PSSCBA IST6351 KOIMVNC ACTIV P CDD3C505D133D2A5 0001 0081 PSSCBA IST635I KOIMVNC ACTIV SV P CDD3C505D133D2A4 0001 0001 PSSCBA IST6351 KOIM2EQ ACTIV P CDD3C505D133D2A1 0001 0023 PSSCBA IST635I KOIM2EQ ACTIV SV P CDD3C505D133D2A0 0001 0001 PSSCBA IST6351 TIVHUBLB ACTIV P CDD3C505D133D29F 0001 15A5 PSSCBA IST3141 END Figure 2 23 VTAM applid display for the Remote HUB in BAO1 with all the z OS agents started Chapter 2 IT environment of the Smart Bank showcase
124. 000000000 0 0 03 16 06 16 44 CRBQM C10 SVRCONN 10 1 1 127 Running No 0 0 0 00 0 Yes 0000000000000000 0 0 03 16 06 17 00 CRBQM C10 SVRCONN 10 1 1 127 Running No 0 0 0 00 0 Yes 0000000000000000 0 QO 03 16 06 17 01 CRBQM C10 SVRCONN 10 1 1 127 Running No 0 0 0 00 0 Yes 0000000000000000 0 0 03 16 06 16 54 t a nan wman aaa 4497 limni TA a nina Van Tanannnannannnann AAAI AREN sn Pi CSQ1 BA01 MQESA S Hub Time Do 03 16 2006 05 04 PM Server Available Channel Performance 9 212 128 31 WOLF1 Figure 3 25 The Channel Performance workspace The system programmer may have to identify the upcoming threads earlier on in order to have enough time to fix the issues before the applications or the entire system collapses We recommend that you perform the following checks gt Achannel is not up and running when there are messages on the transmission queue Only an empty transmission queue is a good queue Ask yourself why the channel is not starting automatically gt A channel gets into the in doubt status for two or more test intervals This indicates for example that the channel connection is either unstable due to communication protocol problems or WebSphere MQ cannot recover the in doubt state by itself gt Check the channel status These channels cannot start up automatically They must be activated by commands These are only a few suggestions Applications are not aware
125. 1 353 439 3168 Method Minor Name doPost Number of Occurrences Occurrence Time 4 474 287 Interval Time 59 Sample Date and Time 03 16 06 10 57 54 Total Average laximut Time CPUTime 3497 271 077 org apache struts a 1089 Figure 2 47 Tivoli Enterprise Portal WebSphere All Workload workspace Chapter 2 IT environment of the Smart Bank showcase 113 Using the Universal Agent to monitor the IBM HTTP Server The IBM Tivoli Open Process Automation Library provides a package for monitoring the IBM HTTP V6 0 Web Server using the IBM Tivoli Monitoring Universal Agent The IBM Tivoli Open Process Automation Library Web site is available on the Web at http www 18 lotus com wps portal tm The Universal Agent uses the file data provider to extract useful metrics from the access_log file regarding the health of the HTTP Server Thus data about the performance characteristics of the IBM HTTP V6 0 Web Server is available including the following gt The throughput of the Web server gt The number of Web hits per hour per day gt Errors including the client that initiated the request to the Web server The IBM HTTP V6 0 Web Servers are installed on two types of platforms gt SUSE Linux Enterprise Server 9 Intel gt SUSE Linux Enterprise Server 9 for IBM eServer zSeries 64 bit Log format The IBM HTTP Server is based on Apache The file data provider e
126. 1 MVSSYS TRX LX Link Indicator Always Enabled 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX w 500 0 0 00 0 0 C BAPLEX BAO1 MYSSYS TRX v 900 0 0 00 0 0 BAPLEX BA01T MVSSYS TRX amaaa scence web 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX ATF T AVGRESp Too 800 a 0 00 0 0 seams al 2 BAPLEX BAO1 MVSSYS TRX_BBI 1 AvgResp 0 Low 100 32 0 32 0 0 Shysical Smart_Bank ez aii a ag A Spi tn aaa SENSES CER ae he Figure 4 61 The link anchor window 4 5 Style in the Logical view A Logical view is a way of organizing data according to the requirements of the user The style features allow you to personalize the Logical views 4 5 1 Using the standard Tivoli Enterprise Portal The Smart Bank showcase team designed a picture that they used for advertising This is in T IBM ITM CNB classes candle fw resources backgrounds user which is the TEP directory dedicated to the user background png jpg or gif files Chapter 4 Customizing the Logical views 241 When used as a background in the workspace located at the root level of the Smart Bank showcase Logical view it opens as shown in Figure 4 62 Graphic View Deox BEERCIO gx Hoo FS eae Building a Smart Bank operating environment _ Ye E ee zBank GDPS HyperSwap Enterprise Operations x gt h Notepad manx Hub Time Thu 03 16 2006 06 25PM f Server Available Smart_Bank 9 212 128 31 SYSADMIN 25m k
127. 1 MYSSYS BATCHLOV 1 Discret 0 na 0 0 0 E ATM BAPLEX BA01 MVSSYS_ CICS_AOR 1 Velocio 0 Medium 50 0 0 E Web BAPLEX BAO1 MVSSYS CICS_CPS 1 Velocio 0 Medium 50 0 0 E zBank GDPS HyperSwap BAPLEX BAOTMVSSYS CICS_TOR 1 Velocio 0 Medium 50 0 0 E PROCESS SOA BAPLEX BAOUMVSSYS OMVSDFLT 1 Velocio 0 Medium 30 0 0 BAPLEX BA01 MVSSYS PR_OSFLT 1 AvgResp 0 Low 600 0 0 BAPLEX BAO1 MVSSYS PR_IOPA1 1 AvgResp 0 Low 500 0 0 BAPLEX BAO1 MVSSYS PR_IOPD 1 AvgResp 0 Low 500 0 23 BAPLEX BAO1 MVSSYS PR_MDBD 1 AvgResp 0 Low 500 0 0 BAPLEX BAO1 MVSSYS PR_MDBDW 1 AvgResp 0 Low 500 0 0 BAPLEX BAO1 MVSSYS PR_LTRF 1 AvgResp 0 Low 600 0 0 BAPLEX BA01 MYSSYS_ PR_WEB 1 AvgResp 0 Low 500 0 0 BAPLEX BA01 MYSSYS_ SYSOTHER 1 SysGoal 0 nla 0 0 0 BAPLEX BA01 MYSSYS_ SYSSTC 1 SysGoal O nla 0 0 0 BAPLEX BA01 MYSSYS_ SYSTEM 1 SysGoal 0 nla 0 0 0 BAPLEX BA01 MVYSSYS_ TRX_ABI 1 AvgResp 0 Low 600 0 29 BAPLEX BAO1 MYSSYS TRX_ABP 1 AvgResp 0 Low 800 0 0 BAPLEX BA01 MYSSYS_ TRX_ACAL 1 AvgResp 0 Low 800 0 0 BAPLEX BAO1 MYSSYS TRX_ACD 1 AvgResp 0 Low 800 0 0 BAPLEX BA01 MYSSYS_ TRX_ACDO 1 AvgResp 0 Low 800 0 0 BAPLEX BA01 MYSSYS_ TRX_ACDT 1 AvgResp 0 Low 800 0 0 BAPLEX BA01 MYSSYS_ TRX_ACW 1 AvgResp 0 Low 800 0 47 BAPLEX BA01 MYSSYS_ TRX_APIA 1 AvgResp 0 Low 500 0 51 BAPLEX BAO1 MVSSYS TRX_APIC 1 AvgResp 0 Low 900 0 0 BAPLEX BA01 MVSSYS TRX_ATOF 1 AvgResp 0 Low 800 0 o BAPLEX BA01 MVSSYS
128. 18 1 3 2 Systems management requirements 000 cece eee eee 22 1 3 3 Use cases this IBM Redbook focuses On 0 c eee ee 23 1 4 IBM Tivoli Monitoring Architectural design and description 23 1 4 1 Products selected from the Tivoli portfolio 0 2 eee eee 24 1 4 2 General architectural considerations 0 00000 c cee eee 32 1 4 3 Distributed environment scenario asas asana aeaa 35 1 4 4 IBM System z environment scenario 0 000 ee 37 1 4 5 Distributed systems and IBM System z working together 44 1 4 6 Virtualized IBM System x with Moveable Hub implementation 46 4 55 GORCIUSION i meaa aa a i a hence tak ps Reece a a a hyena peti al an San dee dea es 49 Chapter 2 IT environment of the Smart Bank showcase 51 2 1 The IBM System z environment 0 000 cette eee 53 2 1 1 The hardware components 00 eee ete 53 2 1 2 The operating systems and the middleware components 54 2 1 3 IBM Tivolicomponents 0 0 tte 57 2 ASA SUMIMALY os cnied dy Seal aan Seagate ne Boke A E als pee ee EA ohn ee 60 2 1 5 Configuring the Smart Bank showcase 00 0c eee eee eee 60 2 1 6 OMEGAMON XE Tivoli enterprise management Initialization checklist for the server ANG tme agen e sl hee r Eae E EE thae Sas n E ene tence RANNE 81 2 2 The distributed environment 0 0 eee 84 2 2 1 Overvie
129. 308 0 0 5 1 No Enabled Enabled Yes No 03 21 06 16 47 24 0 19 No 6127 0 80 76 5 0 264 0 0 4 4 No Enabled Enabled _ Yes No 03 21 06 16 46 24 0 19 No 5853 0 80 73 1 0 274 0 0 4 6 No Enabled Enabled Yes No 4 Hub Time Tue 03 21 2006 05 02 PM Queue CICBEP QLOCAL1 Server Available QMgr CSQ1_ Host BA01 Recent Queue Statistics 9 212 128 31 SYSADMIN Figure 3 35 Processing activity of the queue with the FABBEP batch started Chapter 3 Using Physical views 167 5 Finally in order to monitor what is happening on the DB2 subsystem navigate to DW01 BA01 DB2 where DW01 is the subsystem ID of the DataWarehouse DB2 and BA0O1 is the logical partition LPAR name where this DB2 is running Figure 3 36 shows the details pertaining to the current DB2 threads on the DW01 subsystem A thread is open for plan CORBEP1 This plan has been allocated by the job FABBEP File Edit View Help gt ERRBRPAA SOOM SQSWURBRERERV OTEeD 8 x A Top Ten in DB2 Time Threads Page 1 of4 E a E View m Top Ten In DB2 CPU Time Threads y System Status Detailed Thread Exception Lock Conflicts Subsystem Management Log Manager Utility Jobs EDM Pool Buffer Pool Management Volume Activity CICS Connections IMS Connections DB2 Connect Server 0 6 12 18 24 30
130. 3V50 Velocia 0 Medium 50 0 0 00 0 0 TCP BAPLEX BA01 MVSSYS___ BATCH 1 Velocio 0 Medium 25 185744 0 29 47 WebSphere amp WLM Details BATCH_HI 1 Velocio O Medium 30 0 0 00 0 0 BATCHHOT 1 Velocio 0 Highest 50 Q 0 00 0 0 8 Teler Channel eS amp WLM Help BATCHLOW Discret 0 nia o0 0 0 00 0 0 ATM KJ F i CICS_AOR 1 Velocio 0 Medium 50 0 0 66 53 Web aa amp LinkWizard FT cics_cps 1 Velocio 0 Medium 50 0 0o50 01 zBank GDPS HyperSwap C amp LinkAnchor Cl Velocio O Medium 50 0 0 54 EZ PROCESS S0A z ce S Velocio 0 Medium 30 46 0 38 0 3 BAPLEX BAGTMVSsYS PR_DEFLT 1 AvgResp 0 Low 600 0 0 00 0 0 BAPLEX BA01 MVSSYS_ PRIE aa i S 500 0 0 00 0 0 BAPLEXBADT MVSSYS PR 2 Link Anchor Properties 500 0 000 00 gt BAPLEX BAO1 MVSSYS PR_ Default Link 500 0 0 00 0 0 2 BAPLEX BAD1 MVS8Y8 PR_I fuo Detaut k 500 0 000 0 0 BAPLEX BA01 MVSSYS JPRS WLM Details 600 0 0 00 0 0 BAPLEX BAD1 MVSSYS PR WLM Help 500 0 0 00 0 0 BAPLEX BAOT MVSSYS SYS Q Q 0 00 0 0 BAPLEX BA01 MVSSYS_ SYS 0 0 0 00 0 4 BAPLEX BA01 MVSSYS SYS 0 0 0 00 1 8 E3 BAPLEX BA01 MVSSYS TRX 600 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX w 800 0 0 00 0 0 BAPLEX BA01 MVSSYS TRX 800 0 0 00 0 0 BAPLEX BAD1 MVSSYS TRX Options 800 0 0 00 0 0 2 BAPLEX BAD1 MVSSYS_ TRX FA Show Link Indicator w 800 0 0 00 0 0 BAPLEX BA01 MVSSYS TRX Z 800 0 0 00 0 0 2 BAPLEX BA0
131. 800 0 o BAPLEX BA01 MYSSYS TRX_ACAL 1 AvgResp 0 800 i i BAPLEXBAD1 MVSSYS TRX_ACD 1 AvgResp 0 Low 800 0 o BAPLEXBAD1 MVSSYS_ TRX_ACDO 1 AvgResp 0 Low 800 0 ol BAPLEXBAD1 MV58YS TRX_ACDT 1 AvgResp 0 Low 800 o ol BAPLEXBAD1 MV58Y5 TRXACW 1 AvgResp 0 Low 800 0 a7 BAPLEX BAO1 MVSSYS TRX_APIA 1 AvgResp 0 Low 600 0 51 BAPLEX BA01 MYSSYS TRX_APIC 1 AvgResp 0 Low 900 0 o BAPLEX BA01 MVYSSYS TRX_ATOF 1 AvgResp 0 Low 800 0 o BAPLEXBADIMVSSYS TRICA 1 AvgResp 0 Low 800 o o BAPLEXBADT MVSSYS 1 AvgResp 0 Low 100 o ol E Physical 3 Smart _Bank Hub Time Mon 03 3 2006 08 00 PM 1 Server Available WLM Selected Service Class 9 212 128 31 SYSADMIN Figure 4 43 The define link window close to the workspace window Chapter 4 Customizing the Logical views 225 226 The purpose of an advanced link is to filter and to modify the content of the target workspace To set up the filter value access to the data displayed by the selected view on the source workspace is required This data is displayed in the bottom of the dynamic link definition window Figure 4 44 on the right hand side All the attributes gathered by the query attached to the view and either displayed or not displayed in this view as shown in area A1 in Figure 4 44 are offered for selection in area A2 in Figure 4 44 Se o gt FABRBRGAF SFSOO C SOUR RHEAER FeEH 3 View Smart_Bank v OEB x
132. Architecture IBM Tivoli Composite Application Manager for SOA comes with a predefined set of workspaces that is a part of the product In this section the workspaces are discussed in the way they appear in the physical navigation tree All the window captures in this section are taken from the Smart Bank showcase development system For a detailed description of the agents workspace consult this product s user manual 132 Infrastructure Solutions Building a Smart Bank Operating Environment The Service Management Agent workspace This workspace shown in Figure 3 9 summarizes the actual monitoring settings for SOA services by the specific agent The settings may be modified by the Take Action method field A This changes the amount of data gathered by the agent through the data collector inside the monitored application server Q x a O pe kA amp 2 Fie Edit view Favorites T z Address http 4 9 212 128 31 1920 ienp kd EJ co Ax aes Tivoli Enterprise Portal File Edit View Help HHBR AM STOOC SQSWRRERERYV E 3 View Physical 6 Data Collector Global Configuration Application Application Data Collector Debug Data Collector Hostname co fas A SEEE Bl Server Environment Server Name Onoff Log Level Tracing On Off Ef MVS Operating System I WebSphere_Application_Server aasr011 On Error Off ba01 amp 8 OMEGACENTER Bridge 8 05 390 Unix USS
133. Assign the parameters account based on the access type if AccessType ssh goto UnixEnv if AccessType rexec goto UnixEnv if AccessType rsh goto UnixEnv if AccessType smb goto WinEnv goto WrongAccessTypeMsg Define the parameters to access the Unix environment UnixEnv set RemoteDir opt 1IBM ITM set Account root goto InstallAgent Define the parameters to access the Windows environment WinEnv set RemoteDir c IBM ITM set Account Administrator goto InstallAgent InstallAgent echo on 106 Infrastructure Solutions Building a Smart Bank Operating Environment tacmd createNode h AccessType Target u Account w Passwd d RemoteDir p PROTOCOL1 IP PIPE PROTOCOL2 IP UDP PORT P_PORT SERVER TEMS BACKUP YES BSERVER BTEMS BPROTOCOL1 IP PIPE BPROTOCOL2 IP UDP PORT S_PORT echo off goto End HelpMsg echo Usage itso_inst_os_ agent lt ssh rexec smb gt lt target_hostname gt lt target_passwd gt lt monitoring server gt lt backup monitoring server gt goto End TargetDownMsg echo Error Target is not reachable goto End WrongAccessTypeMsg echo Error Access type AccessType is unknown goto End End 2 2 11 An alternative solution The other solution has been tested successfully with an environment based on a Tivoli Enterprise Monitoring Server Hub running on Windows 2003 and with z OS Tivoli Enterprise Monitoring Servers Remote connected to the Hub The b
134. Be A ea vii TADOIMAKS 23 i Pk A et eR ANS A AER IR Rik ide i AL ARE de hd dd e Ml et viii Preface oak f c d eet aE nied wo Sete oe naan 4 hike ae R a ix The team that wrote this IBM Redbook 0 0 0 cece ett eee x Become a published author 0 2 0 cee eee xii Comments welcome 0 0 00 cette ete teen eee xii Chapter 1 Introducing the technical architecture of the Smart Bank showcase 1 1 1 Understanding the Smart Bank showcase 00 00 cece eee 2 1 1 1 Overview of IBM infrastructure solutions 000 000 c eee ee eee 2 1 1 2 Objective of the Smart Bank showcase 00 000s 4 1 1 3 The banking sector s current key business drivers 00 aruana 5 1 1 4 The banking sector s future key business drivers 0 0 cee eee eee 7 1 1 5 The way the IBM Financial Services Sector addresses these issues 8 1 1 6 Demonstration proof points A day in the life of abank 10 1 2 Architectural Choices s cesas aaua tees 14 1 2 1 Banking clients current architecture 2 ee 14 1 2 2 Reference architectures and models 0 00 c eee eee 14 1 2 3 Functional requirements 0 0 eee 15 1 2 4 Nonfunctional requirements 00 c ee ee 16 1 2 5 Key architectural decisions os earan eia a E RTE ee 16 1 3 The architectural components s a ssaasa saaa rna ee 17 1 3 1 The current architecture of the Smart Bank showcase a sa sasaa aaua
135. Carver acna D a E ee 0 00 25 00 50 00 75 00 100 00 0O 2 4 6 8 10 12 14 16 Dow Read Hit Percent Bh Low write Hit Percent high Response Time a Physical SMS Storage Groups Space ce Goun Nere 8 Storage Group Storage Group Non Enabled Total VTOC Index E Low Volume High Volume Largest Free Space p Status Type Volumes Volumes Status Free Space Fragmentation Index Free Extent MB MegaBytes BENCHARC Enabled Pool No 1 Enabled 99 3 0 8065 8066 CORZBSG Enabled Pool No 96 Enabled 450 8105 197420 DWHZBSG Enabled Pool No 16 Enabled 35 8 52 7841 108428 PRIVATE NON SMS VOLUMES nia No 227 Enabled 0 0 586 8115 981597 STORAGE NON SMS VOLUMES nla No 1 Enabled 205 630 1975 SYSSG Enabled Pool No 10 Enabled i ES 230 2920 20803 TRIADSG Enabled Pool No 1 Enabled 124 1180 1534 gt C Hub Time Sa 03 18 2006 06 04 PM ak Server Available TIVSREMT BA01 STORAGE blade8 WOLF1 ADMIN MODE Figure 3 8 The physical subtree of IBM OMAGEMON for Storage The z OS Storage Management Subsystem SMS is one of the key components in the host environment With a good SMS the system performs well Otherwise the system fails The OMEGAMON for Storage as shown in Figure 3 8 provides a deep insight into the performance of this subsystem These values are extremely focused on the requirements of the system programmers Only a few applications that have high disk or tape
136. D SOO C SSURBSERERV STFS 3 View Physical hd Oe Jul Number of Faults by Operation D Z apa geraes f MVS Operating System Sa 8 OMEGACENTER Bridge 8 05 390 Unix USS B Ba Services Management Agent ey Message Arrival N Services Management Agent Env Performance Summary Message Summary E amp Storage Subsystem B ey WebSphere Application Server 05 39 G BA0LKWWA amp cashWithdraw getP ostingListCounter getPostingListAtm getAccountList deposit cashWithdraw cashDeposit pay getBalance Number of Faults Fault Details s Message Interception Message Interception Application Service Name Operation Name Time Fault Code Fault String oration Server Name Hostname C5 Hub Time Fr 03 17 2006 06 26 PM J Server Available Faults Summary 9 212 128 31 WOLF1 Figure 3 14 The Fault Summary workspace By default there are two different views gt The Fault Summary by Operation gt The Fault Details This workspace is important for investigating errors and detecting upcoming issues IBM Tivoli Composite Application Manager for SOA Summary This product provides the management function managing the services in a service oriented architecture running on application servers and WebSphere Service Integration Bus In the context of the Smart Bank showcase it enables simple control of message traffic between Web services i
137. ERE RR EK EERE KER EERE RE ER ER EER JOBLIB DD DISP SHR DSN DSN810 SDSNLOAD BIND EXEC PGM IKJEFTO1 DYNAMNBR 20 DBRMLIB DD DISP SHR DSN DSNDWOO DBRMLIB DATA SYSTSPRT DD SYSOUT SYSPRINT DD SYSOUT SYSUDUMP DD SYSOUT 160 Infrastructure Solutions Building a Smart Bank Operating Environment SYSTSIN DD DSN SYSTEM DWO1 BIND PACKAGE CORBEP1 MEMBER CORBEP1 ISO CS OW DB2ADM ACT REP BIND PLAN CORBEP1 ISO CS PKLIST CORBEP1 CORBEP OW DB2ADM ACT REP Example 3 4 shows an example of the batch process Example 3 4 Example of batch process FABBEP1 JOB AX4328 CLASS A MSGCLASS 0 MSGLEVEL 1 1 hil NOTIFY amp SYSUID REGION 4M JOBPARM SYSAFF FABRUN EXEC PGM IKJEFTO1 DYNAMNBR 20 COND 4 LT DBRMLIB DD DSN DSNDWO0 DBRMLIB DATA DISP SHR SYSTSPRT DD SYSOUT SYSPRINT DD SYSOUT SYSUDUMP DD SYSOUT SYSOUT DD SYSOUT REPORT DD SYSOUT SYSTSIN DD DSN SYSTEM DWO1 RUN PROGRAM CORBEP1 PLAN CORBEP1 LIB FABRICE MQ USER LOAD PARMS CSQ1 CSQ1 CICBEP QLOCAL1 1 A 1000 X END 1 3 3 3 Monitoring a running CICS Business Event Publisher using OMEGAMON XE for MQSeries This section provides details about monitoring the running CICS Business Event Publisher process especially the activity on the MQ queue 1 In our environment several machines are monitored using IBM Tivoli Monitoring V6 1 When you log in to the TEP a login window is displayed
138. FABBEP job running 168 Infrastructure Solutions Building a Smart Bank Operating Environment A plan called CBMPLAN which is allocated by the CBMDES1 started task the CICS Business Event Publisher event monitor started task is also found as shown in Figure 3 37 On the thread line click the blue anchor next to the time to get more details about this particular thread File Edit View Help Fl Top Ten In DB2 CPU Time Threads gt HFEURRBASCA SOOM SQSWRBRBERAARFSFBE n In DB2 Time Thr amp 082 EDM Pool 00000000A 5 s CB01 B401 D82 Ek System Status Detailed Thread Exception Lock Conflicts Subsystem Management Log Manager Utility Jobs Buffer Pool Management Yolume Activity a view g E Ea 6401 A 400 600 800 Oin pe2 cru Time Hub Time Tue 03 21 2006 05 45 PM Server Available Thread Activity by Plan 9 212 128 31 SYSADMIN In Elapsed package innad DB2 Updates Commits Authorization Interva Time DBRM Status UE P e 01 12 41 400 CBMPLAN NOT IN DB2 00 13 08 394 00 07 00 2 0 0 0 SYS 06 00 00 27 094 CRBCORO AHUKM1 0 WAIT REUSE 00 00 14 440 00 00 44 121 183177 21882 1248 STCUSER CICSRA11 03 21 06 00 00 12 897 CRBCORO AHUKM1 0 0 WAIT REU
139. For a detailed list visit the following Web site http www 306 ibm com software tivoli sw atoz indexM htm Tivoli Enterprise Portal Server The Tivoli Enterprise Portal Server is the central component for mapping the technical information gathered by the agents and the Tivoli Enterprise Managing Server to match client requirements and enable the presentation of this infrastructure to the user The Tivoli Enterprise Portal Server is the repository for the entire graphical presentation of monitoring data All the working data is stored in a relational database including user specific user rights and views The Tivoli Enterprise Portal Server provides the core presentation Chapter 1 Introducing the technical architecture of the Smart Bank showcase 27 layer allowing the retrieval manipulation analysis and preformatting of data The Tivoli Enterprise Portal Server maintains a persistent connection to the Hub Tivoli Enterprise Managing Server and can be considered a logical gateway between the Hub Tivoli Enterprise Managing Server and the Tivoli Enterprise Portal Client A relational database management system must be installed on the same physical system prior to the Tivoli Enterprise Portal Server installation This database stores all the presentation data and manipulation rules Also user settings if any are stored in this database Following are the platforms that are supported Linux on IBM System x Linux on IBM System z W
140. HARE for TIVOLI Smart Bank LPAR BA02 HUB SHARING BASE RTE SHARE for moveable HUB Smart Bank Enter Next Fl Help F3 Back F7 Up F8 Down COMMAND gt Figure 2 25 ICAT Run time Environment screen Chapter 2 IT environment of the Smart Bank showcase 77 2 A screen Figure 2 26 is displayed Select option 1 to configure the LU6 2 logmode Then submit the generated job Select option 2 to specify the configuration values Each RTE can contain only one TEMS To configure Last selected the TEMS for this RTE perform these steps in order Date Time Create LU6 2 logmode 06 03 13 12 05 Specify configuration values 06 03 15 09 42 Specify communication protocols 06 03 15 09 42 Create runtime members 06 03 08 10 52 Configure persistent data store 06 03 03 10 37 Complete the configuration 06 02 27 14 00 Optional 7 View TEMS list and registration status 06 03 01 15 57 8 Generate sample migration JCL OPTION gt F1 HELP F2 SPLIT F3 END F4 RETURN F5 RFIND F6 RCHANGE F7 UP F8 DOWN F9 SWAP F10 LEFT F11 RIGHT F12 RETRIEVE Figure 2 26 ICAT Tivoli Enterprise MonitoringServer configuration screen 3 In the Specify Configuration Values screen Figure 2 27 define the Hub as REMOTE and set the security and integrated cryptographic service facility to No SPECIFY CONFIGURATION VALUES To configure a TEMS for your site complete the items on this panel TEMS started task gt TIVSREMT Hub or Remote gt REMOTE Connected to
141. Il and operational risk Branches close Transforming a branch infrastructure How have we created the architecture for our analytical database and achieved a near real time update of our analytical database We show near real time analytics update speed through simple Structured Query Language SQL queries from Siebel Business Analytics to the banking data warehouse and describe the architecture The bank wants to rapidly create new business products to offer its clients We leverage the capabilities presented with SOA to do this along with leveraging the existing mission critical applications We show the SOA workload running and describe the architectural components and techniques A new capability made possible by SOA a dashboard for business performance helps measure the performance of the channels We show the business dashboard with near real time business metrics and describe how we achieve rapid application build Lunch time workload increases We show how workload management can automatically maintain QoS and service level agreements based on business priorities Our promotion is working better than expected On Off Capacity on Demand We move to the Hardware Management Console to initiate an On Off Capacity on Demand request We show the effect of this request on the workload through TEP and highlight the virtualization capabilities of the platform Some problems arise at this juncture We discuss
142. In frame E the applications are displayed These are the tasks started on z OS that are attached to the different queue managers processing against the different queues The applications running against the WJMA queue manager are seen as being active These are our WebSphere z OS servant region and JMS Server running our Process Choreographer The queue depth for the WQ_ queues is zero indicating that with the current rate of throughput on the WJMA queue manager there are no problems relating to WMQ with the Process Choreographer However there is a queue depth of 20 on queue CICBEP QLOCAL1 which has not triggered the threshold but is indicative that there are 20 messages waiting to be updated to our analytical database The application task FABBEP1 is stopped It is this task that must be a long running task in order to poll the CICBEPQLOCAL1 queue and update our banking data warehouse From this Logical view a lot of information about the queue mechanisms that are central to our integration architecture and process integration is derived 5 1 4 Process integration At this stage we tried to get a more detailed view of the process that is running at volume step 4 in Table 5 1 We run this on WebSphere V5 1 with the Process Choreographer WBI SF In WebSphere V6 this is renamed as the Process Server which at the time of writing this book was not available on z OS From the SOA model Logical view Figure 5 7 we can link to the Proc
143. Infrastructure Solutions Building a Smart Bank Operating Environment Using a live showcase to demonstrate how to deliver key banking projects Building an SOA with IBM System z and IBM BladeCenter with IBM z OS and Linux Using IBM Tivoli Monitoring V6 and Tivoli Composite Application Manager V6 Christian Matthys Guillaume Arnould Neil Ashworth Stefano Delle Chiaie Eric Devezeaud Fabrice Jarassat Francois Lebe Detlef Wolf Redbooks ibm com redbooks International Technical Support Organization Infrastructure Solutions Building a Smart Bank Operating Environment October 2006 SG24 71 13 00 Note Before using this information and the product it supports read the information in Notices on page vii First Edition October 2006 This edition applies to the IBM Smart Bank showcase that demonstrates the value of IBM infrastructure in the retail banking context In particular the following IBM products are used for the showcase for the hardware IBM System z and IBM BladeCenter for the middleware IBM WebSphere Application Server V5 for systems management IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 Copyright International Business Machines Corporation 2006 All rights reserved Note to U S Government Users Restricted Rights Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp Contents Notices oprea feiss Male eee ee eget he
144. KVLOG as shown in Example 2 1 Example 2 1 IBM OMEGAMON Engine Service initialization KLVIN408 IBM OMEGAMON PLATFORM ENGINE VERSION 400 READY ON BA01 0123392084 OMEGAMON address spaces must use SNA either exclusively or in conjunction with TCP IP In the Smart Bank environment we use SNA in conjunction with TCP IP This section discusses how to check the status of the communication protocol between the following gt Between the z OS Tivoli Enterprise Monitoring Server Hub and the z OS Tivoli Enterprise Monitoring Server Remote for the connectivity to the Tivoli Enterprise Monitoring Server Hub and the Server Authentication callback gt Between the z OS Tivoli Enterprise Monitoring Server Remote and the z OS Tivoli Enterprise Monitoring Agent gt Between the z OS Tivoli Enterprise Monitoring Server Hub and the Tivoli Enterprise Portal Server on Windows SNA initialization between z OS Tivoli Enterprise Monitoring Server Hub and z OS Tivoli Enterprise Monitoring Server Remote For the z OS Tivoli Enterprise Monitoring Server Hub on BAO1 a successful SNA initialization message is registered in the RKVLOG as shown in Example 2 2 Example 2 2 z OS Tivoli Enterprise ManagementServer Hub SNA initialization message on BAO1 BSS1_GetEnv KDCFP_ALIAS KDCFC_ALIAS KLXBS_ALIAS TIVHUBLB BSS1_GetEnv KDCFP_TPNAME KDCFC_TPNAME KLXBS_TPNAME SNASOCKETS BSS1_GetEnv KDCFP_MODE KDCFC_MODE KLXBS_MODE CANCTDCS getEnv AF_SNA configuration
145. LST copy JCL Important After the CB VBA01 job runs edit the RKANPAR BAO1 parameter member and follow the directions to ensure the proper resolution of cross system variables Fl Help F3 Back OPTION gt 2 Figure 2 14 ICAT Run time Environment Utility Menu 68 Infrastructure Solutions Building a Smart Bank Operating Environment Configuring a Moveable Hub The Tivoli Enterprise Monitoring Server Hub is the core part of Tivoli OMEGAMON XE platform On one side it connects with the Tivoli Enterprise Portal Server and on the other it connects to the remote Tivoli Enterprise Monitoring Server It is a backend for the Tivoli Enterprise Monitoring Server and the Tivoli Enterprise Monitoring Agent In our environment we use the Moveable Tivoli Enterprise Monitoring Server Hub concept in z OS Parallel Sysplex environment This concept allows restarting a hub Tivoli Enterprise Monitoring Server on different members of the sysplex using a shared direct access storage device DASD The Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server clients from other platforms Windows Linux and AIX are connected with the z OS Moveable Tivoli Enterprise Monitoring Server Hub using TCP IP We used the Dynamic Virtual IP addressing DVIPA function The DVIPA can be retrieved by any member of the sysplex started by the Tivoli Enterprise Monitoring Server hub Tivoli Enterprise Monitoring Server in z OS is connected to the mo
146. Link T Business a S ink To ASM Crore Channel interaction i Processing B PR 3 Launch Access Integration Expand Expand Child Items EJB Container Se ees qj amp Print Preview WebSphere B Print L App Server les Fidelity Corebank CICS WMQ amp JMS amp WebSphere DB2 z OS MQ Internet Banking Physical 3 Smart_Bank Figure 4 7 Properties access 190 Infrastructure Solutions Building a Smart Bank Operating Environment Select the managed systems you want to apply from the menus in the right side Figure 4 8 E Navigator View Properties x Navigator Item Identity Name ATM Description ie the ATM x juf Assigned MYS_CICS BAPLEX MVS SYSPLEX Available Managed Syster Lists Available Managed Systems BA01 K01MYAP KWOSDI BAT KYA im gt gal l ALL_CMS a ALL_UNIX E CPIRA_MGR EIB HUB LINUX_SYSTEM lv Edit Managed System Lists Figure 4 8 Assigning a managed system to a Logical view level After this setup in the workspace build views that deal with one of these assigned managed systems At this level you can also manage situations that apply to all the selected managed systems Chapter 4 Customizing the Logical views 191 4 2 2 Using managed system inheritance During the Edit Navigator View process you can copy
147. Logical view is a more technical view showing the details When we perform the On Off Capacity on Demand the following points become obvious to the client gt System resources can be dynamically added to the System z9 109 environment when required gt The in flight workload immediately takes advantage of this extra resource and maintains service level agreements with business channels and gains business Until now a description of how IBM Tivoli Monitoring V6 1 provides enterprise wide views of the infrastructure while focusing on specific platforms in our case IBM System z9 109 was provided 5 3 Branch transformation and infrastructure simplification heterogeneous view In this proof point we demonstrate to our clients the ability to simplify the distributed environment by consolidating our branch servers to Linux guests on z VM This is in keeping with a real life request proposed by a client The main business reason provided by the bank was reducing operational costs through centralization and simplification With IBM Tivoli Monitoring V6 1 we monitored this environment on z VM with the branch workload we injected directly to the Linux branch servers This section shows the monitoring of a heterogeneous environment Applications that adhere to the J2EE programming model which are consequently platform independent can be deployed on a number of different operating systems With Linux as an open operating environment
148. M Oz OS OMEGAMON XE agents gt Monitoring services V6 1 gt z OS amp Sysplex gt Network gt Storage gt Unix System Services USS gt DB2 gt DB2plex gt CICS CICSplex gt WebSphere gt WebSphere MQ zVM Linux Guest OMEGAMON XE agents gt Linux gt WebSphere IBM eServer xSeries x335 UWindows XP gt Tivoli Enterprise Portal for OMEGAMON XE Dashboard edition V6 1 Enterprise Portal access via browser a Management Server Portal Server B IBM CISCO 6509 Switch BladeCenter QOMEGAMON XE ka agents gt Windows gt Linux gt WebSphere Figure 2 5 Tivoli system monitoring infrastructure Chapter 2 IT environment of the Smart Bank showcase 59 2 1 4 Summary Figure 2 6 describes the complete backend corebanking infrastructure view for the Smart Bank project test environment used in this book CPSM W U 1 Websphere Websphere Websphere Websphere Application Application Application Application Server Server Server Server V5 me V6 V5 CICS BEP Data Server ma MQ CHINIT QMGR AOR CICS BEP Messages Server i j a CICS BEP Event collector Figure 2 6 Detailed corebanking back office infrastructure view 2 1 5 Configuring the Smart Bank showcase
149. Management Server gt OnAIX Remote Tivoli Enterprise Management Server The AlX based Tivoli Enterprise Management Server Remote serves as the Primary Tivoli Enterprise Management Server for all AlX based and Linux based agents It also hosts all the distribution packages for the AIX and Linux systems For AlX based Remote Tivoli Enterprise Management Server it is easy to add a secondary Tivoli Enterprise Management Server Hub statement Thus the support for the Hot Standby configuration of the Tivoli Enterprise Management Server Hub is fully supported 36 Infrastructure Solutions Building a Smart Bank Operating Environment IBM Tivoli Monitoring agents The local agents on this system the operating system agent connect only to the local Remote Tivoli Enterprise Management Server If the machine is lost which is one of the assumptions a secondary connection will not help gt Onz OS Each logical partition LPAR hosts its own Remote Tivoli Enterprise Management Server All the z OS based agents connect only to their local Remote Tivoli Enterprise Management Server using in our case SNA No other protocol is configured Only the Tivoli Enterprise Management Server Remote can use IP communication to connect to the Hub Tivoli Enterprise Management Server 1 4 4 IBM System z environment scenario In this scenario we address a client situation where we have a dominant IBM System z based environment and
150. Manager V6 Although the role of these tools is mainly to optimize the IT infrastructure they play an important role across other solution areas in helping manage heterogeneous infrastructure Copyright IBM Corp 2006 All rights reserved ix This book includes the following chapters gt Chapter 1 Introducing the technical architecture of the Smart Bank showcase on page 1 describes the architecture of the Smart Bank showcase and discusses the choices the components and the IBM Tivoli Monitoring design gt Chapter 2 IT environment of the Smart Bank showcase on page 51 provides details about the components and the implementation of the showcase gt Chapter 3 Using Physical views on page 121 describes the Physical views used in the showcase gt Chapter 4 Customizing the Logical views on page 181 describes the customization of the Logical views used in the showcase gt Chapter 5 Scenarios and use cases on page 257 describes the scenarios presented in the showcase The team that wrote this IBM Redbook This book was produced by a team of specialists from around the world working at the IBM European Products and Solution Support Center PSSC Montpellier France in collaboration with the IBM International Technical Support Organization ITSO Poughkeepsie center The PSSC is the largest support center in Europe for IBM eServer including IBM System z IBM System p IBM System i IBM
151. Model IBM Component Business Model System x DB2 Universal Database IBM System z9 DB2 MQSeries System z Distributed Relational Database NetView Tivoli Enterprise Console Architecture OMEGAMON II Tivoli DRDA OMEGAMON TotalStorage DS6000 OS 390 VTAM DS8000 Parallel Sysplex WebSphere ESCON POWER4 z OS eServer POWER z VM GDPS Rational z9 Redbooks zSeries The following terms are trademarks of other companies SUSE the Novell logo and the N logo are registered trademarks of Novell Inc in the United States and other countries Oracle JD Edwards PeopleSoft Siebel and TopLink are registered trademarks of Oracle Corporation and or its affiliates Interchange Red Hat and the Shadowman logo are trademarks or registered trademarks of Red Hat Inc in the U S and other countries VMware the VMware boxes logo and design are registered trademarks or trademarks of VMware Inc in the United States and or other jurisdictions EJB Enterprise JavaBeans J2EE Java JavaBeans JavaServer JDBC JRE JSP JVM Solaris Sun and all Java based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both ESP Expression Internet Explorer Microsoft PowerPoint Windows Server Windows and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both Intel Intel logo Intel Inside logo
152. Monitoring Agents and Tivoli Enterprise Monitoring Servers Remote However IP PIPE must be used for communication between Tivoli Enterprise Monitoring Servers Remote and the Tivoli Enterprise Monitoring Server Hub when it runs on z OS and uses the VIPA Chapter 2 IT environment of the Smart Bank showcase 87 Table 2 2 shows the listening port setup of each component in our environment Table 2 2 IBM Tivoli Monitoring communication Port usage IBM Tivoli Monitoring Protocol Listening port Comment component Tivoli Enterprise Portal Server Hypertext Transfer Protocol HTTP HTTP over SSL IP PIPE IPUDP Tivoli Enterprise Monitoring Server Hub z OS IP PIPE IP UDP Tivoli Enterprise Monitoring Server Remote IP PIPE IP UDP Tivoli Enterprise Monitoring Agent gt 1920 tcp gt 15001 tcp tcp 2018 udp 2018 tcp 2018 udp 2018 Calculated during Tivoli Enterprise Monitoring Agent startup Listening ports to communicate with Tivoli Enterprise Portal Listening ports to communicate with Tivoli Enterprise Monitoring Server Remote and Tivoli Enterprise Portal Server The ports do not use the default value 1918 due to the implementation of the Moveable Hub on the z OS platform Listening ports to communicate with Tivoli Enterprise Monitoring Agent Listening port 2018 N x 4096 where N is the startup sequence Communication model Network connections Figure 2 32 shows the connectivity using I
153. N XE for Storage on z OS V3 1 0 IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1 1 0 IBM Tivoli OMEGAMON XE on z OS V3 1 0 OMEGAMON XE for 0S 390 UNIX System Services V220 OMEGAMON XE for WebSphere Application Server V130 Fl Help F3 Back F5 Refresh F7 Up F8 Down COMMAND gt Figure 2 9 ICAT Product Selection Menu screen After Tivoli Monitoring Services on z OS V6 1 0 product is selected a run time environment screen is displayed Figure 2 10 Because this is the first OMEGAMON product configured in this environment no run time environment is displayed The run time environment is not yet defined Depending on how you want to use the run time environment you can either define a full run time environment or a set of base run time environment and sharing run time environment RUNTIME ENVIRONMENTS RTEs Actions A Add RTE B Build libraries C Configure L Load all product libraries after SMP E D Delete U Update V View values Z Utilities Action Name Type Sharing Description Enter Next Fl Help F3 Back F7 Up F8 Down COMMAND gt Figure 2 10 ICAT Run time Environment screen Chapter 2 IT environment of the Smart Bank showcase 65 For the Smart Bank environment we created one base run time environment and three sharing run time environments gt One run time environment type BASE named BASE To allocate our base libraries This environment is shared by all the participating images This base ru
154. ND EXEC gt Updating BDW TXN by adding a transaction to the specific account Example 3 2 shows the INSERT statement performed by our batch process Example 3 2 Example of INSERT EXEC SQL INSERT INTO BDWCORO TXN TXN_TP_ID TXN_ID AU ID PRD BAL_TP_ID PNT BAL_TP_ID MSR_PRD_ID UOM_ID CNSL_MTH_ID SRO_ID NET CASH FLOW_AMT PST DT ACG_EFF_TP_ID Chapter 3 Using Physical views 159 TXN_DT TXN BOOK DT PPN_DT TXN_VAL_DT PPN TM EXCP_CAUS_ID PST_ENTR_AMT EXCP_IMP_ID UNQ_ID_SRC_STM DVC ID VALUES TXN TP ID W00 TRANS IDFR AU ID1 PRD BAL TP ID PNT BAL TP ID MSR PRD ID W00 CRNCY IDFR PSTG AC CNSL MTH ID SRO ID W00 ACCTG AMT 2028 03 31 ACG EFF TP ID 2028 03 31 2028 03 31 REAL DATE 2028 03 31 ZZTIME EXCP CAUS ID WOO ACCTG BSE AMT EXCP IMP ID UNQ ID SRC STM WOO WS ID END EXEC To perform an ongoing analysis of an incoming MQ message a batch job FABBEP1 is run It uses the program CORBEP 1 which is linked edited and then bound on DB2 earlier on Example 3 3 shows a sample bind job for the CORBEP1 program Example 3 3 Sample bind job BEPBIND JOB AX4328 CLASS A MSGCLASS 0 MSGLEVEL 1 1 NOTIFY amp SYSUID REGION 0M JOBPARM SYSAFF BRRRRRRRRR e He e e ke e e he He KERR KEE RE REE RR EE RER ERE RR ERE EKER ER ERR EER ER EERE BRRRRRRRRR RRR ERR ERE ER EK RE RE REE REE HK EER
155. NN cart cet eect s a EJB Containers B J2EE Connector Connection F Thread Pools Dynamic Cache Workload Management Web Container SMF Interval J2EE Server Container SMF ls ea MM B es Physical Milliseconds C Connection Creation Rate Bi Connection Destroy Rate Connection Allocation Rate a o a jdbo BPEDB jdbo BDWds jdbe COREBANKds spuosag Jad suoyoauuog DB Connection Pools Datasource Sample Interval Instrumentation Connections Connections Connections Threads That Average Size Average Number of Average Average Name Date andTime Time Level Created Released Allocated Timed Out ofthePool Threads Waiting Wait Time Use Tim amp jdbc BPEDB 03 1 4 06 16 54 58 60 High 0 0 9 0 6 000 0 000 0 000 39 666 jdbciBDWds 03 1 4 06 16 54 58 60 High 0 0 2 0 5 000 0 000 0 000 19 500 jdbciCOREBA 03 1 4 06 16 54 58 60 High 0 0 1 0 3 000 0 000 0 000 23 000 Server Level 03 14 06 16 54 58 60 High 0 0 12 a 14 123 0 000 0 000 34 916 E 2j CS Hub Time Di 03 1 4 2006 04 56 PM I Server Available DB Connection Pools 9 212 128 31 WOLF1 Figure 3 23 The DB Connection Pool workspace Set the following rules gt For system programmers Percentage of the pool connections used The average wait time gt For business managers If database connections that are specific to a sing
156. O Figure 5 3 Initial multichannel workload step1 Chapter 5 Scenarios and use cases 263 Figure 5 4 shows step 2 described in Table 5 1 which we used in this book to show the actual Web services running through the infrastructure Browser client Workload Injection HTTP z OS LPAR SOAP HTTP WebSphere Application Server v6 Neb Container new action beans EJB Containe CICSPlex CICS v3 1 O po i Web service created from action beans HTTP Server plug in stateless session beans APICall Fidelity API data mediation classes Fidelity Server Communication Layer Figure 5 4 Multichannel workload injected with Web services step 2 Figure 5 5 shows step 3 described in Table 5 1 our interim step to use the CICS Transaction Gateway and the strategic software tooling provided by WebSphere and IBM 264 Rational z OS LPAR WebSphere Application Server v5 1 HTTP CICSPlex CICS v3 1 a TORs AORs Web Container action beans Workload Injection HTTP semet HTTP Server plug in Enterprise service java bean proxy JCA ECI java classes Resource adapter CTG Server v5 1
157. P PIPE and IRUDP The arrows indicate the direction of the connection established during the initialization phase of each component 2018 tep 12018 udp Q TEMS Hub 2018 tcp 2018 udp TEMS Remote 2018 tep 2018 udp OS Agent Application Agent A f NG Z 7 k DS EP Browser Universal Agent Figure 2 32 Communication model Network connections TCP environment 88 Infrastructure Solutions Building a Smart Bank Operating Environment Multiple network interface cards In our environment all the Tivoli Monitoring Servers and some Tivoli Monitoring Agents have more than one NIC Therefore for effective communication between the Tivoli Monitoring components it is mandatory to identify which NIC to use KDCBO_HOSTNAME enables you to specify which host name or TCP IP address is bound to the NIC When specifying the KDCBO_HOSTNAME variable the IBM Tivoli Monitoring components listen on all the interfaces However when initiating a connection to a remote component the components use only the NIC specified in the KDCBO_HOSTNAME variable To enable the KDCBO_HOSTNAME variable perform the following tasks 1 Add the KDCBO_HOSTNAME variable in the configuration files used by the miscellaneous Tivoli Monitoring products Table 2 3 shows the names of the config files in which the KDCBO_HOSTNAME variable is added Table 2 3 Config files to add KDCBO_HOSTNAME variable Windows Tivoli KDCBO_HOSTNAME lt prod
158. PROCESS SOA oee Target Selection Mode Absolute O Relative Cancel Delete Figure 4 24 Choosing the absolute link target workspace Go to the selected Navigator view zone A to reach the target workspace In our example we use the Branch workspace Figure 4 25 Select Teller 22 KJRITMOO1I Link Wizard Define New Link Branch details a Target Select the link to workspace z Select the Target Navigator item from the list You can also select a workspace from a different Navigator view y f Workspace shows multiple workspaces select the one to which you want to link x If you want to change the target method click Relative See below Click Finish OR if you want to open the Link expression editor to refine the link definition click Next r Target Workspace Navigator View Smart_Bank x Teller Md Smart_Bank a 8 Teller al Shentification D Eg Banking fj Teller Channel E3 ATM E3 Web zBank GDPS HyperSwap PROCESS SOA Target Selection Mode Absolute O Relative el Back Jil Next gt Finish Help Figure 4 25 Finding the target workspace 208 Infrastructure Solutions Building a Smart Bank Operating Environment Inthe area called Workspace zone B as shown in Figure 4 26 the name of the targeted workspace is displayed In the area call
159. Portal Server is placed on Windows It distributes the TCP IP address of the virtual machine to the network Even if the Tivoli Enterprise Portal Server moves it retains this address e On IBM Tivoli Monitoring agents IBM Tivoli Monitoring agents for monitoring the server software such as the operating system and the DB2 Universal Database are installed on the Tivoli Enterprise Portal Server systems too These agents connect to the Windows based 46 Infrastructure Solutions Building a Smart Bank Operating Environment Tivoli Enterprise Management Server Remote as their primary server and to the AlX based Tivoli Enterprise Management Server Remote as their secondary server Thus they have two ways in which to report to the Hub Tivoli Enterprise Management Server On Linux VMware supports almost all the IBM System x based operating systems including Linux SUSE and Red Hat distributions For support information contact your local IBM Sales Representative gt On Windows Remote Tivoli Enterprise Management Server The Windows based Tivoli Enterprise Management Server Remote acts as the primary Tivoli Enterprise Management Server for all Windows based agents It also hosts all the distribution packages for the Windows systems For Windows based Remote Tivoli Enterprise Management Server it is easy to add a secondary Tivoli Enterprise Management Server Hub statement IBM Tivoli Monitoring agents The local agents
160. Portal Server to handle the connections coming from the intranet network a Launch the Manage Tivoli Monitoring Services program and right click the relevant option in this case the Tivoli Enterprise Portal Server as shown in Figure 2 39 Select Advanced Configure TEPS Interfaces H Manage Tivoli Enterprise Monitoring Services TEMS Mode Local Computer Actions Options Yiew Windows Help Zizo SI 2 A 22 Eclipse Help Server HELPSYR No 3 0 1 Tivoli Enterprise Portal Browser Yes NJA NJA NJA 06 10 00 00 localhost Tivoli Enterprise Portal Desktop Yes NJA NJA NJA 06 10 00 00 blades Tivoli Ente Yes TEMS Started Auto RSA a N a s R a aal A R a i oara 5k o2 Universal s Stop Yes TEMS Started No Yes 06 10 00 00 oe Monitoring Yes TEMS Started Auto LocalSystem Yes Yes 06 10 00 00 Recycle Change Startup Change Startup Parms Set Defaults For All Agents Configure Greate Instance Reconfigure Advanced Configure Adyanced Unconfigure Browse Settings j kad N Remove Instance a a Configure TEPS Interf Configure Java App neea Licensing View Trace Log Edit Variables Edit ENV File Edit EIF Configuration Edit TEC Server Mapping File Set Network Interface Configure SOAP Server Hubs Utilities Configure Firewall Interfaces for TEP Server Figure 2 39 Configuring the T
161. Q is more or less the same across all the supported platforms It always displays the same navigation tree independent of the platform it is running on Some workspaces may stay empty because data is not available for that platform All the rules defined for this agent type can be spread across all the underlying platforms ax File Edt View Favorites T Address http 9 212 128 31 1920 cnp kat E EJ Go ay MEWY Enterprise Portal e Tivoli File Edit View Help AHHH Ha S m Application Statistics Buffer Pool Statistics Channel Definitions Channel Initiator Status Channel Performance Cluster Queue Manager Dead Letter Queue Message Log Manager Performance Message Manager Performar MQSeries Events Page Set Statistics Queue Definitions Queue Manager Status Queue Statistics csQ2 WIMA DE mue Nnarstinn Sucker ES 400 200 h ull Channel Summary Number of Channels 24 s Physical Queue Manager Status HHBAS HAM ZOO VSOUBSEAEET OTH View Physical g nAz FM Queue Summary OZ Pm SPMOSERIES Bl Number of Queues 5 89 csQ1 J 2 EH Application Debugging csat Dimonitored Queues Gs as with High Depth E Curent channels Minactive Channels Din Doubt Channels QMgr Host QmMgr Host Start Mor amar DLA Monitored Local Remote Alias Transmit
162. RL without any error the URL has the status OK The HTTP provider has the ability to manage the exceptions when the URL encounters problems such as The server does not exist and the status field indicates Not a recognized network address The HTTP service does not reply and the status field indicates URI authority not found The HTTP service is up but the page does not exist and the status field indicates 404 resource not found gt Current response time The response time field specifies the number of milliseconds taken to load the content of a Web page This value is a good way of reflecting the amount of time required by users when connecting for the first time to an URL no data in browser s cache In sucha situation the Universal Agent must be installed in a location that is close to the users The measurement can be mitigated assuming that a part of the Web page is stored normally in the browser s cache the Universal Agent does not cache data The percentage of objects that can be cached can be assessed as follows Look in the URL_OBJECTS workspace to identify the number and size of the miscellaneous objects such as GIF and JPEG images that must be cached by a browser The MANAGED_URL workspace provides the total number of bytes downloaded for the objects in the Total Object Size field Estimating the percentage of objects that must be cached 50 means that if the page contains ten
163. S Mig Banking Channel Access Teller Channel Points zBank GDPS HyperSwap amp ATM t Intand Z Te memet Intranet BR Bank GDPSHyperSwap e ae Channel interaction LPR ee RTE IC SN Mi PROCESS SOA gt Access Integration 1 tore systems amp O Enterprise Business ATM Integration Processing 3 Physical lt 3 Smart_Bank i Pamens cs Fes ZE Internet Banking ca PROCESS SOA Enterprise View SSS n a lt m E p 4 Fal Notepad Dab amp Hub Time Sat 03 11 2006 05 54 PM Server Available Smart_Bank 9 212 128 31 SYSADMIN Figure 4 27 Utilization of the new absolute link 210 Infrastructure Solutions Building a Smart Bank Operating Environment 6 The TEP executes the demand and the target workspace is now displayed as shown in Figure 4 28 File Edit View Help e gt FHHRBRGAA STOO CSQWRBSERAERVP OTD 63 View Smart_Ba v D B x Gi ew Dao x ee IRTE R Kk Ho ol S HE Smart_Bank EE Authentification Banking 3 Teller Channel Enterprise a ATM integration Web a zBank GDPS HyperSwap Channel Interaction PROCESS SOA Access Iniegration Core Systems amp Pesca e SaaS Wier aaia Businass Channel Access i R Points EJB Container S Intranet WebSphere App Server Linux z VM All ae S F Branch Server EJB Container Fidelity LA Aeee WebSphere WebSphere Corebank Linux Blade Anp Servar App Server CICS WMQ amp Linux Blade Linux Blade DB2 z OS Branc
164. SE 00 00 08 904 00 00 26 410 113785 13484 776 STCUSER CICSRA10 03 21 06 00 00 03 317 CRBCORO AHUKM1 0 0 WAIT REUSE 00 00 02 145 00 00 06 238 27223 3246 185 S5TCUSER_ CICSRA10 03 21 06 00 00 03 033 CRBCORO AHUKM1 0 0 WAIT REUSE 00 00 01 775 00 00 05 364 22463 2687 153 5TCUSER_ CICSRA11 03 21 06 00 00 03 433 CRBCORO AH2W5R 0 0 WAIT REUSE 00 00 00 700 00 00 04 661 7786 334 151 STCUSER CICSRA10 03 21 06 00 00 10 867 CRBCORO AH2W5R 0 0 WAIT REUSE 00 00 00 615 00 00 03 022 5947 290 132 5TCUSER CICSRA11 03 21 068 00 00 04 569 CRBCORO AH2W5R 0 0 WAIT REUSE 00 00 00 301 00 00 01 712 2953 140 66 STCUSER CICSRA1O 03 21 06 00 00 01 841 CRBCORO AH2WS5R 0 0 WAIT REUSE Sea 00 00 01 454 2323 97 45 STCUSER CICSRAI1 03 21 06 00 00 06 174 KO2PLAN DGO SDOB 0 0 NOT IN DB2 00 00 00 197 00 00 03 922 7006 32 3 SYSTASK__ TIV502 03 21 06 j Figure 3 37 DB2 thread activity with the CICS Business Event Publisher plan Chapter 3 Using Physical views 169 6 The window shown in Figure 3 38 is displayed Note that the CICS Business Event Publisher process is small The CPU consumption and the elapsed time IN DB2 are low The plan is allocated and uses resources only when changes occur in the posting table Because the MQ queue is monitored constantly there are not many messages to process at a given time File Edit Vie
165. SH SITNAME node NODE lt BODY BGCOLOR FEDCEF gt lt div align center gt lt h3 gt lt i gt This is expert advice for lt i gt lt h3 gt lt h2 gt namet lt h2 gt on node lt p gt Please notify your system administrator that we have a lt b gt namet lt b gt alert lt p gt To learn more click here lt a href http www 306 ibm com software sw atoz indexT html gt IBM Tivoli Products lt a gt lt div gt 196 Infrastructure Solutions Building a Smart Bank Operating Environment Copy this data into the advice setup of a situation as shown in Figure 4 13 fe Formula Distribution ice SF Action E Until y Text or Advice Location mame EVENT ATTRIBUTE ISITSTSH SITNAMES mode NODES lt BODY BGCOLOR FEDCEF gt lt div align center gt lt h3 gt lt i gt This is expert advice for lt i gt K h3 gt lt h2 gt name lt h2 gt on node lt p gt Please notify your system administrator that we have a lt b gt name lt b gt alert lt p gt To learn more click here lt a hhref http wiw 306 ibm com software sw atoz indexT html gt IBM Tivoli Products lt lt a gt lt divo NT_Bottleneck_Processor NT_Percent_Processor_Time NT_Percent_Processor_Time_L NT_Percent_Total_Proc_Time NT_Percent_Total_Proc_Time_L NT_Processor_Interrupts_Critic NT_Processor_Interrupts_Warn NT_System_CPU_Critical NT_System_Total_Interrupts_Lo
166. SH SITNAME ISITSTSH SITNAMES is a TEP variable It contains the name of the situation Replace kxx with the corresponding product code At the time of use this function replaces kxx with the full path name If you want to for example use the ADVICE function for a Linux situation on a TEP running on Windows the path is T IBM ITM CNB classes candle kiz resources advice en_us The target file is in an HTML format and its name is identical to the situation name Notes These files are implemented during installation We recommend that you do not add new files in these directories in order to avoid future migration problems If you change the TEP language using the Language Support CD change the subdirectory en_US to one corresponding to the language you have installed Advice as a user Web page Because the objective of a logical tree is to present data in an efficient manner it is a good idea to use the Web page approach directly in the ADVICE part of situation However using it disables the ability to support multiple languages You can generate the content of a Web page formatted advice by using any tool that is able to build a simple Web page When editing a situation copy the HTML content into the Expert Advice part of the situation directly You can also add variables and set up their values using the TEP event attribute variables as shown in Example 4 1 Example 4 1 Web page in a situation advice name EVENT ATTRIBUTE ISITST
167. SNMP Rin a os mee tt a ne On tthe bet A Cont Te te SE eat tt nn lt tan ose eg am See bs en en as et on an SNMP DP Parameters KUMP_SNMP_MONITOR_TRAP N KUMP_SNMP_NET_DISCOVERY Y KUMP_SNMP_NET_DISCOVER_ENTERPRISE N KUMP_SNMP_MANAGE_LOCAL_NETWORK Y KUMP_SNMP_NET_COMMUNITY public Chapter 2 IT environment of the Smart Bank showcase 117 2 Specify a logical name for the production network by editing the symbolic name file KUMSNAME located in lt ITM_install_dir gt tmaitm6 work Example 2 15 shows the contents of this file Example 2 15 Contents of the KUMSNAME file kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Network Symbolic Name Table Specify symbolic name of discovered networks Format Network address Symbolic name string For example 198 210 37 0 Westlake CTDEV 10 10 18 0 DistSystemLab kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk F F HF F F F F HF F Production network dedicated for the inter servers communications 10 1 1 0 Production Net 3 In the KUMSLIST file located in lt ITM_install_dir gt tmaitm6 work define the name of the file containing the Host Lists managed node lists of the Smart Bank servers Add the following line in this file kumlist_Smart Bank showcase def 4 Create the Hot Lists file kumlist_Smart Bank showcase def in the directory lt ITM_install_dir gt tmaitm6 work and specify the list of hosts Examp
168. SSHRBSBERERV OTOH mao x Operating System Interruptsisec G Processor Server Name Timestamp Privileged Time 2 1 220 _Total Primary BLADE12 NT 03 11 06 16 46 12 0 4 gt 2 Current Situation Values manx operating System Interrupts sec Processor Server Name Timestamp Privileged Time 5 2 1 226 _Total Primary BLADE12 NT_ 03 11 06 17 04 44 2 4 D Hee amp oeaox e OSAA Searching database for IBM r Destination Systems P Expert Advice Hub Time Sat 03 11 2006 05 02 PM 4 Server Available NT_System_Total_Interrupts 9 212 128 31 SYSADMIN Figure 4 17 The next stage of situation advice Infrastructure Solutions Building a Smart Bank Operating Environment When the data comes back from the search URL the data is displayed in the advice window Figure 4 18 NT_System_Total_Interrupts 9 212 128 31 SYSADMIN File Edit View Help eo EH RRA F COVSSHURBREAERV OTeOD 3 View Physical Iv nex eee mao x og operating System Interruptsisec Processor Server Name Timestamp rivieged Time By Windows Systems is r y FTE fa BLADE10 2 1 220 _Total Primary BLADE12 NT 03 11 06 16 46 12 ol BLADE11 E BLADE12 5 y windows os GH Disk E Enterprise Services o E Memo
169. S_ TRX_ABP 1 AvgResp 0 Low 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_ACAL 1 AvgResp 0 Low 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_ACD 1 AvgResp 0 Low 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_ACDO 1 AvgResp 0 Low 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_ACDT 1 AvgResp 0 Low 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_ACW 1 AvgResp 0 Low 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_APIA 1 AvgResp 0 Low 500 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_APIC 1 AvgResp 0 Low 900 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_ATOF 1 AvgResp 0 Low 800 0 0 00 0 0 BAPLEX BA01 MVSSYS_ TRX_ATWF 1 AvgResp 0 Low 800 0 0 00 0 0 J BAPLEX BAOI MVSSYS TRX_BBI 1 AvgResp 0 Low 100 0 0 00 0 0 Ea Physical aan ral AR ana AI o Ane Pe SET ES iN IN waa naa a aan A i Hub Time Wed 03 15 2006 06 07 PM Server Available Figure 4 49 The link on the WLM All Service Class view WLM All Service Class 9 212 128 31 SYSADMIN 6 If you click the link it selects the value in the Service Class column It uses it as a filter by setting the SERCLASS symbol to this value It then displays the filtered target workspace 230 Infrastructure Solutions Building a Smart Bank Operating Environment Figure 4 50 with only two lines one for each of the Smart Bank showcase image BAO1 and BAO2 WLM Selected Service Class 9 212 128 31 SYSADMIN Jee File Edit View Help gt ABA RRA FOO C SQOHURBHRETAARDFSOFED
170. System x and IBM TotalStorage Christian Matthys has spent more than 25 years at IBM as a System Engineer working with large mainframe oriented clients in France He spent three years as an ITSO Project Leader on assignment in Poughkeepsie NY USA In 2000 he joined the Europe Middle East and Africa EMEA Design Center for On Demand Business at the PSSC in Montpellier France working on clients projects to make use of leading edge technologies He works as a Project Leader for the ITSO Poughkeepsie Center NY USA He is based at the PSSC He is a certified Consulting IBM IT Specialist Guillaume Arnould joined IBM in 1996 and started working in the IBM System z Manufacturing Test Engineering Department before spending two years in an international assignment in Poughkeepsie NY USA In 2001 he joined the IBM PSSC team in Montpellier France to work as a Performance Expert on IBM DB2 for z OS client benchmarks where he has been since then He is a DB2 for z OS IT Specialist in the infrastructure solutions department at IBM PSSC Guillaume is a Technical Team Leader in the Smart Bank showcase project He is responsible for leading the new developments and production platforms He holds an engineering degree in automation electronics and computing from Ecole Superieure en Informatique Electronique et Automatisme ESIEA Paris His areas of expertise include DB2 DB2 data sharing performance tuning and administration Neil Ash
171. TCHHOT 1 Velocio 0 Highest 50 0 0 0 00 A Teller Channel BAPLEX BA01 MVSSYS_ BATCHLOW 1 Discret 0 nla 0 0 a 0 00 ATM BAPLEX BA01 MVSSYS CICS_AOR 1 Velocio 0 Medium 50 0 0 0 62 B Web BAPLEX BA01 MVSSYS CICS_CPS 1 Velocio 0 Medium 50 0 a 2 00 zBank GDPS HyperSwap Take Action gt ETOR 1 Velocio 0 Medium 50 0 0 0 50 1 H PROCESS S0A pes aG d alacio 0 Medium 30 0 0 1 57 nk To gt amp LinkWizard Resp 0 Low 600 0 0 0 00 E Export sor Ss esp 0 Low 500 0 0 0 00 IOP 1 AvagResp 0 Low 500 0 19 0 03 amp Launch MDBD 1 AvgResp 0 Low 500 0 60 0 12 R p MDBEDW 1 AvgResp 0 Low 500 0 36 0 07 m Splitvertically TRF 1 AvgResp 0 Low 600 0 0 0 00 E Splithorizontally YEB 1 AvgResp 0 Low 500 0 250 0 50 2 OTHER 1 SysGoal O nla 0 0 0 0 00 x Remove STC 1 SysGoal 0 nla 0 0 0 0 00 amp Print Preview TEM 1 SysGoal O nia o o 0 0 00 _ABI 1 AvgResp 0 Low 600 0 0 0 00 Print _ABP 1 AvgResp 0 Low 800 0 0 0 00 A _ACAL 1 AvgResp 0 Low 800 0 0 0 00 E Properes ACD 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BAOT MYSSYS TRX_ACDO 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BA01 MYSSYS_ TRX_ACDT 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BA01 MYSSYS_ TRX_ACW 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BA01 MVSSYS_ TRX_APIA 1 AvgResp 0 Low 500 0 0 0 00 BAPLEX BAO1 MYSSYS TRX_APIC 1 AvgResp 0 Low 900 0 0 0 00 BAPLEX BAO1 MYSSYS TRX_ATOF 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BA01 MVYSSYS_ TRX_AT
172. TF 8 A detailed Installation Guide is available on the CD or in the packages available on this Web site To install the application support on Windows Tivoli Enterprise Portal Server perform the following tasks a Run setupwin32 exe from the CD Monitoring Services on z OS 350 360 Workspace Enablement b During the installation process specify which Tivoli Monitoring component you want to add application support to Select the Tivoli Enterprise Portal Server d Select the application you want to add support for as shown Figure 2 41 4 Installer O x Please select which applications you would like to add support for Je IBM Tivoli OMEGAMON DE on z OS 03 10 00 00 IBM Tivoli OMEGAMON XE for CICS 01 00 00 00 IBM Tivoli OMEGAMON XE for CICS on z OS 03 10 00 00 IBM Tivoli OMEGAMON XE for CICSPlex 02 20 00 00 IBM Tivoli OMEGAMON XE for Cryptographic Coprocessors 01 00 00 00 IBM Tivoli OMEGAMON XE for DB2 03 00 00 00 IBM Tivoli OMEGAMON XE for DB2 03 10 00 00 IBM Tivoli OMEGAMON XE for IMS 01 00 00 00 IBM Tivoli OMEGAMON XE for IMS on z OS 03 10 00 00 IBM Tivoli OMEGAMON XE for IMSplex 02 20 00 00 IBM Tivoli OMEGAMON XE for Mainframe Networks 01 00 00 00 ATVAAAWAAAWASA IBM Tivoli OMEGAMON XE for Mainframe Networks 03 10 00 00 IBM Tivoli OMEGAMON XE for 0S 390 01 40 00 00 IBM Tivoli OMEGAMON XE for OS 390 Unix System Services 02 20 00 00 I IBM Tivoli OMEGAMON XE for SMS 01 00
173. T_DISC Discret O nla BAPLEX BAQUMYSSYS BAT_3V30_ _1_ Velocio 0 Medium BAPLEX BA01 MVSSYS BAT_3V40 Velocio 0 Medium SEET nner CEJ F Query f Fitters Thresholds Az Style Options Show _ Show Border Title Text ProcHeader Text for Chart Header Fortnane Text for Chart Header Helvetica w is 6 m Ejeo taic style Header Figure 4 59 Using the new symbol Chapter 4 Customizing the Logical views 239 Advanced link The full sample Just as a user will open the WLM All Service Class workspace Figure 4 49 on page 230 When you click the blue chain the target workspace displays the now filtered data and a new header that is the substitution of the ProcHeader symbol as a result of the expression A dynamic link can not only filter the data but also dynamically adapt the contents of the view Figure 4 60 2 WLM Selected Service Class 9 212 128 31 SYSADMIN WJiees File Edit View Help e o gt NHHARBROAM TOO CSQOHURBSBERERFAOFTEE E View Smart_Ba max Zz P Smart_Bank E a Teller Authentification amp Banking ccs DB2 MQSeries TCP WebSphere 32 BAT_DISC Selected batch workload discretionary BAT_DISC Selected batch workload discretionary Service Goal Goal i Average Class Percentile Importance Value Duration Response
174. The Tivoli Enterprise Managing Server is responsible for tracking the operability of the connected components by exchanging heartbeat requests with all the Tivoli Enterprise Management Agents connected to it There is a difference between Tivoli Enterprise Managing Server Hub and Tivoli Enterprise Managing Server Remote Any Tivoli Monitoring infrastructure requires at least one Hub Tivoli Enterprise Managing Server The Tivoli Enterprise Managing Server Remote is used to meet scalability requirements The Tivoli Enterprise Managing Server Hub stores initiates and tracks all the situations and policies and is the central repository for storing all active conditions The Tivoli Enterprise Managing Server storage repository is a proprietary database format grouped as a collection of files located on the Tivoli Enterprise Monitoring Server Following are the platforms that are supported z OS AIX Linux Solaris Windows vvvvy Infrastructure Solutions Building a Smart Bank Operating Environment Tivoli Enterprise Portal Client The Tivoli Enterprise Portal Client is a Java based user interface that connects to the Tivoli Enterprise Portal Server to view all the monitoring data collections gt i OK Q a p2 K QO amp Fie Edt View Favorites T Address http 9 212 128 31 1920 cnpikd E EJ Go Ar Tivoli Enterprise Portal File Edit Yiew Help mA eiae r a a E a rE E E E E view Physical gy IF Situ
175. US_BY_REQUEST HIST_STATUS_STAT HIST_TRANSFER_BY_LOCATION HIST_TRANSFER_BY_REQUEST HIST_WORKLOAD_BY_DAY HIST_WORKLOAD_BY_HOUR RKLOAD_DETAIL EH y 10 1 1 125ASFSdp UAGENTOO xl HER SAAS aood SBSUBBEAEARD 9 AeA O 8 EAEE 0 8 O x R Workioad perre D amp O x RT Workload per second last 5 mi O B O x O BytesReceived E BytesReceived PerRequest E BytesReceived PerSecond M BytesSend M BytesSend PerRequest M BytesSend PerSecond f Interval Unit Interval Occurrences LocalTimeStamp_ BytesReceived BytesSend BytesReceived PerSecond BytesReceived PerRequest BytesSend PerSecond BytesSend PerRequest Date Time 300 1 03 23 06 16 32 00 0 14935 878 2006 03 23 16 32 00 00 Figure 3 43 TEP HTTP workload details 3 4 4 Simple network monitoring The Simple Network Management Protocol SNMP data provider available in the Universal Agent provides information pertaining to the network environment such as nodes availability nodes description and so on The installation and settings are described in 2 2 The distributed environment on page 84 In our environment monitoring is focused only on the production network network 10 1 1 0 24 The content of the attribute groups relates to the settings defined during the configuration of the SNMP data provider The managed system lt hostname gt SNMP MANAGEROO has two attribute groups containing data the others are empty gt The fir
176. WF 1 AvgResp 0 Low 800 0 0 0 00 BAPLEX BA01 MVSSYS_ TRX_BBI 1 AvgResp 0 Low 100 0 0 E Physical 8 Smart_Bank Hub Time Mon 03 13 2006 02 33 PM Figure 4 36 Accessing the Link Wizard Server Available WLM All Service Class 9 212 128 31 SYSADMIN Chapter 4 Customizing the Logical views 219 3 A new link named WLM Details is created as shown in Figure 4 37 Clicking the Next button takes you to the next window asking for the target workspace of the link WLM All Service Class 9 212 128 31 SYSADMIN Jae File Edit View Help gt EOERRBRPSCAM S COC S SHRBARRBTARFT SFO View Smart Bov MB x G Class R g as Authentification Banking cics DB2 M Series TCP WebSphere WLM All Deo amp Page 1 of3 a Teller Channel ATM Web zBank GDPS HyperS PROCESS SOA Bee Link Identity Name WLM Details Description View WLM details with data selection 0 00 s Physical Smart _Bank Meni MARARA UAI Fe AA TE mE PR s isase anan a AT CETS Hub Time Mon 03 1 3 2006 02 42 PM Server Available WLM All Service Class 9 212 128 31 SYSADMIN Figure 4 37 Giving a name to the new dynamic link 220 Infrastructure Solutions Building a Smart Bank Operating Environment 4 From the Logical view navi
177. a Gy EEREESIE ces H Message Arrival By Services Management Agent Env Performance Summary Message Summary Faults Summary E amp Storage Subsystem oy fi WebSohere Application Server 05 3960 ills B KFWITMO25I 4 Navigator updates pending Physical ene 14 Data Collector Monitor Control Configuration EE Data Collector Filter Control Configuration A 3 Message Application Application arin Application Application Filtering 3 i Eene Name Operation Name Logging Level Server Name Server Environ Origin Nade Server Environment gem me Hostname Operation Name IF i None aasr011 WebSphere_Applicati KEO EM SSS U CS Hub Time Fr 03 1 7 2006 06 07 PM J Server Available Services Management Agent 9 212 128 31 WOLF1 Figure 3 9 The Service Management Agent workspace Chapter 3 Using Physical views 133 The Message Arrival workspace This workspace shown in Figure 3 10 offers a convenient summary of the number of messages that arrive in the data collector for each combination of service name operation name and remote IP address that are configured for monitoring Because no modifications were made all the messages are filtered by the product predefined situation The default shows the message arrival data for all the service names and operation names z p a 8X OQ O a la pa ke O amp Fie Edt View Favorites T Address
178. a Logical view by including all the systems that participate into a composite application Set up alerts in order to follow the quality of service of these applications at each point gt Determine the priorities of actual incidents Build a Logical view with levels such as Priority One Priority Two and so on Associate a situation to its corresponding severity level The operations team will know where to focus on first gt Migrate from OMEGAVIEW Analyze your OMEGAVIEW organization Reproduce each icon on an OMEGAVIEW display to a child in the Logical view tree and then build situations to map the existing OMEGAMON thresholds and associate them at the right place Then add value using links advice and so on Chapter 4 Customizing the Logical views 255 256 Infrastructure Solutions Building a Smart Bank Operating Environment Scenarios and use cases This chapter provides examples of Logical views and Physical views that the Smart Bank showcase uses to demonstrate its business proof points The focus is on three use cases that help prove three different proof points and demonstrate the efficiency of IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 Following is a list of these use cases gt Core system transformation service oriented architecture gt Optimization of IT resources On Off Capacity on Demand gt Branch transformation and infrastructure simplification heterogeneous view Copyrigh
179. a imposed on the monitored events and provides the data selection and layout criteria for the resulting message Rules also contain the destination message queue names and MQSeries MQPUT options along with properties that control subsequent processing for example when a message will be sent and when an action will be taken if an unrecoverable error is detected The rules are generated on a workstation and sent to the CICS Business Event Publisher for MQSeries message server using TCP IP communication Although they are physically stored in a VSAM file these rules are ultimately cached in a data space owned by the data space server for efficient access and persistence across message server and connector restarts CICS Business Event Publisher for MQSeries provides the necessary means to refresh the cache The rules database resides on the z OS system and contains data built through a Windows technology based graphical user interface GUI Refreshing the rules database is simple You can make changes without interrupting the message server or losing work If a refresh action takes place when a unit of work is in progress it continues to use the previous rules database until it reaches a syncpoint The rules database and workstation administration client utilize an easy to use hierarchy structure in which rules are contained in groups and groups are contained in lists The CICS Business Event Publisher for MQSeries workstation administration clie
180. a specific level 00 eee 190 4 2 2 Using managed system inheritance 0 000 eee 192 4 2 3 Adding views with explicit managed system 000 eee 193 4 3 Assigning situations to a Logical View 0 0 00 cece eee 193 4 3 1 Creating and deleting a situation 0 0 00 cee 194 4 3 2 Associating and dissociating a situation 0 0 00 eee 195 4 3 3 Advice ina situation 6 0 tees 196 4 4 Defining the linkS 0 0 0 0 201 4 4 1 Introducing the links 0 0 0 0 ee eee 201 4 4 2 Defining an absolute link 0 0 0 2 eee 203 4 4 3 Defining a relative link 0 0 eee 211 4 4 4 Defining an advanced link 0 0 e eee 214 4 5 Style in the Logical view 0 00 c cette eee 241 4 5 1 Using the standard Tivoli Enterprise Portal 00 0 020 c ee eee 241 4 5 2 Using the Smart Bank showcase Style 000 0c eee eee eee 242 iv Infrastructure Solutions Building a Smart Bank Operating Environment 4 5 3 Setting up a style in a graphic View 0 0 00 ccc eens 243 4 5 4 The Smart Bank showcase css style file 0 2 0 2 0000 cee eee 245 4 5 5 The example The Smart Bank showcase Logical view 246 4 6 Logical view Lessons learned 0 eee 252 Chapter 5 Scenarios and use casesS 0 0 00 eens 257 5 1 Core system transformation service oriented architecture 0005 258 5 1 1 Introducing t
181. ached to that machine move with the virtual system See Tivoli Enterprise Portal Server implementation based on Linux on IBM System z under z VM on page 42 for more details IBM Tivoli Enterprise Portal Server Linux on IBM System z also gets its own Tivoli Enterprise Management Server Remote that serves as the primary and only Tivoli Enterprise Management Server for all Linux on IBM System z based agents It also hosts all the distribution packages for the Linux on IBM System z systems The functions available are the same as that available Infrastructure Solutions Building a Smart Bank Operating Environment under Windows or Linux on Intel The Tivoli Enterprise Portal Server does not support any high availability functions The entire Linux on IBM System z image is now restarted on another physical system with the same addresses presented to the outside consumers This means that after restarting the Linux on IBM System z image the connected user can continue to work without having to log in again when the system is moving The Tivoli Enterprise Portal Server gives the impression of not being reachable After initialization the communication is reinstated automatically Remote Tivoli Enterprise Management Server The Linux on IBM System z also gets its own Tivoli Enterprise Management Server Remote that serves as the primary and only Tivoli Enterprise Management Server for all Linux on IBM System z based agents It also hosts
182. ailed with the primary Tivoli Enterprise Monitoring Server Refer to 2 2 6 Failover support on page 91 for details about the heartbeat behavior and the setup The heartbeat mechanism is used to monitor the status of the remote monitoring servers and the monitoring agents Each Tivoli Enterprise Monitoring Server expects a heartbeat timestamp from the agents every 10 minutes default value If no heartbeat is received in this time range it concludes that the agent is offline Figure 2 33 depicts the heartbeat behavior TEMS heartbeat status is maintained on the HUB TEMS TEMS generates the heartbeat i OS Agent TEMS Q TTN TEMS Application Agent gent heartbeat status IS maintained on the HUB TEMS 5 jote TEMS communicates Only heartbeat status change Remote TEMS receives the heartbeat request from the agent ents pi pi Universal Agent Figure 2 33 IBM Tivoli Monitoring heartbeat behavior Chapter 2 IT environment of the Smart Bank showcase 91 The main features of the heartbeat are gt Default heartbeat frequency for agents is 10 minutes gt Default heartbeat frequency for Tivoli Enterprise Monitoring Server is 3 minutes gt Heartbeat frequency must be set in the agent and in the Tivoli Enterprise Monitoring Server If no heartbeat interval is set the default value is used gt Agents communicate the heartbeat interval during the initial heartbeat request sent to the Tivo
183. ainer_banode1_bas011 bpecontainer jarProcessContainer MDB i APL_SOAEAR APL_SOASHEJB jar Hello Web App tcl ote APL_SOAEAR APL_SOAEJB javTRFProcessBean EJB Containers APL_SOAEAR APL_SOAEJB javNAProcessBean APL_SOAEAR APL_SOAEJB javCALProcessSBean APL_SOAEAR APL_SOAEJB jan BIProcessBean DB Connection Pools J2EE Connector Con jj D gt 0 10 20 30 40 50 60 70 Invocations Physical e Java Beans Bean Sern Times Bean Objects Times Bean Objects Average Method Average Numbe Name activations Loads Stores Were eee Were estived Z ENOTE Time Active Bean Insta APL_SOAEAR APL_SOAEJB jariCQDProcessBean 0 0 309 684 0 000 a APL_SOAEAR APL_SOAEJB jar TRFProcessBean 0 0 276 102 0 000 APL_SOAEAR APL_SOAEJB jar NAProcessBean 0 0 252 500 0 000 APL_SOAEAR APL_SOAEJB jar BPProcessBean 0 0 183 700 0 000 APL_SOAEAR APL_SOAMdbEJB jar BPDUpdateMdb 0 0 91 955 APL_SOAEAR APL_SOAMbEJB jar BDWUpdatemadb 0 0 79 776 BPEContainer_banode1_basr011 compensate_ejb jar Contex 0 0 0 0 0 0 000 BPEContainer_banode1_basr011 compensate_ejb jar Coordi 0 0 0 0 0 0 000 BPEContainer_banode1_basr011 compensate_ejb jar Standa 0 0 0 0 0 0 000 BPEContainer_banode1_basr011 compensate_ejb jar Comp 0 0 0 1 000 BPEContainer_banode1_basr011 compensate_ejb jar Contex 0 0 0 0 000 BPEContainer_banode1_basr011 compensate_ejb jar Standa 0 0 0 0 000 RPFCnn
184. al Q TEMS Tivoli Enterprise Management Server ITM IBM Tivoli Monitoring ti IBM OM Agent IBM OM Agent Windows E Hub Time Wed 03 22 2006 03 19 PM Server Available Systems Management 9 212 128 31 SYSADMIN Figure 4 71 The Tivoli Systems Management workspace Chapter 4 Customizing the Logical views 251 If from the Operations workspace Figure 4 70 a user chooses the Network link a new workspace opens Figure 4 72 a Network 9 212 128 31 SYSADMIN aax Fie Edt View Help CEA Saian nE a a LA E E n r E EO Smart Bank showcase Network View FII Remote HTTP response time manx POAN RX oa Fe no Sten System z9 109 Remote HTTP response time CISCO 6509 Switch Fast Ethernet BI C Curent Response Time i adeCenter 8627 p Gigabit Ethernet H Maximum Response Time M Average Response Time z lt j zs Ei 6000 76 oon MANAGEQ NODES az Link to Managed Nodes 5000 z OS LPAR1 Linux WAS a ba0t won EA HETE blade ame Sena PE aena da ZOS LPAR2 G blade2 Linux WAS 2 vipa OQ 8 3000 kra fear i ba02 RES blades Linux WAS Cimas z Linux HTTP r ND 2000 Q 6 blade7 Inx4 blade3 nx1 ii Linux WAS Windows AIX Siebel 1000 TEMS Remote O tnx Q blade6 Linux WAS bladet1 Windows z ND TEPS 5 Ed Inx blades a 2 7 i
185. al Agent can manage several types of monitoring functions files snmp and so on Based on these recommendations our environment has the following capacity limit gt Maximum number of agents for the distributed environment two Tivoli Enterprise Monitoring Servers Remote 2 x 500 gt Maximum number of agents for the z OS environment two Tivoli Enterprise Monitoring Servers Remote 2 x 500 Two Tivoli Enterprise Monitoring Servers Remote are implemented in the distributed environment to enable a failover solution in case one Tivoli Enterprise Monitoring Server Remote fails Therefore the maximum number of agents for the distributed environment must be limited to 500 However for a larger environment we recommend that you dedicate only one Tivoli Enterprise Monitoring Server Remote for failover This Tivoli Enterprise Monitoring Server does not manage any agent during normal condition For more information about IBM Tivoli Monitoring environment sizing refer to Deployment Guide Series IBM Tivoli Monitoring 6 1 SG24 7188 90 Infrastructure Solutions Building a Smart Bank Operating Environment 2 2 6 Failover support The global availability depends on the availability of the Hub and the availability of the agents gt IBM Tivoli Monitoring provides a hot standby feature to enable the continuous availability of the Tivoli Enterprise Monitoring Server Hub However in our environment the failover of the Tivoli Enterprise Mon
186. alytical database of choice Batch workload A simulation of a typical I O intensive batch workload against the same operational core system database that characterizes the banking environment Reduce time to market Leveraging information insight development tools and an SOA Reusing of solutions assets where possible Chapter 1 Introducing the technical architecture of the Smart Bank showcase 15 1 2 4 Nonfunctional requirements What qualities of service do we expect for our infrastructure and solution Table 1 8 describes the most common nonfunctional requirements Table 1 8 Nonfunctional requirements Nonfunctional Description requirement Provide systems Creating a Logical view of the infrastructure to monitor and managing management and the infrastructure in as automated a manner as possible monitoring for the enterprise Workload Maintaining the quality of service across the channels and critical management to business business processes to ensure client satisfaction and rapid goals response to business goals Near real time update Using the infrastructure to create a near real time update of the analytical database to provide more up to date information for business analysts and risk reporting Straight through Real time processing of and response to online channel transactions processing and operations Business continuity Providing for a highly available and resilient platform and being able to demonstrate this Pr
187. an initial view of how this will look when we try and monitor all the subsystems LPARs and processors running on an IBM System z9 109 In workspace A we see the CPU utilization for the application owning z OS LPARs The blue bar shows the ZAAP utilization with its Java workloads in our production environment This is used to provide details about the actual CPU utilization during a demonstration when more Java intensive workloads are run Workspaces B C D and E show the breakdown of that CPU by some of the key subsystems running the application load 278 Infrastructure Solutions Building a Smart Bank Operating Environment Workspace B shows the Terminal Owning region and Application Owning region for our ClCSplex We instrumented the queries so that only those subsystems with activity are shown Workspace C shows the WebSphere MQ activity showing the Queue Manager task File Edit View Help gt AEHBReaale TEELT Gov SQHRSAaGE System 29 109 utilisation mo x wy zosceucrars A manx BOOMER X GS Split horizontally a a System 29 109 Dlaverage CPU Percent M Average IFA Percent E Physical CPU Count 8 Enterprise view Operation view CICSRT11 Integrated Coupling 3 Parallel CICSRAIS Ocpu Percent Facility ICFs Sysplex CICSRA14 IFA Percent CICSRT10 z Application Assist Java workloads Processor zAAPs or IFAs for z OS LPARs aen WebSphere MQ
188. and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries 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 viii Infrastructure Solutions Building a Smart Bank Operating Environment Preface All organizations will eventually face the necessity to refresh ageing technology IBM infrastructure solutions are a combination of hardware software services and solutions designed to get the most out of the resources and help move from the existing technology to a new technology without throwing away the existing investments IBM infrastructure solutions simplify the IT infrastructure of businesses and enhance business continuity and systems management through the following features gt Ensuring better utilization When faced with an expanding workload clients may invest in additional hardware although all they may have to do is obtain information about how to get more out of their existing assets gt Aiding effective management Having a wealth of IT resources is one thing being able to monitor manage and allocate virtual resources and physical resources to dynamically address the business requirements is another gt Promoti
189. ans that we keep in mind the fact that any component may fail at any time and be prepared for this If a server or its connection to the network is lost an alternative must be available In our Smart Bank project we assume that if a software component fails it can be restarted If this does not happen we conclude that the server is lost completely 32 Infrastructure Solutions Building a Smart Bank Operating Environment The following guidelines have therefore been put in place for the subsequent alternatives gt The Tivoli Enterprise Management Server Hub must be able to recover in 10 minutes or less gt On each of the systems where a Tivoli Enterprise Management Server Remote resides the installed agents report directly to that server They do not have a second path to another Tivoli Enterprise Management Server As mentioned earlier if we cannot restart the entire system is lost gt Each agent on a Windows or Linux on POWER platform connects to the two Remote Tivoli Enterprise Management Servers located on Windows and on AIX The Windows agents use the Windows based Tivoli Enterprise Management Server Remote as their primary Tivoli Enterprise Management Server Allthe others agents use the AlX based Tivoli Enterprise Management Server Remote as their primary Tivoli Enterprise Management Server This algorithm ensures workload balancing across our two Remote Tivoli Enterprise Management Servers Note In high sca
190. aphic Enter new channels depth Traditional tH Market Channel gt New Figure 1 3 Strategies for innovative growth The future trends forecast by IBM GBS builds on the current trends and strategies that are seen in the marketplace Both the future and the current trends provide the direction for the Smart Bank proof points 1 1 5 The way the IBM Financial Services Sector addresses these issues At the inception of the project we wanted to take clients through a set of business scenarios they would recognize and realize as being strategic for their business We called these proof points because we wanted to demonstrate how IBM architectural concepts products and techniques address these business problems and provide business value to the client We use the business trends and issues described earlier to reinforce the message of what we are providing and why we are providing the same The Financial Services Sector has developed a comprehensive architecture and framework to address these issues Although this project is clearly focused on infrastructure the application layer must also be able to deliver on many of the key business proof points 8 Infrastructure Solutions Building a Smart Bank Operating Environment A distinction is made between business solutions and infrastructure solutions which can be mapped broadly against the service offerings from GBS for the business solutions and the IBM Global Technolog
191. application support Installation ends gt Adding application support for distributed applications on Tivoli Enterprise Portal Server As explained in IBM Tivoli Enterprise Monitoring Server Hub on page 107 Tivoli Enterprise Portal Server must be similar to the Tivoli Enterprise Monitoring Server Remote updated with the application support ODI files only to interact with the Tivoli OMEGAMON XE agents used for the distributed applications The installation process on the Tivoli Enterprise Portal Server is similar to the one used for the distributed application support described earlier in IBM Tivoli Enterprise Monitoring Server Hub on page 107 After the previous installation process is complete it is essential to update the Tivoli Enterprise Monitoring Server Hub catalogs and attributes running on z OS used for the Tivoli OMEGAMON XE agents Without this update the information related to these agents is not available in the Tivoli Enterprise Portal workspaces Infrastructure Solutions Building a Smart Bank Operating Environment Perform this operation from the Tivoli Enterprise Portal Server a Launch the Manage Tivoli Monitoring Services program and right click Tivoli Enterprise Portal Server Utilities FTP Catalog and Attribute Files as shown in Figure 2 43 Manage Tivoli Enterprise Monitoring Services TEMS Mode Local Computer Actions Options View Windows Help Zizie 2 al 2
192. ar resource Controls the security of the monitoring solution Each enterprise monitoring solution must contain one Tivoli Enterprise Monitoring Server Hub and can include multiple Tivoli Enterprise Monitoring Server Remotes which are used to scale large installations Tivoli Enterprise Monitoring Server Remote collects data from the agent and forwards it to the hub monitoring server Tivoli Enterprise Monitoring Server Hub correlates the monitoring data collected by the agents and the remote servers and passes it to the Tivoli Enterprise Portal Server for presentation and evaluation Tivoli Enterprise Portal Server functions as a repository for all the user data such as the user IDs and user access control for the monitoring data meaning the data each user can access and how it is displayed It connects to the Tivoli Enterprise Monitoring Server Hub and can be accessed by the Tivoli Enterprise Portal clients It provides a consistent look and feel for the users The database to store Tivoli Enterprise Portal server information is the DB2 Universal Database UDB The Structured Query Language SQL server is also supported Tivoli Enterprise Portal provides a single point of control for managing the resources that the applications rely on including a range of operating systems servers databases platforms and Web components Tivoli Enterprise Monitoring Agent The agents are the data collectors The agents monitor systems s
193. ards to access the data Open Database Connectivity gt We could use the central analytical database that we chose based on its use of the key retail banking model Information FrameWork Near real time update of analytical database Our GBS colleagues at IBM identified early on in the project that retail banks are striving for more up to date information feeds into their analytical databases for businesses to make more informed decisions based on near real time information Some analysis such as fraud detection and money laundering must be computed real time with special mechanisms put Chapter 1 Introducing the technical architecture of the Smart Bank showcase 19 in place Other forms of analysis such as the credit risk analysis that is discussed in the proof point Risk and compliance on page 21 do not require up to date information because they are primarily historical in nature However most other forms of business analytics benefit from increased real time data feeds There are many possible methods of achieving this We chose two from a demonstration point of view They are gt CICS Business Event Publisher gt WBISF and the SOA model Both use the asynchronous update mechanism afforded by WebSphere MQ To ensure a minimal impact on the quality of service response time that our clients channels experience we chose an asynchronous update mechanism to collect the information and quickly register the update to the banki
194. are read from the disk or are being modified The purpose of the buffer pool is to improve system performance Data can be accessed much faster from memory than from disk Therefore the fewer the number of times the database manager has to read from or write to a disk I O the better the performance Each table space is associated with a Infrastructure Solutions Building a Smart Bank Operating Environment specific buffer pool The default buffer pool IBMDEFAULTBP is used by Tivoli Enterprise Portal Server By increasing the default value the number of logical access is high when compared to the number of physical access direct disk I O Therefore there is a low frequency of disk I O Table 2 5 provides the buffer pool size defined for the Tivoli Enterprise Portal Server database Table 2 5 DB2 Buffer pool value for the Tivoli Enterprise Portal Server Table space Buffer pool Number of Page size KB Memory usage pages MB USERSPACE1 IBMDEFAULTBP 15000 eee Note The default value for the IBMDEFAULTBP buffer pool is as follows gt 250 on Windows gt 1000 on UNIX In order to increase the buffer pool size from the DB2 command prompt perform the following tasks gt Connect DB2 to the Tivoli Enterprise Portal Server gt Change the IBMDEFAULTBP parameter to 15000 2 2 9 Installing the monitoring servers In our case the basic installation process of the Tivoli Enterprise Monitoring Server remote and Tivoli Enterp
195. art Bank showcase 29 109 c D oO Ss fe wn A Firewall Cluster WebSphere _ Application Serve Cluster Network Deployment HTTP Server Virtual Network z VM LPARs Linux Guests 2rSockets PR SM Parallel Sysplex aa BladeCenter Tivoli Enterprise i L Branch servers gt Business Portal gt Siebel Analytics OMEGAMON gt WebSphere Application Infrastructure Intel Linux Power 4 AIX Management Virtual Network EE EE Figure 1 7 Architecture overview Physical view In the architecture diagrams we called the integration techniques protocols and mechanisms used in the project as the ntegration Hub This uses many of the components such as WebSphere MQ that form the basis of the Enterprise Service Bus ESB and are available as a physical implementation with WebSphere V6 which we had not installed at this stage of the Smart Bank showcase 1 3 2 Systems management requirements The showcase requirements for systems management are listed here gt The Smart Bank project requires an Enterprise view of its systems across different platforms for it to monitor and manage the system using one point of control gt Aligning the business goals setup with the IT infrastructure using WLM and IBM Tivoli Monitoring V6 to monitor the quality of service that is delivered to our clients business units and partners gt As per the
196. artitioned HDAM PHDAM hierarchical indexed direct access method HIDAM partitioned HIDAM PHIDAM and data entry database DEDB The connector determines whether a rule matches a particular event based on the selection criteria you have provided When it finds a matching rule the connector creates a message based on the message layout properties contained in the rule It then passes the message and other rule properties to the message server through a highly efficient cross memory interface for subsequent delivery to an MQSeries message queue CICS Business Event Publisher for MQSeries event connectors anticipate the possibility that an event may fit multiple rules Any or all the properties of the rules such as message destination or message construction can differ from one rule to the next A rule can also specify various MQSeries MQPUT options that are to be used with the message written to the MQSeries message queue for you to extend applications in numerous ways without changing the code CICS Business Event Publisher for MQSeries message server The CICS Business Event Publisher for MQSeries message server uses attributes associated with a selected event along with the rule you provide to send a message created by the CICS Business Event Publisher event connector to the appropriate MQSeries message queue While maintaining the integrity of the associated unit of work the message server supports the use of multiple subtasks to proces
197. ary files Example 2 11 shows a partial output of the kwe xml file with the variables that you require to initialize based on your WebSphere V6 0 environment Example 2 11 kwe xml partial output lt xml version 1 0 encoding UTF 8 gt lt KWEAGENT VERSION 130 Agent ID AppSrv41 WebSphere Application ServerInstanceRoot opt IBM WebSphere AppServer profiles AppSrv41 WebSphere Application ServerAppServerRoot opt IBM WebSphere AppServer gt lt KWEAGENT gt 7 Restart the agent with the following command lt CANDLEHOME gt CandleAgent start we 8 View the log files located in the directory lt CANDLEHOME gt logs in order to verify whether the agent has started well without any error Setting instrumentation levels to collect Performance Monitoring Infrastructure data The Performance Monitoring Infrastructure PMI application programming interface API extracts WebSphere Application Server performance data The following Tivoli Enterprise Portal workspaces require the PMI gt DB connection pools gt Web applications gt Serviet JavaServer Pages JSP Chapter 2 IT environment of the Smart Bank showcase 111 vvvvvvvvvvvy Serviet JSPs for the selected Web application Enterprise JavaBeans EJB containers Container transactions Container object pools Enterprise JavaBeans Enterprise JavaBeans methods for the selected bean Java 2 Platform Enterprise Edition J2EE connector connection poo
198. asic installation process of the Tivoli Enterprise Monitoring Server Hub does not require any specific process other than those described in BM Tivoli Monitoring Installation and Setup Guide GC32 9407 IBM Tivoli Enterprise Monitoring Server Hub This section describes the miscellaneous tasks involved in customizing the Tivoli Enterprise Monitoring Server Hub in order to address the requirements of our environment Following are the tasks gt Defining the network interface to communicate with Tivoli Enterprise Monitoring Server Remote After completing the basic installation because the Tivoli Enterprise Monitoring Server Hub has several NICs it is necessary to specify the one used by IBM Tivoli Monitoring Refer to Multiple network interface cards on page 89 for details Chapter 2 IT environment of the Smart Bank showcase 107 gt Adding the application support for z OS on the Tivoli Enterprise Monitoring Server Hub After completing the installation of the Tivoli Enterprise Monitoring Server Hub in order to be able to manage the agents running on z OS run the application support as described in IBM Tivoli Enterprise Monitoring Server Hub on page 107 However specify only the task of installing the application support catalog and attribute files on the Tivoli Enterprise Monitoring Server Hub as shown Figure 2 46 i 4 Installer of x Select which Tivoli Monitoring components you would KSN like to add applicati
199. ation Event Console BAD amp amp amp X O Total Events 14 item Filter Enterprise Situation Name Display Item Source Inv as Syster K83_LCU_Cont_Rate_Waming TIVSREMT BA02 STORAGE EH Logical Conta ga Linux Systems i K83_Vol_Fragment_Index_Warning TIVSREMT BAQ2 STORAGE GH SMS Storage Ef Windows Systems K83_Vol_Free_Space_Pct_Waming TIVSREMT BAQ2 STORAGE GY SMS Storage f 2 05 Systems K83_Vol_Free_Space_Pct_Warning TIVSREMT BAQ1 STORAGE S SMS Storage CJ Open NT_System_Total_Interrupts Primary BLADE1 2 NT E Processor h LO KOZ SYSPLEX_TEST BAPLEX MVS SYSPLEX EH XCF Groups Open MQSeries_Queue_Manager_Problem CS01 BA02 MQESA S Queue Mana Open M Series_Queue_Manager_Problem WJMA BA02 MQESA E Queue Mana 1 Open Crypto_Internal_Error BAPLEX BA02 MYSSYS m Cryptographi CJ Open KS3_LCU_Av_Delay_ Q_Critical TIVSREMT BA02 STORAGE 2 Logical Cont cal EJ Open KS3_Vol_Fragment_Index_Critical TIVSREMT BA02 STORAGE EK SMS Storage DJ Open MQSeries_Queue_Manager_Problem CSQ2 BA01 MQESA EH Queue Mana MQSeries_Queue_Manager_Problem WJMA BA01 MOESA EK Queue Mana Pwned Nodes a Penne RAR AR and AA Po nont 2 Physical Open Situation Counts Last 24 Hours B Name Display Item Origin Noc NT_System_Total_Interrupts Primary BLADE1 2 1 Z KS3_LCU_Av_Delay_Q_Critical TIVSREMT BA02 5 SYSPLEX_TEST KS3_LCU_Cont_Rate_Warnina TIVSREMT BA02 S NT_System_Total_I
200. ation if an existing situation is selected or delete a selected situation Note In a Logical view the management of situations creating deleting and modifying is performed the same way as the management of situations in a Physical view 4 3 2 Associating and dissociating a situation To associate or dissociate a situation perform the following tasks 1 As specified earlier open the Situations for window All the situations defined for the managed system associated with that level appear Right click the situation you want to associate to Attention In the Situations for window all the defined situations are displayed All of them are not set up to run at startup or distributed the way you want them We recommend that you double check a situation s state before creating the association 2 Anew menu is displayed Figure 4 12 Click the Associate option To terminate the association click OK when the button is displayed OAao x Smart_Bank My Teller n ATM 2 Al ATM Channel Situations for ATM Authentification Mig Banking ee fe Formula Distribution 1P Expert Advice 7 Action G Until a m acs am EJ Web Services Management Agent Description B zBank GDPS HyperSwap amp MessageArrivalClearing lebSphere Web Application Error MessageArrivalCritical WebSphere Application Servers for create New create Another Sta
201. ault Port number gt 1918 Enter Next Fl Help F3 Back COMMAND gt Figure 2 12 ICAT Run time environment configuration screen Chapter 2 IT environment of the Smart Bank showcase 67 If the Use z OS system variables field is set to Y a utility is necessary to create the system variables parameter member for the selected run time environment To create the system variables member select Z in the Runtime Environment screen as shown in Figure 2 13 RUNTIME ENVIRONMENTS RTEs Actions A Add RTE B Build libraries C Configure L Load all product libraries after SMP E D Delete U Update V View values Z Utilities Action Name Type Sharing Description BASE BASE RTE BASE for TIVOLI Smart Bank Sysplex BAPLEX BAO1 SHARING BASE RTE SHARE for TIVOLI Smart Bank LPAR BAO1 BAO2 SHARING BASE RTE SHARE for TIVOLI Smart Bank LPAR BA02 HUB SHARING BASE RTE SHARE for moveable HUB Smart Bank Enter Next Fl Help F3 Back F7 Up F8 Down COMMAND gt Figure 2 13 ICAT Run time environment screen A new screen Figure 2 14 is displayed Select 2 in the command area and then submit the generated job Specify the number of the desired utility 1 Create batch mode parameters 2 Create System Variable parameter member Create System Variable VTAM major node rename job Create VTAM major node one node for all products Generate sample transport JCL 6 Generate sample system procedure copy JCL 7 Generate sample system VTAM
202. book or other IBM Redbooks in one of the following ways gt Use the online Contact us review IBM Redbook form found at ibm com redbooks gt Send your comments in an e mail to redbook us i bm com gt Mail your comments to IBM Corporation International Technical Support Organization Dept HYJ HYJ Mail Station P099 2455 South Road Poughkeepsie NY 12601 5400 Infrastructure Solutions Building a Smart Bank Operating Environment Introducing the technical architecture of the Smart Bank showcase This chapter describes the key business drivers for the Smart Bank showcase the features we wanted to showcase and how we used the IBM Tivoli infrastructure and application monitoring for delivering the solution This chapter also discusses the showcase proof points in the context of IBM infrastructure and business solutions As part of this discussion this chapter discusses the key architectural decisions and components involved in the Smart Bank showcase because these form the basis of the elements to be monitored Copyright IBM Corp 2006 All rights reserved 1 1 1 Understanding the Smart Bank showcase The official name of the project is Building a Smart Bank Operating Environment For ease of use we substitute this with Smart Bank showcase in this book The title of this IBM Redbook starts with the phrase infrastructure solutions In fact the Smart Bank showcase was initiated and designed before IBM started the inf
203. c Inthe window that opens Figure 2 44 specify the target the privileged z OS account password and the Data Set Name FTP TEMS data to z OS x See the 2 05 TEMS configuration guide for information on how to use this feature Host Name Address foira User ID Tso Password e DSN TIV HUB RKANDATM Cancel Figure 2 44 FTP of the Tivoli Enterprise Monitoring Server to the z OS parameters d In the window that opens Figure 2 45 click No to update only the new attribute and catalog files Manage Tivoli Enterprise Monitoring Services Q The following files already exist on the host wy KCGATR KCPATR KDPATR KLZATR KMSATR KMQATR KN3ATR KNTATR KOEATR KS3ATR KSDATR KSYATR KULATR KUMATR KUXATR KWOATR KWWATR KCGCAT KCPCAT KDPCAT KL2CAT KMSCAT KMQCAT KN3CAT KNTCAT KOECAT KS3CAT KSDCAT KSYCAT KULCAT KUMCAT KUXCAT KWOCAT KWWCAT The Following files are new kweatr kwecat Files should not be replaced unless instructed by the Readme or IBM Global Services Select Yes to overwrite the files anyway select No to copy only new files Cancel to end copy No Cancel Figure 2 45 Confirmation of the FTP e When the transfer is complete refresh the Tivoli Enterprise Monitoring Server Hub In our case with the Hub running on z OS and the environment provided by Tivoli Enterprise Monitoring Server a manual seeding operation to get the proper information into the Hub is required This invol
204. cation LocalTimeStamp BytesReceived BytesSend A ServiceStatus Request RequestParameters 10 1 1 147 03 16 06 16 05 24 o 0 400 ifssicashDeposit do a Eih m 10 1 1 147 03 16 06 16 05 24 o 0 400 ifssicashDeposit do Piha ma 10 1 1 147 03 16 06 16 05 24 o o 400 ifssicashDeposit do re Linux OS 10 1 1 131 03 20 06 17 18 54 20717 0 404 iss Eb Universal Agent 10 1 1 147 03 1 6 06 17 07 27 631 0 500 fssicashDeposit da Ginx stBMHTTPOO 10 1 1 147 03 16 06 17 07 29 631 Q 500 ss balancelnquiry do E CEPTON DETAIL 10 1 1 147 03 16 06 17 07 30 631 0 500 fss balancelnguiry do HIST_BROWSER_STAT 10 1 1 147 03 16 06 17 07 31 631 0 500 ifssibalancelnquiry do HIST_CLIENT_PLATFORM_STAT 10 11 147 03 16 06 17 07 31 631631 o 500 fssicashDeposit do HIST_HTTP_STAT 10 1 1 147 03 16 06 17 07 32 631 0 500 ifssicashDeposit do HIST_REFERRAL_BY_LOCATION 10 11 147 03 16 06 17 07 32 631 o 500 ifssicashDeposit do HIST_REFERRAL_STAT 10 1 1 147 03 16 06 17 07 32 631 0 500 fssicashDeposit do HST_REQUEST_BY_LOCATION 10 11147 03 16 06 17 07 35 631 o 500 fssicashDeposit do 10 11 147 03 16 06 17 07 39 631 o 500 ifssicashDeposit do HIST_STATUS_BY_REQUEST 10 1 1 147 03 16 06 17 07 41 631 0 500 ifssicashDeposit do HST_STATUS_STAT 10 1 1 147 03 16 06 17 07 41 631 0 500 ifssicashDeposit do HIST_TRANSFER_BY_LOCATION 10 1 1147 03 16 06 17 07 41 631 o 500 fssicashDeposit do HIST_TRANSFER_BY_REQUEST 10 1 1147 03 16 06 17 07 42 631 0 500 fs
205. commonality of operating system across different platforms can be achieved With open standards being adopted increasingly the deployment choices for applications are based more on the quality of service required for business function rather than hardware and software limitations We then arrived at a balance between the cost and the quality of service We therefore chose z VM as our client example as did our client s model based largely on the requirement of reducing cost and increasing simplification The z VM environment however delivers many other key services The other deployment platform for our branch server application is the BladeCenter which was also chosen for the infrastructure simplification qualities that it provides The IBM BladeCenter An IBM BladeCenter is a high density stack of servers that enables you to concentrate physical servers blades together In the Smart Bank project we concentrated 14 servers together 12 Intel and 2 POWER4 blades In the distributed world most times one server is dedicated to one application thus isolating the environment Following are some of the reasons for this gt Facilitate troubleshooting gt Performance of the application gt Operating system compatibility with the application 280 Infrastructure Solutions Building a Smart Bank Operating Environment The individual blade addresses these requirements and concentrates the physical implementation The BladeCenter helps en
206. connection gt To extensively monitor Enterprise JavaBeans EJB based on statistic measurement methods Report activity levels for each EJB container defined in each application server Report activity levels for the enterprise bean object pools associated with enterprise beans Collect and report statistics on EJB transactions Report activity levels for individual enterprise beans including method invocation data Chapter 3 Using Physical views 139 gt To get detailed statistical reports on Web application for each application server engine Using Servlets and Java Server Pages JSP Hypertext Transfer Protocol HTTP sessions OMEGAMON WebSphere Application Server users typically target the monitoring of the application server environment in the production environment The monitoring expenses are low Therefore the costs involved in getting this information is low This section describes only the most important features of OMEGAMON for WebSphere Application Server for the Smart Bank showcase Not all the workspaces are shown The window captures are taken from the z OS system BAO1 The OMEGAMON WebSphere top entry workspace The workspace shown in Figure 3 15 is the default workspace gt In area 1 shown in this figure all the active WebSphere Application Server regions of the system in which the agent is running are displayed including the WebSphere Application Server Deployment Manager and the Node Ma
207. ction_Anal ADLCICSRAIO CCC Transaction Analysis BAO1 CICSRA11 E CicSplex_Transaction_Appli Ban CICSRA14 CiCSplex_Transaction_Defiry pan CICSRT10 e CiCSplex_Transaction_Detei paon CPSMCMO1 a CiCSplex_Transaction_EIB_ BAO2 CICSRA12 hg Wy CicSplex_Transaction_EIB_S amp BY cicSplex_Transaction_File_ Available Managed System Lists a E cicSplex_Transaction_l O_ MYS_CICS E cicSplex_Transaction_Mane 8 HubT a Dy CicSplex_Transaction_Reme Figure 4 10 Adding views with the explicitly managed system 4 3 Assigning situations to a Logical view Situations can be managed at each level of the new Logical view tree When the Logical view is used it is possible to perform the following tasks Create a new situation Delete an existing situation Associate a situation Dissociate a situation vvvy Note If you build a new Logical view using a part of the other existing views situations may already be assigned to the new Logical view Chapter 4 Customizing the Logical views 193 You may create new situations and associate them to any level of the Logical view There is no necessity to attach or create these situations under the physical tree Note Because of these specific associations a logical tree may display and react differently from a physical tree The same rule applies if a part of the physical tree has been copied into the Logical view tree 4 3 1 Creating and deleting a situation 194 To
208. d is a solution that supports both these requirements and links them both neatly To fulfill the Smart Bank showcase requirements we select several products from the Tivoli portfolio After selecting the products the different alternatives are discussed pin pointing to the following gt The products selected The components involved The relationship between various products The communication paths Chapter 1 Introducing the technical architecture of the Smart Bank showcase 23 gt The architectural reflection High availability Embedding in existing environments Virtualization In order to make the different alternatives visible the Tivoli product components that are to be picked how they fit together and the platforms on which they are supported are discussed first This is followed by a discussion of different solutions introducing the idea of virtualizing the Tivoli Enterprise Portal Server The different approaches are then compared 1 4 1 Products selected from the Tivoli portfolio The project uses two main products from the Tivoli portfolio gt IBM Tivoli Monitoring V6 This is the new IBM Tivoli Monitoring solution released in October 2005 It offers a monitoring solution for large numbers of platforms and applications when integrating all the information that is gathered into a common infrastructure The IBM Tivoli Monitoring V6 portal enables the consolidation and presentation from di
209. d product provided us with the necessary risk scoring One of the key principles that was used here was to reuse the existing business intelligence infrastructure We reused the banking data warehouse model to store the data We used our existing Siebel Business Analytics dashboards that also provided a more visual demonstration mechanism as the reporting mechanism We then created an entire range of Basel II and risk analysis reports based on the historical data in our database This allowed us to demonstrate an aspect of credit risk compliance Business continuity and high availability Another aspect of risk and compliance is minimizing operational risk There are many reports under Basel II that cover this area but we focused on the infrastructure and built our operational environment to be resilient and highly available using many of the technologies available to us through IBM System z0 109 including the following gt Geographically Dispersed Parallel Sysplex GDPS HyperSwap for disk resiliency gt Parallel Sysplex for server resiliency gt Sysplex Distributor for workload distribution and high availability gt Virtualization to allow dynamic resource allocation and sharing of resources gt HiperSockets and virtual local area network VLAN for virtualization of the network within the IBM System z9 109 machine gt Workload Manager WLM for intricate workload management on z OS for service level agreements and machine pr
210. d_logio module is not implemented there is no way of feeding the BytesReceived attribute Therefore the l must be replaced with the hardcoded value 0 The BytesSend attribute must get the value returned by b instead of O However the value returned by b and O are not identical The b format string represents only the size of the HTTP response in bytes and not the actual number of bytes sent over the network gt LogFormat directive with the mod_logio module enabled Example 2 12 shows the definition of the LogFormat directive called itmuniagent nickname if the mod_logio module is enabled By default the CustomLog directive for the access_log file uses the nickname common To change the log format output matching the attributes of the Universal Agent meta file the CustomLog directive must use the nickname itmuniagent instead of common Example 2 12 HTTP Server LogFormat and CustomLog directives with the mod_logio module LogFormat h 1 u t Zr gt s b common LogFormat h 1 u t Zr gt s I Referer i gt U User Agent i v q 0 T itmuniagent Do not use the common LogFormat CustomLog logs access log common ITM Universal Agent log format CustomLog logs access_log itmuniagent gt LogFormat directive without the mod_logio module Example 2 13 shows the definition of the LogFormat directive called itmuniagent nickname without the mod_logio module Example 2 13 HTTP Server LogFormat and Cus
211. de a quick overview of SOA activity on this system In the navigation tree individual application servers are found 0X a O po ke O amp Fie Edt View Favorites T Address http 9 212 128 31 1920 cnpykat E EJ Go a Tivoli Enterprise Portal File Edit View Help HHABREAD SOOM SQSWRRSEHAERV STFS View Physical y oa FII Average Response Time by Operation D PIE OMCSACCIVTER nage A F 05 390 Unix LISS A Services Management Agent Message Arrival Ba Services Management Agent Env heners E Performance Summary E Message Summary E Faults Summary il e Storage Subsystem 4 f D E P WebSphere Application Server 05 39 GH BAOLKWWA helloFSS ce Gig BAOZ Gi 2 5 Physical Response Time in Milliseconds m Number of Messages by Operation BS a amp Lull Average Message Size by Operation DS Bs cashWithdraw getPostingListCounter getPostingListAtm helloFSS helloFSS getAccountList deposit cashWWithdraw cashDeposit helloFSS pay C1 aa E AT a a a a aT Se a A E 0 10 20 30 40 50 60 0 100 200 300 400 500 600 Number of Messages Message Size in Bytes CS Hub Time Sa 03 18 2006 11 31 AM J Server Available Application Server Services Management 9 212 128 31 WOLF1 Figure 3 11 The Service Management Environment workspace By default the following key values are displayed gt The average
212. der to be operative the dynamic link function requires the following gt gt Internal symbols to determine whether or not to offer a defined link on that place Queries in the target workspace set up with symbols Association of these symbols with data fields coming from the source workspace Expressions using values functions and operators to build advanced associations if necessary A step by step definition This section describes the definition of an advanced link It is an example that is built by using OMEGAMON XE for z OS Source workspace for dynamic link definition The user displays the Workload Manager WLM definition on the two z OS systems used by the Smart Bank showcase team The workspace called WLM Service Class Resources Workspace is used as a base In our case we defined another one for our own use called WLM All Service Class which is shown in Figure 4 32 2 WLM All Service Class 9 212 128 31 SYSADMIN Lee File Edit View Help gt OUHBACAD SOCO0O SQUBRERERFOveo lt View Emart Bank v max WLM All Service Class Resources information D ang Page 1 of3 a WLM All Service Class Resources information 5 liq Teller Managed Serice Period Goal Goal Goal Goal Duration Average Performance Acti Authentification System Class Type Percentile Importance Value Response Time Index
213. dialog Manual changes to the z OS configuration files are required These changes have to be reinstated after each maintenance For Tivoli Enterprise Portal Server High availability functions and mirroring functions are not supported and the switch in the Hot Standby Tivoli Enterprise Management Server is not recognized A detailed description about the workroom is documented in Getting Started with IBM Tivoli Monitoring 6 1 on Distributed Environments SG24 7143 Remote Tivoli Enterprise Management Server The Windows based Tivoli Enterprise Management Server Remote acts as the Primary Tivoli Enterprise Management Server for all Windows based agents It also hosts all the distribution packages for the Windows systems For Windows based Remote Tivoli Enterprise Management Server it is easy to add a secondary Tivoli Enterprise Management Server Hub statement Thus the support for the Hot Standby configuration of the Tivoli Enterprise Management Server Hub is fully supported IBM Tivoli Monitoring agents On both the systems IBM Tivoli Monitoring agents for monitoring the server software such as the operating system and the DB2 Universal Database will be installed These agents connect to the Windows based Tivoli Enterprise Management Server Remote as their primary server and to the AlX based Tivoli Enterprise Management Server Remote as their secondary server They thus have two ways of reporting to the Hub Tivoli Enterprise
214. dopted a centralized model where the branch servers are physically located on centralized servers in order to help simplify the environment and reduce costs This proof point focuses on horizontally scalable applications deployed in a distributed environment perhaps in a regional hub or in a central server environment The branch transformation proof point also inherits the points from the multichannel transformation point and shows end to end integration across heterogeneous platforms This step involves front office optimization from the business perspective and SOA infrastructure and user platform optimization from the infrastructure perspective gt Rapid product development quicker time to market with SOA After achieving the flexibility accorded by the multichannel architecture we tackled the new programming model and the SOA The key driver for this proof point was rapid development quick time to market of the new business products This development implies the following Leverage the core system functionality by exposing it as a service that is to be used by a business process Build new business processes based on the existing core system functionality and the new functionality created in the new programming model Java 2 Platform Enterprise Edition J2EE Rapid product development leads to a discussion around core systems transformation This step involves SOA infrastructure and IT service mana
215. e SC32 9510 IBM Tivoli Composite Application Manager for Response Time Tracking V6 0 Installation and Configuration Guide GC32 9482 IBM Tivoli Composite Application Manager for WebSphere Installation and Customization Guide GC32 9506 IBM Tivoli Composite Application Manager for WebSphere Operator s Guide SC32 9508 IBM Tivoli Monitoring Installation and Setup Guide GC32 9407 IBM Tivoli Monitoring Agent User s Guide SC32 9459 Online resources The soft copy of these publications can be downloaded from the following Web site http www 306 ibm com software tivoli library The IBM Publications Center http www ibm com shop publications order For current information about IBM Tivoli software education visit the IBM Tivoli software education Web page at http www 3 ibm com software tivoli education Copyright IBM Corp 2006 All rights reserved 285 The current schedule of information about IBM Tivoli training is available on the IBM Tivoli software education schedules Web page at http www 3 ibm com software tivoli education schedules The following Web sites and URLs are also relevant as further sources of information gt Detailed information about Distributed Monitoring and OMEGAMON http www 306 ibm com software tivoli sw atoz indexM htm gt Details pertaining to Request for Comments RFC error codes http rfc net rfc2616 html gt IBM Tivoli Open Process Automation Library http www 18 lotus com
216. e it automatically generates new tables There are no pre existing tables for any application with the exception of two tables that Tivoli Data Warehouse generates to collect information regarding the data being exported from other applications The data collection is initiated by the Tivoli Data Warehouse agent directly with the product specific agent Tivoli Enterprise Management Agent for Windows UNIX and so on The behavior of historical data collection is controlled by the Tivoli Enterprise Portal Server that stores the following parameters for the Tivoli Monitoring Agent for Data Warehousing in the Tivoli Enterprise Managing Server The attribute groups to be collected The frequency at which to collect data The place where this data is to be stored temporarily The periodicity at which to transfer the temporary data to the Tivoli Data Warehouse vvvy 28 Infrastructure Solutions Building a Smart Bank Operating Environment The Summarization and Pruning Agent is responsible for maintaining the warehouse functions inside the database in order to perform the required aggregation summarization and pruning steps Through Tivoli Enterprise Portal Server the following settings are applied gt The period for which raw data is to be retained gt Decision about creating hourly daily monthly quarterly and or yearly reports gt The timeframe for which these generated reports are to be maintained The Summarization and Pruning Agent e
217. e 4 70 The Smart Bank operations workspace This workspace has one view a graphic one Following are some of the features of this workspace gt An enterprise link is offered in this view A user has the choice to go to the Enterprise view from this point The user does not have to return back gt Extra choices are added This includes for example an examination of the network or the IBM System z usage and so on that is much more physical data pertaining to the Smart Bank application components gt Icons with nolabel corresponding style used on the graphic These labels are integrated as part of the graphic gt An extra part called Systems Management This is information pertaining to how the different Tivoli components actually measure the infrastructure Adding a workspace that displays the status of the different supervision products is a good idea At any time the Smart Bank team can see if any of the agents is falling or if one of the platforms on which a Tivoli key component resides is facing problems The Enterprise status 250 Infrastructure Solutions Building a Smart Bank Operating Environment and the Tivoli monitoring status are displayed on only one terminal Figure 4 71 where the Windows station on which the Tivoli Enterprise Portal Server resides is facing a problem Fie Edt View Help 9 f le Windows TEPS Tivoli Enterprise Port
218. e CPU but by the available memory that may cause response time problems 5 3 3 Summary With the branch server Logical views we leveraged the capabilities of IBM Tivoli Monitoring V6 to monitor and manage the heterogeneous environment In the context of the Smart Bank showcase we showed our IT simplification strategy at work and the overall monitoring capability with regard to our enterprise 284 Infrastructure Solutions Building a Smart Bank Operating Environment Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this IBM Redbook IBM Redbooks For information about ordering these publications see How to get IBM Redbooks on page 286 Note that some of the documents referenced here may be available in soft copy only gt gt gt Deployment Guide Series IBM Tivoli Monitoring 6 1 SG24 7188 Getting Started with IBM Tivoli Monitoring 6 1 on Distributed Environments SG24 7143 IBM Tivoli Composite Application Manager V6 0 Family Installation Configuration and Basic Usage SG24 7151 IBM Tivoli OMEGAMON XE V3 1 0 Deep Dive on z OS SG24 7155 Other publications The following publications are also relevant as further sources of information gt gt CICS Business Event Publisher for MQSeries V1 2 Getting Started GC34 6296 002 IBM Tivoli Composite Application Manager for CICS Transactions Product Guid
219. e informed earlier on a two level escalation in severity is implemented A warning event is raised when 70 of the queue is full and a critical event is raised if 85 of the queue is full Infrastructure Solutions Building a Smart Bank Operating Environment gt Application focused situations For specific queues a special watch is implemented Even if the queue is not becoming full a few applications require that the queue is swept up at short intervals Meanwhile in order to avoid getting an alarm when a new message has arrived a situation that watches the latency the period of inactivity is set up This is shown in Figure 3 27 A Show Formula MO Hien Delayed Messape W Formula Queue Name CRB SRVING ALS AND Latency Threshold 60 00 AND Delayed Messages gt 1 MOKAAQg i Queue Name CRB SRVINQ asl Latency Threshold 60 00 Delayed Messages gt 1 if C Show detailed Formula Figure 3 27 Situation MQ_High_Delayed_Messages_W In this situation the queue name is mentioned as shown in Figure 3 27 This means that this rule applies to one specific queue only This type of monitoring must be attached to a single queue at any time For each queue requiring this type of monitoring a single situation must be set up In order to view the applications the according queue must always be open for reading If the queue is not open it indicates that the consuming program is not up and r
220. e management service oriented architecture optimization of IT resources information lifecycle management information warehouse and business continuity The Smart Bank showcase is an implementation of these solutions in a real environment This IBM Redbooks publication looks at the infrastructure monitoring and infrastructure management provided by IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 SG24 7113 00 ISBN 0738496804 INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization Experts from IBM Customers and Partners from around the world create timely technical information based on realistic scenarios Specific recommendations are provided to help you implement IT solutions more effectively in your environment For more information ibm com redbooks
221. e status of each of the components Figure 5 13 shows that it is the Windows environment of the TEP that is causing the alert In the TEP we created situations to detect whether the Moveable Hub is active on one of the z OS partitions or not Instead of sending a red or yellow alert if it is not detected in the other LPAR an informational event is instead sent which shows up as a blue diamond File Edit View Help gt F7ERBRGAA SOOW SBSUBARAARVFOSVtHEE gt Smart Bank showcase Systems Management manx BOARTE hx oo ee TEPS Tivoli Enterprise Portal TEMS Tivoli Enteronse Management Server ITM ITM IBM Tivoli Monitoring i a IBM OM Agent IBM OM Agent Windows Tivoli Monitoring a Figure 5 13 Monitoring the monitoring environment Table 5 8 show the base queries that we used to create the Logical view from the assigned agents in Figure 5 13 Table 5 8 Monitoring view queries Alert Assigned agent and situations Assigned managed system AIX Tivoli Enterprise UNIX Systems UNIX OS js20 1 POWER4 blade Monitoring Server Remote Windows Tivoli Windows Systems Windows OS Blade11 Enterprise Monitoring Server Remote Windows Tivoli Windows Systems Windows OS Blade8 Enterprise Portal Server Windows Systems Universal Agent z OS Moveable Hub MVS System MVS Address Space z OS LPARs BA01
222. each of the installed products to your environment You can install only older OMEGAMON products using this option All the new installations must be performed through the SMP process Option allows you to provide the tool with the high level qualifiers used in our environment no defaults are given Option S Services and Utilities offers you different tools that are useful during the configuration These include the Debug option Modify CSI Add new target in CSI and so on Enter the number to select an option Set up work environment Install products or maintenance for traditional Candle products only Configure products Installation information Services and utilities F1 HELP F2 SPLIT F3 END F4 RETURN F5 RFIND F6 RCHANGE F7 UP F8 DOWN F9 SWAP F10 LEFT F11 RIGHT F12 RETRIEVE Figure 2 7 ICAT Main Menu screen Note In the screens provided in the rest of this chapter the last lines of the screen have been removed The screens describe the keys you can use and which do not provide any specific value to the displayed screens 1 Consolidated software inventory CSI 62 Infrastructure Solutions Building a Smart Bank Operating Environment After you create and submit the allocate work libraries job exit ICAT and allow the job to run before restarting the configuration tool Before configuring a product set up the configuration environment by providing the high level qualifier that you use in your environm
223. each of these products the following questions are discussed gt What can be expected from this agent Each product is represented by a specific agent a Tivoli Enterprise Monitoring Agent The reported data is very specific to the application the agent is designed for On which system must this specific agent type be installed All agents will not be installed on every system of the infrastructure Only those with a specific requirement will be injected by this agent Which attributes does this agent support Each agent type gathers its information into attribute groups These groups are described and a description of the problems that can be addressed by using this information is provided Which are the key points to monitor from a system perspective The different points of view within an IT organization may differ from team to team The system group that is in charge of delivering a stable IT environment faces specific challenges Which additional application requirements can be covered by the rules defined for this agent Business unit managers who are in charge of a special part of the business for example the head of the online banking department are less interested in single system components because their main focus is on the execution of their core business They require designated information about the health of their supporting applications 3 2 1 IBM Tivoli Composite Application Manager for Service Oriented
224. eb services data collector This generates visual representations of the various characteristics of the monitored Web services Chapter 1 Introducing the technical architecture of the Smart Bank showcase 31 Figure 1 11 references the components that come with IBM Tivoli Composite Application Manager for SOA i TEP ITCAM SOA Eclipse Plugin Monitoring 4 TEC Fa ra Remote H TEMS Remote a TEMS S TEMA ITCAM WAS x EN TEMA TEMA for TEMA Windows Databases Universal Figure 1 11 IBM Tivoli Composite Application Manager for SOA and its components The Tivoli Enterprise Management Agent is added on each of the systems where SOA requests are to be measured The agent connects to the IBM Tivoli Monitoring V6 infrastructure Through this connection it may leverage services such as setting thresholds storing historical data data warehousing and so on The focus of this project is to generate Logical views pertaining to the Smart Bank showcase and system infrastructure Therefore the Eclipse based viewer is not described in detail 1 4 2 General architectural considerations After identifying all the components that are necessary to get the required data it is important to set up a reliable IT system management infrastructure where the collected data is consolidated and grouped into Logical views The Smart Bank team requested an infrastructure that withstands any major outage This me
225. ed Target Selection mode zone C select Absolute and then click Finish 2 KJRITMOO1I Link Wizard Define New Link Branch details Ea Target Select the link to workspace Select the Target Navigator item frorn the list You can also select a workspace from a different Navigator view If Workspace shows multiple workspaces select the one to which you want to link If you want to change the target method click Relative See below Click Finish OR if you want to open the Link expression editor to refine the link definition click Next Target Workspace Navigator View Smart_Bank 2 mal Smart_Bank we Teter g Authentification D Eg Banking fj Teller Channel zBank GDPS HyperSwap PROCESS SOA Target Selection Mode Absolute O Relative elet Back Next gt L ay Help Figure 4 26 Absolute link End of definition Chapter 4 Customizing the Logical views 209 5 The process of defining an absolute link is complete To use this new link right click the icon on which the definition is set up The name of the new link is displayed as shown in Figure 4 27 Click it File Edit View Help o gt OOABROAM TOO SQOURBRSRTAARF OTROS E Vew Svan Bany m E x Graphic View nE ges BOBINE hk x Hoo TS 1 Emart Bank ia Teller Authentification d ia
226. eeq int_results jsp portal_id 251l amp domain mecha nicalworks com amp keyword searcht gt 1 Copy this into the Advice setup of a situation as shown in Figure 4 15 Situations for Processor X Hpg fe Formula Distribution TP Expert Advice 7 Action fg Until E Processor Text or Advice Location Windows os search INPUT What do you want to reasearch for enter lt BODY BGCOLOR e6e6fa gt Searching database for lt b gt search lt b gt lt META HITP EQUIV refresh CONTENT 1 URL http iww7 mechanicalworks com seeq int_results jsp portal_id 25l domain mechan icalworks comskeyword search gt NT_Bottleneck_Processor NT_Percent_Processor_Time amp NT_Percent_Processor_Time_L amp NT_Percent_Total_Proc_Time NT_Percent_Total_Proc_Time_L NT_Processor_Interrupts_Critic NT_Processor_Interrupts Warni NT_System_CPU_Critical amp NT_System_CPU_Warning M Srem Total eoe NT_System_Total_Interrupts_Lo Figure 4 15 Advice in a situation using the INPUT function 198 Infrastructure Solutions Building a Smart Bank Operating Environment 2 When the situation becomes true and you select it to obtain details you are prompted as shown in Figure 4 16 amp NT_System_Total_Interrupts 9 212 128 31 File Edit View Help SYSADMIN maxX e OUM EESEL RAE OTHE E View nax Eater je
227. efault link if more than one link is defined gt Decide whether to display or not display the link anchor the blue chain gt Offer conditional link only on the lines in a table view or icons in a graphic view which match the conditions the value of linklsEnabled in the dynamic link definition window 240 Infrastructure Solutions Building a Smart Bank Operating Environment In the same target workspace used earlier add a new link Open the link anchor window to set up the default options and the other options Figure 4 61 In this case WLM details is selected as the default link To see the blue chain icon and show this link on every line check the boxes against Show Link Indicator and Link Indicator Always Enabled in the pop up Edit View Help gt ABHBRA AD S CO C SOU RBRETAERH e se eA we Smat Ba v D B HE WLM All Service Class Resources information A Page 1 mart_Bank WLM All Service Class Resources information 5 J Teler Managed Service Period Goal Goal Goal Goal Average Performance Percent P Authentification System Class Type Percentile Importance value Response Time Index U a Banking BAPLEX BAO1 MYSSYS BAT_DISC Discret 0 nia 0 0 0 00 0 0 CICS BAPLEX BA01 MVSSYS BAT_3V30 1 Velocio 0 Medium 30 0 0 00 0 0 DB2 BAPLEX BA01 MVSSYS BAT_3V40 1 Velocio 0 Medium 40 0 0 00 0 0 MQSeries BAPLEX BA01 MVSSYS BAT_
228. egments Service layer reusable An application layer that allows the reuse of the core system functionality application in a multichannel and later in an SOA programming interfaces APIs Different channels The ability to inject workload across a number of different channels to our core system in order to represent a subset of the many channels most retail banks offer their clients and partners Rapid application build The capability to build an application component to demonstrate the power of the new SOA Credit risk calculation An application to calculate credit risk and other metrics used in calculating a bank s exposure to its clients Creation of an analytical Selecting a database model and creating a central analytical database database that can be used for risk analysis and business intelligence Interface to credit risk Populating the analytical database with credit risk details and feeding the calculation analysis from the analytical database Business intelligence Selecting an application to provide a business intelligence solution and application analytics that can access a database through open standards and not prescribe any proprietary database Business performance Creating a simple dashboard for business metrics using open standards dashboard and leveraging the SOA Basel Il credit risk Selecting a reporting tool to create the Basel II reports without the reporting necessity for any proprietary database to access the an
229. eing changed The user may also be forbidden from changing any of the workspaces The IBM Tivoli Monitoring V6 system administrator decides on the rights the user gets The system administrator creates its own views and makes it available to all the users for further use Following were the agents used for the Smart Bank showcase gt IBM OMEGAMON for IBM z OS V3 10 gt IBM OMEGAMON for UNIX System Services USS V2 20 gt IBM OMEGAMON for DB2 V3 10 gt IBM OMEGAMON for Mainframe Networks V3 10 gt IBM OMEGAMON for client Information Control System CICS V3 10 gt IBM OMEGAMON for Storage on z OS V3 1 0 gt IBM OMEGAMON for WebSphere Application Server on z OS V1 30 part of IBM Tivoli Composite Application Manager Infrastructure Solutions Building a Smart Bank Operating Environment IBM OMEGAMON for WebSphere Application Server on Distributed System V1 30 part of IBM Tivoli Composite Application Manager IBM OMEGAMON for WebSphere Business Integration V1 10 part of IBM Tivoli Composite Application Manager IBM Tivoli Monitoring for Distributed Systems on Windows V6 10 IBM Tivoli Monitoring for Distributed Systems on AIX V6 10 IBM Tivoli Monitoring for Distributed Systems on Linux on IBM System x V6 10 IBM Universal Agent V6 10 IBM Tivoli Monitoring for Service Oriented Architecture V6 0 part of IBM Tivoli Composite Application Manager The following sections describe the various agents and answer the following key
230. ent The final objective of a Logical view is to present relevant views in different points of the newly created tree By extension the entire process the tree definition with the embedded levels and the workspaces set up with view definitions is called the definition of Logical view 4 1 1 Things to be considered before defining the Logical view 182 In order to maximize the use of Logical views a few things must be considered before defining the views The TEP user used to create the Logical views must have the relevant authority In the Administer Users menu this user must have the following permissions gt User administration Author mode eligible Administration mode eligible gt Workspace administration Workspace administration mode The Workspace administration mode authorizes this user to create TEP workspaces that can be shared by all the users Workspace author mode Before creating a new Logical view the administrator must decide the architecture that is to be implemented the information this Logical view shows the tree structure and so on Infrastructure Solutions Building a Smart Bank Operating Environment 4 1 2 Defining a Logical view This section describes the step by step process involved in creating a Logical view Accessing the tree definition 1 Connect to the TEP The default Physical view is displayed Figure 4 1 Tivoli Enterprise Portal Fie Edt
231. ent by selecting option 1 Set up work environment To configure a product select option 3 Configure products from the Main Menu Figure 2 7 This displays the CONFIGURE PRODUCTS screen Figure 2 8 Link the products to the run time environment Enter the number to select an option 1 Set up configuration environment 2 Select product to configure I Configuration information S Services and utilities Figure 2 8 Configure Products screen Building the run time environment The run time environment is a set of z OS runtime libraries and VSAM data sets required for the execution of Tivoli OMEGAMON XE products on a z OS There are three different types of run time environment gt FULL This is for allocating private and base libraries in a single set of data set The FULL run time environment is typically used for a single system image gt BASE This is for allocating base libraries only The BASE run time environment is shared by all the z OS participating images gt SHARING This is for allocating private libraries only Typically you define a separate sharing run time environment for each z OS sysplex image that shares the base run time environment A sharing run time environment must be used only in conjunction with either a base or a full run time environment For each run time environment and for each product you want to install perform the following tasks 1 Add a run time environment This task 1 define
232. ent and the team s Tivoli environment assumptions In the sections that follow the different ways in which to place the two remaining components the Tivoli Enterprise Management Server Hub and the Tivoli Enterprise Portal Server are described 34 Infrastructure Solutions Building a Smart Bank Operating Environment 1 4 3 Distributed environment scenario This scenario addresses a client situation involving a dominant distributed environment and the z OS system is one among the servers The monitoring infrastructure is mostly driven by requirements and is under the responsibility of those running the distributed environment Due to this the Tivoli Enterprise Management Server Hub and the Tivoli Enterprise Portal Server are placed on Windows This implies that most of the maintenance must be performed on this platform Figure 1 13 shows the suggested configuration Windows Hot Standby not implemented Appl Sys Figure 1 13 Windows based IBM Tivoli Monitoring V6 system management infrastructure Two different Windows systems are used to host Tivoli Enterprise Management Server and Tivoli Enterprise Portal Server The infrastructure components for both Tivoli Enterprise Management Server and Tivoli Enterprise Portal Server must have powerful CPUs and plenty of memory For details about the installation refer to the following Web site http publib boulder ibm com infocenter tivihelp v3rl index jsp toc com
233. eo x E Longest Running Wo Error Server Instance Process Thread Message Message BB HTTP Sessions Date and Time Name 908 Name Job asio f SS US origin ID Message Text E Datasources 7 T l KFWITMO25I 60 Navigator updates pending Physical Application Server Instance E Server Server Instance Status Server Instance Control Region Server Region Server Region Production Debugger Isolation Replication Local Remote Name Name Description Identity Identity Stack Size Serer Allowed Policy Policy Identity Identity Baoco01 BASRO11 Running 0 No BAGUEST BAGUEST SSS EE j CB Hub Time Di 03 14 2006 02 53 PM J Server Available Application Server Instance 9 212 128 31 WOLF1 Figure 3 17 Application Server Instance workspace Infrastructure Solutions Building a Smart Bank Operating Environment The Garbage Collector Activity workspace This workspace is important for system programmers A high level of activity in the garbage collection workspace indicates a shortage of resources The reason for this shortage must be investigated On this workspace you may find all the information required for getting closer to the root cause of the problem By placing a rule on the number of garbage collections rate taken by the garbage collection by the minute you can define a powerful alarm mechanism Additionally a look at the percentage of real time for garbage collection
234. erentiators and similarities that you can use to base your system on Table 1 6 describes a typical banking architecture Table 1 6 Summary of a typical banking architecture Centralized model Most retail banks have a number of branches or outlets that communicate back to a central or regional headquarters The IT environment follows a similar model with the outlets channels being termed as front office and central processing and settlement being termed as back office Many channel types Many technically and physically different methods of distributing products and services to the clients Large centralized Often several data stores holding client account product financial and databases analytical information Multiple interfaces for Relationships with numerous external organizations from multiple internal applications suppliers specialized offices results in various technical interfaces partners and recent acquisitions Years of investment in Even if they buy solutions from ISVs many banks spend years trying to mission critical core enrich the functional capabilities of their core systems systems Various IT platforms Often many different hardware platforms and operating systems Heavy One characteristic of the banking workload is the requirement to balance input output intensive the books after a day s activity which results in a batch window in which workloads all the I O intensive workload must be completed for the day i
235. ess Integration view shown in Figure 5 10 Chapter 5 Scenarios and use cases 269 After the IBM Tivoli Monitoring products are installed the capability to gain a Business Process Execution Language BPEL view of the process is not present However with an understanding of the underlying mechanisms and a graphical view of the process taken from WebSphere Studio Application Developer Integration Edition V5 WSAD IE we construct a Logical view Important The same technique that is used to integrate to CICS in our Smart Bank showcase demonstration can be used with IMS Instead of using the CICS Transaction Gateway CTG as the J2EE Connector we used IMS Connect Both CICS and IMS support the use of direct Web service integration using the SOAP HTTP protocol File Edit View Help eo FUHRRBR AD SCOW SSOWRBSERERHFSTESEA 71 Business Process 8 O x BM Database Pool mao x 7 tod 3 BOOI i XH o olg TRFProcess pei A jdbe COREBANKds O Connections Allocated TRFProcess Receive ooa M Average Use Time aL se ji E Connection Allocation Rate J E Average Size of the Pool JavaSrippet1 1 jdbc BPEDB a y R TRFInputTrnsorm Partner Links 4b o 100 200 300 400 4 TeFProcessPartnr i FMT J2 Connectors 42C manx TRFPort TRF TRFEnputTr aera P 3 4 TRFOutputTransformn Dg siceant f Sa z BDWColecto BPOColector i jms BPECF x C current Managed Connections
236. ess continuity and regulatory compliance capabilities Regulatory compliance a matter of survival So banks must pool their resources to provide resilience capabilities Create a risk framework where risk management investments databases analytical engines can be leveraged by client relationship management and business intelligence With these key trends in the background we saw certain emerging and declining trends over shorter timeframes In 2005 for example transforming the bank branch was a key issue across the financial services sector and not just retail banking because financial institutions saw the bank branch as a key sales and client advice and relationship outlet Within the financial services sector we recognized banking financial markets and insurance However behind the trend referred to as rolling out the red carpet to clients in branches key trends such as increasing client profitability multichannel delivery and so on were also identified With these issues in mind we realized that the key drivers for spending by banks are aligned across the same areas as shown in Figure 1 2 Growth Efficiency Resilience 0 Grow top line Q Reduce operation costs Q Reduce overall risk exposure O Growth non interest income O Reduce IT maintenance Q Improve credit quality 0 Create a basis of costs Q Reduce capital requirements differentiation Q Focus on core business s n On O Comply with all regu
237. essagesRead is at 7423 messages with a rate of 124 4 MessagesRead per second e The writing to the queue activity is continued Messages put is 254 messages during a one minute interval 166 Infrastructure Solutions Building a Smart Bank Operating Environment The queue utilization graph shown in Figure 3 35 reflects this processing activity of the queue It is empty The ongoing FABBEP batch reads all the new messages as soon as they arrive File Edit View Help CET FEURRBASCA SFOOM SQSWRBAEAART E View Og Physical v Queue Utilization Application Statistics Buffer Pool Statistics Channel Definitions Channel Initiator Status Channel Performance Cluster Queue Manager Dead Letter Queue Messages Log Manager Performance Message Manager Performance MQSeries Events Page Set Statistics Queue Definitions 03 21 06 16 47 24 03 2106 16 48 24 03 2106 16 49 24 03 21 06 16 50 24 03 21 06 16 51 24 03 2106 16 52 24 fa MoseRIES a Sample Date amp Time n a a csa E Application Debugging CA A iss 03 21 06 1 24 03 21 06 16 54 24 03 21 06 16 55 24 03 21 06 17 00 24 20 30 40 50 60 70 80 90 Percent Full 100 0 0 Enabled 03 21 06 16 49 24 0 6657 0 234 i Enabled Enabled 03 21 06 16 48 24 0 19 No 6419 6401 80 80 2 0
238. est Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Request Entity Too Large 414 Request URI Too Long 415 Unsupported Media Type Following are the most common server errors 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported To obtain all the details pertaining to the error codes refer to Request For Comment RFC 2616 which is available on the Web at http rfc net rfc2616 html In the context of client error the actual severity and impact may be difficult to determine for example Error 404 means that the server has not found anything that matches the client request This error may be due to a bad client request that is wrong URL or due to a resource such as the Hypertext Markup Language HTML page being moved on the server as a result of which a client can no longer access it 174 Infrastructure Solutions Building a Smart Bank Operating Environment Request attribute This contains the resource requested by the client Figure 3 42 shows the errors detected in the access_log file of an IBM HTTP Server gt EXCEPTION_DETAIL blades SYSADMIN BEES Fle Edt View Help SG o gt O UH BRE AM SOCOV SOUR AERAENRS FeOo 2 View Physical E O8 HACI T SCOTS A ClientLo
239. etEnv KDCBO_HOSTNAME 10 1 1 135 Monday February 27 2006 19 12 29 AE4 kdebprc c 676 interface discovery IPV4 interface list 10 1 1 135 Chapter 2 IT environment of the Smart Bank showcase 89 2 2 5 Estimating the capacity of the monitoring environment Estimating the capacity of the monitoring environment helps determine a margin or boundary before considering that the environment is no longer adapted to manage the workload correctly Of course this is not a strict margin because too many factors such as network bandwidth hardware limitation and so on may influence the environment s behavior Following is the maximum capacity of a monitoring environment based on one Tivoli Enterprise Monitoring Server Hub gt The number of Tivoli Enterprise Monitoring Servers Remote supported 15 gt The number of Agents per Tivoli Enterprise Monitoring Server Remote 500 gt The number of heartbeating agents per Tivoli Enterprise Monitoring Server 500 gt The number of consoles connected to the Tivoli Enterprise Portal Server 50 gt The number of active consoles mining data connected to the Tivoli Enterprise Portal Server 10 Note This requirement can also be stated as 50 active consoles on which users access real time data 20 of the time gt Maximum number of total agents 5 000 Note The number of agents may vary on each server Most agents perform a specific monitoring function OS DB applications The Univers
240. etail S 360 INTERNAL INPUT IBMHTTPLogRecord SUMMARY 300 Force ATTRIBUTES ClientLocation D 252 SEQ 1 ClientUserName D 32 SEQ 2 Authorized_User K 32 Date_Time DL 20 LocalTimeStamp CandleTimeStamp Date Time SEQ 3 Time_Zone K 5 OperationName D 32 DLM Request D 252 SEQ 9 DLM ProtocolVersion D 32 DLMSTREND _ ServiceStatus C 99999999 SEQ 8 BytesReceived C 99999999 SEQ 6 SKEY SUM ReferProtocol D 4 DLM Referral D 252 SEQ 12 DLM Browser D 252 SEQ 13 DLM Service D 32 SEQ 4 Chapter 3 Using Physical views 175 176 ServerName D 252 SEQ 5 RequestParameters D 252 SEQ 10 BytesSend C 99999999 SEQ 7 SKEY SUM RequestElapsedTime C 99999999 SEQ 11 Requests PerSecond REAL _Occurrences _Interval_Unit BytesReceived PerSecond BytesReceived _Interval_Unit BytesReceived PerRequest BytesReceived Occurrences BytesSend PerSecond BytesSend _Interval_Unit BytesSend PerRequest BytesSend Occurrences The SUMMARY statement defines the summarization period of data input during monitoring The summarization period cannot exceed 86400 seconds 1 day When using the SUMMARY statement the resulting output attribute group consists of the following LocalTimeStamp This is a timestamp indicating the beginning of a summary interval Interval_Unit This is as defined in the SUMMARY statement parameter 300 seconds Occurrences total count This is the number of records summarized
241. evebpmrent Serbes CustomerArangementListsS ChequeDepositwS Access Services gt CashWithdrawwWS gy PRE Business Analyst Branch CashDepositwS BillP aymentwS Internet Barking BalancelnquinyWS 0 40 80 120 200 280 Sener Name Hosiname _ OPeration Name Semice Name Service Twe Message Round Trip Time Message Count aasr011 ba01 cashWithdraw CashWithdrawWs Requester 291 1 a aasr011 bat cashWithdraw CashWithdrawWvs Provider 280 1 aasr011 ba01 getBalance Balancelnquinws Requester 168 1 aasr011 bat getBalance Balancelnquinwvs Provider 160 1 aasr011 ba01 pay BillPaymentWs Requester 106 1 aasr011 ba01 getPostingListCounter PostingInquiryCountenws Requester 96 1 aasr011 ba01 deposit ChequeDepositws Requester 87 1 aasr011 bal pay BillPaymentWS Provider 86 1 v Figure 5 7 SOA model view IBM Tivoli Composite Application Manager V6 for SOA Table 5 3 shows the base queries that we used to create the Logical view from the assigned agents in Figure 5 7 Table 5 3 SOA model queries from the assigned agents Assigned agent Query Assigned managed system Services Management Agent Environment WebSphere on z OS Services Inventory Query Performance Summary Services Management Agent Environment Services Inventory Query Services Inventory WebSphere on z OS At this stage of the showcase we demonstrated that we have successfully exposed the selected core system functions as ser
242. events that occur in the normal processing of the existing CICS DB2 and IMS applications and data The existing applications do not have to be modified which in turn significantly reduces the risk of disrupting the existing operations across the enterprise 154 Infrastructure Solutions Building a Smart Bank Operating Environment Through real time monitoring an entity that is external to the source data system can be notified about a change in the data held in a Virtual Storage Access Method VSAM record DB2 table or IMS segment Based on the data change the notification can also be used to trigger further activities External event logging or notification about data change activity enables you to perform code logging functions without any application code in real time 08 390 or z OS CICS Transaction Server Dataspace server GLUEs TRUE CICS dataspace Business Event Publisher CICS EventSouree See Business Event Publisher IMS DB Event Source Message server Connector EEAS TE I i Business Event Publisher 5 l 1 1 Source Connector Workstation administration client Figure 3 28 Overview of CICS Business Event Publisher for MQSeries 1 2 As shown in Figure 3 28 CICS Business Event Publisher comprises five components gt CICS Business Event Publisher for MQSeries event connectors CICS Business Event Publisher for MQSeries message server CICS Business Event Publisher for MQSeries da
243. ew in a workspace to another one Drill down from one point to another point in order to obtain detailed information Keep track of the context in order to dynamically filter the target workspace that is displayed Chapter 4 Customizing the Logical views 201 Following are the different link types gt Absolute Jump from one source view to another view in a workspace gt Relative Jump from one source view to another view chosen in a list gt Advanced Jump from the source view and take out data in order to dynamically filter the target view Note Before Fix Pack 2 FP2 what is now called Advanced was called Dynamic Dynamic Workspace Linking involves the ability to link from one product to another product and provide enough information in order to allow the proper target node to be specified At the time of writing this book the Smart Bank case did not implement the FP2 Therefore the book sometimes refers to the Dynamic link although the Advanced link is more appropriate The Dynamic Workspace Linking as provided by FP2 is not described in this book You can define a link in a Physical view or in a Logical view Following are the types of view on which you can define a link A level in a physical or a logical tree An icon in a graphic A row in a table A bar in a bar chart A slice in a pie chart A point in a plot chart vvvvvy Note A view is always a part of a workspace Thus by using a link you jump from one workspace
244. fferent information sources including the IBM Tivoli Monitoring agents on distributed IBM Tivoli OMEGAMON agents on z OS and application data from IBM Tivoli Composite Application Manager V6 IBM Tivoli Monitoring V6 may then be used to create self defined Logical views where the health of an application and its physical implementation can be visualized gt IBM Tivoli Composite Application Manager V6 This was introduced in November 2005 This is a set of products that addresses the necessity for service and application monitoring while fully integrating into the IBM Tivoli Monitoring V6 infrastructure Beside this it adds powerful functions to other interested groups such as application developers with supporting deep dive analysis for transactions and response times Together these two products gather all the data that is required for performance measurement and bottleneck identification in the Smart Bank showcase environment IBM Tivoli Monitoring V6 IBM Tivoli Monitoring V6 is an enterprise class easy to use solution that optimizes the performance and availability of your entire IT infrastructure Through a single customizable workspace portal you can proactively manage the health and availability of your IT infrastructure end to end including operating systems databases and servers across distributed and host environments IBM Tivoli Monitoring detects bottlenecks and potential problems in essential system resources and helps you
245. fic ports and attached tasks so that the link between an open port and the according application may be tracked After this look at the link usage and understand how much network traffic is handled across this special connection and whether any delays are reported Chapter 3 Using Physical views 129 3 1 5 IBM OMEGAMON for CICS V3 10 Q Ee x B Pod Xe Fie Edt View Favorites T Address http fblade8 1920 enp kahytibfene a EJ Go Ay R Tivoli Enterprise Portal File Edit View Help HHABREAD SOOW SSUWRBRSRSERERFGFSH 3 View Physical ag O8 WE Capacity Tracking og F 4 Q 1 BBB a a a a a a S a S a S a a a a a a a a a E a Sab EERE RR EESEEE RE EREBE ER BERBERS BB BES amp Baa RS Baa RS Baa k amp Baa kh amp BRAS v Time E Dump Details ad cee kal Msimum Tass Percent a CPU utilization s Physical Al Transaction Activity MAO x Jayyuap uonoesues CPU Seconds S Hub Time Sa 03 18 2006 05 09 PM JB Server Available CICS Capacity Tracking blade8 WOLF1 ADMIN MODE Figure 3 7 The navigation subtree of OMEGAMON for CICS For each CICS region a subtree with detailed attribute groups is generated in the physical tree of IBM Tivoli Monitoring V6 as shown in Figure 3 7 New capabilities in the OMEGAMON XE for CICS on z OS V3 1 release allow you to view extensive information about your CICS resources for example TCP IP storage use and related Java
246. form the following tasks 1 Right click My Computer and select Properties Advanced Performance Check the Processor Scheduling and Memory Usage parameters 2 The window shown in Figure 2 34 opens The Virtual Memory field in the window is the size of the paging file and reflects the amount of disk space that must be reserved beyond the real storage that is available on the machine Windows sets this parameter based on real storage size Change the value by clicking Change Performance Options visual Effects Advanced pata Execution Prevention Processor scheduling Choose how to allocate processor resources Adjust for best performance of Programs CR M Memory usage Choose how to allocate system memory Adjust for best performance of Programs System cache Virtual memory if it were RAM Total paging file size for all drives 3967 MB Change 4 paging file is an area on the hard disk that Windows uses as Figure 2 34 Windows performance options Chapter 2 IT environment of the Smart Bank showcase 93 3 Return to your desktop and select Start gt My Network Places a Right click My Network Places and select Properties b Right click one of the available network cards and select Properties c Select File and Printer Sharing for Microsoft Networks d Click Properties e Check the relevant Server Optimization parameter as shown in Figure 2 35 File
247. frastructure Solutions Building a Smart Bank Operating Environment Too much detailed information in workspaces and views require many changes if the IT infrastructure is modified Generic supervision is enough if at resolution time the falling element is displayed A Logical view is not a technical view Users want to look at the relevant information to help them carry out their daily jobs A Logical view that is always red is unsuitable Users will stop trusting it Adapt the alert definitions The event console view is a useful tool because it shows all the properties of the events activity However when using a Logical view users want organized information and a quick way in which to resolve issues which the event console is not adapted for A graphical view can have a simple unicolored background To create such a background use any tool that generates a unicolored rectangle and then save it as a jpg file or a png file in the user background directory of the TEP Create a full screen graphic in the Logical view root Create icons to represent the embedded levels Do not set up any refresh interval when displaying this Logical view root If an alert opens on any embedded level this alert is propagated automatically up to the root graphic despite the fact that no automatic refresh is set up This supervision method has the advantage of using few resources Users can utilize the Navigator view to move from one level to one another
248. g V6 system If multiple DB2 subsystems are running on the same system as in the case of the Smart Bank showcase s system a tree is maintained for each subsystem The performance values provided are the key indicators of a healthy DB2 subsystem Most of these values address the requirements of the database administrators and system programmers to successfully operate a DB2 subsystem In the Smart Bank showcase the rules are defined to figure out if a dedicated application is in trouble or not Although the used CICS systems are visible in the CICS connections workspace if they have slow performing threads in DB2 or are creating a lot of lock conflicts they are visible in the lock conflicts workspace Infrastructure Solutions Building a Smart Bank Operating Environment 3 1 4 IBM OMEGAMON for Mainframe Networks V3 10 QOQ 9O d 2 pe vie O s File Edit View Favorites T Tivoli Enterprise Portal File Edit View Help HH BRPFHAF SOOH SSUBREAERD OTB 3 view Physical Oe MECCSRE m amp Gl x Oe Ti Sy TCP IP Ay TCPIP BA01 By Applications E Address Spac S E Gateways am y FTP a E Interfaces 3 By osa A GH TCP IP Memo Dactive Connections By TCP IP Stack M Accepted Connections y TN3270 Diactive Connection High Water Maik 5 VTAM ey VTAM BA0L E Address Spac LA PAR 2 a S o o o 9 o 9 o 9 Bj See eR EE EH HPR Y 8 ey yeh te ee ip eh
249. g gif node name Retail iconImage url icons user retail gif node name Shipping iconImage url icons user shipping gif Note A style is applied on one view You can use different styles for each graphic view on a single workspace 4 5 5 The example The Smart Bank showcase Logical view 246 The objective of the Smart Bank showcase is to demonstrate the value of IBM infrastructure in the context of retail banking The Logical view designed by the Smart Bank showcase team must support this objective As a consequence this Logical view does not show the data that demonstrates the health of the systems but the data that is the backbone of the showcase In fact it is a Logical view designed to support the application the showcase represents This section introduces the organization of the Smart Bank showcase Logical view that is built to support this objective Infrastructure Solutions Building a Smart Bank Operating Environment The Smart Bank main menu At the time of logging in the user receives a welcome menu as shown in Figure 4 67 This menu introduces the showcase a Neils view 9 212 128 31 SYSADMIN Weed Fie Edit View Help gt HOA BREADS COM SQSUBHAEHEERT OTHE Smart Bank showcase BOOIINT Sah x Hoo FS Enterprise Operations je Hub Time Wed 03 22 2006 02 26 PM ie Server Available Neils view 9 212 128 31
250. g place Virtualization with z VM enables moving the entire system within seconds The prerequisites for this are as follows gt Shared discs across the z VM hosting machines Using z VM the user may leverage all the features from IBM System z Implemented high availability features e Multiple data center e Disk mirroring across multiple locations e Nonstop power supply e Dynamic capacity adjustment System z features e Security workload e Powerful network back plane e Resiliency The network is one of the features worth highlighting The Tivoli Enterprise Portal Server has a huge network traffic It serves all the Tivoli Enterprise Portal clients the users and it runs an extremely busy connection to the Hub Tivoli Enterprise Management Server A powerful network connection is the key to useful performance for the users gt Spare capacity in the backup z VM hosting machine The shared discs across the z VM hosting machines feature is fulfilled within almost all the System z environments For details about the spare capacity in the backup z VM hosting machine contact your local IBM Sales Representative Chapter 1 Introducing the technical architecture of the Smart Bank showcase 43 1 4 5 Distributed systems and IBM System z working together With this solution a model that leverages the use of the Moveable Hub while keeping the Tivoli Enterprise Portal Server components on a platform used by most of the clients is
251. gator at the z OS level in our Navigator select the newly defined workspace called WLM Selected Service Class as shown in Figure 4 38 Instead of clicking Finish as is done for the absolute link or the relative link click Next Note In this case a link that jumps from one workspace to another workspace defined at the same level in the logical tree is defined There is no rule that states that such a definition must not be performed WLM All Service Class 9 212 128 31 SYSADMIN File Edit View Help gt S BRGAM ZOO CSOURBRETEART OTe view Svat soy og FA Smart_Bank a Teller Authentification Banking cics DB2 M Series TCP WebSphere a Teller Channel E ATM H Web E3 zBank GDPS HyperS PROCESS SOA i E Xi IEE WLM All Service Class Resources information Page 1 of3 a8 KJRITMOO1I Link Wizard Define New Link WLM Details x Target Workspace Navigator View Smart_Bank IMPTE 5 M All Service Class PA Ra 0 12 E Smart_Bank 0 07 rl Teller 0 00 Authentification 0 50 2 Banking 0 00 CICS 0 00 DB2 0 00 MQSeries 0 00 TCP 0 00 WebSphere 0 00 0 00 E Teller Channel Target Selection Mode 0 00 E ATM 0 00 wel web O Absolt 0 00 E zBank GDPS HyperSwap O Relat
252. gel ih i a 3 Seeeeee 2E N SHS SEER E s Physical Connection NumberID m er O 8 O x TCP Listener Summary Table S a Hex Application Collection Local ASID Connection 400 Name Time N mber IP Address oo eaten AAAGNT 03 18 06 16 17 24 OXOOCA oXx000S6B31 0 0 0 0 Is 3 S AAAGNT1 03 18 06 16 17 24 OX00CA oxo0056B25 0 0 0 0 g 40 amp 60 AAAGNTI 03 1 8 06 16 17 24 OxXO0CA 0X0005682E 0 0 0 0 a s AAAGNT1 03 18 06 16 17 24 OXO00CA oxo0056B2F 0 0 0 0 o Fy as AAAGNT1 03 18 06 16 17 24 OX00CA oxo00056B30 0 0 0 0 Connection NumbeuID 20 AADEMN 03 18 06 16 17 24 OxX00C8 oxoo056a41 0 0 0 0 M connections in Backiog AADMGR 03 18 06 16 17 24 OXO090 0x00056A62 0 0 0 0 Bs kl Limit o AANMAGR NAWANG IRATA naynanan NAYNANACEARA Ann ei irnia Connection Number ID IK gt 5 Hub Time Sa 03 18 2006 04 23 PM je Server Available Application TCP Listeners blade8 WOLF1 ADMIN MODE Figure 3 6 The navigation subtree of IBM OMEGAMON for Mainframe Networks The navigation tree for the OMEGAMON for Mainframe Networks shown in Figure 3 6 includes the TCP IP statistics and the Virtual Telecommunications Access Method VTAM attribute groups This is a system focused monitor providing a lot of performance statistics from the system although many values can be used to observe how the application is progressing This monitoring allows you to check speci
253. gement IBM Tivoli Composite Application Manager V6 for SOA Table 5 4 shows the base queries that we used to create the Logical view from the assigned agents in Figure 5 8 Table 5 4 Service management queries Assigned agent Query Assigned managed system Services Management Agent Environment WebSphere on z OS Services Inventory Query Message Summary Services Management Agent Environment WebSphere on z OS Services Inventory Query Message Average Chapter 5 Scenarios and use cases 267 5 1 3 Integration hub WebSphere MQ From the alert in the integration hub in the SOA model view Figure 5 7 we linked to the WebSphere MQ Logical view displayed in Figure 5 9 WebSphere MQ as a product provides a crucial integration mechanism for our project and is also a foundation for the Enterprise Service Bus We left IBM Tivoli Composite Application Manager for SOA monitoring and used the IBM Tivoli Monitoring V6 1 agents to construct our Logical views File Edit View Help 9 Graphic View BEER XA Bi X BReAA SeO J il am csar wilh i a Bone Qustomer facing Channels Gia e Senice Process Choreographer I MQOPEN Per Sec M MOCLOSE Per Sec Gacet Per Sec E MOPUT Per Sec Omarutt Per Sec MAING Per Sec Omasert Per Sec Wiclose Hndi Per Sec BOW BSHERHEARF sea Miclose Hndi PerSec Cmaoren Per Sec M MOCLOSE PerSec Gacet Per Sec WmorutPersec Omoa
254. gement from the infrastructure perspective 10 Infrastructure Solutions Building a Smart Bank Operating Environment gt Core systems transformation This includes the following Identifying the core competencies and functions encapsulated into the core systems and then leveraging them through an SOA Identifying back office areas that can be optimized for more efficient functioning With access to mission critical core system functionality through SOA and using the new programming model of J2EE and open standards and processes it is possible to optimize these functions and add value such as e Greater integration for cross selling e Enabling transformation of the core operation e Providing system flexibility to deal in a better way with regard to new products and regulatory compliance This step involves core systems transformation from the business perspective and SOA infrastructure and IT service management from the infrastructure perspective gt Client insight business intelligence This includes the following Creating client segmentation using an analytical banking data warehouse This includes identifying key client groups to whom a new product is offered Creating an architecture to update the analytical database in near real time in order to help businesses take more informed decisions based on up to date information This step involves front office optimization from the business perspective and informati
255. gers Query Queue Managers CSQ1 CSQ2 and Message Manager Performance WJMA respectively MQSERIES Queue Statistics Query Queue Managers running on BAO1 Queue Statistics and BA02 z OS LPARs Queue Managers running on BAO1 and BAO2 z OS LPARs MQSERIES Application Statistics Query Application Statistics 268 Infrastructure Solutions Building a Smart Bank Operating Environment For demonstration purposes we included other JPEG graphical views not illustrated here that illustrate the key queues that our system uses gt CRB SRVINQ and alias for the multichannel integration step 1 and step 2 in Table 5 1 on page 261 CSQ1 Queue Manager and CSQ2 Queue Manager gt CICBEP QLOCAL1 for the near real time update of the analytical database through the CICS BEP product CSQ1 Queue Manager gt WQ_BDWUpdateMdbQueue and WQ_BPDUpdateMdbQueue for the near real time update of the analytical database through the process mechanism step 4 in Table 5 1 on page 261 WJMA Queue Manager On the right hand side of the Logical view a Queue Manager view of the WebSphere MQ activity CSQ1 CSQ2 and WJMA corresponding to the frames A B and C is displayed In Table 5 5 frame D the queue depth on our queues is displayed This instantly alerts if the queue depth begins to increase beyond what is expected indicating that the application or mechanism that is listening to the queue in order to process the message may be experiencing a problem
256. gt HUB CMS Security settings Security validation gt N Y N Integrated Cryptographic Service Facility ICSF installed gt N Y N ICSF load library gt CSF SCSFMODO Encryption key gt IBMTivoliMonitoringEncryptionKey Enter Next Fl Help F3 Back F5 Advanced COMMAND gt Figure 2 27 ICAT Tivoli Enterprise Monitoring Server Configuration Values screen 78 Infrastructure Solutions Building a Smart Bank Operating Environment 4 A Tivoli Enterprise Monitoring Server Remote requires a Tivoli Enterprise Monitoring Server Hub connection To select the Hub Primary Tivoli Enterprise Monitoring Server to connect to the Remote Tivoli Enterprise Monitoring Server perform the following tasks a Select F5 and F10 to view the Tivoli Enterprise Monitoring Server list specific panel shown in Figure 2 28 on page 79 The Tivoli Enterprise Monitoring Server eligible list that you have already configured is displayed At this point the importance of first defining the Tivoli Enterprise Monitoring Server Hub and then defining the Remote Tivoli Enterprise Monitoring Server becomes clear Select the Tivoli Enterprise Monitoring Server Hub that you want from the list and select F5 to clear out any IP information COMMUNICATION SELECTION PANEL FOR BAO1 Row 1 to 1 of 1 COMMAND gt Select the hub primary TEMS to connect to this remote TEMS The currently connected hub is HUB CMS The following lists eligible Tivoli Ente
257. h JMS amp WebSphere MQ Physical Smart_Bank Hub Time Sat 03 11 2006 05 58 PM Server Available Teller 9 212 128 31 SYSADMIN Figure 4 28 Absolute link result The absolute link that is created helps establish a static connection from one point for example the Branch icon inside the status channels view to another fixed point for example the Branch workspace 4 4 3 Defining a relative link The purpose of a relative link is to define a link that can be used to target more than one workspace Some agents monitor more than one resource at a time As an example OMEGAMON XE for CICS manages more than one region on a specific z OS system When examining the performance of the entire system a user may want to zoom in on some specific details on a monitored resource with the possibility of choosing the one that is to be examined in detail A relative link is designed for that purpose The process of defining a relative link is the same as that used to define an absolute link except that the Relative button is selected when defining the relative link This link jumps to a chosen subpart of the tree that has the same configuration managed system type and identical workspace Restriction Generally a logical tree has no identical subpart Generally a TEP administrator must not use a relative link in Logical views Chapter 4 Customizing the Logical views 211 To define a relative link perform the follow
258. h LPAR hosts its own Remote Tivoli Enterprise Management Server The communication with the Tivoli Enterprise Management Server Hub uses only SNA based communication All z OS based agents connect only to their local Remote Tivoli Enterprise Management Server using SNA No other protocol is configured Chapter 1 Introducing the technical architecture of the Smart Bank showcase 47 VMware at a glance As Figure 1 18 shows the virtualization feature is now run by VMware that supports the IBM System x platform The prerequisites for this solution are similar to that of z VM gt Shared disks across the VMware hosting machines gt Spare capacity in the backup VMware hosting machine Figure 1 19 shows the principal configuration Backup hostvm01 hostvm02 vmteps VMware image Replication via VMware SAN PPRC mage _ TEP Clients Figure 1 19 VMware setup for Tivoli Enterprise Portal Server system The Tivoli Enterprise Portal Server is installed inside a virtual VMware A configured machine inside VMware is represented by a VMware image This image makes up a completely configured computer including the following gt Hardware definitions Memory Hard disks Network cards Number of processors gt Software that has to be installed on it Operating System Windows However it may also be Linux Database System DB2 Universal Database UDB V8 2 Tivoli Enterprise Po
259. h the underlying monitoring infrastructure such the Tivoli Enterprise Management Server Remote and the agents It hosts all the logical monitoring data and its applied rules If this component fails the coordination inside the management infrastructure and the presentation to the user terminates The Moveable Hub implementation on z OS allows the restart of the Tivoli Enterprise Management Server Hub on any member of the sysplex assuming that common sysplex features such as disk sharing and so on are enabled Because the Tivoli Enterprise Management Server Hub no longer resides on a single physical or logical system its communication credentials may change when it wants to connect to components outside the sysplex environment 40 Infrastructure Solutions Building a Smart Bank Operating Environment In the majority of cases TCP IP is the primary choice for communicating outside of z OS IP addresses are commonly bound to a specific machine so that a request for connection or communication is sent to a specific system Within a z OS sysplex environment VIPA is available With VIPA an IP address can be linked to the entire sysplex and not to only one specific system inside this sysplex In order to do this a port number in the sysplex environment must be reserved for the Hub Tivoli Enterprise Management Server The Hub Tivoli Enterprise Management Server recognizes the sysplex VIPA as its host regardless of which system it is running on Th
260. hat of the Tivoli Enterprise Portal after selecting the All Workload workspace Figure 2 47 shows a window displaying the Tivoli Enterprise Portal output Tivoli Enterprise Portal File Edt View Help BHBRGAF SOSO C SBOWKRARRETERD 9 s ea S5 View Physical ne LEETE E EE blade5 Linux OS a WebSphere Application Server Agent E Application Trace Files Gy Agent Events i WebSphere Application Server t Siq serveri Eg servers2 E Application Server CTG Delay Time Des Home Delay Time EJB Local Home Delay Time EJB Local Object Delay Time EJB Method Delay Time EJB Remote Delay Time D Heap Alloc Delay Time Buca Delay Time Tums Delay Time EUND Delay Time Duta Delay Time M miscellaneous Delay Time Seret Delay Time WEOL Connection Delay Time OSOL Query Delay Time Osa update Delay Time Duser detined Delay Time kb Suspected Memory Leaks dy Heap Usage ki Garbage Collector Activity ki Pool Utilization dy In flight VWorkloads ki Longest Running Workloads jy HTTP Sessions dy Datasources dg Lock Analysis action ActionSenslet doPost dy CTG Summary dy JMS Summary hy Web Applications ky EJB Containers hal a Aia ad 200 400 600 800 1000 1200 Milliseconds Average Average Number Number of CPU Time Heap Allocation Locks Acquired 1 026 806
261. he Smart Bank showcase was created at the IBM European Products and Solution Support Center PSSC in Montpellier France as a vehicle to show the retail banking clients the value of IBM infrastructure solutions in addressing their key business issues As such it was a project whose scope and target audience were spread across the world directed by the IBM Financial Services Sector FSS and the IBM Systems Technology Group STG Following were the objectives of the project gt To demonstrate the value of IBM infrastructure solutions in the context of retail banking gt To provide a tool to engage the clients and interest them in more projects gt To focus on the business value and develop proof points to show how the infrastructure solutions can help deliver key banking projects gt To demonstrate the proof points at operational volumes typical of a European bank which includes the following Six million clients 12 million accounts Average daily online transaction throughput of about 300 transactions per second rising to a peak of up to 800 transactions per second Constant background batch workload setup as the lowest priority workload during the demonstration gt To provide a platform for internal IBM collateral testing of concepts and documentation In this context the following points are relevant We participated in the z9 109 Early Support Programme ESP project testing the new machine with
262. he Web at http publib boulder ibm com infocenter tivihelp v3rl topic com ibm itm doc itm61 Ousersguide pdf For each server a navigator item is available with an identical subtree beneath it Chapter 3 Using Physical views 141 142 The Application Server Instance workspace This workspace as shown in Figure 3 17 provides an overview of the application server s health It is a good place to associate rules that monitor the availability of the server instance Associating or disassociating a situation means this situation will be attached to all the server subtrees to which this situation is distributed to 9 9 x 2 se ea amp s Ble Edt View Favortes T Address http j 9 212 128 31 1920 enprkdt E EJ Go y Tivoli Enterprise Portal File Edit View Help HHABREAD S CO C SSOWURB SERED OTSA View Physical g Oa g E Event Console O A amp f amp amp O Total Events 22 item Fitter Enterprise Status Situation Name Display item Source Ir BACELLA BAOCOO1 BASF LJ MessageArrivalClearing ITCAM450A BA02 D4 6 Message Ana Ba suspected Memory L MessageArrivalClearing ITCAM450A BA01 D4 Message An fal tieop Usane NT_Log_Space_Low Security Primnary BLADE8 NT System NT Service Error Primary BLADE8 NT System faa E Garbage Collector Ac gt Pool Utilization z E tn fght workloads E pplication Server Error Log o
263. he architecture through Tivoli Enterprise Portal 258 5 1 2 Service oriented architecture view 000 eee eee 260 5 1 3 Integration hub WebSphere MQ 0 000 eee 268 5 1 4 Process integration 0 00 eee 269 51 5 SUMMA beige ee eae bee tate eid aca E oa Saat cht bape des 271 5 2 Optimization of IT resources On Off Capacity on Demand 272 5 2 1 The Operations view 0 0 0 0 cc eens 273 5 2 2 Monitoring the monitoring environment 0 00 eee 276 5 2 3 Monitoring the network 0 0c eee 277 5 2 4 IBM System z9 109 utilization 0 0 0 eee 278 5 25 SUMMA goad ates ea ce eee na aes ee aed Gea eh dein Dk 280 5 3 Branch transformation and infrastructure simplification heterogeneous view 280 5 3 1 The Branch VieWise r cidra esa ria eE e eee 282 5 3 2 The Linux utilization view 1 eee 283 53 3 SUMMA ara sider tent cee Gra ert apes ecg were ana eee bets 284 Related publications 00 eee 285 IBM REABDOOKS oa sire Sy ete aid i Srl age tach aati alos AEE ATE Rahat athe danas 285 Other publications 20 000 c eens 285 Online resources 0 0 eee 285 How to get IBM Redbooks 0 cece tees 286 Help trom IBM sas 2043 4 n oben ey tie eth abide Pad E EERE A aceite 286 WN OX curona a eee a tian echt des ated tinder cate ere Sey eed denied ated vee 287 Contents v vi Infrastructure Solutions Building a Sma
264. he title of the view is changed to the new assigned value If you do not select the Split Pane Toolbar option in the TEP view menu this title is not displayed Chapter 4 Customizing the Logical views 231 Advanced link Inserting symbols for the header and the footer In the advanced link definition window new symbols can be added They work in the same way as the symbols used through queries To create a new symbol perform the following tasks 1 Click New at the bottom left of the advanced link definition window zone A in Figure 4 51 4 2 KJRITMOO2I Link Wizard Edit Link WLM Details le Properties Expression Symbols true Y contextlsAvailable d B Target Workspace Cclear_ C Test_ E Query WLM LINK Service Class _ allowable Terms 3 Symbols V NODE G Values al V SERCLASS Link S E Table WLM Selected Servi E Selected Row V Footer Attributes V Header V Actual Host YV Average Response Time V Average Storage V CSS Priority Y Class Flag V Duration V Goal Importance V Goal Percentile V Goal Type V Goal Value V VO Priority V 1O Rate Y IFA Service Units V Managed System V Percent CPU V Percent IFA V Percent IFA on CP Y Performance Index _ _ __ i V Period New L Resource Groun x Figure 4 51 Adding a new symbol for a dynamic link definition 232 Infrastructure Solutions Building a Smart Bank Operating Environment 2
265. high and corresponds to not only the normal peak load at lunch time but also has additional workload due to the success of our new product launch Our bank experiences an unusual increase in workload If our system cannot respond quickly to maintain the quality of service to the client facing channels business will be lost The alerts on our Enterprise view turn yellow or red when our channels start experiencing bad response times In our demonstration we perform an On Off Capacity on Demand to our System z9 109 environment which provisions more processing capacity to our environment that is it automatically makes available more processors such as central processors CPs ZAAPs and Integrated Facility for Linux IFLs for our workload to use An important point here is that without virtualization our workload will not be able to take advantage of this extra processing resource The fact that our mission critical applications run in LPARs on z OS and in z VM which share physical CPs makes this possible Our additional CPs are recognized by the environment and within 3 5 minutes we have our system running with the quality of service we agreed on The Hardware Management Console HMC for the IBM System z9 109 is used to initiate the On Off Capacity on Demand entering the pre prepared policy number which is verified over the Internet by the IBM Resource Link in Poughkeepsie NY USA The Resource Link identifies the policy and enables
266. i Enterprise Portal Server It opens two ports for the Tivoli Enterprise Portal Server clients It creates a connection to the Hub Tivoli Enterprise Management Server It enables access to the underlying database system using the Distributed Relational Database Architecture DRDA Object gt The DRDA Object TEPS2 This is the DB2 client part It enables any program code to access a DB2 server installation either locally or remotely Because we use DB2 Universal Database it is called DRDA which is a common wording across Windows and Linux On Windows it is also called the Open Database Connectivity ODBC definition gt DB2 Universal Database Workgroup Edition or Enterprise Edition Within the database all the presentation data user settings and so on are stored This database cannot be shared by multiple systems The DB2 server must run locally as stated in the installation manual 42 Infrastructure Solutions Building a Smart Bank Operating Environment These components must run on a single system They cannot be distributed across multiple systems Using the Tivoli Enterprise Portal Client the user calls a specific port on a defined host to connect to the Tivoli Enterprise Portal Server If this host is not available for any reason the user will not be able to access this service A backup machine is hard to maintain because the database content has to be mirrored frequently to keep track of the changes takin
267. ibm itm doc toc xml Note You can also place the Tivoli Enterprise Management Server on AIX Linux on IBM System x or Sun Solaris The Tivoli Enterprise Portal Server is also supported on Linux on IBM System x Select your preferred platform All the platforms support the essential features referenced in this book Chapter 1 Introducing the technical architecture of the Smart Bank showcase 35 It is a good practice to place the Tivoli Enterprise Management Server and the Tivoli Enterprise Portal Server on different systems because both may require the same system resources at the same time In the distributed area you must pay special attention to network traffic The Tivoli Enterprise Management Server must be able to handle all the communication across the entire infrastructure including heartbeats requests for data and so on Following are the components gt On Windows For Tivoli Enterprise Management Server Hub For the Tivoli Enterprise Management Server Hub on Windows also UNIX and Linux a feature called Hot Standby is available As shown in Figure 1 13 the Tivoli Enterprise Management Server is the central point of communication It is therefore important that this component is almost always up and running and delivers the service as expected Even a single failure is not acceptable in a production environment It is not possible to add a secondary Tivoli Enterprise Management Server Hub statement in the installation
268. icates a faulty application or an absence of a system resource Total request rate which indicates no activity for this application or vice versa that is an overload of this application gt Rules for business owners Web application specific response time limits Application specific servlet request rate These rules are implemented in our Smart Bank showcase Make a note of the fact that each client may have individual requirements 146 Infrastructure Solutions Building a Smart Bank Operating Environment The Enterprise JavaBeans Container workspace The EJB Container workspace as shown in Figure 3 22 provides information about the EJBs that are executed It is application specific x a pe se e amp File Edit View Favorites I Address Tivoli Enterprise Portal File Edit View Help HHBR AM SFOO C SQSWRBREAERY OTD oea WECM 3 view Physical e lt Garbage Collector Aci Pool Utilization y In flight workloads Longest Running Wo quen querybean jarQuery InterestProjectEAR InterestProjectEJB jar interestProcessBean BPEContainer_banode1_basi011 compensate_ejb ja CompensationRunProclet BPEContainer_banode1_bas011 compensate_ejb jar ContextualProcletFacade HTTP Sessions Dakasources BPEContainer_banode1_basi014 compensate_ejb javCoordinator Lock Analysis wo BPEContainer_banode1_bas011 bpecontainer javintenalClassLoader CTG Summary BPECont
269. ication Server is not covered For a detailed description of IBM Tivoli Composite Application Manager WebSphere Application Server refer to BM Tivoli Composite Application Manager V6 0 Family Installation Configuration and Basic Usage SG24 7151 IBM Tivoli Composite Application Manager for Service Oriented Architecture IBM Tivoli Composite Application Manager for SOA manages Web services These services are remote processing facilities that are defined through the use of Web Services Definition Language WSDL These services are accessed by using SOAP over HTTP Internally Web services are implemented using Java API for Extensible Markup Language based Remote Procedure Call JAX RPC IBM Tivoli Composite Application Manager for SOA installs itself as the JAX RPC handler in order to capture and manage Web service calls IBM Tivoli Composite Application Manager for SOA consists of the following logical components gt A Web services data collector within the Tivoli Enterprise Management Agent The monitoring agent is installed locally on every application server environment where Web services are to be managed It intercepts and instruments Web service requests and responses The data collected by the monitoring agent about Web services is written and stored in a log file Additionally it is sent on request to the IBM Tivoli Monitoring V6 infrastructure gt An Eclipse based viewer that processes the log files that are generated by the W
270. ication support files are installed click Finish h Figure 2 38 shows the installation completion window Installer olx Please wait while application support is added O DERMOMERCANCOCCNO0OAANANCANN A s Installation completed successfully a N Installation details Soe Tivoli software j topping the Tivoli Enterprise Monitoring Server TEMS dding TEMS support for OMEGAMON XE for Websphere Application Server on Distributed Systems Version 01 30 00 C tarting the Tivoli Enterprise Monitoring Server TEMS onfiguring TEMS support for OMEGAMON XE for Websphere Application Server on Distributed Systems Version 01 3C topping the Tivoli Enterprise Monitoring Server TEMS tarting the Tivoli Enterprise Monitoring Server TEMS nstallation completed successfully log file for this installation is located at C DOCUME 1 ADMINI 1 LOCALS 1 Temp 2 ITM_AppSupport_Install log gt Back Ne Finish Figure 2 38 Application support for WebSphere Application Server distributed Installation completion InstallShield Chapter 2 IT environment of the Smart Bank showcase 97 98 Customizing the Tivoli Enterprise Portal Server This section describes the miscellaneous tasks involved in customizing the Tivoli Enterprise Portal Server in order to address the requirements of our environment This section does not discuss the Tivoli Enterprise Monitoring Server requirements They are described in the i
271. ice Innovative and flexible product packages and solutions using core competencies Table 1 3 Outdated core systems and poor M amp A integration Industry issue 2 Outdated core systems and poor M amp A integration Challenge for banks Adapt the core systems and integrate disparate platforms and processes to reduce costs and support changing demands Reduce the high fixed costs of noncore processes while increasing efficiency and flexibility Recommendations Reduce costs and improve efficiency by leveraging existing mission critical core systems with better integration Replacing in a modular fashion certain components of outdated systems Outsource noncore IT infrastructure Share best in class capabilities across product silos horizontal integration Table 1 4 Investment in compliance and risk management Industry issue 3 Investment in compliance and risk management Challenge for banks Ensure compliance with pending regulations while enhancing existing systems and processes Develop business resiliency and operational high risk mitigation capabilities with minimum expenditures Chapter 1 Introducing the technical architecture of the Smart Bank showcase 5 Industry issue 3 Investment in compliance and risk management Recommendations gt Build operational efficiency objectives into risk management strategies Operational efficiency becomes a key performance metric for risk management Share cost of disaster recovery busin
272. ice Class Resources informatior i TTA D 3 Table Views E MM Seeded Ser 2 Ame Description Cc E 3 Description WLM Service Class Resources information for this MVS image WLM_Service_Class_Resov FJ ALM LINK Service Class F WLM Serv Class for Ser x ete vu Service Class Rese Data Source TEMS HUB CMS ip pipe 10 1 1 29 2018 S s OMEGACENTER Gateway Last Modified Se eee Last Modified on Mon 03 13 2005 12 16 PM BE OMEGAMON for DB2 izz a 3 OMEGAMON for IMS Last Modified by SYSADMIN 3 OMEGAMON for MVS gt OMEGAMON for OPR f Specification Q Results S EG OMEGAMON for SMS ery Mesut source S g OMEGAMON for VTAM Specification OMEGA VIEVY k E 05 390 Unix USS S a Queue Sharing Group fx Managed s Services Management Agent System P a Services Management Agent En S a Storage Subsystem C2 SNODES E SSERCLASSS E e Fy TCPAP N m Ea Tivoli Fnternrise Monitoring Serve Figure 4 42 The target workspace with a view and its query Advanced link Matching the elements together The target simple workspace is already known Figure 4 34 on page 217 During the dynamic link definition process a window shows a display with three parts Figure 4 41 In fact there is a direct association between what the dynamic link definition window displays and the content of the workspace By bringing the two windows closer as shown in Figure 4 43 the following points become clear
273. iew Select Link to gt Link Wizard as shown in Figure 4 21 File Edit View Help o gt OBHRBARG AM SOO C SOURS EAAETOTeO View max Graphic View manx BOORIS ATE hx Boo FS tad Authentification Mig Banking Channel Access Teller Channel Points zBank GDPS HyperSwap ATM dmemet iniranet r bee internet Intranet ZBank GDPSHyperSwap A r Channel interaction fF ee PROCESS SOA Access integration Core systems amp Enterprise Business ATM Integration Processing Tate aston Pines H iS skh EA Physical 3 Smart_Bank amp Launch i i ES B Split horizontally Q Print Preview a Bas Properties Ca Teller vi anaa PROCESS SOA Enterprise View Iv lt j m fi pe 5 FA Notepad oao x Hub Time Sat 03 11 2006 06 41 PM Server Available Smart_Bank 9 212 128 31 SYSADMIN Figure 4 21 Accessing the Link Wizard Chapter 4 Customizing the Logical views 205 2 The TEP now displays the Define New Link window Figure 4 22 Click Next Smart Bank 9 212 128 31 SYSADMIN SAX Fie Edt View Help EA n a a A C EE a EA f Graphic View BOOI a hk x Ho olg zBank GDPS HyperSwap PROCESS SOA AHHH a Rh The Link Wizard guides you through creating a new link or editing an existing one Do one of the following Fora new link select Define New Link and click Next To edit a link select it and click Next
274. ific system image This host name and the IP address are used by all the distributed Remote Hub and the agent to refer to the Hub and the Tivoli Enterprise Portal Server On z OS each LPAR hosts its own Remote Tivoli Enterprise Monitoring Server The communication with the Tivoli Enterprise Monitoring Server Hub uses SNA based communication only If the Tivoli Enterprise Monitoring Server Hub moves for any reason the Virtual Telecommunications Access Method VTAM applid moves with it Thus any 72 Infrastructure Solutions Building a Smart Bank Operating Environment component requesting communication with the Tivoli Enterprise Monitoring Server Hub through SNA will find it This Hub implementation called moveable Hub on z OS allows the restart of the Tivoli Enterprise Monitoring Server Hub on any member of the sysplex it is running on Hostname Address stit Started task Recommended default Specify IP PIPE and Web Services SOAP Server configuration Port number gt 2018 IP PIPE Port number gt IP PIPE for IPV6 Port number gt Secure IP PIPE Port number gt Secure IP PIPE for IPV6 HTTP server port number gt 1921 Access TEMS list vian SOAP Server gt N Y N Address translation gt N Y N Partition name gt Note See Fl Help for TSO HOMETEST command instructions Enter Next Fl Help F3 Back COMMAND gt Figure 2 20 ICAT IP PIPE Communication Protocol configuration screen Chap
275. iguration of this product Configuring a Remote Hub on z OS This section describes how to configure a Remote Tivoli Enterprise Monitoring Server Hub in a z OS sysplex environment In our example Tivoli Monitoring Services on z OS V6 1 0 is selected as the product to configure see Figure 2 9 on page 65 with S selected in front of the product This Tivoli Enterprise Monitoring Server is to be configured as the Remote Tivoli Enterprise Monitoring Server Hub Note Only the process involved for one Remote Hub is described here In our environment we followed the same process for both the Remote Hubs Tivoli Enterprise Monitoring Server BAO1 and BAO2 76 Infrastructure Solutions Building a Smart Bank Operating Environment Perform the following tasks 1 Select action C to configure BAO1 as the Remote Tivoli Enterprise Monitoring Server Hub as shown in Figure 2 25 Note From a terminology point there is only one hub in a Tivoli Enterprise environment the Primary hub The Remote Tivoli Enterprise Monitoring Server Hub is now referred to as Tivoli Enterprise Monitoring Server Remote RUNTIME ENVIRONMENTS RTEs Actions A Add RTE B Build libraries C Configure L Load all product libraries after SMP E D Delete U Update V View values Z Utilities Action Name Type Sharing Description BASE BASE RTE BASE for TIVOLI Smart Bank Sysplex BAPLEX BAO1 SHARING BASE RTE SHARE for TIVOLI Smart Bank LPAR BAO1 BAO2 SHARING BASE RTE S
276. iguration values inside the z OS logical partitions LPARs and the sysplex components is provided to a user Figure 3 3 shows the navigation tree from the z OS agent The agent presents a lot of information about the z OS system and its major resources This agent tracks the monitoring activities that help keep the system up and running the health of the system the existence of Chapter 3 Using Physical views 125 126 the dedicated process the correct usage of global resources and all the other aspects regarding the z OS operating system I 8 http 4 9 212 128 31 19204 enp kdt E EJ Go ay z 0O 90 hha pe vie s amp s Fie Edt View Favortes T Address Tivoli Enterprise Portal File Edit View Help HHEBREAD S CO C SSWURB SERED OTSA View Physical ag oa PIT XCF Groups with problems g Mainframe Networks MQSERIES MYS Operating System a Fay BAPLEX BAQ1 MYSSYS Address Space Overview Channel Path Activity Common Storage Cryptographic Coprocessors DASD MYS DASD MVS Devices Enclave Information q Enqueue and Reserve Summ LPAR Clusters Operator Alerts Page Dataset Activity Real Storage System CPU Utilization System Paging Activity Tape Drives User Response Time 2 WLM Service Class Reou Oe ee 1 gt member Count BProblem Count a F Physical eS 2 XCF Groups Data for Sysplex Group Member Problem Name Count Count Karanasan SYSGRS 2
277. indows AIX will be supported in the next release vvvy Tivoli Enterprise Managing Agent The Tivoli Enterprise Managing Agent is installed and implemented on the system or subsystem that requires data collection and monitoring It is responsible for gathering the required data It does this by sampling specific attribute groups that are inherent to a given agent on request by an user or triggered by a given situation In the Smart Bank project the following agents are used IBM Tivoli OMEGAMON XE on z OS V3 10 IBM Tivoli OMEGAMON XE for DB2 on z OS V3 10 IBM Tivoli OMEGAMON XE for Mainframe Networks V3 10 IBM Tivoli OMEGAMON XE for CICS on z OS V3 10 IBM Tivoli OMEGAMON XE for Storage on z OS V3 1 0 IBM Tivoli Monitoring for distributed systems on Windows V6 10 IBM Tivoli Monitoring for distributed systems on AIX V6 10 IBM Tivoli Monitoring for databases IBM Tivoli Monitoring for Composite Application Manager Integration IBM Tivoli Monitoring for Service Oriented Architecture SOA vvvvvvvvvy Tivoli Data Warehouse V2 1 Tivoli Monitoring V6 is delivered with a new version of the Tivoli Data Warehouse The new Tivoli Data Warehouse V2 1 is based on a relational database system of your choice including IBM DB2 Universal Database The Tivoli Monitoring agent for data warehousing is responsible for transporting all the gathered data to the data warehouse Whenever an application exports data to the database for the first tim
278. ing tasks 1 In the window shown in Figure 4 29 open the CICS part of the Navigation tree on the physical tree Define a relative link in one of the displayed views In our case we define a relative link from a simple table view that displays an overview of each CICS region managed by the Smart Bank showcase team The target of this relative link is the DB2 Summary workspace available under each controlled CICS region 0 O HAG Sex e oeaBa Ws ny pes Tivoli Enterprise Portal L ill gt File Edit View Help FAHBRt AM SCO SBSOWURBRBERAERF TSeEH View Physical vl me CICS Performance Summary 12 System CICS Region CICS Maximum Tasks D Transaction CPU SIU ENQUCUE vaa u sy spiea ID Name Version Percent Rate Utilization GRS Ring Systems Data for Sysplex BA01 CICSRAIO 6 4 0 5 0 0 0 Report Classes Data for Sysplex BA01 CICSRA11 6 4 0 5 0 0 0 Resource Groups Data for Sysplex a C BA01 CICSRA14 6 4 0 5 0 AL Service Classes Data for Sysplex BA01 CICSRT10 6 4 0 5 L IRI Service Definition Data for Sysplex LJ BA01 CPSMCMO1 6 4 0 12 00 Shared DASD Groups Data For Sysplex XCF Groups Data for Sysplex i XCF Paths Data for Sysplex XCF Systems Data for Sysplex Ga Bam o a BA01 CICSRA10 j TU Aitomatic Initicte Nacerintare lt IEA s Physical BWEN SSEIQ aomas o 10 20 30 40 50 60 70 80 90 100 Performance Index Percentage
279. inue to define the view Attention Although this option comes with the product we do not recommend it It links this view to specific managed systems It is impossible to assign situations to this level of the Logical view when using only these modes of definition ES View Smart_Bank vl pal Smart _Bank Authentification a Teller 5 views E ATM Table Views ATM Channel 5 Date E Banking ey Query Editor Web E3 ES GDPS HyperSwap iF Cl af Description PROCESS SOA ETAT NE E GiCSplex Region Emel la Description Default Transaction Analysis Query Query Results Source ClCSplex_TCPIP_Statistics CICSplex_Temporary_Storac CICSplex_Temporary_Storac CICSplex_Temporary_Storac Let user assign explicitly ClCSplex_Terminal_Storage 4 Assigned Available Managed Systems Let system assign automatically CiCSplex_Response_Time_ CiCSplex_Response_Time_E ClCSplex_RLS_Lock_Analys DataSource TEMS HUB CMS ip pipe 10 1 1 29 2018 CiCSplex_Service_Class_Ar F E CiCSplex_Service_Task_Det RELIG E CiCSplex_Storage_Analysis Last Modified on Fri 0310 2006 01 48 PM WF CiCSplex_Subpool_Details Last Modified by SYSADMIN a CiCSplex_System_Initializatic L CICSplex_Task_Class_Analy Physical lt 3 Smart_Bank a Gy cicSplex_TCPIP_Service_St Specification Query Results Source ne e E By CiCSplex_Transa
280. iorities for z VM Branch transformation and IT simplification Our branch network forms a part of the multichannel architecture and adheres to the same principles The branch server is a J2EE application and consequently adheres to the principles of being able to run on any platform that can run the Java Virtual Machine JVM We leveraged this capability and deployed the branch servers to a centralized platform on IBM System z9 109 benefiting from the resiliency and availability discussed in Business continuity and high availability on page 21 and the cost efficiency of a highly simplified infrastructure and network We chose Linux running as a guest under z VM as the deployment platform for the combined horizontal and vertical scalability This also provided us the flexibility to deploy the same branch server to other platforms depending on the business requirements and qualities of service required We chose the BladeCenter environment to represent a regional hub or a slightly different business channel that uses the same branch server functionality This server also ran on Linux but on Intel blades Chapter 1 Introducing the technical architecture of the Smart Bank showcase 21 The main reason why clients are pursuing this sort of infrastructure simplification is because of the cost efficiency it enables The second reason is the flexibility this model affords Figure 1 7 illustrates the physical deployment environment for the Sm
281. is ensures that it is always reachable under the same IP address for all communication requests In order to simplify the configuration of the Tivoli components z OS internal communication uses only SNA This avoids switching of ports between the Remote Tivoli Enterprise Management Server its connected agents and the Hub Tivoli Enterprise Management Server The Tivoli Enterprise Management Server Hub must use its port exclusively across the entire z OS sysplex If the Tivoli Enterprise Management Server Hub moves for any reason the VIAM APPLID moves with it Thus any components requesting communication with the Tivoli Enterprise Management Server Hub through SNA will find it Chapter 1 Introducing the technical architecture of the Smart Bank showcase 41 Tivoli Enterprise Portal Server implementation based on Linux on IBM System z under z VM The Tivoli Enterprise Portal Server requires detailed attention It runs only once in a single IBM Tivoli Monitoring V6 installation Figure 1 16 shows the relevant components TEP Client TEP Client Calling TEPS on a specific host and a specific port To Hub TEMS UDB EE WE V8 2 Figure 1 16 Simplified Tivoli Enterprise Portal Server component view The Tivoli Enterprise Portal Server comprises the following three simple components gt The Tivoli Enterprise Portal Server binary code which implements the functions presented by the Tivol
282. is book Table 3 1 CICS Business Event Publisher Components and associated started tasks CICS Business Event Publisher component Implemented started task Event collector for DB2 CBMDES1 DataSpace Server CBMDSSVR Messaging Server CBMMSVR1 158 Infrastructure Solutions Building a Smart Bank Operating Environment Our posting table CRBCORO PSTG is set up to track changes by setting the parameter DATA CAPTURE CHANGES in DB2 As soon as all the three CICS Business Event Publisher components are started every change to the Smart Bank showcase posting table is reported and a message sent to the MQ queue CSQ1 In addition a batch process to read our MQ queue CSQ1 is started Every message posted to the MQ queue is then analyzed and processed At this juncture two operations take place gt Checking whether a banking client account exists and if it does not creating a record to the BDW TXN table An example of the SQL statements is shown in Example 3 1 Example 3 1 Creating a record when an account does not exist EXEC SQL SELECT INTO DCLAR X AU FROM BDWCORO AR_X_AU WHERE AR_ID WOO ARF IDFR END EXEC MOVE SQLCODE TO SQL CODE DISPLAY SQLCODE SEL gt DISPLAY FIELD IF SQLCODE 100 AND TEST1 OK EXEC SQL INSERT INTO BDWCORO AR_X_AU ARID AU ID AR X AU TP ID EFF DT PPN DT PPN END_DT VALUES W00 ARF IDFR 0001 3139 2028 03 31 2028 03 31 ZZTIME 2028 03 31 E
283. istics for each interval 1 minute is our default interval duration File Edit View Help eo OEGERBRGAD TOOW SSHWUHBSHEAEBARVM OTSA 3 View Physical v oa ETATE MOSERIES Sample Date amp Time a cso Application Debugging Application Statistics Buffer Pool Statistics Channel Definitions Channel Initiator Status Channel Performance Cluster Queue Manager Pi Dead Letter Queue Messages Log Manager Performance Message Manager Performance MQSeries Events Page Set Statistics Queue Definitions 031706 14 25 24 03 17 06 14 0341706 14 27 24 03 17 06 14 28 24 03 17 06 14 29 24 03 17 06 14 30 24 03 17 06 14 31 24 03 1706 14 39 24 H cse 2 o 4 Percent Full Sample Retent Intvl Trigger Trigger Trigger Trigger Date amp Time Exceeded Depth Priority Date amp Interval Summary 0 0 No 0 ihis Enabled Enabled None zey 0 10 26 04 T 03 1 7 06 14 39 24 0 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 1 7 06 14 38 24 0 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 1 7 06 14 37 24 0 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 1 7 06 14 36 24 0 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 17 06 14 35 24 0 0 No 0 0 80 0 0 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 1 7106 14 34 24 0
284. ite Application Manager products is a family of products that enable and provide the monitoring tracking and analysis of Java 2 Enterprise Edition J2EE applications This technology allows the opening of the Java Black Box to see what is happening within the application The IBM Tivoli Composite Application Manager consists of a common services address space only for z OS a managing server and data collectors for WebSphere Application Server CICS Information Management System IMS WebSphere MQ The following components are used IBM Tivoli Composite Application Manager Common Services V6 00 00 Product numbers 5698 A69 5698 A70 and 5698 A71 are IBM Tivoli Composite Application Manager components optional features that exist only in a z OS environment where WebSphere Application Servers are monitored It provides Workload Manager WLM information and serves as a repository for the System Management Facility SMF records generated This repository takes copies of the SMF records and provides the basis for real time analysis IBM Tivoli Composite Application Manager for SOA V6 0 0 Product number 5698 A77 provides the function for managing the services and mediations in an SOA It provides a simple control of message traffic between Web services IBM Tivoli Composite Application Manager for Response Time Tracking for z OS V6 0 0 Product number 5698 A75 is the new version of the IBM Tivoli Monitoring for Transaction Performa
285. itoring Server Hub is managed in a different way based on the z OS environment capabilities Refer to 2 1 The IBM System z environment on page 53 for details gt Agents can be configured to connect to a secondary Tivoli Enterprise Monitoring Server to ensure availability If the Tivoli Enterprise Monitoring Server to which agents are connected becomes unavailable the agents switch to the secondary Tivoli Enterprise Monitoring Server The agents exhibit the following behavior When the communication with the primary Tivoli Enterprise Monitoring Server cannot be established agents automatically switch to the secondary Tivoli Enterprise Monitoring Server When the primary Tivoli Enterprise Monitoring Server becomes available there is no automatic fallback of agents to the primary Tivoli Enterprise Monitoring Server In our environment both the Tivoli Enterprise Monitoring Servers Remote are known by the agents and are able to handle the communication coming from the agents for which the primary Tivoli Enterprise Monitoring Server Remote is unavailable Based on the heartbeat mechanism agents try every 10 minutes which is the default value to re establish Tivoli Enterprise Monitoring Server communication when the connection fails When a secondary Tivoli Enterprise Monitoring Server is defined agents connect to the secondary Tivoli Enterprise Monitoring Server when the communication for the heartbeat update has f
286. ive 0 00 0 00 0 00 0 00 Physical Smart_Bank ED T nan T AT o aaa 5 Hub Time Mon 03 13 2006 02 43 PM Figure 4 38 Target workspace selection Server Available WLM All Service Class 9 212 128 31 SYSADMIN Chapter 4 Customizing the Logical views 221 222 5 Anew panel called Link Expression Editor is displayed Figure 4 39 The Helps are also displayed To close the Help window click any field in the left side of the window marked with a bold blue v before it KJRITMOO1I Link Wizard Define New Link WLM Details ho X 8 Symbols Y linkisEnabled V contextisAvailable B Target Workspace S F Query WLM LINK Service Class Symbols Y NODE V SERCLASS S EQ Table WLM Selected Servi V Footer V Header Link expression editor Use the Link expression editor to supply a header footer or filter for any of the data views in the target workspace Left frame Right frame The Properties tree lists the possible link symbols such as V ProcessiD shown in the example you can choose Properties a Symbols V contextisAvailable V linkisEnabled Target Workspace louen Processes E3 Symbols V NODE V ProcessiD V ProcessName ouen Serer Summary a Symbols V NODE Select a V Symbol from the E2 Target Workspacebranch in the left frame to open the Expression and Allowable Terms areas The list of terms is built from the
287. ivoli Enterprise Portal Server interface menu Chapter 2 IT en vironment of the Smart Bank showcase 99 b In the window that opens Figure 2 40 update the Hostname or IP Address parameter Because this one is usually left blank the server uses the IP address that it detects as the server s primary address If specified it defines the interface that is to be used to communicate with the Tivoli Enterprise Portal client as shown in Figure 2 40 Click OK and refresh the Tivoli Enterprise Portal Server Define TEPS Interface Ea Interface Name nps Hostname or jazia 0 Pare 9 212 128 31 Port number fi 5001 Proxy Host Proxy Port I Enable SSL for TEP Clients OK Cancel ok Figure 2 40 Tivoli Enterprise Portal Server interface parameter gt Avoiding password encryption When the integrated cryptographic service facility ICSF on z OS is not activated the Tivoli Enterprise Monitoring Server Hub is unable to decrypt the password that is sent by the Tivoli Enterprise Portal Server to identify a user Therefore the Tivoli Enterprise Monitoring user cannot be identified and the login is rejected To disable the encryption perform the following tasks a Inthe Tivoli Enterprise Portal Server edit the kfwenv configuration file located in the CNPS directory and add the following control statement USE_EGG1_FLAG 1 b Refresh the Tivoli Enterprise Portal Server gt Adding application
288. k To from the pop up menu Use a name that identifies the target workspace Use a description if you want to provide more detailed information about the link and its usage Link Identity Name Branch details Description Detailed informations for the Branch access Delete Hub Time Sat 03 11 2006 05 32 PM Figure 4 23 Link identity Giving a name to a link Server Available Smart_Bank 9 212 128 31 SYSADMIN Chapter 4 Customizing the Logical views 207 4 The next window Figure 4 24 displays three areas Inthe bottom left zone A the Target area allows you to choose the target workspace that will be the target of the link In the Navigator View the current Logical view is displayed Select any other existing view through this prompt 28 KJRITMOO01I Link Wizard Define New Link Branch details Target Select the link to workspace Select the Target Navigator item from the list You can also select a workspace from a different Navigator view S f Workspace shows multiple workspaces select the one to which you want to link If you want to change the target method click Relative See below Click Finish OR if you want to open the Link expression editor to refine the link definition click Next Target ___ Workspace Navigator View Smart_Bank Physical Re Logical wm Smart_Bank RedBook Teller imart_Bank ATM Web zBank GDPS HyperSwap
289. l banks continuing to acquire mid tier banks and mid tier banks merging to become more competitive often seeking foreign investors The banking landscape will change because it will become increasingly hard to remain competitive in the middle ground giving rise to universal banks industry specialists focusing on specific product areas community banks focusing on client relationships and the increasing importance of nonbanking entrants leveraging their existing client relationships and distribution networks including retailers and car manufacturers Chapter 1 Introducing the technical architecture of the Smart Bank showcase 7 These trends will drive growth strategies that are focused on innovation with regard to the following points vvvy Product or service innovation Client intimacy and knowledge of client groups New markets and channels Diversification strategies Figure 1 3 illustrates these points 2 zZ Product Diversification Service Innovation e Enter new product Extend into new categories products and new e Build services around markets products simultaneously e Innovate faster better H o Oo o o 6 Customer Intimacy New Markets 3 amp Market Penetration amp Channels e Increase customer loyalty Extend into new e Improve price realization customer segments e Gain wallet share Enter new e Attract new customers geographic global e Refresh products services markets e Increase geogr
290. l services sector 4 FSA 14 FSDM 4 physical implementation 4 G garbage collection 139 GDPS 21 281 Geographically Dispersed Parallel Sysplex See GDPS Global Location Broker 82 H Hardware Management Console See HMC HMC 272 HTTP session 140 l IBM AIX 17 53 69 125 274 IBM BladeCenter 18 278 SUSE Linux V9 281 IBM OMEGAMON 124 navigation subtree 128 physical tree 149 IBM Redbooks Web site 286 287 IBM System z 23 IBM System z9 environment 258 278 platform 271 utilization 278 IBM System z9 109 machine 21 IBM Tivoli 3 IBM Tivoli Composite Application Management 24 125 260 IBM Tivoli Composite Application Manager V6 3 IBM Tivoli Monitoring 3 121 122 274 agent 24 268 component 26 core part 40 infrastructure 26 122 management infrastructure 49 physical tree 130 product 122 services foundation 26 solution 24 system 128 system administrator 124 system management infrastructure 35 user guide 141 view 281 Independent Solution Vendor See ISV infrastructure perspective 10 user platform 10 infrastructure solution 2 integration hub 266 interface technique 262 Internet channel 12 261 IP communication 39 hyper socket 39 ISV 4 J J2EE 56 139 261 Java Message Service See JMS Java Virtual Machine See JVM JMS 112 149 261 JVM 21 L link absolute link 203 anchor 240 relative link 211 wizard 205 Linux OS 274 local location broker 82 local remote Tivoli Enterprise Management Server Hub 33
291. lations activity Q Rapidly develop and deploy E Sirenattien operation new products O Simplify business structure g P controls Figure 1 2 Current drivers of spending by banks 6 Infrastructure Solutions Building a Smart Bank Operating Environment 1 1 4 The banking sector s future key business drivers A research conducted by the IBM Institute of Business Value among CEOs of leading institutions indicates significant challenges at different levels in the retail banking industry as we look ahead to the year 2015 The challenges include the following gt At the client level Clients will become increasingly individualistic For the financial institution the capability to make intelligent client segmentation becomes a key capability as it becomes more difficult for banks to pin point broad groups of clients This business intelligence allows institutions to target their products more carefully to specific segments Clients will also become more fickle with regard to brand loyalty when their ability to access more information about different competitive products across the market increases They will increasingly control their relationships with financial institutions making the rapid creation of products aligned to the requirements of client groups another key ability of the financial institution gt At the financial institution level Financial institutions will become increasingly consolidated with large internationa
292. le oy 2 blade6 10 1 1 129 Applications Hosts Yes Unavailable IBM PowerPC CHRP Computer Machine Type 0x0 10 4 4 AS1HTTPdp UAGENTOO 1AA ASNN UAGENT 10 11 13 101113 Unknown No Unavailable Unavailable blade 10 1 1 130 Applications Hosts Yes Unavailable IBM PowerPC CHRP Computer Machine Type 0x0 G Production Net SNMP MANAGEROO EH MANAGED NODES blade8 10 1 1 131 IP Node No Unavailable Unavailable BLADES 10 1 1 132 IP Node No Unavailable Unavailable EH MIBNODATA MIBSTATUS blade10 10 1 1 133 IP Node No Unavailable Unavailable blade11 10 1 1 134 IP Node No Unavailable Unavailable blade12 10 1 1 135 IP Node No Unavailable Unavailable 10 1 1 136 10 1 1 136 IP Node No Unavailable Unavailable 10 1 1 137 10 1 1 137 Unknown Unknown No Unavailable Unavailable 10 1 1 138 10 1 1 138 Unknown Unknown No Unavailable Unavailable Fa iii aaa wer re To i Figure 3 46 TEP Production network details Chapter 3 Using Physical views 179 In the managed system SB showcase SNMP MANAGEROO contains one attribute group containing data the others are empty This managed system is created by the Universal Agent based on the information provided in the kumlist_Smart Bank showcase def file This file contains the managed node lists Hot Lists and is created during the setup of the SNMP data provider The attribute group contains useful information regarding the availability and response time of nodes participating in the Smart Bank environme
293. le 2 16 shows a partial static list of hosts belonging to the Smart Bank environment Refer to BM Tivoli Monitoring Agent User s Guide SC32 9459 for details about defining the lists based on the resource filter Example 2 16 Partial listing of the kumslist_Smart Bank showcase def LISTNAME Smart Bank showcase blade2 blade3 blade4 Intl 1nx3 1nx4 1nx5 1nx7 5 Recycle the Universal Agent 6 Load the Hot Lists by issuing the following command kumpcon loadlist kumslist_Smart Bank showcase def 118 Infrastructure Solutions Building a Smart Bank Operating Environment Figure 2 48 displays a window showing the TEP output The default report is customized partially for a better understanding of the published data n 2 Physical B E Name Address Node Status Status TimeStamp Current ResponseTime ms M emeses il blade3 production local 10 1 1 126 2006 03 14 18 48 20 000 2000 a Fay Universal Agent blade4 production local 10 1 1 127 2006 03 14 18 48 45 000 0 By 1011 131 SNMP MANAGEROO blade5 production local 10 1 1 128 2006 03 14 18 49 10 000 0 G k 10 1 1 431SNMPdp UAGENTOO blade6 production local 10 1 1 129 2006 03 14 18 49 10 010 0 LET Production Net SNMP MANAGEROO blade7 production local 10 1 1 130 2006 03 14 18 49 10 020 0 EH MANAGED NODES blade8 production local 10 1 1 131 2006 03 14 18 49 35 000 0 EH MBNODATA blade11 production local_ 10 1 1 134 2006 03 14 18 43 20 000 0 L mestatus ba01 productio
294. le application are defined the same situations used in the case of system programmers may be attached to the Logical view OMEGAMON for WebSphere Application Server Summary This product provides powerful functions for the operations community as well as for application managers to keep track of the performance of the components they are in charge of The agents are installed on z OS and Linux where the WebSphere Application Server is running on Because both the platforms are measured almost identically and the output is almost the same this product provides real value to the Smart Bank showcase and their requirements for platform spanning cross system monitoring and subsystem monitoring 148 Infrastructure Solutions Building a Smart Bank Operating Environment The monitor for WebSphere provides information about the subsystem and the application running inside It provides information about the incorporated service providers and the interfaces such as J2EE Connector architecture JCA Java Database Connectivity JDBC Java Message Service JMS and CICS Transaction Gateway CTG In the new IBM Tivoli Composite Application Manager for WebSphere a deep dive analysis mechanism has been added 3 2 3 IBM OMEGAMON for WebSphere MQ The OMEGAMON for WebSphere MQ agent enables in depth monitoring of the IBM MQSeries subsystem its implementing objects and the messages currently contained in the MQ system OMEGAMON for WebSphere M
295. led 0 No COREBANK LOCAL QUEUE FO CRB SRVING ALS Alias Normal nia Yes Enabled 0 No CRB XCTING Local Normal Predefined 03 15 06 13 41 34 Yes Enabled 0 Yes 4 COREBANK EXTENDED CONT CSQ1 BA01 MQESA Figure 3 31 Queue definitions Chapter 3 Using Physical views 163 3 The Queue Statistics Summary is displayed as shown in Figure 3 32 This window shows that there is currently no activity on the CICBEP QLOCAL1 queue All the metrics related to the queue activity such as Total Opens Input Opens Output Opens Current Depth Full are set to zero Before starting any workload on this queue drill down one more time to view the statistics information pertaining to CICBEP QLOCAL1 Click the blue anchor next to the queue name File Edit View Help ea EXER RAGA SOCOMO SQSWRBRBEAARTSFBE E View Physical v De hE Sao E MQSERIES a Number of Queues 600 a y csa Application Debugging C Monitored Queues B Open Queues Application Statistics Number Queues with High Depth Buffer Pool Statistics M Number of Queues Get Inhibited Channel Definitions CI Number of Queues Put Inhibited Channel Initiator Status E A a Channel Performance 0 Cluster Queue Manager Dead Letter Queue Messages ull Queue Utilization Log Manager Performance i Message Manager Performance MQSeries Events Page Set Statistics Queue Definitions r Status 400
296. li Enterprise Monitoring Server gt Each agent generates its own heartbeat Table 2 4 shows the heartbeat parameters defined in our distributed environment to detect when an agent becomes unavailable In order to avoid heartbeat overflow only OS agents have a heartbeat value that is lower than the default value Table 2 4 Heartbeat parameters Windows Tivoli Enterprise CTIRA_HEARTBEAT 3 KBBENV Monitoring Server UNIX Tivoli Enterprise CTIRA_HEARTBEAT 3 kbbenv ini Monitoring Server a Add a parameter to the ux ini file before the agents are configured Otherwise they are not invoked when the agents are started b Add a parameter to the Iz ini file before the agents are configured Otherwise they are not invoked when the agents are started Note Add or modify the KDC_HEARTBEAT parameter to the agents ini files Otherwise the configuration file are not updated 2 2 7 Operating system specific considerations After installing the OS on the servers dedicated to run the IBM Tivoli Monitoring components such as Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server ensure that the systems have the suitable parameters to run IBM Tivoli Monitoring efficiently Even with powerful hardware the system may face performance issues due to a bad setup of the OS parameters 92 Infrastructure Solutions Building a Smart Bank Operating Environment Tuning the Windows operating system After completing the OS installation per
297. ling environments where a large number of agents more than 200 agents connect to one Remote Tivoli Enterprise Management Server it is useful to set up a dedicated backup Tivoli Enterprise Management Server Remote that is used only when the primary Tivoli Enterprise Management Server Remote fails gt z OS assumptions On each z OS partition there is one Tivoli Enterprise Management Server Remote at all times Between the Tivoli OMEGAMON components z OS internal communication is carried out only through the Systems Network Architecture SNA All Tivoli OMEGAMON products running on z OS communicate with their local Tivoli Enterprise Management Server Remote only If they require communication with the Hub Tivoli Enterprise Management Server it is carried out through the Remote Tivoli Enterprise Management Server gt No agents are connected directly to the Tivoli Enterprise Management Server Hub at any time Avoiding direct connections between the agents and the Tivoli Enterprise Management Server Hub keeps the data traffic to the Tivoli Enterprise Management Server Hub as low as possible The restart time of the Tivoli Enterprise Management Server Hub after an emergency restart or switchover works faster because There are few data sets files to recover The agents communication with the Tivoli Enterprise Management Server Remote is still up and running Only a few Remote Tivoli Enterprise Management Servers mu
298. llowing multiple components as shown in Figure 1 8 IBM Tivoli Enterprise Managing Server IBM Tivoli Enterprise Portal Client IBM Tivoli Enterprise Portal Server IBM Tivoli Enterprise Managing Agent IBM Tivoli Data Warehouse V2 1 IBM Tivoli Enterprise Console vvvvvy 2 Although not shown in Figure 1 8 the Tivoli Enterprise Managing Agents have the ability to connect to the Tivoli Enterprise Managing Server Hub and are not required to go through the Tivoli Enterprise Managing Server Remote Chapter 1 Introducing the technical architecture of the Smart Bank showcase 25 26 The following sections provide a brief description about each of these components For detailed descriptions about the IBM Tivoli Monitoring V6 components refer to Getting Started with IBM Tivoli Monitoring 6 1 on Distributed Environments SG24 7143 To get up to date information about the platform support matrix for IBM Tivoli Monitoring V6 1 visit the following Web site http www 306 ibm com software sysmgmt products support Tivoli_Supported Platform s html Tivoli Enterprise Managing Server The Tivoli Enterprise Managing Server is the most important component within the IBM Tivoli Monitoring Services foundation All the other architectural components depend directly on the way this functions The Tivoli Enterprise Managing Server acts as a collection and control point for alerts received from agents and collects their performance and availability data
299. loaded from the Web site as shown Figure 2 36 and click Next Installer olx Enter your Tivoli Monitoring installation directory CAIBMuTM Browse Enter the location where your installable media is located Caitso kits kwe_websphere_v01 30_app_support_for_itm_v610 Browse InstallShield i Cancel Figure 2 36 Application support for WebSphere Application Server distributed Directories location Back d Usually the installation program detects that the installation is executed on a Tivoli Enterprise Monitoring Server and the check box against Tivoli Enterprise Monitoring Server is selected Click Next Infrastructure Solutions Building a Smart Bank Operating Environment e Select the application for which you want to install the application support files Click Next f The Installer Figure 2 37 displays the installation actions that are performed Click Next amp Installer iof x The following installation actions will be performed Stop TEMS Add TEMS support for OMEGAMON XE for Websphere Application Server on Distributed Systems Version 01 30 00 00 Start TEMS Configure TEMS support for OMEGAMON XE for Websphere Application Server on Distributed Systems Version 01 30 00 00 Stop TEMS Start TEMS InstallShield Back Cancel Figure 2 37 Application support for WebSphere Application Server distributed Installation stages g After the appl
300. ls Servlet sessions Dynamic cache Workload management Thread pools Application server some of the columns Perform the following tasks to set the instrumentation levels in order to collect the performance data on IBM WebSphere V6 0 ona RwWND 7 8 Open the URL http lt was_server gt 9060 admin Enter your account Inthe left frame select Servers Select Application Servers Inthe right frame choose the application server whose configuration you want to modify Select an initial specification level that is higher than None for Performance Monitoring Infrastructure Click the Apply button To save the update click the Save hyperlink Preparing the instrumentation control file for workloads An agent can be configured to collect the workload analysis data including statistics about heap usage and garbage collections The following Tivoli Enterprise Portal workspaces require the collection of workload analysis data All workloads Selected workload delays Longest running workloads Data sources HTTP sessions JMS summary In flight workloads To implement this instrumentation perform the following tasks Edit the file kweiuser xml located in the lt CANDLEHOME gt config directory Note For a production environment where a minimum overhead is expected review carefully the parameters used for the instrumentation Run the Candle class loader setup script lt CANDLEHOME gt bin setu
301. m z9 platform is clearly well positioned to provide Chapter 5 Scenarios and use cases 271 gt The use of the new IBM System z Application Assist Processor ZAAP Java workload specific processors on IBM System z9 makes the cost of running a Java workload on the platform much more attractive In the case of our retail bank this allows them to address the key aspects of revenue growth and integration identified at the beginning and helps them rapidly create new products reducing the time to market while leveraging what they already have After isolating the selected key core system functionality as services we selected the technical binding to suit the type of integration required By using processes and the Process Choreographer WBI SF with WebSphere V5 and Process Server with WebSphere V6 new business functions can be created quickly and flexibly combining core system functionality with other functionality that can be exposed with WSDL definitions Multiple core systems and potentially external services can be integrated together to create what are called composite applications This can also be referred to as services The Process Choreographer or Process Server handle hierarchies of processes and services 5 2 Optimization of IT resources On Off Capacity on Demand 272 In this proof point we show how our operational environment is being stretched from a resource utilization point of view We inject a workload that is unusually
302. mance Message Manager Performance MQSeries Events Page Set Statistics Queue Definitions lt T E g Physical K3 D Active Channels M inactive Channels M indoubt Channels M Active Sender Channels Olnactive Sender Channels M Active Serer Channels Diinactive Server Channels H Active Receiver Channels M inactive Receiver Channels Wcurrent Requesters M inactive Requesters Server Connections ger Summary Start Name Name Subsys Date amp Time CSQ1 BA01 CSQ1 CSQIMSTR 03 15 06 13 41 05 Active MVS 0 E eed CSQ1 BA01 MQESA Figure 3 30 Navigating to MQSeries queue information 162 Infrastructure Solutions Building a Smart Bank Operating Environment 2 Let us now look at the queue definitions To access more details about the CICS Business Event Publisher activity click the Queue Definitions tab The Queue Definitions Summary is displayed as shown in Figure 3 31 Several queues are defined in this window The queue called CICBEP QLOCAL1 is the one we look at in our case It is defined as a local queue Drill down to this particular queue by clicking the blue anchor next to the queue name Before performing this action in order to view the queue statistics click the Queue Statistics tab in the Navigator view File Edit View Help na WETT AAEE Physical v E View CET Eim n e a E RE DEEE n En r E EA E g
303. mands to extract the patch for the Linux or the AIX environment For Linux Intel run the following command tar xvf lt patch_dir gt weli4005 tar For Linux on IBM System z run the following command tar xvf lt patch_dir gt wels4005 tar 110 Infrastructure Solutions Building a Smart Bank Operating Environment For AIX run the following command tar xvf lt patch_dir gt weaix4005 tar 4 Run the class loader setup script lt CANDLEHOME gt bin setupCand eWAEnabler sh 5 Restart the application servers that were stopped in step 2 on page 110 lt WebSphere Application Server_DIR gt bin startServer sh lt server_name gt 6 Update the lt CANDLEHOME gt config kwe xml file In order to support WebSphere V6 0 the agent s configuration file kwe xml must be set up as follows The parameter WebSphere Application ServerAppServerRoot indicates the directory path name to the location where the WebSphere Application Server product is installed Anew parameter called WebSphere Application ServerlnstanceRoot indicates the directory path name to the profile to be monitored by the agent Note WebSphere V6 0 contains at least two separated environments The first one contains only the binary files The others called profiles contain a run time execution environment that includes configuration files the default location for the deployed applications logs and other data All the profiles on a machine can share the same bin
304. mes The MANAGED NODES alert is also a link to the Physical view In the centre is the Blade Center environment with the monitoring nodes Linux branch nodes and Siebel Business Analytics node To the right is the remote monitoring of the response times reported to the different nodes in the network They are from left to right gt Linux HTTP server on an Intel blade gt Linux HTTP server on z VM gt AIX Web server on a Power4 blade gt The IBM Web site which shows the long response time because access was denied by the firewall To return to the Operations view the Back icon in the toolbar on top of the page is selected 5 2 4 IBM System 29 109 utilization Obtaining a Logical view of the IBM System z9 109 utilization is the main challenge for this proof point The views discussed earlier are good for further discussions on the environment and help build a picture of the infrastructure deployed and the capability of IBM Tivoli Monitoring V6 The project development region used for this book is powered by an IBM eServer zSeries z990 whereas our target production platform is IBM System z9 109 Consequently all the Logical view diagrams reference IBM System z9 109 whereas the actual machine being monitored is the z990 which did not have any ZAAP or IFL processors defined We show more power and a greater variety of processors in our production environment However the principles and goals remain the same Figure 5 15 provides
305. n Linux Database IBM DB2 on z OS for both our operational databases based on the Financial Services Data Model for Fidelity Corebank and based on banking data warehouse for our analytical database Central database Using a central database architecture in order to benefit from data sharing architecture with the cluster Parallel Sysplex the speed of access and data propagation and the other key qualities of the IBM System z platform security and high availability Facilitating the flexible integration of new and existing products contributing to a reduction in time to market Systems management IBM Tivoli Monitoring V6 because it allows monitoring and managing of all the environments and subsystems and creates Logical views of this information for an end to end Enterprise view 1 3 The architectural components What is the architecture of the Smart Bank showcase and how are the components of this architecture connected together This section briefly describes the environment to be monitored and managed by IBM Tivoli Monitoring In our case we chose three key use cases proof points to use in the showcase with the newly created Physical and Logical views These views cover a wide cross section of IBM Tivoli Monitoring functionality and represent new views for the showcase They are used to go into more details with regard to specific proof points Chapter 1 Introducing the technical architecture of the Smart Bank showcase 17 1
306. n invokes the core system proprietary mechanism by invoking the method APICALL We re engineered the interface to use Java Message Service JMS and connection pools to put to the WebSphere MQ queue instead of using the native Fidelity Java classes with the MQ API commands We did this to adopt a more open approach and make the interface more efficient Using GET WAITs we created a synchronous implementation of this asynchronous mechanism The core system uses its standard technique to launch the client Information Control System CICS transactions using Dynamic Transaction Routing across the ClCSplex Client The Struts framework action beans do not lend themselves well to the creation of Web services The typical arguments for the Struts action beans are not particularly useful for a Web service call HTTP request HTTP response Consequently we created a new set of specific action beans that receive arguments corresponding to the input parameters for the core system API delivery system arrangement number user ID amount and so on We then created the Web service from these new action beans Integration The same as step 1 Chapter 5 Scenarios and use cases 261 Service orient Client A completely new client This client uses an action bean to call the ed invocation Java bean proxy through a normal Java call that is formed during the of core system creation of what is called an Enterprise service The financial operatio
307. n local Status TimeStamp Current ResponseTime ms 10 1 1 126 10 1 1 127 10 1 1 128 10 1 1 129 10 1 1 130 10 1 1 131 10 1 1 134 10 1 1 20 10 11 21 10141 29 1011 61 Intl production local 2006 03 14 18 48 20 000 2006 03 14 18 48 45 000 2006 03 14 18 49 10 000 2006 03 14 18 49 10 010 2006 03 14 18 49 10 020 2006 03 14 18 49 35 000 2006 03 14 18 43 20 000 2006 03 14 18 43 45 000 2006 03 14 18 43 45 010 2006 03 14 18 44 10 000 2006 03 14 1 2000 lojojojojojojojojojo 10 1 1 71 Inx3 production local 2006 03 14 1 ol i 10 1 1 63 Inx4 production local 2006 03 14 18 45 10 1 1 64 MIBNODATA Inx5 production local 2006 03 14 18 46 03 000 10 1 1 65 MIBSTATUS Inx production local 2006 03 14 18 46 30 000 2000 10 1 1 67 NETSUMMARY blade2 production local 2006 03 14 18 46 57 000 2000 10 1 1 125 NETWORK ROUTER TRAP 2006 03 14 18 47 53 000 1000 Figure 3 47 TEP Availability of the Smart Bank nodes 180 Infrastructure Solutions Building a Smart Bank Operating Environment Customizing the Logical views The objective of a Logical view is to select and reorganize parts of the physical data in order to visualize the status of the physical and logical elements involved in each of the applications This chapter discusses the f
308. n local 1011 20 2006 03 14 18 43 45 000 a L nersunmary ba02 productiontocal 10 11 21 2006 03 14 18 43 45 010 o E NETWORK vipa production local 10 1 1 29 2006 03 14 18 44 10 000 0 E ROUTER ina production local 10 1 1 61 2006 03 14 18 44 35 000 _ 0 B TRAP Inti production local 10 1 1 71 2006 03 14 18 45 01 000 1000 Ja SmartBank SNMP MANAGEROO Inx3 production local 10 1 1 63 2006 03 14 18 45 38 000 0 fle MANAGED NODES Inx4 production local 10 1 1 64 2006 03 14 18 46 03 000 0 LE MBNODATA Inx5 production local 10 1 1 65 2006 03 14 18 46 30 000 2000 LE mestaTus Inx production local 10 1 1 867 2006 03 14 18 46 57 000 2000 E NETSUMMARY blade2 production local 10 1 1 125 2006 03 14 18 47 53 000 1000 By NETWORK E ROUTER Figure 2 48 TEP Monitoring the servers availability Monitoring the Uniform Resource Locators with the Universal Agent A simple solution to monitor the availability and the response time of the Uniform Resource Locator URL requests to the Smart Bank Web servers must be implemented The HTTP data provider available in the Universal Agent provides the ability to monitor URLs in order to diagnose the availability and response time of the remote Web servers Getting Started with IBM Tivoli Monitoring 6 1 on Distributed Environments SG24 7143 explains the configuration of the data provider in detail After installing the U
309. n order to feed the financial settlement systems 1 2 2 Reference architectures and models We had a number of IBM reference architectures and models at our disposal including the following gt On demand infrastructure solutions reference architecture gt IBM Service Oriented Architecture SOA gt IBM Financial Services Architecture FSA gt IBM Component Business Model CBM view of retail banking gt IBM Information FrameWork Critical Business Processes Banking Data Warehouse and Financial Services Data Model 14 Infrastructure Solutions Building a Smart Bank Operating Environment 1 2 3 Functional requirements The high level functional requirements we looked for included those functions that support the proof points and fall under the category of business solutions Table 1 7 describes the most common functional requirements Table 1 7 High level functional requirements Functional Description requirement Core retail banking A fully implemented and functional core retail banking system to simulate application the sort of applications that most retail banks have running at the heart of their operation These are the operational account management systems that provide the retail products to be used by the channels and record client involvement across the banks portfolio in current accounts savings accounts deposit accounts loans and other credit facilities for the general public and for specific client s
310. n order to host an application that is accessible to the users gt Tivoli Enterprise Management Agent for IBM Tivoli Composite Application Manager WebSphere Application Server The Tivoli Enterprise Management Agent for IBM Tivoli Composite Application Manager WebSphere Application Server is an agent that is fully integrated into the IBM Tivoli Monitoring V6 system management infrastructure It gets all the required data from the data collector running inside the WebSphere Application Server instance gt IBM Tivoli Composite Application Manager WebSphere Application Server data collector The data collector for IBM Tivoli Composite Application Manager WebSphere Application Server runs inside each monitored WebSphere Application Server instance It reports its data to the managing server and the Tivoli Enterprise Management Agent if present ITCAM WAS Client TEP Client ITCAM WAS Managing Server Monitoring A eal TEC a TEMS ea Remote H TEMS Remote BA TEMS kN TEMA TEMA for TEMA Windows Databases Universal ITCAM WAS DC WAS Figure 1 10 IBM Tivoli Composite Application Manager for WebSphere and its components 30 Infrastructure Solutions Building a Smart Bank Operating Environment In this book only the use of the Tivoli Enterprise Management Agent for IBM Tivoli Composite Application Manager WebSphere Application Server is described Deep dive analysis of WebSphere Appl
311. n the service oriented architecture The information flow between the services and the related response times and the failure occurrences become visible The agent is installed only on the z OS where the SOA services are implemented All the other systems are left untouched by this agent Because the SOA services are application oriented there are only a few specific system rules that are applicable to this kind of agent The system operation can track only the accumulation of abnormal ends in SOA calls 138 Infrastructure Solutions Building a Smart Bank Operating Environment Monitoring values such as response times or number of messages is application specific These values must be applied in application related rules In most cases application specific rules are not attached to the physical tree Such situations are typical when implementing the Logical view of an application within the monitoring environment 3 2 2 IBM OMEGAMON for WebSphere Application Server Because OMEGAMOM for WebSphere on distributed systems and OMEGAMON for WebSphere on z OS have more or less the same functionality the two products are described together These products are replaced by IBM Tivoli Composite Application Manager for WebSphere Application Server described in 3 2 1 IBM Tivoli Composite Application Manager for Service Oriented Architecture on page 132 Therefore the differences between the functions are no longer visible under IBM Tivoli Monitoring
312. n time environment is used in conjunction with our sharing run time environments To load all the products used by the sharing run time environment gt One run time environment type SHARING named BAO1 To allocate our private libraries for the z OS image BA01 To define and configure the Tivoli Enterprise Management Server Remote on BAO1 To install and configure all Tivoli Monitoring for Applications on BAO1 gt One run time environment type SHARING named BAO2 To allocate our private libraries for the z OS image BAO2 To define and configure the Tivoli Enterprise Management Server Remote on BAO2 To install and configure all Tivoli Monitoring for Applications on BAO2 gt One RTE type SHARING named HUB To allocate our private libraries for the moveable HUB It is not specific to one z OS image To define and configure the primary HUB Tivoli Enterprise Management Server on BAO1 or BA02 Note No agents are installed and configured in this run time environment type Figure 2 11 displays the run time environments defined for the Smart Bank showcase RUNTIME ENVIRONMENTS RTEs Actions A Add RTE B Build libraries C Configure L Load all product libraries after SMP E D Delete U Update V View values Z Utilities Action Name Type Sharing Description BASE BASE RTE BASE for TIVOLI Smart Bank Sysplex BAPLEX BAO1 SHARING BASE RTE SHARE for TIVOLI Smart Bank LPAR BAO1 BA02 SHARING BASE RTE SHARE
313. nager This is the only area where these servers are visible gt In area 2 the default IBM Tivoli Monitoring V6 enterprise console is displayed gt Pal g ax x a yo se QO amp Fie Edit View Favorites T Address http 9 212 128 31 1920 enp kdt EJ co ay Tivoli Enterprise Portal File Edit View Help amete Aa view Physical nea GEELSE 2004 SBSH RBRTHARF FBeOSA ee w Ge X Total Events 13 item Filter Entg So fis Storage Subsystem A Situation Name Display iter Source Impal NT_Log_Space_Low Security Primary BLADE8 NT Sg BA01L KWWA KS3_Vol_Free_Space_Pct_Warning TIVSREMT BAO1 STORAGE E Sms Sage Gr EH Agent Events I KS3_Vol_Free_Space_Pct_Warning TIVSREMT BAO2 STORAGE SMS Storage Gr E Application Server Error Logs Open NT_System_Total_Interrupts Primary BLADE1 2 NT E Processor Application Trace Files Open NT_System_Total_Interrupts Primary BLADES NT EH Processor ii aE F oK MOSeries_Queue_Manager_Problem CSQ2 BADT MQESA E Queue Manfger t A AACELL BBOCOD AASRIF Open MQSeries_Queue_Manager_Problern WUMA BAO1 MOESA EH Queue Maragel m BACELLA BAOCD01 BASF C Open Crypto_Internal_Error BAPLEX BA01 MVSSYS at i Application Server Ir Open MQSeries_Queue_Manager_Problem CSQ1 BA02 MQESA EH Queue All workloads Open MQSeries_Queue_Manager_Problem WJMA BAD2 MQESA 5 suspected
314. nce TMTP for z OS This product captures detailed performance data for all e business transactions IBM Tivoli Composite Application Manager for CICS Transactions V6 00 00 Product numbers 5698 A69 and 5698 A75 are the data collectors for CICS transactions They help profile the composite transactions that originate in J2EE and branch off to CICS IBM Tivoli Composite Application Manager for WebSphere on z OS V6 00 00 Product number 5698 A71 is a data collector for WebSphere Application Server on z OS It allows J2EE administrators application support analysts or subject matter experts to profile composite transactions IBM Tivoli Business Systems Manager V3 1 0 Product number 5698 A21 is an object oriented systems management application that provides monitoring status and event management of the technical resource application and subsystems It manages collects and correlates information within the z OS environment from a variety of sources Note IBM Tivoli Composite Application Manager for Response Time Tracking IBM Tivoli Composite Application Manager for CICS transaction IBM Tivoli Composite Application Manager for WebSphere on z OS and Tivoli Business System Manager were not used for this project Infrastructure Solutions Building a Smart Bank Operating Environment Figure 2 5 shows the monitoring products and tools used in this project Montpellier Firewall router Pa Z990 B16 Oz OS RMF WL
315. nches a Logical view user must drill down to obtain detailed information in order to understand from which part of the branch the incident comes from The process involved Figure 4 19 shows the source workspace E Smart_Bank 9 212 128 31 SYSADMIN Jee File Edit View Help b E atIIyag hx EEE Channel Access Points zBank GDPS HyperSwap Channel Interaction Core Systems amp Enterprise Business integration Processing Branch PROCESS SOA Hub Time Sat 03 11 2006 06 08 PM Server Available Smart_Bank 9 212 128 31 SYSADMIN Figure 4 19 Absolute link source workspace Enterprise view Chapter 4 Customizing the Logical views 203 Figure 4 20 shows the target workspace that is already defined BOORI h X o olg Channel interaction Access Integration Channel Access Points Intranet Branch Server Web Server WebSphere HTTP Wane Linux Blade BE esl Branch Figure 4 20 Absolute link target workspace Branch view Enterprise Integration Core Systems amp Business Processing EJB Container WebSphere App Server Linux Blade 204 Infrastructure Solutions Building a Smart Bank Operating Environment m a The purpose of this new link is to jump from the branch specific icon to the branch specific workspace named Teller on the graphic view To build this link perform the following tasks 1 Right click the icon in the graphic source v
316. nd and style setup window Return to the graphic display The icons have changed and have been replaced by images as shown in Figure 4 63 on page 242 4 5 4 The Smart Bank showcase css style file The TEP uses css files This section focuses on the use of these files by the Smart Bank showcase team In order to build its own style the Smart Bank showcase team first gathered some icons gif and jpg The images were then modified to fit the following parameters gt Large icons created as close to 32 x 32 pixels as possible gt Small icons created as 20 x 20 pixels gt GIFs may have transparent backgrounds and may be animated An image that is larger or smaller is resized to these dimensions automatically and may look distorted Also the image retains the proper proportions only if it is of the same height and width In the directory named T IBM ITM CNB classes candle fw resources style user a file named Smart Bank showcase css is created using Windows Notepad The purpose of the css file is to perform the following functions Define the base style Set up large or small icons Place the label Set up the color of the label Assign an image to each node name used YYYY Y The content of the Smart Bank showcase css file is shown in Example 4 3 Example 4 3 The Smart Bank showcase css style file Gimport base css import baseLargelcon css Gimport baseNodeLabelBottom css node foreground white
317. ndent Logical Unit LU to be used in this process gt KDCFC_MODE identifies the LOGMODE name used The same name is found in the LOGMODE specification of the KDCFC_Alias APPL definition gt KDCFC_TPNAME is the Transaction Processing Name gt KDEII OpenTransportProvider is the last message that indicates that the SNA transport message is operational Many OMEGAMON processes build and query a list of possible Tivoli Enterprise Monitoring Server addresses called server list This server list contains Local Location Broker LLB and Global Location Broker GLB gt The LLB entries of the server list are derived from the GLB gt The GLB entries of the server list are built from the content of the KDCSSITE member of RKANPAR Example 2 5 displays the server list for the Tivoli Enterprise Monitoring Server Hub Example 2 5 Server list for a Tivoli Enterprise Monitoring Server Hub KDE1I_ OpenTransportProvider Transport opened coml sna pipe 008B KDE1I_OpenTransportProvider Transport opened socket ip pipe 00A2 NewSDB LLB entry 1 is sna PSSCBA TIVHUBLB CANCTDCS SNASOCKETS 135 NewSDB LLB entry 2 is ip pipe 10 1 1 29 2018 NewSDB GLB entry 1 is sna PSSCBA TIVHUBLB CANCTDCS SNASOCKETS 135 NewSDB GLB entry 2 is ip pipe 10 1 1 29 2018 NewSDB GLB entry 3 is sna PSSCBA TIVHUBLB CANCTDCS SNASOCKETS 135 NewSDB GLB entry 4 is ip pipe 10 1 1 29 2018 KDSNC004 Bind of local location broker comple
318. near operational volumes and utilization We provided an analytical database developed in Montpellier based on the Information FrameWork IFW Banking Data Warehouse BDW to other IBM teams This book is the first piece of external collateral to be created from the project We were able to leverage the resulting database from an Independent Solution Vendor ISV Fidelity benchmark conducted in Montpellier This plus the agreement with the ISV to use their application software to represent the core system in our retail bank launched the project As the project grew to cover new business proof points we engaged other ISVs to provide the application functionality to highlight our infrastructure The following is a list of the ISVs and IBM assets engaged in the Smart Bank showcase project gt Fidelity Corebank V4 2 a real time retail banking application based on a physical implementation of the Financial Services Data Model FSDM that forms the foundation of the Information FrameWork IFW model from IBM Software Group SWG in Dublin gt Fair Isaac TRIAD V8 0 a risk calculation engine gt Siebel Business Analytics V7 7 1 a business intelligence application gt Stonesoft Stonegate V2 2 7 a Linux firewall security software gt IBM Banking Data Warehouse BDW from IFW built on the FSDM data model gt IBM PSSC Montpellier resources experts hardware and software 4 Infrastructure Solutions Building a Smart Bank
319. network topology several servers are equipped with multiple network interface cards NIC There is a necessity to easily trace the network connections between the miscellaneous components Following are the selected protocols for Tivoli Enterprise Monitoring Server and Tivoli Enterprise Monitoring Agent communications gt IP PIPE This is the name given to the TCP protocol used for the Remote Procedure Call RPC packet transmission This connection oriented transport layer provides reliable and sequenced stream data delivery Note On a single system IP PIPE can share a maximum of 16 processes per listening port This limitation occurs when running large amounts of Tivoli Enterprise Monitoring Agents on one physical system such as running more than 16 Universal Agents or more than 16 Database Agent instances Any processes above 16 will fall back to using the IR UDP protocol It is however not a limitation if the total amount of Tivoli Enterprise Monitoring Agents connect to one Tivoli Enterprise Monitoring Server For details regarding the IP PIPE protocol refer to Getting Started with IBM Tivoli Monitoring 6 1 on Distributed Environments SG24 7143 UDP PIPE This is a connectionless datagram protocol User Datagram Protocol UDP performs faster and uses fewer resources In large environments if there is no security constraint this protocol can be implemented as the first protocol for communication between Tivoli Enterprise
320. ng Environment Use of open standards Using open standards where possible to assist the flexibility and to aid integration and interoperability of the interfaces and the independence of the platforms platform independence Use of industry models IBM Information FrameWork Critical Business Processes banking data warehouse and Financial Services Data Model Core retail banking Fidelity Corebank V4 2 a modern real time core retail banking system application based on our industry model and proven to adhere to many of our nonfunctional requirements This choice was assisted by the availability of the database Prescribed the Customer Information Control System CICS as our transactional subsystem running on z OS instead of the Information Management System IMS Business intelligence Siebel Business Analytics V7 7 1 is a good candidate for an analytics engine This was run on an UNIX platform and implemented on IBM WebSphere on IBM AIX on a POWER4 blade It has Open Database Connectivity ODBC access to our analytical database Credit risk Fair Isaac TRIAD V8 was a good candidate for our credit risk calculation engine and ran on z OS performing the calculations in periodic batch mode Security firewall Stonegate Stonesoft in a Linux firewall that we deployed on a standalone Linux logical partition LPAR and on Linux machines under IBM z VM Transactional CICS and WebSphere Application server on z OS with WebSphere ND subsystem o
321. ng data warehouse by writing this information to a queue This will be present in the same unit of work as the channel transaction A second unit of work under a different service class quality of service ranking that is lower and not as critical then picks up the message and updates the banking data warehouse when there are sufficient machine resources to do so During the demonstration at high volumes this remains virtually real time Figure 1 6 shows the system context diagram and illustrates how these concepts are used in the integration hub in order to integrate with the analytical database as well This system context diagram looks a little more like the IBM SOA reference diagram that we used as a base for our SOA model diagram in the Tivoli Enterprise Portal Channel Browser based Browser based simulations Internet client Internet client If If it HTTP HTTP HTTP 1 Channel Branch Server Business server Analytics Si ae Web services L_ lt ee Integration Hub client aed o a E Process Tivoli 9 Services Core System Enterprise BPEL FSDM Portal i HTTP Browser or client based Internet client Figure 1 6 System context diagram 20 Infrastructure Solutions Building a Smart Bank Operating Environment Risk and compliance Fair Isaac s Tria
322. ng database warehouse database which is located on another DB2 for z OS subsystem Note In our case we want to populate a database located on the same IBM System z machine in the same logical partition As mentioned earlier we can use CICS Business Event Publisher to propagate the event to an external system However in this scenario our intent is to only demonstrate the functionality from the CICS Business Event Publisher Chapter 3 Using Physical views 157 As specified in 3 3 1 Overview of CICS Business Event Publisher for MQ Series on page 154 we picked the relevant components for our infrastructure Following are the installed components CICS Business Event Publisher event connectors for DB2 on z OS CICS Business Event Publisher message server CICS Business Event Publisher data space server The workstation administration client vvvy Figure 3 29 shows the real implementation that was performed while writing this book Set up business rules CICS BEP Gu Figure 3 29 CICS Business Event Publisher as implemented in the Smart Bank showcase The purpose of this book is not to detail the CICS Business Event Publisher setup process For more details about this refer to CICS Business Event Publisher for MQSeries V1 2 Getting Started GC34 6296 002 In order to understand the functioning of our setup Table 3 1 provides the correspondence between component functions and the started tasks implemented for th
323. ng rapid deployment This is the ability to adapt to the changing competitive landscape in which businesses either succeed or fail Usually clients do not know where their next challenge will come from and what kind of tools will be required to address it gt Ensuring business continuity A company s IT infrastructure must ensure that business continues to function well under all conditions and circumstances gt Enhancing security A secure infrastructure must create the necessary conditions for an open dynamic and shared environment in which collaborative processing takes place between employees clients suppliers and partners gt Promoting compliance Regulatory frameworks evolve every day forcing businesses to incorporate changes without affecting business opportunities IBM created the Smart Bank showcase to demonstrate to retail banking clients the benefits of IBM products services and solutions in addressing their key business issues The Smart Bank showcase covers different solution areas such as IT service management service oriented architecture optimization of IT resources information life cycle management information warehouse and business continuity The Smart Bank showcase is an implementation of these solutions in a real situation This IBM Redbooks publication looks at the infrastructure monitoring and infrastructure management provided by IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application
324. ng the WSDL generated from the process RMI IIOP direct calling of the process EJB Integration We incorporated the Enterprise service into a process and integrated this service with other services which can be other Enterprise services or Web Services The other services perform the near real time update of the analytical database for different business purposes These are Web services that have been generated from the Java bean that performs the JMS writes to the queue The figures that follow illustrate steps 1 2 3 and 4 described in Table 5 1 Table 5 2 lists the acronyms used in these figures Table 5 2 List of acronyms used in the diagrams Dynamic transaction routing CICSPlex TRAN CICS Transaction 262 Infrastructure Solutions Building a Smart Bank Operating Environment woe dso Figure 5 3 shows step 1 described in Table 5 1 with the initial multichannel workload on WebSphere on z OS Note The same principle applies to the J2EE applications deployed on WebSphere in Linux in the Blades and in the IBM z VM guests that represent the branch servers Pans z9 109 Browser z OS LPAR client WebSphere Application Server v6 CICSPlex CICS v3 1 HTTP n TORs AORs Web Container EJB Containe x 3 5 PA action lt 3 re 2 beans 2S g Fe Be GS g mis PE 8 stateless g 2 5 Workload o session beans S E E z Injection E a8 8 HTTP z lt Struts framework gt lt 4
325. nits Partners Intranet Client HTTP Business Units Web Services SOAP HTTP or ATM protocol Browser HTTP Browser http gt HTTP Branch Server Integration hub Business Analytics amp Risk J2EE application Management Siebel Business Analytics Fair Isaac amp BDW Fidelity Corebank Systems Management Core System FSDM Tivoli Monitoring Browser or client http Intranet Operations Figure 1 5 Smart Bank showcase architecture with emphasis on the channels that are discussed Business intelligence Based on the extract transform and load ETL process from our core system operational database a subset of the clients was loaded to an analytical database which enriched the data within This created our banking data warehouse on DB2 for z OS the same platform as our operational database The banking data warehouse model is designed specifically for analytics and business intelligence We then created an interface to Fair Isaac to further enrich our analytical database with client credit risk ratings and the probability of default ratings This was run historically to create the necessary history for Basel II reporting Finally Siebel Analytics was used as the business intelligence engine to inquire on our banking data warehouse in order to try and identify key trends and client segments From an architectural point of view two key considerations helped us in our choice gt We could use open stand
326. niversal Agent perform the configuration as follows 1 Update the parameter KUMA_STARTUP_DP in the Universal Agent s configuration file KUMENV KUMA_STARTUP_DP HTTP Update the URL list in the KUMPURLS file located in the directory lt ITM_install_dir gt tmaitm6 work as shown in Example 2 17 The default polling of 300 seconds is changed to 120 seconds StatusInterval parameter for each HTTP link Example 2 17 Updating the URL list List of URLs to monitor by the Universal Agent HTTP Data Provider blade2 production local fss StatusInterval 120 nx1 production local fss StatusInterval 120 safss 9080 web app StatusInterval 120 Note In the URL list it is not possible to specify the Web pages protected by user name and password at the application level The HTTP data provider only tests the URL availability It does not have the capability to manage interactive sessions The product IBM Tivoli Configuration Application Manager for Response Time Tracking addresses this requirement Chapter 2 IT environment of the Smart Bank showcase 119 3 Recycle the Universal Agent Note After the installation of the Universal Agent the TEP is unable to display the contents of the MANAGED_URL workspace The following error is displayed KFWITM220E Request failed during execution This error occurs when the Universal Agent is connected to a Tivoli Enterprise Monitoring Server Remote To work around this connect the Universal Agent direc
327. node name ATM iconImage url icons user ATM32 jpg node name Teller iconImage url icons user TELLER32 jpg node name PROCESS SOA iconImage url icons user SOA gif node name Web iconImage url icons user WEB32 gif node name zBank GDPS HyperSwap iconImage url icons user DISK32 jpg For each node included in the graphic view the Smart Bank showcase css file associates an iconImage The corresponding image must be included in the defined directory Each node name given in the Smart Bank showcase css file must exactly match the one given in the Logical view If not the default style is used instead Chapter 4 Customizing the Logical views 245 You can play with the css contents files using the numerous samples provided As an example modify the foreground color in the Smart Bank showcase css file from white to black The icons legend in the Smart Bank root graphic is displayed in black Example 4 4 shows how to suppress the legend of the icons Example 4 4 Suppressing the legend of the icons Gimport base css import baseLargelcon css node Anchor Center JabelPosition None node name Ming s Kitchen iconImage url icons user ming logo gif node name Human Resources iconImage url icons user human_resources gif node name Merchandising iconImage url icons user merchandisin
328. ns transactions that are called balance inquiry transfers and so on remain the same as in step 1 and step 2 Integration A completely new interface Here we re engineered the interface technique to the core system and instead of using the proprietary mechanism provided by the core system we used the COMMAREA in CICS to interface to the same API We created the Enterprise service definition directly from the COMMAREA using the WebSphere development tool available with WebSphere Studio Application Developer Integration Edition V5 and used CICS Transaction Gateway V5 as the J2EE Connector mechanism part of the J2EE Connector architecture JCA Using this tool a Wizard that drives the creation of the Web Services Description Language WSDL components the JCA connector and the Java bean proxy are created At this point we could have created a Web service from the Java bean proxy However we moved to step 4 Note Another method would be to involve SOAP HTTP directly to the core system Service orient Client Similar client as with step 3 in that we can either call the Java ed invocation bean proxies created from the binding to the process or the process EJB of a process directly through Remote Method Invocation over InterOrb Protocol RMI IIOP The bindings that are available are SOAP HTTP using the WSDL generated from the process SOAP JMS using the WSDL generated from the process not used in our project RMI IIOP usi
329. ns per second Chapter 3 Using Physical views 165 e Full increases We deliberately undersized our queue to have some displayable information The maximum number of messages that can be written on the queue set to 8000 The queue utilization graph shown in Figure 3 34 reflects this activity on the queue File Edit View Help gt OEEHBRGAD TSOOW SSWHSEHRALBARYM OTS FI Queue Utilization View g fy MQSERIES sx Sample Date amp Time fy cso eee ae Dies 03 21 06 16 26 24 03 21 06 16 27 03 21 06 16 28 03 21 06 16 29 03 21 06 16 30 03 21 06 16 31 03 21 06 16 32 24 7 _ 03 21 06 16 33 03 21 06 16 Application Statistics Buffer Pool Statistics Channel Definitions Channel Initiator Status Channel Performance Cluster Queue Manager Dead Letter Queue Messages Log Manager Performance Message Manager Performance MQSeries Events Page Set Statistics Queue Definitions Queue Manager Status Queue Statistics 03 21 06 16 30 Percent Full Sample Output Cur Opened Current Highest High Depth Date amp Time Exclusive D Control y 0 Nl Enabled Enabled Yes None 0726 1 03 21 06 1 0 Enabled Enabled Yes 1 10 26 04 03 21 06 16 39 24 0 0 Enabled Enabled Yes 1 O 10 26 04 1 03 21 06 16 38 24 0 19 No 3695 0 80 46 1 No Enabled Enabled Yes No None 1 O 10 26 04 1 03 21 06 16 37 24 0 19 No 3425 0 80 42 8 No Enabled
330. nstallation documentation Following is a list of the miscellaneous tasks gt Basic tuning of the database Some of the default parameters defined during the DB2 installation must be modified to perform a basic tuning gt Defining the network interface to communicate with Tivoli Enterprise Monitoring Server Hub After completing the basic installation because the Tivoli Enterprise Portal Server has several NICs it is necessary to specify the one used by IBM Tivoli Monitoring Refer to Multiple network interface cards on page 89 for details gt Defining the network interface to communicate with Tivoli Enterprise Portal The Tivoli Enterprise Portal clients desktop and browser are located on the intranet network as specified in Overview of network topology on page 86 Because IBM Tivoli Monitoring servers are configured to communicate only on the production network and there is no routing or bridging between the two networks the Tivoli Enterprise Portal Server is unable to correctly handle the requests coming from the Tivoli Enterprise Portal clients desktop and browser Any Tivoli Enterprise Portal client trying to open a session is able to get the login dialog box but after entering the password the user receives the following error message KFWITM215E Unable to process logon request Infrastructure Solutions Building a Smart Bank Operating Environment Perform the following tasks to enable the Tivoli Enterprise
331. nsures that the Tivoli Data Warehouse database does not grow in an unlimited manner Restriction The Summarization and Pruning Agent currently does not support the IBM Tivoli OMEGAMON products This means that all zZ OS based Tivoli OMEGAMON products may report data to the data warehouse but the maintenance of the data is currently not done by the Summarization and Pruning Agent Manual intervention is required Otherwise your database will grow in an unlimited manner This restriction will be removed when V4 1 becomes available Tivoli Enterprise Console event synchronization The Tivoli Enterprise Console event synchronization enables a two way synchronization between the Tivoli Monitoring V6 infrastructure and the Tivoli Enterprise Console The Tivoli Enterprise Console event synchronization component sends back to the monitoring server the updates of situation events that are forwarded to the Tivoli Enterprise Console server Actions performed in the Tivoli Enterprise Console for Tivoli Monitoring V6 situations are reflected in the Tivoli Enterprise Portal Server and then in the Tivoli Enterprise Portal Client IBM Tivoli Composite Application Manager As described in 1 1 4 The banking sector s future key business drivers on page 7 clients have a specific requirement to monitor their WebSphere environment the application server IBM WebSphere MQ and the objects inside Additionally SOA driven applications are also monitored
332. nt gt Name attribute Contains only the host name specified in the managed node lists Hot Lists gt Node Status attribute When the node replies to the ping the status is Online Otherwise the status is Offline gt Status Time Stamp attribute Indicates when the ping is issued to check if the node is up Note According to BM Tivoli Monitoring Universal Agent User s Guide SC32 9459 a managed node list Hot List issues a ping at 30 second intervals to every device in the list However the Status Time Stamp field is updated every 5 minutes No test is undertaken to determine if the ping is really issued every 30 seconds gt Current Response Time attribute The number of milliseconds to receive a reply from the remote host to the ping request Figure 3 47 shows the availability of the Smart Bank servers The default report is customized for a better understanding of the published data Name Z2 04 SQW SOHERDS7kO Address Node Status B BLADES E 3 Universal Agent EES 10 1 1 131 SNMP MANAGEROO fH 10 1 1 131SNMPdp UAGENTOO Egg Production Net SNMP MANAGEROO KH MANAGED NODES NETWORK ROUTER Inx1 production local ade3 production local ade4 production local ade5 production local ade6 production local ade production local ade8 production local MIBNODATA blade11 production local MIBSTATUS ba1 production local NETSUMMARY ba02 production local vipa productio
333. nt The CICS Business Event Publisher for MQSeries workstation administration client is a Windows technology based GUI used to create and maintain rules After the rules are created they are uploaded to the message server to be stored in the rules file These rules can be downloaded later to a workstation and modified and uploaded to the message server again Rules provide a link between the Business Event Publisher event source connectors and the message server The workstation administration client also contains a robust facility to generate rules and manipulate the contents of MQSeries messages generated by the rules A utility is provided to import a Common Business Oriented Language COBOL copybook into the Business Event Publisher environment so that the selection criteria and message creation are based on named items Configure the workstation administration client to ensure that sensitive information is not left on the workstation after the information is uploaded to the message server Besides helping you overcome shortcomings with regard to storage of rules this also helps avoid a potential security threat 3 3 2 Using CICS Business Event Publisher to populate the banking data warehouse database In our Smart Bank showcase infrastructure we monitor the events that occur on the posting table from the banking DB2 database For each banking transaction a record is created in the posting table We use this record event to populate our banki
334. nterupts P ES Open MessageArrivalClearing ITCAM450A BA01 or ay Open MQ Series_Queue_Manager_Problem CSQ2 BA01 MQES MessageArrivalClearing ES Open MQSeries_Queue_Manager_Problem WJIMA BAO1 MQES KS3_Vol_Fragment_Index Waming tle ES Open MessageArrivalClearing ITCAM450A BA01 Jy ES Open Crypto_Internal_Error BAPLEX BAQ1 MVS kS3_LCU_IO_Rate_Sec_Warming H Oocount 6 Open KS3_Vol_Free_Space_Pct_Warning TIVSREMT BA01 S KS3_LCU_Av_Delay_O_waming fol Open SYSPLEX_TEST BAPLEX MVS SYSF F a Open MessageArrivalClearing ITCAM4S0A BA02 KS3_Channel_Busy_Pot_Warning Ji Open Crypto_Internal_Errar BAPLEX BAO2 MVS KS3_Cachecu_Tik_Dstg_Critical pL Open KS3_Vol_Free_Space_Pet_Warning TIVSREMT BA02 5 Crypto Intemal_Enror fl ay Open KS3_Vol_Fragment_Index_VWarning TIVSREMT BA02 S ra ete F Open KS3_ Vol_Fragment_Index_Critical TIVSREMT BA02 S 4 gt Figure 1 9 The default TEP Client Welcome workspace when the distributed environment component is installed Figure 1 9 shows the predefined workspace displayed by default after a successful login to the Tivoli Enterprise Portal Server The Tivoli Enterprise Portal Client may run as a Java application within the Microsoft Internet Explorer or as a fat Java application on Linux or on Microsoft Windows The Tivoli Enterprise Portal Client may display information from all the monitored systems and applications that are supported by IBM Tivoli Monitoring and IBM Tivoli OMEGAMON
335. of the MQ infrastructure they use Chapter 3 Using Physical views 151 152 The Queue Statistics workspace This workspace shown in Figure 3 26 provides detailed information about each queue and its usage The system aspects are linked to the numbers provided in relative usage amount but the application community is more interested in detailed single numbers for specific queues Both the user groups are supported here Tivoli Enterprise Portal File Edit View Help HHBRE AH S COOC SQW RBAREERVSTEOS View Physical iv o g oea LEEENA Number of Queues Application Statistics Bi 600 Buffer Pool Statistics g Channel Definitions Channel Initiator Status Channel Performance Cluster Queue Manager Dead Letter Queue Message Log Manager Performance Message Manager Performar 4 MQSeries Events Page Set Statistics Queue Definitions Queue Manager Status Oimonitored Queues Hopen Queues E Number Queues with High Depth W number of Queues Get Inhibited number of Queues Put Inhibited Page 1 of 6 E F o 10 20 30 40 50 60 70 80 90 100 Queue Queue Definition Name Output Opens Cur Opened Exclusive Opens Opens Exceeded Status Status KMQ Normal PermDyn 0 0 0 No 0 0 80 0 0 No Enabl Enabl Yes No None a amp KMA Normal PermDyn 0 0 0 No 0 0 80 0 0 No Enabl
336. ollowing topics gt 4 1 Introducing the Logical view on page 182 defines a Logical view gt 4 2 Assigning managed systems to a Logical view on page 189 describes how to set up managed systems to a Logical view gt 4 3 Assigning situations to a Logical view on page 193 describes how to assign a situation to a Logical view gt 4 4 Defining the links on page 201 discusses links gt 4 5 Style in the Logical view on page 241 discusses how to use the style features gt 4 6 Logical view Lessons learned on page 252 summarizes the recommendations Copyright IBM Corp 2006 All rights reserved 181 4 1 Introducing the Logical view When defining a Logical view Tivoli Enterprise Portal TEP administrators can create their own tree By default this tree is completely disconnected from the physical tree shown in a Tivoli Enterprise Console A part of the branch or all the branches of this new tree is then connected to data or alerts or both data and alerts that are gathered by the available Tivoli Enterprise Monitoring Agent To do so on each level of this tree the administrator defines a workspace The purpose of this workspace is to concentrate and highlight all the information that is required to supervise a specific collaboration between physical components Inside each workspace the administrator defines views Each view provides detailed information about the status of a specific physical elem
337. on warehouse and information life cycle management from the infrastructure perspective gt Regulatory compliance This includes the following Regulatory reporting from the risk framework created by leveraging the analytical database created for client insight Showing how an enterprise can meet some of the demands of Basel II through the use of a central banking data warehouse analytical database This step involves banking risk and compliance from the business perspective and information warehouse and business continuity from the infrastructure perspective gt Business continuity operation risk and business resiliency This includes the following Showing how an enterprise can react to unplanned outages even as it maintains data integrity consistency and security Creating a highly available environment with hardening of platforms redundancy and recovery Allowing scalability both horizontal and vertical and planning for prioritizing workloads and systems This step involves banking risk and compliance from the business perspective and business continuity from the infrastructure perspective Chapter 1 Introducing the technical architecture of the Smart Bank showcase 11 gt Infrastructure simplification This includes the following Infrastructure simplification is an underlying message behind the entire demonstration of the monitoring and management of a system which can use virtualization and
338. on Management System IMS applications and data without the necessity to change application code The key features of CICS Business Event Publisher are gt Detection of application and data events without changes being made to the underlying applications gt New approach that enables you to utilize the legacy applications in order to leverage new business opportunities or new technology gt Distribution of CICS DB2 and IMS DB information using MQ Series messages without rewriting code gt Delivery of external event logging or notification of CICS DB2 or IMS activity gt Extension of data from the mainframe to other databases more efficiently CICS Business Event Publisher for MQSeries helps monitor the events within the CICS Transaction Server DB2 and IMS DB When certain events occur for example a file update request CICS Business Event Publisher for MQSeries compares the attributes and data associated with the event against a set of rules you have defined If a rule matches the event it creates a message and sends it to an MQSeries message queue By capturing critical business process events and creating messages from the event s associated data you can quickly and effectively enhance and extend the existing applications without changing any application code By acting as an event publisher CICS Business Event Publisher for MQSeries uses push technology a simple noninvasive capability that transports messages based on
339. on images Here ITM_zlinux_CD is the root of the CD ROM containing the IBM Tivoli Monitoring images for Linux on System z gt The parameter t specifies the agent product code lz for Linux ux for UNIX and so on gt The parameter p specifies the host type Generally the host type value provides the following information Product name aix for AIX sol for Solaris Is for SUSE Linux and so on Product version 51 for AIX 5 1 2 6 for Linux with 2 6 kernel and so on Platform type 3 for 32 bits architecture 6 for 62 bits architecture Running the deployment To quickly deploy the OS agents a simple batch script running on Windows is created to address the following requirements gt The agent installation is done by the tacmd createNode command gt The agent is able to connect on the primary or the secondary Tivoli Enterprise Monitoring Server Remote backup gt The agent uses the port 2018 default is 1918 to connect to the Tivoli Enterprise Monitoring Server Remote gt The script tests the target availability ping before starting the installation gt The script assigns the account used for the connection based on the connection protocol for example smb gt Administrator rexec ssh rsh root Note Before deploying the OS agent always check the prerequisites on the target computer such as the disk space Most times when the tacmd createNode command fails the final error message available in
340. on support to nstallShield lt Back Cancel Figure 2 46 Application support for z OS agents on Windows Tivoli Enterprise Monitoring Server Hub 2 2 12 Installing the key components for the distributed environment This section describes the installation of the key components for the distributed environment Tivoli OMEGAMON XE for WebSphere Application Server The Smart Bank environment has one standalone WebSphere V5 0 server that is used to run the Siebel Analytics program and two groups cells with the WebSphere V6 0 servers managed from two WebSphere Application Server Network Deployment The WebSphere Application Server V6 0 are installed on the following platforms gt SUSE Linux Enterprise Server 9 Intel gt SUSE Linux Enterprise Server 9 for IBM eServer zSeries 64 bit The WebSphere Application Server V5 0 is installed on the AIX 5 2 64 bit platform The monitor for WebSphere does not yet have a package built and released for IBM Tivoli Monitoring V6 1 This support is planned for 2006 check with your local IBM Sales Representative for the latest update However the Tivoli OMEGAMON XE agent can interact with the IBM Tivoli Monitoring environment This chapter focuses on the installation of the Tivoli OMEGAMON XE agent in the WebSphere V6 0 environment However the explanations are applicable to the WebSphere V5 0 environment as well Before starting the installation of the agent ensure the following g
341. ormation is retrieved from the sysLocation object instance of MIB II of the remote node gt Description attribute The information is retrieved from the sysDescr object instance of MIB II of the remote node Figure 3 46 shows the network details of the production network NETWORK blades SYSADMIN olx File Edt View Help CE a a a a OOM E E T E EE S View Physical 7 me Fair OaAad x Name A Address Status Type SNMP Enabled Location Description 10 1 1 12 10 1 1 12 Unknown Unknown No Unavailable Unavailable a Pa raua 1011120 1011120 TP Node No Unavailable Unavailable Wooo ens 10 1 1 121 10 1 1 121 Unknown Unknown No Unavailable Unavailable Ba ACE 10 1 1 122 0 1 1 122 IP Node No Unavailable Unavailable fl h Be BLADEN 10 1 1 123 IP Node No Unavailable Unavailable ia BLADE 2 CMS1 IP Node _ No Unavailable Unavailable _ i BLADER blade2 IP Node No Unavailable Unavailable E E tae blade3 10 1 1 126 IP Node No Unavailable Unavailable T blade4 10 1 1 127 IP Node No Unavailable Unavailable Bis 10 1 1 134 INTERNETOO id 104 1431 SNMP MANAGEROO bladed 10 1 1 128 IP Node No Unavailable Unavailab
342. ortance V Header V Goal Percentile V Goal Type V Goal Value V VO Priority V VO Rate V IFA Service Units V Managed System V Percent CPU V Percent IFA V Percent IFA on CP V Performance Index V Period V Resource Group v rsg YV Service ass Description V Workload Vv Workload Description vid 1 hame Figure 4 53 Assigning value to the new symbol 234 Infrastructure Solutions Building a Smart Bank Operating Environment Advanced link Assigning value using operators and functions Set up a symbol s value by using one of the following gt Attributes setup gt Strings gt Functions applied on attributes gt Operators 1 To complete the value of the current symbol add a string such as selected In our case the operator plus is used to concatenate this string with the current value Figure 4 54 Open the function tree in the bottom right section of the definition window Select the TOLOWER function conversion of a string to lower case 2 KJRITMOO2I Link Wizard Edit Link WLM Details x Properties amp Symbols V contextilsAvailable y linklsEnabled v ProsHeader Target Workspace F Query WLM LINK Service Class Symbols Y NODE V SERCLASS o EQ Table WLM Selected Servi V Footer V Header Expression kfw TableRow ATTRIBUTE MWLMPR CLSNAME Selected w Allowable Term
343. ote Hub in this example D NET ID KO1DSLB E ISTO97I DISPLAY ACCEPTED ISTO75I NAME PSSCBA KOIDSLB TYPE APPL 243 IST4861 STATUS ACT S DESIRED STATE ACTIV IST14471 REGISTRATION TYPE CDSERVR IST977I MDLTAB NA ASLTAB NA IST861I MODETAB KDSMTAB1 USSTAB NA LOGTAB NA IST9341 DLOGMOD CANCTDCS USS LANGTAB NA IST1711 ACTIVE SESSIONS 0000000003 SESSION REQUESTS 0000000000 IST2061 SESSIONS IST6341 NAME STATUS SID SEND RECV VR TP NETID IST635I TIVHUBLB ACTIV S CDD3C505D133D226 09A3 0001 PSSCBA IST635I TIVHUBLB ACTIV SV S CDD3C505D133D225 0001 0001 PSSCBA IST6351 TIVHUBLB ACTIV P CDD3C505D133D227 0001 0A1D PSSCBA Figure 2 22 VTAM applid display for the Remote Hub in LPAR BA01 74 Infrastructure Solutions Building a Smart Bank Operating Environment All the z OS based agents connect to their local Tivoli Enterprise Monitoring Server Remote using only SNA No other protocol is configured Figure 2 23 shows the display provided after one of our Remote Hubs has started all the z OS Tivoli Enterprise Monitoring Agents D NET ID KO1DSLB E IST097I DISPLAY ACCEPTED ISTO75I NAME PSSCBA KOIDSLB TYPE APPL 136 IST4861 STATUS ACT S DESIRED STATE ACTIV IST14471 REGISTRATION TYPE CDSERVR IST9771 MDLTAB NA ASLTAB NA IST8611 MODETAB KDSMTAB1 USSTAB NA LOGTAB NA IST9341 DLOGMOD CANCTDCS USS LANGTAB NA IST1711 ACTIVE SESSIONS 0000000021 SESSION REQUESTS 0000000
344. oviding a secure infrastructure Transactionality Ensuring that data integrity is maintained within the transactional unit of work and ensuring that they have atomicity consistency isolation and durability ACID properties Scalability The architecture must be able to scale in as near linear fashion as possible so that the cost of per unit of work remains constant even if the workload increases Language and platform Maximizing the independence of applications from the underlying neutrality platform so that the appropriate platform is chosen based on the qualities of service required Virtualization Benefitting from virtualization technologies where possible in order to simplify the environment and increase the efficiency and flexibility with which the environment is managed and provisioned 1 2 5 Key architectural decisions Note that the ISVs were chosen by the FSS based on the fact that their applications and technologies fit our architectural requirements However they are not the only ISVs that could have played the role Table 1 9 lists some of the key architectural decisions that were taken during the creation of the showcase and which contributed to our current architecture Table 1 9 Key architectural decisions Central platform IBM System z9 109 Adopting the same mainframe platform as our numerous clients for the mission critical core system workload 16 Infrastructure Solutions Building a Smart Bank Operati
345. owcase environment gt The Enterprise view of our bank through which a more business centric view of channels and the quality of service is explored This is provided by the Workload Manager WLM running on IBM System z9 and Parallel Sysplex that provides a Logical view of the core systems running on IBM z OS logical partitions LPARs gt The more operational Physical view in order to show how to monitor and manage the complex heterogeneous environment We constructed the view shown in Figure 5 1 to provide links and alerts to these two trees of Logical views Many of the figures in this chapter are live screen captures taken from the following gt The TEP running with some operational workload over the banking channels ATM Internet and Branch gt The process channel created for this demonstration to show the service oriented architecture model with additional ATM Internet and Branch workload Green indicates that all the systems are running according to the service level agreements set up in the TEP or are simply up and running Red indicates that there is a problem that requires attention Figure 5 1 shows that there is a problem in the Operations view 258 Infrastructure Solutions Building a Smart Bank Operating Environment For core systems transformation we decided to take the Enterprise route and therefore double clicked the Enterprise alert to link to the next level of the logical tree Throughout this project we
346. p 9 212 128 31 1920 fenpikdk E Go ay a File Edit View Help BReAA S CO C SQOWRKBRERERY OVTEeEA 3 View Physical g na Ae ees og re Pool Utilization A In flight Workloads Longest Running Wo Datasources Lock Analysis CTG Summary JMS Summary AT Ten Largest HTTP Session Objects Web Applications EJB Containers DB Connection Pools J2EE Connector Con Thread Pools La Dynamic Cache I 5 ___ kwrrmozst 60 Navigator updates pending E Physical 420 Y pd t l suoissag o 03 14 06 14 16 00 03 14 06 14 30 00 03 1406 14 45 00 03 1406 16 00 00 03 14 06 15 15 00 03 1406 18 30 00 03 14 06 15 45 00 03 14 06 16 00 00 JaqUinN moy Creating Creating Associated HTTP Sessio Number Date and Time and Time User IP Address Attributes Object Size 03 1 4 06 16 01 04 iss g jsp jspService 03 14 06 15 54 34 Unknd The number of attributes associated with this session 03 14 06 16 01 04 60 p9My3 Servlet org apache jsp _CWOutput _jspService 03 14 06 15 58 14 Unknq Create Date Workload Type Row Sample Interval Session Class Name Method Name 2 3 03 14 06 16 01 04 60 551Jd Servlet org apache jsp _TOFOutput _jspService 03 14 06 15 58 08 Unknown 10 1 1 147 0 4 03 14 06 16 01 04 60 FIP82f Servlet org apache jsp _BPOutput _ispService 03 14 06 15 58 14
347. p OK 2006 03 20 20 15 06 020 Siebel Analytics Log In 4096 203 Maer 1367 gl ofi httpinx1 production localifss OK 2006 03 20 20 15 06 010 FSS Benchmark Test 1917 16 31 17 0 ofi http blade2 production local f OK 2006 03 20 20 15 06 000 FSS Benchmark Test 1917 15 31 15 0 ojl Figure 3 40 TEP Internet URL response time with no ObjCache 172 Infrastructure Solutions Building a Smart Bank Operating Environment Note The ObjCache parameter may be considered when monitoring URLs containing objects such as JPEG and GIF images in order to reflect a more realistic value The response time is impacted by the total objects size especially for connections passing through low bandwidth network gt Average and maximum response time The default sampling interval to check the URLs availability and response time is 300 seconds However this may differ for each URL based on the parameter StatusInterval specified in the KUMPURLS file The calculation for the average and maximum response time is always based on the last 15 minutes of sampling data For long term analysis the historical data collection must be enabled Figure 3 41 shows the maximum and average response time based on the last 15 minutes for miscellaneous URLs gt MANAGED_URL blades SYSADMIN of x File Edit View Help e FEOHABREAA SOOV SBOWRMARBERAANRT FED View Physical E Oa FI URLs Response Time DBIOT
348. pCand1eWAEnabler sh Open the following URL http lt was_server gt 9060 admin 112 Infrastructure Solutions Building a Smart Bank Operating Environment Enter your account In the left frame select Servers Select Application Servers oN Oo ss Select Java and Process Management 9 Select Process Definition 10 Select Java Virtual Machine 11 In the Boot Class Path box enter the following lt CANDLEHOME gt classes kwescl 1 4 2 jar lt CANDLEHOME gt classes kwewa jar Caution lt CANDLEHOME gt is the installation directory of the Omegamon Agent 12 In the Generic JVM Arguments box add the following Dcom candle kwe instrument agent_parms lt CANDLEHOME gt config kweiuser xml 13 Click Apply 14 Click Save In the right frame select the application server whose configuration you want to modify 15 From the Tivoli Enterprise Portal in the Physical View right click your application server and select Take Action from the pop up menu 16 In the Take Action window select the WebSphere Application Server Configuration Setup command and enter the following parameters Workload_Analysis_Y_or_N Y VerboseGC_Y or_N Y to collect garbage File kweiuser xml 17 Select the WebSphere Application Servers in the Destination Systems List and click OK 18 From the WebSphere Application Server Admin Console recyle the application server After executing all these tasks you must have a view that is similar to t
349. ple Date and Time iCALOutp 03 14 06 14 27 12 63 JSP 0 0 High 0 000 0 000 0 000 A ICDTOutp 03 14 06 14 27 12 63 JSP 0 0 High 0 000 0 000 0 000 IPlAOutpu 03 14 06 14 27 12 63 JSP 4 0 High 0 000 7 250 0 000 0 063 IPICOutp 03 14 06 14 27 12 63 JSP 0 0 High 0 000 0 000 0 000 FssProce 03 14 06 14 27 12 63 Servlet_ 817 0 High 20 994 1 619 892 0 000 12 968 SimpleFil 03 1 4 06 14 27 12 63 Servlet 0 0 High 0 000 0 000 0 000 JErrorjsp 03 1 4 06 14 27 12 0 JSP High BlOutput 03 14 06 14 27 12 63 JSP 10 0 High 0 000 3 400 0 000 0 158 5 BPOutpu 03 14 06 14 27 12 63 JSP 1 0 High 0 000 3 000 0 000 0 015 ICDOOut 03 1 4 06 14 27 12 63 JSP 0 0 High 0 000 0 000 0 000 iCDOutpu 03 1 4 06 14 27 12 63 JSP 0 0 High 0 000 0 000 0 000 ICWOutp 03 14 06 14 27 12 63 JSP 0 0 High 0 000 0 000 0 000 iN amp Outnu AB ALN 1 422749 21 ISP n in l Hinh nnan li innnn Tnnnn S WebApplicationName APL_SOAEAR APL_SOAWeb war 0 Hub Time Di 03 1 4 2006 02 29 PM oe Server Available Servlets JSPs for Selected Web Application 9 212 128 31 WOLF1 Figure 3 21 The Web Applications workspace On the other hand the servlet error rate is also useful for system programmers Faulty applications may result in poor overall system performance higher rollback activity and so on Different rules may be applied depending on the audience gt Rules for system programmers Servlet error rate which ind
350. putt PerSec Gaia Per Sec maser Per Sec A eoru put CICS BEP a HE Queue Status FAT am wma High Depth Threshold Input Msg Size aa Avg MQ Resp Time 0 000 0 000 0 000 0 000 0 000 Input Opens Output Opens 5 Full 0 2 0 0 0 0 0 0 0 0 Queue 4 Name CICBEP QLOCAL1 CRB SRVING CRB SRYING WWQ_BDWUpdateMdbQueue WO_BPDUpdateMdbQueue 4 Total Current Opens Depth 20 o Highest Depth QM WJMA 8 aa 0 I MQOPEN Per Sec M MOCLOSE Per Sec MOGET Per Sec E MOPUT Per Sec Omoputt Per Sec 0 0 0 0 0 0 0 5 0 6 1 2 1 1 A 1 1 5 1 0 0 0 0 0 HE Application Statistics Host QMar Appl ID Appl Cur of of of Msgs P Msgs InputMsg Output Msg MONG PerBce Name Name Type Act TaskIDs Tran Pgms Queues Put Read Browsed Size Avg sean AERES BAOT WIMA TIVSMC MVS Yes 1 1 12 208 o 100 2 Benue BA01 WJMA WJMACHIN MYS Yes 6 2 6 1 1 0 752 aan B BAO1 WJMA BASRO111 MVS Yes 3 1 3 0 0 0 0 BA01 CSQ1 FABBEP1 MYS No 0 1 1 0 0 0 0 o o BADI esa FABRICE mvs No x0 il 1 0 0 0 0 amp Figure 9 WebSphere MQ view Part of the integration hub Table 5 5 shows the base queries that we used to create the Logical view from the assigned agents in Figure 5 9 Table 5 5 WebSphere MQ queries Assigned agent Query Assigned managed system A B C MQSERIES Mana
351. quester BillPaymentyS pay 1 0 1 1 Provider BillPaymentNsS pay 4 0 4 1 Requester CashDepositWS cashDeposit 1 0 1 1 Provider CashDepositws cashDeposit 4 0 1 1 Requester CashWVithdrawWvs cashWithdraw 1 0 1 1 Provider CashWithdrawws cashWithdraw A 0 i A Requester ChequeDepositWS deposit 1 0 1 1 Provider ChequeDepositws deposit 1 0 1 1 Requester CustomerArrangementListWS getAccountList 1 0 1 1 Provider CustomerArrangementListWS getAccountList 1 0 1 1 Requester Hello helloFSS 39 28 157 13 lt Provider Hello helloFSS 2 28 16 1 z TT z a Figure 3 12 The Performance Summary workspace By default it is made up of two views gt The average response time taken by the operation gt The services inventory Infrastructure Solutions Building a Smart Bank Operating Environment The Message Summary workspace The Message Summary workspace as shown in Figure 3 13 provides details about the number of messages and the average size of the messages in bytes by service name operation name and type requester or provider This workspace is available for each application server injected with the IBM Tivoli Composite Application Manager data collector for SOA _ 8X Q x a A pe a y amp ae File Edit View Favorites T Address http 9 212 128 31 1920 cnp kdt E EJ Go a Tivoli Enterprise Portal File Edit View Help BHBR AH SOOM SBOUBAEAART TeO
352. r Remote as their secondary server Thus they have two ways in which to report to the Hub Tivoli Enterprise Management Server gt OnAIX Remote Tivoli Enterprise Management Server The AlX based Tivoli Enterprise Management Server Remote works as the primary Tivoli Enterprise Management Server for all AlX based and Linux based agents It also hosts all the distribution packages for the AIX and Linux systems IBM Tivoli Monitoring agents The local agents on this system the operating system agent connect only to the local Remote Tivoli Enterprise Management Server If the machine is lost which is one of the assumptions 1 4 2 General architectural considerations on page 32 a secondary connection will not help gt Onz OS Moveable Hub Tivoli Enterprise Management Server This feature is introduced in 1 4 4 IBM System z environment scenario on page 37 The idea is described in detail in The Moveable Hub on page 40 On z OS each LPAR hosts its own Remote Tivoli Enterprise Management Server The communication with the Tivoli Enterprise Management Server Hub uses only SNA based communication The Tivoli Enterprise Management Server Hub is the only IBM Tivoli Monitoring V6 component on z OS that supports TCP IP communication On z OS each LPAR hosts its own Remote Tivoli Enterprise Management Server The communication with the Tivoli Enterprise Management Server Hub uses only SNA based communication
353. r Remote cannot support a secondary Tivoli Enterprise Management Server statement in its setup this solution is difficult to maintain if large z OS based environments are involved Additionally the Tivoli Enterprise Portal Server does not recognize the switch between the primary and the secondary Hub Tivoli Enterprise Management Server Manual intervention is required Chapter 1 Introducing the technical architecture of the Smart Bank showcase 49 50 On z OS implement the Moveable Hub Tivoli Enterprise Management Server This solution is useful for zZ OS dominant installations where most of the managed systems are z OS based If there is a large distributed environment a performance degradation may take place due to excessive translation between American Standard Code for Information Interchange ASCII Extended Binary Coded Decimal Interchange Code EBCDIC ASCII Refer to Chapter 5 1 3 in IBM Tivoli OMEGAMON XE V3 1 0 Deep Dive on z OS SG24 7155 for more details Virtualize the underlying machine and operating system by using z VM or VMware Because this solution has never been tested this book does not discuss it However the advantages are clearly identifiable e Network addresses never change e The Tivoli Enterprise Portal Server can automatically reconnect in any case e No overheads exist for the Hot Standby feature with regard to synchronization However an IBM System x based virtualization may suffer from network
354. r Summary PKO S File Agent Events Origin Node BAOT KWWA BA01 BAOT KWWA BAO1 BA01 KWWA BAQ1 BAOT KWWA BAO1 BAOT KWWA BA01 BAOT KWWA BA01 BA01 KWWA BA01 BAOT KWWA BA01 BAOT KWWA BAO1 BAOT KWWA BAO1 BAOT KWWA BAO1 Origin Node BAOT KWWA BAO1 BAOT KWWA BAO1 BAOT KWWA BA01 BAOT KWWA BAO1 BAOT KWWA BA01 BAOT KWWA BAO1 BAOT KWWA BA01 BAOT KWWA BAO1 Edit Host Name Application Server Error Logstream Host Name View Favorites I Event Date and Time 03 1 4 06 14 10 03 14 06 14 10 16 03 1 4 06 14 10 16 03 14 06 14 10 16 03 1 4 06 14 10 16 03 14 06 14 10 12 03 1 4 06 14 10 14 03 14 06 14 10 11 Server Instance Info Info Info Info Info Info Info Error hetpij 9 212 128 31 19204 enp kat E EJ co O G SBOGHU BSEETRERVD 97e KWED1221 KWED087I KWEDOOI KWE00121 KWEO086I KWEDO6S KWEDO66 KWEWA0S8 KWE00871 KWE01221 KWEDO9OI Name Date and Time AASRO11 03 14 06 11 34 12 AASROWMS AASRO11 03 14 06 14 26 12 AASROWMS AASRO11 03 14 06 14 26 12 AASRO1W1S AASRO11 03 14 06 14 26 19 AASROMS AASRO11 03 14 06 14 26 19 AASRO11S AASRO11 03 14 06 14 26 22 AASROMS AASRO11 03 14 06 14 26 35 AASRO11S AASRO11 03 14 06 14 26 49 AASRO11S Job Name Severity d Message ID File Name Line Number Q DE E Fu kwwcapse 2059 KAWApplication JEN kwweap
355. r for Windows platforms Secondary Tivoli Enterprise Monitoring Server for UNIX platforms Primary Tivoli Enterprise Monitoring Server for UNIX platforms Secondary Tivoli Enterprise Monitoring Server for Windows platforms Tivoli Enterprise Portal Server blade8 Windows 2003 SE ee SP1 Chapter 2 IT environment of the Smart Bank showcase 85 The IBM Tivoli Monitoring environment must manage the following platforms YYYY Y SUSE Linux Enterprise Server 9 Intel SUSE Linux Enterprise Server 9 for IBM eServer zSeries 64 bit SUSE Linux Enterprise Server 9 for IBM eServer zSeries 31 bit AIX 5 2 64 bit Windows 2003 SE SP1 32 bit 2 2 3 Overview of network topology 86 The network comprises two main segments The first segment is dedicated to the intranet communications between the client computers and the servers The other segment is dedicated to the interserver communications and is called Production Network Most of the servers have two network interfaces connected on each segment or have only one connection to the Production Network Figure 2 31 shows the connection of the main IBM Tivoli Monitoring components to the production and the intranet networks In particular note the following points gt gt gt All the IBM Tivoli Monitoring servers are physically connected to both the segments All the IBM Tivoli Monitoring servers are connected with gigabit interfaces There is no routing or bridging between the prod
356. r the part of an existing logical tree that already has managed systems assigned Directly build a view on that level When assigning the required query go to the Query Result Source index Check the option Let user assigned explicitly and then select the managed system on which the query must run Note You may combine the three methods If you do not use them the views cannot display the data from any agent and situations cannot be assigned Chapter 4 Customizing the Logical views 189 4 2 1 Assigning a managed system to a specific level When creating a Logical view or when using a Logical view right click the desired level and use the Properties option to assign the managed systems Figure 4 7 Note You can assign a Managed System List to a level When selecting the query for a view on a level check the Let user assign explicitly option in the Query Results Source option Manually select the managed system or systems on which this query will apply Because this is a Logical view definition by default the TEP does not propagate the selected query to all the managed systems in the managed system list O O AAD SO xve oas5a Ds D 2 Tivoli Enterprise Portal File Edit View Help M a E EEEE E EA view Smart_Ba M g re Smart_Bank Teller i Workspace a elo Enterprise Integration Take Action gt nternet Intranet Core Systems amp o H w
357. ransport opened coml sna pipe Example 2 7 is based on Tivoli OMEGAMON XE for Mainframe Network Tivoli Enterprise Monitoring Server RKVLOG messages Example 2 7 z OS Tivoli OMEGAMON XE for Mainframe Network SNA initialization messages ON BAO1 BSS1 GetEnv KDCFP_ALIAS KDCFC_ALIAS KLXBS_ALIAS KO1N3NC BSS1 GetEnv KDCFP_MODE KDCFC_MODE KLXBS_MODE CANCTDCS getEnv AF_SNA configuration Alias KO1N3NC Mode CANCTDCS TpName SNASOCKETS KDE1I_OpenTransportProvider Transport opened com1 sna pipe ON BA02 BSS1 GetEnv KDCFP_ALIAS KDCFC_ALIAS KLXBS_ALIAS KO2N3NC BSS1 GetEnv KDCFP_MODE KDCFC_MODE KLXBS_MODE CANCTDCS getEnv AF_SNA configuration Alias KO2N3NC Mode CANCTDCS TpName SNASOCKETS KDE1I_OpenTransportProvider Transport opened coml sna pipe Chapter 2 IT environment of the Smart Bank showcase 83 2 2 The distributed environment This section discusses the design and implementation of the distributed part of the IBM Tivoli Monitoring environment 2 2 1 Overview of the components This section provides an overview of the main IBM Tivoli Monitoring components implemented in our environment Component description The distributed environment comprises the following components gt Tivoli Enterprise Monitoring Server can be considered as the central repository for all monitoring data It performs the following functions Stores the definitions for conditions that indicate a problem with a particul
358. rastructure solutions initiative However Smart Bank showcase not only fits well with the infrastructure solutions strategy but also crosses into the IBM business solutions strategy This book positions the Smart Bank showcase within these IBM initiatives and architectures 1 1 1 Overview of IBM infrastructure solutions IBM offers a portfolio of solutions that focus on optimizing your infrastructure These solutions are specifically tailored for the financial services sector With these solutions IBM helps financial institutions achieve the following goals gt Enhance business resilience and security to protect and strengthen your institution gt Increase business flexibility to drive growth through new capabilities and enhanced value propositions gt Optimize IT environments to enhance efficiency across your company s IT resources including voice data and network Within these three subject areas IBM offers eight solutions that incorporate software hardware and services These are shown in Table 1 1 Table 1 1 Infrastructure solutions Infrastructure solution Brief description IT service management Reduces IT cost by automating integrating and optimizing change processes Service oriented architecture Increases flexibility and reduces complexity by integrating SOA infrastructure applications across disparate systems Information warehouse Delivers complete consistent trusted and actionable information User platfo
359. retrieve significant data from the IBM HTTP Server s access_log file The installation and settings are described in 2 2 The distributed environment on page 84 The content of the attribute groups is related to the settings defined during the configuration of the file data provider Chapter 3 Using Physical views 173 The managed system lt hostname gt IBMHTTP0OO0 contains 15 attribute groups These groups provide data about exceptions workload and connection statistics This section describes only those relating to the exception and workload including the following gt The attribute group EXCEPTION_DETAIL provides information about failed sessions This occurs when the server receives a request from a remote client but encounters an exception and is unable to fulfill the request The client receives an error message indicating the request has failed Thereafter only the most significant attributes listed here are detailed Client location attribute This is the IP address of the client remote host that makes the request to the server Service status attribute This attribute indicates the HTTP status code This indication is useful to determine the origin of the exception client or server Following are the most common client errors 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Requ
360. ring Server except AIX platforms cannot be queried from the Tivoli Enterprise Portal Server The workspaces are empty and an error message is returned Chapter 2 IT environment of the Smart Bank showcase 95 To add the agent specific information for Windows and Linux execute the following from the UNIX command prompt itmcmd support t lt 7EMS name gt nt 1z gt Adding application support for distributed applications on Tivoli Enterprise Monitoring Servers The Tivoli OMEGAMON XE agents are not built specifically for IBM Tivoli Monitoring However they can interact with the IBM Tivoli Monitoring environment by enabling the application support ATTR and CAT files Download the application support for distributed applications from the following Web site after providing a user ID and password https www14 software ibm com webapp iwm web reg download do source tmd1 amp S_PKG d1 amp cp UTF 8 From this Web site download the application installer available for miscellaneous platforms Windows Linux and so on and a package containing the application support for the OMEGAMON products To install the application support on Windows Tivoli Enterprise Monitoring Server perform the following tasks a Run the application installer using the setupwin32 exe command b In the Welcome page that is displayed click Next c Enter the IBM Tivoli Monitoring installation directory specify the location of application support files down
361. rise Portal Server was performed based on the recommendations available in IBM Tivoli Monitoring Installation and Setup Guide GC32 9407 and in Getting Started with IBM Tivoli Monitoring 6 1 on Distributed Environments SG24 7143 We recommend that you also refer to Chapter 2 2 4 Network communication on page 87 regarding the communication ports used for communication between the IBM Tivoli Monitoring components This chapter explains the specific post installation stages to customize the IBM Tivoli Monitoring servers Customizing the Tivoli Enterprise Monitoring Server Remote This section describes the miscellaneous tasks involved in customizing the IBM Tivoli Monitoring Servers Remote to address the requirements of our environment Following is a list of these tasks gt Defining the network interface to communicate with Tivoli Enterprise Monitoring Server Hub and agents After completing the basic installation because all the Tivoli Enterprise Monitoring Servers have several NICs it is necessary to specify the one used by Tivoli Enterprise Monitoring Server Refer to Multiple network interface cards on page 89 for details gt Application support for Windows and Linux On the AIX Tivoli Enterprise Monitoring Server Remote it is necessary to add agent specific information to the monitoring server This task was earlier called seeding operation Without this operation all the OS agents connected to this Tivoli Enterprise Monito
362. rks uses this function in one of the views of the TELNET workspace INPUT Enter Remote IP Enter Value The first string Enter Remote IP is the entity to which the question is asked and the second string Enter Value is the name of the pop up No verification is performed on the data Chapter 4 Customizing the Logical views 229 5 A dynamic association between the SERCLASS symbol in the query and the value of the Service Class column in the line of the view is now realized Click Finish to terminate this advanced link definition The view named WLM All Service Class is now displayed Figure 4 49 with a blue chain in the front indicating that a link is available File Edit View Help 9 f G SReAA F OOCS SUBRERAERTRT STEED avew ver fe e OE WLM All Service Class Resources information nE n x eg Page 1 of3 1 Smart_Bank WLM All Service Class Resources information ral Teller Managed Service Period Goal Goal Goal Goal Average Performance Percent Authentification System Class Type Percentile Importance Value Response Time Index CPU E face BAPLEX BAO1 MVSSYS_ BAT_DISC 1 Discret 01 nia 0 0 0 00 00 a cies Gs BAPLEX BAOTMVSSYS BAT_3V30 1 Velocio 0 Medium 30 0 0 00 0 0 DB2 E Link to WLM Details vSSYS_ BAT_3V40 1 Velocio 0 Medium 40 0 0 00 0 0
363. rm Provides secure personalized access anytime anywhere Optimization of IT resources Creates a responsive IT infrastructure that is easier and less expensive to manage upgrade and run Information life cycle Manages information from creation to disposal on the most management efficient and cost effective IT infrastructure Business continuity Assures that critical business processes IT systems and networks are continuously available IT security Understands mitigates and manages security risks 2 Infrastructure Solutions Building a Smart Bank Operating Environment The rest of this book describes how Smart Bank showcase covers a number of different solution areas However the main purpose of this book is to look at infrastructure monitoring and management provided by IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 These tools help optimize your IT infrastructure and are also useful across other solution areas Figure 1 1 maps the IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 to the infrastructure solutions Linked Banking Smart Bank Environment Showcase Business Back Office Operations FS03 Core Transform Solution Front Office Optimization FS04 Customer Insight Banking Risk amp Compliance FS09 Risk Management IBM Tivoli SBES ivoli Affinity amnio Composite Ranking Monitorin FSS Application Manager Affinity High Medium
364. rol System CICS and IBM CICSPlex IT Specialist within the infrastructure solutions department at the PSSC in Montpellier France He joined IBM in 2000 Before joining IBM he worked at Mag Info which is a part of the French Galeries Lafayette group responsible for managing the transaction system based on CICS He holds a degree in computing from Ecole Superieure Informatique Professionnel Paris His areas of expertise include CICS IBM CICSPlex CICS e business technologies for z OS and CICS Tools He is a Subject Matter Expert in CICS Web enablement Francois Lebe is an IBM System z Technical Pre sales Specialist working at the IBM office in Paris He has been working on Candle since 1999 He joined IBM in 2004 when Candle Corporation was acquired by IBM He has over 20 years of experience in the software business Francois specializes in supervision and automation of System z platforms He holds a degree from the Institute Universitaire De Technologie specializing in IT He has written extensively for French clients on how to supervise System z platforms using the IBM Candle automation and IBM OMEGAMON products Detlef Wolf is an IT Specialist for IBM Tivoli System Automation working for the Tivoli Technical Sales team based in Munich Germany He has 16 years of experience in the IT industry Starting in an application developing department in the medical care industry he became a System Programmer for z OS in an insurance company In
365. rprise Monitoring Servers TEMS that you have configured Enter S next to the TEMS to connect to this remote To manually enter the TEMS information press F5 TEMS RTE name RTE mid level Description RTE SHARE for moveable HUB Smart Bank Fl Help F3 Back F5 Advanced F 7 Up F8 Down F1 HELP F2 SPLIT F3 END F4 RETURN F5 F6 RCHANGE F7 UP F8 DOWN F9 SWAP F10 LEFT F11 RIGHT F12 RETRIEVE Figure 2 28 ICAT Tivoli Enterprise Monitoring Server eligible list Chapter 2 IT environment of the Smart Bank showcase 79 b This displays the advanced communication screen shown in Figure 2 29 In this communication configuration screen provide the primary HUB Tivoli Enterprise Monitoring Server name the Global location applid and the network The Tivoli Enterprise Monitoring Server Remote uses this information to connect to the primary Hub Tivoli Enterprise Monitoring Server You are about to configure a Remote TEMS Enter the following information about the Hub TEMS that the Remote TEMS connects to Hub TEMS name Case sensitive gt HUB CMS Global location broker applid of Hub gt TIVHUBLB Network ID of Hub gt PSSCBA If the Remote TEMS requires TCP support enter the Hub s values for Hostname of Hub gt Address of Hub gt If the Remote TEMS requires IP PIPE and or IP UDP support enter the Hub s values if applicable IP PIPE port number gt Non secure NCS RPC IP6 PIPE port number gt IP PIPE for IPV6 IP
366. rsions all workloads V2 query branch machines Inx4 and Inx5 on All Workloads z VM and Blade4 and Blade5 In the centre of the diagram Link to the Linux utilization Figure 5 16 clearly shows that Inx4 and Blade4 are receiving more workload that the other machines which explains why they are experiencing slightly longer response times than the other application servers in their clusters Inx5 and Blade5 respectively 282 Infrastructure Solutions Building a Smart Bank Operating Environment Using the alert in the center of the diagram we can link to a Linux utilization Logical view which then shows us from a Linux perspective what the physical blades and the virtual machines are doing 5 3 2 The Linux utilization view In the window shown in Figure 5 17 we created a Logical view of our branch server operating environment with our WebSphere clusters on z VM and on BladeCenter In both instances we did not stress on the CPU resources available to us see A and B A view of the memory utilization in C and D is also available File Edit View Help gt FAROR BREADS OOW SRQSHWHRBRBEAERFOSTSD Linux utilisation Branch servers 080 x i zvuceu BRNE k x v alg 8 z VM Linux Inx4 LZ Inx4 LZ Duser CPU Percent M System CPU Percent Inx LZ E Busy CPU Percent enn me ines a 94 Taaa Intel Linux nxt Bade2 HTTP HTTP Duser CPU Percent
367. rt Bank Operating Environment 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 Consult your 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 IBM product program or service may be used Any functionally equivalent product program or service that does not infringe any IBM intellectual property right may be used instead However it is the user s responsibility 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 such provisions are inconsistent with local law INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF NON INFRINGEMENT MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Some
368. rt Situation Stop Situation g Delete Situation Z Associate Dissociate Al Click inside a cell of the formula editor to see a description of the attribute for that column and to compose the expression PROCESS SOA Add a condition by clicking Add conditions and selecting the situations to embed or attributes you want to include Jire ie Situation Formula Capacity 3 Add conditions Advanced Physical lt 3 smert_Bank l ji FA Notepad Sampling interval Sound ieee Enable critical wav W critical ow oR 5H Oo ddd hh mm ss s C Run et startup CB Hub Time ke1 gt Figure 4 12 Associating a situation to a Logical view This situation is now associated with the selected level of the logical tree If this situation becomes true an alert opens up at this logical tree level Dissociating a situation works in the reverse order Select the Dissociate option to suppress the association at this level Chapter 4 Customizing the Logical views 195 4 3 3 Advice in a situation Advice relating to a situation provides explanation about what is happening and what can be done to solve a problem This is especially interesting in a Logical view There is more than one way to write a situation Advice using the ADVICE function The ADVICE function can be used in the Expert Advice definition part of a situation It is called ADVICE kxx ISITST
369. rtal Server software gt Run time data Data stored in the database State of the entire hosted system 48 Infrastructure Solutions Building a Smart Bank Operating Environment By running a disk replication with Storage Area Network SAN or Peer to Peer Remote Copy PPRC the data of the VMware image is always ready for restart on a backup VMware host For more information about VMware refer to the following Web site http www redbooks ibm com redpapers pdfs redp3939 pdf The result of virtualization is almost the same as that under z VM on IBM System z The Tivoli Enterprise Portal Server can be executed on different hardware systems while retaining its known TCP IP address This is essential for the clients connecting to the portal server Even in an emergency situation the virtual Tivoli Enterprise Portal Server system can be restarted on another hardware system assuming the VMware image is available This solution is effective if a VMware ESX Server implementation already exists If not contact your local IBM Sales Representative 1 5 Conclusion This chapter provided guidelines about the major points that must be kept in mind when picking the right alternative for your installation Because many more combinations are possible than are documented in this book we split the two major components Tivoli Enterprise Portal Server and Tivoli Enterprise Management Server gt Tivoli Enterprise Portal Server There are three
370. rtance 0 0 V Goal Percentile 0 0 V Goal Type 0 0 V Goal Value 0 0 pu V VO Priority 0 0 3 Phy V UO Rate 5 V Managed System E V Percent CPU 31 SYSADMIN Figure 4 44 The attributes as gathered by the attached query on the source workspace Infrastructure Solutions Building a Smart Bank Operating Environment Scroll down the advanced link definition window zone A2 in Figure 4 44 to find the functions and operators you can use to build advanced filtering on the available attributes as shown in Figure 4 45 2 KJRITMOO2I Link Wizard Edit Link WLM Details Properties Expression Symbols ftrue V contextisAvailable y inklsEnabled Target Workspace F Query WLM LINK Service Class amp Symbols Vv NODE V SERCLASS Allowable Terms Test E Table WLM Selected Servi Functions Y Footer m Between V Header abe Sub String abe Quote String abe String Scan Compare Date and Time G Time abe Index Of abe Last Index Of abe Length abc Format Values abe Get Resource String Get Advice URL String abe Extract Token abe To String abe To Boolean abc To Integer abe To Float abe To Uppercase abt To Lowercase abe Trim abe Starts With abe Ends With abe Input Value abe Construct Java Object ab Call Java Function abe Get Java Value abe Get Typed object property Operators Assion Valic a a
371. rtant use cases in order to be able to discuss the Logical views we created in TEP The use cases have also been chosen to cover a cross range of the IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 capabilities Following are the use cases this book focuses on from the Smart Bank showcase proof points perspective gt Core system transformation SOA described in 5 1 Core system transformation service oriented architecture on page 258 gt Optimization of IT resources On Off Capacity on Demand described in 5 2 Optimization of IT resources On Off Capacity on Demand on page 272 gt Branch transformation and infrastructure simplification heterogeneous view described in 5 3 Branch transformation and infrastructure simplification heterogeneous view on page 280 We discuss these use cases after discussing monitoring architecture implementation and Physical and Logical views 1 4 IBM Tivoli Monitoring Architectural design and description The Smart Bank showcase is focused on IBM System z as are the bank s employees The employees were therefore looking for a reliable system management tool that supports their requirements in two different ways gt Showing application related Logical views where the health of the application supporting components can be shown gt Identifying and analyzing the root cause of a slowdown or outage in one of the applications What is require
372. ry E Current Situation Values EAX EH Network i ml Operating System T Interupts sec A Processor Server Name Timestamp Privileged Time E Process 2 1 232 _Total Primary BLADE12 NT_ 03 11 06 17 02 54 1 E Processor E System g Physical Smart_Bank 4 Command View manx CE oR a Take Action e OZA Action al Nene Stet Actors e Seeq F 5 i the web starts here ee ee Sponsored results for mechanicalworks Destination Systems 5 a 1 Find a Job using IBM Technology Search for jobs in IT at all levels and across all disciplines IT careers with Capgen w Uk capgemini com 2 Buy IBM on eBay co uk You ll find anything from la and PDAs to printers and monitors at fantastic lov UK s online marketplace Buy it Sell it Love it eBay co uk www ebay co uk x Ie i gt WF Expert Advice Q Hub Time Sat 03 11 2006 05 01 PM 3 Server Available NT_System_Total_Interrupts 9 212 128 31 SYSADMIN Figure 4 18 Result from the prompt in a situation advice 4 4 Defining the links A Logical view displays data in an organized structure Define Jinks to navigate easily from one point of the structure to another point This section explains the different type of links and how to define them 4 4 1 Introducing the links A link is an internal TEP definition It is used by TEP users to easily navigate in the TEP organization Links help you perform the following tasks gt gt Jump from one vi
373. s vid a V Average Storage V CSS Priority Y Class Flag V Duration V Goal Importance V Goal Percentile V Goal Type V Goal Value V WO Priority V VO Rate V IFA Service Units V Managed System V Percent CPU V Percent IFA V Percent IFA on CP V Performance Index Period V Resource Group v V Service Class Description V Workload V Workload Description A a Cancel Delete Back Figure 4 54 Completing the value of the symbol Chapter 4 Customizing the Logical views 235 The skeleton of this fu Properties E Symbols V contextisAvailable Vy linklsEnabled v preceder E Target Workspace F Query WLM LINK Service Class Symbols Y NODE V SERCLASS o EQ Table WLM Selected Servi V Footer V Header nction is shown Figure 4 55 Expression kfw TableRow ATTRIBUTE MWLMPR CLSNAME Selected TOLOWER StrVALUE StrATTRIBUTE we Allowable Terms E Functions m Between abt Sub String abe Quote String abe String Scan E Compare Date and Time Time abe Index Of abt Last Index Of abe Length abc Format Values abe Get Resource String Get Advice URL String abc Extract Token abe To String abt To Boolean abc To Integer abe To Float abe To Uppercase abe Trim abe Starts With abc Ends With abe Next Figure 4 55 Using a function to set up a symbol value
374. s gt Due to constraints in our architecture only the following are specified A secondary Tivoli Enterprise Monitoring Server Candle Management Server in OMEGAMON Port 2018 for communicating with Tivoli Enterprise Monitoring Servers When the server has multiple network cards the Primary Network Name for communicating with other IBM Tivoli Monitoring components updates the KDCBO_HOSTNAME variable gt You must know the directory where WebSphere is installed gt To configure the agent execute the following command lt CANDLEHOME gt CandleConfig A we Example 2 10 shows the output of the configuration program on Linux Example 2 10 Configuration of the Tivoli OMEGAMON XE Agent for WebSphere Application Server CandleConfig A we CandleConfig installer level 350 580 CandleConfig running 11624 jre Will this agent connect to a CMS YES or NO Default is YES YES CMS Host Name Default is blade3 blade7 production local Will the agent connect through a firewall YES or NO Default is NO Network Protocol ip sna or ip pipe Default is ip ip pipe Now choose the next protocol from one of these ip sna none Network Protocol 2 Default is none ip Chapter 2 IT environment of the Smart Bank showcase 109 Now choose the next protocol from one of these sna none Network Protocol 3 Default is none IP Port Number Default is 1918 2018 IP PIPE Port Number Defaul
375. s multiple units of work in parallel providing a high level of performance If the unit of work encompassing the event is not completed successfully the event s message is not published For DB2 and IMS connectors events are processed asynchronously after the actual DB2 or IMS unit of work is complete If a rule specifies that a message must participate in the unit of work the message is not completed on the queue unless the unit of work being processed is successfully committed The message server also contains a TCP IP listener subtask used for communication between the message server and the Business Event Publisher workstation administration client It can for example upload new rules created on the workstation administration client to the message server rules file CICS Business Event Publisher for MQSeries data space server CICS Business Event Publisher for MQSeries data space server is used to provide virtual storage for semi persistent information used by message servers and event source connectors This allows message servers and event source connectors to be stopped and started without losing valuable state information such as cached rules and CICS transaction pattern knowledge 156 Infrastructure Solutions Building a Smart Bank Operating Environment CICS Business Event Publisher for MQSeries rules database CICS Business Event Publisher for MQSeries rules database is used as a repository for rules that contain the selection criteri
376. s oaox og operating Syeiem Interruptsisec A Processor Server Name Timestamp Privileged Time By Windows Systems a x TTY Ga BLADEI0 me 1 220 _Total Primary BLADE1 2 NT 03 11 06 16 46 12 0 a BLADEN a fa BLADE12 y windows os Disk 4 D E Enterprise Services ES Memory EE Current Situation V oaox EH Network B pai Operating System Interruptsisec A Processor Server Name Timestamp Privileged Time EH Process 52 1 232 _Total Primary BLADE1 2 NT 03 11 06 17 02 54 i fal ry 4 What do you want to reasearch for IBM Take Action e Action Name Select Action gt m Ee Destination Systems Run r Expert Advice Hub Time Sat 03 11 2006 05 01 PM Server Available NT_System_Total_Interrupts 9 212 128 31 SYSADMIN Figure 4 16 Prompt from the INPUT function in a situation advice Chapter 4 Customizing the Logical views 199 200 3 After filling the form click OK The next stage of the situation advice that runs at this juncture is shown in Figure 4 17 File Edit View Help e OUM E Vev TEx S By Windows Systems e Ga BLADEtO Ga BLADEN By Blane 5 y windows os Disk Memory Network Printer Process Processor Bs Enterprise Services E Physical E Smart_Bank Take Action 25 Initial Situation V BSBkLeHA EA SCOC
377. s the run time environment in the ICAT tool Additional panels prompt for the required parameter values which are in turn used to allocate the libraries and set the run time environment default values for the products that are to be configured in this run time environment Adding a run time environment creates a configuration tool definition only Chapter 2 IT environment of the Smart Bank showcase 63 64 2 Build the libraries for the run time environment It generates a batch job to allocate the required run time libraries for the selected product This job is presented for your review and submission This task 2 must be performed for every run time environment that contains the selected product This includes the base run time environments Configure the product in the run time environment This task which is not used for a base run time environment presents the panels to collect the parameter values required to configure the selected product for this run time environment The run time environment default values are used when applicable A batch job is generated and presented for your review and submission This task 3 must be performed after step 2 for every run time environment that contains the product Load the product into run time environment This task loads all the product libraries after SMP E It generates a batch job to load the run time libraries from the SMP E target libraries for this run time environment Load the
378. se 2135 KVWWApplications kwweapse 3582 KVWApplications kwweapse 324 KVWWaApplication kwweapse 3441 KWWWiApplications kwweapse 1941 KVWWVApplication kwweapse 1995 KVWWApplications kwweapse 3343 KWWApnplications kwweapse 2135 KVWApplications kwweapse 012A 012A 012A 012A 012A 012A 012A 012A Job ASID 2059 EE 3582 Feinvonioalaad 4 Process ID 03010393 03010393 03010393 03010393 03010393 03010393 03010393 03010393 KWWApplication O80 x Thread ID 17F8F370000051 17F6B71000004C 17F31130000047 17F97B00000056 17F6B71000004C 17F8F370000051 17F31130000047 17F34D70000049 w Server Instance oats ee Server Release Build LDAP LDAP LDAP Control Region Server Region Name Type Role Level Level _ Status PortNumber IP Name PROC Name PROC Name AADMGR Running J2EE Deployrnent_Manager nia AAAGNT1 Running J2EE Node_Agent nia AASRO11 Running J2EE Application_Server nia AAACR AAASR BASRO11 Running J2EE Application_Server 6 1 0 WW510224 nla BAACR BAASR f 5 Hub Time Di 03 1 4 2006 02 31 PM a Server Available WOLF1 WAS z OS 9 212 128 31 WOLF1 Figure 3 16 A customized OMEGAMON WebSphere Application Server z OS Systems workspace For a detailed description about customizing the workspace according to individual requirements refer to Chapter 5 of the IBM Tivoli Monitoring V6 User Guide which is available on t
379. sed on a mainframe with IBM z OS configured in Parallel Sysplex The hardware configuration comprises the following components gt One IBM System z one z990 2094 Model B16 Sixteen shared central processors CPs Two z OS logical partitions LPARs One z VM LPAR Six z linux Guest One coupling facility LPAR Sixteen giga byte GB of memory Four ESCON channels One dedicated gigabit Gb Ethernet Open Systems Adapter OSA card One dedicated fast Ethernet card gt One Enterprise Storage ESS 2105 direct access storage device DASD subsystem with 6 6 terabyte TB gt One IBM System x X335 for simulating the workload injection gt One IBM BladeCenter 8627 with 14 blades for multichannel application simulation and Tivoli infrastructure management HS20 with Windows XP HS20 with SUSE Linux 8 0 JS20 POWER4 with AIX V5 2 gt One CISCO 6509 switch Chapter 2 IT environment of the Smart Bank showcase 53 Figure 2 2 shows the hardware infrastructure setup for the Smart Bank test system that is used in this book Montpellier Firewall router xm IBM eServer xSeries x335 OWindows XP gt Workload Generator IBM BladeCenter 018627 with 14 blades Z990 B16 08832 G1X 3 2 Ghz QOActive CPs 16 Be O4GB RAM Bi OVirtualization into 4 logical F broeeecar i gt partitions CISCO 6509 Switch OHS20 Blades SUSE gt Parallel Sysplex VIPA h Sysplex Distributor Lin
380. sicashDeposit do HIST_WORKLOAD_BY_DAY 10 1 1 147 03 16 06 17 07 42 631 0 500 ifssicashDeposit do HST_WORKLOAD_BY_HOUR 10 1 1 147 03 16 06 17 07 42 631 0 500 fssicashDeposit do WORKLOAD _DETAL 10 11 147 03 16 06 17 07 43 631 o 500 ifssicashDeposit do 10 11 147 03 16 06 17 07 44 631 o 500 ifssicashDeposit do E ana 4447 nam cine A707 Aa eat at ran leanta PREETI HE Report mang x LocalTimeStamp Service ServerName BytesReceived BytesSend ServiceStatus Request RequestParameters RequestElapsedTime Referral Browser INES X UTEE TE 05 29 1 0 i 400 ssicashDeposit do i U aj 10114147 03 16 06 16 05 24 o a 400 ifssicashDepositdo a 10114147 03 16 06 16 05 24 Q ol 400 ifssicashDepositdo a Figure 3 42 TEP Connection exception on the IBM HTTP Server gt The attribute group WORKLOAD_DETAIL provides miscellaneous statistics about the amount of data transferred between the clients and the server during a period of 5 minutes This short term history is based on a feature of the file data provider which helps summarize data for a specific period of time For a better understanding of the data provided by this attribute group briefly explain the content of the metafile used by the file data provider Example 3 5 shows a partial listing of the IBMHTTP mdl metafile where the WORKLOAD_DETAIL attribute group is defined Example 3 5 Partial listing of the IBMHTTPmal meta file NAME Workload D
381. siness issues outlined Chapter 1 Introducing the technical architecture of the Smart Bank showcase 9 1 1 6 Demonstration proof points A day in the life of a bank For this demonstration we took the important strategies and tried to tackle them in a logical order even as we created our environment trying to address a proof point for retail banking each time The following proof points are addressed in the Smart Bank demonstration gt Multichannel transformation The first thing we did was to integrate our modern core retail banking system that was provided by Fidelity to our channels in order to allow our clients to transact with us Multichannel transformation involves the following The ability to reuse business logic across more than one delivery channel and open new delivery channels or enterprise product offerings rapidly The ability to manage these channels centrally and collect metrics in real time This may be used for billing lines of business based on usage To control the quality of service and user experience across these channels To provide a resilient secure scalable and highly available business service for these delivery channels This step involves front office optimization from the business perspective and the SOA infrastructure and user platform from the infrastructure perspective gt Branch transformation This implies multiple tasks including the following For the branch channel we a
382. sion TOLOVER kfw TableRow ATTRIBUTE MWLMPR CLSDESC kfu TableRow ATTRIBUTE MULMPR CLSNAMES Selected omoj V VO Priority V WO Rate V IFA Service Units V Managed System V Percent CPU V Percent IFA V Percent IFA on CP V Performance Index Y Period V Resource Group V Service Class v Service V Workload V Workload Description Vid V Name V Type S EQ Table WLM All Service Class Resources information ical Query WLM Service Class Resources E workspace lt Unnamed gt lt Unnamed gt lt Unnamed gt Figure 4 57 Attribute as a value of the function parameter Chapter 4 Customizing the Logical views 237 5 Anew symbol is ready Its value is a concatenation of the attribute that contains the name of the service class Select a string Then change the contents of the Service Class Description attribute to lower case Click Test to ask the TEP to validate the formula zone A in Figure 4 58 If there is no error the result of the expression is displayed in a pop up 238 f x fl KJRITMO02I Link Wizard Edit Link WLM Details Properties Expression KR Syrtos sk w TableRow ATTRIBUTE MWLMPR CLSNAMES Selected aah ab aera TOLOWER kfw Tab leRow ATTRIBUTE MULMPR CLSDESCS y linklsEnabled v ProcHeader z S Target Workspace mem Galear GT F Query
383. size that this is a real workload on a live operational system 09 00 a m Branches open A new channel comes online and the clients start Workload increases transacting through the branches We introduce our enterprise management IBM Tivoli Enterprise Portal TEP views and show the branch channel arriving from a workload point of view and highlight the quality of service QoS which can be measured across the client facing channels 10 00 a m Business intelligence The bank s analysts have with the help of business Client segmentation intelligence software detected a trend in the mortgage portfolio and continue to identify client segments and promotional opportunities Now we launch into client profitability revenue growth and the client segmentation proof point using Siebel Business Analytics 1 We recognize that many banks operate across different time zones and that this can even out or blur the peaks and troughs of a daily workload For reasons of simplicity and for a more dramatic dynamic demonstration we restricted the demonstration to one time zone for now 12 Infrastructure Solutions Building a Smart Bank Operating Environment 10 30 a m 10 45 a m Near real time business analytics data Leverage the new programming model Introduce business performance dashboards Manage lunch time volumes New promotion launch Promotion peaks internet traffic Business continuity Credit Basel
384. ssic Command and Menu Mode IBM Tivoli OMEGAMON II YYYY Y Copyright IBM Corp 2006 All rights reserved 51 Figure 2 1 shows the overall technical architecture and how multichannel Automated Teller Machine ATM Teller and Internet banking are implemented This view describes the channel traffic across the different components zSeries Central Shared Server ATM channel Simulation Mechanism Internet channel s WebSphere i Y 1 Teller Application Server channels N N BladeCenter server Compliance application I mal Isaac Branch Application Application Intel Linux A ziIVM Siebel Analytics server POWER4 AIX Linux on zSeries Figure 2 1 The Smart Bank s technical architecture 52 Infrastructure Solutions Building a Smart Bank Operating Environment 2 1 The IBM System z environment This section describes the setup of the IBM System z environment for the Smart Bank demonstration Integrated applications span WebSphere and Customer Information Control System CICS transactions with a high volume of data in a core database and a realistic scale of between 100 800 transactions per second For high performance workload management infrastructure management and high availability the corebanking application and operating environment is based on z OS in a Parallel Sysplex 2 1 1 The hardware components The Smart Bank backend infrastructure is ba
385. st Then define children that are either attached directly to the name of the Navigator view or to an existing child The root is the Navigator view the branches are the children attached to the root and the leaves are the children without attachments By extension a Navigator view that represents a Logical view is called a logical tree A level in this tree is either the root a branch or a leaf O O AAGIL Ke Sle Tivoli Enterprise Po File Edit View Help 6 rh View Physical amp E PROCESS SOA g Smart_Bank Enterprise a Teller EHE UNIX Systems Enterprise i Authentification Create New Navigator Item HA UNIX Systems ic Banking a f Linux Systems gl cics Navigator Item Identity G RS Windows Systems H Name ESS800 fm BLADE11 g MQSeries TCP Description Manage the IBM disk E WebSphere fa BLADES L zos xi m pa BLADES La Teller Channel iy z OS Systems S ATM Assigned rAvailable Managed Systems ATM Channel IBAPLEX BAO1 MVSSYS Authentification BAPLEX BA02MYSSYS 5 Banking B BAPLEX MVS SYSPLEX 2 KFviTMo25i 88 t L acs BLADE E Prsia Reo Kies en Ea m Banking amp i Available Managed System Lists EEE m cics oe Web Channel gt q ail Financial Dasboard gt A Edit Managed System Lists Bs a canes __ Heb KFWITM338I Enter a description of the Navigator item
386. st reconnect to the Hub Tivoli Enterprise Management Server Ifthe Remote Tivoli Enterprise Management Server reconnects successfully all the attached agents will go online at the same time With this assumption a well organized communication structure within our system management infrastructure is ensured If necessary in order to meet targets parameters in the Tivoli Enterprise Management Server Remote may be changed to speed up the process for reconnection if the hub has failed Chapter 1 Introducing the technical architecture of the Smart Bank showcase 33 Figure 1 12 shows the dependencies between the various IT components involved Appl Sys stands for the monitored application systems that will be loaded with the Tivoli Enterprise Management Server At the very least all of them will host an operating system agent Additionally they will have agents for the applications they host such as DB2 Universal Database Hypertext Markup Language HTTP Server and so on Note the following points gt All these agents connect to the appropriate primary and secondary Remote Tivoli Enterprise Management Server gt On z OS the agents connect only to the local Remote Tivoli Enterprise Management Server using SNA gt The Tivoli Enterprise Management Server Remote is connected to the Hub Tivoli Enterprise Management Server IBM OM Agent Appl Sys Figure 1 12 General IT infrastructure environm
387. st group called ROUTER contains a set of information pertaining to the routers availability A router may have the following status Verify The SNMP Data Provider is in the process of verifying router status Online The router is active and operational Offline The router is not operational Passive The router is a daemon and is not actively participating in the network operation When starting the SNMP data provider reloads the already discovered routers from the KUMSROUT file Chapter 3 Using Physical views 177 Figure 3 44 shows the routers status Because the production network is isolated from the other networks there is no active router The router detected on the intranet network 9 121 131 0 is the one used as the default gateway on the server running the Universal Agent ROUTER blade8 SYSADMIN oy x File Edit View Help o gt AMOHABR AD SCOM SOUBAETRARD E E View Physical Router Name RouterAddress Router Description Router Status Route Count Destination Networks DD Enterprise 255 255 255 255 255 256 255 255 Verity 1 UNIX Systems 9 212 131 254 9 212 131 254 Verify 1 Ga Linux Systems 10 1 1 209 10 1 1 209 Passive 0 EH Windows Systems Ba BLADE10 h BLADE11 P BLADE12 h BLADES 8 Universal Agent HHE 10 1 1 131 NTERNETO0 10 14 131 SNMP MANAGER00 E MANAGED NODES MIBNODATA MIBSTATUS NETSUMMARY NETWORK TRAP fe 10 1 1 131HTTPdp UAGENTOO
388. states do not allow disclaimer of 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 made to 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 at any time without notice Any references in this information to non IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites The materials at those Web sites are not part of the materials 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 without incurring any obligation to you Information concerning non IBM products was obtained from the suppliers of those products their published announcements 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 on the capabilities of non IBM products must be addressed to the suppliers of those products This information contains examples of data and reports used in daily business operations To illustrate them as completely as possible the examples include
389. stemHostJob hulls SIS aak E Disk MH Enterprise Services 4 Winlogon Job 0 74d85e ER Memory Winlogon Job 0 74d65e L EH Network o aoo00 80000 120000 EH Printer 00 4 0 2 0 Milliseconds our P MEE V E Job Object Eneee C Total mSec Kernel Mode i M Totali msec Processor Historical Job Object ASERS Take Action gt i s Count Terminated E Total msec User Mode RET R E Job Object Details ink To 4 i j 7 Historical Job Object Details WBLADE12 NT Primary BLADE12 NT ee Situations E Historical Process Overview i Curren CUrrenic curren A a a 5 ji i This Period mSec This Period mSec This Period mSec Process Count Process Count Proc Name Uni amp Print Preview bel Kernel Processor User gt B Print Mode Time Time Mode Time Kernel Mode Processor User Mode Active Terminated Winlogon Job 0 74 0 0 0 0 491 093 49 140 31 1 0 WmiProviderSubSys E Properties 0 0 0 078 593 10 468 2 609 1 0 _Total 0 0 0 0 569 686 59 608 2 640 2 0 i gt I Primary BLADE12 NT S Hub Time Fr 03 17 2006 03 02 PM I Server Available Job Object 9 212 128 31 WOLF1 Figure 3 2 The Windows system navigator subtree Process workspaces 124 In Figure 3 2 one Table view and two Bar Chart views are used The different ways of presentation enable a quick overview of the key metrics presented A user can modify all the workspaces However the IBM Tivoli Monitoring V6 system administrator may prevent specific views from b
390. stems and the middleware components 56 Infrastructure Solutions Building a Smart Bank Operating Environment 2 1 3 IBM Tivoli components This demonstration simulates 24 hours in a bank operation through a realistic scenario Many Tivoli System Management products and monitoring tools are used to track monitor and react to different events in a day These include the following gt IBM Tivoli Monitoring Services V6 1 Product number 5698 A79 is the foundation on which all IBM Tivoli OMEGAMONSs mainframe and distributed are built This replaces the old CT engine 350 with the CT engine foundations Following are the three components included in the IBM Tivoli Monitoring Services solution IBM Tivoli Enterprise Portal earlier called CandleNet Portal IBM Tivoli Enterprise Portal Server earlier called CandleNet Portal Server IBM Tivoli Enterprise Management Server IBM Tivoli OMEGAMON XE for CICS on z OS V3 1 0 Product number 5698 A58 provides a comprehensive means of gathering information to detect and prevent problems within the CICS regions IBM Tivoli OMEGAMON XE on 2 OS V3 1 0 Product number 5698 A59 provides comprehensive performance information covering a single z OS image or the sysplex level Tivoli OMEGAMON XE on z OS V3 1 0 integrates Tivoli OMEGAMON XE for sysplex Tivoli OMEGAMON XE for OS 390 and Tivoli OMEGAMON XE for cryptographic coprocessor IBM Tivoli OMEGAMON XE for Storage on z OS V3 1 0 Product
391. sts all the distribution packages for the AIX and Linux systems IBM Tivoli Monitoring agents The local agents on this system the operating system agent connect only to the local Remote Tivoli Enterprise Management Server If the machine is lost which is one of the assumptions a secondary connection will not help gt Onz OS Moveable Hub Tivoli Enterprise Management Server On z OS the Tivoli Enterprise Management Server Hub feature Hot Standby does not exist at all For the Tivoli Enterprise Management Server Hub on z OS a special solution the Moveable Hub is implemented by Tivoli services The idea behind this is that on z OS the sysplex functionality enables functions such as Virtual IP Address VIPA which can also be used by Tivoli components such as Hub Tivoli Enterprise Management Server For a detailed description refer to The Moveable Hub on page 40 Each LPAR hosts its own Remote Tivoli Enterprise Management Server The communication with the Tivoli Enterprise Management Server Hub uses only SNA based communication All the z OS based agents connect to their local Tivoli Enterprise Management Server Remote using only SNA No other protocol is configured gt Linux on IBM System z Linux on IBM System z runs under z VM the virtualization capability for the IBM System z platform It enables the moving of a Linux on IBM System z image from one physical machine to another All the addresses att
392. support for z OS applications Ensure that the version of the products selected here match the versions installed on z OS If the installation process is run multiple times ensure that the same version is selected each time Otherwise the data is corrupted and the product generates unpredictable results The default installation of the Tivoli Enterprise Portal Server does not include the application support ODI files for managing the agents running on z OS Therefore it is necessary to install application support for zZ OS OMEGAMON V350 agent and V360 agent on the Tivoli Enterprise Portal Server Because in our environment all the agents running on z OS are connected to the Tivoli Enterprise Monitoring Servers Remote located on z OS systems it is not necessary to perform this task on the Tivoli Enterprise Monitoring Servers Remote installed on the AIX and Windows platforms Remember that the Tivoli Enterprise Monitoring Server Hub runs on z OS Therefore there is no necessity to update the application support on this server as well 100 Infrastructure Solutions Building a Smart Bank Operating Environment The CD Monitoring Services on z OS 350 360 Workspace Enablement V6 1 contains the specific setup and packages to install the application support Download the contents of this CD from the OMEGAMON v350 v360 Application Enablement Web site https wwwl4 software ibm com webapp iwm web reg download do source tmd1 amp S_PKG d1 amp cp U
393. t ABRRBRPFAD SOOWl SBRSUBARAARV OPTED Branch channel O 8 oO R Response time Servlet milliseconds Deox bladed Channel Access Ponts f hitraret i blades D Average Servlet Response Time 20 40 60 80 100 120 03 Dwonkload Type B Dwonkload Type M Number of Occurrences number of Occurrences DiRate of Occurrence DiRate of Occurrence ie manae Time lidet Brosisae Time CTG Delay Time CTG Delay Time EJB Home Delay Time GEIB Home Delay Time EJB Local Home Delay Time EJB Local Home Delay Time EJB Method Delay Time ELB Method Delay Time M Heap Allocation Delay Time Heap Allocation Delay Time Buca Delay Ti CA Delay Ti Ind ee bladed San Bums Delay Time MMs Delay Time EUNDI Delay Time EUND Delay Time a er aa O Miscellaneous Delay Time gt 7 O Miscellaneous Delay Time Osenvlet Delay Time Osenvlet Delay Time O 20 40 60 80 100 120 140 id o 100 200 300 400 ry Figure 5 16 Branch view Table 5 11 shows the base queries we used to create the Logical view from the assigned agents in Figure 5 16 Table 5 11 Branch view queries Assigned agent and situation Assigned managed system WebSphere Application Servers for all WebSphere Application Server versions Web Applications Query branch machines Inx4 and Inx5 on Web Applications Z VM and Blade4 and Blade5 WebSphere Application Servers for all WebSphere Application Server ve
394. t Download the Fix Pack 1 3 0 TIV OXEWebSphere Application Server IFO005 to support the WebSphere Application Server V6 0 This Fix Pack is applied after the installation of the agent code gt Ensure that the application support for Tivoli OMEGAMON XE for WebSphere Application Server is installed on all the Tivoli Enterprise Monitoring Servers and Tivoli Enterprise Portal Servers 108 Infrastructure Solutions Building a Smart Bank Operating Environment Installation The installation on z OS fails with the following error message Memory fault install sh failure terminating license declined As a workaround before launching the installation script install sh specify an alternate Java run time environment JRE path to Java 1 4 2 Linux on IBM System z 64 bit In this case we use the Java available in the IBM Tivoli Monitoring OS agent directory From the ksh shell enter the following command export alternateJRE opt IBM ITM JRE 1s3266 When executing the install sh script ensure the following gt The OMEGAMON agent home directory CANDLEHOME is opt IBM Omegamon This may be different in your environment This directory must be separate from the one used for the IBM Tivoli Monitoring agents gt Choose the WebSphere Application Server Monitoring Agent V130R205 Configuration The configuration program guides you in defining the protocols and ports used for the connection to the Tivoli Enterprise Monitoring Server
395. t Bank TEP administrator the sublevels are added to some of the channels in order to provide more specific information at these levels This is an implementation of a drill down approach When an alert is received the user expands this corresponding level to analyze from which sublevel the incident comes from Using the existing physical tree or the logical tree When using the Edit Navigator view select the appropriate source view in the right side of the window in the Physical view or in an existing Logical view Develop that view up to your point of interest Drag this point and drop it into the left side of the window in your Logical view at the level you have chosen This process adds a child with content equal to the tree selected in the source window The target source in the right side of the window can be changed at any time to add new children This process is an easy way of reorganizing physical data because it adds parts of the existing trees physical or logical their existing setup queries views and situations attached quickly 188 Infrastructure Solutions Building a Smart Bank Operating Environment Recommendations A Logical view is a tool that is used on a daily basis Therefore this Logical view must be meaningful and easy to use In order to achieve this follow the rules listed here gt gt Use meaningful names for each part of the tree Use standards Keep the depth of the tree at three or
396. t IBM Corp 2006 All rights reserved 257 5 1 Core system transformation service oriented architecture This section shows the new service oriented architecture model working at full volume In the defined views we will show how the Web service channels and the channels using the process mechanism meet service level agreements at a higher enterprise level by measuring the response time the service class in WebSphere z OS for the process running under WebSphere Business Integration Server Foundation In this section the focus is more on the actual components and mechanisms used in order to show at a more detailed level the process of monitoring and managing them In this context some of the techniques suggested by IBM to help enterprises transform the use of their core systems and leverage the key functionality that is otherwise difficult to expose is also discussed 5 1 1 Introducing the architecture through Tivoli Enterprise Portal We created a number of Logical views using Tivoli Enterprise Portal TEP for this IBM Redbook project which we used for the Smart Bank showcase As a base we started with the physical monitoring tree listing the following key monitoring environments IBM System z9 environment Linux environment AIX environment Windows environment vvvy Within these high level environments the subsystem monitoring described in the earlier chapters exists In our case we explored two key areas in a Smart Bank sh
397. t is 1918 2018 Enter name of KDC_PARTITION Default is null Configure connection for a secondary CMS YES or NO Default is NO YES Secondary CMS HostName Default is blade3 bladell production 1local Will the agent connect through a firewall YES or NO Default is NO Secondary CMS protocol ip sna or ip pipe Default is ip ip pipe Now choose the next protocol from one of these ip sna none Secondary CMS Protocol 2 Default is none ip Now choose the next protocol from one of these sna none Secondary CMS Protocol 3 Default is none Secondary CMS IP Port Number Default is 1918 2018 Secondary CMS IP PIPE Port Number Default is 1918 2018 Enter Optional Primary Network Name or none Default is none 10 1 1 126 WebSphere path Default is opt WebSphere AppServer opt IBM WebSphere AppServer kwe xml updated Agent configuration completed Applying the Fix Pack Perform the following tasks to apply and configure the Fix Pack on the Tivoli OMEGAMON agent 1 Stop the Tivoli OMEGAMON agent using the following command lt CANDLEHOME gt bin CandleAgent stop we 2 To stop all the monitored application servers a First retrieve the running servers using the following command lt WAS_dir gt bin serverStatus sh al b Then use the following command lt WAS_dir gt stopServer sh lt application_server_name gt 3 Ata shell prompt from the lt CANDLEHOME gt directory run the following com
398. ta space server CICS Business Event Publisher for MQSeries rules database The workstation administration client vvvyv CICS Business Event Publisher for MQSeries event connectors CICS Business Event Publisher for MQSeries event connectors allow you to monitor events that occur within specific areas including the following gt ACICS event source connector running in a CICS region which allows you to monitor VSAM file control temporary storage transient data interval control and program control LINK requests gt A DB2 event source connector running on a z OS address space which allows you to capture DB2 database events for any DB2 table with change data capture enabled Chapter 3 Using Physical views 155 Note In our installation we use the event monitoring for DB2 to track the changes in the posting table in the banking database Because every banking transaction involves an update of the posting table the table is a good candidate for event monitoring gt An IMS event source connector running in a z OS address space that allows you to capture IMS DB events for any database that has IMS change data capture enabled This includes IMS DB TM Database Control DBCTL and IMS batch CICS Business Event Publisher for MQSeries supports a range of database types that include hierarchical indexed sequential access method HISAM simple hierarchical indexed sequential access method SHISAM hierarchical direct access method HDAM p
399. tainer hanndet hasr11 eamnensate rib iariCnmn 4 n n Annn mo 3 aS el ContainerName Default EJB Container CS Hub Time Di 03 1 4 2006 06 00 PM JE Server Available Enterprise Java Beans 9 212 128 31 WOLF1 Figure 3 22 The EJB Container workspace Web applications using EJBs are measured from the single methods that are invoked by the Web applications or other EJBs An EJB by itself does not have a response time Set the following rules gt For system programmers None at this time gt For business managers EJB specific response time measurements EJB specific invocation rate Most of the time these situations are client specific Chapter 3 Using Physical views 147 The DB Connection Pool workspace This workspace as shown in Figure 3 23 provides details about the information provided by the Data source workspace In this workspace only the data sources to the database are displayed but with more specific information N fX 0 li a pe se eae File Edt View Favorites T Address http 9 212 128 31 1920 cnpykat bal EJ Go ay Tivoli Enterprise Portal File Edit View Help HHBR AM SFS OO C SQSWRBRBERERHM OTED 3 View Physical ag g O8 WEC EATER HTTP Sessions E jdboscoREBANKas jdbc COREBANKds Datasources e e a Lock Analysis jdbo BDWids jdbe BDWids CTG Summary Fi JMS Summary jdbe BPEDB jdbo BPEDB Web Applications mR
400. te sna PSSCBA TIVHUBLB CANCTDCS SNASOCKETS KDSNC004 Bind of local location broker complete ip pipe 10 1 1 29 2018 KDSNC007 Local Location Broker is active KDSNCO08 Global Location Broker is activ 82 Infrastructure Solutions Building a Smart Bank Operating Environment SNA initialization between z OS Tivoli Enterprise Monitoring Server Remote and z OS Tivoli Enterprise Monitoring Server For the z OS Tivoli Enterprise Monitoring Agent a successful SNA initialization message is registered in the RKVLOG for BAO1 and BAO2 The example shown in Example 2 6 is based on Tivoli OMEGAMON II for Multiple Virtual Storage MVS Tivoli Enterprise Monitoring Server RKVLOG messages Example 2 6 z OS Tivoli OMEGAMON XE for MVS on z OS SNA initialization messages ON BAO1 BSS1 GetEnv KDCFP_ALIAS KDCFC_ALIAS KLXBS_ALIAS KO1M2EQ BSS1 GetEnv KDCFP_TPNAME KDCFC_TPNAME KLXBS_TPNAME SNASOCKETS BSS1 GetEnv KDCFP_MODE KDCFC_MODE KLXBS_MODE CANCTDCS getEnv AF_SNA configuration Alias KO1M2EQ Mode CANCTDCS TpName SNASOCKETS eee eee ee KDE1I_ OpenTransportProvider Transport opened com1 sna pipe ON BAO2 BSS1 GetEnv KDCFP_ALIAS KDCFC_ALIAS KLXBS_ALIAS K02M2EQ BSS1 GetEnv KDCFP_TPNAME KDCFC_TPNAME KLXBS_TPNAME SNASOCKETS BSS1 GetEnv KDCFP_MODE KDCFC_MODE KLXBS_MODE CANCTDCS getEnv AF_SNA configuration Alias KO2M2EQ Mode CANCTDCS TpName SNASOCKET eee ecee KDE1I_ OpenTransportProvider T
401. ted during the setup of the SNMP data provider The attribute group contains useful information pertaining to the nodes available on the production network 178 Infrastructure Solutions Building a Smart Bank Operating Environment gt Name attribute This contains the host name of the node as defined in the Domain Name System DNS or hosts file or the TCP IP address only if the host name cannot be resolved not defined in DNS or hosts file However the TCP IP address is always displayed even if no node on the network used this address In such a situation the Status attribute is Unknown gt Status attribute When the node is up the status is Online Otherwise the status is always Unknown There is no way of making a distinction between node down meaning it is now Offline but was up in the past and the nonexisting node gt Type attribute If SNMP is enabled on the remote node the SNMP data provider is able to determine the node type router bridge and so on The data provider must know the SNMP read only community authorized by the remote node to access the Management Information Base MIB The default community is Public However this may be different based on the information provided in the following The KUMP_SNMP_NET_COMMUNITY environment variable to define the default SNMP community name The KUMSCOMM file to define the SNMP community name for a particular network address gt Location attribute The inf
402. ter 2 IT environment of the Smart Bank showcase 73 6 In order to verify the SNA communication display the VTAM applid for the Hub and the Remote Hub using the D NET command as shown in Figure 2 21 D NET ID TIVHUBLB E ISTO97I DISPLAY ACCEPTED ISTO75I NAME PSSCBA TIVHUBLB TYPE APPL 236 IST4861 STATUS ACT S DESIRED STATE ACTIV IST14471I REGISTRATION TYPE CDSERVR IST977I MDLTAB NA ASLTAB NA IST861I MODETAB KDSMTAB1 USSTAB NA LOGTAB NA IST9341 DLOGMOD CANCTDCS USS LANGTAB NA IST1711 ACTIVE SESSIONS 0000000006 SESSION REQUESTS 0000000000 IST2061 SESSIONS IST6341 NAME STATUS SID SEND RECV VR TP NETID IST635I KOIDSLB ACTIV S CDD3C505D133D227 0A10 0001 PSSCBA IST635I KOZDSLB ACTIV S CDD3C505D133D200 0A00 0001 PSSCBA IST635I KOIDSLB ACTIV P CDD3C505D133D226 0001 0996 PSSCBA IST635I KOIDSLB ACTIV SV P CDD3C505D133D225 0001 0001 PSSCBA IST635I KO2ZDSLB ACTIV P CDD3C508D133E5D4 0001 09A0 PSSCBA IST635I KO2DSLB ACTIV SV P CDD3C508D133E5D3 0001 0001 PSSCBA IST3141 END Figure 2 21 VTAM applid display for the Hub 7 This screen Figure 2 22 shows that the names of the sessions KO1DSLB and KO2DSLB are the active session names in our Hub Tivoli Enterprise Monitoring Server Display the information for this session using another D NET command for the Remote Hub located in BAO1 TIVHUBLB is the active session name for our Remote s Hub located in BAO1 TIVHUBLB is the active session name of our Rem
403. terprises address hardware manageability reliability and flexibility by allowing clients to horizontally scale their implementation easily with different types of CPU common chassis specifications and hot swap capabilities among other capabilities We deployed our additional branch server applications to four HS20 8832 G1X blades running SUSE Linux V9 on the BladeCenter in a WebSphere V6 cluster for high availability The z VM environment Our choice of mission critical branch server implementation platform is the z VM environment where unlike the BladeCenter resources such as memory and CPU can be shared Consequently if one branch server is under utilized we do not have resources tied specifically to that server The available z990 or System z9 109 resources can be allocated to the branch servers that receive the bulk of the workload One of our goals for Smart Bank is to show our clients that System z9 109 and IBM System z can always run at 100 CPU utilization The virtual machines running on our z VM LPAR on z990 development environment for this book and System z9 109 production environment run the same level of SUSE Linux V9 and the same WebSphere V6 cluster configuration with the same branch server application as the BladeCenter Some of the other qualities of service that the z VM environment brings to our branch servers are gt Virtual network within the 29 109 machine using virtual local area network VLAN and HiperSocke
404. th two CTG instances one per z OS LPAR gt CICS Business Event Publisher BEP V1 2 is used to publish and populate the BDW database in real time It is configured with Three address spaces in BAO1 one data space server one message server and one DB2 event collector A Batch for DB2 BDW population in BAO1 gt Named Counter Server is used by the corebanking COBOL application It is configured with two address space servers one per z OS LPAR Figure 2 4 shows the operating systems and middleware infrastructure used for the Smart Bank development and for this book Montpellier Firewall router E IBM eServer xSeries S x335 z990 B16 OWindows XP BladeCenter OzlOS 1 7 gt Workload generator OWindows XP gt CICS TS 3 1 a gt Tivoli Enterprise gt CTG V5 0 1 amp V6 0 0 meee iae ao inux 8 gt CICSplex SM 3 1 4 paes 4 Event Publish gt WebSphere Application VA gt usiness Event Publisher m Server V5 0 2 gt WebSphere Application Server gt DB2 UDB V8 2 oye a PP CISCO 6509 Switch DAIX 5 2 gt Websphere Application Server gt WebSphere Application V6 pR Sd _ Server V5 1 gt WBI SF V5 1 gt Siebel Business Analytics gt WebSphere MQ V5 3 1 s v7 7 1 gt DB2 z OS V8 2 gt Fidelity Corebank V4 2 gt Fair Isaac TRIAD V8 0 OzVM 5 2 z Linux Guest ue Linux Enterprise Server gt WebSphere Application Server V5 0 2 gt WB ISF V5 1 gt DB2 UDB V8 2 Figure 2 4 The operating sy
405. the concepts of business continuity and from an IT point of view we achieve recovery redundancy and hardening Using TEP we run the different scenarios of planned and unplanned outages Having discussed some of the ways in which to counter operational risk we now turn to credit risk reporting another aspect of Basel II compliance We return to Siebel Business Analytics to reuse the business intelligence framework for regulatory compliance reporting with credit risk For branch consolidation and the ability to have platform independence we choose a platform based on the quality of service Simplification of the infrastructure is achieved We discuss the concepts of branch transformation and how we have simplified the environment and saved costs a The time is sometimes contrived for purposes of demonstration The business event does not have to be restricted only to this timing Chapter 1 Introducing the technical architecture of the Smart Bank showcase 13 1 2 Architectural choices This section contains a synopsis of some of the key decisions and thinking behind the architecture we adopted to address our proof points 1 2 1 Banking clients current architecture What architectures do your clients have If you can build the same type of architecture you can better simulate the problems and issues that they are trying to solve Luckily banks have similar architectures They are highly complex but have some key diff
406. 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 business enterprise is entirely coincidental COPYRIGHT LICENSE This information contains sample application programs in source language which illustrates programming techniques 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 application programs conforming to the application programming interface for the operating platform for which the sample 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 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 application programs conforming to IBM s application programming interfaces Copyright IBM Corp 2006 All rights reserved vii Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States other countries or both AIX Geographically Dispersed Parallel Redbooks logo BladeCenter Sysplex Resource Link CICSPlex HiperSockets System i CICS HyperSwap System p Component Business
407. the physical processors on our IBM System z9 109 Our bank is billed for this on a daily basis until such time as they are deprovisioned Through the HMC the number of CPs that have been activated and the monitoring of the On Off Capacity on Demand process are shown To have a more transparent billing of CPU utilization within an enterprise on the IBM System 29 109 is something that a number of clients are looking to implement Under this they pay for what they use and they along with IBM enter into an overall system wide agreement that covers hardware software and services This type of agreement is customized and comes under an Open Infrastructure Offering OIO agreement In this proof point we take a different path down the Logical view tree and move down the Operations track We link to the Operations view from our opening Smart Bank screen Figure 5 1 on page 259 Infrastructure Solutions Building a Smart Bank Operating Environment 5 2 1 The Operations view Figure 5 11 shows the Operations view Red alerts in the TEP are cascaded down the tree hierarchy In this view the fact that the red alert is related to systems management is seen In this Logical view we created a JPEG graphical image depicting our physical environment We added a number of alerts that reflect the status of the underlying subsystems and platforms Not all of them have links but they could We focused only on those aspects that concern our project On the
408. the trace_cn log indicates only the following An installation error occurred on host The script usage is as follows itso_inst_os_agent lt ssh rexec smb gt lt target_hostname gt lt target_passwd gt lt monitoring server gt lt backup monitoring server gt Chapter 2 IT environment of the Smart Bank showcase 105 Example 2 9 shows the entire script used for the deployment Example 2 9 itso_inst_os_agent cmd script listing echo off Product itso_inst_os_agent cmd Description simple script to deploy an OS agent to a s remote computer Created Feb 23 2006 Author IBM Redbook Team Port number to use for communications with the TEMS Remote primary 1918 is the default set P_PORT 2018 Port number to use for communications with the TEMS Remote secondary 1918 is the default set S_PORT 2018 Parameters Connection protocol ssh rexec rsh or smb Note the script assigns the account used for the connection based on the connection protocol e g smb gt Administrator rexec ssh rsh gt root set AccessType l Target computer where OS agent is deployed set Target 2 Password for the remote account set Passwd 3 Monitoring Server hostname set TEMS 4 Backup Monitoring server hostname set BTEMS 5 No parameter if 1 goto HelpMsg Verify if the target is up ping Target n 1 w 3000 find TTL if errorlevel 1 goto TargetDownMsg
409. tify system bottlenecks and evaluating tuning decisions Selecting the most effective threshold values Reviewing the status information when a change in the state of a given resource occurs All the workspaces in OMEGAMON for WebSphere MQ are important to set up successful enterprise wide monitoring WebSphere MQ is spread across the entire company to deliver a common layer for message exchange The monitoring is also spread over these systems The performance and efficiency of this system is a key point for a performing application environment The Channel Performance workspace on page 151 and The Queue Statistics workspace on page 152 demonstrate how varied monitoring requirements between system programmers can be and how they are supported by IBM Tivoli Monitoring V6 and IBM Tivoli Composite Application Manager V6 Infrastructure Solutions Building a Smart Bank Operating Environment The Channel Performance workspace Channels are related to queue managers and their interconnection Except for client channels which are often application specific most of the rules applied for channel performance are system focused A Channel Performance workspace is shown in Figure 3 25 Tivoli Enterprise Portal File Edit View Help HHBR HAA TCO CSQOURBSETARFOTED View Physical g g Oa m Channel Performance Summary Diindoubt Channels M Active Channels Diinactive Channels 20 W
410. tionKey Enter Next Fl Help F3 Back F5 Advanced COMMAND gt Figure 2 18 ICAT Tivoli Enterprise Monitoring Server Configuration Values screen 4 In the screen shown in Figure 2 19 specify the communication protocols you want the Tivoli Enterprise Monitoring Server to support When performing this task keep the following points in mind One protocol must be SNA The communication protocols are used in the priority sequence you set Chapter 2 IT environment of the Smart Bank showcase 71 In the Smart Bank environment we used SNA and TCP After the communication protocol is set press Enter Specify the communication protocols in priority sequence for TEMS HUB CMS IP PIPE gt 2 Non secure NCS RPC IP UDP gt Non secure NCS RPC IP6 PIPE gt IP PIPE for IPV6 IP6 UDP gt IP UDP for IPV6 IP SPIPE gt Secure IP PIPE IP6 SPIPE gt Secure IP PIPE for IPV6 SNA PIPE gt 1 Non secure NCS RPC Note One of the protocols chosen must be SNA PIPE Web Services SOAP Server is enabled TCP protocol is required Enter Next Fl Help F3 Back COMMAND gt Figure 2 19 ICAT Communication Protocols screen 5 This displays the screen shown in Figure 2 20 Specify a unique IP address and a host name The IP address used in our example 10 1 1 29 is a DVIPA Within the z OS sysplex distributor with VIPA an IP address may be linked to the entire sysplex It is not attributed to only one spec
411. tly to the Tivoli Enterprise Monitoring Server Hub When the Universal Agent is successfully connected to the Tivoli Enterprise Monitoring Server Hub the workspace is able to display data Later return to the original Tivoli Enterprise Monitoring Server Remote The reason for this is described in Using the Universal Agent to monitor the IBM HTTP Server on page 114 120 Infrastructure Solutions Building a Smart Bank Operating Environment Using Physical views This chapter describes the main workspaces that we used in the Smart Bank project These workspaces are provided by different products gt From IBM Tivoli Monitoring This is described in 3 1 Physical views from IBM Tivoli Monitoring V6 on page 122 gt From IBM Tivoli Composite Application Manager This is described in 3 2 Physical views from IBM Tivoli Composite Application Manager on page 131 gt From IBM OMEGAMON XE for MQ This is described in 3 3 IBM CICS Business Event Publisher for MQ Series and event processing on page 154 gt From the distributed environment This is described in 3 4 Multichannel architecture Physical views on page 170 Copyright IBM Corp 2006 All rights reserved 121 3 1 Physical views from IBM Tivoli Monitoring V6 122 With IBM Tivoli Monitoring the Tivoli Enterprise Portal Client and Server application was introduced This application enables user monitoring and easy access of all the required system
412. tomLog directives without the mod_logio module LogFormat h 1 u t Zr gt s b common LogFormat h 1 u t Zr gt s 0 Referer i gt ZU User Agent i v q b T itmuniagent Chapter 2 IT environment of the Smart Bank showcase 115 Do not use the common LogFormat CustomLog logs access_log common ITM Universal Agent log format CustomLog logs access_log itmuniagent Deploying the Universal Agent The OS agents were deployed earlier on all our systems Therefore deploying other agents from the Windows Tivoli Enterprise Monitoring Server Remote is possible This must also be carried out from the AIX Tivoli Enterprise Monitoring Server Remote In order to quickly deploy the Universal Agent initiate the installation from the command prompt by performing the following tasks 1 Place the IBMHTTP mdl file in the directory lt ITM_install dir gt CMS depot UACONFIG 2 Edit the IBMHTTP mdl file and verify whether the path defined in the SOURCE control statement matches the location of the access_log file on the target computer 3 Deploy the Universal Agent on the Linux remote target with the following command tacmd addsystem t um n lt hostname gt LZ p UA CONFIG IBMHTTP md1 Note After the first installation of the Universal Agent the TEP is unable to display the contents of the Universal Agent workspaces After connecting the Universal Agent to a Tivoli Enterprise Monitoring Server Remote CAT
413. ts gt Resiliency of the platform with z VM benefiting from some of the Geographically Dispersed Parallel Sysplex GDPS business continuity aspects specifically the GDPS Peer to Peer Remote Copy PPRC HyperSwap of z VM Linux to secondary disks in the event of disk failure gt Workload management on the z9 109 machine at the individual Linux guest machine level gt Virtualization capabilities of the z VM environment allowing considerable horizontal scalability and quick deployment of the virtual servers Our IBM Tivoli Monitoring V6 1 views With IBM Tivoli Monitoring V6 1 we monitored both these environments with the same Linux and WebSphere agents This provided us with a view of our branch environment The BladeCenter solution can be viewed in our context as providing servers for specialized business functions that use the same core branch server functionality Chapter 5 Scenarios and use cases 281 5 3 1 The Branch view Figure 5 16 shows the detailed branch view of the workload from an operational point of view In workspace A the response time in milliseconds of the servlet receiving the workload on each machine BladeCenter and z VM is seen This response time reflects the routing shown in the JPEG diagram on the left with the transaction being sent to our core system running in CICS with DB2 for z OS and the response returning to our Teller and Client Service Representative in the branch File Edit View Help g
414. ttribute groups that are dependent on the type of the reporting agent Infrastructure Solutions Building a Smart Bank Operating Environment If there are multiple instances for example on z OS subsystems on the same system each instance has its own subtree View Favorites T Address http 9 212 128 31 1920 enp ka E EA co a x File Edit nE AO ekee g Tivoli Enterprise Portal File Edit View Help 9 augere Aalls Otl SB GuURBSEFTEARDT FBa 3 View Physical F B G3 UNIX Systems Linux Systems 8 Physical a pa a pa a a a pa a pa Ea e Ba a el a Ue Ca BoP sw a Ew a Deme Windows Systems 2 05 Systems E Situation Event Console BAPD aM Total Events 2 Item Filter Enterprise Loc x 03 v 03 Source Primary BLADE1 2 NT Primary BLADE8 NT Status Display Itern Open Open Situation Name NT_System_Total_Interrupts NT_System_Total_Interrupts Impact E Processor E Processor blade2 blades blade blades A Linux OS WebSphere Application Server Agent E Application Trace Files Shy Agent Events n amp WebSphere Application Server Int Inx1 Inx4 Inxs Inx BAPLEX MYS SYSPLEX BA01 cics DB2 Mainframe Networks MQSERIES MYS Operating System OMEGACENTER Bridge 05 390 Unix LISS Services Management Agent Storage Subsystem WebSphere Application Server 05 39
415. u_ lt ITM_Install_dir gt cms KBBENV Enterprise Monitoring ction_network_id gt lt server_id gt Server UNIX Tivoli Enterprise KDCBO_HOSTNAME lt produ lt ITM_Install_dir gt config kbbenv ini Monitoring Server ction_network_id gt lt server_id gt Windows Tivoli KDCBO_HOSTNAME lt produ_ lt ITM_Install_dir gt cnps KFWENV Enterprise Portal ction_network_id gt lt server_id gt Server UNIX or Linux agents KDCBO_HOSTNAME lt produ_ lt ITM_Install_dir gt config env config ction_network_id gt lt server_id gt read by all products in CANDLEHOME Therefore all the agents installed on the servers use the value defined in KDCBO_HOSTNAME Otherwise update the file lt ITM_Install_dir gt config lt product_co de gt ini Windows operating KDCBO_HOSTNAME lt produ__ lt ITM_Install_dir gt tmaitm6 KNTENV system OS agent ction_network_id gt lt server_id gt Other agents on KDCBO_HOSTNAME lt produ_ lt ITM_Install_dir gt tbd K lt product_co Windows ction_network_id gt lt server_id gt de gt ENV ini 2 When the config file is updated recycle the Tivoli Enterprise Monitoring Server or the Agent 3 When a Tivoli Enterprise Monitoring Server or Agent starts if the KDCBO_HOSTNAME variable is enabled a message is retrieved in the log file as shown in Example 2 8 Example 2 8 KDCBO_HOSTNAME activation in the Tivoli Enterprise Monitoring Server log Monday February 27 2006 19 12 29 AE4 kbbssge c 52 BSS1 G
416. ubsystems or applications collect data and pass the data to the Tivoli Enterprise Portal Server through the Tivoli Enterprise Monitoring Server The agents pass commands from the user to the system subsystem or application An agent interacts with a single system or application and in most cases resides on the same machine where the system or application is running 84 Infrastructure Solutions Building a Smart Bank Operating Environment Component model The component model shows the static structure of the main elements that make up our IBM Tivoli Monitoring environment This is shown in Figure 2 30 TEP Desktop P Browser TEPS DB TEMS DB me f FEMS Remote secondary lt i 7 1 OS Agent Application Agent Universal Agent Figure 2 30 IBM Tivoli Monitoring component model 2 2 2 Platform description The core of the IBM Tivoli Monitoring environment is based on the operating systems as described in Table 2 1 Table 2 1 IBM Tivoli Monitoring servers Platform description IBM Tivoli Monitoring Operating system Comment component Tivoli Enterprise Monitoring vipa z OS Refer to 2 1 The IBM System z environment on page 53 to get more information about the z OS environment Server Hub Tivoli Enterprise Monitoring blade11 Windows 2003 SE Primary Tivoli Enterprise Monitoring Server Remote Service Pack 1 SP1 Tivoli Enterprise Monitoring Server Remote blade7 IBM AIX 5 2 Serve
417. uction network and the intranet network These networks are isolated from one another There is no firewall between the IBM Tivoli Monitoring servers and agents No network address translation is implemented Intranet network Production network TEMS HUB TEMS Remote TEP Browser TEMS Remote 9 amp g TEP Browser TEMA TEMA Figure 2 31 Network topology overview Infrastructure Solutions Building a Smart Bank Operating Environment 2 2 4 Network communication Network communication depends on the protocol used in the environment and the facilities offered by the hardware Communication protocol settings The protocols selected for communication between the IBM Tivoli Monitoring components are based on the following requirements gt Encryption is not required considering that all the communication between the IBM Tivoli Monitoring components are on a protected production network that is unreachable directly from the intranet or other external sources The Tivoli Enterprise Monitoring Server Remotes must communicate with the DVIPA of the z OS system about where the Tivoli Enterprise Monitoring Server Hub is located For such communication we recommend IP PIPE A Moveable Hub solution is implemented on the z OS Therefore the distributed environment must use port 2018 instead of the default port 1918 after verifying that 2018 is not already used for other applications Due to the
418. uilding a Smart Bank Operating Environment Simple Network Management Protocol data provider setup The basic installation of the Universal Agent is done on a Windows platform It must be done on UNIX as well After completing the installation of the Universal Agent customize it by performing the following tasks 1 Update the Universal Agent s configuration file Table 2 7 shows the basic parameter settings of the Universal Agent s configuration file KUMENV Table 2 7 SNMP data provider settings KUMA_STARTUP_DP SNMP The Universal Agent starts the SNMP data provider during the startup KUMP_SNMP_NET_DISCOVERY Y All the network resources are discovered servers gateways and so on KUMP_SNMP_MANAGE_LOCAL_NETWORK Manage the local network Y KUMP_SNMP_NET_DISCOVER_ENTERPRIS Do not manage the status of the entire network E N enterprise Example 2 14 shows a partial output of the configuration file with the definition of the parameters relating to the SNMP Data Provider The Universal Agent runs on a server with multiple network cards Therefore the KDCBO_HOSTNAME parameter is initialized Example 2 14 Partial listing of the KUMENV file KDCBO_HOSTNAME 10 1 1 131 KUM_DCH_HOSTNAME KUM_DP_HOSTNAME KUM_DCH_HOST KUMP_DCH_HOST a a A a a a ea A na aa D a A a aa UA Startup automatic start DP options x ASFS APIS FILE SOCK HTTP SNMP POST ODBC SCRP a NR PN ee ce OR ee EE ee ET rii KUMA_STARTUP_DP
419. ulative preemptab Movable Hub address space BA02 Situation Formula Capacity fj 6 Add conditions mi MYS Address Space BA01 MYS Address Space BA02 B UNIX OS rSampling interval Saund State Windows OS Blade11 D Enable critical wav Critical ddd Play Edit Z Run at start lt m IE Hub Time wed 03 22 2008 9x cancer ar Figure 4 69 A new situation at the Moveable Hub level Chapter 4 Customizing the Logical views 249 Using the Smart Bank Logical view When you click the Operations link in the Smart Bank showcase welcome menu Figure 4 67 on page 247 a new workspace the Smart Bank showcase Operations workspace Figure 4 70 is displayed View 6 Operations 9 212 128 31 SYSADMIN Jeg File Edit View Help ee Gumpe AmS COO EONA Sn J Smart Bank show jperations view AnNVSOrTEE POARI a hk x Enterprise view ee Channel Access Points z OS LPARs internet Intranet 8 z9 utilisation Storage devices gt Linux utilisation Network Enterprise Operational Z V M Linux machines View Internet Banking n Ai Business Analysts Systems Management AIX power 4 blades Muti platform nu 1 O Linux Intel Blades LA Branch x d v lt gt 4 S Hub Time Wed 03 22 2006 03 08 PM gt Server Available View 6 Operations 9 212 128 31 SYSADMIN lt Neils view Figur
420. um 1 i Figure 4 33 Target workspace for dynamic link definition 216 Infrastructure Solutions Building a Smart Bank Operating Environment Defining the target workspace for advanced link definition To demonstrate this a simple example is provided The target workspace WLM Selected Service Class includes only the following two elements Figure 4 34 gt The Logical view navigator gt The view displaying the WLM Service Class File Edit View Help gt OOHBRSAD S 0 4 BOuWUaBSEHERD g 2 amp View Emart Ban v max sources information uE Erg Page 1 of3 EJ Smart_Bank WLM Selected Service Class Resources information E Teller i 5 3 a Authentification ARa Flas anod Soal Percentile eaeh vaue Duration Pecpome tiie HEA E a Banking BAPLEX BAO1 MVSSYS BAT_DISC 1 Discret 0 nia 0 0 0 a cics BAPLEX BAO1 MVSSYS BAT_3V30 1 Velocio 0 Medium 30 0 0 DB2 BAPLEX BAO1 MVSSYS BAT_3V40 1 Velocio 0 Medium 40 0 0 MQSeries BAPLEX BAO1 MVSSYS BAT_3V50 1 Velocio 0 Medium 50 0 0 TCP BAPLEX BA01 MYSSYS BATCH 1 Velocio 0 Medium 25 0 0 WebSphere BAPLEX BA01 MVSSYS BATCH_HI 1 Velocio 0 Medium 30 0 0 zos BAPLEX BA01 MYSSYS BATCHHOT 1 Velocio 0 Highest 50 0 0 r Teller Channel BAPLEX BAO
421. unning correctly for some reason This situation is useful for testing whether the trigger programs are correctly set up When the MQ monitor is unable to test the existing processes the information required is made available in this manner Testing the existence of processes is performed through the operating system agent Note There only a few examples available on WebSphere MQ Monitoring The product comes with a lot of predefined situations Most of them are not activated after the installation We recommend that you review these rules and amend them to suit your installation Chapter 3 Using Physical views 153 3 3 IBM CICS Business Event Publisher for MQ Series and event processing This section describes the way we used the CICS Business Event Publisher for MQ Series to populate our data warehouse database in the following order gt Overview of CICS Business Event Publisher for MQSeries gt The way this was implemented in our Smart Bank showcase infrastructure gt Physical views from the OMEGAMON XE for MQ to explain the CICS Business Event Publisher in action 3 3 1 Overview of CICS Business Event Publisher for MQ Series CICS Business Event Publisher CICS BEP for MQSeries V1 2 helps you to gain maximum value out of your existing core business systems It enables you to create MQ Series messages based on events within your applications allowing you to rapidly integrate and extend the existing current CICS DB2 and Informati
422. ure Solutions Building a Smart Bank Operating Environment gt This project uses a private giga bit network as shown in Figure 2 3 for workload injection and for the Tivoli monitoring infrastructure All the other remote hubs and agents in the distributed platform use the dynamic virtual IP address DVIPA address 10 1 1 20 for BAO1 10 1 1 21 for BA02 10 1 1 29 for the DVIPA address RO ALL D TCPIP NETSTAT HOME IEF1961 IEF2371 782A ALLOCATED TO SYS00250 EZZ2500I NETSTAT CS V1R7 TCPIP 374 HOME ADDRESS LIST ADDRESS LINK FLG 10 1 1 20 GEOLINK 200 1 1 20 HECLINK P 190 1 1 1 EZASAMEMVS 10 1 1 29 VIPLOA01011D I 200 1 1 5 VIPLC8010105 190 1 1 1 EZAXCF02 127 0 0 1 LOOPBACK 8 OF 8 RECORDS DISPLAYED END OF THE REPORT EZZ25001 NETSTAT CS V1R7 TCPIP 185 HOME ADDRESS LIST ADDRESS LINK FLG 10 1 1 21 GEOLINK 200 1 1 21 HECLINK P 190 1 1 2 EZASAMEMVS 190 1 1 2 EZAXCFO1 10 1 1 29 VIPLOA01011D 200 1 1 5 VIPLC8010105 127 0 0 1 LOOPBACK 8 OF 8 RECORDS DISPLAYED END OF THE REPORT Figure 2 3 Smart Bank networking for the test system gt CICSPlex SM V3 1 CPSM is used for CICSPlex Single System Image management providing a single point of control and dynamic workload transaction balancing over the corebank ClCSplex CPSM is configured with Two coordinating address space CAS one per z OS LPAR Two CICSPlex SM address space CMAS one per z OS LPAR gt CICS Transaction Server V3 1 CICS TS is
423. used as the backend corebanking COBOL application to host the CoreBank 4 2 application It is configured with Two terminal owning regions TOR one per z OS LPAR Six application owning regions AOR three per z OS LPAR gt IBM DB2 V8 1 is used for data store and is configured with two DB2 instances in data sharing mode One for operational corebanking application data store using the financial services data model FSDM with two members one per z OS LPAR One for data warehouse using the model banking data warehouse model from the Dublin software group SWG with two members one per z OS LPAR Chapter 2 IT environment of the Smart Bank showcase 55 gt WebSphere MQ for z OS V5 3 1 is used as the classical access layer for corebanking and for publishing It is configured with Two queue managers one per z OS LPAR Two channel initiators one per z OS LPAR gt WebSphere Application Server V5 0 2 with WebSphere Business Integration Foundation Server V5 1 WBIFS is used for the ATM Teller and Internet banking channel applications and for the service oriented architecture SOA It is configured with one servant region in BAQ1 gt WebSphere Application Server V6 is used for the ATM Teller and Internet banking channel application It is configured with two servant regions one per z OS LPAR gt CICS Transaction Gateway CTG V6 is used for J2EE connectors and for the SOA activity It is configured wi
424. ux 8 0 ea x OTwo JS20 POWER4 gt 2 z OS 1 7 application LPARs Re blades with AIX 5 2 gt 1 zVM 5 2 LPAR gt 6 z Linux LPARs gt 1 Coupling Facility LPAR for Parallel Sysplex 2105 ESS800 Figure 2 2 Hardware infrastructure components The Smart Bank operating environment is not just a collection of product demonstrations It is a real z OS operating environment with real life mixed workloads generated by real business applications It is a large scale operational environment that simulates major application processes in a large bank The database owns six million clients and 12 million client accounts and is running a complex transactional workload between 100 800 transactions per second The corebanking application is based on an Independent Solution Vendor ISV Fidelity application named CoreBank V4 2 2 1 2 The operating systems and the middleware components The project is based on z OS for the corebanking backend infrastructure Following are the components gt z OS 1 7 in Parallel Sysplex mode with Two z OS V1 7 LPARs namely BA01 and BAO2 Sysplex named BAPLEX One CF LPAR named CF1 One LPAR with z VM V5 2 Five Linux on IBM System z guests in SUSE V9 64 bit usage One Linux on IBM System z guest in SUSE V9 32 bit usage gt Communication Server V1 7 as the network server with Systems Network Architecture SNA and TCP IP configured for both LPARs 54 Infrastruct
425. veable Tivoli Enterprise Monitoring Server Hub with Systems Network Architecture SNA communication Tivoli Enterprise Monitoring Agent in z OS is connected to the Tivoli Enterprise Monitoring Server Remote in z OS by an SNA communication Figure 2 15 shows the Tivoli monitoring infrastructure that is put in place for the Smart Bank showcase Hub TEMS y Remote TEMS Appl Sys Figure 2 15 The Smart Bank Tivoli Monitoring Services infrastructure with the Moveable Hub Chapter 2 IT environment of the Smart Bank showcase 69 The configuration process Following are the steps involved in configuring the primary Tivoli Enterprise Monitoring Server Hub in the z OS sysplex environment 1 In our case Tivoli Monitoring Services on z OS V6 1 0 is selected in the Product Selection screen Figure 2 9 on page 65 2 To configure Tivoli Enterprise Monitoring Server as the Tivoli Enterprise Monitoring Server Hub select option C as shown in Figure 2 16 RUNTIME ENVIRONMENTS RTEs Actions A Add RTE B Build libraries C Configure L Load all product libraries after SMP E D Delete U Update V View values Z Utilities Action Name Type Sharing Description BASE BASE RTE BASE for TIVOLI Smart Bank Sysplex BAPLEX BAO1 SHARING BASE RTE SHARE for TIVOLI Smart Bank LPAR BAO1 BA02 SHARING BASE RTE SHARE for TIVOLI Smart Bank LPAR BA02 c HUB SHARING BASE RTE SHARE for moveable HUB Smart Bank Enter Next Fl Help F3 Back F7
426. ves selecting Actions Advanced Add TEMS Application Support If this task is not performed some of the products do not function 2 2 10 Deploying the remote operating system agents The remote deployment from the command prompt enables you to quickly distribute the OS agents and get them up and running from a central location In our environment all the OS agents are installed from the Windows Tivoli Enterprise Monitoring Server Remote When the OS agent is available on a target server it is possible to install other agents directly from the Tivoli Enterprise Portal or from the Tivoli Enterprise Monitoring Server command prompt 104 Infrastructure Solutions Building a Smart Bank Operating Environment Populating the deployment depot Before beginning the installation ensure that the packages are already in the depot server where the installation process is run By default our depot does not contain all the packages required to install the OS agents on the following platforms SUSE Linux Enterprise Server 9 Intel SUSE Linux Enterprise Server 9 for IBM eServer zSeries 64 bit SUSE Linux Enterprise Server 9 for IBM eServer zSeries 31 bit AIX 5 2 64 bit YYY Y In order to add the OS agent for Linux on System z 64 bit use the tacmd addBundles commands tacmd addbundles i lt ITM_zlinux_CD gt unix t 1z p 1s3266 In this command the parameters indicate the following gt The parameter i specifies the source of the installati
427. vice oriented Logical views Figure 5 7 shows the results of running the workload described in step 2 IBM Tivoli Composite Application Manager for SOA is able to provide a Logical view identifying the individual Web services through the use of the Java API for Extensible Markup Language based Remote Procedure Calls JAX RPC On the right hand side the response time in milliseconds for each individual Web service is displayed This response time includes transaction routing from WebSphere z OS to CICS through WebSphere MQ accessing and updating DB2 on z OS through the Fidelity Corebank application and back again Chapter 5 Scenarios and use cases 265 Figure 5 7 is a JPEG image loaded as a graphic into one of the TEP frames with alerts superimposed as with the initial Smart Bank and Enterprise views A diagram that conforms to the IBM SOA reference architecture is displayed here As indicated earlier we use the term Integration Hub because we do not have the WebSphere V6 implementation of the Enterprise Services Bus implemented in our project environment File Edit View Help 5 gt 8 0m SRLeM A SOOWM SHSMUBARTANRF STEED O 80 x R Average response time Average response time Daverage Elapsed Message Round Trip Time O80 x 1 Service Oriented Architecture view Beara R XH o oal g SOA New Programming interaction Senice Process Services PostingInquiryCounterwWS D
428. vices using open standards Now it is up to the institution whether these functions are invoked as Web Services as shown here in order to demonstrate IBM Tivoli Composite Application Manager for SOA or as enterprise services using the WSDL definitions to help integrate the core system functionality 266 Infrastructure Solutions Building a Smart Bank Operating Environment After using IBM Tivoli Composite Application Manager for SOA that is deployed here on z OS for a better understanding of our services we select the IT Services Management link in the window shown in Figure 5 7 This displays the window displayed in Figure 5 8 Here the size of the individual service messages and the number of messages flowing through the system are monitored File Edit View Help gt OERBREAM SCOHM SBOSMBAHRAARFOPFTBOH FTI Number of messages manx Number of messages Transfers PostinginquiryCountenns EA PostinginquiyAtmWwS CustomerArrangementListwS f C Message Count ChequeDepositWS CashWithdrawis CashDepositws A BillPaymentWS HA BalancelnquirwS FI Message Size in Bytes a0 x Message Size in Bytes Transfers TransfeiwS PostingInquiryAtmwS PostinginquiryAtmiw s i Dlaverage Message Length CustomerArrangementListwS CustomerArrangementListiS ChequeDepositw s i ChequeDepositwS a o 200 400 600 800 1000 1200 1400 1600 Figure 5 8 Service mana
429. w Help gt OUR BROMAD SOOV SONUBASEHARFA OTHE E View Physical he max Beier manx o g on End Connection Correlation e Connection Job AGNT Package A Ea Baot F Plan ID ID Authorization Type Us Name asip DBRM Collection cics EJ CBMPLAN DB2CALL CBMDES1 BATCH CBMDES1 173 DB2 5 s CB01 B401 DB2 5 System Status Detailed Thread Exception Lock Conflicts H iE Triggers Ooaao x Subsystem Management In Trigger Trigger Trigger Trigger Log Manager B DB2 B2 DB2 CPU Elapsed CPU Elapsed Utility Jobs i CPU Time Not Enclave Not Enclave In Enclave In Enclave EDM Pool 07 00 00 13 08 417 00 00 13 08 00 00 00 000 00 00 00 000 Buffer Pool Management Volume Activity s Physical s Neils view Thread Activity ser Defined Functions uong dh gt HHO aL oon Elapsed CPU MVS CPU Parallel Active In UDF UDF UDF UDF UDF Time Time Status Rate Tasks Tasks UDF TCB Wait Elapsed SAL SaL WAIT REMREQ 10 02 20 000 00 06 43 808 WAIT MISC 0 0 oo o Time Wait Time Time Time __ Elapsed Time Events 00 00 00 000 00 00 00 000 00 00 00 000 00 00 00 000 00 00 00 000 0 i Stored Procedures U Eg x avePoints SP SP SP SP g i Release Rollback S Elapsed SQL Schedule Schedule Schi Savepoints Savepoints Savepoints Time Elapsed Time Wait Time Current Wait Time Ww 0 0l 0 00 00 00 000 00 00 00 000 00 00 00 000 00 00 00 000 00 00 00 000
430. w of the components 0 000 cece eee eee 84 2 2 2 Platform description s aAA LATAE E eee 85 2 2 3 Overview of network topology 0 000 e eee tte eee 86 2 2 4 Network communication 0 0 0 tee 87 Copyright IBM Corp 2006 All rights reserved iii 2 2 5 Estimating the capacity of the monitoring environment 5 90 2 2 6 Eallover SUPPOMt sac eeu dpa eels ewe sa Fawley eae a ae O 91 2 2 7 Operating system specific considerations 00 0 cece eee eee 92 2 2 8 Database considerations 0 cee tee 94 2 2 9 Installing the monitoring servers 0 0 00 e ee te ee 95 2 2 10 Deploying the remote operating system agents 00 eee 104 2 2 11 An alternative solution 0200000 c eee ee 107 2 2 12 Installing the key components for the distributed environment 108 Chapter 3 Using Physical views 0 0 00 cee eee eee 121 3 1 Physical views from IBM Tivoli Monitoring V6 0 000 ee 122 3 1 1 IBM OMEGAMON for z OS V3 10 0 0 eee 125 3 1 2 IBM OMEGAMON for UNIX System Services V2 20 0 00 00 ee 127 3 1 3 IBM OMEGAMON for DB2 V3 10 0 000 cee 128 3 1 4 IBM OMEGAMON for Mainframe Networks V3 10 0 0000 eee 129 3 1 5 IBM OMEGAMON for CICS V3 10 aonana 130 3 1 6 IBM OMEGAMON for Storage on z OS V3 1 0 000 eee eee 131 3 2 Physical views from IBM Tivoli Composite Application Manager
431. ways of dealing with the missing backup and high availability mechanism Leave it as it is However this is not acceptable in many environments Create a standby solution as described in Chapter 12 3 5 of Getting Started with IBM Tivoli Monitoring 6 1 on Distributed Environments SG24 7143 However this option is fault intolerant with regard to the processes used to implement replication Virtualize the underlying machine and operating system by using z VM or VMware This book focuses on this solution By virtualizing the Tivoli Enterprise Portal Server hardware the same network address can be retained when moving the machine from one location to another In case of emergency the Tivoli Enterprise Portal Server hardware may move to a backup location without changing any credentials for the user workstations gt Tivoli Enterprise Management Server The Tivoli Enterprise Management Server Hub has been identified as the most important component inside the IT management infrastructure of IBM Tivoli Monitoring V6 Several methods exist to avoid the inherent problems Leave it as it is Most of the time however this is not acceptable in production environments Implement the Hot Standby solution provided by the product This is a good solution if only the distributed Tivoli Enterprise Management Server Remote is connected to the Hub Tivoli Enterprise Management Server When a z OS based Tivoli Enterprise Management Serve
432. worth is a Senior Certified IT Architect working in the IBM Design Center for On Demand Business at IBM PSSC Montpellier France He has been with IBM since 2001 He has over 10 years experience in the financial services sector working on international banking client projects Neil specializes in integration technologies and techniques around the IBM System z platform Stefano Delle Chiaie is a certified IT Specialist based in IBM PSSC Montpellier France He has 18 years of IT experience half of which is in the aerospace industry as a client He joined IBM in 1995 and has since performed various benchmark and performance studies for clients in the financial sector He currently works in the IBM PSSC s industry infrastructure solutions group x Infrastructure Solutions Building a Smart Bank Operating Environment Eric Devezeaud is an Advisory IT Specialist working in IBM Information Technology Services in Geneva Switzerland He joined IBM in 1999 and has more than 15 years of experience in the IT sector He holds a Masters degree in Computer Science from the University of Savoie France He specializes mainly in the performance availability and configuration management domains He is a Project Leader for designing and implementing solutions based on Tivoli products such as IBM Tivoli Monitoring IBM Tivoli Enterprise Console IBM Tivoli NetView and IBM Tivoli Configuration Manager Fabrice Jarassat is an IBM Customer Information Cont
433. wps portal tm gt Latest documents pertaining to IBM Tivoli Monitoring http publib boulder ibm com infocenter tivihelp v3rl topic com ibm itm doc it m610usersguide pdf gt LogFormat description and directives http httpd apache org docs 2 0 mod mod_log config html logformat gt OMEGAMON V350 V360 agents application enabling Web site https www14 software ibm com webapp iwm web reg download do source tmd1 amp S_PKG d1 amp cp UTF 8 gt OMEGAMON XE agents download https www14 software ibm com webapp iwm web reg download do source tmd1 amp S_PKG d1 amp cp UTF 8 gt Tivoli products installation documents http publib boulder ibm com infocenter tivihelp v3rl index jsp toc com ibm i tm doc toc xml gt Up to date information about the platform support matrix for IBM Tivoli Monitoring V6 1 http www 306 ibm com software sysmgmt products support Tivoli_Supported_Platf orms htm How to get IBM Redbooks You can search for view or download IBM Redbooks IBM Redpapers Hints and Tips draft publications and Additional materials as well as order hardcopy IBM Redbooks or CD ROMs at this Web site ibm com redbooks Help from IBM IBM Support and downloads ibm com support IBM Global Services ibm com services 286 Infrastructure Solutions Building a Smart Bank Operating Environment Index A ACID 16 advanced link 214 architecture 261 assigned agent 266 267 logical view 266 ATM 52 192
434. xtracts useful data from the access_log file based on the parameters defined in the meta file IBMHTTP mdl The default log format output defined in the HTTP server configuration file httpd conf does not provide all the fields that match the meta file s attributes However the log file output can be customized to suit individual requirements The httpd conf contains directives relating to the log file format gt The LogFormat directive defines which information must be redirected to a log file The use of LogFormat is described in the following Web site http httpd apache org docs 2 0 mod mod_log config html 1ogformat Several LogFormat directives can be defined gt The CustomLog directive defines the log file name and the LogFormat used to define the log format output Table 2 6 shows the correspondence between meta file attributes and LogFormat strings Table 2 6 Meta file attributes and LogFormat strings BytesReceived l requires mod_logio module otherwise put hard coded value 0 114 Infrastructure Solutions Building a Smart Bank Operating Environment Meta file attribute LogFormat string BytesSend O requires mod_logio module otherwise use b Note The module mod_logio is supported since Apache V2 0 43 was introduced The IBM HTTP Server V6 is based on Apache 2 0 47 but does not include this module However a third party module can be used This solution has not been fully tested in our project If the mo
435. y Services GTS for the infrastructure solutions However when you look at the business solutions for banking within Financial Services Sector FSS the borders are blurred as shown in Figure 1 4 Smart Bank Environment Showcase Front Office Banking Risk amp Optimization Compliance Fos Fs04 E08 Core Transform Customer Insight Se Management Infrastructure Higher Solution Emphasis Lower oat E 7 4 1 To drive growth through new capabilities and enhanced value propositions Fidelity core Bank Siebel Business Fair Isaac Analytics Triad Back Office Operations Optimize IT Environments To enhance efficiency across your IT resources including voice data and network Enhance Business Resilience amp Security To protect and strengthen your financial institution Figure 1 4 FSS business solutions affinity with the infrastructure solutions mapped to the Smart Bank Gray areas where business and infrastructure solutions merge exist including the following gt Addressing risk and compliance with analysis of data The Information Warehouse Infrastructure Solution is required gt Addressing core systems transformation service oriented architecture SOA Infrastructure and IT Service Management is used The solutions whether business or infrastructure remain practical initiatives that IBM uses to help its clients address the key bu
436. ys the Navigator tree zone A and a table view B as shown in Figure 4 42 As stated earlier in order to create this table view a query named WLM LINK Service Class Resources zone C is used We have two symbols in this query NODE and 4 WLM Selected Service Class 9 212 128 31 SYSADMIN MEX File Edt View Help gt FOR BREADS OO C SOHWHBRBEAERFTSVTSD Kes View Smart_Ba ve VVLM Selected Service Class Resources information ez Page 1 of3 E Smart_Bank WLM Selected Service Class Resources information ST S gt Teller Managed Service Period Goal Goal Goal Goal Duration Average Performance Actual Authentification System Class Type _ Percentile Importance Value Response Time Index Host 4 Banking BAPLE MVSSYS BAT_DISC 1 Discret O nla 0 0 0 0 00 0a cics BAPLEJ MYSSYS BAT_3V30 1 Velocio 0 Medium 30 0 0 0 00 0 DB2 BAPLI MVSSYS BAT_3V40 1 Velocio 0 Medium 40 0 0 0 00 0 MQSeries BAPLE MVESYR RAT Al 1 Velocio 0 Medium 50 0 0 0 00 0 TCP BAPL a 1 Velocio 0 Medium 25 0 0 0 00 0 WebSphere BAPL Propertie 1 Velocio 0 Medium 30 a 0 0 00 a BAPLEX BAOQ1 MVSSYS BATCHHOT 1 Velocio 0 Highest 50 0 0 0 00 0 4 Teller Channel BAPLEX BA01 MYSSYS BATCHLOW 1 Discret 0l nia 0 0 0 0 00 0 a Pror f ye 0 58 86 z z S 074 67 zOS F Click here to assign a query ces z5 aije C Views 2 WLM Selected Serv

"user manual"

Contents

Download Pdf Manuals

Related Search

Related Contents

&quot;user manual&quot;

Contents

Download Pdf Manuals

Related Search

Related Contents

"user manual"