Tasks
Naming for resources
When naming resources, associate the resource to both the app using it and the physical resource to which it refers. As an example for our discussion, we use a data source, but the concept holds also for other types of resources such as messaging queue. Remember, if the company already has a naming convention for other environments (non-WebSphere) in place, it is probably a good idea to use the same naming convention in WebSphere.
Assume that we have a database called ORDER that holds orders placed by the customers. The obvious name of the data source would be Order and its JNDI name jdbc/Order.
If the ORDER database is used only by a single app, the app name can also be included to further explain the purpose of the resource. The data source would then be called Order_OrderApplication and its JNDI name jdbc/Order_OrderApplication.
Because the Integrated Solutions Console sorts resources by name, we might want to include the name of the app first in the resource, such as in OrderApplication_Order. This gives we the possibility to sort the resources according to the app using them.
To group and sort resources in the Integrated Solutions Console, we can also use the Category field, which is available for all resources in the Integrated Solutions Console. In this text field, we can enter, for example, a keyword and then sort the resource on the Category column. So, instead of including the name of the app in the resource name, we enter the app name in the Category field instead. If we have several different database vendors, we might also want to include the name of the database vendor for further explanation. The Category field is a good place to do that.