General considerations

IBM® Control Center Monitor V6.2 has the following general considerations:

  • TLS 1.2 can be used to secure all connections between IBM Control Center Monitor components, such as between event processors (EPs), between EPs and Web servers, between EPs and IBM Control Center Monitor consoles.

  • The typical time to install and configure IBM Control Center Monitor V6.2 is one hour or less (Sterling B2B Integrator tables migration time is not included).

  • IBM Control Center Monitor can run in a virtual machine environment provided that enough resources (memory, processing power, and storage) are allocated to the virtual machine.

  • If the console loses connectivity to the event processor, it attempts to reconnect to the event processor every 30 seconds until it reconnects, or until you exit the console.

  • If you are not able to access the IBM Control Center Monitor launch page URL after upgrading to IBM Control Center Monitor V6.2, ensure that the URL is included in the browser list of trusted sites.

  • If you do not enable the globalization parameter for the Microsoft® SQL server during an IBM Control Center Monitor installation or upgrade, then you cannot use multi-byte characters. When a multi-byte character is used without enabling this parameter, IBM Control Center Monitor event processors cannot be started, and you must manually remove the character from your database. If you choose to enable the globalization parameter at a later time, then you must reinstall IBM Control Center Monitor.

  • If you want to secure event posting to the event repository, run the configCC utility and enable event authentication for the Event Repository. Events posted are going to then require valid credentials.

  • The installation of a specific root pass phrase can be secured using a user-defined key instead of a system key. For more information, see Securing the IBM Control Center root passphrase with a user key.

  • In a high availability environment, you can install and configure a load balancer to evenly distribute IBM Control Center web console sessions to the web servers, or the events of a dynamically discovered server that are posted to the IBM Control Center event repository.

  • When you compare the performance of an IBM Control Center Monitor V6.0 single engine with the performance of an IBM Control Center Monitor V6.2 single event processor (formerly the engine), the IBM Control Center Monitor V6.2 event processor requires 20% more CPU capacity to process the same volume. You can have delays in event processing on any event processor that is running at more than 80% of the CPU capacity. To prevent delays, you can increase the number of available CPU cores by 20% for those event processors running at more than 80% of the CPU capacity. You can also install more event processors and spread the load.

  • Before you upgrade your IBM Control Center Monitor V6.0 instance that uses IBM DB2 V10.1, V10.5, or V11.1 to IBM Control Center Monitor V6.1 or later, two of the existing tables need to be moved to bigger table spaces for a successful upgrade. The tables need to be moved because schema upgrade scripts add new columns to the CC_USER and CC_SERVER tables. When new columns are added, the table width becomes larger.

Prerequisites for upgrading IBM Control Center Monitor V6.0 with DB2 V10.1, V10.5, or V11.1 to IBM Control Center V6.1 or later

Run the following DB2 Move command for the CC_USER and CC_SERVER tables to move the tables to bigger table space: 
CALL SYSPROC.ADMIN_MOVE_TABLE('<schema>', '<table_name>', '<data_table_space>',
'<index_table_space>', '<lob_table_space>', NULL, NULL, NULL, NULL, NULL, 'MOVE')
Attention
  • <data table space>, <index table space>, or <lob table space> must be a 16K or 32K table space.
  • To run these commands, you need to have the database administrator privilege.

Examples

CALL SYSPROC.ADMIN_MOVE_TABLE('SCCPROD', 'CC_USER', 'TS_REG16_SCCPROD', 
'TS_REG16_SCCPROD', 'TS_REG16_SCCPROD', NULL, NULL, NULL, NULL, NULL, 'MOVE') 

CALL SYSPROC.ADMIN_MOVE_TABLE('SCCPROD', 'CC_SERVER', 'TS_REG16_SCCPROD',
'TS_REG16_SCCPROD', 'TS_REG16_SCCPROD', NULL, NULL, NULL, NULL, NULL, 'MOVE')