3. Why build a mobile mainframe app?
• The problem we started with
– Checking the status of a Mainframe took too long
– Required laptop/desktop, VPN and many clicks…
• The app of our dreams
– On-call team members can quickly check the status of a
Mainframe from anywhere, anytime
– Speedy – top priority
– Smart and customizable – not just another 3270 emulator
Helping us maintain our SLAs by enabling us to find out
what is wrong with the system faster.
6. Biggest challenges
• We had several obstacles to overcome
1. We had to be able to accept and process a self-signed certificate
that z/OSMF sends
2. For our iOS version, we have a proxy that must be authenticated
during development
3. Creating a queue that would ensure jobs were not consistently
submitted. (1st person gets through, everyone else piggy-backs)
4. Figuring out how to parse the job output and what information we
want to use
5. Integration with our Enterprise App Security team while still
maintaining the same functionality we originally envisioned
7. Looking ahead to Version 2
Submitting inline
JCL
Viewing job
JCL
Showing job details
(SDSF view)
The code is there to easily parse whatever information we want, and work with
teams to determine what ‘GO’ means for them.
10. The need for a mobile app
• The inspiration for mobile
– 24x7 visibility to CICS environments – with out
needing laptops!
– Proactive monitoring to avoid errors before they
happen
– Management Dashboard – management can
access critical application status at any time
• Expected Benefits
– Mobility == Flexibility for CICS Systems
Engineering
– Respond to issues or simply verify the current
DB2 and MQ status
– Improve overall reliability, availability and
serviceability of CICS processing
Ensure 24X7 processing for our critical online
applications such as Claims and Real Time Eligibility
WUzUP
CICS?
Aetna
11. The Existing Application
Built on the CICSPlex System Manager Web UI (CPSM WUI),
and requiring laptop access via web browser.
12. CPSM
WUI
Browser
Interface
PC Workstation
CPSM
WUI
Browser
Interface
PC Workstation
CPSM WUI
Server
T8D1CWB91
CPSM
Web
User
Interfa
ce
CPSM
view sets
CPSM
T8DCMS91
CICS TS V5.2
T8D1EAZA
CICS TS
V5.2
T8D1EWZA
CICS TS
zSeries
CPSM
view sets
CPSM
T8DCMS92
CICS TS V5.2
T8D1EAZC
CICS TS V5.2
T8D1EWZC
CICS TS
zSeries
CPSM WUI
Server
T8D1CWB92
AE91
AE92
CPSM
Web
User
Interface
JSON
Webservice
JSON
Webservice
Worklight
Server
WUzUP
Adapter
P8D1WZUP
CPSM API
P8D1WZUP
CPSM API
What we built – The Architecture
• Components
– CICS TS v5.2
– Worklight Server
– WUzUP Interface Utility
• Implementation
– Utility used to generate
JSON schemas from
COBOL
– RESTful Adapter
created in Worklight
Studio and deployed to
the Worklight server
– Mobile application
developed to invoke the
Worklight Adapter
13. Launch the WUzUp app.
Use “+” to configure settings.
Specify Userid & password.
Add CICSplex connections.
Indicate which
connections to check.
What we built – The Mobile App
14. 14
Green = No connection issues.
Red = At least one issue.
Lists all regions that have MQ
and/or DB2 Connectivity issues.
What we built – The Mobile App
15. The Results
• Expectations were exceeded!
– CICS Support Engineers – easily identify mobile process to verify the
connectivity state for the CICS-DB2 and CICS-MQ interfaces across
the various CICS complexes.
– Management Visibility – Management now has the ability to use this
tool to verify/assess the current processing status of the CICS
environments as it relates to DB2 and MQ connectivity.
• Next steps
– Enhance existing app – more functionality for the technicians as well
as enhanced analytics for management
– Develop New mobile offerings – Enable Application Development
partners new capabilities to enhance dev and QA processing.
– Investigate WebSphere Liberty profile and z/OS Connect with CICS
Mobile enabling mainframe applications will enhance the
experience of employees and customers
Notas do Editor
Version 2 which is on the last slide of the powerpoint we submitted will allow us to pull up what is the equivalent to an SDSF screen to show all of the details about the job. We will also be able to submit inline JCL which will give users the option to submit a quick job they think might be able to get more info or to possibly fix a problem.
What was the business need that drove you to want to build a mobile app?
A mobile implementation of the current CPSM WUI utility will enable Aetna CICS Systems Engineers to provide 24X7 support of the various CICS processing environments without being tied to a laptop. With the initial mobile offering CICS Systems Engineers will have the capability of verifying the status of the DB2 and MQ connections across Aetna’s CICS complexes both proactively and after an alert was raised. Additionally, the mobile offering can be utilized as a dashboard for management to view the current status of the DB2 and MQ connectivity for the CICS platforms.
Describe how creating the mobile app could enhance the experience of a customer or employee.
This application will provide mobility and flexibility for the CICS Systems Engineering support staff in respect to on call coverage responsibilities. The CICS technicians' will have the flexibility of responding to connectivity issues or simply verifying the current connection statuses for DB2 and MQ from a mobile device. Mobilization enables a more proactive posture as well as timely reaction to issues while ensuring the overall reliability, availability and serviceability of the CICS processing environments and continued 24X7 processing for our critical online applications such as Claims, Real Time Eligibility etc. ..
Describe your existing infrastructure.
Executing CICS Transaction Server (CICS TS) V5.2 on z/OS Version 2.1. in our OLTP Lab environment. The mobile application was created using Worklight and the WUzUp application interfaces with the CICS CPSM online Application Programming Interface(API).
Describe how you went about the mobile enablement of your mainframe applications
The DHFLS2JS utility was used to generate JSON schemas from our Cobol Commarea
A matching RESTful Adapter in Worklight Studio was created and deployed to the Worklight server
The mobile application was developed to invoke the Worklight Adapter
Include key technical components and/or architecture diagram
Worklight
CICS TS V5.2
WUzUP utility created to interface with the CICS CPSM online API
Highlight any key obstacles you overcame
Worklight Studio is not a standard software deployment therefore a special installation was required for invocation/execution
On subsequent launches and Refreshes, REST JSON calls will be made to all ‘checked’ connections
Green light indicates no CICS regions in that Plex have MQ or DB2 Connectivity issues
Red light indicates at least one CICS region, in that Plex is not connected to MQ and/or DB2
Touch the Red Light ‘Arrow’ for details
What were your expectations and did you meet them?
Expectations were exceeded.
Provide CICS Support Engineers a mobile process to verify the connectivity state for the CICS-DB2 and CICS-MQ interfaces across the various CICS complexes. Additionally, Management now has the ability to use this tool to verify/assess the current processing status of the CICS environments as it relates to DB2 and MQ connectivity.
What worked well?
The DFHLS2JS utility provided for conversion of Cobol to JSON worked extremely well
Are there outstanding issues you still need to work on, or need help with?
Preference was to exploit/implement z/OS Connect and WebSphere Liberty Profile (WLP). However although IBM plans to deliver Liberty z/OS Connect support with CICS TS V5.2 z/OS Connect executing under CICS requires Liberty fix pack 8.5.5.2 + 2 interim fixes (or a later fix pack). CICS TS V5.2 is currently delivered with Liberty 8.5.5.1. and there is no stated ETA for an upgrade.
What are the future plans for your app?
Going forward, this initial mobile application will be enhanced to provide more functionality for the technicians as well as enhanced analytics for Management. Additional mobile offerings are planned targeting our Application Development partners to purge transactions and perform new copies in the development and QA processing environments.