WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Assigning aliases to service types

When you define service types for the Parlay Connector, you must create a unique definition for each service type. Therefore, you might have service types with the same name that have different properties. To differentiate between service types that have the same name but different properties, you can assign an alias name to represent a service type with specific properties.

About this task

Every service manager name has two parts, for example ServiceType:ServiceID. The combination is unique for the Parlay gateway, and therefore for the Parlay Connector. When you assign an alias for a service manager, your applications can then use that alias to obtain access to the service manager.

If you have a service type called connection type, and its properties are cable, dial up, and DSL, you might define three aliases for the one service type, but each with a different connection property definition. When you want to use the cable connection, you must specify the cable alias. By using an alias for each, you are guaranteed to get the connection type you requested.

You might also have service types with different names but the same properties. An array of service types can be defined for each connection type, such as multiple service types which use the cable connection type. In this case, all the service type names are treated as aliases. A dummy alias with the same name as the service type is automatically created, so each alias is a list of services from 1 to n entries.

A record of which service type was last used is kept so that the next request for that service type uses the next entry in the list. This feature spreads the demand across the services, balancing the load.

A service type explicitly defined under an alias is also defined under the implicit alias, which is the service name. So if alias A is defined for a service type X with a specific property definition of X, all service types in alias A are in service type X, but not all service types in X are in alias A.

In this case, If a user application needs a service type specifically defined by alias A, and another application needs the same service type, if the properties of service type X are irrelevant for both applications, the applications might receive the same service type. Load balancing is not an issue because the service type is specified from two different lists, and load balancing only knows about the service types in the alias list.

Complete these steps to assign an alias for a service type.

  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
    3. Click Log in.
  2. In the navigation pane, expand TWSS Parlay Administration.
  3. Click Telecom Server to display the list of deployed telecom applications.
  4. Click Telecom Applications > Parlay Connector > Parlay Connector Template > Svc Type Alias Defs.
  5. Assign aliases for one or more service types.
  6. Click OK.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.