Configuring the Web Interface › Web Directors and Web Engines Configuration › Make Changes Using pdm_edit.pl › Create an Alias Example

Previous Topic: Add Repository Daemons

Next Topic: Move Knowledge Daemons

Create an Alias Example

Aliases are optional in CA SDM. This example demonstrates how you prepare to create an alias, and then how to create the alias.

Example: Prepare to Create an Alias

Before you create aliases, do the following:

  1. Define object managers and add some to groups. The names of the object managers are: domsrvr:group1:11, domsrvr, domsrvr:seattle:12, domsrvr;seattle:13, domsrvr:Tacoma:11.
  2. Define web engines and assign object managers to the web engines. If you accept the default, the object manager is assigned domsrvr.
  3. Enter a regular expression that matches a group of object managers. If the web engine connects to any object manager, enter ANY. ANY is a default alias. The web engines and Java clients use the aliases to specify ANY or a subset of the running object managers to which they can connect. For example, you want the Java clients located in Washington to connect to object managers located in Seattle. You connect them to /domsrvr:seattle.*. Or, you can define an alias named SEATTLE and assign it the value /domsrvr:seattle.*.

Example: Create an Alias

This example assumes that you defined an object manager and associated it with a group named seattle. If not, the alias is created, but a warning is displayed. This warning indicates that the defined alias does not match any existing object managers.

  1. From the pdm_edit.pl top menu select A, and press Enter.

    The Alias submenu appears.

  2. Enter a name for your alias. In this example, enter SEATTLE.

    You are prompted for the regular expression that is to be associated with this alias.

  3. Enter /domsrvr:seattle.*, which matches any object manager with a name that starts with domsrvr:seattle. You can use this alias when you configure web engines and Java clients.
  4. Save and exit the pdm_edit.pl utility.

    An alias install script (named alias_install.bat or alias_install.sh) is created.

  5. Run the alias install script on your primary server. This creates the aliases and transmits them to all secondary servers and java clients.