brm application management pack · † brm system architecture in the brm documentation. † brm...

BRM Application Management PackUser Guide

Oracle® CommunicationsBilling and Revenue Management 7.4

April 2010

Oracle Communications Billing and Revenue Management 7.4

Revision Date: April 2010

Copyright © 1999-2010, Oracle. All rights reserved. PORTAL, the PORTAL LOGO, CONTENT CONNECTOR, INTEGRATE, and INTERCONNECT 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

1. BRM Application Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About the BRM Application Management Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Operating system versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Database servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Operating system versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Database servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Operating system versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Database servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

HP-UX IA64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Operating system versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Database servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Hardware requirement for the Management Service plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . 8Hardware requirement for the Management Agent plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . 9Disk space required by BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Before installing the BRM Application Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Accessing the Oracle Enterprise Manager Grid Control console. . . . . . . . . . . . . . . . 10Creating the Oracle Software Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Downloading the BRM Application Management Pack . . . . . . . . . . . . . . . . . . . . . . . 10

Installing the BRM Application Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Installing the Management Service Plug-in by Using Oracle Universal Installer . . 12Installing the Management Service Plug-in by Using a silent install . . . . . . . . . . . . 13Installing the Management Agent Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Installing the Management Agent Plug-in by Using Oracle Universal Installer . . . 15Installing the Management Agent Plug-in by Using Enterprise Manager Grid Control16Installing the Management Agent Plug-in by Using a silent install . . . . . . . . . . . . . 18About log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2. Using the Oracle Enterprise Manager Grid Control . . . . . . . . . . . . . . . . . . . . . . 21About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Using the BRM Application Management Pack to administer your BRM system . . . . . . . . 21About the Oracle Enterprise Manager Grid Control Home page . . . . . . . . . . . . . . . . . . . . . . 22Deploying BRM components Using Enterprise Manager Grid Control . . . . . . . . . . . . . . . . . 23

BRM ISMP packages, installable, and base components. . . . . . . . . . . . . . . . . . . . . . . 24Before deploying BRM components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Creating BRM source components in the Oracle Software Library . . . . . . 28Uploading BRM source components using the utility . . . . . . . . . . . . . . . . . 30

Adding the BRM subtab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Contents iii

Oracle Corporation

Setting up preferred credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Modifying the default configuration values for a BRM component. . . . . . 33

Installing the Third-Party software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Installing the SNMP software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Deploying BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Diagnosing deployment procedure failures . . . . . . . . . . . . . . . . . . . . . . . . . . 43Deploying BRM components with database creation . . . . . . . . . . . . . . . . . . 44Deploying BRM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Deploying BRM Base components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Modifying Oracle DM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

About zero down time upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Patching BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Before patching BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Updating the BRM products list in Enterprise Manager . . . . . . . . . . . . . . . 51Creating a patch source component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Patching BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Uninstalling BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Uninstalling (rolling back) BRM software updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Rolling back BRM software patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61About Monitoring BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

About monitoring system performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64About alerts and notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65About BRM metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66About BRM reports and graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68About BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Monitoring and managing BRM components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Adding BRM components using guided discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . 71Adding SNMP components using guided discovery . . . . . . . . . . . . . . . . . . . . . . . . . 73How BRM log files are monitored for errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Monitoring BRM component performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Viewing BRM component metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Monitoring component performance history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Monitoring BRM component configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75About monitoring component configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Viewing component configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Modifying component configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Rebalancing CM connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Updating the DMO farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Monitoring alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuring alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuring the collection schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Adding corrective actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Viewing alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Managing BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Viewing BRM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Starting, stopping, or restarting individual BRM components . . . . . . . . . . . . . . . . . 82

iv BRM Application Management Pack

Starting, stopping, or restarting selected BRM components . . . . . . . . . . . . . . . . . . . 83Loading events into the BRM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Removing a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Viewing the list of patches that have been applied to a component . . . . . . . . . . . . . 84

Managing BRM groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Creating BRM groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Monitoring BRM groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Uninstalling the BRM Application Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Removing components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Uninstalling the Management Service Plug-in by Using Oracle Universal Installer 86

Performing a Silent Uninstallation of the Management Service Plug-in . . 86Uninstalling the Management Agent Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Using Enterprise Manager Grid Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Performing a Silent Uninstallation of the Management Agent Plug-in . . . 88

3. Using the command line interface to run deployment procedures . . . . . . . . . 91About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Enterprise Manager command line interface requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Executing the deployment procedure using the Enterprise Manager command line interface 92

4. Setting up a new BRM instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97About setting up a new BRM instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Setting up a new BRM instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Configuring BRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Starting BRM components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

5. BRM Plug-in Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101About BRM plug-in pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

BRM page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Oracle BRM Suite System page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Oracle BRM Suite System (Components tab) . . . . . . . . . . . . . . . . . . . . . . . . . 105Oracle BRM Suite Service page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Oracle BRM Suite page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Oracle BRM Suite page (Members tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Oracle BRM component home page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Host’s home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

6. BRM error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115About BRM codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115BRM error codes monitored by Oracle Enterprise Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Contents v

Oracle Corporation

vi BRM Application Management Pack

BRM Application Management Pack 1

About this documentThis chapter provides an overview of the Oracle Communications Billing and Revenue Management (BRM) Application Management Pack and how to use it to deploy 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.

About the BRM Application Management PackThe BRM Application Management Pack is an add-on module for Oracle Enterprise Manager Grid Control.

Enterprise Manager Grid Control provides a wide range of functionalities that allow system administrators to install, configure, administer, and monitor their environment. 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.

The BRM Application Management Pack is developed using the Enterprise Manager framework and extends Enterprise Manager Grid Control to add support for BRM system administration. You can use the Enterprise Manager Grid Control console to:

• Deploy BRM components.

• Modify the configuration of BRM components.

• Apply or roll back BRM software patches.

• Uninstall BRM components.

• Manage and monitor BRM components.

• Discover and monitor a pre-installed BRM component.

The BRM Application Management Pack consists of the following plug-ins:

• The Oracle Management Service plug-in is installed on the Management Service and the Management Repository in the location where Oracle Enterprise Manager Grid Control 10gRelease5 is installed. The Management Service plug-in includes scripts related to deployment procedures, UI and API jar files, default configuration XML templates the Data Definition Language (DDL) to create related tables, indexes, stored procedures, sequences, and triggers on the Management Repository.


Oracle Corporation

• The Oracle Management Agent plug-in is installed on each Management Agent in the location where the Oracle Enterprise Manager 10gRelease5 Agent is installed. The Management Agent plug-in includes the BRM target definition files, metric definition files, Perl scripts, and Java classes.

Installing your BRM Application Management Pack includes these steps:

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

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

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

• Install the BRM Application Management Pack. See Installing the BRM Application Management Pack.

Hardware and software requirementsThis section describes the hardware and software requirements for the BRM installation for Oracle Enterprise Manager Grid Control. The BRM Application Management Pack is currently supported on Oracle Enterprise Manager Grid Control 10gRelease5 database on Solaris, AIX, HP-UX IA64, and Linux platforms.

Solaris

This section describes the primary software components compatible with a Solaris implementation.

Operating system versions

The following table shows operating system compatibility for servers and clients:

Operating system Notes

Solaris 9 (32-Bit) Patches:

• 111722-04 (libms, lmsx, libm)

• 111711-08 (libC)

• 111712-08 (libCx)

• 111703-03 (fix for /usr/ccs/bin/sccs and make).

Required patches for Daylight Savings Time (DST) change in 2007:

• 112233-11

• 112335-03

• 112874-33 (libc)

Solaris 9 (64-Bit)

2 BRM Application Management Pack

Database servers

The following table shows compatible database servers:

Solaris 10 (32-Bit) Required patches for Daylight Savings Time (DST) change in 2007:

• 119254-06

• 122032-02

• 119689-07 (libc)

Solaris 10 (64-Bit)

Database server version Notes

Oracle9i Database Release 2 (Oracle 9.2.0.8 and later patch levels)

(Enterprise Edition only)

Supported on Solaris 32-bit and Solaris 64-bit.

To partition your BRM database, you must use the Oracle Partitioning component. You must purchase a separate license for this component from Oracle.

BRM supports the UTF8 character set on Oracle.

Oracle 10g Database Release 2 is required if you are using TIMOS.

Oracle 10g Database Release 2(Oracle 10.2.0.1 and later patch levels)


Oracle Real Application Clusters 10g

Use Oracle Real Application Clusters 10g for high availability configurations only. For scalability, use a multidatabase system. See A BRM multidatabase production system in the BRM documentation.




Oracle Corporation

AIX

This section describes the primary software components compatible with an AIX implementation.


The following table shows operating system compatibility for servers and clients.

Database servers


Oracle 11g Database(Oracle 11.1.0.6 and later patch levels)


• Solaris 9 Update 7 or later

• Solaris 10


• Solaris 9 Update 7 or later

• Solaris 10


IBM AIX Version 5.3

IBM AIX Version 6.1




Supported on AIX 5.3.








Linux

This section describes the primary software components compatible with a Linux implementation.










Oracle Enterprise Linux 4.5, AS release 4 (October Update 5) and higher 4.x updates

Red Hat Enterprise Linux, (RHEL4.5), AS release 4 (Nahant Update 5) and higher 4.x updates

Oracle Enterprise Linux 5 and higher 5.x updates

RHEL5 and higher 5.x updates



Oracle Corporation

Database servers


HP-UX IA64

This section describes the primary software components compatible with a HP-UX IA64 implementation.






Supported on Oracle Enterprise Linux 4.5 and Oracle Enterprise Linux 5.













Database servers



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

Required patches:

• PHSS_34040 11.23 linker + fdp cumulative patch

• PHSS_34885 C Compiler

• PHSS_34856 aC++ Compiler (A.06.12)

• PHSS_35055 aC++ patch

• PHCO_34599 lib (c ) cumulative patch

• PHCO_34669 for Daylight Savings Time (DST)

• PHCO_36098 tztab cumulative patch

HP-UX IA64 11i Version 3 (B.11.31)




Supported on 64-bit HP-UX IA64 only.







Oracle Corporation

Hardware requirement for the Management Service plug-inThe following table lists the approximate amount of disk space required to install the Management Service plug-in on the Management Service system. The size estimates include 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.

Important When the amount of disk space used on the EMD file system exceeds the configured value for UploadMaxDiskUsedPct in the emd.properties file, the data collection will be disabled. To enable data collection, you must clean up the file system and upload the agent.







Operating system Total disk space required (MB)

Solaris 200

AIX 175

HP-UX IA64 150

Linux 157

Note The Oracle Management Service is supported on 64-bit versions of the operating systems.



Hardware requirement for the Management Agent plug-inThe following table lists the approximate amount of disk space required to install the Management Agent plug-in on the agent system. The size estimates include the space required by third-party software.

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

The amount of disk space required by BRM components during installation is approximately 650 MB.

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 BRM Application Management PackBefore you install the BRM Application Management Pack, you must install and configure the following:

• Oracle Enterprise Manager Grid Control 10gRelease5.

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

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

• The Oracle Management Agent 10gRelease5 on each of the target hosts where you plan to install BRM components.

Important The minimum version of the Management Agent required to install BRM components is 10gRelease5.

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 the TNS_ADMIN environment variable is set to the location of the tnsnames.ora file and that the ORACLE_SID environment variable is set to the database alias on the Agent machine. Otherwise, deploying 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.

Operating system Total disk space required (MB)

Solaris 200

AIX 175

Linux 367

HP-UX IA64 199


Oracle Corporation

Accessing the Oracle Enterprise Manager Grid Control console

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

https://OMS_hostname.domain:port/em

where:

• OMS_hostname is the host on which Oracle’s Management Service is installed.

• domain is the network domain on which you install your Oracle’s Management Service.

• port is the console port.

Creating the Oracle Software Library

The Oracle Software Library maintains versions of the software executables and acts as a repository for the software components that may be deployed to your servers. During the installation of the BRM Application Management Pack, the install scripts are copied to the Oracle Software Library.

To create the Oracle Software Library:

1. From the Oracle Enterprise Manager Grid Control console, 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 the location.

For example, /oracle/OracleHomes/swlib.

Downloading the BRM Application Management Pack

To download the BRM Application Management Pack:

1. Go to the Oracle E-Delivery Web site (https://edelivery.oracle.com).

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

The Media Pack Search page appears.

3. From the Select a Product Pack list, select Oracle Enterprise Manager.

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. Go to temp_dir and unzip the downloaded package:

unzip package-name.zip

where package-name is the name of the BRM Application Management Pack.

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

temp_dir/

em/

Disk1/

install/

runInstaller

Installing the BRM Application Management PackThis installation uses the Oracle Universal Installer, a graphical Java-based application.

To use the Oracle Universal Installer, install a GUI application such as X Windows and set the DISPLAY environment variable.

Important The BRM Application Management Pack is certified for Oracle Enterprise Manager 10gRelease5. It will not install with an earlier version of Oracle Enterprise Manager.

You must install the Management Service and Management Agent plug-ins. There are two options for installing the Management Service plug-in:

• You can install the Management Service plug-in using the Oracle Universal Installer. The Universal Installer enables you to install the plug-in on a single machine at a time. To install the plug-in on multiple machines, you have to run the Universal Installer install procedure multiple times. See Installing the Management Service Plug-in by Using Oracle Universal Installer.

• You can also perform silent installations to install service components. See Installing the Management Service Plug-in by Using a silent install.

Note

• To reinstall the BRM Application Management Pack, you must follow the same installation process given below.

• You do not need to stop the Management Service or Management Agent during the installation or reinstallation process.


Oracle Corporation

Installing the Management Service Plug-in by Using Oracle Universal Installer

To install the Management Service plug-in:

1. Go to temp_dir/em/Disk1/install and enter the following command:

./runInstaller -invPtrLoc OMS_home/oraInst.loc

where OMS_home is the directory where the Management Service is installed.

-invPtrLoc specifies the location of the product inventory. If you do not specify -invPtrLoc, the inventory in the OMS_home is updated.

The Oracle Universal Installer Welcome screen appears.

2. Click Next.

The Select Installation Type screen appears.

3. Select OMS and click Next.

The Specify Home Details screen appears.

4. From the Name list, select the Management Service name.

5. From the Path list, select the Management Service location.

Important You must select the location where the Management Service is installed. If the Management Service is not installed in the specified location, the Universal Installer displays an error message.

Tip When you select the Management Service name, the Universal Installer automatically populates the Path list. Similarly, when you select the Path, it automatically populates the Name list.

6. Click Next.

The Database Credentials screen appears.

7. Enter the database credentials needed by the Management Service 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.


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

The Install screen appears and displays the installation steps being processed 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 processed automatically to perform post-installation configurations, such as running SQL scripts 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.

Note If the configuration assistants fail, the installer displays a message to check the log file. The log file provides the details of how to run the script from the command line.

9. Click Installed Products.

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

10. Click Exit.

Installing the Management Service Plug-in by Using a silent install

A silent installation uses a response file to provide the necessary installation information.

To perform a silent installation of the Management Service plug-in:

1. Go to temp_dir/Disk/stage/Response.

2. Make a copy of the oracle.sysman.plugin.comms.brm.managementpack.OMS.rsp file.

3. Open the oracle.sysman.plugin.comms.brm.managementpack.OMS.rsp file in a text editor.

4. Find the ORACLE_HOME entry and set it to the name of the path where the Management Service is installed.

For example:

ORACLE_HOME = "/home/oracle/OracleHomes/oms10g"

5. Find the ORACLE_HOME_NAME entry and set it to the name of the directory where the Management Service is installed.

For example:

ORACLE_HOME_NAME = "oms10g"


Oracle Corporation

6. Find the ORACLE_HOST_NAME entry and set it to the name of the host where the Management Service is installed.

For example:

ORACLE_HOST_NAME = "localhost"

7. Find the db_usr entry and set it to the Enterprise Manager repository database related values.

For example:

db_usr = {"emrep.us.oracle.com","sysman","hello","localhost","1521","emrep"}

8. Save and close the file.


./runInstaller -invPtrLoc /home/oracle/OracleHomes/oms10g/oraInst.loc -responseFile response_file_name -silent

where response_file_name is the name of the response file along with the complete path.

For example:

./runInstaller -invPtrLoc /home/oracle/OracleHomes/oms10g/oraInst.loc -responseFile "/home/oracle/response_files/oracle.sysman.plugin.comms.brm.managementpack.OMS.rsp" -silent

Installing the Management Agent Plug-in

Important The BRM Application Management Pack is certified for Oracle Enterprise Manager 10gRelease5. It will not install with an earlier version of Oracle Enterprise Manager.

There are three options for installing the Oracle Management Agent plug-in:

• You can install the Management Agent plug-in using the Oracle Universal Installer. The Universal Installer enables you to install the Management Agent plug-in on a single agent machine at a time. To install the Management Agent plug-in on multiple agent machines, you have to run the Universal Installer install procedure multiple times. See Installing the Management Agent Plug-in by Using Oracle Universal Installer.

• You can install the Management Agent plug-in from Enterprise Manager Grid Control. Enterprise Manager Grid Control enables you to install the Management Agent plug-in on multiple agent machines at the same time. See Installing the Management Agent Plug-in by Using Enterprise Manager Grid Control.

• You can install the Management Agent plug-in using the silent installation method. See Installing the Management Agent Plug-in by Using a silent install.


Note If the Agent user and BRM user are different, they must belong to the same group. Also, in the .profile file of the Agent and BRM users, set the following:

umask = 002

Installing the Management Agent Plug-in by Using Oracle Universal Installer

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

To install the Management Agent plug-in:

1. Go to temp_dir/em/Disk1/install and enter the command:

./runInstaller -invPtrLoc Agent_home/oraInst.loc

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


2. Click Next.

The Select Installation Type screen appears.

3. Select Agent, and click Next.

The Specify Home Details screen appears.

4. From the Name list, select the Management Agent name.

5. From the Path list, select the Management Agent location.

Important You must select the location where the Management Agent is installed. If the Management Agent is not installed in the specified location, the Universal Installer displays an error message.

Tip When you select a Name for the Management Agent, the Universal Installer automatically populates the Path list. Similarly, when you select the Path, it automatically populates the Name list.

6. Click Next.

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


Oracle Corporation

7. Verify the information you entered is correct and click Install.

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

When the installation is complete, the Configuration Assistants screen appears. This screen displays the recommended configuration script that is processed 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.

Note If the configuration assistants fail, the installer displays a message to check the log file. The log file provides the details of how to run the script from the command line.


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

9. Click Exit.

Installing the Management Agent Plug-in by Using Enterprise Manager Grid Control

To stage and deploy the Management Agent plug-in to one or more hosts, first you have to manually upload the agent software as a patch to the patch cache. After the software has been added to the patch cache, you can stage the patch on any host where the Management Agent is running and then run the patch to install the agent plug-in. You can install the plug-in on multiple agents at a time from the Enterprise Manager Grid Control console.

To install the Management Agent plug-in:


The Deployments page appears.

2. Scroll down to the Patching section and click the View/Upload Patch link.

The Patch Cache page appears.

3. Select the button next to the patch number and click the Patch button.

The Patch: Select Destination page appears.

4. From the Available Target section, select the component.

5. Click the Move button.

The component moves to the Selected Target section.

6. Click Next.

The Patch: Set Credentials page appears.


7. Select Override Oracle Home Preferred Credentials, to override the preferred credentials.

8. Do one of the following:

– From the Specify Credentials For list select Each Home, to specify a user name and password for each home.

a. Enter the new administrator Username.

b. Enter the new administrator Password.

Note You must perform the above steps for each component.– From the Specify Credentials For list select All Homes, to specify a

single user name and password to be used for all homes.


b. Enter the new administrator Password.c. Re-enter the new administrator Password.

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

9. (Optional) Click the check box below Save Oracle Home Credentials.

10. Click Next.

The Patch: Stage or Apply page appears.

11. Select the Apply button and enter the necessary details in the section below.

12. Click Next.

The Patch: My Oracle Support Details page appears.

13. (Optional) Enter the necessary details.

14. Click Next.

The Patch: Schedule page appears.

15. In the Schedule Patch Job section, specify whether to start the patch job immediately or at a later time, then click Next.

The Patch: Summary page appears.

16. Review the patch and Oracle Home information. To make any changes to the information displayed, click the Back button to go to the previous pages and make the changes.

17. Click Finish.

The Confirmation page appears showing that the patch job has been submitted.

You can click View Job to view the status of the job. To view the status of the tasks in the job, click Expand All link. To view the task log files, right-click on the task link and select Open in New Window to view the log.

Note If the patching fails with Initialization error, repeat the instructions from 1 through 17 and do the following:

a. Select the Staged Location check box.

b. Enter %emd_root%/EMStagedPatches/patch_number


Oracle Corporation

where patch_number is the patch number that you entered earlier.

c. Click Next.d. Click Finish.

Installing the Management Agent Plug-in by Using a silent install

To perform a silent installtion of the Management Agent plug-in:


2. Make a copy of the oracle.sysman.plugin.comms.brm.managementpack.Agent.rsp file.

3. Open the oracle.sysman.plugin.comms.brm.managementpack.Agent.rsp file in a text editor.

4. Find the ORACLE_HOME entry and and set it to the path where the Management Agent is installed.

For example:

ORACLE_HOME = "/home/oracle/OracleHomes/agent10g"

5. Find the ORACLE_HOME_NAME entry and and set it to the name of the directory where the Management Agent is installed.

For example:

ORACLE_HOME_NAME = "agent10g"

6. Find the ORACLE_HOST_NAME entry and set it to the name of the host where the Management Agent is installed.

For example:



./runInstaller -invPtrLoc /home/oracle/OracleHomes/agent10g/oraInst.loc -responseFile response_file_name -silent


For example:

./runInstaller -invPtrLoc /home/oracle/OracleHomes/agent10g/oraInst.loc -responseFile "/home/oracle/response_files/oracle.sysman.plugin.comms.brm.managementpack.Agent.rsp" -silent


About log files

You can find the silent install session logs with the following file name format:

central_inventory_location/logs/silentInstallDate_Time.log

where

• central_inventory_location is the home directory for all the log directories

• Date_Time is the date and time at which the log file is created.

For example:

/home/oracle/oraInventory/logs/silentInstall2009-08-11_04-15-59PM.log


Oracle Corporation


Using the Oracle Enterprise Manager Grid Control 2

About this documentThis chapter explains how you can deploy, discover, monitor, manage, and uninstall BRM components using the Oracle Enterprise Manager Grid Control.

Using the BRM Application Management Pack to administer your BRM system

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

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

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

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

• The Oracle Management Repository, which resides in an Oracle database and contains objects such as packages and procedures and all information pertaining to the managed components within Enterprise Manager Grid Control. Information stored in the Management Repository is retrieved by Oracle’s Management Service and displayed in the Enterprise Manager Grid Control console.

For more information about Oracle Enterprise Manager Grid Control components, see the discussion of the overview on Enterprise Manager components in the Oracle Enterprise Manager online Help.


Oracle Corporation

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

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

The Home tab on the Oracle Enterprise Manager Grid Control console provides information that helps you assess the health of all the components 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 page displays an overview of all the components and also allows you to have an overview of specific components. It also displays high-level information on alerts, policy violations, jobs executed, security policy violations, and so on. You can also view a summary of the hardware, operating system, database installation, and application server installation deployments.


For more information, see the Oracle Enterprise Manager online Help.

Deploying BRM components Using Enterprise Manager Grid ControlTo deploy BRM components, you run the BRM deployment procedure from the Oracle Enterprise Manager Grid Control console. The BRM deployment procedure is developed using the Enterprise Manager provisioning framework and extends Enterprise Manager Grid Control to add support for deploying BRM components.

The BRM deployment procedure uses BRM InstallShield MultiPlatform (ISMP) packages to install BRM components. For example, for BRM 7.4 release, it uses 7.4_Portal_Base_linux_32_opt.bin for Portal base and 7.4_Pipeline_linux_64_opt.bin for Pipeline Manager on the Linux platform.

To deploy BRM components using the Enterprise Manager Grid Control feature, you must first create BRM source components in Oracle Enterprise Manager using the BRM ISMP packages. See Creating BRM source components in the Oracle Software Library.

In some cases, you would use the same BRM ISMP package to deploy multiple BRM components. For example, Connection Manager (CM), CMMP, DM_Oracle, Formatter, and BRM applications can be deployed using the BRM PortalBase ISMP package. For a list of the BRM ISMP packages and the installable components, see BRM ISMP packages, installable, and base components.

Important You cannot deploy an already existing component. For example, if you deployed a CM using the BRM ISMP installer, you cannot install another CM component using the Enterprise Manager Grid Control as Enterprise Manager cannot access the vpd.properties file of a pre-installed environment.


Oracle Corporation

Optional managers are deployed on top of the BRM Base component. For example, the Diameter Manager optional manager would be deployed over the AAA Gateway Manager base component. For a list of BRM Base components for optional managers, see BRM ISMP packages, installable, and base components.

When you deploy BRM components, you must provide configuration details that are needed to configure and start up the BRM process. During deployment, the deployment User Interface (UI) reads a default configuration file and displays default values for all mandatory parameters and for some optional parameters. The optional manager inherits the mandatory parameters from the base component. You can change the configuration by doing the following:

• Edit the values of the mandatory or additional parameters.

• Add or delete additional parameters.

Note

• You cannot add or delete any mandatory configuration parameters.

• You cannot add additional configuration parameters for BRM Base, Third-Party, and SNMP components.

Additionally, you have the option to save your configuration as the default. The deployment UI saves your configuration to the default configuration file of the respective component. You can reuse this configuration when you deploy another component.

For more information about modifying the default configuration values, see Modifying the default configuration values for a BRM component.

BRM ISMP packages, installable, and base components

The table lists the following:

• BRM ISMP packages

• Installable components

• Source component name format

The source component name is in the format ISMPpackage_release_OS, where:

– ISMPpackage specifies the BRM ISMP package.

– release specifies the BRM release.

– OS specifies the operating system.

For example, the source component name for BRM 7.4 AAA_Gateway ISMP package for Linux operating system would be AAAGateway_7.4_Linux.


• Base component for optional managers

You can deploy optional managers on top of a Base component.

BRM ISMP package Installable componentsSource component

name formatBase component

AAA_Gateway AAA Gateway AAA_Gateway_release_OS

AccountSynchTool • Account Synchronization CM

• Account Synchronization DM

AccountSynchTool_release_OS

oracle_brm_cm

BRM Base • Batch Controller

• CM Proxy

• CMMP

• Connection Manager

• Email Data Manager

• Formatter

• Invoice Data Manager

• Oracle Data Manager

• BRM Applications (Device Management, Load notification event, Load price list, Pin A/R taxes, Pin balance transfer, Pin billed, Pin bill handler, Pin bulk adjust, Pin export price, Pin invoice, Pin monitor, Pin ood handler, Pin rate change, Pin remit, Pin rerate, Pin subscription, Pin trial bill, Pin unlock service Invoicing, Misc, Pin_cfg_bpdump, SOX_Unlock, Subscription, Testnap, UEL, GL_Export, Diagnostics, Infranet Manager CLI, Infranet Manager, Node Manager, Export_price, Credit_Control Billing, Account Dump Utility, Development_Files)

PortalBase_release_OS

BRM_Services_Framework_Mgr_AAA

BRM Services Framework Manager AAA

BRMServicesFrameworkMgrAAA_release_OS

oracle_brm_cm

BRM_Services_Framework_Mgr

BRM Services Framework Manager

BRM_Services_Framework_Mgr_release_OS

oracle_brm_cm

CIBERRoaming CIBER Roaming CIBERRoaming_release_OS

oracle_brm_pipeline

CollectionsMgr Collections Manager CollectionsMgr_release_OS

oracle_brm_cm


Oracle Corporation

ContentMgr Content Manager ContentMgr_release_OS oracle_brm_cm

Diameter Diameter Manager Diameter_release_OS oracle_brm_aaagw

EAI_FrameworkMgr • EAI Connection Manager (CM) module

• EAI Data Manager

• Payload Generator External Module

EAIFrameworkMgr_release_OS

oracle_brm_cm

EmailMgr Email Manager EmailMgr_release_OS oracle_brm_cm

GPRS_AAA_Mgr GPRS AAA Manager GPRSAAAMgr_release_OS

oracle_brm_cm

GPRS_Mgr_30 GPRS Manager 3.0 GPRSMgr_release_OS oracle_brm_cm

GSM_AAA_Mgr GSM AAA Manager GSMAAAMgr_release_OS

oracle_brm_cm

GSM_Mgr GSM Manager GSM_Mgr_release_OS oracle_brm_cm

HPOpenCall HP Open Call Manager HPOpenCall_release_OS

oracle_brm_aaagw

IPAddressMgr IP Address Manager IPAddressMgr_release_OS

oracle_brm_cm

Interconnect Interconnect Manager Interconnect_release_OS

oracle_brm_pipeline

InventoryMgr Inventory Manager InventoryMgr_release_OS

oracle_brm_cm

LDAPMgr LDAP Manager

Note LDAP Manager has a single component, LDAPMgr. The pin_channel_export component gets deployed as part of it.

LDAPMgr_release_OS

MultiDBMgr MultiDB Manager MultiDBMgr_release_OS

oracle_brm_cm

NumberMgr Number Manager NumberMgr_release_OS

oracle_brm_cm

PaymentechMgr Paymentech Manager PaymentechMgr_release_OS

Pipeline • BRE

• Real-Time Pipeline

Pipeline_release_OS

Pipeline_ConfMgr Pipeline Configuration Manager PipelineConfMgr_release_OS

oracle_brm_pipeline




Before deploying BRM components

Before you deploy BRM components, do the following:

RadiusMgr Radius Manager RadiusMgr_release_OS oracle_brm_cm

RatedEventLoader Rated Event Loader, Event Extraction Manager

REL_release_OS

ResourceResMgr Resource Reservation Manager ResourceResMgr_release_OS

oracle_brm_cm

RevAssuranceMgr Revenue Assurance Manager RevAssuranceMgr_release_OS

oracle_brm_cm

SIMMgr SIM Manager SIMMgr_release_OS oracle_brm_cm

SNMP_3rd_party_tool SNMP SNMP_release_OS

SuspenseMgr Suspense Manager SuspenseMgr_release_OS

oracle_brm_cm

TAPRoamingmanager TAP Roaming Manager TAPRoamingMgr_release_OS

oracle_brm_pipeline

ThirdParty ThirdParty Applications ThirdParty_release_OS

Timos Timos Data Manager Timos_release_OS

VertexMgr Vertex Manager VertexMgr_release_OS

VertexQuantumMgr Vertex Quantum Manager VertexQuantumMgr_release_OS

VoucherMgr Voucher Manager VoucherMgr_release_OS

oracle_brm_cm

WirelessSuite • GSM AAA Manager

• GSM Manager

• GPRS AAA Manager

• GPRS Manager

• Number Manager

• RRF Manager

• Services Framework Manager

• Services Framework AAA Manager

• SIM Manager

Note You cannot choose which features to install. They are all installed.

WirelessSuite_release_OS

oracle_brm_cm




Oracle Corporation

• You must first upload the BRM ISMP packages to the Oracle Software Library by creating source components. See Creating BRM source components in the Oracle Software Library.

• Upload the source components. See Uploading BRM source components using the utility.

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

• Ensure that the Third-Party software and SNMP software are installed in the Agent machines using the Deployment Procedure. See Installing the Third-Party software and Installing the SNMP software.

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.

– The SNMP master agent should be running on the Agent machine before a TIMOS installation. If multiple components are running on the same machine, only one master agent is required.

• (Optional) Copy the vpd.properties.componentname file to BRM_home

where componentname is the name of the BRM component that is deployed.

Note

– You must copy the vpd.properties.thirdparty file if you install the Third-Party software without using the Deployment Procedure.

– The componentname cannot have any spaces.

• If using an existing database:

– Ensure that the BRM schema has been initialized and corresponds to the version of the BRM ISMP files. For example, if this BRM database is used for TIMOS, the database should be initialized with the required TIMOS packages.

– Ensure that the tnsnames.ora file in all the Agent machines contains an entry for the BRM database and the file location is set in the TNS_ADMIN environment variable.

– Using SQLPlus, ensure that you are able to connect to the BRM database from the Agent machines.

Note You must specify the absolute path of the directory when you deploy or discover BRM components. You must not use symbolic links.

Creating BRM source components in the Oracle Software Library

The BRM Application Management Pack uses the BRM ISMP packages for deploying and patching of the BRM components. To deploy BRM components from Oracle Enterprise Manager Grid Control, you must first create BRM source components using the BRM ISMP packages, and upload the source components in Oracle Enterprise Manager.


To create BRM source components:

1. Download the BRM ISMP package that you want to install for your platform from the Oracle E-Delivery Web site (https://edelivery.oracle.com) to your Agent machine. For example, 7.4_Portal_Base_linux_32_opt.bin.

2. From the Oracle Enterprise Manager Grid Control console, click the Deployments tab, and then the Provisioning subtab.

The Provisioning page appears.

3. Click the Components subtab.

4. Select BRM Components and click Create Component.

The Create Component: Describe page appears.

5. From the Type list, select Generic Component.

6. In the Name field, enter the source component name.

Important You must enter the BRM source component name in the format ISMPPackage_release_OS.

where:

– ISMPPackage specifies the BRM ISMP package or the Third-Party package.



See BRM ISMP packages, installable, and base components.

7. In Description field, enter the description.

8. In the Product Name/Patch number field, enter BRM.

9. In the Product Version field, enter 2.0.

10. In the Vendor field, enter Oracle.

11. Click Next.

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

The Create Component: Upload File page appears.


– Select the Upload Later button, to upload the file at a later time.

– Select the Upload from Agent Machine button, to upload the file from the agent machine.

a. Click the Select Target button.

b. In the Search and Select: Targets page, select the target, and click the Select button.

a. Click the Select File button.

b. In the Browse and Select: File or Directory page, select the file, and click the Select button.


Oracle Corporation

– Select Upload from Local Machine, to upload the file from the local machine.

a. Click the Browse button.

b. Select the file and click Open.

14. Click Next.

The Create Component: Set Directives page appears.

15. Select Stage and click the Choose Directives button.

16. Select BRM Directives and click + to expand the list.

17. Select copy_file and click OK.

18. Click Next.

The Review page appears.

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

20. From the Enterprise Manager Grid Control console, click Deployments tab.

21. Click Provisioning subtab.

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

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

The status of the source components created should be Ready.

24. Repeat the above steps to create source components for all the BRM ISMP packages.

Uploading BRM source components using the utility

You can use the upload source components utility to automate the upload procedure. This utility uploads multiple BRM source components in Oracle Enterprise Manager.

Note You must use Perl to execute this utility.

To upload the BRM source components:

1. Go to OMS_home/sysman/admin/emdrep/sql/brm.

2. Copy the create_src_utility.tar file to the location where the BRM ISMP packages have been copied.

3. Untar the create_src_utility.tar file:

tar -xvf create_src_utility.tar

4. Open the upload_src.xml file in a text editor.


5. Make changes to the following:

HOSTSTRSIDDB_USERDB_PWD

6. Add component details for each source component that you want to upload in the following format:

<COMPONENT_DETAILS><DISPLAY_NAME>Component_release_OS</DISPLAY_NAME><DESCRIPTION>Component_release_OS</DESCRIPTION><VENDOR>Oracle</VENDOR><PRODUCT_NAME>BRM</PRODUCT_NAME><PRODUCT_VERSION>2.0</PRODUCT_VERSION><FILE_NAME>release_ISMPPackage_OS_opt.bin</FILE_NAME></COMPONENT_DETAILS>

where:

– Component specifies the BRM source component.



– ISMPPackage specifies the BRM ISMP package.

Note The file name must be entered in the format release_ISMPPackage_OS_opt.bin

7. Save the file.

8. Run the following command:

$ perl upload_src_comp.pl -n

where n is a number between 0 through 2 and specifies what will be written to the log file. The default value is 0. The numbers indicate the following:

– If the value of n is 0, only errors are written to the log file.

– If the value of n is 1, errors and warnings are written to the log file.

– If the value of n is 2, debug messages are written to the log file.

9. Enter the location of the OMS_home.

The BRM source components are uploaded to OMS_home.

Note

– If you try to reload a same component with a different vendor, product name, and product version, these details are not changed.

– The upload_src_comp.log file displays error messages even though the source components are uploaded successfully.


Oracle Corporation

Adding the BRM subtab

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

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

To add the BRM subtab using the Enterprise Manager Grid Control console:

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

2. Click the Target Subtabs link.

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

Setting up preferred credentials

You must set preferred credentials for all managed hosts in your enterprise. The preferred credentials should be set to the credentials of the agent owner. The preferred credentials are used for registering the BRM component and in modifying the execution of the deployment procedure.

To set up preferred credentials:

1. From the Oracle Enterprise Manager Grid Control console, 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, do the following for each host:

a. In the Normal Username field, enter the user name. b. In the Normal Password field, enter the password.c. In the Privileged Username field, enter the user name.d. In the Privileged Password field, enter the password..

5. Click Test.

If the test is successful, “Credentials successfully verified for component” message is displayed at the top of the page.

6. Click Apply.

For more information about preferred credentials, see the discussion of managing preferred credentials in the Oracle Enterprise Manager online Help.


Modifying the default configuration values for a BRM component

When you deploy BRM components from the Oracle Enterprise Manager Grid Control, you need to provide configuration information through the deployment UI that is 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 deployment UI prompts for the mandatory configuration details.

The deployment UI uses default values for all mandatory parameters and some of the optional parameters. The deployment UI reads the default values from a default configuration file. You can change these default values and set additional optional configuration parameters for a component and save your changes to the default configuration file. Later, when you run the deployment procedure to install a component, the deployment UI reads the default configuration file and displays the default values for that component.

Note You must not edit the default XML file manually to modify or add configuration parameters. You must use the Edit Default Configuration feature to perform these operations.

To change the defaults or add additional parameters:

1. Navigate to the BRM page.

2. In the Related Links section, click the Edit Default Configuration link.

3. From the Component Type list, select a Component Type.

The default XML file of the selected component opens. The default XML file exists in the OMS_home/sysman/admin/emdrep/sql/brm/default_xml directory.


To edit the mandatory parameters, do this:

a. Edit the required parameters.You must enter the values for the parameters as mentioned in the table below:

Parameter Values

createdatabasetables • YES

• NO

setupcreatepartitions • YES

• NO

setupdropalltables • YES

• NO

enablepartition • YES

• NO

setupinitdb • YES

• NO


Oracle Corporation

b. Click Save.– To add additional parameters, do this:

a. Click Add Row.

b. In the ParamName field, enter the parameter name.c. In the ParamValue field, enter the parameter value .d. Click Update Configuration.

– To remove additional parameters, do this:

a. Click the delete icon.

A confirmation dialog appears.

b. Click OK.

Note

– You cannot add or delete any mandatory configuration parameters.

– You cannot add additional configuration parameters for BRM Base, Third-Party, and SNMP components.

Installing the Third-Party software

The Third-Party software includes Remote Diagnostic Agent (RDA), Perl libraries and JRE to enable the installation of BRM components that use the InstallShield MultiPlatform (ISMP) installation method.

Note You only need to install the Third-Party software once, before deploying BRM components.

To install the Third-Party software:

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

brmtype • Prepaid

• Postpaid

version • 7.3.1

• 7.4

storagemodel • Test

• Small

• Medium

• Large

hamode • TRUE

• FALSE

timosmgr.highavailabilitymanager.role

• Primary

• Secondary

Parameter Values


2. In the BRM page, scroll to the Related Links section and click the Deploy BRM Targets link.

The Source Selection page appears.

3. Click Add.

The Search and Select: Source page appears.

4. Click the ShowAll button.

All the source components appear.

5. Select the ThirdParty_release_OS check box and click Select.

6. Click Next on the Source Selection page.

The Component Selection page appears.

7. Select the ThirdParty Applications check box.

8. Click Next.

The Target Selection & Configuration page appears.

9. Select ThirdParty Applications and click Add.

10. Select the target host on which to install the Third-Party software.

11. Click Select.

The default configuration values for the instance are displayed.

Note


– You cannot add additional configuration parameters for Third-Party software.

12. (Optional) To save your configuration as the default, click Save.

13. Click Next.

The Credentials page appears.


– Select Use Preferred Credentials, to use the preferred credentials.

– Select Override Preferred Credentials, to override the preferred credentials.

15. (Optional) If you selected Override Preferred Credentials, do one of the following:

– From the Specify For list select Each Target, to specify a user name and password for each host.



Note You must perform the above steps for each target.


Oracle Corporation

– From the Specify For list select All Hosts, to specify a single user name and password to be used for all hosts.




16. Click Next.

The Schedule page appears.


To start the deployment procedure immediately:

a. Click One Time (Immediately).b. Click 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. Click One Time (Later).The current date and time 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. Click 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.

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

19. Click Next.


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

21. Click Finish to start the deployment procedure.

Installing the SNMP software

BRM uses the Simple Network Management Protocol (SNMP) to configure some system components.

To install the SNMP software:





3. Click Add.

The Search and Select: Source page appears.

4. Click the ShowAll button.

All the source components appear.

5. Select the SNMP_release_OS check box and click Select.


The Component Selection page appears.

7. Select the SNMP check box.

8. Click Next.


9. Select SNMP and click Add.

10. Select the target host on which to install the SNMP software.

11. Click Select.

The default configuration values for the instance are displayed.

Note


– You cannot add additional configuration parameters for SNMP software.

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


13. Click Next.









Note You must perform the above steps for each target.


Oracle Corporation

– From the Specify For list select All Hosts, to specify a single user name and password to be used for all hosts.




16. Click Next.












19. Click Next.




When the BRM deployment procedure finishes successfully, you should be able to view the installed SNMP software and its status under the Targets tab.

Deploying BRM components

You deploy BRM components by running the BRM deployment procedure from the Oracle Enterprise Manager Grid Control console. You can deploy a single BRM component or multiple BRM components at the same time. For example, you can install Oracle DM, TIMOS DM, CM, RTP, and AAA Gateway Manager at the same time.


Note Before deploying TIMOS DM, you deploy Oracle DM on the same host. This ensures that the pin_setup utility for TIMOS DM is executed successfully.

This is essential to execute the pin_setup utility for TIMOS DM successfully.

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

• Copies installation files from the Agent system to a staging directory on the host machine.

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

• Registers the BRM components to Oracle Enterprise Manager.

• Registers in the Oracle BRM Suite.

• Generates the configuration file for the component.

• Starts the BRM component service.

• Verifies the service is running.

To deploy BRM components:




3. Click Add.

The Search and Select: Source page displays the BRM source components that are available in the Oracle Software Library. For information about creating BRM components in the Oracle Software Library, see Creating BRM source components in the Oracle Software Library.

Note The search functionality allows you to search on the component name, file name, or the author. You must enter the complete name while using the search functionality.

4. In the Source page, select the check boxes of the BRM source components that you want to install and click Select.


The Component Selection page appears and displays all the components, and optional managers that can be deployed using the selected source component.

For a list of installable components and optional managers for a source component, see BRM ISMP packages, installable, and base components.

6. Select the BRM components to install.

7. Click Next.


8. Select the BRM component and click Add.

For each component, repeat steps 8 through 12.


Oracle Corporation


a. For a BRM Base component, select all the target hosts on which to install the base component.

Note Use the search functionality to find target hosts. Your target hosts must all be of the same platform as the source component you have chosen.

b. For optional managers, select the instance of the BRM Base component over which to install the optional manager.

Note Optional managers are deployed on top of the BRM Base component. You cannot deploy an optional manager unless the base component has already been deployed.

10. Click Select.

The default configuration values for the component are displayed. You can choose to keep the default values or edit them.

Note

– You cannot edit or delete a mandatory parameter. You must specify a value for all mandatory parameters.

– If you are deploying an optional manager on top of a CM, you must add an additional parameter, dm_pointer and provide an appropriate value. For example, if you want to deploy BRM_Services_Framework_Mgr_AAA manager on top of CM, you must do the following:

a. In the ParamName field, enter cm.dm_pointer.

b. In the ParamValue field, enter 0.0.10.2 ip host_name 11990where host_name is the name of the host machine.

– For Batch Controller, REL, and UEL components, enter the values in the following format for the Infranet Connection field:

pcp://root.0.0.0.1:password@host_name:CM_port/service/pcm_client

where:

- password is the user password.

- CM_port is the Connection Manager port number.

– For AAA Gateway and Diameter DM components, enter the values in the following format for the CM Pointer List field:

host_name:CM_port True root.0.0.0.1 password socket_timeout

where socket_timeout is the connection time out value. The default value is 3000.

You can select to create the BRM database or use an existing database with BRM schema. To create a BRM database while deploying, see Deploying BRM components with database creation.

Note Ensure that you configure all database related parameters in the CM's Monitoring Configuration page before deploying an optional manager on top of a pre-installed CM.

11. (Optional) To specify additional optional configuration parameters, click Edit More Parameters.



13. Click Next.

The Credentials page appears. For each component, repeat steps 14 through 16.

14. Select the BRM component.








Note You must perform the above steps for each target.– From the Specify For list select All Hosts, to specify a single user name

and password to be used for all hosts.




17. Click Next.













Oracle Corporation

20. Click Next.




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

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

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

The Procedure Completion Status page appears.

3. Select the Deployment Procedure Instance Name link

where Deployment Procedure Instance Name is the deployment procedure instance name.

The progress details are displayed under the Status Details section.

When the BRM deployment procedure finishes, the Deployment Procedure Manager screen appears and the following details are displayed:

– Run - Deployment Procedure Instance Name

– Procedure - Deployment Procedure Name

– Procedure version - version_no

– Owner - User name used to log into Oracle’s Management Service host machine

– Status - Succeeded (If the deployment procedure fails or is still running, the status displays Failed or Running respectively).

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

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

You can also verify this by searching the file vpd.properties.componentname in the BRM_home directory of the BRM user.

Note Click Refresh to update the configuration values instantly after BRM components are deployed.

The deployment procedure logs all the activity in the unzip.log, copy_to_stage.log, generate_configuration.log, installBRM.log, and registerTarget.log files that are in the staging location. If the procedure fails to deploy the BRM components, see Diagnosing deployment procedure failures, to diagnose the reasons why the deployment procedure failed and how to resolve those issues.

Important

• You must deploy BRM 7.4 Patch Set 3 after deploying BRM components.

• When you encounter an error at the Start Service step while executing the patching deployment procedure, you must merge the values in the pin_ctl.conf file and retry the failed step using the Enterprise Manager Grid Control. For more information, see the BRM 7.4 Patch Set 3 README file.


Diagnosing deployment procedure failures

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



The Deployment Procedure Manager page appears.

3. Click a failed procedure link.

The Status page appears.


– Click the corresponding link against the status Failed.

– Click OMS Log from the Status Detail section to view OMS related error messages.

The Step Status page appears.

5. View the output log of the failed step for the error message.

6. If the error was caused by an incorrect directive parameter value, select the target check box and click the Update & Retry button.

7. Verify the following:

Copy Install Scripts

– verify that you have the right permission to copy files to the staging area.

– verify that the InstallScripts BRM source component exists in the Software Library.

Unzip Binary

– verify that the InstallScripts source component has correct common.zip file uploaded in Software Library.

Copy Binary file to the staging directory

– verify that the BRM source component has the ISMP file uploaded to the Software Library.

Copy Customer values

– verify if the component’s customer.values file exists in the Software Library.

Stop Service

– verify that the pin_ctl.conf file has the right version and is working

Install BRM component

– verify that you have provided valid ThirdParty software information.

– verify if you have the permission to execute the ISMP package.

– verify that the package has not been installed already under the same install location and the uninstaller.bin file does not exist in the component’s uninstaller folder.

Register target


Oracle Corporation

– verify that the host’s preferred credentials are set to the agent owner’s credentials.

– verify that the component does not exist in Oracle’s Management Service already.

– verify if the agent upload is functioning.

Generate Configuration file

– verify that the correct parameters are provided for TNS_ADMIN, ORACLE_HOME, DM_POINTER, CM_POINTER_LIST, and other database related parameters.

– verify that the corresponding filesystem has enough space if tablespace creation is specified.

– verify that Oracle DM dd_write_enable parameters are enabled if schema update is involved.

Start Service

– verify if the log directory is valid and the pin_ctl.conf file is working properly.

– verify that the configuration file has valid port number and connection information.

– verify if all dependencies are up and running.

– verify if SNMP master agent is up and running on the agent host for TIMOS and all Pipeline instances and check the availability of ports that are specified.

Verify Service

– verify that the configuration file has valid port number and connection information.

– verify if all dependencies are up and running.

– verify if SNMP master agent is up and running on the agent host for the TIMOS instance.

8. Make the necessary changes and click the Retry button.

9. Click the Done button.

Deploying BRM components with database creation

Some BRM components, such as the Data Manager (DM), Batch Rating Engine (BRE), and Real-time Pipeline (RTP), require connection to the BRM database to complete installation and to start up the service. When you deploy BRM components from Enterprise Manager Grid Control, you can select to create the BRM database at the time of deploying or use an existing database with BRM schema.

Important If you are using an existing database, ensure that the BRM schema is for the BRM release you are deploying.


To create the BRM database during deploying of BRM component, you will need to provide the following configuration information in the deploying UI:

Field Description Default value

SetupInit DB Specify whether to initialize the BRM databases. Yes

Create Partition Specify whether to add partitions to your event tables.

• Enter Yes to have the installer add 12 monthly partitions, a historic partition, and a last partition to your event tables.

• Enter No if you want the installer to add only a historic partition and a last partition to the tables. You can use this partitioning layout for a simple test or demonstration system. For a production system, however, you must add purgeable partitions after installation is complete and before the system generates events.

Note This sets the $CREATE_PARTITIONS parameter in the pin_setup.values file to Yes.

This prompt is displayed only if you enter Yes to Partition event tables.

Yes

Enable Partition Specify whether you want to enable partitioning.

Caution! To partition any tables, you need Oracle Partitioning. If you select Yes but don’t have Oracle Partitioning installed, the BRM setup program fails when it tries to create partitions.

Note This sets the $ENABLE_PARTITION parameter to Yes in the pin_setup.values file.

Important

• If you select No and then change your mind after you’ve installed BRM, you will have to upgrade your BRM database from a nonpartitioned to a partitioned version before you can partition your tables.

• If you plan to use Rated Event Loader to load prerated events, you must partition your event tables.

• If you select Yes, you must configure pin_setup to set up any non-event partitions. Your event tables will be partitioned automatically.

Yes

Classes to be partitioned

Assign a list of classes that you want to partition.

Important You cannot partition classes after you run the pin_setup utility.


Oracle Corporation

Note You cannot create the BRM database for Pipeline components using the BRM Deployment procedures, in this release.

Drop Tables Enter whether you want to drop the database tables.

Caution! If you select Yes, the installer drops all existing tables on your system. This results in irrecoverable loss of data. Do not use this unless you have backed up all of your existing data.

If you select No, the installer uses your existing BRM tables.

In test systems, select Yes to reinitialize the database.

Yes

Create DBTables Enter whether you want the installer to create default BRM tablespaces for you.

Enter No to create custom tablespaces manually. You must create your tablespaces before you run the pin_setup script.

Yes

DB Version Specify the database server version. For example,

• Oracle 9i

• Oracle 10g

• Oracle 11g

9i

DB Vendor Specify the database vendor. Oracle

DB Alias Enter your database alias.

DB User Enter your database user name. pin01

DB Password Enter your database password. pin01

System password Enter your Oracle database system password.

The Oracle database system password is needed only if you enter Yes to Create BRM Database Tablespaces.

Oracle

Table Space Storage Model

Enter the desired size of your database.

• Enter Test for test or demonstration databases smaller than 700 MB.

• Enter Small for demonstration databases smaller than 1.5 GB.

• Enter Medium for production databases smaller than 30 GB.

• Enter Large for production databases larger than 30 GB.

Small

Tables Group Enter the name of your data tablespace. pin00

Indexes Group Enter the name of your index tablespace. pinx00

DM port Enter the port number for the Data Manager. 12001

TNS Admin Specify the location of the TNS home directory.

Field Description Default value


Deploying BRM Applications

You can deploy several components together grouped as BRM applications on the same host. The following are grouped as BRM applications:

• Device Management

• Load notification event

• Load price list

• Pin A/R taxes

• Pin balance transfer

• Pin billed

• Pin bill handler

• Pin bulk adjust

• Pin export price

• Pin invoice

• Pin monitor

• Pin ood handler

• Pin rate change

• Pin remit

• Pin rerate

• Pin subscription

• Pin trial bill

• Pin unlock service Invoicing

• Misc

• Pin_cfg_bpdump

• SOX_Unlock

• Subscription

• Testnap

• UEL

• GL_Export

• Diagnostics

• Infranet Manager CLI

• Infranet Manager

• Node Manager

• Export_price

• Credit_Control Billing

• Account Dump Utility

• Development_Files

See Deploying BRM components.


Oracle Corporation

Deploying BRM Base components

You can deploy several components together grouped as BRM Base components on the same host. The following are grouped as BRM Base components:

• Portal Base Install Scripts

• Rogue Wave Libraries

• Common Database Scripts

• Batch Controller

• Billing

• Pin_cfg_bpdump

• Invoicing

• CM Proxy

• CMMP


• CM Proxy

• Development_Files

• Email DM

• Formatter

• Export_price

• GL_Export

• Account Dump Utility

• Infranet Manager

• Infranet Manager CLI

• Invoice_DM

• DM

• Oracle DM

• Invoice Formatter

• Misc

• Node Manager

• Subscription

• Testnap

• UEL

• Java PCM Program Files

• Shared Objects for Communication

• partition_utils

• Shared Perl Modules

• Common Install Scripts


See Deploying BRM components.

Note The Enterprise Manager Grid Control console supports the deployment of Invoice DM, but does not support any other operations.

Modifying Oracle DM configuration

You must modify the configuration for Oracle DM.

To modify the configuration:


2. Click the dm_oracle link.

3. In the Related Links section, click the Edit Configuration link.

The Target Selection & Credentials page appears.

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

b. Enter the new administrator Username and Password for the target host.


5. Click Next.

The Configure page appears.

6. Click Editor Mode.

The configuration details for the component appears.

7. Make the following changes.

- dm dd_write_enable_fields 1 - dm dd_write_enable_objects 1 - dm dd_write_enable_portal_objects 1

8. Click Next.




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



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


Oracle Corporation



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.


11. Click Next.

The Review page appears displaying the original content and the changes made.


13. Click Finish.

About zero down time upgradeYou apply BRM software patches by running the BRM deployment procedure from the Oracle Enterprise Manager Grid Control console. The BRM patching deployment procedure applies BRM software patches serially on different components using the ZDU logic. See Patching BRM components.

If any error is encountered, the procedure continues to apply the patch to other components only. When an error occurs, you can view the status of the procedure by viewing Procedure Completion status tab. You must run the patch deployment procedure again for the component that failed after correcting the errors.

Similarly, when the patch deployment procedure detects that the selected patch has already been applied on a component, the deployment procedure logs a warning and the procedure continues to apply the patch to other components.

Patching BRM componentsThere are two methods for applying patches:

• You can connect to Oracle MetaLink Web site from Enterprise Manager, search for a specific patch and apply the patch. To apply a patch from Oracle MetaLink, you need to specify My Oracle Support credentials from the Patching Setup page for Enterprise Manager to connect to MetaLink. Additionally, you need to create a RefreshFromMetaLink job to update the BRM patch information in the Enterprise Manager repository. See Before patching BRM components.

• You can apply patches that you have locally on the Agent machines by manually adding the patch to the Oracle Software Library and then applying the patch. See Before patching BRM components.

Note You can only apply one patch at a time.


Before patching BRM components

Before you patch BRM components, do the following:

1. Set up Oracle MetaLink credentials on the Patching setup page. See the discussion of specifying patching credentials in the Oracle Enterprise Manager online Help.

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

3. Set up preferred credentials. See Setting up preferred credentials.

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

Updating the 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. From the Create job list, select Refresh From My Oracle Support and click Go.

The Create 'Refresh From My Oracle Support' Job page appears.

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

4. Click Save to Library.

5. Click the Job Library subtab.

6. Select the job created in step 4.

7. Click Submit.

8. Click Submit again.

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

9. Stop and restart the Management Service.

10. From the Oracle Enterprise Manager Grid Control console, click on the Deployments tab.

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


12. Select Patch Oracle BRM Software

13. Click Schedule Deployment to start the patch deployment procedure.

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


Oracle Corporation

15. Verify Oracle Communications Applications appears in the Product Family list and Oracle Communications Billing & 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 Oracle MetaLink or Oracle 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. From the Enterprise Manager Grid Control console, click on the Deployments tab.

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

The Patch Cache page appears.

3. Click Upload Patch.

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

The Patch File name should be in the format ppatch_number_7.4_OSid

where:

– patch_number specifies the patch number.


– OSid specifies the operating system id.

The following table lists the ids for different operating systesms:

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.4.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 Add Patch File to Patch Cache checkbox.

7. Click Upload.

Operating System Operating System Id

HP-UX Itanium 197

HP-UX Itanium (32-bit) 278

HP-UX PA-RISC (32-bit) 999

HP-UX PA-RISC (64-bit) 59

Sun Solaris SPARC (64-bit) 23

Sun Solaris SPARC (32-bit) 453

IBM AIX on POWER Systems (64-bit) 212

IBM AIX on POWER Systems (32-bit) 319

Linux x86-64 226

Sun Solaris x86-64 (64-bit) 267

Sun Solaris x86 (32-bit) 173


Oracle Corporation

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

Patching BRM components

You apply BRM software patches by running the BRM 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 patch deployment procedure:

• Checks if the selected patch has already been installed on the host. If yes, a warning will be logged in the patchRouter.log file.

• Stops the BRM component.

• Upgrades BRM to the new patch level.

• Updates the component patch information.

• Starts the BRM component.

• Verifies that the component is running.

– If the component failed to start, you must perform any merge operation required by the patch and retry starting the service.


– If you want to rollback to the previous version of the patch, you must use the rollback deployment procedure.

Note If all the components are deployed in the same BRM_home location, the patch is applied to all the components even if you select a single component

To patch BRM components using the Enterprise Manager Grid Control console feature:

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

2. Scroll to the Related Links section and click the Patch BRM Targets link.

The Patch Oracle BRM Software: Software Updates page appears.

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

Note You can only apply one patch at a time.

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

Tip When you initially install a patch from MetaLink, the patch is automatically added to the Oracle Software Library. The next time you want to apply the same patch, you can select the patch from the Oracle 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 & 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.

6. Click Go.

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

7. 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 patches that must be installed prior to applying the patch that you have selected.

– Perform all pre-install and post-install instructions as specified in the Readme file before or after applying the patch manually.


Oracle Corporation

8. Click Next.

The Target List page appears.

9. Click Add.

The Select Target page appears.

10. From the Target Type list, select the target type.

11. From the Platform list, select the platform.

12. Click Go.

Note Based on the patch selected, the patching deployment procedure populates the Platform field with a default value.

13. Select the check boxes of the components on which to apply the patch.

14. Click Select.

15. Perform steps 9 thru 13 for patching multiple components using the same patch.

16. On the Target List page, click Next.














19. Click Next.



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

To start the patching deployment procedure immediately:

a. Select One Time (Immediately).


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

To start the patching deployment procedure at a later time:





21. Click Next.



23. Click Finish to start the patching deployment procedure.

You can view the progress of the deployment procedure.

To view the progress of the steps executed by the deployment procedure:




3. Click the PATCH_BRM_SOFTWARE_username_timestamp link.

where:

– username specifies the user name.

– timestamp specifies the date and time at which the procedure is executed.


When the BRM patching deployment procedure finishes, the Deployment Procedure Manager screen appears and the following details are displayed:

• Run - PATCH_BRM_SOFTWARE_username_timestamp

• Procedure - Patch Oracle BRM Software

• Procedure version - version_no

• Owner - User name used to log into Oracle’s Management Service host machine

• Status - Succeeded (If the deployment procedure fails or is still running, the status displays Failed or Running respectively).

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

To verify the patch has been applied successfully, do one of the following:


Oracle Corporation

• Check the name of the patch in the Patches Applied field on the Target page.

• Run the following command on the agent machines where the patch was installed:

install_loc/bin/pinrev

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

All the activity is logged in the unzip.log, copy_to_stage.log, patchRouter.log, update_patch_info.log, and patch_log.txt files. If the deployment fails to apply the patch, check the log files for the reason for the failure. You can also click the Management service Log in the Status detail section to view error messages related to the Management service.

Uninstalling BRM componentsTo uninstall BRM components:


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


3. Select Uninstall BRM Software and click Schedule Deployment.

The Uninstall BRM Software: Target List page appears.

4. Click Add.

The Select Target page appears

5. From the Target Type list, select a Target Type.

The target of the selected target type are displayed below.

Note You must click the Go button to display the search results of the default target type.

6. Select the target type, click Select, and click Next.

The Uninstall BRM Software: Component Selection page appears and displays the base component and all its optional managers that can be uninstalled.

For a list of Base components for optional managers, see BRM ISMP packages, installable, and base components.

Note You can uninstall only one component instance at a time.


– Select the Select All check box, to uninstall the base component and all its optional managers.

– Select the check box against the BRM component, to uninstall the component.


– (Optional) Select the check box against an optional manager, to uninstall a specific optional manager.

Note You cannot choose to uninstall only the base component when the optional managers are still installed.

8. Click Next.














11. Click Next.












Oracle Corporation

13. Click Next.




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




3. Click the UNINSTALL_BRM_SOFTWARE_username_timestamp link.

where:



The progress details are displayed under the Status Details column.

Note When you uninstall a CM optional manager, the deployment procedure will prompt you to update the pin.conf file. You can remove the optional manager entries from the CM pin.conf file before you start the service. You must select the component, click Confirm and then click Done.

When the BRM deployment procedure finishes, the Deployment Procedure Manager screen appears and the following details are displayed:

• Run - UNINSTALL_BRM_SOFTWARE_username_timestamp

• Procedure - Uninstall BRM Software

• Procedure version - version_no

• Owner - User name used to log into Oracle’s Management Service host machine

• Status - Succeeded (If the deployment procedure fails or is still running, the status displays Failed or Running respectively).

• Last updated - Date and time when the BRM deployement procedure was completed.

Note

• Database changes are not rolled back when you uninstall a BRM component.

• Oracle Enterprise Manager does not support uninstallation of Third-party software.


Uninstalling (rolling back) BRM software updatesYou 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.

Important You can uninstall any patch that has been applied to a component, however the BRM rollback deployment procedure does not check for patch dependencies. You should check for any dependencies first to ensure that patch does not consist of any required files before uninstalling a patch. Otherwise, uninstalling the patch could result in loss of functionality. To view the list of patches applied to a component, see Viewing the list of patches that have been applied to a component.

Note

• If a database schema was created during the patch install, there are no changes made to the database schema when the patch is uninstalled.

• Any database changes that were applied during the patch install are not rolled back when the patch is uninstalled.

• 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 no patch is applied.

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.

3. Updates the component patch information.

4. Starts the BRM service.

5. Verifies that the service is running. If the service failed to start, a non-zero error code is returned to Oracle’s Management Service.

Rolling back BRM software patches

Note You cannot choose the patch you want to roll back. The last BRM software patch that was installed on the BRM component machine is automatically rolled back. For example, if patch 1, patch 2, and patch 3 are applied, patch 3 is automatically rolled back.

To roll back a BRM software patch:


2. In the BRM page, scroll to the Related Links section and click the Rollback BRM Patch link.

The Target List page appears.

3. Click Add.

The Select Target page appears.

4. From the Target Type list, select the target type.


Oracle Corporation

5. From the Platform list, select the platform

6. Click Go.

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

7. Select the check boxes of the components for which to roll back the BRM software patch and click Select.

8. Click Next.














11. Click Next.



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

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:






13. Click Next.



15. Click Finish to start the rollback deployment procedure.

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




3. Select ROLLBACK_BRM_PATCH_username_timestamp link

where:




When the BRM roll back deployment procedure finishes, the Deployment Procedure Manager screen appears and the following details are displayed:

– Run - ROLLBACK_BRM_PATCH_username_timestamp

– Procedure - Rolback BRM Software Patch

– Procedure version - version_no

– Owner - User name used to log into Oracle’s Management Service host machine

– Status - Succeeded (If the deployment procedure fails or is still running, the status displays Failed or Running respectively).

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

To verify the patch has been rolled back successfully, check the Patches Applied field on the Target page. If the patch has been rolled back, the Patches Applied field will be empty.

The roll back procedure logs all the activity in unzip.log, copy_to_stage.log, rollback.log, rollback_log.txt, and update_patch_info.log files in the staging location of the component that is rolled back. If the procedure fails to roll back the patch, check the log files and the Management service log for the reason for the failure.


Oracle Corporation

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

The BRM Application Management Pack consists of BRM extensions to Oracle’s Management Service, Oracle’s Management Agent, and Oracle’s Management Repository. These extensions are a collection of target definition files used for deploying and monitoring of BRM components from Enterprise Manager Grid Control.

Each target definition file defines a BRM component and includes the following types of information:

• Component type

• Metrics to be monitored for the component

• Method for obtaining the metric data

• Collection schedule for each metric

• Alert threshold values

When BRM components are deployed using Enterprise Manager Grid Control, the BRM component instances are registered in Enterprise Manager Grid Control. During the auto discovery process, Oracle’s Management Agent collects the configuration provided while deploying each component instance and sends the information to Oracle’s Management Service to be stored in Oracle’s Management Repository.

Note Automatic discovery of BRM component instances is initiated only when BRM components are deployed using Enterprise Manager Grid Control. You use guided discovery to find and register BRM components not deployed using Enterprise Manager Grid Control. See Monitoring and managing BRM components.

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

• Monitor current status and performance of BRM components.

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

• View log file details.

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

• View and manage configuration of BRM components. See About monitoring component configuration.

About monitoring system performance

To maintain high levels of performance it is necessary to identify problems by monitoring performance of the components and take corrective action before the problems impact business operations.


Comprehensive component monitoring lets you identify the problem areas in your components that affect its performance and thus provides a clear picture about the overall health of the component. The BRM Integration feature helps you monitor the components and supports timely detection and notification of impending problems across your enterprise. For more information about how the system is monitored, See Monitoring and managing BRM components.

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 component. For batch pipeline, you can see the graph for event detail records (EDR) processed per second; for TIMOS components, you can see the quality of service (QOS) statistics graph. You can also represent the graphs in a table. See Monitoring component performance history.

The following is the list of graphs for Batch Rating Pipeline and Real-time Pipeline processing:

• Process Input Table(processing time VS time)

• Output Stats Average (transaction count VS time)

• Ouput Stats Table(process time VS index)

The following is the list of graphs for TIMOS:

• Quality of Service (qos_bucket1 , qos_bucket2, qos_bucket3, qos_bucket4, qos_bucket5, qos_bucket6, qos_bucket7, Average VS process_name)

• ROC Objects (object_size VS object_name)

• Heart Beat (transition beat sent, received VS time)

• Bulk Data Group (number payload queued, number payload sent VS time)

• Bulk Data Object Table (object type VS object count)

• Data Migrator (transaction size, migration size VS time)

• Startup Migration (startup migration duration VS time)

• Hot Standby (on going post com, on going pre com VS time)

• MTF State Mgr (number open con VS time)

• Pending Batch Migration Request

• Pending Realtime Migration Request

See Monitoring component performance history.

About alerts and notifications

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


Oracle Corporation

You can configure alerts for all the defined metrics. Metrics are units of measurement used to determine the health of a component. Oracle Enterprise Manager sends alerts using the defined metrics and the associated thresholds notifying you of the problems with the component. By default, the alerts are configured and the metrics are defined for each of the components. 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 the Enterprise Manager Grid Control console or from the respective component’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.

About BRM metrics

For each of the monitored components, the metrics data is collected over time and is stored in the repository database. The metrics details can be collected for BRM processes such as memory consumption and disk space usage. The collected data helps you in detecting potential memory leaks.

The following table lists all the metrics for BRM components:

Component Metrics

BRE

RTP

• Duration since last start

• Information About Module Processing Times

• Log File Monitoring

• Process Information

• Process Input EDR Max Min Information

• Process Input Table Information

• Process Output Stats Average Information

• Process Output Table Information

• Response

Connection Manager

CMMP

CM Proxy

Batch Controller

Formatter

Oracle DM



• Response

• Memory Utilization (%)


TIMOS Data Manager

• Duration since last start

• HAManager State, Log File Monitoring

• Process Information, Response

• Timos Acceptor Pool Configuration

• Timos Acceptor Pool Table

• Timos Bulk Data Group Information

• Timos Bulk Data Object Table Information

• Timos Connection Configurations

• Timos Connector Pool Configuration

• Timos DMO Server Table

• Timos Data Migrator Information

• Timos HA Information

• Timos HA Role Mediator Information

• Timos Heartbeat Information

• Timos Hot Standby Information

• Timos Index Controller Table

• Timos MTF State Manager Information

• Timos Memory Manager

• Timos Migration Types Information

• Timos Overload Detection Configuration

• Timos Pending Batch Migration Request Information

• Timos Pending Realtime Migration Request Information

• Timos Per-Thread Statistics

• Timos Poid Index Controller

• Timos Pool-Wide Statistics

• Timos Private Peer Acceptor Pool Configuration

• Timos Private Peer Acceptor Pool Table

• Timos QoS Opcode Configuration Table

• Timos QoS Opcode Table

• Timos ROC Object InformationTimos ROC Sync Manager Information

• Timos Startup Migration Information

• Timos Thread Check Manager Information

• Timos Transaction Co Ordinator

• Timos Transient Object Manager Information

Component Metrics


Oracle Corporation

You can monitor all BRM processes including CM, DMO, DMT, and Pipeline processes. For more information about how the BRM processes are monitored, see Viewing BRM component metrics.

About BRM reports and graphs

For each of the monitored components, 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 components. 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 BRM component metrics.

AAA Gateway Manager

Account Synchronization Data Manager

Email Manager

EAI

EAI JS

Fusa

LDAP

Taxware

Telco

Vertex

Vertex Quantum Manager

Rated Event Loader



• Response

Universal Event Loader


Component Metrics


About BRM components

The following table lists the BRM components that you can discover, configure, and monitor using Oracle Enterprise Manager Grid Control:

Component Component type Description

Connection Manager oracle_brm_cm 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. Connection Manager includes Connection Manager process types, such as cm, cm_proxy, and cmmp.

CM Proxy cm_proxy A system process (cm_proxy) that provides a fast, unauthenticated Connection Manager (CM) connection for BRM applications. CM Proxy allows access to the database without a login, which improves performance.

CMMP cmmp A system process that redirects client connections to Connection Manager (CM)s. If a CM goes offline, the CMMP reroutes connections to another CM.

TIMOS Data Manager

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

Note The Enterprise Manager does not support Performing Graceful Switchover of TIMOS in this release.

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

Email Manager dm_email A optional component that integrates your company’s email service with the BRM system.

EAI dm_eai Enterprise Applications Integration is an optional component that enables the use of BRM with other data-sharing applications in your enterprise.

Fusa dm_fusa A credit card and direct debit processing service that BRM supports.

Account Synchronization Data Manager

dm_ifw_sync A Data Manager that informs Pipeline Manager when account data has changed.

LDAP dm_ldap BRM integration with Lightweight Directory Access Protocol, a set of protocols for accessing data directories.

Telco dm_prov_telco Telco services are the services that are provisioned on a telco network. There are groups of telco services, such as telephony, data, and fax.


Oracle Corporation

Monitoring and managing BRM componentsTo monitor and manage the BRM components, you must first discover them. You can use the discovery feature of Oracle Enterprise Manager Grid Control to find the deployed BRM components. Components can be discovered using the automatic discovery process or the guided discovery process. Automatic discovery process occurs automatically and registers component instances when BRM components are deployed using Oracle Enterprise Manager. Guided discovery process is used to manually discover and register already existing component instances not deployed using Oracle Enterprise Manager.

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

Vertex dm_vertex The company that produces Communications Tax Q Series, which calculates telecommunications taxation, and Sales Tax Q Series, which calculates tax for sales and use.

Vertex Quantum Manager

dm_vertex An optional component that integrates BRM with the Vertex Sales Tax Q Series software.

AAA Gateway Manager

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

EAI JS eai_js An optional component enabling the use of BRM with other data-sharing applications in your enterprise.

Batch Controller batchcontroller A BRM software component used for running applications automatically.

Formatter formatter The formatter is a Java process that takes XML data and an XSLT style sheet and generates an HTML invoice.

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

RTP rtp The Real-time pipeline.

Taxware dm_taxware The company that produces the Sales/Use Tax and WorldTax programs. BRM supports both Taxware programs.

Rated Event Loader rel An application that loads pipeline prerated events into BRM database.

Universal Event Loader

uel An application that loads event records from event log files into BRM database.

BRM Applications A group of utilities with each utility having a specific function.

Component Component type Description


Important You must encrypt all passwords in the configuration files. When you modify the configuration without encrypting the passwords, the passwords are displayed in plain text.

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

Note If the Agent user and BRM user are different, you must grant the Agent user with write permission to the BRM user account. The Agent user and BRM user must belong to the same group and be granted equal privileges.

Important If you perform operations such as patching, rollback, or uninstall on the server side without using the Enterprise Manager Grid Control, the information on the home page of the component displays incorrect values. To resolve this problem, you must remove the component and discover it.

Adding BRM components using guided discovery

Note You must configure the http port in the BRE and RTP configuration files before you run guided discovery as the specified http port becomes part of the component name. This port is unique and helps differentiate different components during guided discovery. If you have used guided discovery without configuring the http port, remove those components and re-discover them.

To discover BRM components using a guided discovery:

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

2. Click the Add BRM Enterprise button.

The BRM Targets Discovery page appears.


– Select the Portal Base Components button, to add BRM Base components.

– Select the PipeLine Components button, to add Pipeline components.

4. Click Add.

The Search and Select: Targets page appears.

5. Select Host as the Target Type.

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

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

8. 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 components is PIN_home.


Oracle Corporation

– Third Party Location—the path where the third-party applications are installed.

– BRM User—the user name used while connecting to the host.

– BRM Password—the password used while connecting to the host.

– Oracle Home—the directory where BRM Database Oracle client is installed.

– BRM Type—Prepaid or Postpaid.

– IFW Home Path—the path where Pipeline components are installed. The default home path for Pipeline components is IFW_home.

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

– IFW-Event Handler Port—the port where Pipeline Event handler is available.

Note The fields that are displayed depends on the component you have selected.

9. Click Ok.

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

Note

– Click Refresh to refresh the list of discovered components.

– You can discover components of one type only each time you run guided discovery. For example, all BRM Base components that are in PIN_home or Pipeline components in an install path or SNMP.

– You can discover only one PIN_home per host at a time even if you select multiple hosts.

– Discovery of BRM Applications is not supported.

Important

• You must deploy BRM 7.4 Patch Set 3 after deploying BRM components, if the patch set is not already deployed.

• When you encounter an error at the Start Service step while executing the patching deployment procedure, you must merge the values in the pin_ctl.conf file and retry the failed step using the Enterprise Manager Grid Control. For more information, see the BRM 7.4 Patch Set 3 README file.

• On a pre-installed setup, if both BRE and RTP are deployed in the same location, when you patch BRE, RTP also is patched and vice-versa. Due to this the configuration files of both are updated. You must update the files manually based on the backup file created while updating the patch and start the service.

• After discovering BRE, RTP, and TIMOS components, you have configure the SNMP master agent port going to Monitoring Configuration Page of that particular target to enable the metric collection.


Adding SNMP components using guided discovery

To discover SNMP components using guided discovery:

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

2. Click Add BRM Enterprise.

The BRM Targets Discovery page appears.

3. Select the SNMP Component button and click Add.


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:

– SNMP Install Location—the path where BRM is installed.

– Third Party Location—the path where the third-party applications are installed.

– BRM User—the user name used while connecting to the host.

– Host Password—the password used while connecting to the host.

– SNMP Master Agent Port—the port number where SNMP master agent is available.

– SNMP AgentX Port—the port number where SNMP AgentX is available.

Important You must provide valid port number details as these details will not be validated.

8. Click Ok.

The discovery process starts and the All Targets page appears with a list of all the discovered SNMP components. This process creates a BRM SNMP component with the data provided and the same is then uploaded into the Oracle Enterprise Manager repository.

Note

– Click Refresh to refresh the list of discovered components.

– If a component is discovered once again when you run guided discovery, the name of the target will be changed and will be in the format SNMP.hostname_port.

– You must update the registry file with the correct SNMP port details for AAA Gateway, TIMOS, RTP, and BRE.


Oracle Corporation

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

Monitoring BRM component performance

Viewing BRM component metrics

To view BRM component metrics:

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

2. Click the component for which you want to view the metrics.

The component’s home page appears.

3. Scroll to the Related Links section and click the All Metrics link.

A list of metrics being monitored for the component appears.

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

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

– To view function module statistics, in the pipeline registry file you must set WriteMessageKey = TRUE.

For information on how to configure collection of metrics, see Configuring the collection schedule.

Monitoring component performance history

To monitor the performance history of a components:



2. Click the component for which you want to view the performance history.


3. Click the Performance tab.

The performance details of the component appear.

4. Select the period for which you want to view the performance data for the component.

The page refreshes and shows the relevant performance data.

Monitoring BRM component configuration details

About monitoring component 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 Oracle’s Management Repository. The View Configuration link on the home page of BRM components lets you view the latest configuration.

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

Viewing component configuration details

To view the configuration details of a component:

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

2. Click the component for which you want to view the configuration details.


3. Scroll to the Configuration section and click the View Configuration link.

The View Configuration page appears.

Note

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

• To view the configuration details of a AAA Gateway component, the instance should be running. Enterprise Manager cannot fetch the configuration details if the instance is stopped.

• Enterprise Manager will display an error message if the value of a configuration parameter for any component exceeds 100 characters. This is due to a limitation in Enterprise Manager. If this occurs, edit the pin.conf and the registry files 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.


Oracle Corporation

Modifying component configuration details

You can modify the configuration details of the existing components.

To modify the configuration details of a component:


2. Click a component instance link.

For example, click the dmEmailTest link.

3. In the Related Links section, click the Edit Configuration link.

The Target Selection & Credentials page appears.













6. Click Next.

The Configure page appears.


– Click Default Mode and do one or more of the following:

a. Remove parameters.

b. Configure the desired parameters.c. Click Add Configuration, add the parameter name and value, and

click Update Configuration.– Click Editor Mode.

The configuration details for the component appears.

– Make the required changes.

Note If you make changes in the Default Mode, these changes will not appear in the Editor Mode and vice versa.


8. Click Next.












11. Click Next.

The Review page appears displaying the original content and the changes made.


13. Click Finish.

Note

• When you deploy a BRM component or an optional manager such as Account Synchronization DM, you must manually update the CM pin.conf file with non-CM optional manager entries and the correct port details.

• Enterprise Manager does not update the component properties by monitoring change in the registry file. You must rediscover the registry file or edit the configuration file from Enterprise Manager.

Rebalancing CM connectionsYou use the Rebalance AAA Gateway feature to rebalance the CM connectionss. You can rebalance AAA Gateway connections to CMs after one or more CMs is taken off line and brought back up. For example, if you have four CMs in the connection pool and one CM goes offline, the load is automatically balanced among the three remaining CMs. When you bring the fourth CM back on line, the load is not automatically rebalanced.

To rebalance CMs:



Oracle Corporation

2. Click a AAA Gateway component instance link.

3. Click the Rebalance AAAGW button.

Updating the DMO farmDMO farm corresponds to the configured DM Oracle processes that a TIMOS DM communicates with. This refreshes the Oracle DMs that TIMOS DM uses.

To update the DMO farm:


2. Click a TIMOS DM component instance link.

3. Click the Update DMO Farm button.

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

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:

• AAA Gateway


• Java Process

• Pipeline

• RTP

• TIMOS Data Manager

• Data Manager

Pipeline EDR throughput

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


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.

To configure alerts:


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

2. Click Oracle BRM Suite_System.

The Oracle BRM Suite_System page appears.

3. Click the Components tab.

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

4. Click the component for which you want to configure the alert.


5. In the Related Links section, click the Metric and Policy Settings link.

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

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

The Edit Advanced Settings page appears.


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


Oracle Corporation

Modify the existing threshold settings.

8. Click Continue.

You are returned to the Edit Advanced Settings page.

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

The Metric and Policy Settings page appears.

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

1. Navigate to the component’s home page.

2. Click the Metric and Policy Settings link.

3. From the View list, select All metrics.

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

5. Select the frequency type.

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

7. Click Continue.

You are returned to the Metric and Policy Settings page.

8. Click OK to save the changes.

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:

1. Navigate to the component’s home page.


2. From the component’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.

Viewing alerts

To view the log file alerts for BRM components:

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

The Alerts section lists all the defined metrics for the component, 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 component 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.

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 component is displayed in the alerts and violations column of the members table.

Managing BRM components

Viewing BRM components

To view BRM components:

1. On the Grid Control console, click Targets tab.


Oracle Corporation

2. Click the BRM subtab to view all BRM targets.

3. Click the component link to view component information.

Starting, stopping, or restarting individual BRM components

You can perform one of the following:

• Starting, stopping, or restarting individual BRM components

• Starting, stopping, or restarting selected BRM components

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

To start, stop, or restart individual BRM components:

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

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

2. Click Oracle BRM Suite_System.

The Oracle BRM Suite_System page appears.

3. Click the Components tab.

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

4. Click the name of the component you want to start, stop, or restart.

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

5. Click Start, Stop, or Restart to start, stop, or restart the component respectively.

Note The following is applicable for BRE components that are discovered using guided discovery:

• To start the BRE component, 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.conf file 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.

• Update the following environmental variables in the PIN_home/bin/pin_ctl.conf file with the appropriate values:

– CTL_SNMP_PATH

– LD_LIBRARY_PATH

– LD_LIBRARY_PATH_64

– ORACLE_HOME

– TNS_ADMIN


– CTL_SNMP_MAGENT_HOST

– CTL_SNMP_MAGENT_PORT

Starting, stopping, or restarting selected BRM components

To start, stop, or restart selected BRM components:

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

The Oracle BRM Suite page appears.

2. Click the Members tab.

A list of all the BRM components is displayed.

3. Select the components 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 components.

– Stop—Stops all the selected components.

– Restart—Stops and starts all the selected components.

Loading events into the BRM database

You use the Run utility to load Oracle BRM Rated Event (RE) Loader and Oracle BRM Universal Event (UE) Loader events to the BRM database.

To load events to the BRM database:

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


– To load the RE Loader events:

a. From the Search list, select Oracle BRM REL, and click Go.

b. Click the relevant REL component link.The Targets Home page appears.

c. Click Run.The Parameters page appears.

d. From the REL Mode list, select REL mode.e. In the Rated out file location box, enter the Rated output file

location.f. In the Rated out file name box, enter the Rated output file name.

– To load the UE Loader events:

a. From the Search list, select Oracle BRM UEL, and click Go.

b. Click the relevant UEL component link.The Targets Home page appears.

c. Click Run.


Oracle Corporation

The Execute UEL utility page appears.

d. In the Event Template Name box, enter the event template name.e. In the Event Log file box, enter the event log file name.

3. Click Ok.

The events are loaded to the BRM database.

Removing a component instance

To remove a component instance from the Management Service system:

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

A list of all the components is displayed.

2. Select a component and click Remove.

The selected component instance is removed.

Viewing the list of patches that have been applied to a component

To view the list of patches that have been applied to a component:

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

A list of all the BRM components is displayed.

2. Click a component instance.

The list of patches that have been applied to the selected component are displayed in the Patches Applied field.

Note Optional Managers that are applied on top of a base component such as Configuration Manager are displayed in the Components field.

Managing BRM groupsYou can create a customized group and associate similar BRM components like DM or CM, and monitor them.

Creating BRM groups

To define BRM groups:


2. In the BRM page, scroll to the Related Links section and click the Create custom group for monitoring link.

The BRM Custom group creation page appears.

3. In the Name box, enter a name for the group.


4. Click Add.


5. From the Target Type list, select a Target Type, and click Go.

The components are displayed.

6. Select the check box of the BRM component and click Select.

7. To add more components to the same group, repeat steps 4 through 6.

8. Select the check boxes of all the BRM components and click OK.

A group with the given name is created.

Note After creating a customized group, the status displays Pending on the BRM subtab page.

Monitoring BRM groups

To monitor BRM groups:


2. Click the componentgroup link you want to monitor.

where componentgroup is the name of the component group.

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

Uninstalling the BRM Application Management PackNote After uninstalling the BRM Application Management Pack from the

Oracle Management Service or Oracle Management Agent, the respective component (Management Service or Agent) needs to be restarted.

Removing components

Note You can uninstall the BRM Application Management Pack without removing the BRM components. The components will be accessible when you reinstall the BRM Application Management Pack.

You can remove the discovered components and component pages from the Oracle Enterprise Manager Grid Control console.

To remove the discovered components and component pages:

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

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

3. Repeat step 2 for all BRM discovered components.

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


Oracle Corporation

Uninstalling the Management Service Plug-in by Using Oracle Universal Installer

Note You must uninstall the Management Service plug-in on each system on which it is installed.

To uninstall the BRM Application Management Pack:

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 Oracle’s Management Service plug-in on multiple Management Service systems that use the same database repository, running the remove_dbch.pl script will remove the database changes for all the Management Service plug-ins. You should not remove the database changes unless you plan to uninstall all the Management Service plug-ins.

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

./runInstaller -invPtrLoc OMS_home/oraInst.loc


3. Click Deinstall Products.

4. Select OMS and click + to expand the list.

5. Select Application Management Pack for BRM.

6. Click Remove.


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

Performing a Silent Uninstallation of the Management Service Plug-in

To perform a silent uninstallation of the Management Service plug-in:


2. Make a copy of the oracle.sysman.plugin.comms.brm.managementpack.OMS.rsp file.

3. Open the oracle.sysman.plugin.comms.brm.managementpack.OMS.rsp file in a text editor.

4. Find the ORACLE_HOME entry and set it to the name of the path where the Management Service is installed.

For example:

ORACLE_HOME = "/home/oracle/OracleHomes/oms10g"


5. Find the ORACLE_HOME_NAME entry and set it to the name of the directory where the Management Service is installed.

For example:

ORACLE_HOME_NAME = "oms10g"

6. Find the ORACLE_HOST_NAME entry and set it to the name of the host where the Management Service is installed.

For example:


7. Find the db_usr entry and set it to the Enterprise Manager repository database related values.

For example:

db_usr = {"emrep.us.oracle.com","sysman","hello","localhost","1521","emrep"}

8. Save and close the file.

9. Go to OMS_home/oui/bin and enter the following command:

./runInstaller -invPtrLoc OMS_home/oraInst.loc -responseFile response_file_name -silent -deinstall


For example:

./runInstaller -invPtrLoc /home/oracle/OracleHomes/oms10g/oraInst.loc -responseFile "/home/oracle/response_files/oracle.sysman.plugin.comms.brm.managementpack.OMS.rsp" -silent -deinstall

The Management Service plug-in is uninstalled.

Uninstalling the Management Agent Plug-in

Note You must uninstall the Management Agent plug-in on each system on which it is installed.

To uninstall the Management Agent plug-in:

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

./runInstaller -invPtrLoc Agent_home/oraInst.loc


2. Click Deinstall Products.

3. Select Agent and click + to expand the list.


Oracle Corporation

4. Select Application Management Pack for BRM.

5. Click Remove.


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

Using Enterprise Manager Grid Control

To uninstall the Management Agent plug-in using Enterprise Manager Grid Control, follow these steps:

1. Schedule a job to uninstall the Application Management Pack for BRM.

For more information, see the Oracle Enterprise Manager documentation.

2. Enter the following command:

%emd_root%/oui/bin/runInstaller -invPtrLoc %emd_root%/oraInst.loc -responseFile %emd_root%/setup/scripts/oracle.sysman.plugin.comms.brm.managementpack.Agent.rsp -silent -deinstall

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

Performing a Silent Uninstallation of the Management Agent Plug-in

To perform a silent uninstallation of the Management Agent plug-in:


2. Make a copy of the oracle.sysman.plugin.comms.brm.managementpack.Agent.rsp file.

3. Open the oracle.sysman.plugin.comms.brm.managementpack.Agent.rsp file in a text editor.

4. Find the ORACLE_HOME entry and and set it to the path where the Management Agent is installed.

For example:

ORACLE_HOME = "/home/oracle/OracleHomes/agent10g"

5. Find the ORACLE_HOME_NAME entry and and set it to the name of the directory where the Management Agent is installed.

For example:

ORACLE_HOME_NAME = "agent10g"


6. Find the ORACLE_HOST_NAME entry and set it to the name of the host where the Management Agent is installed.

For example:


7. Go to Agent_home/oui/bin and enter the following command:

./runInstaller -invPtrLoc Agent_home/oraInst.loc -responseFile response_file_name -silent -deinstall


For example:

./runInstaller -invPtrLoc Agent_home/oraInst.loc -responseFile "/home/oracle/response_files/oracle.sysman.plugin.comms.brm.managementpack.Agent.rsp" -silent -deinstall

The Management Agent plug-in is uninstalled.


Oracle Corporation


Using the command line interface to run deployment procedures 3

About this documentThis chapter provides an overview of how to use the Oracle Enterprise Manager command line interface to run Oracle Communications Billing and Revenue Management deployment procedures.

OverviewTo deploy BRM components from the command line, you run the executeDP.pl script. Before you run the executeDP.pl script, you need to create and configure the .properties file, and upload the component_customer.values file of the component you want to deploy to the software library (where component is the BRM component).

When you run the script, you specify the following:

• RuntimeData XML Template. The RuntimeData XML template file provides configuration parameters required for executing a procedure. You can create the RuntimeData template file by modifying a RuntimeData.xml file from a previous run.

• Procedure Global Unique Identifier (GUID). Each deployment procedure is associated with a GUID.

• Procedure Instance GUID. Each deployment procedure that is run is associated with an instance GUID. This instance GUID is generated at run time and can be used to manage and monitor the execution of the procedure.

• Properties file. Each time you execute a deployment procedure, you must modify the configuration parameter values in the RuntimeData.xml file. Instead of manually editing the values in the RuntimeData.xml file, you can replace the values in the RuntimeData.xml file with variable names and provide the actual values in a .properties file.

• Procedure Execution scripts. You can use Perl scripts that are available in the OMS_home/emcli/scripts directory to execute the procedures using the command line interface (where OMS_home is the directory where the Oracle management service is installed).

Enterprise Manager command line interface requirementsBefore you use the Enterprise Manager command line interface, you must do the following:

• Set up the command line interface client.

Refer to Oracle Enterprise Manager Command Line Interface 10gRelease5 in the Oracle Enterprise Manager documentation.

• Download the procedure execution scripts, RuntimeData templates, and properties files to the machine where you set up the command line interface client.


Oracle Corporation

Executing the deployment procedure using the Enterprise Manager command line interface

To execute the deployment procedures using the Enterprise Manager command line interface:

1. Get the list of all deployment procedure types by running the following command:

emcli get_procedure_types

2. Find the procedure GUID of a deployment procedure type by running the following command:

emcli get_procedures -type="procedure_type"

where procedure_type is the deployment procedure type.

For example, to find the GUID of BRM Software Deployment Procedure, use the following command:

emcli get_procedures -type="brmprov"

3. Get the list of instance GUID for a given procedure, using the following command:

emcli get_instances -type="procedure_type"

For example, to find the instance GUID of BRM Software Deployment Procedure, use the following command:

emcli get_instances -type="brmprov"

4. Download RuntimeData, using the following command:

emcli get_instance_data_xml -instance=instance_guid

where instance_guid is the GUID instance.

For example,

emcli get_instance_data_xml -instance=74E9CF543B5A3231E040930AE1F81AD4

The following is a sample Runtime Data template for deploying a BRM component. You must provide the actual values of the variables in the .properties file.

<runtimeData xmlns="http://www.oracle.com/paf/runtimeDataXML"><elements><targetList name="hostBeingInstalled"><elements><target targetName="joust.us.oracle.com" targetType="host">


Oracle Corporation

<scalar value="DB_PASSWORD" classname="java.lang.String" name="dbPassword"/><scalar value="STORAGE MODEL" classname="java.lang.String" name="storageModel"/><scalar value="-" classname="java.lang.String" name="logfile"/><scalar value="HA_MODE" classname="java.lang.String" name="haMode"/></elements><jobCredRecord targetName="joust.us.oracle.com" targetType="host" setName="HostCredsNormal" userName="SYSMAN"><values credentialSetColumn="username" credentialValue="75379B22297F8C6FE040930AE1F844C9" encrypted="true"/><values credentialSetColumn="password" credentialValue="75379B2229808C6FE040930AE1F844C9" encrypted="true"/></jobCredRecord></target></elements></targetList><scalar value="Components/BRM Components/PortalBase_7.4_Linux" classname="java.lang.String" name="PortalBase_7.4_LinuxsrcLoc"/><scalar value="7.4_Portal_Base_linux_32_opt.bin" classname="java.lang.String" name="PortalBase_7.4_LinuxsrcFilename"/><scalar value="7.4_Portal_Base_linux_32_opt.bin" classname="java.lang.String" name="PortalBase_7.4_LinuxconfigTemplateLoc"/><scalar value="6.4_Portal_Base_linux_32_opt.bin" classname="java.lang.String" name="PortalBase_7.4_LinuxtemplateFilename"/><scalar value="SYSMAN" classname="java.lang.String" name="emuser"/></elements></runtimeData>

5. Create a .properties files.

The following sample .properties file contains the actual values for a DMO deployment for the sample RuntimeData template in the earlier section:

COMP_TYPE=oracle_brm_dmoSRC_FILE_NAME=7.4_Portal_Base_linux_32_opt.binSRC_LOC=Components/BRM Components/PortalBase_7.4_LinuxCONFIG_FILE_NAME=dmo_customer.valuesCONFIG_LOC=Components/BRM Customer Configuration/dmo_customer.valuesHOST=joust.us.oracle.comSWLIB_VERSION=0.2INSTALL_LOC=/export/u01/app/oracle/mei/DIT3/dmo_newBASE_TYPE=nullORACLE_HOME=/export/u01/app/oracle/OracleHomes0/db10gLOG_FILE_LOC=/export/u01/app/oracle/mei/DIT3/dmo_new/varTHIRDPARTY_LOC=/export/u01/app/oracle/ThirdPartySTAGE_LOC=/export/u01/app/oracle/mei/DIT3/dmo_new/stagingBRM_TYPE=prepaidVERSION=7.4COMP_NAME=dmo_new


SETUP_CREATE_PARTITIONS=NOENABLE_PARTITION=NOSETUP_DROP_ALL_TABLES=NOSETUP_INIT_DB=NOCREATE_DATABASE_TABLES=NOSYS_PASSWORD=-TABLES_GROUP=-INDEXES_GROUP=-DB_VERSION=10gDB_ALIAS=FU60.portal.comDB_VENDOR=oracleDB_USER=pinDB_PASSWORD=pinSTORAGE_MODEL=-HA_MODE=-

6. Upload the component_customer.values file to the software library.

For example, you must upload the dmo_customer.values file to the software library before you execute the dmo deployment procedure.

This is available in the PIN_home/staging directory.

Following is a sample dmo_customer.values file required for deploying the dmo instance dmo_new:

dmo_new.dm.dm_port 13005dmo_new.TNS_ADMIN /export/u01/app/oracle/OracleHomes0/db10g/network/admindmo_new.NLS_LANG American_America.UTF8dmo_new.dm.sm_oracle_ddl 1dmo_new.dm.dd_write_enable_fields 0dmo_new.dm.dd_write_enable_objects 0dmo_new.dm.dd_write_enable_portal_objects 0dmo_new.dm.dm_n_fe 4dmo_new.dm.dm_bigsize 2097152dmo_new.dm.dm_in_batch_size 80dmo_new.dm.dm_max_per_fe 16dmo_new.dm.dm_n_be 8dmo_new.dm.die_on_exception 1dmo_new.dm.dm_restart_children 1dmo_new.dm.dm_shmsize 33554432dmo_new.dm.dm_trans_be_max 4dmo_new.dm.dm_trans_timeout 0dmo_new.dm.encrypt_passwd 1dmo_new.dm.extra_search 0dmo_new.dm.stmt_cache_entries 32

7. Execute the following executeDP.pl script:

perl executeDP.pl -t template -p properties_file_name -g dp_guid


Oracle Corporation

[-s yyyy/MM/dd HH:mm]

[-z time_zone_id] [-d command_line_interface_directory_path ]

where

– -t template specifies the RuntimeData template for BRM procedures or the RuntimeData.xml file downloaded after a BRM procedure is executed.

– -p properties_file_name specifies the name of the .properties file created for executing the procedure.

– -g dp_guid specifies the GUID of the procedure that needs to be run.

– -s yyyy/MM/dd HH:mm specifies the time when the deployment procedure is scheduled to run. By default, the deployment procedure is executed immediately.

– -z time_zone_id specifies the time zone in which the deployment procedure is scheduled to run. By default, it is set to the time zone of the Management Service.

– -d command_line_interface_directory_path specifies the directory where the command line interface executable file resides. By default, the path is set to Oracle_home/oms10g/bin

For example:

perl executeDP.pl -t RuntimeData_dmo.xml -p dmo.properties -g 7537A17658CF4283E040930AE1F84AAF -s 2007/02/03 10:00 -z Americas/New_York -d /export/u01/app/oracle/OracleHomes0/oms10g/bin

Check the procedure execution status from the Procedure Completion Status page.

For additional commands, refer to Oracle Enterprise Manager Command Line Interface 10gRelease5 in the Oracle Enterprise Manager documentation.


Setting up a new BRM instance 4

About setting up a new BRM instanceThis document provides an overview of how to set up a new Oracle Communications Billing and Revenue Management (BRM) instance using Oracle Enterprise Manager Grid Control and the BRM Application Management Pack. A BRM instance is the BRM database, CM, DM, and Pipeline Manager put together. The set up can be deployed on multiple machines.

To understand how the BRM Application Management Pack works, see Using the BRM Application Management Pack to administer your BRM system.

Setting up a new BRM instanceTo set up a new BRM instance, you need to do the following tasks:

1. Deploy the BRM components by using the Oracle Enterprise Manager Grid Control console.

2. Configure the components in the order described below.

3. Start the components in the order described below.

Prerequisites

Before you set up a new BRM instance:

• Create BRM source components. See Creating BRM source components in the Oracle Software Library.

• Upload the source components. See Uploading BRM source components using the utility.

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

• Install the third-party software and SNMP software in the Agent machines. See Installing the Third-Party software and Installing the SNMP software.

Note

• The procedure below is a guideline. You need not deploy components that you might not use. For example, you need not install GSM Manager if you do not offer GSM services.

• Some BRM components require connection to the BRM database to complete installation and to start up the service. You can create the BRM database at the time of deploying or use an existing database with BRM schema. For more information, see Deploying BRM components with database creation.

• When you deploy BRM components from Oracle Enterprise Manager Grid Control, you need to provide configuration information through the deployment UI to configure and start up the BRM process. See Modifying the default configuration values for a BRM component and Modifying component configuration details.


Oracle Corporation

To set up a new BRM instance:

1. Deploy BRM Base components. See Deploying BRM Base components.

Note To deploy BRM components, see Deploying BRM components.

2. Deploy the following BRM optional managers: See BRM ISMP packages, installable, and base components.

– Account Migration Manager

– BRM Services Framework Manager AAA

– BRM Services Framework Manager

– GPRS AAA Manager

– GPRS Manager 3.0

– GSM AAA Manager

– GSM Manager

– Number Manager

– Resource Reservation Manager

– SIM Manager

3. Deploy TIMOS Data Manager.

Note The SNMP master agent should be running on the Agent machine before a TIMOS installation. If multiple components are running in the same machine, only one master agent is required.

4. Deploy Pipeline Manager.

– Deploy batch rating engine.

– Deploy real-time pipeline.

5. Deploy AAA Gateway Manager.

Deploy Diameter or HP OpenCall protocol.

6. Deploy and configure MultiDB Manager.

For more information on configuring MultiDB Manager, see Managing a multidatabase system in the BRM documentation.

7. Load events into the BRM database. See Loading events into the BRM database.

Configuring BRM

After deploying BRM components, you must configure them. To configure BRM components, see Modifying component configuration details.

Configure the components in the following order:

1. Configure the LDAP servers in HA mode.

2. Configure TIMOS DM to use HA Role Mediator.

3. Configure CMMP.

4. Configure the DMs.

5. Configure AAAGW.


Starting BRM components

To start BRM components, see Starting, stopping, or restarting individual BRM components.

Start the components in the following order:

1. dm_oracle

2. dm_email

3. dm_fusa

4. dm_invoice

5. dm_vertex

6. dm_ldap

7. dm_eai

8. dm_ifw_sync

9. dm_timos

10. cm

11. cm_proxy

12. cmmp

13. formatter

14. nmgr

15. infmgr

16. eai_js

17. answer

18. batch_controller

19. rtp

20. aaagw

21. bre


Oracle Corporation


BRM Plug-in Pages 5

About BRM plug-in pagesThis chapter describes the following Oracle Communications Billing and Revenue Management (BRM) plug-in pages:

• BRM page. See BRM page.

• Oracle BRM Suite System page. See Oracle BRM Suite System page.

• Oracle BRM Suite Service page. See Oracle BRM Suite Service page.

• Oracle BRM Suite page. See Oracle BRM Suite page.

• Oracle BRM Component’s home page. See Oracle BRM component home page.

• Host’s home page. See Host’s home page.

Note Oracle BRM Suite System, Oracle BRM Suite Service, and Oracle BRM Suite are displayed if you have already deployed BRM components or initiated guided discovery to find and register BRM components. See Deploying BRM components, Adding BRM components using guided discovery, and Adding SNMP components using guided discovery.

BRM page

The BRM page appears as one of the subtabs in the Targets page if it has been added to the list of subtabs. For more information about adding the BRM subtab, see Adding the BRM subtab.

The BRM page displays a list of all the BRM components available on your managed hosts.

The BRM page lets you do the following:

• Deploy and uninstall BRM components

• Patch BRM components and roll back patches.

• Configure or delete BRM components displayed in the BRM page.

• Create custom groups for monitoring.

• Initiate guided discovery to find and register BRM components.

• Edit default configuration.

BRM Plug-in Pages 101

Oracle Corporation

Oracle BRM Suite System page

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 information about targets of the BRM system, without the need to navigate to individual BRM components to check on availability and performance. You can view the entire system on a single screen and obtain detailed information.

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.

• Drill down for more detailed information.


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


Oracle Corporation

For more information about the Related Links section on the Oracle BRM Suite System page, see the discussion of the system’s home page in the Oracle Enterprise Manager online Help.

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:

Policy Violations Shows how many of the BRM components 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 the discussion of managing policy violations in the Oracle Enterprise Manager online Help.

Security Policy Violations

Shows how many of the BRM components 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 the discussion of managing policy violations in the 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 the 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 the discussion of confuring the history page in the Oracle Enterprise Manager online Help.

Section Description


• 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 the discussion of system page administration in the Oracle Enterprise Manager online Help.

Oracle BRM Suite System (Components tab)

The Components tab on the Oracle BRM Suite System page summarizes information about the BRM components 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 the discussion on creating, editing, and viewing systems in the Oracle Enterprise Manager online Help.


Oracle Corporation


Oracle BRM Suite Service page

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

Oracle BRM Suite page

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 Corporation

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 components 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 specific BRM processes.


For more information about starting, stopping, and restarting BRM components, see BRM error codes monitored by Oracle Enterprise Manager.

Oracle BRM component home page

A BRM component’s home page displays information about the general health of a component. It shows the following information for the component: status, availability, instance type, home, log directory, component name, component type, parameters, port, version, patches applied, optional managers information, and the target machine on which the component is installed. This page also lists the alerts that are triggered for this component.

The component home pages contain two subtabs—Home and Performance. The home page displays the process status, alerts, ECM links, general link, and process control buttons. The performance pages contain the graph to display the process performance.


Oracle Corporation

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

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 component’s availability; whether the BRM component is in up, down, or unknown state. The Up arrow shows that the component is up and running and the Down arrow shows that the component is not available.

BRM components 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 component.

Stop Stops the BRM component.

Restart Stops and then restarts the BRM component.


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 the discussion of viewing a configuration page in the Oracle Enterprise Manager online Help.

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

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

Availability Shows the percentage of time, excluding any blackouts, that the BRM component 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.

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.

Common elements Description


Oracle Corporation

For more information about these links, see the 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.

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.

Links Purpose


Oracle Corporation


BRM error codes 6

About BRM codesThis chapter provides the details and a brief description of the Oracle Communications Billing and Revenue Management (BRM) errors, error codes, and error messages.

BRM error codes monitored by Oracle Enterprise ManagerThe following table shows the BRM-related errors monitored by Oracle Enterprise Manager and a brief description of the errors.

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

BRM error codes 115

Oracle Corporation

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

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 Target Description


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

BRM error codes 117

Oracle Corporation


brm application management pack · † brm system architecture in the brm documentation. † brm...

Documents