Contexts

A context is a lightweight, immutable object that is used to retrieve a specific administration interface instance. You create a connection to the Unwired Server when you invoke an API (such as ping) on a supported interface (such as SUPServer), but not when context objects (such as AgentContext or ServerContext) are initialized. There is no need to maintain the states of contexts because state changes are not supported.

The administration client API includes these contexts:
Context Description
AgentContext Optional. Connects to the Unified Agent that acts as a proxy and manages the connection to the Unwired Server instance identified in the ServerContext.
DefaultAdminContext The super class of other concrete context classes.
AdminContext The AdminContext is an interface that all context classes implement.
ServerContext Required to connect to the Unwired Server instance. If you don't specify an AgentContext, the ServerContext creates one for you using default values. See Connecting to an Unwired Server Instance. Use this context to retrieve the ClusterContext .
ClusterContext Required to manage a specific cluster. Use this context to retrieve the DomainContext.
DomainContext Required to manage a specific domain. Use this context to retrieve the PackageContext
PackageContext Required to deploy and manage a package. Use this context to retrieve the MBOContext
MBOContext Required to manage a mobile business object. Use this context to retrieve the OperationContext
OperationContext Required to manage an operation.
SecurityContext Required to manage the security for the platform

For details on these classes, and the methods that implement them, see the Javadocs for com.sybase.sup.admin.client.

Related tasks
Connecting to an Unwired Server Instance