Known Limitations

IBM Control Center Monitor has the following limitations:
  • Rules, Action, Email, and Calendar views do not have the cross-reference ability.
  • Cross Reference from Metadata Action to Roles shows all Roles instead of showing only the associated Roles.
  • Cross Reference from Metadata Schedules to Metadata Rules and Roles show all entries.
  • While creating a report, in Server Group selection page, option to view Server Group details is not available.
  • Cross reference from Reports to Automated Reports shows all Automated Reports.
  • While creating report schedule, ability to view the calendar details is not available.
  • From Standard SLCs listing view, Alerts option shows all alerts instead of Active Alerts.
  • Cross Reference from DVG to Rules shows all Rules instead of the rules where DVG is referenced..
  • Cross reference from Report schedules to Roles and Automated Reports shows all entries instead of referenced objects entries alone.
  • SLC set Global appears twice in SLC set drop-down.
  • Audit Log date range selector has intermittent issues.
  • When a Calendar is saved, Email list is shown instead of Calendar list.
  • When Functional Auth report is duplicated, after Server Group selection, an unexpected error message is displayed.
  • IBM Control Center does not support third-party monitoring tools (such as Dynatrace®) being loaded into the Control Center Java Runtime Environment (JRE).
  • If you are running IBM Control Center with many data visibility groups (DVGs) configured, you might experience a decrease in IBM Control Center performance. To improve the performance, you can either disable some of the DVGs or add more CPUs.
  • In the IBM Control Center Monitor web console, if the monitor views, such as completed file transfers, completed processes, queued processes, active alerts, or handled alerts, have more than 3 million table entries, then you should not use the search filter. If you use the search filter, then the response time can be long, and the web console might time out. When the web console has a time out, you can receive an error that the user interface is out of sync. To avoid the long response time and time-out error, select a specific server type or decrease the range of the date and time sliders.
  • When monitoring a large number of server types, the web console dashboard could encounter errors in the third party d3.js graphic code causing the refresh of the data to stop. To resolve this issue, use the browser reload button to refresh.

    Note: This issue is likely to occur the longer you view the web console dashboard.
  • The IBM Control Center Monitor web console does not support defining rule IDs with GB18030 characters, such as Mongolian, Tibetan, and Arabic characters. Server names or descriptions might be displayed incorrectly if they contain GB18030 characters.
  • Older Microsoft SQL databases limit a single index to a total length of 900 bytes. When the total length of the proc_id, proc_name, orig_node, and server_id fields exceeds 900 bytes, the PROC_ID, PROC_NAME, and ORIG_NODE fields of an incoming event are shortened to 145 characters respectively in the EVENTS table of IBM Control Center Monitor.

    The 900 bytes total length limitation of a single index in Microsoft SQL databases causes the REMOTE_FILE_NAME and LOCAL_FILE_NAME fields of the CC_FILE_TRANSFER table (or the completed file transfers view) to be shortened to 200 characters.

    Shortening the characters can affect IBM Control Center Monitor V6.2 Service level criteria (SLCs), metadata, or tag mapping when you identify an exact matching condition for the proc_id, proc_name, or orig_node field when the field contains more than 145 characters, or for the remote_file_name or local_file_name field when the field contains more than 200 characters.

    The following options are a solution to this limitation:
    • Specify a shorter proc_id, proc_name, orig_node, remote_file_name, or local_file_name field if it can be configured.
    • Use a matching condition such as "contains" or "start with" instead of exact matching.
    This limitation does not apply to IBM DB2 or Oracle databases.
  • When an event from a server triggers a linked rule, but the event processor that the server is assigned to stops before the event processor takes the linked rule resolution action or non-resolution action, neither of the actions is taken. Processing of the linked rule is stopped and not taken over by remaining event processors.
  • IBM Control Center Monitor currently cannot override the time zone for the monitored Sterling Connect:Enterprise® servers. Thus, the generated Sterling Connect:Enterprise transaction data in IBM Control Center Monitor still uses the original time zone that is set by the Sterling Connect:Enterprise server.
  • Some alerts with message CSLC047E (Did not start by NSRs) are left in the Active Alerts list even when the SLC meets one of the following criteria:
    • The workflow SLC with calendar schedule is in progress and the workflow SLC fails over to another controller event processor
    • The workflow SLC with calendar schedule is in progress and the only active event processor in the IBM Control Center Monitor cluster is restarted
  • If you use IBM Control Center Monitor V6.1 or later to monitor Sterling B2B Integrator V5.2.5 Hotfix 10 or later, duplicate entries for Sterling File Gateway activities might be generated in the completed process view. The duplicate entries occur because Sterling B2B Integrator V5.2.5 Hotfix 10 or later sets the FileGatewaySendMessage, FileGatewayReroute, and FileGatewayRoutePGPUnpackageDocument business processes as non-system business processes, which exposes the events to IBM Control Center and causes duplicate entries.The following steps are a resolution to this issue:
    1. Click Servers > Server List on the menu bar.

    2. On the right, in the list of servers displayed, find and Click on the B2Bi server to be changed.
    3. Click on the Edit icon after the server details are displayed.
    4. Click Settings.
    5. Click BP List.
    6. In the business process list, clear the check boxes for FileGatewaySendMessage, FileGatewayReroute, and FileGatewayRoutePGPUnpackageDocument.
    7. Click Summary.
    8. Click Update.
  • IBM Control Center might stop monitoring Sterling B2B Integrator servers or other servers, and show an unknown status in the web console if the following conditions are met:
    1. In a high availability environment, a stopped event processor is restarted.
    2. The controller event processor starts reassigning monitored servers to the started event processor.
    3. Before the server reassignment process is completed, the user stops the controller event processor.
    To avoid this issue, you should wait for all of the server reassignments to complete before you stop the controller event processor.

    If you encounter this issue, you can manually reassign the affected server to another event processor in the cluster after another event processor becomes the controller event processor. After the server is reassigned and starts monitoring, you can assign the server back to the original event processor.

  • If you pause monitoring for a server, the processes of the server is going to remain in the queued processes view. If you resume monitoring the server from the pause point, the completed processes in the queued processes view are moved to the completed processes view when they are complete. However, if you resume monitoring the server from the current time, completed processes might remain in the queued processes view if the process end events are missing. To remove the completed processes from the queued processes view, manually complete the entries one by one.

    Processes that are manually completed in the queued processes view will appear in the Completes Process monitor under User completed.
  • IBM Control Center Monitor cannot monitor Sterling B2B Integrator servers using IPv6. You must specify an IPv4 address or a DNS name for the connection.
  • When you access the web console, you might notice that portions of the UI are not visible in high contrast mode, to avoid this issue, do not use high contrast mode.
  • The configCC utility does not update the system-wide administrator email address in existing actions. After you update the email address in the configCC utility, go to the IBM Control Center Monitor web console to access the existing actions that are configured for email notification and manually change the email address.
  • When you import a configuration into an existing instance of IBM Control Center Monitor in Windows using the configCC utility, the service name is not updated to include the name of the event processor. Instead, the service name includes the date and time of the installation. You must manually import the conf folder and install a new instance to create a new service name with the new event processor. Create a target installation folder for a new IBM Control Center Monitor instance, copy the conf folder that you want to import to the planned install location, and then install a new instance of IBM Control Center.
  • DVG criteria that specify server groups do not match events that are produced by servers in those server groups. As a result, events that should trigger those DVG rules and SLCs do not trigger them. Users who are limited to the data that matches those DVGs do not view anything in their IBM Control Center Monitor instance. You can resolve this issue in the following ways:
    • Change all DVG definitions that contain server groups in their criteria to specify each individual server in those server groups.
    • Define a role that is restricted by a server group, without a DVG.
  • Daylight Saving Time rules for Brazil are not correct for 2009 and beyond. A fix is available to address this problem by allowing the user to add or update time zone definitions. See Timezone settings for help configuring time zone definitions.
  • If the login attempt fails, clearing the browser cache may resolve the issue.
  • If you are using IBM DB2 10.5 or earlier version with IBM Sterling Control Center, you must upgrade DB2 to 11.1 or later version before upgrading to Control Center version 6.2 or later.
  • When a pre-6.2 Control Center Monitor is upgraded and configured to run with both Control Center Monitor and Director, Control Center Director Web Console may not show the server address in the server list view. After making any change to server properties from classic console, Control Center Director Web Console's server list view will show the server address.