Best practices for applying SOA-P 5.3.1 2014 roll-up patch 1 - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

In the readme file of the the patch file BZ-1073034.zip of Roll up patch SOA_5.3.1_1_2014 [1] , there is a list of many files in .jar format. And some in the following .xml, .java, .class, .properties, .sql etc formats as well. Do the users need to replace them all in one go?
It seems there are a lot of such files to patch or replace in one go. So can users just patch one type of files first, like .jar and then do another batch on the next day and so on and so forth?
Is there a link for best practice for doing patching like this one or in general?

[1] Roll up patch SOA_5.3.1_1_2014

Environment

Red Hat JBoss SOA Platform (SOA-P)
- 5.3.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)