ibm impact session 1654-how to move an existing cics application to a smartphone

© 2014 IBM Corporation

ACI-1654 How to Move an Existing CICS Application to a Smartphone

© 2013 IBM Corporation

Reginaldo W. Barosa Executive IT Specialist - Rational Software on System [email protected]

Michael C. Lavacca Client Technical Professional - Rational Software on System [email protected]

mailto:[email protected]

mailto:[email protected]

2

Please Note

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

3

AGENDA

1. Demo Scenario

2. Part 1 – Create, deploying, test and debug Web Service

3. Part 2 – Create Worklight adapter and application to consume the Service

4

CICS Application Overview

CICS Catalog Manager Application

• COBOL based CICS application (EGUI)

• VSAM File

• Separate Presentation Logic and Business Logic

• Callable Interface - Container

4

55

z/OS

3270 Client

VSAM File (EXMPCAT)

CICS

EGUI Main

Inquiry itemBrowse

Existing CICS 3270 Application

Place Order

6

z/OS

VSAM File (EXMPCAT)

CICS

EGUI Main

Inquiry itemBrowse

Place Order

6

RDZ and Debug Tool Web Service enables and test existing app

CICS Web

Service

77

Mobile Client

Worklight Server

Shopping Cart

Enhanced Search and Shopping Cart Features are added via Worklight.

Features do not currently exist in the CICS application.

Enhanced Search

Worklight enhances the CICS Web Service Enabled App

z/OS

VSAM File (EXMPCAT)

CICS

EGUI Main

Inquiry itemBrowse

Place Order

CICS Web

Service

Adapters

9

Rational Team Concert (RTC)

Rational Developer for System z (RDz)

Rational Development and Test Environment for System z (RD&T)

CICS Explorer

z/OS Debug Tool

Worklight

Products and technologies to be used

10

Developer 2

RDz client

COBOL, PL/I, C++, Java, EGL, Batch, Assembler, Debug Tool

x86 PC running Linux

IMS

z/OS

WAS

DB2

MQ

CICS

Wireless Router

RD&T Server

Developer 1

CLM(running on Linux)

CLM = Collaborative Lifecycle Management

Topology used in this Demo

RDz client

11

Objective: Mobile-ize your mainframe application

1. Using Rational Team Concert (RTC) integrated with Rational Developer for System z (RDz) to verify the requirement (work item) and load the code into the RDz Workspace.

2. Using RDz to CREATE, DEPLOY and INSTALL (pipeline scan) web services to CICS using Rational developer and Test (RD&T) as the server.

3. Using RDz to TEST and DEBUG web service generate. Using CICS Explorer and IBM z/OS Debug to debug the COBOL program. Pass the work item for smarthphone creation to other developer.

4. Creating the Worklight client and show the application running on the iPhone .

12






5. Migrating from VSAM to DB2 using CICS VT. Running same application but using DB2 now instead of VSAM.

13

Collaborative software development using IBM Rational Team Concert

QueryStorage

Collaboration

Discovery

Administration: Users, projects,

process

JAZZ SERVICES

Business Partner Extensions Your Extensions

Rational Developer for z

Rational Software Architect

Rational Systems Developer

Rational Business Developer

Rational Developer for i

Eclipse Clients Remote Clients

Visual Studio

Microsoft .NET Clients Rational Desktop Clients

Rational Team Concert

Web 2.0IBM Jazz™ Client Extensions

Eclipse Platform

IBM Rational Extensions

Best PracticesPresentation:

Mashups

An open, extensible architectureSupporting a broad range of desktop clients, IDEs and languages

TSO/ISPF

Rational Team Concert: Workbench for Collaborative Lifecycle Management

14







15







1616

RDz provides a complete set of System z Development and Test capabilities

Rational Developer for System z

A modern IDE for productive development of cross-platform applications written in COBOL, PL/I, ASM, Java, EGL or C/C++ in System z

CICS, IMS, DB2, Batch applications

Access to typical System z sub-system functionality in

z/OS, CICS, IMS, DB2, WAS

Integration with Debug Tool for Development and Test

Integration with Fault Analyzer for Dump Analysis Integration with File Manager

for file and test data handling

Integration with Asset Analyzer for Application

Understanding and Impact Analysis

Integration with Rational Team Concert for Lifecycle and Source Management

Integration with RD&T for flexible access to System z

environment

16Shown on this demo

17






18

Rational IDEs with IBM WorklightDesign, code, build, test, and deploy mobile apps that run on a wide variety of mobile platforms; extend existing back-end services and data to mobile apps

Integrated multi-platform development environmentsIntegrated multi-platform development environments

Construct, debug, and test mobile UIs

Refactor and extend existing logic on enterprise platforms (System z, Power)

as mobile-consumable services

Rational Developer for zEnterprise Rational Developer for Power Systems

Rational Application Developer Rational Software Architect

IBM Worklight is now included in the following IDEs (for development purposes only):IBM Worklight is now included in the following IDEs (for development purposes only):

19

IBM Worklight – Support for Different Mobile Application Styles

Native code

Access to full set of lower-level device capabilities

Native Appl.

Device APIs

100101010101110100101001001010111010010011010101010100100100101111001001100101010100101010101001010101010101010101011111

10

HTML, JavaScript, CSS, with optional native code

Installed and run like a native mobile app; mobile-optimized UI

Access to lower-level device capabilities

Native Shell

Web Native

Device APIs

<!DOCTYP

E html PUBLIC

created

100101010101110100101010

HTML5, JavaScript, CSS,

Accessed from a mobile web browser; mobile-optimized / aware web UI

Limited access to device capabilities

HTML, JavaScript, CSS

Accessed from a mobile web browser

No device-specific capabilities

Mobile Browser

Web Code<!DOCTYPE html

PUBLIC<html>

<! - - created 2003-12-12 - -

<head><title>XYZ</title>

</head><body>

</p>

WebWeb Mobile WebMobile Web Hybrid MobileHybrid Mobile NativeNative

Mobile Browser

Web Code<!DOCTYPE html

PUBLIC<html>

<! - - created 2003-12-12 - -

<head><title>XYZ</title>

</head><body>

</p>

•Simplifies the development of mobile applicationsacross multiple mobile platforms - iOS, Android,

BlackBerry, and Windows® Phone

20

Reporting for Statisticsand Diagnostics

Worklight Application Center

Worklight Application Center

Development Team Provisioning

App Feedback Management

Enterprise App Provisioning and Governance

Device RuntimeDevice Runtime

Cross-Platform Compatibility Layer

Encrypted and Syncable Storage

Runtime Skins

Server Integration Framework

Ap

pli

cati

on

Co

de

Ap

pli

cati

on

Co

de

Worklight ConsoleWorklight Console

Unified Push and SMS Notification

Development and Operational Analytics

App Version Management

En

terp

rise

Bac

ken

d S

yste

ms

&

Clo

ud

Ser

vice

s

Worklight ServerWorklight Server

User Authentication and Mobile Trust

Mashups and ServiceComposition

JSON Translation

Adapter Library for Backend Connectivity

Sta

ts a

nd

Lo

gs

Ag

gre

ga

tio

n

Unified PushNotifications

Client-SideApp Resources

Direct Update

Mobile Web Apps

Geolocation Services

HTML5, Hybrid, and Native Coding

Optimization Framework

Integrated Device SDKs

3rd Party Library Integration

Worklight StudioWorklight Studio

SDKs

Functional Testing

WYSIWG Editor and Simulator

Blackberry

Android

iOS

Windows Phone

Java ME

Windows 8

Mobile Web

Desktop Web Enhanced crash & platform-level exception capture

Location-based event handling

IBM Worklight Components Overview

21

Mobile Device

MobileApplications

Sec

uri

ty L

ayer

1

DB2DB2

Sec

uri

ty L

ayer

2

Cac

hin

g S

ervi

ce (

Op

tio

nal

)

CICS, IMS

Client SideApp Code

The App. interaction & present.

logic on mobile devices

Server side App code

Application logic:• Security (access &

authorization)• Application logic• Integration logic• Push logic

Adapters

connect with back-

end transaction

and data

services.Cac

hin

g S

ervi

ce (

Op

tio

nal

)

Mobile application overview diagram

Mobile Enterprise Application Platform (MEAP) - Worklight - Mobile Enterprise Application Platform (MEAP) - Worklight -

Portal

Web Services•Salesforce.com•Amazon•Any SOAP service

A mobile application needs end-to-end consideration for:- Transactional integrity- Data integrity- Security

A mobile application needs end-to-end consideration for:- Transactional integrity- Data integrity- Security

Mobile application integration is realized with Worklight Adapters Mobile application integration is realized with Worklight Adapters

22

Worklight Server- Adapters Information Systems Databases Applications

QueryUpdate

data

Data/Resultas JSON

Invoke adapter

procedure

SQL WS

Worklight

HTTP

Response

1

2 3

4

Caching Mechanism

Universality• Supports multiple integration technologies and back-end

information systems

Read-only & Transactional Capabilities• Adapters support read-only and transactional access

modes to back-end systems

Security• Flexible authentication APIs for back-end connections• Connected user identity control

Caching• Leveraged to store data retrieved from back-end

Transparency• Uniform exposure of back-end data for all adapter types

Fast Development• Defined using simple XML syntax• Easily configured with JavaScript APIs

Adapters

23

Worklight Server

HTTP

Adapters

HTTP

HTTP

CICS Connectivity Options with Worklight

23

HTTP

HTTP

TN3270

System z

CICS

HATS 3270SNA

HTTP HTTP

MQ MQ

MQ MQMQTT

JSON

REST

SOAP

Web Services

Messaging

25

We Value Your Feedback

Don’t forget to submit your Impact session and speaker feedback! Your feedback is very important to us – we use it to continually improve the conference.

Use the Conference Mobile App or the online Agenda Builder to quickly submit your survey

• Navigate to “Surveys” to see a view of surveys for sessions you’ve attended

25

26

Thank You

27

Legal Disclaimer

• © IBM Corporation 2014. All Rights Reserved.• The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained

in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

• References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

• If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete:Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

• If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete:All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

• Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

• If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete:Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

• If you reference Java™ in the text, please mark the first use and include the following; otherwise delete:Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

• If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete:Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

• If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete:Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

• If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete:UNIX is a registered trademark of The Open Group in the United States and other countries.

• If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete:Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

• If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only.

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

28

BACKUP

http://www.ibm.com/software/rational

29

Supporting the full mobile development lifecycleIBM Solution for Mobile Development and Delivery

Cross-platform mobile web and hybrid app development, test, and build

Manage plans, tasks, code, builds from a common development workbench

Developing for multiple mobile platformsDelivering high quality apps that engage users

and meet business objectives

Linkage and traceability across all phases of development

UI sketching and storyboarding

Test plan optimization and management and integration with mobile “Device-clouds”

Portfolio management

Integrate Worklight Studio with the Rational IDEs to create a comprehensive IDE for all parts of the app (UI, mid tier, back-end)

Extend enterprise assets as mobile-consumable services and connect via Worklight adapters

Integrating with enterprise systemsMeeting accelerated time to market

requirements

Agile planning

Automate and manage continuous, end-to-end build and deployment process with RTC

Deploy to private dev/test app

Reduce cycle times by aligning dev and operations teams

30

Typical Mainframe to Mobile Customer Scenario With Rational Developer for System z

Modernize Front end UI (RDz/Worklight)Componentize/Service EnableBack-end Application (RDz/WODM)

Test/Deploy UI(Native Mobile)

Test/Deploy Service (Native CICS)

Communicate (RESTful API Calls to Native CICS Services)

MobilezEnterprise

Manage (RTC)

31

Sample distributed build flow

32

Generate the web service definitions which enable mobile connectivity to back-end enterprise resources with RDz’s Web Services Explorer.

Trace the connection routes with auto-generated maps/diagrams to understand how everything connects together!

33

Test the generated web services to verify that expected data is returned from the back-end before testing with mobile.

RDz reveals the SOAP message structure needed for mobile UI to communicate with the back-end.

34

Develop and test mobile applications in RDz using the IBM Worklight plug-in. Includes the developer edition of Worklight Server for deployment testing, AND the Mobile Browser Simulator to test app functionality/features on various mobile device platforms

35

Debug mobile applications at source code level as they communicate with back-end resources.

Trace the entire call-stack from mobile to mainframe!

36

Worklight Studio - WYSIWYG Development Environment

37

Lifecycle techniques to help optimize user experience

Improve collaboration and communications between line-of-business stakeholders and development team

• Ensure that development understands and will deliver an app that meets business objectives

• Engage non-technical stakeholders• Improve collaboration to find a cheaper yet satisfying solution

Put more focus on the application design and conceptualization phase

• Iterate during the phase of the lifecycle when it is cheapest to make changes, not when the code is done and changes require drastic re-architecture

Use UI sketching, storyboarding, and business process diagrams

• Improves communications – “a picture is worth a thousand words”• Avoid over-elaboration with sketches; focus on high-level, big-picture issues• Ensure proper application flow and interactions with business process

diagrams

38

Storyboards depict the flow of the application

Collaborate as a team using comments and annotations

Get feedback from non-technical stakeholders

39

Diagrams communicate interactions and flows

Provide visual representation of flow and interactions

Capture the current state and propose a future state with business process diagrams

40

Formal reviews drive agreement and prevent re-work

Test Artifacts

Test Artifacts

RequirementsRequirements

Work Items

Work Items

Reviews & approvals ensures artifacts are reviewed and/or approved by key team members and captures compliance requirements.

41

IBM Rational mobile testing solution

Middle Tier ServerClient Tier Devices Back-end Data & Services

Test automation on deviceMobile device cloud access

Rational Test Workbench / Rational Test Virtualization Solution Simulation of mid-tier or backend systemsTest automation of mid-tier or back-end systems

RQM Test PlanningConfiguration testingTest Construction

Test ExecutionTeam CollaborationReporting & Dashboard

42

Incremental Integration TestingIncremental Integration Testing

Actual Service/App

Virtual Service/App

Test Virtualization is an enabler for continuous Integration Testing

o Isolate front-end from back-end o Control over data and interfaceo Decrease expensive setup costs

Services, applications, systems are introduced into the continuous integration cycle in a prioritized, controlled fashion.

IBM Rational Test Virtualization Solution is a key enabler for Continuous Integration Testing

ibm impact session 1654-how to move an existing cics application to a smartphone

Technology