1 / 14

LCH.Clearnet – Sysgem AG

Follow the lifecycle scenario where users submit requests via a web form, automated processing tasks are carried out, and results are displayed and sent back.

christner
Download Presentation

LCH.Clearnet – Sysgem AG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  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 email to requestor giving results • User checks “Results” window in web application (and/or receives confirmation by email), 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 # # Command Table # @columns = (); push(@columns, "RequestID=VARCHAR=64"); push(@columns, "Command=VARCHAR=32"); push(@columns, "Source=VARCHAR=32"); push(@columns, "RequestDate=VARCHAR=23"); push(@columns, "RequestStatus=VARCHAR=32");

  7. Paramtable

  8. Paramtable # # Param table. # @columns = (); push(@columns, "RequestID=VARCHAR=64"); push(@columns, "ParamName=VARCHAR=32"); push(@columns, "ParamValue=VARCHAR=255");

  9. Results table

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

  11. Example Use of Tables

  12. Example Use of Tables

  13. Example Use of Tables

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

More Related