|
1
|
Get the vCPU, memory, and hard disk space required for Microsoft SQL Server based on your Avaya Oceana® deployment size.
|
|
|
|
2
|
Deploy Avaya Control Manager and configure the Avaya Control Manager database SQL Server cluster.
|
See Installing Avaya Control Manager for Enterprise - Multiplex High Availability.
|
|
|
3
|
Create database tables for External Data Mart (EDM).
|
|
|
|
4
|
Create an optional non-system administrator user on the primary Avaya Control Manager SQL Server.
|
|
|
|
5
|
Create the EDM Advanced Availability Group on Avaya Control Manager SQL Server.
|
|
|
|
6
|
Create an optional non-system administrator user on the secondary Avaya Control Manager SQL Server.
|
|
|
|
7
|
Generate certificates from System Manager to secure the connection between Context Store and Microsoft SQL Servers.
|
|
|
|
8
|
Change the SQL server to use the new certificate by configuring MS SQL Server for forced encryption.
|
|
|
|
9
|
Enable Transparent Data Encryption (TDE) on EDM.
Note:
TDE is an alternative to using VMWare encryption when VMWare encryption is not possible. For example, a CPOD deployment.
|
|
|
|
10
|
Configure automated SQL Server Agent jobs.
|
|
|
|
11
|
Load a JDBC-compatible driver jar file, configure the driver on System Manager, and then install the driver on the Context Store cluster.
|
|
|
|
12
|
Configure the OceanaConfiguration and ContextStoreManager attributes in System Manager to enable connection from Context Store to EDM.
|
|
|