Databases Reference
In-Depth Information
Master and template application
Create a master application that contains publishable shared components such
as authentication schemes, authorization schemes, lists of values, and templates.
Changes can be pushed from the master application to all subscribing applications.
Other applications will reference the standard templates by subscribing to the
master application.
To make newly created applications subscribe to the master application, we need to
create a template application. Create the template application as a copy of the master
application and change the subscription of all the shared components to reference
the master application. To change the subscription of multiple templates, you can
replace templates in this application with templates from another application. This
can only be done for currently used templates. Another option is to delete templates
and recreate them as a copy (and subscribe) from the master application. The
remaining templates and shared components can be modiied manually.
The template application is also the place where Page Zero is added.
In more complex situations, the master can have more than one theme or more
variants of shared components. We can then create more than one template—which
serve as a starting point for the applications.
To create a new application, we simply need to make a copy of the template
application. Because the new application is a copy, all the subscriptions to the
master application are also copied. For the shared components, it's always possible
to unsubscribe. To unsubscribe from multiple templates, the
Unsubscribe Templates
option from the
Task
menu can be selected.
Login application—optional
When more than one application in the workspace share the same authentication,
we can extend the framework with an application dedicated to the authentication
process. This application will handle the login and can serve as a starting menu for
the other applications.
We can create this login application as a copy of the template application. The
authentication of this application is different than the other applications. Here we
create the actual authentication schema, which we want to use in all our applications.
When switching between applications without having to log in again, we need
to share the session state between the applications. To do so we have to give
the session cookie the same name. We do that in the authentication schema of
the master application.
