Logging from the Omnissa Access service and the Omnissa Access connector components are available using syslog. The Integration Broker component logs locally. The logs can be collected and reviewed on the server or through a central logging service such as vRealize Log Insight or Splunk. For Omnissa Access connector log-file information, see the Installing Omnissa Access Connector guide.
Omnissa Access Service Logging
Log Locations
Most service logs are located at Please contact Support for the correct input..
| Log | Purpose |
|---|---|
| greenbox_web.log | Log which contains all user interface interactions for web and mobile |
| horizon.log | Omnissa Access service log which includes Identity Adapters, RabbitMQ, OpenSearch, Ehcache, and other subsystems |
| cert-proxy.log | Omnissa Access service CertProxy component for Android Mobile SSO |
| configurator.log | Requests that the Configurator receives from the REST client and the Web interface |
| Please contact Support for the correct input. | A record of output messages related to update requests during an upgrade of Omnissa Access |
| Please contact Support for the correct input. | The files in this directory are useful for troubleshooting. You can find these files on all virtual machines after an upgrade. |
| catalina.log | Apache Tomcat records of messages that are not recorded in other log files |
| /var/log/journal/<logfoldername> | iOS KDC logs for Mobile SSO To retrieve the logs for iOS KDC, run Please contact Support for the correct input.. |
Syslog Server Setup
To set up a syslog server, see Configure Syslog Servers for Omnissa Access
Was this page helpful?