Verifying the dashboard data provider is enabled

Check the Tivoli® Enterprise Portal Server configuration to verify the dashboard data provider is enabled by using Manage Tivoli Enterprise Monitoring Services or the command-line.

• Using Manage Tivoli Enterprise Monitoring Services
  1. Start Manage Tivoli Enterprise Monitoring Services on the computer where the portal server is installed:
     • Click Start → Programs →IBM® Tivoli Monitoring → Manage Tivoli Enterprise Monitoring Services.
     • Where install_dir is the IBM Tivoli Monitoring installation directory, change to the install_dir/bin directory and run ./itmcmd manage [-h install_dir].
  2. Right-click Tivoli Enterprise Portal Server:
     • Click Reconfigure, and click OK to accept the existing configuration and go to the second TEP Server Configuration window.
     • Click Configure. The Common Event Console Configuration window is displayed. Click OK to accept the current values. On the Configure Tivoli Enterprise Portal window, select the Dashboard data provider tab.
  3. In the dashboard data provider area of the configuration window, verify the Enable the dashboard data provider check box is selected. If it is not selected, then select it.

     In this same area of the configuration window, you can specify a domain override value and enable authorization policies.

     1. The domain override value is optional and is only valid when the dashboard data provider is enabled. It changes the default dashboard data provider ID and domain name for authorization policies from itm.<hub monitoring server name> to itm.<domain override value>. The value cannot exceed 124 characters. Best practice is to configure a domain override value for these scenarios:
        • The Hot Standby high availability feature is being used for the hub monitoring server. By configuring a domain override value, the dashboard data provider ID and domain name will not change when the portal server is configured to connect to the new acting hub monitoring server. If you do not configure a domain override value in this scenario, you must reconfigure the connection between the IBM Dashboard Application Services Hub and the dashboard data provider and update any domain specific authorization policies when the portal server is configured to connect to the new acting hub monitoring server.
        • You have multiple hub monitoring servers and you are setting up a dashboard environment with single sign-on with authorization policies, and you want to create some domain specific authorization policies. You must specify a domain override value for this scenario if you want to use a more user-friendly domain name in your authorization policies other than the default value of itm.<hub monitoring server name>.
     2. The Enable authorization policies option is selected if you want to use authorization policies to control which managed systems and managed system groups a user can access in monitoring dashboards. Only enable authorization policies if you are setting up a dashboard environment with single sign-on, you plan to use authorization policies to control access to monitoring dashboards, and your administrators have already created the initial set of policies for dashboard user access.
        Note: If you plan to use authorization policies and they have not been created yet, leave this box unchecked. After the authorization policies are ready, reconfigure the portal server and enable authorization policies.
  4. If you made changes to the portal server configuration, click OK. Otherwise, click Cancel to exit.
  5. If you clicked OK and are prompted to reconfigure the warehouse connection information, answer No.
  6. On Windows, after some processing of the configuration settings, the Common Event Console Configuration window is displayed. Sometimes this window does not open in the foreground and is hidden by other windows. If processing seems to be taking longer than expected, minimize other windows and look for the configuration window. When the Common Event Console Configuration window is displayed, click OK.
  7. If you made configuration changes, ensure the portal server is restarted.
• Using the command-line

  If the Tivoli Enterprise Portal Server is on Linux or UNIX, you can check the portal server configuration from the command-line and enable the dashboard data provider if it is not already enabled.

  1. Log on to the computer where the Tivoli Enterprise Portal Server is installed.
  2. At the command-line, change to the install_dir/bin directory, where install_dir is the directory where you installed the product.
  3. Run the following command to view the Tivoli Enterprise Portal Server configuration settings: ./itmcmd config -g -A cq.
  4. Check if the KD8_ITM_REST_SERVICE_ENABLE variable is set to Y.

     If is not present, or is set to N, then the dashboard data provider is not enabled, so proceed with the remaining steps in this procedure.

     If it is set to Y, you have successfully verified the dashboard data provider is enabled and can skip the remaining steps.

  5. Run the following command to configure the Tivoli Enterprise Portal Server: ./itmcmd config -A cq.

     The message Agent configuration started is displayed, followed by a prompt: Tivoli Enterprise Portal Server will be stopped during configuration. Do you want to continue? [1=Yes, 2=No] (Default is: 2).

  6. Enter 1. The following prompt is displayed: Edit "Common event console for IBM Tivoli Monitoring" settings? [ 1=Yes, 2=No ] (default is: 1).
  7. Enter 2. The following prompt is displayed: Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1).
  8. Accept the default values for this prompt and the prompts that follow it until you see the prompt about configuring the dashboard data provider. If it is not enabled, select a value of 1 to enable it.
  9. Next you are asked if you want to specify a domain override value.
     1. The domain override value is optional and is only valid when the dashboard data provider is enabled. It changes the default dashboard data provider ID and domain name for authorization policies from itm.<hub monitoring server name> to itm.<domain override value>. The value cannot exceed 124 characters. Best practice is to configure a domain override value for these scenarios:
        • The Hot Standby high availability feature is being used for the hub monitoring server. By configuring a domain override value, the dashboard data provider ID and domain name will not change when the portal server is configured to connect to the new acting hub monitoring server. If you do not configure a domain override value in this scenario, you must reconfigure the connection between the IBM Dashboard Application Services Hub and the dashboard data provider and update any domain specific authorization policies when the portal server is configured to connect to the new acting hub monitoring server.
        • You have multiple hub monitoring servers and you are setting up a dashboard environment with single sign-on with authorization policies, and you want to create some domain specific authorization policies. You must specify a domain override value for this scenario if you want to use a more user-friendly domain name in your authorization policies other than the default value of itm.<hub monitoring server name>.
  10. If the dashboard data provider is enabled, you are prompted whether you want to enable authorization policies. Only enable authorization policies if you are setting up a dashboard environment with single sign-on, you plan to use authorization policies to control access to monitoring dashboards, and your administrators have already created the initial set of policies for dashboard user access.
      Note: If you plan to use authorization policies and they have not been created yet, leave this box unchecked. After the authorization policies are ready, reconfigure the portal server and enable authorization policies.
  11. After the installer has completed the configuration, the following message is displayed: Agent configuration completed and you are asked if you want to restart the portal server. Select 1 to restart it.