The document discusses using CICS (Customer Information Control System) transactions as a source of business events for event processing. CICS handles billions of transactions daily and is critical for many businesses. CICS can emit events at predefined points without changing existing applications, to provide insight into business processes and enable new extensions. This allows businesses to gain agility while avoiding risky changes to production code.
13. CICS TS V4.1 is aimed at helping users to – Business Flexibility and Innovation Compete for new opportunity by gaining insight into business processes and responding by modifying key business applications quickly and with confidence Control costs by simplifying IT infrastructure and improving development and operations productivity through easier-to-use interfaces and functions – IT Simplification Comply with corporate, industry and government policies to manage business risk of critical business applications – Governance and Compliance Event Processing
14.
15.
16. CICS and event processing – overview Existing Business Logic Captured Events CICS Event Processing Event Capture Filtering Enrichment Formatting Routing Extensible Secured Monitored etc. Development & Deployment Tools WebSphere Business Monitor WebSphere Business Events Code NOT changed CICS Transaction Server for z/OS Other Event Consumers Events
23. The Role-Based CICS Event Workflow Event Consumer Business Modeler Business Dashboard LoB Manager Application Analyst Systems Programmer CICS TS Existing Application CICS Event Processing Support
24. LoB defines the business events Event Consumer Identify Business Events Studies existing business processing and identifies business events that occur and information to be collected. May define patterns between events and specify delivery destinations or event display using other tooling. LoB Manager Application Analyst Systems Programmer CICS TS Existing Application CICS Event Processing Support
25. Application Analyst identifies events in application Event Consumer Business Modeler Business Dashboard Identify Business Events Create Event Capture Specification Inspects program(s) to determine how to capture the business events and collect the required data. Specifies where and how event is to be emitted. LoB Manager Application Analyst Systems Programmer CICS TS Existing Application CICS Event Processing Support
26. Systems Programmer configures the infrastructure CICS TS Existing Application CICS Event Processing Support Event Consumer Business Modeler Business Dashboard Identify Business Events Create Event Capture Specification Deploy Events Specifies format and destination for the captured events. Defines CICS resources to deploy the events LoB Manager Application Analyst Systems Programmer
27. LoB defines the business actions CICS TS Existing Application CICS Event Processing Support Event Consumer Business Modeler Business Dashboard Identify Business Events Create Event Capture Specification Deploy Events Specify Business Actions Specifies the actions to take on consuming an event LoB Manager Application Analyst Systems Programmer
28. LOB optionally configures a dashboard CICS TS Existing Application CICS Event Processing Support Event Consumer Business Modeler Business Dashboard Identify Business Events Create Event Capture Specification Deploy Events Specify Business Actions Optionally Configure Dashboard Optionally configures a business dashboard to display metrics based on events from CICS and other components of the application system LoB Manager Application Analyst Systems Programmer
42. CICS Event Processing Adapters ‘ WMQ’ EP Adapter Custom EP Adapter Transactions Security Dispatching Monitoring EVENT DISPATCHER Event Capture Existing Business Logic WBM Internal Event CICS Event CBE CBE XML CICS Event Tooling & Schema EP Adapter Interface CICS Tran ‘ TS queue’ EP Adapter CCE WBE ‘ Transaction Start’ EP Adapter EXEC CICS SIGNAL EVENT Sent to one of CFE WBE XML CICS TS Queue CFE Capture Point WBE Any format Anywhere CEI
46. CICS Explorer Resource Perspective Showing a number of Bundle Projects in the Project Explorer, one expanded to show that it contains an event binding, and the bundle manifest
49. Event Binding Editor – Event Specification (2) Another Event Specification with Name, Description and Emitted Business Information also shows where the Capture Specification is added
56. Event Binding Editor – Information Sources (2) Capture Specification, showing the Information Sources panel defining how the event information is obtained from data available on the command (or from standard event context data)
57. Event Binding Editor – Information Sources Import Showing use of imported source code (copybook) to fill in the Information Sources
58. Event Binding Editor – Information Sources Import (2) Showing use of imported source code (copybook) to fill in the Information Sources
59. Event Binding Editor – Information Sources Import (3) Another example of using imported source code to fill in Information Sources
60. Event Binding Editor – EP Adapter EP Adapter specification, showing the configuration details for WMQ Queue EP adapter, with Queue name and other WMQ parameters. The Advanced Dispatcher Options are shown, but nothing other than the defaults have been selected.