iWay Sentinel: Centralized Monitoring and Management Inessa Gerber iWay Product Manager

iWay Sentinel Features Centralized application Monitoring and Management Reflective feeds of activity recorded by sentinel Facilitates distributed environment upgrades Facilitates distributed configuration updates ReST driven, documented APIs enable customization Mobile ready

WF reporting using Sentinel data iWay Sentinel Monitoring Health & connectivity of servers, applications, components Statistics and resource utilization at all levels Sentinel, Server and Application logging with filtering WF reporting using Sentinel data

iWay Sentinel Management Remote update of runtime and environment properties Distribute application updates & environmental upgrades Scheduled and scripted management tasks Group management for servers, applications and file artifacts Direct template update User/Role management

iWay Sentinel Technical Architecture iIT Enterprise Network Files/ SVN iIT Enterprise Network Monitor/Manage iSM Instances, iWay Integrated Applications (iIAs), and channels via Envoy listener running on iSM instance. Note that iIAs run within their own JVMs and are communicated to via iSM Instance. So we have: “SPOG  Sentinel  Envoy  iIA  Channel” communication line. OS level operations such as Start of the server, require a separate link directly on the OS, as we don’t have a running iSM instance to connect to for management. Such, we have “SPOG  Sentinel  Remote OS command” SPOG is a frontend to Sentinel. Sentinel is the managing/monitoring “server” which communicates to iSM instances across the enterprise running on various systems. The plan is for Sentinel to communicate not only to iSMs, but to other instances such as WF, or external resources via the same paradigm. iSM Instance iIA iSM Channel Host Server iSM Instance iIA iSM Channel Host Server

iWay Sentinel Technical Architecture iIT Enterprise Network WebUI Artifacts iWay Sentinel Uploaded via Web UI Stored on Sentinel Files/ SVN iIT Enterprise Network Monitor/Manage iSM Instances, iWay Integrated Applications (iIAs), and channels via Envoy listener running on iSM instance. Note that iIAs run within their own JVMs and are communicated to via iSM Instance. So we have: “SPOG  Sentinel  Envoy  iIA  Channel” communication line. OS level operations such as Start of the server, require a separate link directly on the OS, as we don’t have a running iSM instance to connect to for management. Such, we have “SPOG  Sentinel  Remote OS command” SPOG is a frontend to Sentinel. Sentinel is the managing/monitoring “server” which communicates to iSM instances across the enterprise running on various systems. The plan is for Sentinel to communicate not only to iSMs, but to other instances such as WF, or external resources via the same paradigm. iSM Instance iIA iSM Channel Host Server iSM Instance iIA iSM Channel Host Server

iWay Sentinel Technical Architecture iIT Enterprise Network WebUI Monitor Manage Artifacts iWay Sentinel Uploaded via Web UI Stored on Sentinel Files/ SVN iIT Enterprise Network Monitoring/Management via Envoy Monitor/Manage iSM Instances, iWay Integrated Applications (iIAs), and channels via Envoy listener running on iSM instance. Note that iIAs run within their own JVMs and are communicated to via iSM Instance. So we have: “SPOG  Sentinel  Envoy  iIA  Channel” communication line. OS level operations such as Start of the server, require a separate link directly on the OS, as we don’t have a running iSM instance to connect to for management. Such, we have “SPOG  Sentinel  Remote OS command” SPOG is a frontend to Sentinel. Sentinel is the managing/monitoring “server” which communicates to iSM instances across the enterprise running on various systems. The plan is for Sentinel to communicate not only to iSMs, but to other instances such as WF, or external resources via the same paradigm. iSM Instance iIA iSM Channel Envoy Host Server iSM Instance iIA iSM Channel Envoy Host Server

iWay Sentinel Technical Architecture iIT Enterprise Network WebUI Monitor Manage Artifacts iWay Sentinel Uploaded via Web UI Stored on Sentinel Files/ SVN iIT Enterprise Network OS-level operations Monitoring/Management via Envoy OS-level operations Monitor/Manage iSM Instances, iWay Integrated Applications (iIAs), and channels via Envoy listener running on iSM instance. Note that iIAs run within their own JVMs and are communicated to via iSM Instance. So we have: “SPOG  Sentinel  Envoy  iIA  Channel” communication line. OS level operations such as Start of the server, require a separate link directly on the OS, as we don’t have a running iSM instance to connect to for management. Such, we have “SPOG  Sentinel  Remote OS command” SPOG is a frontend to Sentinel. Sentinel is the managing/monitoring “server” which communicates to iSM instances across the enterprise running on various systems. The plan is for Sentinel to communicate not only to iSMs, but to other instances such as WF, or external resources via the same paradigm. iSM Instance iIA iSM Channel Envoy Host Server iSM Instance iIA iSM Channel Envoy Host Server

Demo

Demo Walkthrough Server Connectivity Monitoring

Demo Walkthrough Server Health Monitoring

Demo Walkthrough iSM Server Details

Demo Walkthrough Application Details

Demo Walkthrough Group Management

Demo Walkthrough Artifact Management

Demo Walkthrough Script Execution

Demo Walkthrough Deploying Applications

Demo Walkthrough Deploying Packages

Demo Walkthrough Scheduled Tasks