Database Reference
In-Depth Information
Figure 12-6. Register New Application functional screen
The Application ID is really just a name for the application—a way to refer to it in the database. The
primary use for the application ID is as one of the keys to select the proper secure Application Role. The
other key is the name of the Application User (proxy user). These three data elements are what we insert
into the appsec.v_application_registry view.
At the bottom of the screen, there are three fields that make up the definition of an application inner
class. The first field is the package, then the Class name, and finally the InnerClass name. We will create
an instance of that class locally and submit it to Oracle in order to create a placeholder in the
appsec.v_app_conn_registry view for a list of connection strings for this new application. In order for
that entry to be made in appsec.v_app_conn_registry , a representative class needs to exist on the Oracle
database.
There is an optional button on the Register New Application screen that appears if the user types
“Login” into the Class field. In that case the Create App Class on Oracle From Login Template button
 
Search WWH ::




Custom Search