34
IMS In The Mobile Era William Li – [email protected] IBM – IMS Development April 23, 2015 Phoenix RUG 1

IMS in the Mobile Era - RUG 2015 Phoenix

  • Upload
    ibm-ims

  • View
    56

  • Download
    1

Embed Size (px)

Citation preview

Page 1: IMS in the Mobile Era - RUG 2015 Phoenix

IMS In The Mobile Era

William Li – [email protected]

IBM – IMS Development

April 23, 2015Phoenix RUG

1

Page 2: IMS in the Mobile Era - RUG 2015 Phoenix

� IBM’s statements regarding its plans, directions, and intent are subject to change or

withdrawal without notice at IBM’s sole discretion.

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

� The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract.

� The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

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

2

Please note

Page 3: IMS in the Mobile Era - RUG 2015 Phoenix

CICSIMS

DB2

The New Natural Resource

3

Page 4: IMS in the Mobile Era - RUG 2015 Phoenix

Inadequate integration with back-office systems

Inadequate security

Inadequate master-data management

Inadequate content management

Slow or unpredictable performance

42%

35%

34%

30%

30%

The most significant technical barrierto creating effective customer-facing systems

1

Source: A commissioned study conducted by Forrester Consulting on behalf of IBM, Q1 201391% of CIOs said new

customer client-facing apps

will access the mainframe

Primary challenge: Back-office system integration

4

Page 5: IMS in the Mobile Era - RUG 2015 Phoenix

Cloud-based Services Enterprise

SystemsIntegration

EnterpriseApplications

EnterpriseData

On-Premise Enterprise APIs Enterprise Transaction Processing

IBM WebSphere

Liberty z/OS Connect

5

CICS,IMS

Batch,WAS

• IBM WebSphere Liberty z/OS Connect – Shipped with WAS, CICS, and IMS

• Unifies z/OS connectors – a common solution for mobile, cloud, and web

• Simplified integration – Hide complexity of connecting to z/OS using REST

Cloud APIs

Mobile-Optimized APIs

Systems of Engagement Systems of Record

Consistent enterprise connective for mobile and cloud

5

Page 6: IMS in the Mobile Era - RUG 2015 Phoenix

z/OS Connect

• Combine mobile and cloud for best of both – mobile applications in the cloud

linked to the enterprise is your competitive advantage

• Fast time to market of cloud based applications – combined with the trusted

transactions of traditional mainframe systems

• Securely connect – leverage data from your existing enterprise systems

Bluemix DataPower

Secure connectivity to Systems of Record

6

Page 7: IMS in the Mobile Era - RUG 2015 Phoenix

define, assemble, secure

Enterprise API Management

•Rapidly define APIs – Use the web interface to construct the API contract

•Manage and monitor – Built in analytics provide insight into your API usage

•Develop new revenue streams – Safely make APIs available externally

a branded developer portal analytics and operational insight

7

Page 8: IMS in the Mobile Era - RUG 2015 Phoenix

8

Page 9: IMS in the Mobile Era - RUG 2015 Phoenix

• Describing details on how to invoke an API• Listing and categorizing APIs

9

Page 10: IMS in the Mobile Era - RUG 2015 Phoenix

10

Page 11: IMS in the Mobile Era - RUG 2015 Phoenix

System z Service DeveloperDevelop SOAP or REST services for IMS, CICS, other z apps

Cloud APIs

Others

Cloud-based Services

CICSIMSWAS

API DeveloperDevelop Enterprise APIs from z services

Mobile Developer Use API to access z services

IBM Datapower Appliance(Security & Integration API

Gateway)

Shavon BobJane

Mobile/Cloud/Third-party Application Development- Invokes APIs for accessing SOR (System of Record)

API Management- Consumable by internal and external developers (creation and look up)- Entitlement Management (securing, workload enforcement) - Usage monitoring & Analytics

Service Enablement- Enables invocation of z applications by remote applications using standard protocols (WSDL, REST) - Converts SOAP or JSON into application specific (e.g., COBOL, PL/I) data and invokes applications

Mobile/Cloud Enablement

Enterprise API Development

System z Service Enablement

Enterprise APIs

On-Premise APIs

Enterprise Services

Services

IBM API Management

System z

Mobile Applications

System of Engagement System of Record

End-to-end API accessing System z services

11

Page 12: IMS in the Mobile Era - RUG 2015 Phoenix

z/OSz/OS

CICS TSCICS TS

WorklightWorklight

BlueMix

Systems of Engagement meets System of Record

WebSphereWebSphere

IMSIMS

DB2DB2Secure

Gateway

IBM Integration Bus

IBM Integration Bus

z/O

S

Co

nn

ect

z/O

S

Co

nn

ect

Customer

3rd Party

APIMAPIM

12

Page 13: IMS in the Mobile Era - RUG 2015 Phoenix

TCP/IP

WOLA

WOLA Link Server Task CICS

Programs

Bluemix

IMS

DB2

DLI

zConnectJSON to/from byte[]

(Cobol copybook)

CICS

WOLA directzConnect

JSON to/from byte[]

(C structure)

zConnectJSON to/from byte[]

(PL/I structure)

WOLA

WAS Liberty z/OS

RESTful

RESTful

Data binding

conversion/routing

Mobile/APIM

Mobile/APIM

Java,

Node.js,

JavaScript

CICS

Batch

CICS

Batch

Data binding

conversion/routing

Data binding

conversion/routing

Security / Auditing /

Metering VSAM

IMS Connect OTMA

OTMA

IMS

IMS dependent regions

MPPJMPIFPBMP

IMS

DB2

Liberty z/OS Connect

A service that encapsulate calling z/OS target applications using REST calls. zOSConnect will support JSON payloads for calls from external cloud or mobile-basedclients and will enable the conversion of the payload to the target program'sexpected format. It will also provide the response payload conversion from a bytearray into JSON format before returning the response to the caller.

13

Page 14: IMS in the Mobile Era - RUG 2015 Phoenix

IMS Mobile Feature Pack

� The IMS mobile strategy gives our customers a mobile foundation they can

depend on

� Expand IMS ecosystem via delivery of mobile infrastructure

� Offer an integrated platform for full discovery, modeling, deployment and execution of

transaction assets for mobile consumption

� REST interface with JSON wire protocol

74% of CIOs say mobile solutions are part of their vision for increasing competitiveness

14

Page 15: IMS in the Mobile Era - RUG 2015 Phoenix

Create and publish REST services – IMS Explorer for Development

15

Page 16: IMS in the Mobile Era - RUG 2015 Phoenix

Create and publish REST service – IMS Explorer for Development

Demo

16

Page 17: IMS in the Mobile Era - RUG 2015 Phoenix

Resources

IMS Enterprise Suite

http://www-01.ibm.com/software/data/ims/enterprise-suite/

William Li

[email protected]

17

Page 18: IMS in the Mobile Era - RUG 2015 Phoenix

18

Backup

Page 19: IMS in the Mobile Era - RUG 2015 Phoenix

19

Create and publish REST service

Page 20: IMS in the Mobile Era - RUG 2015 Phoenix

20

IMS Mobile Perspective

Page 21: IMS in the Mobile Era - RUG 2015 Phoenix

21

IMS Gateway Navigator

Page 22: IMS in the Mobile Era - RUG 2015 Phoenix

22

IMS Connection Profile

Page 23: IMS in the Mobile Era - RUG 2015 Phoenix

23

IMS Interaction Properties

Page 24: IMS in the Mobile Era - RUG 2015 Phoenix

24

IMS Transaction Navigator

Page 25: IMS in the Mobile Era - RUG 2015 Phoenix

From the IMS Gateway Navigator view, right click the Services folder and select “Create an IMS mobile transaction service”.

Create REST on mobile server

25

Page 26: IMS in the Mobile Era - RUG 2015 Phoenix

Give the service a name and click browse to select a transaction and the input and output message layouts you want.

26

Create REST on mobile server

Page 27: IMS in the Mobile Era - RUG 2015 Phoenix

27

Create REST on mobile server

Page 28: IMS in the Mobile Era - RUG 2015 Phoenix

Define the interface to the service by selecting the fields to include in the input and output messages (i.e. the mobile applications can only provide values for the included fields). provide any default values for either included or excluded fields. Excluded field default values cannot be overridden by the mobile applications.

28

Create REST on mobile server

Page 29: IMS in the Mobile Era - RUG 2015 Phoenix

On page 3 of the wizard you can type in remarks describing information about the service.

29

Create REST on mobile server

Page 30: IMS in the Mobile Era - RUG 2015 Phoenix

After clicking Finish you will see that the new service has been added to the IMS Gateway Navigator view.

30

Create REST on mobile server

Page 31: IMS in the Mobile Era - RUG 2015 Phoenix

31

Test the REST service

Page 32: IMS in the Mobile Era - RUG 2015 Phoenix

From the “Run a Test Case” window you can double click an input message field to change its value and then click the “Run” button to test.

32

Test the REST service

Page 33: IMS in the Mobile Era - RUG 2015 Phoenix

Inspect the output message payload in the lower panel to ensure that the transaction was invoked and that it returned the expected output message.

33

Test the REST service

Page 34: IMS in the Mobile Era - RUG 2015 Phoenix

Text view, JSON payload.

34

Test the REST service