A context object for an administered object is used to look up queues and topics dynamically using automatic destination wrapping, which is described in Using Automatic Destination Wrapping.
Automatic destination wrapping allows applications to bind an administered object in the application server's JNDI tree that represents a WebLogic JNDI context. Applications can then look up this WebLogic JNDI context to look up JMS destinations by their name in the WebLogic JNDI tree. This can simplify the configuration for applications that have a large number of destinations because only one administered object must be configured with the application server.
Use the following elements to define a context object for an administered object:
<adminobject-interface>—Use weblogic.jms.ra.WLDestinationContextInterface.
<adminobject-class>—Use weblogic.jms.ra.WLDestinationContext.
Use the following configuration properties in the <config-property> element:
group—The name of the group to associate with this adminobject definition.
rpContextLocation—Provides information to the resource adapter describing how to look up JMS destinations using the context object for the administered object. You specify this using the following syntax:
connector:<connectorName>/
The macros defined in a groupDefinition may be used for the value of connector in this property value. For example, you can use connector:{connectorName}/ in place of connector:wlDevelopment/ when the value of the macro {connectorName} within a group is wlDevelopment. For more information, see Advanced Method for Configuring Resource Providers.