Home > Articles > Mobile Application Development & Programming > HTML5 & Web Standards

  • Print
  • + Share This
From the author of

Establishing Connection

Before interacting with a UDDI registry for publishing purposes, it's essential to establish correct credentials with the UDDI deployer. For the Microsoft registry, this means getting a Passport account. Once this account is established, it can be used to interact with the Microsoft registry.

Per the UDDI specification, a registered and validated user (or program) can publish information on a UDDI registry. The registration and validation comes in form of an authentication token. This token has a specific lifespan during which it can be presented to the registry for publishing purposes. A C# program segment used for this purpose might look like this:

Publish.AuthenticationMode =
Publish.Url = "URL of the UDDI registry";
Publish.User = "Passport login name";
Publish.Password = "Passport login password";
GetAuthToken gat = new GetAuthToken();
gat.UserID = Publish.User;
gat.Credentials = Publish.Password;
AuthToken at = gat.Send();

When the Send method of the GetAuthToken object is invoked, the UDDI .NET SDK APIs interact with the UDDI registry in XML format and receive an authentication token upon successful authentication. This token can then be used when publishing data about a service or service provider. Let's consider an example.

Prudentially 401(k), Inc. is a subsidiary of a global financial services conglomerate that specializes in providing pension fund management services to its clients. The company has established a large clientele through the years and is one of the founding members of the Financial Interactions and Transactions Standardization Organization (FITSO).

FITSO is an established not-for-profit consortium of large financial institutions in North America, including pension fund providers. FITSO has embarked on a standardization effort to make interacting with financial service organizations simpler and more predictable. FITSO is currently focusing on pension fund providers and hopes to roll out the experience to other financial service areas thereafter. After investigating web services standards and interaction patterns, FITSO decides that it needs to adopt and encourage two types of standards:

  • Classification scheme for business entities

  • Set of basic interaction patterns

Given the familiarity of the North American Industry Classification System (NAICS) in the financial industry, FITSO decides to recommend the NAICS classification scheme to classify the business entities behind the pension services. This taxonomy choice translates to using the NAICS tModel preloaded in the UDDI registry.

FITSO has also decided to standardize on basic interactions. Service consumers would be able to develop applications that interact with the services; the vision is that applications designed to work with one service would easily interchange with another. Based on the types of interactions that are simple enough to standardize, FITSO designs a set of service interfaces for the pension fund services. For this example, we focus on the 401(k) information services specification. The functions that should be supported by a FITSO pension fund are as follows:

  1. Get list of funds.

  2. Get fund performance.

  3. Add employee to a plan.

  4. Get employee contribution data.

FITSO needs to register a tModel associated with this service interaction interface, as shown later in this article.. This tModel is called TM401k. Prudentially 401(k), Inc. needs to use this information when registering as a company that provides a service abiding by the TM401k tModel. Assume that the registration data for Prudentially 401(k) is as shown in Table 1.

Table 1 FITSO Compliance-Based Prudentially 401(k), Inc. Modeling


UDDI Representation


Entity: Prudentially 401(k), Inc.







Interface Specification


  • + Share This
  • 🔖 Save To Your Account