Extending Systems Management Application Programminng Interface for z/VM
Publication Date: 2014-Sep-22
The IP.com Prior Art Database
z/VM currently has a fixed set of APIs (Application Programming Interface) available through a facility called SMAPI (Systems Management API). These provide north-bound APIs into z/VM and allow management products and solutions to interact with z/VM (Query configuration and alter configuration). This article discusses a method for extending and enhancing SMAPI in an automated way, with minimal manual intervention, allowing products and solutions to provide their own set of API extensions.
Page 01 of 4
Extending Systems Management Application Programminng Interface for z /
Disclosed is a method for extending and enhancing SMAPI, allowing products and solutions to provide their own set of API extensions, with minimal user intervention. The method consists of one or more service machines which are created, deployed and managed using existing and standard interfaces such as SMAPI itself and FTP (File Transfer Protocol). These service machines may provide additional functionality, which SMAPI does not provide, and/or replace existing SMAPI functionality.Overview
While SMAPI does provide means for extension, using custom APIs, this process requires significant z/VM skills, and a significant amount of work (write the APIs, alter the SMAPI configuration, etc.). Products or solutions requiring additional or enhanced function would have to either require the user to manually deploy these extensions, or, generate a custom deploy program to do so. Since this deploy program modifies SMAPI, it is dependent on the SMAPI architecture. Vendors may have to modify this deployment program following changes in the SMAPI architecture. The method disclosed hereunder is decoupled from the SMAPI architecture and can be deployed as stand-alone. See figure-1 below.
Page 02 of 4
Figure 1 Schematic view of SMAPI and service machines
Conceptually, the method consists of one or more Service Machines which are created, deployed and configured using existing, standard interfaces such as SMAPI itself and FTP. Because only these interfaces are used, it is possible for the product or solution to deploy these service machines autonomously, without any manual intervention from the user. These Service Machines are CMS (Conversational Monitor System) guests running in the z/VM LPAR (Logical Partition). When IPL-ed (Initial Program Load), the Service Machine runs a compiled REXX (Restructured Extended Executor) script which accepts connections from clients, performs authentication and authorization checks, executes the API call and returns the output to the client. The Service Machine guest has a small amount of storage attached to it which is used to store this main REXX script, the UAF (User Authorization File) which is used for authorization checking, and various REXX scripts which contain the actual implementation of the API calls. If the REXX scripts need to be shipped in compiled form, the attached storage can also be used to store the REXX Runtime Environment libraries.
Communication Protocol Overview
There is a unique protoco...