Oracle® Communications Service Broker System Administrator's Guide Release 5.0 Part Number E15183-01 |
|
|
View PDF |
This chapter describes how you maintain your deployment and to perform housekeeping. For details, see
Back-up can be done on a set of different levels:
Processing Server and Signaling Server level
Administration client level
Domain configuration level
To back-up a Processing Server or Signaling Server, back-up everything under the following directory:
Oracle_home/axia/managed_server
Where Oracle_home is the Oracle Home directory you defined when you installed the product.
You should do a backup immediately after you installed, upgraded, or patched your Processing Server or Signaling Server.
If you want to backup any log files, see "Archiving and Cleaning Up Log Files".
When backing up an administration client, the following is backed up:
The Stand-alone Administration Console
The Web administration Console server
The Scripting Engine
To backup an administration client, back-up everything under the following directory:
Oracle_home/axia/admin_console
Where Oracle_home is the Oracle Home directory you defined when you installed the product.
You should backup immediately after you install, upgrade, or patch your administration client.
If you want to backup any log files, see "Archiving and Cleaning Up Log Files".
To backup your domain configuration, backup everything in your domain configuration directory. This directory was defined when you created the domain.
You should perform backups on a regular basis and always immediately after you:
Update or change any configuration.
Add or remove a Processing Server or Signaling Server from your installation.
Upgrade a Processing Server or Signaling Server.
Patch a Processing Server, Signaling Server, or an administration client.
To backup your full Oracle Home, backup all files and directories under Oracle_home.
Oracle_home is the Oracle Home directory you defined when you installed Service Broker.
Processing Servers, Signaling Servers, and administration client installations, including log files, are also backed up when you back up Oracle_home.
Domain configurations are backed up if they are stored in an Oracle_home subdirectory.
Log files are stored in the file system of your servers and administration clients.
You should archive and clean up your log files on a regular basis.
Log files for servers are by default stored directly under the directory:
Oracle_home/axia/managed_server
Where Oracle_home is the Oracle Home directory you defined when you installed the product.
Log files for the administration clients are by default stored in the directory:
Oracle_home/axia/admin_console
Where Oracle_home is the Oracle Home directory you defined when you installed the product.
Log files are stored using a roll-over pattern.
The file currently in use, current_log_file is named:
server.log for Processing Servers and Signaling Servers
console.log for administration clients
When current_log_file reaches a given size, the suffix .sequence_number is added to the file name and a new current_log_file is created. The suffix .sequence_number is a sequence number that is increased each time the file is rolled-over.
Log files with the suffix sequence_number can be archived for future reference and deleted. The roll-over occurs when the log-file reaches a size of 100 KB.
The default log files are controlled by the configuration file named log4j.xml located in the directory:
Processing Servers and Signaling Servers: managed_server
Administration clients: admin_console
These directories are located under:
Linux and Solaris: Oracle_home/axia
Where Oracle_home is the Oracle Home directory you defined when you installed the product.
log4j.xml is a standard Log4J configuration file that can be changed to suit your needs. For detailed information on Log4J and the configuration file, see the Log4J documentation at: