Oracle JHeadstart Developer's Guide - Downloads - Oracle

Before you generate the SecurityAdminAppDef you might want to inspect the file
locations properties, and change them if you have set other naming standards for these
properties.
The default settings are in line with what we recommend:
• Generate all Main faces-config files in the WEB-INF directory with a suffix
indicating the service
• JhsCommon-beans.xml is shared by all services (application definitions); the
location should never be changed.
• Create a subdirectory per service for the generation of group beans faces
config files, pages and regions. Make a subdirectory under this “service”
directory for each of these file types.
• The View Package property should be the same across all services
• The Resource Bundle Type and NLS Resource Bundle properties should be
the same across all services.
Note that all service-level properties that are generally the same across all services have
got the same values as in your “own” application definition. If you later on decide to
make changes to these settings in your own application definition, then you will need to
make the same change in the SecurityAdminAppDef Application Definition.
As you can see in the above screen shot, the generated SecurityAdminAppDef file
contains groups to maintain all JHeadstart security tables. Depending on your security
settings, you may delete groups that maintain tables you will not use:
• You can remove the Users, UserRoleGrants and RoleUserGrants groups if you
use Authentication Type “JAAS” and Authorization Type “JAAS”.
• You can remove the PermissionsLov, Permissions, and RolePermissionGrants
groups if you unchecked the Authorize Using Group Permissions checkbox.
Now, if you are satisfied with the settings, you can run the JAG for the
SecurityAdminAppDef.
10 - 10 Application Security JHeadstart Developer’s Guide