Enabling the JMX RMI Interface on an Execution Server that is Running as a Service

For security reasons, the JMX RMI interface is disabled by default on the execution server. To enable the JMX RMI interface on the execution server, when the execution server is running as a service, perform the following actions:

Double-click the Silk Performance Manager Service Manager tray icon in the Windows task bar. The Silk Performance Manager Service Manager displays, with up to five tabs visible, depending on the services that are installed on this computer.
Click the Execution Server tab. This tab represents the Performance Manager execution server, running as a Windows system service.
Click Stop to stop the execution server system service.
Click Query Status to check the service’s status. Make sure that the service status is stopped.
Open the Registry Editor.
1. Click Start.
2. Type regedit into the search field.
3. Select the first result.
Remove the following from the HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\SPMExecServer<version>\Parameters\Java\Options registry key:
```
-Dcom.sun.management.jmxremote=false
```

Type the following into the registry key:

-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.port=19144

Double-click the Silk Performance Manager Service Manager tray icon in the Windows task bar. The Silk Performance Manager Service Manager displays, with up to five tabs visible, depending on the services that are installed on this computer.
Click the Execution Server tab. This tab represents the Performance Manager execution server, running as a Windows system service.
Click Start to start the execution server.