1        Installing Tzunami Oracle WebCenter Interaction Exporter

This chapter contains information about installing Tzunami Oracle WCI Exporter. It contains the following topics:

• System Requirements
• Installing Tzunami Oracle WCI Exporter
• Post Installation Steps

System Requirements

The following table lists the system requirements for Tzunami Oracle WCI Exporter Version 2.7.

Table 1: Hardware Requirements

Installing Tzunami Oracle WCI Exporter

You must install Tzunami Oracle WCI Exporter on the Oracle WCI Server.

To install Tzunami Oracle WebCenter Interaction Exporter:

1. Unzip the zip file, and run Tzunami Oracle WCI Exporter Setup.msi. The Tzunami Oracle WCI Exporter Setup Wizard will launch. To advance through the install wizard, click Next on the bottom of the window.

Figure 1: Welcome Window

 2. In the End-User Licensing Agreement panel, click “I accept the terms in the License Agreement” and click Next to continue installation.

Figure 2: End-User License Agreement Window

You are advised to read the terms of the license carefully before proceeding with the installation. If you decline the license terms, the installation cannot proceed.

 3. In the Custom Setup panel,  do one of the following:

• To accept the default Destination Folder, click Next.
• Click Browse, locate and select a destination folder, click OK, and then click Next.

Figure 3: Custom Setup Window

 4. In the Ready to install Tzunami Oracle WebCenter Interaction Exporter panel, click Install. Tzunami Oracle WebCenter Interaction Exporter is installed.

Figure 4: Installing Tzunami Confluence Exporter Window

 5. Click Finish to exit from the setup wizard.

Figure 5: Installation Complete Window

When Tzunami Oracle WCI Exporter is installed, it comes with a default license that can be used for evaluation purpose only. This license is limited in time and number of operations.

Post Installation Steps

This step grants SELECT permissions on Collab/Publisher tables to the portal database user. This can be performed manually using the steps below or Exporter can perform this automatically for you. For more information, see Table 4 on page 2-15.

For Collaboration table:

If the Oracle WCI Server has Collaboration component and you wish to export its contents or the contents published from Collaboration and/or Content Server to the Knowledge Directory, the Portal database user should be given the SELECT permission on specific tables in the Collaboration database. This should be done using the database scripts supplied with the setup, or manually by the database administrator. Separate scripts are provided for Collaboration table and Publishing table for Oracle Server and SQL Server.

Follow these steps to run this script to grant SELECT permissions on Collaboration table to portal database user on Oracle Server:

1. Copy the script collaboration-server-portal-role-grant.sqlto a directory in the Oracle Server machine hosting Oracle WCI database or on a machine having Oracle client.
2. Open a command prompt window (Start > Run, type “cmd” and press Enter).
3. Switch to the directory containing the DB script copied in step 1.
4. Log in to Oracle with the collaboration database user credential by running the command.
            
   sqlplus <collab_user_name>/<user_pwd>@<ORACLE_SID> @collabortation-server-portal-role-grant.sql
   
   <ORACLE_SID> is the Oracle service name assigned to Oracle WCI Server database.
5. You should receive the SQL prompt.
6. Execute the script by typing command:       
   @collaboration-server-portal-role-grant.sql
7. Enter Portal database user name when prompted and press Enter. The script should be executed successfully.

Follow these steps to run this script to grant SELECT permissions on Collaboration table to portal database user on SQL Server:

1. Copy the script collaboration-server-portal-role-grant.sql to a directory in the SQL Server machine hosting Oracle WCI database or on a machine having SQL Server client.
2. Open the script in notepad and change the portalusername value (portaluser)in line ‘SELECT @portalusername = 'portaluser'’to the portal database user created during installation.
3. Start Query Analyzer tool as the collaboration database user. Make sure that the collaboration database is shown in the database dropdown.
4. Browse to the directory containing the script copied in step 1, and open the file.
5. Execute the script and make sure that it is successfully executed.

For Publisher table:

Similarly if the Oracle WCI Server has Publisher (Content Server) component and you wish to export the contents published from the Publisher to the Knowledge Directory, the Portal database user should be given SELECT permission on specific tables in the Publisher database. Please note that this version of exporter can only export Publisher components published to the Knowledge Directory.

Follow these steps to run this script to grant SELECT permissions on Publisher table to portal database user on Oracle Server:

1. Copy the script portal-collaboration-server-role-grant.sqlto a directory in the Oracle Server machine hosting Publisher database or on a machine having Oracle client.
2. Open a command prompt window (Start > Run, type “cmd” and press Enter).
3. Switch to the directory containing the DB script copied in step 1.
4. Log in to Oracle with the System database user credential by running the command:
   
   sqlplus <portal_user_name>/<portal_pwd>@<ORACLE_SID> @portal-collaboration-server-role-grant.sql
   <ORACLE_SID> is the Oracle service name assigned to Publisher database.
5. You should receive the SQL prompt.
6. Execute the script by typing command:
   @portal-collaboration-server-role-grant.sql
7. Enter Portal database name, Portal database user name, Publisher database user name and password when prompted and press Enter. The script should be executed successfully.

Follow these steps to run this script to grant SELECT permissions on Publisher tables to portal database user on SQL Server:

1. Copy the script portal-collaboration-server-role-grant.sqlto a directory in the SQL Server machine hosting Publisher database or on a machine having SQL Server client.
2. Open the script in notepad and change portaluser in line exec sp_grantdbaccess 'portaluser' to your portal database user name.
3. Start Query Analyzer as Publisher database user. Make sure that the publisher database is shown in the database dropdown.
4. Browse to the directory containing the script copied in step 1, and open the file.
5. Execute the script and make sure that it is successfully executed.
6. Please consult your database administrator prior to performing any changes to the Oracle WCI server. For questions, contact the Tzunami Support Team at[email protected]

2        Tzunami Oracle WebCenter Interaction Exporter

 This chapter contains information of Tzunami Oracle WCI Exporter. It contains the following topics:

• Overview
• Exporting from Oracle WCI
• Command-line Export
• Best Practices

Overview

Tzunami Oracle WCI Exporter enables you to migrate contents from Oracle WCI to Microsoft Office 365, SharePoint 2010 and 2007 using Tzunami Deployer.  Tzunami Oracle WCI exporter supports extraction of content from Oracle WCI and loads content into Tzunami Deployer.

To load Oracle WCI content into Tzunami Deployer, you must first extract the content, using Tzunami Oracle WCI Exporter, into TDX (Tzunami Deployer Export) and STDX (Separate Tzunami Deployer Export) files. You can then load this TDX file into a Deployer project.

When working with Tzunami Deployer on several machines, you can run an export on one machine and load the exported data on another. Tzunami Oracle WCI Exporter is an extension module of Tzunami Deployer. You can work with this module independently of Tzunami Deployer.

Supported Types

The Tzunami Oracle WCI Exporter supports basically three types of content repositories:

Knowledge Directory: Oracle WCI has an embedded, portal-specific document content management system called the Knowledge Directory. The Knowledge Directory includes facilities for importing and uploading existing documents, for storing, sharing, and managing them, and for helping users find them through search and navigation. The contents model for Knowledge Directory is built on content items. The content items that are exported by Tzunami Oracle WCI Exporter are:

1. Documents
2. Links: these point to external or internal web contents
3. Shortcuts: these points to documents in other repositories like Collaboration Projects.
4. Published Documents
5. Content Service – Windows Files

Projects: Projects are part of a separate component Collaboration that interacts with Portal to provide tools for user interaction and work flow management. The items that are exported by Oracle WCI Exporter are:

1. Announcement
2. Discussion
3. Document Folder
4. Document
5. Event
6. Task List

Publisher/Content Server: Publisher is a web application that functions as a remote portlet server for BEA AquaLogic Interaction Publisher. Publisher enables content creations, content publishing and workflow management etc.

Tzunami Oracle WCI Exporter does not support extraction of contents from Publisher/Content Server. Only Published Documents in the Knowledge Directory are extracted.

Security

In addition to the structure and items, Tzunami Oracle WCI Exporter extracts security information. The following permissions are used in the exporter:

• None
• Read
• Write
• Edit
• Admin

Each item is assigned an ACL defining the permissions of the various members according to the roles they were assigned.

The exporter automatically creates six default roles that are used during the deployment process. The roles include None (No permission), Read (Read permission), Write (Read and Write permissions), Edit (Read, Write and Edit permissions), and Admin (user has full permissions).

Exporting from Oracle WCI

The Tzunami Oracle WCI Exporter enables you to export Oracle WCI contents to a TDX file. It has a simple user interface and lets you quickly extract contents such as Projects, Attachments, Knowledge Directory etc.

When exporting, keep the following in mind: Export in small chunks: When exporting from your source system, perform the export in small chunks of about 40K-50K files each that have a common business logic or some other logic. Ensure consistency: Make sure that the content of the different exports does not overlap and that, while exporting, no changes are made to the source data.

In order to handle the different type of Oracle WCI installations and configurations, advanced settings and parameters are available in the TzunamiExporter.exe.config file. The file contains parameters which can be configured according to the Oracle WCI setup against which the exporter needs to run. Please refer the Appendices A-B for the various possible setups and configurations parameter needed.

To export to a TDX file:

1. In Tzunami Deployer, right-click in the Oracle WCI tab source store area and select Export Oracle WCI to TDX.
   
   Or
   Click Start > All Programs > Tzunami > Tzunami Oracle WCI Exporter.
   The Welcome screen of the Export Wizard appears.
2. Click Next. The Oracle WCI Configurations screen appears. Use this screen to enter the settings required for the exporter to connect to Oracle WCI. The screen includes three tabs: Projects, Directory, and Database.

a)      Project  tab

The Project tab allows you to select Projects, Project Attachments, Project contents, Version and their contents that you wish to migrate from Oracle WCI.

Figure 6: Oracle WCI Configurations Screen – Projects Tab

Table 2: Oracle WCI Configurations, Projects Tab – Description of Fields

b)      Directory Tab

The Directory tab allows you to Knowledge Directory content. It allows you to export links as file and export documents shortcuts as link.

Figure 7: Oracle WCI Configurations Screen – Directory Tab

Table 3: Oracle WCI Configurations, Directory Tab – Description of Fields

c)       Database Tab

The database tab allows you to enter the information required for the exporter to access Collaboration database and Publisher database.

Figure 8: Oracle WCI v6.x Configurations Screen – Database Tab

Table 4: Oracle WCI v6.x Configurations, Database Tab – Description of Fields

Field	Description
Collaboration database password	Put the password for the Collaboration database user created during collaboration installation in this field.
Grant permission on selected Collaboration tables to Portal database user	Check this option if you wish to grant required SELECT permission on Collaboration tables to Portal database user automatically. Certain configuration parameters will need to be filled up in ‘TzunamiExpoter.exe.config’ file, located in the exporter installation directory, as described in Appendix A and B below. Granting permission can also be done manually as described in Post Installation Steps. Granting SELECT permission to Portal database user on selected Collaboration database is required for extracting the contents from Collaboration.   You can click on ‘selected’ link to see the list of Collaboration tables in the screen-tip for which the required permission will be granted.
Save password	Check this option if you wish to save the Collaboration database password. If checked, the database password is remembered when the exporter is run next time.
Publisher database password	Put the password for the Publisher (or Content Server) database user created during installation in this field.
Grant permission on selected Publisher tables to Portal database user	Check this option if you wish to grant required SELECT permission on Publisher tables to Portal database user automatically. Certain configuration parameters will need to be filled up in ‘TzunamiExpoter.exe.config’ file, located in the exporter installation directory, as described in Appendix A and B below. Granting permission can also be done manually as described in Post Installation Steps. Granting SELECT permission to Portal database user on selected Publisher database is required for extracting the documents published to Knowledge Directory from Publisher.   You can click on ‘selected’ link to see the list of Publisher table(s) in the screen-tip for which the required permission will be granted.
Save password	Check this option if you wish to save the Publisher database password. If checked, the database password is remembered when the exporter is run next time.

Collaboration database password is needed for exporting Collaboration contents and documents published to Knowledge Directory from Collaboration. Publisher database password is needed for exporting documents published to Knowledge Directory from Publisher. A message will prompt if the DB password is missing or incorrect. You can choose to ignore and proceed with the export but an error message will prompt if you try to export the component for which correct password was not supplied.

 3. Click Next. The Connection screen appears. You need to provide the required portal credential to connect to the Oracle WCI server. If your Oracle WCI server supports user authentication from  an external source (like LDAP) other than ALUI database, and you want to use this user for connection, you need to provide username in the format: <Authentication Source Category>\<username>  i.e. by providing  the Authentication Source Category followed by the username.

Figure 9: Connection Screen

 Authentication source category is not required if the user is in local ALUI database.

 4. Click Next. The Folders screen appears. Navigate the Oracle WCI folders and select the folders to export.

Figure 10: Folder Selection Screen

You can select all subfolders of a selected folder by checking Automatically select subfolders.

 5. Click Next. The Filter screen appears.

Figure 11: Filter Screen

 6. Set up filtering as follows:

a)      In the Properties field, select a property.

b)      In the Condition field, select a condition from the drop down list and enter or select values in the corresponding field.

c)       Click Add Condition. The condition is added to the Filter area, displaying the full filter expression.

You can only add one condition per property. You can edit a condition for a property by selecting the property and modifying the condition type or values that are currently assigned to it. You can remove a condition from a property or all the conditions from all the properties by clicking Clear Condition or Clear All, respectively. This option works only for Data Items. If multiple conditions are applied, only items that match all conditions are exported.

 7. Click Next. The Destination Folder screen appears.

Figure 12: Destination Folder Screen

 8. Specify where to export the files and generated TDX information. Make sure you are saving to a folder with a descriptive name and under a well-organized file system hierarchy. It is recommended to export to a folder that is as close to the root as possible.

9. Click Save for saving export specification details as an XML file which can be used to run the exporter in command-line mode.  See the section ‘Command-line Export’ below for more details.

10. Click Next.

If the export folder already exists, a warning appears, informing you that the destination folder already exists and if you continue all existing information will be deleted. Clicking OK confirms overwrite and clicking Cancel returns you to the Destination Folder screen to change the destination folder.

An Exporting screen appears with a progress bar and execution report, and the export process begins.

Figure 13: Exporter Progress Screen

You can save the export report by clicking Save as after export is complete. You can display only export errors by checking Errors only. You can check Auto-scroll to display the latest progress messages, as they appear.

 11. Click Next. The Export Complete screen appears.

12. Click Done. The Oracle WCI Export wizard is closed.

After the extraction process completes successfully, you are prompted to load the exported data into the current Tzunami Deployer project. Clicking ‘Yes’ begins the process of loading the content from the previously exported TDX file into the project. For more information about loading sources, refer to the Tzunami Deployer User Guide.

Command-line Export

Tzunami Exporter for Oracle WCI provides ability to run export sessions non-interactively using command line instructions. This allows administrators to plan and schedule long running migration jobs through scripts, batch files and schedulers according to needs and organizational timetables. To run the exporter in batch mode you will need exporter specification file explained in the ‘Choose Destination Folder’ step of the export wizard. The file contains all the export option details including:

• Source ECM connectivity information (Server Address, User Name, Password etc.)
• Items to export
• Destination and Log Folder
• Filter
• Exporter specific options

This file can be edited to suit your needs however the XML schema of the file should not be altered. It is recommended that you generate a sample specifications file in the Destination Folder Screen selection step of the export wizard and use it as a template to create your own specification file.

Once the specification file is ready, you can run the exporter from command line using command:

TzunamiExporter.exe [-r <ResultFile>] -s <ExportSpecificationsFile>

-r    Outputs export results into an XML file [Optional]

-s    XML file containing export specifications

Based on your needs you can create number of specification files and use them to run multiple export sessions as batch commands.

You will need to provide absolute path for TzunamiExporter.exe and ExportSpecificationsFile in the command if you are not running from the exporter installation directory.

In Microsoft Windows Server 2003 and Windows Server 2008 environment, if UAC (User Access Control) is enabled, Users with low privileges sometimes cannot export ECM contents. To export contents using command line, User must run with elevated or administrative privileges.

To export contents with elevated or administrative privileges, you can run the exporter from command line using command:

RUNAS /trustlevel: “Unrestricted” “<Exporter Installation Directory>\TzunamiExporter.exe -s\ “<Spec file path>\Specfilename.xml””

For example:     RUNAS /trustlevel: “Unrestricted” “C:\Program Files (x86)\Tzunami\Deployer 2.7\Exporters\OracleWCI\TzunamiExporter.exe -s\ “D:\Spec Files\specs1.xml””

Best Practices

Due to the technological differences between Oracle WCI and SharePoint, the following best practices should be taken into consideration:

• Migrate folders to their relative list types, based on the items in those folders:

Table 5: Target Structure Guidelines

• Knowledge Links can be migrated in two ways:
  • Migration as data-items in a Links List.
  • Migration as documents in a Document Library. MOSS 2007, SPS 2010 and Microsoft Office 365 provides a Content Type named Link to a Document, which functions in a similar way to a shortcut. For more information about migrating using this Content Type, please contact the Tzunami Support Team, at [email protected].

2        Licensing Information

Tzunami Oracle Exporter uses a default license that can be used for evaluation purposes. This license is limited in the number of items that are exported. If the license does not match your evaluating needs, contact [email protected] for an extended license. For this purpose you will need to provide the Product Serial Code, and then enter the License Key you receive back from the Tzunami.

To retrieve the Tzunami Product Serial Code:

1. Select Start > Programs > Tzunami > Tzunami License Update. Tzunami License Update window opens.

Figure 14: License Update window

 2. Click Copy. This copies the Product Serial Code to the clipboard.

3. Paste the contents of the clipboard into an email and send it to the Tzunami Support Team at [email protected].

To extend the Tzunami license:

1. Select Start > Programs > Tzunami > Tzunami License Update. Tzunami License Update window opens (Figure 14).
2. Click Browse and select the new License Key file received from the Tzunami Support Team.

If an error message appears, contact Tzunami Support Team at [email protected].

Appendices

Appendix A – Oracle WebCenter Interaction with SQL

 *These parameters are not required in exporter configuration file (TzunamiExporter.exe.config) located in exporter installation folder, if user grants SELECT permissions on Collaboration and Publisher database manually as specified in Post Installation Step.

If parameter values are left blank, the exporter will try to auto-detect the settings from local Portal server.  Remote components (Collaboration/Publisher etc.) will fail to be extracted in this case. These parameters have therefore been listed under mandatory parameters.

Export should work without optional parameters. However if there is an issue in export, these parameters can be configured for better results. For details on how to find the different parameters needed, please refer to the ‘TzunamiExpoter.exe.config’ file in the exporter installation folder.

Appendix B – Oracle WebCenter Interaction with Oracle

*These parameters are not required in exporter configuration file (TzunamiExporter.exe.config) located in exporter installation folder, if user grants SELECT permissions on Collaboration and Publisher database manually as specified in Post Installation Step.

If parameter values are left blank, the exporter will try to auto-detect the settings from local Portal server.  Remote components (Collaboration/Publisher etc.) will fail to be extracted in this case. These parameters have therefore been listed under mandatory parameters.

Export should work without optional parameters. However if there is an issue in export, these parameters can be configured for better results. For details on how to find the different parameters needed, please refer to the ‘TzunamiExpoter.exe.config’ file in the exporter installation folder.

Download a PDF version of this guide at: https://www.tzunami.com/download/OracleWCIExporter-Guide