17
IMS as a client to new systems Dusty Rivers GT Software March 11, 2014 Session 14778

IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

  • Upload
    jefpear

  • View
    29

  • Download
    3

Embed Size (px)

DESCRIPTION

IMS as a Client to New Systems IMS can participate in a variety of the new systems. However, more and more business needs are requiring that IMS be the client to new systems. We will show how to enable existing IMS online and batch programs to easily invoke services residing on other platforms or in the cloud.

Citation preview

Page 1: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

IMS as a client to new systems

Dusty Rivers

GT Software

March 11, 2014

Session 14778

Page 2: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

Why IMS as a client?

Page 3: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

MobileBanking, Agents

WebStock trading,

Self-service, Portals

Packaged ApplicationsCRM, SAP, Oracle, Billing

Mainframe integration challenges

IMS

Page 4: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

• Mainframe applications to/from the cloud

IMS as a client

• IMS Applications can be called by mobile or cloud

• IMS Applications calling mobile or cloud applications

• IMS Applications calling in native language (COBOL, PL/1)

• IMS Application does not worry about XML/SOAP

• IMS Application can be orchestrated

Page 5: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

• New Mainframe applications leveraging standards

Use standards

• New services can leverage industry

standards (IFX, SWIFT, ACORD, etc.)

• Applications can use company specified

standards and mappings (XSD’s, WSDL)

• Services can easily be mapped in Ivory®

Studio that will handle difficult data types.

Page 6: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

IMS applications calling other distributed apps

Must not require many products or installs

Must use existing resources

Must not be intrusiveor cause changes

Must beeasy to call

Page 7: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

IMS applications calling in native language (COBOL,PL/1)

• No new COBOL PL/1 XML Coding

• No knowledge of SOAP or XML required

• Communication in native language

• Must be easy to create interface from IMS

• Must be Secure (SSL,AT-TLS, WS-*…..)

IMS applications in native language

Page 8: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

Mainframe applications can be orchestrated

Must be able to import WSDL from external

systems

Must convert WSDL to

COBOL/PL/l

Multiple distributed

systems may be required

•Must do it quickly and easily

Page 9: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

Schema, WSDL & more

Page 10: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

IMS Application

JAVA App

.NET APP

IMS talking to distributed apps

Page 11: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

IMS Application

JAVA App

.NET APP

IMS talking to distributed apps

• COBOL/PL/I• Data Types• XML?• SOAP?

WSDL

WSDL

Copybooks

JAVAData Types

C##Data Types

Page 12: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

• Imports WSDL from distributed service

• No knowledge of SOAP or XML required

• Generates the required COBOL/PL/I Artifacts

• Creates a project to handle delivery and transformation

• Generates a sample routine to guide the user

• No other software required

• Minutes instead of days

Ivory callable service wizard

WSDL

SOAP XML

COBOL/

PL/I EASY

Delivery Transform

Sample

routineSoftware

Page 13: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

• New applications developed at the speed of business

Do it Quickly

• Mainframe based services developed in minutes

• Mainframe based services developed as new business needs

• Mainframe based services in easy drag and drop studio

• Mainframe based services immediately available

• No new Mainframe application code is generated

Page 14: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

• No coding or code generated

• Rapid iteration gets the job done

• One click deployment

• Deployed to Mainframe (CICS, Started task, z/Linux) or off-platform(Windows or Linux)

• Leverages z/Linux and specialty engines to slash costs

At the speed of the customer

Page 15: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014
Page 16: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

• IMS can easily be used as a client

• IMS applications can interface with new applications with knowing SOAP or XML

• No new software needed

• IMS can rapidly call distributed systems

Summary

Page 17: IMS as a Client to New Systems - IMS Phoenix UG - June 19th, 2014

[email protected]

1 (800) 765-4348

www.gtsoftware.com

Q&A