Migrating Security

Migrating an application across different environments is something one must do in any implementation. In the “Migration” series I intend to highlight how each of the key components of an Essbase/Hyperion application need to be migrated.

In this post we’ll discuss the migration of security settings. Hyperion Planning comes with a utility to import and export security settings. This utility is called ImportSecurity.cmd and is found in the %HYPERION_HOME%/Planning/bin folder.

The syntax of the utility is relatively simple

ImportSecurity.cmd “appname,user,password,<delimiter(SL_COMMA/SL_SPACE/SL_COLON/SL_SEMI-COLON)>,<run_silent>,<SL_CLEARALL>”

The other complementary utility is ExportSecurity.cmd found in the same location. The syntax of this utility is

ExportSecurity.cmd /A=appname,/U=username,/P=password, { [/S=searchCriteria] |[[/S_USER=user],[/S_GROUP=group]] |[/S_MEMBER=mem | /S_MEMBER_C=mem | /S_MEMBER_IC=mem|/S_MEMBER_D=mem|/S_MEMBER_ID=mem]}, [/DELIM={delim}] , [/DEBUG=true|false],[/TO_FILE=fileName]
Ex: ExportSecurity.cmd /A=app1,/U=user,/P=password,/S=user

To migrate the security settings follow the following steps:

  1. Make sure the users/groups are created and provisioned in the target environment
  2. Navigate to the folder where you want to store the security export file
  3. Launch %HYPERION_HOME%/Planning/bin/ExportSecurity.cmd /A=<application>,/U=<username>,/P=<password>
  4. If the destination server is not accessible from current environment then copy (or move) the exported security export file to the target environment. Navigate to the folder where the security export file is copied in the target environment
  5. Launch %HYPERION_HOME%/Planning/bin/ImportSecurity.cmd “<application>,<username>,<password>”. Please note that the application name, username and password follow a specific order and are all enclosed with quotation marks.

This is a relatively simple process to migrate security. Please note that you need to have the users/groups created and provisioned if this is being done for the first time.

In a separate post I will discuss how this same method can be used to modify/add security settings to the application using the ImportSecurity.cmd method.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s