Pre-Con Ed: Webhooks & Continuous Feedback with CA Application Lifecycle Conductor

World®
’16
Webhooks & Continuous Feedback with
CA Application Lifecycle Conductor
Vaughn Marshall
Sr. Principal Product Owner
MFX57E
MAINFRAME

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
For Informational Purposes Only
Terms of this Presentation
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The presentation provided at CA
World 2016 is intended for information purposes only and does not form any type of warranty. Some of the specific slides with customer
references relate to customer's specific use and experience of CA products and solutions so actual results may vary.
Certain information in this presentation may outline CA’s general product direction. This presentation shall not serve to (i) affect the rights
and/or obligations of CA or its licensees under any existing or future license agreement or services agreement relating to any CA software
product; or (ii) amend any product documentation or specifications for any CA software product. This presentation is based on current
information and resource allocations as of November 1, 2016, and is subject to change or withdrawal by CA at any time without notice. The
development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion.
Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in
this presentation, CA may make such release available to new licensees in the form of a regularly scheduled major product release. Such
release may be made available to licensees of the product who are active subscribers to CA maintenance and support, on a when and if-
available basis. The information in this presentation is not deemed to be incorporated into any contract.

Abstract
Today's application development landscape frequently includes
a heterogeneous toolset with solutions varying across vendors
and even differing between teams. In such an environment,
how do you ensure the critical events occurring in one system
can trigger events in another, creating a seamless SDLC out of
the many participating tools? Join us for a technical deep-dive
to see how CA Application Lifecycle Conductor can both
consume and produce webhooks and other events for both
distributed & mainframe products to produce a fully integrated
SDLC.
Vaughn
Marshall
CA Technologies
Sr. Principal Product
Owner

Mainframe DevOps Strategy

Development Deployment & OperationalTesting
Challenges to Delivering Innovations … Continuously
Developers Release
Team
Operations
TESTBUILD DEPLOY
Testers
OPERATE
Deploy to
Production
Cultural
Barriers,
Large Code
Monoliths
Constrained
Environments
Test
Environment
Provisioning
Challenges
Manual
Testing and
Scripting
Incomplete
Test Cases
and Data
Cross-Enterprise
Delivery,
Coordination
and Visibility
Lack of
Integrated
Toolsets
IDLE TIME DELAYS
Code/Integrate/
Build
Functional
& UA Testing
Performance
Testing
defect
RE-WORK
defect defect
DELAYS DELAYS
RE-WORK

Introducing Mainframe DevOps Solution
CA offers Solutions in 4 key areas to foster principles of Agile and DevOps
Continuous MonitoringContinuous TestingAgile Development Continuous Delivery
Develop and maintain
mainframe applications
with agile and modern
methodologies,
toolsets and coding
languages
TEST
Early & Often
DEVELOP
Swiftly
DEPLOY
Reliably
OPERATE
Efficiently
Continuous Feedback Loop
Reduce test cycle times
and costs of mainframe
testing for better time
to market and
mainframe economics
Remove the barriers to
business agility on the
mainframe, with
automation to reduce
time to market and
manage skills gaps
Unify monitoring and
performance
management across
mobile and mainframe
teams for better MTTR
and lower skills costs

Webhooks and Continuous Feedback

What are Webhooks?
§ Term coined in 2007 from the programming term “hook”
§ Web hooks are user-defined callbacks which run using Http
infrastructure
§ They are generally triggered by an application event such as
updating a form field or performing some application-specific
operation

What are Webhooks? (Continued)
§ Administrators define a Http end point that can “receive”
notification of the event
§ When the event occurs, a POST is done to the defined end-
point
§ Webhooks have evolved as an industry standard way of
integrating applications via events

Consuming Webhooks – Challenges
§ The only thing webhooks have in common across different
tools and applications is that an Http POST is performed to a
URL
§ Exactly what is POST’d is unspecified – it could be anything:
– XML data
– JSON data
– Raw text
– Nothing!

Consuming Webhooks – Challenges (Continued)
§ No standards on security
– Typically API keys are used but some webhook producers may require
additional considerations
§ Typically, systems integrators would code & stand up simple
web services to consume the webhook events
– This requires custom coding & knowledge of web service infrastructure
– This can also lead to a proliferation of services

Introducing the CA ALC Event Broker
§ CA ALC 3.0 includes a new component called the CA ALC Event
Broker to simplify webhook consumption
– Provides a generic end point for handling any number events to prevent
service proliferation
– Multiple methods of authentication
– Provides dynamic, rules-based formatting and processing using workflow
widgets to avoid writing code

Introducing the CA ALC Event Broker (Continued)
§ CA ALC 3.0 includes a new component called the CA ALC Event
Broker to simplify webhook consumption
– Leverage CA ALC connectors and connector workflow widgets to quickly build
out integrations
– Extensible with custom handlers where special processing or extremely high
throughput is required
– Includes a NoSQL database for event capture & logging

Producing Webhooks from the Mainframe
§ Webhook producer support is present in common ALM tools
§ Webhook support is now coming to your favorite Mainframe
tools via the Mainframe Webhook Server

Introducing the Mainframe Webhook Server
§ The Mainframe Webhook Server monitors locations for file-
based “events” and posts them to a webhook end point
§ Events are monitored to ensure delivery and can be reposted
in the event of failure
§ Simple administrative interface provided to configure the
webhook event and review & manage event data

Webhook Events for CA Endevor SCM & Beyond
§ Will initially allow CA Endevor SCM to produce package events
to allow for automation around operations such as package
CAST or EXECUTE
§ Eventually, the list of supported products will be extended to
other CA Application Development Products

Extending the Event Broker
A Developers View of CA ALC’s Newest Integration Capabilities

Extending the CA ALC Event Broker
§ Extensibility is provided by allowing for the creation of
customer handler Jar files
§ Handlers are configured to be called in a particular order via
the CA ALC Event Broker configuration file
– Simplicity rules – no OSGI plugins, hot swap or other “plugin” capabilities
– Handlers inherit from a base class provided in the distribution
§ All handlers are equal – when an event is received, the
handlers are notified in their configured order

Extending the CA ALC Event Broker (Continued)
§ Each handler may declare the event handled during
processing and if it does so, the event stops propagating
§ Otherwise, it passes to the next handler
§ All operations are handled via Handler Jars. Handlers are
provided OOTB to:
– Authenticate with various methods
– Format events with a target rule flow
– Process events with a target rule flow

§ For the rule based formatting and processing, the
authentication is assumed to have happened so handler
ordering matters!
– A securityContext object is expected to be placed in the bindings by an
authentication handler prior to triggering it
– Unless you wish to override security provided by another handler,
subsequent handlers should not set a securityContext unless one is not
yet set

§ It is up to the individual handlers to inspect the event body
and/or query parameters and determine what to do (if
anything). For example:
– Perform an action such as custom authentication or preformatting
– Propagate the event; or
– End event processing

CA ALC Event Handler Abstract Class
§ Determines if an event should be handled
public boolean doesHandleEvent(String data, Map<String, List<String>> headers, final Map<String, Object>
additionalBindings);
§ Processes the event
public String handleEvent(String data, Map<String, List<String>> headers, final Map<String, Object>
additionalBindings);
§ Determine whether to propagate or stop event processing
public boolean doneProcessing();

Recommended Sessions
SESSION # TITLE DATE/TIME
MFX112S
Roadmap Session: Mainframe Application Development
Portfolio Review
11/16/2016 at 12:45 pm
MFT148S
Roadmap Session: Achieve DevOps on the Mainframe for
Faster Time to Market
11/16/2016 at 4:30 pm
MFX111S
Advanced Techniques for Initiating the DevOps Journey
[HSBC]
11/17/2016 at 12:45 pm

Must See Demos
Continuous Development and
Testing
Mainframe Theater
Continuous Delivery
Mainframe Theater

Questions?

Thank you.
Stay connected at communities.ca.com

@CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.27 @CAWORLD #CAWORLD
Mainframe and Workload Automation
For more information please visit ca.com/alc
Vaughn Marshall
Sr. Principal Product Owner
vaughn.marshall@ca.com

Pre-Con Ed: Webhooks & Continuous Feedback with CA Application Lifecycle Conductor

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Pre-Con Ed: Webhooks & Continuous Feedback with CA Application Lifecycle Conductor

Similar to Pre-Con Ed: Webhooks & Continuous Feedback with CA Application Lifecycle Conductor (19)

More from CA Technologies

More from CA Technologies (20)

Recently uploaded

Recently uploaded (20)

Pre-Con Ed: Webhooks & Continuous Feedback with CA Application Lifecycle Conductor