VMx as they say in short is available for purchase to licensed clients. It provided distributed access to Vision plus modules,
What is the need of VMx?
Complex enterprise environments
–Emphasis on CRM(Customer Relationship Management)
–Many interactive systems
–Mainframe vs. IVR / VRU, online banking, call center, etc.
–Need real-time access to card system data / functions
VisionPLUS <8.17 = legacy architecture
–File & screen model (human<->system paradigm)
–Functions & data tied directly to presentation
–Suitable for 3270 (green-screen) model
–Difficult to interact with system other than online
–Requires invasive interface code
–Interface code requires regular updates / retrofits
So it gave rise to birth of new definitions:
SBA = Service Based Architecture:
Foundation technology for future VisionPLUS enhancements (8.17 and beyond)
SDM = Service Delivery Manager (part of SBA):
Broker for message routing between service consumers and providers
VMx = VisionPLUS messaging framework:
Expands services concept for full systems integration
SBA changes the real-time model
–Separates data / function from presentation (online)
–Defines business ‘services’ to get data or perform functions
–Isolates applications & data from external invasion
–Enables re-use of services
–By humans (online)
–By other host-based systems (CRM, loans, deposits, etc.)
èVMx goes beyond mainframe
–Communicates with other platforms
–Uses services defined under SBA
SBA is a concept, implemented in VisionPLUS as
SDM / “Service Delivery Manager”
SDM developed in 2004
–Part of VisionPLUS 8.17 release
–Added to common modules in SSC
–Includes
–Service Delivery Manager (SDM)
–Services repository (SMSD)
SBA converts systems into service providers
e.g., VisionPLUS applications
SDM directs service messages
–Consumers request services
–Providers “own” services and respond to requests
SDM works within host environment
–Among VisionPLUS modules
–Between VisionPLUS and other mainframe applications
VMx routes messages among environments
–Works through SDM for VisionPLUS services
So we reach below shown architecture of VMx:
VMX
Supports multiple protocols
Promotes platform independence
Makes integration truly seamless
Interprets messages between systems
Accesses any VisionPLUS data*
Builds its own metadata
Encapsulates VisionPLUS modules
to be continued…
Learn Payment Card 