You can only inspect the details of Java services of the node instance the used Bridge is running on. If you have aggregated multiple node instances into a Bridge domain, you need to use the Bridge of the specific node instance the Java service is running on.

All users may view details of a Java service. Expand the tree below a node instance in the Node Instances section of the navigation. Then, navigate to a Java service entry below the sub-navigation item Java. The tab Java Service is initially displayed.

Figure: Java Service Details

BRIDGE > Java Service Details > java_service_details.png

Status Information

In the Status Information section, the status of the Java service (Running or Stopped) is displayed. Here you can start, stop, delete, or kill the service.

Stopping the service
Killing the service

Service Details

In the Overview section, the following information is displayed:

Element	Description	Origin (MANIFEST.MF)
Version	Version of the Java service as specified in package.json.	`E2E-Service-Version`
Description	Description of the Java service as specified in package.json.	`E2E-Service-Description`

Preferences

In the Preferences section, the following preferences can be modified:

Option	Description
Automatic Startup
Automatic Restart	Also consider the implications of Minimum Uptime in Seconds when setting this option.
Minimum Uptime in Seconds
UI URL	Specify the URL of the user interface of the Java service. It then will be displayed as an additional tab within the Bridge and you can access it directly via the Bridge.
UI Tab Title	If the Java service has a user interface that is integrated to the Bridge, you can specify the title of the tab here. The default title is User Interface.
Owner
Remote Debug Port	If you want to debug your Java service, save the number of the port you want to use for debugging in this field. While starting the service on the Bridge, the port number will automatically be committed to the service and you can attach a Java debugger to this port. The Java service process will be started with the following options in this case: `-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=<REMOTE DEBUG Port>` If no remote debug port is specified, debugging is disabled.

History

Switch to the History tab to view the history of all user actions that were executed on the selected Java service since its deployment.

In the Java service history all user actions are listed - comprising starting and stopping the service, modification of the preferences, etc. The list is sorted in a chronological order and also shows the user who initiated the action.
The history also lists internal actions, for instance, when the system started or stopped a Java service automatically.

All users have access to the history information.

Figure: Java Service History

BRIDGE > Java Service Details > java_service_history.png