The type that determines the deployment size for the installation.

• For an Avaya Oceana® deployment that supports up to 4500 active agents, select 3X Large.

• For an Avaya Oceana® deployment that supports up to 2000 active agents, select Extra Large.

• For an Avaya Oceana® deployment that supports up to 1000, 500, or 250 active agents, select Large.

• For an Avaya Oceana® deployment that supports up to 100 active agents, select Small.

The locale or language for the installation.

The attribute that enables or disables the secure communications across the clusters in the installation.

For Https-only and wss-only connections across the clusters, select Enabled.

This is used to allow requests to access resource end-points, even if there is no Authorization token. Set to false if all clients must have an Authorization Token

To set this attribute, select Avaya Oceana® Cluster 1.

The cluster that hosts Context Store services.

To set this attribute, select Avaya Oceana® Cluster 1.

The cluster that hosts the CoBrowse service.

To set this attribute, select Avaya Oceana® Cluster 4.

The cluster that hosts Omnichannel Provider services.

To set this attribute, select Avaya Oceana® Cluster 3.

The cluster that hosts the CustomerManagement service.

To set this attribute, select Avaya Oceana® Cluster 1.

The cluster that hosts the BotConnector service.

• For an Avaya Oceana® deployment that supports up to 100 active agents, select Avaya Oceana® Cluster 1.

• For an Avaya Oceana® deployment that supports up to 4500, 2000, 1000, 500, or 250 active agents, select Avaya Oceana® Cluster 2.

The cluster that hosts Unified Agent services.

• For an Avaya Oceana® deployment that supports up to 100 active agents, select Avaya Oceana® Cluster 1.

• For an Avaya Oceana® deployment that supports up to 4500, 2000, 1000, 500, or 250 active agents, select Avaya Oceana® Cluster 2.

The Fully Qualified Domain Name or IP of the cluster where Authorization Service is installed.

The first cluster that you want to monitor through OceanaMonitorService.

To set this attribute, select Avaya Oceana® Cluster 1.

The second cluster that you want to monitor through OceanaMonitorService.

To set this attribute, select Avaya Oceana® Cluster 2.

The third cluster that you want to monitor through OceanaMonitorService.

To set this attribute, select Avaya Oceana® Cluster 3.

The fourth cluster that you want to monitor through OceanaMonitorService.

To set this attribute, select Avaya Oceana® Cluster 4.

The fifth cluster that you want to monitor through OceanaMonitorService.

Do not select any value for this attribute.

The attribute that enables or disables EASG authorization for the Oceana Monitor.

• To enable EASG authentication, keep the default value true.

• To disable EASG authentication, select false.

Restart the snap-in for the changes to reflect.

If the Avaya Oceana® deployment has the Voice Channel feature, select true.

If the Avaya Oceana® deployment has the Video Channel feature, select true.

If the Avaya Oceana® deployment has the Chat Channel feature, select true.

If the Avaya Oceana® deployment has the Email Channel feature, select true.

If the Avaya Oceana® deployment has the SMS Channel feature, select true.

If the Avaya Oceana® deployment has the Social Channel feature, select true.

If the Avaya Oceana® deployment has the Generic Channel feature, select true.

If the Avaya Oceana® deployment has the Asynchronous Messaging Channel feature, select true.

If the Avaya Oceana® deployment has the Customer Journey feature, select true.

If the Avaya Oceana® deployment has the Reporting feature, select true.

If the Avaya Oceana® deployment has the Outbound Channel feature, select true.

If the Avaya Oceana® deployment has the Automation feature, select true.

The geo-redundancy mode for this system. For a standalone deployment, set this to Standalone. For a geographical disaster recovery deployment, set this attribute to Geo Primary on the primary site, and Geo Secondary on the secondary site.

A mandatory attribute configured on a geographical disaster recovery deployment.

Certificate name of the geo-redundancy keystore.

The password of the geo-redundancy keystore.

The name of the Voice provider (Type:CM) that you plan to configure in Avaya Control Manager.

The IP address of the Application Enablement Services server that you plan to connect to Communication Manager through a TSAPI link.

If two instances of Application Enablement Services are used for HA, click the plus sign (+) and add the second instance of Application Enablement Services.

The name of the Communication Manager switch connection that you plan to configure on Application Enablement Services.

If two instances of Application Enablement Services are used for HA, the same name must be configured for both instances.

The user name of the Application Enablement Services account.

If two instances of Application Enablement Services are used for HA, the same user name must be configured for both instances.

The password of the Application Enablement Services account.

If two instances of Application Enablement Services are used for HA, the same password must be configured for both instances.

The FQDN or IP address of Omnichannel Database.

The user name for Omnichannel Database.

The default user name for Omnichannel Database is mmJava.

The password for Omnichannel Database.

The default password for Omnichannel Database is mmJav.

The attribute that toggles a secure connection to Omnichannel Database.

To set this attribute, select true.

The Fully Qualified Domain Name or IP address of the Omnichannel Provider (OCP).

The number that you plan to configure in Engagement Designer Event Mapper to trigger the Web Voice workflow.

The number that you plan to configure in Engagement Designer Event Mapper to trigger the Web Video workflow.

The FQDN of Avaya Aura® Web Gateway.

The location of the shared network folder that all Unified Agent clients can access to upload the logs when the agents select the Upload option.

Unified Agent clients are the clients that are running remotely on the agent’s computer.

The Avaya Aura® Device Services (AADS) FQDN, which the Avaya Workspaces address book uses to search for enterprise directory contacts using LDAP.

The attribute that specifies how the Context Store data is stored in the EDM.

For more information, see the External Data Mart persistence section in the Avaya Context Store Snap-in Reference guide.

The options are:

• Audit: Enables persistence of Audit context data to EDM.

• Journey: Enables persistence of Customer Journey and Context Resurrection related data to EDM.

The type of the EDM database.

The available value for both upgrading to Avaya Oceana® Release 3.8 and new Avaya Oceana® Release 3.8 deployment is Microsoft SQL Server.

The FQDN of the EDM database.

The port number of the EDM database.

The name of the EDM database.

The user name of the EDM database.

The password for the user specified in the External Data Mart Username attribute.

Specifies if communications between the Context Store and the EDM should use a secure connection.

The default value is true.

The version of TLS to use when connecting to EDM.

The supported versions are:

• TLSv1.2

• TLSv1.1

• TLSv1.0

When you set this attribute to true, External Data Mart (EDM) stops storing the following types of data:

• Any digits collected during self-service

• Custom data entered in the in the Data field.

EDM stops storing these types of personally identifiable data to comply with data privacy laws.

The attribute that enables or disables the deletion of completed instances.

For Avaya Oceana®, select true.

The attribute that enables or disables the inclusion of Avaya Aura® Media Server.

To configure Avaya Oceana® for Web Voice/Video, select true.

A comma separated string of BotConnector Site IDs in the Site Id:Friendly Name format.

The name of the first MessagingConnector snap-in service.

The database key for the first snap-in account, which is obtained after setting up data in Omnichannel Database. For example, if you set this attribute for SMS, you must enter the name of the snap-in that you create while configuring the SMS gateway.

The cluster that hosts the first MessagingConnector snap-in service.

The name of the second MessagingConnector snap-in service.

The database key for the second snap-in account, which is obtained after setting up data in Omnichannel Database.

The cluster that hosts the second MessagingConnector snap-in service.

The name of the third MessagingConnector snap-in service.

The database key for the third snap-in account, which is obtained after setting up data in Omnichannel Database.

The cluster that hosts the third MessagingConnector snap-in service.

The URL of the cluster where the MessagingService is installed.

The Snap-in field configured in Omnichannel Database Administration client.

The user name for the Co-Browse database.

To set this attribute, type the user name as Cobrowse.

The password for the Co-Browse database.

To set this attribute, type the password as Oceana16.

The name of the Co-Browse database.

The attribute that enables or disables event notifications to be sent out to subscribed services. You must enable this attribute if you use Avaya Analytics™.

The FQDN or IP address of the POM server that is to be serviced by Outbound Connector.

The port number that the POM server uses to connect to Outbound Connector.

The attribute that enables the requests to access resource end-points without any authorization token.

To enable tokenless access, retain the default value true.

This feature is available for Avaya Oceana® mode only.

The attribute to enable the maintenance mode.

The supported values are true and false. The default value is false.

This feature is available for Avaya Oceana® mode only.

The attribute to enable or disable Avaya Oceana® support for ZangSmsConnector.

The attribute used for polling the Avaya Oceana® SMS snap-in for accounts information.

This attribute is mandatory to support the Oceana mode.

The Avaya Oceana® cluster that hosts the MessagingService snap-in.

This option is mandatory for the Oceana mode.

The name of the MessagingService snap-in.

This option is mandatory to support the Avaya Oceana® mode.

The cluster that hosts the CustomerControllerService.