MDB Connectivity Scalability Tests r11 October 25 th

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 2 Objectives -The main objective is to determine the Maximum number of MDB connections that can accomplished in a Distributed Deployment. This is particularly important when large number of Distributed State Machines (dsm) are to be deployed -In addition, the test is also geared to determine the limit of maximum number Ingres Sessions based on memory constraints

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 3 Out-of-Box -Ingres has been configured for 500 Maximum connections -For Local MDB, Ingres Client is configured with InBound=500 and OutBound=500 -For Ingres Client only setup, In Bound and Out Bound limits are configured as 64.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 4 MDB Connection Limit MDB Default Medium Size Configuration. The limit will be different for other MDB configuration

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 5 Ingres Server MDB default Medium Size Configuration NSM r11 Install configures MDB with Medium size settings

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 6 Ingres Client Only Configuration

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 7 Ingres Server – SMALL MDB Setting MDB small Size Configuration NSM r11 Install Process configures MDB with Medium size settings. Out-of-box NSM install process will not permit MDB size customization

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 8 MDB Setup Ingres Server Ingres Client Only Local MDB exists but connects to Highly Available remote MDB Cluster Node 1Cluster Node 2 HA Windows Cluster In and Out bound Limit = 64 In and Out bound Limit = 500 Max Connection Limit = 500 I14YCLUSTER HA MDB I14Y229I14Y204

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 9 Server Specification MDB Server Ingres Client

Test 1 -Distributed DSM

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 11 Objective -The main objective is to determine in a distributed deployment, the number of distributed DSMs (agent technology) with key components installed, can connect to a Central MDB. -The test is performed with out-of-box Ingres Configuration.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 12 MDB Setup Cluster Node 1Cluster Node 2 HA Windows Cluster In and Out bound Limit = 64 Max Connection Limit = 500 I14YCLUSTER HA MDB Ingres Client Only I14Y229

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 13 MDB – Active Sessions at Start Client HostNo of Active Sessions Internal22 Ingres Client8 Local server32

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 14 Remote Client - Installed Components

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 15 Remote Client - Installed Components

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 16 Ingres Client Session Breakdown -There are 8 permanent sessions from the Ingres Client. Application Number of Sessions aws_wvgate2 Continues Discovery Manager2 aws_dsm2 ca-notify1 Worldview Agent1 Total Sessions at Start8

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 17 Client Connections -If the continuous discovery manager is not installed, this will reduce the number of connections by 2, bringing the permanent connections to 6. -Allow for 4 additional dynamic connections. This will bring the average number of connections to 10. These dynamic connections may be classic 2dmap gui, worldview command line utilities, etc -MDB internally takes up 22 connections. In additional local MDB application takes up 32. The bulk of these are taken up by SevPropCom and Enterprise Management (JMO) -In a typical setup, after 475 connections, out-of-memory condition may be experienced on the local MDB. So the architecture should be designed around 475 max connections

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 18 Distributed Agent Technology DSMs Maximum number of Active Connections 475 Permanent Connections Local MDB32 Internal22 Number of Connection Available for Remote Clients 421 Number of Permanent Connections aws_wvgate2 aws_dsm2 Worlview Agent1 CA-Notify1 Additional dynamic Connections4 Total likely Connections per DSM Setup10 Max number of DSM per MDB 42

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 19 Conclusion -Without any Ingres configuration customization, approximately 42 Agent Technology DSMs can connect to one MDB. -If more than 42 dsms need to be deployed then federated MDB concept should be reviewed

Test 2

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 21 Objectives -Analyze the impact if the inbound or outbound limit is exhausted -Out-of-box, the Inbound and Outbound limits are set to 64. If this limit is exhausted, it will not be able to connect to the MDB until some connections are released

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 22 Test 2 -Connect to Highly Available remote MDB from Ingres Client setup -Setup a Loop to connect remote CORE (mdb) until it fails to connect -Review Ingres Connections -Out-of-box Inbound an Out bound limit set to 64.It cannot exceed this limit

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 23 MDB Setup Cluster Node 1Cluster Node 2 HA Windows Cluster In and Out bound Limit = 64 Max Connection Limit = 500 I14YCLUSTER HA MDB Ingres Client Only I14Y229

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 24 MDB – Active Sessions at Start Client HostNo of Active Sessions Internal22 Ingres Client8 Local server32

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 25 Generate Additional Connections from Ingres Client Setup Fails to connect after 56 connections as expected.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 26 Aws_dsm fails with rc=28

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 27 Ingres Sessions Review on Local MDB Confirms failure due to In/Out Bound Limit

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 28 Connection breakdown by Applications ApplicationAverage Number of Sessions JMO (WLM)8 SevProp5 StartBPV2 rmi_Server4 setdsmname2 Component Security3 aws_dsm2 aws_wvgate2 wvobjectcell1 Ingres (Internal)22 wv Tools objbrows1 catng2d1 managobj1 ca-notify1 Total54 This is not a comprehensive list. Shows breakdown of Ingres Sessions for key applications running on the HA Server connecting to the local HA MDB

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 29 Conclusion -If the Inbound or Outbound limit is exhausted, the wv connection will fail with return code 28 -aws_dsm may loose a connection but will reconnect when MDB connection is available

Test 3 -Out-of-Memory Test

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 31 Objectives -The main objective is to exhaust the Ingres Connections until out-of-memory condition is experienced. Then ascertain the maximum number of active connections.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 32 Fails to Connect after 415 additional connections

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 33 Out-of-Memory -Attempt to launch SQL from local MDB server fails due to out-of-memory condition

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 34 Ingres Sessions Review on Local MDB -Stop awservices to release 4 sessions. -This shows Ingres Sessions after stopping awservices Confirms failure due to out-of- memory

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 35 Conclusions -After connection of approximately 475 sessions, no more connections will be possible to the MDB due to out of memory condition.

Test 4 -DSM Session Breakdown

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 37 Test 4 -The main objective is to provide breakdown by process of DSM mdb sessions. -The test was performed with not much activity except one DSMExplorer was launched.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 38 Domain Management Component Database Communication

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 39 DSM – MDB Connection Breakdown MDB UserGroupProcessCount ca_itrmca_itrm_groupamobjectmanager.exe3 ca_itrmregadminamobjectmanager.exe1 ca_itrmca_itrm_groupcmEngine.exe3 ca_itrmca_itrm_groupegc30n.exe3 ca_itrmca_itrm_groupsd_taskm.exe3 ca_itrmca_itrm_groupcmobjectmanager.exe1 ca_itrmca_itrm_groupdmdeploy.exe1 ca_itrmca_itrm_groupsd_apisrv.exe1 ca_itrmca_itrm_groupsd_dialog_m.exe1 ca_itrmca_itrm_grouptngdtdtos.exe1 Total 18

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 40 DSM -In summary, DSM will take approx 18 connection when Asset Domain Manager and Software delivery. -This is connecting a remote MDB