This is to help validate the number of connections made to an Oracle E-Business Suite (EBS) server at one time.
- Okta Access Gateway (OAG)
- Oracle E-Business Suite (EBS)
- Server Connections
- Socket (A Logical Connection)
How the agent works and connects
The OAG server uses an ebs-ssoagent that connects to the EBS server. This agent queries the database to validate the user for each authentication attempt. If the agent is started, no connections will be made to the EBS server until the very first authentication attempt is made by the user. Below are the default parameters for the agent (Typically, the total connections seen will mimic the "spgw.ssoagent.datasource.MaxLimit= " value).
spgw.ssoagent.datasource.MaxLimit=5 (This indicates the max number of connections to each ebs server per ebs application)
spgw.ssoagent.datasource.InitialLimit=2 (This indicates the initial number of connections to each ebs server per ebs application)
spgw.ssoagent.datasource.connTimeout=10000 (This property specifies the maximum number of milliseconds that the pool will wait for a connection to be established before throwing an exception.)
spgw.ssoagent.datasource.leakTimeout=30000 (This controls how long a connection can be outside of the pool before a potential leak is logged in milliseconds)
Setting the application to inactive will not close the connections that the ebs-ssoagent has made to the EBS server. They will stay active. If connections are closed on the EBS server, the ebs-ssoagent will just keep trying to connect and establish connections. To check the status,start, stop, or restart the agent, the command can be run from the shell of the OAG server.
Select only one option: status, start, stop, or restart. Stopping or restarting will interrupt all authentication attempts that users are trying since the connections will not be established. No active sessions will be affected.
sudo systemctl status|start|stop|restart ebs-ssoagentMore information on how the authentication process works can be found in How OAG Authenticates Users to EBS.
Checking Connections on the Okta Access Gateway
The following steps can be used to access the shell of the OAG server:
- Once in the OAG shell, the following commands can be run to show the network sockets that are created.
- Checking based on the EBS server IP:
sudo ss -an | egrep 'EBS_ip|EBS_ip1' | wc -l- Below is an example (The number is the total sockets created):
sudo ss -an | egrep '192.168.4.123|172.30.8.92' | wc -l 5
- Below is an example (The number is the total sockets created):
- Checking based on the EBS server port used.
- Access the EBS application through the admin UI and view the DBC contents.
- To find the port defined, find where it says "(PORT\= 1234". This is the port that is configured.
- Use this port in the grep search ( "| wc -l" counts the lines, which will give a number of sockets).
sudo ss -an | grep 1234
- Access the EBS application through the admin UI and view the DBC contents.
- Checking based on the EBS server IP:
Checking Connections on the EBS Server
This should be done by the EBS administrator:
- Access the EBS server through an SSH session.
- Check the physical connections with the ss utility (replace oag_ip with the IP address of the OAG server|s).
ss -an | egrep 'oag_ip|oag_ip1|oag_ip2' | wc -l
