Avaya Breeze platform Snap-in log files

Last Updated : May 05, 2025 |

Each Avaya Breeze® platform node uses a WebSphere application server to host various SVARs (service archive files). The SVAR services provide the basic functional blocks of the Avaya Oceana®.

Some of Avaya Oceana®’s SVARs also include a GigaSpaces Processing Unit (PU).  A PU is the fundamental unit of deployment in the GigaSpaces In-Memory Computing Platform. The PU runs within a Processing Unit Container and is deployed onto the Service Grid. Once a PU is deployed, a PU instance becomes a run time entity.

The following table shows the Avaya Oceana®’s SVAR log files location:

Log name

Location

WebSphere Service

/var/log/Avaya/services/

GigaSpaces PU

/var/log/Avaya/dcm/pu/
Note:

If a SVAR has both Service and PU log files, the PU log file provides more diagnostic and troubleshooting information.

Each Avaya Breeze® platform node has a log file for all of the SVARs deployed on a cluster. If a cluster has two nodes, examine the log files on both nodes to troubleshoot the issue.

The following table lists the log file locations and services associated with them:

Cluster

Log name

Location

Services

1

GigaSpaces PU

/var/log/Avaya/dcm/pu

  • CallServerConnector

  • ContactCenterService

  • ContextStoreManager

  • UCAStoreService

  • UCMDataCollector

  • UCMService

  • WorkAssignmentManagerService

WebSphere Service

/var/log/Avaya/services/

  • CallEventControl

  • CallServerConnector

  • ContactCenterService

  • ContextStoreManager

  • ContextStoreQuery

  • ContextStoreRest

  • CustomerJourneyService

  • CustomerManagement

  • EngagementDesigner

  • EventingConnector

  • OCPDataServices

  • OceanaCoreDataService

  • OceanaMonitorService

  • OmniCenterProvisioningCollector

  • UCAStoreService

  • UCMDataCollector

  • UCMService

  • WAIMRestService

  • WorkAssignmentManagerService

  • CRMGateway

    Note:

    For a footprint of 100 agents deployment, CRMGateway is installed on Cluster 1, while for deployments that support more than 100 agents CRMGateway is installed on Cluster 5.

2

GigaSpaces PU

/var/log/Avaya/dcm/pu

  • UnifiedAgentContextService

  • UnifiedAgentController

WebSphere Service

/var/log/Avaya/services/

  • AuthorizationService

  • BotConnector

  • CallEventControl

  • EventingConnector

  • OceanaMonitorService

  • UnifiedAgentContextService

  • UnifiedAgentController

3

GigaSpaces PU

/var/log/Avaya/dcm/pu

  • AgentControllerService

  • EmailService

  • CustomerControllerService

  • OBCService

  • ORCRestService

    Note:

    For the ORCRestService SVAR, the services log file contains most of the useful information.

WebSphere Service

/var/log/Avaya/services/

  • AgentControllerService

  • AutomationController

  • CallEventControl

  • CustomerControllerService

  • EmailService

  • EventingConnector

  • GenericChannelAPI

  • MessagingService

  • OBCService

  • OceanaDataViewer

  • OceanaMonitorService

  • ORCRestService

  • SMSVendorSnapin

  • SocialConnector

4

WebSphere Service

/var/log/Avaya/services/

CoBrowse

5

WebSphere Service

/var/log/Avaya/services/

  • CRMGateway

  • ZangSmsConnector

    Note:

    For a footprint of 100 agents deployment, CRMGateway is installed on Cluster 1, while for deployments that support more than 100 agents CRMGateway is installed on Cluster 5.