• Shared Services LCM Administrator
• Reporting and Analysis Global Administrator

1.

In the Source environment, log on to Shared Services as the user who is provisioned with the appropriate LCM roles.

2.

Navigate to Foundation > Shared Services, and select the Native Directory provisioning artifacts and the Task Flows that are applicable to the Reporting and Analysis repository, as follows:

• Users – Native Directory users
• Groups – Native Directory groups
• Assigned Roles – Roles granted to users and groups through the provisioning process. You should select the roles for the associated product artifacts that pertain to the Reporting and Analysis repository.

Note: You should choose the assigned roles for all products that contain artifacts for the Reporting and Analysis repository.

Navigate to the Reporting and Analysis repository to select the artifacts that you want to migrate.

On the Selected Artifacts tab, review the set of artifacts that you selected for the Reporting and Analysis migration.

Click the Define Migration button to define the Reporting and Analysis migration.

Select the first product to migrate (for example, Shared Services), and click Next.

On the Source Options page, enter the user, groups, and role filters, and click Next.

On the Destination page, enter the name of the file system folder where the Shared Services artifacts will be extracted, and click Next.

Review the destination options to ensure that the parameters are correct, and click Next.

You are directed back to the beginning of the migration wizard so that you can define the other product migrations.

Select Reporting and Analysis, and click Next.

On the Source Options page, optionally select Export with Job Output if you want that information to be migrated, and click Next.

On the Destination page, enter the name of the file system folder where the Shared Services artifacts will be extracted, and click Next.

Review the Destination Options page to ensure that the parameters are correct, and click Next.

Review the Migration Summary to ensure the defined migrations are correct.

Click Save Migration Definition.

Select Save as XML, and click OK.

Click Save.

Enter the location and name for the migration definition file, and click Save.

In the Download Complete dialog box, click Close.

Click Close.

Click Execute Migration.

The Reporting and Analysis migration is executed.

Click Launch Migration Status Report.

On the Migration Status Report page, review the status of the migration. Refresh the Migration Status Report to see that the migration is completed.

When the report status changes to Completed, the migration is completed successfully, and the Reporting and Analysis artifacts are extracted to the file system.

In the source environment, navigate to Windows Explorer on the file system.

Select Tools > Map Network Drive.

Enter the parameters for the destination environment file system location.

Click Finish.

Navigate to the location of the source environment database artifacts.

Select the folders, right-click, and select Copy.

Navigate to the newly mapped destination location, right-click, and select Paste.

The Reporting and Analysis artifact folders now reside on the destination server file system location.

In the Destination environment, log on to Shared Services as the user who is provisioned with the appropriate LCM roles..

Navigate to Application Groups > File System, and select the Reporting and Analysis and Shared Services artifacts.

On the Selected Artifacts tab, review the artifacts that you selected for the migration .

Click Define Migration.

Select the Shared Services artifacts, and click Next.

Review the Source Options page, and click Next.

On the Destination page, select the Shared Services destination, and click Next.

On the Destination Options page, select the Import Operation Type, enter the number of Max Errors Before Stopping Import, and click Next.

Select the Reporting and Analysis artifacts, and click Next.

Review the Source Options page, and click Next.

Choose the Reporting and Analysis repository where you want the artifacts imported and click Next.

On the Destination Options page, optionally select Exclude Job Output on Import, and click Next.

Review the Migration Summary, and click Save Migration Definition.

Click OK.

In the File Download dialog box, click Save.

Enter the location and migration definition file name, and click Save.

17 .

In the Download Complete dialog box, click Close.

Click Close again.

Click Execute Migration.

Click Launch Migration Status Report.

Migration has been completed.

Log on to Workspace.

Select Tools > Change Database Connections.

Select the appropriate Financial Reporting object, and click OK

The Change Database Connection dialog box is displayed.

In the Replace With list, select a replacement database connection.

Optional: Create another database connection.

Launch CMC UI (%HYPERION_HOME%\common\workspacert\9.5.0.0\bin\StartUI.bat).

Log on to http://host:55000/cmc with your user ID and password.

Right-click the Interactive Reporting Data Access Service, select Properties, and select the Data Sources tab.

Click New and specify your ODBC connection information.

Click OK.

Restart the Agent for the Interactive Reporting Data Access Service.

Log on to the Service Configurator.

Note: The Service Configurator may be manually accessed through %HYPERION_HOME%\products\Foundation\workspace\bin\ServiceConfig.bat.

Select the job factory service ( JF1_hostname) from the Services list and click the Properties button.

The Properties dialog box is displayed.

Select the PR tab and click Add.

Select the appropriate SQR Server type, and click OK.

In the Setup PR Server dialog box, enter the path to the appropriate SQR server bin folder, and click OK.

For example, %HYPERION_HOME%\products\biplus\bin\SQR\Server\ODBC\bin.

The SQR server is defined.

If the generic application definition is already imported, select the Application tab, and choose the application from the drop-down list.

Select the Executable tab, and click Add.

Enter the path to the command window (for example, C:\windows\system32\cmd.exe) and the environment variables, if necessary.

Click OK twice.

The Generic Application executable is defined.