5-14 Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite
5.6.2 Setting Default Project Document Information
When you create a new web site in Site Studio, a new project file is created and checked into Oracle Content Server for you. Before you can create web sites, you must
specify the metadata that will be assigned to the new project files. You do this on the Set Default Project Document Information page in Oracle Content Server.
To set the default project document information: 1.
Log in to Oracle Content Server as an administrator.
2. Go to the Administration page, and click Site Studio Administration.
The Site Studio Administration page is displayed.
3. Click Set Default Project Document Information.
This option displays the Set Default Project Document Information page, where you can assign the default metadata for new projects generated by Site Studio.
4. Set the metadata as required, and click Update when you have finished.
This button returns you to the Site Studio Administration page.
5.6.3 Setting Default Metadata for Web Site Assets
Site Studio web sites created by Site Studio for External Applications in Oracle JDeveloper need their default metadata set in Oracle Content Server. You can set this
default metadata on the Set Default Web Asset Document Information page, available through the Oracle Content Server Administration tray or menu under Site Studio
Administration
. For information about setting default metadata for Site Studio web site assets, see
Section A.8, Set Default Web Asset Document Information Page, in Oracle Fusion Middleware Administrator and Managers Guide for Site Studio.
5.6.4 Configuring Zone Fields
The Site Studio component uses several metadata fields that are added to Oracle Content Server. If you do not use Oracle Text Search, some of these fields must be
configured as zone fields to ensure that they are full-text indexed.
Make sure that the DBSearchContainsOpSupport component is enabled on Oracle Content Server. This component ensures that the zone fields are full-text indexed,
which is required for Site Studio sites to work correctly. If this component is not enabled, you should enable it with the Component Manager, as described in
Section 5.6, Enabling and Configuring Site Studio on Oracle Content Server. Configuring zone fields is configuring Site Studio metadata fields as zone fields. Make
sure that the zone fields are configured as follows.
To configure Site Studio metadata fields as zone fields: 1.
Log in to Oracle UCM as an administrator.
2. In the Oracle Content Server Administration tray, click Zone Fields
Configuration .
3. On the Zone Fields Configuration page, select Web Sites and Exclude From Lists
as zone text fields. You do not need to rebuild the search index after enabling these fields as zone fields.
Configuring Oracle Universal Content Management 5-15
5.6.5 Enabling JavaServer Pages on Oracle Content Server
If you plan to use JavaServer Pages in Site Studio, you must enable JSP on Oracle Content Server. This enables you to access and modify content and services
personalization, security definitions, predefined variables, and so on on Oracle Content Server.
If you enable any JSP groups after you enable the Site Studio component, you must configure the JSP support so that the JSP fragments function properly.
If you enable the Site Studio component and then add a group to the list of JSP Enabled Groups in Oracle Content Server, you must redeploy the JSP support files for
that group to enable Site Studio JSP fragments to work correctly.
For more information about enabling JavaServer Pages, see Getting Started with the Software Developers Kit SDK, which is part of the Oracle Content Server 10gR3
documentation set.
To configure JSP Support for a new JSP group: 1.
Log in to Oracle UCM as an administrator.
2. In the Administration tray, click Site Studio Administration.
3. On the Site Studio Administration page, click Manage Fragment Libraries.
4. Click the Configure JSP Support button.
The JSP support files are extracted to the required directories on Oracle Content Server.
5.6.6 Rebuilding the Oracle Content Server Index
If you are using database search and indexing full-text or metadata-only, you do not need to rebuild the search index after you install or upgrade the Site Studio
component on Oracle Content Server. If you are using a different search engine typically, Verity, you must rebuild the search index when installing or upgrading the
Site Studio component. You should rebuild the search index after enabling the component and configuring Oracle Content Server.
The index rebuild is necessary to take advantage of new metadata fields introduced by Site Studio.
Important:
■
JSP is supported only in legacy Site Studio projects; that is, projects that use the pre-10gR4 architecture. These are typically
projects that were created in a Site Studio release before 10gR4 and that are opened in Designer 11gR1.
■
You cannot enable JSP on Oracle Content Server and then use Site Studio for External Applications remote templates in the same
security group. If you did, Oracle Content Server would attempt to evaluate the Site Studio for External Applications page
templates, resulting in an error that would shut down the server.
5-16 Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite
If you plan to upgrade web sites created in Site Studio releases before 7.5 see Oracle Fusion Middleware Technical Reference Guide for Site Studio, you must rebuild the search
index on Oracle Content Server at that time. To prevent rebuilding the index more than once, you may want to skip this step until after you have successfully upgraded
your sites.
For more information on rebuilding the index, see Working with the Search Index in Oracle Fusion Middleware System Administrators Guide for Oracle Content Server.
5.7 Configuring Oracle Content Server for Desktop Integration Suite
Before clients can use Desktop Integration Suite DIS with Oracle Content Server, you need to make sure the CoreWebdav system component is enabled, and you need to
enable the DesktopIntegrationSuite, DesktopTag, FolderStructureArchive, and Folders_g components. You can also enable
EmailMetadata, which maps email message fields to email metadata fields.
To configure Oracle Content Server for Desktop Integration Suite: 1.
In the Oracle Content Server Administration tray, click Admin Server to display the Component Manager page.
2.
Make sure that the CoreWebdav component is enabled:
a. In the first paragraph of the Component Manager page, click advanced
component manager .
b. On the Advanced Component Manager page, select Show System
Components .
c. If CoreWebdav is not in the Enabled Components box, select CoreWebdav in
the Disabled Components box, and click the Enable button.
This component will be enabled when you restart Oracle Content Server.
3. In the first paragraph of the Advanced Component Manager page, click simple
component manager .
4. On the Component Manager page, select Folders.
5. Select the DesktopIntegrationSuite, DesktopTag, FolderStructureArchive, and
Folders_g components and, optionally, the EmailMetadata component.
6. Click the Update button.
7.
Restart Oracle Content Server, as described in Section 10.3, Restarting a Managed
Server.
Important: Rebuilding the search index can be a time-consuming
process, depending on the number of content items managed by your Oracle Content Server instance. You should perform this rebuild
during off-peak hours of Oracle Content Server use typically at night or on the weekend.
