Site Capture can be installed graphically or silently. You will first create the war
file using the installer, then manually deploy the war
file and test the installation.
This chapter contains the following topics:
To install Site Capture, you will complete the following basic steps:
Run the silent or GUI installer to create the Site Capture war
file (ROOT.war
).
Note:
Keep in mind the following about clustered installations and installing the sample crawlers:If you are creating a clustered installation:
Run the installer once. You will deploy the ROOT.war
file (and ROOT
folder) on all cluster members, as shown in this chapter. The Site Capture installation directory must be a shared directory, accessible to all other cluster members.
We recommend installing the sample crawlers. Procedures for quickly testing and using the Site Capture installation are based on the Sample crawler, described below.
Sample is a basic crawler that can be easily configured to capture any dynamic site. The configuration step amounts to setting the crawler's start URI in the crawler's configuration file.
FirstSiteII is a crawler with advanced configuration code for capturing the WebCenter Sites FirstSiteII sample website. The code demonstrates the implementation of various methods and interfaces that are used to control the crawler's site capture process, in this example, downloading a dynamic site (FirstSiteII) as a static site.
Crawlers can be easily deleted should you no longer need them.
If WebCenter Sites is running with Oracle Access Manager (OAM), integrate OAM with Site Capture.
Deploy the Site Capture application.
Detailed steps are provided in the rest of this section.
Note:
If you wish to run the GUI installer instead of the silent installer, skip to Section 23.1.2, "Running the GUI Installer."Unzip the sitecapture.zip
file into the desired location on the server.
Configure the omii.ini
file (located at the root level in the extracted folder) according to instructions provided in the file, and save the file.
The host name and port number of both single and clustered installation must be accessible externally.
Reminder:
We recommend installing the sample crawlers. For information about the crawlers, see the note in step 1 in Section 23.1, "Installation Steps."Open the Install.ini
file (located at the root level in the extracted folder), add the line loadfile=omii.ini
to the first section, and save the file.
Open a command prompt and run one of the following commands:
Windows: scInstall.bat -silent
Linux: scInstall.sh -silent
You will see the following message in the command window after installation is successful – "Installation Finished Successfully"
Wait until the installer process exits normally and shows the command prompt again. The ROOT
folder and the ROOT.war
file will be created in the webapps
folder of the installation directory specified in the omii.ini
file.
Do one of the following:
If WebCenter Sites is running with Oracle Access Manager (OAM), integrate the Site Capture application with OAM. For instructions, see the section "Adjusting the root-context.xml File" in Oracle Fusion Middleware WebCenter Sites: Installing and Configuring Supporting Software.
If WebCenter Sites is running with CAS, continue to Section 23.1.3, "Deploying Site Capture."
Note:
If you wish to run the silent installer instead of the GUI installer, go to Section 23.1.1, "Running the Silent Installer."Download sitecapture.zip
to a directory on your Site Capture server and extract it into a temporary directory. The extracted folder contains the scInstall.bat
and scInstall.sh
files, which are needed to run the Site Capture installer.
Execute the following installer script:
On Windows: scInstall.bat
On UNIX: scInstall.sh
The installer "Welcome" screen is displayed (Figure 23-1).
Specify the path to the directory where Site Capture will be installed (Figure 23-2) and click Next.
Figure 23-2 Site Capture Installation Directory
Select the product (Site Capture) to be installed (Figure 23-3) and click Next.
Select either Single Server or Cluster (Figure 23-4), and click Next.
Figure 23-4 Site Capture Installation Type
Enter information about the Site Capture host machine (Figure 23-5). The host name and port number of both single and clustered installation must be accessible externally.
Single-server installation:
Enter the host name (or IP address) of the machine running the Site Capture application server.
Enter the port number of the Site Capture application server (the same number that you specified in the application server configuration steps).
Specify the protocol to be HTTP
or HTTPS
.
Figure 23-5 Site Capture Information: Single Server
Clustered installation (Figure 23-6):
Enter the host name (or IP address) of the machine running the load balancer.
Enter the port number of the load balancer.
Specify the protocol to be HTTP
or HTTPS
.
Figure 23-6 Site Capture Information: Clustered Installation
Enter information about the WebCenter Sites system on which Site Capture will run as an application (Figure 23-7):
WebCenter Sites host name or IP address
Port on which WebCenter Sites is listening
Protocol of the WebCenter Sites application server (HTTP
or HTTPS
)
Context root of the WebCenter Sites application
Figure 23-7 Oracle WebCenter Sites Information
Enter the WebCenter Sites administrator's credentials (Figure 23-8):
Current user name of the WebCenter Sites general administrator
Current password
Figure 23-8 Oracle WebCenter Sites Admin Information
Enter information about the CAS application (Figure 23-9):
CAS host name (or IP address)
Port number
Protocol of the CAS application server (HTTP
or HTTPS
)
CAS context root
Select the application server on which Site Capture will be installed (Figure 23-10).
Note:
The installer will create aROOT.war
file, which you will deploy on the application server.Figure 23-10 Application Server Information
Enter database information (Figure 23-11):
Select the database to which Site Capture will connect (select either Site Capture's database or WebCenter Sites' database).
Specify the name of Site Capture's data source exactly as it is configured in the application server.
Select whether to install the sample crawlers (Figure 23-12):
Note:
We recommend installing the sample crawlers. For information about the crawlers, see the note in step 1 in Section 23.1, "Installation Steps."Figure 23-12 Sample Crawler Configuration
Review the settings summary to verify the data you have entered (Figure 23-13). To edit your settings, click Previous to return to the relevant screens.
Once you have confirmed your settings (Figure 23-14), click Install.
When the installation process successfully ends (Figure 23-15), the installer displays the following message: "Site Capture war file was successfully created"
.
Figure 23-15 Site Capture Installation Successful
The Site Capture file system was also created. The war
file, called ROOT.war
, is located in the <SC_INSTALL_DIR>/fw-site-capture/webapps
folder. For information about the Site Capture file system, see the chapter, "Site Capture File System" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.
Do one of the following:
If WebCenter Sites is running with Oracle Access Manager (OAM), integrate the Site Capture application with OAM. For instructions, see the section "Adjusting the root-context.xml File" in Oracle Fusion Middleware WebCenter Sites: Installing and Configuring Supporting Software.
If WebCenter Sites is running with CAS, continue to Section 23.1.3, "Deploying Site Capture."
Note:
Consider the following:For clustered installations, complete the deployment steps on each cluster member.
The Site Capture application must have a context root of /
.
This section provides instructions for deploying the Site Capture ROOT.war
file. For instructions, see one of the following sections:
Section 23.1.3.2, "Deploying on WebLogic Application Server"
Section 23.1.3.3, "Deploying on WebSphere Application Server"
Copy the ROOT
folder in <SC_INSTALL_DIR>\fw-site-capture\webapps\
and overwrite the ROOT
folder in the <apache-tomcat-6.0.29 directory>\webapps\
directory.
To start Site Capture:
Ensure that WebCenter Sites is running.
Start the application server (run the startup.bat
or startup.sh
file in the <apache-tomcat-6.0.29 directory>\bin
folder).
Continue to Section 23.2, "Post-Installation Steps."
Copy the files named antlr-2.7.7.jar
and commons-lang-2.5.jar
in Site capture's WEB-INF\lib
folder:
<SC_INSTALL_DIR>\fw-site_capture\webapps\ROOT\WEB-INF\lib
and paste them into the WebLogic installation path:
<Weblogic Home>\wlserver_10.3\common\lib
.
Set the pre-class path in the setdomainEnv.cmd
or setdomainEnv.sh
file (located in <Weblogic Home>\user_projects\domains\<domain name>\bin
) for the Site Capture domain.
Below is an example of where the changes need to be made:
On Windows (in setdomainEnv.cmd
):
set WL_HOME=E:\<WL HOME\Weblogic\wlserver_10.3 set PRE_CLASSPATH=%WL_HOME%\common\lib\antlr-2.7.7.jar;%WL_HOME %\common\lib\commons-lang-2.5.jar(in windows machine) for %%i in ("%WL_HOME%") do set WL_HOME=%%~fsi
On Linux (in setdomainEnv.sh
):
WL_HOME="/root/Oracle/Middleware/wlserver_10.3" PRE_CLASSPATH=$WL_HOME/common/lib/antlr-2.7.7.jar: $WL_HOME/common/lib/commons-lang-2.5.jar export WL_HOME
Deploy the Site Capture application:
Go to the deployment section in the console and select the path to the ROOT
folder located in <SC_INSTALL_DIR>\fw-site-capture\webapps
.
Select the managed server as the deployment target.
To start Site Capture:
Ensure that WebCenter Sites is running.
Start the managed server <managed_server_name>.
For example:
./startmanagedweblogic.sh <managed_server_name>
http://<admin_server_hostname>:<admin_server_port>/
Continue to Post-Installation Steps.
In the WebSphere Admin interface, do the following:
Go to the path Application > Application Types > WebSphere enterprise applications and select the ROOT.war
file located in <SC_INSTALL_DIR>\fw-site-capture\webapps\
.
From the WebSphere console, navigate to Enterprise Applications > Site Capture Webapp > Class loader (Class loading and update detection) to display the classloading options. Site Capture requires default configuration for War Policy. Ensure that the Class loader for each WAR file in application option is selected under the WAR class loader policy section.
Complete the deployment process.
To start Site Capture:
Ensure that WebCenter Sites is running.
Start the application server.
Continue to Section 23.2, "Post-Installation Steps."
When Site Capture is installed and the application server is started, Site Capture starts and automatically registers itself as an application enabled on AdminSite. In addition, Site Capture adds the necessary tables and records to its database, unless the database is Oracle.
To complete and verify your Site Capture installation, complete the steps in the following sections:
Section 23.2.1, "If Site Capture Is Using an Oracle Database"
Section 23.2.2, "Add the Site Capture URL in the customBeans.xml File"
Section 23.2.4, "Authorizing Users to Work with Site Capture"
When Site Capture uses the Oracle database, the sql
script that creates the schema must be run manually. The script, named crawler_oracle_db.sql
, is available in the <SC_INSTALL_DIR>/Sql-Scripts
folder.
In your installation, navigate to <Sites_Installation_Directory>/bin/customBeans.xml
.
Open the customBeans.xml
file.
In the bean id
section, add the Site Capture URL as follows:
<bean id="RequestParamValidator" class="com.fatwire.cas.web.RequestParamValidator"> <property name="validUrls"> <list> <value>http://<Sites_Host_Name>:<Sites_Port>/<Sites_Context_root>/*</value> <value>http://<Site Capture Hostname>:<SiteCapture_port>/__admin/*</value> </list> </property> </bean>
Restart WebCenter Sites application servers and Site Capture servers.
Ensure that the Site Capture application is available in the WEM Admin interface:
Log in to WebCenter Sites as a general administrator.
Navigate to AdminSite and select the WEM Admin application.
In the menu bar, click Apps and verify that Site Capture is listed on the "Apps" page.
Navigate to the Site Capture application, represented by the icon shown in Figure 23-16.
Figure 23-16 Site Capture Application Icon
The home page opens. If you chose to install the sample crawlers, they are listed on the home page as Sample and FirstSiteII (Figure 23-17).
Figure 23-17 FirstSiteII and Sample Crawlers
The Site Capture application is designed for WebCenter Sites general administrators and developers with general administrator rights. All such users have access to AdminSite, where the Site Capture application is registered and running. (Access is granted via the GeneralAdmin
role on AdminSite and the user's membership in the RestAdmin
security group. For more information about user authorization and the WEM Admin interface, see the chapter "Creating and Authorizing Users" in theOracle Fusion Middleware WebCenter Sites Administrator's Guide.
Site Capture users also require administrative access to its host machine, especially to retrieve statically captured sites and crawler logs.
If you wish to set up publishing-triggered site capture, see Chapter 24, "Enabling Publishing-Triggered Site Capture."
To get started with Site Capture, see the Oracle Fusion Middleware WebCenter Sites Administrator's Guide for information about navigating the interface and writing crawler configuration code.