Physical tree not loaded in Tivoli Enterprise Portal Server

Edit online

Explains how to resolve issues where the Tivoli® Enterprise Portal Server physical tree does not load correctly after installation and update.

By default, the self-describing agent feature is enabled (TEPS_SDA=Y). After the installation is complete and the Tivoli Enterprise Portal Server connects to the z/OS hub Tivoli Enterprise Monitoring Server, the application support files will be downloaded from the hub Tivoli Enterprise Monitoring Server, and then automatically installed and configured in the Tivoli Enterprise Portal Server. For more information about the self-describing agent, see Self-describing agent installation.

Problem
The self‑describing agent (SDA) does not update the Tivoli Enterprise Portal Server physical tree definitions correctly.
Cause
You accessed the Tivoli Enterprise Monitoring Server before the SDA process finished. During the update, the SDA modifies the tep.jnlp file as it processes data from the hub Tivoli Enterprise Monitoring Server. If you open the Tivoli Enterprise Monitoring Server in a browser and select the Java® Web Start option too early, the system downloads a partially updated tep.jnlp file, which results in missing workspace definitions.
Solution

After you start the IBM Tivoli Monitoring - Tivoli Enterprise Portal Server Container wait 10 to 15 minutes before accessing the container.

For Java Web Start: If the physical tree does not load correctly, delete the Java cache and download the tep.jnlp file again.

You can also check the tep.jnlp file to verify that it contains the expected product file names processed by the SDA from the hub Tivoli Enterprise Monitoring Server system.

  1. Log in to the itmzcx_teps container: 
    podman exec -it itmzcx_teps bash
    docker exec -it itmzcx_teps bash
  2. Verify the contents of the tep.jnlp file: 
    more /opt/IBM/ITM/ls3266/cw/tep.jnlp
    If any expected products are missing, wait for 5 minutes and check the file again.