In WebSphere Portal how to Export and Import WebContent Library ?

We can export the contents of a web content library to disk and import this data into another web content server. With this process we can make a backup copy of a web content library, and can also be used to move data between servers. But this function cannot be used to send updates, deletes and moves. It is only suitable for populating new items.

1. Exporting and importing a web content library versus syndication.

    This feature does not replace the syndication feature. Although this feature can be used to transfer data between servers, it is a manual process and is not meant to be used for regular updates between servers. Syndication is instead used to automatically keep two or more servers synchronized. Also, whereas syndication can be used to send updates, deletes and moves, the import feature is only suitable for populating new items.

2. Limitations of exporting and importing a web content library.

    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.
    Library and item level access controls are left unchanged when a library is exported and imported. You need to run the member fixer tool on the imported library to fix references to missing users and groups.You cannot import an item if an item on the target server has the same ID but a different parent than the item being imported.

3. Disabling JCR text search :

    It is recommended you disable JCR text search indexing on your WebSphere® Portal server before exporting or importing large libraries to reduce the load on the database during export and import. Edit the wp_profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties file and set the jcr.textsearch.enabled property to false. After the file is updated, restart your server for the changes to take effect. When you have completed exporting or importing your library you must then enable JCR text search again. It can take some time to rebuild the indexes when you re-enable JCR text search indexing.

4. Exporting and importing large libraries :

    When importing web content libraries, a temporary directory is used to store the library files during the upload process. If the size of the uploaded files exceeds the available disk space for the temporary directory, the import operation fails. When uploading large libraries, ensure that there is sufficient disk space to accommodate the import. The location of the temporary directory is specified by the jcr.binaryValueFileDir property in the wp_profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties file.
    When exporting or importing large libraries, increase the total transaction lifetime timeout and the maximum transaction timeout of your server to 360 seconds through the WebSphere Application Server administrative console. To change these settings, go to Servers > Server Types > WebSphere application servers > portal_server > Container Services > Transaction Service

Export Process :
----------------------
1. Log in to the IBM® WebSphere Application Server administration console on the source server.
2. Goto, Resources -> Resource Environment -> Resource Environment Providers -> WCM WCMConfigService -> Custom properties.
3. Create or update the export properties.
1. export.directory = ${USER_INSTALL_ROOT}/PortalServer/wcm/ilwwcm/system/export (default location of exporting files)
2. export.libraryname = Lib_1;Lib_2;Lib_3 (ex : SourceLibrary; which library to be exported)
3. export.singledirectory = true/false (If set to true, multiple libraries are written into a single directory specified by the export)

Note: You must restart your server any time you change these settings.

4. Open a command prompt on the source server and goto 'wp_profile_root/ConfigEngine' and run 'export-wcm-data' command;
1. ConfigEngine.bat export-wcm-data -DWasPassword=password -DPortalAdminPwd=password   -- for windows
2. ./ConfigEngine.sh export-wcm-data -DWasPassword=password -DPortalAdminPwd=password  -- for unix
3. ConfigEngine.sh export-wcm-data -DWasPassword=password -DPortalAdminPwd=password    -- for i/os

Note : If you get error of unable to delete .sql database, check permissions

Note:
1. You can override the export.directory property defined in the WCM WCMConfigService service by using the -Dexport.directory parameter. For example:
  export-wcm-data -Dexport.directory=c:\export
2. You can override the export.singledirectory property defined in the WCM WCMConfigService service by using the -Dexport.singledirectory parameter.
  For example: export-wcm-data -Dexport.singledirectory=false saves the exported libraries under different directories.
3. You can override the export.libraryname property defined in the WCM WCMConfigService service by using the -Dexport.libraryname parameter. For
  example: export-wcm-data -Dexport.libraryname=libraryname
4. To ensure that your exported libraries can be successfully imported, do not change the names of any of the folders or files within the exported data.

Import Process :
----------------------
1. Log in to the IBM® WebSphere Application Server administration console on the source server.
2. Goto, Resources -> Resource Environment -> Resource Environment Providers -> WCM WCMConfigService -> Custom properties.
3. Create or update the export properties.
1. import.directory = this is the path of the directory where you kept exported directory.i.e ${USER_INSTALL_ROOT}/PortalServer/wcm/ilwwcm/system/export

Note: You must restart your server any time you change these settings.

4. Open a command prompt on the source server and goto 'wp_profile_root/ConfigEngine' and run 'import-wcm-data' command;
1. ConfigEngine.bat import-wcm-data -DWasPassword=password -DPortalAdminPwd=password   -- for windows
2. ./ConfigEngine.sh import-wcm-data -DWasPassword=password -DPortalAdminPwd=password  -- for unix
3. ConfigEngine.sh import-wcm-data -DWasPassword=password -DPortalAdminPwd=password    -- for i/os

Note:
1. You can override the import.directory property defined in the WCM WCMConfigService service by using the -Dimport.directory parameter. For example:
  import-wcm-data -Dimport.directory=c:\import\Lib1

Ref Url :
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Exporting_and_importing_a_web_content_library_wcm7



Thanks,
MS

What is the difference between WebSphere Portal and WebSphere Portal Express ?

As far as Portal functionality is concerned, both Portal and Portal Express are identical. You'll install the same Portal in both cases.

The actual differences are limited to the license and the bundle you get. 

Portal Express was designed to be an out of the box production ready environment for smaller businesses. It's a different license package from "WebSphere Portal Enable or Portal Extend". It installs and configures DB2 out of the box (as opposed to Derby for Portal Enable/Extend). Also the license forbids clustering with Express.

The major differences between the two are:

1. The licenses and CD bundle
2. Express installs/configures DB2 out of the box; Portal installs/configures Derby
3. Express license forbids clustering; Portal license does not

For more details on Express, visit this link:
http://www-01.ibm.com/software/genservers/portalexpress/


Difference between IBM® WebSphere® Portal Extend and IBM WebSphere Portal Enable?

WebSphere Portal Enable and WebSphere Portal Extend are the same, with the only difference being that WebSphere Portal Extend versions come bundled with the Lotus® Collaborative Components (including Lotus Notes®, Sametime® and QuickPlace®).



Thanks,
MS