Untitled Document
Table of contents | Next | Previous
Exporting and importing libraries
WCM provides a capability to manually export a WCM library from a source
environment and then manually import it to a target environment. This
capability allows you to backup WCM libraries and also moves WCM libraries
between environments. However, this process cannot replace the WCM Syndication
process due to the following reasons -
a) Only published items can be exported using this method. This method will
not export draft items.
b) Only the current versions of items will be exported using this method.
c) Child items will only be exported and imported if the parent items have
been successfully exported and imported.
d) If an item exists on the target server with the same path, name and ID,
then the item is overwritten.
Note: If JSP components are being
used, you will need to manually move the related JSP files to the target
environment. The WCM Syndication process and the exporting and importing
libraries method behave the same way in this regard. |
The configuration information required to perform the WCM library export and
import process is stored in the file
<wp_profile_root>/PortalServer/wcm/config/wcm60_conf.xml
E.g. C:\IBM\WebSphere\wp_profile\PortalServer\wcm\config\wcm60_conf.xml
The configuration file contains property tags with “name” and “value”
attributes.
E.g. <property name="ExportDir"
value="C:/JCR_Export"/>
Note: Please use the / (forward
slash) character for separating directories on all platforms.
The table below describes the various property values used in the configuration
file. |
The server that the data is being exported from is called the source server,
and the server that the data is being imported into is called the target
server.
Property Name |
Description |
ExportDir |
The directory path on the source server
where the exported library will be saved once the export library process is
successfully completed.
This property is used by the export process.
Example -
<property name="ExportDir" value="C:/JCR_Export"
/> |
ImportDir |
The directory path from where the import
library process will read the files to be imported to the target server.
If you copy the exported directory from the source server to the
target server, this value will be the directory path available on the target
server.
If exporting and importing across a network, this can be the same
directory as the one specified in "ExportDir".
This property is used by the import process.
Example -
<property name="ImportDir"
value="C:/JCR_Import" /> |
SourceServerPort |
The host name and port for the source
server.
The default value set for this property is = http://$
{WpsHostName}:${WpsHostPort}
During our export test we used the default value.
This property is used by the export process.
Example -
<property name="SourceServerPort" value="http://$
{WpsHostName}:${WpsHostPort}"/> |
TargetServerPort |
The host name and port for the target
server.
The default value set for this property is = http://$
{WpsHostName}:${WpsHostPort}
During our import test we used the default value.
This property is used by the import process.
Example -
<property name="TargetServerPort"
value="http://${WpsHostName}:${WpsHostPort}"/> |
ExportUserId |
This value is only required if the source
server does not use the default Portal administrator ID “wpsadmin”. Enter the
short name of the administrator user.
The default value set for this property is = ${PortalAdminId}
During our export test we used the default value as our target
environment was configured to use wpsadmin as the Portal administrator.
This property is used by the export process.
Example -
<property name="ExportUserId"
value="${PortalAdminId}"/> |
ExportPassword |
The administrator user password on the
source server.
The default value set for this property is = ${PortalAdminId}
During our export test we used the default value as we had specified
the Portal administrator password in the <wp_profile_root> /
ConfigEngine/properties/wkplc.properties file.
This property is used by the export process.
Example -
<property name="ImportUserId"
value="${PortalAdminId}"/> |
ImportUserId |
This value is only required if the target
server does not use the default Portal administrator ID “wpsadmin”. Enter the
short name of the administrator user.
The default value set for this property is = ${PortalAdminId}
During our import test we used the default value as our target
environment was configured to use wpsadmin as the Portal administrator.
This property is used by the import process.
Example -
<property name="ExportPassword"
value="${PortalAdminPwd}"/> |
ImportPassword |
The administrator user password on the
target server.
The default value set for this property is = ${PortalAdminId}
During our import test we used the default value as we had specified
the Portal administrator password in the <wp_profile_root> /
ConfigEngine/properties/wkplc.properties file.
This property is used by the import process.
Example -
<property name="ImportPassword"
value="${PortalAdminPwd}"/> |
WebLib |
The name of the WCM library to be
transferred. The default option is to select the Web Content libraries by name.
In order to select the libraries by UUID, make sure to also change the
WebLibProperty below.
The default value set for this property is = Web Content.
During our export test we used the value = RiverBend.
This property is used by the export process.
Example -
<property name="WebLib" value="RiverBend"/>
|
WebLibProperty |
In order to select the libraries by name
(set by default), use the value = icm:title
To select the libraries by UUID, use the value = jcr:uuid
The default value set for this property is = icm:title
During our export test we used the default value.
This property is used by the export process.
Example -
<property name="WebLibProperty"
value="icm:title"/> |
Exporting a library
Follow these steps to export a library on the source server -
- Enter the property values in the
<wp_profile_root>/PortalServer/wcm/config/wcm60_conf.xml file
- Navigate to the directory <wp_profile_root>/ConfigEngine in the
console
- Run the following command–
- Windows platform: ConfigEngine.bat export-wcm-data
- Unix platform: ConfigEngine.sh export-wcm-data
- Verify the export process completed successfully by carefully reviewing
the messages available in the console and also check the Portal logs.
- The screen shot of the sample exported directory and its contents is
provided below.
Figure: Sample Exported Directory Contents
Importing a library
Follow these steps to import a library on the targer server -
- 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.
- Enter the property values in the
<wp_profile_root>/PortalServer/wcm/config/wcm60_conf.xml file
- Navigate to the directory <wp_profile_root>/ConfigEngine in the
console
- Run the following command–
- Windows platform: ConfigEngine.bat export-wcm-data
- Unix platform: ConfigEngine.sh export-wcm-data
- Verify the import process completed successfully by carefully reviewing
the messages available in the console and also check the Portal logs.
| Note: If the source and target
environments don't use the same LDAP server, you will notice warning messages.
You will need to use the Member Fixer tool to resolve this issue. |
- Stop the Portal server.
- Reset the Web content event log.
- Start the Portal server.
- Check the target Portal administration portlet and verify if the new
library is visible in the Web Content Libraries portlet.
Exporting and importing multiple libraries
You can only export a single library at a time by running the
"export-wcm-data" command. The "import-wcm-data" command
can be used to import multiple libraries at one time. If you are exporting and
importing multiple libraries it is best practice to export your individual
libraries to the same directory, and then import all your libraries from that
directory at the same time by using the "import-wcm-data" command.