1 ASAP Server Configuration Overview

This chapter provides an overview of Oracle Communications ASAP server configuration tasks.

Overview of ASAP Server Configuration Tasks

After you have installed ASAP and defined the initial user security, perform the following procedures to configure ASAP.

• Set up ASAP security. For more information, see ASAP Security Guide.

• Build custom service request processor (SRP) interfaces or use the Java SRP or C SRP emulator that ASAP provides. ASAP provides two mechanisms to configure SRP interfaces: the Service Activation Configuration Tool (SACT) and stored procedures. See "Configuring ASAP Servers" for more information.

• Configure network element processors (NEPs) and network elements (NEs). To configure NEPs, use the SACT. See "Configuring Network Element Processors, Resource Pools, and Devices" for more information. To configure NEs, see Oracle Communications Design Studio for Activation and ASAP Cartridge Development Guide.

• Deploy services. ASAP provides two mechanisms to configure ASAP services: the installCartridge script and Design Studio for Activation. For more information, see "Configuring ASAP Servers" and see ASAP Installation Guide.

• Configure Atomic Service Description Layer (ASDL) command routing options (see ASAP Cartridge Development Guide).

• Configure system events and alarms. For more information, see ASAP System Administrator's Guide.

• Tune ASAP by modifying configuration parameters. For more information, see ASAP System Administrator's Guide.

• Optionally configure remote servers. It may be necessary to configure ASAP to execute one or more of its processes on a separate, or remote, server. This can be done to improve performance (for example, to distribute processing loads) or because certain downstream interfaces or networks are not accessible from the machine where ASAP is running. For more information, see ASAP Installation Guide.

• Monitor ASAP using the asap_utils utility. For more information, see ASAP System Administrator's Guide.