Event processor worksheets fields

The event processor worksheets calculate your estimated IBM® Sterling Control Center Monitor events per second and events per day. This table describes the input fields on the event processor worksheets.

Hardware sizing of your IBM Sterling Control Center Monitor environment is critical to proper functioning of the software. Clients should size their environment when they are planning for implementation, and at times when your environment changes. To help clients with proper sizing, you can request a Sizing Study from your IBM® Professional Services Project Manager or an IBM Sales Executive. You are going to be provided a Sizing Questionnaire that you complete with details about intended processing volumes in your environment. IBM Sterling Control Center Monitor documentation can help you make decisions and find information for the Questionnaire. If you intend to monitor Sterling Connect:Direct®, you can use the Event Counter Utility that is installed with IBM Sterling Control Center Monitor, to help collect some event statistics. If you have questions or issues filling out the Sizing Questionnaire, you can contact your IBM® Professional Services Project Manager or an IBM Sales Executive. After you complete the Questionnaire, return it back to your IBM® Professional Services Project Manager or an IBM Sales Executive for further analysis in the Sizing Study. IBM is going to send back a sizing recommendations document to help you with your planning.

Description More Information
Number of monitored Sterling Connect:Direct servers The number of Sterling Connect:Direct servers that you will manage with IBM Sterling Control Center Monitor.
Number of Processes per Sterling Connect:Direct server in peak two-hour period The number of processes that a Sterling Connect:Direct server runs during a peak two-hour period. You can use the Event Counter Utility to get this number or run a series of Sterling Connect:Direct SELECT STATISTICS commands for a two-hour period to obtain the number.
Number of events per average Sterling Connect:Direct Process A Sterling Connect:Direct process consisting of a COPY step, an IF step, a RUNTASK step, an ELSE step and another RUNTASK step, generates the following nine IBM Sterling Control Center Monitor events.
  • Server Command (Process Submit) Event
  • Connection Started (Session Begin) Event
  • Process Start Event
  • Step Start (Copy Initiation) Event
  • Step End (Copy Term) Event
  • Step End (If End) Event
  • Step Start (RUNTASK Start) Event
  • Step End (RUNTASK End) Event
  • Process End Event

    Use this as a guideline to determine how many events one of your typical processes generates. If your processes are less complex, use a number less than nine. If your processes are more complex, use a number greater than nine.

Number of monitored Sterling Connect:Enterprise® servers The number of Sterling Connect:Enterprise servers that you will monitor with IBM Sterling Control Center Monitor.
Number of batches retrieved and added per Sterling Connect:Enterprise server in peak two-hour period Use the output from cmureports to count the number of batches added and retrieved for a two-hour peak period.
Number of monitored Sterling Connect:Express servers The number of Sterling Connect:Express servers that you will monitor with IBM Sterling Control Center Monitor.
Number of files retrieved and added per Sterling Connect:Express server in a peak two-hour period The number of files that a Sterling Connect:Express retrieves and adds during a peak two-hour period.
Number of monitored FTP servers The number of FTP servers that you will monitor with IBM Sterling Control Center Monitor.
Number of files sent/received per FTP server in a peak two-hour period) The number of files sent/received per FTP server in a peak two-hour period.
Number of monitored MQ MFT servers The number of MQ MFT servers that you will monitor with IBM Sterling Control Center Monitor.
Number of files sent/received per MQ MFT server in a peak two-hour period The number of files sent/received per MQ MFT server in a peak two-hour period.
Number of monitored Sterling B2B Integrator servers The number of Sterling B2B Integrator servers that you will monitor with IBM Sterling Control Center Monitor.
Number of Processes per Sterling B2B Integrator server in peak two-hour period The number of processes that a Sterling B2B Integrator server runs during a peak two-hour period.
Number of events per average Sterling B2B Integrator Process A Sterling B2B Integrator process consisting of 10 activities (including 3 file transfer activities) will generate 28 events:
  • 2 events (Process start, Process ended)
  • 2 events per activity (Process step started, Process step ended)
  • 4 events per file transfer activity (Connection started, Process step started (for the file transfer), Process step ended (for the file transfer), Connection shutdown started).
    Note: If not monitoring Sterling B2B Integrator business Processes, count each file transfer as a process that generates 4 events.

Number of monitored Sterling File Gateway servers

 The number of Sterling File Gateway servers you will monitor with IBM Sterling Control Center Monitor.
Number of files retrieved and added per Sterling File Gateway server in a peak two-hour period The number of Sterling File Gateway files that will be retrieved/added in a peak two-hour period.
Number of events per average Sterling File Gateway file The number of events for an average Sterling File Gateway file.
Number of enabled SLCs The number of enabled IBM Sterling Control Center Monitor SLCs. Use 500 SLCs as an estimate.
Percentage of Sterling Connect:Direct Processes to which SLCs apply Assume 50% of the processes.
Percentage of Sterling Connect:Enterprise batches to which SLCs apply Assume 50% of the batches.
Percentage of Sterling Connect:Express files to which SLCs apply Assume 50% of the files.
Percentage of FTP server files to which SLCs apply Assume 50% of the files.
Percentage of MQ MFT server files to which SLCs apply Assume 50% of the files.
Percentage ofSterling B2B Integrator processes to which SLCs apply Assume 50% of the processes.
Percentage of Sterling File Gateway files to which SLCs apply Assume 50% of the files.
Number of enabled rules The number of enabled IBM Sterling Control Center Monitor rules. Use 500 rules as an estimate.
Percentage of Events that rules that match (used in Database Sizing Worksheet) The percentage of events to which an enabled rule will apply. If you are unsure, use 10.
Number of attached consoles The numbers of consoles that will connect to the IBM Sterling Control Center Monitor engine.
Number of attached Web consoles The number of Web consoles that will attach to the IBM Sterling Control Center Monitor engine.
Number of enabled DVGs The number of enabled IBM Sterling Control Center Monitor data visibility groups.
Number of monitored servers per DVG The number of monitored servers assigned to each data visibility group.