5-2 Oracle Fusion Middleware Developers Guide for Site Studio for External Applications
+-- MySites.war +-- wcmtemplates
+-- WEB-INF +-- web.xml
+-- wcm-config.xml +-- weblogic.xml
wcmtemplates : Directory containing all local templates JSPJSPX files that are
registered in the wcm-config.xml file.
WEB-INFwcm-config.xml : The main Site Studio configuration file, which lists the
available sites, connection name, and other configuration settings.
WEB-INFweblogic.xml : Weblogic-specific file that holds the reference to the shared
Site Studio WAR library.
WEB-INFweb.xml : The standard JavaEE configuration file that lists out the servlets,
filters and security settings for the application.
5.2 Site Studio Technologies
Site Studio technology uses servlets, filters and tag libraries to deliver Site Studio sites via the deployed web application.
The examples in this section describe the default configuration for a single Site Studio site using the site ID MySite and is delivered via a Site Studio application called
MyApplication:
■
Section 5.2.1, Site Studio Servlets
■
Section 5.2.2, Site Studio Filters
5.2.1 Site Studio Servlets
These are the available Site Studio servlets:
■
SiteStudio Proxy Servlet : Proxies the content from Oracle Content Server to your
local application; allows the content server to be treated as a local resource within the domain, allows for single sign-on via identity propagation.
■
Initialization Servlet : Initializes the Site Studio libraries; does not handle any web
requests.
5.2.2 Site Studio Filters
These are the available Site Studio filters:
■
Mode Filter : Handles the determination of the mode of the current request. The
mode will either be Consumption, Contribution, or Design.
■
Site Filter : Delivers Site Studio web pages using the Site Studio URL syntax, based
on the associated project file in Oracle Content Server.
■
Proxy Filter : Proxies the content server content to allow for the content server UI
to be served from the local web application.
Mode Filter The mode filter listens for URLs which map to the contribution mode root
wcm-contrib or the design mode root wcm-design. If the first segment of the URL matches either of these URLs, the mode is set for the request and the
Site Studio Application Components and Technology 5-3
resource is then forwarded, without the first segment, to the web application for processing.
Site Filter The site filter allows for the processing of Site Studio URLs. Site Studio URLs are
hierarchical, based on the structure of the a project file. A typical Site Studio URL looks like mysiteaboutindex.html. For more information, see
Section 1.6, Understanding the Site URL Format.
Site Studio control flow:
1.
Site URL via the browser is requested: mysiteaboutindex.html
2.
Determine the current site ID and section.
■
Matches against urlPath in the wcm-config.xml file.
■
The site ID is set to mysite and site path set to aboutindex.html
3.
Instantiate a new SiteContext object and place it in the HttpServletRequest as an attribute named wcmContext.
4.
Determine the Page Template ID. In this case, page template is primary via the index.html file name.
5.
Lookup the template ID in the wcm-config.xml file to find the local JSPJSPX resource.
6.
Invoke RequestDispatcher to include and render the associated JSPJSPX page.
Proxy Filter The proxy filter proxies the content server content, using the local user ID, to enable
the Oracle Content Server user interface to be served from the local web application. This allows the web application to be integrated with Site Studio Contributor and the
Oracle Content Server user interface pages, which reside in the content server domain.
5.3 Using Site Studio Technologies in Your Integration
