Back Up and Restore Essbase: Weblogic Security Plus an Identity Provider

Use the following process to back up and restore an Essbase instance if you are using WebLogic Security plus an identity provider.

Back Up Essbase: WebLogic Security Plus an Identity Provider

Use the following process to back up an Essbase instance if you are using WebLogic Security plus an identity provider.

Back Up Contents of the Source Application Directory

Your backup strategy for the source <Application Directory> will depend on the hardware used to create it. If you mounted a separate disk volume, then you have a portable backup. You should still routinely take a backup your <Application Directory> with every planned periodic backup.

If you do not know where <Application Directory> is, see Environment Locations in the Essbase Platform.

If you haven’t mounted your source <Application Directory> as a separate drive, you can simply compress its contents and safely move the archive to a secure, separate location. If you mounted a separate disk volume, you can copy the disk volume.
1. Check that the Essbase services are stopped. See Stop, Start, and Check Servers.
2. Navigate to the <Application Directory>.
  
  Example:
```
cd /scratch/user/oracle_home/user_projects/applications/essbase
```
3. Compress the directory contents, providing the location and file name.
  
  There is no need to back up jagentId.id. A new one is created on the target, and you should not overwrite it. The example shows how to exclude it from the backup.
```
tar -czvf <path to backup file location>/<backupfilename>.tar.gz --exclude jagentId.id *
```
  Example:
```
tar -czvf /scratch/user/backups/appdir_backup.tar.gz --exclude jagentId.id *
```
Back Up the source Essbase Relational Database Schema.

Depending on the relational database you configured for use with Essbase, your steps may vary. The following example illustrates the use of Oracle Data Pump against supported Oracle Databases.

Execute Oracle Data Pump from the command line on the server where your Oracle Database is installed.

Note:
Alternatively, you can manage your database remotely using Oracle Instant Client.

Assume your source Essbase instance is deployed with a relational database schema prefix called essbase1.
1. Make sure that the source Essbase services are still stopped.
2. Confirm that the pluggable database (PDB) into which you deployed the Essbase schemas is in the tnsnames.ora file.
3. On the server running Oracle Database, create a directory path into which Data Pump can write database export files. Make sure the operating system user executing Data Pump commands has write privileges on this path.
  
  Example:
```
mkdir /scratch/user/expuserfiles
```
4. Connect to the database containing the source Essbase schema.
5. Log in to SQL*Plus as sysdba, and create a role for your Data Pump user with the following minimum roles/privileges:
```
alter session set container=<your container name>;
create user <username> identified by <password>;
create directory <dirname> as '<full path disk location>';
create role <rolename>;
grant create session, create table to dp_role;
grant read, write on directory exports to <rolename>;
grant DATAPUMP_EXP_FULL_DATABASE to <rolename>;
grant DATAPUMP_IMP_FULL_DATABASE to <rolename>;
grant <rolename> to <username>;
alter user <username> default tablespace users;
alter user <username> quota unlimited on users;
exit;
```
  Example:
```
alter session set container=orclpdb; 
create user expuser identified by password;
create directory exports as '/scratch/user/expuserfiles';
create role dp_role;
grant create session, create table to dp_role;
grant read, write on directory exports to dp_role;
grant DATAPUMP_EXP_FULL_DATABASE to dp_role;
grant DATAPUMP_IMP_FULL_DATABASE to dp_role;
grant dp_role to expuser;
alter user expuser default tablespace users;
alter user expuser quota unlimited on users;
exit;
```
6. Execute Oracle Data Pump from the command line on the server where Oracle Database is installed.
  
  Note:
  Alternatively, you can manage your database remotely using Oracle Instant Client.
  On the server where Oracle Database is running, export the <schemaprefix>_Essbase schema using the Data Pump expdp command:
  
  Note:
  Be sure to set the Oracle environment for your database before running Data Pump.
```
expdp <username>@<service name> directory=<dirname> dumpfile=<dumpfilename>.dmp logfile=<logname>.log schemas=<schemaprefix>_Essbase
```
  Example:
```
expdp expuser@orclpdb directory=exports dumpfile=essbase1.dmp logfile=essbase1.log schemas=essbase1_Essbase
```

Restore Essbase: WebLogic Security Plus an Identity Provider

Use the following process to restore an Essbase instance if you are using WebLogic Security plus an identity provider.

Configure a target Essbase instance.

If your source host/hardware didn't fail and you are just recovering your Essbase instance, you can unconfigure the source instance and then configure a new target instance using the same Fusion Middleware <ORACLE_HOME>.

If you do not know where <ORACLE_HOME> is, see Environment Locations in the Essbase Platform.
1. Use the Essbase Configuration Tool to configure a target Essbase instance. The configuration tool is located at:
```
/<path to Fusion Middleware Oracle Home>/essbase/bin/config.sh
```
  Example:
```
/scratch/user/oracle_home/essbase/bin/config.sh
```
2. Configure the target domain:
  1. Use the same WebLogic administrator username and password as is used in the Essbase source instance.
  2. Use the same domain name as is used in the source instance.
  3. Use the same <Application Directory> as is used in the source instance.
    
    It is essential that the full <Application Directory> is identical on the target instance, otherwise, some Essbase functionality will not work.
    
    If you do not know where <Application Directory> is, see Environment Locations in the Essbase Platform.
  4. You may use the same pluggable database (PDB), or a different one.
    
    Note:
    
    You will need a new schema prefix, unless you removed your source schemas during unconfiguration.
  5. Do not select EPM Shared Services security.
  Refer to your configuration response file from the source instance, which was originally created at /tmp/essbase_config_<date_timestamp>/config.rsp.
Configure an identity provider.

After configuring your target instance, configure your identity provider. See WebLogic Authentication.

Note:
When you configured your source domain, you may have selected a federated user and assigned system administrator role to that user. In that case, you do not need to assign roles in this new target domain.
Restore the <Application Directory> contents from the source backup into the target instance.
1. Confirm that all services on the target instance are stopped. See Stop, Start, and Check Servers.
2. Move the existing/source <Application Directory> to a different location.
  
  Example:
```
mv /scratch/user/oracle_home/user_projects/applications/essbase /scratch/user/oracle_home/user_projects/applications/essbase.old 
```
3. Create the new/target <Application Directory>.
  
  Example:
```
mkdir /scratch/user/oracle_home/user_projects/applications/essbase
```
4. Navigate to the new/target <Application Directory>.
  
  Example:
```
cd /scratch/user/oracle_home/user_projects/applications/essbase
```
5. Unzip the contents of the source <Application Directory> backup into the new/target <Application Directory> (directories extracted may include app, catalog, and hybrid, depending on what you backed up).
```
tar -zxvf <path to backup file location>/<backup file name>.tar.gz
```
  Example:
```
tar -zxvf /scratch/user/backups/appdir_backup.tar.gz
```
Restore the Essbase Relational Database Schema.

Depending on the relational database you configured for use with Essbase, your steps may vary. The following example illustrates the use of Oracle Data Pump against supported Oracle Databases.
1. Confirm that all services on the target instance are stopped.
2. Execute Oracle Data Pump from the command line on the server where Oracle Database is installed.
  
  Note:
  Alternatively, you can manage the database using Oracle Instant Client.
3. Import the Essbase source schema backup (.dmp file) into the target, replacing the source schema prefix with the target schema prefix:
```
impdp <username>@<service name> directory=<dirname> dumpfile=<source dumpfilename>.dmp REMAP_SCHEMA=<source schemaprefix>_Essbase:<target schemaprefix>_Essbase partition_options=merge table_exists_action=replace
```
  Example:
```
impdp expuser@orclpdb directory=exports dumpfile=essbase1.dmp  REMAP_SCHEMA=essbase1_ESSBASE:essbase2_ESSBASE partition_options=merge table_exists_action=replace
```
Start target instance Essbase services. See Stop, Start, and Check Servers.