Skip Headers
Oracle® Communications Service Broker System Administrator's Guide
Release 6.0

Part Number E23523-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

16 Maintaining Oracle Communications Service Broker

This chapter describes how you maintain your deployment and perform housekeeping.

Backing Up Your Installation

Backup can be done on a set of different levels:

Backing Up a Processing Server or Signaling Server

To back up a Processing Server or a Signaling Server, back up all the files located in the following directory:

Oracle_home/ocsb60/managed_server

Oracle_home is the Oracle Home directory you defined when you installed the product.

You should perform a backup immediately after installing, upgrading, or adding a patch to your Processing Server or Signaling Server.

See "Archiving and Cleaning Up Log Files" for information on backing up log files.

Backing Up an Administration Client

Backing up an administration client involves backing up the following:

  • The Standalone Administration Console

  • The Web Administration Console Server

  • The Scripting Engine

To back up an administration client, back up all the files located in the following directory:

Oracle_home/ocsb60/admin_console

Oracle_home is the Oracle Home directory you defined when you installed the product.

You should perform a backup immediately after installing, upgrading, or adding a patch to your administration client.

See "Archiving and Cleaning Up Log Files" for information on backing up log files.

Backing Up a Domain Configuration

To back up your domain configuration, back up all the files in your domain configuration directory. This directory was defined when you created the domain.

Perform backups on a regular basis and always immediately after:

  • Updating or changing any configuration

  • Adding or removing a Processing Server or Signaling Server from your installation

  • Upgrading a Processing Server or Signaling Server

  • Adding a patch to a Processing Server, Signaling Server, or an administration client

Backing Up Oracle Home

To back up your full Oracle Home, back up 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.

Archiving and Cleaning Up Log Files

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/ocsb60/managed_server

Oracle_home is the Oracle Home directory you defined when you installed the product.

Log files for the administration clients are by default stored under the directory:

Oracle_home/ocsb60/admin_console

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:

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:

These directories are located under:

Linux and Solaris: Oracle_home/ocsb60

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 Log4J documentation at:

http://logging.apache.org/log4j/