14.01.2013 Views

Oracle JHeadstart Developer's Guide - Downloads - Oracle

Oracle JHeadstart Developer's Guide - Downloads - Oracle

Oracle JHeadstart Developer's Guide - Downloads - Oracle

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

You can right-mouse-click on the JhsModelCreate.sql, then choose Run in SQL*Plus, and<br />

then the database connection you want to run the script in.<br />

Attention: We recommend installing the <strong>JHeadstart</strong> tables in the same schema<br />

as your own application tables. If you nevertheless prefer to install the<br />

<strong>JHeadstart</strong> tables in a different database schema, then you need to ensure that<br />

your application schema has full access to the <strong>JHeadstart</strong> tables and synonyms<br />

with the same name as the table name. This is required because the <strong>JHeadstart</strong><br />

runtime accesses the database tables through View Object usages defined in<br />

application module JhsModelService. When generating your application<br />

while using one or more of the table-driven features, this JhsModelService<br />

application module is added as a nested usage to your own application<br />

module, thereby “inheriting” the database connection of its parent application<br />

module.<br />

Attention: The JhsModelCreate.sql script creates database tables for all tabledriven<br />

<strong>JHeadstart</strong> runtime features. Additional tables for dynamic menus,<br />

translations and flex items are also created. If you do not plan to use these<br />

other features you can create your own script that only creates the above<br />

tables and view, and the JHS_SEQ sequence that is used to populate the ID<br />

column in these tables.<br />

You can use your own security tables rather than the <strong>JHeadstart</strong> tables, if you prefer so.<br />

See section Using Your Own Security Tables for more information.<br />

The <strong>JHeadstart</strong> runtime includes predefined “hooks” where you can plug in your own<br />

security code to access your own security tables. The hooks to use depend on your<br />

security settings, and will be described in the next paragraphs.<br />

10.2.2. Generating Security Administration Pages<br />

If you generate your application with security settings that use one or more <strong>JHeadstart</strong><br />

database tables (see above), then as part of the generation run, a separate application<br />

definition SecurityAdminAppDef.xml is generated that can be used to generate the<br />

security administration screens. This application definition is only generated when it<br />

does not exist yet, so after it has been generated, you can make any changes you want<br />

using the Application Definition Editor, without loosing these changes when you<br />

regenerate your “own” application definition.<br />

<strong>JHeadstart</strong> Developer’s <strong>Guide</strong> Application Security 10- 9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!