|Oracle® Fusion Middleware Technical Reference Guide for Site Studio
11g Release 1 (11.1.1)
Part Number E10615-02
Site Studio 11gR1 (18.104.22.168 and higher) can work with site assets and content managed by Oracle Content Server 10gR3. However, some manual steps are required for this to work.
This section covers the following topics:
Site Studio 11gR1 will work with Oracle Content Server 10gR3. However, some additional components to the server must be downloaded and installed in order to use Site Studio.
The following must be installed and enabled on Oracle Content Server 10gR3:
The latest 10gR35CoreUpdate and 10gR35NativeUpdate bundles (which update Oracle Content Server and Dynamic Converter to the required feature set level and also updates the web filter to the required version).
The SiteStudio component, which is included in the Site Studio 11gR1 PS3 (22.214.171.124) bundle (along with the Site Studio Designer client installer).
If you are planning to use dynamic conversion of native documents on your Site Studio web sites, then you need to configure Dynamic Converter in Oracle Content Server.
The Site Studio Designer 11gR1 client installer is checked in to the content server when the SiteStudio component is installed and enabled. You can download the installer from Oracle Content Server's configuration information page and run it to install Site Studio Designer 11gR1 on a client computer.
Additionally, the following must be completed:
JDK version 1.6 must be installed (Oracle Content Server 10gR3 is shipped with JDK 1.5).
The Oracle Content Server configuration file intradoc.cfg must be updated to reference the new JDK 1.6 installation directory. Add the JDK_custom entry to the #Additional Variables section of the configuration file.
The necessary Oracle components are available from the Oracle Fusion Middleware Universal Content Management section of the Oracle Technology Network (OTN):
When you install the SiteStudio 11gR1 component on Oracle Content Server 10gR3, the Site Studio Designer 11gR1 installer is checked in to the server as a content item. You can download the Site Studio Designer installer from Oracle Content Server's General Information page. For information on how to use the Designer 11gR1 application, see the Oracle Fusion Middleware User's Guide for Site Studio Designer.
When you create a new Web site in Site Studio, a new project file is created and checked into the content server for you. Thus, 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 Project Default Document Information page in the content server.
To set the default metadata used for Site Studio project files, perform these tasks:
Log on to the Oracle Content Server as an administrator.
Go to the Administration page, and click Site Studio Administration.
The Site Studio Administration page is displayed.
Click Set Default Project Document Information.
The Set Default Project Document Information page is displayed, where you assign the default metadata for new projects generated by Site Studio.
Set the metadata as required, and click Update when you have finished.
This returns you to the Site Studio Administration page.
If you are using an Apache web server as your web server, you should update the configuration file to take advantage of the path-based URLs in Site Studio. If you are not using Apache as your web server, you can skip this section.
To edit the Apache web server configuration file, perform these tasks:
Open the Apache httpd.conf configuration file, which is located in the conf directory of Apache's installation location.
Locate the entries that look something like this:
LoadModule IdcApacheAuth CS-Dir/shared/os/OS_Name/lib/IdcApacheAuth2.dll IdcUserDB myserver CS-Dir/data/users/userdb.txt Alias /myserver "CS-Dir/weblayout" <Location "/myserver"> DirectoryIndex portal.htm IdcSecurity myserver </Location>
Note:On UNIX, the LoadModule line refers to IdcApacheAuth2.so.
Add the following lines:
<Location "/"> IdcSecurity myserver </Location>
Then locate the "UseCanonicalName" configuration variable and make sure it is set to Off.
Save the configuration file and restart Apache HTTP Server.
All code examples use "myserver" as the Content Server name.
If you want to use Site Studio domain-based sites, then you must use the <Location "/"> entry (in step 3).
If you prefer not use the <Location "/"> entry (in step 3), then you must use a separate entry for each of the Web sites that the server should recognize. For example, if you have two sites with the addresses "http://domain/site1/index.htm" and "http://domain/site2/index.htm," then you could set up two location entries as follows:
<Location "/site1"> IdcSecurity myserver </Location> <Location "/site2"> IdcSecurity myserver </Location>
For information on changing Web site URLs in Site Studio, see the Oracle Fusion Middleware User's Guide for Site Studio Designer .
If you are using a Sun ONE web server as your web server, you should update the configuration file to take advantage of the path-based URLs in Site Studio. If you are not using Sun ONE as your web server, you can skip this section.
To edit the Sun ONE web server configuration file, perform these tasks:
Go to the Sun web server software directory, and open the https-host_name/config subdirectory (where host_name is the name of the system on which the software is installed), for example:
Open the file obj.conf in a text editor.
Inside the <Object name="default"> section, add the web id to the NameTrans entry:
NameTrans fn="pfx2dir" from="/Site_ID" dir="Weblayout_Dir"
where Site_ID is the web id of your web site, and Weblayout_Dir is the full path to the web-viewable file repository.
Apply the changes that you just made to the obj.conf file on the web server's administration page.
Stop and restart the web server.
When you install the Site Studio component, several metadata fields are added to the content server. Some of these must be configured as zone fields to ensure that they are full-text indexed.
Make sure that the DBSearchContainsOpSupport component is installed and enabled on the content server. This component ensures that the zone fields are full-text indexed properly, which is required for Site Studio sites to work correctly. If this component is not installed and enabled, you should install and enable it. You can find the component zip file in the \packages\allplatform directory of the Oracle Content Server distribution package.
Configuring Site Studio Metadata Fields as Zone Fields
To configure Site Studio metadata fields as zone fields, perform these tasks:
Log in to Oracle Content Server an administrator.
Open the Administration page.
Click Zone Fields Configuration.
Designate 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.
Adding a Setting to the Content Server Configuration File
To add a setting to the Content Server configuration file, perform these tasks:
Open a new browser window and log in to Oracle Content Server as a system administrator (with the "sysmanager" role).
Go to the Administration Applets page and click the Admin Server link.
On the Content Admin Server page, click the button of the appropriate content server instance.
The status page for the selected content server instance is displayed.
In the option list for the server instance, click the General Configuration link.
The General Configuration page is displayed.
Scroll down to the bottom of the page, and add the following line to the Additional Configuration Variables box:
Optionally, you can also add the following line:
This improves the responsiveness of queries performed by Site Studio Designer and Contributor.
Restart the content server.
If you plan to use JavaServer Pages in Site Studio, you must enable JSP on the content server. This enables you to access and modify content and services (personalization, security definitions, predefined variables, and so on) on the content server. For more information on enabling JavaServer Pages, see the Getting Started With the Software Developer's Kit (SDK) guide, which is part of the Content Server documentation set.
If you enable any JSP groups after you enable the Site Studio component, you must configure the JSP support so the JSP fragments function properly.
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 10gR4.
If you install the Site Studio component and then add a group to the list of JSP Enabled Groups in the content server, you must redeploy the JSP support files for that group to allow Site Studio JSP fragments to work correctly.
To configure JSP support, perform these tasks:
Log in to Oracle Content Server as an administrator.
Under Administration, click Site Studio Administration.
Click Manage Fragment Libraries.
Click the Configure JSP Support button.
The JSP support files are extracted to the required directories on the content server.