The Repository Configuration Task

 

+
Search Tips   |   Advanced Search

 

Overview

By default, Web Content Management uses Cloudscape as a data repository. The WCM Repository configuration task updates the WCM configuration to use a different JDBC data repository such as DB2.

To transfer data to an IBM Content Manager data repository follow the instructions in the Storing Data in IBM Content Manager topic.

When transferring data to Microsoft SQL Server, enter the WcmDbUser name in uppercase in wpconfig.properties The WcmDbUser name must also be entered in uppercase in Microsoft SQL Server.

Before running this configuration task ensure that you have entered the WebSphere Portal Administrators Password in the PortalAdminPwd parameter in the Portal Config Properties section of...

/PortalServer/config/wpconfig.properties

Ensure that this password is also removed from wpconfig.properties once the configuration task is completed.

The Repository configuration task can be used to move data from one data repository to another data repository on a single instance of WCM. This task does not migrate data from one version of WCM to another. If you are upgrading WCM and are using the Repository configuration task to enable your data repository, migrate your old data after setting up the new data repository.

Only database transfers from Cloudscape to DB2 on z/OS are supported for z/OS installations.

 

Configure WCM to use an existing data repository

This option only configures WCM to use an existing WCM data repository. This existing data repository could be empty, or could contain WCM data.

Before running this task, edit...

/PortalServer/config/wpconfig.properties

...and include information about the data repository you intend to use.

To configure WCM to use an existing data repository:

  1. Stop the WebSphere_Portal server.

  2. Open a command prompt:

  3. Go to the /PortalServer/config

  4. Remove any existing data repository by running the following command. (This only removes the data repository references from the WCM configuration. It does not delete data from the data repository.):

    Windows: WPSconfig.bat remove-wcm-repository
    UNIX: WPSconfig.sh remove-wcm-repository
    i5/OS: WPSconfig.sh -instance [WAS Instance] remove-wcm-repository

  5. Re-configure WCM by running the following command:

    Windows: WPSconfig.bat config-wcm-repository
    UNIX: WPSconfig.sh config-wcm-repository
    i5/OS: WPSconfig.sh -instance [WAS Instance] config-wcm-repository

  6. If using this task to upgrade your WCM application, you will also need to migrate your User data.

 

Configure WCM to use an existing data repository and transfer current data to the existing data repository

This option is used to transfer data from your current data repository to a new data repository that you have already created. This new data repository must contain two empty tables (that you manually create) with the same name as the tables in the database you are transferring data from.

Before running this task, edit...

/PortalServer/config/wpconfig.properties

...to include information about the data repository you intend to use.

To transfer data to an existing data repository:

  1. Stop the WebSphere_Portal server.

  2. Open a command prompt.

  3. Go to the /PortalServer/config

  4. Run the following command:

    Windows: WPSconfig.bat transfer-wcm-to-existing-repository

    UNIX:

    		WPSconfig.sh transfer-wcm-to-existing-repository

    i5/OS:

    		WPSconfig.sh -instance [WAS Instance] transfer-wcm-to-existing-repository

 

Configure WCM to use a new data repository and transfer current data to the new data repository

This option is used to transfer data from your current data repository to an empty database with no tables. This empty database must be created prior to running this task.

Before running this task, edit...

/PortalServer/config/wpconfig.properties

...to include information about the data repository you intend to use.

To transfer data to a new data repository:

  1. Stop the WebSphere_Portal server.

  2. Open a command prompt.

  3. Go to the /PortalServer/config

  4. Run the following command:

    Windows:

    		WPSconfig.bat transfer-wcm-to-new-repository

    UNIX:

    		WPSconfig.sh transfer-wcm-to-new-repository

    i5/OS:

    		WPSconfig.sh -instance [WAS Instance] transfer-wcm-to-new-repository

 

Configure WCM to use a Cloudscape repository and transfer file system data to the Cloudscape data repository

This option is used to transfer data currently stored on the file system to a new Cloudscape data repository. This task would only be used when upgrading to the current version of WCM.

Before running this task, edit...

/PortalServer/config/wpconfig.properties

...to include information about the data repository you intend to use and to specify the location of your File System data ("WcmFileSystemDataLocation").

Note that transferring file system data to other databases This task can only be used to transfer file system data to a Cloudscape database. To transfer file system data to other database types initially transfer the file system data to Cloudscape, and then either:

  • transfer this data to another database using "transfer-wcm-to-existing-repository" or transfer-wcm-to-new-repository, or

  • setup a second WCM application and then syndicate the data to the second WCM application from the first. E.g. - you would need to do this to transfer file system data to a Content Manager repository.

When transferring data from file system to Cloudscape, and then to a DB2 on z/OS data repository ensure that the data has a valid format. For example: The XML files from the files system can only have either:

  • Carriage return and line feed (CRLF - windows end of line style), or

  • Just line feed (LF - unix end of line style)
An XML file that combines CRLF and LF in the same file will be classed as invalid and you will have problems when transferring it to z/OS. Even though most windows editors can view these files, they are not technically valid as they have inconsistent end of line styles.

  1. Stop the WebSphere_Portal server.

  2. Open a command prompt.

  3. Go to the /PortalServer/config

  4. Run the following command:

    Windows: WPSconfig.bat transfer-wcm-filesystem-to-cloudscape

    UNIX:

    		WPSconfig.sh transfer-wcm-filesystem-to-cloudscape

    i5/OS:

    		WPSconfig.sh -instance [WAS Instance] transfer-wcm-filesystem-to-cloudscape

  5. If using this task to upgrade your WCM application, you will also need to migrate your User data.

Parent topic: Configuration Tasks.

Parent topic: Data Storage.

IBM Workplace WCM - V5.1.0.1 -

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.