One of the
biggest advantages, besides the support for the Red Hat JBoss Enterprise
Middleware are the access to continuous updates and bug fixes. In previous
versions, minor patches could not be applied automatically, also updates or bug
fixes had to be installed manually, by changing individual configuration files
and replacing Java Archives.
Since version
6.2 the Command Line Interface of the JBoss Enterprise Application Platform
(EAP) contains a command to apply minor updates and patches without changing
individual files manually.
JBoss patches are released in two forms.
Asynchronous updates: one-off patches
which are released outside the normal update cycle of the existing product.
These may include security patches, as well as other one-off patches provided
by Red Hat Global Support Services (GSS) to fix specific issues.
Planned updates: These include
cumulative patches, as well as micro, minor or major upgrades of an existing
product. Cumulative patches include all previously developed asynchronous
updates for that version of the product.
High level Patch installation Steps:
1. Download
the patch zip file from the Customer Portal at
https://access.redhat.com/downloads/
2. From the
Management CLI, apply the patch with the following command including the
appropriate path to the patch file:
syntax ::
patch apply /path/to/downloaded-patch.zip
3. Restart the JBoss EAP 6 server for the
patch to take effect:
syntax :
shutdown --restart= true
-----------------------------------------------------------------------------------------------
Detailed Steps
-----------------------------------------------------------------------------------------------
1.Check version
|
[domain@192.168.1.12:9999 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /u03/local/opt/jboss-eap-6.2
JBoss AS release: 7.3.0.Final-redhat-14
"Janus"
JBoss AS product: EAP 6.2.0.GA
JAVA_HOME: null
java.version: 1.7.0_75
java.vm.vendor: Oracle Corporation
java.vm.version: 24.75-b04
os.name: Linux
os.version: 2.6.18-194.el5
|
2. Before
patching take a snapshot: Run the take-snapshot operation to capture a copy of the current server
configuration
|
[domain@192.168.1.12:9999 /] :take-snapshot()
{
"outcome" =>
"success",
"result" =>
"/u03/local/opt/jboss-eap-6.2/mydomain/master/configuration/domain_xml_history/snapshot/20160205-104031406domain.xml"
}
|
3.Apply a patch through CLI on master domain:
|
[domain@192.168.1.12:9999 /] patch --host=master
apply /u03/local/opt/jboss-eap-6.2/bin/jboss-eap-6.2.4-patch.zip --override-modules
{
"outcome" :
"success",
"response-headers"
: {
"operation-requires-restart"
: true,
"process-state"
: "restart-required"
},
"result" : null,
"server-groups" : null
}
|
4.Restart the JBoss EAP 6 host/server for the patch installation to take effect.
|
[domain@192.168.1.12:9999 /]
/host=master:shutdown(restart=true)
{"outcome" => "success"}
[domain@192.168.1.12:9999 /]
|
5. Apply a patch through CLI on Slave domain:
Before
patching take a snapshot Run the take-snapshot
operation to capture a copy of the current server configuration.
|
[domain@192.168.1.12:29999 /] /host=slave02:take-snapshot()
{
"outcome" =>
"success",
"result" =>
"/u03/local/opt/jboss-eap-6.2/mydomain/slave2/configuration/host_xml_history/snapshot/20160205-111016532host-slave.xml",
"server-groups"
=> undefined
}
[domain@192.168.1.12:29999 /]
|
Apply a patch
|
[domain@192.168.1.12:29999 /] patch
--host=slave02 apply /home/jboss/Desktop/jboss-eap-6.2.4-patch.zip --override-modules
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
"result" : null,
"server-groups" : null
}
|
Restart the slave for the patch installation to take effect.
|
[domain@192.168.1.12:29999 /]
/host=slave02:shutdown(restart=true)
{"outcome" => "success"}
[domain@192.168.1.12:29999 /]
|
Note: after a patch has been applied,
the jars picked up at runtime are picked up from the EAP_HOME/modules/system/layer/base/.overlays/$PATCH_ID/$MODULE directory.The original files are left in EAP_HOME/modules/system/layers/base/$MODULE.
The patching mechanism cripples the original jar files for security reasons.
This means that if you apply a patch which updates a module, the original
module's jar files are altered to be unusable. If the patch is rolled back, the
original files will be reverted back to a usable state.
check version after path applied:
|
[domain@192.168.1.12:29999 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /u03/local/opt/jboss-eap-6.2
JBoss AS
release: 7.3.4.Final-redhat-14 "Janus"
JBoss AS
product: EAP 6.2.4.GA
JAVA_HOME: null
java.version: 1.7.0_75
java.vm.vendor: Oracle Corporation
java.vm.version: 24.75-b04
os.name: Linux
os.version: 2.6.18-194.el5
[domain@192.168.1.12:29999 /]
|
Patch
history
You can
display the information about the history of the installed patches using the
patch history command. Additionally the patch info command can show you all
currently installed patches.
|
[domain@192.168.1.12:9999 /]patch info --host=master
{
"outcome" : "success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.2.4.CP",
"patches" : ["eap-624-bz1281945"],
"version" : "6.2.4.GA",
"addon" : null,
"layer" : {"base" : {
"cumulative-patch-id" :
"layer-base-jboss-eap-6.2.4.CP",
"patches" : ["BZ1281945"]
}}
}
}
|
This
information(history) are stored in the .installation
directory inside the JBOSS_HOME directory of the JBoss Application Server.
Be careful manipulating this directory, because changed files and the last
configuration to perform a rollback are stored in this directory. However, it
is always recommendable to make a backup before applying a patch.
|
[jboss@middlewaretech jboss-eap-6.2]$ cd
/u03/local/opt/jboss-eap-6.2/.installation
[jboss@middlewaretech .installation]$ ls -ltr
total 12
drwxr-xr-x 4 jboss dba 4096 Feb
1 16:14 layers
drwxr-xr-x 4 jboss dba 4096 Feb
1 16:14 patches
drwxr-xr-x 4 jboss dba 4096 Feb
1 16:21 identity.conf
[jboss@middlewaretech .installation]$ cd patches
[jboss@middlewaretech .installation]$ ls -l
drwx------.
4 jboss dba 4096 Feb 1 16:21 eap-624-bz1281945
drwx------. 4 jboss dba 4096 Feb
1 16:14 jboss-eap-6.2.1.CP
drwx------. 4 jboss dba 4096 Feb
1 16:14 jboss-eap-6.2.2.CP
drwx------. 4 jboss dba 4096 Feb
1 16:14 jboss-eap-6.2.3.CP
drwx------. 4 jboss dba 4096 Feb
1 16:14 jboss-eap-6.2.4.CP
|
Rollback the patches:
1. From the
Management CLI, use the patch info command to find the ID of the patch that is
to be rolled back.
- For cumulative patches, the patch ID is the value of the first cumulative-patch-id shown in the patch info output.
- Individual security or bug fix patch ID's are listed as the value of the first patches shown in the patch info output, with the most recently applied individual patch listed first.
2. From the
Management CLI, rollback the patch with the appropriate patch ID from the
previous step.
syntax : patch rollback --patch-id =
PATCH_ID --host=master --reset-configuration= TRUE --override-all
3. Restart the
JBoss EAP 6 server for the patch rollback to take effect:
-----------------------------------------------------------------------------------------------
Detailed Steps
-----------------------------------------------------------------------------------------------
Run the rollback command:
|
[domain@10.128.157.7:9999 /] patch rollback
--patch-id=jboss-eap-6.2.4.CP --host=master --reset-configuration=true --override-all
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
|
When the patch is roll backed, the
application server/host requires a restart, also executable with the CLI.
|
[domain@192.168.1.12:9999 /]
/host=master:shutdown(restart=true)
{"outcome" => "success"}
[domain@192.168.1.12:9999 /]
|
No comments:
Post a Comment