How to check if ESP WEB UI is active

Products

• ESP Workload Automation

Issue/Introduction

How to check if ESP WEB UI active in the system? 

Environment

ESP Workload Automation 12.0 - z/OS supported releases - 

Resolution

1. Web Browser Verification: 
   The most direct way to confirm the Web UI is active is by sending a request to its health endpoint.
   Action: Open a web browser and navigate to: protocol://host:port/actuator/health
   Protocol: http or https (depending on your TLS configuration).
   Host: The address of the server running the ESP Web UI.
   Port: The port specified in the server.port property of your ADPTPROP configuration.
   Expected Result: Should receive a JSON response indicating "status": "UP".
2.  Check the Started Task (STC) Logs: 
   If the browser check fails, inspect the system logs for the Web UI's started task:
   STDOUT/JESMSGLG: Look for successful initialization messages. In the STDOUT DD, check messages like: I Starting EdaBootKt using Java... I No active profile set, falling back to 1 default profile: "default"
   Errors to Watch For: If the output is different or the task has failed, check for errors such as ICH420I or connection timeouts.
3. Verify Product/Service Status within ESP: 
   Verify the status of related services directly within ESP using Page Mode or via a MODIFY command:
   Command: F ESP,SERVICE LIVEDATA (or just SERVICE LIVEDATA in Page Mode).
   Expected Output:
   LIVE DATA SERVICE : Enabled
   LOGSTREAM STATE : Connected
4. Display Status via XCF: 
   If using a sysplex environment, check the status of the listener services:
   Command: XCF D A
   Expected Result: Ensure that listeners for services like ROUTING, SCOREBD, and TRACKING show as Active.