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:
Business support systems (BSS):
Oracle Communications Billing and Revenue Management (BRM)
Oracle Communications Elastic Charging Engine (ECE)
Oracle Communications Network Charging and Control (NCC)
Oracle Communications Pipeline Configuration Center (PCC)
Oracle Communications Pricing Design Center (PDC)
Operations support systems (OSS):
Oracle Communications ASAP
Oracle Communications Order and Service Management (OSM)
Oracle Communications Unified Inventory Management (UIM)
Integrations:
Oracle Application Integration Architecture for Communications (Oracle AIA)
See "Supported Applications" for supported Oracle Communications application versions.
You perform a variety of actions in Enterprise Manager Cloud Control, including discovering, provisioning, patching, upgrading, and monitoring applications.
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 about supported Oracle Communications applications and versions.
Table 4-1 Supported Application Management Pack for Communications Actions
| Action | BRM | ECE | PDC | PCC | NCC | OSM | UIM | ASAP | Oracle AIA |
|---|---|---|---|---|---|---|---|---|---|
|
Discover |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Provision |
Yes |
No |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
No |
|
Start and Stop Processes |
Yes |
No |
No |
No |
No |
No |
No |
No |
No |
|
Patch |
Yes |
No |
No |
No |
No |
No |
No |
No |
No |
|
Upgrade |
No |
No |
Yes |
No |
No |
No |
No |
No |
No |
|
Monitor |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
|
View/Edit Configuration |
Yes |
No |
No |
No |
No |
No |
No |
No |
No |
|
Manage Alerts |
Yes |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
View Topology |
Yes |
Yes |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
Manage Compliance |
No |
No |
No |
No |
No |
Yes |
Yes |
No |
No |
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 about adding existing Oracle Communications targets to your Enterprise Manager Cloud Control instance.
You provision and upgrade 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 for installing those applications are met. See "Preparing New Hosts for Application Provisioning" for more information about ensuring application hosts are ready. See "About Providing Valid Installation Parameter Values" for information about required values for installation parameters.
You can provision one or more applications 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.
The Communications Suite Installation Procedure supports:
Provisioning application suites. See "About Provisioning Application Suites".
Provisioning highly-available suites and clustered applications. See "About Provisioning Highly-Available Suites and Clustered Applications".
Upgrading PDC. See "Upgrading PDC".
Provisioning all supported applications. See "Provisioning Applications and Suites" and "Provisioning BRM".
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 about adding new and existing hosts as managed targets.
Note:
On Oracle Real Application Clusters (Oracle RAC) databases, the Communications Suite Installation Procedure supports provisioning BRM and OSM only.The values that you provide for the installation parameters during the Oracle Communications Installation Procedure are required by the Oracle Communications application installer for the selected application. Typically, you enter these values during the installation interview process for the application you are installing.
You must use values that respect the validations performed by the application installer. 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 those requirements.
The Communications Suite Installation procedure validates that you have provided values for all required fields, but it does not immediately validate the content of the values. You will not be notified that you have used invalid values until after the procedure fails.
See the specific Oracle Communications application product installation guides for information about the parameters and their required values.
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.
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:
OSM
UIM
ASAP
BRM
PDC
PCC
OSS Service Fulfillment suite:
OSM
UIM
ASAP
You provision a suite in the same way as other targets, as described in "Provisioning Applications and Suites".
After provisioning applications suites, you must manually deploy solution cartridges. For information about deploying cartridges for the individual applications, see:
Oracle Communications Order and Service Management Cartridge Guide for Oracle Application Integration Architecture
Oracle Communications Unified Inventory Management Installation Guide
Oracle Communications ASAP Installation Guide
You can provision supported Oracle Communications applications in the following high-availability and cluster configurations:
A highly-available OSS fulfillment suite
A highly-available Order to Cash suite
An OSM cluster with multiple nodes
A UIM cluster with multiple nodes
You provision highly-available or clustered targets in the same way as other targets, as described in "Provisioning Applications and Suites".
By default, the Communications Suite Installation Procedure includes OSM and UIM clusters with two nodes. You can add more nodes using the Configure button as described in "Provisioning Applications and Suites".
Important:
If you are provisioning an OSM cluster on a WebLogic Server domain that uses a shared storage system such as Network File System (NFS), ensure that the user IDs are consistent across all WebLogic Server client machines that access the shared storage.For more information about best practices for WebLogic Server on shared storage, see the Oracle Maximum Availability white paper, available at the following link:http://www.oracle.com/au/products/database/fusion-middleware-maa-155387.html
Upgrading PDC involves the following steps:
Perform the following tasks as described in the discussion of pre-installation tasks for the PDC patch installation in Oracle Communications Pricing Design Center Installation and System Administration Guide:
Shut down the current PDC instance.
Back up your existing PDC installation.
Install the recommended BRM version or patch.
Install the recommended version of JRE/JDK.
Upgrade WebLogic Server to the recommended version.
Enable the SSL Port for the WebLogic Server domain and ensure that the domain's state is Release Configuration.
Upgrade Oracle Application Development Runtime to the recommended version.
Set the path to the JAVA_HOME environment variable as described in "Setting the Java Home Path for PDC".
Provision PDC as described in "Provisioning PDC".
To set the Java home path for PDC:
Go to the MW_Home/user_projects/domains/bin directory, where MW_Home is the directory in which the Oracle Middleware components are installed.
Open the setDomainEnv.sh file in a text editor.
Search for the following line:
JAVA_HOME="
Edit the value to match the absolute path to the directory where you installed the version of Java required by the version of PDC to which you are upgrading.
For example:
JAVA_HOME="/pinhome/pin136/opt/portal/7.5/ThirdPartyApps/jre/1.7.0"
Save and close the file.
Restart the administration server.
Provision PDC as described in "Provisioning Applications and Suites" and, when specifying the domain parameters under ADMIN Configuration, ensure that you select the Do you want to upgrade PDC option.
This section describes provisioning the following Oracle Communications application types:
Order to Cash and OSS Fulfillment suites
OSM single nodes and OSM clusters
UIM single nodes and UIM clusters
ASAP
PCC
PDC
See "Provisioning BRM" for information about provisioning BRM.
To provision an Oracle Communications application or suite:
Log in to the Enterprise Manager Cloud Control administration console.
From the Enterprise menu, select Provisioning and Patching, and then Procedure Library.
The Deployment Procedure Manager page appears.
In the Select column, select the Communications Suite Installation Procedure option.
Click Launch.
The Communications Suite Provisioning page appears.
Under Choose Targets, click Add to select the types of Oracle Communications targets to provision.
The System Types dialog box appears.
Select the check box for each type of system to provision.
You can provision multiple system types at a time, but you cannot provision multiple OSS system types unless they are included in a suite. For example, you can select a PCC target and an OSM target, but if you select an invalid combination, such as an OSM target and an ASAP target, an error is displayed when you click OK and you cannot proceed.
To provision multiple OSS system types included in a suite, select one of the OSS Fulfillment Suite or Order to Cash Suite options.
Click OK.
The selected systems are added to the Choose Targets table, which displays each system's components.
For applications that require an Oracle WebLogic Server installation, an ADMIN row is automatically added for specifying the WebLogic Server installation used for provisioning. The ADMIN row also lets you provide details for the Fusion Middleware Repository Creation Utility (RCU).
For highly-available suites and application clusters, a PROXY row is automatically added for each OSM and UIM cluster and rows are added for OSM and UIM nodes.
(Optional) You can save your provisioning configuration as a custom system. This is useful when you plan to provision 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:
Click Save.
The Custom System Name dialog box appears.
In the Name field, enter a name for the configuration.
Click OK.
For targets that require an Oracle WebLogic Server domain, do the following:
Select the ADMIN row.
From the menu in the Target Name column, select the host of the administration server from which to provision the target.
The table is updated with the Free RAM, RAM, Free Storage and Storage values for the selected host.
In the Host Configurations region, under ADMIN Configuration, enter values for the required fields.
The RCU fields are required for OSM, UIM, and ASAP on Fusion Middleware 12c. On Fusion Middleware 11g, they are required for UIM only. Any values provided in these fields when provisioning OSM or ASAP on Fusion Middleware 11g are ignored.
(Optional) For PDC targets, to upgrade PDC, select the Do you want to upgrade PDC option.
For highly-available suites and cluster applications, do the following:
(Optional) To add more cluster nodes or proxies:
Select a UIM or OSM cluster row.
Click Configure.
Select Add Application or Add Proxy.
A row for the application or proxy is added to the table under the cluster.
Specify the port for the WebLogic Server proxy:
Select the PROXY row.
From the menu in the Target Name column, select the host for the proxy.
For highly-available and cluster environments intended for demonstrations and development, you can use the same host for the administration server, the proxy server, and the application.
The table is updated with the Free RAM, RAM, Free Storage and Storage values for the selected host.
In the Host Configurations region, in the WebLogic Proxy Server Port field, enter the port for the WebLogic Server proxy.
Note:
Using the Remove button can result in invalid configurations, such as an OSM cluster with no nodes. When provisioning a cluster, do not remove the individual application rows. When provisioning a highly-available suite, you can remove all of the rows representing an entire cluster, but do not remove only the individual application rows within the cluster.For PDC targets, do the following:
Select the PDC BRM PACK row.
In the Host Configurations region, under PDC BRM PACK Configuration, enter values for the required fields.
Selecting Support Migration is optional. The Migration Username and Migration User Password fields are required only if you select the Support Migration option.
(Optional) Select the Support Migration option and enter values for all of the Migration fields.
For each component in the Choose Targets table that you have not yet configured, do the following:
Select the component's row.
From the menu in the component's Target Name column, select the host on which to provision the component.
The table is updated with the Free RAM, RAM, Free Storage and Storage values for the selected target host.
Note:
For OSS applications, the provisioning procedure uses the hosts that you select for the application rows as managed servers in the WebLogic Server domain. The procedure installs the applications from the administration server host, not the managed server hosts. As a result, the application home directories are located on the administration server host.In the Host Configurations region, enter values for all required fields.
Note:
For PDC targets, the PDC Managed Server SSL Port field is required. During installation, Secure Sockets Layer (SSL) is enabled by default for the WebLogic servers used by PDC. If you do not want to use SSL, you can disable it in the WebLogic Server Administration Console. See the WebLogic Server documentation for more information about using SSL.Click Next.
Provide the preferred credentials for the target host. See "Setting Up Host Preferred Credentials" for more information.
Under Schedule, specify when the installation 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 Procedure Steps table displays all of the provisioning procedure steps and their corresponding statuses. View details about any step by selecting the option for that step in the Select column.This section provides an overview of how to set up a new Oracle Communications BRM system and components using the Communications Suite Installation Procedure. Applications Management Pack for Oracle Communications provides two options for provisioning BRM:
The BRM Basic option installs a limited set of components on a single target host. Use these systems for development or simple deployments of BRM. See "Provisioning a Basic BRM System" for a list of included components.
The BRM Advanced option enables selecting specific components for installation on one or more hosts. Use this option when installing production systems or testing systems with distributed component architecture.
Using the procedure requires an understanding of BRM architecture and installation. See Oracle Communications Billing and Revenue Management Installation Guide for more information about installation details, including installation parameters.
To set up a new BRM instance:
Download the required BRM InstallShield MultiPlatform (ISMP) packages from the Oracle Software Delivery Cloud to a location accessible from the Management Server. See "Downloading the BRM Installers" for more information.
Create the BRM source components in the Enterprise Manager Cloud Control Software Library. See "Creating the BRM Source Components" for more information.
Create the Oracle Enterprise Database used by BRM. See "Specifying the BRM Database" for more information.
Provision either a single instance BRM system or individual components on one or more host targets. See "Provisioning a Basic BRM System" and "Provisioning BRM Components" for more information.
Download the BRM ISMP installer packages from the Oracle Software Delivery Cloud at:
You must download all of the BRM 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 BRM components. For example, the Portal Base package includes the Connection Manager (CM), Data Manager (DM) 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 BRM 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
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 BRM 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 BRM 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 BRM 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.
BRM requires an Oracle Enterprise Database. When provisioning either a BRM 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 BRM System" for more information on provisioning a BRM system on a single host using an existing database.
Some BRM components, such as the Data Manager, Batch Rating Engine, and Real-time Pipeline, require connection to a BRM database to complete provisioning and to start the service. When provisioning one or more BRM components using the BRM Advanced option, you can specify whether to create a database or use an existing database. See "Provisioning BRM 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 BRM components:
Portal_Base
AccountSyncTool
RatedEventLoader
WebServicesMgr
BRM_JCA_Adapter
DM_AQ
PaymenttechMgr
EAI_FrameworkMgr
CollectionsMgr
ContentMgr
WirelessSuite
AccountMigrationMgr
To provision a BRM system on a single host:
Log in to the Enterprise Manager Cloud Control administration console.
From the Enterprise menu, select 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.
A BRM Basic entry is added to the Choose Targets table, which displays the BRM component as a row.
(Optional) You can save your provisioning configuration as a custom system. This is useful when you plan to provision 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:
Click Save.
The Custom System Name dialog box appears.
In the Name field, enter a name for the configuration.
Click OK.
Select the Target Name text box from the BRM row.
Select a managed host target from the drop down list.
The resource information for the target host appears. The Host Configurations area also displays the parameters required for BRM Basic provisioning.
Enter the path to the location where the BRM 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 BRM installer. Typically, you enter these values during the installer interview process. Enterprise Manager Cloud Control does not immediately validate the values you provide. 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 BRM instance. The procedure creates the specified database user based on the parameter values entered.
(Optional) Expand Advanced and edit the default port numbers for the BRM components.
For multischema environments, provide details for the additional BRM schemas:
Select Enable MultiDB.
From the No Of Schemas list, select the number of schemas to provision.
Click Go.
The Add Schemas dialog box appears with fields for the number of schemas that you selected from the No Of Schemas list.
In the Secondary Schema Details area, provide the value for the required parameters for each additional schema.
Click Save.
Click Next.
The Credentials page appears.
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 BRM 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 CM and DM 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 about installing a distributed architecture on multiple hosts.
To provision BRM components using the BRM Advanced option:
Log in to the Enterprise Manager Cloud Control administration console.
From the Enterprise menu, select 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.
A BRM Advanced row is added to the Choose Targets table, which displays the component as a row.
(Optional) You can save your provisioning configuration as a custom system. This is useful when you plan to provision 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:
Click Save.
The Custom System Name dialog box appears.
In the Name field, enter a name for the configuration.
Click OK.
Select the row for the added component and click Configure.
The Search and Select: Entities window containing a list of BRM ISMP installer packages.
Select the BRM 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.
An entry for the selected installer is added to the list of systems on the Choose Targets page.
Select the newly added installer row in the list.
The BRM Components list appears. This list contains the BRM components included in the installers selected.
Select the BRM components to provision.
Click Add.
A row for the BRM components is added to the list of systems on the Choose Targets page.
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 appear.
In Host Configurations - target_name, provide the parameters needed by the BRM installer for the selected component. Typically, you enter these values during the installer interview process. Enterprise Manager Cloud Control does not immediately validate the values you provide.
The BRM Advanced option enables specifying whether to use an existing BRM 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 BRM configuration. For information about pin_setup.values, see the chapter about installing BRM in Oracle Communications Billing and Revenue Management Installation Guide.
When adding components to an existing BRM 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 BRM 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 |
(Optional) Expand Advanced to specify the component's configuration parameters used in the BRM pin.conf file.
Click Next.
The Credentials page appears.
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 their corresponding statuses. View any step's status by clicking on the link in the Status column.Rediscover the BRM target as described in "Rediscovering BRM Targets Using Guided Discovery".
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:
You can start, stop, and restart BRM application processes on BRM base targets using the Enterprise Manager Cloud Control administration console. You can control single processes or all processes running on a managed host.
When starting or stopping all processes, only the BRM base components included in the pin_ctl.conf file will be started or stopped. You cannot start or stop all processes for BRM pipeline components.
See the discussion of customizing the pin_ctl utility environment variables in Oracle Communications Billing and Revenue Management System Administrator's Guide for more information about specifying components in the pin_ctl.conf file.
To start and stop BRM processes:
Log in to the Enterprise Manager Cloud Control administration console.
Click Targets, and then Communications Applications.
A table of managed BRM systems appears.
To stop or start either a one or more BRM processes on a managed target:
Click the top-level BRM_target_name link.
The home page for the BRM target appears.
Click either STOP ALL or START ALL.
(Optional) Monitor the status of the processes under Status.
To restart one or more BRM 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 appears.
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 Server domains hosting Oracle Communications applications. For example, you can start a WebLogic Server domain hosting OSM or PDC.
To start and stop WebLogic Server domains:
Log in to the Enterprise Manager Cloud Control administration console.
From the Targets menu, select Middleware.
The managed Middleware targets list appears.
Click the name of the domain to be controlled.
The selected middleware target's home page appears.
Under the target's name, from the system type menu, select Control.
Click Start Up or Shutdown for the desired operation.
The Credentials page appears.
Specify the required credential parameters.
Click OK.
Go to the middleware target's home page and confirm that the domain has either started up or shutdown.
You can patch BRM 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 BRM 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 more information about performing offline patch installation, see Oracle Enterprise Manager Lifecycle Management Administrator's Guide.
You can patch a single BRM target at a time using the BRM Patching Procedure. To patch multiple targets, run the procedure for each target individually.
Patching BRM involves the following tasks:
To patch managed BRM targets:
Log in to the Enterprise Manager Cloud Control administration console.
Ensure that the Management Agent for the target you intend to patch is up and running.
For information about verifying Management Agent status, see the discussion of controlling and configuring Management Agents in Oracle Enterprise Manager Cloud Control Administrator's Guide.
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 appears.
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 BRM target to patch.
Click Select.
The Choose Targets and Patches page appears. The BRM component to be patched is now listed.
In the target's row, click Add Patch.
The Choose BRM Patches window appears.
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 BRM release, specify a release value in the Search Releases field.
Click Search Patches.
A list of patches meeting the search criteria appears.
If needed, click the readme link for detailed patch information from Oracle Support.
Select the correct patches to apply and click Add Patches.
The Choose Targets and Patches page appears.
Under Target Configuration, provide the information required about your BRM target. Typically, this information includes the location of your BRM installation and database credentials.
Click Next.
The Credentials page appears.
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.
(Optional) Monitor the status of the patching process as described in "Monitoring BRM Patching Status".
Perform post-patch tasks as described in "BRM Post-Patch Tasks".
To monitor the status of the patching procedure:
Log in to the Enterprise Manager Cloud Control administration console.
From the Enterprise menu, select Patching and Provisioning, and then Procedure Activity.
In the Run column, click the name of the BRM patching procedure for which you want to monitor status.
The Procedure Steps table for the selected BRM patching procedure appears.
In the Name column, expand the BRM Patching Phase and host name entries.
All of the steps for the BRM patching procedure appear.
In the Status column, review the status of the steps.
In the Select column, select any step for which you want to view more details.
Click Refresh.
The status of all steps is updated.
If any steps fail, review the logs, resolve the issue, and try again.
For example, if the Automate Post Patch Steps PortalBase step fails and the Connection Manager target is down:
In the BRM_home/var/cm.pinlog file, search for the following line:
fm_collections_config_scenario_cache cache not specified in pin.conf
If the line appears, open the Connection Manager configuration file (BRM_home/sys/cm/pin.conf).
Add the following line anywhere in the file:
- cm_cache fm_collections_config_scenario_cache number_of_entries, cache_size, hash_size
where number_of_entries, cache_size, and hash_size are appropriate numbers for your system. For example:
- cm_cache fm_collections_config_scenario_cache 256, 40960, 54
Save and close the file.
Retry the patching procedure.
After patching BRM, perform the following tasks:
Verify the patch log files for any errors. By default, the patch log files are located in the following directory:
BRM_home/staging/patching/
Where BRM_home is the directory where BRM is installed.
Verify that the testnap utility works. See Oracle Communications Billing and Revenue Management Developer's Guide for information about using testnap.
The patching process backs up your Pipeline and Real-Time Pipeline registry files, such as wireless.reg and wirelessRealtime.reg, and creates new ones. For each registry file, merge any configuration changes that you made in the original files to the new registry files.
For example:
In the new Real-Time Pipeline registry file, search for the following section:
RealtimePipeline
{
ModuleName = NET_EM
Module
{
ThreadPool
{
Port =
Edit the Port entry so that the value is the same as in the backup registry file. For example:
ThreadPool{ Port = 14579
See the discussion of using registry files to configure Pipeline Manager in Oracle Communications Billing and Revenue Management System Administrator's Guide for more information about registry files.
Rediscover the BRM target as described in "Rediscovering BRM Targets Using Guided Discovery".
To view the list of patches that have been applied to a BRM CM or pipeline target:
Log in to the Enterprise Manager Cloud Control administration console.
Navigate to the home page for the BRM or Pipeline target to which you applied the patch, as described in "Viewing Home Pages".
The Patch Set Level field in the Summary displays the component's patch level.
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 applications, components, and suite level targets managed in Enterprise Manager Cloud Control. These summary pages provide an overview of the target, including information such as availability, metric alerts and other performance data.
Home pages are available for the following target types:
ASAP targets
BRM targets
ECE targets
Communications suite targets (Comms Suite target type)
OSM node and system targets
UIM targets
NCC targets
Oracle Communications Integration targets (Oracle AIA)
To view a home page:
Log in to the Enterprise Manager Cloud Control administration console.
From the Targets menu, select All Targets.
In the Target Type tree, select the type of target you want to view.
In the list of targets, click the name of the target you want to view.
The target's home page appears.
To view data from individual metrics for Oracle Communications application targets:
Log in to the Enterprise Manager Cloud Control administration console.
Navigate to the home page for the target for which you want to view metrics, as described in "Viewing Home Pages".
Under the target's name, from the target type menu, select 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.
Navigate to the home page for the target for which you want to view log files, as described in "Viewing Home Pages".
In the Quick Links region, 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.
Navigate to the home page for the target for which you want to configure metrics and thresholds, as described in "Viewing Home Pages".
Under the target's name, from the target type menu, select Monitoring, and then Metric and Collection Settings.
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.
Navigate to the home page for the target for which you want to configure collection schedules, as described in "Viewing Home Pages".
Under the target's name, from the target type menu, select Monitoring, and then Metric and Collection Settings.
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, ensuring 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.
Navigate to the home page for the target for which you want to configure collection schedules, as described in "Viewing Home Pages".
Under the target's name, from the target type menu, select Monitoring, and then 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 targets and dynamic groups for monitoring groups of targets in the administration console. For example:
Create a generic system that logically groups a selection of managed targets best suited for your environment, such as:
Targets that comprise a collection of integrated products, as in an Oracle Rapid Service Design and Order Deliver or Rapid Offer Design and Order Delivery solution
Targets in a highly-available BRM environment with services across hosts used for different deployment models
Create a dynamic group containing the same target type for monitoring groups of targets that perform the same function.
By default, Application Management Pack for Oracle Communications includes the following systems targets:
BRM Target
Comms Suite
See the discussion of dynamic groups in Oracle Enterprise Manager Cloud Control Administrator's Guide for more information about using dynamic groups.
See the overview of relationships in Oracle Enterprise Manager Lifecycle Management Administrator's Guide for more information about creating generic systems.
You can create new generic systems with the following methods:
By selecting the Enable Logical Grouping option and creating a new system or adding targets to an existing system when discovering and promoting targets as described in "Discovering and Rediscovering Targets Using Guided Discovery" and "Promoting Discovered Targets".
By creating the system and then adding targets to it. To create a new generic system and add targets to it:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Generic System.
Create a new generic system as described in the overview of relationships in Oracle Enterprise Manager Lifecycle Management Administrator's Guide.
You can monitor the overall health of your system and access more details about incidents, jobs, and unavailable or incompliant targets. You can also access the topology view to see the system topology and relationships between targets in the system.
To monitor the default BRM and Comms Suite systems, or generic systems you have created:
Log in to the Enterprise Manager Cloud Control administration.
From the Targets menu, select Systems.
In the Search list, select BRM Target, Comms Suite, or Generic System.
Click the right arrow icon.
Select a system from the list.
The home page for that system appears.
The home page for generic system targets organizes metrics into the regions described in Table 4-5.
Table 4-5 Regions on the Generic System Home Page
| Region | Description |
|---|---|
|
General |
Lists the user who created the system and whether privilege propagation is enabled in Enterprise Manager Cloud Control. |
|
Overview of Incidents and Problems |
Summarizes incidents and problems over the last 24 hours and the last 7 days. |
|
Jobs Activity |
Summarizes jobs started in the last 7 days. |
|
Status |
Summarizes the availability of the system overall and of the targets in the system. Lists the targets that have been down the most in the last 24 hours. |
|
Compliance Summary |
Summarizes any compliance evaluations, violations, and scores for the targets in the system. |
|
Dependent Targets |
Lists any targets dependent on the targets in the system. |
You can see a full list of metrics collected for a system target and you can monitor the data that an individual metric collects for the target. See "Viewing Target Metrics" for information about accessing the list of metrics.
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-6 describes each attribute in a condition.
Table 4-6 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-7 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-7 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:
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 about monitoring supported Oracle Communications application targets.
See the chapter about using Incident Management in Oracle Enterprise Manager Cloud Control Administrator's Guide for information about 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, Oracle Service-Oriented Architecture (SOA), and Coherence cluster targets. You use the monitoring capabilities to monitor the domains and clusters on which some Oracle Communications applications run.
See the chapters about managing Fusion Middleware, SOA, and Coherence in Oracle Enterprise Manager Cloud Control Oracle Fusion Middleware Management Guide for more information about discovering and monitoring these targets.
You must discover and promote SOA targets before discovering Oracle AIA targets. Discovering the SOA targets lets you resolve system faults in bulk for the AIA targets that you are monitoring. See "Viewing and Recovering from Faults" for more information.
Enterprise Manager Cloud Control monitors and manages Oracle Enterprise and Exadata Databases used by 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 view, edit, and compare configurations for managed BRM 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 BRM 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.
Navigate to the home page for the BRM target for which you want to view configurations, as described in "Viewing Home Pages".
Under the target's name, from the target type menu, select Configuration, and then Last Collected.
The configuration viewer for the selected system appears.
Table 4-8 describes the configuration viewer tabs.
Table 4-8 Configuration Viewer Tabs
| Tab | Description |
|---|---|
|
System_Name |
Contains host information and configuration parameters of the BRM 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 BRM managed targets. |
|
Immediate Relationship |
Displays the immediate relationships of the managed target to other selectable managed BRM targets. |
|
Member Of |
Lists selectable managed BRM target component's membership in managed system targets. |
|
Uses |
Lists selectable targets used by the managed BRM target. |
|
Used By |
Lists selectable targets using the managed BRM target. |
You can edit BRM configuration files with Enterprise Manager Cloud Control. See the chapter about 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 BRM component target. You can edit multiple BRM component configurations at a time.
To run the procedure:
Log in to the Enterprise Manager Cloud Control administration console.
Navigate to the home page for the BRM target for which you want to edit configurations, as described in "Viewing Home Pages".
In the Components Installed region, click the link to the component you want to configure.
The home page for the BRM component appears.
In the Quick Links region, click Edit Configurations.
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 BRM component targets appears.
Select the managed BRM targets to edit.
Click Select.
The selected components are added to the Choose BRM Targets table, which displays the component as a row.
Select the row for the added component.
The component's Configuration parameter in the Configurations - Name Value Mode appears. You edit in a text editor by setting the Config Mode value in the target row to File.
In Component Configurations - mode, provide the updated configuration parameters.
Note:
if you are editing the configuration of a Connection Manager Proxy, DM-EMAIL, or DM-FUSA target to which a patch has been applied, the value in the target_type.qm_port field will contain a dash (-). For example:
dm_email.qm_port -1234
Do not remove this dash when updating the port number.
Click Next.
The Credentials page appears.
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.
Rediscover the BRM target as described in "Rediscovering BRM Targets Using Guided Discovery".
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 BRM 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 BRM target configurations:
Log in to the Enterprise Manager Cloud Control administration console.
Navigate to the home page for the BRM target for which you want to compare configurations, as described in "Viewing Home Pages".
Under the target's name, from the target type menu, select Configuration, and then Compare.
The Compare Configurations wizard launches 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 appears.
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 5.
Provide a name in the Target Name field, if known.
Click Search.
A list of managed targets meeting the search criteria appears.
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 topology 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. The views are displayed in the Configuration Topology Viewer in Oracle Enterprise Manager Cloud Control.
The Configuration Topology Viewer shows you the relationships between different elements in the target's topology. Different elements appear for different target types. For example:
The topology for an OSM node target shows relationships between elements for the node, the WebLogic Server domain (including servers, hosts, homes, and clusters), and the database elements, while the topology for an OSM system also shows relationships between the members of the system.
The topology for an Oracle Communications Integration target shows relationships between elements for Oracle AIA, SOA, WebLogic Server, the Oracle AIA and SOA databases, and integrated applications such as OSM and BRM.
The topology for a Comms Suite target shows relationships between elements for the OSM nodes, OSM systems, ASAP, UIM, and the suite.
Note:
Database elements appear in a target's topology only if a Management Agent is installed on the database host.For BRM and OSM targets deployed on Oracle RAC databases, you must manually associate the database with the target from the BRM or OSM target's home page. See "Associating Oracle RAC Database Targets with BRM and OSM Targets" for more information.
You can filter the elements that appear in the topology using the sidebar and the View list. The View list includes the following views:
Uses: Shows the targets that the selected target depends on. If a target is having problems, this view can help you determine whether its problems have been caused by another target it depends on.
Used By: Shows the targets that depend on the selected target. This view can help you determine how shutting down the selected target might affect other targets.
System Members: Shows the members of the system (available only for targets that are systems, such as generic systems or OSM system targets).
The Configuration Topology Viewer also lets you view more information about the elements in the topology, including properties, metrics, and incidents.
You can use the Configuration Topology Viewer to view topology for systems, such as Comms Suite targets or generic systems that you have created, and individual applications, such as OSM node targets.
To view topology for systems or applications:
Log in to the Enterprise Manager Cloud Control administration console.
Do one of the following:
Access the Configuration Topology Viewer from the list of targets:
From the Targets menu, select All Targets.
From the Target Type tree, select the type of target for which you want to view the topology.
From the list of targets, right click the target for which you want to view the topology.
From the menu, select Configuration, and then Topology.
Access the Configuration Topology Viewer from the target home page:
From the Targets menu, select All Targets.
From the Target Type tree, select the type of target for which you want to view the topology.
From the list of targets, right click the name of the target for which you want to view the topology.
The target's home page appears.
Under the target's name, from the target type menu, select Configuration, and then Topology.
The Configuration Topology Viewer appears for the selected target, displaying the target's relationships to other targets and components.
(Optional) To view summary information about a component in the target's topology, including the target type, host, and number of incidents:
Hover your cursor over a component.
A pop-up caption containing the target name appears.
Hover your cursor over the arrows beside the target name.
The pop-up caption expands with summary information about the target.
(Optional) In the summary information pop-up caption, click any link to go to the related page. For example, click the target name to go to the target's home page, or click an incident icon to go to the Incident Manager.
(Optional) To view more detailed information about a component in the target's topology:
Click the component.
From the sidebar:
To view a summary of metrics for the component, expand Metric History.
To view information about the target, the host, incidents, jobs, and configuration compliance or changes, expand Properties and click any of the tabs.
(Optional) Click any link to go to the related page. For example, click the target name to go to the target's home page or click an incident name to go to the Incident Manager.
See the overview of Configuration Topology Viewer in Oracle Enterprise Manager Lifecycle Management Administrator's Guide for more information about using and interpreting topology.
See the chapters about managing Enterprise Database and Fusion Middleware in the Oracle Enterprise Manager Cloud Control Administrator's Guide for information about viewing topologies for these applications.
Oracle Enterprise Manager Cloud Control provides a framework and features for evaluating how well your targets comply with default standards that Oracle provides or custom standards that you create. See Oracle Enterprise Manager Lifecycle Management Administrator's Guide for more information about the compliance framework.
Application Management Pack for Oracle Communications provides ready-to-use compliance standards for UIM targets and OSM node targets. See "Managing OSS Compliance" for more information.