Skip to content

Changing the RMI Port

The RMI port is configured in two places: on the server (daemon) and on the client (the Spectrum console or Script Server). Both must be updated together whenever the port changes, and the daemon must be restarted afterwards.

Spectrum installation

Edit $SPECROOT/DICOS/OneClickExt/bin/oneclickext.props and update:

oneclickext.rmi.port:     <new port>
oneclickext.rmi.connport: <new connection port>

Restart the OneClickExt daemon for the change to take effect. In the Spectrum OneClick console, select File > Exit — this triggers a restart of the embedded OneClickExt process.

The Spectrum console reads the RMI connection details from the JNLP launch file. These are managed through the OneClick Web Application configuration UI — editing the file directly is not recommended as changes may be overwritten.

  1. Open the OneClick Web Application in a browser. By default it is available at:

    http://<host>:9443/spectrum/

  2. Log in.

  3. Select Manage in the upper right corner.

  4. Go to the Applications tab and select the OneClick WebApp.

  5. Open the App Config tab and scroll down to Java/JVM Arguments.

  6. Update the following arguments:

    Argument Description
    -Doneclickext.rmi.primary.port RMI registry port (must match oneclickext.rmi.port on the server)
    -Doneclickext.rmi.primary.host Hostname of the daemon host (only if the host changed)

  7. Click Apply. The change takes effect when users next launch the console.

Standalone installation

Both the daemon and any clients (Script Server) read their configuration from properties files.

Edit $DCSROOT/DICOS/OneClickExt/bin/oneclickext.props and update:

oneclickext.rmi.port:     <new port>
oneclickext.rmi.connport: <new connection port>

Restart the daemon for the change to take effect.

Edit the Script Server properties file and update:

sl.rmi.port: <new port>
sl.rmi.host: <daemon hostname>

Restart Tomcat for the change to take effect.