Configuring subcontexts
You can use the verbs CHANGE, DEFINE, DISPLAY and DELETE to configure directory namespace subcontexts.
About this task
The use of these verbs is described in the following table.
| Command syntax | Description |
|---|---|
| DEFINE CTX(ctxName) | Attempts to create a child subcontext of the current context, having the name ctxName. Fails if there is a security violation, if the subcontext already exists, or if the name supplied is not valid. |
| DISPLAY CTX | Displays the contents of the current context. Administered objects are annotated with a, subcontexts with [D]. The Java type of each object is also displayed. |
| DELETE CTX(ctxName) | Attempts to delete the current context's child context having the name ctxName. Fails if the context is not found, is non-empty, or if there is a security violation. |
| CHANGE CTX(ctxName) | Alters the current context, so that it now refers to the child context having the name ctxName. One of two special values of ctxName can be supplied:
Fails if the specified context does not exist, or if there is a security violation. |
The names of JMS objects that are stored in an LDAP environment must comply with LDAP naming conventions. One of these conventions is that object and context names must include a prefix, such as cn= (common name), or ou= (organizational unit). The administration tool simplifies the use of LDAP service providers by allowing you to refer to object and context names without a prefix. If you do not supply a prefix, the tool automatically adds a default prefix to the name you supply. For LDAP, this is cn=. If required, you can change the default prefix by setting the NAME_PREFIX property in the configuration file. For more information, see Configuring the JMS administration tool.