Configurations made in Application Management Configuration Editor are not reflected in workspaces

The problem: The workspaces for an agent are not being displayed, or the agent is not otherwise behaving, according to the configuration that is defined in the Application Management Configuration Editor.

The solution: This problem might occur for any of the following reasons:
  • The transaction to monitor is not assigned to a profile which distributes the configuration where you are monitoring the transaction.

    As shown in the following example, the letter “i” is displayed in a blue square next to the affected application if this situation occurs.

    AMCE node tree showing an affected application

    To correct this condition, complete the following steps:
    1. Open the Application Management Console Editor.
    2. Navigate to the Profiles tab.
    3. Select the Profile to distribute this configuration.
    4. Click the Transactions tab for the selected profile.
    5. Click Add.
    6. Select the transaction to monitor (in this example, Web Transactions is selected).
      The selected application and transactions to monitor
    7. Click OK.

    After you return to the Applications tab in the Application Management Console Editor, the letter ‘i’ is no longer displayed next to the selected application.

  • The profile that distributes the configuration is not defined correctly to distribute the changes to the preferred monitoring agent.
    To investigate this possibility, complete the following steps:
    1. Open the Application Management Console Editor.
    2. Navigate to the Profiles tab.
    3. Select the applicable profile.
    4. Select the Distribution tab.
    5. Verify that the particular agent is included in the Assigned panel, similar to the following example:
      Verifying the agent is included in the list of agents receiving the distributed configuration.
  • There is more than one Application Management Console (T3) agent running in your environment. You can have only one T3 agent in your environment.
    To resolve this problem, use the listSystems -t T3 Take Action command to determine where there are T3 agents running in your environment. You can typically find this command in the following locations on your Tivoli Enterprise Management Console system:
    • On Windows systems: C:\ibm\itm\bin
    • On UNIX systems: opt/IBM/ITM/bin
    The output of this command is similar to the following example:
    Managed System Name Product Code Version Status
    rtRHLinux1:T3 T3 07.20.02.00 Y
    rTEMS2:T3 T3 07.20.02.00 Y
    Look for multiple entries that have the following characteristics:
    • The managed system name ends with :T3 (for example, rtRHLinux1:T3 or rTEMS2:T3)
    • The status is Y.

    You can ignore any entry that has a managed system name ending in :KT3A or :KT3S. These entries refer to nodes appearing under the Applications folder or Internet Services folder in the Tivoli Enterprise Portal physical navigator tree.