Application Management Pack for BRM · Application Management Pack for BRM 1 Application Management...

Application Management Pack for BRM

Oracle® CommunicationsBilling and Revenue Management 7.3.1

September 2008

Oracle Communications Billing and Revenue Management 7.3.1

Revision Date: September 2008

Copyright © 1999-2008, Oracle. All rights reserved. PORTAL, the PORTAL LOGO, BILLINGAGILITY, CONTENT CONNECTOR, INTEGRATE, INTERCONNECT, and TELCOONE are trademarks or registered trademarks in the United States and in other countries, all owned by Oracle Corporation. Marks or names owned by other companies remain the property of their respective owners.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). THIS SOFTWARE IS PROVIDED “AS IS,” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.Copyright © 1999-2001 The Apache Software Foundation. All rights reserved.

This material is the confidential property of Oracle Corporation and its subsidiaries or licensors and may be used, reproduced, stored, or transmitted only in accordance with a valid Oracle license or sublicense agreement.

Oracle Corporation500 Oracle ParkwayRedwood Shores, CA 94065 USA

Contents

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About the Application Management Pack for BRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Using the Application Management Pack for BRM to administer your BRM system . . . . . 2

BRM target types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Using Oracle Enterprise Manager Grid Control for the first time . . . . . . . . . . . . . . . 5

Accessing the Oracle Enterprise Manager Grid Control console . . . . . . . . 5BRM plug-in pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Oracle Enterprise Manager Grid Control console (Home tab) . . . . . . . . . . 7Targets tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Host’s home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Oracle BRM Suite page (Home tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Oracle BRM Suite page (Members tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Generic Service: Oracle BRM Suite_Service . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Adding the BRM subtab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19About discovering BRM targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About system monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21About monitoring the BRM target configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21About alerts and notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21How BRM log files are monitored for errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

BRM error codes monitored by Oracle Enterprise Manager . . . . . . . . . . . . 22About BRM reports and graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25About monitoring system performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing the Application Management Pack for BRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Operating system and database support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Hardware requirement for BRM OMS Plug-in . . . . . . . . . . . . . . . . . . . . . . . 26Hardware requirement for BRM Oracle Management Agent Plug-in . . . . 26

Before installing the Application Management Pack for BRM. . . . . . . . . . . . . . . . . . 27Configuring the Software Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Installing the RPM software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Downloading the Application Management Pack for BRM installation software . 30Using Oracle Universal Installer to install the Application Management Pack for BRM31

Installing the BRM OMS components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installing the BRM Oracle Management Agent components. . . . . . . . . . . . 33Creating BRM source components in the Software Library . . . . . . . . . . . . . 35Creating customer configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Setting up a customer configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Uploading customer configuration files to Oracle Enterprise Manager . . 41Uninstalling the Application Management Pack for BRM . . . . . . . . . . . . . . 42Before uninstalling the Application Management Pack for BRM . . . . . . . . 42Uninstalling the Application Management Pack for BRM from OMS . . . . 43Uninstalling the Application Management Pack for BRM from the Agent 43

Deploying BRM prepaid components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Contents iii

Oracle

Before deploying BRM prepaid components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Setting up preferred credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Deploying BRM prepaid components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Component configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Deploying BRM Optional Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Before deploying BRM Optional Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Deploying BRM Optional Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Discovering BRM targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Monitoring and controlling BRM targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Starting, stopping, or restarting BRM targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Starting, stopping, or restarting individual BRM targets . . . . . . . . . . . . . . . 58Starting, stopping, or restarting all or selected BRM targets . . . . . . . . . . . . 59

Viewing log file alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Viewing the metric current value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Viewing the configuration details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Monitoring the performance history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Configuring alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configuring the collection schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Adding corrective actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Displaying BRM system topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Patching BRM prepaid components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Before patching BRM prepaid components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Updating BRM products list in Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 66Creating a patch source component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Patching BRM prepaid components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Rollback of BRM software patch installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Rollback of a BRM software patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Adding your custom code to a high-availability system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Adding custom code to a BRM RPM package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

iv Book Title

Application Management Pack for BRM 1

About this documentThis document provides an overview of the Application Management Pack for Oracle Communications Billing and Revenue Management (BRM) and how to use it to install and administer your BRM system.

Before you read this document, you should be familiar with Oracle Enterprise Manager Grid Control and BRM concepts and architecture. See the following documents:

• Enterprise Manager Concepts at http://www.oracle.com/technology/documentation/oem.html.

• BRM system architecture in the BRM documentation.

• BRM system administration in the BRM documentation.

Note This document provides instructions for installing a BRM prepaid system. To set up a BRM postpaid system, see Installing BRM on UNIX in the BRM documentation.

About the Application Management Pack for BRMThe Application Management Pack for BRM is a plug-in for the Oracle Enterprise Manager Grid Control. The Application Management Pack for BRM runs on top of the Oracle Enterprise Manager framework and extends Enterprise Manager Grid Control to add support for BRM system administration.

Enterpise Manager Grid Control provides a wide range of functionalities that allow system administrators to efficiently deploy and administer their enterprise. Using Enterprise Manager Grid Control, system administrators can detect, solve, and prevent problems in the networks, systems, and applications in the enterprise. The Enterprise Manager Grid Control console provides system administrators the capability to manage and monitor their distributed systems from a central location using a Web browser.

Note The Application Management Pack for BRM supports deployment of prepaid high-availability systems and management and monitoring of prepaid and postpaid systems.

You can use the Application Management Pack for BRM to:

• Provision (install) BRM prepaid high-availability systems.

• Install BRM patches (prepaid components only).

• Roll back BRM patches (prepaid components only).

• Manage and monitor your BRM system (prepaid and postpaid components).

BRM prepaid components include:

• Oracle Data Manager (Oracle DM)

• Connection Manager (CM)

• Real-time pipeline (RTP)


Oracle

• Transactional In-Memory Object Store database (TIMOS DM)

• Authorization, Authentication and Accounting Gateway Manager (AAA Gateway Manager)

For an overview of a BRM high-availability system, see Understanding a high-availability system in the BRM documentation.

Using the Application Management Pack for BRM to administer your BRM system

The Application Management Pack for BRM plug-in allows you to administer your BRM system by using Oracle Enterprise Manager Grid Control.

To understand how the Application Management Pack for BRM works, it is important to understand the Enterprise Manager Grid Control architecture. The Enterprise Manager Grid Control consists of the following components:

• Oracle Enterprise Manager Grid Control console is a Web-based interface that allows system administrators or operators to perform monitoring and administration tasks for their enterprise from a central location.

• Oracle Management Service (OMS) is a middle-tier Java 2, Enterprise Edition (J2EE) Web application that is deployed on an Oracle Application Server. OMS provides the interface between the Enterprise Manager Grid Control console and the rest of the system. It processes the monitoring information from the Oracle Management Agents and stores the information into the Oracle Management Repository by using Java Database Connectivity (JDBC).

• Oracle Management Agent is a process that is deployed on each managed host. The Management Agent monitors all the managed targets on the host and communicates that information to the OMS using HTTP or HTTPS. Managed hosts and managed targets are entities within your enterprise that you want to monitor and manage from the Enterprise Manager Grid Control console.

• Oracle Management Repository resides in an Oracle database and contains objects such as packages and procedures and all information pertaining to the managed targets within Enterprise Manager Grid Control. Information stored in the Management Repository is retrieved by the OMS and displayed in the Enterprise Manager Grid Control console.

For more information about the Oracle Enterprise Manager Grid Control components, see Enterprise Manager Components Overview in the Enterprise Manager online Help.

2 Application Management Pack for BRM

The following diagram provides a high-level overview of the Enterprise Manager Grid Control architecture.

Enterprise Manager Grid Control supports default target types such as host, database, and application server. The Application Management Pack for BRM extends Enterprise Manager Grid Control by adding support for the BRM target types. See BRM target types.

The Application Management Pack for BRM is installed on top of Enterprise Manager Grid Control and consists of BRM extensions to the OMS, Oracle Management Agent, and Oracle Management Repository. These extensions are a collection of target definition files that are needed to provision and monitor BRM targets from Enterprise Manager Grid Control. Each target definition file defines a target and includes the target type, the metrics that should be monitored for the target type, the method for obtaining the metric data, alert threshold values, and the collection schedule for each metric.

When BRM prepaid components are provisioned using Enterprise Manager Grid Control, discovery scripts are used to automatically find and register instances of the BRM prepaid targets in Enterprise Manager Grid Control. During the discovery process, the Oracle Management Agent collects the configurations for each provisioned target instance and sends the information to the OMS to be stored in the Oracle Mangement Repository.

Note Automatic discovery of target instances is initiated only when BRM components are provisioned using Enterprise Manager Grid Control. BRM components not provisioned using Enterprise Manager Grid Control, such as BRM postpaid components, are discovered using guided discovery. See About discovering BRM targets.

Once BRM components have been discovered, Oracle Enterprise Manager managing and monitoring functionalities are automatically extended to the BRM targets. Using Enterprise Manager functionalities, you can:

• Monitor current status and performance of BRM components. See About system monitoring.

• View alerts and manage alert thresholds. See About alerts and notifications.


Oracle

• View configuration of BRM components. See About monitoring the BRM target configuration.

• Gather diagnostics data to monitor and compare system performance over a period of time. See About monitoring system performance.

• Provision BRM prepaid high-availability system. See Deploying BRM prepaid components.

• Upgrade BRM software to a later version (prepaid only). See Patching BRM prepaid components.

• Roll back software upgrades (prepaid only). See Rollback of BRM software patch installation.

BRM target types

The following table lists the BRM target types that can be discovered and monitored through Oracle Enterprise Manager Grid Control:

Target type Description

Oracle BRM AAA Gateway Manager

The AAA Gateway Manager is a BRM component that interfaces between BRM and the network Service Control Point (SCP). AAA Gateway Manager is used for a prepaid setup.

Oracle BRM Connection Manager

Process used by BRM client applications to establish connections to the Oracle BRM database.

Connection Managers also contain the Facilities Modules (FMs) that carry out BRM functions. Oracle BRM Connection Manager includes Connection Manager process types, such as cm, cm_proxy, and cmmp.

Note cmmp cannot be provisioned or managed as part of a prepaid setup from Oracle Enterprise Manager Grid Control.

Oracle BRM Java Process

Includes the Java processes that run in a postpaid environment. For example, eai_js, batch_controller, and formatter.

Oracle BRM Pipeline Used for rating and discounting events in batch and real time. Oracle BRM Pipeline includes the postpaid batch pipeline, zoning, and discounting pipeline.

Oracle BRM RTP The Real-time pipeline discovered as part of prepaid installation.


Using Oracle Enterprise Manager Grid Control for the first time

Oracle Enterprise Manager Grid Control provides a Web-based console for managing your entire enterprise. The Oracle Enterprise Manager Grid Control console provides support for creating and managing Oracle Enterprise Manager Grid Control administrator accounts. These administrator accounts are granted privileges and roles to log in to the Oracle Enterprise Manager Grid Control console and to manage specific target types and to perform specific management tasks.

For more information about creating and managing administrator accounts, see Creating, Editing, and Viewing Administrators in Oracle Enterprise Manager online Help.

Accessing the Oracle Enterprise Manager Grid Control console

The Oracle Enterprise Manager Grid Control console is the primary tool for managing your targets.

Use the following URL to log in to the Oracle Enterprise Manager Grid Control console:

http://OMS_hostname.domain:port/em

or

https://OMS_hostname.domain:port/em

where

OMS_hostname is the host on which OMS is installed.

domain is the network domain on which you install your OMS.

port is the console port.

Oracle BRM TIMOS Data Manager

Transactional In-Memory Object Store (TIMOS) DM caches, in the reference object cache (ROC), persistent data stored in the database for fast read-only access. It also stores, in memory, transient data that reflects the status of ongoing sessions such as phone calls. TIMOS DM is a part of a prepaid setup.

Oracle BRM Data Manager

Process that translates BRM operations into a database language. BRM uses Data Managers (DMs) to communicate with the Oracle or SQL Server database, credit card processors, and the Taxware database.

Oracle BRM Data Manager includes all the different data managers other than the TIMOS DM. The following are the supported Data Managers:

• DM Oracle (dm_oracle)

• DM Email (dm_email)

• DM EAI (dm_eai)

• DM Paymentech (dm_fusa)

• DM Account Synchronization Oracle AQ (dm_ifw_sync)

• DM Invoice (dm_invoice)

Target type Description


Oracle

BRM plug-in pages

This section describes the following:

• Oracle Enterprise Manager Grid Control console (Home tab)

• Targets tab

– The All Targets subtab

– System: Oracle BRM Suite_System (Home tab)

– System: Oracle BRM Suite_System (Administration tab)

– System: Oracle BRM Suite_System (Components tab)

• BRM Target’s home page

• Host’s home page

• Oracle BRM Suite page (Home tab)

• Oracle BRM Suite page (Members tab)

• Generic Service: Oracle BRM Suite_Service


Oracle Enterprise Manager Grid Control console (Home tab)

The Home tab on Oracle Enterprise Manager Grid Control console provides information that helps you in assessing the health of all the targets that are being monitored. It provides high-level data, as well as the ability to drill down so you can investigate and repair availability and performance problems.

The Oracle Enterprise Manager Grid Control console is the first page that appears after you log on to Oracle Enterprise Manager.

For more information, see Oracle Enterprise Manager online Help.


Oracle

Targets tab

The Targets tab displays subtabs that further define targets by type, such as hosts, databases, application servers, and so on. BRM subtab appears as one of these subtabs if it has been added to the list of subtabs. For more information about adding the BRM subtab, see Adding the BRM subtab. Subtabs can be reordered. For information about reordering the subtabs, see Targets Subtabs page in Oracle Enterprise Manager online Help.

All Targets subtab

The All Targets subtab displays a list of all the targets available on your managed hosts, regardless of the target type.

The All Targets page lets you do the following:

• Check the availability of each target by scanning the Status column. You can also click the icons in Status column to view the overall availability information of the target in detail.

• View detailed information about a particular target by clicking the target name to drill down to the target’s home page.

• Add new targets or reconfigure existing targets.

Note You can create a group of various target types. Groups make it easy to monitor a set of groups and targets. For example, if you have 10 different CMs and 10 different DMs, you can group all the CMs together. For more information about creating and managing groups, see Creating, Editing, and Viewing Groups in Oracle Enterprise Manager online Help.

• Initiate guided discovery for BRM postpaid targets. For more information about how to discover postpaid targets, see Discovering BRM targets.

System: Oracle BRM Suite_System (Home tab)

A system is a generic target that helps in monitoring all the BRM components as part of the system and provides an additional feature of drawing a topology of the system.

The Home tab on the Oracle BRM Suite_System page displays key information about targets of the BRM system, eliminating the need to navigate to individual BRM targets to check on availability and performance. You can view the entire system on a single screen and drill down to obtain detailed information. The Oracle BRM Suite_System page lets you define and view the system topology.

Note If you have not configured the BRM tab, you can click BRM on the All Targets page.


The Oracle BRM Suite_System page lets you do the following:

• View a summary status of the targets within the system.

• View a rollup of outstanding alerts and policy violations.

• View configuration changes during the past seven days.

• Access drilldowns for more detailed information.


Oracle

The following table describes the various components displayed on the Home tab of the Oracle BRM Suite_System page:

Section Description

Status Shows how many BRM targets are in up, down, and unknown states.

Click a portion of the pie chart or its corresponding legend to go to the Member Status page. For example, if you click the Up area or the Up link, the Member Status page appears with a list of all the targets that are up and running.

Click Status History to go to the Status History page, which shows bar graphs that depict a historical view of the targets during a specified time period.

Alerts Shows the number of outstanding critical and warning alerts associated with this system.

Click a number in the Current column to go to the Status Report page that shows a summary table with alert messages.

Click Alert History to go to the Alert History page. The bar graphs on the page depict the chronological history of the alerts for the members in the system. Each bar graph is a summary of all the alerts for all the metrics associated with that target type.

Policy Violations Shows how many of the BRM targets do not comply with Oracle Enterprise Manager Grid Control policy rules. Non-compliant members are indicated with the number of critical, warning, and informational policy violations.

The Current column shows the number of violations; the Distinct Rules Violated column represents the number of unique policies that have been violated. Because a given policy can result in multiple violations, these numbers can be different.

Click the number for a particular severity level in either the Current column or the Distinct Rules Violated column to go to the Policy Violations page for the selected severity level, or click the Total number to display the policy violations for all severity levels. Click the Policy Trend Overview link to go to the Policy Trend Overview page. By comparing the compliance scores over a period of time, you can decide the course of action needed to improve the policy violation trend.

For more information about policy violations, see Managing Policy Violations in Oracle Enterprise Manager online Help.

Security Policy Violations

Shows how many of the BRM targets do not comply with Oracle Enterprise Manager Grid Control security policy rules. These rules let you enforce enterprise security by checking whether the BRM components have been installed or configured in an insecure manner. Non-compliant members are indicated with the number of critical, warning, and informational security policy violations.

Click the number for a particular severity level in either the Current column or the Distinct Rules Violated column to go to the Policy Violations page for the selected severity level, or click the Total number to display the security policy violations for all severity levels. Click the Security At a Glance link to go to the Security At a Glance page for an overview of the security health of the enterprise for this system, especially the critical security patches that have not been applied.

For more information about policy violations, see Managing Policy Violations in Oracle Enterprise Manager online Help.


For more information about the Related Links section on the Oracle BRM Suite_System page, see System: Home Page in Oracle Enterprise Manager online Help.

Services Shows the status of the services in the BRM system. This section displays information like performance alerts, usage alerts, and policy violations for the service.

Configuration Changes

Shows a summary of the changes for the last seven days grouped by high-level configuration categories. Subcategories under the high-level categories represent the types of targets.

Click a number in the Changes column to go to the Configuration History page for the selected category type. The Configuration History page shows history information about the target category, such as the date and time the change was discovered and the type of change.

For more information about configuration history, see Enterprise Configuration History Page in Oracle Enterprise Manager online Help.

Section Description


Oracle

System: Oracle BRM Suite_System (Administration tab)

The Administration tab on the Oracle BRM Suite_System page provides a central point for performing common administrative tasks for the system.

Use the Administration tab to:

• Create jobs and view the status of job executions.

• Create blackouts and view the status of current blackouts.

• Drill down to host operations and database operations, if applicable.

• View a summary of deployed components.

• Search for selected targets.

For more information about the Administration tab, see System: Administration Page in Oracle Enterprise Manager online Help.


System: Oracle BRM Suite_System (Components tab)

The Components tab on the Oracle BRM Suite_System page summarizes information about the BRM targets in the system. It includes information on their current availability status, roll up of open alerts and policy violations, and key performance metrics based on the type of targets in the system.

Use the Components tab to:

• Access individual target home pages by clicking the respective target name.

• Edit the existing system by clicking the Edit System link. For more information about editing the system, see Creating, Editing, and Viewing Systems in Oracle Enterprise Manager online Help.


Oracle

BRM target’s home page

BRM target’s home page displays information about the general health of a target. It shows the following information for the target: status, availability, instance type, home, log directory, target name, target type, port, version, HA role, and the host on which the target is installed. This page also lists the alerts that are triggered for this target.

The following table describes the fields or links that appear on the home page of various BRM targets. Not all elements will appear on every target’s home page.

You can also view a summary of the selected target’s configuration information and view detailed information for some categories of configuration data by clicking the View Configuration link in the Configuration section. For more information, see View Configuration Page in Oracle Enterprise Manager online Help.

Common elements Description

General Area that shows the general status of the target in terms of availability, BRM instance type, BRM home, BRM log path, host, and so on.

Status Indicates the BRM target’s availability; whether the BRM target is in up, down, or unknown state. The Up arrow shows that the target is up and running and the Down arrow shows that the target is down.

BRM targets can have any of the following statuses:

• Up

• Down

• Unknown. The Unknown status includes the following other statuses:

– Metric Collection Error

– Agent Down

– Agent unreachable

– Under Blackout

– Status Pending

Start Starts the BRM target.

Stop Stops the BRM target.

Restart Stops and then restarts the BRM target.

Blackout Creates a blackout for the BRM target or manages the existing one.

Availability Shows the percentage of time, excluding any blackouts, that the BRM target has been available since it was registered in Oracle Enterprise Manager Grid Control.

Alerts and Host Alerts

Lists any alerts that have been generated. Click a specific alert message to drill down to explicit details about the metric in the alert.


The following table describes the purpose of the links in the Related Links section:

For more information about these links, see Oracle Enterprise Manager online Help.

Host’s home page

You can access the home page of the host (the host on which BRM is installed) by clicking the host name from the Components tab on the Oracle BRM Suite_System page. The host’s home page provides a quick glance of the vital statistics for this host.

Use the host’s home page to:

• Drill down to view detailed statistics about this host.

• Study the policy violations for the host.

• Study all the alerts associated with this host.

• Analyze the job activity.

• Determine whether there are outstanding patch advisories.

• Determine the last security evaluation of the host.

• Investigate further the health of the host.

Links Purpose

All Metrics View a list of all the performance metrics available for the selected target.

Blackouts View the status of existing blackouts, create blackouts, edit existing blackouts, stop blackouts, and delete blackouts.

Note If you are not a Super Administrator, you will only be able to see those blackouts where you have at least a View privilege on at least one of the targets in the blackout. Super Administrators can see all blackouts created by regular Oracle Enterprise Manager administrators.

Access Administer access privileges for a target.

Metrics and Policy Settings

View and modify the metric thresholds and policies defined for the domain.

Monitoring Configurations

View target properties such as host name, BRM DMO name, port, BRM component type, BRM home path, and so on.

Target Properties Provide optional descriptive attributes that you can associate with any target. They can be used by Oracle Enterprise Manager Grid Control for search, filtering, or classification purposes.

Alert History View a bar graph that depicts the chronological history of an alert.

Reports View standard Oracle Enterprise Manager Grid Control reports available for the target.


Oracle


Oracle BRM Suite page (Home tab)

A suite is a custom target created to include all components belonging to BRM and is used to perform a process control and monitoring the BRM components as a group.

Use the Home tab on the Oracle BRM Suite page to monitor and control all processes from a single screen. It does not provide the option of viewing the topology.

Oracle BRM Suite page (Members tab)

The Members tab on the Oracle BRM Suite page displays a list of member targets of the BRM suite. The Members tab summarizes information about all the BRM targets in the suite. It includes information on their current availability status, rollup of open alerts and policy violations, and key performance metrics based on the type of targets in this suite. This page provides you an option to start, stop, or restart all or specificBRM processes.


Oracle

For more information about starting, stopping, and restarting BRM targets, see Starting, stopping, or restarting BRM targets.


Generic Service: Oracle BRM Suite_Service

A service is associated with a system stating the availability of the system. The status of service depends on the status of a few key components of the system; for example, CM target type. The Oracle BRM Suite_Service page provides an overview of the availability, performance, and usage of your service. Access this page by clicking Oracle BRM Suite_Service from the All Targets page.

Adding the BRM subtab

You can add BRM as a subtab within the Targets tab. The BRM subtab provides quick access to all the discovered BRM targets.

Note If you have not configured the BRM subtab, you can access the targets from the All Targets subtab.


Oracle

To add the BRM subtab:

1. At the top of the Oracle Enterprise Manager Grid Control console, click the Preferences link.

2. Click the Target Subtabs link.

3. In the Available Target Subtabs list, select BRM .

4. Move the BRM entry to the Selected Targets Subtab field by clicking Move.

5. (Optional) Move the BRM entry up or down in the list to specify where you want the BRM subtab to appear in relation to the other subtabs.

6. Click Apply.

About discovering BRM targets

You can use the discovery feature of Oracle Enterprise Manager Grid Control to find the deployed BRM targets. Targets are the components that you can configure or monitor using Oracle Enterprise Manager Grid Control. The discovery of the targets is required to manage and monitor the BRM targets in Oracle Enterprise Manager Grid Control. Oracle Enterprise Manager 10g supports two different kinds of discovery process: Automatic discovery and guided discovery.

Automatic discovery is the process of finding the BRM prepaid components during the initial installation of the BRM components using Oracle Enterprise Manager deployment procedure. When BRM prepaid components are provisioned (only prepaid components can be provisioned) using Oracle Enterprise Manager, discovery scripts are used to automatically find and register instances of the BRM prepaid targets.

Guided discovery is the process of finding the BRM postpaid components. The BRM postpaid components must be installed using the BRM installation process. After the postpaid components are installed, they can be discovered using guided discovery. Although, the provisioned components are automatically discovered, you must not attempt to discover the provisioned components using guided discovery. For more information about how to prepare a BRM postpaid setup and how to install the BRM postpaid components, see Installing BRM on Unix in the BRM online documentation.

Note This release supports only the Linux and HP-IA platforms. You cannot provision prepaid components for other platforms and discover them using the guided discovery.

BRM has its processes running on multiple hosts, and each installation can have its own PIN_HOME and IFW_HOME. PIN_HOME is the host path for BRM base components and IFW_HOME is the home path for BRM pipeline components.

Discovering multiple instances (sets of components) on a single host requires running the discovery process multiple times. For example, if you have multiple instances of BRM components (CM1 and CM2) installed on the same host, the discovery process must be run twice: first to discover CM1 and then to discover CM2.


In the case of multiple processes running on a single host (for example, multiple pipeline processes), each target instance is given a unique name as part of guided discovery. This enables each target to be identified distinctly.

For more information about how to discover the postpaid targets using guided discovery, see Discovering BRM targets.

About system monitoring

Monitoring the performance of the targets and quickly identifying and correcting problems before they can impact business operations is crucial to maintain high levels of component availability and performance. Comprehensive target monitoring lets you identify the problem areas in your targets that are affecting its performance and thus provide a clear picture about the overall health of the target. The BRM Integration feature helps you monitor the targets and supports the timely detection and notification of impending problems across your enterprise. For more information about how the system is monitored, See Monitoring and controlling BRM targets.

About monitoring the BRM target configuration

The Enterprise Configuration Management (ECM) framework is used to track the changes made to pin.conf and infranet.properties files and to pipeline registry details by the users. Oracle Enterprise Manager runs a script at predetermined intervals to collect the configuration data and upload it to the Oracle Management Repository. The View Configuration link on the home page of BRM targets lets you view the latest configuration.

The View Configuration page provides the target configuration details and the date on which the configuration data is collected. This data helps in performing root cause analysis. For more information, See Viewing the configuration details.

About alerts and notifications

Alerts are triggered when a potential problem occurs in the performance or availability of a target: that is, when the warning or critical threshold for a metric associated with the target is crossed.

You can configure alerts for all the defined metrics. Metrics are units of measurement used to determine the health of a target. Oracle Enterprise Manager sends alerts using the defined metrics and the associated thresholds notifying you of the problems with the target. By default, the alerts are configured and the metrics are defined for each of the targets. You can modify the existing configurations of the alerts. For more information about modifying the configurations for alerts, see Configuring alerts.

When an alert is triggered, you can access details about the alert from Oracle Enterprise Manager Grid Control console or from the respective target’s home page. Oracle Enterprise Manager provides various options to respond to alerts. Administrators can be automatically notified when an alert is triggered and corrective actions can be set up to automatically resolve an alert condition.


Oracle

How BRM log files are monitored for errors

The BRM system activities are recorded in a set of log files, one for each component or application. These files are frequently monitored to quickly detect and diagnose any system problems.

A preprocessing Perl script is scheduled to run at user-specified intervals, as specified in the default collections file. This Perl script searches the log files for a specific pattern. These patterns are specified in the brm_pattern.values file. The file is present in Agent_home/sysman/admin/scripts directory. If a match is found, a message is sent to the Oracle Enterprise Manager Grid Control console.

For more information about how to view the log file alerts, see Viewing log file alerts.

BRM error codes monitored by Oracle Enterprise Manager

The following table shows the BRM-related error messages monitored by Oracle Enterprise Manager.

Error Component Description

PIN_ERRCLASS_SYSTEM_DETERMINATE CM Error caused by a system failure during the operation. Retrying the operation is unlikely to succeed, and the system failure should be investigated immediately.

PIN_ERRCLASS_SYSTEM_INDETERMINATE

CM The error was caused by a system failure during the commit phase of an operation. The error might not be repeatable, and the system might not save specific information about the error.

PIN_ERR_NO_MEM CM Insufficient memory to complete the attempted operation.

PIN_ERR_DM_CONNECT_FAILED CM BRM could not connect to the Data Manager.

PIN_ERR_MASTER_DOWN CM The main BRM system is down.

PIN_ERR_STORAGE_FAILOVER CM A RAC failover message.

PIN_ERR_STREAM_IO CM Either the network is down or the BRM server (CM, DM) is down.

PIN_ERR_STREAM_EOF CM Either the network is down or the BRM server (CM, DM) is down.

PIN_ERR_TRANS_LOST DMO The transaction was lost. The DM failed during a transaction.

PIN_ERR_STORAGE_DISCONNECT DMO Connectivity to the database service has been lost.

PIN_ERR_STORAGE DMO Error occurred at the database layer.


The following table shows a list of Pipeline-related and TIMOS-related error codes that are monitored by Oracle Enterprise Manager.

PIN_ERRCLASS_SYSTEM_RETRYABLE CM The error was probably caused by a transient condition. Try the operation again. Common causes include a temporary shortage of system resources (perhaps caused by too many connections to the CM) or a failure of a network connection that you can route around.

PIN_ERR_NO_SOCKET CM BRM could not create a socket.

PIN_ERR_DM_ADDRESS_LOOKUP_FAILED CM The CM could not find the DM.

PIN_ERR_STREAM_EOF CM The application unexpectedly lost the connection to the BRM database.

PIN_ERR_CM_ADDRESS_LOOKUP_FAILED CM The application could not find the computer running the CM. The Bind (or DNS) service is pointing to the wrong TCP/IP address, or the network is having problems.

PIN_ER_CONNECTION_LOST CM The connection has been lost.

NULL MAPINFO pointer IN DMO Field mapping error – field not found.

Unable to establish database connection. Batch Controller

Connection failed.

PIN_ERRCLASS_APPLICATION CM The error was caused by a custom application passing invalid data to BRM or by system failure within the client application.

PIN_ERR_DEADLOCK DMO Two or more database sessions attempted to access the same database resource.

Error code Number Error message

ERR_THREAD_DIED_UNEXPECTED 30021 AccountBatch? – Error: Thread died unexpectedly.

ERR_BALANCE_DATABASE 31233 BalanceRealtime? – Error: Database operation failed.

ERR_ALL_CM_CONNECTIONS_DOWN 17006 ConnectionPool? – All the CM connections are down.

ERR_CM_CONNECTION_LOST 17008 ConnectionPool? – CM connection lost.

ERR_DATABASE_CONNECTION 11225 Error – Cannot connect database.

ERR_ALL_CM_CONNECTIONS_LOST 15902 FCT_Opcode – All CM connections lost.

ERR_CANNOT_OPEN_DATABASE 00213 Framework – Cannot open database.

ERR_DB_CONNECTION_NOT_VALID 00411 Framework – Could not connect to database.

ERR_INSUFFICIENT_MEMORY 00231 Framework – Insufficient memory available.

ERR_NOT_ENOUGH_CONNECTIONS 30014 AccountBatch? – Not enough connections available.

Error Component Description


Oracle

ERR_THREAD_CANCELLED 30081 AccountBatch? – Error: Thread Cancelled.

ERR_BALANCE_THREAD_INIT 31235 BalanceRealtime? – Error: Initial Thread for loading balance failed to create and start.

ERR_BALRT_EXECUTING_OPCODE 31303 BalanceRealtime? – Error executing the opcode.

ERR_CONNECT_FAILED 17001 ConnectionPool? – Connect call failed from CM.

ERR_LOGIN_FAILED 17002 ConnectionPool? – Login to CM failed.

ERR_QUEUE_NOT_INSTALLED 31007 Listener – Database queueing infrastructure has not been installed.

ERR_CANNOT_CREATE_CTL_QUEUE 11203 Error – Cannot create queue of controller files.

ERR_CANNOT_CREATE_RECORD 11204 Error – Cannot create record.

ERR_CANNOT_CREATE_CONTROLLER 11205 Error – Cannot create controller.

ERR_DOC_TABLE_FIND 11114 DeferredObjectController? – Error finding table.

ERR_DOC_OPEN_NEXT_QUEUE 11160 DeferredObjectController? – Failed to open next queue.

ERR_BEGIN_EDR 18006 FCT_Discount_Error – Cannot begin EDR transaction.

ERR_COMMIT_EDR 18007 FCT_Discount_Error – Cannot commit EDR transaction.

ERR_SEND_DATA 15914 FCT_Opcode – Error occurred while sending data to CM.

ERR_STREAM_NOT_FOUND 00110 Framework – Could not create any statistic information for this device.

ERR_DB_CONNECTION_MODULE 00218 Framework – Database connection module is invalid.

ERR_CANNOT_FORK 00354 Framework – Cannot create child process.

ERR_LINE_NOT_IDENTIFIED 00410 Framework – Wrong database version. Please check module and database version.

ERR_RECYCLING_DATA_MODULE_NOT_FOUND

10502 INP_Recycle_Error – Cannot find recycling data module.

ERR_INP_RECYCLE_NO_DB_CONNECTION

10510 INP_Recycle_Error – Unable to get DB Connection.

Error code Number Error message


About BRM reports and graphs

For each of the monitored targets, the metrics data is collected over time and is stored in the repository database. The collected data can be plotted as a graph, and comparisons can be made between the collected data for two or more targets. The metrics details can be collected for BRM processes such as memory consumption and disk space usage, which can be used to plot a graph over a specific time period. The collected data helps you in detecting potential memory leaks.

You can monitor all BRM processes including CM, DMO, DMT, and Pipeline processes. For more information about how the BRM processes are monitored using the reports and graphs, see Viewing the metric current value.

About monitoring system performance

Oracle Enterprise Manager provides an option to capture and save performance-related information during the period of performance monitoring. This performance data can be used to compare the system performance in future.

You can configure the period for which you want to save the history data in Oracle Enterprise Manager. By default, the period is 24 hours, last 7 days, and last 31 days. The Performance Details page displays graphs showing the memory and CPU usage of the target. For batch pipeline, you can see the graph for event detail records (EDR) processed per second; for TIMOS targets, you can see the quality of service (QOS) statistics graph. See Monitoring the performance history.

Installing the Application Management Pack for BRMThe Application Management Pack for BRM consists of the following plug-ins:

• BRM OMS Plug-in components are installed on the Oracle Management Service (OMS) and Oracle Management Repository in the Oracle home location where Oracle Enterprise Manager 10g Grid Control Release 3 is installed. BRM OMS Plug-in components include the BRM RPM packages and the Data Definition Language (DDL) to create related tables, indexes, stored procedures, sequences, and triggers on the Oracle Management Repository.

• BRM Oracle Management Agent Plug-in components are installed on each Oracle Management Agent in the Oracle home location where the Oracle Enterprise Manager 10g Release 3 Agent is installed. BRM Oracle Management Agent Plug-in components include the BRM target definition files, Perl scripts, and Java classes.

Installing your Application Management Pack for BRM includes these steps:

• Determine the hardware and software requirements. See Hardware and software requirements.

• Install and configure software prerequisites. See Before installing the Application Management Pack for BRM.

• Download the Application Management Pack for BRM software. See Downloading the Application Management Pack for BRM installation software.

• Install the Application Management Pack for BRM. See Using Oracle Universal Installer to install the Application Management Pack for BRM.


Oracle

Hardware and software requirements

This section describes the hardware and software requirements for the BRM plug-ins for Oracle Enterprise Manager Grid Control.

Operating system and database support

The Application Management Pack for BRM is supported on the following platforms:

• HP-UX IA64 11i Version 2.0 (B.11.23).

• Linux x86 OEL 4 Updates 4, 5.

The Application Management Pack for BRM is currently supported on Oracle 10g Release 2 database on HP-UX IA64 and Linux platforms.

For more information about HP-UX IA64 and Linux platform support, see BRM software compatability in the BRM documentation.

Hardware requirement for BRM OMS Plug-in

The following table lists the approximate amount of disk space required to install the BRM OMS Plug-in on OMS. The size estimates include the RPM packages and a backup copy of each. It also includes an estimate for the space required by third-party software and the extra space required by customization tools.

Note The exact amount may vary with:– The software components you manage using Enterprise Manager Grid

Control.

– The amount of customization you perform on these software components.

– The number of extra RPM package versions you have.

Hardware requirement for BRM Oracle Management Agent Plug-in

The following table lists the approximate amount of disk space required to install the BRM Oracle Management Agent Plug-in on the Agent system. The size estimates include the space required by third-party software.

Operating systemTotal disk space required in OMS

Oracle home

Linux 161000KB

HP-UX IA64 483000KB

Operating systemTotal disk space required in

Oracle home

Linux 376,192K

HP-UX IA64 874,429K


Disk space required by BRM prepaid components

You can use any system that meets the basic BRM hardware requirements to install the BRM prepaid components on the Agent system. For details, see Hardware and software requirements for UNIX in the BRM documentation.

Note Log files for all agents require additional space and can be put anywhere you have space for them. The amount of space required depends on the logging level you use and your policies on clearing logs.

Before installing the Application Management Pack for BRM

Before you install the Application Management Pack for BRM, you must install and configure the following:

• Oracle Enterprise Manager 10g Grid Control Release 3 (10.2.0.3).

Important The minimum version of the Oracle Enterprise Manager Grid Control software required to install BRM plug-ins is 10g Release 3.

Refer to Oracle Enterprise Manager Grid Control Installation and Basic Configuration Guide in the Oracle Enterprise Manager documentation.

• Oracle Management Agent 10g Release 3 on each of the target hosts.

Important The minimum version of Oracle Management Agent required to install BRM plug-ins is 10g Release 3.

Install Oracle Management Agent on each of the hosts where you plan to install BRM prepaid components. Refer to Oracle Enterprise Manager Grid Control Installation and Basic Configuration Guide in the Oracle Enterprise Manager documentation.

Important Before installing the Management Agent, ensure that TNS_ADMIN environment variable is set to the location of the tnsnames.ora file and ORACLE_SID environment variable is set to the database alias on the Agent machine. Otherwise, provisioning of BRM will fail. If these environment variables are set after installing the Management Agent, you must restart the Management Agent for the changes to take affect..

• Configure a directory in the Oracle Software Library to store BRM binary files.

The Oracle Software Library maintains versions of the software binaries and acts as a repository for the software components that may be provisioned to the hardware servers in your enterprise. During the installation of the Application Management Pack for BRM, the BRM binary files are copied to the Software Library. To store BRM binary files in Oracle Enterprise Manager, you must first configure a directory in the Oracle Software Library. See Configuring the Software Library.

• Install RPM software on the OMS and Agent machines.

The Application Management Pack for BRM uses BRM RPM packages for installation and patching of BRM prepaid components. You must install RPM software and ensure that the RPM install location is set in the PATH variable. See Installing the RPM software.

• Install third-party software on the OMS and Agent machines. See Installing the Third-Party software in the BRM documentation.


Oracle

• Install the SNMP software on the OMS and Agent machines. See Installing the SNMP software in the BRM documentation.

Important

– SNMP software must be installed under the directory where Third-Party software is installed. For example, if Third-Party software is installed in the directory /opt/portal/ThirdPartyApps, then SNMP install location should be /opt/portal/ThirdPartyApps/snmp_dir.

– The SNMP master agent should be running on the OMS and Agent machines. If multiple components are running in the same box, only one master agent is required. To start the SNMP master agent, see Configuring SNMP components in the BRM documentation.

• Install the BRM database. See Installing BRM on UNIX in the BRM documentation.

Important Using SQLPlus, ensure that the BRM database is accessible from the Agent machines. Verify that the tnsnames.ora file contains an entry for the BRM database and the file location is set in the TNS_ADMIN environment variable.

Note

– BRM schema should have been initialized to the database that corresponds to the version of RPM files.

– If this BRM database is used for TIMOS, the database should be initialized with the required TIMOS packages.

Configuring the Software Library

To configure a directory in the Software Library:

1. From Oracle Enterprise Manager Grid Control page, click the Deployments tab.

2. In the Deployments page, click the Provisioning subtab.

3. In the Provisioning page, click the Administration subtab.

4. In the Software Library Configuration section, click Add and enter a location. For example, /oracle/OracleHomes/swlib.

Installing the RPM software

Important:

• Install the RPM software on the OMS and on all Agent machines.

• The instructions in this section apply to installing this software for the first time. If you are reinstalling, some of the tasks and commands are different. For details, see Reinstalling RPM/YUM changes in the BRM documentation.

Note For Linux, the RPM software is installed as part of the operating system.


HP-UX IA64 installation

To install the RPM software on HP-UX IA64:

1. Use the df command to confirm that you have:

– At least 500 MB of free space in a download location.

– At least 600 MB of free space in your /opt directory.

2. Log in as user root.

3. Create a download directory under /opt.

# mkdir /opt/download_dir

For example:

# mkdir /opt/TWW_download

4. Use a Web browser to navigate to the Oracle open software site: oss.oracle.com/projects/pkgmgrutils.

5. Select the link for the HP-UX IA64 download file to download the file to /opt/download_dir.

6. Uncompress and untar it:

# cd /opt/download_dir# gunzip pkgmgrutils_hpia_73v1.tar.gz# tar -xvf pkgmgrutils_hpia_73v1.tar# tar -xvf pkgmgrutils-1.5.32.depot.tar

Tip If you get an error message indicating you cannot create the necessary directory, see Permission problems in the BRM documentation.

7. Complete the installation:

# /usr/sbin/swinstall -s 'pwd' TWWpkgut15

8. Use the ls command to confirm that the installation was successful:

# ls /opt/TWWfswbin/ man/ pkgutils15/

You should see the directories listed above.

9. Set a path variable to the new software:

# set path=(/opt/TWWfsw/bin $path)

10. Run the following command:

# cd /opt/download_dir/PKG# /opt/TWWfsw/bin/pkg-inst --ignoredeps *.pkg-inst


Oracle

11. Remove any old versions of the rpm package from /usr/local/bin.

12. Change permissions on the TWW files with this command:

# cd /var/opt/TWWfsw# chmod -R a+w

13. Verify that the installation was successful:

# which rpm/opt/TWWfsw/bin/rpm# rpm --versionRPM version 4.2.3 [TWW]

14. Open the /opt/TWWfsw/rpm42/lib/rpm/macros file in a text editor.

15. Search for the lines:

%__perl_provides /opt/TWWfsw/rpm42/lib/rpm/perl.prov%__perl_requires /opt/TWWfsw/rpm42/lib/rpm/perl.req

16. Edit the lines to read as follows:

%__perl_provides perl /opt/TWWfsw/rpm42/lib/rpm/perl.prov%__perl_requires perl /opt/TWWfsw/rpm42/lib/rpm/perl.req

17. Search for the line:

%_transaction_color 2

18. Edit the line to read as follows:

%_transaction_color 0

19. Save and close the file.

20. Remove any old versions of the rpm package from /usr/local/bin.

Downloading the Application Management Pack for BRM installation software

Download the Application Management Pack for BRM media pack from the Oracle E-Delivery Web site:

1. Use a Web browser to access the Oracle E-Delivery Web site: https://edelivery.oracle.com.

2. Click Continue and log into the E-Delivery Web site.

3. On the Media Pack Search page, select Oracle Enterprise Manager in the Select a Product Pack list.

4. Select the appropriate platform, and click Go.


5. From the Results list, select Application Management Pack for BRM and click Continue.

6. Click Download and download the package to a temporary directory (temp_dir).

7. Untar the downloaded package:

tar -xvf package-name.tar

The media downloaded should contain the Disk1 and install directories. For example, when you download and untar the Linux package, the directory structure should look similar to:

temp_dir/

EM/

Disk1/

install/

runInstaller

Using Oracle Universal Installer to install the Application Management Pack for BRM

The Application Management Pack for BRM installation uses Oracle Universal Installer (OUI), a graphical Java-based application that enables you to install Oracle components.

To install the Application Management Pack for BRM:

1. Specify the installation type.

When you install the Application Management Pack for BRM, you are provided with two install options:

– OMS installs the BRM OMS Plug-in. Select this install type to install the BRM OMS Plug-in on the OMS machine.

– Agent installs the BRM Oracle Management Agent Plug-in. Select this install type to install the BRM Agent Plug-in on the Agent machine where you plan to deploy BRM prepaid components.

2. Specify the Oracle home.

BRM components are installed in the Oracle home directories.

– If you select OMS, you must specify the Oracle home directory where Oracle Enterprise Manager 10g Grid Control Release 3 is installated on the OMS system.

– If you select Agent, you must specify the Oracle home directory where the Oracle Enterprise Manager Agent 10g Release 3 is installated on the Oracle Management Agent machine.


Oracle

3. Review the summary information

Before the installation begins, a summary page displays the information you entered. Review the information on this page to make sure it is correct.

4. Begin installation.

Installs the BRM plug-in components.

Installing the BRM OMS components

Important The Application Management Pack for BRM is certified for Oracle Enterprise Manager 10g Release 3 (10.2.0.3). It will not install with an earlier version of Oracle Enterprise Manager.

To install the BRM OMS components on the Oracle Management Service:

1. Install a GUI application such as X Windows to enable a graphical user interface (GUI) installation, and set the DISPLAY environment variable.

2. Go to temp_dir/EM/Disk1/install and enter the following command:

./runInstaller -invPtrLoc OMS_home/oraInst.loc

where

OMS_home is the Oracle home directory where OMS is installed.

The Oracle Universal Installer welcome screen appears.

3. Click Next.

The Select Installation Type screen appears.

4. Select OMS and click Next.

The Specify Home Details screen appears.

5. In the Name drop-down list, select the Oracle home name of the Oracle Management Service where the BRM OMS components are to be installed.

6. In the Path drop-down list, select the Oracle home location where Oracle Management Service is installed.

Important You must select an Oracle home location where OMS is installed. If the Oracle home location does not have OMS installed, OUI displays an error message.

Tip When you select the Name of the OMS Oracle home, OUI automatically populates the Path. Similarly, when you select the Path, it automatically populates the Name.

7. Click Next.

The Database Credentials screen appears.

8. Enter the database credentials needed by the OMS to connect to the database repository where the BRM database components should be created:

a. For Oracle Service name, enter the database service specified in the tnsnames.ora file.

b. For Username and Password, enter a valid user name and password to connect to the database.

c. For Hostname and Port number, enter the database host and port number.


d. For Oracle SID, enter the database system identifier.e. Click Next.

The Summary screen appears.

The Summary screen provides a summary of all the information you entered during the installation process.

9. Verify the information you entered is correct and click Install to begin the installation.

Note Before the installation begins, OUI displays a message to ensure that the Oracle Software Library is correctly set up. If you have not set up the Software Library already, follow the instructions in Configuring the Software Library, then click Install to begin the installation.

The Install screen appears and displays the installation steps being executed and the progress bar.

When the installation is complete, the Configuration Assistants screen appears.

The Configuration Assistants screen displays the recommended configuration script that is executed automatically to perform post-installation configurations, such as running SQL script to update the BRM database repository.

After the configuration script runs successfully, the End of Installation screen appears. This screen tells you whether or not the installation was successful and displays some important information about the product you have installed. This information can also be found in the OMS_home/install/setupinfo.txt file.

10. Click Installed Products.

Verify that the Application Management Pack for BRM is in the list of installed products under OMS.

11. Click Exit to exit the install.

Installing the BRM Oracle Management Agent components

Important The Application Management Pack for BRM is certified for Oracle Enterprise Manager 10g Release 3 (10.2.0.3). It will not install with an earlier version of Oracle Enterprise Manager.

To install the BRM Oracle Management Agent components to the Oracle Management Agent, follow these steps:

Important The following procedure enables you to install the BRM Oracle Management Agent Plug-in software on a single Agent machine. If you have multiple Agent machines, you will need to repeat this procedure to install BRM Oracle Management Agent Plug-in software on each Agent machine.

1. Install a GUI application such as X Windows to enable a graphical user interface (GUI) installation, and set the DISPLAY environment variable.


Oracle

2. Go to temp_dir/EM/Disk1/install and enter the command:

./runInstaller -invPtrLoc Agent_home/oraInst.loc

where

Agent_home is the Oracle home directory where Oracle Management Agent is installed.

The Oracle Universal Installer welcome screen appears.

3. Click Next.

The Select Installation Type screen appears.

4. Select Agent, and click Next.

The Specify Home Details screen appears.

5. In the Name drop-down list, select the Oracle home name of the Oracle Management Agent on the Agent machine where the BRM Agent components are to be installed.

6. In the Path drop-down list, select the Oracle home location where Oracle Management Agent is installed.

Important You must select an Oracle home location where Oracle Management Agent is installed. If the Oracle home location does not have Oracle Management Agent installed, OUI displays an error message.

Tip When you select the Name of the Oracle Management Agent Oracle home, OUI automatically populates the Path. Similarly, when you select the Path, it automatically populates the Name.

7. Click Next.

The Summary screen displays.

The Summary screen provides a summary of all the information you entered during the installation process.

8. Verify the information you entered is correct and click Install to begin the installation.

The Install screen appears and displays the installation steps being executed and the progress bar.

When the installation is complete, the Configuration Assistants screen appears. This screen displays the recommended configuration script that is executed automatically to perform post-installation configurations and to start up the BRM services.

After the configuration script runs successfully, the End of Installation screen appears. This screen tells you whether or not the installation was successful and displays some important information about the product you have installed. This information can also be found in the Agent_home/sysman/setupinfo.txt file.



Verify the Application Management Pack for BRM is in the list of installed products under Oracle Management Agent.

10. Click Exit to exit the install.

Creating BRM source components in the Software Library

The Application Management Pack for BRM uses the existing BRM RPM packages for the installation and patching of the BRM prepaid components. For example, for BRM 7.3.1 release, it uses Portal_Base-7.3.1-1.0.sparc64.rpm for Portal base and Pipeline-7.3.1-1.0.sparc64.rpm for Pipeline Manager.

To deploy BRM prepaid components from Oracle Enterprise Manager Grid Control, you must first create BRM source components in Oracle Enterprise Manager.

Follow these steps to create the BRM source components:

1. Download and package the BRM RPM files.

2. Create the BRM source components in Oracle Enterprise Manager.

Download and package the BRM RPM files

1. Download the following BRM RPM packages for your platform from the Oracle E-Delivery Web site (https://edelivery.oracle.com) to your Agent machine.

– Portal_Base-7.3.1-1.0.x86

– Portal_Virtual-7.3.1-1.0.x86

– Timos-7.3.1-1.0.x86

– Pipeline-7.3.1-1.0.x86

– Diameter-7.3.1-1.0.x86

– AAA_Gateway-7.3.1-1.0.x86

If you also plan to install any BRM optional managers, download the corresponding RPM packages:

– ResourceResMgr-7.3.1-1.0.x86

– GPRS_Mgr_30-7.3.1-1.0.x86

– GPRS_AAA_Mgr-7.3.1-1.0.x86

– GSM_Mgr-7.3.1-1.0.x86

– GSM_AAA_Mgr-7.3.1-1.0.x86

– NumberMgr-7.3.1-1.0.x86

– SIMMgr-7.3.1-1.0.x86

– VoucherMgr-7.3.1-1.0.x86

– ContentMgr-7.3.1-1.0.x86

– MultiDBMgr-7.3.1-1.0.x86

– Diameter-7.3.1-1.0.x86_64.rpm


Oracle

– HPOpenCall-7.3.1-1.0.x86

– BRM_Services_FrameworkMgr-7.3.1-1.0.x86

– BRM_Services_FrameworkMgr_AAA-7.3.1-1.0.x86

2. Use a utility such as WinZip and create the following ZIP files as follows:

a. Zip Portal_Base-7.3.1-1.0.x86 and Portal_Virtual-7.3.1-1.0.x86 RPM files together and save the file as PortalBase_Virtual_7.3.1_x86.zip.

b. Zip Timos-7.3.1-1.0.x86 and Portal_Virtual-7.3.1-1.0.x86 RPM files together and save the file as Timos_7.3.1_x86.zip.

c. Zip Pipeline-7.3.1-1.0.x86 and Portal_Virtual-7.3.1-1.0.x86 RPM files together and save the file as Pipeline_7.3.1_x86.zip.

d. To create a source component for Diameter:a. Copy AAA_Gateway-7.3.1-1.0.x86 and Diameter-7.3.1-1.0.x86 RPM

files to the Agent_home/sysman/admin/scripts/brm directory.

b. Merge AAA_Gateway-7.3.1-1.0.x86 and Diameter-7.3.1-1.0.x86 RPM files manually using the pin_repackage.sh utility. For example:

$Agent_home/sysman/admin/scripts/brm/pin_repackage.sh AAA_Gateway-7.3.1-1.0.x86_64.rpm Diameter-7.3.1-1.0.x86_64.rpm >& pin_repackage.log

Important Specify the absolute path of the RPM packages, otherwise the merge will fail.

c. Zip the merged package and Portal_Virtual-7.3.1-1.0.x86 RPM file together and save it as AAAGW_7.3.1_2.0x86.zip

You can retrieve the merged package name from the pin_repackage.log file. Look for a line in the file that has the format:

Wrote: merged_pkg_name

For example,

Wrote: /tmp/packages/x86_64/Portal_Base-7.3.2-2.6777682.x86_64.rpm

e. To create a source component for MBI:a. Copy the AAA_Gateway-7.3.1-1.0.x86 and HPOpenCall-7.3.1-1.0.x86

RPM files to the Agent_home/sysman/admin/scripts/brm directory.

a. Merge AAA_Gateway-7.3.1-1.0.x86 and HPOpenCall-7.3.1-1.0.x86 RPM files manually by using the pin_repackage.sh utility. For example:

$Agent_home/sysman/admin/scripts/brm/pin_repackage.sh AAA_Gateway-7.3.1-1.0.x86_64.rpm HPOpenCall-7.3.1-1.0.x86_64.rpm >& pin_repackage.log

Important Specify the absolute path of the RPM packages, otherwise the merge will fail.

b. Zip the merged package and Portal_Virtual-7.3.1-1.0.x86 RPM file together and save it as AAAGW_MBI_7.3.1_x86.zip


3. (Optional) Create zip files for the optional manager RPM packages that you want to install.

Note Do not zip optional manager RPM packages with Portal_Virtual RPM package.

For example, to create a package for GPRS Manager, zip GPRS_Mgr_30-7.3.1-1.0.x86 RPM file and save it as GPRS_Mgr_30-7.3.1-1.0_x86.zip.

Create the BRM source components in Oracle Enterprise Manager

Repeat the following steps to create source components for each BRM prepaid component (CM, DM, DMT, RTP, AAAGW):

1. In the Oracle Enterprise Manager Grid Control page, click the Deployments tab.


3. In the Provisioning page, click the Components subtab.

4. Select BRM Components and click Create Component.

5. In the Create Component: Describe page, enter the following:

a. In the Type field, enter Generic Component.b. In both the Name and Description field, enter the source component name

as follows:

Important You must enter the BRM source component names as shown below. The BRM deployment procedures checks for these component names.

Note You can specify any name for the optional manager source component names. For example, for GPRS, you can specify GPRS Source Component for the source component name.

c. In the Product Name field, enter BRM.d. In the Product Version field, enter 0.1.e. In the Vendor field, enter Oracle.

6. Click Next.

7. In the Create Component: Customize page, click Next.

BRM component Source component name

CM BRM CM Source Component

DMO BRM DMO Source Component

DMT BRM DMT Source Component

RTP BRM RTP Source Component

AAAGW and Diameter BRM AAAGW Diameter Source Component

AAAGW and MBI BRM AAAGW MBI Source Component


Oracle

8. In the Create Component: Upload File page, upload the ZIP file corresponding to the source component name:

Note For optional managers, upload the zip file corresponding to the optional manager source component name.

9. Click Next.

10. In the Create Component: Set Directives page, click Choose Directives.

11. In the Choose Directives page, select BRM Directives and click + to expand the list.

12. Select copy_file and click OK.

13. Click Next.

The Review page appears.

14. Review the information you entered and click Finish to create the source component.

15. In Enterprise Manager Grid Control console, click Deployments tab.

16. Click Provisioning subtab.

17. In the Components table, choose Components and click + to expand the list.

18. Choose BRM Components and click + to expand the list.

The status of the source component created should be Ready.

Creating customer configuration files

When you deploy BRM prepaid components from the Oracle Enterprise Manager Grid Control, you provide some configuration information through the UI that is minimaly needed to configure and start up the BRM process. For example, when you deploy Oracle DM from the Oracle Enterprise Manager Grid Control console, the UI prompts you to enter the following:

• Host Name

• DM Port Number

• SM Database

• SM ID

• SM Password

Source component name ZIP filename

BRM CM Source Component PortalBase_Virtual_7.3.1_x86.zip

BRM DMO Source Component PortalBase_Virtual_7.3.1_x86.zip

BRM DMT Source Component Timos_7.3.1_x86.zip

BRM RTP Source Component Pipeline_7.3.1_x86.zip

BRM AAAGW Diameter Source Component AAAGW_7.3.1_2.0x86.zip

BRM AAAGW MBI Source Component AAAGW_MBI_7.3.1_x86.zip


• DM Name

• Oracle Home

• Log File Location

• Staging Location

• Install Location

• Third Party Location

For all other Oracle DM configuration parameters, the deployment procedure uses default values.

To change the default values or set additional configuration parameters for a component, you set up a customer configuration file with the configuration values and upload the configuration file in Oracle Enterprise Manager. Later, when you run the deployment procedure to install the component, you select the corresponding customer configuration file to use to configure the component.

Note Creating custom configuration files for CM, Oracle DM, TIMOS DM, RTP, and AAA Gateway Manager components is optional. You need to create these configuration files only if you want to change the default settings.

Setting up a customer configuration file

To set up a customer configuration file:

1. Use a text editor to create a file with your configuration setting entries in the format:

instanceName.attr_name value

where

instanceName specifies a component's instance name. For example, dmo1.

Note To specify all instances of a component type, use an asterisk (*) for instanceName. You can also use an asterisk (*) for partial matching. For example, dmo1* will match all instances that begin with "dmo1".

attr_name is the derived name of an attribute.

– For an attribute specified in a registry file, the attr_name is created by joining all of the heirarchical names separated with periods (.). For example, in a RTP registry file:

ifw {

Semaphore { FileName = "abc" }

}

The attr_name would be ifw.Semaphore.FileName.

Note For the AAA Gateway Manager and RTP components, the prefix is ifw. For the TIMOS DM component, the prefix is timosMgr.


Oracle

– For an attribute specified in a pin.conf file, the attr_name is created by joining all of the names except the first "-" separated with periods (.). For example for a CM pin.conf line:

- cm cm_loglevel 1

The attr_name would be cm.cm_loglevel.

Note The name after the "-" in the a pin.conf is the name of the piece of software that reads the attribute. Thus for a CM component, this name can be cm but it can also be the name of any Facilities Module (FM). For example, fm_bill, fm_cust_pol. For a Oracle DM component, this will be dm.

– The attr_name can also specify an environment variable used by a component. In this case, the environment variable name is used as the attr_name. For example, ORACLE_HOME.

value specifies the value for the attr_name.

Note When a configuration parameter exists both in the customer configuration file and as an input entry in the UI, the UI entry takes precedence.

2. Save the text file to one of the filenames below.

Important Specify the filenames exactly as shown below. The filenames are case sensitive.

The following is a sample of the dmo_customer.values file:

dmop1.dm.database_request_timeout_duration 0*.dm.dd_write_enable_fields 1*.dm.dd_write_enable_objects 1*.dm.dd_write_enable_portal_objects 1*.dm.die_on_exception 1dmop1.dm.dm_bigsize 2097152dmop1.dm.dm_db_no 0.0.0.1 / 0dmop1.dm.dm_in_batch_size 80dmop2.dm.database_request_timeout_duration 0dmop2.dm.dm_bigsize 5097152dmop2.dm.dm_db_no 0.0.0.1 / 0dmop2.dm.dm_in_batch_size 100

BRM component File name

CM

Optional Manager

cm_customer.values

Note Use this file name for optional manager components also.

Oracle DM dmo_customer.values

TIMOS DM dmt_customer.values

RTP rtp_customer.values

AAA Gateway Manager

aaa_customer.values


Uploading customer configuration files to Oracle Enterprise Manager

To upload customer configuration files to Oracle Enterprise Manager:



3. In the Provisioning page, click the Components subtab.

4. Select Components and click Create Folder.

5. In the Create Folder page, enter BRM Customer Configuration in both the Name and Description fields.

6. Click OK.

7. In the Provisioning page, select BRM Customer Configuration, and click Create Component.

8. In the Create Component: Describe page, do the following:

a. In the Type field, enter Generic Component.

b. In both the Name and Description fields, enter the customer configuration name as follows:

Important You must enter the BRM source component names as shown below. The BRM deployment procedures checks for these component names.

.

c. In the Product Name field, enter BRM.d. In the Product Version field, enter 0.1.e. In the Vendor field, enter Oracle.f. Click Next.

9. In the Create Component: Customize page, click Next.

BRM component Customer configuration name

CM

Optional manager

BRM CM Customer Config

Note Use this configuration name for optional manager components also.

Oracle DM BRM DMO Customer Config

TIMOS DM BRM DMT Customer Config

RTP BRM RTP Customer Config

AAA Gateway Manager

BRM AAAGW Customer Config


Oracle

10. In the Create Component: Upload page, select Upload from Agent machine.

a. In the Host field, enter the Agent machine name or click Select Target and navigate to the Agent machine.

b. In the File name field, enter the full path or click Select File and navigate to the file corresponding to the customer configuration name:

11. Click Next.

12. In the Create Component: Set Directives page, click Choose Directives and click + next to BRM Directives to expand the list.

13. Select copy_file and click OK.

14. Click Next.

The Review page appears. Review the information you entered and click Finish to create the source component.

Uninstalling the Application Management Pack for BRM

Before uninstalling the Application Management Pack for BRM

Before uninstalling the Application Management Pack for BRM, remove the discovered targets and target pages from the Oracle Enterprise Manager Grid Control console.

1. In the Oracle Enterprise Manager Grid Control page, click the Targets tab and then click the All Targets subtab.

2. Select the BRM target to remove and click Remove.

3. Repeat step 2 for all BRM discovered targets.

4. Similarily, select Oracle BRM Suite, Oracle BRM Suite_Service, Oracle BRM Suite_System individually from the All Targets subtab and click Remove.

Customer configuration name Filename

BRM CM Customer Config cm_customer.values

BRM DMO Customer Config dmo_customer.values

BRM DMT Customer Config dmt_customer.values

BRM RTP Customer Config rtp_customer.values

BRM AAAGW Customer Config aaa_customer.values


Uninstalling the Application Management Pack for BRM from OMS

To uninstall the Application Management Pack for BRM, follow these steps:

1. (Optional) Uninstall the database changes by performing the following step:

a. Go to OMS_home/setup/scripts and run the following command:

perl remove_dbch.pl

Important If you have deployed BRM OMS Plug-in on multiple Oracle Management Service systems that use the same database repository, running the remove_dbch.pl script will remove the database changes for all the BRM OMS Plug-ins. You should not remove the database changes unless you plan to uninstall all the BRM OMS Plug-ins.

2. Go to OMS_home/oui/bin and run the following command:

./runInstaller -invPtrLoc OMS_home/oraInst.loc

3. On the Oracle Universal Installer welcome screen, click Deinstall Products.

4. Select Application Management Pack for BRM.


Verify that the Application Management Pack for BRM is not in the list of installed products under OMS.

Uninstalling the Application Management Pack for BRM from the Agent

To uninstall the Application Management Pack for BRM, follow these steps:

1. Go to Agent_home/oui/bin and run the following command:

./runInstaller -invPtrLoc Agent_home/oraInst.loc

2. On the Oracle Universal Installer welcome screen, click Deinstall Products.

3. Select Application Management Pack for BRM.

4. Click Remove.


Verify that the Application Management Pack for BRM is not in the list of installed products under Agent.


Oracle

Deploying BRM prepaid components

Before deploying BRM prepaid components• Ensure the hardware and software requirements are met for the component

that you want to deploy. See Hardware and software requirements.

• Ensure that the SNMP package and the Third-Party package are installed in the Agent and the OMS machines.

• Ensure that the database with all the needed BRM tables has been created.

• Ensure that the tnsnames.ora file in all the Agents has an entry for the BRM database.

• Ensure that you are able to connect to the BRM database from the Agents.

• (Optional) Set up and upload the customer configuration files. Creating customer configuration files.

Setting up preferred credentials

You can set preferred credentials for all managed targets in your enterprise. If preferred credentials are set for a target, applications automatically use the preferred credentials to log into that target.

To set up preferred credentials, follow these steps:

1. In Enterprise Manager Grid Control page, click Preferences link at the top of the page.

2. Click Preferred Credentials link in the navigation bar.

3. Click Set Credentials for Target Type Host.

The Host Preferred Credentials page appears.

4. Under the Target Credentials section, enter the username and password in the Normal Username, Normal Password, Privileged Username, and Privileged Password fields for each target host.

5. Click Test.

If the test is successful, "Credentials successfully verified for target" message is displayed at the top of the page.

6. Click Apply.

For more information about preferred credentials, see Managing Preferred Credentials in the Enterprise Manager online Help.


Deploying BRM prepaid components

You deploy BRM prepaid components by running the BRM provisioning deployment procedure from the Oracle Enterprise Manager Grid Control console.

The following is a high-level description of the steps that are executed by the deployment procedure:

• From the OMS system, it copies the install file, component binary file, and the customer configuration file to the staging directory on the target host machine and unzips the files.

• Invokes the installation script for the specific component to install the component.

• Generates the configuration file for the component.

• Starts the service.

• Verifies the service is running.

• Registers BRM targets to Oracle Enterprise Manager.

To deploy BRM prepaid components:


2. In the Deployments page, scroll to the Deployment Procedure Manager section and click the Deployment Procedures link.

The Deployment Procedure Manager page appears.

3. Select BRM Software Provisioning.

4. Click Run to invoke the deployment procedure.

The Source Selection page appears.

5. Click Add.

The Search and Select: Source page displays the BRM components that are available in the Software Library.

Note The BRM components displayed are from the default BRM location in the Software Library. If you want to view components created in other locations, use the search functionality.

a. Select the check boxes of the BRM components that you want to install.If you select multiple BRM components, they are installed in the following order:

– Oracle DM

– TIMOS DM

– CM

– RTP

– AAA Gateway Manager

b. (Optional) Select the check boxes of the customer configuration files for the BRM components that you want to install.

6. Click Select.


Oracle

7. Click Next.

The Target Selection and Configuration page appears.

8. Select the BRM component to install.

9. Click Add.

The Search and Select: Targets page appears.

10. Select the target hosts on which to install the component.

Note Use the search functionality to find target hosts. Your target hosts must all be on the same platform.

11. Click Select.

12. Specify the configuration information for the selected component. See Component configuration information.

13. Repeat steps 9 through 12 for each component selected.

14. Click Next.

The Credentials page appears.

15. Select the BRM component.

16. (Optional) To override the preferred credentials, do the following:

a. Select Override Preferred Credentials.Oracle Enterprise Manager prompts for the new user name and password.

Note The credentials you enter do not get stored in the Management Repository.

b. Enter the new administrator Username and Password for the target host.c. Repeat steps a through c for each BRM component selected.

17. Click Next.

The Schedule page appears.

18. In the Schedule section, do one of the following:

To start the deployment procedure immediately:

a. Select One Time (Immediately).b. Select Indefinite or End After Grace Period

If you select End After Grace Period option, enter the length of time for Oracle Enterprise Manager to attempt to run the procedure.

To start the deployment procedure at a later time:

a. Select One Time (Later).The current time and date of the database repository is displayed.

b. Specify the Time Zone, Start Date, and Start Time to run the procedure.

Note The procedure will run when the time on the database repository is the time you specify.

c. Select Indefinite or End After Grace Period.If you select End After Grace Period, enter the length of time for Oracle Enterprise Manager to attempt to run the procedure.


19. In the Deployment Procedure Instance Name section, enter a name for the deployment procedure instance.

20. Click Next.


21. (Optional) To make changes to the information displayed, click Back to go to the previous pages and make the changes.

22. Click Finish to start the provisioning deployment procedure.

To view the progress of the steps executed by the procedure, follow these steps:

a. In the Enterprise Manager Grid Control page, click the Deployments tab.b. In the Deployments page, scroll to the Deployment Procedure Manager

section and click the Procedure Completion Status link.The Procedure Completion Status page appears.

c. Select BRM Software Provisioning link. The progress details are displayed under the Status Details sectoin.

When the BRM provisioning deployment procedure finishes, the Deployment Procedure Manager screen appears with the following details:

– Deployment procedure name - BRM Software Provisioning

– Status - Succeeded

– Procedure name - BRM Software Provisioning version

– Type - BRM Provisioning

– Owner - User name used to log into the OMS host machine

– Last updated - Date and time when the BRM provisioning procedure was completed.

After the provisioning deployment procedure is complete, you should be able to view the newly provisioned components and their status under the Targets tab. See Targets tab.

The deployment procedure logs all the activity in the file installRPM.log in the staging location. If the procedure fails to deploy the BRM components, check the log file for the reason for the failure.


Oracle

Component configuration information

The following tables list the component configuration entries:

DMO

DMT

Field name Description

Host Name Name of the host machine on which to install Oracle DM.

DM Port Number Port number for the Oracle DM process.

SM Database BRM database alias name.

SM ID Database user name that the Oracle DM uses to log in to the BRM database. This entry is set when you install BRM, but it can be changed.

SM Password Password for the user specified in the SM ID entry.

DM Name Name of the Oracle DM instance. For example, dmop1.

Important If there are multiple Oracle DM instances, DM Name should be unique for each instance.

Oracle Home Oracle home of the client connecting to the BRM database.

Note Oracle DM Oracle home should be the same version as the Oracle home of the BRM database.

Log File Location Location where Oracle DM log file is created.

Staging Location Location where files are temporarily staged before the installation.

Install Location Directory where you want to install Oracle DM.

Third Party Location Directory where Third-Party software is installed.


Host Name Name of the host machine on which to install TIMOS DM.

HTTP Port HTTP port to connect to browser.


Acceptor Port Port on which TIMOS DM is listening.

SNMP AgentX Port SNMP AgentX port.

SNMP Master Agent Port SNMP listener port.

HA Mode Yes or No

Set to Yes, if your system is provisioned for high-availability with multiple instances of TIMOS DM. Otherwise, it is set to No.

Private Peer Acceptor Port Handshake port where the primary and secondary TIMOS DMs exchange heartbeat.

Note If HA Mode is Yes, then Private Peer Acceptor Port entry is enabled, otherwise it is disabled

Peer Name Port Acceptor port of peer TIMOS DM.

Note If HA Mode is Yes, then Peer Name Port entry is enabled, otherwise it is disabled.

Private Peer Port Acceptor port of peer TIMOS DM.

Note If HA Mode is Yes, then Private Peer Port entry is enabled, otherwise it is disabled

Connector List DM Oracle processes that connect to the TIMOS DM.

DM Oracle list should be in the format “host port” where:

host is the server where DM Oracle process is running.

port is the DM Oracle port.

Note Multiple DM Oracle pointers should be separated using “|” symbol. For example, “host1 port1 | host2 port2|host3 port3”.

DMT Name Name of the DMT instance. For example, dmtp1.

Important If there are multiple DMT instances, DMT Name should be unique for each instance.




Oracle

CM

Log File Location Location where TIMOS DM log file is created.

Role Primary or Secondary

Primary TIMOS or Secondary TIMOS.


Install Location Directory where you want to install TIMOS DM.



Host Name Name of the host machine where CM will be installed.

CM Port Number Port number for the CM process.


Note CM Oracle home should be the same as the Oracle home of the BRM database.

DM Pointer Host and port number for DMs connecting to BRM database.

Use '|' symbol to separate multiple DM pointer entries:

For IP communication:

"db_no ip host1 port1 | db_no ip host2 port2 |"

For pipes (AF_unix sockets):

"db_no local filename | db_no local filename |"

HA entries are separated by A space within each entry before '|':

"db_no ip host1 port1 ip host2 port2 |"

EM Pointer Discounting Host and port number in the formatip <host> <port>.

EM Pointer Rerating Host and port number in the formatip <host> <port>.



RTP

EM Pointer Zoning Host and port number in the formatip <host> <port>.

CM Name Name of the CM instance. For example, cmp1.

Important If there are multiple CM instances, CM Name should be unique for each instance.

Log File Location Location where CM log file is created.


Install Location Directory where you want to install CM.



Host Name Name of the host machine where RTP will be installed.

Threadpool Port Number Port number for the treadpool of the RTP.

Event Port Event Handler port for RTP.


SNMP Port SNMP Agentx port.

Threadpool Max Threads Maximum number of threads in the threadpool.

BRM DB Alias BRM database alias name.

BRM DB Userid User name used to log into the BRM database.

BRM DB Password Password used to log into the BRM database.

Pipeline Mgr DB Alias Pipeline Manager database alias name.

Pipeline Mgr DB Userid User name used to log into the Pipeline Manager database.

Pipeline Mgr DB Passwd Password used to log into the Pipeline Manager database.



Oracle

AAAGW

Roguewave OCI Library Version The version of the Roguewave OCI Library. For example, oci61.

RTP Name Name of the RTP instance.


Note Oracle home should be the same as the Oracle home of the BRM database.

Log File Location Location where RTP log file is created.


Install Location Directory where you want to install RTP.



Host Name Name of the host machine where AAA Gateway Manager will be installed.

AAAGW Port Number AAAGW port number provided in the Dispatcher pipeline.

AAAGW Protocol Diameter or MBI.

Event Port Event Handler port for the AAA Gateway Manager.


SNMP Agentx Port SNMP Agentx port.

CM Pointer Host and port number.

AAAGW Name Name of the AAA Gateway Manager instance.


Note Oracle Home should be the same as the Oracle home of the BRM database.

Log File Location Location where AAA Gateway Manager log file is created.



Deploying BRM Optional ManagersThe BRM prepaid components also includes the following optional managers:

• Content manager

• GPRS AAA Manager

• GPRS Manager

• GSM AAA Manager

• GSM Manager

• MultiDB Manager

• Number Manager

• Resource Reservation Manager

• SIM Manager

• Telco Framework Manager

• Telco Framework AAA Manager

• Voucher Manager

• Services Framework Manager

• Services Framework AAA Manager

• WirelessSuite

Note The postpaid components, Account Synchronization Manager and Rated Event Loader, are not available when you install the WirelessSuite optional manager in Enterprise Manager Grid Control.

Optional managers are installed as a patch on top of the BRM Base component.

Before deploying BRM Optional Managers• You must first upload the Optional Manager RPM packages to the Oracle

Software Library by creating source components. See Creating BRM source components in the Software Library.

• Set up preferred credentials. See Setting up preferred credentials..

Staging Location Location where files are temporarily staged before the installation..

Install Location Directory where you want to install AAA Gateway Manager.




Oracle

Deploying BRM Optional Managers

To deploy BRM optional managers:




3. Select Patch Oracle BRM Software.

4. Click Run to invoke the patch deployment procedure.

The Software Updates page appears.

5. In the Source section, click Add and search for BRM optional manager source components in the Software Library.

Note Only one optional manager can be deployed at a time.

6. In the Search And Select Source page, enter the search criteria to locate the optional manager source component and click Go.

Tip When entering the search criteria, enter the full optional component name. For example, BRM GSM Manager source component. Otherwise, the search will result in no components found.

Oracle Enterprise Manager displays the list of components that are applicable based on your search criteria.

7. Select the check box of the component that you want to install and click Select.

Important Only select one optional manager component to deploy.

8. (Optional) Select the customer configuration file to be used for the optional manager installation.

9. Ensure that the BRM Application Updates section does not have any patch selected.

Important You can not apply a patch while deploying an optional manager.

10. Click Next.

The Target List page appears.

11. Click Add.

12. In the Select Target page, specify the target type and the platform and click Go.

13. Select the check boxes of the target hosts on which to install the component.

14. Click Select.

15. Click Next.



16. In the Specify For list box, do one of the following:

a. Select Each Host to specify a user name and password for each host.b. Select All Hosts to specify a single user name and password to be used for

all hosts.

17. Do one of the following:

a. If you selected Each Host, to override the preferred credentials, edit the default user name and password.

b. If you selected All Hosts, enter a user name, password, and re-enter the password to confirm.

18. Click Next.



Note The Repeating option is not used in BRM Software patching.

To start the patching deployment procedure immediately:


If you select End After Grace Period option, enter the length of time for Oracle Enterprise Manager to attempt to run the procedure.

To start the patching deployment procedure at a later time:





20. Click Next.



22. Click Finish to start the patch deployment procedure.

To view the progress of the steps executed by the deployment procedure, follow these steps:


section and click the Procedure Completion Status link.c. The Procedure Completion Status page appears.d. Click Patch Oracle BRM Software link.

The progress details are displayed under the Status Details section.


Oracle

To verify the optional manager has been deployed successfully, run the following commands on the agent machines where the optional manager was installed:

rpm -qa --root cm_install_loc --dbpath cm_install_loc/rpm_db

where

cm_install_loc is the install location of the CM component. For example, /export/pin01/cmp1.

The command will return the Portal_Base version, for example, Portal_Base-7.3.1-2.0.

Run the following command to get the version information of the optional manager.

rpm -qi portal_base_version --root cm_install_loc --dbpath cm_install_loc/rpm_db

For example:

rpm -qi Portal_Base-7.3.1-2.0 --root /export/pin01/cmp1 --dbpath /export/pin01/cmp1/rpm_db

You can also check for the following:

– CM configuration file has been updated with the optional manager entries.

– Services are up and running.

The patch deployment procedure logs all the activity in patchRouter.log file in the staging location of the CM component. If the procedure fails to install the optional manager, check the log file for the reason for the failure.

Discovering BRM targetsTo monitor and manage the BRM targets, you must first discover them. Targets can be discovered using the auto discovery process or the guided discovery process. Auto discovery applies when BRM components are provisioned using Oracle Enterprise Manager. Guided discovery is used to discover and monitor the post-paid components. Currently, only the prepaid components can be provisioned through Oracle Enterprise Manager. To discover postpaid components, you must run the guided discovery.

To discover BRM post-paid targets using a guided discovery:

1. From the Oracle Enterprise Manager Grid Control console, click the Target tab, then All Targets subtab.

2. From the Add drop down list, select Oracle BRM Suite, then click Go.

The BRM Targets Discovery page appears.

3. Click Add.

The Search and Select: Targets page appears.


4. Select Host as the Target Type.

5. Specify the host name for Target Name to search, and click Go.

The respective host is listed in the table.If you do not specify the Target Name, the table lists all the host targets.

6. Select the hosts where BRM is running by clicking the corresponding check boxes, and click Select.

All the selected hosts are listed in the BRM Targets Discovery page.

7. Select the hosts you want to add and specify the following information for each selected host:

– BRM Home path--the path where BRM is installed. The home path for BRM base components is PIN_HOME and the home path for Pipeline components is IFW_HOME.

– IFW Registry File to be discovered--the registry file name for IFW. You must specify this for discovering the batch pipeline processes. If this information is not provided, wireless.reg is taken as a default value.

– BRM ThirdPartyApps path--the path where the third-party applications are installed.

– Host user name--the user name used while connecting to the host.

– Host password--the password used while connecting to the host.

8. Click Ok.

The discovery process starts and the AllTargets page appears with a list of all the discovered BRM targets. This process creates a BRM system with the data provided and the same is then uploaded into the Oracle Enterprise Manager repository.

Note You might need to click Refresh to refresh the list of discovered targets.

Monitoring and controlling BRM targetsOEM provides an option of monitoring and controlling all BRM targets by using an existing BRM utility called pin_ctl. This utility monitors the following BRM processes:

• Connection Manager (cm)

• CM Master Process (cmmp)

• Connection Manager Proxy (cm_proxy)

• DM Oracle (dm_oracle)

• DM Email (dm_email)

• DM EAI (dm_eai)

• DM Paymentech (dm_fusa)

• DM Account Synchronization Oracle AQ (dm_ifw_sync)

• DM Account Synchronization MSMQ (dm_ifw_msmq)

• DM Invoice (dm_invoice)

• EAI Java Server (eai_js)


Oracle

• Invoice Formatter (formatter)

• AAA Gateway

• Real-time and Batch Pipeline

• DM TIMOS

• Batch Controller (batch_controller)

You can monitor the targets by monitoring the following:

• Start, stop, or restart individual BRM targets or start, stop, or restart multiple BRM targets at once. For example, you can start or stop only CMs by selecting the CMs and clicking Start. You can also restart individual target or selected BRM targets. For more information about starting, stopping, and restarting BRM targets, see Starting, stopping, or restarting BRM targets.

The starting, stopping, and restarting of targets take place in a rolling phase according to the order supported by BRM.

• Performance history

• Log file alerts and other alerts related to the target

• Current value of metric

• Configuration details of a target

Starting, stopping, or restarting BRM targets

You can perform one of the following:

• Starting, stopping, or restarting individual BRM targets

• Starting, stopping, or restarting all or selected BRM targets

Note You can start, stop, or restart individual targets from the respective target’s home page. For starting, stopping, and restarting all or selected BRM targets, go to the Members tab on the Oracle BRM Suite page.

Starting, stopping, or restarting individual BRM targets

To start and stop BRM targets:

1. From the Oracle Enterprise Manager Grid Control console, click the Target tab, then the BRM subtab.

The Oracle BRM Suite_System page appears.

Note If you have not configured the BRM subtab, you can access the targets from the All Targets tab. For more information, see Adding the BRM subtab.

2. Click the Components tab.

The Components tab on the Oracle BRM Suite_System page becomes active and displays a list of all the discovered targets. This list shows the status of all the listed targets, alerts pertaining to the targets, and the policy violations.


3. Click the name of the target you want to start, stop, or restart.

The home page of the respective target opens with the details including the status of the target, services impacted, availability, and so on.

4. Click Start, Stop, or Restart to start, stop, or restart the target respectively.

Note To start BRE target, you must define IFW_EVENTHANDLER_PORT with absolute paths for variables TNS_ADMIN and ORACLE_HOME in $IFW_DIR/bin/pin_ctl.conf. If this environment variable is not set, pin_ctl will not be able to start BRE and will terminate. It should be set in the pin_ctl.conf of the pin_ctl script, which is used for the process control of BRE.

Starting, stopping, or restarting all or selected BRM targets

To start and stop all BRM targets:

1. From the Oracle Enterprise Manager Grid Control console, click the All Target tab, then Oracle BRM Suite.

The Oracle BRM Suite page appears.

2. Click the Members tab.

A list of all the BRM targets is displayed.

3. Select the targets you want to start or stop by selecting the corresponding check boxes and click the following buttons to perform the respective actions:

– Start--Starts all the selected targets.

– Stop--Stops all the selected targets.

– Restart--Stops and starts all the selected targets.

– Start All--Starts all the targets irrespective of whether you have selected the target or not.

– Stop All--Stops all the targets irrespective of whether you have selected the target or not.

– Restart All--Stops and starts all the targets irrespective of whether you have selected the target or not.

Viewing log file alerts

To view the log file alerts for BRM targets:

1. Navigate to the home page of the target you want to view the alerts for.

The Alerts section lists all the defined metrics for the target, the severity of the alert, the time the alert was triggered, the last value of the alert, and the time when the metric was last checked. The Host Alerts section lists all the alerts related to the host on which the target is running.

2. Click the alert for which you want to view the detailed information.

The Alert Detail page appears. This page displays the alert statistics, graph for the metric value, and the alert history.


Oracle

You can also monitor alerts in the following ways:

• From the Alerts section in home page

• From the Alerts column in the Members table of Suite page

• From the Home page in the suite/system--Here the number of alerts for a target is displayed in the alerts and violations column of the members table.

Viewing the metric current value

To view the current value for any particular metric:

1. Navigate to the target’s home page.

2. Scroll to the bottom of the page and click the All Metrics link.

A list of metrics being monitored for the target appears.

3. Click the metric.

The metric’s home page appears, which displays all the current data (dynamic real-time values) for the selected metrics. For example, if the Process Information metric is selected, only the CPU usage and the Memory usage is displayed. If the Log file Monitoring metric is selected, log file related entries, matching string, and so on are displayed. If the Response metric is selected, the status of the component is displayed with the respective values (0-down and 1-up).

Note QOS is displayed only for BRE (batch pipeline) and EDR/sec is displayed only for TIMOS.

Viewing the configuration details

To view the configuration details of a target:


2. Scroll to the bottom of the page and click the View Configuration link under the Configuration section.

The View Configuration page appears.

Note

• You might have to click Refresh to view or refresh the data.

• Enterprise Manager will display an error message if the value of a configuration parameter for any target exceeds 100 characters. This is due to a limitation in Enterprise Manager. If this occurs, edit the pin.conf file and comment out the entry that exceeds 100 characters. Also, if a configuration parameter has multiple values then the combined values must not exceed 100 characters.


Monitoring the performance history

To monitor the performance history of a target:

1. From the Oracle Enterprise Manager Grid Control console, click the Targets tab, then click the BRM subtab.


Note If you have not configured the BRM subtab, you can access the targets from the All Targets tab.


A list of all the BRM targets appears.

3. Click the target for which you want to view the performance history.

The target’s home page appears.

4. Click the Performance tab.

The performance details of the target appear.

5. Select the period for which you want to view the performance data for the target.

The page refreshes and shows the relevant performance data.

Configuring alerts

Alerts can be configured for the following cases:

• When a BRM process goes down or comes up.

• When a critical or major error occurs.

• When the CPU or memory usage by a BRM process exceeds a configured threshold.

• When EDR processing (EDRs per second) by a pipeline falls below a configured threshold.

• When AAA opcode performance falls below a configured level.

Note Currently, alerts are not configured for EDR processing and AAA opcode performance. These can be configured later, if required.

The following table shows the default configurations for alarms:

Alarms Description

CPU Usage This type of alarm monitors CPU usage for BRM components such as CMs, DMs, and AAA Gateway.

Alarms are raised as follows:

If the CPU usage crosses 20%, a Warning alarm is raised.

If the CPU usage crosses 25%, a Critical alarm is raised.

Memory Usage If the memory usage crosses 20%, a Warning alarm is raised.

If the memory usage crosses 25%, a Critical alarm is raised.


Oracle

To configure alerts:





The Oracle BRM Suite_System page appears with a list of all the BRM targets.

Note You can configure alerts for all the BRM targets other than BRM suite system and BRM suite services. BRM suite system and BRM suite services are repository-only targets, which means these targets are not physically available and are just a logical grouping of multiple targets.

3. Click the target for which you want to configure the alert.

The target’s home page appears.

4. Click the Metric and Policy Settings link under the Related Links section.

The Metric and Policy Settings page appears. This page lists the defined metrics, and their thresholds for the selected target.

5. Click Edit corresponding to the metric you want to modify.

The Edit Advanced Settings page appears.

Opcode Performance

There are no alarms for opcode performance. These are information-only metrics.

Error Messages These alarms occur whenever a specified error message occurs.

The alarms are read from log files for the following components:

• Oracle BRM AAA Gateway

• Oracle BRM Connection Manager

• Oracle BRM Java Process

• Oracle BRM Pipeline

• Oracle BRM RTP

• Oracle BRM TIMOS Data Manager

• Oracle BRM Data Manager

Pipeline EDR throughput

There are no alarms for EDR statistics. These are information-only metrics.

Alarms Description



– To add a new process object to the metric, click Add . Enter a value for Process Name, Warning Threshold, and Critical Threshold and click Continue to add the new process name to the list.

– To edit the existing Process Name object, click Edit .

The Edit Advanced Settings page appears for the Process Name object.

You can specify different threshold settings for each Process Name object. You can use this page to perform the following actions:

Specify the corrective actions to be taken when a warning or a critical alert is triggered. See Adding corrective actions.

Modify the existing threshold settings.

7. Click Continue.

You are returned to the Edit Advanced Settings page.

8. Click Continue if you have finished making the changes to the configurations.

The Metric and Policy Settings page appears.

9. Click OK to save the changes.

A confirmation message is displayed on the Confirmation page.

Configuring the collection schedule

You can modify the metric collection schedule, change the collection frequency (if the data collection is enabled), and view any metrics and policies that will be affected by the collection schedule change. You can modify the metric collection schedule from the Edit Collection Settings page.

To configure the collection schedule:


2. Click the Metric and Policy Settings link.

3. Click the link under the Collection Schedule column for the metric that needs to be modified.

The Edit Collection Settings page for the metric appears.

4. Select the frequency type.

5. In the Repeat Every field, enter a value .

The Affected Metrics section lists the metrics that are affected by editing the current metric.

Note If you change the CPU usage collection schedule, the memory usage schedule will also change.

6. Click Continue.

You are returned to the Metric and Policy Settings page.

7. Click OK to save the changes.


Oracle

Adding corrective actions

Corrective actions let you specify automated responses to alerts. Corrective actions ensure that routine responses to alerts are automatically executed, ensuring problems are dealt with before they impact the business operations.

Note By default, there are no corrective actions set for alerts in BRM.

To add corrective actions for warnings and critical alerts:


2. From the target’s home page, click the alerts for which you want to add a corrective action.

The Alert Details page appears.

3. In the Related Links section, Click Metric and Policy Settings.

The Metric Thresholds page appears.

4. Click the pencil icon for a specific metric.

The Edit Advanced Settings page appears.

5. Under Corrective Actions, click Add for the metric severity (Warning or Critical) for which you want to associate a corrective action.

The Add Corrective Action page appears.

6. Select the task type and click Continue.

The Create Corrective Action pages appears.

7. Define the corrective action.

8. Click Continue.

You are returned to the Edit Advanced Settings page. The corrective action is set for the metric thresholds.

Displaying BRM system topologyBRM is a distributed system with its processes existing on different servers. The system topology feature provides a graphical representation of all the BRM components and the association among these components. The system topology helps in visualizing, monitoring, and controlling the BRM processes from a central location. You can click any of the components to view the information related to the components, like the name and status of the component, critical and warning alerts for the component, and the host of the component.

To display the BRM system topology:





2. Click the Topology subtab.

The BRM system topology appears. The topology consists of icons that represent the components of BRM system. The topology also shows associations between two components.

Patching BRM prepaid componentsYou apply BRM software patches by running the BRM patching deployment procedure from the Oracle Enterprise Manager Grid Control console.

The BRM patching deployment procedure applies BRM software patches serially on different hosts using zero downtime upgrade (ZDU) logic. With ZDU, while a primary prepaid component is patched, calls are routed to the secondary prepaid component. The ZDU allows you to upgrade your high-availability system to a new patch version without disrupting services for the end user.

If any error is encountered, no further steps are processed for that target host but the procedure continues to apply the patch to the other targets. When an error occurs, the user or system administrator can view the status of the procedure by viewing Procedure Completion status tab. The user or system administrator can rerun the patch deployment procedure after correcting the errors.

Similarily, when the patch deployment procedure detects that the selected patch has already been applied on the target host, no further steps are processed for that target but the procedure continues to apply the patch to other targets.

The following is a high-level description of the steps that are executed by the BRM patch deployment procedure:

• Checks if the selected patch has already been installed on the target host. If yes, it skips to the next target host.

• Creates a backup of the previous RPM package.

• Merges the patch package with the existing RPM package.

• Stops the BRM services.

• Upgrades BRM to the new patch level. The system retrieves configuration information from the Oracle Management Repository and applies the patch serially on different hosts in a rolling fashion using the ZDU logic.

• Generates the new configuration file.

• Starts the BRM service.

• Verifies that the service is running. If the service failed to start, the patch is rolled back to the previous version and a non-zero error code is returned to OMS.


Oracle

Before patching BRM prepaid components• Apply the mandatory patch 6512039 for Oracle Enterprise Manager.

a. Download the mandatory Oracle Enterprise Manager patch 6512039 from http://metalink.oracle.com/ Web site.

b. Follow the instructions provided in the patch and apply the patch.

• Create a job to update BRM products list in Oracle Enterprise Manager. See Updating BRM products list in Enterprise Manager.

• Set up Oracle MetaLink credentials on the Patching setup page. See Specifying Patching Credentials in the Oracle Enterprise Manager online Help.

• (Optional) Set up and upload the customer configuration file. See Creating customer configuration files.

• Set up preferred credentials. See Setting up preferred credentials.

• (Optional) Create a patch source component. See Creating a patch source component.

Updating BRM products list in Enterprise Manager

To retrieve BRM patches from Metalink, Enterprise Manager needs to know about BRM product names. Your Enterprise Manager repository contains patch and release information that was current at the time Enterprise Manager was released. To update BRM products information in Enterprise Manager, you create a job to refresh the product information from Metalink.

To create a refresh job, follow these steps:

1. In Enterprise Manager Grid Control page, click on the Jobs tab.

2. In the Create job list box, select RefreshFromMetalink.

3. Click Go.

Create RefreshFromMetalink Job page appears.

4. In the General subtab, enter a name for the job in the Name field. For example, RefreshBRMProducts.

5. Click Save to Library.

6. Click the Job Library subtab.

7. Select the job created in step 4.

8. Click Submit.

9. Click Submit again.

If the job is created, the message ‘Job was created successfully’ is displayed at the top of the page.

10. Stop and restart Oracle Management Service.

11. In the Oracle Enterprise Manager Grid Control page, click on the Deployments tab.




13. Select Patch Oracle BRM Software

14. Click Run to invoke the patch deployment procedure.

15. Click Add in the BRM Software Updates section.

16. Verify Oracle Communications Applications appears in the Product Family list and Oracle Communications Billing and Revenue Management appears in the Product list.

Creating a patch source component

To apply a BRM patch in Oracle Enterprise Manager Grid Control, the patch must be available in Oracle Metalink or Oracle Software Library. If you have a patch that is not available in Metalink or Software Library, you will need to create a Software Update Component for the patch and upload the component to the Oracle Software Library. For example, if you have a patch downloaded on your machine, you will need to create a Software Update Component for the patch.

To create a Software Update Component, follow these steps:

1. In the Enterprise Manager Grid Control page, click on the Deployments tab.

2. In the Deployments page, scroll to the Patching section and click the View Patch Cache link.

The Patch Cache page appears.


Oracle

3. Click Upload Patch File.

4. Enter the patch filename in the Patch File box or click Browse to locate the patch zip file.

Note For Linux, the Patch File name should be in the format:p<patch_number>_7.3.1_226.

5. Enter the patch attributes information in the Patch Attributes section.

a. In the Patch Number box, enter the patch number.b. In the Patch Type box, enter “patch”.c. In the Description box, enter a description. d. In the Product Family box, enter “Oracle Communications

Applications”.e. In the Product box, enter “Oracle Communications Billing & Revenue

Management”.f. In the Release box, enter “7.3.1”.g. In the Platform box, enter the platform. For example, Linux x86-64.h. In the Language box, enter “American English”.i. In the Comments box, enter a comment.

6. Select Create Oracle Software Update Component checkbox.

7. Click Upload.


After the upload is complete, the Software Update Component should be listed under OracleSoftwareUpdates on the Components page under the Provisioning subtab.

Patching BRM prepaid components

To patch BRM components:

1. In the Enterprise Manager Grid Control page, click the Deployments tab.



3. Select Patch Oracle BRM Software.

4. Click Run to invoke the patching deployment procedure.

The Software Updates page appears.

5. In the BRM Software Updates section, click Add.

Note You can only apply one patch at a time.


Oracle

6. In the Search And Select Software Updates page, select Search MetaLink or Search Software Library to locate the patch.

Note When you initially install a patch from Metalink, the patch is automatically added to the Software Library. The next time you want to apply the same patch, you can select the patch from the Software Library.


– If you know the patch number to search, enter the patch number in the Patch Number field and click Go.

– If you do not know the patch number, provide all of the following information:

a. In the Product Family field, select Oracle Communications Applications.

b. In the Product field, select Oracle Communications Billing and Revenue Management.

c. In the Release field, select the BRM release of the patch.d. In the Patch Type field, select All Patches.

e. In the Platform field, select the platform of the patch.f. In the Language field, select American English.

Note You must specify the release, platform, and language search criteria for Oracle Enterprise Manager to locate the patch.

8. (Optional) In the Source section, select the customer configuration file to be used for the patch installation.

9. Click Go.

Oracle Enterprise Manager displays the list of patches that are applicable based on your search criteria.

10. Click the check box of the patch that you want to apply and click Select.

Important Before installing a patch, read the patch Readme file for information about the BRM release level and any prerequisite patch or patches that must be installed prior to applying the patch that you have selected.

11. Click Next.


12. Click Add.

13. In the Select Target page, specify the target type and platform and click Go.

14. Select the check boxes of the target hosts on which to apply the patch.

15. Click Select.

16. Click Next.




all hosts.





19. Click Next.




To start the patching deployment procedure immediately:


If you select End After Grace Period, enter the length of time for Oracle Enterprise Manager to attempt to run the procedure.

To start the patching deployment procedure at a later time:





21. Click Next.



23. Click Finish to start the patching deployment procedure.




c. Click Patch Oracle BRM Software link. The progress details are displayed under the Status Details section.

When the BRM patching deployment procedure finishes, the Deployment Procedure Manager screen is appears with the following details:

– Deployment procedure name - Patch Oracle BRM Software


– Procedure name - Patch Oracle BRM Software

– Type - Patch Oracle BRM Software


Oracle


– Last updated - Date and time when the BRM deployment patch procedure was completed.

To verify the patch has been applied successfully, run the following command on the agent machines where the patch was installed:

On Linux:

rpm -qa --root install_loc --dbpath install_loc/rpm_db

On HPIA:

rpm -qa --dbpath install_loc/rpm_db

where

install_loc is the install location of the component that is patched.

The patch deployment procedure logs all the activity in the file patchRouter.log in the staging location of the component that is patched. If the procedure fails to apply the patch or install the optional manager, check the log file for the reason for the failure.

Rollback of BRM software patch installationYou roll back a BRM software patch to a previous patch version by running the BRM rollback deployment procedure from the Oracle Enterprise Manager Grid Control console.

Note You can perform a roll back only if a patch has been applied previously. If there are no patches applied then an error message is displayed to indicate that a backup file does not exist. Also, you can only roll back to the last patch version. For example, if patch 1, patch 2, and patch 3 are applied on your system, you can only roll back patch 3.

The following is a high-level description of the steps that are executed by the BRM rollback deployment procedure:

1. Stops the BRM services.

2. Restores BRM to the previous patch level. The system retrieves configuration information from the Oracle Management Repository and applies the patch serially on different hosts in rolling fashion using the ZDU logic.

3. Generates the new configuration file.

4. Starts the BRM service.

5. Verifies that the service is running. If the service failed to start, the patch is rolled back to the previous version and a non-zero error code is returned to OMS.


Rollback of a BRM software patch

To roll back a BRM software patch:

1. In the Enterprise Manager Grid Control page, click the Deployments tab.



3. Select Rollback BRM Software Patch.

4. Click Run to invoke the rollback deployment procedure.


Note The rollback procedure will roll back only the last BRM software patch that was installed on the target host machine.

5. Click Add.

6. In the Select Target page, specify target type and platform and click Go.

Note It is recommended that you perform roll back for one component at a time. For example, if you select BRM Connection Manager target type, you should not attempt to roll back patch for RTP or TIMOS DM in the same attempt.

7. Select the check boxes of the target hosts on which to roll back the BRM software patch.

8. Click Select.

9. Click Next.




all hosts.




12. Click Next.





Oracle

To roll back the patch immediately:


If you select End After Grace Period, enter the length of time for Oracle Enterprise Manager to attempt to run the procedure.

To roll back the patch at a later time:





14. Click Next.



16. Click Finish to start the rollback deployment procedure.




c. Select Rollback BRM Software Patch link. The progress details are displayed under the Status Details sectoin.

When the BRM rollback deployment procedure finishes, the Deployment Procedure Manager screen is displayed with the following details:

– Deployment procedure name - Rollback BRM Software Patch


– Procedure name - Rolback BRM Software Patch

– Type - Rollback BRM Software Patch


– Last updated - Date and time when the BRM deployment patch procedure was completed.


To verify the patch has been rolled back successfully, run the following command on the agent machines where the patch was installed:

On Linux:

rpm -qa --root install_loc --dbpath install_loc/rpm_db

On HPIA:

rpm -qa --dbpath install_loc/rpm_db

where

install_loc is the install location of the component that is rolled back.

The rollback deployment procedure logs all the activity in rollback.log file in the staging location of the target componet that is rolled back. If the procedure fails to rollback the patch, check the log file for the reason for the failure.

Adding your custom code to a high-availability systemNote To add custom code to a high-availabiltiy system, you must perform the

initial installation of the BRM prepaid component. See Deploying BRM prepaid components.

To add custom code to a high-availability system:

1. Merge your custom code into an existing BRM RPM package. See Adding custom code to a BRM RPM package.

2. Upload this package to the Oracle Software Library by creating a source component in the Software Library. See Creating BRM source components in the Software Library.

3. Use the Oracle Enterprise Manager Grid Control console to deploy the package similar to deploying BRM optional managers by using the BRM patching deployment procedure. See Deploying BRM Optional Managers.

Adding custom code to a BRM RPM package

To merge your custom code into a BRM RPM package:

1. Install RPM if you have not already done so. See Installing the RPM software.

2. Set your RPM path to /opt/TWWfsw/bin.

Note For C shell, use:

setenv PATH ${PATH}:rpm path

3. Set your RPM target_path to a local disk drive.

Important target_path is the directory where you want your RPM package installed. Make sure you have write permission in this directory.

4. Copy the Agent_home/sysman/admin/scripts/brm/portal_rpmrc file to rpmrc.


Oracle

5. Change this line of the rpmrc file to reflect the location of your cust_macro file:

Macrofiles: cust_macro_file_location

6. Create a cust_macro file in a working directory. The file must contain these two lines:

%_rpmdir target_path%_provides /bin/sh

where target_path is the location of your new RPM file.

7. Create an rpmrc file for your component based on portal_rpmrc sample file provided. Change the following line to location of the cust_macro file.

Macrofiles: cust_macro_file_location

8. (Optional) If you are creating a new RPM package, create an rpm.spec file in your working directory with the following information:

Prefix: /BuildRoot: directory_being_packagedSummary: your_package_summaryName: your_package_name%define version arbitrary_number.your_package_number%define _unpackaged_files_terminate_build 0%define _missing_doc_files_terminate_build 0Version: %{version}Release: your_release_number Group: ApplicationsVendor: your_nameCopyright: your_copyright_statementURL: your_URLPackager: your_packager_name < packager, eg. [email protected]>Provides: < what this package depend on that’s provided by the env but not provided via RPM, eg. /bin/sh /bin/csh>Requires: your_package_name%descriptionyour_component_description%files%defattr(-, pin, pin)%{prefix} # use this line if you want to automatically package all files# under BuildRoot, otherwise use the next line fomat to list # the required files individually%{prefix}/path/file


# use this format to list all the files# under BuildRoot where path is relative to BuildRoot# one line per file.

where

directory_being_packaged specifies the directory containing all the files your custom component requires.

your_package_summary is a short description of this version of your package.

your_package_name is the name of the package you are creating.

If you are replacing an existing BRM software package, be sure to use the same name.

arbitrary_number.your_package_number defines your version number. You create a version number to keep track of your custom software versions.

– arbitrary_number can be any positive, non-punctuated number because it is overwritten during installation.

– your_package_number is displayed in the RPM package header.

your_package_number must be a positive non-punctuated number that does not conflict with the BRM version numbers. BRM has reserved the numbers under 10000. Use a version number larger than 10000.

your_release_number is a release number that you use for your custom component.

BRM_release_number is the number of the current BRM release; for example, 7.3.1

your_name is the name of your organization.

your_copyright_statement is the legal statement that protects your intellectual property.

your_URL is a URL that you can direct your customers to for more information or help.

your_packager_name is the name of the packaging software that you use to create your custom component.

your_component_description is the description of your custom component. This is displayed in the RPM package header.

9. Create the rpm.spec file for creating the RPM packages.

rpmbuild -bb --rcfile rpmrc_include_path rpm.spec_include_path

where

rpmrc_include_path - specifies your rpmrc file. Include the path to the file if it's not located in the current directory.

rpm.spec_include_path - specifies your rpm.spec file. Include the path to the file if it's not located in the current directory.

10. Confirm that the new package is created in the target_path directory.

11. Change directory to /tools.


Oracle

12. Merge your new RPM package into the Portal_Base package using the pin_repackage.sh utility:

pin_repackage.sh Portal_pkg.rpm pkg_changes.rpm >& pin_repackage.log

For example:

pin_repackage.sh PortalBase-7.3.1-11.0.sparc64.rpm CUST-7.3-1.10001.sparc64.rpm >&pin_repackage.log

For more information on using pin_repackage.sh, see pin_repackage.sh in the BRM documentation.


Application Management Pack for BRM · Application Management Pack for BRM 1 Application Management...

Documents

Transcript of Application Management Pack for BRM · Application Management Pack for BRM 1 Application Management...