By TopDown Team
August 13th, 2014
In the first part of this blog series, we’ll learn how to create a DRM application. In subsequent posts, we’ll configure this application with the intent of managing & loading metadata for Essbase.
I’d like to recognize Steve Davis, TopDown Consulting Principal Architect. Steve has mentored me in the ways of DRM and was also kind enough to review these blog posts prior to them going live, many thanks!
The environment used for this series is a Windows Server 2008 R2 Standard virtual machine running SQL Server 2008 R2. Essbase is version 126.96.36.199, and DRM is version 188.8.131.52.
The DRM Footprint
DRM is not currently part of the Oracle EPM System Installer, but rather has a stand-alone installer (setup.exe).
Once installed, you can locate the result of the installation by navigating to…
Start -> All Programs -> Oracle EPM System -> Data Relationship Management
The Migration Utility and Web Client are both web-based applications. The Migration Utility is used to load and extract metadata to and from DRM applications. In the next section, we’ll use the Migration Utility to load some properties for Essbase. The Web Client is the primary interface for all DRM-related objects including imports, exports, properties, queries, action scripts, etc. This is where we’ll be spending most of our time.
The Configuration Console
To begin, open the Configuration Console, we are going to create a new application.
If the DRM service is not already running, click Start Service.
To create a new application, click Add.
A default name will appear in the application field, “APHRODITE-1” in this case. It follows the convention of <servername>-<application sequence>. For example, if I kept this default name and then created another application it would be populated with “APHRODITE-2”.
First, give your application a name. I chose “Sample” because I am going to reverse engineer the Sample.Basic database that comes packaged with Essbase.
Click Save Configuration to save the application name to the DRM configuration file.
Now we need to create the relational repository for this new application.
Click on the Repository Wizard button.
The option to Create a new repository should be selected by default; click Next.
If you do not have access to your database, use the option to Generate SQL scripts and then send the resulting code to your DBA.
Select the Database Provider. I have SQL Server running on this machine, Oracle is also supported. Please see the Oracle Supported Platform Matrix for all compatible versions.
I’ve left the Service Connection field blank as SQL Server is running locally on this machine. If your instance of SQL is running on a remote server, enter the appropriate connection string into this field.
Enter the User ID and Password for a SQL account with enough permission to create a new database.
You can click Test Connection to make sure your service connection, User ID, and Password are all entered correctly.
The User Id was already populated with “DRM_DB”, but I chose the password. This is the schema owner in the database, so if you have multiple applications, you will need to make these unique. If there is already another DRM_DB, you will need to change this to something else.
For the database name, I’ve been following the naming convention for DRM applications of “EPM_DRM_<name of app>”. This database does not currently exist; the repository wizard will create it.
The paths in the data file and log file sections were wrong for my machine by default so I had to update those (this will depend on how your MS SQL server was set up). Verify the path exists prior to moving forward because if it does not, the process will error out and you will have to start over.
The user name will be populated by default with “ADMIN”, leave that as is.
Chose a password for the admin user and make sure not to misplace it. The admin user will be used to create accounts for the other users.
This screen is confirming the settings you’ve entered.
If everything is correct, click Next to execute the repository creation.
This screen is displaying the results of the repository creation. You can see that this process finished successfully. However, the first time I ran this the paths for the SQL Server log files did not exist so the process returned an error and I had to start over.
If you wish, you can save the log of the repository creation, or just click Finish.
Now we’re back to the home screen of the Configuration Console.
You can see that the database information including the Database Provider, User Id, and Password have been populated for us.
Click on Test Connection to verify all settings.
Everything looks good so we can Save Configuration.
Now we’re going to verify the application by starting it and then logging in through the Web Client.
Right-click on your newly created application and then click Start Application.
The application icon should change from…
Finally, open the Web Client as our final confirmation of the application.
If you don’t have the bookmark saved, you can open through the Start menu.
Internet Explorer is supported, but we’ve found Google Chrome to be more responsive.
Enter “admin” for the User Name, the Password you chose for this root user, and make sure to select your new Application from the drop down.
Click Log On.
The application has started normally and opened to the Browse section of the Web Client.
In the next post, we are going to use the Migration Utility to build some properties for managing our Essbase member settings.