25 Managing Export, Import, Backup, and Recovery of WebCenter

Oracle WebCenter stores data related to its configuration and content for the various feature areas in several locations. To facilitate disaster recovery and the full production lifecycle from development through staging and production, WebCenter provides a set of utilities that enable you to back up this data, move the data between WebCenter applications in staging and production environments. This chapter describes the backup, import, and export capabilities and tools available. It includes the following sections:

To best plan the proper usage of these tools, record which WebCenter features your WebCenter applications are using: WebCenter Framework, WebCenter Spaces, Oracle WebCenter Discussions Server, Oracle WebCenter Wiki and Blog Server, and so on.

Audience

The content of this chapter is intended for Fusion Middleware administrators (users granted the Admin role through the Oracle WebLogic Server Administration Console) and WebCenter Spaces administrators (users granted the WebCenter Spaces Administrator role or a custom role that grants the Application-Manage permission).

See also, Section 1.8, "Understanding Administrative Operations, Roles, and Tools".

25.1 Exporting and Importing WebCenter Spaces for Data Migration

WebCenter Spaces provides a set of export and import utilities that enable you to back up or move content between WebCenter Spaces applications and stage or production environments. This section describes how to export and import the whole WebCenter Spaces application, and also individual group spaces and group space templates. It includes the following subsections:

Migrating an entire WebCenter Spaces application:

Migrating group spaces:

Migrating group space templates:

25.1.1 Understanding WebCenter Spaces Export and Import

Using export and import, Fusion Middleware administrators can migrate entire WebCenter Spaces applications between stage and production environments. This includes every personal space, group space, group space template, and also application and service customizations (applied to the application, pages, and task flows), application and service metadata (object definitions), and data, as outlined in Figure 25-1.

Figure 25-1 Information Exported with WebCenter Spaces

Information Exported with WebCenter Spaces

This migration can be performed using Fusion Middleware Control Console or WLST commands. For details, see:

Group Space and Group Space Template Export and Import

WebCenter Spaces administrators can also export and import individual group spaces and group space templates, and their related objects, through WebCenter Spaces Administration and using WLST Commands.

The primary purpose of these export and import features is to enable cloning and migration of data. The export and import combination enables WebCenter Spaces administrators to:

  • Move content between stage and production environments.

  • Move content to remote instances.

For more detail, see.

Customizations and Personalizations

Some WebCenter Spaces customizations are optional on export, as noted in Figure 25-1. If you want to migrate these customizations you must set the export option "Include Customizations". For more information, reference Table 25-3, "WebCenter Spaces - Service Customizations" and Table 25-4, "WebCenter Spaces - Application and Group Space Customizations" at the end of this chapter.

User personalizations are not migrated during export and import. For more information on customization and personalization and the difference between them, see "Customizing and Personalizing Page Content" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.

25.1.2 Prerequisites for WebCenter Spaces Export and Import

The Oracle Database in which the application metadata or schema is stored must be up and running for the successful completion of the export and import operation.

All the back-end components must be migrated before you export or import a WebCenter Spaces application. For more information, refer to the next section, Section 25.1.3, "Migrating Back-end Components for an Entire WebCenter Spaces Application".

WebCenter Spaces is temporarily unavailable during import and export operations to prevent data conflicts. Any user who tries to login or access WebCenter Spaces pages will see an "application unavailable" page.

25.1.3 Migrating Back-end Components for an Entire WebCenter Spaces Application

Before migrating a WebCenter Spaces application, you must migrate all the back-end components that are used by the application. This section tells you how to migrate the Identity Store, Credential Store, Policy Store, Oracle WebCenter Discussions Server, Oracle WebCenter Wiki Server, Oracle Content Server, Oracle WebLogic Communications Server, and portlet producers.

The configured services in the target instance must be a superset of the services that are configured in the source instance. That is, the target must be configured with at least the same set of services that the source is configured with. If this is not the case, the import will fail.

This section includes the following sub-sections:

25.1.3.1 Exporting the LDAP Identity Store

To export users, groups, and passwords from an external identity store, use the ldapsearch command. This command creates an ldif file, which the ldapadd command uses during the import operation. The ldapsearch utility is located in the OID/IdM IDM_ORACLE_HOME/bin directory.

Example 25-1 shows the ldapsearch command for exporting an LDAP identity store. Where LDAP_OH/bin is the OID/IdM IDM_ORACLE_HOME/bin directory:

Example 25-1 ldapsearch Command to Export LDAP Identity Store

LDAP_OH/bin/ldapsearch -h ldap_hostname -p ldap_port -D  "cn=ldap_user" -w password -b "cn=users,dc=example,dc=com"
-s subtree "objectclass=*" "*" orclguid -L > my_users.ldif

When exporting users, ensure that the command includes the orclguid attribute, for as shown in Example 25-1.

To migrate groups, repeat the command with appropriate group base DN. For example: -b "cn=groups,dc=example,dc=com"

For detailed syntax and examples, see "ldapsearch" and "ldapaddmt" in Oracle Fusion Middleware User Reference for Oracle Identity Management.

For information on migrating an external LDAP identity store, refer to "Managing Directory Entries" and "Performing Bulk Operations" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

Note:

To migrate users, groups, and passwords between two embedded LDAP servers, refer to "Exporting and Importing Information in the Embedded LDAP Server" in Oracle Fusion Middleware Securing Oracle WebLogic Server. Ensure that the command includes the orclguid attribute.

The source and target LDAP servers must both be the same type, that is, both embedded LDAP servers or both external LDAP servers. It is not possiible, for example, to migrate users, groups, and passwords stored in an embedded LDAP server to an external LDAP server.

25.1.3.2 Importing the LDAP Identity Store

To import users and groups from another external identity store, use the ldapaddmt utility. The ldapaddmt utility is located in the OID/IdM IDM_ORACLE_HOME/bin directory.

Example 25-2 shows how to run the ldapaddmt utility to import the ldif file. Where LDAP_OH/bin is the OID/IdM IDM_ORACLE_HOME/bin directory:

Example 25-2 ldapaddmt Utility to Import the ldif File

LDAP_OH/bin/ldapaddmt -h ldap_hostname -p ldap_port -D "cn=ldap_user" -w password -c -r -f my_users.ldif

For detailed syntax and examples, see "ldapaddmt" in Oracle Fusion Middleware User Reference for Oracle Identity Management.

For information on migrating the LDAP identity store, refer to "Managing Directory Entries" and "Performing Bulk Operations" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

Note:

To import users, groups, and passwords from another embedded LDAP server, refer to "Exporting and Importing Information in the Embedded LDAP Server" in Oracle Fusion Middleware Securing Oracle WebLogic Server.

The source and target LDAP servers must both be the same type, that is, both embedded LDAP servers or both external LDAP servers. It is not possiible, for example, to migrate users, groups, and passwords stored in an embedded LDAP server to an external LDAP server.

25.1.3.3 Exporting and Importing the LDAP Credential Store

To migrate your credential store to a different target, use the WLST command migrateSecurityStore. Before running this command you must specify details relating to your source credential store in a jps-config.xml file.

  1. Create your own jps-config.xml (namedjps-config-cred.xml in this example) and then specify the domain name, JPS root, and LDAP URL of the source credential store:

    1. Create a copy of your target's jps-config.xml file, located at DOMAIN_HOME/config/fmwconfig/jps-config.xml, and name the copy jps-config-cred.xml as follows:

      cp MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config.xml 
MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config-cred.xml

      , and name the copy jps-config-cred.xml as follows:

      cp MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config.xml 
MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config-cred.xml

    2. In the jps-config-cred.xml file, duplicate the following section:

      <serviceInstance provider="ldap.credentialstore.provider" name="credstore.ldap">
  ...
</serviceInstance>

      The next few steps describes how to edit this new section to point to your source credential store. Once complete, jps-config-cred.xml file will contain both source and target information for the migration process.

    3. First, change the name of the new element to indicate that it contains source information. For example, change:

      From: name="credstore.ldap."

      To: name="credstore.ldap.s"

    4. Modify the domain name, JPS root, and LDAP URL values as appropriate. For example:

      <serviceInstance provider="ldap.credentialstore.provider" name="credstore.ldap.s">
            <property value="bootstrap" name="bootstrap.security.principal.key"/>
            <property value="cn=my_domain" name="oracle.security.jps.farm.name"/>
            <property value="cn=jpsroot_webcenter_mytest_to_prod" name="oracle.security.jps.ldap.root.name"/>
            <property value="ldap:myhost:myport" name="ldap.url"/>
        </serviceInstance>

    5. Since we're only concerned with the credential store, modify the <jpsContext name="default"> element, removing references to the identity store and the policy store. For example:

      <jpsContext name="default">
     <serviceInstanceRef ref="keystore"/>
     <serviceInstanceRef ref="audit"/>
     <serviceInstanceRef ref="credstore.ldap"/>
</jpsContext>

    6. Duplicate the <jpsContext> element, and change the name in the new <jpsContext> element to "source". For example, change:

      From: <jpsContext name="default">

      To: <jpsContext name="source">

    7. Modify the credential store reference to point to the value specified in step c. For example:

      <jpsContext name="source">
     <serviceInstanceRef ref="keystore"/>
     <serviceInstanceRef ref="audit"/>
     <serviceInstanceRef ref="credstore.ldap.s"/>
</jpsContext>

  2. Find the name of the source folder using the ldapsearch utility.

    For example, enter:

    LDAP_OH/bin/ldapsearch -h srcldap_hostname -p ldap_port -D  "cn=ldap_user" -w password -b "" -s sub "cn=<application_name>-*"

    Where <application_name> is the name of the source WebCenter application.

    The folder name returned is named: <application_name>-xxxx

    For WebCenter Spaces, <application_name> is always webcenter. If, for example, the source folder is named webcenter-1646, the following information might be returned:

    cn=webcenter-1646,cn=CredentialStore,cn=my_domain, cn=JPSContext,  cn=jpsroot_webcenter_t2ptest
objectclass=top
objectclass=orclContainercn=webcenter-1646

  3. Find the name of the destination folder using the ldapsearch utility.

    For example, enter:

    LDAP_OH/bin/ldapsearch -h dstldap_hostname -p ldap_port -D  "cn=ldap_user" -w password -b "" -s sub "cn=<application_name>-*"

    Where <application_name> is the name of the destination WebCenter application.

    The folder name returned is named: <application_name>-xxxx

    For WebCenter Spaces, <application_name> is always webcenter.

  4. To import the credential store, run the WLST command migrateSecurityStore.

    For example (Example 25-3):

    Example 25-3 migrateSecurityStore - Credential Store

    migrateSecurityStore(type="credStore", configFile="/MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config-cred.xml",
src="source", dst="default", overWrite="true", srcFolder="<source folder>", dstFolder="<destination folder>")

    For detailed syntax and examples, see "migrateSecurityStore" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

25.1.3.4 Exporting and Importing the LDAP Policy Store

With WebCenter Spaces, there is no need for manual policy store migration because the WebCenter Spaces export/import commands migrate security policy data for you. For details, see Section 25.1.4, "Exporting an Entire WebCenter Spaces Application".

While Oracle does not recommend that you perform policy store migration manually for WebCenter Spaces, there may be circumstances where this is required. In such cases, use the WLST command migrateSecurityStore to perform the migration as described below.

For custom WebCenter applications, always use the migrateSecurityStore command to migrate security policy data.

Before running the migrateSecurityStore command you must specify details relating to your source policy store in a jps-config.xml file.

  1. Create your own jps-config.xml (namedjps-config-policy.xml in this example) and then specify the domain name, JPS root, and LDAP URL of the source policy store:

    1. Create a copy of your target's jps-config.xml file, located at DOMAIN_HOME/config/fmwconfig/jps-config.xml, and name the copy jps-config-policy.xml as follows:

      cp MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config.xml 
MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config-policy.xml

    2. In the jps-config-policy.xml file, duplicate the following section:

      <serviceInstance provider="ldap.policystore.provider" name="policystore.ldap">
  ...
</serviceInstance>

      The next few steps describes how to edit this new section to point to your source policy store. Once complete, jps-config-policy.xml file will contain both source and target information for the migration process.

    3. First, change the name of the new element to indicate that it contains source information. For example, change:

      From: name="policystore.ldap."

      To: name="policystore.ldap.s"

    4. Modify the domain name, JPS root, and LDAP URL values as appropriate. For example:

      <serviceInstance provider="ldap.policytore.provider" name="policystore.ldap.s">
            <property value="bootstrap" name="bootstrap.security.principal.key"/>
            <property value="cn=my_domain" name="oracle.security.jps.farm.name"/>
            <property value="cn=jpsroot_webcenter_mytest_to_prod" name="oracle.security.jps.ldap.root.name"/>
            <property value="ldap:myhost:myport" name="ldap.url"/>
        </serviceInstance>

    5. Duplicate the <jpsContext> element, and change the name in the new <jpsContext> element to "source". For example, change:

      From: <jpsContext name="default">

      To: <jpsContext name="source">

    6. Modify the policy store reference to point to the value specified in step c, removing references to the identity store and the credential store. For example:

      <jpsContext name="source">
    <serviceInstanceRef ref="keystore"/>
    <serviceInstanceRef ref="audit"/>
    <serviceInstanceRef ref="policystore.ldap.s"/>
</jpsContext>

    7. Modify the <jpsContext name="default"> element, removing references to the identity store and the credential store. For example:

      <jpsContext name="default">
     <serviceInstanceRef ref="keystore"/>
     <serviceInstanceRef ref="audit"/>
     <serviceInstanceRef ref="policystore.ldap"/>
</jpsContext>

  2. Find the full name of the source WebCenter application using the ldapsearch utility.

    For example, enter:

    LDAP_OH/bin/ldapsearch -h srcldap_hostname -p srcldap_port -D  "cn=ldap_user" -w password -b "" -s sub "orclapplicationcommonname=<application_name>*"

    Where <application_name> is the name of the source WebCenter application.

    The application name returned is: <application_name>xxxx

    For WebCenter Spaces, <application_name> is always webcenter. If, for example, the full source application name is webcenter#V2.0, the following information might be returned:

    cn=webcenter\#V2.0,cn=my_domain,cn=JPSContext,cn=jpsroot_webcenter_t2ptest
objectclass=top
objectclass=orclJavaApplicationEntity
orclapplicationcommonname=webcenter#V2.0cn=webcenter#V2.0

  3. Find the full name of the destination WebCenter application using the ldapsearch utility.

    For example, enter:

    LDAP_OH/bin/ldapsearch -h dstldap_hostname -p dstldap_port -D  "cn=ldap_user" -w password -b "" -s sub "orclapplicationcommonname=<application_name>*"

    Where <application_name> is the name of the destination WebCenter application.

    The application name returned is: <application_name>xxxx

    For WebCenter Spaces, <application_name> is always webcenter.

  4. To import the policy store, run the WLST command migrateSecurityStore.

    For example (Example 25-4):

    Example 25-4 migrateSecurityStore - Policy Store

    migrateSecurityStore(type="appPolicies", configFile="/MW_HOME/user_projects/domains/my_domain/config/fmwconfig/jps-config-policy.xml",
src="source",dst="default",overWrite="true", srcApp="<full application name>", dstApp="<full application name>")

    For detailed syntax and examples, see "migrateSecurityStore" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

25.1.3.5 Exporting and Importing a File-based Credential Store

To migrate a file-based credential store to a different target, use the WLST command migrateSecurityStore. Before running this command you must specify details relating to your source credential store in the target's jps-config.xml file.

  1. Backup your target's jps-config.xml file located at DOMAIN_HOME/config/fmwconfig/jps-config.xml.

  2. Add source and target information to the target's jps-config.xml:

    1. Add the following section (above the closing </serviceInstances> tag) to point to the source credential store:

      <serviceInstance name="sourcecredstore" provider="credstoressp" location="/MW_HOME/user_projects/domains/base-domain/config/fmwconfig/.">
      <description>File Based Credential Store Service Instance</description>
</serviceInstance>

      Replace /MW_HOME/user_projects/domains/base-domain with the path to the source domain.

    2. Update the credential store reference to point to the value specified in step a. Add the following entries above the closing </jpsContexts> tag:

      <jpsContext name="targetcredstore">
      <serviceInstanceRef ref="credstore"/>
</jpsContext>
<jpsContext name="sourcecredstore">
       <serviceInstanceRef ref="sourcecredstore"/>
</jpsContext>

  3. Import the file-based credential store using the WLST command migrateSecurityStore.

    For example (Example 25-5):

    Example 25-5 migrateSecurityStore - Credential Store

    migrateSecurityStore(type="credStore", configFile="/MW_HOME/user_projects/domains/base-domain/config/fmwconfig/jps-config.xml", src="sourcecredstore", dst="targetcredstore")

    Note that the configFile parameter maps to the jps-config.xml file in the target domain, and that the src and dst parameters map to the newly created jpsContext elements.

    For detailed syntax and examples, see "migrateSecurityStore" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

Output similar to the following displays and includes a WARNING that you can ignore:

{srcFolder=null, preserveAppRoleGuids=null, dst=targetcredstore, type=credStore, dstFolder=null, resourceTypeFile=null, dstLdifFile=null, srcApp=null, configFile=/scratch/product/target/user_projects/domains/domain4/config/fmwconfig/jps-config.xml, dstApp=null, srcConfigFile=null, src=sourcecredstore, overWrite=null, migrateIdStoreMapping=null, processPrivRole=null}
Oct 26, 2009 11:23:42 AM oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstCredential setCredential
WARNING: Cannot migrate credential folder/key webcenter-1111/anonymous#oracle.portlet.client.adapter.adf.ADFPortletContainerExternalConfig.Reason oracle.security.jps.service.credstore.CredentialAlreadyExistsException: The credential with map webcenter-1111 and key anonymous#oracle.portlet.client.adapter.adf.ADFPortletContainerExternalConfig already exists.

25.1.3.6 Exporting and Importing a File-based Policy Store

With WebCenter Spaces, there is no need for manual policy store migration because the WebCenter Spaces export/import commands migrate security policy data for you. For details, see Section 25.1.4, "Exporting an Entire WebCenter Spaces Application".

While Oracle does not recommend that you perform policy store migration manually for WebCenter Spaces, there may be circumstances where this is required. In such cases, use the WLST command migrateSecurityStore to perform the migration as described below.

For custom WebCenter applications, always use the migrateSecurityStore command to migrate security policy data.

Before running the migrateSecurityStore command you must specify details relating to your source policy store in your target's jps-config.xml file.

  1. Backup your target's jps-config.xml file located at DOMAIN_HOME/config/fmwconfig/jps-config.xml.

  2. Add source and target information to the target's jps-config.xml:

    1. Add the following section (above the closing </serviceInstances> tag) to point to the source policy store:

      <serviceInstance name="srcpolicystore.xml" provider="policystore.xml.provider" location="/MW_HOME/user_projects/domains/base_domain/config/fmwconfig/system-jazn-data.xml">    <description>File Based Policy Store Service Instance</description></serviceInstance>

      Replace /MW_HOME/user_projects/domains/base-domain with the path to the source domain.

    2. Update the policy store reference to point to the value specified in step a. Add the following entries above the closing </jpsContexts> tag:

      <jpsContext name="targetFileStore">
     <serviceInstanceRef ref="policystore.xml"/>
</jpsContext>
<jpsContext name="sourceFileStore">
     <serviceInstanceRef ref="srcpolicystore.xml"/>
</jpsContext>

  3. Import the file-based credential store using the WLST command migrateSecurityStore.

    For example (Example 25-6):

    Example 25-6 migrateSecurityStore - Credential Store

    migrateSecurityStore(type="appPolicies", srcApp="webcenter", configFile="/MW_HOME/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml", src="sourceFileStore", dst="targetFileStore", overWrite="true")

    Note that the configFile parameter maps to the jps-config.xml file in the target domain, and that the src and dst parameters map to the newly created jpsContext elements.

    For detailed syntax and examples, see "migrateSecurityStore" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

Output similar to the following displays and includes a WARNING that you can ignore:

{srcFolder=null, dst=targetFileStore,type=appPolicies, dstFolder=null, resourceTypeFile=null,dstLdifFile=null, srcApp=webcenter,configFile=/scratch/product/target/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml,dstApp=null, srcConfigFile=null, src=sourceFileStore, overWrite=true,migrateIdStoreMapping=null, processPrivRole=null}Oct 26, 2009 4:14:42 AM oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy <init>WARNING: No identity store associate with policy store found.wls:/offline>

25.1.3.7 Exporting Oracle WebCenter Discussions Server

To export Oracle WebCenter Discussions Server, use the database export utility. For example, go to WC_ORACLE_HOME/bin of your database and run the command described in Example 25-7.

Note:

The Oracle Data Pump utility does not support LONG columns types that exist in the DISCUSSIONS schema. Therefore, Oracle recommends using Oracle Database Utilities. See also, the Oracle Database Utilities guide.

Example 25-7 Export Database Utility

DB_ORACLE_HOME/bin/expdp \"sys/password@serviceid as sysdba\" OWNER=srcrcuprefix_DISCUSSIONS FILE=/tmp/df.dmp STATISTICS=none

where:

  • DB_ORACLE_HOME is the directory in which the database for Oracle WebCenter Discussions Server schema is installed.

  • password is the password for the system database user.

  • serviceid is the service ID of the database connection.

  • OWNER is the schema to be exported. This is the RCU suffix that was used during installation, _DISCUSSIONS, along with the user supplied prefix. For example, DEV_DISCUSSIONS.

  • FILE contains the exported data.

25.1.3.8 Importing Oracle WebCenter Discussions Server

To import Oracle WebCenter Discussions Server, use the database import utility.

Note:

The Oracle Data Pump utility does not support LONG columns types that exist in the DISCUSSIONS schema. Therefore Oracle recommends using Oracle Database Utilities. See also, the Oracle Database Utilities guide.

  1. Shut down the target Oracle WebCenter Discussions Server.

  2. Go to DB_ORACLE_HOME/bin of the database where Oracle WebCenter Discussions Server schema is installed, and connect to the database using sqlplus as sysdba:

    DB_ORACLE_HOME/bin/sqlplus "sys/password@serviceid as sysdba"

  3. Drop the target user:

    drop user tgtrcuprefix_DISCUSSIONS cascade;

  4. Create the target user:

    create user tgtrcuprefix_DISCUSSIONS identified by password default tablespace tgtrcuprefix_IAS_DISCUSSIONS temporary tablespace name_IAS_TEMP;

  5. Grant connect and resource to the user:

    grant connect,resource to tgtrcuprefix_DISCUSSIONS;

  6. Exit sqlplus.

  7. Run the import tool as described in Example 25-8.

    Example 25-8 Database Import Utility

    DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\" FROMUSER=srcrcuprefix_DISCUSSIONS TOUSER=tgtrcuprefix_DISCUSSIONS FILE=/tmp/df.dmp STATISTICS=none

    where:

    • DB_ORACLE_HOME is the directory in which the database for Oracle WebCenter Discussions Server schema is installed.

    • password is the password for the system database user.

    • serviceid is the service ID of the database connection.

    • FROMUSER is the exported schema.

    • TOUSER is the imported schema. This is the RCU suffix that was used during installation, _DISCUSSIONS, along with the user supplied prefix. For example, DEV_DISCUSSIONS.

    • FILE contains the data to be imported.

25.1.3.9 Exporting Oracle WebCenter Wiki Server

To export Oracle WebCenter Wiki Server, use the Data Pump export utility. For example, go to ORACLE_HOME/bin of your database and run the command described in Example 25-9.

Note:

The Oracle Data Pump utility does not support LONG columns types that exist in the WIKI schema. Therefore Oracle recommends using Oracle Database Utilities. See also, the Oracle Database Utilities guide.

Example 25-9 Data Pump Export Utility

DB_ORACLE_HOME/bin/expdp \"sys/password@serviceid as sysdba\" OWNER=srcrcuprefix_WIKI FILE=/tmp/wiki.dmp STATISTICS=none

where:

  • DB_ORACLE_HOME is the directory in which the database for Oracle WebCenter Wiki Server schema is installed.

  • password is the password for the system database user.

  • serviceid is the service ID of the database connection.

  • OWNER is the schema to be exported. This is the RCU suffix that was used during installation, _WIKI, along with the user supplied prefix. For example, DEV_WIKI.

  • FILE contains the exported data.

25.1.3.10 Importing Oracle WebCenter Wiki Server

To import Oracle WebCenter Wiki Server, use the Oracle Data Pump import utility.

Note:

The Oracle Data Pump utility does not support LONG columns types that exist in the WIKI schema. Therefore, Oracle recommends using Oracle Database Utilities. See also, the Oracle Database Utilities guide.

  1. Shut down the target Oracle WebCenter Wiki Server.

  2. Go to DB_ORACLE_HOME/bin of the database where Oracle WebCenter Wiki Server schema is installed, and connect to the database using sqlplus as sysdba:

    DB_ORACLE_HOME/bin/sqlplus "sys/password@serviceid as sysdba"

  3. Drop the target user:

    drop user tgtrcuprefix_WIKI cascade;

  4. Create the target user:

    create user tgtrcuprefix_WIKI identified by password default tablespace tgtrcuprefix_WIKI temporary tablespace name_TEMP;

  5. Grant connect and resource to the user:

    grant connect,resource to tgtrcuprefix_WIKI;

  6. Exit sqlplus.

  7. Run the import tool as described in Example 25-10.

    Example 25-10 Database Import Utility

    DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\" FROMUSER=srcrcuprefix_WIKI TOUSER=tgtrcuprefix_WIKI FILE=/tmp/wiki.dmp STATISTICS=none

    where:

    • DB_ORACLE_HOME is the directory in which the database for Oracle WebCenter Wiki Server schema is installed.

    • password is the password for the system database user.

    • serviceid is the service ID of the database connection.

    • FROMUSER is the exported schema.

    • TOUSER is the imported schema. This is the RCU suffix that was used during installation, _WIKI, along with the user supplied prefix. For example, DEV_WIKI.

    • FILE contains the data to be imported.

25.1.3.11 Exporting Oracle Content Server

First use Oracle Data Pump to export the Oracle Content Server schema, and then export the native (vault) and web-viewable (weblayout) files.

  1. Export Oracle Content Server using the Oracle Data Pump export utility.

    For example, go to ORACLE_HOME/bin of your database and run the command described in Example 25-11.

    Note:

    The Oracle Data Pump utility does not support LONG columns types that exist in the OCSERVER schema. Therefore, Oracle recommends using Oracle Database Utilities. See also, the Oracle Database Utilities guide.

    Example 25-11 Data Pump Utility (Export)

    DB_ORACLE_HOME/bin/expdp \"sys/password@serviceid as sysdba\" OWNER=srcrcuprefix_OCSERVER FILE=/tmp/ucm.dmp STATISTICS=none

    where:

    • DB_ORACLE_HOME is the directory in which the database for Oracle Content Server schema is installed.

    • password is the password for system database user.

    • serviceid is the service ID of the database connection.

    • OWNER is the schema to be exported. This is the RCU suffix that was used during installation, _OCSERVER, along with the user supplied prefix. For example, DEV_OCSERVER.

    • FILE contains the exported data.

  2. Export the native (vault) and web-viewable (weblayout) files:

    • Vault files - Tar up the <WC_ORACLE_HOME>/ucm/vault folder on the source system. For example:

      tar cvf ucm_vault.tar WC_ORACLE_HOME/ucm/vault

    • Weblayout files - Tar up the <WC_ORACLE_HOME>/ucm/weblayout folder on the source system. For example:

      tar cvf ucm_weblayout.tar WC_ORACLE_HOME/ucm/weblayout

  3. Import the source vault and weblayout folder archives on the target system as follows:

    • Vault files - Restore the vault folder. For example:

      cd WC_ORACLE_HOME/ucm;
tar xvf ucm_vault.tar

    • Weblayout files - Restore the weblayout folder. For example:

      cd WC_ORACLE_HOME/ucm;
tar xvf ucm_weblayout.tar

25.1.3.12 Importing Oracle Content Server

First use Oracle Data Pump to import the source Oracle Content Server schema, and then import the source vault and weblayout folder archives.

  1. Import Oracle Content Server using the Oracle Data Pump import utility.

    For example, go to ORACLE_HOME/bin of your database and run the command described in Example 25-12.

    Note:

    The Oracle Data Pump utility does not support LONG columns types that exist in the OCSERVER schema. Therefore, Oracle recommends using Oracle Database Utilities. See also, the Oracle Database Utilities guide.

    Example 25-12 Data Pump Utility (Import)

    DB_ORACLE_HOME/bin/impdp  \"sys/password@serviceid as sysdba\" FROMUSER=srcrcuprefix_OCSERVER TOUSER=tgtrcuprefix_OCSERVER FILE=/tmp/UCM.dmp STATISTICS=none TRANSFORM=oid:n

    where:

    • DB_ORACLE_HOME is the directory in which the database for Oracle Content Server schema is installed.

    • password is the password for system database user.

    • serviceid is the service ID of the database connection.

    • FROMUSER is the exported schema.

    • TOUSER is the imported schema. This is the RCU suffix that was used during installation, _OCSERVER, along with the user supplied prefix. For example, DEV_OCSERVER.

    • FILE contains the data to be imported.

  2. Import the source vault and weblayout folder archives on the target system as follows:

    • Vault files - Restore the vault folder. For example:

      cd WC_ORACLE_HOME/ucm;
tar xvf ucm_vault.tar

    • Weblayout files - Restore the weblayout folder. For example:

      cd WC_ORACLE_HOME/ucm;
tar xvf ucm_weblayout.tar

After importing the Oracle Content Server, log in to WebCenter Spaces and open any imported group space. Verify that the Documents service is enabled in that group space and that imported group space folders are available as expected.

25.1.3.13 Exporting Oracle WebLogic Communications Server

For information on exporting Oracle WebLogic Communications Server, see Oracle WebLogic Communication Services Administrator's Guide.

25.1.3.14 Importing Oracle WebLogic Communications Server

For information on importing Oracle WebLogic Communications Server, see Oracle WebLogic Communication Services Administrator's Guide.

25.1.3.15 Exporting Portlet Producers

This step is only require to migrate entire producer metadata and not just the producer metadata associated with your WebCenter Spaces application. For information on how to export entire producer metadata, see the appendix "Portlet Preference Store Migration Utilities" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

25.1.3.16 Importing Portlet Producers

This step is only required to migrate entire producer metadata and not just the producer metadata associated with your WebCenter Spaces application. For information on how to import entire producer metadata, see the appendix "Portlet Preference Store Migration Utilities" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

25.1.4 Exporting an Entire WebCenter Spaces Application

This section describes how to export an entire WebCenter Spaces application using Oracle Enterprise Manager Fusion Middleware Control and WLST commands.

A WebCenter Spaces application is exported into a single export archive (.ear file). The EAR file contains a metadata archive (.mar file) and a single XML file containing the security policy information. You can save export archives to your local file system or to a remote server file system. For more information about what is exported, read Section 25.1.1, "Understanding WebCenter Spaces Export and Import".

WebCenter Spaces is temporarily unavailable during import and export operations to prevent data conflicts. Any user who tries to login or access WebCenter Spaces pages will see an "application unavailable" page.

The export process does not include data associated with external services, that is, Mail, Discussions, Announcements, Worklists, Wiki, Blogs, Personal Events, Instant Messaging and Presence (IMP), and Documents. To learn how to move data associated with these services, see Section 25.1.3, "Migrating Back-end Components for an Entire WebCenter Spaces Application".

If a shared identity store is not used and the users in both the export and import environment must be identical, then these users must also be migrated. Refer to Section 25.1.3, "Migrating Back-end Components for an Entire WebCenter Spaces Application".

Note:

No icons, skins, images, out-of-the-box t emplates, or personalizations are exported. For more information on personalizations, see the section "Personalizing Your Page View" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

This section includes the following:

25.1.4.1 Exporting WebCenter Spaces Using Oracle Enterprise Manager Fusion Middleware Control

Fusion Middleware administrators can export an entire WebCenter application using Fusion Middleware Control.

To export WebCenter Spaces:

  1. In Fusion Middleware Control, navigate to the home page for WebCenter Spaces.

    See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".

  2. From the WebCenter menu, select Application Export, as shown in Figure 25-2.

    Figure 25-2 WebCenter Menu - Application Export Option

    WebCenter menu - Application Export option
    Description of "Figure 25-2 WebCenter Menu - Application Export Option"

  3. Change the File Name for the export archive or accept the default name.

    To ensure uniqueness, the default .ear filename contains a timestamp: webcenter_wholeapp_ts_timestamp.ear, as shown in Figure 25-3.

    Figure 25-3 Naming the Export Archive

    Select the Archive to be Exported
    Description of "Figure 25-3 Naming the Export Archive"

  4. Set export options as required. For details, see Table 25-1.

    Table 25-1 WebCenter Spaces Application Export Options

    Field Description

    Include ServicesData

    Select to export data stored in the WebCenter repository for the following services: Activity Streams, Events, Feedback, Lists, Links, Message Boards, Connections, and Profiles. Note data stored in the MDS repository is exported too.

    Always re-export list data if source and target list definitions do not match. Mis-match only occurs when a list definition exists on the target and it is subsequently changed in the source.

    If the application selected for export contain a large amount of data, consider using the database export utilities to export (and import) the WebCenter schema data instead. For example:

    DB_ORACLE_HOME/bin/expdp \"sys/password@serviceid as sysdba\" OWNER=srcrcuprefix_WEBCENTER FILE=/tmp/WCS.dmp STATISTICS=none

    DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\" FROMUSER=srcrcuprefix_WEBCENTER TOUSER=tgtrcuprefix_WEBCENTER FILE=/tmp/WCS.dmp STATISTICS=none TRANSFORM=oid:n

    For details, refer to the Oracle Database Utilities guide.

    Deselect this option if you do not want to export any data associated with lists, events, tags, links, connections, profiles, message boards, activity streams, and feedback. For example, when moving an application from a test environment to a stage or production environment the test data may no longer be required.

    Note: The export process does not export data associated with other, external services such as Mail, Discussions, Announcements, Worklists, Instant Messaging and Presence (IMP), Personal Events, and Documents. To learn how to move data associated with these services, see documentation for that product. See also, Section 25.1.3, "Migrating Back-end Components for an Entire WebCenter Spaces Application".

    Include Customizations

    Select to export application customizations. For information about which customizations are optional on export, see Table 25-3 and Table 25-4.

    If you deselect this option, WebCenter Spaces is exported without these application customizations.

    Portlet and page customizations are always exported. See also Figure 25-1, "Information Exported with WebCenter Spaces".

    Include Security Policy

    Select to generate an XML file (policy-store.xml) listing:

    • WebCenter Spaces application roles (and permissions assigned to each role).

    • WebCenter user role assignments.

    • Group space members (and their role assignments).

    Deselect this option if you do not want to export user details, that is, users and their current role assignments. When you import an application without any user data, existing permissions (if any) are removed and the WebCenter Spaces administrator who is importing the application becomes the default moderator for any group spaces that are imported. This option is useful when exporting an application between a stage and production environment for the first time and where users added during the testing phase are no longer required.

    Tip: Always select this option when backing up WebCenter Spaces so that you can restore the application's security policy. If you deselect this option, no security policy will exist after the import/restore operation.

  5. Click Export.

  6. In the Download dialog, as shown in Figure 25-3, click Export to confirm that you want to go ahead.

    Figure 25-4 Downloading an Export Archive

    Download
    Description of "Figure 25-4 Downloading an Export Archive"

    Progress information is displayed during the export process. The application being exported cannot be accessed during export operations.

  7. When the export process is complete, specify a location for the export archive (.ear).

    Figure 25-5 Saving an Export Archive

    Download
    Description of "Figure 25-5 Saving an Export Archive"

    Select one of:

    • Download - Saves the export EAR file to your local file system.

      Your Browser will download and save the archive locally. The actual download location depends on your Browser set up.

    • Save to Server - Saves the export EAR file to a server location.

      When the Archive Location dialog box displays (Figure 25-6), enter a suitable path for Server Location, for example, /tmp, and then click Save. The name of the EAR is not required here.

      Ensure that the server directory you specify has write permissions.

      Figure 25-6 Saving Export Archives to a Server Location

      Download
      Description of "Figure 25-6 Saving Export Archives to a Server Location"

  8. Click Close to dismiss the Export window.

The export archive (.EAR) is saved to the specified location.

Check the diagnostic log file, WLS_Spaces-diagnostics.log, for any warnings or errors reported during the export process. To view the log file, choose the menu option WebCenter > Logs > View Log Messages. For details, see Section 24.3, "Viewing and Configuring Log Information". See also Section 25.4, "Troubleshooting Import and Export Issues for WebCenter Spaces".

25.1.4.2 Exporting WebCenter Spaces Using WLST

Use the WLST command exportWebCenterApplication to export WebCenter Spaces. For command syntax and examples, see "exportWebCenterApplication" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

WebCenter Spaces is temporarily unavailable during export operations to prevent data conflicts. Any user who tries to login or access WebCenter Spaces pages will see an "application unavailable" page.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

Note:

No icons, skins, images, out-of-the-box templates, or personalizations are exported. For more information on personalizations, see the section "Personalizing Your Page View" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

25.1.5 Importing an Entire WebCenter Spaces Application

This section describes how to import an entire WebCenter Spaces application using Fusion Middleware Control and WLST commands.

Before importing WebCenter Spaces:

WebCenter Spaces is temporarily unavailable during import and export operations to prevent data conflicts. Any user who tries to login or access WebCenter Spaces pages will see an "application unavailable" page.

This section includes the following:

25.1.5.1 Importing WebCenter Spaces Using Oracle Enterprise Manager Fusion Middleware Control

Fusion Middleware administrators can import an entire WebCenter application using Fusion Middleware Control.

To import a WebCenter Spaces application using Fusion Middleware Control:

  1. In Fusion Middleware Control, navigate to the home page for WebCenter Spaces.

    See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".

  2. From the WebCenter menu, select Application Import.

  3. In the WebCenter Spaces Application Import page, as shown in Figure 25-7, specify the location of your WebCenter Spaces application archive (.ear). Select one of the following:

    • Archive Located on Local File System - Enter the File System Location. Alternatively, click Browse to locate the directory on the local file system where the .ear file is stored.

    • Archive Located on Server File System - Enter the Server Location. Any shared location accessible from this WebCenter Spaces application.

    The .ear you select must contain an entire WebCenter Spaces application export—you cannot import individual group spaces from here. Refer to Chapter 32, "Exporting and Importing Group Spaces" for more infomration.

    Figure 25-7 WebCenter Spaces Application Import Page

    WebCenter Spaces Application Import page
    Description of "Figure 25-7 WebCenter Spaces Application Import Page"

  4. Click Import.

  5. In the WebCenter Spaces Application Import dialog, as shown in Figure 25-8, click Import.

    Figure 25-8 WebCenter Spaces Application Import dialog

    WebCenter Spaces Application Import dialog
    Description of "Figure 25-8 WebCenter Spaces Application Import dialog"

    Once the import is complete, a success message displays.

  6. Restart the managed server on which the newly imported WebCenter Spaces application is deployed.

    In a cluster environment, restart each managed server in the cluster. See also, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments".

  7. Initiate the Oracle Secure Enterprise Search crawler to index newly imported data.

    See also, Oracle Secure Enterprise Search Administrator's Guide.

25.1.5.2 Importing WebCenter Spaces Using WLST

Use the WLST command importWebCenterApplication to import a WebCenter Spaces. For command syntax and examples, see "importWebCenterApplication" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

Note:

After import:

25.1.6 Prerequisites for Group Space Export and Import

To export one or more group spaces, the WebCenter Spaces application which contains the group spaces must be up and running, and all the group spaces you want to export must be offline to prevent data conflicts. See, Section 31.3.1, "Taking Any Group Space Offline".

Group space data associated with some back-end components, specifically Oracle WebCenter Discussions Server and Oracle WebCenter Wiki Server, must be migrated after you export or import group spaces. See next section, Section 25.1.7, "Migrating Back-end Components for Individual Group Spaces".

Note:

The simultaneous export or import of large numbers of group spaces is not recommended as, depending on server configuration, it may affect system performance. If a serious deterioration in performance is observed, break the export or import down into several smaller groups.

25.1.7 Migrating Back-end Components for Individual Group Spaces

When migrating one or more group spaces, you must also migrate the back-end components used by the group space. This section tells you how.

This section includes the following sub sections:

You must import the group spaces on to the target before importing these back-end components.

25.1.7.1 Exporting Discussions for a Group Space

Use the Oracle WebCenter Discussions Server Admin Console to export discussions associated with a particular group space.

Group space discussions are exported to an .xml file, and saved to a .zip file in the DOMAIN_HOME/config/fmwconfig/servers/<target_server_name>/owc_discussions_11.1.1.2.0/data/ directory.

Where DOMAIN_HOME is the path to the Oracle WebLogic Server domain. For example, MW_HOME/user_projects/domains/my_domain/config/fmwconfig/servers/WLS_Services/owc_discussions_11.1.1.2.0/data/.

Before importing group space discussions on the target system, the target group space must exist. See Section 25.1.9.1, "Importing Group Spaces Using WebCenter Spaces".

To export group space discussions:

  1. Login to the Oracle WebCenter Discussions Server Admin Console.

    You can login directly if you know the console's URL. For example: http://example.com:8890/owc_discussions/admin

    Alternatively, login through WebCenter Spaces as follows:

    1. Login to WebCenter Spaces with administrative privileges.

      See Section 26.1, "Logging into WebCenter Spaces as an Administrator."

    2. Click the Administration link at the top of the application.

    3. Click the Group Spaces tab.

    4. From the Actions menu, choose Edit Group Space, for the group space you want to export.

    5. Click the Services tab, then Discussions.

    6. Note down the Forum Name/ID or Category Name/ID associated with this group space.

      Oracle WebCenter Discussions Server generates discussion category and forum IDs sequentially. If this ID exists on the target system, the imported forum (or category) will be assigned a new, unique ID, and therefore you must reconfigure the imported group space, to point to the new ID. For details, see Section 25.1.9.1, "Importing Group Spaces Using WebCenter Spaces" - Step 11.

    7. Click Forum Administration, and login to the Admin Console.

  2. In the Admin Console, select the System menu and choose XML Export & Import in the sidebar.

  3. Select Data Export.

  4. Set the following options (Figure 25-9):

    1. Export Options - Select Custom Options, and select all the check boxes.

    2. Export Content - Select Export Specific Content, and select the name of the forum or category required.

      Note: Group spaces that support multiple forums will use a category to store discussions. Other group spaces use a single forum.

    3. Export location, Export filename, Export file encoding - Keep the default values.

    Figure 25-9 Exporting Group Space Discussions

    Exporting Group Space Discussions

  5. Click Start Export.

  6. Once complete, copy the .zip file (that contains the export .xml file) from the MW_HOME/user_projects/domains/my_domain/config/fmwconfig/servers/<server_name>/owc_discussions_11.1.1.2.0/data directory to same location on the target discussions server.

    For example, MW_HOME/user_projects/domains/my_domain/config/fmwconfig/servers/WLS_Services/owc_discussions_11.1.1.2.0/data.

Before importing group space discussions on the target system, the group space you are migrating must exist on the target. See Section 25.1.9.1, "Importing Group Spaces Using WebCenter Spaces".

25.1.7.2 Importing Discussions for a Group Space

Use the Oracle WebCenter Discussions Server Admin Console to import group space discussions exported from another WebCenter Spaces application.

Ensure that the associated group space exists on the target before you import the group space discussion data. See Section 25.1.8.1, "Exporting Group Spaces Using WebCenter Spaces".

Note:

Oracle WebCenter Discussions Server generates discussion category and forum IDs sequentially. Therefore, when importing discussion data between two targets (or source to target), there is a chance that the same IDs will exist on both systems. When ID clashes occur, the imported forum (or category) is assigned a new, unique ID and therefore you must reconfigure the group space to point to the new ID. See Step 11 below for details.

To import group space discussions:

  1. Login to the Oracle WebCenter Discussions Server Admin Console.

    You can login directly if you know the console's URL. For example: http://example.com:8890/owc_discussions/admin

    Alternatively, login through WebCenter Spaces as follows:

    1. Login to WebCenter Spaces with administrative privileges.

      See Section 26.1, "Logging into WebCenter Spaces as an Administrator."

    2. Click the Administration link at the top of the application.

    3. Click the Group Spaces tab.

    4. From the Actions menu, choose Edit Group Space, for the group space you want to export.

    5. Click the Service tab, then Discussions.

    6. Click Forum Administration, and login to the Admin Console.

  2. In the Admin Console, select the System menu and then choose XML Export & Import in the sidebar.

  3. Select Data Import.

  4. Choose the appropriate group space export file from the list available (Figure 25-10).

    If the file you want is not listed, copy the export .zip file from the source directory DOMAIN_HOME/config/fmwconfig/servers/<target_server_name>/owc_discussions_11.1.1.2.0/data/ to same location on this target. See also, Section 25.1.7.1, "Exporting Discussions for a Group Space".

    Where DOMAIN_HOME is the path to the Oracle WebLogic Server domain. For example, MW_HOME/user_projects/domains/my_domain/config/fmwconfig/servers/WLS_Services/owc_discussions_11.1.1.2.0/data/.

    Figure 25-10 Importing Group Space Discussions

    Importing Group Space Discussions

  5. Click Start Import.

    On import, the group space discussions data is copied to the discussions server. In the next step you will reassociate the group space you migrated earlier with this newly imported data.

  6. Select the Content menu, and then choose Content Summary in the sidebar.

    All the categories and forums in the system are listed here.

  7. Select WebCenter, and then click the Move button for the newly imported forum or category.

  8. Select the root category for the target WebCenter Spaces application, and click Move Categories.

    The Category Summary page shows the new location.

  9. Click Permissions in the sidebar.

  10. Deselect all the permissions for the User Types: Anyone and Registered Users, and click Save Changes (Figure 25-11).

    Figure 25-11 Editing Forum Permissions

    Editing Forum Permissions

  11. In WebCenter Space, navigate to the group space's Discussions Forum Settings tab, to reassociate the group space with the discussion data that you just imported:

    1. Login to WebCenter Spaces with administrative privileges.

      See Section 26.1, "Logging into WebCenter Spaces as an Administrator."

    2. Click the Administration link at the top of the application.

    3. Click the Group Spaces tab.

    4. From the Actions menu, choose Edit Group Space, for the group space you want to export.

    5. Click the Services tab, then Discussions.

    6. Click the Search icon besides Category ID or Forum ID, and choose the imported category (or forum) from the list.

    7. Click Apply.

25.1.7.3 Exporting Wikis and Blogs for a Group Space

Use Oracle Data Pump utilities and the group space export script (owc_wiki_export.sql) to export wikis and blogs associated with a particular group space.

See Also:

For more information, see "Oracle Data Pump" in Oracle Database Utilities.

During the export process, wikis and blogs stored on Oracle WebCenter Wiki schema are exported to the data pump directory (the WC_PUMP_DIR directory in the example below.)

Before you start, you must copy the group space export script provided with Oracle WebCenter (WC_ORACLE_HOME/wikiserver/owc_wiki/WEB-INF/classes/owc_wiki_export.sql) to the computer where you run SQL. If you ran the script previously, be sure to remove the dump file WCWIKI_EXPDP.dmp from the WC_PUMP_DIR directory before running the script again.

To export group space wikis and blogs:

  1. Copy the group space export script from /WC_ORACLE_HOME/wikiserver/owc_wiki/WEB-INF/classes/owc_wiki_export.sql to the computer where you run SQL, for example, /myscripts/.

  2. Go to ORACLE_HOME/bin of your database where the Oracle WebCenter Wiki schema is installed, and connect to the database using sqlplus as the schema owner:

    DB_ORACLE_HOME/bin/sqlplus "<srcrcuprefix>_WIKI/password@dbhost"

  3. Create the data pump directory (data_pump_dir):

    SQL> create or replace directory WC_PUMP_DIR as '<full_path_to_existing_directory_on_the_file_system>';

    For example:

    SQL> create or replace directory WC_PUMP_DIR as '/tmp/wikiData/';

  4. Grant the Oracle WebCenter Wiki schema (srcrcuprefix_WIKI) read/write access to the data pump directory.

    For example:

    SQL> grant read, write on directory WC_PUMP_DIR to srcrcuprefix_WIKI;

  5. Run owc_wiki_export.sql:

    For example, if you copied the script to a directory called /myscripts/:

    SQL> connect srcrcuprefix_WIKI/password@//dbhost:dbport/service

    SQL> @/myscripts/owc_wiki_export.sql

  6. When prompted, enter the wiki domain associated with the group space.

WCWIKI_EXPDP.dmp is created in the WC_PUMP_DIR. For example, /tmp/wikiData/.

25.1.7.4 Importing Wikis and Blogs for a Group Space

Use Oracle Data Pump utilities and the group space import script (owc_wiki_import.sql) to import group space wikis and blogs, exported from another WebCenter Spaces application.

See Also:

For more information, see "Oracle Data Pump" in Oracle Database Utilities.

Before you start, you must copy the group space import script provided with Oracle WebCenter (WC_ORACLE_HOME/wikiserver/owc_wiki/WEB-INF/classes/owc_wiki_import.sql) to the computer where you run SQL. If the source and target databases are different, you must edit this script, as described below.

The import script will import the data based on the domain name, so make sure the same domain name does not exist in the target schema before running the script. Also ensure that the associated group space exists on the target before you import the group space wikis and blogs. See Section 25.1.8.1, "Exporting Group Spaces Using WebCenter Spaces".

To import group space wikis and blogs:

  1. Copy the group space import script from WC_ORACLE_HOME/wikiserver/owc_wiki/WEB-INF/classes/owc_wiki_import.sql to the computer where you run SQL, for example, /myscripts/.

  2. Copy the exported file, for example WCWIKI_EXPDP.dmp, to an appropriate directory on the target system.

    For example:

    SQL> cp /testserver/tmp/wikiData/WCWIKI_EXPDP.dmp /productionserver/tmp/wikiDataTarget/WCWIKI_EXPDP.dmp

  3. Go to ORACLE_HOME/bin of your database where Oracle WebCenter Wiki schema is installed, and connect to the database using sqlplus as the schema owner:

    DB_ORACLE_HOME/bin/sqlplus "<tgtrcuprefix>_WIKI/password@dbhost"

  4. Grant the Oracle WebCenter Wiki schema (tgtrcuprefix_WIKI) read/write access to the data pump directory.

    For example:

    SQL> grant read, write on directory WC_PUMP_DIR to tgtrcuprefix_WIKI;

  5. Create the data_pump_dir:

    SQL> create or replace directory WC_PUMP_DIR as '<full_path_to_existing_directory_on_the_file_system>';

    For example:

    SQL> create or replace directory WC_PUMP_DIR as '/tmp/wikiDataTarget/';

  6. If the source and target databases are different, edit the import script /myscripts/owc_wiki_import.sql as follows:

    DBMS_DATAPUMP.METADATA_REMAP(dp_handle,'REMAP_SCHEMA','SOURCE_WIKI_SCHEMA','TARGET_WIKI_SCHEMA');

    1. SOURCE_WIKI_SCHEMA - replace with the source schema where you ran owc_wiki_export.sql

    2. TARGET_WIKI_SCHEMA - replace with the target schema where you will run owc_wiki_import.sql

  7. Run owc_wiki_import.sql:

    For example, if you copied the script to a directory called /myscripts/:

    SQL> connect tgtrcuprefix_WIKI/password@//dbhost:dbport/service

    SQL> @/myscripts/owc_wiki_import.sql

25.1.7.5 Exporting Documents for a Group Space

After importing a group space you can use WebDAV to upload group space documents stored in Oracle Content Server to the new target; there is no need to export the content first.

25.1.7.6 Importing Documents for a Group Space

Before migrating group space documents to a new target you must enable the Documents service in the imported group space. Once the service is enabled, you can use WebDAV to upload group space documents onto the target system.

When dragging and dropping content to the target system, do not drag the group space folder to the target; you must only drag and drop content that is stored under the group space folder.

WebDAV is enabled on Oracle Content Server out-of-the-box. If you do not know the WebDAV URL for the Oracle Content Server that is used to store group space and personal space documents, contact your Fusion Middleware Administrator. If the base URL for that Oracle Content Server is http://<host>:<port>/<relative_web_root>, the WebDAV root URL will be http://<host>:<port>/<relative_web_root>/idcplg/webdav.

Note:

Depending on the WebDAV client you use, all properties may not be copied over (for example, document descriptions, checkin and checkout status, and versions may not be carried across).

To set up the target group space and import documents from another group space:

  1. In WebCenter Spaces, enable the Documents service in the imported group space:

    1. Login to the WebCenter Spaces application that contains the imported group space.

      See Section 26.1, "Logging into WebCenter Spaces as an Administrator."

    2. Click the Administration link at the top of the application.

    3. Click the Group Spaces tab.

    4. From the Actions menu, choose Edit Group Space, for the imported group space.

    5. Click the Services tab.

    6. Select the check box next to Documents to enable this service, and then click Apply.

    7. Click OK to dismiss the warning about permission configuration requirements.

    8. Click the Roles tab, and assign appropriate Documents permissions to each group space role.

    9. Click Apply to save.

  2. Using WebDAV (for Oracle Content Server), drag and drop content from the folder belonging to the source group space to the empty folder assigned to the target group space.

25.1.8 Exporting Group Spaces

Administrators can export one or more group spaces using WebCenter Spaces and WLST commands.

Group space information is exported into a single export archive (.ear file). The EAR file contains a metadata archive (.mar file) and a single XML file containing the security policy information. You can save export group space archives to your local file system or to a remote server file system.

For more information about what is exported, see Section 25.1.1, "Understanding WebCenter Spaces Export and Import".

The export process does not include data associated with external group space services, such as, Discussions, Announcements, Wiki, Blogs, and Documents. To learn how to move data associated with these services, see Section 25.1.7, "Migrating Back-end Components for Individual Group Spaces".

Groups spaces are locked during an export operation to prevent simultaneous imports/exports of the same group space. If someone else is exporting a particular group space, all subsequent attempts to export (or import) the same group space are blocked.

Note:

No icons, skins, images, or personalizations are exported. For information on personalizations, see the section "Personalizing Your Page View" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

This section includes the following:

If you want to export an entire WebCenter Spaces application, see Section 25.1.4, "Exporting an Entire WebCenter Spaces Application".

25.1.8.1 Exporting Group Spaces Using WebCenter Spaces

WebCenter Spaces administrators can export one or more group spaces from WebCenter Spaces administration pages. For details, see Section 32.1, "Exporting Group Spaces".

25.1.8.2 Exporting Group Spaces Using WLST

Use the WLST command exportGroupSpaces to export one or more group spaces. For command syntax and examples, see "exportGroupSpaces" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

25.1.9 Importing Group Spaces

Administrators can import a group space archive (.EAR) using WebCenter Spaces and WLST commands.

On import, all group spaces included in the archive are created or re-created on the target application. Existing group spaces are deleted then replaced, and new group spaces are created.

If you intend to import group spaces with names identical to those available on the target application, ensure that those group spaces are offline in the target application. It is not possibe to overwrite a group space, on import, if it is online. For details, see "Taking a Group Space Offline" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

Groups spaces are locked during an import operation to prevent simultaneous imports/exports of the same group space. If someone else is importing a particular group space, all subsequent attempts to import (or export) the same group space are blocked.

All group spaces must have a security policy. When you import a brand new group space you must ensure that the group space's security policy is included in the export archive. Existing group spaces have a security policy in place so, in this case, it's up to you whether to overwrite the security information on import or maintain the existing security policy.

When you import a group space (with security), security policy updates do not apply immediately. Any user logged in to WebCenter Spaces must log out and log back in to adopt the new group space security policy.

If data migration is important, group space documents, discussions, and wikis and blogs can be migrated for individual group spaces. For details, see Section 25.1.7, "Migrating Back-end Components for Individual Group Spaces".

This section includes the following:

After importing one or more group spaces, consider initiating an Oracle Secure Enterprise Search crawl to index the newly imported data.

25.1.9.1 Importing Group Spaces Using WebCenter Spaces

WebCenter Spaces administrators can import a group space archive (.EAR) into another WebCenter Spaces application. For details, see Section 32.2, "Importing Group Spaces".

25.1.9.2 Importing Group Spaces Using WLST

Use the WLST command importGroupSpaces to import one or more group spaces. For command syntax and examples, see "importGroupSpaces" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

25.1.10 Migrating Back-end Components for Group Space Templates

Group space templates do not contain any data so there is no need to migrate back-end component data when exporting and importing group space templates.

You must, however, migrate the group space template's folder (on Oracle Content Server) to the target instance as described below. If you do not, the Documents service is not enabled in any group space that you create, using this template.

Importing the Back-end Folder for a Group Space Template

Use WebDAV (for Oracle Content Server), to drag and drop the folder belonging to the source group space template to the target instance.

WebDAV is enabled on Oracle Content Server out-of-the-box. If you do not know the WebDAV URL for the Oracle Content Server that WebCenter Spaces uses, contact your Fusion Middleware Administrator. If the base URL for that Oracle Content Server is http://<host>:<port>/<relative_web_root>, the WebDAV root URL will be http://<host>:<port>/<relative_web_root>/idcplg/webdav.

25.1.11 Exporting Group Space Templates

Administrators can export group space templates and import them into other WebCenter Spaces applications. Out-of-the-box templates, such as the Group Project and Community of Interest templates, cannot be exported.

While export and import utilities are primarily used to move information between WebCenter Spaces applications, the group space template export feature is also useful as a backup service, and for sharing and exchanging templates with others.

Group space template information is exported into a single export archive (.EAR file). The EAR file contains a metadata archive (.MAR file) and a single XML file containing group space security policy information.

Group space templates include pages, metadata, security information such as custom roles, and service information only; no data, such as documents, discussion threads, and list data, is stored with the template.

You can save export archives to your local file system or to a remote server file system.

This section includes the following:

See also, Section 25.1.8, "Exporting Group Spaces".

25.1.11.1 Exporting Group Space Templates Using WebCenter Spaces

WebCenter Spaces administrators can export one or more group space templates from WebCenter Spaces administration pages. For details, see Section 32.3, "Exporting Group Space Templates".

25.1.11.2 Exporting Group Space Templates Using WLST

Use the WLST command exportGroupSpaceTemplates to export one or more group space templates. For command syntax and examples, see "exportGroupSpaceTemplates" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

25.1.12 Importing Group Space Templates

Administrators can import a group space template archive (.EAR) into another WebCenter Spaces application.

On import, all group space templates included in the archive are re-created on the target application. If a group space template exists on the target, then it is deleted and replaced. If a group space template does not exist, then it is created.

Newly imported group space templates are not immediately available for general use. You must publish the imported templates to make them available to everyone. See Section 31.5.3, "Publishing and Hiding Group Space Templates".

This section includes the following:

See also, Section 25.1.9, "Importing Group Spaces".

25.1.12.1 Importing Group Space Templates Using WebCenter Spaces

WebCenter Spaces administrators can import one or more group space templates from WebCenter Spaces administration pages. For details, see Section 32.4, "Importing Group Space Templates"

25.1.12.2 Importing Group Space Templates Using WLST

Use the WLST command importGroupSpaces to import one or more group space templates. For command syntax and examples, see "importGroupSpaces" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

25.2 Exporting and Importing Custom WebCenter Applications for Data Migration

This section describes how to export and import metadata and customizations of a custom WebCenter application developed with Oracle WebCenter Framework.

It includes the following sections:

25.2.1 Understanding Custom WebCenter Application Export and Import

Several migration tools are available to export and import custom WebCenter applications, their connections and customizations (that is, customizations applied to an application, pages, and portlets) between stage and production environments (Figure 25-12).

Figure 25-12 WebCenter Application Export and Import

WebCenter Import and Export

Table 25-2 lists available migration tools and their capabilities. All customizations listed in Table 25-2 are migrated with custom WebCenter applications.

Table 25-2 Custom WebCenter Application Migration Tools

Migration Tools Capabilities

Portlet Client WLST Commands

Enable export and import of portlet client metadata, and producer customizations and personalizations.

MDS WLST Commands

Enables export and import of:

  • WebCenter application metadata including customizations made to pages and WebCenter services

  • Data stored in the connections.xml and adf-config.xml documents

Migration WLST Commands

Enables export and import of security policies, including roles and mapping of users and roles.

Oracle Database Utilities

Enables export and import of WebCenter application data. For information, see the part "Oracle Data Pump" in the Oracle Database Utilities guide.

25.2.2 Prerequisites for Custom WebCenter Application Export and Import

Before exporting or importing metadata and customizations for a custom WebCenter application, ensure the following:

  • The Oracle Database in which the application metadata and schema is stored is up and running.

  • The target instance is configured with the same set of services as the source instance. Additional services can be configured in the target, if required, but minimally, service configuration in the source and target must match.

  • The jps.policystore.removal parameter is set to OFF in your application's weblogic-application.xml so that policies are migrated on import:

    <application-param>
    <param-name>jps.policystore.removal</param-name>
    <param-value>OFF</param-value>
  </application-param>

    If this option is not set, no policy information is imported. In some instances you may not want to migrate policy data, for example, when migrating from a test environment to a production environment where test data is not required. You should note, however, that pages created on the source instance at runtime will not display on the target instance because no page grants will exist on the target.

25.2.3 Exporting Portlet Client Metadata (Custom WebCenter Applications)

To export portlet client metadata and producer customizations and personalizations, for a custom WebCenter application, use the WLST command exportPortletClientMetadata. This command is run on the entire application, and therefore, it exports metadata of all the producers stored in an application. You cannot opt to export metadata for specific producers.

Note:

Both the portlet producer and individual portlets must include an <allow-export> tag that is set to true. If this tag is not set, the portlet producer (and the portlets) are excluded from the export process. For details, refer to "How to Implement Export/Import of Customizations (WSRP 2.0)" in the Oracle WebCenter Framework Developer's Guide.

For detailed syntax and examples, see "exportPortletClientMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands"

For information on how to import portlet client metadata associated with all applications, see "Portlet Preference Store Migration Utilities" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

25.2.4 Importing Portlet Client Metadata (Custom WebCenter Applications)

This section describes how to import portlet client metadata and producer customizations and personalizations, for a custom WebCenter application, using the WLST command importPortletClientMetadata.

Prerequisites:

  • The Oracle Database in which the application metadata or schema is stored and the portlet producers must be up and running.

  • Both the portlet producer and individual portlets must include an <allow-import> tag that is set to true. If the tag is not set, the portlet producer (and the portlets) are excluded from the import process. For details, refer to "How to Implement Export/Import of Customizations (WSRP 2.0)" in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

To import portlet client metadata:

  1. Start the WebLogic Scripting Tool (WLST) located at WC_ORACLE_HOME/common/bin.

    On UNIX, start WLST using wlst.sh.

    On Windows, use wlst.cmd.

    See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

  2. Run the WLST command deleteMetadata to delete the metadata under /oracle/adf/portlet.

    deleteMetadata(application='application', server='server', docs='docs')

    where:

    • application: Name of the WebCenter application (for example, sampleApp)

    • server: Name of the managed server (for example, portletConsumer).

    • docs: List of comma separated fully qualified document name(s) or document name patterns (such as * and ** patterns).

    For example:

    deleteMetadata(application='sampleApp', server='WLS_CustomApp', docs='/oracle/adf/portlet/**')

    For detailed syntax and examples, see "deleteMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

  3. Run the WLST command importPortletClientMetadata:

    importPortletClientMetadata(appName, fileName, server, applicationVersion)

    where:

    • appName: Name of the WebCenter application (for example, sampleApp).

    • fileName: Name of the exported EAR file containing the portlet client metadata (for example, export.ear).

    • server: Name of the managed server (for example, portletConsumer).

    • applicationVersion: Version number of the deployed application, if multiple versions of the application is deployed.

For detailed syntax and examples, see "importPortletClientMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. See also the chapter "Metadata Services (MDS) Custom WLST Commands" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

25.2.5 Exporting WebCenter Services Metadata and Data (Custom WebCenter Applications)

The metadata created by WebCenter services is stored in the Oracle metadata store (MDS). This section describes the transfer of the base documents and their customizations using WLST. For detailed information about MDS, see the chapter "Managing the Oracle Metadata Repository" in Oracle Fusion Middleware Administrator's Guide.

Customizations listed in Table 25-3 are also exported when WebCenter applications are migrated between stage and production environments.

  1. Start the WebLogic Scripting Tool (WLST) located at WC_ORACLE_HOME/common/bin.

    On UNIX, start WLST is called wlst.sh.

    On Windows, use wlst.cmd.

    See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

  2. Run the WLST command exportMetadata:

    exportMetadata(application, server, toLocation, docs, [restrictCustTo],
[excludeAllCust], [excludeBaseDocs], [excludeExtendedMetadata], [fromLabel],
[toLabel], [applicationVersion])

    For example:

    exportMetadata(application='sampleApp', server='WLS_CustomApp', toLocation='/tmp/myrepos', docs='/oracle/webcenter/**')

    For detailed syntax and examples, see "exportMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

    Note:

    In this example, "docs='/oracle/webcenter/**" will export the required documents for all WebCenter services storing metadata in MDS.

    The "docs='/oracle/webcenter/**" command does not export portlet customizations and personalizations or changes to configuration files such as connections.xml and adf-config.xml. To export portlet metadata, run the WLST command exportPortletClientMetadata. To export configuration file updates that are stored in MDS, run the WLST command exportMetadata with "docs='META-INF/mdssys/cust/adfshare/adfshare/**".

Where:

  • application: Application name for which the metadata is to be exported (for example, sampleApp).

  • server: Target server on which this application is deployed (for example, WLS_CustomApp).

  • toLocation: Target directory to which documents selected from the source partition are to be transferred. The toLocation parameter can be used as a temporary file system for transferring metadata from one server to another.

  • docs: List of comma separated fully qualified document name(s) and/or document name patterns (* and ** patterns).

  • restrictCustTo: List of customization layer names. This list is used to restrict the export of customization documents that match the specified customization layers. This option is ignored if the excludeAllCust option is also specified.

  • excludeAllCust: Specifies whether to export all customization documents. This option overrides the restrictCustTo option.

  • excludeBaseDocs: Specifies whether to export base documents.

  • excludeExtendedMetadata: Specifies whether to export the Extended Metadata documents.

  • fromLabel: If specified, transfers the documents from the source partition that is associated with this label.

  • toLabel: If specified, works with the fromLabel variable to transfers the delta between fromLabel to toLabel from the source partition.

  • applicationVersion: Application version in case multiple versions of the same application are deployed.

The metadata for WebCenter services, which consists of base and customization documents, are stored in the following paths:

  • Announcements: /oracle/webcenter/collab/announcement/**

  • Documents: /oracle/webcenter/doclib/** and /oracle/webcenter/doclib/view/jsf/fragments/**

  • Discussions: /oracle/webcenter/collab/forum/**

  • General Settings: /oracle/webcenter/generalsettings/**

  • Group Space Events:/oracle/webcenter/collab/calendar/community/**

  • Lists: /oracle/webcenter/list/** and /oracle/webcenter/list/view/jsf/regions/**

  • Mail: /oracle/webcenter/collab/mail/**

  • Notes: /oracle/webcenter/note/**

  • Page: /oracle/webcenter/page/** and /pageDefs/**

  • Recent Activity: /oracle/webcenter/recentactivity/**

  • RSS News Feed: oracle/webcenter/rss/**

  • Links: /oracle/webcenter/relationship/**

  • Scope: /oracle/webcenter/framework/scope/**

  • Search: /oracle/webcenter/search/**

  • Tags: /oracle/webcenter/tagging/**

  • adf-config.xml, connections.xml: /META-INF/mdssys/cust/adfshare/adfshare/**

    Configuration file updates are not stored under the /oracle/webcenter/ directory alongside WebCenter services. To export customizations associated with these files, run exportMetadata again with "docs='META-INF/mdssys/cust/adfshare/adfshare".

25.2.6 Importing WebCenter Services Metadata and Data (Custom WebCenter Applications)

To import custom WebCenter application metadata and customizations:

  1. Start the WebLogic Scripting Tool (WLST) located at WC_ORACLE_HOME/common/bin.

    On UNIX, start WLST using wlst.sh.

    On Windows, use wlst.cmd.

    See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

  2. Run the WLST command importMetadata:

    importMetadata( application, server, fromLocation, docs, [restrictCustTo],
[excludeAllCust], [excludeBaseDocs], [excludeExtendedMetadata],
[cancelOnException], [applicationVersion])

    For example:

    importMetadata(application='sampleApp', server='WLS_CustomApp', fromLocation='/tmp/myrepos', docs='/**')

    Where:

    • application: Application name for which the metadata is be imported (for example, sampleApp).

    • server: Name of the target server on which this application is deployed (for example, WLS_CustomApp).

    • fromLocation: Source directory from where documents are selected for the transfer. The fromLocation parameter can be used as a temporary file system location for transferring metadata from one server to another.

    • docs: List of comma separated fully qualified document name(s) and/or document name patterns (* and ** patterns).

    • restrictCustTo: List of customization layer names. This list is used to restrict the import of customization documents that match the specified customization layers. This option is ignored if the excludeAllCust option is also specified.

    • excludeAllCust: Specifies whether to import all customization documents. This option overrides the restrictCustTo option.

    • excludeBaseDocs: Specifies whether to import base documents.

    • excludeExtendedMetadata: Specifies whether to import the Extended Metadata documents.

    • cancelOnException: Whether to terminate the import operation when an exception is encountered. On termination, the delete is rolled back if supported by the target store.

    • applicationVersion: Application version in case multiple versions of the same application are deployed.

For detailed syntax and examples, see "importMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

25.2.7 Migrating Security for Custom WebCenter Applications

Security migration involves moving the identity store, credential store, and policy store, from one WebCenter application to another. The process is the same for all WebCenter applications so, for custom WebCenter applications, you can follow the same instructions provided for WebCenter Spaces:

25.2.8 Migrating Data (Custom WebCenter Applications)

To export the custom WebCenter application data, use the export and import database utilities. This section includes the following sub sections:

25.2.8.1 Exporting Data (Custom WebCenter Applications)

To export the custom WebCenter application data, use the Oracle Data Pump export utility. For example, go to DB_ORACLE_HOME/bin of the database and run the command described in Example 25-13.

See Also:

For more information, see "Oracle Data Pump" in the Oracle Database Utilities guide.

Example 25-13 Data Pump Utility (Export)

DB_ORACLE_HOME/bin/expdp \"sys/password@serviceid as sysdba\" OWNER=srcrcuprefix_WEBCENTER FILE=/tmp/wc.dmp STATISTICS=none

where:

  • DB_ORACLE_HOME is the directory in which the database for the Oracle WebCenter schema is installed.

  • password is the password for system database user.

  • serviceid is the service ID of the database connection.

  • OWNER is the schema to be exported. This is the RCU suffix that was used during installation along with the suffix _WEBCENTER. For example, DEV_WEBCENTER.

  • FILE contains the exported data.

25.2.8.2 Importing Data (Custom WebCenter Applications)

To import data for custom WebCenter applications, use the Oracle Data Pump import utility. For example, go to DB_ORACLE_HOME/bin of the database and run the command described in Example 25-14.

See Also:

For more information, see "Oracle Data Pump" in the Oracle Database Utilities guide.

Example 25-14 Data Pump Utility (Import)

DB_ORACLE_HOME/bin/impdp  \"sys/password@serviceid as sysdba\" FROMUSER=srcrcuprefix_WEBCENTER TOUSER=tgtrcuprefix_WEBCENTER FILE=/tmp/wc.dmp STATISTICS=none TRANSFORM=oid:n

where:

  • DB_ORACLE_HOME is the directory in which the database for the Oracle WebCenter schema is installed.

  • password is the password for system database user.

  • serviceid is the service ID of the database connection.

  • FROMUSER is the exported schema.

  • TOUSER is the imported schema. This is the RCU suffix that was used during installation, _WEBCENTER, along with the user supplied prefix. For example, DEV_WEBCENTER.

  • FILE contains the data to be imported.

25.3 Backing Up and Recovering WebCenter Applications

To recover data from disasters, such as the loss of database hardware, inadvertent removal of data from file or database, it is important to back up WebCenter applications on a frequent basis. The frequency of backup depends on how often the underlying information stored by WebCenter changes in a particular customer application, and how much time and amount of information could acceptably be lost. Incremental or partial backups may be applied where the data is critical to the business and must be restored due to a failure.

Backup and recovery of WebCenter components can be managed through database export and import utilities, and various other tools. For more information, see "Part IV Advanced Administration: Backup and Recovery" in Oracle Fusion Middleware Administrator's Guide.

25.4 Troubleshooting Import and Export Issues for WebCenter Spaces

This section contains the following subsections:

25.4.1 ResourceLimitException Issue

Problem

The ResourceLimitException error displays when you try to export all group spaces or an entire WebCenter Spaces application:

Weblogic.common.resourcepool.ResourceLimitException

Solution

Increase the maximum capacity in the JDBC connection pool. To reconfigure the connection pool, log in to the WLS Administration Console. From Services, select Data Sources, JDBC, and then the Connection Pool tab.

25.4.2 Exporting and Importing Group Spaces in Multibyte Languages

Problem

On Linux, group space export or import fails for one or more group spaces created in multibyte languages due to naming restrictions. Group space names are restricted to alphanumeric and space characters ("a" through "z", "A" through "Z", "0" through "9", and the single-byte space character, which WebCenter Spaces replaces with "_"(underscore) ). If any other characters are used in the group space name, export or import fails.

Solution

Enforce the naming restriction on the server on which Oracle WebCenter is deployed. To do this, set the environment variable LC_ALL set to utf-8.

25.4.3 Page or Group Space Not Found Messages After Import

Problem

When users first log in to WebCenter Spaces after an import operation they may see a "Page not found" or "Group space not found" message if the page or group space they last visited no longer exists. Such messages display beacuse "last accessed" page information is retained during an import operation.

Solution

No action required. Users will not see the message the next time they log in.

25.4.4 Group Space Import Archive Exceeds Maximum Upload File Size

Problem

There is a file size limitation uploading content to WebCenter Spaces. If your export archive exceeds the maximum upload size then the import operation through WebCenter Spaces administration will fail.

Solution

Import the group space archive using WLST.For details, see Section 25.1.9.2, "Importing Group Spaces Using WLST".

Alternatively, modify the content repository upload parameter in web.xml. The default maximum upload size is 2 GB. See also, "Editing web.xml" in Appendix A, "WebCenter Configuration".

25.4.5 Lists Not Imported Properly

Problem

Lists are not importing properly due to list definition differences in the source and target systems.

Solution

Consider exporting and importing list data. This ensures that list data is consistent with the list definitions being imported.

If you choose to import without data, the list data in the target system is migrated to be consistent with the imported list definitions. If a list column data type is changed, the column values are converted from the target data type to the imported data type, if possible, otherwise the value is deleted. If a list column is removed during import, the column values are deleted.

25.4.6 Exporting WebCenter Spaces Customizations

When you export WebCenter Spaces you can choose whether certain application customizations are included in the export archive or whether to exclude them, using the option "Include Customizations". Table 25-3 highlights those services and task flows that store customizations, and which are optional on migration. Table 25-4 lists all the application and group space customizations which are optional on export.

Note:

User personalizations are never migrated during export and import. For more information on customization and personalization and the difference between them, see "Customizing and Personalizing Page Content" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.

Table 25-3 WebCenter Spaces - Service Customizations

Services in WebCenter Spaces Customizations Export

Announcements Service

None

  

Announcement Tab

None

  

Announcement Task Flow

None

  

Discussions Service

    

Sidebar

None

  

Discussions Tab

None

  

Discussion Forum Manager Task Flow

None

  

Forum Task Flow

None

  

Discussion Task Flows

None

  

Documents Service

    

Documents Tab

None

  

Document Manager Task Flow

  • Document Manager display preferences, such as, Description, Size, Status, Modified by, Last Modified, Links, and so on.

  • Table column settings, such as, visible columns, column sizes, and ordering.

See also, "Undestanding the Document Manager Task Flow" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

Optional

Document List Viewer Task Flow

Table column settings, such as, visible columns, column sizes, and ordering.

In page edit mode, default fields that display document search results can be customized and additional fields can be added.

Group Space Documents

See also, "Understanding the Document List Viewer Task Flow" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

Optional

Content Presenter Task Flow

Content presenteIn page edit mode, content and display template settings.

See also, "Understanding the Content Presenter Task Flow" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

Optional

Recent Documents Task Flow

None

  

Events Service

    

Events Tab

None

  

Events Task Flow

Page edit mode:

- Task flow customizations: Display Mode, Grid Start Hour, Second Timezone. - Calendars overlay properties: Name, Order, Color and Visibility.

Optional

Instant Messaging and Presence Service

    

Buddies Task Flow

None

  

Lists Service

    

List Tab

None

  

List Viewer Task Flow

Page edit mode:

  • Banding type and interval, and column filter settings

    Banding type and interval

  • Column settings: Sort column and sort direction (ascending, descending), column sizes, and column order

See also, "Working with the Lists Service" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

Optional

List Manager Task Flow

None

  

Mail Service

    

Sidebar

None

  

Mail Task Flow

None

  

Notes Service

None

  

Pages

Page edit mode: task flow and portlet customizations using Oracle Composer, such as, Maximize, Move, Vertical Height

Always
 

Page properties: Page Name, Description, Keywords, Scheme, Scheme Background Color, Page Security, Page Parameters, Page modified date, and so on.

Always
 

Component properties: Title, Background Color, and so on.

Always

People Connection Service

    

Activity Stream Task Flow

Display options for the Activity Stream task flow.

Optional

Portlets

Customizations/edit defaults (if any) stored in the producers.

Always

Recent Activities Service

None

  

Resource Catalog

None

  

RSS News Feed Service

None

  

Search Service

None

  

Saved Search

Shared/Private option for saved searches.

Saved search customizations.

Optional

Tags Service

    

Tags

None

  

Tags Center

None

  

Tag Sidebar

None

  

Worklist Service

None

  

Table 25-4 WebCenter Spaces - Application and Group Space Customizations

WebCenter Spaces
 Customizations Export

Application Settings

  

Optional

Administration: General tab

All properties

  

Administration: General tab

Language

  

Administration: Pages tab

Settings such as, Set Page Defaults, Order, and Show Page

  

Administration: Sidebar tab

All properties

  

Administration: Services tab

Default settings for Discussions, Mail, and People Connections (Profiles, Message Boards, Feedback, Connections, Activity Streams)

  

Application Sidebar

Applications/folder display order, and personalization allowed setting

  

Group Space Settings

  

Optional

Group Spaces Settings: Pages tab

Settings such as, Set Page Defaults, Order, and Show Page

  

Group Spaces Settings: other tabs

All properties