 |
|
| SAS Namespace Submodels |
Software Deployment Submodel
The Software Deployment submodel contains the metadata types that are used to describe software, servers, and connection information.
| Metadata Types |
The following metadata types, relevant to the Software Deployment submodel, are classified as Software, Connection, Service, and Other. Click on a metadata type to display its attributes and associations.
| Software Metadata Types |
The SoftwareComponent metadata type represents a type of software, for example, SAS/ACCESS for ORACLE, Version 9.0. The DeployedComponent metadata type describes software that is actually installed. An actual installation of SAS/ACCESS for ORACLE on any machine is a DeployedComponent. An installation of software can have various configurations that are defined to run the software. This submodel contains several subtypes of DeployedComponent that represent different types of configured software.
-
The ConfiguredComponent metadata type represents software that is configured to run. This includes software such as Java components or customizers.
-
The ServiceComponent metadata type represents software that acts as a service.
-
The ServerComponent metadata type is used to represent servers and spawners.
-
The LogicalServer metadata type represents a grouping of homogeneous servers for the purpose of load balancing or pooling. It is important to note that IOM workspace servers will always use the logical server construct even if it is a single server.
-
The ServerContext metadata type groups non-homogeneous servers that all share common resources. ServerContext gives an application context for the grouped servers.
| Connection Metadata Types |
These metadata types contain information about how to communicate with a DeployedComponent. The Connection metadata type is the parent class and has two primary subtypes: OpenClientConnection and SASClientConnection. The SASClientConnection metadata type was created because of specific limitations that SAS software has on connection information, such as the eight-character length limitation on the name used to refer to the server.
TCPIPConnection and COMConnection are subtypes of OpenClientConnection, and each contains attributes that provide protocol-specific connection information.
| Service Metadata Types |
There are two metadata types in this category: ServiceType and NamedService. ServiceType contains descriptive information about the kinds of services that are provided by a DeployedComponent. "DBMS" may be a ServiceType specified for an Oracle or DB2 server. NamedService contains the name used by a naming service, such as the RMI registry, or Active Directory, to refer to a DeployedComponent.
| Other Metadata Types |
The other metadata types in the Software Deployment submodel are Machine, Login, and AuthenticationDomain. The Machine metadata type is used to identify the computer that can run a DeployedComponent. The Login metadata type contains a user ID and password. The AuthenticationDomain metadata type is used to identify which Login objects can be used with which Connection objects. For example, MYNET might be an AuthenticationDomain, and any Login metadata objects associated with that domain can be used with any Connection object associated with that domain.
| Usage |
The metadata types in the Software Deployment submodel are used to define the software that is found in an enterprise and information about how to initialize and access the software. The metadata types are generic in nature since it is impractical to have a metadata type for every software system or every type of connection. In most use cases, these metadata types will have associated Property objects which give more specific information about the deployment of the system or provide additional options that can be used. A prototype will typically be defined for these classes, which represent software that is supported by an application. Many of these prototypes are installed by the SAS Management Console during the initialization of a new repository.
|
|
Copyright © 2011 by SAS Institute Inc., Cary, NC, USA. All rights reserved.