Debug Profile Service diagnostics

  • Debug Profile Service uses standard HTTP status codes to indicate the success or failure of the API call. If a failure occurs, the response contains a JSON body with an IBM message ID, which can be used to look-up more information about the error in Debug Profile Service messages.
  • The following logging indicators are used to verify whether Debug Profile Service has started or stopped. Logs that are prefixed with CWWKZ are generated by the IBM z/OS Liberty Embedded server framework.
    • Server Started:
      • Server’s JES Job Standard Output (STDOUT)
        Debug Profile Service API started with context path  [<context_path>/profile]      
IMS Transaction Isolation Service API started with context path  [<context_path>/imsiso]
Authentication Service API started with context path [<context_path>/auth]
      • JES System Log
        +CWWKZ0001I: Application profile-management started in <time> seconds
+CWWKZ0001I: Application ProfileService started in <time> seconds
    • Server Stopped:
      • JES System Log
        +CWWKZ0009l: The application ProfileService has stopped successfully.
+CWWKZ0009l: The application profile-management has stopped successfully.
  • Use the Debug Profile Service API discovery endpoint in a web browser of your choice to produce a single manual HTTP request to the server, if in doubt whether the server is not running or cannot fulfill a request. The discovery endpoint is in the form of <protocol>://<hostname>:<port>/<context_path>/profile/dtcn, and it queries the contents in the dtcn.ports file. If the server fulfills the discovery endpoint request, then it responds back with a JSON body that contains {"hostname":"<hostname>","apiversion":"<version>,"regions": <a list of regions defined in dtcn.ports file>}.