STEPS FOR MIGRATING PLANNINGAPPLICATION This process of Migrating planning application is carried out in 5 main steps as given below…

I. II. III. IV. V. I. Export/Import of the application schema from DB server. Expor/Import of Business Rules. Exportig Data from source application and importing in target applciation. Export/Import Shared Services Security and provisioning Export/Import of BI+ Reports Export/Import of the application schema from DB server.

Source Server Side: 1. Export source planning application schema (appName.dmp)

2. Transefer the dump file appName.dmp to the Targer server location Target Server Side: 3. Stop the Planning service on target server 4. Copy the SID for admin user from target appName Schema Select * from HSP_USERS; USER_ID=50001 for admin SID=native://DN=cn=a761603468c8757b:66e3e0c5:119112a5db7:7f2a,ou=People,dc=css,dc=hyperion,dc=com?USER 5. Copy the applciation owner user detials on the target application 6. Drop all the objects from the target appName schema 7. Import the schema exported in step 1 for target application schema

8. Update SID for user whose object_id=50001 on newly imported schema on target SQL> select * from HSP_USERS where user_id=50001; USER_ID SID ROLE SYNC_PSWD OFFLINE_ENABLED HUB_ROLES -----------------------------------------------------------------------------------------50001 native://DN=cn=e9a26e998aa8de30:3f6f31ff:117d27fada9:7ffe,ou=People,dc=css,dc=hyperion,dc=com?USER 3 2 0 411 SQL> update HSP_USERS set SID='native://DN=cn=a761603468c8757b:66e3e0c5:119112a5db7:7f2a,ou=People,dc=css,dc=hyperion,dc=com?USER' where user_id=50001; 1 row updated. SQL> commit; Commit complete. 9. Update username on the target applciation schema SQL> select OBJECT_NAME from HSP_OBJECT where OBJECT_ID=50001; OBJECT_NAME -------------------------------------------------------------------------------Testuser SQL> update HSP_OBJECT set OBJECT_NAME='hypadmin' where OBJECT_ID=50001; 1 row updated. SQL> commit; Commit complete. 10. Update Group details on the Target schema: SQL> select * from HSP_GROUP; GROUP_ID SID -----------------------------------------------------------------------------------------50488 native://DN=cn=e9a26e998aa8de30:-14a35b39:1181f27754a:7ff1,ou=Groups,dc=css,dc=hyperion,dc=com?GROUP 50490 native://DN=cn=e9a26e998aa8de30:-14a35b39:1181f27754a:7ffc,ou=Groups,dc=css,dc=hyperion,dc=com?GROUP 64673 native://DN=cn=e9a26e998aa8de30:-14a35b39:1181f27754a:7ffa,ou=Groups,dc=css,dc=hyperion,dc=com?GROUP

SQL> select OBJECT_NAME from HSP_OBJECT where OBJECT_ID in (50488,50490,64673); OBJECT_NAME -------------------------------------------------------------------------------Administrators FPA Planner 11. Start the Planning Service on the target server 12. On Target serverLogin into Hyperion Workspace with the applciation userid and Password 13. Open the Newly migrated application to confirm the the objects are moved (Forms, Dimension and Members) Navigate->Applications->Planning->CMC (To open application)

Administration->Dimension (To confirm Dimensions) Administration-> Manage Data Forms (To confirm Data Forms)

14. Update the Shared Services URL and Register with Shared Services Administration->Application Settings

15. Confirm the URL and PORTS Administration->Manage Properties->System Properties

16. Migrate any “Substituation Variables” used in source application from AAS console

17. Refresh the Application from Planning web to sync with Essbase. Administration -> Manage Database -> Refresh

18. Migrate all other objects (calc script, report script, outline, business rules etc) of this application from source using Migration Wizars in AAS console

19. Repeat step 16 once again to refresh the database and sync with Essbase.

II.

Expor/Import of Business Rules.

The process of Business Rule migration involves exporting “Variables”, “Macros”,“Sequences” and “Business Rules”, “Projects” togather in the same order from source server and Importing on to the target server. Here basically we are exporting the above-mentioned objects in the XML format and importing. Source Server Side: 1. Login into AAS console and from the navigation panel right click on the “Business Rules” and select “Export Business Rules” option.

2. From the “Export Business Rules” window select the “Variables” tab and select the all variables and click on the “Export” button, this action will prompt for filename and location for storing this XML file. Provde the file name and location to save this XML file.

3. Repeat the above steps for Macros and Sequences if you have any, finally select Business Rules and Projects togather and export so that the association of Business Rules with Projects will take place. 4. Finally export these XML files to the Target server location. Target Server Sode: 1. Login into AAS console and from the navigation panel right click on the “Business Rules” and select “Import Business Rules” option.

2. From the “Import Business Rules” window select the “Variables” tab and select the all variables and click on the “Import” button, this action will prompt for XML filename. Browse to the directory and select the XML file for Variables and which is transeferred from the source click OK to import.

III.

Exportig Data from source application and importing in target applciation.

Exporting Data from Source: 1. Export All data from source app/db in txt format from AAS in .txt format  Login into AAS console:  In the Navigation Panael drill down till application and right click on the database and select the option “Export”.  In the “Export Database” pop-up window enter the file name and select “All Data” option click “OK”  Perform the same steps for all other databases in the application.

Transefer these exported data files to the target server using FTP or anyother way.

Loading Data into Application a. Login into target AAS console b. From the Navigation Panel dirll down till the application which is migrated newly c. Right click on the Database and selcect the option “Load Data”

d. In the “Data Load” pop-up window confirm the “Data Source Type” is “Data File” and click on “Find Data File” button to select the data file

Browse to the directory where the data files are transefered and select the file for loading and click “OK” button

Click on the “OK” button on the “Data Load” window to being the dataload process.

Confirm the dataload is success in Data Load Results window and also in the AAS console’s message panel whices says Dataload Succeeded.

Repeat step 3 and 4 for other databases in the application.

IV. Export/Import Shared Services Users and provisioning This step is peroformed using Shared Services Import/Export command line utility to import, export and validation user provisioning data in the native OpenLDAP directory, performs this process. Source Server side: 1. Login into Source Shared Services server machine. 2. Browse to the following directory HYPERION_HOME/common/utilities/CSSImportExportUtility Unzip “cssimportexport.zip”on the same location and this will create a new directory “importexport”.

Browse to importexport/Samples directory and copy “importexport.properties” file to “importexport” directory

Open the importexport.properties file from the location HYPERION_HOME/common/utilities/CSSImportExportUtility/importexport directory And update the following lines which are highlighted .

Also update the highlighted line under “EXPORT OPERATIONS”

Save the changes in the above file and run the CSSExport.bat with parameter as importexport.properties filename from the command line.

This will generate an XML file on the location mentioned in the importexport.properties file, transefer that file to the target server. Target Server Side: 1. Login into Target server machine 2. Browse to the following directory HYPERION_HOME/common/utilities/CSSImportExportUtility Unzip “cssimportexport.zip”on the same location and this will create a new directory “importexport”.

Browse to importexport/Samples directory and copy “importexport.properties” file to “importexport” directory

Open the importexport.properties file from the location HYPERION_HOME/common/utilities/CSSImportExportUtility/importexport directory And update the following lines which are highlighted .

Also update the lines highlighted under IMPORT OPERATIONS section

Save the changes in the above file and run the CSSImport.bat with parameter as importexport.properties filename from the command line.

V. Export/Import of BI+ Reports The process of exporting and importing BI+ reports is very simple task; this does not involve security and provisioning migration. The security and provisioning for reports is performed manually once the reports are imported on the target. The database connection for these reports has to be created or can be created during import process. Source Server Side: 1. Login into Source Workspce URL and go to Navigate -> Explore page. 2. Select on File -> Export option

3. The above step will pop-up “Select Financial Documents to Export” window, from this window select the reports you wanted to export and click OK button. This action will pop-up “File Download” window to save the Reports to the local disk, click “Save” on this window and Save the reports as ZIP or DES format Note: Save as ZIP if you have more than one report, for single report save as ReportName.dec

Target Server Side: 1. Login into Target Workspace URL and go to Navigate->Explore page. 2. Select File -> Import -> Financial Reports option

4. From the “Import” pop-up window browse to the directory where you have transeferred reports/books from the source and select the file and click “Import” Button.

The above step will prompt for Database Connection for the Reports, if the DB connections are already created then select the DB connection for the available list else click on “New Database Connection” button to create a new DB connection for this Report.

Sign up to vote on this title
UsefulNot useful