The sps-compSDK.jar contains the N1 SPS public Java API
Install the sps-compSDK.jar file on your development system, not on your N1 SPS Master Server. Once you place the sps-compSDK.jar file where you want, be sure to modify the classpath for your Java tools to find the file.
The sps-compSDK.jar file contains the following Java classes for creating plug-ins. For detailed explanations of the classes and interfaces in these packages, see Sun N1 Service Provisioning System 5.2 JavaDoc.
Includes classes and interfaces to execute CLI commands and query information from the Master Server
Includes classes and interfaces to identify the version number, visibility, and ID of N1 SPS objects
Includes three interfaces to group related objects, such as components and plans, in categories
Includes interfaces and classes for defining component information
Includes interfaces and classes for defining provisioning comparisons
Includes interfaces and classes for running plans and native OS commands
Includes interfaces for defining N1 SPS folders
Includes interfaces and classes for defining host criteria, including host sets, host IDs, host searches, applications running on specific hosts, and upgrade activities for specific hosts.
Includes interfaces for gathering information about components that are installed on target hosts
Includes interfaces and classes for running N1 SPS plans
Includes interfaces for defining plug-ins and enabling other users to browse these plug-in in the browser interface
Includes an interface for defining a resource
Includes interfaces and classes that you can use to define criteria and rules for specific actions
Includes interfaces and classes that you can use to set user and group permissions, IDs, and variables
Includes interfaces, classes, and exceptions that you can use to perform basic network connectivity validation, through ping and traceroute
Includes interfaces for defining lists and sets
Includes interfaces, classes, and exceptions for enumerations and enumerations types
Includes one interface that you can use to identify the source of variable settings