1 if the Functional Alias is connected to a pool and that pool can be pinged.

The number of connections currently being used. (TotalConnections - AvailableConnections)

Current number of available unused JDBC Connections

Minimum number of connections the pool must keep open at all times. If you use this pool alias for more than one function, each pool instance keeps the specified number of connections open. For example, if you specify keeping at least 3 connections open, and the IS Core Audit Log and the Document History database components both use this pool, the pool keeps a total of 6 connections open - 3 for the IS Core Audit Log pool instance and 3 for the Document History pool instance.

Maximum number of connections the pools can have open at one time. Calculate this value as part of the total possible number of connections that could be opened simultaneously by all functions and applications that write to the database. Make sure the total number does not exceed the database's connection limit. If one of the applications opens more connections than the database allows, the database will reject subsequent requests for connections from any application. To continue the previous example, if Trading Networks also writes to the database and has a pool that could open up to 5 connections, you could specify only 17 as the maximum number of connections for the current pool. The IS Core Audit Log pool instance could use up to 17 connections, and the Document History pool instance could use the remaining 5 connections.

The total number of currently active connections.

Percentage of Connections currently in use (AssignedConnections / TotalConnections).

When the available connections reach the specified percentage, a warning is issued in Integration Server.