Red Hat Training

A Red Hat training course is available for Red Hat JBoss Operations Network

3.4. Deploying Server-Side Plug-ins

Server-side are deployed in one of two ways:
  • Copying the plug-in JAR file into the sourceRoot/plugins/ folder in the server root directory (locally).
  • Uploading the plug-in JAR file through the web interface (remotely).
Server-side plug-ins are hot-deployed, so they are active as soon as they are deployed without having to restart any of the JBoss ON servers. Every server-side plug-in is deployed globally and is automatically propagated among the server cloud. The configuration for each server is polled regularly (at an interval defined in the server properties file).
By default, every server-side plug-in is automatically enabled (and therefore active) unless the configuration in the plug-in descriptor explicitly prevents it from being deployed enabled. When a plug-in is deployed and enabled, it is automatically propagated to other JBoss ON servers in the infrastructure.

Figure 3.1. Server-Side Plug-in Propagation

Server-Side Plug-in Propagation
There are two possible states for a server-side plug-in:
  • Deployed and enabled
  • Deployed and disabled
Report a bug

3.4.1. Remotely Deploying Server-Side Plug-ins

  1. In the top menu, click the Administration tab.
  2. In the Configuration box on the left navigation bar, click the Server Plugins link.
  3. Scroll to the Upload Plugin section at the bottom of the page.
  4. Click the Browse... button, and browse to the plug-in JAR file's location.
  5. To deploy the plug-in, click the Upload button.
Any plug-ins uploaded to one server are automatically deployed and registered on all other JBoss ON servers in the cloud within a few minutes.
Report a bug

3.4.2. Locally Deploying Server-Side Plug-ins

Each server installation has a top-level plugins/ directory. The server periodically polls this directory. Any new or updated JAR files are copied to the appropriate directory in the server configuration, and then the original JAR file is deleted from the plugins/ directory.
If the JAR file is on the same host machine as an JBoss ON server, the JAR file can just be copied into that sourceRoot/plugins/ directory and the server will deploy it.
Report a bug