1 - INSTALLING TZUNAMI AQUALOGIC EXPORTER

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

• System Requirements

• Installing Tzunami AquaLogic Exporter

• Post Installation Steps

 

System Requirements

The following table lists the system requirements for Tzunami Deployer AquaLogic Exporter Version 2.8

lL0p5Jg2i-QJoN3Lnogn2XrBL745QMMLAg.png


If using version 5.x of AquaLogic Server with an Oracle database, and the database server is running on a separate machine than the AquaLogic Server, Oracle Client will need to be installed on the AquaLogic Server machine where the exporter is run.

It is recommended that the Oracle Client version is same as the Server version. Oracle Client can be installed from the Oracle Server software package or can be downloaded from Oracle download page http://www.oracle.com/technology/software/products/database/index.html

During the installation of the Oracle Client, the Oracle service name configured at the client should be same as the service name at the Oracle Server which AquaLogic Server is using. The properties file (PlumtreePortal_v5-0.properties) in AquaLogic installation directory can be referred to check which service name has been assigned to the AquaLogic Server. The PORTAL_DB_NAME entry in this file represents the service name. Configure and test the service using Oracle’s Net Manager utility and make sure that it is successful.

IacTkFaQy2FmvUtFMFJv1s-bxQ1PXvtFQQ.png


Please consult your database administrator for configuring Oracle Service to connect to the AquaLogic Server database. For questions, contact the Tzunami Support Team at: support@tzunami.com .

 

Installing Tzunami AquaLogic Exporter

You must install Tzunami AquaLogic Exporter on the AquaLogic Application Server.

To install Tzunami AquaLogic Exporter:

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

 

YiI58lNgl0kdag8rxO8MMj5SKubu2xHlDQ.png

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

 

5-uFww4AXWZdZH3kasEfoyFOK1EEA3yclw.png

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 .

 

-eY6IgOriIPFVbUm4O0_k44Uy8t41q5VLA.png

4. In the Ready to install Tzunami AquaLogic Exporter panel, click Install .

S3PxOdfG0ru6jpKNvSxp17BaaUDaWPrGPg.png

 

5. In the Completed Tzunami AquaLogic Exporter Setup Wizard, to exit the wizard, click Close .

 

bVic-dbK3oAqMupg2YjI4YKaYIUFpXnHvg.png

When Tzunami AquaLogic 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 is needed only for version 6.x of AquaLogic Server.

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 5.

For Collaboration table:

If the AquaLogic 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 Oracle_Grant_Select_OnCollabTables_ToPortalUser.sql  to a directory in the Oracle Server machine hosting AquaLogic 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 <collaboration DB user>/<collaboration user password>@<Portal SID>

<Portal SID> is the Oracle service name assigned to AquaLogic Server database.

5. You should receive the SQL prompt.

6. Execute the script by typing command

7. @Oracle_Grant_Select_OnCollabTables_ToPortalUser.sql

8. 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 SQLServer_Grant_Select_OnCollabTables_ToPortalUser.sql  to a directory in the SQL Server machine hosting AquaLogic 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 step1, and open the file.

5. Execute the script and make sure that it is successfully executed.

  

For Publisher table:

Similarly if the AquaLogic 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 Oracle_Grant_Select_OnPublisherTable_ToPortalUser.sql  to 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 system/<system user password>@<Publisher SID>

<Publisher SID> is the Oracle service name assigned to Publisher database.

5. You should receive the SQL prompt.

6. Execute the script by typing command: @Oracle_Grant_Select_OnPublisherTable_ToPortalUser.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 SQLServer_Grant_Select_OnPublisherTable_ToPortalUser.sql  to 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 step1, 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 AquaLogic server. For questions, contact the Tzunami Support Team asupport@tzunami.com .

  

 

2 - TZUNAMI AQUALOGIC EXPORTER

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

• Overview

• Exporting from AquaLogic

• Command-line Export

• Best Practices

  

Overview

Tzunami AquaLogic Exporter enables migrating AquaLogic User Interaction content into Microsoft Office 365, SharePoint Server 2010/SharePoint Foundation 2010 (SPS2010/SPF2010), Microsoft Office SharePoint Server 2007/Windows SharePoint Services 3.0 (MOSS/WSS3.0), or Microsoft SharePoint Portal Server 2003/Windows SharePoint Services 2.0 (SPS2003/WSS2.0) using Tzunami Deployer.

To load AquaLogic content into Tzunami Deployer, you must first extract the content, using Tzunami AquaLogic 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 AquaLogic Exporter is an extension module of Tzunami Deployer. You can work with this module independently of Tzunami Deployer.

Supported Types

The Tzunami AquaLogic Exporter supports basically three types of content repositories:

Knowledge Directory: AquaLogic Interaction 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 AquaLogic 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 AquaLogic Exporter are:

1. Folders and Documents

2. Tasks Lists and Tasks

3. Discussions and Messages

4. Calendars and Events

5. Announcements

6. Links and Shortcuts

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

AquaLogic 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 AquaLogic Exporter extracts security information. The following permissions are used in the exporter:

• None

• Read

• Select

• 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), Select (Read and Select permissions), Write (Read, Select and Write permissions), Edit (Read, Select, Write and Edit permissions), and Admin (user has full permissions).

 

Exporting From AquaLogic

The Tzunami AquaLogic Exporter enables you to export BEA AquaLogic contents to a TDX file.

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 AquaLogic installations and configurations, advanced settings and parameters are available in theTzunamiExporter.exe.config file. The file contains parameters which can be configured according to the AquaLogic setup against which the exporter needs to run. Please refer the Appendices A-D  for the various possible setups and configurations parameter needed.

To export to a TDX file:

1. In Tzunami Deployer, right-click in the AquaLogic tab source store area and select Export AquaLogic to TDX.

Or Click Start > All Programs > Tzunami > Tzunami AquaLogic Exporter.

The Welcome screen of the Export Wizard appears.

2. Click Next. The AquaLogic Configurations screen appears. Use this screen to enter the settings required for the exporter to connect to AquaLogic. The screen includes three tabs: Projects, Directory, and Database.

3. Click the Projects tab to configure how Projects and their contents are exported.

 

VulbY9nM3SJVCxqfIfvMtKerLDjrMLMuxw.png


sjpCzWH2Mtyqa72f4-rt6PNpvdJjwWtrkw.png

KQlmQ1Gz2v7H4Ss4oboZrJB4Sx9i85rMgg.png


4. Click the Directory  tab and configure how to handle Knowledge Directory content.

 

8d96VWhXj-0IlxGzH8U3rWY3n7J7mTEWzw.png

 

5. If the AquaLogic Server is version 5.x  then, Click the Database  tab and configure database access options as shown below:

AveLthfjcxSu588_kQ8a2UHsQwr4Cq6nzw.png

 

If the AquaLogic Server is version 6.x , Click the Database  tab and configure database access options.

70b_bc-7WeH9eRp9UxRPr88QLBzuWYPCcA.png


Portal database password is needed (in AquaLogic v5.x) for exporting Knowledge Directory contents.

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.

6. Click Next . The Connection screen appears. You need to provide the required portal credential to connect to the AquaLogic server. If your AquaLogic 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.

 

_vzIoRQxlLPLj2PLwScFHZNFztTUp15a6w.png

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

7. Click Next . The Folders screen appears. Navigate the AquaLogic folders and select the folders to export.

 

Olm8j5TUd_vgxZQRdW4KAKDWFvsvKozjuw.png

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

8. Click Next . The Filter screen appears.

 

edqmbYdq8JZPwACzCTAd9CAQOas2wbInNA.png

9. 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.

10. Click Next . The Destination Folder screen appears.

 

DFJNO2XXCUew19rHMPBdsZ60vytDGtxBng.png

11. 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.

12. 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.

13. 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.

  

JySExxUaCrpDkjgoVg1Be90y8wuEdh5ESw.png

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.

14. Click Next . The Export Complete screen appears.

15. Click Done . The AquaLogic 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 AquaLogic 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 7, Windows Vista, Windows Server 2003 and Windows Server 2008 environment, if USG (Universal Security Group) 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" "<ExporterInstallationDirectory>\TzunamiExporter.exe –s \"<Spec file path>\Specfilename.xml \" "

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

 

Best Practices

Due to the technological differences between AquaLogic 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:

 

• Knowledge Links can be migrated in two ways:

• Migration as data-items in a Links List.

• Migration as documents in a Document Library. MOSS/WSS3.0 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 support@tzunami.com .

  

 

3 - LICENSING INFORMATION

Tzunami AquaLogic 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 support@tzunami.com 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 for Aqualogicc. Tzunami License Update window opens:

  

qXReEAZ_Ri2JuTTaDMjJNGa4EOcB3u2viw.png

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 support@tzunami.com.

 

To extend the Tzunami license:

1. Select Start > Programs > Tzunami > Tzunami License Update for Aqualogic. Tzunami License Update window opens (Figure 16).

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 a support@tzunami.com .

 

APPENDICES

 

APPENDIX A - AQUALOGIC 6.5 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 - AQUALOGIC 6.5 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.

  

APPENDIX C - AQUALOGIC 6 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 D - AQUALOGIC 6 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.

  

APPENDIX E - AQUALOGIC 5 WITH SQL

 

 

 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 F - AQUALOGIC 5 WITH ORACLE

 

 

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: http://download.tzunami.com/go.aspx?ALGuide=Download