Sterling Control Center 5.4/5.4.0.1 Release Notes

Product documentation


Abstract

The IBM Sterling Control Center V5.4/5.4.0.1 Release Notes document supplements Sterling Control Center V5.4 documentation.

Content

Release notes contain last-minute changes and other important product information. Read the document before installation.

What's New

To meet your business needs, IBM® Sterling Control Center introduces important new features and enhancements.

Sterling Control Center V5.4 has the following new features:

  • Integration of IBM Cognos® Business Intelligence with Sterling Control Center for reporting
  • Addition of a menu option to launch IBM Cognos Connection directly from the Sterling Control Center console
  • Addition of a rich web-based client for monitoring managed servers
  • Addition of a simple dashboard to the Web client
  • Inclusion of web client REST APIs
  • Support for monitoring IBM Sterling Connect:Express for UNIX and IBM Sterling Connect:Express for Microsoft Windows
  • Support for monitoring IBM QuickFile
  • Addition of an API for configured managed servers
  • Addition of a report that shows how many versions of each configuration object exist for Sterling Connect:Direct® servers

Sterling Control Center V5.4.0.1 has the following new features:
  • Support for monitoring IBM Sterling Connect:Express for z/OS®
  • Capability for natively balancing high-volume IBM Sterling B2B Integrator instances
  • Support for Internet Explorer 9
  • Improvements in performance and scalability

Accessibility

Accessibility features help users who have a physical disability, such as a visual impairment, hearing impairment, or limited mobility, to use software products successfully.

Sterling Control Center provides the following accessibility features in the web console:

  • Keyboard for navigation instead of the mouse
  • Interfaces that are commonly used by screen readers
    Tip: When using a screen reader, the user may need to toggle the virtual PC cursor mode in order to hear the content correctly while navigating within the web UI application.
  • Each field, button, and widget in the user interface has a focus indicator when it is in focus
  • All information is communicated independent of color

Accessibility testing was completed with Firefox 10 and JAWS 13.

The IBM Sterling Control Center Console is not accessible.

The documentation includes the following features to aid accessibility:

  • All documentation is available in HTML formats to give the maximum opportunity for users to apply screen-reader software technology.
  • All images in the information center documentation are provided with alternative text so that users with vision impairments can understand the contents of the images.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility.

System requirements

System requirements have changed significantly since the previous release of Sterling Control Center. If you are upgrading, use the system estimation tools in Determining system and database requirements in Getting Started on the Sterling Control Center Information Center prior to upgrading. For information about hardware and software compatibility for Sterling Control Center, see Detailed system requirements.

Important: Some Sterling Control Center functionality applies only to specific server types. See Functionality by server type.

Important: Sterling Control Center 32-bit versions should only be used for evaluation purposes and should not be used in a production environment.

See Getting Started on the Sterling Control Center Information Center for information about determining configurations for the Sterling Control Center engine.

Required operating system patches

Sterling Control Center uses Cognos Business Intelligence V10.1.1 as the reporting engine. Install required operating system patches before you install Sterling Control Center. Required patches can be found at Cognos Business Intelligence 10.1.1 Software Environments.

Important: In addition to the libraries listed on the Cognos Business Intelligence web site, the following libraries are required for Cognos to operate with Sterling Control Center: libstdc++.so.6, libX11.so.6, libXau.so.6, and libXdmcp.so.6.

Fixes

For information about fixes for Sterling Control Center, see Fix Central.

Configuration management functions supported for each Sterling Connect:Direct platform

Sterling Connect:Direct functionality supported in Sterling Control Center varies by Sterling Connect:Direct platform.

The following table lists major components of Sterling Control Center Configuration Management functionality broken down by Sterling Connect:Direct platform. Support request-generated and other fixes required to use central management components are referenced.

Sterling Connect:Direct Platform and Release
Sterling Control Center Functional Authority
Initialization Parameters
Netmap
Sterling Connect:Direct Secure Plus
User Proxy
Directory Restrictions
Sterling Connect:Direct for UNIX version 3.8 QC 20638 QC 20403 QC 20638 Not Supported Supported N/A
Sterling Connect:Direct for UNIX version 4.0 QC 20638 QC 20403 QC 20638, RTC140646 QC20035, APAR IC85987 Supported N/A
Sterling Connect:Direct for UNIX version 4.1.0 Fix Pack 3 (4.1.0.3) Fix Pack 3 (4.1.0.3) Fix Pack 3 (4.1.0.3) APAR IC85987 Supported Supported
Sterling Connect:Direct for Microsoft Windows version 4.5 Supported Supported Supported Supported Supported Supported
Sterling Connect:Direct for Microsoft Windows version 4.6 Supported Supported Supported Supported Supported Supported
Sterling Connect:Direct for z/OS® version 4.7 Supported Not Supported Supported Not Supported N/A N/A
Sterling Connect:Direct for z/OS version 4.8 Supported Not Supported Supported Not Supported N/A N/A
Sterling Connect:Direct for z/OS version 5.0 Supported Supported Supported Supported N/A N/A
Sterling Connect:Direct for z/OS version 5.1 Supported Supported Supported Supported N/A N/A



Functionality by server type

The following table lists Sterling Control Center functionality broken down by server type:


Sterling Connect:Direct Platform and Release Base Functionality High Watermark Report Process goes to Hold Queue Process Interrupted Events Push Licenses Resolved Missing and Omitted Statistics
Sterling Connect:Direct for HP NonStop version 3.5
Yes
No
No
No
No
No
Sterling Connect:Direct for HP NonStop version 3.6
Yes
No
No
No
No
No
Sterling Connect:Direct for OpenVMS version 3.4
No
No
No
No
No
No
Sterling Connect:Direct for OpenVMS version 3.5
No
No
No
No
No
No
Sterling Connect:Direct for OpenVMS version 3.6
No
No
No
No
No
No
Sterling Connect:Direct for z/OS version 4.7
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for z/OS version 4.8
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for z/OS version 5.0
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for z/OS version 5.1
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for i5/OS™ version 3.6
Yes
Yes
No
No
No
Yes
Sterling Connect:Direct for i5/OS version 3.7
Yes
Yes
No
No
No
Yes
Sterling Connect:Direct for UNIX version 3.8
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for UNIX version 4.0
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for UNIX version 4.1
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for Microsoft Windows version 4.5
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Direct for Microsoft Windows version 4.6
Yes
Yes
Yes
Yes
Yes
Yes
Sterling Connect:Enterprise for UNIX version 2.4
Yes
No
No
No
No
No
Sterling Connect:Enterprise for UNIX version 2.5
Yes
No
No
No
No
No
Sterling Connect:Enterprise for z/OS version 1.4
No
Yes
No
No
No
N/A
Sterling Connect:Enterprise for z/OS version 1.5
No
Yes
No
No
No
N/A
Sterling B2B Integrator version 5.0
Yes
Yes
No
No
No
N/A
Sterling B2B Integrator version 5.1
Yes
Yes
No
No
No
N/A
Sterling B2B Integrator version 5.2
Yes
Yes
No
No
No
N/A


Considerations

Review the following considerations before installing Sterling Control Center.

General considerations

Sterling Control Center has the following general considerations:

  • The time required to install and configure Sterling Control Center V5.4 has increased from the time required by previous releases due to architectural changes. The typical time to install and configure Sterling Control Center V5.4 is one hour or less.
  • Sterling Control Center Mobile V1.1.01 is supported.
  • When the “NO” symbol is displayed on a server icon, Sterling Control Center does not attempt to reconnect to the server until the login information is updated, or monitoring is paused and resumed, or the Sterling Control Center engine is stopped and restarted.
  • Some Sterling Control Center functionality is not available for all versions of managed server types. Ensure full Sterling Control Center functionality by having the latest version of your managed server software.
  • If the console loses connectivity to the engine, it attempts to reconnect to the engine every 30 seconds until it reconnects, or until you exit the console.
  • If the Sterling Control Center engine is running on the Microsoft Windows 2003 Server operating system, to prevent the loss of a connection to the MS-SQL database when you are adding servers, change the HKLM/System/Current Control Set/TcpIp/Parameters/MaxUserPort parameter in the registry to 65534.
  • To receive emails that contain Sterling Connect:Direct licenses to apply to centrally managed servers, configure license retrieval email settings on the License Management tab of System Settings.
  • Configuring Sterling Connect:Direct Secure Plus objects on a Sterling Connect:Direct server requires a secure connection between the server and the Sterling Connect:Direct engine unless a non-secure connection is allowed by the Sterling Connect:Direct server initialization parameters. For instructions on setting up a secure connection, see Configuring a Secure Connection in Getting Started on the Sterling Control Center Information Center. Disable this requirement by setting s+cmd.enforce.secure.connection=n in the initialization parameters.
  • If the reporting engine (Cognos Business Intelligence) process BmtMDProviderMain gets the CCL-SRV-0513 error, then the issue could be caused by the ulimit setting being too high.

    The following ulimit parameters are sufficient to run the Sterling Control Center engine on Red Hat Linux 64-bit platform.
    core file size          (blocks, -c) 0
    data seg size           (kbytes, -d) unlimited
    scheduling priority             (-e) 0
    file size               (blocks, -f) unlimited
    pending signals                 (-i) 30720
    max locked memory       (kbytes, -l) 32
    max memory size         (kbytes, -m) unlimited
    open files                      (-n) 4096
    pipe size            (512 bytes, -p) 8
    POSIX message queues     (bytes, -q) 819200
    real-time priority              (-r) 0
    stack size              (kbytes, -s) 10240
    cpu time               (seconds, -t) unlimited
    max user processes              (-u) 30720
    virtual memory          (kbytes, -v) unlimited
    file locks                      (-x) unlimited
  • On a SUSE Linux 10 system, you may receive the following message during installation:

    user1@qaxxxx10:~> ./CCInstall.bin
    Preparing to install...
    Extracting the JRE from the installer archive...
    Unpacking the JRE...
    Extracting the installation resources from the installer archive...
    Configuring the installer for this system's environment...
    awk: error while loading shared libraries: libdl.so.2: cannot
    open shared object file: No such file or directory
    dirname: error while loading shared libraries: libc.so.6: cannot
    open shared object file: No such file or directory
    /bin/ls: error while loading shared libraries: librt.so.1: cannot
    open shared object file: No such file or directory
    basename: error while loading shared libraries: libc.so.6: cannot
    open shared object file: No such file or directory
    dirname: error while loading shared libraries: libc.so.6: cannot
    open shared object file: No such file or directory
    basename: error while loading shared libraries: libc.so.6: cannot
    open shared object file: No such file or directory
    Launching installer...
    grep: error while loading shared libraries: libc.so.6: cannot open
    shared object file: No such file or directory
    /tmp/install.dir.22159/Linux/resource/jre/bin/java: error while loading
    shared libraries: libpthread.so.0: cannot open shared object file:
    No such file or directory

    If you receive this message, run the following commands:

    cp CCInstall.bin CCInstall.bak
    cat CCInstall.bak | sed "s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/
    " > CCInstall.bin
    rm CCInstall.bak

    After you run these commands, you will be able to run the installer to completion.

  • Do not kill a Sterling Control Center process unless you first try to stop Sterling Control Center with the Sterling Control Center console stop Control Center option or the stopEngine.bat/sh option.
  • Sterling Control Center V5.4 is the last release that supports Sterling Connect:Direct License Management.
  • You can change default system server group names by editing the systemGroups.properties file in Installation Directory\conf\servergroups\ (Windows) or Installation Directory/conf/servergroups/ (UNIX). System server group names must be changed before you define objects that reference them.
  • Sterling Control Center has the following globalization considerations:
    • Freeform text input fields support all language strings; however, they are not translatable.
    • Pre-defined reports are displayed in the authored language.
    • Messages generated by server engines other than Sterling Control Center are not translated.
  • For greater efficiency, Sterling Control Center keeps caches of information rather than going to the database repeatedly. For example, Sterling Control Center keeps a cache of alerts for each data visibility group (DVG) defined to the system in addition to a cache for all completed processes. Before Sterling Control Center V5.4, these caches of information were not initialized until they were needed the first time. Starting with Sterling Control Center V5.4, all of the caches are being initialized during startup. New engine logs are produced as this initialization is done; as a result, it can take a long time to initialize these caches. To turn off the initialization of these caches at startup, you edit the CCEngineService.xml configuration file. For more information, see Performance and Tuning in System Administration on the Sterling Control Center Information Center.
  • To secure the connection between the engine and the web console, use an HTTP/S connection by configuring secure ports and disabling non-secure ports. For more information, see Configuring a Secure Connection in Getting Started on the Sterling Control Center Information Center.
  • If you need secure web client access, the non-secure HTTP port cannot be disabled. However, it can be limited to accept connections from localhost only.
  • The Sterling Control Center web console presents data in a grid format. You can adjust the width of each grid column by clicking the border of the grid column heading and dragging it to the right or left. In addition, you can change the order of columns by clicking the column heading and dragging the column to a new location. There is a minimum width that a column can be adjusted that is based on the length of the column title. You cannot drag the column boundary beyond this minimum width. When grid column widths are adjusted or a grid column is moved to a new location, the column widths and locations are persisted in browser cookies if you are using Firefox browser. In Internet Explorer, column changes are not persisted due to cookie limitations imposed by the browser.

Sterling Connect:Direct for Microsoft Windows considerations

Observe the following considerations when monitoring Sterling Connect:Direct for Microsoft Windows servers:

  • When Sterling Control Center is connected to a Microsoft Windows node and the application is stopped, the following statistics records may be generated:
  • LSDI010I— Call to recv() in sdipc_srvr_recv() failed
  • LIPT027I—Call to recv() failed. OS message=&OSMSG
  • LCOT000I—comm thread termination has started. API connection comm channel failed with LSDI010I

Sterling Connect:Direct for UNIX considerations

Observe the following special considerations when managing Sterling Connect:Direct for UNIX servers:

  • For best results, apply the latest maintenance for the Sterling Connect:Direct for UNIX server.
  • When Sterling Control Center runs on a UNIX platform and polls a Sterling Connect:Direct for UNIX server, multiple cmgr exited messages are written to the Sterling Connect:Direct statistics file.
  • For Sterling Connect:Direct Secure Plus configuration management, Sterling Connect:Direct for UNIX 4.00 or above is required.
  • InstallAnywhere requires temporary space for some of its operations during installation. If there is insufficient space in the system temp, InstallAnywhere attempts to extract the installer into the user’s home directory. Ensure that the system temp has sufficient space for the installation.

    Tip: You can force InstallAnywhere to use a different location for temp space by specifying the IATEMPDIR variable as shown in the following example:

    export IATEMPDIR=$HOME

  • In some UNIX environments, the installer reports that there is not enough disk space to perform the installation when there really is sufficient disk space.

    To bypass this situation:

    1. Type the following commands:

      export IATEMPDIR=$HOME
      export CHECK_DISK_SPACE=OFF  

    2. Run the Sterling Control Center V5.4 installer.

Sterling Connect:Direct for i5/OS considerations

Observe the following considerations when managing Sterling Connect:Direct for i5/OS:

  • Set up the following items before you begin using Sterling Control Center:
    • Create a relational database entry (ADDRDBDIRE or WRKRDBDIRE).
    • Create a user profile with access rights to the Sterling Connect:Direct library. Do not use the user profile called CDADMIN.
    • Ensure that the DDM server is active.
  • If a firewall is configured between a Sterling Connect:Direct for i5/OS server managed by Sterling Control Center, Sterling Control Center uses the following i5/OS services and ports. The ports listed are the default values. These port assignments can be modified using the WRKSRVTBLE command. Sterling Control Center uses ephemeral ports to establish connections to the i5/OS services. For more information on the WRKSRVTBLE command, refer to the i5/OS manuals.
    Service Port
    drda 446
    as-svrmap 449
    as-central 8470
    as-database 8471
    as-file 8473
    as-rmtcmd 8475
    as-signon 8476
  • The Sterling Connect:Direct statistics record may incorrectly report the submitter ID as the SNODEID. This situation results when the Process SNODEID and the submitter ID are different.
  • When invalid authentication credentials are provided for a node, Processes do not write a Process start record, SMPST, in the statistics file.
  • Guided Node Discovery requires Sterling Connect:Direct for i5/OS version 3.5 or later.

Sterling Connect:Direct for HP NonStop considerations

Observe the following special considerations when managing Sterling Connect:Direct for HP NonStop servers:

  • In order for Sterling Control Center to manage a Sterling Connect:Direct for HP NonStop server, create three API Managers pointing to the same port in the network map and one adjacent node record which is referenced by all of the API managers on the Sterling Connect:Direct for HP NonStop server. This configuration allows Sterling Control Center to attempt three simultaneous connections, which may occur if Sterling Control Center is polling a managed Sterling Connect:Direct for HP NonStop server and performing Guided Node Discovery at the same time. Refer to Defining and Maintaining the Network Map in the IBM Sterling Connect:Direct for HP NonStop Administration Guide.
  • A problem in Sterling Connect:Direct for HP NonStop causes events for some Process step end records not to be generated. This situation could result in rules not triggering and SLCs generating erroneous events. To address this issue, apply the fix for SR135624.
  • Guided Node Discovery requires Sterling Connect:Direct for HP NonStop version 3.4.02 or later.

Sterling Connect:Direct for z/OS considerations

Observe the following special considerations when managing Sterling Connect:Direct for z/OS servers:

  • Only PKCS #12 base64 encoded certificates can be imported into Sterling Connect:Direct for z/OS version 5.0. Binary encoded PKCS#12 certificates cannot be imported.
  • When Processes end for reasons such as session outages, and remain in the Sterling Connect:Direct TCQ to attempt to run again, rather than generate a Process End event Sterling Control Center now generates a Process Interrupted event (see Functions supported for each Sterling Connect:Direct platform).If you have rules in a previous Sterling Control Center release that watch for Process End events, these rules will no longer be triggered under such circumstances. Therefore, to achieve the same behavior add rules that watch for events with an event type of Process Interrupted. Likewise, SLCs satisfied with a Process End event may not be satisfied under the same conditions with Sterling Control Center version 5.4.
  • Sterling Connect:Direct for z/OS nodes require the fix for SR1344775 to address the lack of a Process interrupted record being written at appropriate times by Sterling Connect:Direct for z/OS nodes. The lack of Process interrupted records can cause issues with the High Watermark Report, SLC processing, and other areas of Sterling Control Center functionality.

Sterling Connect:Enterprise for UNIX considerations

Observe the following when managing Sterling Connect:Enterprise for UNIX servers:

  • When choosing the API port value during set up a Sterling Connect:Enterprise for UNIX server, see the Sterling Connect:Enterprise for UNIX documentation on how to find the correct API port value.
  • InstallAnywhere requires temporary space for some of its operations during installation. If there is insufficient space in the system temp, it attempts to extract the installer into the user’s home directory. Ensure that the system temp has sufficient space for the installation.

    Tip: You can force Install Anywhere to use a different location for temp space by specifying the IATEMPDIR variable as shown in the following example:
    export IATEMPDIR=$HOME

  • In some UNIX environments, the installer reports that there is not enough disk space to perform the installation when there really is sufficient disk space.

    To bypass this situation:

    1. Type the following commands:

      export IATEMPDIR=$HOME
      export CHECK_DISK_SPACE=OFF

    2. Run the Sterling Control Center V5.4 installer.

Sterling Connect:Express considerations

Observe the following considerations when monitoring Sterling Connect:Express servers:

  • Sterling Connect:Express logs errors differently than other server types supported by Sterling Control Center. If you want to use the predefined Bad Return Code rule or create a rule to watch for failed Sterling Connect:Express transfers, you need to watch for non-zero return codes in the Server Status and Server Error event types in addition to the Process Step Ended event type.
  • For Sterling Connect:Express for UNIX and Sterling Connect:Express for Microsoft Windows, you must specify a monitor rest time that is less than the API timeout for Sterling Connect:Express.

    Important: The API timer for Sterling Connect:Express for UNIX is not currently configurable. It will be configurable in fix pack 1.5.0.7. Until the fix pack is available, specify a monitor rest time of less than 30 seconds.

  • For Sterling Connect:Express for z/OS users, processes that are held or deferred are not shown in the Sterling Control Center Queued Activity Monitor.


Sterling B2B Integrator considerations

Observe the following considerations when managing Sterling B2B Integrator servers:

  • To monitor Sterling B2B Integrator activity, Event Persistence must be enabled on the Sterling B2B Integrator server.
  • In Sterling B2B Integrator, set the Opsserver.commandTimeout parameter located in centralops.properties file so that it is greater than or equal to the timeout value provided in Sterling Control Center. After you adjust this parameter, restart the Sterling B2B Integrator server.

QuickFile considerations

Observe the following considerations when monitoring QuickFile servers:

  • No step start or step end events are generated for failed transfers.
  • If the same QuickFile appliance will be monitored multiple times, by one or more Sterling Control Center engines, the subscriber name value specified when adding the server must be a unique value each time.
  • If the JMS Queue Manager on the QuickFile Appliance has been password protected, which it is by default, the User ID and password values must be specified when adding the server to Sterling Control Center.

    Important: The default JMS Queue Manager ID and password for QuickFile appliances are eventmon and password, respectively. Be sure to check the current values to determine if the default JMS Queue Manager ID and password have been changed.


FTP Server considerations

Sterling Control Center supports both z/OS FTP servers and non-z/OS FTP servers (including WS_FTP). All FTP servers produce logs or SNMP traps to record transfer activities and you need to make sure that Sterling Control Center can properly use the information in these logs or traps to display statistics so that you can monitor these servers.

FTP server reference information

For additional information on working with FTP servers in Sterling Control Center, see the following topics on the Sterling Control Center Information Center.

Topic
See
FTP xferlog and IIs Log Formats Managing servers in System Administration
How to translate the fields shown in Sterling Control Center statistics into FTP terms Keys and fields in System Administration
Configuring the WS_FTP Server to use the FTP Agent Setting up Sterling Control Center to monitor an FTP server in Getting Started


Accommodating changes to IIS logs

Sterling Control Center V5.4 has the following default IIS log format:


    c-ip cs-username date time s-sitename s-computername s-ip time-taken
    cs-bytes sc-bytes sc-status sc-win32-status cs-method cs-uri-stem parameter

If the layout in future releases of IIS logs changes, you can modify the layout for IIS by clicking the Advanced button on the Server Properties Connection page. The only restriction is that the layout must match your actual IIS log layout and the following fields are required: date time, cs-username, s-sitename, time-taken, cs-bytes, sc-bytes, sc-win32-status, cs-method, and cs-uri-stem.

If fields are added to an IIS log that are not listed on the Advance File Format panel, you can use the <ignored-field> place holder. For example, if a future version of IIS adds a new field such as transfer-mode after the parameter, the layout can be changed to be:


    c-ip cs-username date time s-sitename s-computername s-ip time-taken cs-bytes
    sc-bytes sc-status sc-win32-status cs-method cs-uri-stem parameter <ignored-field>

Configuring an xferlog format

Prior to Sterling Control Center V5.1, only FTP servers that wrote transfer activities in the following standard xferlog format were supported:


    %T %Xt %R %Xn %XP %Xy %Xf %Xd %Xm %U ftp %Xa %u %Xc

which translated into the following format:

    current-time transfer-time remote-host bytes-transferred filename transfer-type
    special-action-flag direction access-mode username service-name
    authentication-method authenticated-user-id completion-status

To accommodate different third-party FTP log formats, Sterling Control Center gives you the ability to modify the xferlog format and layout. You can move fields or eliminate certain fields. To modify the layout, click the Advanced button on the Server Properties Connection page.

For Sterling Control Center to read an xferlog, the following requirements must be met:

  • The layout must match the actual xferlog log layout
  • The following fields are required: current-time, transfer-time, file-size, file-name, direction, username, service-name, completion-status.
  • The current-time field must be the first field.

Following is a valid xferlog format because it has required fields and the first field is current-time:

    current-time transfer-time direction file-name username service-name
    file-size access-mode completion-status

The following is an invalid xferlog format because username is missing:

    current-time transfer-time direction file-name service-name file-size
    access-mode special-action-flag completion-status

If you have an xferlog FTP server running with an FTP Agent, you can continue to run with that FTP Agent as long as you do not need to change the xferlog layout or the log filename to a rotating log. To change the layout or to support rotating logs, for example, a log based on day or hour, install the Sterling Control Center FTP Agent.

Cognos Business Intelligence server and WebSphere Application Server considerations

Observe the following special considerations regarding IBM Cognos® Business Intelligence server and IBM WebSphere Application server:

  • For Sterling Control Center V5.4, if you stop Sterling Control Center using the Microsoft Windows Service stop option, Cognos Business Intelligence server and IBM WebSphere® Application Server are not stopped.
  • A Microsoft Windows Service created by Install Anywhere does not provide a shutdown hook to stop Cognos Business Intelligence server and WebSphere Application Server. To perform an orderly shutdown, use either the Sterling Control Center console Stop Control Center option or the stopEngine.bat/sh option.
  • If you kill a Sterling Control Center process on Microsoft Windows or UNIX, Cognos Business Intelligence server and WebSphere Application Server processes have to be stopped or killed separately. To perform an orderly shutdown, use either the Sterling Control Center console Stop Control Center option or the stopEngine.bat option.
  • Upon initial startup of Sterling Control Center, the Cognos Business Intelligence server may take up to 4 minutes to start. The amount of time it will take on your system will vary depending on the performance of your system and the number of servers being monitored.
  • To meet Cognos Business Intelligence requirements, ensure that the host name is resolvable to the engine server IP address.

Known restrictions

Sterling Control Center has the following restrictions:

  • Daylight Saving Time rules for Brazil are not correct for 2009 and beyond. The fix for SR 1367170 addresses this problem by allowing the user to add or update time zone definitions. See Changing Engine Settings After Installation in Getting Started on the Sterling Control Center Information Center for help in configuring time zone definitions.
  • When a node receives a login failed message, the node is shunned until the node service is recycled. Recycle the node by pausing and resuming the node or by changing information in the node properties.
  • At peak volume, the number of events processed per second may be decreased by up to 20%, caused by an additional database operation during event processing.
  • If you mix private permissible objects when you create objects such as rules, SLCs, and automated reports, that reference permissible objects such as calendars, schedules, and actions, you may prevent other users from updating the created object.

    For example, the administrator creates schedule A that is private to Role A and schedule B that is private to Role B. The administrator then creates an Automated Report that includes both schedule A and schedule B, two private schedules. Only the administrator can edit the Automated Report because Role A does not have permission to see Schedule B and Role B does not have permission to see Schedule A.

  • Server-group restricted users (as determined by the role assigned to their user ID) cannot use the batch creation utility to create a server.
  • When the Auto Refresh option is used, the web console session does not time out.
  • Sterling Control Center cannot monitor Sterling B2B Integrator servers using IPv6. You must specify an IPv4 address or a DNS name for the connection.
  • The context-sensitive Help in the Sterling Control Center Console provides definitions for new fields added with this release. However, some Console fields do not have context-sensitive Help. To access the complete product documentation, click the Console Help button, which goes to the Sterling Control Center Information Center.
  • In Internet Explorer 8, the website for the Sterling Control Center web console must be displayed with Browser Mode set to Internet Explorer 8 and Document Mode set to Internet Explorer 8 Standards. To set these modes,
    1. Press F12 to bring up the Developer Tools windows.
    2. Click Browser Mode to select Internet Explorer 8.
    3. Click Document Mode to select Internet Explorer 8 Standards.

    This issue does not occur with Internet Explorer 9.

Installation notes

All Sterling Control Center maintenance releases and specific fixes require that you perform a complete installation and include previous maintenance release fixes.

Tip: Generic steps may require additional steps.

Important: Operating system patches required for Cognos Business Intelligence V10.1.1 must be installed before you install Sterling Control Center. Cognos Business Intelligence 10.1.1 Software Environments.


Falling back to a previous release of Sterling Control Center

You can fall back to a previous release of Sterling Control Center using the backed up \conf folder.

Important: The backed up \conf folder should be used only for falling back to a previous release. Never use the back up version of this folder to replace \conf after upgrading or applying maintenance.
To fall back to a previous release:

1. Create an installation directory for the fall back version, such as C:\Program Files\ControlCenter53.

2. Close all Sterling Control Center consoles.

3. Stop the engine.

4. Make a back up copy of the \conf subfolder located in the installation directory of your currently installed Sterling Control Center version.

5. Copy the back up \conf folder to the directory you created for the fall back version, for example, C:\Program Files\ControlCenter53\conf.

6. Run the installer for the previous version of Sterling Control Center and select the fall back installation directory as the destination folder, for example, C:\Program Files\ControlCenter53.

7. Start the engine.

8. Launch the console from the Sterling Control Center launch page.


Install maintenance releases and fixes in Microsoft Windows

To install a maintenance release or fix in Microsoft Windows:

1. Close all Sterling Control Center consoles.

2. Stop the engine.

3. Back up \conf subfolder in the Sterling Control Center installation folder.

4. Run the installer and select the existing installation folder as the destination folder. The previous version is uninstalled.

5. For all prompts, preserve the same value defined in the previous version and click Next. Do not select Yes for reinitialization of the database for either Production or Staging.

6. Start the engine.

7. Launch the console from the Sterling Control Center launch page.


Install maintenance releases and fixes in UNIX

To install a maintenance release or fix in UNIX:

1. Close all Sterling Control Center consoles.

2. Stop the engine.

3. Back up /conf subfolder in the Sterling Control Center installation folder.

Important: On AIX, before you start the installer, run the slibclean command as "root" user to unload all object files with load and user counts of 0.

4. Run the installer and select the existing installation folder as the destination folder. The previous version is uninstalled.

5. Run configCC.sh. Do not reinitialize the database for either Production or Staging.

6. Start the engine.

7. Launch the console from the Sterling Control Center launch page.

Important: When you install maintenance Sterling Control Center V5.4 and above on AIX platforms, if the installation fails with the following systems, you must run the slibclean command as "root" user and then repeat the maintenance installation.

Symptom 1: The following message displays at the end of the installation:

IBM Sterling Control Center v5.4 had errors installing to:<<scc_install_location>>. Check <<scc_install_location>>/IBM_Sterling_Control_Center_v5.4_InstallLog.log for more information.

Symptom 2: The installation log contains the following types of messages:

Additional Notes: ERROR - ZeroGlq: <<scc_install_location>>/Cognos/bin64/libCCLCFGAPI.so (Cannot open or remove a file containing a running program.)
Additional Notes: ERROR - ZeroGlq: <<scc_install_location>>/Cognos/bin64/libCCLCore.so (Cannot open or remove a file containing a running program.)
Additional Notes: ERROR - ZeroGlq: <<scc_install_location>>/Cognos/bin64/libCCLCryptoShared.so (Cannot open or remove a file containing a running program.)
Additional Notes: ERROR - ZeroGlq: <<scc_install_location>>/Cognos/bin64/libCCLIDOM.so (Cannot open or remove a file containing a running program.)


Migrate data from MySQL databases

Sterling Control Center V.5.4 no longer supports MySQL as a database type. You must migrate your MySQL database to one of the databases supported by Sterling Control Center: DB2, Oracle, or SQL Server 2008.

Migrating data from a MySQL database to a DB2 database

You can migrate data from a MySQL database to a DB2 database.

  • Make sure you have access to the DB2 database and have administrative privileges on the database instance.
  • You must have an IBM account to download the IBM Data Movement Tool.

To migrate data from MySQL to DB2:

1. Create a user ID on the DB2 database that matches the schema name that will be migrated from MySQL. For example, if schema "CCDEV53" is the candidate for migration on MySQL, create a user ID named "CCDEV53" on DB2.


2. Install Sterling Control Center V5.4 and configure it with a DB2 database. For connection parameters, provide the user ID you configured in step 1.
    Important: Do not start the engine until the migration is complete.

3. Ensure the tables, views, and indexes relevant to Sterling Control Center V5.4 have been created on the DB2 database used in step 2.

4. Download IBM Data Movement Tool.

5. After the tool has been downloaded, extract the contents of the .zip folder to a temporary location on the host where DB2 is installed.

6. Configure the source database.


    a. Select MySQL from the drop-down list.

    b. Provide the connection parameters, along with a MySQL JDBC driver to establish the connection.


7. Configure the destination datasource.

    a. Select DB2 LUW from the drop-down list.

    b. Provide the connection parameters, along with a DB2 JDBC driver to establish the connection.

    c. Connect with the user ID you configured in step 1.


8. Select the candidate schema for migration from the list of MySQL schemas displayed.

9. Click Extract DDL/Data. The tool extracts the data from the MySQL schema and stores it on the file system in the same location where the tool is installed.

10. After the data extraction is complete, click Deploy DDL/Data. The MySQL data is deployed on DB2.

11. Validate the row counts on both the source and destination tables.

12. Start the Sterling Control Center engine.

Migrating data from a MySQL database to an Oracle schema

You can migrate data from a MySQL database to an Oracle schema.

Make sure you have access to the Oracle database and have administrative privileges on the database instance. For more information, see the Oracle website.

To migrate data from MySQL to Oracle:

1. Create a user ID on the Oracle database that matches the schema name that will be migrated from MySQL. For example, if schema "CCDEV53" is the candidate for migration on MySQL, create a user ID named "CCDEV53" on Oracle.

2. Install Sterling Control Center V5.4 and configure it with an Oracle database. For connection parameters, provide the user ID you configured in step 1.

Important: Do not start the engine until the migration is complete.

3. Ensure the tables, views, and indexes relevant to Sterling Control Center V5.4 have been created on the Oracle database used in step 2.

4. Download Oracle Sql Developer version 3.1.07 or above.

5 Launch Sql Developer.

6. Configure the MySQL JDBC driver by clicking Tools > Preferences.


    a. Navigate to the Database section.

    b. Click Third Party JDBC Drivers.

    c. Add the MySQL JDBC driver.


7. To establish a connection to the MySQL database, click + and select the MySQL tab.

8. Right-click the MySQL schema and choose the option to migrate. The migration wizard opens.

9. Follow the instructions in the migration wizard. When prompted to connect to the Oracle database, provide the user ID you configured in step 1.

10. Validate the row counts on both the source and destination tables.

    Important: Data from the views is not migrated.

11. Start the Sterling Control Center engine.

Migrating data from a MySQL database to a SQL Server 2008 database

You can migrate data from a MySQL database to a SQL Server 2008 database.

Make sure you have access to the Microsoft SQL Server 2008 Management Studio database and have administrative privileges on the database instance.

To migrate data from MySQL to SQL Server 2008:

1. Install Sterling Control Center V5.4 and configure it with an SQL Server 2008 database.

    Important: Do not start the engine until the migration is complete.

2. Ensure the tables, views, and indexes relevant to Sterling Control Center V5.4 have been created on the SQL Se3rver 2008 database used in step 1.

3. Create a link to the MySQL database server as follows:


    a. On the host where SQL Server 2008 is installed, create an ODBC connection to the MySQL database server. Use MySQL ODBC Driver 5.1 or above to configure the DSN.

    b. After the DSN has been configured, replace the following parameters in the script:

    • <DSN> - Replace it with the DSN that is configured in the ODBC sources.
    • <mysqldbserverhostname> - Replace it with the host name where the MySQL database server is installed.
    • <mysqldb> - Name of the MySQL database where the data needs to be migrated from.
    • <mysqlpassword> - Password to connect to the MySQL database.
4. Execute the following script by creating a new query within SQL Server 2008 Management Studio:

    EXEC master,dbo.sp_addlinkedserver
    @server=N'<DSN>',
    @srvproduct=N'<DSN>',
    @provider=N'MSDASQL',
    @provstr=N'DRIVE={MySQL 5.1 Driver};SERVER=<mysqldbserverhostname>;_
    DATABASE=<mysqldb>;USER=<mysqluser.;PASSWORD=<mysqlpassword?;OPTION=3'

5. After the MySQL database server is linked, it appears as a linked server under the Server Objects folder.

6. Replace the following elements before excecuting the following scripts:


    <sqlserverdb>  - The SQL Server database where the data will be imported to. (Destination)
    <mysqldb> - The MYSQL database where the data will be imported from. (Source)
    insert into <sqlserverdb>.dbo.audit_log
    select * from openquery(DSN,'select * from <mysqldb>.audit_log')
    insert into <sqlserverdb>.dbo.ccc_info
    select * from openquery(DSN,'select * from <mysqldb>.ccc_info')
    insert into <sqlserverdb>.dbo.cd_stats_log
    select * from openquery(DSN,'select * from <mysqldb>.cd_stats_log')
    insert into <sqlserverdb>.dbo.ce_stats_log
    select * from openquery(DSN,'select * from <mysqldb>.ce_stats_log')
    insert into <sqlserverdb>.dbo.config_jobs
    select * from openquery(DSN,'select * from <mysqldb>.config_jobs')
    insert into <sqlserverdb>.dbo.config_server_ids
    select * from openquery(DSN,'select * from <mysqldb>.config_server_ids')
    insert into <sqlserverdb>.dbo.config_versions
    select * from openquery(DSN,'select * from <mysqldb>.config_versions')
    insert into <sqlserverdb>.dbo.discovery_node
    select * from openquery(DSN,'select * from <mysqldb>.discovery_node')
    insert into <sqlserverdb>.dbo.event_comments
    select * from openquery(DSN,'select * from <mysqldb>.event_comments')
    insert into <sqlserverdb>.dbo.event_type
    select * from openquery(DSN,'select * from <mysqldb>.event_type')
    insert into <sqlserverdb>.dbo.events
    select * from openquery(DSN,'select * from <mysqldb>.events')
    insert into <sqlserverdb>.dbo.events_ext
    select * from openquery(DSN,'select * from <mysqldb>.events_ext')
    insert into <sqlserverdb>.dbo.file_counts
    select * from openquery(DSN,'select * from <mysqldb>.file_counts')
    insert into <sqlserverdb>.dbo.licenses
    select * from openquery(DSN,'select * from <mysqldb>.licenses')

7. After the queries execute successfully, validate the row counts on both the source and destination tables.
    Important: Data from the views is not migrated.

8. Start the Sterling Control Center engine.

Contacting IBM Software Support

If you encounter a problem with this product that cannot be resolved using the information outlined in the documentation:

1. Go to the Sterling Control Center support page.

2. Expand the Contact Support section.

  • Click Exchanging information with IBM Tech Support and follow the information instructions provided.
  • Click Directory of worldwide contacts to find the appropriate contact information for your geography.

Collecting information to send to IBM Software Support

Sterling Control Center provides a utility that collects information you can send to IBM Software Support. The SCCDataCollector utility is located in the Installation Directory/bin directory. It consists of two files: runDataCollector.sh and runDataCollector.bat used to create an archive file (.zip file). The .zip file created by the utility is located in the Installation Directory and named SCCdataXXXXXXXXXXXXX.zip, for example, SCCdata1350322062887.zip. After the file is created, upload it to the Enhanced Customer Data Repository System (ECuRep).


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Sterling Control Center
Documentation

Software version:

5.4, 5.4.0.1

Operating system(s):

HP-UX, Linux, Solaris, Windows

Reference #:

7036580

Modified date:

2013-10-02

Translate my page

Machine Translation

Content navigation