The InComm tab displays the status of the InComm Connection Service application running on the SC//AcuVigil™ edge security device (ESD). The application provides a secure connection for loyalty transactions between your InComm-approved POS and the InComm authorization server. Use this tab to check connection activity, review errors, and configure the application.
The tab shows the application's connection activity, error log, and settings for this site. For an overview of the application, see InComm CS.
Application description: "The InComm Connection Service app runs on Acumera's Merchant Gateway and securely and reliably connects IP-based POS systems to InComm's gateway to transmit and approve loyalty card transactions."
Note: "Merchant Gateway" in the subtitle is legacy wording stored in the application package. The service runs on the ESD. |
Supported ESD models: MG3, SG1v1, SG2v1
Layout
The InComm tab has a standard app header and three sub-views: Transactions, Error Log, and Settings. The default sub-view is Transactions.
Header
| Element | Description |
|---|---|
| App icon | InComm app icon. Decorative. |
| InComm Connection Service | App name / block title. |
| Subtitle | "The InComm Connection Service app runs on Acumera's Merchant Gateway and securely and reliably connects IP-based POS systems to InComm's gateway to transmit and approve loyalty card transactions." Static descriptor. |
| Version | Package version string. |
| Transactions | Link. Switches to the Transactions sub-view. |
| Error Log | Link. Switches to the Error Log sub-view. |
| Settings | Link. Switches to the Settings sub-view. |
Transactions sub-view
The default sub-view. Shows connection activity to the InComm authorization server.
Summary line
Connections — N connections in the last 24 hours
The count reflects connections in the rolling 24-hour window.
Activity by hour table
The Activity by Hour table shows an hourly breakdown of connection counts.
| Column | Description |
|---|---|
| Date | The date. |
| Hour | The hour of the day. |
| Primary Ingress | The number of connections routed through the primary ingress point during that hour. |
| Backup Ingress | The number of connections routed through the backup ingress point during that hour. |
TLS relay timestamp
At the bottom of the sub-view:
TLS Relay started <time> on <date>
This shows when the TLS relay on the ESD last started. A recent time means the relay restarted, for example after a reboot. The relay must be running for transactions to pass.
Error log sub-view
The Error Log (last 50) view shows the 50 most recent InComm application error log entries. When the log is empty, it shows:
No log data available.
This is the healthy empty state.
Settings sub-view
Note: Scale Computing manages these settings as part of the managed service. You can view them here. To request a change, contact Scale Computing Support: open a ticket in the SC//AcuVigil dashboard, email team@scalecomputing.com, or call (512) 687-7401. |
An info banner shows where the configuration comes from, for example:
Using company default configuration.
| Field | Type | Options | Tooltip or description |
|---|---|---|---|
| App Mode | Dropdown | Production, Test | Whether the site connects to the InComm production or test environment. |
| Auth Server IP Address | Text | — | "The IP address or FQDN of the Incomm Authorization server" |
| Auth Server Name | Text | — | "Should match the Common Name (CN) on the TLS certificate the server will tender" |
| Auth Server Port | Text | — | The port of the InComm authorization server. |
| Intercept Server IP Address | Text | — | The IP address the ESD intercepts POS traffic for. |
| Intercept Server Port | Text | — | The port the ESD intercepts POS traffic on. |
| Cipher | Dropdown | Automatic, TLS_RSA_WITH_AES_256_GCM_SHA384 | The TLS cipher used for the connection to InComm. |
| Update Settings | Button | — | Saves the settings and applies them to the ESD. |
Note: A settings change applies to the live site right away. A wrong server address or port stops InComm transactions. |
What to look for
- Connections count above 0 — confirms the application is passing transactions.
- Backup Ingress counts — connections on the backup ingress point can mean the primary ingress point wasn't available.
- TLS Relay started timestamp — a very recent time means the relay restarted. If this happens often, check the Error Log.