Databases Reference
In-Depth Information
No Authentication : This is like a public web site. Users aren't prompted for any type of
authentication. This is useful for informational applications where the question
“Who are you?” isn't important.
Database Account : This option uses the Oracle Database schema usernames and passwords
for credentials. Some organizations use this type of database-driven authentication to keep
track of users. The application still executes as the chosen “parse as” schema, not as the
individual user in the database.
For simplicity, the default is to use the Application Express authentication scheme. This is the one setting that
provides login security; by default, the developer writing the application can log in without any additional work.
Many organizations have an existing method of authenticating users. if an ldap server is currently available
(such as oracle internet directory, Microsoft active directory for network domain authentication, or even an oracle
e-Business suite), you may want to use this system for apeX authentication. the number of options and methods are
beyond the scope of this topic. simply know that with the oracle database technology and the technology of your
application server, it's possible to use many of the most common authentication infrastructures.
Note
Selecting Tab Options
Tabs are a common navigational structure for web applications. They provide an intuitive interface for switching
subjects or general areas in an application. Three options are available:
No Tabs : This is a basic page style where no tabs are generated by the wizard and no tabs are
displayed by the page template. This is often selected for small applications or applications
where navigation is managed by a different method such as lists, buttons, or other template
constructs.
One Level Tabs : This is the most common style of tab layout; it's useful for small to mid-sized
applications where functionality needs to be separated yet easily accessible. This is also the
easiest type of tab style to manage.
Two Level Tabs : The construction of two-level tabs uses a parent tab construct and breaks the
standard tabs into tab sets. It's similar to having a controlling tab.
APEX supports up to two-level tabs in the display templates provided, and the wizard builds the shared
components for the tab set as part of the wizard. If you know your application's page outline and can lay it out during
the creation of the application, the wizard will do most of the tab setup. Designing the page at creation time can be a
big time saver if the application design calls for a significant number of tabs. In any case, you can create and modify
the shared component after the initial run of the Create Application Wizard.
Globalization Options
The authentication step in the wizard also includes six additional settings, as shown in Figure 5-13 . A few of the
settings have to do with the ability to translate the application to other languages. Multilingual applications are
beyond the scope of this topic, but for completeness the general usage descriptions of these options are included.
 
 
Search WWH ::




Custom Search