Tivoli Enterprise Portal Server physical tree is not correctly loaded

Access the Tivoli® Enterprise Portal Server container after the self-describing agent (SDA) update process is completed, otherwise, the physical tree might not be correctly loaded.

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.

Problem

The self-describing agent (SDA) doesn't update the Tivoli Enterprise Portal Server physical tree definitions correctly.

Cause

You accessed the Tivoli Enterprise Portal Server before the SDA process was competed. The SDA process updates the tep.jnlp file as it processes the data being sent from the hub Tivoli Enterprise Monitoring Server. Accessing the newly installed Tivoli Enterprise Portal Server via your browser, and selecting the Java Web Start option will download a copy of partially updated tep.jnlp file, which causes the missing workspace definitions.

Solution

After IBM® Tivoli Monitoring - Tivoli Enterprise Portal Server Container is started, wait for 10 to 15 minutes, and then access the container.
  • For Java Web Start: If the physical tree is not completed correctly, then delete the Java cache and download the tep.jnlp file again.
  • For Open Web Launch: If the physical tree is not completed correctly, then delete the directory or directories under C:\Users\yourUserID\AppData\Roaming\Rocket Software\Open Web Launch\cache and download the tep.jnlp file again.
You can also check the tep.jnlp file for the expected files names of the products that the SDA process would have processed from the hub Tivoli Enterprise Monitoring Server system:
  1. Log in to the itmzcx_teps Docker container:
    docker exec -it itmzcx_teps bash
  2. Verify the contents of the tep.jnlp file:
    more /opt/IBM/ITM/ls3266/cw/tep.jnlp
    If you see any expected products are missing, wait for 5 minutes and check the file again.

For more information about the self-describing agent, see Self-describing agent installation.