Configuring dispatcher URIs

If you install the gateway component on a different computer than Content Manager or Application Tier Components, you must configure the gateway computer so that it knows the location of a dispatcher. A dispatcher is installed on every Content Manager and Application Tier Components computer. Configure the gateway to use the dispatcher on an Application Tier Components computer.

For failover protection, you can configure more than one dispatcher for a gateway computer. When multiple dispatchers are configured, requests are normally routed to the first dispatcher in the list. If this dispatcher becomes unavailable, the gateway determines the next functioning dispatcher on the list and routes requests there. The primary dispatcher status is monitored by the gateway, and requests are routed back to this component when it returns to service.

After you do the required configuration tasks, the gateway computer can work in your environment.

Before you begin

Ensure that the computers where you installed Content Manager are configured and the default active Content Manager computer is available before you configure gateway computers.

Procedure

  1. Start IBM® Cognos® Configuration.
    1. On Microsoft Windows, click Start > IBM Cognos Configuration.

      If you are using a Windows 7, or Windows 2008 computer, and have installed the product to the Program Files (x86) directory, start IBM Cognos Configuration as an Administrator.

    2. On UNIX or Linux® operating systems, go to the install_location/bin64 directory and then type the following command:

      ./cogconfig.sh

      If IBM Cognos Configuration does not open, ensure that you set the DISPLAY environment variable.

      If you see a JAVA.Lang.unsatisfied link message, verify that you are using a supported version of Java™.

      If you see a Java.lang.unsupportedClassVersionError message, ensure that you are using a 64-bit version of Java.

  2. In the Explorer window, click Environment.
  3. In the Properties window, under Gateway Settings, specify the values for Dispatcher URIs for the gateway:
    • Click in the Value column.
    • Click the Edit button.
    • Change the localhost portion of the URI to the name or IP address of an Application Tier Components computer.

      This will ensure that users in different locations can connect to reports and workspaces that are sent by email.

      Tip: If you want to send requests to the dispatcher from a Software Development Kit application or an IBM Cognos Analytics modeling tool that is outside of a network firewall, connect to a dedicated gateway that is configured to connect to the dispatcher using the internal dispatcher URI for your environment (for example, http://localhost:9300/p2pd/servlet/dispatch). For security reasons, the default setting for the Dispatcher URI for gateway property prevents the dispatcher from accepting requests for an Software Development Kit application or modeling tool that is outside the firewall. Ensure that you configure appropriate security for this dedicated gateway, such as SSL (see Configuring the SSL protocol for IBM Cognos components). Do not change your main gateway to use the internal dispatcher URI. Doing so will reduce the security of the IBM Cognos Analytics portal and studios.
    • If you want to add another URI, click Add and change the localhost portion of the new URI to the name or IP address of another Application Tier Components computer.
      Tip: If you want to use the dispatcher on a standby Content Manager computer, ensure that you add it after you add the Application Tier Components computers. If you add the dispatcher from the active Content Manager computer, ensure that it is last in the list.
    • After you specify all the URIs, click OK.
  4. In the Explorer window, under Security > Cryptography, click Cognos, the default cryptographic provider.
  5. Under the Certificate Authority settings property group, set the Password property to match what you configured on the default active Content Manager computer.
  6. Ensure that all other cryptographic settings match what you set on the default active Content Manager computer.
  7. Test that the symmetric key can be retrieved. In the Explorer window, right-click Cryptography and click Test.

    IBM Cognos Analytics components check the common symmetric keys (CSK) availability.

  8. From the File menu, click Save.