1. Shut down the target WebCenter Portal instance.
2. Go to DB_ORACLE_HOME/bin of the database where the WEBCENTER schema is installed, connect to the database using sqlplus as sysdba and run the following commands:

   DB_ORACLE_HOME/bin/sqlplus "sys/password@serviceid as sysdba"
   create or replace directory dmpdir as 'mydmpdirectory';
   GRANT read,write ON directory dmpdir TO public;
   

3. Do one of the following:

   • If schema names on the source and target match:

     drop user tgtprefix_WEBCENTER cascade;
     exit;
     

   • If schema names on the source and target are different:

     drop user tgtprefix_WEBCENTER cascade;
     create user tgtprefix_WEBCENTER identified by password default tablespace
     tgtprefix_IAS_WEBCENTER temporary tablespace name_IAS_TEMP;
     grant connect,resource to tgtprefix_WEBCENTER;
     exit;
     

   Where:

   • tgtprefix_WEBCENTER is the user name. This is the RCU suffix that was used during installation, _WEBCENTER, along with a user supplied prefix. For example, DEV_WEBCENTER.

   • password is the password for the target user.

   • tgtprefix_IAS_WEBCENTER identifies the default tablespace. For example, the RCU suffix that was used during installation, IAS_WEBCENTER, along with a user supplied prefix. For example, DEV_IAS_WEBCENTER.

   • name_IAS_TEMP identifies the temporary tablespace. For example, DEV_IAS_TEMP.

4. Run the import tool.

   For example, to import WebCenter Portal schema data where source and target schema names match, run the following command:

   DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\"
    directory=mydmpdirectory dumpfile=webcenterportal.dmp SCHEMAS=tgtprefix_WEBCENTER
   

   For example, to import WebCenter Portal schema data where source and target schema names are different, run the following command:

   DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\"
    directory=mydmpdirectory dumpfile=webcenterportal.dmp 
    remap_schema=srcprefix_WEBCENTER:tgtprefix_WEBCENTER
    remap_tablespace=source_tablespace:target_tablespace exclude=user
    TABLE_EXISTS_ACTION=REPLACE
   

   Where:

   • DB_ORACLE_HOME is the directory in which the database for WebCenter Portal's schema (WEBCENTER) is installed.

   • password is the password for the system database user.

   • serviceid is the unique SID for the database. For example, mydb1234.

   • directory is the location on the database machine where the dump file is located.

   • dumpfile is the name of the file that contains data to be imported.

   • SCHEMAS identifies the target schema to be imported. Schema names include the RCU suffix that was used during installation (_WEBCENTER), along with a user supplied prefix. For example, DEV_WEBCENTER.

     Use this parameter when schema names on the source and target match. For example, both schemas are named DEV_WEBCENTER.

   • REMAP_SCHEMA identifies the source and target schemas. Use this parameter when schema names on the source and target are different. Schema names include the RCU suffix that was used during installation, _WEBCENTER, along with the user supplied prefix. For example, DEV_WEBCENTER.

   • REMAP_TABLESPACE identifies the source and target tablespace. Remaps all objects selected for import with persistent data in the source tablespace to be created in the target tablespace. For example, source_tablespace:target_tablespace.

   • TABLE_EXISTS_ACTION=REPLACE drops the current table and creates the table as it is in the dump file.

   For detailed impdp command information, see guide.

1. Shut down the target MDS instance.
2. Go to DB_ORACLE_HOME/bin of the database where the MDS schema is installed, connect to the database using sqlplus as sysdba and run the following commands:

   DB_ORACLE_HOME/bin/sqlplus "sys/password@serviceid as sysdba"
   create or replace directory dmpdir as 'mydmpdirectory';
   GRANT read,write ON directory dmpdir TO public;
   

3. Drop the MDS schema and exit sqlplus:

   drop user tgtprefix_MDS cascade;
   exit;
   

4. Run the import tool. For example, run the following command:

   DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\"
    directory=mydmpdirectory dumpfile=mds.dmp SCHEMA=tgtprefix_MDS
   

   Where:

   • DB_ORACLE_HOME is the directory in which the database for WebCenter Portal's MDS schema is installed.

   • password is the password for the system database user.

   • serviceid is the unique SID for the database. For example, mydb1234.

   • directory is the location on the database machine where the dump file is located.

   • dumpfile is the name of the file that contains data to be imported.

   • SCHEMAS is the schema to be imported. Include the RCU suffix that was used during installation (_MDS), along with the user supplied prefix. For example, DEV_MDS.

     Schema names on the source and target must match. For example, both schemas must be named DEV_MDS.

1. Shut down the target discussions server.
2. Go to DB_ORACLE_HOME/bin of the database where the DISCUSSIONS and DISCUSSIONS_CRAWLER schema is installed, connect to the database using sqlplus as sysdba and run the following commands:

   DB_ORACLE_HOME/bin/sqlplus "sys/password@serviceid as sysdba"
   create or replace directory dmpdir as 'mydmpdirectory';
   GRANT read,write ON directory dmpdir TO public;
   

3. Do one of the following:

   • If schema names on the source and target match:

     drop user tgtprefix_DISCUSSIONS cascade;
     drop user tgtprefix_DISCUSSIONS_CRAWLER cascade;
     exit;
     

   • If schema names on the source and target are different:

     drop user tgtprefix_DISCUSSIONS cascade;
     drop user tgtprefix_DISCUSSIONS_CRAWLER cascade;
     create user tgtprefix_DISCUSSIONS identified by password default tablespace
     tgtprefix_IAS_DISCUSSIONS temporary tablespace name_IAS_TEMP;
     grant connect,resource to tgtprefix_DISCUSSIONS
     exit;
     

   Where:

   • tgtprefix_DISCUSSIONS is the user name. This is the RCU suffix that was used during installation, _DISCUSSIONS, along with a user supplied prefix. For example, DEV_DISCUSSIONS.

   • password is the password for the target user.

   • tgtprefix_IAS_DISCUSSIONS identifies the default tablespace. For example, the RCU suffix that was used during installation, IAS_DISCUSSIONS, along with a user supplied prefix. For example, DEV_IAS_DISCUSSIONS.

   • name_IAS_TEMP identifies the temporary tablespace. For example, DEV_IAS_TEMP.

4. Run the import tool.

   For example, to import the discussions schema data where source and target schema names match, run the following command:

   DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\"
    directory=mydmpdirectory dumpfile=discussions.dmp
    SCHEMAS=tgtprefix_DISCUSSIONS,tgtprefix_DISCUSSIONS_CRAWLER
   

   For example, to import the discussions schema data where source and target schema names are different, run the following command:

   DB_ORACLE_HOME/bin/impdp \"sys/password@serviceid as sysdba\"
    directory=mydmpdirectory dumpfile=discussions.dmp 
    remap_schema=srcprefix_DISCUSSIONS:tgtprefix_DISCUSSIONS
    remap_schema=srcprefix_DISCUSSIONS_CRAWLER:tgtprefix_DISCUSSIONS_CRAWLER
    remap_tablespace=source_tablespace:target_tablespace exclude=user
    TABLE_EXISTS_ACTION=REPLACE
   

   Where:

   • DB_ORACLE_HOME is the directory in which the database for WebCenter Portal's discussions schemas are installed.

   • password is the password for the system database user.

   • serviceid is the unique SID for the database. For example, mydb1234.

   • directory is the location on the database machine where the dump file is located.

   • dumpfile is the name of the file that contains data to be imported.

   • SCHEMAS identifies the schema (or schemas) to be imported. Include the RCU suffix that was used during installation (_DISCUSSIONS and _DISCUSSIONS_CRAWLER), along with a user supplied prefix. The DISCUSSIONS and DISCUSSIONS_CRAWLER schemas have the same user supplied prefix, for example, DEV_DISCUSSIONS and DEV_DISCUSSIONS_CRAWLER.

     Use this parameter when schema names on the source and target match. For example, schemas in the source and target database are both named DEV_DISCUSSIONS and DEV_DISCUSSIONS_CRAWLER.

   • REMAP_SCHEMA identifies the source and target schemas. Use this parameter when schema names on the source and target are different. Schema names include the RCU suffix that was used during installation, _DISCUSSIONS, along with the user supplied prefix. For example, DEV_DISCUSSIONS.

     The DISCUSSIONS and DISCUSSIONS_CRAWLER schemas have the same user supplied prefix.

   • REMAP_TABLESPACE identifies the source and target tablespace. Remaps all objects selected for import with persistent data in the source tablespace to be created in the target tablespace. For example, source_tablespace:target_tablespace.

   • TABLE_EXISTS_ACTION=REPLACE drops the current table and creates the table as it is in the dump file.

1. In Fusion Middleware Control, navigate to the home page for WebCenter Portal.
2. From the WebCenter Portal menu, select Application Export.

   Figure 29-2 WebCenter Portal Menu - Application Export Option

   
   Description of "Figure 29-2 WebCenter Portal Menu - Application Export Option"
3. Change the File Name for the export archive or accept the default name.

   To ensure uniqueness, the default .par filename contains a unique ID—webcenter_wholeapp_ts_unique_ID.par.

   Figure 29-3 Naming the Export Archive

   
   Description of "Figure 29-3 Naming the Export Archive"
4. Click Export.
5. In the Download dialog, click Export to confirm that you want to go ahead.

   Figure 29-4 Downloading an Export Archive

   
   Description of "Figure 29-4 Downloading an Export Archive"

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

6. When the export process is complete, specify a location for the export archive (.par).

   Figure 29-5 Saving an Export Archive

   
   Description of "Figure 29-5 Saving an Export Archive"

   Select one of:

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

     Your browser downloads and saves the archive locally. The actual download location depends on your browser set up.

   • Export to Server - Saves the export PAR file to a server location.

     When the Archive Location dialog displays, enter a suitable path for Server Location, for example, /tmp, and then click Save. The name of the PAR is not required here.

     Ensure that the server directory you specify has write permissions.

     Figure 29-6 Archive Location

     
     Description of "Figure 29-6 Archive Location"
7. Click Close to dismiss the Export window.

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

   See Navigating to the Home Page for WebCenter Portal.

2. From the WebCenter Portal menu, select Application Import.
3. In the Application Import page (Figure 29-7), specify the location of your WebCenter Portal archive (.par).

   Figure 29-7 Application Import Page

   
   Description of "Figure 29-7 Application Import Page"

   Select one of the following:

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

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

   The archive you select must contain an entire WebCenter Portal export—you cannot import individual portals or portal templates from here. Refer to Importing Portals from an Archive for more information.

4. Click Import.
5. In the Application Import dialog (Figure 29-8), click Import.

   Figure 29-8 Application Import dialog

   
   Description of "Figure 29-8 Application Import dialog"

   Once the import is complete, a success message displays.

1. Restart the managed server (WC_Portal) on which the newly imported WebCenter Portal instance is deployed.

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

2. Log in to WebCenter Portal and verify that all portals and portal templates are available as expected.

   If not, see Portals and Portal Templates Not Available After Import.

3. Initiate the Elasticserch server crawler to index newly imported data.

master_script.sh can back up (export) WebCenter Portal data stored in the following database schemas:

• WEBCENTER

• MDS

• DISCUSSIONS

• DISCUSSIONS_CRAWLER

• OCS

• ACTIVITIES

• PORTLET

During back up, the script executes an export database command expdp for each schema you want to back up:

DB_ORACLE_HOME/bin/expdp \"sys/password@serviceid as sysdba\" directory=backup_directory dumpfile=dump_file_name.dmp SCHEMAS=prefix_SCHEMA_NAME EXCLUDE=STATISTICS NOLOGFILE=y 

The script also exports or imports WebCenter Content native files (vault folder) and web-viewable files (weblayout folder) stored on the file system.

• To back up WebCenter Content files stored on the file system, the script executes the following:

  tar cvf wcc_vault.tar WCP_ORACLE_HOME/ucm/vault

  tar cvf wcc_weblayout.tar WCP_ORACLE_HOME/ucm/weblayout

• To restore WebCenter Content files on the target file system, the script executes the following:

  tar xvf wcc_vault.tar

  tar xvf wcc_weblayout.tar

Finally, the script calls the WLST command script wlst_script.py. For details, see wlst_script.py.

The following is a sample master_script.sh script:

## master_script.sh
## Backs up or restores a WebCenter Portal installation
## Executes database export or import commands and a Python script containing WLST commands.
############ No User Input Required ########################################
# Reading the properties files for WebCenter Portal back up or restore...
PROPS_FILE=$1

exportimport=`sed '/^\#/d' $PROPS_FILE | grep 'OPERATION'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
dump_directory=`sed '/^\#/d' $PROPS_FILE | grep 'DATA_DIRECTORY'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_home=`sed '/^\#/d' $PROPS_FILE | grep 'DB_ORACLE_HOME'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_admin=`sed '/^\#/d' $PROPS_FILE | grep 'DB_ADMIN_USER'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_adminpwd=`sed '/^\#/d' $PROPS_FILE | grep 'DB_ADMIN_PASSWORD'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_sid=`sed '/^\#/d' $PROPS_FILE | grep 'DB_SID'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_connect_webcenter=`sed '/^\#/d' $PROPS_FILE | grep 'DB_CONNECT_WEBCENTER_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_connect_mds=`sed '/^\#/d' $PROPS_FILE | grep 'DB_CONNECT_MDS_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_connect_discussions=`sed '/^\#/d' $PROPS_FILE | grep 'DB_CONNECT_DISCUSSIONS_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_connect_ocs=`sed '/^\#/d' $PROPS_FILE | grep 'DB_CONNECT_OCS_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_connect_activities=`sed '/^\#/d' $PROPS_FILE | grep 'DB_CONNECT_ACTIVITIES_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
oracle_db_connect_portlet=`sed '/^\#/d' $PROPS_FILE | grep 'DB_CONNECT_PORTLET_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`

#Read schema information from the properties file.
src_webcenter_schema=`sed '/^\#/d' $PROPS_FILE | grep 'EXP_WEBCENTER_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
src_mds_schema=`sed '/^\#/d' $PROPS_FILE | grep 'EXP_MDS_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
src_ocs_schema=`sed '/^\#/d' $PROPS_FILE | grep 'EXP_OCS_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
src_discussions_schema=`sed '/^\#/d' $PROPS_FILE | grep 'EXP_DISCUSSIONS_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
src_discussions_crawler_schema=`sed '/^\#/d' $PROPS_FILE | grep 'EXP_DISCUSSIONS_CRAWLER_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
src_activities_schema=`sed '/^\#/d' $PROPS_FILE | grep 'EXP_ACTIVITIES_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
src_portlet_schema=`sed '/^\#/d' $PROPS_FILE | grep 'EXP_PORTLET_SCHEMA'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`


# Read WLST connection information from the properties file.
username=`sed '/^\#/d' $PROPS_FILE | grep 'WLST_ADMIN_USER'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
password=`sed '/^\#/d' $PROPS_FILE | grep 'WLST_ADMIN_PASSWORD'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
adminconsole=`sed '/^\#/d' $PROPS_FILE | grep 'WLST_ADMIN_CONSOLE'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
wlstlocation=`sed '/^\#/d' $PROPS_FILE | grep 'WLST_LOCATION'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
wlstscriptfile=`sed '/^\#/d' $PROPS_FILE | grep 'WLST_SCRIPT_LOCATION'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
wcpServer=`sed '/^\#/d' $PROPS_FILE | grep 'WCP_SERVER_NAME'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
jpsConfigFile=`sed '/^\#/d' $PROPS_FILE | grep 'JPS_CONFIG_FILE'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
sourceJpsContextPolicy=`sed '/^\#/d' $PROPS_FILE | grep 'SRC_JPS_CONTEXT_POLICYSTORE'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
destinationJpsContextPolicy=`sed '/^\#/d' $PROPS_FILE | grep 'TGT_JPS_CONTEXT_POLICYSTORE'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
sourceJpsContextCred=`sed '/^\#/d' $PROPS_FILE | grep 'SRC_JPS_CONTEXT_CREDSTORE'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
destinationJpsContextCred=`sed '/^\#/d' $PROPS_FILE | grep 'TGT_JPS_CONTEXT_CREDSTORE'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
backupPolicyStoreFile=`sed '/^\#/d' $PROPS_FILE | grep 'POLICYSTORE_FILE_NAME'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
backupCredStoreFile=`sed '/^\#/d' $PROPS_FILE | grep 'CREDSTORE_FILE_NAME'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
wccVaultLoc=`sed '/^\#/d' $PROPS_FILE | grep 'WCC_VAULT_LOC'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
wccWeblayoutLoc=`sed '/^\#/d' $PROPS_FILE | grep 'WCC_WEBLAYOUT_LOC'  | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`

#Data dump files that database schema data is exported to or imported from
wcdmp=wcdmp.dmp
mdsdmp=mdsdmp.dmp
discussionsdmp=discussionsdmp.dmp
ocsdmp=ocsdmp.dmp
activitiesdmp=activities.dmp
portletdmp=portlet.dmp

#Portlet client metadata export archive (.EAR) that portlet client metadata is exported to or imported from
portletdatafilename=portletdata.ear

#Audit configuration file that audit information is exported to or imported from
auditFileName=audit.xml

#Running WebCenter Portal back up and recovery scripts...

#On backup - Create a folder with a timestamp under the dump_directory folder
#On restore - Read user specified base directory to import from
current_time=$(date "+%Y.%m.%d-%H.%M.%S")
backup_directory=$dump_directory
if [ ! -z "$exportimport" ]; then
  if [ $exportimport = 'export' ]; then
    #'Creating backup directory.'
    backup_directory=$dump_directory/$current_time
    rm -rf $backup_directory
    mkdir $backup_directory
  fi
  if [ $exportimport = 'import' ]; then
    backup_directory=$dump_directory
  fi
fi

#Writing output to a log file
outputLogFile=$2
# Create a pipe file
mknod $backup_directory/pipefile.$$ p
# Start tee process in background to read it and output content to screen and log file
rm -rf $backup_directory/$outputLogFile
tee $backup_directory/$outputLogFile <$backup_directory/pipefile.$$ &
exec &>$backup_directory/pipefile.$$


#Common for backup (export) and restore (import)
#Create directories and grant read write permissions
export ORACLE_HOME=$oracle_db_home
export ORACLE_SID=$oracle_db_sid
export TNS_ADMIN=$ORACLE_HOME/network/admin
cd $oracle_db_home/bin

if [ ! -z "$exportimport" ]; then
  # Start back up (export)
  if [ $exportimport = 'export' ]; then
    echo 'Back up started...'
    if [ -n "$src_webcenter_schema" ] && [ -n "$wcdmp" ]; then
      ./sqlplus "$oracle_db_connect_webcenter as sysdba" << eof_disp
      create or replace directory dmpdir as '$backup_directory';
      GRANT read,write ON directory dmpdir TO public; 
eof_disp
      echo 'Exporting the WEBCENTER  schema...'
      ./expdp \"$oracle_db_connect_webcenter as sysdba\" directory=dmpdir
 dumpfile=$wcdmp  SCHEMAS=$src_webcenter_schema EXCLUDE=STATISTICS NOLOGFILE=y
    fi
    if [ -n "$src_mds_schema" ] && [ -n "$mdsdmp" ]; then
      ./sqlplus "$oracle_db_connect_mds as sysdba" << eof_disp
      create or replace directory dmpdir as '$backup_directory';
      GRANT read,write ON directory dmpdir TO public; 
eof_disp
      echo 'Exporting the MDS schema...'
      ./expdp \"$oracle_db_connect_mds as sysdba\" directory=dmpdir
 dumpfile=$mdsdmp  SCHEMAS=$src_mds_schema EXCLUDE=STATISTICS NOLOGFILE=y
    fi
    if [ -n "$src_discussions_schema" ] && [ -n "$discussionsdmp" ]; then
      ./sqlplus "$oracle_db_connect_discussions as sysdba" << eof_disp
      create or replace directory dmpdir as '$backup_directory';
      GRANT read,write ON directory dmpdir TO public; 
eof_disp
      echo 'Exporting the DISCUSSIONS schema...'
      ./expdp \"$oracle_db_connect_discussions as sysdba\" directory=dmpdir
 dumpfile=$discussionsdmp  SCHEMAS=$src_discussions_schema EXCLUDE=STATISTICS
 NOLOGFILE=y
    fi
    if [ -n "$src_ocs_schema" ] && [ -n "$ocsdmp" ]; then
      ./sqlplus "$oracle_db_connect_ocs as sysdba" << eof_disp
      create or replace directory dmpdir as '$backup_directory';
      GRANT read,write ON directory dmpdir TO public; 
eof_disp
      echo 'Exporting the OCS schema...'
      ./expdp \"$oracle_db_connect_ocs as sysdba\" directory=dmpdir
 dumpfile=$ocsdmp  SCHEMAS=$src_ocs_schema EXCLUDE=STATISTICS NOLOGFILE=y
      if [ -n "$wccVaultLoc" ]; then
        echo -e '\nExporting vault files for WebCenter Content...'
        cd $backup_directory
        tar cvf wcc_vault.tar -C $wccVaultLoc/vault .
        if [ -f "$backup_directory/wcc_vault.tar" ]; then
          echo -e '\nExported vault files for WebCenter Content to:
 '$backup_directory'/wcc_vault.tar'
        fi
        cd $oracle_db_home/bin
      fi 
      if [ -n "$wccWeblayoutLoc" ]; then
        echo -e '\nExporting weblayout files for WebCenter Content...'
        cd $backup_directory
        tar cvf wcc_weblayout.tar -C $wccWeblayoutLoc/weblayout .
        if [ -f "$backup_directory/wcc_weblayout.tar" ]; then
          echo -e '\nExported weblayout files for WebCenter Content to:
 '$backup_directory'/wcc_weblayout.tar'
        fi
        cd $oracle_db_home/bin
      fi
    fi
    if [ -n "$src_activities_schema" ] && [ -n "$activitiesdmp" ]; then
      ./sqlplus "$oracle_db_connect_ocs as sysdba" << eof_disp
      create or replace directory dmpdir as '$backup_directory';
      GRANT read,write ON directory dmpdir TO public; 
eof_disp
      echo 'Exporting the ACTIVITIES schema...'
      ./expdp \"$oracle_db_connect_activities as sysdba\" directory=dmpdir
 dumpfile=$activitiesdmp  SCHEMAS=$src_activities_schema EXCLUDE=STATISTICS
 NOLOGFILE=y
    fi
    if [ -n "$src_portlet_schema" ] && [ -n "$portletdmp" ]; then
      ./sqlplus "$oracle_db_connect_ocs as sysdba" << eof_disp
      create or replace directory dmpdir as '$backup_directory';
      GRANT read,write ON directory dmpdir TO public; 
eof_disp
      echo 'Exporting the PORTLET schema...'
      ./expdp \"$oracle_db_connect_portlet as sysdba\" directory=dmpdir
 dumpfile=$portletdmp  SCHEMAS=$src_portlet_schema EXCLUDE=STATISTICS NOLOGFILE=y
    fi

    #Call the WLST command script.
    cd $wlstlocation 
    ./wlst.sh $wlstscriptfile $exportimport $username $password $adminconsole
 $backup_directory/$portletdatafilename $wcpServer $jpsConfigFile
 $sourceJpsContextPolicy $destinationJpsContextPolicy $sourceJpsContextCred
 $destinationJpsContextCred $backup_directory/$auditFileName

#Copy the backup policy store and credential store files to the backup location.
    if [ -f "$backupPolicyStoreFile" ]; then
      mv $backupPolicyStoreFile $backup_directory
    fi
    if [ -f "$backupCredStoreFile" ]; then
      mv $backupCredStoreFile $backup_directory
    fi
    echo 'Back up completed successfully. Backup created at location:
 '$backup_directory'. Check the log file: '$backup_directory/$outputLogFile' for additional details.'
  fi

  #Start restore (import)...  
  if [ $exportimport = 'import' ]; then
    echo 'Restore started...'
    if [ -f "$backup_directory/wcc_vault.tar" ]; then
        echo -e '\nImporting vault files for WebCenter Content...'
        cd $wccVaultLoc/vault
        tar xvf $backup_directory/wcc_vault.tar
        echo -e '\nImported vault files for WebCenter Content from:
 '$backup_directory'/wcc_vault.tar to the location: '$wccVaultLoc'/vault'
    fi
      if [ -f "$backup_directory/wcc_weblayout.tar" ]; then
        echo -e '\nImporting weblayout files for WebCenter Content...'
        cd $wccWeblayoutLoc/weblayout
        tar xvf $backup_directory/wcc_weblayout.tar
        echo -e '\nImported weblayout files for WebCenter Content from:
 '$backup_directory'/wcc_weblayout.tar to the location:
 '$wccWeblayoutLoc'/weblayout'
      fi
    #Call the WLST commands script. 
    cd $wlstlocation
    ./wlst.sh $wlstscriptfile $exportimport $username $password $adminconsole
 $backup_directory/$portletdatafilename $wcpServer $jpsConfigFile
 $destinationJpsContextPolicy $sourceJpsContextPolicy $destinationJpsContextCred
 $sourceJpsContextCred $backup_directory/$auditFileName
    echo 'Restoration completed successfully. Check the log file:
 '$backup_directory/$outputLogFile' for additional details.'
  fi
fi
#Clean up pipe file
rm -f $backup_directory/pipefile.$$

The wlst_script.sh script connects to the Admin Console for your WebCenter Portal installation, and then either backs up (exports) or restores (imports) the following:

• Portlet client metadata

• Policy store

• Credential store

• Audit configuration information

Export WLST Commands Executed During Back Up

During back up, the script executes the following WLST export commands:

• exportPortletClientMetadata(appName, fileName, server)

• migrateSecurityStore(type='appPolicies', configFile, src, dst, overWrite, srcApp, dstApp)

• migrateSecurityStore(type='credStore', configFile, src, dst)

• exportAuditConfig(fileName)

Import WLST Commands Executed During Restore

During restore, the script executes the following WLST import commands:

• importPortletClientMetadata(appName, fileName, server)

• migrateSecurityStore(type='appPolicies', configFile, src, dst, overWrite, srcApp, dstApp)

• migrateSecurityStore(type='credStore', configFile, src, dst)

• importAuditConfig(fileName)

The following is a sample wlst_script.py script:

## wlst_script.py
## Python script that runs export and import WLST commands.
############ No User Input Required ###################

# Get user credentials and other parameters from the properties file
exportOrImport = sys.argv[1]
username = sys.argv[2]
password = sys.argv[3]
adminconsole = sys.argv[4]
fileName = sys.argv[5]
wcpServerName = sys.argv[6]
jpsConfigFile = sys.argv[7]
destination = sys.argv[8]
source = sys.argv[9]
dstCred = sys.argv[10]
sourceCred = sys.argv[11]
auditFileName=sys.argv[12]
 
# Connect to the given host
connect(username,password,adminconsole)
 
if (exportOrImport == 'export' ):
# Run export WLST commands
  # Export portlet data
  print 'Exporting portlet data...'
  exportPortletClientMetadata(appName='webcenter', fileName=fileName, server=wcpServerName)
  if webcenterErrorOccurred(): # COMMAND STATUS
      print "Error while exporting the portlet data."
  else:
      print 'Successfully exported the portlet data.'
 
  # Export security
  disconnect() 
  print 'Exporting the policy store...'
  migrateSecurityStore(type='appPolicies', configFile=jpsConfigFile, src=source,
 dst=destination, overWrite='true', srcApp='webcenter', dstApp='webcenter')
  print 'Exporting the credential store...'
  migrateSecurityStore(type='credStore', configFile=jpsConfigFile, src=sourceCred,
 dst=dstCred)
  print 'Exporting audit configuration...'
  exportAuditConfig(fileName=auditFileName)
 
elif (exportOrImport == 'import' ):
# Run import WLST commands
  # Import portlet data
  print 'Importing portlet data...'
  importPortletClientMetadata(appName='webcenter', fileName=fileName, server=wcpServerName)
  if webcenterErrorOccurred(): # COMMAND STATUS
      print "Error while importing portlet data."
  else:
      print 'Successfully imported portlet data.'
 
  # Import security
  disconnect()
  print 'Importing the policy store...'
  migrateSecurityStore(type='appPolicies', configFile=jpsConfigFile, src=source, dst=destination, overWrite='true', srcApp='webcenter', dstApp='webcenter')
  print 'Importing the credential store...'
  migrateSecurityStore(type='credStore', configFile=jpsConfigFile, src=sourceCred, dst=dstCred)
  print 'Importing audit configuration...'
  importAuditConfig(fileName=auditFileName)

1. Create a directory on the file system for your scripts and backups.

   For example: /scratch/aime1/mywebcenterportal_scripts/backups

2. Copy the sample code for master_script.sh from master_script.sh, paste into a text editor, and save the file as master_script_backup.sh into the directory you created in step 1.

   Note:

   Ensure that the script does not contain any hidden characters or DOS characters if running on Unix/Linux.

3. Copy the sample code for wlst_script.py from wlst_script.py, paste into a text editor, and save the file as wlst_script.py in the same directory.
4. Copy the sample code for backup.properties from backup.properties and restore.properties Files, paste into a text editor, and save the file as backup.properties in the same directory.

1. Open backup.properties in a text editor.
2. Ensure OPERATION=export.
3. Specify values for parameters in the file.

   Refer to Table 29-3 for a description of each parameter.

   Note:

   You can comment out parameters that are not required.

4. Customize the back up scripts, if required.

   To exclude objects, comment out the associated back up command code. To back up additional objects using the script, add the required code.

5. Save the changes.

1. Set the following environment variables:

   ORACLE_HOME

   ORACLE_SID

   TNS_ADMIN

2. Verify that you have permissions to read and write to all directories used during the backup process.
3. Run the master back up script, specifying the name of the backup properties file and a log file name as follow:

   sh master_backup_script_name backup_properties_file_name log_file_name
   

   For example:

   sh master_script_backup.sh backup.properties mybackup.log
   

   The message "Backup completed successfully..." indicates when the backup process is complete and the directory in which your backups and the export.log file are located.

   Each time you run the script, backup data is saved to a different folder under the main backup folder (DATA_DIRECTORY) so that previous backups are retained. Timestamp information is included in backup folder names so its easy to associate your backups with a particular date and time.

1. Navigate to the directory containing your data backups, that is, a timestamped folder under the location you specified for the DATA_DIRECTORY parameter in backup.properties.
2. Verify the following back up files are available:

   • one or more .dmp files

   • wcc_vault.tar

   • wcc_weblayout.tar

   • portletdata.ear

   • backup-system-jazn-data.xml

   • cwallet.sso

   • audit.xml

   • .log file

1. Duplicate the backup scripts that you created earlier master_script.sh wlst_script.py (following steps in section Using Scripts to Back Up WebCenter Portal) and copy them to a different location.

   For example: /scratch/aime1/mywebcenterportal_scripts/restore

2. Copy the sample code for restore.properties from backup.properties and restore.properties Files, paste into a text editor, and save the file as restore.properties in the same directory.
3. Rename the files, if required.

   For example: master_script_restore.sh, wlst_restore_script.py, restore.properties

1. Ensure that all the target schemas were created using RCU and the names of the target schemas match the source schema names.
2. (Optional). If you want to point the default data sources to different schemas, use the WebLogic Server Admin Console to update the schema names, and database details.
3. Stop all the servers.
4. Restore schema data, as required.

   Note:

   Database schemas WEBCENTER and MDS must be restored together to ensure the data is in-sync.

   If you need to restore additional schemas, such as PORTLET or OCS, you must restore them at the same time, after WEBCENTER and MDS, and from the same point to maintain data integrity.

   This example shows you commands to restore WEBCENTER and MDS schemas:

   ./sqlplus "sys/password@serviceid as sysdba"
   create or replace directory dmpdir as 'mydmpdirectory';
   GRANT read,write ON directory dmpdir TO public;
   
   ##Drop WEBCENTER and MDS schemas ##
   
   drop user srcprefix_WEBCENTER cascade;
   drop user srcpreix_MDS cascade;
   exit;
   ./impdp \"sys/password@serviceid as sysdba\" directory=dmpdir dumpfile=webcenterportal.dmp SCHEMAS=srcprefix_WEBCENTER
   ./impdp \"sys/password@serviceid as sysdba\" directory=dmpdir dumpfile=mds.dmp SCHEMAS=srcprefix_MDS
   

   Where:

   • password is the password for the system database user.

   • serviceid is the unique SID for the database. For example, mydb1234.

   • directory is the location on the database machine where the dump files are located.

   • dumpfile is the name of the file that contains data to be imported.

   • SCHEMAS identifies the target schemas. Schema names include the RCU suffix that was used during installation (_WEBCENTER and _MDS), along with a user supplied prefix. For example, DEV_WEBCENTER.

     Schema names on the source and target must match. For example, both schemas must be named DEV_WEBCENTER.

   For example:

   ./sqlplus "sys/mypassword@db1234 as sysdba"
   create or replace directory dmpdir as '/scratch/mywebcenterportal_scripts/backup/2013.05.04-02.36.48';
   GRANT read,write ON directory dmpdir TO public;
   
   ##Drop WEBCENTER and MDS schemas ##
   
   drop user DEV_WEBCENTER cascade;
   drop user DEV_MDS cascade;
   exit;
   ./impdp \"sys/mypassword@db1234 as sysdba\" directory=dmpdir dumpfile=wcdmp.dmp SCHEMAS=DEV_WEBCENTER
   ./impdp \"sys/mypassword@db1234 as sysdba\" directory=dmpdir dumpfile=mdsdmp.dmp SCHEMAS=DEV_MDS

   Note:

   If you need to restore other schemas, such as DISCUSSIONS, PORTLETS, ACTIVITIES, and OCS, then do so now before starting the servers.

5. Start all the servers.

1. Open restore.properties in a text editor.
2. Ensure that OPERATION=import.
3. Specify values for all parameters in the file.

   Refer to Table 29-3 for a description of each parameter.

4. Save the changes.

1. Set the following environment variables:

   ORACLE_HOME

   ORACLE_SID

   TNS_ADMIN

2. Verify that you have permissions to read and write to all directories used during the restore process.
3. Run the master restoration script, specifying the name of the restore properties file and a log file name as follow:

   sh master_restore_script_name bestore_properties_file_name log_file_name
   

   For example:

   sh master_script_restore.sh backup.properties myrestore.log
   

   The message "Restoration completed successfully..." indicates when the restore process is complete and the directory where the restore.log file is located.

1. If you import one or more database schemas, shut down and restart those databases, and restart all managed servers.
2. Verify the target WebCenter Portal instance includes the restored data.