When you enable the remote RMI interface, the AdminServer can communicate with the OpenEdge resources, such as the NameServer, OpenEdge DataServer for Oracle, and OpenEdge DataServer for MS SQL Server and management tools, such as DBMAN.
Warning: Enabling the remote RMI interface introduces significant security risks by expanding the AdminServer attack surface. Progress recommends not to enable the remote RMI interface unless absolutely necessary. If the remote RMI must be enabled, then:
  • Restrict access using firewall rules and host-based controls.
  • Enforce strong authentication mechanisms.
  • Apply the principle of least privilege when granting access to the host environment.
  • Monitor and audit RMI activity regularly to detect misuse.

To enable the remote RMI interface, perform the following steps using a dedicated, minimally privileged service account:

  1. Stop the AdminServer. For more information, see Stop the AdminServer.
  2. Navigate to the location where the AdminServerPlugins.properties file is placed.
    • On Windows, go to: %DLC%\properties\AdminServerPlugins.properties
    • On Linux, go to: $DLC/properties/AdminServerPlugins.properties
  3. Open the file using a text editor and locate the [PluginPolicy.Progress.AdminServer] and [PluginPolicy.Progress.ProAdsv] sections.
  4. Add -DenableRemoteRMI=true to the end of the jvmargs lines in both sections. Ensure that you add a space before the new entry, as shown below: 
    
% AdminServer Plugin Properties file
...
[PluginPolicy.Progress.AdminServer]
    pluginclasspath=!{value-of:classpath}
    classpath=${DLC}/java/ext/esapi-*.jar,
${DLC}/java/oe/esamapi-*.jar,
...
jvmargs=-Xms512m -Xmx1024m -DenableRemoteRMI=true
...
[PluginPolicy.Progress.ProAdsv]
    pluginclasspath=!{value-of:classpath}
    classpath=${DLC}/java/ext/esapi-*.jar,
${DLC}/java/oe/esamapi-*.jar,
...
jvmargs=-DenableRemoteRMI=true
..
  5. Save the file and start the AdminServer. For more information, see Start the AdminServer.