Sie sind auf Seite 1von 4

 Exporting and Importing a Web Content Library

Limitations of exporting and importing a Web content library.

 Draft items are not exported. Only published and expired items can be exported and
imported.

 Saved versions of items are not exported. Only the current version of each item is
exported.

 Children are only exported and imported when the parent is successfully exported and
imported.

 If an item exists on the target server with the same path, name and ID, then the item is
overwritten.

 Follow these steps to export and import a Web content library

a). Source server: The server that the data is being exported.
b). Target Server: The server that the data is being imported.
*Confirm that the following properties in the init section are set as specified, modifying the
properties if necessary:

 ExportDir: This is the directory on the source server where the exported data will be
written.
E.g - <property name="ExportDir" value="C:/JCR_Export"/>
 ImportDir: This is the directory from where the exported data will be read when
importing the data to the target server. If exporting and importing across a network, this can be
the same directory as the one specified in "ExportDir". Otherwise, you must copy the exported
data from the "ExportDir" to the "ImportDir" before running the import task in step 4.
E.g - <propertyname="ImportDir"value="C:/JCR_Import"/>
 SourceServerPort: The host name and port for the source server. By default, the port is
10038.
E.g - <propertyname="SourceServerPort"value=
"http://${WpsHostName}:${WpsHostPort}"/>
 TargetServerPort: The host name and port for the target server. By default, the port is
10038

E.g-<propertyname="TargetServerPort” value="http://$
{WpsHostName}:${WpsHostPort}"/>
 ExportUserId: If the source administrator is not the default (wpsadmin), set this value
to the source administrator short name.
E.g-<propertyname="ExportUserId” value="${PortalAdminId}"/>

 ExportPassword: Set this value to the source administrator password.


E.g-<propertyname="ExportPassword" value="$
{PortalAdminPwd}"/>
 ImportUserId: If the target administrator is not the default (wpsadmin), set this value to
the target administrator short name.
E.g-<propertyname="ImportUserId" value="${PortalAdminId}"/>
 ImportPassword: Set this value to the target administrator password.
E.g-<propertyname="ImportPassword" value="$
{PortalAdminPwd}"/>

 WebLib: The name of the Web content library to transfer.


E.g -<property name="WebLib" value="RiverBend"/>
 WebLibProperty: Set the value for this property to icm:title .
E.g -<property name="WebLibProperty" value="icm:title"/>

 Exporting a library
Follow these steps to export a library on the source server -

(1) Enter the property values in the


C:\ProgramFile\IBM\WebSphere\Portal
Server/jcr/migration/conf/wcm60_conf.xml
(2) Navigate to the directory <wp_profile_root>/ WPSconfig.bat in the console.
C:\ProgramFile\IBM\WebSphere\PortalServer\config\ WPSconfig.bat
(3) Run the following command–

Windows: WPSconfig.bat export-wcm-data


UNIX: WPSconfig.sh export-wcm-data
i5/OS: WPSconfig.sh -profileName profile_root export-wcm-data

(4) Verify the export process completed successfully by carefully reviewing the
messages available in the console and also check the Portal logs.
(5) The sample exported directory and its contents is provided.

Importing a library
Follow these steps to import a library on the target server -

(1) You may want to copy the exported directory from the source server to the target
server OR choose to perform the import process over the network.

(2) Enter the property values in the

C:\ProgramFile\IBM\WebSphere\Portal
Server/jcr/migration/conf/wcm60_conf.xml
(3) Navigate to the directory <wp_profile_root>/WPSconfig.bat in the console
C:\ProgramFile\IBM\WebSphere\PortalServer\config\ WPSconfig.bat
(4) Run the following command–

Windows: WPSconfig.bat import-wcm-data


UNIX: WPSconfig.sh import-wcm-data
i5/OS: WPSconfig.sh -profileName profile_root import-wcm-data
(5) Verify the import process completed successfully by carefully reviewing the
messages available in the console and also check the Portal logs.

(6) Stop the Portal server.

(7) Reset the Web content event log.

(8) Start the Portal server.

(9) Check the target Portal administration portlet and verify if the new library is
visible in the Web Content Libraries portlet.

Das könnte Ihnen auch gefallen