This chapter describes how you maintain your deployment and perform housekeeping.
Backup can be done on a set of different levels:
Processing Server and Signaling Server
Administration client
Domain configuration
To back up a Processing Server or a Signaling Server, back up all the files located in the following directory:
Oracle_home/ocsb62/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 involves backing up the following:
The Administration Server
The Scripting Engine
To back up an administration client, back up all the files located in the following directory:
Oracle_home/ocsb62/admin_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 administration client.
See "Archiving and Cleaning Up Log Files" for information on backing up log files.
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
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 Controller.
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/ocsb62/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/ocsb62/admin_server
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 log4j2.xml located in the directory:
Processing Servers and Signaling Servers: managed_server
Administration clients: admin_server
These directories are located under Oracle_home/ocsb62.
Oracle_home is the Oracle home directory you defined when you installed the product.
log4j2.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:
A patch is always associated with a specific OSGi bundle, whereas a patch set is not associated with one specific bundle and might contain a collection of unrelated patches. A patch or patch set can be targeted to a specific bundle or to a server. The delivery format is ZIP files.
The patches and patch sets are either delivered with a bundled copy of Oracle Universal Installer or as a input file to be used with a standard installation of Oracle Universal Installer.
Instructions are shipped with the patch or patchset.
The settings of each OSGi Bundle identify the bundle in the domain.
Table 12-1 describes OSGi Bundle properties.
Table 12-1 OSGi Bundle Properties
| Property | Description |
|---|---|
|
Name |
Symbolic name of the OSGi bundle. Format: Alpha-numeric characters. Case sensitive. No spaces in the name. |
|
Version |
Version number of the bundle. Format: Alpha-numeric. IP-address form or DNS name format. |
|
State |
The state of the bundle:
|
|
Start Level |
OSGi start level of the bundle Format: Numeric |
The following sections describe how you can manage OSGi bundles with the Administration Console and Java MBeans.
To access the Bundles Configuration screen:
In the domain navigation pane, expand OCSB and do one of the following:
Expand Signaling Tier and then expand Domain Management
Expand Processing Tier and then expand Domain Management
Select Packages.
The Packages configuration pane displays the properties described in Table 12-1.
Typing a package name into the Filter field displays a filtered list of packages.
Before you install a bundle in the domain, you must extract a copy of the bundle in the Domain Configuration Directory.
To install a bundle:
In the Bundles screen, click Install.
The Install dialog box is displayed.
In the Location column, type the location from where you extracted the bundle.
In the Start Level column, type a digit to indicate the level, then click Apply.
The new OSGi Bundle now appears in the Bundle list.
Before you uninstall a bundle, you must stop the bundle. See "Stopping a Bundle" for instructions.
To uninstall a bundle:
From the Bundle list, select the check box corresponding to the bundle you want to uninstall.
Click Uninstall.
The selected OSGi Bundle is removed from the list. The bundle is not deleted from the Configuration Directory.
To start a bundle:
In the Bundle list, select the check box corresponding to the bundle you want to start.
Click Start.
To stop a bundle:
In the Bundle list, select the check box corresponding to the bundle you want to stop.
Click Stop.
You can manage OSGi Bundles through JMX using the DeploymentServiceMBean, which exposes operations for installing and deploying these bundles.