If you are an administrator performing an initial installation of Dodeca at your company, you will need to prepare the relational database store used by Dodeca. The easiest way to assure Dodeca is configured properly is to create and use the sample application that is shipped with the Dodeca Framework. To create the sample application, follow these steps:
- Launch dshell by double-clicking "dshell.cmd" located in "C:\Program Files\Applied OLAP\Dodeca Framework 8.1.4.35\bin"
Type "connect dodeca-hibernate.properties" and hit enter to connect to your Dodeca Repository.
dshell/:>connect dodeca-hibernate.properties
Type "upgrade" and press enter to upgrade the Dodeca schema to the current version.
dshell/:>upgrade
Copy your dodeca.license file to the \bin directory and then import the Dodeca license by typing "import-license dodeca.license"
Create the SAMPLE tenant with the SAMPLE metadata by typing this command:
dshell/:>create-tenant --tenant SAMPLE --file "C:/Program Files/Applied OLAP/Dodeca Framework {version}/metadata/Sample.zip"
Note
By convention, tenant keywords and application IDs are normally expressed in all capital letters with only alphanumeric characters and no spaces.
After creating the tenant, set SAMPLE as the active tenant by using the command:
dshell/:>use SAMPLE
At this point, you have completed the setup of the sample application. To install the application, you will use the ClickOnce URL. List the ClickOnce URLs by typing this command:
dshell/SAMPLE:>list-application-urls --server-address http://servername:port
- Copy the URL into Microsoft Edge and press enter to launch the Dodeca client on your computer and start the ADMIN application. Initially, the 'Launching Application' dialog will display while ClickOnce deployment determines if the Dodeca application has been installed on your desktop.
Note
If you wish to launch Dodeca using a browser other than Internet Explorer, you will need to install a ClickOnce extension/plugin. For Firefox, see the Microsoft .NET Framework Assistant extension. For Chrome, see the third-party ClickOnce for Google Chrome extension.
If the Dodeca application has not yet been run on your desktop, you will see the following installation dialog.
Press the 'Run' button to install and run the Dodeca client.
Note
The 'Publisher' field will reflect the name of the organization who owns the digital signing key. If you used the temporary key provided by Applied OLAP, the 'Publisher' value will be 'Unknown Publisher' (because it is a self-signed key).
The installation will proceed and update its progress in the dialog. The amount of time required to install Dodeca on a client workstation will vary based on your network speed.
Note
This installation occurs only the first time the application is run.
Upon completion of the download/installation, the Dodeca splash screen will be displayed, indicating the startup of the Dodeca Smart Client.
Congratulations! You have successfully launched the Dodeca Smart Client.
- Once in the ADMIN application (assuming you have the Essbase Sample/Basic and Demo/Basic sample databases available), you need to configure the location of your Essbase services. To configure those services, select 'Admin' from the menu, and then select 'Essbase Connections' to open the Essbase Connections metadata editor.
- Select the 'Sample Basic' connection and modify the 'ServletPath' and (Essbase) Server properties to point to the proper location.
- Once you have modified the properties, click the Commit All button to store the changes in the metadata repository on the server.
- Next, test the functionality by opening the 'Adhoc Analysis' view which is configured to use the Sample Basic connection. To open the view, click on the 'Adhoc' category in the View Selector pane to expand open the 'Adhoc' category. Then click on the 'Adhoc Analysis' view to launch it.
- Enter your username and password and press OK. The 'Adhoc Analysis' view will connect to Essbase and bring back the initial retrieve.
Now that you have successfully tested your client and server setup, you can start authoring your own applications. The first thing you will need to do is choose a tenant keyword for use with your application. The tenant key is used to segregate sets of applications within the metadata server. For example, if you intend to implement a forecasting application and a retail merchandise planning system for your company (ABC, Inc.), you may want to use multiple tenant keys to separate the metadata for your different applications. You could, for example, decide to use ABCForecast and ABCMerchPlan for your tenant keys. When you create your applications, the metadata for the application(s) you create will be keyed in the database by each of these values. These applications are completely isolated from each other even if you create and access them using the same Dodeca metadata server.