cics seminar 2014

Title

Legal Disclaimer

IBM Corporation 2013. 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 IBMs 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 IBMs 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.

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.

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 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, WebSphere, are trademarks of International Business Machines Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

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.

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.

Worklightis a trademark or registered trademark of Worklight, an IBM Company.

Welcome

Roger BraemIBM WebSphere Business Unit Executive,
Asia/Pacific System z Software | [email protected] | LinkedIn

Jennifer NottSenior IT Specialist, System z A/NZ Techline,
IBM Sales & Distribution | [email protected] | LinkedIn

Mark CockerIBM CICS Development | [email protected] | LinkedIn

Seminar materialsWill be on a web site and link sent via email

Text in red links to more details

About IBM Centre

CICS: Trusted by 1000s of customer in 23 industries, spanning 75 countries90% of the Global Fortune 100 Banking and Financial Services use CICS

The world as we know it doesnt exist without Systems of Record

CICS Stats: Our customers span a broad range of industries across the world, supporting business as the premier enterprise grade mixed language application server

Where transaction processing is an essential component of doing business, such as Banking and Financial Services, clients rely on CICS and the System z platform to act as their system of record.

Mainframe as System of Record

Essential for doing business

SoR have evolved to become efficient, secure, auditable solutions, driving high-volume transaction processing in support of business.

But, Systems of Engagement are changing the way people interact with business services

Mobile is the dominant system of engagement and customers expect an omni-channel experience

150 interactions per day per devicetypical mobile devices switched on 100% of time10 billion+
devices accessing
information

Mobile: driving back-end transactions to system of record

91% of new customer facing apps CIOs report that are accessing the mainframemobile banking customers46 percent banks said mobile application development is central to overall digital strategy

32% more profitable19% higher revenues53% less attritionTower Group stats on mobile banking customershttp://www.computerweekly.com/news/2240217391/Bank-mobile-apps-are-being-overwhelmed 46% banks said mobile app dev central to strategyhttp://www.zdnet.com/forgotten-but-not-gone-why-mainframes-remain-the-power-behind-techs-throne-7000023988/ - 90% of new apps accessing mainframe

Mobile transactions can quickly outpace traditional transactionsMainframe is the the smart phones ultimate accessory that enables business impact through optimized engagement

As Robert LeBlanc said, Mobile is the killer app for SOA, and CICS operates at the heart of SOA environments, with its broad range of connectivity options, processing business transactions.

The combination of Systems of Engagement (mobile) and Systems of Record is driving up the volume of transactions which provides business with new opportunities for insight

Please answer each statement as it best describes the growth of different types of data in your firm

Source: 2012 IBM Global Big Data Online Survey

Gartner Survey Analysis: Big Data Adoption in 2013 Shows Substance Behind the Hype
Published: 12 September 2013Types of data analyzedHow strongly do you agree with the following statements about why your firm runs analytics on the mainframe?What types of data/records are you planning to analyze using big data technologies?

Opportunity: Next generation applications drawing on mainframe-based transactional data

Transactional data is a rich seam for big data insights

The convergence of mobile with enterprise data and transaction processing places greater demands than ever on the underlying infrastructure, demanding the highest levels of performance, availability and security.

For example

Mobile banking is a fast growing channel for Halkbank. As for all other channels, we run the transactions themselves on our CICS and DB2 for z/OS systems, which helps to ensure the highest levels of performance, availability and security

Core enterprise applications process transactions lots of transactions and so cant be scaled by adding load balancers and spawning new copies of services. They scale by adding capacity to the transaction processing engine

25 years of continuous operationOn CICS, DB2, and System zAyhan Yalkut, System z Manager, Halkbank.The Turkish state pays most of the government salaries through the bank, causing a once-monthly peak in daily transactions, increasing from 25m to 50m ScalableIn more than 25 years of continuous operations, we have never had any unplanned downtimeReliable

Mobile

Reference Link: http://public.dhe.ibm.com/common/ssi/ecm/en/zsc03244usen/ZSC03244USEN.PDF

Halkbank are responding to the needs of their customer by deploying new mobile applications, relying on the mainframes qualities of service.

Built on CICS and DB2, their systems not only deal with the mobile channel, but have to contend with traditional workloads too. For example, once per month they process the state governments salaries, doubling the number of transactions the bank processes in a single day.

Throughout the last 25 years the bank has depended upon CICS, and System z not once experiencing unplanned downtime.

For customers like Halkbank who are exploiting the mobile channel and integrating it with existing mainframe applications, IBM has announced new mobile pricing

Cloud technology is driving change cloud integration becomes key

Cloud offers clients a new approach to building and deploying new solutions and services (Eg. SoE)

Cloud is an enabler that brings service agility and operational efficiency, but clients must assess whether they are best served by a public, private, or hybrid cloud.

For some clients, hybrid cloud offers the best of both worlds, allowing them to retain their existing Systems of Record often providing secure and auditiable solutions for sensitive data exploiting public cloud services for Systems of Engagement.

Clients have a choice of how to build, deploy, and integrate their cloud offerings

1,2 North Bridge Venture Partners and GigaOM Research, The Future of Cloud Computing: 3rd Annual Survey 2013, October 2013.

Cloud platforms & integration

BlueMix

Instant services, runtimes, and infrastructure for cloud based applications.

Integration with existing Systems of Engagement

TXSeries

Clients using TXSeries who need to balance costs against growth.

TXSeries on Softlayer for cloud-style scalability

CICS TS V5

Simplified system management and rapid application deployment.

On premise pattern based cloud deployment.Codename: Bluemix is IBMs new public cloud offering, providing a wide range of development tools, integration tools, and services to enable clients to build cloud based application and integrate them with their existing Systems of Record for example, mobile applications.

CICS and TX Series cloud offerings for private clouds

For most CICS customers the fastest route to value is to adopt cloud-style practices in a private or hybrid cloud solutions (security of data, co-location)

CICS V5 delivers cloud capabilities to provide better platform management and improved application deployment thanks to our new first-class application resources and first-class platforms were able to provide an abstraction between the application and the collection of CICS regions on which it runs, helping our clients to manage the risks associated with deploying new applications.

For customers on TXSeries, who are balancing costs against growth (perhaps from mobile) there is a new TXSeries offering on Softlayer virtualisation of TXSeries

CICS TS V5

V5 introduce cloud capabilities to CICS, providing first-class application resources, to allow clients to package and manage the application lifecycle and..

V5 introduce first-class platforms, to enable clients to rapidly deploy their applications onto target platforms and have CICS manage to resource deployment

CICS TS V5.2 extends our cloud capabilities further

Improved support for application multi-versioning, which improves service agility and ability to deploy and manage new application versions

CICS V5.2 Inclusion in IWD can add a deployed CICS application as a target

Having applications running in the cloud is great, but to really transform your business you need to be able to integrate them with your Systems of Record, which is why we have announce z/OS Connect

...to Maximize the value of these new technologies

Systems of Interactionour clients must integrate their existing Systems of Record with their new Systems of Engagement creating a new class of system: Systems of InteractionCodename: Bluemix is IBMs new public cloud offering, providing a wide range of development tools, integration tools, and services to enable clients to build cloud based application and integrate them with their existing Systems of Record for example, mobile applications.

CICS and TX Series cloud offerings for private clouds

For most CICS customers the fastest route to value is to adopt cloud-style practices in a private or hybrid cloud solutions (security of data, co-location)

CICS V5 delivers cloud capabilities to provide better platform management and improved application deployment thanks to our new first-class application resources and first-class platforms were able to provide an abstraction between the application and the collection of CICS regions on which it runs, helping our clients to manage the risks associated with deploying new applications.

For customers on TXSeries, who are balancing costs against growth (perhaps from mobile) there is a new TXSeries offering on Softlayer virtualisation of TXSeries

CICS TS V5

V5 introduce cloud capabilities to CICS, providing first-class application resources, to allow clients to package and manage the application lifecycle and..

V5 introduce first-class platforms, to enable clients to rapidly deploy their applications onto target platforms and have CICS manage to resource deployment

CICS TS V5.2 extends our cloud capabilities further

Improved support for application multi-versioning, which improves service agility and ability to deploy and manage new application versions

CICS V5.2 Inclusion in IWD can add a deployed CICS application as a target

Having applications running in the cloud is great, but to really transform your business you need to be able to integrate them with your Systems of Record, which is why we have announce z/OS Connect

z/OS Connect: Systems of Engagement to Systems of Record

Discover/Reuse services

Enhance customer experience by exposing mainframe services

Audit and chargeback

Integration with mainframe accounting to determine usage & traffic patternsIntegrates with standard z/OS middleware

Simplifyconnection

Standard open API technology for securely connecting mobile and cloud applications to System z

Mobile-Optimized APIsCloud enabled

JSON/RESTJSON/REST

z/OS Connect

z/OS Connect provides a unified approach to integrating applications on the cloud (or anywhere else within your enterprise for that matter) with the applications and data that are your Systems of Record.

z/OS Connect allows you to integrate your mobile applications using RESTful APIs and JSON payloads (the language of mobile) with your existing z/OS middleware exploiting the enterprise applications and data that you have built and invested in.

The reality of business is complex with a large number of integration points

API Management

DataPower

Systems of Engagement Meet Systems of Record

Cloud and API Economy

CICS TG

CICS on Multi-platforms

zLinux Worklight

WebSphere Application Server

z/OS DB2

MQ

CICS TS

z/OS Connect

IMS

Systems z is the only platform that can support the growing demands of mobile, and the growth in data, to securely and reliably process your business transactions and deliver the promise of cloud.

Bringing it all together With CICS at the heart of your enterprise you can continue to exploit your investment in your core applications and services.

Combine SoE with SoR using private and hybrid cloud infrastructure to build secure and scalable systems

IBMs Mobile First strategy enables clients to build mobile channel solutions that integrate SoE and SoR

CICS and CICS TG capabilities allow our clients to deliver a mobile channel to their customers, with control over where the integration tier resides (in Worklight, in CICS TG, or direct to CICS)

NEW: CICS Transaction Gateway for z/OS V9.1 open beta demonstrates the capability to integrate mobile applications, talking JSON, with existing in-support versions of CICS Transaction Server in addition to the existing integration options it provides

With z/OS Connect you can integrate with the wider IBM cloud platform Bluemix

With API management, integrating with services running on the mainframe (potentially through z/OS connect) you have the potential to create new revenue streams

When you bring everything together you have a platform you can trust to deliver new workloads, new customer services, reliably and securely just like Banca Carige have done

BA Cognos 10 Template

9/4/14

Prensenter name here.ppt

Trusted platform for new mobile workloadOn CICS, DB2, and System zTrust is crucial, so whenever we launch new services, the challenge is always to ensure that the underlying data and transactions are secure and reliable. We needed a robust and trustworthy platform for our new analytics and mobile capabilities

Daniele Cericola, ICT Governance Manager at Banca Carige.

97% of executives surveyed said that information security is highly critical to their companys ability to compete in their market or industry

Banca Cariges new mobile application runs in the cloud, it hooks back into web services running on the zEnterprise. Mobile transactions are processed through CICS and DB2 on the mainframe. Integratedavailability and security are business-critical; the fact that these are tried-and-tested features of the mainframe makes it our natural platform of choice for our new initiativesSecureTrusted

http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=AB&infotype=PM&appname=SWGE_ZS_ZS_USEN&htmlfid=ZSC03256USEN&attachment=ZSC03256USEN.PDF#loaded

Banca Carige use the platform they trust to develop new analytics and mobile capabilities on the worlds most secure business platform.

Leveraging existing investment whilst responding to mobile and cloud is critical for our customers which is why, in CICS V5.2, we are bringing you more capabilities for service agility, operational efficiency, and cloud enablement

New System z mobile pricing

Current WorkloadPrior Peak UtilizationGrowth Due to Mobile

New Peak UtilizationReduced cost of growth on Mobile workloads Scale IT Investments with the growth & business returns of mobile

Leverage existing System z data and transaction processing for mobile

No Infrastructure Changes Required

Applicable to workloads running on zEC12 and zBC12

Up to a 60% reduction in reported CPU utilization for Mobile transactions

Mobile pricing helps customers leverage their investment

New pricing for mobile workloads on z/OS can improve the cost of growth for mobile transaction volumes that can cause a spike in software charges.

This new pricing will provide up to a 60 percent reduction on the processor capacity reported for Mobile transactions, helping normalize the rate of transaction growth used for software charges.

Its not just mobile thats affecting how clients build and charge for services, cloud computing offers customer a new approach for building, deploying, and paying for new (potentially mobile) applications

Weve just launched a Mobile Mainframe App Throwdown its an app-building contest that can help you get a fast start with your next generation mobile apps.Well provide support for you to develop your own mobile proof-of-concept in-house we reckon you could have it up and running in a couple of weeks.And whats more, impress us with your app and you could win a week with our IBM zMobile Experts to help turn your concept into a reality.So whether you want to connect your Android tablet to your CICS stock control system, or your iPhone to your IMS database, you should take part in our competition.

How do we help you?Weve built a bank of getting started content and downloads, whether you run CICS, IMS, WAS or DB2.Well show you how you can get a headstart with Worklight on zLinux.Youll have access to our Throwdown Forum and our IBM zMobile Experts for questions and queries.

What do you need to do?Register at ibm.biz/mmathrowdownWe need to receive your entry by 17 September 2014 we do not want you to send us any code, just some screenshots and a few explanatory slides.

===

NotesContest is open to existing System z customers.They can build their app however they wish, as long as it involves some IBM products, and they cannot submit a solution that is pre-existing or commercially available.We do NOT want their code they retain ownership.Winners will be announced at IBM Enterprise2014 in Las Vegas in October. The prize of a week with IBM experts could be at customers site or at an IBM site.

Agenda

Please note

IBMs statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBMs 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 users 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.

CICS TS V5.2

CICS TS purpose and vision

CICS TS V5.1 and feature packs review

CICS TS V5.2Service agility

Operational efficiency

Cloud

CICS Explorer

Documentation

CICS TS purpose

IBM CICS Transaction Server V5

the premier enterprise grade mixed language application server

Service Agility

Operational Efficiency

Cloud Enablement

Notes

Service agility CICS TS V5.2 significantly enhances the portability of web applications into CICS, by upgrading WebSphere Application Server Liberty Profile to Version 8.5.5 and supporting a broader set of its features. Java database connectivity, transactionality, and security infrastructure are all functionally enhanced. This makes applications written in Java even more capable.Service-oriented architecture (SOA) support is extended by integrating the JSON and REST capabilities, introduced in the CICS TS Feature Pack for Mobile Extensions, into CICS TS V5.2. This makes it easier to interact with mobile devices and mobile-optimized gateways, such as Worklight Server.Operational efficiency For operational efficiency, the number of supported policy thresholds is expanded to cover an increased number of threshold types, safeguarding critical runtime resources. This enables a wider range of service-level agreement thresholds to trigger automatic actions.The integration of CICS applications with distributed security standards has been simplified by incorporating the Security Assertion Markup Language (SAML) support, introduced in the CICS TS Feature Pack for Security Extensions, into CICS TS V5.2. Also introduced is support for Kerberos security tokens and stronger cryptographic ciphers. SAML support is provided for both inbound and outbound use of SAML tokens, and SAML tokens can now be augmented by adding new attributes.Cloud enablement Major advances are made in CICS TS V5.2 in the area of cloud enablement, to enhance application lifecycle management by allowing different versions of a multi-program application to run concurrently, and simplify deployment of application updates or to easily rollback to an earlier version if required.Application versioning assists with the consolidation of applications onto fewer CICS regions.

CICS TS vision

Complex

Easy

Dumb

Smart

As CICS has got smarter, the level of complexity has increased.

CICS TS V5 will continue to deliver more advanced capabilities.

At the same time, CICS will simplify common tasks, and provide automatic features to better manage your environments.

Use with CICS TS

CICS TS versions and feature packs

CICS TS V3.1 & V3.2In service until December 2015

CICS TS V4.1 & V4.2In service until at least 3Q 2017 as per IBM statement of direction

CICS TS V5.1Available since 14 December 2012

Feature PacksCICS TS Feature Pack for Dynamic Scripting V1.1V4.1 V4.2

CICS TS Feature Pack for Dynamic Scripting V2 V5.1 V5.2

CICS TS Feature Pack for Mobile Extensions V4.2 V5.1integrated

CICS TS Feature Pack for Security Token Extensions V4.2 V5.1 integrated

CICS TS Feature Pack for Modern Batch V4.2 V5.1 V5.2

Feature packs

CICS TS Feature Pack for Mobile Extensionsextend your CICS applications to mobile devices and brings support for JSON data within CICS applications

CICS TS Feature Pack for Modern Batchcombine batch and online CICS workloads to minimise downtime and improve operational efficiency

CICS TS Feature Pack for Dynamic Scripting V2.0adds support for the PHP scripting language support to CICS TS V5.1 to rapidly create and deploy situational applications

CICS TS Feature Pack for Security Token Extensionsadds support for the open standard Security Assertion Markup Language (SAML) data format for exchanging authentication and authorization data between CICS and other parties

Order in ShopzSeries for delivery by internet or tape

Supported by IBM service

CICS TS V4.1

IntegrationEvent processing

Atom feeds from CICS

Web services standards, monitoring, stats

Integrated support for WSRR

Transaction routing & system links for IPIC

IPv6, identity propagation,
large file hosting

Performance and scaleXML System Services parsing

JVM server runtime environment

Wild branch diagnosis improvements

Adherence to z/Architecture MVS linkage

Application supportApplication bundles

Application components

Improvements to data mappings & new API

Java 6

Enterprise managementCICS Explorer

RESTful API (CMCI)

Improved (WUI) browser views

Workload management optimisations

WebSphere MQ queue-sharing groups

Governance and SPI for resources

Improvements in CICS monitoring

Discovery Library Adapter for CICS

CICS TS V4.2

EventsSystem events

Assured events

Lifecycle management

JavaJava 7 64-bit applications

Multi-threaded server

OSGi packaging & management

ScalabilityMore threadsafe

Optimised threadsafe

64-bit exploitation and assembler applications

ConnectivityAxis2 web services

Web Services offload

HTTP & IP extensions

ManagementTransaction tracking

Workload management

Password phrases

CICS TS V5.1


Greater capacity - achieve cost savings through consolidation

Managed operations - control critical resource thresholds with policies

Increased availability - reduce the need for planned downtime

Deeper insight - extend performance and compliance information

Service Agility

First-class applications - create agile services from existing assets

First-class platforms - create agile service delivery platforms

Modern interfaces - build rich web experiences for critical applications

Foundational enhancements - extend core capabilities

125+ requirements satisfied!

CICS TS V5.1

CICS supports "one-to-many" event emission

Greater-than-32KB across MQ (DPL) bridge

Enhancements to IPIC add IMS support

Reduced application storage needs with GET and PUT container

Backup and restore entire CICSPlex System Manager (CICSPlex SM) systems

Automatic adjustment of the CICS clock for daylight saving time changes

A production-ready web container

Deploy lightweight Java servlets and JSPs

Local access to CICS applications and data

Roll-out of interface updates through OSGi

Integration with applications and platforms

Built on WebSphere Application Server Liberty profile for compatibility

CICS TS Feature Pack for Mobile

Group new and existing regions as platforms

Decoupling applications from the region topology.

automatic resource deployment and validation

De-provision resources when requested

Deploy applications to regions within a platform

Dynamically manage platforms with policies

Modern Interfaces

Foundational Enhancements

First-class Platforms

Manage disparate resources as a single entity

Rapidly move through the application lifecycle

Automate dependency management

Ensure rigorous yet flexible provisioning

Measure entire application resource usage

Dynamically manage applications with policies

First-class Applications

Platforms2.pngFoundation2.pngApplication2.png

CICS TS V5.1

Auditing of SPI commands that alter the system

Improved auditing of user IDs that make requests over IP

Extended identity propagation to include started tasks

Cipher suites used for SSL connections to be stored in the performance records

Calculate the actual and potential use ofspecialty processors

Regular status updates provided while lost locks recovery is taking place

Upgrade CICS versions and releases without requiring a z/OS restart

Modern batch feature pack

Refresh Secure Sockets Layer (SSL) certificates

Keep IPIC connections up and running

Support more IBM GDPS/AA solutions

Dynamically specify cross-system coupling facility groups

Better reflect current best practices with updated and simplified defaults

Automated control over critical system resources

Set data access thresholds on SQL or file access

Set program loop thresholds on EXEC LINK

Set storage request thresholds

Set CPU time thresholds

Policies can issue messages, abending tasks, or create events

Doubling the MAXTASK limit to 2,000

Increased 64-bit and reduced 24-bit storage usage

Greater parallelism from threadsafe API and SPI

Greater system parallelism through optimized TCB usage

Performance improvements from 64-bit Java 7

Greater access to 64-bit storage from Assembler programs

Greater Capacity

Scalability2.pngIncreased Availability

ec12_beauty_02-copy

24x7

Policy.pngDeeper Insight

10011010

Managed Operations

24x7

11011010

CICS TS V5.2 brings you more...

Integrates mobile capabilities and broadens the web programming model

without requiring additional middleware

Service Agility

Support distributed security standards and automatically safeguard critical runtime resources

without requiring additional system code


Deploy and manage several versions of a multi-program application and run them concurrently

without requiring additional regions

Cloud Enablement

+ Continuous enhancements to the solid foundation

CICS TS V5.2 editions and supporting tools

CICS TS V5.2Available since 13 June 2014

Software requirements includes:z/OS 1.13, or later

IBM 64-bit SDK for z/OS, Java Technology Edition V7 SR 1, V7.1, or later

CICS Transaction Server V5.2 Value Unit EditionOne-time-charge price metric for new Java workloads

For eligible workloads deployed in qualified System z New Application License Charge LPARs

CICS Transaction Server V5.2 Developer TrialEnables try-before-you-buy evaluation of CICS Transaction Server

CICS Tools V5.2 and z/OS Problem determination toolsAcceleraterate deployment of new CICS workloads on System z

Streamline CICS version-to-version migration efforts

CICS Transaction Gateway V9.1 Open BetaNew mobile support within CICS TG which enables new, modern workloads to be quickly and efficiently incorporated into existing CICS systems

Enhancements in connectivity and security

CICS TS V5 VUE (OTC)

zNALC LPAR (discounted z/OS)Java based CICS Service Enablement*New Java workloads*CICS TS V5, V4 or V3 (MLC)Regular LPAR (full-price z/OS)Existing CICS COBOL, PL1,C/C++, ASM applications running core business logicDPL* zNALC approval is required for each application CICS TS VUE is a separately licensed program and does not initiate Single Version ChargingTS V5.1 avoiding SVCReduced price for the z/OS operating system on LPARs that run a qualified application*zNALC pricingAlternative pricing model for new applications* using a one-time-charge price metricCICS One-time-chargeResponding to customer demand for an alternative pricing structureCICS TS Value Unit Edition

CICS TS V5 VUE (OTC)

zNALC LPAR (discounted z/OS)IBM Business Rules for z/OS providing new dynamic rules*CICS liberty profile providing new modern web interfaces*CICS TS V5, V4 or V3 (MLC)Regular LPAR (full-price z/OS)Existing CICS COBOL, PL1,C/C++, ASM applications running core business logicDPL* zNALC approval is required for each application Exploit the features of CICS TS V5.1 without having to upgrade existing back-end systemsNon-disruptiveRapidly augment existing CICS applications using the latest CICS Java support and Java service enablement capabilitiesService enablement*Using the latest 64-bit, Java 7, multithreaded JVMSERVER architecture for maximum scalability New Java Applications*Responding to customer demand for an alternative pricing structureCICS TS Value Unit Edition example workloads

CICS TS V5.1 Developer Trial

Evaluate the ValueExplore the CapabilityCreate the business caseTry before you buyNo charge license, no single version charging period

Feature-rich for evaluationSome restrictions such as 30 max tasks, works for 90+ days from download date

Assistance via CICSdev forum and IBM service APARs delivered in periodic service refresh and to CICS TS V5.1

See technote for details

Order from IBM Shopz with internet or physical delivery optionsOrder as often as needed

CICS TS V5.2 service agility

Mobile web services now integratedProvides support for RESTful web service requestsJSON in the HTTP body

New JSON assistant programsGenerate a JSON schema and WSBIND file from a copy bookCOBOL, PL/I, C and C++

Create a language structure and WSBIND file from a JSON schema

New linkable interfaceEquivalent to EXEC CICS XMLTRANSFORMAllows application programs to process JSON data

Support for Liberty features that provide JAX-RS, JAX-WS, and JAXB

Notes

CICS Transaction Server for z/OS, Version 5 Release 2 provides support for web service requests with JSON and the conversion between JSON and application data. Support for JSON greatly simplifies the use of existing CICS services by mobile applications, particularly those managed by IBM Worklight Server. You can expose CICS applications as web services with JavaScript Object Notation (JSON) payloads, create new RESTful applications, call existing JSON applications, and convert JSON from any source to and from the application data.This support for JSON and REpresentational State Transfer (REST) was previously available in the CICS TS Feature Pack for Mobile Extensions.


CICS JSONAssistant

Mobile web services architecture


Mobile and SOAP web services enhancementsMapping between unicode and UTF-16-BEUTF-16-BE supported as native type by COBOL, PL/I and C/C++ compilers

Basis for broader globalisation projects

Simple COBOL dynamic arrays supportedOccurs Depending On

Occurs Indexed By clauses

SOAP native parser optimisationsParser output stays in 64 bit storage

SOAP message built in 64 bit storage

Code page conversions use 64 bit storage

Benefit is 31 bit Virtual Storage Constraint Relief

Notes

Data mapping for SOAP and JSON web services supports UTF-16 data and more COBOL clauses, including OCCURS DEPENDING ON. With this support, you can represent a larger range of characters in web services application data and the TRANSFORM API. In the CICS data transformation service for SOAP and JSON web services and the TRANSFORM API, Unicode characters are transformed to UTF-16 data in COBOL, C, C++ and PL/I. Unicode is the widely adopted standard for handling most of the characters in use today and can be used as a basis for globalization of CICS applications. This release of CICS also supports the COBOL clause OCCURS DEPENDING ON, when the field is last in the structure, and the clause OCCURS INDEXED BY.

Mobile scenario

A

B

C

DFHLS2JS to generate the JSON artefacts for the target CICS service.

Mobile developer uses JSON schema to build a Worklight adapter.

Frontend mobile developer calls the Worklight adapter which calls the service hosted in CICS.

Connect directly to CICS from Worklight using end-to-end JSON


WebSphere Application Server Liberty profileIntroduced in CICS TS V5.1

Light weight web containerProvides Servlets and JSPs support for CICS

Runs in a JVM server in the CICS address space

Access to CICS functionality through the JCICS API

Existing web interfaces developed using JSPs and Servlets can be easily moved into CICS

Direct access to DB2, providing application developers with two routes to the data

CICS TS

JVM server

Liberty profile

Web
App

JDBC

DB2

CICS Resources

Notes

CICS Transaction Server for z/OS, Version 5 Release 2 upgrades the WebSphere Application Server Liberty profile to Version 8.5.5 and supports a broader set of its features. Java database connectivity, transactionality, and security infrastructure are all functionally enhanced. The Liberty profile is a lightweight development and application runtime environment that is well-suited to building web applications that do not require the full Java EE environment of traditional enterprise application server profiles.


Liberty profile in CICS TS V5.2Core featuresJava Transaction API (JTA 1.0)

Access to local DB2 resources (JDBC 1.0)

CICS Liberty Security

Liberty profile featuresAccess to remote DB2 resources with T4 driver (JDBC 1.0)

Java API for RESTful Services (JAX-RS 1.1)

Java Script Object Notation (JSON 1.0)

Java API for XML Web Services (JAX-WS 2.2)

Java Architecture for XML Binding (JAXB 2.2)

Notes

Support is provided for JDBC type 2 data sources. This support enriches your options for access to other data managers. You can use the JDBC DataSource API to access relational data that is stored in either a local DB2 database, managed by CICS resources, or a remote database using JDBC type 4 connectivity.Java Transaction API (JTA) support enables transactional web application developing using JTA API to be run in a Liberty JVM server and to coordinate transactional updates to both CICS resources and other third party resource managers, such as a JDBC type 4 driver connection using a remote data source. You can take advantage of the full range of WebSphere Liberty Profile application security functions. These include an extended range of authentication options, including HTTP basic authentication, single sign-on using LTPA cookies, form login, Trust Association Interceptors, and SSL client certificate mapping. Authorization options include both JEE role authorization and CICS transaction and resource security, which is based on the authenticated SAF userid. The Secure Sockets Layer (SSL) support in the Liberty JVM server HTTP listener is extended to support certificates that are stored in both System Authorization Facility (SAF) keyrings and Java keystores.


Java Transaction API

CICS TS 5.2

TransactionManager

Application

CICSXAResource

Type 4 DB

Liberty Profile

OT Domain

RM Domain

JTA can provide coordination of
updates across CICS and a remote DB

Liberty profile scenario

A

B

C

Modify application data logic to make JCICS API calls or direct JDBC calls, if required

Package application into a EBA for deployment into CICS Liberty

Install CICS application into CICS Liberty Server and enable using the CICS Explorer

Port JSP, servlet or JAX-RS presentation code into CICS Transaction Server


IPIC High AvailabilityAllows CICS to connect to a cluster entry pointAllows CICS to know the actual endpoint for recoveryNew TCPIPSERVICE attribute SPECIFTCPS

Notes

IP-connectivity (IPIC) support is extended to support more high-availability scenarios. This support helps to minimize the impact of issues that can arise when CICS communicates across a wide area network, for example, if the network fails to respond. Groups of regions from CICS Transaction Server for z/OS, Version 5 Release 2 can be clustered together and accessed through a shared TCP/IP end point from other client regions of CICS Transaction Server for z/OS, Version 5 Release 2 . This support enables individual CICS regions to be removed as a single point of failure, while permitting planned or unplanned outages of individual components, and provides a migration path for VTAM generic resource support when moving from SNA to an IP network

CICS TS V5.2 operational efficiency

Double the number of policy triggers

CICS TS

Cumulative Time

Syncpoint

Start

TSQ

DB2 SQL

Files

Storage

CPU Time

Policy

Task

Abend Task

Emit Event

Output Message

New V5.2 Triggers

CICS V5.1

Trigger:

Action:

TDQ

Prog. Link

Double the number of triggers are available to provide greater level of control to CICS

Notes

Double the number of policy triggersTemporary StorageNumber of requests or amount of data written

Transient DataNumber of requests

Elapsed TimeCheck is made at dispatch

Action triggered at next API call

STARTsNumber of requests

SyncpointsNumber of requests

Program LinkINVOKE APPLICATION is now included

Policy scenario

Define a policy to trigger an event when an application consumes too much total elapsed CPU time

A

B

C

Define the policy thresholds and trigger action that CICS should take

Associate the policy with the appropriate platform or application and deploy

When the threshold is breached, CICS triggers an event, updating an operations dashboard


Support for TLS 1.2 protocol and FIPS 140.2 Cryptographic StandardsFIPS 140.2 mandated by NIST SP800-131A directiveCipher suites can now be defined in XML in a zFS file

Greater flexibility and ease of definition

APAR PM97207 available for TS 5.1

System initialisation parametersENCRYPTION={ALL|TLS12|STRONG|}

USSCONFIG={/var/cicsts/dfhconfig|directory}Cipher XML files in USSCONFIG/security/ciphers

Extend NIST SP800-131A checking beyond sockets domainNew System Initialisation parameterNISTSP800131A={NOCHECK|CHECK}

CHECK means CICS is required to check for compliance with the NIST SP800-131A security standard

Checked by Sockets (SO), Java (SJ) and Pipeline (PI) domains

NIST=National Institute of Standards and TechnologyFIPS=Federal Information Processing Standards

Notes

Cryptographic ciphers enable CICS to enforce the use of TLS 1.2, and check for conformance to the NIST-SP800-131a security standard.Support for stronger cryptographic standards allows you to permit all system SSL supported ciphers and protocols, or restrict to those that are supported by Transport Layer Security (TLS) 1.2. CICS can check and report on conformance to the guidelines in the National Institute of Standards and Technology (NIST) Special Publication 800-131A (NIST-SP800-131A), which includes support for TLS.


Security Assertion Markup Language (SAML)OASIS open standard

XML based framework for describing and exchanging security information between
on-line business partners.

Web Single Sign-On

Dynamic creation of Identity Federations
(SSO across domains)

Notes

Security Assertion Markup Language (SAML) is an XML-based framework for describing and exchanging security information between online business partners. This security information is expressed in the form of portable SAML assertions that applications working across security domain boundaries can trust. The OASIS SAML standard defines precise syntax and rules for requesting, creating, communicating, and using these SAML assertions.SAML provides a solution for a number of problems: It provides an open standard for exchanging security information between Service Providers, also known as Federated Identity. It provides a means for end-to-end auditing. It provides a common source for user role or authority-based information


Security Assertion Markup Language (SAML)

IdP

SP

bookahotel.com

1

2

Authentication

bookaflight.com

SAML Token

3

Validate

IdP domain

Notes

An example of a security assertion while booking a flight and deciding at add a hotel. The identity provider aserts the users identity to the next service provider.


SAML Feature Pack integrated into CICS TS V5.2Linkable interface program DFHSAML

Channel and containers to provide input and output

DFHSAML links to Secure Token Service (STS), running inside a dedicated JVM server (preferably in a dedicated CICS region)

STS parses and validates SAML token

Most of STS function is zIIP off loadable

Outbound SOAP support for reusing inbound SAML TokensPreviously validated tokens only

Requester pipeline retrieves token from DFHSAML-OUTTOKEN container and puts in in WSSE security header of the SOAP request

Input SAML token is passed on unchanged

Configuration sample samlrequester.xml provided

Using the DFHTRANSACTION channelNo application changes are necessary

Notes

CICS supports SAML by providing an application programming interface (API), which consists of a linkable interface DFHSAML, a channel, and a set of containers. The API provides the means to enable CICS applications to validate SAML tokens, to extract SAML parts, and to augment SAML assertions by adding attributes. SAML support for web services provides the following facilities: Automatic token validation and extraction of SAML parts for inbound SOAP messages Addition of a SAML token into a web service request Augmentation of a SAML token before it is added into an outbound SOAP message

SAML security scenario

A

B

C

Client requests SAML assertion from Tivoli Federated Identity Manager or Datapower

CICS COBOL application extracts SAML containers from DFHSAML channel

The application can add additional attributes to the assertion for downstream components

A CICS application developer writes a COBOL program with behavior thats dependent on the SAML security token


Transaction channel & containersCreated for use by SAML, but can be used independently

No changes to EXEC CICS APIA PUT CONTAINER can create the Transaction Channel CHANNEL(DFHTRANSACTION)

If the Transaction Channel does not exist, a GET CONTAINER command will return CHANNELERR

New JCICS method in Task class
Task t = Task.getTask();
Channel tranChan = t.getTransactionChannel();


Kerberos supportSupport for inbound tokens from Kerberos systems

RACF definitions can map the Kerberos principal to a RACF userid

Web services can be configured to handle Kerberos tokens as the security tokenAlternatively, the userid extracted from the Kerberos token can be used to run the request

CICS API enhancement to validate a Kerberos token/extract the RACF userid

EXEC CICS VERIFY
TOKEN() TOKENLEN() TOKENTYPE(KERBEROS)

Notes

CICS Transaction Server for z/OS provides support for Kerberos.CICS supports Kerberos using the external security manager (ESM). The level of support depends on the support provided by the ESM. If your ESM is RACF, support is based on Kerberos Version 5 and Generic Security Services (GSS).CICS can verify a Kerberos token by configuring a service provider pipeline or by using the API command VERIFY TOKEN.


Commands that been made threadsafeEXTRACT, INQUIRE, SET STATISTICS

INQUIRE, SET MONITOR

INQUIRE, SET DISPATCHER

INQUIRE, SET SYSTEM

INQUIRE MVSTCB

INQUIRE, SET, DISCARD PROGRAM

INQUIRE, SET, DISCARD TRANSACTION

INVOKE APPLICATION

Dispatcher, transaction and monitoring statisticsTo better understand TCB pool usage

Notes 1

Dispatcher statisticsNew fields to understand the TCB pool performanceLast Excess TCB ScanDate/time of the last CICS dispatcher excess MVS TCB scan that did not detach any TCBs

Last Excess TCB ScanNo TCB DetachedDate/time of the last CICS dispatcher excess MVS TCB scan

Pool Limit reachedTime when pool limit reached

Dispatchable Queue (only applicable to the single TCB non-Open TCB modes):Current number of dispatchable tasks queued for the TCB

Peak number of dispatchable tasks that have queued for the TCB

Average number of dispatchable tasks have queued for the TCB

Notes 2

DSGLXSCN The date and time of the last CICS dispatcher excess MVS TCB scan that did not detach any TCBs. If the DFHSTUP report shows the date and time as --/--/---- --:--:--:---- then that indicates then an excess TCB scan has not happened yet.Reset characteristic: not resetDSGLXSND The date and time of the last CICS dispatcher excess MVS TCB scan. If the DFHSTUP report shows the date and time as --/--/---- --:--:--:---- then that indicates then an excess TCB scan has not happened yet.Reset characteristic: not resetDSGTMCDQ The current number of dispatchable tasks queued for the TCB.Reset characteristic: not resetDSGTMPDQ The peak number of dispatchable tasks that have been queued for the TCB.Reset characteristic: reset to currentDSGTMADQ The average number of dispatchable tasks that have been queued for the TCB.Reset characteristic: reset to currentDSGLTCBL The time at which the pool reached the maximum TCB limit. If the DFHSTUP report shows the time as --:--:--:---- then that indicates that the pool limit has not been reached since the statistics were last reset.Reset characteristic: reset to zero

Notes 3

Transaction StatisticsNew fields to understand the TCB pool performanceTime MAXTASKS last changed

Time last transaction was attached

Time MAXTASK was last reached

Currently at MAXTASK indicator

New Monitoring Domain statistics fieldsNumber of user transactions ended in interval

Number of system transactions ended in interval

Time last transaction attached

Time last transaction ended

MAXTASK at last transaction attached

Current user tasks at last transaction attached

Average user response time

Peak user response time

Time of peak user response time

CICS TS

CICS TS V5.2 cloud application multi-versioning

Rolling back to an older version of an application is a simple operation - mark the version as unavailable

Versioning provides support for the major.minor.micro system

Transition to newer (or older) version

Version 1.0.0

Version 1.0.1

Version 1.2.0

Version 2.0.0

Install, enable, make available

make unavailable

Notes

CICS TS V5.2 enables a platform to host multiple versions of the same application, and multiple applications at the same time. New versions of an application can be deployed to the platform without the need to disable or remove the previous version, and be made available to users without service interruption. This can improve service agility and reduce the business risk of deploying applications as users can be progressively switched to the new version to gain confidence in it, or switched to an older version if there are any issues.

Application multi-versioning with private resources

Application packaging helps you consolidate onto fewer regions by providing private program definitions

CICS TS

X

Y

Private programs

Customer App

Private programs

Payroll App

URIMAP

PROG1

LIBRARY

URIMAP

PROG1

LIBRARY

Notes

Library and program resources that are defined in CICS bundles as part of an application can be made private to that version of the application. This separation avoids resource name clashes between applications and application versions, and is useful for server consolidation.

Multi-versioning scenario

A

B

C

After fixing the bug in the code, repackage it with a new micro version number

A bug has been found and an urgent fix is required immediately

Once installed, switching to a new version of the application is simply a case of making it available

CICS takes care of moving clients to the new version of the application across all regions within a platform

CICS TS V5.2 cloud

Define more resources in a bundle for easier deploymentFILE

JVMSERVER

TCPIPSERVICE

PIPELINE

WEBSERVICE

Notes

The type of resources that can be defined in CICS bundles and managed as part of a platform is broadened to include files, JVM servers, pipelines, TCP/IP services, and web services. In addition, library and program resources that are defined in CICS bundles as part of an application are made private to that version of the application. This facility avoids resource name clashes between applications and application versions, and is particularly useful for server consolidation.

CICS Explorer V5.2

New Repository Explorer view

New Operation viewsTask related User Exits

Global User Exits

Shared TS Queues

Transaction Dumps

System Dumps

Unit of Work Links

Updated Pipelines view

New Workload Management viewsWLM Specifications and editorManage CICS workloads with a simplified and consolidated view of the CICSPlex SM elements that control workload distribution

Creates default routing rules

Add and rename additional routing rules

Can import an existing rule

Active Workload Definition, also known as Routing Rules, Editor

Notes

CICS Explorer, the strategic management interface for CICS TS, is upgraded to CICS Explorer V5.2. This is a major update to support the latest CICS TS and CICS Tools capabilities.CICS Explorer V5.2 is updated to include support for the new and enhanced capabilities of this CICS TS deliverable, such as:* Enhanced support for CICSPlex SM WLM* Improvements in support for modification of associated CICSPlex SM workload definitions, using a new sophisticated editor* Intuitive access to information about the state of running workloads

CICS Explorer presents a new way of managing your CICSPlex SM workloads. There is no change to the way the CICSPlex SM workload management operates, but by using CICS Explorer you can get a simplified and consolidated view of the CICSPlex SM elements that control where, and how, the work is distributed in a workload.

CICS TS V5.2 documentation

IBM Knowledge CenterAll IBM product documentation from one URL

Includes books in PDF format

Replacing online Information Centers for all supported versions of CICSDownloadable ICs are still available

http://www.ibm.com/support/knowledgecenter/

Notes

Documentation for CICS is supplied in the IBM Knowledge Center. This format offers benefits in searching, filtering, saving, customizing, and printing documentation for all IBM products. IBM Knowledge Center provides information for over 2500 IBM products. The information that was previously provided in product information centers is in IBM Knowledge Center. IBM Knowledge Center provides integrated tools for finding, filtering, customizing, saving, and sharing information.

IntegrationIBM Knowledge Center is one place to go to find information about all IBM products that you use.ConsistencyThere were differences in the presentation and function of information centers between products. IBM Knowledge Center provides the same set of functions for all product information.CustomizationYou can use IBM Knowledge Center filtering capabilities to select the information that you need to use. You can build the information that you need into customized collections. For example, you might create a collection about the products that you use regularly, or a collection about a particular task, involving multiple products, that you plan to do in the coming months. IBM updates to the information in your collection are automatically reflected and you can create PDFs of your collections. Feedback

You can rate the quality of topics and share your comments and tips with other users in the IBM Knowledge Center. You can continue to send feedback privately to IBM, if you prefer.

Runtime support for production ready web applications.

Integration with mobile applications.

Service Agility

Increased system capacity and capability to achieve more with less.

Automatic control of critical resources using policies.


Simplified system management and rapid application deployment.

On premise pattern based cloud deployment.

Cloud Enablement

CICS Transaction Server V5
the premier enterprise grade mixed language application server

Agenda

Rapid elasticity

Broad network access

Resource pooling

Measured service

On-demand self-service

5 Characteristics

Private cloud

Public cloud

Hybrid cloud

Community cloud

4 Deployment Models

Cloud - Deployment, Service, Characteristics

http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf

Getting started with CICS cloud deployment

Software as a Service (SaaS)

Platform as a Service (PaaS)

Infrastructure as a Service (IaaS)

3 Service Models

IBM Confidential

IaaS: Server, Storage, DatenbankPaaS: deploy Applications, Applikationsentwicklung und Testing / kurzfristigen Bereitstellung von Hardware inkl. deren Konfiguration mit den bentigten Images (Betriebssystem, Application Server, Datenbank)SaaS: ERP, CRM, SCM, Communication&Collaboration

Cloud Service Models

SaaS

PaaS

IaaS

Cloud Service Models CICS Perspective

CICS Applications

CICS Platform

System z


CICS Applications

CICS Platform

System z

Security

Integrity

Runtimes

Database

Communications

Lifecycle


CICS Applications

CICS Platform

System z

COBOL

Java

JSP

C++

PL/I

ASM

PHP

Groovy

CICS Platform

Security

Integrity

Runtimes

Database

Communications

Lifecycle

Stage 1: Create a platform

Simple layer of abstraction to decouple applications from the underlying complexities of a CICS topology

Consists of Region Types logical grouping collecting CICS regions with common characteristics

enables them to be managed as a unit in a platform

Created: define a region type & set up new CICS region definitions

Adopted: adopt existing CICS system group (CSYSGRP) as region type with its existing CICS regions

Terminal Owning Region (TOR)ProductionPayroll

Platform enhancements in 5.2

Platforms can both create and adopt your CICS topology

Advanced and consistent editing support for all Cloud resources

Share regions between platforms and region types

Create cloned regions and enforce capability at the region type level

Add/remove regions at run-time for extra control

Stage 2: Create an application and application entry points

Package CICS application in Application bundle

Deploy, manage, then monitor as a single entity across multiple regions in a platform

Application entry points

identify resources as access points to Application

control users' access to different Application versions

Bind application to platform for additional characteristics

TransactionsProgramsFiles

Applications in CICS

How we think about applications in CICS

How applications look after they have been installed

Bundle your resources > get Application Context

Create a CICS Bundle to keep your resources together

Consider as a vehicle to get them into (and out of) CICS

A CICS Application can contain several CICS Bundles

About Entry Points

PROGRAM that tasks call to access application

Program not required in this bundle

URIMAP* resources providing URIs for requesters to access application

Unique name (still) required

Must be contained in same bundle

Access for Liberty, HTTP, MQ

Application context data if entry point passed

Operation = FrontDoor

CICS Application Binding

Maps CICS bundles for application to region types in the target platform

Stage 3: Add resources for the application

Transfer responsibility for creating, installing, managing resources

Don't modify resources individually (use CICS Bundle/Application operations)

Application architects: carefully consider which resources to tie to CICS Bundle lifecycle

Specify resource separately and declare as import (dependency) if resource

cannot be defined in a CICS bundle

has different lifecycle

should not be private (only LIB & PROGRAM)

Transaction *Program *File **Library *OSGi BundleJVM Server **Pipeline **TCP/IP Service **URI map *Web service **Event (Application or System)Atom feedXML-based serviceChannel-based service*CICS 5.1 **CICS 5.2

What can be defined in a
CICS Bundle

V4Event Processing

Atom

Java/OSGi

V5.1LIBRARY

POLICY

PROGRAM

TRANSACTION

URIMAP

V5.2TCPIPSERVICE

JVMSERVER (including Liberty)

FILE (recoverable & unrecoverable)

WEBSERVICE, PIPELINE

Stage 4: Add a policy

Rules to describe controls or actions

For one or more application tasks

Threshold conditions to manage behavior of user tasks

e.g. define a threshold for the amount of storage allocated by a user task, and make CICS issue a message if the threshold is exceeded

Stage 5: Remove the application from the platform

Complete lifecycle by removing application from platform
>> unavailable, disable, discard

Removal of individual versions possible

Provisioning application
update with no loss of service

Video - 3 minutes

Getting started with CICS cloud deployment

Hosting two versions of a CICS application concurrently on the same platform

Video - 9 minutes

Agenda

Connecting and managing mobile workloads with CICS

IBM MobileFirst and Ready Apps

Mobile workload pricing

Mobile Integration with CICS

CICS Mobile Demo

Using IBM MobileFirst Ready App:
Banking Retail

Jennifer NottA/NZ Techline

[email protected]

Video - 2 minutes

Ready Apps

Part of IBM MobileFirst application development portfolio

An extension to WorklightA suite of industry-specific pre-configured Apps

Saves up to 60% of time and resources in development

Streamlines design & enables customization to client standards

Deploy to any platform or device

Enabled for API integrationMobile apps can access & locally integrate remote and diverse data and featuresIntegration with backend or partner systems

Using open protocols and Web standards

Launched in Feb 2014

Include Apps for banking, retail, health care,
insurance, transportation, government, industrial

Backed by a formal application release programEnsures ongoing refresh & enhancements

designed to integrate with Back-End environments

flexible to accommodate multiple client environment situations. Each Ready App has a customized set of API calls based on industry focus

Ready App Architecture

Ready Apps address customer needs by enabling basic API (Application Programming Interface) integration. Ready Apps enhance the ability to easily integrate mobile API consumption models by participating in the emerging API ecosystem. They use open web APIs and standards to invoke remote resources that reside on multiple systems of record. In this way, mobile devices can leverage API ecosystems to consume enterprise data and create composable digital products that aggregate digital content in new ways.

Mobile application overview diagram

Mobile Device

MobileApplications

Security Layer 1

DB2

Security Layer 2

CICS, IMS

DeviceFamily.pngClient 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.

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

Mobile application integration is realized with Worklight Adapters

Worklight is a MEAP (Mobile Enterprise Application Platform) positioned between the mobile devices and the back-end systems. It will provideas the platform where the server side of the app resides, but its function is not limited to hosting the mobile app. It can act as a Console to fulfill Application Management tasks as version control, it can provide information of what devices are connected does some analytics. The whole application lifecycle tasks can be carried out. In addition IBMs MEAP (Worklight) provides adapters. These are predefined (but customizable) structures to connect to back-end using protocol-transformation from JSON to HTTP(S), WS, XML, SOAP, MQ etc.

Implement a CICS Integration using JAX-RS

This demo doesn't use Worklight - the app connects directly to the JAX-RS application hosted in CICS Liberty, but would normally put Worklight or another gateway between the app and CICSCICS TS V5.1 introduced support for the WebSphere liberty profile (available with WAS V8.5) - a fast and lightweight Java web container. Using the Liberty profile, developers can use the rich features of the Java Servlet and JavaServer Pages (JSP) specifications to write modern web applications for CICS.

CICS TS V5.2 has extended the range of Liberty features that it supports including Java API for RESTful Services (JAX-RS 1.1) and Java Script Object Notation (JSON 1.0).

CapabilitiesTasks that are authenticated in CICS using Liberty security can use the user ID derived from any of the Liberty application security mechanisms to authorize transaction and resource security checks in CICS. The CICS user ID is determined according to the following criteria:1. Liberty application security authentication.(Note: All SAF user IDs authenticated by Liberty must be granted read access to the Liberty JVM server APPLID in the APPL class.)2. If an unauthenticated subject is supplied from Liberty, then the USERID defined in the URIMAP will be used.3. If no USERID is defined in the URIMAP the request will run under the CICS default user ID.

Note: The SSL support in the Liberty JVM server HTTP listener is extended to support certificates that are stored in both System Authorization Facility (SAF) keyrings and Java keystores. Provided by JSSE

The CICS TS Feature Pack for Mobile Extensions V1.0 enables you to extend the reach of your existing COBOL, C/C++, and PL/I programs to mobile devices, without having to make costly changes to your applications. The feature pack adds support for web service requests using JavaScript Object Notation (JSON) and the conversion between JSON and high-level language data structures, creating an efficient method of consuming enterprise data on a mobile device.

Axis2 is a Java-based implementation of a web services SOAP engine

New support for JSON is built on the existing web services support. The Feature Pack uses existing CICS web service technology: a separate WSBIND file provides the mapping from the COBOL, C/C++, or PL/I language structures to JSON, or from JSON back to the language structure. Requests are process by CICS in a web service pipeline, taking advantage of the proven web service infrastructure within CICS Transaction Server.

Ready App demonstration - Banking: Retail Bank

Message Center

User can access personal inbox with messages from agents and application notifications

Accounts Management

User can lookup summary by accounts and drill down to transaction details as well as filter transactions (debit, credit)

Mobile Cash

User can withdraw cash from an ATM without inserting a tangible ATM card by requesting code from device and entering it at ATM

Transfer Funds

User can transfer funds from one account to another account

Pay Bills

User can set up reoccurring or one-time bill pay from accounts.

Peer to Peer Payments

User can make a peer to peer payment and add new payees from their personal contact list on their mobile device.

Deposit Check

User can take a picture of an endorsed paper check and remotely deposit the check into a selected account.

Goal Setting

User can set financial goals for the future, whether they are saving for a future event (vacation) or budget control

Find Nearby Branches

User can locate nearby branches through GBS-functionality on mobile device, and view banking services and hours by location

Branch Contact

Quickly contact branch and account managers to inquire about account services, problems, or mobile support

Intelligent Alerts

User receives customized alerts concerning account activity such as overdraft, bill payments, and money transfers

Preference Management

User can set alerts for certain thresholds

Spend Analysis

User can view spend behaviors based on users tagging of transactions

Banking Retail Bank Ready App Features

CICS Explorer Views

Demo uses Resource Group MOBBANK in Region CICSAOR1

- uses a VSAM file (BANKTRAN)- accessed by a COBOL program (TRANV) to store transactions

File we will use

CICS Explorer Views

Open the Files view and filter for file BANKTRAN

- Browse and Add count are 0

The Mobile Device

Select Accounts

Select Everyday Savings

The Mobile Device

Browse count increases one for each record browsed in the file

Transfer Funds causes Add count to increase by 2

- transaction created for both sending & receiving accounts

Mobile Workload Pricing for z/OS

Jennifer NottA/NZ Techline

[email protected]

No Infrastructure Changes Required

Applicable to workloads running on zEC12 and zBC12

60% reduction in reported CPU utilization for Mobile transactions

New System z mobile pricing

Current Workload

Prior Peak Utilization

Growth Due to Mobile

New Peak Utilization

Reduced cost of growth on Mobile workloads

Scale IT Investments with the growth & business returns of mobileLeverage existing System z data and transaction processing for mobile

Mobile pricing helps customers leverage their investment

New pricing for mobile workloads on z/OS can improve the cost of growth for mobile transaction volumes that can cause a spike in software charges.

This new pricing will provide up to a 60 percent reduction on the processor capacity reported for Mobile transactions, helping normalize the rate of transaction growth used for software charges.

Its not just mobile thats affecting how clients build and charge for services, cloud computing offers customer a new approach for building, deploying, and paying for new (potentially mobile) applications

Mobile Workload Pricing for z/OS

Mobile Workload definitionWorkload that is processed by a defined mobile application

Originates from a Smartphone or TabletEither Mobile App or Web browser from device

MWP enhancement to Sub-Capacity pricingIs not a new pricing metric

Mitigates the impact of Mobile on MLC charges when higher transaction volumes can cause a spike in machine utilization

Improves the cost of growth due to mobile transactions in System z

No infrastructure changes requiredNo separate LPARs needed

Pricing basics

zSW product pricing is based on either MLC or OTC/S&SCICS, IMS, DB2, WAS and MQ are MLC

MLC is calculated each month per product according to usage

Usage is based on either Full capacity of the machine or Sub Capacity

Full capacity means that products are all charged for the msu rating of the machine/modelEg. A machine which is rated at 1000 msus will cause

every product licensed on that machine to be charged at 1000 msus every month

Sub-capacity means that only the peak msu utilization of the machine across a month is used to charge the products SCRT tool is used monthly to report peak utilization and submitted to IBMBased on SMF data

Key requirements

Enterprises running a zEC12 or BC12Mobile workload can be running on any zEnterprise machine incl z196 or z114

Use one of the MWP defining programs to process mobile transactionsCICS, IMS, DB2, WMQ, WAS

Implement sub-capacity pricing with AWLC or AEWLC

Meet mobile workload tracking and reporting requirements

MWP Reporting Process

New tool: MWRTReplaces SCRT for customer who take advantage of MWP

Windows-based Java tool makes adjustments to reported LPAR MSUs based on Mobile transaction data

Customers need to track mobile transactions and produce a file showing mobile CPU consumption each monthIBM-specified CSV format inputs into MWRT tool

MSU adjustments and monthly peak calculation for billingMWRT subtracts 60% of reported Mobile MSUs from an LPAR in each hour

All software in the LPAR will benefit from lower MSUs

Tool calculates new monthly MSU peakEssentially redraws the rolling 4 hour average curve across the month

Example: Sample LPAR MSU values by hour

SCRT calculates the Rolling 4-Hour Average (R4HA) MSU peakAll workloads are included

Peak R4HA value = 1404 MSUs

LPAR MSU values adjusted for mobile contribution

MWRT removes 60% of the Mobile workload, interval-by-intervalNon-mobile workload is unchanged

Billing for the month is based upon the newly calculated R4HA curve after the mobile workload has been reduced

New Peak R4HA Value = 1231 MSUs
MWRT savings = 173 MSUs

Provides benefit when Mobile workloads contribute to monthly peak MSUs;
Off-peak MSU adjustments will not affect MSUs used for billing.

Original Peak R4HA value = 1404 MSUs

Example: reducing Mobile impact to LPAR peak

z/OS &Other

CICS

Measure LPAR MSUs: Standard SCRT methodology, SMF 70 records

1,500

Usage

Tag Mobile transactions:e.g. Capture CICS transaction details (SMF 110 records) and filter by transaction type

Other

Mobile

Other

1,380 MSUs

Subtract 60% of mobile MSUs:-60% * 200 = -120

Measure CICS usage:Capture SMF 89 record in new IBM reporting tool (replaces SCRT); SMF 89 is IBM usage standard

CICS,z/OS &Other

200

100

100

80

Adjusted LPAR MSUs:
Per new MWRT reporting tool

Transactiondefinitions

Adjusted LPAR MSUs used to determine peak for month; Pricing & billing BAU based on peak

MSUs

1

2

3

4

5

6

300

Mobile

LPAR MSUs for billing (Standard)z/OS/Other 1,500CICS 1,500

LPAR MSUsfor billing (Adjusted)z/OS/Other 1,380CICS 1,380

Figures are for illustrative purposes only.

MWP Reporting Process

Mechanisms by which existing capabilities of z/OS sub-systems can track mobile transactions

How can you detect mobile workload

Mobile workloads can include applications of many sortsNew applications specifically designed for the platform

New application procedures that utilize existing application logic under the covers RESTful Liberty

Existing applications accessed in a new way

Customers need to process mobile txn data in a predefined CSV file for MWRTIBM must approve the data gathering methodology

Data must be general purpose processor CPU secondsCICS, DB2, IMS, MQ or WAS by hour, by LPAR

MWRT Users Guide available

New applications may be sufficient to simply identify the transactionsFor all other mobile originated work, need to identify all work that originated from mobile, not just the programs initiated by it

Detecting the origin of a mobile workload in CICS

Can use CICS monitoring records to tie all work togetherDFHCICS Performance class record (SMF 11) Origin DataAlso returned in Task Association on active tasks

Available in CICS Explorer Tasks transaction tracking search with history on

Use modified Pipeline attach transaction to identify mobile work entering CICSCant use origin data directly CWXN -> CPIH

Cant differentiate mobile from other web services

URIMAP can alter the pipeline attach transactionCan be used toIdentify mobile application workload

Provide an identifier to track more complex mobile application work

Example:Pipeline Attach Transaction: MBL0 in URIMAP

MBL0 is a clone of CPIH

Once the pipeline attach transaction is knownIdentify all tasks with the same Origin

Use Origin data to identify tasks initiated by mobile work regardless of the type or location of the program being run

ThankYou_Graphic_White

Mobilizing the Mainframe.
Customer mobile enabling a CICS-based
warehouse management system

Video - 2 minutes

DataPower Gateway Appliance

CICSCOBOL, PL/I, C/C++, and Java Services

z/OS ConnectJSON/httpJSON/http(s)JSON or SOAP/httpJSON/http(s)JSON/httpWOLA JCICS

CICS TransactionGateway *

ECIMobile topologies to connect to CICS

Mention CICS TG (in place of z/OS Connect)Particularly useful for customers with CTG infrastructure today or want direct Restful interface to CICS applications running in older versions of CICS

Link: Look at each topology in turn, capabilities, deployment scenarios and benefits

CICS TS mobile support

CICS Mobile Feature Pack - Available on CICS TS V4.2 and V5.1Provides support for RESTful web service requests

JSON in the HTTP bodyJSON assistant programs

Generate a JSON schema and WSBIND file from a copy book

COBOL, PL/I, C and C++

Create a language structure and WSBIND file from a JSON schema

CICS TS V5.1 and V5.2Provides support for Java based restful APIs

JAX-RS and JSON Liberty features

CICS TS V5.2Integrates Mobile Feature Pack

New LINKable interfaceAllows COBOL application programs to process JSON data

Set of Application containers

Good for outbound JSON services

CICS Transaction Gateway V9.1JSON to ECI Gateway

Support CICS JSON assistant and wsbind file

Worklightapps

Worklight HTTP adapters

CICSLibertyJAX-RS applicationCICS
appJSON

z/OS ConnectCTGWeb services pipelineSOAP

Connecting via Worklight to CICS

JAX-WS application

Worklight can create either Native, Web, or hybrid apps.Green indicates a supported path. Red an unsupported path. Yellow is a path that is already in plan.The Worklight HTTP adapter is used to invoke web services (SOAP over HTTP) or RESTful services (JSON over HTTP)See the Worklight InfoCenter for a description of all the Adapters: http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m5/topic/com.ibm.worklight.help.doc/devref/c_overview_of_ibm_worklight_adap.htmlTo prevent chart confusion, I did not include lines from MQ/WMB to all other components, we know that MQ can talk to CICS, IMS, and DB2.

Kyle Charlet (IMS):The JDBC adadpter in worklight can also be used for access to IMS data - we need to validate thisThe HTTP adapter in worklight can also be used for access to IMS trans - we need to validate thisMuch of the infrastructure we hope to have complete this year. We are currently planning for a public rollout in October 2014. This isn't hardened in plan yet however.

To access DB2 on z/OS you still need a DB2 Connect license. That is installed in WAS with the JDBC driver.

WMB users can use patterns in the WMB GUI to create Worklight adapters to send messages to SAP, CICS, IMS, DB2, Seibel, Peoplesoft. The patterns are deployed to the Message Broker, and the adapters are imported into Worklight to be used by mobile applications. WMB adapter uses HTTP/JSON to communicate to WMB on z.

XML

JohnDoeAnnaSmithPeterJones

300 Bytes Approx.

JSONvar employeesArray = [ { "firstName":"John" , "lastName":"Doe" }, { "firstName":"Anna" , "lastName":"Smith" }, { "firstName":"Peter" , "lastName": "Jones" }];

150 Bytes Approx.

Its the same data, but 50% smaller!50,000 Example customer records:

XML: ~14 MBJSON: ~7 MB

05 inquireCatalogRequest. 10 startItemRef PIC 9(4) DISPLAY. 10 itemCount PIC 9(3) DISPLAY. COBOL copybookJSON request JSON Response{ "inquireCatalogRequest" : { "startItemRef" : 5, "itemCount" : 1 } }{ "inquireCatalogResponse": { "returnCode": 0, "responseMessage": " ", "listStartRef": 5, "lastItemRef": 10, "itemCount": 1, "catalogItem": { "itemRef": 10, "itemDescription": "Ball Pens Black "department": 10, "itemCost": "002.90", "inStock": 0, "onOrder": 0 } }}Example: Catalog Manager Inquire Catalog

Deploying a JSON web service in CICS

Steps to deploy a CICS JSON web serviceDecide whether to start with a language structure (bottom-up approach) or from a JSON schema (top-down approach)

Run the JSON assistant batch job, supplying the appropriate artifacts to generate a WSBIND file

Define and install a PIPELINE resource in CICS with an appropriate pipeline configuration file for JSON

Copy the WSBIND file to the PIPELINE's web services directory, and perform a PIPELINE SCAN to generate the WEBSERVICE and URIMAP resources

Your JSON web service is ready to process requests

JSON web services pipeline

Request-response and RESTful patterns

Request-responseRequest message and a response message may differ

Action to be performed is encoded in the message

HTTP POST method only

Similar to a remote procedure call style of interaction

RESTfulA single message serves as the request or response depending on the HTTP method

Application uses the HTTP method to determine the action. Supported methods specified when running DFHJS2LS.

Each service operates on a single type of resource. The resource can be identified using the URI.

DFHLS2JSLanguage structuresWSBindJSON Schemas

Developing a JSON web service Starting with a language structure

Run the DFHLS2JS batch tool with language structures for the request and response messages

Generates JSON schemas and a WSBind file.

Use the JSON schema to send appropriate messages from the client application

DFHJS2LSJSON schemasWSBINDLanguage structures

Developing a JSON web service Starting with a JSON schema

Create JSON schemas describing the messages to be sent and received by the client application.

Run the DFHJS2LS batch tool with your JSON schemas

Generates language structures and a wsbind file.

Use the language structures as the interface to your application or wrapper program

Use this approach:

When you are writing a new application and you'd like to begin with a JSON interface

When you want to expose an existing application as a JSON web service by writing a wrapper program

Mobile appWorklight HTTP adapter

CICS

LibertyJVM serverJAX-RS applicationCOBOL programVSAM FileDB2TSQ

JSONJSONJSON web service with JAX-RS - Liberty

There are two main ways to notify a mobile user:OS notifications. These are the small message windows that pop up from iOS or Android devices, and are what we typically think about when we say push notification. To trigger these, your Worklight application uses a Worklight service to send the push notification. Under the covers, Worklight code sends the push request to either an Apple or Android service, who will then verify the users acceptance of push notifications, and then send the notification to the mobile device. Worklight helps here by providing a single push API that talks to all the mobile push services.

SMS. You use a third-party SMS Aggregator service to send an SMS message to the mobile device. This service is configured in Worklight and invoked via an adapter.

For more information, read:

http://www.ibm.com/developerworks/websphere/techjournal/1305_ramachandra/1305_ramachandra.html

https://www.ibm.com/developerworks/community/blogs/worklight/entry/sms_push_notifications_in_worklight1?lang=en

@Path("/catalog/items")public class Catalog {

@GET @Path(/categories/{category}) @Produces("application/json") publicList getItemsByCategory ( @PathParam("category") String category) { .... application logic .... }

@PUT @Path({itemRef}) @Produces("application/json") @Consumes(application/json) public CatalogItem updateCatalog( @PathParam("itemRef") String itemRef, CatalogItem updatedItem){... application logic ...}}

Skeleton JAX-RS application

Interoperable with WorklightCICS TG for z/OS V9.1 open beta - JSON Web Services

Typical concerns for mobile workloads in CICS

What is the impact toVolume of work and data

Change in usage patterns/peaks

SolutionsCICS Performance monitoring - CMF 110

Vertical scaling 64-bit.. VSCR

Tagging of mobile transactions Monitoring, transaction tracking, entry points

CICS Tools PA, IA

Polling

Bad for back-end load

Bad for user data restrictions

Only do something when you need to do work

Push notifications

Saves mainframe MIPS

Saves user data

Application design - notifications

CICS ApplicationCICS Event

Adapter

Business events from CICS TS V4.1

Assured events from CICS TS V4.2

System events from CICS TS V4.2

Push notifications from CICS

Agenda

Building hybrid application interfaces using JSPs, Servlets and PHP with CICS TS V5

Modern web interfaces

cics seminar 2014

Documents