|
| |
| Sun Java Enterprise System 2005Q1 Upgrade and Migration Guide | |
Chapter 1
Planning for UpgradesThis chapter describes the tasks and decisions required for upgrading the Sun Java™ Enterprise System (Java ES) software.
This chapter contains the following sections:
Determining Your Upgrade NeedsThe following sections provide information to help you make decisions on how best to upgrade your particular set of component products:
Choosing an Upgrade Method
The method of upgrading your particular component product(s) to Java Enterprise System 2005Q1 levels depends on the version currently on your system:
Previous Java Enterprise System versions - To upgrade your product from previous Java Enterprise System versions find the appropriate procedure in Upgrading from Previous Java Enterprise System Versions.
Pre-Java Enterprise System versions - To upgrade your product from pre-Java Enterprise System versions find the appropriate procedure in Upgrading Components from Versions Predating Java Enterprise System.
Understanding Component Product Dependencies
To determine the best sequence for upgrading Java Enterprise System, it is important to understand how the component products depend on each other. Table 1-1 shows the dependencies between the Java Enterprise System component products (not including dependencies on shared components, such as J2SE). Using this table, you can list or diagram the chain of dependencies in your upgrade set. The left column lists the component products, the middle column lists what is required for each component product, and the right column indicates whether or not the required components must be installed on the local machine.
Access Manager, Communications Express, and Portal Server all require a web container. Any can use either Application Server or Web Server as a web container. Access Manager and Portal Server can also use BEA WebLogic Server or IBM WebSphere Application Server.
Understanding Shared Product Dependencies
Table 1-2 shows the dependencies between the Java Enterprise System component products and shared components, such as J2SE. Using this table, you can list or diagram the chain of dependencies in your upgrade set. The left column lists the component products and the middle column lists what shared component is required for each component product.
For a complete listing and description of shared components see Upgrading Shared Components.
Checking for Existing Software
It is a good idea to verify the versions of installed software before upgrading.
You can use commands such as prodreg and pkginfo to examine installed software.
Note
Do not rely only on the installer for this information. You must also perform an independent survey of the system to determine what software is currently installed.
Preparing for UpgradesIn preparing to upgrade your servers, note the following:
- Prior to upgrading your product(s), read the Java Enterprise System 2005Q1 Release Notes at http://docs.sun.com/doc/819-0057 and the release notes for each product to be upgraded.
- Find the patches you need at the SunSolve web site:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
- Back up all data prior to upgrading.
- Do not run Java Enterprise System 2005Q1 and any pre-Java Enterprise System 2005Q1 component products on the same system.
- All components installed in a single system, must be upgraded to the same Java Enterprise System 2005Q1 level.
- Upgrade shared components before the other Java Enterprise System component products (see Upgrading Shared Components).
- To see a listing of previous Java Enterprise System component products and their revisions see Previous Java Enterprise System Releases.
- Apply the latest Solaris patch clusters appropriate to your system (see Upgrading Access Manager).
- If you have a Sun Cluster installation you may need to apply: Sun Cluster 3.1 patch info doc for Solaris 8 users or Sun Cluster 3.1 Patch Info Doc for Solaris 9 users. To access the PatchPro tool for Sun Cluster software, go to http://www.sun.com/PatchPro/, click “Sun Cluster,” then choose either Interactive Mode or Expert Mode. Follow the instructions in the PatchPro tool to describe your cluster configuration and download the patches.
Upgrade Dependencies
Many component products depend on other products to be upgraded before they are upgraded. See Determining Your Upgrade Needs for information necessary to list or diagram the chain of dependencies that determines your upgrade process.
The following list the products in the order that they should be upgraded. Find the products appropriate to your situation and upgrade them in this order.
- Shared Components (See Upgrading Shared Components)
- Sun Cluster (See Upgrading Sun Cluster)
- Administration Server (See Upgrading Administration Server, Directory Server, and Directory Proxy Server)
- Directory Server (See Upgrading Directory Server)
- Directory Proxy Server (See Upgrading Directory Proxy Server)
- Web Server (See Upgrading Web Server)
- Message Queue (See Upgrading Message Queue)
- Application Server (See Upgrading Application Server)
- Access Manager (formerly Identity Server) (See Upgrading Access Manager
- Messaging Server (See Upgrading Messaging Server)
- Calendar Server (See Upgrading Calendar Server)
- Communications Express (See Upgrading Communications Express)
- Portal Server (See Upgrading Portal Server)
- Instant Messaging (See Upgrading Instant Messaging)
- Mobile Access Upgrading Mobile Access
- Sun Cluster agents (See Upgrading Sun Cluster)
Next StepsProceed to the appropriate upgrade chapter: