H Migrating Folders_g to FrameworkFolders

This appendix describes how to migrate Oracle WebCenter Portal content from the Folders_g folder service to the FrameworkFolders folder service on Oracle WebCenter Content Server.

This appendix includes the following sections:

H.1 Understanding Folders_g Migration to FrameworkFolders

Oracle WebCenter Content offers two folder solutions: Folders_g and FrameworkFolders. The Folders_g component (aka the Contribution Folders interface) provides a hierarchical folder interface to content on Content Server. The FrameworkFolders component (aka the Folders interface) also provides a hierarchical folder interface similar to a conventional file system, for organizing and locating some or all of the content in the repository. However, Folders is a scalable, enterprise solution and is designed to replace Contribution Folders as the folder service for Content Server.

For a completely new installation of Oracle WebCenter Portal, it is recommended that you enable the FrameworkFolders component on Content Server. For an Oracle WebCenter Portal instance patched from an earlier version that used the Folders_g folder service, you can choose to continue with Folders_g or migrate to the FrameworkFolders folder service. Oracle recommends that you enable the FrameworkFolders component for better performance and so as to be able to use any new Content Server features.

Note:

FrameworkFolders is the name of the component that replaces the older Folders_g component. The older Folder interface is now referred to as Contribution Folders. The interface supported by the FrameworkFolders component is referred to as Folders.

In this chapter, the migration process has been described using the terms FrameworkFolders and Folders_g. Unless referring to a UI selection or a command, the term FrameworkFolders can be used interchangeably with Folders, and the term Folders_g can be used interchangeably with Contribution Folders.

For more information about the migration procedure, see the "Migrating Folders_g to Folders" chapter in Administering Oracle WebCenter Content.

Figure H-1 and Table H-1 depict the Oracle WebCenter Portal installation starting points that best describes your current environment, and the path you can follow to choose the Folders_g and FrameworkFolders folder services.

Figure H-1 Starting Points for Folders_g and FrameworkFolders Setups

Description of Figure H-1 follows
Description of ''Figure H-1 Starting Points for Folders_g and FrameworkFolders Setups''

Table H-1 Starting Points for Folders_g and FrameworkFolders Setups

Starting Point Task Sub-task

New installation of Oracle WebCenter Portal?

Enable the FrameworkFolders component

 

Existing installation of Oracle WebCenter Portal 11g upgraded to 11.1.1.9.0?

Choose whether to continue using Folders_g or migrate to FrameworkFolders.

To continue using Folders_g, no further configuration is required.

When migrating from Folders_g to FrameworkFolders:

  • Same Content Server: If WebCenter Portal and Portal Framework applications are connected to the same Content Server, migrate them together.

  • Different Content Servers: If WebCenter Portal and Portal Framework applications are connected to different instances of Content Server, migrate them separately.


H.2 Understanding the Folders_g and FrameworkFolders Directory Structure

Both Folders_g and FrameworkFolders provide a hierarchical folder interface, however, the way content is organized differs in these two setups. This section describes the directory structure used for organizing content in Folders_g and FrameworkFolders.

When WebCenter Portal uses a Content Server repository with Folders_g enabled, portals are stored under the WebCenter Portal root folder. Each user has a personal folder (the Home portal) stored under the path /PersonalSpaces, and this folder is named after the user. Whereas, when WebCenter Portal is configured to use FrameworkFolders, all portal folders and personal folders are treated as enterprise libraries and are stored under the path /Enterprise Libraries. Portal folders are named after the portal and personal folders are usually named after the user.

For example, consider a company with the following portals and users:

  • HR Portal: contains HR policies and documents

  • Partner Portal: contains documents related to partners

  • Users: Karen, Monty, and Sam

Figure H-2 shows how WebCenter Portal folders are organized in the Folders_g and FrameworkFolders setups on Content Server. In a Folders_g setup, personal folders for users Karen, Monty, and Sam are organized under PersonalSpaces, and the portals HR Portal and Partner Portal are organized under the WebCenter Portal root folder WebCenter0202. In a FrameworkFolders setup, personal folders Karen, Monty, and Sam and the portal folders HR Portal and Partner Portal are organized under Enterprise Libraries.

Figure H-2 Folders_g and FrameworkFolders Folder Structure on Content Server

Description of Figure H-2 follows
Description of ''Figure H-2 Folders_g and FrameworkFolders Folder Structure on Content Server''

For example, if Karen creates any new folders in the Home portal in a Folders_g setup, the new folders are created under /PersonalSpaces/Karen as shown in Figure H-3.

Figure H-3 Folder Path When Folders_g is Enabled

Description of Figure H-3 follows
Description of ''Figure H-3 Folder Path When Folders_g is Enabled ''

If Karen creates any new folders in the Home portal in a FrameworkFolders setup, the new folders are created under /Enterprise Libraries/Karen as shown in Figure H-4.

Figure H-4 Folder Path When FrameworkFolders is Enabled

Description of Figure H-4 follows
Description of ''Figure H-4 Folder Path When FrameworkFolders is Enabled ''

Item Level Security in Folders_g and FrameworkFolders

In the Folders_g setup, Item Level Security (ILS) can be set on files and folders. ILS settings on folders are inherited by all files within a folder unless a file has its own ILS defined. In the FrameworkFolders setup, ILS can be set only on files. ILS cannot be set on folders.

After you migrate from Folders_g to FrameworkFolders, you will not be able set ILS for a folder, but the ILS settings on each file contained in that folder are retained. You can update or remove file-level ILS settings after migration.

H.3 Migrating WebCenter Portal and Portal Framework Applications Connected to Separate Content Servers

This section describes the steps for migrating WebCenter Portal and Portal Framework applications from Folders_g to FrameworkFolders setup when they are connected to separate Content Servers. You can choose to migrate WebCenter Portal and Portal Framework applications in any order. It is not mandatory to migrate WebCenter Portal first.

H.3.1 Migrating WebCenter Portal Metadata to FrameworkFolders

This section describes the procedure for migrating WebCenter Portal content from Folders_g to FrameworkFolders.

This section includes the following subsections:

H.3.1.1 Migration Roadmap

The flow chart (Figure H-5) and the table (Table H-2) in this section provide an overview of the steps required to migrate WebCenter Portal content from Folders_g to FrameworkFolders.

Note:

In a clustered environment, you must bring down all the managed servers except one WebCenter Portal managed server and one WebCenter Content managed server. Ensure that you run the migration WLST commands from the machine where WebCenter Portal is running.

In a non-clustered environment, if WebCenter Portal and WebCenter Content managed servers run on different machines, run the migration WLST commands from the machine where WebCenter Portal is running.

Figure H-5 Migrating WebCenter Portal Data from Folders_g to FrameworkFolders

Description of Figure H-5 follows
Description of ''Figure H-5 Migrating WebCenter Portal Data from Folders_g to FrameworkFolders ''

Table H-2 Migrating WebCenter Portal Data from Folders_g to FrameworkFolders

Task Description Documentation

Run the exportFoldersGData WLST command

Run the exportFoldersGData WLST command from the WebCenter Portal Oracle home directory to generate the pre-migration data.

Section H.3.1.2, "Running exportFoldersGData to Generate the Pre-Migration Data."

Migrate Folders_g metadata for WebCenter Portal to FrameworkFolders

Run the migration utility on Content Server to migrate WebCenter Portal data from Folders_g to FrameworkFolders.

Section H.3.1.3, "Migrating WebCenter Portal MetaData to FrameworkFolders."

Run the migrateFoldersGDataToFrameworkFolders WLST command

Run the migrateFoldersGDataToFrameworkFolders WLST command from the WebCenter Portal Oracle home directory to validate the migrated data.

Section H.3.1.4, "Running migrateFoldersGDataToFrameworkFolders to Validate the Migrated Data."

Restart all the managed servers

Restart all the managed servers, including the WebCenter Portal and Content Server managed servers.

See "Starting and Stopping Oracle WebLogic Server Instances" in Administrator's Guide.


H.3.1.2 Running exportFoldersGData to Generate the Pre-Migration Data

Use the WLST command exportFoldersGData to generate the Folders_g pre-migration data:

exportFoldersGData(appName,server,[connectionName,directoryPath,applicationVersion])

The following example exports the Folders_g data for a WebCenter Portal application deployed to the WC_Spaces managed server. The content server connection named MyContentServerConnection is used, and Folders_g data exported to the /scratch/myTemp_Dir directory.

exportFoldersGData(appName='webcenter',server='WC_Spaces',connectionName='MyContentServerConnection',directoryPath='/scratch/myTemp_Dir/')

For command syntax and examples, see the "exportFoldersGData" section in WebLogic Scripting Tool Command Reference. You must run this command from the WebCenter Portal Oracle home directory. For information about how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

The pre-migration data generated by exportFoldersGData can be used to generate data consistency reports and ascertain the sanity of the migrated files and folders after you have migrated WebCenter Portal data to FrameworkFolders.

The exportFoldersGData WLST command performs the following tasks:

  • Generates the pre-migration metadata for all portal folders under the WebCenter Portal root folder

  • Generates the pre-migration metadata for all user folders under the Home portal root folder

  • Writes the generated metadata to the PreMigrationData.csv file.

  • Exports all MDS documents

The PreMigrationData.csv file includes the following metadata for the portal folders and user folders stored in the Folders_g data structure:

  • Folder name for the WebCenter Portal root folder or the Home portal root folder

  • dCollectionGUID, the identifier used by WebCenter Portal to map a portal to the corresponding folder on Content Server

  • dCollectionID, the identifier used in Folders_g to uniquely identify a folder

  • dCollectionName, the folder name

  • dSecurityGroup, the security group

  • dDocAccount, the account name

By default, PreMigrationData.csv is stored at the following path: WCP_ORACLE_HOME/common/wlst/FG_FF_MIGRATION. You can choose a different location for the file while running the exportFoldersGData WLST command.

Figure H-6 shows a sample PreMigrationData.csv file. Each row displays the metadata for a portal folder or a user folder.

Figure H-6 Sample PreMigrationData.csv File

Description of Figure H-6 follows
Description of ''Figure H-6 Sample PreMigrationData.csv File''

H.3.1.3 Migrating WebCenter Portal MetaData to FrameworkFolders

You use the Folders Migration utility available on Content Server to migrate WebCenter Portal metadata and folder structure from Folders_g to FrameworkFolders.

To migrate WebCenter Portal metadata from Folders_g to FrameworkFolders:

  1. Log on to Content Server as an administrator.

  2. Enable Framework Folders. Ensure Folders_g is also enabled. For information, see Section 9.2.3.1, "Enabling Mandatory Components."

    Note:

    When you migrate from the Folders_g to the FrameworkFolders setup, both the Folders_g and FrameworkFolders components must be enabled during the migration process.
  3. Add the following attribute to the config.cfg file:

    MigrationFormatForfApplicationGUID=dCollectionName:dCollectionGUID

    The config.cfg file is available at WCC_DOMAIN/ucm/cs/config/config.cfg, where WCC_DOMAIN refers to the Oracle WebCenter Content domain.

  4. Restart Content Server, and log on as an administrator.

  5. Choose Administration, then Folder Migration to begin performing data migration.

  6. Migrate the PersonalSpaces root folder.

    1. Under the Run Migration section on the Folder Migration page, click Modify Excluded Folders.

    2. In the Folder Migration: Excluded Folders dialog, specify the folders that need to be excluded from migration. Ensure that all folders other than the PersonalSpaces root folder appear in the Legacy Folders to Exclude from Migration box. In Figure H-7, WebcenterSpaces-Root refers to the WebCenter Portal root folder.

      Figure H-7 Specifying Folders Excluded from Migration

      Description of Figure H-7 follows
      Description of ''Figure H-7 Specifying Folders Excluded from Migration''

    3. Click OK.

    4. Click Migrate Folder Data to migrate the data.

  7. Migrate the WebCenter Portal root folder.

    1. Under the Run Migration section, click Modify Excluded Folders.

    2. In the Folder Migration: Excluded Folders dialog, ensure that all folders other than the WebCenter Portal root folder appear in the Legacy Folders to Exclude from Migration box. In Figure H-8, WebcenterSpaces-Root refers to the WebCenter Portal root folder.

      Figure H-8 Specifying Folders Excluded from Migration

      Description of Figure H-8 follows
      Description of ''Figure H-8 Specifying Folders Excluded from Migration''

    3. Click OK.

    4. Click Migrate Folder Data to migrate the data.

  8. Remove the MigrationFormatForfApplicationGUID attribute added in step 3.

  9. Restart Content Server.

  10. If Contribution Folders contains any content that is referenced in WebCenter Portal, you must migrate the Contribution Folders folder as an enterprise library.

    1. In the Run Migration section, click Modify Excluded Folders.

    2. In the Folder Migration: Excluded Folders dialog, ensure that all folders other than Contribution Folders appear in the Legacy Folders to Exclude from Migration box (Figure H-9).

      Figure H-9 Specifying Folders Excluded from Migration

      Description of Figure H-9 follows
      Description of ''Figure H-9 Specifying Folders Excluded from Migration''

    3. Click OK.

    4. In the Folder Migration Destination section, click Browse to specify the destination for the folders to be migrated.

    5. In the Browse dialog, select Enterprise Libraries, and click OK.

    6. Click Migrate Folder Data.

  11. Migrate folders other than PersonalSpaces, the WebCenter Portal root folder, and Contribution Folders if they contain any content that is referenced in WebCenter Portal. Follow the same procedure that you used in step 10.

    In the Folder Migration: Excluded Folders dialog, ensure that all folders other than the folder you want to migrate are listed in the Legacy Folders to Exclude from Migration box.

  12. Disable Folders_g.

    On the Advanced Component Manager page, from the Enabled Components list box, select Folders_g and click Disable. For information about accessing this page, see Section 9.2.3.1.2, "Enabling the Folders_g Component."

  13. Restart Content Server.

  14. Rebuild the collection and update the search index using the Repository Manager utility. When rebuilding the collection, ensure that the Use fast rebuild check box is unchecked in the Indexer Rebuild dialog (Figure H-10). For information, see "Working with the Search Index" section in Administering Oracle WebCenter Content.

    Figure H-10 Rebuilding the Index

    Description of Figure H-10 follows
    Description of ''Figure H-10 Rebuilding the Index''

Logs generated during the migration process are available at WCC_DOMAIN/servers/UCM_server1/logs, where WCC_DOMAIN refers to the Oracle WebCenter Content domain.

H.3.1.4 Running migrateFoldersGDataToFrameworkFolders to Validate the Migrated Data

Use the migrateFoldersGDataToFrameworkFolders WLST command to migrate Folders_g data to FrameworkFolders and check the integrity of the migrated data:

migrateFoldersGDataToFrameworkFolders(appName,server,contentDbConnectionUrl,contentDbUserName,[connectionName,directoryPath,reportMode,applicationVersion])

The following example migrates Folders_g data from the /scratch/myTemp_Dir directory to FrameworkFolders and validates the migrated data for the WebCenter Portal application deployed to the WC_Spaces managed server. Content Server connection named MyContentServerConnection and the specified WebCenter Content database connection and username are used to perform the migration.

migrateFoldersGDataToFrameworkFolders(appName='webcenter',server='WC_Spaces',contentDbConnectionUrl='wccdbhost.example.com:wccdbport:wccdbsid', contentDbUserName='SCHEMA_PREFIX_OCS',connectionName='MyContentServerConnection',directoryPath='/scratch/myTemp_Dir/)

The path specified in the directoryPath attribute must be the same that you specified while running the exportFoldersGData WLST command.

For command syntax and examples, see the "migrateFoldersGDataToFrameworkFolders" section in WebLogic Scripting Tool Command Reference. For information about how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

The migrateFoldersGDataToFrameworkFolders command performs the following tasks:

  • Generates the metadata for the migrated WebCenter Portal content and validates it against the pre-migration metadata generated by the exportFoldersGData WLST command. It verifies that each migrated folder is an enterprise library, and the values for the account name and the security group are same as the pre-migration metadata.

    Any data inconsistency is reported in the summary text displayed after the command is executed, and is also stored in a log file available at this default location: WCP_ORACLE_HOME/common/wlst/POST_MIGRATION/MigrationDiagnostic.log.

  • Creates MigrationMap.csv, a mapping file that maps the Folders_g identifier dCollectionID to the FrameworkFolders identifier fFolderGUID. The mapping file is stored here: Migration_Directory/POST_MIgration/MigrationMap.csv.

    In case of any folder name changes, the file also contains a mapping of the Folders_g path and the FrameworkFolders path. For example, suppose there is a user folder named Monty, and also a portal folder by the same name. In the Folders_g setup, the user folder Monty appears under the PersonalSpaces root folder, and the portal folder Monty appears under the WebCenter Portal root folder (such as, WebCenter0202). During migration, PersonalSpaces folders are migrated first. To resolve the folder name conflict, the portal folder is renamed as Monty(WebCenter0202), as shown in Figure H-11. This folder path change is stored in the mapping file.

    Figure H-11 FrameworkFolders Directory Structure After Migration

    Description of Figure H-11 follows
    Description of ''Figure H-11 FrameworkFolders Directory Structure After Migration''

  • Using the mapping file, replaces the dCollectionID value with the fFolderGUID value in the MDS documents generated by the exportFoldersGData WLST command. It also replaces any old path references containing the WebCenter Portal root folder name or PersonalSpaces, with the new path. For example, /PersonalSpaces/weblogic is replaced with /Enterprise Libraries/weblogic.

    Any inconsistencies are reported in MigrationDiagnostic.log. For troubleshooting information, see Section H.5, "Troubleshooting Migration Issues."

  • Imports all the updated MDS documents.

H.3.2 Migrating Portal Framework Applications to FrameworkFolders

This section describes the procedure for migrating Portal Framework application metadata from Folders_g to FrameworkFolders.

This section includes the following subsections:

H.3.2.1 Migration Roadmap

The flow chart (Figure H-12) and the table (Table H-3) in this section provide an overview of the steps required to migrate Portal Framework applications from Folders_g to FrameworkFolders.

Figure H-12 Migrating a Portal Framework Application from Folders_g to FrameworkFolders

Description of Figure H-12 follows
Description of ''Figure H-12 Migrating a Portal Framework Application from Folders_g to FrameworkFolders''

Table H-3 Migrating Portal Framework Application Data from Folders_g to FrameworkFolders

Task Description Documentation

Run the exportFoldersGData WLST command

Run the exportFoldersGData WLST command from WebCenter Portal Oracle home directory to export the pre-migration data.

Section H.3.2.2, "Exporting the Folders_g Data for a Portal Framework Application"

Run the Folders Migration utility on Content Server

Run the migration utility on Content Server to migrate your Portal Framework application's data from Folders_g to FrameworkFolders.

Section H.3.2.3, "Migrating Portal Framework Application MetaData to FrameworkFolders"

Run the migrateFoldersGDataToFrameworkFolders WLST command

Run the migrateFoldersGDataToFrameworkFolders WLST command from WebCenter Portal Oracle home directory to validate the migrated data.

Section H.3.2.4, "Validating the Migrated Data"

Migrate the source code and redeploy the Portal Framework application

Migrate the source code of the Portal Framework application, and redeploy the application.

Section H.3.2.5, "Migrating the Source Code of the Portal Framework Application"

Restart the managed server where Portal Framework application is deployed

Restart the managed server where the Portal Framework application is deployed.

Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments"


H.3.2.2 Exporting the Folders_g Data for a Portal Framework Application

Use the WLST command exportFoldersGData to export the Folders_g data for your Portal Framework application. The following is the command syntax:

exportFoldersGData(appName,server,[connectionName,directoryPath,applicationVersion])

The following example exports the Folders_g data for a Portal Framework application named customapp, deployed to the Custom_Server managed server. The content server connection named MyContentServerConnection is used, and Folders_g data exported to the /scratch/myTemp_Dir directory.

exportFoldersGData(appName='customapp',server='Custom_Server',connectionName='MyContentServerConnection',directoryPath='/scratch/myTemp_Dir/')

For details about the command syntax and examples, see the "exportFoldersGData" section in WebLogic Scripting Tool Command Reference. You run this command from the WebCenter Portal Oracle home directory. For information about how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

Folders_g pre-migration data generated by exportFoldersGData is used by the WLST command migrateFoldersGDataToFrameworkFolders to generate data consistency reports and verify that all files and folders have been correctly migrated to FrameworkFolders.

The exportFoldersGData WLST command performs the following tasks:

  • Generates pre-migration metadata for the Portal Framework application

  • Writes the generated metadata to the PreMigrationData.csv file

  • Exports all MDS documents

The PreMigrationData.csv file includes the following metadata for the Portal Framework application:

  • Folder name for the Portal Framework application

  • dCollectionGUID, the identifier used to map the Portal Framework application to the folder on Content Server

  • dCollectionID, the identifier used in Folders_g to uniquely identify a folder

  • dCollectionName, the name of the Portal Framework application

  • dSecurityGroup, the security group

  • dDocAccount, the account name

By default, the output file is stored at the following path: WCP_ORACLE_HOME/common/wlst/FG_FF_MIGRATION. You can choose a different location for the file while running the exportFoldersGData WLST command.

Figure H-6 shows a sample PreMigrationData.csv file. Each row displays the metadata for a Portal Framework application:

Figure H-13 Sample PreMigrationData.csv File

Description of Figure H-13 follows
Description of ''Figure H-13 Sample PreMigrationData.csv File''

H.3.2.3 Migrating Portal Framework Application MetaData to FrameworkFolders

You use the Folders Migration utility available on Content Server to migrate a Portal Framework application's metadata and folder structure from Folders_g to FrameworkFolders.

To migrate Portal Framework application metadata from Folders_g to FrameworkFolders:

  1. Log on to Content Server as an administrator.

  2. Enable Framework Folders. Ensure Folders_g is also enabled. For information, see Section 9.2.3.1, "Enabling Mandatory Components."

    Note:

    When you migrate from the Folders_g to the FrameworkFolders setup, both the Folders_g and FrameworkFolders components must be enabled during the migration process.
  3. Restart Content Server, and log on as an administrator.

  4. Choose Administration, then Folder Migration.

  5. To specify folders to be excluded from the migration process, click the Modify Excluded Folders link (Figure H-14). This displays the Folder Migration: Excluded Folders dialog.

  6. Select one or more folders from the Browse Legacy Folders pane that you want to exclude, for example, PersonalSpaces and Trash. The selected folders are moved to the Legacy Folders to Exclude from Migration pane, as shown in Figure H-15.

    For a Portal Framework application, you need to migrate the top-level folder(s) to which the application is wired, for example Contribution Folders or the WebCenter Portal root folder. Ensure these folders are not included in the exclude list.

    Figure H-15 Excluding Folders from Migration

    Description of Figure H-15 follows
    Description of ''Figure H-15 Excluding Folders from Migration''

  7. Click OK.

  8. In the Folder Migration Destination section, click Browse to specify the destination for the folders to be migrated.

  9. In the Browse dialog, select Enterprise Libraries, and click OK (Figure H-16).

    Figure H-16 Selecting Folder Migration Destination

    Description of Figure H-16 follows
    Description of ''Figure H-16 Selecting Folder Migration Destination''

    The folders selected for migration will get migrated as enterprise libraries under Enterprise Libraries.

  10. Click Migrate Folder Data.

  11. Disable Folders_g.

    On the Advanced Component Manager page, from the Enabled Components list box, select Folders_g and click Disable. For information about accessing this page, see Section 9.2.3.1.2, "Enabling the Folders_g Component."

  12. Restart Content Server.

  13. Rebuild the collection and update the search index using the Repository Manager utility. When rebuilding the collection, ensure that the Use fast rebuild check box is unchecked in the Indexer Rebuild dialog (Figure H-10). For information, see the "Working with the Search Index" section in Administering Oracle WebCenter Content.

    Figure H-17 Rebuilding the Index

    Description of Figure H-17 follows
    Description of ''Figure H-17 Rebuilding the Index''

Logs generated during the migration process are available at WCC_DOMAIN/servers/UCM_server1/logs, where WCC_DOMAIN refers to the Oracle WebCenter Content domain.

H.3.2.4 Validating the Migrated Data

Use the migrateFoldersGDataToFrameworkFolders WLST command to migrate Folders_g data to FrameworkFolders and check integrity of the migrated data.

Syntax:

migrateFoldersGDataToFrameworkFolders(appName,server,[contentDbConnectionUrl,contentDbUserName,connectionName,directoryPath,reportMode,applicationVersion])

The following example migrates the Folders_g data from the /scratch/myTemp_Dir directory to FrameworkFolders for the Portal Framework application named customapp, which is deployed to the server Custom_Server. MyContentServerConnection is the Content Server connection used to perform migration.

migrateFoldersGDataToFrameworkFolders(appName='customapp',server='Custom_Server',connectionName='MyContentServerConnection',directoryPath='/scratch/myTemp_Dir/')

The path specified in the directoryPath attribute must be the same that you specified while running the exportFoldersGData WLST command.

For details about the command syntax and examples, see the "migrateFoldersGDataToFrameworkFolders" section in WebLogic Scripting Tool Command Reference. For information about how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

The migrateFoldersGDataToFrameworkFolders command performs the following tasks:

  • Generates the metadata for the migrated Portal Framework application content and validates it against the pre-migration metadata generated by the exportFoldersGData WLST command. It verifies that each migrated folder is an enterprise library, and the value for the account name and the security group are same as the pre-migration metadata.

    Any data inconsistency is reported in the summary text displayed after the command is executed, and is also stored in a log file available at the default location here: WCP_ORACLE_HOME/common/wlst/POST_MIGRATION/MigrationDiagnostic.log.

  • Creates a mapping file that maps the Folders_g identifier dCollectionID to the FrameworkFolders identifier fFolderGUID. The mapping file is available here: Migration_Directory/POST_MIgration/MigrationMap.csv.

  • Using the mapping file, replaces the value of dCollectionID with the fFolderGUID value in the MDS documents generated by the exportFoldersGData WLST command.

    Any inconsistencies are reported in MigrationDiagnostic.log. For troubleshooting information, see Section H.5, "Troubleshooting Migration Issues."

  • Imports all the updated MDS documents.

H.3.2.5 Migrating the Source Code of the Portal Framework Application

After you have migrated the Portal Framework application to the FrameworkFolders setup, you must also migrate the source code of the application and redeploy the application.

To migrate the source code of a Portal Framework application:

  1. Copy the Folders_g pre-migration data on the machine that contains the source code for the Portal Framework application. By default, Folders_g pre-migration data is exported to the WCP_ORACLE_HOME/common/wlst/FG_FF_MIGRATION directory path.

  2. Go to WCP_ORACLE_HOME/webcenter/archives.

  3. Run the following command:

    java -jar foldersg-metadata-migration-tool.jar source AppSourceRootDirectory PreMigrationDataDirectory UCMConnectionName UCMUser UCMConnectionUrl ReportMode
     
    

    Where:

    • source: Identifier to specify that the source code of the application needs to be migrated. Specify the value as source.

    • AppSourceRootDirectory: Path to the Portal Framework application's source code directory.

    • PreMigrationDataDirectory: Path to the directory where you copied the Folders_g pre-migration data.

    • UCMConnectionName: Name of the Content Server connection.

    • UCMUser: Name of the Content Server user.

    • UCMConnectionUrl: Content Server URL in the format idc://server:port.

    • ReportMode : If this argument is set to true, a report file is generated when the command is executed. This report file contains all the metadata changes that will be made during the actual migration. The default value of the argument is false.

      Note: When this argument is set to true and the WLST command is executed, the actual migration does not occur.

    For example, the following command migrates the source code for the Portal Framework application named doclibCusApp using the Content Server connection my-ucm.

    java -jar foldersg-metadata-migration-tool.jar source /home/monty/doclibCusApp /home/monty/cusapp/PRE_MIGRATION my-ucm sysadmin
     
    
  4. Compile and redeploy the Portal Framework application. For information, see Section 42.3, "Redeploying Portal Framework Applications."

    After redeploying the Portal Framework application, you must restart the managed server where the application is deployed. For information, see Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

H.4 Migrating WebCenter Portal and Portal Framework Applications Connected to the Same Content Server

The flow chart (Figure H-18) and the table (Table H-4) in this section provide an overview of the steps required to migrate WebCenter Portal and Portal Framework application data from Folders_g to FrameworkFolders when they are connected to the same Content Server.

Figure H-18 Migrating WebCenter Portal and Portal Framework Applications Wired to the Same Content Server

Description of Figure H-18 follows
Description of ''Figure H-18 Migrating WebCenter Portal and Portal Framework Applications Wired to the Same Content Server''

Table H-4 Migrating WebCenter Portal and Portal Framework Applications Wired to the Same Content Server

Task Description Documentation

Run the exportFoldersGData WLST command for WebCenter Portal data

Run the exportFoldersGData WLST command to export the pre-migration data for WebCenter Portal.

Section H.3.1.2, "Running exportFoldersGData to Generate the Pre-Migration Data"

Run the exportFoldersGData WLST command for each Portal Framework application

Run the exportFoldersGData WLST command for each Portal Framework application to export its pre-migration data.

Section H.3.2.2, "Exporting the Folders_g Data for a Portal Framework Application"

Ensure FrameworkFolders and Folders_g are enabled

Enable the FrameworkFolders component. Also, ensure that Folders_g is enabled.

Section 9.2.3.1, "Enabling Mandatory Components"

Migrate WebCenter Portal data, and then the Portal Framework application data

Run the migration utility on Content Server to migrate the WebCenter Portal data, and then the Portal Framework application data from Folders_g to FrameworkFolders.

Section H.4.1, "Migrating WebCenter Portal and Portal Framework Application Metadata"

Run the migrateFoldersGDataToFrameworkFolders WLST command for WebCenter Portal

Run the migrateFoldersGDataToFrameworkFolders WLST command to validate the migrated data for WebCenter Portal.

Note that it is mandatory to specify the contentDbConnectionUrl and contentDbUserName parameters for the WebCenter Portal application.

Section H.3.1.4, "Running migrateFoldersGDataToFrameworkFolders to Validate the Migrated Data"

Run the migrateFoldersGDataToFrameworkFolders WLST command for the Portal Framework application

Run the migrateFoldersGDataToFrameworkFolders WLST command to validate the migrated data for the Portal Framework application.

Note that it is optional to specify the contentDbConnectionUrl and contentDbUserName parameters for Portal Framework applications.

Section H.3.2.4, "Validating the Migrated Data"

Restart the WC_Spaces managed server

Restart the WC_Spaces managed server.

Section 7.3, "Starting and Stopping the WebCenter Portal Application"

Migrate the source code of the Portal Framework application and redeploy the application

Migrate the source code of the Portal Framework application and redeploy the application.

Section H.3.2.5, "Migrating the Source Code of the Portal Framework Application"

Restart the managed server where Portal Framework application is deployed

Restart the managed server where the Portal Framework application is deployed.

Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments"


H.4.1 Migrating WebCenter Portal and Portal Framework Application Metadata

To migrate the WebCenter Portal and Portal Framework application metadata from Folders_g to FrameworkFolders when they are connected to the same Content Server:

  1. Log on to Content Server as an administrator.

  2. Add the following attribute to the config.cfg file: MigrationFormatForfApplicationGUID=dCollectionName:dCollectionGUID

    The config.cfg file is available at WCC_DOMAIN/ucm/cs/config/config.cfg, where WCC_DOMAIN refers to the Oracle WebCenter Content domain.

  3. Restart Content Server and log on as an administrator.

  4. Choose Administration, then Folder Migration.

  5. Migrate the PersonalSpaces root folder.

    1. Under the Run Migration section on the Folder Migration page, click Modify Excluded Folders.

    2. In the Folder Migration: Excluded Folders dialog, specify the folders that need to be excluded from migration. Ensure that all folders other than the PersonalSpaces root folder appear in the Legacy Folders to Exclude from Migration pane (Figure H-19).

      Figure H-19 Specifying Folders Excluded from Migration

      Description of Figure H-19 follows
      Description of ''Figure H-19 Specifying Folders Excluded from Migration''

    3. Click OK.

    4. Click Migrate Folder Data to migrate the data.

  6. Migrate the WebCenter Portal root folder.

    1. Under the Run Migration section, click Modify Excluded Folders.

    2. In the Folder Migration: Excluded Folders dialog, ensure that all folders other than the WebCenter Portal root folder appear in the Legacy Folders to Exclude from Migration box.

    3. Click OK.

    4. Click Migrate Folder Data to migrate the data.

  7. Remove the MigrationFormatForfApplicationGUID attribute from config.cfg added in step 2.

  8. Restart Content Server and log on as an administrator.

  9. If Contribution Folders contains content that is referenced in WebCenter Portal or your Portal Framework application is wired to Contribution Folders, migrate Contribution Folders as an enterprise library.

    1. In the Run Migration section, click Modify Excluded Folders.

    2. In the Folder Migration: Excluded Folders dialog, ensure that all folders other than Contribution Folders appear in the Legacy Folders to Exclude from Migration box (Figure H-9).

      Figure H-20 Specifying Folders Excluded from Migration

      Description of Figure H-20 follows
      Description of ''Figure H-20 Specifying Folders Excluded from Migration''

    3. Click OK.

    4. In the Folder Migration Destination section, click Browse to specify the destination for the folders to be migrated.

    5. In the Browse dialog, select Enterprise Libraries, and click OK (Figure H-21).

      Figure H-21 Selecting Folder Migration Destination

      Description of Figure H-21 follows
      Description of ''Figure H-21 Selecting Folder Migration Destination''

    6. Click Migrate Folder Data.

  10. Migrate folders other than PersonalSpaces, the WebCenter Portal root folder, and Contribution Folders if they contain any content that is referenced in WebCenter Portal or Portal Framework applications. You must migrate the folders as enterprise libraries. Follow the same procedure that you used in step 9.

    In the Folder Migration: Excluded Folders dialog, ensure that all folders other than the folder you want to migrate are listed in the Legacy Folders to Exclude from Migration box.

  11. Disable Folders_g.

    On the Advanced Component Manager page, from the Enabled Components list box, select Folders_g and click Disable. For information about accessing this page, see Section 9.2.3.1.2, "Enabling the Folders_g Component."

  12. Restart Content Server.

  13. Rebuild the collection and update the search index using the Repository Manager utility. When rebuilding the collection, ensure that the Use fast rebuild check box is unchecked in the Indexer Rebuild dialog (Figure H-10). For information, see "Working with the Search Index" section in Administering Oracle WebCenter Content.

    Figure H-22 Rebuilding the Index

    Description of Figure H-22 follows
    Description of ''Figure H-22 Rebuilding the Index''

Logs generated during the migration process are available at WCC_DOMAIN/servers/UCM_server1/logs, where WCC_DOMAIN refers to the Oracle WebCenter Content domain.

H.5 Troubleshooting Migration Issues

This section provides information to assist you in troubleshooting the problems you may encounter while migrating the Folders_g setup to the FrameworkFolders setup.

Problem

The migration summary displayed for the migrateFoldersGToFrameworkFolders WLST command contains a warning that a few MDS documents contain Folders_g path references that do not adhere to any known patterns.

Solution

Manually verify the MigrationDiagnostic.log file present in the WCP_ORACLE_HOME/common/wlst/POST_MIGRATION directory and look for the warning messages. For the specified files, verify whether the Content Server path reference is valid. If required, manually update the Folders_g path to the FrameworkFolders path and import the file.

Problem

When you run the exportFoldersGData WLST command for a non-primary Content Server connection for WebCenter Portal, the following exception is reported in the MigrationDiagnostic.log file:

oracle.stellent.ridc.protocol.ServiceException: Unable to open folder. 

Solution

When you have multiple Content Server connections registered, to run the exportFoldersGData WLST command using a non-primary Content Server connection, set it as the active connection and specify the Root Folder and Application Name values. After running exportFoldersGData, set the active connection back to the previous Content Server connection and continue with migration.

Problem

Navigation links in Portal Framework applications are not visible after migration from the Folders_g to the FrameworkFolders folder service. After migration of the Portal Framework applications deployed to the WC_CustomPortal managed server, the following exception is reported in the migration log:

oracle.webcenter.content.integration.spi.ucm.UCMBridge setTrashStatus[[SEVERE: Unable to retrieve trash status for repository UCM.  When calling service COLLECTION_GET_ADMIN_MARKED_CONFIG, as user sysadmin, at timestamp7/28/14 3:21 AM, recieved status code -32.

Solution

If your Oracle WebCenter Portal environment has both WC_Spaces and WC_CustomPortal managed servers configured, before migrating the Portal Framework application, verify the WEBCENTER schema. In the WC_PORTAL_PROPERTIES table, if the WCPP_VALUE row contains the value FOLDERS_G, you must delete the row.

Problem

Both WebCenter Portal and Portal Framework applications are connected to the same Content Server, and the startFolderPath in the document task flows in Portal Framework applications is specified as /PersonalSpaces. After migration of Portal Framework applications from the Folders_g folder service to the FrameworkFolders folder service, content is not visible in the document task flows. For example, if startFolderPath = /PersonalSpaces/Karen, content of the document task flow in Portal Framework applications is not visible.

Solution

Update the startFolderPath attribute to replace /PersonalSpaces with /Enterprise Libraries. You must update this both in the source code of the application and on the managed server on which the application is deployed.

In the source code of the Portal Framework application:

  1. Search the .xml files for /PersonalSpaces and replace with /Enterprise Libraries.

    For example, if the value of startFolderPath is set to /PersonalSpaces/Karen, change it to /Enterprise Libraries/Karen.

  2. Compile and redeploy the Portal Framework application, as described in Section 42.3, "Redeploying Portal Framework Applications."

On the Managed Server where the Portal Framework application is deployed:

  1. Export the .xml files of your Portal Framework application using the exportMetadata WLST command and back up the files. For information about exportMetadata, see the "exportMetadata" section in WebLogic Scripting Tool Command Reference.

  2. In the exported .xml files, search for /PersonalSpaces and replace with /Enterprise Libraries.

    For example, if the value of startFolderPath is /PersonalSpaces/Karen, change it to /Enterprise Libraries/Karen.

  3. Import the .xml files back using the importMetadata WLST command. For information about importMetadata, see the "importMetadata" section in WebLogic Scripting Tool Command Reference.

Problem

Your WebCenter Portal application and Portal Framework applications include custom codes that use various Folders_g services-based queries. After migration to FrameworkFolders, the queries do not work.

Solution

Folders_g services cannot be used in WebCenter Portal and Portal Framework applications migrated to FrameworkFolders. If your application includes Folders_g services, after migration you must replace them with the equivalent FrameworkFolders services. Table H-5 provides a mapping of Folders_g services and the corresponding FrameworkFolders services.

For information about FrameworkFolders services, see the "Folders Services" chapter in Services Reference for Oracle WebCenter Content.

Table H-5 Mapping of Folders_g Services with FrameworkFolders Services

Folders_g Service FrameworkFolders Service

COLLECTION_ADD

FLD_CREATE_FOLDER

COLLECTION_BROWSE

FLD_INFO

COLLECTION_COPY_COLLECTION

FLD_COPY (with item1 specified as a folder)

COLLECTION_COPY_ITEM

FLD_COPY (with item1 specified as a file)

COLLECTION_COPY_LOT

FLD_COPY (with items specified)

COLLECTION_DELETE

FLD_DELETE

COLLECTION_DELETE_COLLECTION

FLD_DELETE (with item1 specified as a folder)

COLLECTION_DELETE_ITEM

FLD_DELETE (with item1 specified as a file)

COLLECTION_DELETE_LOT

FLD_DELETE (with items specified)

COLLECTION_DISPLAY

FLD_BROWSE

COLLECTION_GET_COLLECTIONS

FLD_RETRIEVE_CHILD_FOLDERS

COLLECTION_GET_CONTENTS

FLD_RETRIEVE_CHILD_FILES

COLLECTION_GET_LINKS

FLD_INFO (with item1 specified as a shortcut)

COLLECTION_GET_REFERENCE

FLD_INFO (with path specified or item1 specified as a path)

COLLECTION_INFO

FLD_INFO

COLLECTION_MOVE_ALL

FLD_MOVE (with items specified)

COLLECTION_MOVE_COLLECTION

FLD_MOVE (with item1 specified as a folder)

COLLECTION_MOVE_ITEM

FLD_MOVE (with item1 specified as a file)

COLLECTION_MOVE_LOT

FLD_MOVE (with items specified)

COLLECTION_SEARCH_RESULTS

FLD_FOLDER_SEARCH

COLLECTION_UPDATE

FLD_EDIT_FOLDER