You are on page 1of 13

Migration of Application

Creation of Database First create a database in SQL Server 2005 for the planning repository. Creating a Planning Application For creating an application you have to open Planning AppWizard whose url is as follows http://localhost:8300/HyperionPlanning/AppWizard.jsp First we need to create a datasource (DSN) via which we shall be making connection between Planning application and its database. After creating data source proceed to create application. After creating application we need to first refresh database so that tables are created in database.

Steps to be followed after Application Creation


After creation of database tables for migration purpose we need to perform certain changes in the tables which are as follows: After application is made go to table HYPSYS_APPLICATION and remove version from the column VERSION

Now note down the SID for the user 50001 from HSP_USERS table in a notepad

Next we need to restore database forcefully with the backup of application repository After you restore the database you need to change the values in tables HSP_OBJECTS by introducing a row with object ID 50001

Details 0f the previous step are as follows: 50001 admin 10/10/2008 19:03 5 3 n 10/10/2008 19:03 0 50001 0 admin null 1 0 7/4/2007 11:14

After this make changes in HSP_USERS table by entering a row by ID 50001 and pasting the stored SID and other details as follows:

50001 native://DN=cn=911,ou=People,dc=css,dc=hyperion,dc=com?USER 4507

After this login to planning and after failure of first attempt a TAB shall emerge by the name MIGRATE press that and your application gets migrated into 9.3.1 version.

Security Export&Import
The next step in our approach would be to export security from existing application to the migrated application and for this we shall be using CSSImportExport utility. Procedure to use the utility is as follows: The Import/Export utility,a standalone, command-line utility, is primarily a tool to manage provisioning by facilitating the bulk-provisioning of user and groups with Hyperion product roles. It allows Hyperion Shared Services Administrators to use an XML or CSV file as the source file to create Native Directory users, groups, and provisioning information. Shared Services Administrators can use the Import/Export utility to export, import, and validate data related to various entities: Users Groups and their relationships Roles and their relationship with other roles User and group provisioning data Delegated lists Internal identities of users and groups defined in Native Directory The utility can be used to export data from all user directories configured with Shared Services but not to import data into external user directories. Hyperion recommends that you run the utility on the computer that hosts Shared Services.

SECTION A: Export Source Shared Services Information with the use of the CSS Import and Export utility.
1) In the Shared Services server machine, find the utility cssimportexport.zip located under: %HYPERION_HOME%\common\utilities\CSSImportExportUtility.

2). Unzip the file named cssimportexport.zip in the current location.

3) Create two folders one called "files" and another called "logs" under the directory of %HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexport 4) Go to the "....CSSImportExportUtility\cssimportexport\importexport\samples" folder of the utility and copy the importexport.properties file to the root folder of the utility, "....CSSImportExportUtility\cssimportexport\importexport".

5) Configure the importexport.properties file: a. Open the file importexport.properties file under the "....CSSImportExportUtility\cssimportexport\importexport" directory. Each option of the file is fully documented. The file contains three sections, Global, Export and Import section. The Global section defines the Shared Services environment that you want to import from or load into. The Export section defines the export options. Import section defines import options.

b. Configure the location of the CSS file. The URL is the best method to define it. Ensure, that the location displays the correct syntax as in: importexport.css=http://SERVERNAME:58080/interop/framework/getCSSConfigFile

c. Configure the Shared Services host and port number as follows: importexport.cmshost=SERVERNAME importexport.cmsport=58080

d. Configure the administrator account that will be used as the default admin account that has all of the Shared Services privileges to export and load: importexport.username=admin

e. Configure the password for the administrator account. The password is typed in clear text but the utility will encrypt the password in the file when you execute the utility. Clear Text importexport.password=Password

f. Configure the location of the trace log. Ensure to define path locations with the use of forward slashes like importexport.trace.events.file=%HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimpo rtexport\importexport\logs\trace.log

g. Configure the location of the error log. importexport.errors.log.file=%HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimporte xport\importexport\logs\errors.log

h. Configure the file format, in the EXPORT section. In this example, csv format will be used. export.fileformat=csv

i. Configure the location of the export file. Ensure to include the file extension. export.file=%HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexp ort\files\export.csv

j. Accept all other options in the file. This will produce a file that you will need in order to move the provisioning information to a target environment.

k. Do not change the User or Group filter values. This will search all external providers and extract all users and groups. This process can be time-consuming. The external users will be displayed with the default options as both members of native groups and if they are directly provisioned to the applications.

l. Save the file as export_source.properties 7) Execute the CSSexport utility. a. Open a command prompt and change the directory location to: %HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexport

b. From the command prompt location set in step G2 type the command: CSSexport export_source.properties Hit Enter and the operation will execute. The time for completion will vary based on the size of the environment.

SECTION B: Prepare the Load File In this step, you will identify the important parts of the file that was exported, export.csv. You can limit the process for the entire environment or for a particular application. A tool that can be used to edit the export.csv can be Microsoft Excel. After completing the necessary modifications to the export.csv, please ensure to rename the file to a different name such as import.csv. #user This is the first section of the file and it contains the native users that are in your environment. You can use this section to create new native users if you like but for the system transfer its focus will be to copy the necessary native users from our source to target system. Below are the most important fields in this section.

FIELD Id

EXAMPLE admin

NOTES This is the username field This defines what provider in the css.xml file the user is stored in. This should always display Native Directory. The login name for the user. Make

Provider

Native Directory

login_name

admin

Internal_id

bd9de0e7ae67869b:66eb093d:1156300bf03:-7ffe

This field represents the internal identifier stored in the Shared Services Openldap repository. This identity matches the SID value stored in the HSP_USERS table of the Planning application's relational repository.

Password

This is the encrypted the password value for the user. {XPA}W8ph4Mn5Qz9JgiXLvPgzG37mj9= You can also type a new clear text password here when creating new users.

If you are not transferring any specific accounts you can remove their lines, you can remove the whole section. I would recommend deleting the admin, and essadmin (default admin account for Hyperion Essbase) lines because those are usually environment specific. #group This section contains the group that are stored in the Native Directory OpenLdap repository. The internal id is also stored in the HSP_GROUPS table in the Hyperion application's relational repository. This section can be very important if your application utilizes group security. FIELD Id EXAMPLE HP_KNGSP_FA-ReadWrite NOTES Group identifier This defines what provider in your css.xml file the group is stored in. The descriptive name of the group. This should be the same value as the ID.

Provider

Native Directory

name

HP_KNGSP_FA-ReadWrite

Internal_id

This field represents the internal identifier of the bd9df0e7ae7695b:4f0cc7a3:22b096aa7344:- group stored in Openldap. 8ff9 This identity matches the identity of the group stored in the HSP_GROUPS table in

the Hyperion Planning application's relational database repository. This section can be edited to remove any groups that you do not want transferred from source to target or you could remove this whole section if you are only using external groups. #group_children When you first export you will have a section for each group defined in #group, it can be combined into one section or left as separate sections. This section will list the users or the groups that belong from each group. Ensure to remove any groups that you do not want to transfer because the users that are listed in this file will overwrite your target system. For example, if you have the same group in both your source and target. Source has 5 users in it and target has 10. When you go to load the group definition it will only have 5 users in it and it will remove the other five. You can add those extra 5 to the file or chose to not load the group definition section. FIELD Id Group_id EXAMPLE HP_MWTSP_AllUsers HP_MWTSP_All Regions NOTES Group Identifier Groupname that belongs to this group The provider the group is stored in. This can be any provider defined in the css.xml file A user that belongs to the group The provider the user is stored in. This can be any provider defined in the css.xml file

group_provider

Native Directory

User_id

bjr10

User_provider

MSAD

#Provisioning Similar to the previous section there will be one definiton for each product-application combination. If you prefer, this section can be combined into a single comprehensive section. When preparing this section for transfer, you will notice that there are certain products that list the server name in it's related provisioning, for example Essbase and BI plus. Hyperion Planning does not use server names, therefore, if the groups and users exist then the import will work fine. The project names and application names must exist in the target environment before loading the file.

FIELD Project_name Application_name

Planning Planning MWTSP

Notes Shared Services project name Planning application name as it appears in Shared Services The provider the group is stored in. This can be any provider defined in the css.xml file. Provisioning level The version of the product. Please do not change this value and use the exported value to prevent any errors.

group_provider

Native Directory

Role_ID

View User

Product_type

HP-9.3.1

The next part of the section has the users and or groups that are provisioned to the application. Ensure to scroll to the right in order to see the full user and group names.

Under the #provisioning section you can remove the projects and associated applications that are not Hyperion Planning applications. Maintain only the Hyperion Planning application names and corresponding projects.

Since this document is only focusing on Hyperion Planning you could only include the Hyperion Planning applications in your load file because it will assign the necessary Essbase and Business Rules access.

SECTION C: Import Target Shared Services Information Before proceeding with the import of the provisioning information to the target environment, ensure that you have created a shell of the Planning application with the same name, plan types and plan type names, multi-currency support options, number of years, starting year, and starting period as the Planning application in the source environment. Also, ensure that the same Project name, which contains the Planning application, exists in the target environment.

In this section, the cssimportexport utility will be used to load are file into the target Shared Services environment. 1) Copy your load file that you prepared in the last section to: %HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexport\files\im port.csv 2)Copy the file %HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexport\export_ source.properties to import_target.properties. 3) Open and edit the GLOBAL section of the import_target.properties file in a text editor such as Notepad. a. The first option to configure is the location of the css.xml file. The web URL is the easiest and most dynamic method to define it. Here is an example of the correct syntax of the target server: importexport.css=http://TARGETSERVER:58080/interop/framework/getCSSConfigFile b. The next part is to define the Shared Services host this will be the same server as your url above. importexport.cmshost=TARGETSERVER Same for the port importexport.cmsport=58080 c. Define an administrator account I would use the default admin account because it has all of the necessary Shared Services provisioning to extract and load importexport.username=admin d. Define the password. You type the password here in clear text and when you run the utility it will encrypt the password in the file. Clear Text importexport.password=Password Encrypted importexport.password={CSS}MRcYv323uzxGr8rFdvQLcA== e. Define the location of the trace log. When defining logs its important to use the Unix slash / convention method, for example:

importexport.trace.events.file=%HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimpo rtexport\importexport\logs\trace.log f. Define the location of the error log. importexport.errors.log.file=%HYPERION_HOME%\common\utilities\CSSImportExportUtility\ cssimportexport\importexport\logs\errors.log 4) Edit the IMPORT section in the import_target.properties file. You can ignore the export section of the file and move directly to import. a. Change import.fileformat=csv the import file format to csv

b. Define the file that you will be using as your load file. This is the file you first copied in the import section. import.file=%HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexp ort\files\import.csv c. Verify that your update option is set to CREATE/UPDATE. This will update the information if it already exists or create the new user or group. import.operation=CREATE / UPDATE

d. Specify a failed import operations file. import.failed.operations.file=%HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimport export\importexport\logs\failed.csv e. Save and close the import_target.properties file. 5) Execute the CSSIMPORT utility. a. Open a windows command prompt and navigate to the following directory: %HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexport b. From the above location set in the windows command prompt, type the command: CSSimport export_target.properties c. Hit enter. d. The import process should execute at this point and the time for completion will vary based on the size of your environment. If there are any errors, please refer to the failed.csv file defined under the %HYPERION_HOME%\common\utilities\CSSImportExportUtility\cssimportexport\importexport\logs directory.