This document discusses exposing mainframe applications and services to mobile through APIs. It provides an overview of IBM's API Management and z/OS Connect solutions. z/OS Connect allows exposing mainframe services running on CICS, IMS and other systems as RESTful APIs that can be accessed by mobile and cloud applications. It provides discovery of mainframe services, handles data transformation between JSON and mainframe data formats, and includes interceptors for security and auditing.
According to IDC, in 2013 “the worldwide smartphone market reached yet another milestone, having shipped one billion units in a single year for the first time”. This was an increase of almost 40% over 2012. If much of your business runs on CICS, you have probably already exposed at least some your CICS applications to the mobile world. But are you exposing these services in the optimal way for your company? Come to this session to discover what the supported options are for mobile exploitation in CICS Transaction Server, CICS Transaction Gateway and z/OS Connect. This session will compare and contrast the options available, so you can understand what is right for you. It will also demonstrate how you can use IBM Worklight with CICS TS to optimize your mobile deployments. Make sure your phone is on silent – you won’t want to be disturbed in this session.
Learn how IBM is using new technologies, applications and mobile devices to enable a smarter, more productive workforce. This short presentation shares IBM's journey enabling a flexible, mobile enterprise.
According to IDC, in 2013 “the worldwide smartphone market reached yet another milestone, having shipped one billion units in a single year for the first time”. This was an increase of almost 40% over 2012. If much of your business runs on CICS, you have probably already exposed at least some your CICS applications to the mobile world. But are you exposing these services in the optimal way for your company? Come to this session to discover what the supported options are for mobile exploitation in CICS Transaction Server, CICS Transaction Gateway and z/OS Connect. This session will compare and contrast the options available, so you can understand what is right for you. It will also demonstrate how you can use IBM Worklight with CICS TS to optimize your mobile deployments. Make sure your phone is on silent – you won’t want to be disturbed in this session.
Learn how IBM is using new technologies, applications and mobile devices to enable a smarter, more productive workforce. This short presentation shares IBM's journey enabling a flexible, mobile enterprise.
A technical overview of IBM MobileFirst Platform that explains how it can solve key enterprise challenges for a successful mobile journey.
Learn more on how IBM MobileFirst Platform can help your business: http://ibm.co/1L1SttH
Developing for Hybrid Cloud with BluemixRoberto Pozzi
How can you get all the benefits of developing your application in the cloud and guarantee a secure integration in a Hybrid Cloud scenario?
This deck, presented at IBM CloudKnow event in October 2014, explains how to do it with @IBMBluemix, the Platform as a Service solution from IBM.
The application is available on http://cloudknow-italy-web.mybluemix.net/home.html.
When communicating over public networks it is essential to send and receive information securely. The protocol widely used to secure these communications is SSL/TLS. (SSL/TLS refers to Secure Sockets Layer or to its successor, TLS, or Transport Layer Security). SSL/TLS uses digital certificates to provide authentication and encryption. To trust that a certificate is genuine and valid, it is digitally signed by a root certificate belonging to a trusted certificate authority (CA). Operating systems and browsers maintain lists of trusted CA root certificates so that they can easily verify certificates that the CAs have issued and signed.
IBM Collaboration Solutions Application Development - Frequently Asked QuestionsNiklas Heidloff
IBM Collaboration Solutions Application Development: Frequently Asked Questions
Entwicklercamp, Closing Session, 19.03.2014
http://www.entwicklercamp.de/EC14/Track0Session6
Niklas Heidloff, IBM
IBM Collaboration Solutions App Dev Community Advocate
OpenNTF Director and Technical Committee Chair
@nheidloff / heidloff.net
4156 Twist and cloud-how ibm customers make cics dancenick_garrod
InterConnect 2015 Session 4156 Twist and Cloud - How customers make CICS dance. Putting CICS into the cloud, is someone actually doing this? Since 2012 CICS TS Version 5 has been introducing and continuously enhancing its capabilities to support a Platform As A Service approach. Join speakers from CICS Technical Sales to hear about their experiences and how their customers gained value from cloud capabilities in CICS.
“Liberté, Égalité, Fraternité” (Liberty, Equality, Fraternity), is the slogan of France, coined around the time of the French Revolution. It also seems a pretty appropriate slogan for the mini revolution that is happening right now with CICS and WebSphere. The Liberty profile is a highly composable and dynamic application server runtime environment that is shipped as a part of both WebSphere and CICS. This session will introduce Liberty in CICS, compare the capability with WebSphere (note the ‘equality’ word) and discuss how these new Liberty applications can interact with and support the established fraternity of existing CICS applications that run your core business.
A technical overview of IBM MobileFirst Platform that explains how it can solve key enterprise challenges for a successful mobile journey.
Learn more on how IBM MobileFirst Platform can help your business: http://ibm.co/1L1SttH
Developing for Hybrid Cloud with BluemixRoberto Pozzi
How can you get all the benefits of developing your application in the cloud and guarantee a secure integration in a Hybrid Cloud scenario?
This deck, presented at IBM CloudKnow event in October 2014, explains how to do it with @IBMBluemix, the Platform as a Service solution from IBM.
The application is available on http://cloudknow-italy-web.mybluemix.net/home.html.
When communicating over public networks it is essential to send and receive information securely. The protocol widely used to secure these communications is SSL/TLS. (SSL/TLS refers to Secure Sockets Layer or to its successor, TLS, or Transport Layer Security). SSL/TLS uses digital certificates to provide authentication and encryption. To trust that a certificate is genuine and valid, it is digitally signed by a root certificate belonging to a trusted certificate authority (CA). Operating systems and browsers maintain lists of trusted CA root certificates so that they can easily verify certificates that the CAs have issued and signed.
IBM Collaboration Solutions Application Development - Frequently Asked QuestionsNiklas Heidloff
IBM Collaboration Solutions Application Development: Frequently Asked Questions
Entwicklercamp, Closing Session, 19.03.2014
http://www.entwicklercamp.de/EC14/Track0Session6
Niklas Heidloff, IBM
IBM Collaboration Solutions App Dev Community Advocate
OpenNTF Director and Technical Committee Chair
@nheidloff / heidloff.net
4156 Twist and cloud-how ibm customers make cics dancenick_garrod
InterConnect 2015 Session 4156 Twist and Cloud - How customers make CICS dance. Putting CICS into the cloud, is someone actually doing this? Since 2012 CICS TS Version 5 has been introducing and continuously enhancing its capabilities to support a Platform As A Service approach. Join speakers from CICS Technical Sales to hear about their experiences and how their customers gained value from cloud capabilities in CICS.
“Liberté, Égalité, Fraternité” (Liberty, Equality, Fraternity), is the slogan of France, coined around the time of the French Revolution. It also seems a pretty appropriate slogan for the mini revolution that is happening right now with CICS and WebSphere. The Liberty profile is a highly composable and dynamic application server runtime environment that is shipped as a part of both WebSphere and CICS. This session will introduce Liberty in CICS, compare the capability with WebSphere (note the ‘equality’ word) and discuss how these new Liberty applications can interact with and support the established fraternity of existing CICS applications that run your core business.
GSE Nordic 2015 CICS Connectivity in DevOps The business driver behind adopting a DevOps approach to developing software, is the need to deliver applications to the market faster, with lower costs and higher quality. With CICS Transaction Server providing the core services on which many of these applications rely, the importance of being able to connect to CICS and reuse these core services continues to increase. When CICS introduced native Web services about a decade ago, SOA became a reality for CICS customers. Today, many customers are doing tens of millions of SOAP based CICS Web services per day. Some are doing much more. But SOAP based CICS Web services are only a part of the CICS connectivity story. Support for the REST architectural style in CICS is an increasingly popular alternative to SOAP. And JSON is a popular alternative to XML for many application use cases. In this session, we will explore the different CICS connectivity options, suggest use-cases in which they can be of most value, and most importantly, learn which is the right tool for the job.
“My systems work perfectly—it’s the applications that are the problem!” If you have ever said (or thought) that, then this session is for you. Outages do not have to be "an application issue" anymore. In CICS TS 5, new policy-based capabilities allow you to set thresholds on the resources that your applications are allowed to consume. Rogue applications can be detected through various task threshold policies, such as excessive file or database access, repetitive program links, or abnormal storage requests. Once detected, you have the ability to notify, to react, or to ABEND. There’s a new sheriff in town, and it’s you. Come to this session to learn how to exercise your new power wisely.
S108 - 1 Billion Smartphones a year and counting – How is your CICS connected?nick_garrod
GSE Nordic 2015 1 Billion Smartphones a year and counting – How is your CICS connected? According to IDC, in 2013 “the worldwide smartphone market reached yet another milestone, having shipped one billion units in a single year for the first time”. This was an increase of almost 40% over 2012. If much of your business runs on CICS, you have probably already exposed at least some your CICS applications to the mobile world. But are you exposing these services in the optimal way for your company? Come to this session to discover what the supported options are for mobile exploitation in CICS Transaction Server, CICS Transaction Gateway and z/OS Connect. This session will compare and contrast the options available, so you can understand what is right for you. It will also discuss how you can use IBM MobileFirst with CICS TS to optimize your mobile deployments. Make sure your phone is on silent – you won’t want to be disturbed in this session.
Unlocking the universe of microservices for next gen cognitive appsDev_Events
Presentation by MobileFirst Developer Advocate, Marek Sadowski.
In this hands-on talk IBM approach to architecting apps and delivering framework of mobile backend as a service will be covered. Building cognitive mobile apps becomes easy with IBM Bluemix. Building an app that connects with StrongLoop, synchronizes offline datastore with Cloudant and leverage Presence Insights for location based services will be covered. Get inspired by adding Watson API for cognitive tweaks to spice up your app functionality. Finally it will be shown to give a final touch in creating better apps while monitoring its user sentiment in the app stores.
Key factors to enable a productive innovation through the use of Cloud technologies.
The role of a Platform as a Service to enable Hybrid Cloud and the API economy.
Presentation held @IBM Business Connect 2015
GSE Nordic 2015 Twist and cloud – How customers make CICS dance. Putting CICS into the cloud, is someone actually doing this? Since 2012 CICS TS Version 5 has been introducing and continuously enhancing its capabilities to support a Platform As A Service approach. Join speakers from CICS Technical Sales to hear about their experiences and how their customers gained value from cloud capabilities in CICS.
Frank Van der Wal - Technical Lead IBM Z BENELUX Digital Transformation Specialist :
Mainframe Innovation Tour (API enconomy, Hybrid Cloud, Machine learning)
Frank Van der Wal - Technical Lead IBM Z BENELUX Digital Transformation Specialist :
IBM Z to facilitate GDPR (and other regulation) compliance journey
Similar to Session 3 _exposing_mainframe_applications_services_v4 (20)
GSE Nordic 2015 Liberty, Egality, Fraternity “Liberté, Égalité, Fraternité” (Liberty, Equality, Fraternity), is the slogan of France, coined around the time of the French Revolution. It also seems a pretty appropriate slogan for the mini revolution that is happening right now with CICS and WebSphere. The Liberty profile is a highly composable and dynamic application server runtime environment that is shipped as a part of both WebSphere and CICS. This session will introduce Liberty in CICS, compare the capability with WebSphere (note the ‘equality’ word) and discuss how these new Liberty applications can interact with and support the established fraternity of existing CICS applications that run your core business.
GSE Nordic 2015 CICS Java – Beauty and the Beast After giving sessions about Java in the past few years that tell system programmers they should do Java on IBM z Systems and that Java is just like every other language, this session tries to explain why Java is a bit different in operating and handling. We will compare COBOL/PLI/Assembler with Java and provide insight into how the Java technology works on z Systems. Come along if you want to find out the answers to questions such as: Why can't you phase in a Java program? What does the JIT compiler do and how does it work? What is the development process of Java applications? How do I debugging and logging in Java applications?
S107 5 compelling reasons for using cics in the cloudnick_garrod
GSE Nordic 2015 5 Compelling reasons for using CICS in the cloud. So what does creating a CICS ‘Cloud’ really mean? And what exactly are these new CICS Cloud capabilities? How do these new Applications and Platforms artifacts relate to existing CICS technologies such as programs, transactions and regions? Where do these new Policies fit in? And most importantly, why would you do any of this? What value can you expect to derive from creating a CICS Cloud architecture? If you have ever asked yourself any of those questions, this session will give you five compelling answers. If you ever wondered what the CICS Cloud means in the real world, this session if for you.
S106 using ibm urban code deploy to deliver your apps to cicsnick_garrod
GSE Nordic 2015 Using IBM UrbanCode Deploy to deliver your apps to CICS. Deploying applications to CICS can be tricky, and you may be struggling to figure out how to handle the many new zFS artifacts such as cloud, bundles, Java, and web services. This could even be slowing down the adoption of new technologies that could deliver the solutions your business needs. This session will introduce IBM UrbanCode Deploy as a tool to automate many types of application deployments through your environments. It can provide rapid feedback and continuous delivery in agile development while providing the audit trails, versioning and approvals needed in production. See the new z/OS and CICS TS plug-ins for UrbanCode Deploy in action to deploy COBOL, web services, and Java applications to CICS in a single action.
GSE Nordic 2015 CICS Performance and Consolidation The CICS TS V5 releases introduce a number of runtime enhancements to reduce CPU usage, improve response times, reduce resource usage, while providing additional insight into transaction performance. Come along to this session as we explore some of the newer performance benefits found in CICS TS and how savings can translate to your environment. We will also look at a lab benchmark that consolidated CICS regions, maintaining throughput, saving significant MIPS, and reducing the management overhead.
GSE Nordic 2015 CICS Cloud and DevOps agility2 Creating a CICS cloud can provide a step change in agility. Add DevOps to the equation and it’s more like a quantum leap. Imagine if the latest CICS DevOps technology could fully automate the reliable and repeatable deployment of CICS applications through the entire lifecycle. Imagine a fully automated build environment for any style of CICS application. With common scripting languages and tools to create a continuous deployment model. Or imagine using a tool like IBM UrbanCode Deploy to provision any type of CICS application, in coordination with other application and database components in a single action. Better still, don’t try and imagine it. Attend this session and see it for yourself.
S102 cics the future is closer abridgednick_garrod
GSE Nordic 2015 - Future of CICS is closer than you think. There is a lot going on behind that mysterious curtain. Recently, the CICS development organization has adopted a new practice called ‘IBM Design Thinking’, which will forever change the way CICS products are developed. The core principle of this approach is to make sure we get as much feedback as possible on our future ideas. This is a quite unique opportunity to participate in a discussion regarding the future of IBM CICS technology. We will be sharing our views. And we will be hoping for lots for interactive feedback. Please don’t be shy!
GSE Nordic 2015 Conferece - CICS Opening. CICS TS V5.1 became available at the end of 2012, followed by CICS TS V5.2 in mid 2014. So what does that mean for you? Perhaps you can reduce operational complexity by hosting modern application interface logic inside the Liberty profile server within CICS? Perhaps you can use the new CICS Cloud capabilities to improve application reliability and accelerate deployments? Maybe you can improve your integration with Mobile devices? Or better control your costs though policies and consolidation? Nick and Ian open the CICS track to help you find out how CICS is reinventing mainframe application serving one again. Discover which sessions you should attend to get the most value from your attendance.
When CICS Transaction Server introduced native Web services about a decade ago, SOA became a reality for CICS customers. Today, many customers are doing tens of millions of SOAP based CICS Web services per day. Some are doing much more. But SOAP based CICS Web services are only a part of the SOA story. Support for the REST architectural style in CICS is an increasingly popular alternative to SOAP. And JSON is a popular alternative to XML for many application use cases. Additionally, there have been a great many enhancements to both these SOA styles in recent years. Come to this session to get up to speed on the evolution of these technologies. And most importantly, learn which is the right tool for the job.
Session 6638 - The One-Day CICS Transaction Server Upgrade: Migration Conside...nick_garrod
InterConnect 2015 Session 6638 The One-Day CICS Transaction Server Upgrade: Migration Considerations. After months of writing letters of justification you‘re finally OK to order CICS TS. The software has arrived and is ready to install. What next? Do you have to buy lunch for the z/OS Sys Progs to get them to install the latest release of z/OS? What do you need from the database administrators? Is this the time to “byte” the bullet and use CICSPlex Systems Manager? Are your CICS Exits and User Replaceable Modules still valid? What will it take to get them working with this release of CICS? What will you have to tell the Application Programmers? Is your shop relying on any function that has been removed from this release of CICS? Come to this technical session to get the answers to the above questions and more.
Artificia Intellicence and XPath Extension FunctionsOctavian Nadolu
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
AI Pilot Review: The World’s First Virtual Assistant Marketing SuiteGoogle
AI Pilot Review: The World’s First Virtual Assistant Marketing Suite
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-pilot-review/
AI Pilot Review: Key Features
✅Deploy AI expert bots in Any Niche With Just A Click
✅With one keyword, generate complete funnels, websites, landing pages, and more.
✅More than 85 AI features are included in the AI pilot.
✅No setup or configuration; use your voice (like Siri) to do whatever you want.
✅You Can Use AI Pilot To Create your version of AI Pilot And Charge People For It…
✅ZERO Manual Work With AI Pilot. Never write, Design, Or Code Again.
✅ZERO Limits On Features Or Usages
✅Use Our AI-powered Traffic To Get Hundreds Of Customers
✅No Complicated Setup: Get Up And Running In 2 Minutes
✅99.99% Up-Time Guaranteed
✅30 Days Money-Back Guarantee
✅ZERO Upfront Cost
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI AppGoogle
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-fusion-buddy-review
AI Fusion Buddy Review: Key Features
✅Create Stunning AI App Suite Fully Powered By Google's Latest AI technology, Gemini
✅Use Gemini to Build high-converting Converting Sales Video Scripts, ad copies, Trending Articles, blogs, etc.100% unique!
✅Create Ultra-HD graphics with a single keyword or phrase that commands 10x eyeballs!
✅Fully automated AI articles bulk generation!
✅Auto-post or schedule stunning AI content across all your accounts at once—WordPress, Facebook, LinkedIn, Blogger, and more.
✅With one keyword or URL, generate complete websites, landing pages, and more…
✅Automatically create & sell AI content, graphics, websites, landing pages, & all that gets you paid non-stop 24*7.
✅Pre-built High-Converting 100+ website Templates and 2000+ graphic templates logos, banners, and thumbnail images in Trending Niches.
✅Say goodbye to wasting time logging into multiple Chat GPT & AI Apps once & for all!
✅Save over $5000 per year and kick out dependency on third parties completely!
✅Brand New App: Not available anywhere else!
✅ Beginner-friendly!
✅ZERO upfront cost or any extra expenses
✅Risk-Free: 30-Day Money-Back Guarantee!
✅Commercial License included!
See My Other Reviews Article:
(1) AI Genie Review: https://sumonreview.com/ai-genie-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIFusionBuddyReview,
#AIFusionBuddyFeatures,
#AIFusionBuddyPricing,
#AIFusionBuddyProsandCons,
#AIFusionBuddyTutorial,
#AIFusionBuddyUserExperience
#AIFusionBuddyforBeginners,
#AIFusionBuddyBenefits,
#AIFusionBuddyComparison,
#AIFusionBuddyInstallation,
#AIFusionBuddyRefundPolicy,
#AIFusionBuddyDemo,
#AIFusionBuddyMaintenanceFees,
#AIFusionBuddyNewbieFriendly,
#WhatIsAIFusionBuddy?,
#HowDoesAIFusionBuddyWorks
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
Why Mobile App Regression Testing is Critical for Sustained Success_ A Detail...kalichargn70th171
A dynamic process unfolds in the intricate realm of software development, dedicated to crafting and sustaining products that effortlessly address user needs. Amidst vital stages like market analysis and requirement assessments, the heart of software development lies in the meticulous creation and upkeep of source code. Code alterations are inherent, challenging code quality, particularly under stringent deadlines.
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
What is Augmented Reality Image Trackingpavan998932
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Launch Your Streaming Platforms in MinutesRoshan Dwivedi
The claim of launching a streaming platform in minutes might be a bit of an exaggeration, but there are services that can significantly streamline the process. Here's a breakdown:
Pros of Speedy Streaming Platform Launch Services:
No coding required: These services often use drag-and-drop interfaces or pre-built templates, eliminating the need for programming knowledge.
Faster setup: Compared to building from scratch, these platforms can get you up and running much quicker.
All-in-one solutions: Many services offer features like content management systems (CMS), video players, and monetization tools, reducing the need for multiple integrations.
Things to Consider:
Limited customization: These platforms may offer less flexibility in design and functionality compared to custom-built solutions.
Scalability: As your audience grows, you might need to upgrade to a more robust platform or encounter limitations with the "quick launch" option.
Features: Carefully evaluate which features are included and if they meet your specific needs (e.g., live streaming, subscription options).
Examples of Services for Launching Streaming Platforms:
Muvi [muvi com]
Uscreen [usencreen tv]
Alternatives to Consider:
Existing Streaming platforms: Platforms like YouTube or Twitch might be suitable for basic streaming needs, though monetization options might be limited.
Custom Development: While more time-consuming, custom development offers the most control and flexibility for your platform.
Overall, launching a streaming platform in minutes might not be entirely realistic, but these services can significantly speed up the process compared to building from scratch. Carefully consider your needs and budget when choosing the best option for you.
Exposing mainframe applications and services to mobile
Exposing mainframe applications and data to mobile devices makes business sense, but how can you ensure that the critical connection of z Systems to mobile is as straightforward as possible? This session focuses on technologies that simplify the integration of z/OS applications such as CICS, IMS and WAS on z/OS with mobile applications. We examine the WebSphere Liberty z/OS Connect feature, which provides a simple, secure and standards-based interface to applications that must access z/OS assets. Additional technologies such as MQ, API Management and DataPower, which can further enhance integration, management and security also are covered.
The "API economy” has changed how developers think about building apps, and how organizations deploy software in the cloud.
Everywhere you look on the Web these days, it seems as if somebody’s launching new APIs.
There are over 10,000 API documented on programmable web today… and is significantly increasing as we speak.
Several years ago Jeff Bezos declared that all Amazon IT assets were to be exposed as APIs. Out of that “simple” declaration came an IT (and cultural) architecture that led to the stunning growth of Amazon Web Services, which is thought to be a billion-dollar business unit after only a few short years of growth.
Perhaps even more impressive is the fact that, today, Salesforce.com generates more than half of its revenue through its APIs, not its user interfaces.
Twitter is said to process 13 billion transactions a day through its APIs.
Google is around 5 billion transactions a day. (Hotel map)
New industries defined – Airbnb, Uber, etc
Let’s look at the Cars.com mobile app as an example.
Cars.com is a consumer of APIs, and has assembled several 3rd party apis together to form the base function of their cars app.
For example, they use a Map Provider API to provide a “store locator function”
APIs from a car dealer data aggregator for availability of certain makes and models.
They use APIs from a Bank to offer Loan calculators and origination
Auto insurance from an Insurance companies APIs
And can imagine them using the new Xtify API from IBM to provide notifications, that a car they were looking for was now found.
As the definition explains, the Web Economy is where companies [providers], expose their internal digital assets or service in the form of Web APIs to third party [consumers] with the goal of unlocking additional business value through the creation of new assets.
<MAXX> Emphasize definition… Also… Re-sub-title – The API Economy lifecycle
Businesses in various industries have developed “core competencies” over time, with supporting software functions and matching “brick and mortar” capabilities, such as banking, auto-dealership, healthcare providers, etc. These capabilities can be leveraged by exposing these functions as APIs.
Many of these software functions reside in z Systems
There are three key drivers for exposing these assets as APIs
Reaching new customers and markets through partner applications and solutions that leverage these business capabilities
Improving end-user experience with Mobile apps and/or with new system of engagement applications, possibly running in a cloud environment that access systems of record, and
Improving consumability of existing services by making it easy to look up via catalog, and easy to set up through self-service registration, and improving governance of access to existing services by managing entitlement and gaining insight from access history
Publishing an API for external consumption is not the same as
Listing in the internal asset repository for development and maintenance, or
Listing in runtime SOA Service Registry for use in Enterprise Service Bus (ESB) for routing, mediation and policy enforcement
A business web site (as in this example, by Sabre) lists all the APIs offered by this business to its partners, external (and also internal) application developers. An API description includes not just the description of the business functions, interface for invoking the API, and detailed description of various information field, example on its use. The APIs are categorized and listed using associated categories for ease of look up. Additional details include various entitlement policies and offering levels.
SOA efforts have been driven by developers’ productivity gain and enabling reuse of functions, i.e., focused on development of services.
API Management, on the other hand, is driven by consumption of these services, i.e., improving consumability of these services for both external and internal developers of applications accessing these APIs, while also retaining control by the providers of these APIs.
Improving consumability includes listing APIs in a browsable/searchable catalog and making it easy to register applications with the right entitlement level
Retaining control includes not only enforcing entitlements and managing workloads, but also providing insight based on access history and accountability for chargeback.
CAMS – Cloud, Analytics, Mobile and Social – are the enablers for new applications and services.
This includes:
Cloud – new applications, including by partners, accessing existing assets can be cloud based
Analytics – can be used both to improve system of interaction addressing customer experience as well as to gain business insight
Mobile – new forms of applications can be used in improving customer experience, and/or to deliver new services to end-consumers directly
Social – helps to understand better consumers and deliver services in new ways
Introducing IBM API Management: capabilities include
Exposing business services securely as APIs to developer communities, and analyzing API usage
Providing self-service API portals to external/internal app developers
Managing & monitoring the entire API platform
Key steps in Managing APIs
Create, assemble and define an API
Secure & scale the API
Share with developers
Manage growth & analyze results
End-to-end Architecture and IT roles in exposing, and consuming z assets as APIs
Three-tier Architecture:
Development of enterprise services from existing z assets, making it easy to invoke these applications
z application environments (CICS, IMS, WAS) provides tools and runtimes to develop and invoke Web and REST based services from applications based on COBOL and PL/I
IT role (Bob) is knowledgeable about this SW stack
Development and management of APIs exposing existing enterprise services
Addressing consumption and governance of APIs
Create an API , discover a suitable existing service, and assemble this API from this service
Development of Mobile, Cloud or Third-party applications consuming APIs
Browse catalog and identify APIs to consume
Register an application that will consume a specific API at a specified entitlement level
Use of developer portal to test APIs
APIM capabilities for discovering z assets:
Get a list of metadata maintained for various types of z based services (e.g., CICS or IMS, Web or REST services)
Discover a service based on keywords and attributes from the deployed services in z System
Import definition and configurations details of a service for creation and assembly of an API
Matching z capabilities:
Support for Web Services in CICS and IMS
z/OS Connect for supporting REST services for all z Applications
Discovery protocol support for both Web and REST services
IBM API Mgmt provides the management platform, while IBM DataPower provides the API Gateway to enforce API security and control . IBM APIM sits on a server as a virtual appliance, while DataPower can be a virtual appliance or a physical appliance
We start with a discussion that sets the context for the details that follow.
At the very heart of this discussion is the idea of devices and systems using RESTful calls and JSON data to access the mainframe and the applications and data that resides there. REST and JSON are becoming more and more common in the world of mobile and cloud system access to systems of record. REST and JSON are briefly described here. A more detailed description is offered a bit later in this presentation.
For REST and JSON to be effective, something has to be in place to recognize and handle the REST call and the JSON data.
Key Point: z/OS Connect is designed to be a REST/JSON interface to a z/OS LPAR.
z/OS Connect is software function written by IBM that runs inside an instance of WebSphere Liberty Profile z/OS, and uses existing connector technology to get to the backend systems. There is no charge for z/OS Connect; it is supplied as part of license entitlement to WAS z/OS, CICS or IMS.
This chart is a follow-on to the point made at the end of the previous chart. This chart explains the business value of z/OS Connect. The bullet points on the right side of the chart summarize the value proposition of z/OS Connect. At the end of the day it’s about a manageable and simplified interface to the z/OS LPAR for mobile and cloud devices that use REST and JSON.
This chart is intended to show the various solutions that IBM currently has to access System z Systems of Record. Note that several of these solutions will be moving towards have affinity with z/OS Connect and are moving towards integration.
The intent if for z/OS Connect to become established as the reference architecture for exposing z/OS through RESTful services.
As mentioned earlier, z/OS Connect is a no-charge software function that is part of your license entitlement for WAS z/OS, CICS or IMS. Each provides a delivery mechanism – Liberty and z/OS Connect will be supplied by WAS z/OS, CICS and IMS.
Note: the Liberty and z/OS Connect for CICS will run inside a CICS region. It is intended to be used only inside CICS regions and not outside. The Liberty and z/OS Connect supplied by WAS z/OS and IMS look very similar on the surface, but for IMS the access mechanism is a JCA resource adapter and not the local adapters. To use the JCA resource adapter with IMS, a running copy of IMS Connect is required.
For the purposes of this presentation the focus will be on WAS z/OS. That implies a Liberty Profile server instance with z/OS Connect enabled and configured. The implementation supplied with IMS is very similar, with the difference being the connectivity to IMS supplied as a JCA resource adapter that will talk to a running instance of IMS Connect. The CICS implementation is somewhat different in that the Liberty instance will run inside the CICS region, and the backend connectivity is provided through the JCICS interface of the CICS region.
We mention these delivery mechanisms because we have seen some confusion created by this. The different delivery approaches tends to obscure the story of z/OS Connect and the value it brings. We thought it best to bring this point out early to clear any misunderstandings that may be present. This will allow us to focus back on z/OS Connect and what it provides.
IMS specifics
The IMS mobile solution is a no-charge offering that provides a RESTful endpoint to access IMS transactions. The solution comprises the service provider for z/OS Connect and a Windows-driven, Eclipse-based tooling platform for service creation and administration.
Obtaining the service provider:
For customers who already have WAS for z/OS Liberty Profile, the IMS service provider is downloadable as 'IMS Mobile Feature Pack' from within the Liberty repository as described here: https://developer.ibm.com/wasdev/downloads/#asset/features-com.ibm.ims.imsmobile-1.0
For customers who do not have WAS Liberty Profile, the IMS Mobile Feature Pack service provider is available as a component of IMS Enterprise Suite for z/OS Version 3.1.1, PID 5655-TDA, orderable from Shop zSeries. WAS LP is bundled with IMS ES for z/OS 3.1.1.
Obtaining the IMS mobile tooling platform:
Service creation and administration is handled through IMS Explorer for Development, downloadable from http://www.ibm.com/software/data/ims/downloads.html.
This chart provides a little background on what “REST” is.
As the chart shows, REST is built on the notion of using HTTP verbs (GET, PUT, POST, DELETE) along with the URI (the portion of the URL that comes after the host and port) to indicate the function to perform. The example above is suggesting a function that gets some information on a customer number.
For this to work, both the client and the server much understand what functions are available and what URI formats are accepted. To assist in this, z/OS Connect has a discovery function that allows developers to understand what services are available through a z/OS Connect instance, and what the details of those services are.
RESTful services are growing in popularity because it’s relatively simple to implement.
JSON is a way of representing data in a name/value pair manner. The chart above shows a simple example of JSON for a customer data record – name, age, and address.
When a client (smart phone, tablet, browser, etc.) sends in a REST call with data, the JSON associated with the request (or response) is serialized and appended to the end of the URI. The data flows back and forth between client and server in this fashion. That means the “state” of the interaction is maintained with the flows going back and forth. That means there’s no affinity requirements – that is, there’s no requirement that a client talk to the same server instance each time. A cluster of server instances can exist and, provided they can access the same data and provide the same functions, it doesn’t matter if the client goes to server A, B or C. The lack of affinity routing requirements means the requests are stateless (state is carried with the request; not maintained outside the request). Stateless requests are very easy to manage in a network topology; stateful requests require stateful routing or state replication. REST and JSON avoids the need to worry about stateful routing.
Anticipated Question Answered: yes, z/OS Connect instances can be clustered, either on the same LPAR or across LPARs. The important thing is that all the z/OS Connect instances in a cluster operate identically, and have access to the same backend systems. The way to make multiple instances of z/OS Connect operate identically is to make sure they run with the same configuration information. On z/OS with Parallel Sysplex the ability to insure shared data in the background is quite achievable.
That talk about state and affinity routing was a bit of a detour from the main point about JSON as a means of representing data. JSON tends to be favored over XML because it is a bit lighter weight. Both XML and JSON need to be parsed (that is, the data extracted so it can be understood and worked on). Parsing JSON is a bit easier than parsing XML.
One of the concerns we’ve heard expressed is this – “Does z/OS Connect expose all my backend CICS programs to Internet?” And the answer to that is an emphatic “No!”
Key Point: z/OS Connect will only expose those services you code in the Liberty Profile configuration file. z/OS Connect does not scan your z/OS LPAR looking for programs to expose. z/OS Connect is only as smart as the configuration file information it operates from. You control what programs and applications are exposed as services through z/OS Connect.
That’s what this chart is saying … z/OS Connect operates from the information provided in the Liberty Profile configuration file, which is the server.xml file. You control what goes into that file. Only those backend programs you wish to expose as services will be discoverable and usable through z/OS Connect.
We mentioned earlier how there is a “discovery function” provided with z/OS Connect. This provides developers a means of determining what services an instance of z/OS Connect exposes, as well as details about a given service.
Sending in a URI with just /services will return a JSON list of services and their service URLs. A developer would use this to get an idea what services are configured in the server.xml for that instance of z/OS Connect.
If a service is of interest, they can send in a second URL, this one asking for details on the specific service. That will return a JSON object with details about the service. It is also possible to query for and receive the JSON schema for the service … both the request JSON schema as well as the response JSON schema. With that, a developer can develop the client-side code to invoke and make use of a service exposed through z/OS Connect.
We mentioned earlier how there is a “discovery function” provided with z/OS Connect. This provides developers a means of determining what services an instance of z/OS Connect exposes, as well as details about a given service.
Sending in a URI with just /services will return a JSON list of services and their service URLs. A developer would use this to get an idea what services are configured in the server.xml for that instance of z/OS Connect.
If a service is of interest, they can send in a second URL, this one asking for details on the specific service. That will return a JSON object with details about the service. It is also possible to query for and receive the JSON schema for the service … both the request JSON schema as well as the response JSON schema. With that, a developer can develop the client-side code to invoke and make use of a service exposed through z/OS Connect.
Here we’ll introduce some terminology that’s used with z/OS connect – a “Service Provider.” A service provider is simply the functional implementation that gets the request to a backend system like CICS or IMS. In the previous charts we showed the local adapters used to access a single CICS region. That was an example of a single service provider. But you are not limited to a single service provider; you may configure multiple service providers if you wish. For example, if you wished to expose programs in CICS and IMS, you would configure two service providers – one for accessing CICS (using the local adapters), and one for accessing IMS (which is implemented with a JCA resource adapter that communicates with a running instance of IMS Connect to access IMS).
If you had two CICS regions you wished to communicate with, you’d configure two service providers in the instance of z/OS Connect – one to access CICS region A and another to access CICS region B.
Note: the service provider interface is documented so that you may write your own service provider if you wish. You are not limited to just those supplied with z/OS Connect.
The earlier chart showed a bit of XML that pointed to a data transform definition. Here we’re showing you what that data transformation XML might look like.
On the surface this looks complicated but in reality it’s not – it’s really just telling z/OS Connect where to find the “bind” files and the JSON schema. Bind files provide the data field conversion information. They are produced by running a supplied utility (based on the WSBIND utility supplied by CICS) to transform program data definitions structures (for example, COPYBOOK for COBOL) into a file that allows z/OS Connect to understand the JSON-to-COPYBOOK conversion pattern. The XML above is illustrating how you tell z/OS Connect where the bind files are located, the suffix used for those bind files, as well as the location and suffix used for the JSON schema files.
With that information available, z/OS Connect can read in the bind files and perform JSON conversion. The converted data – now in something other than JSON – can be passed back to the backend program for processing. The backend program doesn’t need to know anything about REST or JSON … z/OS Connect is doing all that work in its role as a service interface to backend systems.
This is emphasizing the point made on the earlier chart – the bind files are created by using a program originally developed for the CICS web services function. This utility reads in COPYBOOK (or other data structures) and produces the bind file and JSON schema. The gray box on the chart is simply showing the JCL that might be used to run this utility program.
Note: you may either use the DFHLS2JS program supplied with the CICS Feature Pack, or use the utility supplied with z/OS Connect.
Another functional element of z/OS Connect is something called an “Interceptor,” which is a callout point that may be invoked for each request and invoked again for each response. It’s optional – you aren’t required to use the interceptor function – but if you wish to have callout processing performed for requests and responses you have this capability present.
Two provided interceptors are available – one is for security, which will work with SAF to perform authorization (EJBROLE) checks; and another for auditing, which will work with SMF to cut activity records. You can configure global interceptors that apply to all defined services, or you may define interceptors that apply to just those you wish them to apply to. For global interceptors you can ‘opt out’ of those global interceptors for specific services if you wish.
Note: like Service Providers, this Interceptor interface is documented and you may write your own interceptor code if you wish.
When the backend system is CICS and the local adapter support is used, it implies installing into the CICS region the Optimized Adapter support. This is not difficult to do; but it is necessary so the CICS region has the ability to communicate using the optimized local adapters.
The picture is showing the basics of the optimized local adapter function in the CICS region:
The Task Related User Exit (TRUE) provides the low-level function support for the optimized adapters. This TRUE must be active in the CICS region to communicate across the optimized local adapters.
The BBO$ link server is a long running task that handles the calls from z/OS Connect prior to invoking the target program. This is what makes the optimized local adapter calls transparent to the target program – BBO$ shields the target from the local adapter specifics.
BBO$ starts an instance of BBO# for each call. The reason this is separate from BBO$ is because the optimized local adapters supports the assertion of identity. When the thread ID from Liberty is asserted over, then each instance of BBO# is run under the identity of the asserted ID. When thread ID from Liberty is not asserted, then BBO# is run under the same ID as BBO$ and the instance is re-used.
The final link in this chain is an EXEC CICS LINK call to the target program from the BBO# invocation task. To the target program this looks like any other CICS program calling it. It has no knowledge of the optimized local adapters being part of the picture.
The WP101490 Techdoc at ibm.com/support/techdocs provides more information on WebSphere Optimized Local Adapters.
Another use-case for z/OS Connect and the optimized local adapters is for exposing “batch as a service.” This is possible because the local adapter APIs support a “listen mode” API that will put a batch program into a wait state until someone calls. That “someone” can be z/OS Connect calling to the batch.
To avoid updating all your batch programs, you can write a batch program that uses the local adapter APIs to “host a service” (go into a wait state), then have that program do a dynamic or static link to another program. That way the linked program doesn’t have to have any knowledge of the local adapter APIs. Upon return the first batch program would loop back and call the “host a service” API again. It would keep doing that for as long as you wished z/OS Connect to have a backend batch program exposing batch as a service.
z/OS Connect may work with IMS as well, though in the case of IMS it will use a JCA resource adapter to connect to IMS, not the local adapters. The JCA resource adapter will make a network call to a running copy of IMS Connect, which will then turn and use OTMA to get into the IMS region.
Everything else about z/OS Connect is the same as we discussed earlier. The only difference is the “service provider” being a JCA resource adapter. (And in truth the optimized local adapters also use a JCA resource adapter, but a different one. The difference is really the implementation below the JCA API layer – for the optimized local adapters code is invoked that does a cross-memory call; for IMS code is called that makes a network call to IMS Connect.)
Now let’s take a peek inside z/OS Connect to get a feel for how it works.
If we wanted to quantify those benefits we do have a view….this is from an external analyst – studying…
And the more use messaging is put to…the greater the benefits
So what does MQ offer? – messaging middleware – an interface layer helping to isolate applications connecting across different platforms from the mainframe to the mobile…
As we just covered MQ provides guaranteed, assured messaging that provides transactional integrity with the speed and security that any enterprise will need for mission critical applications. E.g., transactions at a bank, money movement in finance sector, retailer processing of payment card or purchase details, border security and immigration processing, moving data through factories and in and out of ERP systems
MQ enables you to connect applications and services together with valuable qualities-of-service.
Applications can exchange information without tying themselves up – just like email where people communication a-synchronously.
MQ has been doing all this for years – we have 10000+ customers who have built their businesses around it – and rely on it not just every day – but every second.
It helps their businesses be more flexible, more reliable and more secure. Deployments on platforms like System z with its coupling facility helps customers to be robust and recover from failures without interrupting their processing – and we have hundreds if not thousands of partners and skilled practioners to support these deployments – as well as big teams in IBM enhancing the product and delivering major new updates – such as the new IBM MQ V8.
In april 2014 IBM announced our latest major new version of MQ – V8 to be available on all major platforms this quarter. As we have covered – by using messaging solutions like MQ, businesses can keep their applications simple, while delivering data from pretty much any source to any other endpoint, helping the business to streamline, cutting costs and time, and meeting the changing needs of the business.
So although thousands of customers are already current with MQ – what can they expect in the new V8 release?
Well MQ is broadly common across bother distributed and z/OS platforms but there are some distinctions – on distributed there are updates focused on helping customers to scale their workload deployments – supporting larger workloads, more messages, more queues, and doing that without increasing the tasks on the administration and operation team. Security is of course high on everyone’s agenda and there have been big changes there too – both to enhance security and to ensure it is easier to use and manage. And there are some new functions as well – in support of new standards like JMS2.0 – plus exciting news for customers on IBM I – with MQ AMS available on that platform for the first time.
For z/OS it gets the benefit of a lot of the same updates but also some specific new features to really exploit the platform capabilities – helping deployments to scale better, perform better, and with easier administration, boosting reliability and robustness. And of course with z being critical to so many businesses, security again is featured with stronger SHA-2 encryption. Plus as a bonus customers on V8, as well as V7 can now connect MQ clients on other platforms directly to the z/OS MQ without the additional CAF charge – this will help customers choose how to connect and exploit the data movement and business needs far more flexibly.
By consuming APIs to assemble their App, Cars.com… Can focus on their core competence and value add, rather then reinventing common capabilties
Sees Quicker time to market, decreases cost and speeds up their cars.com app development and delivery
Drives innovation, from others, into their app (like, perhaps the notifications from Xtify)
Perhaps the insurance company offers value to their affiliates (which cars.com is now part of) by marketing the cars.com app to their insurance customers
Expands into new customer bases and niches that the bank would normally not reach on their own
Expands their brand and brand loyalty – you think about google when you see their maps appear in apps, perhaps you will think of “the bank” when you see their signature mortgage calculator
And now you have third parties (not necessarily external) innovating with your content in ways you haven’t imagined and you are now monetizing those sources – across a wide array of app, running on a wide array of platforms
The primary configuration file for Liberty Profile is server.xml. It is in this configuration file that updates are made to enable the z/OS Connect function and to configure the behavior of z/OS Connect. The chart above is showing an example of a “HelloWorld” URL coming into z/OS Connect and the configuration that would be in place to support responding to the request:
The <featureManager> section of server.xml is used to tell the instance of Liberty what functional features you wish to be loaded. z/OS Connect is loaded with the zosConnect-1.0 feature. z/OS Connect uses the cross-memory local adapters function to access backend services like CICS and Batch, and to enable that function requires the zosLocalAdapters-1.0 feature.
The next section is what tells z/OS Connect about the HelloWorld service. The serviceName= value is what is matched to the URI. The serviceRef= value is what points to the section of XML that defines how the backend system will be accessed to deliver the service. That section defines the local adapter “register name” and “service name” to be used when the HelloWorld service is requested by a client. The register name is the cross-memory connection to, in this example, a CICS region. The service name is the program back in CICS that will be called.
Without getting too deep into configuration XML, the main point here is that the configuration spells out what services are exposed, and how the backend system is accessed. In this “HelloWorld” example we illustrated the URL, the service definition and the backend local adapter definitions. Those aren’t the only configuration updates needed, but that’s a good start to show the essential elements.
The previous chart showed one configured service. This chart is illustrating the point that you may have multiple configured services. Here we’re showing three configured services – Create, Update and Delete contact information.
Three service definitions are configured in the server.xml … one for each service to be exposed. In addition, the example above is showing that all three are going to make use of the same serviceRef=, which is the local adapter connector to the backend CICS. That means Create, Update and Delete are all hosted in the same CICS region. (You are not limited to a single CICS region; you can configure services in multiple CICS regions if you wish.)
Further, this example is showing dataxform=, which is a pointer to XML (not shown on this chart, but we’ll show it on an upcoming chart) that defines how the JSON data will be converted to the format needed by CICS and the backend program. This illustrates another important function of z/OS Connect – the ability to transform data back and forth.
This chart illustrates the SMF record information to be written for each request. This will produce an SMF 120.11 record, which is different from the traditional WebSphere Application Server z/OS 120.9 record.