This chapter describes how to manage Oracle Communications applications using Oracle Application Management Pack for Oracle Communications with Oracle Enterprise Manager Cloud Control.
Application Management Pack for Oracle Communications provides management capabilities for the following Oracle Communications applications:
Oracle Communications Billing and Revenue Management
Oracle Communications Elastic Charging Engine
Oracle Communications Pricing Design Center
Oracle Communications Pipeline Configuration Center
Oracle Communications Network Charging and Control
Oracle Communications Order and Service Management
Oracle Communications Unified Inventory Management
Oracle Communications ASAP
See "Supported Applications" for supported Oracle Communications application versions.
You perform the following actions in Enterprise Manager Cloud Control:
Actions supported vary by application. Not all actions are supported by all applications. Table 4-1 lists supported actions for each application.
See "Supported Applications" for information on supported Oracle Communications applications and versions.
Table 4-1 Supported Application Management Pack for Communications Actions
| Application | Discover | Provision | Process Control | Patch | Monitor | View Topology | View/Edit Configuration | Manage Alerts |
|---|---|---|---|---|---|---|---|---|
|
Billing and Revenue Management |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Elastic Charging Engine |
Yes |
No |
No |
No |
Yes |
Yes |
No |
Yes |
|
Pricing Design Center |
No |
Yes |
No |
No |
No |
No |
No |
No |
|
Pipeline Configuration Center |
No |
Yes |
No |
No |
No |
No |
No |
No |
|
Network Charging and Control |
Yes |
No |
No |
No |
Yes |
No |
No |
Yes |
|
Order and Service Management |
Yes |
Yes |
No |
No |
Yes |
Yes |
No |
Yes |
|
Unified Inventory Management |
Yes |
Yes |
No |
No |
Yes |
Yes |
No |
Yes |
|
ASAP |
Yes |
Yes |
No |
No |
Yes |
Yes |
No |
Yes |
You can provision one or more of the applications listed above using a single Communications Suite Installation Procedure execution. For example, you can provision Oracle Communications applications that form the Order to Cash solution at the same time.
Discovery enables adding already installed Oracle Communications applications in your environment to Enterprise Manager Cloud Control. Application Management Pack for Oracle Communications provides automatic and guided discovery modules for supported Oracle Communications applications and components running on managed host targets. After discovery, you promote new Oracle Communications targets to a managed status.
See "Adding Oracle Communications Targets" for information on using guided discovery to add existing Oracle Communications targets to your Enterprise Manager Cloud Control instance.
See "Discovering Elastic Charging Engine Targets Automatically" and "Discovering Network Charging and Control Targets Automatically" for information on setting up and using automatic discovery.
See "Adding Existing Oracle Communications Applications Using Monitoring Properties" for information on adding Oracle Communications targets not covered by guided or auto discovery.
The Network Charging and Control automatic discovery process only adds targets for known Network Charging and Control nodes. You must add an aggregate Network Charging and Control node manually using the Enterprise Manager Command Line Interface (emcli) to properly monitory Network Charging and Control instances.
Application Management Pack for Oracle Communications uses this aggregate node for system level management of existing Network Charging and Control Service Management System, Voucher and Wallet Server and Service Logic Controller nodes.
To manually add a Network Charging and Control aggregate node:
Connect to the management server with a secure shell as a privileged user.
Change directory to the oms/bin directory of your Enterprise Manager Cloud Control installation.
Install_directory/oms/bin
Set up the emcli connection to your Enterprise Manager Cloud Control management server using the following command:
./emcli setup -url=https://host:port/em -username=sysman -password=password -trustall
Add the aggregate target using the following emcli command:
./emcli add_target -host="hostname" -name="aggregate_target_name" -type="comms_ncc" -properties="nccDBHost:localhost;nccDBPort:1521;nccDBSID:smf;nccDBUserName:smf;nccDBPassword:db_password;nccDBServiceName:smf"
where:
hostname is the name of the Network Charging and Control host
aggregate_target_name is the name of the new aggregate node
db_password is the Network Charging and Control database user's password.
Specify the correct information for your environment if you are not using the default user, SID and service name values.
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then All Targets.
Confirm that the new aggregate target has been created in the list of comms_ncc targets.
You provision supported Oracle Communications applications, components and suite configurations using the Communications Suite Installation Procedure in Enterprise Manager Cloud Control. The procedure requires an understanding of the installation parameters of each application and assumes that all prerequisites are met.
See "Preparing New Hosts for Application Provisioning" for more information on ensuring application hosts are ready.
The Communications Suite Installation Procedure supports:
The Communications Suite Installation Procedure requires that application and component hosts exist as managed host targets in your Enterprise Manager Cloud Control environment. See "Understanding Oracle Communications Targets" for information on adding new and existing hosts as managed targets.
Note:
The installation procedure does not support provisioning of applications onto Oracle RAC databases.You can save your provisioning configuration during the Choose Targets step. See "Saving Provisioning Configurations" for information about saving your procedure configurations.
This section describes provisioning the following Oracle Communications applications:
ASAP
Order and Service Management
Pipeline Configuration Center
Pricing Design Center
Unified Inventory Management
See the following sections for information on provisioning other Oracle Communications applications and suite solutions:
To provision an Oracle Communications application using Enterprise Manager Cloud Control:
Log in to the Enterprise Manager Cloud Control administration console on your management server as a privileged user.
Click Enterprise, then Provisioning and Patching, and then Procedure Library.
In the Deployment Procedure Manager, select Communications Suite Installation Procedure.
Click Launch.
Under Choose Targets, click Add to select the system types of Oracle Communications target system to provision. Supported system types include:
ASAP Single Node
OSM 2 Node Cluster
OSM Single Node
PCC Single Node
PDC Single Node
UIM 2 Node Cluster
UIM Single Node
Select the check box for each system type to provision. You can provision more than one system type while running the procedure.
Note:
When running the procedure, you can only select one operational support system (OSM, UIM, or ASAP) option each time.Click OK.
The Communications Suite Installation Procedure adds the selected systems to the Choose Targets table and displays each system's components as a row. Some Oracle Communications applications, including all Operation Support System (OSS) applications, require an Oracle WebLogic installation before provisioning. For these systems, an ADMIN row is automatically added for specifying the WebLogic installation used for provisioning.
Select a row for a system component.
Click the blank field in the component's target name column and select the managed host from the list the component will be provisioned on.
Enterprise Manager Cloud Control retrieves the Free RAM, RAM, Free Storage and Storage values of the selected target host and updates the table.
In the Host Configurations - target_name, provide the parameters needed by the Oracle Communications application installer for the selected component. Typically, you enter these values during the Oracle Universal Installer interview process for the application you are installing.
You must use values that respect the validations performed by the Oracle Communications application installers. For example, if a product does not allow a user name and password to be the same or requires special characters in the password, you must use values that meet the requirements. See the specific Oracle Communications application product installation guides for information on setting these parameters.
Under Installer Locations, click Browse to specify the location of the Oracle Communications application installer. See "Downloading Oracle Communications Application Installers" for information on obtaining Oracle Communications application installer packages.
For Oracle Communications applications requiring a pre-existing Oracle WebLogic domain before installation, such as Order and Service Management, Unified Inventory Management and ASAP, specify the domain parameters under ADMIN Configuration. The procedure uses these values to create the required domain.
Under application Configuration, provide the installation parameters required by the Oracle Communications application installer.
Click Next.
Provide the preferred credentials for the target host. See "Setting Up Host Preferred Credentials" for more information.
Under Schedule, specify when the procedure should run.
Click Next.
Under Review, verify your provisioning configuration by checking the summary provided, and then click Finish.
Tip:
You can view the status of the provisioning process in the Procedure Activity tab. Click the procedure name in the Run column to view the procedure's status. To update the status, click Refresh. The Status Detail displays all of the provisioning procedure steps and corresponding status. View any step's status by clicking on the link in the Status column.This section provides an overview of how to set up a new Oracle Communications Billing and Revenue Management system and components using the Communications Suite Installation Procedure. Applications Management Pack for Oracle Communications provides two options for provisioning Billing and Revenue Management:
The BRM Basic option installs a limited set of components on a single target host. Use these systems for development or simple deployments of Billing and Revenue Management. See "Provisioning a Basic Billing and Revenue Management System" for a list of included components.
The BRM Advanced option enables selecting specific components for installation on one ore more hosts. Use this option when installing production systems or testing systems with distributed component architecture.
Using the procedure requires an understanding of Billing and Revenue Management architecture and installation. See Oracle Communications Billing and Revenue Management Installation Guide for more information on installation details such as parameters.
To set up a new Billing and Revenue Management instance:
Download the required Billing and Revenue Management InstallShield MultiPlatform (ISMP) packages from the Oracle Software Delivery Cloud to a location accessible from the management server. See "Downloading the Billing and Revenue Management Installers" for more information.
Create the Billing and Revenue Management source components in the Enterprise Manager Cloud Control Software Library. See "Creating the Billing and Revenue Management Source Components" for more information.
Create the Oracle Enterprise Database used by Billing and Revenue Management. See "Specifying the Billing and Revenue Management Database" for more information.
Provision either a single instance Billing and Revenue Management system or individual components on one or more host targets. See "Provisioning a Basic Billing and Revenue Management System" and "Provisioning Billing and Revenue Management Components" for more information.
Download the Billing and Revenue Management ISMP installer packages from the Oracle Software Delivery Cloud at:
You must download all of the Billing and Revenue Management ISMP installer packages when using the BRM Basic option.
Place the downloaded ISMP packages into a file share location accessible from your Enterprise Manager Cloud Control management server. The Communications Suite Installation Procedure requires either a local or remote path to the location where the packages are installed.
In some cases, a single ISMP package provisions multiple Billing and Revenue Management components. For example, the Portal Base package includes the Connection Manager, Oracle Data Manager and BRM Applications. Table 4-2 contains a list of the ISMP packages and the included installable components in each package.
Table 4-2 BRM ISMP Packages Descriptions and Base Components
| BRM ISMP Package | Installable Components | Source Component Name Format | Base Component |
|---|---|---|---|
|
AccountSynchTool |
Account Synchronization CM Account Synchronization DM |
AccountSynchTool_release_OS |
oracle_brm_cm |
|
BRM Base |
Batch Controller CM Proxy CMMP Connection Manager Email Data Manager Formatter Invoice Data Manager Oracle Data Manager BRM Applications (Device Management, Load notification event, Load price list, Pin A/R taxes, Pin balance transfer, Pin billed, Pin bill handler, Pin bulk adjust, Pin export price, Pin invoice, Pin monitor, Pin ood handler, Pin rate change, Pin remit, Pin rerate, Pin subscription, Pin trial bill, Pin unlock service Invoicing, Misc, Pin_cfg_bpdump, SOX_Unlock, Subscription, Testnap, UEL, GL_Export, Diagnostics, Infranet Manager CLI, Infranet Manager, Node Manager, Export_price, Credit_Control Billing, Account Dump Utility, Development_Files) |
PortalBase_release_OS |
NA |
|
BRM_Services_Framework_Mgr_AAA |
BRM Services Framework Manager AAA |
BRMServicesFrameworkMgrAAA_release_OS |
oracle_brm_cm |
|
BRM_Services_Framework_Mgr |
BRM Services Framework Manager |
BRM_Services_Framework_Mgr_release_OS |
oracle_brm_cm |
|
CIBERRoaming |
CIBER Roaming |
CIBERRoaming_release_OS |
oracle_brm_pipeline |
|
CollectionsMgr |
Collections Manager |
CollectionsMgr_release_OS |
oracle_brm_cm |
|
ContentMgr |
Content Manager |
ContentMgr_release_OS |
oracle_brm_cm |
|
EAI_FrameworkMgr |
EAI Connection Manager (CM) module EAI Data Manager Payload Generator External Module |
EAIFrameworkMgr_release_OS |
oracle_brm_cm |
|
EmailMgr |
Email Manager |
EmailMgr_release_OS |
oracle_brm_cm |
|
GPRS_AAA_Mgr |
GPRS AAA Manager |
GPRSAAAMgr_release_OS |
oracle_brm_cm |
|
GPRS_Mgr_30 |
GPRS Manager 3.0 |
GPRSMgr_release_OS |
oracle_brm_cm |
|
GSM_AAA_Mgr |
GSM AAA Manager |
GSMAAAMgr_release_OS |
oracle_brm_cm |
|
GSM_Mgr |
GSM Manager |
GSM_Mgr_release_OS |
oracle_brm_cm |
|
IPAddressMgr |
IP Address Manager |
IPAddressMgr_release_OS |
oracle_brm_cm |
|
Interconnect |
Interconnect Manager |
Interconnect_release_OS |
oracle_brm_pipeline |
|
InventoryMgr |
Inventory Manager |
InventoryMgr_release_OS |
oracle_brm_cm |
|
LDAPMgr |
LDAP Manager LDAP Manager has a single component, LDAPMgr. The pin_channel_export component gets deployed as part of it. |
LDAPMgr_release_OS |
NA |
|
MultiDBMgr |
MultiDB Manager |
MultiDBMgr_release_OS |
oracle_brm_cm |
|
NumberMgr |
Number Manager |
NumberMgr_release_OS |
oracle_brm_cm |
|
PaymentechMgr |
Paymentech Manager |
PaymentechMgr_release_OS |
NA |
|
Pipeline |
BRE Real-Time Pipeline |
Pipeline_release_OS |
NA |
|
Pipeline_ConfMgr |
Pipeline Configuration Manager |
PipelineConfMgr_release_OS |
oracle_brm_pipeline |
|
RadiusMgr |
Radius Manager |
RadiusMgr_release_OS |
oracle_brm_cm |
|
RatedEventLoader |
Rated Event Loader, Event Extraction Manager |
REL_release_OS |
NA |
|
ResourceResMgr |
Resource Reservation Manager |
ResourceResMgr_release_OS |
oracle_brm_cm |
|
RevAssuranceMgr |
Revenue Assurance Manager |
RevAssuranceMgr_release_OS |
oracle_brm_cm |
|
SIMMgr |
SIM Manager |
SIMMgr_release_OS |
oracle_brm_cm |
|
SuspenseMgr |
Suspense Manager |
SuspenseMgr_release_OS |
oracle_brm_cm |
|
TAPRoamingmanager |
TAP Roaming Manager |
TAPRoamingMgr_release_OS |
oracle_brm_pipeline |
|
ThirdParty |
ThirdParty Applications |
ThirdParty_release_OS |
NA |
|
Timos |
Timos Data Manager |
Timos_release_OS |
NA |
|
VertexMgr |
Vertex Manager |
VertexMgr_release_OS |
NA |
|
VertexQuantumMgr |
Vertex Quantum Manager |
VertexQuantumMgr_release_OS |
NA |
|
VoucherMgr |
Voucher Manager |
VoucherMgr_release_OS |
oracle_brm_cm |
|
WirelessSuite |
GSM AAA Manager GSM Manager GPRS AAA Manager GPRS Manager Number Manager RRF Manager Services Framework Manager Services Framework AAA Manager SIM Manager You cannot choose which features to install. They are all installed. |
WirelessSuite_release_OS |
oracle_brm_cm |
You must configure the ISMP packages as source components in the Enterprise Manager Cloud Control Software Library before running the provisioning procedure. If your environment uses custom applications, you must also create source components for the applications. Use the upload source components utility to upload the ISMP packages into the Software Library.
To add the Billing and Revenue Management ISMP packages to the Software Library:
Confirm the BRMComponents folder exists in the Software Library. See "Creating the Oracle Communications Folders for BRM Installers" for more information.
Open a shell session to the host where your Enterprise Manager Cloud Control management server is installed.
Change directories to the following location:
em_home/gc_inst/user_projects/domains/GCDomain/default_xml/platform/swlibUtil
where em_home is the Enterprise Manager Cloud Control home directory.
Open the upload_src.xml file for editing.
Edit the environment parameters in Table 4-3 for your environment.
Table 4-3 upload_src.xml Environment Parameters
| Parameter | Description |
|---|---|
|
HOSTSTR |
The Enterprise Manager Cloud Control fully qualified domain name. |
|
SID |
The database SID for the Enterprise Manager Cloud Control repository. |
|
DB_USER |
The database administrative user. For example, sysman. |
|
DB_PW |
The database administrator's password. |
|
PATH |
The relative path of the BRMComponents directory in the Software Library. |
|
FILEPATH |
The file path to the location where the ISMP installers are stored. This path must be accessible from the management server. |
Confirm that the listing of Billing and Revenue Management components is consistent with the ISMP packages downloaded in your environment. The packages and names must match the operating system platform you are provisioning on. For example, the listing for the Billing and Revenue Management Account Synch Tool installer uses the following format in the upload_src.xml file:
On Linux:
<DISPLAY_NAME>BRM_AccountSynchTool_7.5.0_Linux</DISPLAY_NAME> <DESCRIPTION>AccountSynchTool_7.5.0_Linux</DESCRIPTION> <FILE_NAME>7.5.0_Accountsynchtool_linux_32_opt.bin</FILE_NAME>
On Solaris:
<DISPLAY_NAME>BRM_AccountSynchTool_7.5.0_Solaris</DISPLAY_NAME> <DESCRIPTION>AccountSynchTool_7.5.0_Solaris</DESCRIPTION> <FILE_NAME>7.5.0_SMSSettlement_Reports_solaris_32_opt.bin</FILE_NAME>
Upload the source components configuration using the following command in the same directory:
perl upload_src_comp.pl -loglevel 2 OMS_HOME
where OMS_HOME is the path of your management server's home directory. The Billing and Revenue Management components ISMP installers are uploaded to the Software Library.
Check the upload_src_comp.log file for errors if the procedure is unsuccessful. Increase the log level to a maximum of 3 when running the perl command if more detail is needed in the utility's log.
Billing and Revenue Management requires an Oracle Enterprise Database. When provisioning either a Billing and Revenue Management system or components you must choose whether to create a database instance or use and existing instance.
You must specify an existing database when using the BRM Basic option. See "Provisioning a Basic Billing and Revenue Management System" for more information on provisioning a Billing and Revenue Management system on a single host using an existing database.
Some Billing and Revenue Management components, such as the Data Manager, Batch Rating Engine, and Real-time Pipeline, require connection to a Billing and Revenue Management database to complete provisioning and to start the service. When provisioning one or more Billing and Revenue Management components using the BRM Advanced option, you can specify whether to create a database or use an existing database. See "Provisioning Billing and Revenue Management Components" for more information on specifying database information with component provisioning.
Use the BRM Basic option in the Communications Suite Installation Procedure to provision a basic system onto a single host. The procedure installs the following Billing and Revenue Management components:
Portal_Base
AccountSyncTool
RatedEventLoader
WebServicesMgr
BRM_JCA_Adapter
DM_AQ
PaymenttechMgr
EAI_FrameworkMgr
CollectionsMgr
ContentMgr
WirelessSuite
AccountMigrationMgr
To provision a Billing and Revenue Management system on a single host:
Log in to the Enterprise Manager Cloud Control administration console on your management server as a privileged user.
Click Enterprise, then Provisioning and Patching, and then Procedure Library.
In the Deployment Procedure Manager, select Communications Suite Installation Procedure.
Click Launch.
Under Choose Targets, click Add.
Select BRM Basic.
Click OK.
The Communications Suite Installation Procedure adds a BRM Basic entry to the Choose Targets table and displays the BRM component as a row.
Select the Target Name text box from the BRM row.
Select a managed host target from the drop down list.
Enterprise Manager Cloud Control displays the resource information for the target host. The Host Configurations area also displays the parameters required for BRM Basic provisioning.
Select whether to enable MultiDB.
Enter the path to the location where the BIlling and Revenue Management ISMP installers are located in the BRM Installer Folder field. Click Browse to use the Remote File Browser tool.
In Host Configurations, provide the parameters needed by the Billing and Revenue Management installer for single host provisioning. Typically, you enter these values during the installer interview process. See Oracle Communications Billing and Revenue Management Installation Guide for more information on installation parameters.
The BRM Basic option requires an existing database on which to install and configure the Billing and Revenue Management instance. The procedure creates the specified database user based on the parameter values entered.
Expand Advanced to edit the default port numbers for the Billing and Revenue Management components.
Click Next.
The Credentials page is displayed.
Provide the preferred credentials for the target host. See "Setting Up Host Preferred Credentials" for more information.
Click Next.
Under Schedule, specify when the procedure should run.
Click Next.
Under Review, verify your installation configuration by checking the summary, and then click Finish.
You provision individual Billing and Revenue Management components using the Communications Suite Installation Procedure BRM Advanced option. For example, configure production system components requiring a distributed architecture across multiple target hosts using this functionality.
You must deploy the ThirdParty and BRM Base packages to a target in your installation before deploying optional components. Optional components require Billing and Revenue Connection (CM) and Data Manager (DM Oracle) configuration data when using the BRM Advanced provisioning procedure. Be sure to provide the proper CM and DM parameter values, including correct host names and port numbers, for the environment your optional managers are joining. The procedure cannot validate these parameters as they are specific to your environment.
See Oracle Communications Billing and Revenue Management Installation Guide for more information on installing a distributed architecture on multiple hosts.
To provision Billing and Revenue Management components using the BRM Advanced option:
Log in to the Enterprise Manager Cloud Control administration console on your management server as a privileged user.
Click Enterprise, then Provisioning and Patching, and then Procedure Library.
In the Deployment Procedure Manager, select Communications Suite Installation Procedure.
Click Launch.
Under Choose Targets, click Add.
Select BRM Advanced.
Click OK.
The Communications Suite Installation Procedure adds a BRM Advanced row to the Choose Targets table and displays the component as a row.
Select the row for the added component and click Configure.
The Search and Select: Entities window containing a list of Billing and Revenue Management ISMP installer packages.
Select the Billing and Revenue Management packages containing the components to provision. You can select more than one component to provision for the procedure by holding the control key.
Click Select.
Enterprise Manager Cloud Control adds an entry for the selected installer to the Choose Targets page list of systems.
Select the newly added installer row in the list.
The BRM Components list is displayed. This list contains the Billing and Revenue Management components included in the installers selected.
Select the Billing and Revenue Management components to provision.
Click Add.
Enterprise Manager Cloud Control adds a row for the Billing and Revenue Management components to the Choose Targets page list of systems.
Click in the Target Name field of the newly added components and select a target from the drop down list.
The component's required Host Configuration parameters are displayed.
In Host Configurations - target_name, provide the parameters needed by the Billing and Revenue Management installer for the selected component. Typically, you enter these values during the installer interview process.
The BRM Advanced option enables specifying whether to use an existing Billing and Revenue Management database or to initialize a new database instance for use with provisioning. Set the database usage and partitioning behavior using the parameters in Table 4-4.
The procedure uses the values specified for the pin_setup.values file used during Billing and Revenue Management configuration. For information on the pin_setup.values file, see the chapter on installing Billing and Revenue Management in Oracle Communications Billing and Revenue Management Installation Guide.
When adding components to an existing Billing and Revenue Management system, you must provide parameters for the database already in use and ensure that the procedure is not set to drop existing tables. By default, the options to initialize the database and drop all Billing and Revenue Management tables is set to YES.
Table 4-4 Component Provisioning Database Parameters
| Parameter | Description | Default Value |
|---|---|---|
|
SetupInitDb |
Specifies whether to initialize the BRM databases. |
YES |
|
SetupCreatePartition |
Specify whether to add partitions to your event tables. Enter Yes to have the installer add 12 monthly partitions, a historic partition, and a last partition to your event tables. Enter No if you want the installer to add only a historic partition and a last partition to the tables. You can use this partitioning layout for a simple test or demonstration system. For a production system, however, you must add purgeable partitions after installation is complete and before the system generates events. This sets the $CREATE_PARTITIONS parameter in the pin_setup.values file to Yes. This prompt is displayed only if you enter Yes to Partition event tables. |
YES |
|
EnablePartition |
Specify whether you want to enable partitioning. To partition any tables, you need Oracle Partitioning. If you select Yes but do not have Oracle Partitioning installed, the BRM setup program fails when it tries to create partitions. This sets the $ENABLE_PARTITION parameter to Yes in the pin_setup.values file. Important If you select No and then change your mind after you've installed BRM, you will have to upgrade your BRM database from a nonpartitioned to a partitioned version before you can partition your tables. If you plan to use Rated Event Loader to load prerated events, you must partition your event tables. If you select Yes, you must configure pin_setup to set up any non-event partitions. Your event tables will be partitioned automatically. |
YES |
|
CLASSES_TO_BE_PARTITIONED |
Assign a list of classes that you want to partition. You cannot partition classes after you run the pin_setup utility |
NA |
|
SetupDropAllTables |
Enter whether you want to drop the database tables. If you select Yes, the installer drops all existing tables on your system. This results in irrecoverable loss of data. Do not use this unless you have backed up all of your existing data. If you select No, the installer uses your existing BRM tables. In test systems, select Yes to reinitialize the database. |
YES |
|
CreateDatabaseTables |
Enter whether you want the installer to create default BRM tablespaces for you. Enter No to create custom tablespaces manually. You must create your tablespaces before you run the pin_setup script. |
YES |
Expand Advanced to specify the component's configuration parameters used in the Billing and Revenue Management pin.conf file.
Click Next.
The Credentials page is displayed.
Provide the preferred credentials for the target host. See "Setting Up Host Preferred Credentials" for more information.
Click Next.
Under Schedule, specify when the procedure should run.
Click Next.
Under Review, verify your installation configuration by checking the summary, and then click Finish.
Tip:
You can view the status of the provisioning process in the Procedure Activity tab. Click the procedure name in the Run column to view the procedure's status. To update the status, click Refresh. The Status Detail displays all of the provisioning procedure steps and corresponding status. View any step's status by clicking on the link in the Status column.Oracle Communications application suites, such as the Order to Cash solution suite, provide cross-application functionality. Provision supported applications suites using the Communications Suite Installation Procedure in Enterprise Manager Cloud Control.
You can provision the following application suites on both a single server meeting the minimum technical requirements for multi-application installation or across distributed high-availability hosts:
Order to Cash Suite:
Order and Service Management
Unified Inventory Management
ASAP
OSS Service Fulfillment:
Order and Service Management
Unified Inventory Management
ASAP
To provision a suite solution, select the required suite from the System Types menu and complete steps 7 through 15 from the "Provisioning Individual Applications" section.
You can provision supported Oracle Communications applications in high availability and cluster configurations. The following high availability and cluster system types are supported:
OSS Fulfillment Suite - HA
OSM 2 Node Cluster
UIM 2 Node Cluster
To provision a high-availability or clustered configuration, select the required option from the System Types menu and complete steps 7 through 16 from the "Provisioning Individual Applications" section.
For high-availability and cluster configurations, the Communications Suite Installation Procedure adds a PROXY system configuration row. Provide the WebLogic Proxy Server Port parameter for these configurations. Obtain the proxy configuration information from your application administrator.
You can save your provisioning configurations as custom systems while running the provisioning procedure. Use custom system when provisioning multiple instances of the same application on multiple targets or for backing up configurations for reuse at a later time.
To save a provisioning procedure configuration as a custom system:
In the Choose Targets provisioning procedure step, click Save at any time.
Enter a Custom System Name for the configuration.
Click OK.
You can start and stop supported Oracle Communications application processes managed as targets using the Enterprise Manager Cloud Control administration console. See the following sections for information on controlling application processes:
Starting and Stopping Billing and Revenue Management Processes
Starting and Stopping Domains Hosting Oracle Communications Applications
You can start, stop, and restart Billing and Revenue Management application processes on managed targets using the Enterprise Manager Cloud Control administration console. You can control single processes or all processes running on a managed host.
Note:
When using the START ALL and STOP ALL process control commands, only the components included in the pin_ctl.conf file will be started or stopped. See the section on customizing the pin_ctl utility environment variables in Oracle Communications Billing and Revenue Management System Administrator's Guide for more information on specifying components in the pin_ctl.conf file.To start and stop Billing and Revenue Management processes:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then Communications Applications.
A table of managed Billing and Revenue Management systems is displayed.
To stop or start either a one or more Billing and Revenue Management processes on a managed target:
Click the top-level BRM_target_name link.
The overview page for the BRM Target is displayed.
Click either STOP ALL or START ALL.
(Optional) Monitor the status of the processes under Status.
To restart one or more Billing and Revenue Management processes on a managed target:
Expand the top-level BRM_target_name where the process is running.
Click the process link to control.
The overview page for the selected process is displayed.
Click ReStart.
(Optional) Monitor the status of the process under Status.
You can use Enterprise Manager Cloud Control to start and shutdown managed Oracle WebLogic domains hosting Oracle Communications applications. For example, you can start a WebLogic domain hosting Order and Service Management or Pricing Design Center.
To start and stop WebLogic domains:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then Middleware.
The managed Middleware targets list is displayed.
Click the name of the domain to be controlled.
The selected middleware target's overview page is displayed
Under the system_name, expand the system type menu.
Click Control.
Click Start Up or Shutdown for the desired operation.
The Credentials page is displayed.
Specify the required credential parameters.
Click OK.
Go to the middleware target's overview page and confirm that the domain has either started up or shutdown.
You can patch Billing and Revenue Management installations using the BRM Patching Procedure. The procedure uses Enterprise Manager Cloud Control integration with Oracle Support for searching and downloading patches. The procedure then performs patch installation on managed Billing and Revenue Management targets.
The BRM Patching Procedure does not support installing password protected patches. Only generally available patches from My Oracle Support are supported.
Install password protected patches and patches unavailable from within Enterprise Manager Cloud Control using the offline patching process. For information on performing offline patch installation, see the relevant sections in Oracle Enterprise Manager Lifecycle Management Administrator's Guide at:
http://docs.oracle.com/cd/E24628_01/em.121/e27046/pat_mosem_new.htm#BABEGBCC
Application Management Pack for Oracle Communications supports patching a single Billing and Revenue Management target using the BRM Patching Procedure. Patching multiple targets at the same time is not support. You must run the procedure for each target individually.
To patch managed Billing and Revenue Management targets:
Log in to the Enterprise Manager Cloud Control administration console on your management server as a privileged user.
Click Enterprise, then Provisioning and Patching, and then Procedure Library.
In the Deployment Procedure Manager, select BRM Patching Procedure.
Click Launch.
Under Choose Targets and Patches, click Add.
The Search and Select: Targets window is displayed.
Specify the target information:
In the Target Type field, enter the target type.
In the Target Name field, enter the name of the target.
In the Host field, enter the host name.
Click Search.
Select the Billing and Revenue Management target to patch.
Click Select.
Enterprise Manager Cloud Control returns to the Choose Targets and Patches window. The Billing and Revenue Management component to be patched is now listed.
In the target's row, click Add Patch.
The Choose BRM Patches window is displayed.
In the Search Platforms pull down menu, specify search criteria for the patch by doing one of the following:
To search for a specific patch, specify the patch ID in the Search Patches field and specify the platform in the Search Platforms list.
To search for all patches for a Billing and Revenue Management release, specify a release value in the Search Releases field.
Click Search Patches.
A list of patches meeting the search criteria is displayed.
If needed, click the readme link for detailed patch information from Oracle Support.
Select the correct patch(es) to apply and click Add Patches.
Enterprise Manager Cloud Control returns to the Choose Targets and Patches window.
Under Target Configuration, provide the information required about your Billing and Revenue Management target. Typically, this information includes the location of your Billing and Revenue Management installation and database credentials.
Click Next.
The Credentials page is displayed.
Provide the preferred credentials for the target host. See "Setting Up Host Preferred Credentials" for more information.
Click Next.
Under Schedule, specify when the procedure should run.
Click Next.
Under Review, verify your installation configuration by checking the summary, and then click Finish.
Tip:
You can view the status of the patching process in the Procedure Activity tab. Click the procedure name in the Run column to view the procedure's status. To update the status, click Refresh. The Status Detail displays all of the patching procedure steps and corresponding status. View any step's status by clicking on the link in the Status column.To view the list of patches that have been applied to a Billing and Revenue Management CM or pipeline target:
Log in to the Enterprise Manager Cloud Control administration console on your management server as a privileged user.
Click Targets, and then All Targets.
Click the Billing and Revenue Management CM or pipeline target you want to view patch information for.
The Patch Set Level field in the Summary displays the component's patch level.
Oracle Communications applications rely on host health and performance. Enterprise Manager Cloud Control provides the following functions used in monitoring hosts and foundational software:
See "Monitoring Oracle Communications Application Targets" for information on monitoring supported Oracle Communications application targets.
See the chapter on using Incident Management in Oracle Enterprise Manager Cloud Control Administrator's Guide for information on setting up notification channels and resolving incidents.
Enterprise Manager Cloud Control monitors basic collection item (non-metric) and metrics for all managed host targets. The management agent installed on a managed host provides system information including software and hardware configuration, status, health, performance, and storage.
See the chapter on enterprise monitoring in Oracle Enterprise Manager Cloud Control Administrator's Guide for more information on monitoring, managing incidents, and notifications.
Enterprise Manager Cloud Control provides comprehensive monitoring of Fusion Middleware instances and Coherence clusters. You use these monitoring capabilities to monitor the domains and clusters on which some Oracle Communications applications run.
See the chapter on middleware management with Enterprise Manager Cloud Control in Oracle Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management for more information on monitoring Fusion Middleware.
See the chapter on managing Oracle Coherence in Oracle Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management for more information on monitoring Coherence.
Enterprise Manager Cloud Control monitors and manages Oracle Enterprise and Exadata Databases used bCommunications Suite Installation Procedurey Oracle Communications applications. For more information on monitoring databases, see the Enterprise Manager Cloud Control Documentation database management and Exadata Database Machine documents available at:
You can monitor supported Oracle Communications application and component targets in Enterprise Manager Cloud Control. Monitoring targets enables you to maintain your Oracle Communications environment and manage incidents and alerts.
Application Management Pack for Oracle Communications provides extended metrics for Oracle Communications applications that augment standard monitoring data.
Once you have discovered and promoted your Oracle Communications targets, you can monitor a variety of metrics. You use configurable thresholds when configuring warning and critical event states notifications useful for alerting you to potential system problems.
The following monitoring procedures are supported:
See "About Conditions that Trigger Notifications" for information on the formatting of the included information in the application monitoring chapters.
You can view home pages for application and suite level targets managed in Enterprise Manager Cloud Control. These summary pages provide an overview of each application or suite including information such as availability, metric alerts and other performance data.
Home pages are available for the following target types:
ASAP Targets
BRM Targets
Comms Suite Targets
OSM Targets
UIM Targets
NCC Targets
To view a home page:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then Communications Applications.
In the list of targets, click the application or suite target name you want to view.
The target's home page is displayed.
You can view home pages for component targets managed in Enterprise Manager Cloud Control. These summary pages provide an overview of each application component including information such as availability, metric alerts and other performance data.
To view a component's home page:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then All Targets.
In the list of targets, click the component target name you want to view.
The target's home page is displayed.
To monitor Oracle Communications application targets:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then All Targets.
In the list of targets, click the target name you want to monitor.
The target's overview page is displayed.
Under the target_name, expand the target type menu.
Click Monitoring, and then All Metrics.
In the left-hand tree control, expand the metric category and select the metric you want to view.
To view Oracle Communications application log files:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then Communications Applications.
In the list of targets, click the target name you want to view logs for.
The target's overview page is displayed.
Under Quick Links, click View Log Files.
Application Management Pack for Oracle Communications comes with default thresholds for critical metrics in supported applications. Enterprise Manager Cloud Control also includes default thresholds for host metrics including CPU and physical memory usage. You can define additional metrics needed for your environment.
To better suit the monitoring needs of your organization, you can edit the thresholds provided and define new thresholds. When defining thresholds, choose acceptable values to avoid unnecessary alerts.
You can establish thresholds that quickly provide important information by defining baselines reflecting how your system runs for a normal period.
To edit existing or configure new metrics and related thresholds for Oracle Communications targets:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
From the All Targets list, choose a managed Oracle Communications host, application or component target.
On the target's overview page, click the target name and from the Monitoring menu, and then choose Metric and Collection Settings.
On the Metric and Collection Settings page, configure the monitoring thresholds as required for your environment by clicking the Edit pencil icon for a metric.
Edit the Warning Threshold and Critical Threshold fields.
Click Add to create a monitored object for the selected metric.
Click Continue.
Click OK to save your changes.
For detailed information on configuring Enterprise Manager Cloud Control notification settings, see Oracle Enterprise Manager Cloud Control Administrator's Guide.
To configure collection schedules for collection items and metrics:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
From the All Targets list, choose a managed Oracle Communications host, application or component target.
On the target's overview page, click the target name and from the Monitoring menu, and then choose Metric and Collection Settings.
On the Metric and Collection Settings page, configure the Collection Schedule time interval by clicking on the currently set interval link for a listed metric.
Set the new Frequency Type and Repeat Every values, and then click Continue.
Click OK to save your changes.
Corrective actions let you specify automated responses to alerts. Corrective actions ensure that routine responses to alerts are automatically executed, esuring problems are dealt with before they impact business operations. By default, Application Management Pack for Oracle Communications does not include any corrective actions set for alerts generated by Oracle Communications applications.
See the section on creating corrective actions in Oracle Enterprise Manager Cloud Control Administrator's Guide for more information on configuring corrective actions.
To add corrective actions for warnings and critical alerts:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
From the All Targets list, choose a managed Oracle Communications host, application or component target.
On the target's overview page, click the target name and from the Monitoring menu, and then choose Metric and Collection Settings.
Click the edit pencil icon for the metric you want to configure a corrective action for.
Under Corrective Actions, click Add.
Select a task from the pull down menu in the Add Corrective Action step.
Click Continue.
Define the corrective action and provide the necessary information.
Click Continue.
You can use Enterprise Manager Cloud Control generic system and dynamic group functionality for customizing the monitoring interface in the administration console. For example, you can create generic system that includes a selection of managed targets best suited for your environment. You can create a dynamic group containing the same target type for monitoring groups of targets performing the same function.
By default, Application Management Pack for Oracle Communications includes the following systems:
BRM Target
Comms Suite
To create new systems or access the default BRM and Comms Suite systems:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
From the Targets menu, select Systems.
Choose one of the following options:
In the Search pull down menu, select BRM Target or Comms Suite to view a default system, and then click the right arrow icon.
Click Add, to create a generic system.
See the discussion on generic systems in Oracle Enterprise Manager Lifecycle Management Administrator's Guide for more information on using generic systems.
See the overview of dynamic groups in Oracle Enterprise Manager Cloud Control Administrator's Guide for more information on using dynamic groups.
Management agents continuously collect metrics on the health and performance of your Oracle Communications applications and host targets and return the information to the management server. Enterprise Manager Cloud Control generates alerts and notifications when metric values exceed preset conditions notifying you of potential issues with your environment.
Application Management Pack for Communications includes default conditions with thresholds for metrics such as application process up/down status, CPU and memory usage by a process, and transaction latency. You can customize the conditions containing the metric thresholds using the Enterprise Manager Cloud Control administration console.
See "Configuring Metric Monitoring Thresholds and Alerts" for information on setting thresholds.
Table 4-5 describes each attribute in a condition.
Table 4-5 Condition Attributes
| Attribute | Description |
|---|---|
|
Condition Name |
The name of the condition. |
|
Evaluation and Collection Frequency |
The rate at which the metric is collected and evaluated to determine whether it has crossed its threshold. The evaluation frequency is the same as the collection frequency. |
|
Upload Frequency |
The rate at which the management agent moves data to the Management Repository. For example, upload every nth collection. The upload frequency for a metric comes from the Enterprise Manager default collection file for that target type. This column is present in the Metric Collection Summary table only when the Upload Frequency is different from the Collection Frequency. |
|
Operator |
The comparison method Enterprise Manager Cloud Control uses to evaluate the metric value against the threshold values.
|
|
Default Warning Threshold |
Value that indicates whether a warning alert should be initiated. If the threshold is reached for the number of consecutive occurrences, a warning alert is triggered. |
|
Default Critical Threshold |
Value that indicates whether a critical alert should be initiated. If the threshold is reached for the number of consecutive occurrences, a warning alert is triggered |
|
Consecutive Number of Occurrences Preceding Notification |
Consecutive number of times a metric's value reaches either the warning threshold or critical threshold before a notification is sent. |
|
Alert Text |
Message indicating why the alert was generated. See the chapter on managing alerts in Oracle Enterprise Manager Cloud Control Administrator's Guide for information on formatting alert text. |
See the overview of key default collection metadata elements and attributes in Oracle Enterprise Manager Cloud Control Extensibility Programmer's Reference for more information about using and customizing collection item conditions in target definition files.
Table 4-6 provides an example of a metric attributes summary table. Collected metrics for each Oracle Communications application with default conditions are summarized in similar tables in the monitoring chapters. The table shows the attributes that trigger warning or critical notifications, and when configurable, the threshold values.
Table 4-6 Sample Conditions Summary Table
| Condition Name | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
CANCEL_MAX_LATENCY |
5 minutes |
5 minutes |
GT |
10000000 ns |
12500000 ns |
1 |
Bytes sent by the server are %value% |
See the following chapters for information about monitored metrics in specific Oracle Communications applications:
You can view, edit, and compare configurations for managed Billing and Revenue Management targets including host systems and individual components. See the following sections for information on performing configuration tasks:
Enterprise Manager Cloud Control retains configuration changes and history as part of Configuration Management. See the chapter on managing configuration information in Oracle Enterprise Manager Lifecycle Management Administrator's Guide for more information at:
http://docs.oracle.com/cd/E24628_01/em.121/e27046/config_mgmt.htm#EMLCM11614
You view Billing and Revenue Management system and component configurations using the Enterprise Manager Cloud Control administration console.
To access the configuration viewer:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then Communications Applications.
A table containing managed Oracle Communications systems is displayed.
Click the name of the managed system or component for which you want to view the configuration for.
Enterprise Manager Cloud Control presents the overview dashboard for the system or component.
Under the system_name, expand the system type menu.
Click Configuration, and then Last Collected.
Enterprise Manager Cloud Control presents the configuration viewer for the selected system in the administration console.
Table 4-7 describes the configuration tabs shown in the administration console:
Table 4-7 Configuration Viewer Tabs
| Tab | Description |
|---|---|
|
System_Name |
Contains host information and configuration parameters of the Billing and Revenue Management target including host and component version, user name, directories and port numbers. |
|
System Structure |
Shown for only managed system targets, contains an expandable and selectable listing of the system's installed and managed Billing and Revenue Management managed targets. |
|
Immediate Relationship |
Displays the immediate relationships of the managed target to other selectable managed Billing and Revenue Management targets. |
|
Member Of |
Lists selectable managed Billing and Revenue Management target component's membership in managed system targets. |
|
Uses |
Lists selectable targets used by the managed Billing and Revenue Management target. |
|
Used By |
Lists selectable targets using the managed Billing and Revenue Management target. |
You can edit Billing and Revenue Management configuration files with Enterprise Manager Cloud Control. See the chapter on using configuration files to connect and configure components in Oracle Communications Billing and Revenue Management System Administrator's Guide for information on configuration files and parameters.
Use the Edit Configurations for BRM Targets procedure for changing the configuration of a managed Billing and Revenue Management component target. You can only edit a single Billing and Revenue Management component configuration at a time. Run the procedure for each configuration change you make.
To run the procedure:
Log in to the Enterprise Manager Cloud Control administration console on your management server as a privileged user.
From Targets, select All Targets.
Select the Billing and Revenue Management target where the component to be configured in installed.
In the BRM Target home page, click the component link in the Components Installed table you want to configure.
On the component home page click Edit Configurations under Quick Links.
The Edit Configurations for BRM Targets procedure is launched.
Under Choose BRM Targets, click Add.
The Search and Select: Targets window containing a list of managed Billing and Revenue Management component targets is displayed.
Select the managed Billing and Revenue Management targets to edit.
Click Select.
The Communications Suite Installation Procedure adds the selected components to the Choose BRM Targets table and displays the component as a row.
Select the row for the added component.
The component's Configuration parameter in the Configurations - Name Value Mode is displayed. You can set the Config Mode value in the target row to File if editing the configuration file in a text editor is preferred.
In Component Configurations - mode, provide the updated configuration parameters.
Click Next.
The Credentials page is displayed.
Provide the preferred credentials for the target host. See "Setting Up Host Preferred Credentials" for more information.
Click Next.
Under Schedule, specify when the procedure should run.
Click Next.
Under Review, verify your new configuration by checking the summary, and then click Finish.
Tip:
You can view the status of the configuration process in the Procedure Activity tab. Click the procedure name in the Run column to view the procedure's status. To update the status, click Refresh. The Status Detail displays all of the configuration procedure steps and corresponding status. View any step's status by clicking on the link in the Status column.You can compare two or more managed Billing and Revenue Management target configurations, as well has historical configurations for a single target, using the Enterprise Manager Cloud Control administration console. You can compare configurations of a single component type running on multiple systems for compliance or troubleshooting reasons.
The Enterprise Manager Cloud Control administration console provides multiple ways of running a configuration comparison. The following procedure uses the Communications Applications target page. For additional methods for searching for and comparing target configurations. see the chapter about enterprise configuration management in Oracle Enterprise Manager Cloud Control Extensibility Programmer's Guide.
To compare two or more managed Billing and Revenue Management target configurations:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then Communications Applications.
A table containing managed Oracle Communications systems is displayed.
Click the name of the managed system or component for which you want to compare other component configurations against.
Enterprise Manager Cloud Control presents the overview dashboard for the system or component.
Under the system_name, expand the target type menu.
Click Configuration, and then Compare.
Enterprise Manager Cloud Control launches the Compare Configurations wizard in the administration console with the first configuration already set in the first step, Compare Configurations: First Configuration.
Click Next.
In the Compare Configurations: Comparison Configurations screen, click Add Configurations.
The Search and Select Configurations window is displayed.
Select either the Latest Configuration or Saved Configuration search option.
Ensure that the Target Type matches the type of the first configuration selected in step 7.
Provide a name in the Target Name field, if known.
Click Search.
A list of managed targets meeting the search criteria is displayed.
Select the targets you want to compare.
Click OK to return to the Compare Configurations: Comparison Configurations screen.
Click Next.
Specify a comparison template and template settings in step 3 if you are comparing configurations against a template.
See the chapter about enterprise configuration management in Oracle Enterprise Manager Cloud Control Extensibility Programmer's Guide for information on creating and using configuration templates.
Click Next.
In the Compare Configurations: Schedule and Notify screen, specify when the procedure should run and any notification email addresses.
Click Next.
In the Compare Configurations: Review and Submit screen, review your new configuration by checking the summary.
Click Submit.
Tip:
You can view the status of the configuration process in the Procedure Activity tab. Click the procedure name in the Run column to view the procedure's status. To update the status, click Refresh. The Status Detail displays all of the configuration procedure steps and corresponding status. View any step's status by clicking on the link in the Status column.Application Management Pack for Oracle Communications provides topological views of Oracle Communications applications and components managed as systems in Enterprise Manager Cloud Control. The views supplement existing Enterprise Manager Cloud Control configuration and routing topology views for Oracle Fusion Middleware and Oracle Enterprise Database, providing graphical and relational diagrams of managed targets using the Configuration Topology Viewer.
See the chapter on managing configuration in Oracle Enterprise Manager Lifecycle Management Administrator's Guide and the Enterprise Manager Cloud Control online help for more information about the Configuration Topology Viewer.
See the chapters on managing Enterprise Database and Fusion Middleware in the Oracle Enterprise Manager Cloud Control Administrator's Guide for information on viewing topologies for these applications.
The Communications Suite Installation Procedure installs applications and components as Enterprise Manager Cloud Control systems viewable in the Configuration Topology Viewer. See "Provisioning Applications" for more information about the installation procedure.
To view installed system topologies:
Log in to the Enterprise Manager Cloud Control administration console as a privileged user.
Click Targets, and then Communications Applications.
A table containing managed Oracle Communications systems is displayed.
Click the system for which you want to view the configuration topology.
Enterprise Manager Cloud Control presents the overview dashboard for the system.
Under the system_name, expand the system type menu.
Click Configuration, and then Topology.
Enterprise Manager Cloud Control presents the configuration topology for the selected system.
In the Configuration Topology Viewer, you view additional information about targets and their relationships, such as metrics and incidents.
To obtain more information or a target:
Hover your cursor over a component.
Click the horizontal chevrons icon in the pop-up caption containing the target name.
Click more to view General, Incident Summary and Configuration information about the managed target.
Click the target name to go to the target's overview page.
You perform additional actions, such as stopping and starting a component, from the target's overview page. See "Starting and Stopping Application Processes" for more information on managing component processes using Application Management Pack for Oracle Communications.
Click Agent, Host, or Member of to navigate to the related overview pages.