Demand Profile Creation - Avaya CS7000 Administrator's Manual

9.4 suite release
Hide thumbs Also See for CS7000:
Table of Contents

Advertisement

Chapter 14: Administering the Avaya Data Services Client Application (DSCA)
LDAP attributes to query for name, telephone number, and e-mail searches are set in the DSCP
properties file. This file is in the same format as the Web Portal LDAP. It might possibly be
shared out to the Web Portal LDAP, to minimize configuration.
The LDAP search filter used to retrieve user data is "objectclass=<user account schema>". For
example, the default schema for active directory is 'user', so that the LDAP search filter is
"objectclass=user". The user account schema name is a configurable option for DSCA.
Communication with the LDAP server is done using an LDAP Client API. Communication to the
CRS database is done using the ODBC API, callling the standard Booking and Scheduling
database stored procedures.

Demand Profile Creation

Demand (conference) profiles are generated for each new Client added to the CRS database if
configured to do so.
Some of the details used to create this demand profile are taken from the DSCA configuration.
Other details are taken from the BSDefaults table found in the BSRes2 database.
Note:
Setting the DefaultEnabledInd to 0 on the BSDefaults table disables the creation
Note:
of demand profiles.
226
CS7000 System Administrator Guide for Release 9.4
January 2006

Advertisement

Table of Contents
loading

Table of Contents