Installing Maintenance Updates and Service Packs
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This section includes the following quick-reference aids, which are provided to guide you through the steps to complete two basic tasks and to explain the icons and labels used in the graphical interface:
This section provides a quick-reference aid that guides you through the steps of retrieving and applying a private patch that BEA Customer Support has provided for you.
The quick-reference aid described in this section is available at the following URL as a downloadable PDF file that is optimized for printing. To download this aid: |
To retrieve and apply a private patch, complete the following steps.
Smart Update provides a mechanism for capturing information about your BEA product installation that you can send to BEA Customer Support when reporting a problem. This information is called a maintenance snapshot. This section guides you through the steps of creating a maintenance snapshot.
The quick-reference aid described in this section is available at the following URL as a downloadable PDF file that is optimized for printing. To download this aid: |
To generate a maintenance snapshot, complete the following steps.
If you want to limit the scope of a class or library path patch to a specific domain or server, you need to:
This section provides a quick-reference aid that shows how to complete these steps, and uses the example of a test engineer who has downloaded a patch and plans to test the patch in a QA domain before incorporating the patch into a production domain.
The quick-reference aid described in this section is available at the following URL as a downloadable PDF file that is optimized for printing. To download this aid: |
To create a custom patch profile and point a domain or server at the patches applied to the profile, complete the following steps:
Example: The test engineer wants to run the QA domain at the same patch maintenance level as the production system, but with the addition of the patch downloaded in step 2. So the engineer creates the custom patch profile, QADomainProfile, and clones the contents of the default patch profile to it. Later she will apply the downloaded patch to this custom patch profile.
Note that any existing installation-wide patches that have already been applied to the target installation are included in the custom patch profile by default.
After you click Create, the custom patch profile is displayed in a tab adjacent to the tab for the default patch profile.
Example: The test engineer now applies the patch that was downloaded in step 2 to the QADomainProfile custom patch profile.
domain_home
represents the path to the domain's root directory.
To point the following at patches applied to the custom patch profile . . . | |
---|---|
Example: Because the test engineer needs to point the QA domain to the custom patch profile, she opens the setDomainEnv.cmd
script, which sets the environment for all servers in that domain only. Unless you need to limit the scope of a patch to a specific server instance, we generally recommend that you choose the setDomainEnv
for pointing to custom patch profiles.
Example: The particular patch being tested in the QA domain example contains patch JARs that are to be inserted into the beginning of the WebLogic system classpath. Therefore, the specific patch path variable that needs to be defined so that the domain points to the custom patch profile is PATCH_CLASSPATH
.
The test engineer locates the following line in the setDomainEnv.cmd
script:
@REM set PATCH_CLASSPATH=[myPatchClasspath] (windows)
She replaces this line with the following snippet that is generated in the bottom panel of the Start Script Editor:
SET PATCH_CLASSPATH=%BEA_HOME%\patch_weblogic910\profiles\QADomainProfile\sys_manifest_classpath\weblogic_patch.jar
The following example shows the change that the test engineer makes to the setDomainEnv.cmd
script.
setDomainEnv
script, make sure it is placed before the invocation to the commEnv
script.If you use custom scripts in your environment that do not invoke the WL_HOME
\common\bin\commEnv
script, or any of the other default scripts produced by the Configuration Wizard, you also need to modify the statements in your scripts that set the class and library paths for your environment so that the environment variables you have defined are properly inserted into those statements.
For example, to set the WebLogic system classpath so that patch JARs in a custom patch profile supersede same-named classes appearing later in the classpath, add the PATCH_CLASSPATH
variable as follows, shown in bold:
set WEBLOGIC_CLASSPATH=
%PATCH_CLASSPATH%;%JAVA_HOME%\lib\tools.jar;
%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%WL_HOME%\server\lib\webservices.jar
Example: When the test engineer approves the patch that has been tested in the QA domain, the patch can then be promoted for use in the production domains. To promote the patch, the test engineer does the following:
Table 1 provides a key to the graphical symbols and labels used throughout the Smart Update graphical interface.
The quick-reference summary described in this section is available at the following URL as a downloadable PDF file that is optimized for printing. To download this summary: |
![]() ![]() |
![]() |
![]() |