Advantages Of Erp; Processing Cycle; Connectivity - Lucent Technologies AP-3 User Manual

APS (Application Plus Server) 4.1 Users Guide

Advantages of ERP

Connectivity

Processing Cycle

350
This directory is a repository for all reports. The secondary APSs will not
house any reports generated by the ERP, but will hold any reports that
APS generates.
Batch processing includes creation of a billing report and several call
activity reports initiated by cron on a nightly basis. The reports are
generated primarily from a single table in an Informix database. The
database, an instance of which resides on each APS, is named "issg_db"
and the table, named cmd_jr_log, serves as a log of call activity
associated with an APS Inbound Call Completion (ICC) application. A
second table in issg_db, cmd_test_call, is used at some sites for billing
and contains only a minimal number of entries.
By off-loading the batch processing to the ERP, reporting is performed on
a dedicated processor, freeing the APS processors to perform other
functions. Additionally, a new database can be built on the ERP to house
only the cmd_jr_log and cmd_test_call tables (a merged version of these
tables in the case of a multiple-APS configuration) and indexing can be
built in to enhance performance.
The ERP system connects to the APS via a TCP/IP protocol. In small
configurations of 1 to 2 APS systems , the ERP Ultra 5 uses a 10/100
autosensing TCP/IP card to connect to a LAN switch. In a large
configuration of 3 to 4 APS systems, the ERP Ultra 2 uses the onboard
TCP/IP connection to go to the LAN switch.
ERP also allows remote access the ERP via rlogin or telnet.
For report processing to begin on ERP, all data must be successfully
transported from all APS systems.
In the ERP processing cycle, call activity data are taken from the APS
system(s) and merged on the ERP system. Report data are then processed,
and the reports generated are sent back to the primary APS.
A single report processing cycle contains the following phases:
n
Shortly after midnight, the root crontab on the ERP system starts
the erpmgr process.
n
erpmgr remotely spawns each APS system's apsmgr to initiate
unloading of the cmd_jr_log and the primary APS's cmd_test_
call table.
n
The resulting ASCII file(s) are transferred to the ERP.
n
The ASCII files are loaded into fresh cmd_jr_log and cmd_test_
call tables with indexing.
n
Reports are generated.
n
Reports are sent back to only the primary APS.
101-1830-001 Issue 1.0