1. Integrating The Datacenter OpalisRobot MOM Operator

2. Integrating The Datacenter OPR Basic Components Developer Client and Operations Console Windows & Unix Servers, PCs & Other Devices OpalisRobot Execution Server Connector Objects WEB Console Foundation Objects

3. Integrating The Datacenter OpalisRobot MOM Objects Monitor Alert Update Alert Create Alert Maintenance Mode MOM Connector MOM Server MCF Alerts MOM – OpalisRobot Integration MOM OnePoint DB Maintenance Mode Events

4. Integrating The Datacenter OpalisRobot MS MOM Operator Monitor MOM Event –Setup and filter MOM Events from OpalisRobot  Monitor MOM Alert –OpalisRobot can respond to a MOM Alert  Update MOM Alert –Automatically change the resolution status of an Alert  Send MOM Alert –Provide workflow success/failure notices via MOM  Maintenance mode management –Suppress Alerts in MOM during server maintenance Monitor MOM Event –Setup and filter MOM Events from OpalisRobot  Monitor MOM Alert –OpalisRobot can respond to a MOM Alert  Update MOM Alert –Automatically change the resolution status of an Alert  Send MOM Alert –Provide workflow success/failure notices via MOM  Maintenance mode management –Suppress Alerts in MOM during server maintenance

5. Integrating The Datacenter  Customer problem/pain point –MOM admins and Help Desk personnel must manually synchronize data between systems (phone calls and data entry) –Tickets not always opened in timely manner if at all (not ITIL) –Existing integrations involve time consuming scripts or code –Limited flexibility in filtering which Events should have tickets opened (Event storms cause Trouble Ticket storms)  Opalis Solution –Filter Events based on ID, Name, Severity, then auto-create relevant trouble tickets –Use DB lookups to determine who to assign trouble ticket to, whether to notify (phone, pager) based on time of day, type of Event –Add relevant data to WorkLog of ticket for HelpDesk personnel –Acknowledge that MOM Event is being handled (co-ordinate MOM and help desk staff)  Customer problem/pain point –MOM admins and Help Desk personnel must manually synchronize data between systems (phone calls and data entry) –Tickets not always opened in timely manner if at all (not ITIL) –Existing integrations involve time consuming scripts or code –Limited flexibility in filtering which Events should have tickets opened (Event storms cause Trouble Ticket storms)  Opalis Solution –Filter Events based on ID, Name, Severity, then auto-create relevant trouble tickets –Use DB lookups to determine who to assign trouble ticket to, whether to notify (phone, pager) based on time of day, type of Event –Add relevant data to WorkLog of ticket for HelpDesk personnel –Acknowledge that MOM Event is being handled (co-ordinate MOM and help desk staff) MOM CAP Use Case 1 Service Management Integration

6. Integrating The Datacenter MOM CAP Use Case 1 Help Desk Integration OpalisRobot Value-add 1.MOM admin is auto informed that Event has been acknowledged 2.Ticket instantly created 1.No manual work 2.No time lag 3.Filtered for relevancy 3.Additional info + data can be added to ticket for help desk personnel OpalisRobot Value-add 1.MOM admin is auto informed that Event has been acknowledged 2.Ticket instantly created 1.No manual work 2.No time lag 3.Filtered for relevancy 3.Additional info + data can be added to ticket for help desk personnel

7. Integrating The Datacenter  Customer problem/pain point –When a server fails or maintenance occurs, “Event Storms” occur, overwhelming the system and adminstrator’s console –Maintenance windows are often at inconvenient hours and without Robot they require human attendance –Only MOM Admins have access to ON/OFF switch in many shops, but it’s the IT guys that need to flick the switch  Opalis Solution –Set Scheduled Maintenance Object provides automation for unattended maintenance windows –Set Ad-Hoc Maintenance Object will dynamically set a single server or groups of servers into quiet mode for repairs (groups important for larger customers) –Robot can monitor for ‘Event Storms’ and auto-suppress Events when repeat counts get too high –Robot can watch email from IT admins who are in the field and need to suppress Events on a particular machine with no Admin Console  Customer problem/pain point –When a server fails or maintenance occurs, “Event Storms” occur, overwhelming the system and adminstrator’s console –Maintenance windows are often at inconvenient hours and without Robot they require human attendance –Only MOM Admins have access to ON/OFF switch in many shops, but it’s the IT guys that need to flick the switch  Opalis Solution –Set Scheduled Maintenance Object provides automation for unattended maintenance windows –Set Ad-Hoc Maintenance Object will dynamically set a single server or groups of servers into quiet mode for repairs (groups important for larger customers) –Robot can monitor for ‘Event Storms’ and auto-suppress Events when repeat counts get too high –Robot can watch email from IT admins who are in the field and need to suppress Events on a particular machine with no Admin Console MOM CAP Use Case 2 Maintenance Mode Management

8. Integrating The Datacenter MOM CAP Use Case 2 Maintenance Mode Management

9. Integrating The Datacenter  Customer problem/pain point –Not all shops have 24x7 admins or people at the MOM Consoles – they need to forward relevant info to relevant people –Existing integrations involve time consuming scripts or code –Limited conditional logic for deciding priority levels of tickets, who to assign it to, what type of escalation (email/phone/pager)is needed based on day/time –Traditional forwarding systems are NOT ACTIONABLE  Opalis Solution –Simple interface for creating rich conditional logic for prioritizing which Events to forward to which admin by the appropriate system (email, pager, phone) at various times of day/week –Provides Actionable notification – admin can reply to email/phone to acknowledge Event, perform corrective action, maintenance mode –Robot provides a remote interface for non-admin IT types  Customer problem/pain point –Not all shops have 24x7 admins or people at the MOM Consoles – they need to forward relevant info to relevant people –Existing integrations involve time consuming scripts or code –Limited conditional logic for deciding priority levels of tickets, who to assign it to, what type of escalation (email/phone/pager)is needed based on day/time –Traditional forwarding systems are NOT ACTIONABLE  Opalis Solution –Simple interface for creating rich conditional logic for prioritizing which Events to forward to which admin by the appropriate system (email, pager, phone) at various times of day/week –Provides Actionable notification – admin can reply to email/phone to acknowledge Event, perform corrective action, maintenance mode –Robot provides a remote interface for non-admin IT types MOM CAP Use Case 3 Actionable Notification & Escalation

10. Integrating The Datacenter MOM CAP Use Case 3 Actionable Notification & Escalation

11. Integrating The Datacenter MOM Operator Benefits  Reduce IT Latency –Instantaneously respond to Events –Auto diagnose and notify/escalate –Perform corrective actions –Integrate with Trouble Ticketing for data synchronization, administrator coordination  Automate Maintenance Windows –Use Maintenance Mode toggles to eliminate 3AM administrator attended sessions –Use 100% of time available during Maintenance Window –Dynamically suppress Event messages on ailing servers  Centralize System Monitoring –Route messages from custom Apps or 3rd Party systems to MOM console –Provide OpalisRobot Policy success/failure notices via MOM  Reduce IT Latency –Instantaneously respond to Events –Auto diagnose and notify/escalate –Perform corrective actions –Integrate with Trouble Ticketing for data synchronization, administrator coordination  Automate Maintenance Windows –Use Maintenance Mode toggles to eliminate 3AM administrator attended sessions –Use 100% of time available during Maintenance Window –Dynamically suppress Event messages on ailing servers  Centralize System Monitoring –Route messages from custom Apps or 3rd Party systems to MOM console –Provide OpalisRobot Policy success/failure notices via MOM

12. Integrating The Datacenter MOM Operator Benefits  Achieve ITIL Compliance –ITIL = “Standardize the process, execute that process, then document that you have followed the process” –Robot executes standardized, repeatable Policies that are auto documented (log files, DB, or event logs)  Improve Productivity –Automate repetitive tasks, let humans deal with exceptions –Improve system availability and performance for SLAs  Achieve ITIL Compliance –ITIL = “Standardize the process, execute that process, then document that you have followed the process” –Robot executes standardized, repeatable Policies that are auto documented (log files, DB, or event logs)  Improve Productivity –Automate repetitive tasks, let humans deal with exceptions –Improve system availability and performance for SLAs

13. Integrating The Datacenter OpalisRobot Virtual Server CAP v2.0 Turns of a Virtual Machine Adds a VM to the VM list Lists all VMs on server Checks the status of a VM Powers on a Virtual Machine Removes a VM from the VM list

14. Integrating The Datacenter OpalisRobot SMS CAP v1.1 Create an advertisement using a predefined package, program and collection

15. Integrating The Datacenter Product Use Cases

16. Integrating The Datacenter Common Starting Points Multi-Step, Complex RunBook Procedures –Problem Management Event driven from a monitor (MOM) –Acknowledge, diagnose, resolve –Escalation + Notification –Maintenance Procedures Backups –File Storage –Oracle/SQL Server DBs Reboot procedures –Windows servers with leaky apps Event log archiving and purging –Data & File Automation Application feed procedures Multi-Step, Complex RunBook Procedures –Problem Management Event driven from a monitor (MOM) –Acknowledge, diagnose, resolve –Escalation + Notification –Maintenance Procedures Backups –File Storage –Oracle/SQL Server DBs Reboot procedures –Windows servers with leaky apps Event log archiving and purging –Data & File Automation Application feed procedures

17. Integrating The Datacenter Typical Customer Use Cases

18. Integrating The Datacenter MOM Maintenance Mode Policy

19. Integrating The Datacenter MOM Alert Escalation

20. Integrating The Datacenter MOM & SMS Deployment

21. Integrating The Datacenter Automated Diagnosis

22. Integrating The Datacenter Corrective Action + Resolution

23. Integrating The Datacenter VERITAS BackUp Policy