When running the background service or the servlet engine, it is often helpful to do some administration jobs without having direct access to the server. The xBus offers two possibilities for remote administration:

When running the background service or running the xBus inside a servlet engine, a JMX server will run in one thread as well. JMX stands for Java^TM Management Extension and is the Java standard technique for distributed management and monitoring of applications.

JMX administration is allowed out of the box only on the local machine. To make JMX remote administration possible, you have to edit the start scripts for the background service respectively the servlet engine. The necessary lines are already prepared and marked with a comment. The default port is 1099, if this is already occupied by another process, xBus will not start. You can change the port in the scripts and have to reflect this additionally in the configuration.

The easiest way to access the JMX administration is with the JConsole tool provided with the Java JDK. When starting on the same machine as the xBus is running, you can access the ReceiverService directly as a local process. If the remote administration is configured, you have to set the Remote Process URL to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi (localhost to be replaced by the hostname on which the xBus is running).

The attributes and operations to administrate the xBus are gathered under the MBean named xBus:

When running the xBus inside a servlet engine, some basic administration jobs, including querying the Journal from the database and starting/stopping of background receivers, can be done with any webbrowser. The address to start the HTML administration is:

http://localhost:8080/xbus/admin/index.html

or

https://localhost:8443/xbus/admin/index.html

You have to provide a user and a password to access the HTML administration. They are configured in XBUS_HOME/services/jakarta-tomcat/conf/tomcat-users.xml, their initial values are xbus / xbus. You should change these values before deploying the xBus in a productive environment.

This screenshot shows the menu entries of the HTML administration site:

When running the xBus inside a servlet engine, a restart of the xBus can be done by calling a SOAP web service. The WSDL describing the web service can be retrieved by calling:

https://localhost:8443/xbus/services/xBusAdministration?wsdl

This screenshot shows a part of the WSDL: