System and method for performing lookups across namespace domains using universal resource locators

BACKGROUND

[0001] Naming services and directory services provide a way of identifying and associating names with data. Similarly, naming and directory services may also be used for referencing data and data locations using more easily comprehendible names. For example, NIS and NIS+ are naming services developed by Sun Microsystems for allowing users to access files and applications on any NIS host using a single login name and password. DNS, an Internet naming service, associates people-friendly names with computer network addresses. Additional naming and/or directory services include LDAP (Lightweight Directory Access Protocol), NDS (Novell Directory Services), and COS (Common Object Services). While normally having similar basic functionality, each naming or directory service may specify its own protocols, syntax, nomenclature, naming conventions, etc. When a naming service is implemented in accordance with such specifications, the implementation is often referred to as a namespace. For example, a person using a web browser on a personal computer to access a web page via a friendly DNS name (i.e. www.widgetcompany.com), is considered to be utilizing the DNS namespace.

[0002] Application programming interfaces (“APIs”) such as the Java Naming and Directory Interface (“JNDI”) provide an interface for communication between namespaces. For example, where namespace A and namespace B have been implemented in accordance with JNDI, a request for data from namespace B by a host in namespace A may be satisfied without requiring the host to be configured as a node of namespace B. Likewise, a request for data from namespace A by a host in namespace B may be satisfied without requiring the host to be configured as a node of namespace A. However, inter-namespace data exchange APIs such as JNDI require that a request for data from a foreign namespace by a host in a local namespace include specific location/naming information. Solutions have been offered that require special mechanisms within a naming service itself to create, recognize, and traverse federated junctions between namespaces, however such solutions require participation by the naming service and are therefore limited to naming services that implement identical federation schemes.

SUMMARY OF THE INVENTION

[0003] A system and method for performing a lookup in a second namespace, the lookup being performed from a first namespace, whereby a component performing the lookup is not required to be configured for performing a lookup in the second namespace, the system and method further comprising: parsing a first lookup request for a URL tag, the first lookup request for an object located in the second namespace, the lookup request including a symbolic name corresponding to a target location in the second namespace, the URL tag corresponding to a URL context; searching the URL context for a provider URL corresponding to the symbolic name; and creating a second lookup request, the second lookup comprising the provider URL and the object's name.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004]FIG. 1 shows the flow of an exemplary lookup request across namespaces.

[0005]FIG. 2 is a continuation of FIG. 1 and shows the flow of an exemplary lookup request across namespaces.

[0006]FIG. 3 shows an exemplary system for performing a lookup request across namespaces.

[0007]FIG. 4 shows an alternative exemplary system for performing a lookup request across namespaces.

DETAILED EMBODIMENT

[0008] In an exemplary embodiment, the invention is used in conjunction with naming services that support namespace lookups via universal resource locators (URLs) and that include a mechanism for delegating namespace requests to a third party provider. For purposes of explanation and example, the embodiments of the invention are described in conjunction with the JNDI SPI/API to satisfy these requirements. It is understood that the invention may be implemented in conjunction with any namespace API/SPI or similar mechanism known to one of ordinary skill in the art without exceeding the scope of this disclosure. While JNDI itself describes the use of URLs in lookup names, this usage incorporates explicit network location information in the URL itself. An embodiment of the invention uses only symbolic names in a federation URL that is mapped locally within the local namespace to the actual network location information, to achieve namespace federation. This provides for the insulation of applications from namespace reconfiguration and changes to topography by prescribing a method to map the application's lookup name to the actual lookup name. Moreover, the an embodiment of the invention advantageously allows programming model neutrality by prescribing a method to map the facilities of a particular naming system to the underlying naming interface (JNDI, for example) without requiring an additional API set that is separate and distinct from the underlying naming interface API set. This provides for federation without the need for disparate namespaces to explicitly participate in a federation scheme.

[0009] JNDI provides a NamingManager that manages naming context creation. Naming contexts are the programming implements used to perform namespace operations, such as lookup and bind. Actual naming contexts are produced by context factories, which are registered with the NamingManager. As prescribed by JNDI, there are both regular and URL (universal resource locator) contexts and context factories. The JNDI NamingManager, using a context factory registered specifically for the purpose of creating regular naming contexts, creates regular naming contexts. Instantiating a new InitialContext object creates a regular naming context in the Java programming language. All JNDI contexts must support URL composite name syntax. This syntax is of the form:

[0010] URL_TAG:<location-information>/<JNDI-name>

[0011] “URL_TAG” identifies the type of URL context and “location-information” identifies the namespace location of the object (i.e. “JNDI-name”) bound in the namespace. A JNDI context is required to process a URL composite name by stripping off the “URL_TAG” from the composite name and then requesting a new naming context from the JNDI directory manager that supports the specified “URL_TAG”. The returned naming context is known as a “URL naming context”. The naming context request in process must be forwarded to the newly created URL naming context.

[0012] The JNDI NamingManager, using a URL context factory registered specifically for a particular “URL_TAG”, creates URL naming contexts that correspond to a specified “URL_TAG”. This is accomplished through an interaction between a naming context and the JNDI NamingManager, as described in the preceding paragraph.

[0013] The J2EE architecture defines a particular URL context factory and context that use the URL_TAG name of “java”. The java namespace is defined as a local, in-memory name space for use by a J2EE component. Names in this namespace are unique with respect to a particular component: each of two components can independently use the same unique name within their java namespace; each component's use of the name need not correspond to the same namespace binding.

[0014] The J2EE architecture specifies that components use local, composite lookup names of the form:

[0015] java:comp/env/<JNDI name>

[0016] The J2EE architecture specifically requires an administrative action during component deployment to map the component's local lookup name to an actual lookup name. This mapping information is specific to the environment in which the component is deployed. Furthermore, this mapping information is retained as part of the component's configuration data. When a J2EE server loads a component, this configuration information is used to construct the local, in-memory java namespace.

[0017] An embodiment of the invention introduces a specific URL context factory and context for use in achieving namespace federation. In the preferred embodiment, the chosen URL_TAG is “df”. Each namespace to be bound together in a federation has a name context bound to the namespace root context by the name “df”. Within the “df” naming context are bound linkages to other namespaces. Each such binding contains the necessary “provider url” information necessary to establish a regular naming context into another namespace. The java property ‘java.naming.provider.url” is the architectured mechanism by which one identifies to the JNDI NamingManager the location of the target namespace, when creating a regular naming context. For use by applications following the J2EE architecture, provider URLs are typically for the iiop protocol, and take either the form “corbaloc:iiop:ip-name:port” or the form “iiop://ip-name:port” which identifies the iiop (CORBA) protocol for connecting to the namespace located at the Internet address and port number referred to by ip-name:port.

[0018]FIGS. 1 and 2 collectively describe the flow of an exemplary JNDI Lookup across domains. Lookups are implemented using a URL syntax that designates a component namespace (i.e. Java:) to be performed. The component namespace reference is configured using a URL that designates a federated lookup and the local namespace includes URL information referencing the target namespace. Referring now to FIGS. 1 and 2. A component (not shown) in domain A requests (1.1) a new initial context from the JNDI Naming manager <b>10</b>. The JNDI NamingManager <b>10</b> drives (1.2) a registered JNDI context factory <b>12</b> to create (1.3) a regular naming context <b>14</b>. The regular naming context <b>14</b> is returned to the component. The component issues (2.1) a lookup request for “java:comp/env/ejb/myEJB B” to the regular naming context <b>14</b>. The regular naming context <b>14</b> parses off URL TAG “java:” and drives (2.2) the javaURLContextFactory <b>16</b>. In general however, the regular naming context does not drive the javaURLContextFactory directly, but rather goes through the JNDI NamingManager <b>10</b> to select the URL context factory that corresponds to the specified URL_TAG:. The javaURLContextFactory <b>16</b> creates and returns (2.3) a javaURLContext <b>18</b>. The regular naming context <b>14</b> forwards (2.4) the lookup request to the javaURLContext <b>18</b>.

[0019] The javaURLContext <b>18</b> locates and reads (2.5) “comp/env/ejb/myEJB_B” from the java namespace <b>22</b> belonging to current component. The returned data is another JNDI lookup name “df://domainB/EJB_B”, which the javaURLContext <b>18</b> uses recursively to continue the lookup.

[0020] The javaURLContext <b>18</b> (as with all contexts) parses off URL TAG “df:” and drives (2.6) the dfURLContextFactory <b>20</b> to create a corresponding URL context. As stated previously, a naming context does not drive a URLContextFactory directly, but rather goes through the JNDI NamingManager <b>10</b> to select the URLContextFactory that corresponds to the specified URL_TAG:. The dfURLContextFactory <b>20</b> creates and returns (2.7) a dfURLContext <b>24</b>.

[0021] The javaURLContext <b>18</b> forwards (2.8) the lookup request to the dfURLContext <b>24</b>. The dfURLContext locates and reads (2.9) the entry “df/domainB” <b>32</b> from domain A's name space <b>25</b>. The returned data <b>32</b> is a provider URL to the target domain's namespace <b>35</b>, which is used to create a regular context for that namespace.

[0022] The dfURLContext <b>24</b> creates a Java Properties object (as per JNDI specification) to configure a new InitialContext. The dfURLContext <b>24</b> sets the provider URL value for this new InitialContext using the provider URL for domain B <b>35</b>, which was configured in the namespace of Domain A <b>25</b>. The dfURLContext <b>24</b> creates an initial context by issuing a request for a new initial context to the JNDI NamingManager <b>10</b>. The JNDI NamingManager <b>10</b> drives the registered JNDI context factory to create the new context and the regular naming context <b>34</b> for the domain B namespace returned. The dfURLContext <b>24</b> strips the JNDI lookup name from the URL composite name following the &lt;location-information&gt; portion of the name yielding the lookup name “EJB_B”. The dfURLContext <b>24</b> forwards (6.1) the lookup request to the domain B regular JNDI context <b>34</b>. The regular JNDI context (for domain B) <b>34</b> performs a lookup (6.2) in domain B's namespace <b>35</b> and returns the lookup result.

[0023]FIG. 3 shows an exemplary system for implementing a lookup request across namespaces. Namespace X at <b>60</b> is located at x.x.x.x and includes URL context factory df at <b>62</b>, where df includes references to a logical set of namespaces to be federated. The URL context factory <b>62</b> creates context df <b>64</b> which includes entry <b>66</b> for targeting namespace Y <b>68</b> at location y.y.y.y. The entry <b>66</b> comprises the following:

[0024] Y=URL_scheme://y.y.y.y:zzz.

[0025] It is understood that URL_scheme://y.y.y.y:zzz is an exemplary scheme and location and that a scheme and location may comprise any scheme and location type known to one of ordinary skill in the art including a DNS scheme/IP location having a form similar to 192.168.0.1:88. For example, namespace Y <b>68</b> includes a reference <b>70</b> to the object “sample data”. Namespace X <b>60</b> and namespace Y <b>68</b> each comprise at least one computer or other data device as is known to one of ordinary skill in the art. In addition, namespace X <b>60</b> and namespace Y <b>68</b> communicate using any method of data communication known to one of ordinary skill in the art including propagated signals <b>76</b> such as those generated by electronic data communications networks. Computer program code enabling namespace X <b>60</b> to perform a lookup in namespace Y <b>68</b> is located in a computer readable medium <b>72</b> and is received by namespace X <b>60</b> and/or namespace Y <b>68</b> via a propagated signal <b>74</b> or via any mechanism known to one of ordinary skill in the art. Alternatively, the computer readable program code may be integrated into a component of namespace X <b>60</b> and/or namespace Y <b>68</b>.

[0026] Namespace <b>60</b> contains entry Y <b>66</b>, which contains a URL that identifies the location of namespace Y <b>68</b>. The naming service for namespace <b>60</b> delegates namespace requests to a 3rd party provider <b>62</b>. Namespace <b>68</b> contains the entry “sample” <b>70</b>, which contains sample data. A client performs a lookup in local namespace <b>60</b> using the lookup name “df//Y/sample”. The lookup request is passed to the 3rd party provider <b>62</b>. The 3rd party provider <b>62</b> parses the lookup string into two parts: “df://Y” and “sample”. The 3rd party provider <b>62</b> uses the first part (“df://Y”) to lookup the URL <b>64</b>, <b>66</b> that locates namespace <b>68</b>. The 3rd party provider <b>62</b> then uses that URL <b>66</b> to direct a subsequent lookup request to namespace <b>68</b> and uses the remaining part of the original lookup name—“sample”—as the lookup name passed to namespace <b>68</b>. The result of this lookup is passed to the client that performed the original lookup.

[0027]FIG. 4 shows an alternative exemplary embodiment using a WEB server product such as IBM WEBSPHERE. A CosNaming service, associated with AE namespace <b>80</b>, contains the entry wsndf/PLEX<b>1</b><b>86</b> that contains the string “iiop://x.x.x.x:ppp”. An LDAP naming service, associated with <b>390</b> namespace <b>82</b>, contains a home reference <b>88</b> named “ivp.policysession”. The AE namespace <b>80</b> includes an installed URL context factory <b>84</b> named wsndfURLContextFactory. A client (not shown) of the AE namespace <b>80</b> performs a lookup with name “wsndf://PLEX<b>1</b>/ivp.policysession”. The AE JNDI service matches the URL scheme, “wsndf”, with installed URL context factory <b>84</b> “wsndfURLContextFactory” and passes the lookup request to it. The wsndfURLContextFactory <b>84</b> breaks the lookup name into two parts: “wsndf/PLEX<b>1</b>” and “ivp.policysession”. The wsndfURLContextFactory <b>84</b> uses “wsndf/PLEX<b>1</b>” to lookup the java.naming.provider.url <b>86</b> necessary to do a lookup in <b>390</b> namespace <b>82</b>, then does a lookup in the 390 namespace <b>82</b> for the second part of the name—“ivp.policysession”. The lookup result is returned to the client of the AE namespace <b>80</b>.

[0028] The description applying the above embodiments is merely illustrative. As described above, embodiments in the form of computer-implemented processes and apparatuses for practicing those processes may be included. Also included may be embodiments in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. Also included may be embodiments in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or as a data signal transmitted, whether a modulated carrier wave or not, over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.

[0029] While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiments disclosed for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims.