Skip to Content
Information
This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Configuring the Java plug-in server

Configure the Java plug-in server in the AR System Administration: Plugin Server Configuration form. The configuration is stored in the pluginsvr_config.xml file in the pluginsvr subdirectory of your AR System server installation directory. This file should be in the same directory as the plug-in server JAR files and startup script. (It must be in the class path for the plug-in server.) When you add a plug-in to the plug-in server configuration in the AR System Administration: Plugin Server Configuration form and save the form, the plug-in server loads the new plug-in after a configured delay. If you remove a plug-in server or make other configuration changes, use armonitor to stop and restart the plug-in server for it to process the changes.

The file encoding of the pluginsvr_config.xml file is UTF-8, which enables you to use localized plug-in names in the configuration file. If you modify the pluginsvr_config.xml file, save it as a Unicode file. Some text editors, such as Windows Notepad, save files as single-byte ANSI (ASCII) by default.

Success

Tip

Install critical plug-ins, such as an LDAP plug-in that performs LDAP authentication, in separate plug-in servers. If multiple plug-ins are installed on a single server, problems with one plug-in might affect the use of the other plug-ins.

For descriptions, valid values, and default values for the Java plug-in server configuration options, see Configuring-Java-plug-in-servers. For configuration of the C-based plug-in server, arplugin, see Enabling-plug-ins.

This section includes the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

AR System 21.05