This chapter contains procedures for installing and configuring the Content Integration Platform to support publishing from file systems and Microsoft SharePoint systems to WebCenter Sites.
This chapter contains the following sections:
This section contains the following topics:
Microsoft Visual C++ 2008 redistributable (x86), which can be downloaded from http://www.microsoft.com
OpenSSL, which can be downloaded from http://www.openssl.org
Content Integration Platform is delivered as the following set of files:
| File | Description |
|---|---|
cipagent-vNo.msi (for Windows) cipagent-vNo.rpm.bin (for Linux) |
These files install Content Integration Agent (CIPCommander and service), and configuration files used to control the Agent process. |
csagentservices.war |
This file installs Sites Agent Services, including property files used to set the detail of log files and regulate access to the WebCenter Sites database. |
cs_filesystem_schema.zip |
This file installs the FileSystem flex family. |
cs_sharepoint_schema.zip |
This file installs the SharePoint flex family. |
Content Integration Platform uses native executables.
To install Content Integration Platform:
Install Content Integration Agent on any computer that runs a supported operating system and can access both the source and target systems.
Note:
For information about supported systems in this release, see the Oracle WebCenter Sites Certification Matrix.Deploy csagentservices.war to a system that has access to the WebCenter Sites Shared directory.
The WebCenter Sites system must be fully functional. It must not be a production (delivery) system.
Install the applicable schema on WebCenter Sites:
cs_filesystem_schema.zip
cs_sharepoint_schema.zip
Complete installation instructions are provided in Section 31.2, "Installing Content Integration Platform."
Note:
To ensure a smooth installation process, read the steps below to gain an understanding of the installation procedure and the information you will be asked to provide. To efficiently complete "Step 3: Installing Schema on WebCenter Sites," you must be an experienced WebCenter Sites administrator.In this section, you will complete the following steps:
If you are using a Windows operating system, install Microsoft Visual C++ 2008 Redistributable Package (x86) on the same computer that will host Content Integration Agent. (The redistributable package is available for download from the Microsoft web site.)
Run the cipagent file on a computer that runs a supported operating system and can access both the source and target systems.
Windows:
Run cipagent-11.1.1.6.0-36.msi and follow the steps on the screen. The 11.1.1.6.0 CIP Agent installer is located in CIP 11.1.1.6.0 Installation Binaries under the Agent folder.
The following folders are created in the target directory:
bin
cipagent.exe
cipcommander.exe
conf
..all conf files
security
..all certificates and private keys
logs
..log file
licenses
..licenses
Linux:
The 11.1.1.6.0 CIP Agent installer is located in CIP 11.1.1.6.0 Installation Binaries under the Agent folder.
Run as a root user the following command on the source system:
./cipagent-11.1.1.6.0-38.el5.i386.rpm.bin
This command installs the following directories:
usr
local
bin
cipagent -exe
cipcommander
lib
cipagent
..all librariesshare
share
cipagent
conf
security
logs
licenses
Back up the configuration file catalog.xml (located in [path_to_cipagent]/conf/ and in Linux in /usr/local/share/conf/).
Edit catalog.xml.
The catalog.xml file stores configuration settings that are required by Content Integration Agent to connect to the source system and WebCenter Sites. You will edit this file to provide Content Integration Agent with system location and user information.
Using a text editor, open catalog.xm l.
Edit the adapter for Oracle WebCenter Sites.
Locate the provider element with name "cs" and id "70b1e307-26a1-499c-9295-cf0b6bd01342" and set the following parameters:
urlAS: Point to the Web Services module deployed with WebCenter Sites. Only the host name and port need to be modified. Typically, they are the name of the host and port where WebCenter Sites is running. Do not alter the context name and context-related path unless you are sure they differ from the default (http://localhost:8080/csagentservices/InfostoriaService).
username: User name of the account that has permissions to modify WebCenter Sites database tables (e.g., fwadmin, the general administrator).
password: Above user's password (e.g., xceladmin, assuming fwadmin as the username).
context: Leave this blank
If you are using Microsoft SharePoint, edit the adapter for the SharePoint installation.
Locate the provider element with name "sharepoint" and id "7137dd5d-9ed7-4327-b4fd-8caeebd5889a", and set the following parameters:
urlSharepoint: URL pointing to the SharePoint site from which you plan to publish. Typically you need to modify only the host name (the default value is http://localhost).
username: User name for the account that has permissions to publishable content.
password: Above user's password.
Save catalog.xml.
Restart the Content Integration Agent executable:
Windows: Restart the Content Integration Agent service.
Linux: Type as root user: /sbin/service cipagent restart
Note:
The Content Integration Agent executable can be run as a standalone process or as a system daemon. The executable will start a simple HTTP server on the default port7070, which is reserved for CIPCommander communications with Content Integration Agent. Port 7070 is bound to the localhost, and therefore does not expose your system to any additional security risks.The fileserver facility default configuration takes port 7071 and attempts to automatically detect the host name. If you have more than one network interface installed on the machine where Agent is running, we advise changing auto to the DNS name or the IP address that is accessible from the Sites Agent Services installation.Should you need to change the port, edit the port designation in facilities.xml and add -p <port> to all commands that start CIPCommander.Continue to the next step, "Step 2: Installing Sites Agent Services."
Note:
Sites Agent Services can be installed on any WebCenter Sites system other than production (delivery). We recommend a content management (staging) system.Edit the following files in csagentservices.war (all the files are located in csagentservices/WEB-INF/classes ):
commons-logging.properties: defines the log file and log detail settings
csAgentServices.properties: enables access to the WebCenter Sites database
Using a text editor, edit commons-logging.properties to point to the Agent Services log file (agentservices.log).
Create a data source specific to the application server (more information is available in Part VIII, "Installing Oracle WebCenter Sites.")
Modify csAgentServices.properties to enable access to the WebCenter Sites database.
Using a text editor, set the following properties:
uploader.username: User name of an account with permissions to edit flex families.
uploader.password: Password for the provided user name.
cs.installDir: WebCenter Sites installation directory (e.g., C:\CS)
cs.url: WebCenter Sites URL. Point to the WebCenter Sites web application. The default value is: http://localhost:8080/cs
Save csAgentServices.properties.
Deploy csagentservices.war on the application server on the WebCenter Sites host.
Restart the application server.
Continue to the next step, "Step 3: Installing Schema on WebCenter Sites."
In this step, you will import the applicable zip file(s), listed below, into WebCenter Sites:
cs_filesystem_schema.zip
cs_sharepoint_schema.zip
To install schema
Run catalogmover.bat (or catalogmover.sh on Linux) from the WebCenter Sites installation directory.
Note:
To use CatalogMover, you must connect it to WebCenter Sites:Choose Server, and then Connect.
Provide the following information:
Server: The name of the HTTP server you want to connect to, and the port on which the server is running.
Name: ContentServer
Password:<password>
Below the "Password" field, select (or enter) a value that applies to your WebCenter Sites installation.
Click Connect.
Go to Catalog, and then Auto Import Catalog(s).
Select the file to import.
In the import dialog, fill in the fields as shown below:
Catalog Data Directory: Leave the default value
Catalog ACL List: Browser,SiteGod,xceleditor,xceladmin
If necessary, import the remaining files.
Log in to the WebCenter Sites Admin interface as the general administrator (fwadmin/ xceladmin, by default) and continue as follows:
Enable each imported flex family for an existing content management site (names of flex family members begin with the name of the source system). You can also create a new site for the flex family (or families).
For easy access to published content, create a tree tab (for example, FileSystem tab or SharePoint tab).
For instructions on enabling flex families, creating sites, and creating tree tabs, see the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.
Continue to the next step, "Step 4: (Optional) Configuring Event Notification."
When CIP administrators must be notified of events at the source system and their synchronization, you (or the administrators) can enable any or all of the sample workflows.
Note:
The following workflows must be installed and enabled before an asset is published:CIPAssetDeleted and CIPAssetDeletionFailedFor information and instructions on installing sample workflows, see the chapter "Configuring Event Notification" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.
In this step, you will publish a test folder to WebCenter Sites. You will also verify the synchronization process by adding, deleting, and modifying the test folder's contents.
To verify the CIP installation
Back up mappings.xml (located on the server that hosts Content Integration Agent).
Select (or create) a test folder with default metadata (defined in the default mappings.xml file). That is:
The folder type matches the folder type in mappings.xml (for quick reference, see the table "Source-System Metadata Supported by Default" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.
The test folder contains subfolders and documents whose folder type, document type, and attributes match those in mappings.xml (for more information, see the Oracle Fusion Middleware WebCenter Sites Administrator's Guide).
Note:
If you are verifying the publishing process from a Microsoft SharePoint system, run a test on both the document library and picture library, usingmappings.xml (or See Table 1-1 "Source-System Metadata Supported by Default" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide) to determine the default content types and attributes.Test the publishing process. For instructions, see the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.
Test the synchronization process by renaming, moving, deleting, and creating subfolders and documents (including pictures in SharePoint). Test the attributes by deleting and adding them. (When adding attributes, follow the instructions in the "Remapping" chapter in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.)
Test the unpublish process by running the unpublish command (see the Oracle Fusion Middleware WebCenter Sites Administrator's Guide).
The quickest way to publish objects is to use the default mappings.xml file and flex families provided with CIP. Complete one of the following steps, depending on how your source system is configured:
Objects are ready for publishing if their schema matches the default schema in mappings.xml and the default flex family. Follow the steps in Publishing chapter in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.
Objects cannot be published successfully if their schema differs from the default schema in mappings.xml and the default flex family. Before publishing the objects, remap the schema. This requires you to update the flex family for your source system and reconfigure mappings.xml. For instructions, refer to in the "Remapping" chapter in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.
Content Integration Platform can be customized in many ways. For example:
Default flex families can be modified for custom scenarios, or they can be replaced with custom flex families.
Flex filters can be added to flex families. (If you implement flex filters, make sure to add the corresponding jar files to both the WebCenter Sites and Sites Agent Services applications.)
Attributes can be modified on the source system, or added to the source system.
New document types can be added to the source system.
Workflows can be implemented in order to notify administrators of CIP-related events that occur or fail to occur in WebCenter Sites, in response to changes on the source system.
Information about customizing a CIP installation can be found in the Oracle Fusion Middleware WebCenter Sites Developer's Guide.