If you are trying to connect to D3 to consume Web Services, you need to attend this session! It covers all aspects of the D3 Toolkit. You will learn the components and how to create MV Web Servers and MVSP Servers as well as SOAP or REST BASED services.

1. 1
D3 MVS Toolkit
Dorien Michael Gardner, Solution Engineer

2. 2
Abstract
 If you are trying to connect to D3 to consume Web Services, you need to attend this
session! It covers all aspects of the D3 Toolkit. You will learn the components and how to
create MV Web Servers and MVSP Servers as well as SOAP or REST BASED services.
Many questions you may have are answered: How do I use a Basic Subroutine or an AQL
statement that I want to execute from my Web Application? How would I manage the Life
Cycle of my Web Services and Promote from one stage of release to the next or deploy to
a customer?
©2015 Rocket Software, Inc. All Rights Reserved.

3. 3
Agenda
 What is the MVS Toolkit and why do I care?
 Architecture
 The Toolkit Interface
 Creating Web Services
 Testing Web Services
 Promoting Web Services (Live Cycle Management)
 Resources
©2015 Rocket Software, Inc. All Rights Reserved.

4. 4
What is the MVS Toolkit
Enables creation and management of Web Services
Supports both REST and SOAP services
Wraps D3/mvBase Subroutines or AQL statements
Provides in-tool testing of Web Services
Security
• ACL based Users and Groups
• Handles (GET, PUT, POST, DELETE)
©2015 Rocket Software, Inc. All Rights Reserved.

5. 5
Why should I care?
 Modernize and futureproof your application
 Retain the robust and mature business logic
 Leverage almost any modern programming language and development
environment
 Re-use Web Services for Web Application Deployment and Mobile
 Have access to plentiful development resources
 Attract and retain new talent
 Make more SALES!!

6. 6
Preparing the BASIC Programs
Modularize as subroutines
• Remove all statements that have user interaction
 CRT, INPUT, PRINT, IN, HEADING, FOOTING, PAGE, PRINTER
 Make sure SUB arguments have a RETURN parameter
 Programs MUST be FLASH COMPILED and CATALOGED

7. 7
SOAP vs REST
• Simple Object Access Protocol
 Only uses XML which tends to be overly verbose
 Requires SOAP Envelope and brings its own protocol
 Focuses on exposing pieces of Application Logic, not data as services
 Cannot cache READS
• Representational State Transfer
 True Web Service based on standard HTTP
 Much simpler to use
 Handles multiple formats
 JSON is usually better for data and parses faster
 Better performance and scalability
 READS can be cached

8. 8
Integration – RESTful or SOAP Web Services
O
JSON Data
MVS
Server
XML Data
Rest Rest
SOAP
MVS
ToolKit
Port 9000
Port 3410

9. 9
Nuts and Bolts of MVS Toolkit

10. 10
Additional Resources
 Where you can get further information
 The MVS Toolkit installation provides documentation and a tutorial that
leverages the MVDemo Account
 http://www.rocketsoftware.com/products/rocket-mvs-toolkit
 D3 sample code: https://github.com/RocketSoftware that leverages the Web
Services in the ACME Account discussed in the session
©2015 Rocket Software, Inc. All Rights Reserved.

11. 11
Next Steps
 Install MVSP and the MVS Toolkit
 Review sample (not production code) on GitHub/RocketSoftware
 Create a small prototype project
• Either create some new Basic programs as Subroutines or remove user I/O
 Create Mobile Application with Rocket Mobile for MultiValue
 Pick a development language to call the Web Services
©2015 Rocket Software, Inc. All Rights Reserved.
.Net (C#, VB) ASP.NET Java
PHP JavaScript, HTML
Angular.js Python

12. 12
Summary
MVS Toolkit is easy to use
• Create REST or SOAP based Web Services
• Wrap Subroutines or AQL Statements
Provides robust security
Enables ease of Life Cycle Management/Promotion
Samples to get you started
©2015 Rocket Software, Inc. All Rights Reserved.

13. 13
Disclaimer
THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED
IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
IN ADDITION, THIS INFORMATION IS BASED ON ROCKET SOFTWARE’S CURRENT PRODUCT PLANS AND STRATEGY,
WHICH ARE SUBJECT TO CHANGE BY ROCKET SOFTWAREWITHOUT NOTICE.
ROCKET SOFTWARE SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR
OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:
• CREATING ANY WARRANTY OR REPRESENTATION FROM ROCKET SOFTWARE(OR ITS AFFILIATES OR ITS OR
THEIR SUPPLIERS AND/OR LICENSORS); OR
• ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF
ROCKET SOFTWARE.
©2015 Rocket Software, Inc. All Rights Reserved.

14. 14
Trademarks and Acknowledgements
The trademarks and service marks identified in the following list are the exclusive properties of Rocket Software,
Inc. and its subsidiaries (collectively, “Rocket Software”). These marks are registered with the U.S. Patent and
Trademark Office, and may be registered or pending registration in other countries. Not all trademarks owned by
Rocket Software are listed. The absence of a mark from this page neither constitutes a waiver of any intellectual
property rights that Rocket Software has established in its marks nor means that Rocket Software is not owner of
any such marks.
Aldon, CorVu, Dynamic Connect, D3, FlashConnect, Pick, mvBase, MvEnterprise, NetCure,
Rocket, SystemBuilder, U2, U2 Web Development Environment, UniData, UniVerse, and
wIntegrate
Other company, product, and service names mentioned herein may be trademarks or service marks of
others.
©2015 Rocket Software, Inc. All Rights Reserved.

15. 15