This chapter discusses configuring new and existing Oracle Communications targets in Oracle Enterprise Manager Cloud Control for use with Oracle Application Management Pack for Oracle Communications.
You provision, configure, and monitor Oracle Communications applications on hosts set up as managed targets in Enterprise Manager Cloud Control. Enterprise Manager Cloud Control also manages non-host targets. Managed non-host targets consist of applications and their components, and infrastructure such as Oracle Enterprise Databases and Oracle WebLogic Server domains.
An Oracle Management Agent runs on each host where one or more targets exist. The Enterprise Manager Cloud Control Management Server communicates with the Management Agent performing operations including application provisioning, configuration, and monitoring. You must install the Management Agent on any host you plan on using with Application Management Pack for Oracle Communications.
For more information about managed targets see the chapter about discovering and monitoring targets in Oracle Enterprise Manager Cloud Control Administrator's Guide available at:
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/discovery.htm
Application Management Pack for Oracle Communications uses preferred credentials for authentication between the Management Server and managed host targets. You set either default credentials for target types or target-specific credentials that are stored in the Enterprise Manager Cloud Control repository. Executing procedures and administrative tasks on host targets from the Management Server, such as provisioning applications and starting Oracle WebLogic Server domains, uses preferred credentials.
To set up host preferred credentials:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Security, and then Preferred Credentials.
Select Host under Target Type in the table.
Click Manage Preferred Credentials.
Do one of the following:
To set default preferred credentials, click Set under Default Preferred Credentials.
To use target preferred credentials, click Set under Target Preferred Credentials.
You can also set up target preferred credentials when adding a new managed host.
See the discussion of preferred credentials in Oracle Enterprise Manager Cloud Control Administrator's Guide for more information about preferred credentials.
Remote procedures and administrative tasks launched from the Management Server execute on target hosts. You must set the necessary file and directory permissions on target hosts for the users that perform actions on the target host. This ensures that commands and scripts execute properly on target hosts.
For example:
A WebLogic Server domain on a target host may be deployed in a mounted file share physically located on a third host. The user that starts this domain must exist on the third host and have execute permissions in the mounted file share to run the start scripts.
The BRM user must have full permissions on the directory where the agent is installed, and the agent user must have at least read and execute permission on the directory where BRM is installed. See "Setting Permissions on BRM Hosts" for more information about setting BRM permissions.
Ensure that the preferred credentials you create for the managed hosts in your environment exist on accessed hosts and have the needed permissions in the file locations where your applications may be installed.
To manually add a host to Enterprise Manager Cloud Control and install the Management Agent on the new host:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Add Targets Manually.
From the Instruction options, select Add Host Targets.
Click Add Host.
In the Add Host Targets: Host and Platform wizard, click Add.
In the Host field, enter the new target's host name.
From the Platform menu, select the correct operating system platform.
Click Next.
In the Installation Base Directory field, enter an installation base directory for the new target. This specifies the directory on the target host where you want the software binaries, security files, and inventory files of the Management Agent to be copied.
In the Instance Directory field, enter an instance directory on the new target. This specifies the directory on the target host where Management Agent configuration files are stored.
Select a Named Credential for Management Agent installation on the new target. See "Setting Up Host Preferred Credentials" for more information on setting up host credentials.
Confirm the Privileged Delegation Setting and Port, as well as any Optional Details needed in your installation.
Click Next.
Confirm the value in the Host Information field and click Deploy Agent.
Confirm that the Management Agent is properly installed and the new target is now visible in the administration console.
Note:
To see database associations in the topology view for Oracle Communications applications, you must add the host on which the database resides to Enterprise Manager Cloud Control and install a Management Agent on the host.For detailed information on installing the Management Agent, see Oracle Enterprise Manager Cloud Control Basic Installation Guide at:
http://docs.oracle.com/cd/E24628_01/install.121/e22624/install_agent.htm
For BRM targets, after installing the Management Agent on the BRM host, you must set specific permissions that correspond to the credentials you use in Enterprise Manager for monitoring BRM. These permissions allow you to use Enterprise Manager Cloud Control to perform actions on BRM components and run scripts located in the directory where the Management Agent is installed.
To set the required BRM permissions:
On the BRM host operating system, add the agent user and the BRM host user to the same user group.
Give BRM user read, write, and execute permissions for the directory where the Management Agent is installed.
Give the agent user read and execute permissions for the directory where BRM is installed.
Run the root.sh script in the directory where the Management Agent is installed.
You add Oracle Communications targets after their hosts obtain managed status and receive a Management Agent. You must also deploy the Application Management Pack for Oracle Communications plug-in to each Management Agent before performing discovery.
Add Oracle Communications application targets using guided or automatic discovery. Table 3-1 shows which type of discovery Application Management Pack for Oracle Communications supports for each application target.
Table 3-1 Types of Discovery for Oracle Communications Targets
| Type of Discovery | Target |
|---|---|
|
Automatic |
Oracle Communications Elastic Charging Engine (ECE) Oracle Communications Billing and Revenue Management (BRM) Oracle Application Integration Architecture (AIA) Oracle Communications Pre-Built Integrations (Oracle Communications Integration target type) Oracle Communications Network Charging and Control (NCC) Oracle Communications Order and Service Management (OSM) Oracle Communications Unified Inventory Management (UIM) Oracle Communications ASAP |
|
Guided |
BRM OSM UIM ASAP |
When you discover operations support systems (OSS) targets such as OSM, UIM, and ASAP, Enterprise Manager Cloud Control automatically discovers their WebLogic Server domains as well. The domain appears in the application's topology view and you can monitor the domain on the domain's home page.
Use the following methods for adding non-host Oracle Communications targets to your Enterprise Manager Cloud Control Management Server:
Discovering and Rediscovering Targets Using Guided Discovery
Adding Existing Oracle Communications Applications Using Monitoring Properties
Before discovering Oracle Communications application targets, obtain information about the application instances, such as installation locations, user credentials, and database and server connection details, from your system administrator.
Application Management Pack for Oracle Communications provides a guided discovery module for discovering existing targets on managed hosts for the following Oracle Communications applications:
BRM
OSM
UIM
ASAP
You must rediscover BRM targets after provisioning or uninstalling an individual BRM component, editing the BRM configuration files, or patching BRM.
Rediscovering a BRM target ensures that Enterprise Manager Cloud Control accurately reflects any changes made to the BRM system.
Rediscover a BRM target in the same way as you discover a new target, as described in "Discovering Targets Using Guided Discovery", ensuring that you do the following:
When you enter information in the Application Information fields, use the same values as the existing BRM target.
Select the Overwrite existing BRM Targets option before clicking Submit.
Confirm that Enterprise Manager Cloud Control has updated the BRM targets with the latest information.
When you rediscover the target, Enterprise Manager Cloud Control rediscovers the entire BRM suite of targets and components.
If you have configured automatic discovery for BRM, you are not required to rediscover BRM after provisioning or uninstalling components.
To discover and promote existing Oracle Communications application targets:
Back up existing Oracle Communications applications configurations files, such as pin.conf and pin_ctl.conf for BRM or oms-config.xml for OSM.
For BRM, confirm the variables listed in Table 3-2 are correctly set in the pin_ctl.conf file for your environment. This file is located in the BRM_home/bin directory on your BRM server, where BRM_home is the directory where BRM is installed.
See the section about customizing the pin_ctl utility environment variables in Oracle Communications Billing and Revenue Management System Administrator's Guide for more information on setting the required variables.
Table 3-2 Required pin_ctl.conf Variables for Guided Discovery
| Variable | Description |
|---|---|
|
NLS_LANG |
The database language used in the BRM database. |
|
ORACLE_HOME |
The home directory of the Oracle database used by BRM. |
|
TNS_ADMIN |
The directory in which the tnsnames.ora file referencing the database used by BRM is located. |
|
PIN_LOG_DIR |
The BRM directory in which logs are stored. Set PIN_LOG_DIR to: BRM_home/var |
|
LD_LIBRARY_PATH |
Set LD_LIBRARY_PATH to: Oracle_home/lib64:Oracle_Home/lib:Database_Home/lib: Database_home/rdbms/lib:$LD_LIBRARY_PATH |
|
LD_LIBRARY_PATH_64 |
Set LD_LIBRARY_PATH_64 to: Oracle_home/lib64:Oracle_home/lib:Database_home/lib: Database_home/rdbms/lib:$LD_LIBRARY_PATH |
|
PATH |
Set PATH to:
Oracle_Home/bin:$PATH
|
|
EVENT_HANDLER_PORT |
For BRM Pipeline only. Set EVENT_HANDLER_PORT to the port to which the Pipeline Manager Event Handler listens. |
Ensure that the Application Management Pack for Oracle Communications plug-in is deployed on the application host.
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Add Targets Manually.
The Add Targets Manually page appears.
From the Instruction options, select Add Targets Using Guided Process.
From Target Types, select one of the following:
For OSM, UIM, or ASAP targets, select Oracle Communications OSS Applications Discovery.
For BRM, select Oracle Communications Billing and Revenue Management Discovery.
Click Add Using Guided Process.
In the Choose Targets wizard, click Add.
Select the host on which the existing application is installed, and then click Select.
Select one of the following check boxes for the application to discover:
OSS (OSM, UIM, and ASAP)
BRM
You cannot discover both OSS and BRM targets at the same time.
Under Application Information, do one of the following:
To discover OSS targets, from the SelectApplication list, select the applications to discover. You can select more than one option.
To discover BRM targets, from the Select Product Type list, select PortalBase or Pipeline.
Enter the information for the environment in the Domain Configuration and Application Information fields.
Table 3-3 describes the BRM discovery fields.
Table 3-3 BRM Discovery Fields
| Fields | Description |
|---|---|
|
PipelineIFWhome or Portalbase Pinhome |
The path to the directory in which BRM is installed. |
|
ThirdPartyLocation |
The path to the directory in which the BRM Third Party package is installed. |
|
DatabaseHome |
The path to the Oracle Enterprise Database client package directory located on your BRM server. |
|
TNS_ADMIN |
The path to the directory on your BRM host in which the tnsnames.ora file pointing to your database is located. |
|
BRM Pin User |
The BRM host user. |
|
BRM Pin Password |
The BRM host password. |
|
BRM Registry File Name |
For Pipeline targets only, the names of the registry files, such as wireless.reg or wirelessRealtime.reg. To discover both pipeline and real-time pipeline targets, enter both registry files separated by a comma. For example:
wireless.reg,wirelessRealtime.reg
|
Table 3-4 describes the OSS discovery fields.
Table 3-4 OSS Discovery Fields
| Field | Description |
|---|---|
|
EM Repository Owner |
The user name of the Enterprise Manager repository owner. |
|
EM Repository Owner Password |
The password of the Enterprise Manager repository owner. |
|
WebLogic Hostname |
The host name of the domain on which the OSS products are deployed. |
|
WebLogic Port |
The port number of the host on which the OSS products are deployed. |
|
WebLogic Admin User |
The administrator user name with which to connect to the WebLogic Server host. |
|
WebLogic Admin Password |
The administrator password with which to connect to the WebLogic Server host. |
|
JMX Protocol |
The connection protocol to use when connecting to the WebLogic server. |
|
ASAP Environment ID |
The unique identifier for your ASAP environment. This field appears when you select ASAP from the SelectApplication list. |
(Optional) To rediscover the BRM base target after provisioning or uninstalling an individual BRM component, editing BRM configuration, or patching BRM:
Select the Overwrite existing BRM Targets option.
(Optional) To register the database for monitoring and topology view:
For UIM and ASAP targets, and BRM and OSM targets without an Oracle Real Application Clusters (Oracle RAC) database:
Select the Register DB option.
Provide the connection details and user credentials for the database. If you are discovering multiple OSS products, enter the database details for each product.
If you are discovering a UIM or ASAP target installed on an Oracle RAC database, selecting this option registers the database as a single-instance database. You cannot register a multi-instance database with these target types.
For BRM or OSM with an Oracle RAC database, do not select the Register DB option. Instead, associate the database manually after discovering the Oracle RAC target and the BRM or OSM target. See "Associating Oracle RAC Database Targets with BRM and OSM Targets" for more information.
(Optional) To create a logical group or add the target to an existing logical group:
Select the Enable Logical Grouping option.
Do one of the following:
Create a new logical group by entering a unique logical group name.
Add the target to an existing logical group by clicking Browse and selecting an existing logical group.
Click Submit.
Confirm that the existing application installation is added by verifying that the new targets are now visible in the Enterprise Manager Cloud Control administration console. Some applications result in a single target addition while others may include more than one target.
See "Monitoring Oracle Communications Application Targets" for information on how to view newly discovered targets.
Perform the appropriate post-discovery tasks for the target, as described in "Post-Discovery Tasks".
For general information about discovering existing hosts and promoting targets, see the discussion of automatically discovering and monitoring targets in Oracle Enterprise Manager Cloud Control Administrator's Guide.
Enterprise Manager Cloud Control can automatically discover unmanaged hosts on your network by using IP scanning or discovery modules. Once you have discovered unmanaged hosts, you can promote them to managed status. Promoting a host to managed status installs a Management Agent on the host, allowing Enterprise Manager Cloud Control to perform additional functions on the new target, including automatic discovery of applications.
Application Management Pack for Oracle Communications provides discovery modules used for automatically discovering the following target types on managed hosts:
ECE running on Oracle Coherence
BRM
Oracle Communications Integration (AIA)
NCC
OSM
UIM
ASAP
Automatic discovery involves the following tasks:
For ECE and Integration targets:
For all targets:
For BRM and OSM targets on Oracle RAC databases:
Before configuring automatic discovery for ECE targets:
Discover and promote the Coherence clusters on which ECE is running.
For more information about adding existing ECE Coherence clusters to Enterprise Manager Cloud Control, see the discussion of discovering Coherence targets in the Getting Started with Management Pack for Oracle Coherence chapter in Oracle Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management.
Enable the Coherence Management Pack as follows:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Management Packs, and then Management Pack Access.
Under View Options, select All Targets.
From the Pack Access options, select Pack Based Batch Update.
Enable the Management Pack for Oracle Coherence by selecting the pack and moving it to the Selected Packs window.
Click Apply.
Before configuring automatic discovery for Integration targets:
Discover and promote the SOA application and infrastructure targets on which the integration is deployed.
See the discussion of managing Oracle SOA in Oracle Enterprise Manager Cloud Control Oracle Fusion Middleware Management Guide for more information about discovering SOA targets.
Ensure that you have set the preferred credentials for the WebLogic Server domain on which the integration is deployed. See "Setting Up Host Preferred Credentials" for more information.
To configure managed hosts to run automatic discovery:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Configure Auto Discovery.
The Setup Discovery page appears.
Click the Targets on Hosts tab.
Highlight the host on which you want to discover targets. For ECE, this is a Coherence target host.
Click Discovery Modules.
From the Enabled column, select the type of target you want to discover.
You can select more than one type of target at once.
For all Oracle Communications target types except NCC, click Edit Parameters. NCC does not have any editable parameters.
For NCC targets, skip this step.
For all other targets, enter the parameters for the application you want to discover.
Table 3-5 describes the fields for ECE.
Table 3-5 ECE Automatic Discovery Fields
| Field | Description |
|---|---|
|
Agent EMD URL |
The main URL of the Management Agent on the target host. |
|
ECE Home |
The path to the directory in which ECE is installed. |
|
JMX Port |
The JMX port number of the ECE management node. |
|
Hostname |
The host name of the ECE management node. |
|
Service Name |
The service name of the ECE management node. |
Table 3-6 describes the fields for BRM.
Table 3-6 BRM Automatic Discovery Fields
| Field | Description |
|---|---|
|
Portalbase Pinhome |
The path to the directory in which BRM is installed. |
|
ThirdPartyLoc |
The path to the directory in which the BRM third-party package is installed. |
|
TNS_ADMIN |
The path to the directory on your BRM host in which the tnsnames.ora file that points to your database is located. |
|
Oracle Client Directory |
The Oracle home directory containing access libraries and binaries, corresponding to the 64-bit client. |
|
Pipeline InstallLoc |
The directory where BRM pipeline is installed. |
|
Pipeline RegistryFile |
The path to the BRM pipeline registry file. |
Table 3-7 describes the fields for OSS products.
Table 3-7 OSS Product Automatic Discovery Fields
| Field | Description |
|---|---|
|
WebLogic Host Name |
The host on which the OSS product is deployed. |
|
WebLogic Port |
The port number of the host on which the OSS product is deployed. |
|
WebLogic User Name |
The user name with which to connect to the WebLogic Server host. |
|
WebLogic Password |
The password with which to connect to the WebLogic Server host. |
|
T3/T3s Protocol |
The connection protocol to use when connecting to the WebLogic server. |
|
Deployment Names |
A colon-separated list of the types of OSS products to discover. The default value is oms:asap:oracle.communications.inventory. |
|
Comms Plugin Version |
The version of Application Management Pack for Oracle Communications that you are using. |
Table 3-8 describes the fields for Integration targets (Oracle AIA).
Table 3-8 Integrations Automatic Discovery Fields
| Field | Description |
|---|---|
|
SOA WebLogic Admin Server Host Name |
The host name of the WebLogic Server administration server. |
|
SOA WebLogic Admin Server Port |
The port number of the WebLogic Server administration server. |
|
SOA WebLogic Protocol (t3/t3s) |
The connection protocol to use when connecting to the WebLogic server. |
|
SOA WebLogic Admin Server User Name |
The user name with which to connect to the WebLogic Server host. |
|
SOA WebLogic Admin Server Password |
The password with which to connect to the WebLogic Server host. |
These fields are not immediately validated. The discovery module uses the values to contact the Management Agent on the specified host when attempting to add the target and reports any validation errors at that time.
Click OK in the Edit Parameters window.
Click OK.
The list of managed hosts appears.
By default, automatic target discovery runs once daily. You can set a discovery interval to suit your environment, as described in Oracle Enterprise Manager Cloud Control Administrator's Guide.
You can also run automatic discovery on demand at any other time you want to discover targets.
To run automatic discovery on demand:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Configure Auto Discovery.
Click the Targets on Hosts tab.
Select a row from the list of managed host targets.
Click Discover Now.
A confirmation dialog box appears.
Click Yes.
The Targets on Hosts tab appears.
If the discovery succeeded, a green check mark appears beside the date and time in the Most Recent Ended On column. You can promote the targets as described in "Promoting Discovered Targets".
If the discovery failed, a red and white X appears beside the date and time in the Most Recent Ended On column. Follow the steps in "Viewing Automatic Discovery Errors" to help you resolve the error and then retry the automatic discovery.
To view failed automatic discoveries and get more details about automatic discovery errors:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Configure Auto Discovery.
Click the Targets on Hosts tab.
From the Most Recent Ended On column, click the date and time link for the failed discovery.
The diagnostic details for that host appear.
From the Error column, click an error link for more details.
The full error text appears. For example:
Failure ::Wrong Directories for the host entry example.com : InstallLocation - /brm_home/installation
Use the information provided in the error text to help you resolve the automatic discovery failure. In the example above, you would provide the correct installation directory in the Edit Parameters dialog box for the BRM discovery module of the example.com host.
After automatically discovering targets, promote them so that you can monitor and manage them. For ECE, you must promote each cluster and node found by automatic discovery.
To promote discovered targets:
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Auto Discovery Results.
The Auto Discovery Results page appears
Click the Targets on Hosts tab.
Select the row of the automatically discovered targets that you want to promote.
Note:
Oracle ECE Cluster target types include BRM in the target name. Oracle ECE Node target types include the name of the host and the name of the ECE node in the target name.Click Promote.
The Promote target_type Target(s) page appears.
For BRM and NCC targets, skip this step.
For ECE, OSS, and Integrations targets, enter the required credentials and properties for the target.
Table 3-9 describes the required fields for ECE.
Table 3-9 ECE Promotion Fields
| Field | Description |
|---|---|
|
Monitoring Username |
The user name for the ECE monitoring user. |
|
Monitoring Password |
The password for the ECE monitoring user. |
|
Bulk Operations MBean |
The name of the bulk operations MBean. |
|
Cluster Name |
The name of the ECE cluster. |
|
Communication Protocol |
The cluster communications protocol. |
|
ECE Installation Directory |
The path to the directory where ECE is installed. |
|
ECE Version |
The version of ECE. |
|
JMX Remote Port |
The ECE target's JMX remote port. |
|
Machine Name |
The host on which the ECE target runs. |
|
Service Name |
The service used for performing remote management. |
|
Service URL |
The service URL used for remote management. |
Table 3-10 describes the required fields for OSS targets:
Table 3-10 OSS Promotion Fields
| Property | Description |
|---|---|
|
EM repository Owner |
The user name of the Enterprise Manager repository owner. |
|
EM repository Owner Password |
The password of the Enterprise Manager repository owner. |
|
WebLogic Admin Password |
The password of the WebLogic Server administrator account. |
|
ASAP Environment ID |
The unique identifier for your ASAP environment. This field appears when you are promoting an ASAP target. |
Table 3-11 describes the required fields for Integration targets (AIA).
Table 3-11 Integration Promotion Fields
| Property | Description |
|---|---|
|
EM Admin/Sysman User-name |
The user name of the Enterprise Manager administrator. |
|
EM Admin/Sysman Password |
The password of the Enterprise Manager administrator. |
|
SOA Home |
The path to the directory in which SOA is installed. |
|
Communications Integration Home (Pre-built/AIA Home) |
The path to the directory in which the Oracle AIA pre-built integrations are installed. |
|
Host-Name |
The host name of the database. Enter values for this field under both Communications Integration and SOA database details. |
|
Port |
The port number of the database. Enter values for this field under both Communications Integration and SOA database details. |
|
SID |
The unique identifier of the database. Enter values for this field under both Communications Integration and SOA database details. |
|
User-Name |
The user name of the database user. Enter values for this field under both Communications Integration and SOA database details. |
|
Password |
The password of the database user. Enter values for this field under both Communications Integration and SOA database details. |
|
System User-Name |
The user name of the database system user. Enter values for this field under both Communications Integration and SOA database details. |
|
System Password |
The password of the database system user. Enter values for this field under both Communications Integration and SOA database details. |
For NCC, OSS, and Integrations targets, skip this step.
For BRM targets, edit the monitoring credentials:
Click Specify Common Monitoring Credentials.
Select an existing credential name or create a new one.
In the Credential Details table, enter the username and password for the BRM user for whom you set permissions in "Setting Permissions on BRM Hosts".
Click Save.
The credentials for all BRM targets in the list of targets to be promoted are saved.
(Optional) To register the database for monitoring and topology view, do one of the following:
For NCC, ECE, UIM, and ASAP targets, and BRM and OSM targets without an Oracle RAC database:
Select the Register DB option.
Provide the connection details and user credentials for the database.
If you are promoting an NCC, ECE, UIM, or ASAP target installed on an Oracle RAC database, selecting this option registers the database as a single-instance database. You cannot register a multi-instance database with these target types.
For BRM or OSM with an Oracle RAC database, do not select the Register DB option. Instead, associate the database manually after discovering the Oracle RAC target and the BRM or OSM target. See "Associating Oracle RAC Database Targets with BRM and OSM Targets" for more information.
For Integration targets:
Under Communication Integration Database Detail or SOA Database Detail, select the Register DB for Monitoring option.
You can register the Oracle AIA database only, the SOA Database only, or both.
Provide values for the System User-Name and System Password fields.
For Integrations targets, skip this step.
(Optional) For all other target types, to create a logical group or add the target to an existing logical group:
Select the Enable Logical Grouping option.
Do one of the following:
Create a new logical group by entering a unique logical group name.
Add the target to an existing logical group by clicking Browse and selecting the logical group.
Click Promote.
The target is promoted to managed status. You can view the target on the All Targets page.
Perform the appropriate post-discovery tasks for the target, as described in "Post-Discovery Tasks".
For some Oracle Communications applications you must perform additional tasks before you can monitor them correctly. The following tasks apply to certain targets:
Adding BRM Components to the pin_ctl.conf File: For BRM targets.
Configuring SNMP for BRM Pipeline Targets: For BRM Pipeline and Real-Time Pipeline targets.
Associating Oracle RAC Database Targets with BRM and OSM Targets: For application targets installed on Oracle RAC databases.
Adding the UIM Database Password to the Communications Suite Target: For UIM targets in a Communications suite.
Configuring Compliance for OSM Clusters: For OSM targets in clustered environments.
You may have installed BRM components that do not appear in the pin_ctl.conf file. Before you can use Enterprise Manager Cloud Control to start or stop these components, you must add them to pin_ctl.conf.
If you do not know whether you installed components that do not appear in pin_ctl.conf, you can check using the following procedure.
To add components to pin_ctl.conf:
Log in to the Enterprise Manager Cloud Control administration console.
Navigate to the BRM target home page, as described in "Viewing Home Pages".
In the Components Installed region, review the list of installed components.
On the host where BRM is installed, open the following file:
BRM_home/bin/pin_ctl.conf
Search for the following line:
1 dm_oracle
Compare the list of components to the list in the Components Installed region of the BRM target home page in Enterprise Manager Cloud Control.
Add a line for any components that appear in the Components Installed region but do not appear in the pin_ctl.conf file.
For example, if DM_AQ and DM_PROV_TELCO components appear in the Components Installed region, add the following lines:
1 dm_oracle 1 dm_prov_telco 1 dm_aq start_dm_aq cpidproc:dm_aq: cport:port
where port is the port on which the Oracle Advanced Queueing Data Manager listens.
Note:
The target name column of the Components Installed region includes host information with the component name. Do not include the host in pin_ctl.conf.Save and close the file.
After discovering BRM Pipeline and Real-Time Pipeline targets, configure Simple Network Management Protocol (SNMP). For more information about using SNMP with BRM, see the discussion of using the SNMP Instrumentation protocol to monitor and control BRM components in Oracle Communications Billing and Revenue Management System Administrator's Guide.
To configure SNMP, do the following for each BRM Pipeline and Real-Time Pipeline target:
Install the SNMP software as described in Oracle Communications Billing and Revenue Management Installation Guide.
Start the SNMP master agent with the following command:
master_agent -l Master_agent_port -x AgentX_port &
where Master_agent_port is the port for the SNMP server and AgentX_port is the port for the SNMP agent
Open the following file:
Pipeline_home/conf/wireles.reg
where Pipeline_home is the directory where the BRM Pipeline target is installed
In the Instrumentation section, under SnmpServer, edit the value for the Port entry to match the value you used for AgentX_port when you started the master agent. For example:
Instrumentation
{
SnmpServer
{
Port = AgentX_port
Save and close the file.
Log in to the Enterprise Manager Cloud Control administration console.
From the Targets menu, select All Targets.
In the Target Type tree, select Oracle BRM Pipeline or Oracle BRM RTP.
From the list of targets, right-click the name of the BRM Pipeline target for which you are configuring SNMP.
From the context menu, select Target Setup, and then Monitoring Credentials.
In the SNMP AgentX Port field, enter the port that you used for AgentX_port when you started the master agent.
In the SNMP Master Agent Port field, enter the port that you used for Master_agent_port when you started the master agent.
Click OK.
The home page for the BRM Pipeline target appears.
In the Summary region, click ReStart.
When your BRM or OSM targets are installed on Oracle RAC databases, you must perform additional tasks before you can view the Oracle RAC database details on the application target's topology page.
You can associate an Oracle RAC database with BRM and OSM only. For other applications, although you can register the Oracle RAC database when discovering or promoting the target, it will be shown as a single-instance database on the topology page.
To associate an Oracle RAC database with a BRM or OSM target:
In any order, do the following:
Discover the Oracle RAC database target as described in the discussion of discovering cluster database targets in Oracle Enterprise Manager Cloud Control Administrator's Guide.
Discover the BRM or OSM target as described in "Adding Oracle Communications Targets". During discovery or while promoting automatically discovered targets, do not select the Register DB option.
Do one of the following:
On the BRM target home page, click AssociateRACDB.
On the OSM target home page, click Associate RAC Database.
Confirm that the database was successfully associated by viewing the BRM or OSM target's topology page. See "Viewing Topology" for more information about topology pages.
To add the UIM database password to the communications suite target:
Log in to the Enterprise Manager Cloud Control administration console.
Navigate to the UIM target home page, as described in "Viewing Home Pages".
Under the target's name, from the target type menu, select Target Setup, and then Monitoring Configuration.
In the UIM DB User Password field, enter the database password for UIM.
Click OK.
If you are monitoring compliance for OSM targets in a clustered environment, you must configure coherence remote management, which allows you to specify one server as the MBean server that manages all other servers.
You configure coherence remote management by adding and setting system properties for the OSM managed servers that you have discovered.
To configure coherence remote management:
Go to the directory of the domain where OSM is deployed, for example:
/u01/Oracle/Middleware/user_projects/domains/OSM_Domain
Open the startup script for the single OSM managed server that you want to designate as the MBean server.
Add and set the following properties:
-Dtangosol.coherence.management.remote=true -Dtangosol.coherence.management=all
Save and close the file.
Open the startup script for any other OSM managed server.
Add and set the following properties:
-Dtangosol.coherence.management.remote=true -Dtangosol.coherence.management=none
Save and close the file.
Repeat steps 5 to 7 until you have updated the startup scripts for all managed servers that you have discovered.
You can manually add existing installations of supported versions of Oracle Communications applications or components as managed non-host targets by specifying the target host type and monitoring properties.
The plug-in supports the following Oracle Communications application target types for property monitoring:
ASAP Target
NCC SLC Target
NCC SMP Target
NCC VWS Target
OSM Target
Oracle BRM Account Sync Tool
Oracle BRM Batchcontroller Process
Oracle BRM Connection Manager
Oracle BRM Connection Manager Master Process
Oracle BRM Connection Manager Proxy
Oracle BRM DM AQ
Oracle BRM DM Invoice
Oracle BRM DM LDAP
Oracle BRM DM Prov Telco
Oracle BRM DM-EAI
Oracle BRM DM-EMAIL
Oracle BRM DM-FUSA
Oracle BRM DM-TAXWARE
Oracle BRM DM-VERTEX
Oracle BRM DMO
Oracle BRM DMTT
Oracle BRM Diameter Gateway
Oracle BRM EAI JS Component
Oracle BRM Formatter Process
Oracle BRM Pipeline
Oracle BRM REL
Oracle BRM RTP
Oracle BRM SNMP Process
Oracle BRM UEL
Oracle ECE Cluster
Oracle ECE Node
UIM Target
To manually add existing Oracle Communications applications or processes:
Add the server host of each application or process instance as a managed host and install the Management Agent. See "Adding Host Targets Manually and Installing the Management Agent" for more information.
Deploy the Application Management Pack for Oracle Communications plug-in to the Management Agent. See "Deploying the Application Management Pack for Oracle Communications Plug-In" for more information.
Log in to the Enterprise Manager Cloud Control administration console.
From the Setup menu, select Add Target, and then Add Targets Manually.
Select Add Targets by Specifying Target Monitoring Properties.
From Target Types, select the Oracle Communications application or process.
Click the magnifying glass to search for the monitoring agent running on the host where the Oracle Communications application or process is running. The Search and Select: Targets window appears.
Select the Management Agent running on the Oracle Communications application or process host.
Click Select.
Click Add Manually....
Provide the required parameters for the target type. Obtain these values from the installed Oracle Communications application or component environment. See the documentation for the application or component for more information.
Click OK to add the new target.
Confirm that the new target is now visible in the Enterprise Manager Cloud Control administration console.
This section describes the steps needed to prepare a new host for Oracle Communications application provisioning. You must prepare a host for an Oracle Communications application before initiating provisioning from Enterprise Manager Cloud Control. This involves the following steps:
The managed host must meet the application's hardware and software requirements. See the product's installation guide for more information.
Hardware and software requirements vary depending on the type of installation you are performing. For example, development and testing systems require lower minimum technical requirements compared to production systems. However, all managed hosts must meet the minimum requirements.
Most Oracle Communications applications require foundational software, such Oracle Enterprise Database or Oracle WebLogic Server, before installation. Required software can exist on the same host you are provisioning an Oracle Communications application on or on a remote host. Consult the installation guides for these requirements. Foundational software configuration details, such as host names, credentials, and port numbers may be required for provisioning.
You can install foundational software on any host, then use discovery to promote the hosts to managed target status. This enables monitoring components such as Enterprise Database and WebLogic Server domains in Enterprise Manager Cloud Control along side Oracle Communications applications.
Add the new host to Enterprise Manager Cloud Control and install a Management Agent on the host either manually or with discovery. See "Adding Oracle Communications Targets" for more information.
You must download supported versions of Oracle Communications applications before installing them on managed hosts in Enterprise Manager Cloud Control. The Communications Suite Installation Procedure copies the installers onto the target host during the installation process.
Obtain the installer packages for supported products from the Oracle Software Delivery Cloud at:
See "Supported Applications" for a list of supported Oracle Communications applications and versions.
Place the installers in a shared network location accessible by the Enterprise Manager Cloud Control host and the managed targets on which Oracle Communications applications will be installed.
For BRM, you must upload the installers into the BRMComponents folder in the Software Library. See "Creating the BRM Source Components" for more information on uploading BRM components.
WARNING:
Do not change names of the BRM installation packages. The provisioning procedure does not support custom file names for the installation packages.
See "Provisioning and Upgrading Applications" for more information on the installation procedure.