3 Configuring Oracle Communications Targets

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.

Understanding Oracle Communications Targets

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.

About Host Preferred Credentials

Application Management Pack for Oracle Communications uses preferred credentials for authentication between the Management Server and managed host targets. Preferred credentials let you perform operations, such as provisioning applications or starting Oracle WebLogic Server domains, on managed targets without being prompted to log in to the target. The credentials are stored in the Enterprise Manager Cloud Control repository.

Host preferred credentials are defined according to the following aspects:

  • Target specificity:

    • Default: Applies to all host targets.

    • Target-specific: Applies to a specific host target.

    Target-specific credentials override the default credentials. Default credentials apply to any targets that do not have target-specific credentials defined.

  • Privilege level:

    • Normal: Used for simple administration tasks.

    • Privileged: Used for privileged administration tasks that require root access.

    Application Management Pack for Oracle Communications requires both normal and privileged credentials for each host.

  • User specificity:

    • Global: Applies to all Enterprise Manager Cloud Control users. Only administrators with the required privileges can set global preferred host credentials.

    • User-specific: Applies only to the user who is currently logged in.

See the discussion of preferred credentials in Oracle Enterprise Manager Cloud Control Administrator's Guide for more information about preferred credentials.

Setting Host Preferred Credentials

To set host preferred credentials:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. From the Setup menu, select Security and then Preferred Credentials.

  3. From the Target Type column, select Host.

  4. Click Manage Preferred Credentials.

  5. Do one of the following:

    • To set global host preferred credentials, click the Global Preferences tab.

    • To set user-specific host preferred credentials, click or stay on the My Preferences tab.

  6. From the lists of default or target preferred credentials, select the row for which you want to set host credentials.

  7. Click Set.

  8. Do one of the following:

    • To use an existing named credential:

      1. From the Credential Name menu, select a named credential.

      2. Verify the details.

      3. Click Save.

    • To create a new named credential:

      1. Select the New option.

      2. Enter the user name and password.

      3. From the Run Privilege menu, select the relevant run privilege.

      4. In the Save As field, enter a name for the new credential.

      5. Click Save.

You can also set target named credentials when adding a new managed host.

Ensuring Correct Preferred Credentials Permissions on Host Targets

Remote procedures and administrative tasks launched from the Management Server run 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 run 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 and ECE 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 are installed.

Adding Host Targets Manually and Installing the Management Agent

To manually add a host to Enterprise Manager Cloud Control and install the Management Agent on the new host:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. From the Setup menu, select Add Target and then Add Targets Manually.

  3. Do one of the following, based on the Enterprise Manager Cloud Control version you are using:

    • For 12c, from the Instruction options, select Add Host Targets, and then click Add Host.

    • For 13c, click Install Agent on Host.

  4. In the Add Host Targets: Host and Platform wizard, click Add.

  5. In the Host field, enter the new target's host name.

  6. From the Platform menu, select the correct operating system platform.

  7. Click Next.

  8. 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.

  9. 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.

  10. Select a Named Credential for Management Agent installation on the new target. See "About Host Preferred Credentials" for information about setting up host credentials.

  11. Confirm the Privileged Delegation Setting and Port, as well as any Optional Details needed in your installation.

  12. Click Next.

  13. Confirm the value in the Host Information field and click Deploy Agent.

  14. 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

Setting Permissions on BRM and ECE Hosts

For BRM and ECE targets, after installing the Management Agent on the BRM or ECE host, you must set specific permissions that correspond to the credentials you use in Enterprise Manager for monitoring BRM or ECE. These permissions allow you to use Enterprise Manager Cloud Control to perform actions on BRM and ECE components and run scripts located in the directory where the Management Agent is installed.

To set the required permissions:

  1. On the BRM or ECE host operating system, add the agent user and the BRM or ECE host user to the same user group.

  2. Give the BRM or ECE user read, write, and execute permissions for the directory where the Management Agent is installed.

  3. Give the agent user read and execute permissions for the directory where BRM or ECE is installed.

  4. As the root user, run the root.sh script in the directory where the Management Agent is installed.

Adding Oracle Communications Targets

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 Application Integration Architecture (Oracle AIA) (Oracle Communications Integration target type)

Oracle Communications Billing and Revenue Management (BRM) and the following BRM components:

  • Elastic Charging Engine (ECE)

  • Pricing Design Center (PDC)

Oracle Communications Network Charging and Control (NCC)

Oracle Communications Offline Mediation Controller

Oracle Communications operations support systems (OSS) applications:

  • Oracle Communications ASAP

  • Oracle Communications Order and Service Management (OSM)

  • Oracle Communications Unified Inventory Management (UIM)

Guided

ASAP

BRM

Offline Mediation Controller

OSS applications:

  • ASAP

  • OSM

  • UIM

PDC

When you discover targets deployed on WebLogic Server domains, such as OSM, UIM, ASAP, and PDC, Enterprise Manager Cloud Control automatically discovers the 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.

When you discover BRM targets, you discover both included components, such as the BRM Batch Controller, and custom components, such as cloned Data Managers and Connection Managers. All actions supported for included components are supported for custom components, including monitoring, process control, and configuration management.

When you discover PDC targets, you can also discover a target representing a PDC transformation engine. If the transformation engine and the main PDC instance are on the same host, you discover them at the same time using the same module. If they are on different hosts, you discover them using two separate modules and associate them using the main PDC module.

Discovering applications involves the following tasks:

  1. Pre-Discovery Tasks

  2. One of the following discovery methods:

  3. Post-Discovery Tasks

Pre-Discovery Tasks

Perform the tasks described in this section before discovery.

For all target types, see "Common Pre-Discovery Tasks".

For BRM targets, see "BRM Pre-Discovery Tasks".

For ECE targets, see "ECE Pre-Discovery Tasks".

For Oracle Communications Integration targets, see "Oracle Communications Integration Pre-Discovery Tasks".

Common Pre-Discovery Tasks

Before discovering Oracle Communications applications, perform the following tasks:

  1. Back up existing configurations files, such as pin.conf and pin_ctl.conf for BRM or oms-config.xml for OSM.

  2. Obtain information from your system administrator about the application instances, such as installation locations, user credentials, and database and server connection details.

    You will enter this information into the Enterprise Manager Cloud Control administration console during discovery.

    For details about the application information you will enter in the console fields, see the section for the type of discovery you will use:

BRM Pre-Discovery Tasks

Before manually discovering BRM targets, 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.

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 where the tnsnames.ora file referencing the database used by BRM is located.

PIN_LOG_DIR

The BRM directory where 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 Manager only.

Set EVENT_HANDLER_PORT to the port to which the Pipeline Manager Event Handler listens.

ECE Pre-Discovery Tasks

Before configuring automatic discovery for ECE targets:

  1. 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.

  2. Enable the Coherence Management Pack as follows:

    1. Log in to the Enterprise Manager Cloud Control administration console.

    2. From the Setup menu, select Management Packs and then Management Pack Access.

    3. Under View Options, select All Targets.

    4. From the Pack Access options, select Pack Based Batch Update.

    5. Enable the Management Pack for Oracle Coherence by selecting the pack and moving it to the Selected Packs section.

    6. Click Apply.

Oracle Communications Integration Pre-Discovery Tasks

Before configuring automatic discovery for Oracle Communications Integration targets:

  1. Discover and promote the SOA application and infrastructure targets on which the Oracle AIA is deployed.

    See the discussion of managing Oracle SOA in Oracle Enterprise Manager Cloud Control Oracle Fusion Middleware Management Guide for information about discovering SOA targets.

  2. Ensure that you have set the preferred credentials for the WebLogic Server domain on which the Oracle AIA is deployed. See "About Host Preferred Credentials" for more information.

Discovering and Rediscovering Targets Using Guided Discovery

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

  • Offline Mediation Controller

  • OSS:

    • ASAP

    • OSM

    • UIM

  • PDC (includes PDC transformation targets)

You must rediscover BRM targets after provisioning or uninstalling an individual BRM component, editing the BRM configuration files, or patching BRM.

Discovering Targets Using Guided Discovery

To discover and promote existing Oracle Communications application targets:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. From the Setup menu, select Add Target, and then Add Targets Manually.

    The Add Targets Manually page appears.

  3. Do one of the following, based on the Enterprise Manager Cloud Control version you are using:

    • For 12c:

      1. From the Instruction options, select Add Targets Using Guided Process.

      2. From Target Types, select the type of target to discover.

        For ASAP, OSM, or UIM, select Oracle Communications OSS Applications Discovery.

        For PDC transformation targets, if the transformation target is on the same host as the main PDC target, select Oracle Communications Pricing Design Center Discovery. If the transformation target is on a different host than the main PDC target, select Oracle Communications Pricing Design Center Transformation Discovery.

      3. Click Add Using Guided Process.

    • For 13c:

      1. Click Add Using Guided Process.

        The Add Using Guided Process dialog box appears.

      2. Select the type of target to discover.

        For ASAP, OSM, or UIM, select Oracle Communications OSS Applications Discovery.

        For PDC transformation targets, if the transformation target is on the same host as the main PDC target, select Oracle Communications Pricing Design Center Discovery. If the transformation target is on a different host than the main PDC target, select Oracle Communications Pricing Design Center Transformation Discovery.

      3. Click Add.

  4. In the Choose Targets wizard, click Add.

  5. Select the host on which the existing application is installed, and then click Select.

  6. Select one of the following options for the application to discover:

    • BRM

    • OMC (Offline Mediation Controller)

    • OSS (OSM, UIM, and ASAP)

    • PDC (includes PDC transformation nodes)

    You cannot discover both OSS and BSS targets (including BRM, Offline Mediation Controller, and PDC) at the same time.

  7. For Offline Mediation Controller and PDC, skip this step.

    For BRM targets, from the Select Product Type menu, select the type of BRM system to discover.

    For OSS targets, from the Select Application menu, select the applications to discover.

  8. Enter the required information in the Application Information fields. See the following for information about these fields:

  9. To rediscover the BRM base target, select the Overwrite existing BRM Targets option. See "Rediscovering BRM Targets Using Guided Discovery" for more information about rediscovery.

  10. (Optional) To register the database for monitoring and topology view for ASAP, PDC, and UIM targets, and BRM and OSM targets without an Oracle Real Application Clusters (Oracle RAC) database:

    1. Select the Register DB option.

    2. Provide the connection details and user credentials for the database in the Database Registration Details fields. See Table 3-7, "BRM Database Association Fields" and Table 3-8, "Application Database Association Fields" for information about these fields.

      If you are discovering multiple OSS products, enter the database details for each product.

      If you are discovering an ASAP, UIM, or PDC 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.

    Note:

    For BRM or OSM with an Oracle RAC database, do not select the Register DB option. Instead, associate the database manually as part of the post-discovery tasks.

  11. (Optional) To create a logical group or add the target to an existing logical group:

    1. Select the Enable Logical Grouping option.

    2. 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.

  12. (Optional) To include the target in a dynamic group, enter values in the TargetProperties fields. For example:

    • To include the target in a dynamic group of production environments, select Production from the Lifecycle Status menu.

    • To include the target in a dynamic group of OSS targets, enter OSS in the Line of Business field.

  13. Click Submit.

  14. 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.

  15. 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.

Rediscovering BRM Targets Using Guided Discovery

Rediscovering a BRM target ensures that Enterprise Manager Cloud Control accurately reflects any changes made to the BRM system.

You must rediscover a BRM target after:

  • Provisioning or uninstalling an individual BRM component

  • Editing BRM configuration

  • Patching BRM

If you have configured automatic discovery for BRM, you are not required to rediscover BRM after provisioning or uninstalling components.

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.

Guided Discovery Fields

This section describes the information required for guided discovery.

Table 3-3 describes the guided discovery fields for BRM targets.

Table 3-3 BRM Guided Discovery Fields

Field Description

Select Product Type

The type of BRM system to discover (base or Pipeline).

PipelineIFWhome or Portalbase Pinhome

The path to the directory where BRM is installed.

ThirdPartyLocation

The path to the directory where the BRM third party software 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 where the tnsnames.ora file that points to your database is located.

BRM Host UserName

The BRM host user.

BRM Host Password

The password for the BRM host user.

BRM Registry File Name

The names of the registry files, such as wireless.reg or wirelessRealtime.reg.

Required for pipeline targets only.

To discover both batch rating and real-time rating pipeline targets, enter both registry files separated by a comma. For example:

wireless.reg,wirelessRealtime.reg

Table 3-4 describes the guided discovery fields for Offline Mediation Controller targets.

Table 3-4 Offline Mediation Controller Guided Discovery Fields

Field Description

Install Location

The path to the directory where Offline Mediation Controller is installed.

Table 3-5 describes the guided discovery fields for OSS targets (ASAP, OSM, and UIM).

Table 3-5 OSS Guided Discovery Fields

Field Description

Select Application

The OSS application to discover.

EM repository Owner

The user name of the Enterprise Manager repository owner.

EM repository Owner Password

The password of the Enterprise Manager repository owner.

WebLogicHostname

The host name of the domain on which the targets are deployed.

WebLogicPort

The port number of the host on which the targets are deployed.

WebLogicAdminUser

The administrator user name with which to connect to the WebLogic Server host.

WebLogicAdminPassword

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.

ASAPEnvironmentID

The unique identifier for your ASAP environment.

Required for ASAP targets only.

ASAP_HOME

The path to the directory where ASAP is installed.

Required for ASAP targets only.

UIM_HOME

The path to the directory where UIM is installed.

Required for UIM targets only.

Table 3-6 describes the guided discovery fields for PDC targets.

Table 3-6 PDC Guided 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.

WebLogicHostname

The host name of the domain on which the targets are deployed.

WebLogicPort

The port number of the host on which the targets are deployed.

WebLogicAdminUser

The administrator user name with which to connect to the WebLogic Server host.

WebLogicAdminPassword

The administrator password with which to connect to the WebLogic Server host.

Transformation Home

(Optional)

The path to the directory where the PDC transformation configuration is stored. For example:

BRM_Integration_Pack_Home/apps/transformation

where BRM_Integration_Pack_Home is the directory where the BRM-PDC integration pack is installed.

Provide the path to monitor the log files for the PDC transformation target in addition to the PDC target.

BRM Host

(Optional)

The discovered host of the BRM target with which the PDC target is integrated.

Provide the path to monitor the log files for the PDC transformation target in addition to the PDC target.

PDC Home

The path to the directory where PDC is installed.

JMX Protocol

The connection protocol to use when connecting to the WebLogic server.

Table 3-7 describes the fields used when associating a database with a BRM target running on a non-Oracle RAC database.

Table 3-7 BRM Database Association Fields

Field Description

DB HostName

The host on which the BRM database resides.

DB Port No

The port number for the host on which the BRM database resides.

DB SID

The system ID for the BRM database.

DB UserName

The BRM database user.

SYS DB Password

The password for the BRM database user.

Table 3-8 describes the fields used when associating a database with an ASAP, NCC, OSM, PDC, or UIM target running on a non-Oracle RAC database.

Table 3-8 Application Database Association Fields

Field Description

target SYSDBA User

Where target is ASAP, NCC, OSM, PDC, or UIM, depending on the target type you are discovering.

The database user for the application.

target SYSDBA Password

Where target is ASAP, NCC, OSM, PDC, or UIM, depending on the target type you are discovering.

The password for the database user for the application.

Discovering Targets Automatically

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:

  • BRM

  • ECE

  • NCC

  • Offline Mediation Controller

  • Oracle Communications Integration (Oracle AIA)

  • OSS:

    • ASAP

    • OSM

    • UIM

  • PDC (includes PDC transformation targets)

Automatic discovery involves the following tasks:

Configuring Automatic Discovery

To configure managed hosts to run automatic discovery:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. From the Setup menu, select Add Target and then Configure Auto Discovery.

    The Setup Discovery page appears.

  3. Click the Targets on Hosts tab.

  4. Highlight the host on which you want to discover targets. For ECE, this is a Coherence target host.

  5. Click Discovery Modules.

  6. From the Enabled column, select the discovery module for the type of target you want to discover.

    You can select more than one module at a time.

    For PDC transformation targets, if the transformation target and main PDC target are on the same host, select only the PDC module. If the targets are on different hosts, also select the PDC Transformation module.

  7. For NCC targets, skip this step.

    For all other target types, click Edit Parameters and in the Edit Parameters dialog box, enter information in the fields for the application you want to discover. See the following for details about these fields:

    These fields are not immediately validated. When attempting to add the target, the discovery module uses the values to contact the Management Agent on the specified host and reports any validation errors at that time.

  8. Click OK in the Edit Parameters dialog box.

  9. Click OK.

    The list of managed hosts appears.

Automatic Discovery Fields

This section describes the information required for automatic discovery.

Table 3-9 describes the automatic discovery fields for BRM targets.

Table 3-9 BRM Automatic Discovery Fields

Field Description

Enter Portalbase Pinhome

The path to the directory where BRM is installed.

Enter ThirdPartyLoc

The path to the directory where the BRM third-party software package is installed.

Enter TNS_ADMIN

The path to the directory on your BRM host where the tnsnames.ora file that points to your database is located.

Enter Oracle Client Directory

The Oracle home directory containing access libraries and binaries, corresponding to the 64-bit client.

Enter Pipeline InstallLoc

The directory where BRM Pipeline Manager is installed.

Enter Pipeline RegisteryFile

The path to the BRM Pipeline Manager registry file.

Table 3-10 describes the automatic discovery fields for ECE targets.

Table 3-10 ECE Automatic Discovery Fields

Field Description

Enter ECE Home

The path to the directory where ECE is installed.

Enter Java Home

The path to the directory where Java is installed.

Enter JMX Port

The JMX port number of the ECE management node.

Enter Hostname

The host name of the ECE management node.

Enter Service Name

The service name of the ECE management node.

ECE JMX UserName for Coherence MBean Server

The user name for the Coherence management JMX server.

ECE JMX Password for Coherence MBean Server

The password for the Coherence management JMX server user.

Table 3-11 describes the guided discovery fields for Offline Mediation Controller targets.

Table 3-11 Offline Mediation Controller Automatic Discovery Fields

Field Description

Enter Install Location

The path to the directory where Offline Mediation Controller is installed.

Table 3-12 describes the automatic discovery fields for Oracle Communications Integration targets (Oracle AIA).

Table 3-12 Oracle Communications Integration Automatic Discovery Fields

Field Description

SOA Web-Logic Admin-Server Host-Name

The host name of the WebLogic Server administration server.

SOA Web-Logic Admin-Server Port

The port number of the WebLogic Server administration server.

SOA Web-Logic Protocol (t3/t3s)

The connection protocol to use when connecting to the WebLogic server.

SOA Web-Logic Admin-Server User-Name

The user name with which to connect to the WebLogic Server host.

SOA Web-Logic Admin-Server Password

The password with which to connect to the WebLogic Server host.

Table 3-13 describes the automatic discovery fields for OSS targets (ASAP, OSM, and UIM).

Table 3-13 OSS Automatic Discovery Fields

Field Description

Enter Weblogic HostName

The host on which the target is deployed.

Enter WeblogicPort

The port number of the host on which the target is deployed.

Enter Weblogic User Name

The user name with which to connect to the WebLogic Server host.

Enter Weblogic Password

The password with which to connect to the WebLogic Server host.

Enter t3/t3s Protocol

The connection protocol to use when connecting to the WebLogic server.

Enter Deployment Names

A colon-separated list of the types of OSS products to discover. The default value is oms:asap:oracle.communications.inventory.

Enter UIM HOME Directory

The path to the directory where UIM is installed.

Required for UIM targets only.

Enter ASAP HOME Directory

The path to the directory where ASAP is installed.

Required for ASAP targets only.

Enter Comms Plugin Version

The version of Application Management Pack for Oracle Communications that you are using.

Table 3-14 describes the automatic discovery fields for PDC targets.

Table 3-14 PDC Automatic Discovery Fields

Field Description

Enter Weblogic HostName

The host on which the target is deployed.

Enter Weblogic Port

The port number of the host on which the target is deployed.

Enter Weblogic User Name

The user name with which to connect to the WebLogic Server host.

Enter Weblogic Password

The password with which to connect to the WebLogic Server host.

Enter t3/t3s Protocol

The connection protocol to use when connecting to the WebLogic server.

Enter BRMHostName

(Optional)

The discovered host of the BRM target with which the PDC target is integrated.

If the main PDC target and the transformation target are on the same host, you discover both at the same time by specifying the transformation home and BRM host in the main PDC module.If the main PDC target and the transformation target are on different hosts, you discover the targets separately by using the PDC transformation module and the main PDC module. You can associate the two by specifying the transformation home and BRM host of the transformation target in the main PDC discovery module.

Enter Transformation Path

(Optional)

The path to the directory where the PDC transformation configuration is stored. For example:

BRM_Integration_Pack_Home/apps/transformation

where BRM_Integration_Pack_Home is the directory where the BRM-PDC integration pack is installed.

If the main PDC target and the transformation target are on the same host, you discover both at the same time by specifying the transformation home and BRM host in the main PDC module.If the main PDC target and the transformation target are on different hosts, you discover the targets separately by using the PDC transformation module and the main PDC module. You can associate the two by specifying the transformation home and BRM host of the transformation target in the main PDC discovery module.

Enter PDC Home

The path to the directory where PDC is installed.

Enter Comms Plugin Version

The version of Application Management Pack for Oracle Communications that you are using.

Running Automatic Discovery On Demand

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:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. From the Setup menu, select Add Target and then Configure Auto Discovery.

  3. Click the Targets on Hosts tab.

  4. Select a row from the list of managed host targets.

  5. Click Discover Now.

    A confirmation dialog box appears.

  6. 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.

Viewing Automatic Discovery Errors

To view failed automatic discoveries and get more details about automatic discovery errors:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. From the Setup menu, select Add Target and then Configure Auto Discovery.

  3. Click the Targets on Hosts tab.

  4. From the Most Recent Ended On column, click the date and time link for the failed discovery.

    The diagnostic details for that host appear.

  5. 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.

Promoting Discovered Targets

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:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. From the Setup menu, select Add Target and then Auto Discovery Results.

    The Auto Discovery Results page appears

  3. Click the Targets on Hosts tab.

  4. Select the row of the automatically discovered targets that you want to promote.

    Note the following:

    • 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.

    • If the servers in the SOA cluster on which your Oracle AIA instance is deployed are configured with IP, host, and domain, an Oracle Communications Integration target is discovered for several combinations of IP and host.

      For example, if your administration server is configured on samplehost.example.com:7001 and its IP equivalent, 192.0.2.1:7001, the following targets are discovered:

      • Communications_Integration_192.0.2.1_7001

      • Communications_Integration_samplehost_7001

      • Communications_Integration_samplehost.example.com_7001

      You only need to promote one target for each cluster. For complete monitoring functionality, Oracle recommends promoting a target for the server on which Oracle AIA is installed.

  5. Click Promote.

    The Promote target_type Target(s) page appears.

  6. For BRM and NCC targets, skip this step.

    For all other target types, enter the required information for the target. See the following for details about the required information and fields:

  7. For all target types other than BRM, skip this step.

    For BRM targets, edit the monitoring credentials:

    1. Click Specify Common Monitoring Credentials.

    2. Select an existing credential name or create a new one.

    3. In the Credential Details table, enter the user name and password for the user with permissions for the BRM environment.

    4. Click Save.

      The credentials for all BRM targets in the list of targets to be promoted are saved.

  8. (Optional) To register the database for monitoring and topology view:

    If you are promoting an ASAP, ECE, NCC, PDC, or UIM 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 ASAP, ECE, NCC, PDC, and UIM targets, and BRM and OSM targets without an Oracle RAC database:

      1. Select the Register DB option.

      2. Provide the connection details and user credentials for the database in the Database Registration Details fields. See Table 3-19, "BRM Database Association Fields" and Table 3-20, "Application Database Association Fields" for information about these fields.

    • For Oracle Communications Integration targets:

      1. Under Communication Integration (FP/Cross Reference) Database Detail or SOA (Infra) Database Detail, select the Register DB for Monitoring option.

        You can register the Oracle AIA database, the SOA database, or both.

      2. Provide values for the System User-Name and System Password fields. See Table 3-21, "Oracle Communications Database Association Fields" for information about these fields.

    Note:

    For BRM or OSM with an Oracle RAC database, do not select the Register DB option. Instead, associate the database manually as a post-discovery task.

  9. For Oracle Communications Integration targets, skip this step.

    (Optional) For all other target types, to add the target to a logical group:

    1. Select the Enable Logical Grouping option.

    2. Do one of the following:

      • Create a new logical group for the target by entering a unique logical group name.

      • Add the target to an existing logical group by clicking Browse and selecting the logical group.

  10. (Optional) To include the target in a dynamic group, enter values in the TargetProperties fields. For example:

    • To include the target in a dynamic group of production environments, select Production from the Lifecycle Status menu.

    • To include the target in a dynamic group of OSS targets, enter OSS in the Line of Business field.

  11. Click Promote.

    The target is promoted to managed status. You can view the target on the All Targets page.

  12. Perform the appropriate post-discovery tasks for the target, as described in "Post-Discovery Tasks".

Target Promotion Fields

This section describes the information required for promoting automatically discovered targets.

Table 3-15 describes the promotion fields for ECE targets.

Table 3-15 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-16 describes the required fields for Oracle Communications Integration targets (Oracle AIA).

Table 3-16 Oracle Communications 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 where SOA 11g is installed. Not required for SOA 12c.

Communications Integration Home (Pre-built/AIA Home)

The path to the directory where the Oracle AIA pre-built integrations are installed.

Required only for integration targets that are installed on the same host as the Management Agent.

Communications Integration OPatch File Location

The path to the directory where the OPatch utility is located.

Required only for integration targets running on SOA 12c that are installed on the same host as the Management Agent. Not required for targets running on SOA 11g.

Host-Name

The host name of the database.

You can enter values for this field under both Communications Integration and SOA database details.

Port

The port number of the database.

You can enter values for this field under both Communications Integration and SOA database details.

SID

The unique identifier of the database.

You can enter values for this field under both Communications Integration and SOA database details.

User-Name

The user name of the database user.

You can enter values for this field under both Communications Integration and SOA database details.

Password

The password of the database user.

You can enter values for this field under both Communications Integration and SOA database details.

Table 3-17 describes the promotion fields for OSS targets (ASAP, OSM, and UIM).

Table 3-17 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.

WebLogicAdminPassword

The password of the WebLogic Server administrator account.

ASAPEnvironmentID

For ASAP targets only.

The unique identifier for your ASAP environment.

Table 3-17 describes the promotion fields for PDC targets.

Table 3-18 PDC 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.

WebLogicAdminPassword

The password of the WebLogic Server administrator account.

Table 3-19 describes the fields used when associating a database with a BRM target running on a non-Oracle RAC database.

Table 3-19 BRM Database Association Fields

Fields Description

DB HostName

The host on which the BRM database resides.

DB Port No

The port number for the host on which the BRM database resides.

DB SID

The system ID for the BRM database.

DB UserName

The BRM database user.

SYS DB Password

The password for the BRM database user.

Table 3-20 describes the fields used when associating a database with an ASAP, NCC, OSM, PDC, or UIM target running on a non-Oracle RAC database.

Table 3-20 Application Database Association Fields

Fields Description

target SYSDBA User

Where target is ASAP, NCC, OSM, PDC, or UIM, depending on the target type you are discovering.

The database user for the application.

target SYSDBA Password

Where target is ASAP, NCC, OSM, PDC, or UIM, depending on the target type you are discovering.

The password for the database user for the application.

Table 3-21 describes the fields used when associating a database with an Oracle Communications Integration target.

Table 3-21 Oracle Communications Database Association Fields

Property Description

System User-Name

The user name of the database system user.

You can enter values for this field under both Communications Integration and SOA database details.

System Password

The password of the database system user.

You can enter values for this field under both Communications Integration and SOA database details.

Post-Discovery Tasks

For some Oracle Communications applications, you must perform additional tasks before you can monitor them. See the following sections for the tasks to perform:

Adding BRM Components to the pin_ctl.conf File

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 the pin_ctl.conf file:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. Navigate to the BRM target home page, as described in "Viewing Home Pages".

  3. In the Components Installed region, review the list of installed components.

  4. On the host where BRM is installed, open the BRM_home/bin/pin_ctl.conf file.

  5. Search for the following line:

    1 dm_oracle

  6. Compare the list of components to the list in the Components Installed region of the BRM target home page in Enterprise Manager Cloud Control.

  7. 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.

  8. Save and close the file.

Configuring SNMP for BRM Pipeline Targets

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:

  1. Install the SNMP software as described in Oracle Communications Billing and Revenue Management Installation Guide.

  2. 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

  3. Open the following file:

    Pipeline_home/conf/wireles.reg

    where Pipeline_home is the directory where the BRM pipeline target is installed

  4. 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

  5. Save and close the file.

  6. Log in to the Enterprise Manager Cloud Control administration console.

  7. From the Targets menu, select All Targets.

  8. In the Target Type tree, select Oracle BRM Pipeline or Oracle BRM RTP.

  9. From the list of targets, right-click the name of the BRM Pipeline target for which you are configuring SNMP.

  10. Under the target's name, from the target type menu, select Target Setup, and then Monitoring Credentials.

  11. In the SNMP AgentX Port field, enter the port that you used for AgentX_port when you started the master agent.

  12. In the SNMP Master Agent Port field, enter the port that you used for Master_agent_port when you started the master agent.

  13. Click OK.

    The home page for the BRM Pipeline target appears.

  14. In the Summary region, click ReStart.

Associating Application Targets with Database Targets

After discovering and promoting BRM, NCC, OSM system, and PDC targets and their related Oracle Database targets, you can associate the application target with the database target so that the database appears on the application target's topology page.

To associate an application target with a database target:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. Navigate to the target home page, as described in "Viewing Home Pages".

  3. Under the target name, from the target type menu, select Target Setup and then Monitoring Configuration.

  4. In the DB Host field (BRM Database Host for BRM targets), enter the host for the database that you are associating.

  5. In the DB SID field (BRM Database SID for BRM targets), enter the system ID for the database that you are associating.

  6. Click OK.

    A message appears confirming that the settings were saved.

  7. Click OK.

  8. Under the target's name, from the target type menu, select Monitoring and then Associate Database.

    The Associate Database region appears.

  9. Click Associate Database.

    A message appears confirming that the database was associated.

  10. Click OK.

  11. Confirm that the database was successfully associated by viewing the target's topology page. See "Viewing Topology" for information about topology pages.

Associating Oracle RAC Database Targets with BRM and OSM Targets

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:

  1. In any order, do the following:

    1. 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.

    2. 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.

  2. Do one of the following:

    • On the BRM target home page, click AssociateRACDB.

    • On the OSM target home page, click Associate RAC Database.

  3. 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.

Adding the UIM Database Password to the Communications Suite Target

To add the UIM database password to the communications suite target:

  1. Log in to the Enterprise Manager Cloud Control administration console.

  2. Navigate to the UIM target home page, as described in "Viewing Home Pages".

  3. Under the target's name, from the target type menu, select Target Setup, and then Monitoring Configuration.

  4. In the UIM DB User Password field, enter the database password for UIM.

  5. Click OK.

Configuring Compliance for OSM Clusters

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:

  1. Go to the directory of the domain where OSM is deployed, for example:

    /u01/Oracle/Middleware/user_projects/domains/OSM_Domain

  2. Open the startup script for the single OSM managed server that you want to designate as the MBean server.

  3. Add and set the following properties:

    -Dtangosol.coherence.management.remote=true
-Dtangosol.coherence.management=all

  4. Save and close the file.

  5. Open the startup script for any other OSM managed server.

  6. Add and set the following properties:

    -Dtangosol.coherence.management.remote=true
-Dtangosol.coherence.management=none

  7. Save and close the file.

  8. Repeat steps 5 to 7 until you have updated the startup scripts for all managed servers that you have discovered.

Adding Existing Oracle Communications Applications Using Monitoring Properties

You can manually add existing installations of supported versions of Oracle Communications applications or processes 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

  • NCC SLC Target

  • NCC SMP Target

  • NCC VWS 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 Communications Integration

  • Oracle ECE Node

  • Oracle OMC NodeManager

  • Order and Service Management Node

  • PDC

  • Unified Inventory Management

To manually add existing Oracle Communications applications or processes:

  1. 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 instructions.

  2. 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 instructions.

  3. Log in to the Enterprise Manager Cloud Control administration console.

  4. From the Setup menu, select Add Target, and then Add Targets Manually.

  5. Do one of the following, depending on the version of Enterprise Manager Cloud Control you are using:

    • For 12c:

      1. Select Add Targets Declaratively by Specifying Target Monitoring Properties.

      2. From Target Types, select the Oracle Communications application or process.

      3. Click the magnifying glass and search for the monitoring agent running on the host where the Oracle Communications application or process is running.

        The Search and Select: Targets dialog box appears.

      4. Select the Management Agent running on the Oracle Communications application or process host.

      5. Click Select.

      6. Click Add Manually.

    • For 13c:

      1. Click Add Target Declaratively.

      2. Click the magnifying glass and search for the host where the Oracle Communications application or process is running.

        The Select host dialog box appears.

      3. Select a host from the list and click Select.

      4. Select a target type from the list and click Add.

  6. 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.

  7. Click OK to add the new target.

  8. Confirm that the new target is now visible in the Enterprise Manager Cloud Control administration console.

Preparing New Hosts for Application Provisioning

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:

Ensuring Proper Application System Requirements

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.

Installing Required Software

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.

Database Password Restrictions

When provisioning targets that require a database, you provide the credentials for the database users. For example, with OSM, you provide credentials for the database system user, the application schema database user, and the reporting schema database user.

If the password provided for any database user starts with $$, Application Management Pack for Oracle Communications cannot connect to the database. You must ensure that the database user passwords for your applications do not start with $$.

Adding a Host to Enterprise Manager Cloud Control

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.

Downloading Oracle Communications Application Installers

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:

https://edelivery.oracle.com

See "Supported Applications, Suites, and Solutions" 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.