Package com.sas.metadata.remote

Interface DeployedDataPackage

All Superinterfaces:
CMetadata, MdObjectBase, MdObjectBaseUtil, MdObjectBaseXML, PrimaryType, Remote, Root
All Known Subinterfaces:
AnalyticContext, ArchiveEntry, ArchiveFile, COMConnection, Connection, ContentLocation, DatabaseCatalog, DatabaseSchema, DataSourceName, Device, Directory, Document, Email, File, Memory, OLAPSchema, OpenClientConnection, RelationalSchema, SASCatalog, SASCatalogEntry, SASClientConnection, SASFileRef, SASLibrary, SecuredLibrary, Stream, TCPIPConnection, Text, TextStore
public interface DeployedDataPackage extends PrimaryType
A container of data files (files that contain data) or other Deployed Data Packages. This type has associations with DeployedComponents that can access the package. This type could be a directory, a database catalog or schema or a SAS library.

Database schemas and catalogs should be associated with the DBMS that provides access to those packages.

Attributes of DeployedDataPackage are:

Associations of DeployedDataPackage are:

Usage

To create an instance of this DeployedDataPackage, use the factory create methods.
Example: create a DeployedDataPackage with name "DeployedDataPackage_Object", in repository "AAAAAAAA".
 // create a store to contain your objects for this change. If you do not have an existing object
 // or store to use.  You may obtain the store from another object by using Object.getObjectStore().
 MdFactory factory; //where "factory" is a valid MdFactory instance
 MdObjectStore objectStore = factory.createObjectStore();
 DeployedDataPackage myObject = (DeployedDataPackage) factory.createComplexMetadataObject(objectStore, "DeployedDataPackage_Object", MetadataObjects.DEPLOYEDDATAPACKAGE, "AAAAAAAA");
 myObject.updateMetadataAll();  // Write object to server
 objectStore.dispose();  // dispose of the object store if it is no longer needed

Behavior

  • Attributes and associations for this object can be retrieved by using the methods in MdOMIUtil.
  • When changes are made to the object, either by setting an attribute or adding objects to a particular association, they can be persisted to the metadata server with the updateMetadataAll method.
  • If an object needs to be deleted, the delete method can be used. This will flag the object as being deleted on the client, and will require an update call to persist the change to the server.

Dependencies

This class depends on objects being contained in an MdObjectStore. Object stores should be disposed of when they are no longer needed as this will help clean up memory. Disposing an object store will dispose of all objects contained within that store.

Since:
9.0