WELLS FARGO BANK

WebLogic 10.3.5.0.7 Patching for

WebConnect Environment (Windows)

8/21/2014

Table of Contents
Preparing to Install Oracle WebLogic Server Patch Set Update 10.3.5.0.7 ............................................ 3
Installing Oracle WebLogic Server Patch Set Update 10.3.5.0.7 ............................................................ 3
Verification.......................................................................................................................................... 4
Post-Installation Instructions .............................................................................................................. 4
Uninstalling Oracle WebLogic Server Patch Set Update 10.3.5.0.7 ........................................................ 5
Post-Uninstallation Instructions ......................................................................................................... 5

Preparing to Install Oracle WebLogic Server Patch Set Update 10.3.5.0.7

1. Copy Files from https://wmgsvn.wellsfargo.com/svn/trustsystemstechnology/SharedJEE/trunk/WebLogic/Patches/
2. WebLogic Server Patch Set Update (PSU) can be applied on a per-domain basis (or on a
more fine-grained basis), Oracle recommends that PSU be applied on an installationwide basis.
3. PSU applied to a WebLogic Server installation using this recommended practice affect
all domains and servers sharing that installation.
4. Login as same "user" with which the component being patched is installed.
5. Stop all WebLogic servers.
6. Stop NodeManagers if any are running.
7. From Control Panel, Select Administrative tools - > Services
8. Stop the Oracle NodeManager service "Oracle WebLogic NodeManager
(C_oracle_Middleware_wlserver_10.3)"
9. Remove any previously applied WebLogic Server Patch Set Update and associated
overlay patches.
10. The windows servers which will be patched as part of this activity are advww00a0049,
acvwa00a0031, arvwa00a0113 and apvwa00a0113.
Installing Oracle WebLogic Server Patch Set Update 10.3.5.0.7

1. Note down the %MW_HOME% and %WL_HOME% for future steps

For this installation I used
MW_HOME=C:\oracle\Middleware
WL_HOME=C:\oracle\Middleware\wlserver_10.3

Open a Dos command prompt.

cd %MW_HOME%\wlserver_10.3\server\bin
setWLSEnv.cmd
java weblogic.version

OUTPUT:
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
Use 'weblogic.version -verbose' to get subsystem information
Use 'weblogic.utils.Versions' to get version information for all modules

1. Unzip p16088411_1035_Generic.zip to %MW_HOME%/utils/bsu/cache_dir or any

local directory. If the cache_dir is not there, please create it. Also Make sure to rename
patch_catalog_xxxxx.xml to patch_catalog.xml.
- Note: You must make sure that the target directory for unzip has required write
and executable permissions for "user" with which the component being patched
is installed.
2. In the command prompt
Navigate to the %MW_HOME%/utils/bsu directory.
cd %MW_HOME%/utils/bsu
3. Execute
bsu.cmd -install -patch_download_dir=%MW_HOME%/utils/bsu/cache_dir patchlist=L5TD -prod_dir=%WL_HOME% -log=bsu.log
Where, WL_HOME is the path of the WebLogic home.
Example
C:\oracle\MIDDLE~1\utils\bsu>bsu.cmd -install patch_download_dir=%MW_HOME%/utils/bsu/cache_dir -patchlist=L5TD prod_dir=%WL_HOME% -log=bsu.log
Checking for conflicts..
No conflict(s) detected
Installing Patch ID: L5TD..
Result: Success
Verification:
C:\oracle\MIDDLE~1\utils\bsu>java weblogic.version

Output
WebLogic Server 10.3.5.0.7 PSU Patch for BUG16088411 Mon Apr 01 15:13:52 IST 2013
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
Use 'weblogic.version -verbose' to get subsystem information
Use 'weblogic.utils.Versions' to get version information for all modules
Post-Installation Instructions:
1. Restart Node Managers and all WebLogic servers.

Uninstalling Oracle WebLogic Server Patch Set Update 10.3.5.0.7:

1.
2.
3.
4.

Stop all WebLogic Servers

Navigate to the %MW_HOME%/utils/bsu directory.
Execute bsu.sh -remove -patchlist= L5TD -prod_dir=%WL_HOME%
Verify the version.

Post-Uninstallation Instructions:
1. Restart Node Managers and all WebLogic Servers.