The legacy product of Novell Teaming is the SiteScape Forum product. To assist with migrating data from SiteScape Forum to an installation of Novell Teaming, Novell developed a set of Web services.
Although this section provides guidance about migrating, the task is complex and requires the active assistance of the Teaming support team. This is especially true for workflow migration. For more information, please contact the support team and arrange to receive consultation as you perform this task.
Some operations require the previous execution of other operations. For example, migrating an entry requires that you have already migrated the folder. As another example, a workflow process requires that you have already migrated user and group names, so that these names can be applied to its access control.
Here are notes regarding the sequence of operations:
Migrate users and groups, and create personal workspaces early in the process.
Use either LDAP or portal administration to establish the Forum users in Novell Teaming.
You need the existence of personal workspaces to be able to migrate sub-workspaces and child folders. Also, migrating workflow and some types of custom commands requires that your users be established in Novell Teaming first.
The Forum term “custom command” maps to “custom view and form” in Novell Teaming.
Generally, migrate parents before children you wish to create.
Examples include migrating parent workspaces before its child folders, and migrating entries before migrating attached files.
Using SiteScape Forum, a “forum” maps to a “folder” in Novell Teaming, a “reply” maps to a “comment” in Novell Teaming, and the process of “attaching a file” maps to the Web services phrase “adding a folder file.”
Migrate binders before setting their ownership, team members, and access control.
The Forum items “workspaces and folders” map to the Novell Teaming Web services term of “binders.” The Forum term “access control” maps to “membership.” Also, the Web services term “function” is equivalent to the term “roles” in the UI for Novell Teaming.
Migrate custom commands before creating entries.
The custom command migration process cannot be done using only Web services (see Section 1.7.5, Migrating Custom Commands and Workflow, for more information).
Migrate workflow processes before migrating entries.
First, the workflow-migration process cannot be done using only Web services (see Section 1.7.5, Migrating Custom Commands and Workflow, for more information). Second, any entry that is currently in a workflow state requires the presence of the workflow definition in Novell Teaming.
After migrating custom commands and workflow, you can migrate workflow associations for specific folders.
Finalizing operations include indexing folders and synchronizing any mirrored folders that you created.
Remember that migrated entries do not appear in the UI until you index the folders containing these entries.
The Novell Teaming UI does not begin to mirror the files on the drive until someone manually synchronizes them. The Web services call is equivalent to a manual synchronization in the UI.
Two operations require that you perform the operation for all items using one call to the message; they do not allow you to perform the operation incrementally on subsets of items, using multiple calls to the message. If you call these messages sequentially for subsets of the information, each successive call erases the established data from the previous call.
The messages that require you to perform the operation for all items using only one call are:
setDefinitions: Associates entry types with workflow processes (see setDefinitions).
setFunctionMembership: Sets access control for a workspace or folder (see setFunctionMembership).
Migrating users requires two steps:
Use either LDAP or the administration-portlet tool to add your Forum users to Novell Teaming.
Use the addUserWorkspace message to add personal workspaces for the new Novell Teaming users.
Migrating custom commands and workflow involve additional work in regard to users. See Section 1.7.5, Migrating Custom Commands and Workflow, for more information.
If you have a small number of files to migrate to Novell Teaming, you can use the migrateFolderFile message (see migrateFolderFile).
However, most Forum installations include a significant number of files, and those files might be large. To improve performance, you should strongly consider using the migrateFolderFileStaged message.
Staging involves moving all of the files from SiteScape Forum to the server running the Novell Teaming installation. Although the files can be located using any folder hierarchy on the server, a convenient way to migrate files is to unzip the Forum hidden directory onto the Novell Teaming server machine and to work within that existing folder hierarchy from Forum. After placing the files on the Novell Teaming server, the migrateFolderFileStaged message takes files from the staging area and migrates them into the Novell Teaming installation.
Here are the steps needed to migrate files:
Establish a directory on the Novell Teaming server machine where you want to place the Forum files.
Make the three required changes to the ssf.properties and ssf-ext.properties files. This action indicates the location of the staging directory. (See the installation guide for more information about the these files.)
Multiple Forum file versions are separate files in the staged area. Call the migrateFolderFileStaged message once for each version of the file, using the same filename for each call but specifying a different path. This method creates versioned files in Novell Teaming.
Copy the Forum files onto the Novell Teaming server, using the specified staging directory as your top directory.
Use the migrateFolderFileStaged message to migrate the files into the Novell Teaming installation.
This command attaches files to an existing entry. Also, it accepts as one of its arguments a relative path, which traverses the subfolders beneath the designated staging directory.
See migrateFolderFileStaged, for more information.
Migrating custom commands and workflow require tasks beyond the scope of using only Web services calls. It is highly recommended that you work closely with the Teaming support team while completing these tasks.
These are the general steps needed to migrate custom commands and workflow processes:
Migrate your Forum users to Novell Teaming.
Use the getAllPrincipalsAsXML message to get a list of the user identifiers for the newly created Teaming users.
Create a mapping file that maps Teaming user identifiers to Forum usernames.
Run a Tcl script-which uses the mapping file-to generate an XML file of workflow information.
Import the workflow XML file into Novell Teaming.
Create another mapping file, which maps workflow identifiers in Novell Teaming to Forum workflow names.
Run a Tcl script-which uses the second mapping file-to generate an XML file of custom command information.
Some custom commands are associated with workflow processes. Because of this, the mapping file of workflow information is necessary.
Import the custom command XML into Novell Teaming.
NOTE:This process migrates custom commands created using Forum’s user interface. It does not migrate template-based custom commands. To migrate template-based custom commands, use the Teaming entry designer and any necessary JSPs to recreate the command.