An object store is used to store Message Queue administered objects, which encapsulate implementation and configuration information specific to a particular Message Queue provider. An object store can be either a Lightweight Directory Access Protocol (LDAP) directory server or a directory in the local file system.
Although it is possible to instantiate and configure administered objects directly from within a client application’s code, it is generally preferable to have an administrator create and configure these objects and store them in an object store, where client applications can access them using the Java Naming and Directory Interface (JNDI). This allows the client code itself to remain provider-independent.
Although the Administration Console allows you to manage an object store, you cannot use it to create one; the LDAP server or file-system directory that will serve as the object store must already exist ahead of time. You can then add this existing object store to the Administration Console, creating a reference to it that you can use to operate on it from within the Console.
The sample application used in this chapter assumes that the object store is held in a directory named Temp on the C drive. If you do not already have a folder named Temp on your C drive, create one before proceeding with the following exercise. (On non-Windows platforms, you can use the /tmp directory, which should already exist.)
Click on the Object Stores item in the Administration Console window’s navigation pane and choose Add Object Store from the Actions menu.
Alternatively, you can right-click on Object Stores and choose Add Object Store from the pop-up context menu. In either case, the Add Object Store dialog box (Figure 2–11) will appear.
Enter a name for the object store in the Object Store Label field.
This provides a label that identifies the object store in the Administration Console.
For this exercise, type in the name MyObjectStore.
Enter the JNDI attribute values to be used for looking up administered objects:
Select the name of the attribute you wish to specify from the Name pull-down menu.
Type the value of the attribute into the Value field.
Click the Add button to add the specified attribute value.
The property and its value will appear in the property summary pane.
For this exercise, set the java.naming.factory.initial attribute to
and the java.naming.provider.url attribute to
(or file:///tmp on the Solaris or Linux platforms). These are the only attributes you need to set for a file-system object store; see LDAP Server Object Stores for information on the attribute values needed for an LDAP store.
Click OK to add the object store and dismiss the dialog box.
The new object store will appear under Object Stores in the navigation pane, as shown in Figure 2–12. The red X over the object store’s icon indicates that it is not currently connected to the Administration Console.
When you click on the object store in the navigation pane, its contents are listed in the result pane. Since you have not yet added any administered objects to the object store, the Count column shows 0 for both destinations and connection factories.
Once you have added an object store, you can use the Properties command on the Actions menu (or the pop-up context menu) to display an Object Store Properties dialog box, similar to the Add Object Store dialog shown in Figure 2–11, to view or modify any of its properties.
Now that you have added an object store to the Administration Console, you must connect to it in order to add administered objects to it.
Click on the object store’s name in the Administration Console window’s navigation pane and choose Connect to Object Store from the Actions menu.
Alternatively, you can right-click on the object store’s name and choose Connect to Object Store from the pop-up context menu. In either case, the red X will disappear from the object store’s icon, indicating that it is now connected to the Administration Console.