Universal Agent for SOA for Windows - Pre-Installation - Upgrade Backups
Universal Agent for SOA for Windows - Pre-Installation / Upgrade Backups
Before upgrading to the latest release of Universal Agent for SOA, we recommend stopping any active Universal Application Container (UAC) Server instances (via the Universal Control utility or by stopping the local Universal Broker). If the UAC Server is active during the upgrade, the Windows Installer will require a reboot of the system. Also, stopping the UAC Server before backing up the files listed below will ensure the latest copies of each are captured.
The installation process overwrites the current files (exception: see the Note for Log4jConfiguration.xml in the following table), effectively removing your modifications. Backing up these files will optimize the time it takes you to get up and running after installing or upgrading.
The following table identifies the files - and their locations - that should be backed up or copied before you install a new release or upgrade a current release.
File |
Location |
|---|---|
UAC.xml File |
|
Log4jConfiguration.xml File |
Note The installation process does not overwrite Log4jConfiguration.xml files. |
JMS Provider Client Jar Files |
Note The names of the jar files differ depending on which JMS Provider you are using. |
JMS Provider Client Properties Files |
Note These are suggested locations; you can place these files anywhere on the files system. If you have located these files under the uai directory, you should back them up. |
Payload Files |
Normally, payload files should be located on the host system where Universal Command Manager is installed. Note You can place these files anywhere on the files system. If you have located these files under the uai directory, you should back them up. |