Administering Oracle Number Portability

This section presents information on task-based procedures required for ongoing system maintenance, and includes information on administration tools and utilities. The chapter covers the following topics:

This chapter covers the following topics:

Resubmitting an Order

You use the Resubmission Utility to re-run orders that have been previously submitted to Oracle Service Fulfillment Manager provisioning engine. This is useful, for example, if a network switch fails, or experiences service disruption that causes a provisioning order to fail. The order, however, has not been lost by the system, and can be resubmitted when the unit becomes available.

For example, a particular fulfillment element fails at 3:02 a.m. on a particular date. It remains unavailable for service until 5:20 a.m. the same day. This fulfillment element was to be used to provision a number of orders during that span of time, but as it was unavailable, the orders failed to complete. After the fulfillment element (or its replacement) becomes available, it is necessary to resubmit all orders that were to be provisioned by that particular fulfillment element during the window of time from 3:02 to 5:20 a.m. The order information is not lost, and can be re-used to resubmit the original provisioning orders.

You use the Resubmission Utility to perform the following tasks:

For instructions, refer to the Oracle Service Fulfillment Manager documentation.

Managing System Queues

You perform a number of tasks with system queues. These include:

Use the Queue Console window (Navigator window > Functions (tab) > Administration > Queue Console) to perform these tasks. For instructions, refer to the Oracle Service Fulfillment Manager documentation.

Managing Network Connections

Use the Connection Manager (Navigator window > Functions (tab) > Administration > Connection Manager) to manage all types of fulfillment elements and their network adapters. You can also use the Connection Manager to control network connections.

The Connection Manager allows you to perform the following tasks:

For instructions on performing these tasks, refer to the Oracle Service Fulfillment Manager documentation.

Oracle Number Portability Start and Stop

Application Start and Stop are mutually exclusive processes. If one is pending, the opposite operation does not proceed until the first finishes. In addition, the Oracle Provisioning Concurrent Manager processes must be up and running. Note that you set the number of running dequeuers through the Queue Console (Navigator window > Functions (tab) > Administration > Queue Console).

Start

Application Start (Navigator window > Functions (tab) > Administration > Application > Start) is a concurrent request that is performed by the Oracle Provisioning Concurrent Manager. You use the Application Start process to perform the following tasks:

The system automatically starts all the dequeuers and the Controller during the start process. If any dequeuers are already started, the number actually running is first determined, and matched against the number that are required to be started. The system automatically starts as many dequeuers as needed.

For instructions on performing the tasks, refer to the Oracle Service Fulfillment Manager documentation.

Stop

Application Stop is a concurrent request that is performed by the Oracle Provisioning Concurrent Manager. You use the Application Stop process to perform the following tasks:

For instructions on performing these tasks, refer to the Oracle Service Fulfillment Manager documentation.

Recompiling Fulfillment Procedures

Use the Recompile Fulfillment Procedure window (Navigator window > Functions (tab) > Administration > Recompile Fulfillment Procedures) to perform the following tasks:

For instructions, refer to the Oracle Service Fulfillment Manager documentation.

Purging Transactional Data

Oracle Number Portability is an event-based application. It uses Oracle Advanced Queue and Oracle Workflow extensively in order to facilitate the asynchronous communication required by the business processes. A large number of events are recorded in the system, and the numbers grow with time. Once an event expires, or the associated host objects such as orders have been processed or canceled, the record may be purged from a transactional database.

The Purge window (Navigator window > Functions (tab) > Administration > Purge) in Oracle Number Portability allows you to selectively purge transactional data recorded in Oracle Service Fulfillment Manager. This utility helps you to better serve business needs without impeding transactional performance.

A set of predefined business areas are available for purging. In Oracle Number Portability, the following data parameters are defined in the purging utility:

Note that the data parameter SOA, defined in the purging utility, is exclusive to Oracle Number Portability. See Service Order Administration for more information.

For instructions on purging obsolete data, refer to the Oracle Service Fulfillment Manager documentation.

Validating System Configuration

You use the Configuration Diagnostics tool to validate the existing system configuration. The validation process consists of two levels:

Error indicates the items that must be corrected for the system to work as expected.

Warnings indicates potential problems, but which in some case, are acceptable.

Tip: It is recommended that you run this utility after any major change in the system configuration.

Prerequisites

None

To validate the existing system configuration:

  1. From the NP System Administrator Navigator window, use the following navigation path to launch the Configuration Diagnostics page:

    Functions (tab) > Diagnostics > Configuration.

    This action dynamically executes a validation tool that returns information on the validity of the system configuration

  2. Close the browser window to exit this diagnostics page.