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

16.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 ORACLE_HOME/bin directory.

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

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

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.

16.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 ORACLE_HOME/bin directory.

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

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.

16.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
      

   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 16-3):

   Example 16-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.

16.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 16.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 16-4):

   Example 16-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.

16.1.3.5 Exporting Oracle WebCenter Discussions Server

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

DB_OH/bin/exp \"sys/password@dbhost serviceid as sysdba\" OWNER=rcuprefix_DISCUSSIONS FILE=/tmp/df.dmp STATISTICS=none

16.1.3.6 Importing Oracle WebCenter Discussions Server

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

1. Shut down the target Oracle WebCenter Discussions Server.

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

   DB_OH/bin/sqlplus "sys/password@dbhost 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_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 16-6.

   Example 16-6 Database Import Utility

   DB_OH/bin/imp \"sys/password@dbhost as sysdba\" FROMUSER=srcrcuprefix_DISCUSSIONS TOUSER=tgtrcuprefix_DISCUSSIONS FILE=/tmp/df.dmp statistics=none
   

   where:

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

   • password is the password for the system database user.

   • dbhost is the host name of the database.

   • 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.

16.1.3.7 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 16-7.

DB_OH/bin/exp \"sys/password@dbhost as sysdba\" OWNER=rcuprefix_WIKI FILE=/tmp/wiki.dmp STATISTICS=none

16.1.3.8 Importing Oracle WebCenter Wiki Server

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

1. Shut down the target Oracle WebCenter Wiki Server.

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

   DB_OH/bin/sqlplus "sys/password@dbhost 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 16-8.

   Example 16-8 Database Import Utility

   DB_OH/bin/imp \"sys/password@dbhost as sysdba\" FROMUSER=srcrcuprefix_WIKI TOUSER=tgtrcuprefix_WIKI FILE=/tmp/wiki.dmp statistics=none
   

   where:

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

   • password is the password for the system database user.

   • dbhost is the host name of the database.

   • 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.

16.1.3.9 Exporting Oracle Content Server

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

DB_OH/bin/expdp \"sys/password@dbhost as sysdba\" SCHEMAS=srcrcuprefix_OCSERVER DIRECTORY=data_pump_dir DUMPFILE=UCM.dmp

16.1.3.10 Importing Oracle Content Server

To import Oracle Content Server, use the Oracle Data Pump import utility. For example, go to ORACLE_HOME/bin of your database and run the command described in Example 16-10.

DB_OH/bin/impdp  \"sys/password@dbhost as sysdba\" REMAP_SCHEMA=srcrcuprefix_OCSERVER:tgtrcuprefix_OCSERVER 
DIRECTORY=data_pump_dir DUMPFILE=UCM.dmp TABLE_EXISTS_ACTION=REPLACE

where:

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

• password is the password for system database user.

• dbhost is the host name of the database.

• REMAP_SCHEMA maps the schema exported from the stage environment to the schema in the production environment. This is the RCU suffix that was used during installation, _OCSERVER, along with the user supplied prefix. For example, DEV_OCSERVER.

• DIRECTORY specifies the directory object created for the export and import operation.

  Note:

  The data_pump_dir file must have been created in SQL using a tool like SQL*Plus. For example:

  SQL> create or replace directory DATA_PUMP_DIR as '<full_path_to_a_directory_on_the_file_system>';
  SQL> commit;
  SQL> quit
  

• DUMPFILE contains the data to be imported.

• TABLE_EXISTS_ACTION replaces the existing table with the imported table.

After the Oracle Content Server repository has been imported, log into WebCenter Spaces and ensure that the Documents service is provisioned for that Group Space. The provisioned/unprovisioned state of Documents in a group space is determined by the presence of a group space specific folder in the Content Server. This occurs when the you provision the group space for a new Content Server instance, or when the already provisioned source Content Server is exported and imported to the target Content Server.

16.1.3.11 Exporting Oracle WebLogic Communications Server

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

16.1.3.12 Importing Oracle WebLogic Communications Server

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

16.1.3.13 Exporting Portlet Producers

This step is only required if you want 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.

16.1.3.14 Importing Portlet Producers

This step is only required if you want 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.

16.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 16-2.

   Figure 16-2 WebCenter Menu - Application Export Option

   
   Description of "Figure 16-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 16-3.

   Figure 16-3 Select the Archive to be Exported

   
   Description of "Figure 16-3 Select the Archive to be Exported"
   
   

4. Set export options as required. For details, see Table 16-3.

   Table 16-3 WebCenter Spaces Application Export Options

   Field	Description
   Include Data	Select to export data stored in the WebCenter repository for Lists, Events, Links, and Tags. For example, list items, group space events, any links/associations between objects in the application, and tag data. 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 the WebCenter schema data instead. For example: DB_OH/bin/expdp \"sys/password@dbhost as sysdba\" schemas=RCUPREFIX_WEBCENTER directory=data_pump_dir dumpfile=WC.dmp For details, refer to Oracle Database Utilities. Deselect this option if you do not want to export any data associated with lists, events, tags, and links. 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), and Documents. To learn how to move data associated with these services, see documentation for that product. See also, Section 16.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 16-1 and Table 16-2. If you deselect this option, WebCenter Spaces is exported without these application customizations. Portlet and page customizations are always exported. See also Figure 16-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 user data, the WebCenter Spaces administrator that is importing the application becomes the default moderator for any group spaces that are imported. This option is useful when exporting applications between a stage and production environments where users used during testing are no longer required.

   
   

5. Click Export.

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

   Figure 16-4 Download

   
   Description of "Figure 16-4 Download"
   
   

   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). 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. For example, /tmp. Ensure that the server directory you specify has write permissions.

     After clicking Save to Server, enter the Server Location and then click Save.

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 warnings or errors during the export process. For details, see Section 15.3, "Viewing and Configuring Log Information". See also Appendix B, "Troubleshooting".

16.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.

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

16.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 16-5, 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.

   Figure 16-5 WebCenter Spaces Application Import Page

   
   Description of "Figure 16-5 WebCenter Spaces Application Import Page"
   
   

4. Click Import.

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

   Figure 16-6 WebCenter Spaces Application Import dialog

   
   Description of "Figure 16-6 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".

16.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.

If you intend to import group spaces with names identical to those available on the target application, ensure that group spaces in the target application are offline. If existing group spaces with identical names are online, then the import fails.

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

16.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/fmwconfig/server/<target_server_name>/owc_discussions_11.1.1.1.0/data directory.

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

Before importing group space discussions on the target system, the target group space must exist. See Section 16.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 17.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 16.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 16-7):

   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 16-7 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/fmwconfig/server/<server_name>/owc_discussions_11.1.1.1.0/data directory to same location on the target discussions server.

   For example, MW_HOME/user_projects/domains/my_domain/fmwconfig/server/WLS_Services/owc_discussions_11.1.1.1.0/data.

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

16.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 16.1.8.1, "Exporting Group Spaces Using WebCenter Spaces".

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 17.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 16-8).

   If the file you want is not listed, copy the export .zip file from the source directory DOMAIN_HOME/fmwconfig/server/<target_server_name>/owc_discussions_11.1.1.1.0/data to same location on this target. See also, Section 16.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/fmwconfig/server/WLS_Services/owc_discussions_11.1.1.1.0/data.

   Figure 16-8 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 16-9).

    Figure 16-9 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 17.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.

16.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.

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 are running SQL. If you've already run the script, 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 are running 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_OH/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_a_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/.

16.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.

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 are running 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 16.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 are running 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_OH/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_a_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> @/myscripts/owc_wiki_import.sql

16.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.

16.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.

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 17.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.

16.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 23.1, "Exporting Group Spaces".

16.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".

16.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 23.2, "Importing Group Spaces".

16.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".

16.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 23.3, "Exporting Group Space Templates".

16.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".

16.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 23.4, "Importing Group Space Templates"

16.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".

16.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 ORACLE_HOME/bin of your database and run the command described in Example 16-11.

DB_OH/bin/expdp \"sys/password@dbhost as sysdba\" SCHEMAS=rcuprefix_WEBCENTER DIRECTORY=data_pump_dir DUMPFILE=wc.dmp

16.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 ORACLE_HOME/bin of your database and run the command described in Example 16-12.

DB_OH/bin/impdp  \"sys/password@dbhost as sysdba\" REMAP_SCHEMA=srcrcuprefix_WEBCENTER:prdrcuprefix_WEBCENTER 
DIRECTORY=data_pump_dir DUMPFILE=wc.dmp TABLE_EXISTS_ACTION=REPLACE

where:

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

• password is the password for system database user.

• dbhost is the host name of the database.

• REMAP_SCHEMA maps the schema exported from the stage environment to the schema in the production environment. This is the RCU suffix that was used during installation along with the suffix _WEBCENTER. For example, DEV_WEBCENTER.

• DIRECTORY specifies the directory object created for the export and import operation.

  Note:

  The data_pump_dir file must have been created in SQL using a tool like SQL*Plus. For example:

  SQL> create or replace directory DATA_PUMP_DIR as '<full_path_to_a_directory_on_the_file_system>';
  SQL> commit;
  SQL> quit
  

• DUMPFILE contains the data to be imported.

• TABLE_EXISTS_ACTION replaces the existing table with the imported table.