Object Types Optional Aspects

The TIBCO Enterprise Administrator Agent library supports optional aspects for defining the object type: members, status, and configuration.

To control the definition of an object type, the following interfaces can be added to the interfaces that are used to create object types.

com.tibco.tea.agent.api.WithMembers
com.tibco.tea.agent.api.WithStatus
com.tibco.tea.agent.api.WithConfig

Define an object type with members

An object type can have members or subclasses that the object type contains or refers to. For example, an enterprise might have environments, a machine might have processes, a domain might have applications and so on. Such relationships can be defined using com.tibco.tea.agent.api.WithMembers. TopLevelTeaObject is expected to support this interface.

Define an object type with status

An object type can have a status. For example, a process might be running or stopped. Such object types can be defined using the com.tibco.tea.agent.api.WithStatus.

Define an object type with configuration

An object type can have a configuration. For example, an environment might have virtualization layer configuration or the node might have port configuration. These can be defined using the com.tibco.tea.agent.api.WithConfig.