Skip to end of metadata
Go to start of metadata

Initial Context classes are needed to get a handle to a database connection that is registered with a JNDI lookup service. In DbVisualizer, these context classes are similar to JDBC driver classes in that an Initial Context implementation for a specific environment is required. 

Remember that the appropriate JDBC driver classes must be loaded into the Driver Manager even if the database connection is obtained using JNDI.

To load Initial Context classes into the Driver Manager, simply follow the steps outlined for installing a custom JDBC driver. The difference is that you will load paths containing Initial Context classes instead of JDBC drivers. When you load a path, DbVisualizer locates all Initial Context classes in the path and lists them in the User Specified paths list.

When you create a database connection using a JNDI Lookup driver, the Properties sub tab in the connection's Object View tab will then, in this case, contain the same set of driver properties.

The list of options for JNDI lookup is determined by the constants in the javax.naming.Context class. To change a value, just modify the value of the parameter. The first column in the list indicates whether the property has been modified or not, and so, whether DbVisualizer will pass that parameter and value onto the driver at connect time. 

New parameters can be added using the buttons to the right of the list. Be aware that additional parameters do not necessarily mean that the InitialContext class will do anything with them. 

  • No labels