Monitoring and managing your file transfer and B2B environments

IBM® Sterling Control Center Monitor can help you answer questions about activities in your managed file transfer and B2B environment.

It helps you answer questions such as:

  • Did my business process run on time?
  • Did my file transfer take place when it should have?
  • Are my servers operating the way they should?

IBM Sterling Control Center Monitor gives you tools to effectively monitor and manage your environment by giving you a common, centralized view of that environment. This insight into the environment helps you offer higher levels of service to your internal and external customers. IBM Sterling Control Center Monitor accomplishes this service level management by:

  • Providing a real-time view of all your servers across products, platforms, and locations. To facilitate monitoring “like” servers, you can group them into server groups, by business unit or location for example, for a single view of system-wide activity.
  • Monitoring activities such as business processes and file transfers.
  • Monitoring the overall health of the environment in terms of server status, adapter status, Global Mailbox data center status, and cluster health.
  • Using a common set of capabilities to create an early warning system for exceptions by:
    • Ensuring critical processing windows are met through service level criteria (SLCs) you set up for your environment.
    • Reducing the impact on downstream processing by verifying that expected processing occurs based on rules you define that are triggered by server events.
    • Providing proactive notification for at-risk business processes in the form of emails, SNMP traps, and alerts.
  • Consolidating information for throughput analysis, capacity planning, post-processing operational or security audits, and workload analysis. This consolidation helps ensure that your file transfer and B2B environments are functioning at a high level.
  • Reducing the risk of error associated with manual system administration, including:
    • The requirement to log on to each individual server to view activity
    • The necessity of separately configuring servers for error and exception notification