Database Reference
In-Depth Information
By identifying the most-accessed pages, you can focus your attention on trying to
speed them up. Slow pages may require tuning, but if they're accessed infrequently,
you may not need to spend a lot of time on them.
Here are some other examples of uses for the activity log:
•
Top browsers
: If you build your application to support Firefox and IE and
then find that half your users are using Chrome, you may want to invest
some time ensuring that your application supports Chrome.
•
The time frame when people are using your application
: This gives you an
idea of the best time for maintenance and upgrades. You can also derive the
peak usage times.
•
Search criteria in interactive reports
: If there is a consistent search pattern,
perhaps you need a better report or preset filters.
Login Attempts
The APEX_WORKSPACE_ACCESS_LOG stores all the login attempts to your APEX
applications. The access log can be extremely useful when you're debugging user-au-
thentication issues.
An example of utilizing the access log is to monitor invalid login attempts. When a
user attempts to log in with invalid credentials, it's not recommended that you display
the exact reason why their login attempt failed. You don't want to tell the user the exact
reason because it could reveal valuable information, such as whether the user exists. It
may still be important for your operations team to know why a user wasn't able to log
in, in case they need to resolve the issue. Because all login attempts are stored in the
access log, for a failed login attempt you can see exactly why a user wasn't able to log
in.
Note
If you create your own authentication process, you should use the
APEX_UTIL.SET_AUTHENTICATION_RESULT and
APEX_UTIL.SET_CUSTOM_AUTH_STATUS procedures to ensure that you populate
the access log with meaningful messages. For more information on these authentication
procedures, please read the APEX API documentation.
