Skip Headers
Oracle® Collaboration Suite Migration and Coexistence Guide
10g Release 1 (10.1.1)

Part Number B14486-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

9 Migrating Content to Oracle Content Services

This chapter provides information about how to migrate content and users from legacy systems to Oracle Content Services.

This chapter contains the following sections:

Migrating Data from Other File Systems

Oracle Content Services migration is applicable to customers migrating from the following systems:

Note:

Oracle Content Services does not currently offer a migration toolkit. You must migrate your files manually.

Migration Tasks

Consolidating users, folder hierarchy, content, and access privileges from other file server systems to Oracle Content Services involves the following tasks:

Migrating Oracle Content Services Users

The first task in moving to a new Oracle Content Services server is creating the user list. For each user you want to migrate to Oracle Content Services, create a user in Oracle Internet Directory.

See Also:

Oracle Internet Directory Administrator's Guide for more information.

After users have been created in Oracle Internet Directory, they are automatically provisioned in Oracle Content Services by Oracle Internet Directory Credential Manager Agent.

Also, once a user has been created in Oracle Internet Directory, logging in to Oracle Content Services as that user immediately provisions the user in Oracle Content Services.

Creating Oracle Content Services Libraries

To migrate user groups into Oracle Content Services, you must create or update corresponding Libraries and member roles in Oracle Content Services.

Scripted Library Creation

If your management tools let you export group information to a file, you can write a translation script to convert the groups into XML format. Then, you can use the Library Creation tool to create corresponding Libraries in Oracle Content Services.

See Also:

"Oracle Content Services Command-line Tools" for more information about the Library Creation tool.

Migrating Oracle Content Services Content

After creating users and Libraries, the next step is to move files and folders into Oracle Content Services. However, if your old file system had application-specific metadata, this information cannot be automatically copied.

Protocols for Copying Data

Use one of the following network protocols to copy your files:

  • File Transfer Protocol (FTP/FTPS): FTP is the most lightweight protocol and can move large amount of data faster than any other protocols. For bulk operations, such as migrating from an existing system, FTP is the preferred protocol. You need to use either a command line FTP application or a Graphical User Interface (GUI) FTP client for this. As an alternative, you can use FTPS. FTPS is FTP with the added option of Secure Socket Layer (SSL) security.

    To FTP your files into Oracle Content Services, the following requirements must be met:

    • An FTP client must be installed on your local computer.

      You must know the port number for FTP. The default port number is 21. Use the Oracle Collaboration Suite Control to check the IFS.SERVER.PROTOCOL.FTP.Port property if you are unsure.

    • An account on the Oracle Content Services server must be already set up.

    To FTP your files into Oracle Content Services:

    1. Using an FTP client, log on to the Oracle Content Services server. You can use either the hostname of the Oracle Content Services server or the IP address of the server.

    2. Navigate to the files on your local computer that you want to load into Oracle Content Services and use the utilities of your FTP client to load the files.

      By default, to use FTP, you require an FTP password. Set this password from the User Preferences page in Oracle Content Services.

  • Web-based Distributed Authoring and Versioning (WebDAV): WebDAV, a protocol designed for Internet and intranet collaboration on files, enables you to drag and drop data from one system to another.

    See Also:

    Oracle Content Services online help for more information

    In Windows:

    1. Connect to a Web folder.

    2. Select the files from your local directory.

    3. Drag and drop the files into a folder in the Oracle Content Services Web folder.

      If you want to retain the file structure, click and drag the entire directory structure from the original file system into Oracle Content Services, or drag different parts of the directory tree separately, confirming that each part of the tree has been copied before copying the next one.

    4. Log on to Oracle Content Services through Windows as a test user and verify that all the files and folders are accessible.

    Oracle Drive: Oracle Drive is a desktop client that uses the WebDAV protocol to access Oracle Content Services. After it is installed, Oracle Drive appears as a mapped drive in your Windows Explorer. Oracle Drive also provides file synchronization capabilities between your local computer and Oracle Content Services.

Oracle Content Services Command-line Tools

You can use the command-line tools to create and modify groups and Libraries.

Each tool works in a similar manner: it reads an XML file containing a list of actions (such as creating a Library or updating users), processes the list, and performs the actions.

To run the command-line tools, you must have appropriate privileges and access to the command-line on the server where Oracle Content Services is running.

This section includes the following topics:

Running the Oracle Content Services Command-line Tools

The command-line tools run over the Oracle Content Services Web services.

To run the command-line tools, perform the following steps:

  1. Download and extract the Oracle Content Services Web Services Development Kit to your computer. You can obtain the Oracle Content Services Web Services Development Kit from the Oracle Technology Network (OTN) at http://www.oracle.com/technology.

    The ContentServices_WebServices/command_line_tools directory of the Development Kit includes scripts and configuration files that you can use to set up and run the Oracle Content Services command-line tools.

  2. If you are not using HTTPS, change the IFS.DOMAIN.WS.CleartextAuthenticationRequiresHttps domain property to false. Otherwise, you will not be able to use the command-line tools. See Oracle Content Services Administrator's Guide for information about how to set domain properties.

  3. Set up your environment:

    • Install JDK 1.4 on your computer.

    • Set the JAVA_HOME environment variable. JAVA_HOME is required to use the javac and java executables for running the command-line tools program.

  4. Create an XML file for group or Library creation that complies with the respective XML Schema Definition (XSD) file. Specify command-line operations for groups and Libraries in separate XML files. For each command-line tools operation, you can use only one operation type at a time, which is either create or modify. The XSD files for groups and Libraries are stored in the conf directory under your command-line tools home directory.

  5. Set up property files by editing the sample property file, property.txt. You can find this file in the ContentServices_WebServices/command_line_tools/examples directory. Provide values for the following properties:

    • operation: group or workspace

    • xmlfile: name of the XML file

    • xmlpath: location of the XML file

    • username: name of the Oracle Content Services user

    • url: use the format http://hostname:port/content/ws

  6. Run the command-line tools program.

    • For Linux or Solaris, run the following shell script:

      sh runbulktools.sh property_file
      
      

      For example:

      sh runbulktools.sh /private/bulktools/property.txt
      
      
    • For Windows, run the following batch file:

      runbulktools.bat property_file
      
      

      For example:

      runbulktools.bat C:\property.txt
      
      
  7. When prompted, provide the Oracle Content Services password of the user specified in the property file.

If an operation fails, an error message is shown. The program continues to the next operation until the entire list is processed. All exception stack traces and details are logged in the Bulk-log.log file, located in the ContentServices_WebServices/command_line_tools/log directory.

Using the Oracle Content Services Group Tool

The Group tool uses an XML file that provides the name, description, and members of a group that have User or Manager role. The Group tool performs the following within a Site:

  • Create groups: Create groups provides a mechanism for bulk group creation. Group details such as name (mandatory), description, and members are taken from the XML file, and are validated against the existing schema. If the validation fails, for example, if the group already exists, the operation is terminated and an appropriate error message is reported based on command line interface (CLI) property file options.

    In addition, member names can be provided through a separate file for each group member's role. This file contains the list of members separated by new line characters.

  • Modify groups: Modify groups provides a mechanism for bulk group modification. Group details such as name (mandatory), description, and members are taken from the XML file, and are validated against the existing schema. If the validation fails—for example, because the group does not exist—the operation is terminated and an appropriate error message is reported based on CLI property file options.

    In addition, member names can be provided through a separate file for each Library member's role. This file contains the list of members separated by new line characters. The modify operation can be performed by a Site administrator or group managers.

Sample XML File for Group Creation

<groups>
 
  <create>
 
    <group name="IDCTest10">
 
      <member name="ken" role="manager"/>
 
      <member name="steve" role="user"/>
 
    </group>
 
  </create>
 
</groups>

Sample Property File for Groups

operation=group
 
xmlfile=group.xml
 
xmlpath=C:\bulktool
 
username=tim
 
url=http://sampleserver.domain.com:7777/content/ws

Using the Oracle Content Services Library Tool

The Library tool uses an XML file that provides the name, description, quota, path, and members of the Library that have Viewer, Author, or Manager role. The Library tool performs the following within a Site:

  • Create Libraries: Create Libraries provides a mechanism for bulk Library creation. Library details such as name (mandatory), description, quota, path, and members are taken from the XML file, and are validated against the existing schema. If the validation fails, for example, if the Library already exists, the operation is terminated and an appropriate error message is reported based on CLI property file options.

    The user who creates the Library automatically assumes the Administrator role for the Library. If optional parameters are not provided, these parameters are given default values.

    In addition, member names can be provided through a separate file for each Library member's role. This file contains the list of members separated by new line characters.

  • Modify Libraries: Modify Libraries provides a mechanism for bulk Library modification. Library details such as name (mandatory), description, quota, path, and members are taken from the XML file, and are validated against the existing schema. If the validation fails, for example, because the Library does not exist, then the operation is terminated and an appropriate error message is reported based on CLI property file options.

    In addition, member names can be provided through a separate file for each Library member's role. This file contains the list of members separated by new line characters.

Sample XML File for Library Creation

<workspaces>
 
  <create>
 
    <workspace name="A7" description="test">
 
      <member name="A" role="reader"/>
 
      <member name="B" role="reader"/>
 
    </workspace>
 
  </create>
 
</workspaces>

Sample Property File for Libraries

operation=workspace
 
xmlfile=workspace.xml
 
xmlpath=C:\bulktool
 
username=tim
 
url=http://sampleserver.domain.com:7777/content/ws