1 LCH.Clearnet – Sysgem AG Automated Production Manager Requests Discussion, 24 Aug 2011 WebEx Conference

2 Automated Production Manager Request Form Process Requests Request DB Requestor Multi-platform Servers

3 Possible Life Cycle Scenario User makes request via a web based form on LCH Intranet LCH web application writes the request into Sysgem “Web Access Request” DB ( Record Status = “Submitted”) Automated Sysgem “Process Requests” task running on Sysgem Server (sgmpr1) reads DB; e.g, once every minute, searching for “Submitted” records “Submitted” record status changed to “Processing” and transaction submitted to remote SEM Agent on target server Script on Target server takes action as in current procedures when the “Prod Manager” menu option is invoked manually by Service Desk Results normally displayed to Service Desk operator are transmitted back to “Post- Processing” script on sgmpr1, which: - updates the record with the “results” - changes record status to “Finished” (or “Finished with Errors / Warnings” ) - if required, sends to requestor giving results User checks “Results” window in web application (and/or receives confirmation by ), this would normally be available after about a minute from making the request

4 Web Access Request DB Three Tables: –Command Table –Param Table –Results Table

5 Command Table

6 # # Command Table = (); "RequestID=VARCHAR=64"); "Command=VARCHAR=32"); "Source=VARCHAR=32"); "RequestDate=VARCHAR=23"); "RequestStatus=VARCHAR=32");

7 Param table

8 # # Param table. = (); "RequestID=VARCHAR=64"); "ParamName=VARCHAR=32"); "ParamValue=VARCHAR=255");

9 Results table

10 Results table # # Results table. = (); "RequestID=VARCHAR=64"); "ResultSequence=INTEGER"); "ResultAgent=VARCHAR=255"); "ResultContext=VARCHAR=255"); "ResultFieldName=VARCHAR=32"); "ResultValue=VARCHAR=255");

11 Example Use of Tables

12 Example Use of Tables

13 Example Use of Tables

14 SEM Installed Components Management Console (Windows GUI) Authorization Server Managed Agents on Target Systems