Sun Java Communications Suite 5 Upgrade Guide |
Chapter 2
Upgrading Communications Suite Shared ComponentsThis chapter provides information on upgrading Communications Suite shared components.
Each Communications Suite product component depends on one or more locally shared libraries known as shared components. These shared components are installed automatically by the installer during initial product component installation. During the upgrade process, shared components are manually selected and installed, depending on the products you want to upgrade.
For Communications Suite products, you need to upgrade shared components explicitly, using the procedure described in this chapter.
The chapter contains the following sections:
Shared Component Upgrade OverviewUpgrading shared components to Communications Suite 5 should be done as part of a larger upgrade plan, as discussed in Chapter 1, "Planning for Upgrades." To ensure that you have a successful upgrade, read Chapter 1 carefully and prepare an upgrade plan that meets your needs.
This section covers the following topics
General Considerations
When upgrading shared components, consider the following issues:
- Operating System Issues. Perform any operating system upgrades, as described in Operating System Issues. For all platforms except for Solaris 10 OS, perform operating system upgrades before you upgrade shared components.
- Sequencing Guidelines. Review the sequencing guidelines listed in General Sequencing Guidelines. Typically, shared components are upgraded first. However, you should understand the entire sequence of your upgrade to Communications Suite 5 before beginning your upgrade process.
Solaris 10 Zone Considerations
Communications Suite can be deployed in a Solaris 10 multi-zone environment, however, there are some limitations due to shared component considerations.
The major consideration impacting the use of Communications Suite in a multi-zone environment is that a large number of shared components cannot be installed in sparse root zones because of the read-only file systems in sparse root zones. This limitation applies to those shared components whose base directory is /usr (a directory that by default is shared by the global zone).
The inability to install a number of Communications Suite shared components in sparse root zones means that to successfully install or to upgrade product components which have dependencies on such shared components into sparse root zones, the shared components must first be installed or upgraded in the global zone and propagated to non-global zones. The Communication Suite products should be installed or upgraded in the sparse zones.
When shared components are installed in and propagate from the global zone, then special care must be taken to maintain synchronization of shared components in all zones. Otherwise it would be possible for shared components of an earlier version in a non-global zone to be mixed with Communications Suite 5 shared components that have been propagated from the global zone.
Special care means following the practices recommended for the use of Communications Suite in a multi-zone environment (see Communications Suite and Solaris 10 Zones).
Special Upgrade ProceduresThis section provides special procedures needed for upgrading the following shared components:
Note
These procedures should be performed before upgrading component shared components described in Shared Component Upgrade Procedure.
J2SE Upgrade Procedures
Communications Suite 5 is certified for Java 2 Platform, Standard Edition (J2SE) Version 5.0 Update 6, identified here as J2SE 5.0 Update 6. (J2SE 5.0 is sometimes referred to as developer version 1.5.0).
You should not remove the previously installed J2SE Version 1.4.2 because other applications might depend on that version. Instead, make sure that your upgrade sets a symbolic link, /usr/jdk/entsys-j2se, to reference the Communications Suite 5 version. See the J2SE documentation for upgrade instructions.
You should maintain any pointers to J2SE 1.4.2 for those services that require the earlier version. Consult the appropriate product component documentation for information on how to maintain symbolic links to the earlier versions of J2SE.
When upgrading J2SE you might want to first shut down any services that depend on the currently installed J2SE. This is to avoid any problems that might arise with those services. If you do not shut down services that depend on J2SE, you should reboot your system after upgrading J2SE to 5.
Checking the J2SE Symbolic Link
You will need to check the symbolic link to the supported version of J2SE platform to ensure that Communications Suite services can find the correct J2SE runtime to use.
Check the symbolic link as follows:
ls -l /usr/jdk/entsys-j2se
lrwxrwxrwx 1 root other 7 Jul 7 23:18 ‘ -> /usr/jdk/instances/jdk1.5.0where /usr/jdk/instances/jdk1.5.0 is the default location.
Verifying the Current J2SE Version
To determine which version of J2SE your Communications Suite installation is using, run the following command, which verifies the version of J2SE referenced by the J2SE symbolic link:
/usr/jdk/entsys-j2se/bin/java -version
The outputs are shown in Table 2-1.
Common Agent Container Upgrade Procedures
If you are upgrading the common agent container (CAC) shared component in preparation for upgrading the Monitoring Framework (MFWK) software that can be used with Instant Messaging, the following section describes the procedure for upgrading common agent container packages for standalone systems.
- If the current installation uses custom configuration settings (for example, which ports are used) capture the configuration settings using the following commands:
On Solaris platforms:
/opt/SUNWcacao/bin/cacaoadm list-params
On the Linux platform:
/opt/sun/cacao/bin/cacaoadm list-params
The output will be similar to the following:
java-flags=-Xms4M -Xmx64M
jmxmp-connector-port=10162
snmp-adaptor-port=10161
snmp-adaptor-trap-port=10162
commandstream-adaptor-port=10163
retries=4The example above lists the default values. Note any nondefault settings for use in Step 5.
- On the Linux platform only, back up the SNMP security files.
mkdir /tmp/cacao_snmp
/bin/cp /etc/opt/sun/cacao/security/snmp/* /tmp/cacao_snmpThe security files for the Linux platform will be restored after applying Patch 120677-01.
- Stop common agent container processes using the following commands:
On Solaris platforms:
/opt/SUNWcacao/bin/cacaoadm stop
echo $?If the exit code is not 0, force the stop:
/opt/SUNWcacao/bin/cacaoadm stop -f
On the Linux platform:
/opt/sun/cacao/bin/cacaoadm stop
echo $?If the exit code is not 0, force the stop:
/opt/sun/cacao/bin/cacaoadm stop -f
- Upgrade the common agent container.
See Shared Component Upgrade Procedure.
- Apply any custom configuration settings previously captured in Step 1.
On Solaris platforms, use the following commands:
/opt/SUNWcacao/bin/cacaoadm set-param java-flags=Value
/opt/SUNWcacao/bin/cacaoadm set-param jmxmp-connector-port=Value
/opt/SUNWcacao/bin/cacaoadm set-param snmp-adaptor-port=Value
/opt/SUNWcacao/bin/cacaoadm set-param
snmp-adaptor-trap-port=Value
/opt/SUNWcacao/bin/cacaoadm set-param
commandstream-adaptor-port=Value
/opt/SUNWcacao/bin/cacaoadm set-param retries=ValueOn the Linux platform, use the following commands:
/opt/sun/cacao/bin/cacaoadm set-param java-flags=Value
/opt/sun/cacao/bin/cacaoadm set-param jmxmp-connector-port=Value
/opt/sun/cacao/bin/cacaoadm set-param snmp-adaptor-port=Value
/opt/sun/cacao/bin/cacaoadm set-param snmp-adaptor-trap-port=Value
/opt/sun/cacao/bin/cacaoadm set-param
commandstream-adaptor-port=Value
/opt/sun/cacao/bin/cacaoadm set-param retries=ValueOn the Linux platform only, restore the original SNMP security files you backed up in Step 2:
/bin/cp /tmp/cacao_snmp/* /etc/opt/sun/cacao/security/snmp/\
rm -rf /tmp/cacao_snmp- If you upgraded J2SE to J2SE Version 5, run the rebuild-dependencies utility:
On Solaris platforms:
/opt/SUNWcacao/bin/cacaoadm rebuild-dependencies
On the Linux platform:
/opt/sun/cacao/bin/cacaoadm rebuild-dependencies
The output of this command will be:
Property updated: [java-home].
Property updated: [jdmk-home].
Property updated: [nss-lib-home].
Property updated: [nss-tools-home].- Restart common agent container services:
cacaoadm start
- Verify the upgrade of common agent container:
cacaoadm status
cacaoadm verify-configuration
Shared Component Upgrade ProcedureTo upgrade the shared components in the Communications Suite, you will need to determine all the required shared components for your deployment and manually upgrade these components to their Communications Suite 5 versions.
Manual upgrade procedures rely on the following two upgrade technologies:
Table 2-1 shows the upgrade patches that are available for each shared component when upgrading to Communications Suite 5 from 2005Q4, 2005Q1, or 2004Q2.
Because patching technology is not available to upgrade Communications Suite on the Linux platform, you typically upgrade Linux shared components by replacement of RPM packages. However, some shared components deliver RPM packages as patches.
Table 2-1 shows the shared components that use replacement of packages when upgrading to Communications Suite 5 from 2005Q4, 2005Q1, and 2004Q2.
The general steps you take to upgrade shared components are discussed below:
- Create an upgrade plan determining the products in the Communications Suite that you plan to upgrade.
In addition, think about any Java Enterprise System products you need to update that are not included in the Communications Suite distribution or documentation (for example, Sun Java System Application Server). For information on upgrading those products, you will need to read the Sun Java Enterprise System Upgrade Guide.
Review the earlier sections in this overview for information on developing an upgrade plan. You can also refer to Upgrade Planning for additional information.
- Determine the shared components specified in your upgrade plan. See Table 2-2.
Note
In Table 2-2, the trailing two digits in the patch ID specify the revision number for the patch. A higher revision number indicates a newer version.
Table 2-2 lists the minimum revision required for upgrade. If newer revisions of the patch become available, you should apply those revisions instead of the ones listed in the table.
The full names of shared components listed in Table 2-2 are provided in Communications Suite Shared Components.
- Apply the appropriate platform-specific patch required for each product in the Communications Suite that you are upgrading. These patches are available at: http://sunsolve.sun.com/pub-cgi/show.pl?target=tous
- In some cases, Linux RPM packages are bundled as patches that can be downloaded from the same site. Check http://sunsolve.sun.com/pub-cgi/show.pl?target=tous for more information.
Table 2-2 Upgrade Technologies to Upgrade Communications Suite Shared Components from Previous Versions
Shared Component
Communications Suite Product
Solaris 8
SPARCSolaris 9
SPARCSolaris 10
SPARCSolaris 9
x86Solaris 10
x86Linux
ICU
Messaging Server; Calendar Server
116103-09
114677-11
119810-02
114678-11
119811-02
sun-icu-3.2.1-2.i386.rpm
IM SDK
Instant Messaging
118789-27
118789-27
118789-27
118790-27
118790-27
118791-27
J2SE
Delegated Administrator
Install J2SE 5.0 as described in J2SE Upgrade Procedures.
JSS
Instant Messaging
119209-05
119211-05
119213-06
119212-05
119214-06
Replace packages
LDAP J SDK
Instant Messaging
119725-02
Replace packages
LIBMTMALLOC
Messaging Server; Calendar Server
111308-05
115697-02
-
115698-02
-
-
LIBCPLUSPLUS
Messaging Server; Calendar Server
-
111711-16
119963-03
111713-13
119964-03
-
MFWK
(Note the dependency on CAC)
Instant Messaging
119803-02
119804-02
Replace packages
See the Java Enterprise System Upgrade Guide (http://docs.sun.com/doc/819-6553) for more information on shared component dependencies for MFWK and CAC.
NSPR
Calendar Server, Instant Messaging,Messaging Server
119209-05
119211-05
119213-05
119212-05
119214-05
Replace packages
NSS
Messaging Server, Calendar Server, Instant Messaging
See Additional NSS Instructions for details.
PATCHUTILS
Messaging Server; Calendar Server
-
-
119254-26
-
119255-25
-
PKGINSTALL
Calendar Server
-
113713-21
-
114568-20
-
-
SASL
Messaging Server, Calendar Server
115328-02
115342-02
119345-01
115343-02
119346-01
sun-sasl-2.19-4.i386.rpm
Additional NSS Instructions
You only need to apply the NSS patches listed in Table 2-3 if the package version of SUNWtls is the following:
To check the package version of SUNWtls, use the following command:
Linux RPM Instructions
Some Linux rpms are not created into patches. Therefore, you need to manually apply the rpm.
The following rpms should be used to upgrade the ICU and SASL shared components:
To upgrade existing Linux shared component rpms to the following shared component rpms, cd into the following directory:
Product/shared_components/Packages
and then use the following command to apply the new rpms:
If you are not upgrading Application Server to version 8.x, you also need to complete the following steps: