The default value is @EventServer.

You can specify multiple server names as a comma-delimited list. Server names later in the list can be backups for times when the gateway cannot contact its primary server for an event and the RetryInterval has expired without successfully contacting the primary server. You can specify a host name as you would for a non-TME adapter, and the events are then forwarded to that host using the non-TME Tivoli Event Integration Facility. For more details, see the examples in the ServerPort description.

When the gateway cannot contact the adapter-specified event server, the server names specified in the list are backups. If ServerLocation is not present in the gateway configuration file, the backup functionality uses the default @EventServer value.

To prevent event delivery to backup servers, set the

ServerLocation keyword to NONE.

ServerPort Specifies the port for the event server when sending events using the non-TME Tivoli Event Integration Facility. This keyword is ignored if you are not using the non-TME Tivoli Event Integration Facility.

The default value is zero (0). A value of zero tells the non-TME Tivoli Event Integration Facility to contact the portmapper on the specified host to determine where the event server is listening for incoming event. Note that if you are forwarding events to a Tivoli Availability Intermediate Manager, you cannot specify zero (0) as the port because the Tivoli Availability Intermediate Manager does not register itself with the portmapper.

If you specify a value for ServerPort, the value must be either one integer value or a comma-delimited list containing the same number of values as the list of event servers specified in ServerLocation. You can use one integer value to apply to all of the event servers listed in ServerLocation; otherwise, each event server in ServerLocation requires a corresponding value in ServerPort.

The following example shows how to specify multiple server names to use backup servers in case the primary server fails to receive events. Suppose you have a Tivoli Availability Intermediate Manager running on hosts aim.xyz.com and aimbkup.xyz.com, and ServerLocation and ServerPort are specified as follows:

ServerLocation=aim.xyz.com,aimbkup.xyz.com,@EventServer

ServerPort=5530,5531,0

This sends events to port 5530 on the host aim.xyz.com using the non-TME Tivoli Event Integration Facility. If that fails, events are sent to port 5531 on the host aimbkup.xyz.com. If that also fails, events are sent directly to the event server using the TME Tivoli Event Integration Facility. The port value of zero (0) specified for @EventServer is ignored because port numbers are not needed with the TME Tivoli Event Integration Facility.

100IBM Tivoli Enterprise Console: Adapters Guide

Page 112
Image 112
IBM manual IBM Tivoli Enterprise Console Adapters Guide

Enterprise Console specifications

IBM Enterprise Console is a robust solution designed to centralize and streamline IT operational monitoring and management. As organizations increasingly rely on complex IT infrastructures, including cloud services, on-premise systems, and hybrid environments, the need for an effective monitoring tool has become paramount. IBM Enterprise Console addresses these needs by providing a comprehensive view of IT operations, enabling organizations to respond to incidents with agility and precision.

One of the key features of IBM Enterprise Console is real-time monitoring. The solution offers a single pane of glass through which IT teams can observe the performance of various systems and applications. This capability allows organizations to detect and respond to incidents promptly, minimizing downtime and ensuring that services remain available for end users. The console integrates seamlessly with multiple data sources, allowing for the aggregation of alerts, events, and logs from diverse IT environments.

Another significant aspect of IBM Enterprise Console is its automation capabilities. The platform supports automated workflows and incident management processes, helping to reduce the workload on IT teams. Automation not only enhances efficiency but also ensures consistency in incident response. By leveraging predefined rules and actions, organizations can standardize their operational protocols, leading to faster resolution times and improved service quality.

The IBM Enterprise Console utilizes advanced analytics and artificial intelligence to enhance operational insights. Machine learning algorithms can help identify patterns and anomalies in system performance, allowing organizations to anticipate potential issues before they escalate into critical incidents. This proactive approach to IT monitoring not only improves reliability but also fosters a culture of continuous improvement across the organization.

Security features are also integrated into the IBM Enterprise Console, allowing for the monitoring of security incidents alongside IT operations. This unified approach helps organizations to respond more effectively to security threats, enabling them to correlate operational and security data for a comprehensive view of their infrastructure.

In conclusion, IBM Enterprise Console stands out as a powerful tool for IT operations management. Its real-time monitoring, automation capabilities, advanced analytics, and integrated security features make it an ideal solution for organizations looking to enhance operational efficiency and responsiveness. By leveraging this technology, businesses can ensure that their IT environments remain stable, secure, and aligned with their strategic goals.