JBoss Enterprise Application Platform 6 Deployment and Patching

Red Hat JBoss EAP 6 Deployment and Patches

Alexandre Cavalcanti

Middleware Technical Account Manager

[email protected]

mailto:[email protected]

JBoss Deployment and Patches - Alexandre Cavalcanti2

AGENDA

Introduction

Supported Deployment Types

Types of deployment

Applying patches to EAP

Applying patches to JBPMS

JBoss Troubleshooting - Alexandre Cavalcanti3

Is it possible to deploy applications like we did in EAP 5?

Can we have hot deployment enabled in production?

How do I know if a deploy was successful?

Apply a patch is like replace all files?

Is the process the same for EAP and JBPMS?

Introduction


Enterprise Archives (ear)

Web Application Archives (war)

Enterprise Java Bean (EJB) Jars (jar)

Resource Adapter Archives (rar)

JBoss Service Archives (sar) • We recommend you migrate your sar to a standard JavaEE type and not use sars as

they are JBoss specific and could be removed in a future JBoss EAP release

https://access.redhat.com/solutions/460073

Supported Deployment Types



Deploy with the management console • Benefit of a graphical interface that is easy to use Deploy with the management CLI • Benefit of single command line interface with the ability to create and run deployment

scripts Deploy with the HTTP API • curl -f --digest -u "<user>:<pass>" -H Content-Type:\ application/json -d '<json request>'

"http://localhost:9990/management" Deploy with the Deployment Scanner • Allows you to build and test applications in a manner suited for rapid development cycles

(Not recommended for production environments) Deploy with Maven • Allows you to incorporate a deployment cycle as part of your existing development

workflow

Types of deployment


To facilitate patch management with zip-based installations, Red Hat has added a new patch command in the JBoss CLI. For standalone mode: • [standalone@localhost:9999 /] patch apply /<patch_download_url>/jboss-eap-

<cumulative_patch_version>.zip For domain mode specify the --host attribute as follows: • [domain@localhost:9999 /] patch --host=$HOST apply /<patch_download_url>/jboss-eap-

<cumulative_patch_version>.zip To apply to the EAP installation jboss-cli is running from • $JBOSS_HOME/bin/jboss-cli.sh --command="patch apply /<patch_download_url>/jboss-

eap-<cumulative_patch_version>.zip"


Applying patches to EAP



Unzip the file and use apply-updates.[sh|bat] script to automatically apply the patch.

The script takes two parameters: path to distribution root that should be patched and type of the distribution. You can run apply-updates.[sh|bat] -h to get more information.

There is blacklist.txt file in the root of the patch directory. Users can edit the file and add paths to files that they don't want to update. Instead of overwriting those files, new files with ".new" extension are created.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html/Installation_Guide/chap-Patching_and_Upgrading_Red_Hat_JBoss_BPM_Suite.html

Applying patches to JBPMS

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html/Installation_Guide/chap-Patching_and_Upgrading_Red_Hat_JBoss_BPM_Suite.html

Questions?

JBoss Enterprise Application Platform 6 Deployment and Patching

Technology