as400 webservices - the adapter create cloud apps in a couple of days
Upload: harmony-the-1-cloud-application-development-run-time-platform
Post on 26-Jun-2015
4.588 views
DESCRIPTION
Connecting the AS/400 to the cloud, a.k.a. modernization & integration, requires web services. Creating and implementing (consuming) web services is easy, fast and at a low cost using WAS400 and Harmony. This presention demonstrates (1) how to create business process applications in a matter of days and (2) how to integrate with the AS400 (RPG and database). The result is a business services layer, that "sits" on top of your AS/400 [RPG] programs allowing easy integration with Microsoft Windows, the cloud (Google DOCS, maps) and it makes developing new web and mobile radically simple. The Showcase in this presentation is about purchase order processing / inventory management.TRANSCRIPT
WAS400: Web services Adapter AS/400
Fast path to modernization & integrationHow to implement a business services layer on top of the
AS/400
Showcase purchase order processing
Audience: RPG developers and system engineers
This presentation reflects a “build” with an old release ([1:3] of Harmony. A new version will be
released in Q1-2015. The last slide contains references to more recent materials
Harmony Services for IBM i
• Benefits of WAS400: what does it do?• AS400: “5250”/RPG situation (slide 7 onwards)
– “co”-existence of RPG and modern (rules)• Animated (short) demo – using slides– Solution in action (slide 12 onwards)
• How it works (slide 20 onwards)
• Other interesting features (slide 29 onwards)
– Standard Harmony features• WAS400 Configuration (slide 35 onwards)
In this presentation
• “Opens” up the AS/400 to other systems• Simple 3 step approach to connect your AS400 to the
internet/cloud • Integrate with Windows, unix, open source
• Easy web services generation• Turns tables into web services• Turns RPG *pgms into “headless” programs with a web
service interface(Removing/ignoring the [5250] UI )
• Replicates/mirrors AS400 transaction data • To support your new process /new applications• To run your BI / data warehouse
• Easy, fast, reliable “must-do” modernization step•Web services are de-facto standard for any app
Why WAS400 ?
1. monitoring servicesa.Specify which modifications to the database
(tables) are to be replicated
2. mapping servicesa.Map AS400 data structures to web services
i. Table (file) structuresii. Program parameters
b.Map web services to AS400 data structuresi. Table (file) structuresii. Program parameters
3. (out of the box) ESB support
WAS400 features
Showcase WAS400
• Goal: – Implement a smart, efficient and easy to maintain
solution for purchase order processing• Implementation
– Create web services for AS/400 sales order entry – (new) Purchasing solution
• using business rules and workflow
– Warehousing: goods received modern UI• Benefits
– Fast , implementation in < 2weeks)– Smallest possible learning curve– Low cost
• For business case linked on last slide– The new AS400 - a modernization scenario for the IBM i (powerpoint)
AS/400 “OLD” AND “NEW”Sales orders & purchase order systems (RPG/5250)
Purchasing(inlcl warehousing)
Sales Order Entry
(Old) System overview AS400
• Sales Order Entry– Records article, quantity and
delivery date• Purchasing
– If stock levels are too low• Raises a PO (Purchase Order)
which has to be signed & sent
– Supports the reception of goods• Implemented at multiple
warehouses
– Supported by 5250
Sales Order Entry – main screen
The RPG “maintain sales order” system records the sales order1
1
Sales Order Entry - orders
Maintain / create sales order lines:
product
stock quantity
shipment date
1
1
2
3
1
2
3
New situation
• Business goals / requirements: – Implement a new solution to support purchase order
processing• Flexible rules (easy to modify when business changes )• Mobile support
– Support warehousing / goods reception• Transporters data must be captured• Replace 5250 workstations• Mobile support
• Technical Implementation– Create web services for AS/400 sales order entry – Purchasing & warehousing solutions
• using business rules and workflow
Sales Order Entry
“co”-existence old & new
Harmony purchasing business rules
WAS400 web services for AS/400
Modern UI-browser AND mobile
Business logic & business rules-easy to maintain
Web services
1
2
3“Headless”
Copy of *pgm
Sales Order Entry WAS400: monitors database & applies changes
Business services layer (all Logic)
The solution in actionRPG program started; user enters data, order files + stock are updated0
0
Sales Order Entry WAS400: monitors database & applies changes
HARMONY Business services layer (all Logic)
The solution in actionIf WAS400 detects a database change it sends the change to Harmony1
1
Sales Order Entry WAS400: monitors database & applies changes
HARMONY Business services layer (all Logic)
Issue an PO?
The solution in actionHarmony receives the transaction – calculates stock level and issues a PO
(Purchase Order) when stock level falls below threshold
2
2
Sales Order Entry WAS400: monitors database & applies changes
Business services layer (all Logic_
Issue an PO?
PO >
10.000?
The solution in action PO value more than 10,000 ?
-> approval required
3
3
Sales Order Entry WAS400: monitors database & applies changes
Business services layer (all Logic)
Issue an PO?
PO >
10.000?
The solution in action: warehousing Manually start “Receive
goods” process
4
Sales Order Entry WAS400: monitors database & applies changes
Business services layer (all Logic_
all goods received?
Issue an PO?
PO >
10.000?
The solution in action Rules checks if
“open” PO quantity
5
5
Sales Order Entry WAS400: monitors database & applies changes
Business services layer (all Logic)
all goods received?
Issue an PO?
PO >
10.000?
The solution in action Harmony submits
goods received to WAS
WAS400 sends data to
AS/400
6
7
6
7
WAS400 & HARMONYHow it works: new purchasing with AS400 integration
WAS400 sends data to HarmonySales order is put on Harmony queue1
1
WAS400: monitors database changes
WAS400 sends data to HarmonySales order is put on Harmony queue
The content of the queue
1
1
2
2
WAS400: monitors database changes
WAS400 sends data to HarmonySales order is put on Harmony queue
The content of the queue
The details of case [3nyte]
1
1
2
3
3
2
WAS400: monitors database changes
Harmony “sensors” changesHarmony “picks” the sales order from the queue
starts the purchase order [task]
(simultaneously) starts Approve purchase order [task]
1
3
2
1
3
2
Workflow and decision support
Approval = YES next step is scheduled1
Harmony’s decision support turns business
logic and business rules into information
1
Workflow is started
2 When Approval = NO Decision support
changes immediately – showing the
steps that will be schedule next
2
Next in workflow: supplier must confirms
Suppliers have access to their own cases or queues
Confirms delivery quantity, date and time
1
2
1
2
Warehouse: receives stock
When goods received is submitted
WAS400 will update AS400 stock by 81
1
2
2
1
WAS400: commits changes to database
OTHER INTERESTING FEATURESWorkflow, History, Google DOCS, ESB, cloud verus enterprise
Workflow history
• Process history: – Overview of all process steps is
maintained by Harmony– Per step [data] changes are
shown– Outputs (like email sent) can be
seen by “hovering over” with your mouse)
Case history
• Data history: – All data that is created / updated
by the business process is “logged”– Distinction is made between
Reference data and process data
Harmony replicates to Google DOCS
• Automatic update/synchronization: – All data can be saved in spreadsheets– Use pivot tables/reports
Harmony is the “single source of truth”, maintaining data integrity between all systems
WAS400 uses ESB
• Why ESB ?• ESB is optional, but recommended, since this part of
the SOA model. ESB offers:• application de-coupling• routing• protocol and data conversion
Deployment options1
2
1
2
• Deployment options: Implement your new process in the cloudImplement within your firewall. Share data using Google DOCS (spreadsheets, documents)
WAS400 SETUP & OPERATIONImplementation aspects
What must be done
• Goal I: to invoke the Purchasing processo How: when a sales order is created
• Goal II: support “goods received” • Create new application + process (rules)
• Using Harmony
• Commit received goods to AS400 database• Using WAS400
• For business case see• The new AS400 - a modernization scenario for the IBM i
(powerpoint)
1) Map AS400 data structures to web servicesTable (file) structure mapped to webservice(optional) Program parameters
2) Map web services to AS400 data structuresCase data to RPG program parameters(optional) Table (file) structures
3) Configure HarmonyCreate and map “data capture sensor” and process
4) Configure WAS400 monitoring servicesThe database updates (tables) are to be monitored
• Implement network infrastructure• Cloud or private enterprise network
How this is done
Documentation: data model & functions
11
1) Create web service / map order
• Mapping is stored in Google spreadsheets
• Map AS400 [order_details] to business terms1. Article ID
2. Quantity sold
3. Delivery date
• All other data is stored in Harmony
1
1
2) Link webservice to Harmony
3) Map goods received• The Goods received will be mapped
to an RPG program
• Case data is mapped to variables1. Article ID
2. Received quantity
3. Delivery date
4. Warehouse ID
4. Monitoring the AS/400
Order_details file is updated when a sales order is created/changed1
1
WAS pre-requisites AS/400
• ILE RPG• Java 1.5• RPG Open Access• SQL
For more information
• Visit– www.liquidsequence.com
• Release overview – (all new features)
• Contact us– http://liquidsequence.com/Contact.html – Business process flowchart– https://www.lucidchart.com/documents/view/48d3-c748-50c6fb88-ab71-3f
b70a7cdee7
– AS400 website info (including architecture diagrams)– http://liquidsequence.com/AS400-webservices-adapter.html
– Business case presentation (management)– The new AS400 - a modernization scenario for the IBM I– Pricing– http://liquidsequence.com/Pricing.html