/
Universal Agent for SOA for UNIX - Pre-Installation-Upgrade Backups

Universal Agent for SOA for UNIX - Pre-Installation-Upgrade Backups

Owned by Stonebranch (Deactivated)
Jan 31, 2024

Universal Agent for SOA for UNIX - Pre-Installation / Upgrade Backups

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 list 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

/etc/universal

Log4jConfiguration.xml File

/etc/universal (UAC)
/etc/universal (UAI)
 

Note

The installation process does not overwrite Log4jConfiguration.xml files.

JMS Provider Client Jar Files

/opt/universal/uac/container/webapps/axis2/WEB-INF/lib
 

Note

The names of the jar files differ depending on which JMS Provider you are using.

JMS Provider Client Properties Files

/opt/universal/uai/xml
 

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.
 
If you have chosen to store them elsewhere, the suggested location is:
 
/opt/universal/uai/xml
 

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.