Purpose
This tutorial shows you how to migrate an Essbase application from one server to another using Migration Wizard.
Scenario
In this tutorial, you migrate an Essbase application from an Essbase Release 7.1.0 server (localhost:1425) to a Release 9.3.1 server (WIN3KB). Both servers are running Essbase native security.
Prerequisites
Before starting this tutorial, you should:
| 1. |
Have both an Essbase Release 7.1.0 server and an Essbase Release 9.3.1 server installed and running.
|
| 2. |
Utilize Essbase native security on both servers.
|
| 3. |
Have an Essbase application on the Release 7.1.0 server available for migrating. This tutorial migrates an application called Mexcorp.
|
Usage Notes
The following points apply to applications migrated using Migration Wizard:
| 1. |
Only application and database objects and user/group security are migrated . No data is transferred.
|
| 2. |
Objects and security on the source server are unchanged. Migration Wizard makes copies on the target server.
|
| 3. |
Source and target servers may be on different operating systems. For example, you can migrate an application from a Windows to a Unix server.
|
Examining Source and Target Servers
| 1. |
From Administration Services Console in the navigation panel, double-click the Release 7.1.0 server node localhost:1425 and expand Applications to reveal the Mexcorp application.
 |
| 2. |
Expand the Mexcorp application to reveal the Mexsales database, including the database outline, calculation script CalcMex, and rules file LoadMex.
 |
| 3. |
Expand the localhost:1425 Security node, right-click Users, and from the drop-down list, select Display users table.
In a subsequent step, we will select to migrate user JCanseco, shown here in the source server Users table.
User JCanseco has filter access to the Mexsales database. This security privilege will be preserved during the migration.
 |
| 4. |
On target server WIN3KB, expand the Security node and openthe Users table.
 |
| 5. |
On target server WIN3KB, user JCanseco is not yet represented.
 |
Launching Migration Wizard
| 1. |
From the Administration Services Console control menu, select File > Wizards > Migration.
The Migration Wizard dialog box is displayed, showing the following steps to be performed:
 |
Selecting Source and Target Servers
From the User level drop-down list, select Advanced (to enable user/group security transfer). From the Source Analytic Server drop-down list, select localhost:1425. Finally, from the Target Analytic Server drop-down list, select WIN3KB and then click Next.
 |
Selecting Source and Target Applications
From the Source application on Analytic Server drop-down list, select Mexcorp. In the Target application on Analytic Server text box, enter Mexcorp. Finally, select Replace target objects if they exist and then click Next.
Selecting Application-Level Objects to Migrate
Ensure that all application-level checkboxes are checked. Click Next.
Selecting Database-Level Objects to Migrate
Expand the Databases node and ensure that all database-level checkboxes are selected.
Optionally, expand subnodes to see individual objects.
Click Next.
Selecting Security Migration Options
Select radio button Do not change permissions of user/group. Click Next.
Selecting Individual Groups to Migrate
There are no groups to migrate in this example. Click Next.
Selecting Individual Users to Migrate
Ensure that user JCanseco is displayed under Selected Users. If not, select user JCanseco in Available Users and use the arrow button to move the username to Selected Users.
Click Finish.
When the migration is complete, a message is displayed in the message panel of Administration Services Console.
Examining Migration Results
| 1. |
In the Navigation panel, expand the target server node (WIN3KB) to reveal the migrated Mexcorp application. If Mexcorp is not displayed, right-click Applications and select Refresh application list.
 |
| 2. |
In the Navigation panel under the target server node (WIN3KB), expand Security , then right-click Users and select Display users table.
The target server (WIN3KB) users table is displayed, showing that user JCanseco has migrated from the Release 7.1.0 server to the Release 9.3.1 server.
 |
| 3. |
Optionally, review access privileges for user JCanseco on the target server (WIN3KB). Permissions should reflect filter-level access to the Mexsales database through filter jcanfilter.
 |
Summary
In this lesson, you learned how to migrate an Essbase application from one server to another using Migration Wizard, where native security was in force.
