Upgrade Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Upgrade Overview

This section provides an overview of the process for upgrading AquaLogic Service Bus 2.1 to 2.5.

AquaLogic Service Bus 2.1 runs on WebLogic Server 9.1. AquaLogic Service Bus 2.5 runs on WebLogic Server 9.2.

 


Comparing In-Place and Migration Upgrade Methods

There are two types of upgrades that you can do from AquaLogic Service Bus 2.1 to 2.5: In-place Upgrade and Migration Upgrade.

For In-place Upgrade, a wizard is available to help you with the upgrade process. It does not do everything; there are still manual steps involved. However, security-related information is already in place in the new domain, along with JMS connection factories, so this method can be easier.

An advantage of doing an in-place upgrade is that fewer manual steps are required than when you do a migration upgrade. The additional effort and number of manual steps for a migration upgrade depend on how much security information must be exported from the old domain and imported into the new one, the number of proxy services, the number of JMS connection factories to be recreated, and so on.

 


Which Upgrade Method Should I Use?

The choice you make depends on your use case. If you have a 2.1 domain in a development environment, you have a large number of proxy services and connection factories, and you want to test the domain in a 2.5 environment, then select the in-place method of upgrading your domain.

If, on the other hand, you have a working 2.1 domain that needs to remain intact and running while you upgrade to 2.5, then BEA recommends that you use the migration upgrade method. You can leave the 2.1 environment up and running while you test a new 2.5 domain into which you import the 2.1 configuration, security data, and so on. When you are satisfied that the new domain is working properly, you then put it into production.

 


Improved Support for Validation in 2.5

When you import credential management into an AquaLogic Service Bus 2.5 domain, it becomes part of the session. Note that this behavior is different from that in a 2.1 domain; in 2.1, credential management was outside a session. This enables 2.5 to do more thorough validation than was possible in 2.1. Thus errors that were reported at run time in AquaLogic Service Bus 2.1 are caught at design time in AquaLogic Service Bus 2.5.

After the credential management configuration is imported into 2.5, any changes must be made through the AquaLogic Service Bus 2.5 Console and not through the WebLogic Server Administration Console.

In-Place Upgrade and Migration Upgrade describe in-place and migration upgrade procedures. Upgrade Considerations describes various differences between AquaLogic Service Bus 2.1 and 2.5 that you should consider when upgrading from 2.1 to 2.5.


  Back to Top       Previous  Next