Red Hat Training

A Red Hat training course is available for JBoss Enterprise SOA Platform

Chapter 20. Deploy Archive Files

20.1. Hot Deployment

"Hot deployment" refers to the SOA Platform server's ability to detect a deployed ESB archive as soon as it lands in the server profile's deploy directory. The SOA Platform server software constantly monitors that directory and automatically detects any changes to it. It can also detect changes to the state of existing archives and automatically re-deploy them.
These actions have life-cycle support. This means that, upon hot re-deployment, they terminate "gracefully" by finishing active requests. They will not accept any more incoming messages until they are re-started. (All of this occurs automatically.)

Note

You cannot deploy archives if the JBoss Enterprise SOA Platform is running in standalone mode.
The node monitors the time-stamp on this file and re-reads its contents if a change occurs.

20.2. Hot Deployment and jbossesb.sar

The jbossesb.sar archive can be deployed live. It will deploy when:
  • its time-stamp changes, (if the archive is compressed.)
  • the timestamp of the META-INF/jboss-service.xml file changes, (if the archive is in exploded form.)

20.3. Hot Deployment and ESB Archives

An *.esb archive will automatically redeploy when:
  • the time-stamp of the archive changes, (if the archive is compressed.)
  • the META-INF/jboss-esb.xml file's time-stamp changes, (if the archive is in exploded form.)

20.4. Redeploy a Rules File

Procedure 20.1. Task

  1. To redeploy a .DRL or .DSL file, redeploy the jbrules.esb directory by copying it back into SOA_ROOT/jboss-as/server/PROFILE/deploy.
  2. Alternatively, you can activate the Action Configuration's ruleReload feature. After activating this functionality, if a rule file changes, it is re-loaded automatically.

20.5. Redeploy a Transformation File

Procedure 20.2. Task

  1. Redeploy the .ESB archive in which it resides by copying it back into the SOA_ROOT/jboss-as/server/PROFILE/deploy directory.
  2. Alternatively, launch a web browser and log into the Monitoring and Management Console at http://localhost:8080/admin-console.
  3. Send out a notification message over the Java Message Service. Smooks will process this event causing it to reload automatically.

20.6. Redeploy a Business Process Definition

Prerequisites

  • JBoss Developer Studio

Procedure 20.3. Task

  • Use the jBPM Eclipse plug-in to deploy a new version of a business process definition to the jBPM database.

    Note

    Please be aware that only a fresh process instance will use this new version. Existing process life-cycles will still use the previous definition.

    Note

    Note that this procedure works in standalone mode, too.

20.7. Reload Rules Whilst Running in Standalone Mode

Procedure 20.4. Task

  • Run ruleReload.