The data collected shows the number of active users on both Full and Self Service Connections. The only difference is the way the data is gathered for the Full Service connection.
In some environments the FND_LOGINS.TERMINAL_ID isn't being populated for FORMS connections that are initiated with a direct Jinitiator session, and/or more rarely, some environments don't populate the FND_LOGINS.PID column.
There are two main ways to launch into Forms:
The first is via a specific URL, like http://host:port/dev60cgi/f60cgi, that launches the Jinitiator. This will place records in the FND_LOGINS table which will then be picked up as Full Service Users in our SQL.
The second is using a Personal Home Page, or PHP, that always logs a record to the ICX_SESSIONS table, but no record to FND_LOGINS unless there is a navigation to a Forms based page that uses the Jinitiator.
In version 1.1.3 we use a separate second query in conjunction with the one used up until now. If the initial query returns zero for the Connected_Users (Full Service), the agent then runs the second query. If it returns rows for the connected_users.current_users, then the result set from the second query is returned to the agent tables; otherwise, it will revert back to the result set from the first query.
Additional Environment Details:
Foglight version: 4.2
Foglight Server OS: All
Foglight Client OS: All
Application version: Oracle 11i
Agent name: Oracle Ebus
Agent version: 1.1.1 & 1.1.3