You can run the command-line Content Engine Upgrader to upgrade the
items that you selected for upgrade in the upgrade status file upgrade.xml.
Before upgrading an object store, the command-line Content Engine Upgrader takes the object
store offline. After upgrading an object store, the Upgrader updates
the corresponding status value for the object store in the upgrade.xml file.
To perform the upgrade:
- Log on to the system where the command-line Content Engine Upgrader is installed as
the ce_upgrade_user.
- Navigate to the ce_install_path\tools\upgrade
directory, which contains CE35_to_50Upgrader.bat.
- Optional: To see the available options, run
the Upgrader tool from a command line, as follows: CE35_to_50Upgrader.bat
-h
- Run the Upgrader tool by entering
the following command:
CE35_to_50Upgrader
-i upgrade.xml -r
The -r flag
is optional. If you include it in the command, the tool generates
an HTML report.
Important: The Upgrader upgrades
only the items that have an initial status of ReadyToUpgrade and a
SelectedForUpgrading value of yes.
The Upgrader sends a status message to the command
line and to a log4j logging system as it attempts to upgrade each
item. If the upgrade for a specific item fails, the Upgrader stops.
- If the upgrade fails for an item, complete the following
steps:
- Use the information (exception code and stack trace)
in the command-line output or the log4j file
to correct the error.
- Edit the upgrade.xml file to replace
any Status value of UpgradeStarted or UpgradeFailed to ReadyToUpgrade.
- If the object store add-on upgrade takes longer than
10 minutes and the upgrade fails, note the exceptions in the log.
Increase your application server timeout settings.
Complete
the following steps:
- Increase your application server transaction timeout value. Make
a note of your existing values before you change them. Depending on
your hardware, you might need to increase the timeout value to as
much as 6000 seconds.
- IBM® WebSphere® Application Server
- Navigate to , and increase
the values for Total transaction lifetime timeout and
Maximum transaction timeout.
- Oracle WebLogic Server
- Increase the value for and the value for . Use the
same value for both settings.
- JBoss Application Server
- Edit the jboss-service.xml file to set the
value for <attribute name="TransactionTimeout">.
- Restart the application server.
- Restart the upgrade for the object store add-ons.
- After the upgrade completes successfully, you can reset the application
server timeout settings to the previous values.
- If the failure occurred due to an error after the database
upgrade has completed, then restore your database from backup.