Replace WebLogic Side-By-Side Production Redeployment in Red Hat JBoss Enterprise Application Platform 6

Updated -

Summary

Oracle WebLogic Server includes a proprietary side-by-side production redeployment feature. For applications that meet certain requirements and restrictions, the new version of the application is deployed while the older version is still running. The old and new applications must be running on the same server or cluster. The new version of the application accepts new web session requests while the older version finishes processing requests already in process. Upon completion of the existing session requests, the older version of the application is then undeployed.

In Red Hat JBoss Enterprise Application Platform 6, you can achieve the same result using either of the following approaches.

Deploy the new application to a secondary server group or cluster

This approach requires the use of a hardware or software dispatcher, for example, Apache, on the front end to route the new session requests to the new version of the application deployed to the secondary server group.

Deploy the new application serially to the same clustered domain

For this approach, you must create a rollout deployment plan using the Management CLI. The following is an example of a CLI command to create a rollout plan in a clustered domain.

deploy ClusterWebApp.war --name=ClusterWebApp.war --runtime-name=ClusterWeb.war --server-groups=ha-server-group --headers={rollout ha-server-group(rolling-to-servers=true)}

For more information, see How to create a roll out deployment plan to deploy applications in a clustered domain in JBoss EAP 6.x?

Comments