whitepaper: roambi blink best practices version 1.0

Whitepaper:

Roambi Blink Best Practices Version 1.0

Whitepaper: Roambi Blink Best Practices v1.0

Roambi™, the Roambi™ Logo, MeLLmo™, the MeLLmo™ Logo are trademarks of MeLLmo Inc.

© Copyright 2010. All Rights Reserved.

2

Table of Contents

Whitepaper: ...................................................................................................................................... 1

Roambi Blink Best Practices ...................................................................................................... 1

Version 1.0 ........................................................................................................................................ 1

Introduction ...................................................................................................................................... 3

Specifications .................................................................................................................................. 4

Roambi Blink Detailed Features ................................................................................................ 5 Edit Options ................................................................................................................................................ 5 Browsing Available Dimensions.......................................................................................................... 6 Browsing Available Measures .............................................................................................................. 6 Filters ............................................................................................................................................................ 7 Refinements ................................................................................................................................................ 8

Dimension limit not exceeded........................................................................................................................................8 Dimension limit not exceeded (user imposed reduction) ........................................................................... 10 Dimension limit exceeded ............................................................................................................................................. 11

Roambi Blink Interface ............................................................................................................... 13

Roambi Blink Publishing ........................................................................................................... 14

Example: How-to source OLAP data step-by-step............................................................ 16

Example: How-to use Roambi Blink on the device ........................................................... 25

Appendix A –Roambi Blink current limitations .................................................................. 26 The Roambi Blink View always displays the ALL member for non-time dimensions .... 26 The Publisher doesn’t allow a base time member to be defined ........................................... 26 MSAS server-side sets not supported ............................................................................................. 26 Multiple members selection not supported on filters ................................................................ 26

Appendix B – How-to configure connection to Microsoft MSAS ................................. 28 Configure HTTP Access to SQL Server Analysis Services (2005 or 2008) ......................... 28

Get the required files for IIS virtual directory ..................................................................................................... 28 Create an application pool ............................................................................................................................................ 28 Create an application ....................................................................................................................................................... 28 Setup the application properties ............................................................................................................................... 29 Test your HTTP connection to MSAS .................................................................................................................... 31

Update Roambi-Settings.xml .............................................................................................................. 31

Appendix C – How-to configure connection to Hyperion Essbase ............................. 33 Configure Hyperion Provider Services XMLA............................................................................... 33 Update Roambi-Settings.xml .............................................................................................................. 33

Appendix D – How-to configure publishing to Oracle Hyperion Workspace .......... 34 Hyperion 9.3.x .......................................................................................................................................... 34 Hyperion 11.x ........................................................................................................................................... 35




3

Introduction

Roambi Blink turns data into answers. It gives you the ability to visually explore your company data and answer critical questions – in the blink of an eye, from the palm of your hand.

Fast Roambi Blink gives you "speed-of-thought" response time while easily and intuitively analyzing key business performance metrics on your mobile device. It locally stores a subset of your company data from BI reports or data warehouse cubes on your iPhone or iPad, so you can access and analyze it at lightning-quick speeds – whether or not you are connected to the Internet.

Cube Connectivity Blink is powered by Roambi ES3 enterprise server which connects directly to the cube layer of Oracle Essbase and Microsoft Analysis Services, and allows a subset of these cubes to be sourced and delivered to your iOS device.

Visual Blink automatically transforms these subsets of cubes (mini-cubes) into secure, interactive visualizations that you tap and swipe to make instantaneous iterations and calculations -- enabling quick, convenient on-the-go analysis, right from your iPhone or iPad. Slice your data anyway you choose – to explore and analyze, and answer your business questions.

Multi-dimensional Roambi Blink mini-cubes can have up to 4 viewable dimensions and 6 measures. Other dimensions can be setup as filter dimensions to create a very specific dataset from the source cube. There are no limits in the number of filters used, but each filtered dimension can have only one member selected. Each one of the 4 dimensions can show up to 100 members - but if the dimension is tagged as “time”, the limit is 52 members. If any viewable dimension has more than 100 members, Roambi will allow only one measure to be displayed. During the publishing process, users can select which measure to display and how these members get selected. Users can select the best or worst performers and how Roambi Blink evaluates measure amounts. For example, if looking at an expense measure, low values are usually considered to be good. But if looking at revenue, low values are bad. When time is used as the x-axis, the user will see a vertical bar chart with the amount auto-scaled on the y-axis. When a non-time dimension is used as the x-axis, the user will see a horizontal bar chart with the amount auto-scaled on the y-axis. Users are presented with a histogram-like chart related to the dimension & measure currently in focus.




4

Up to three dimensions not included in the graph can be restricted to a single member including the „All‟ member if included in the report. Users also can:

o Swipe between measures if multiple measures are included o Define the dimension to use as the x-axis o Sort members of a dimension o Request a refreshed report including new data available from the source cube

Specifications

Supported iOS Devices:

iPhone

iPod Touch

iPad Supported Data Sources:

Microsoft Analysis Services 2005

Microsoft Analysis Services 2008

Microsoft Analysis Services 2008 R2

Oracle Hyperion Essbase 9.x (requires Hyperion Provider Services)

Oracle Hyperion Essbase 11.x (requires Hyperion Provider Services)




5

Roambi Blink Detailed Features

The first step in building a Roambi Blink visual analytic is to select a subset of dimensions and measures from the source cube or data source. This process is done in the Roambi Mini Cube Builder. To access the Roambi Mini Cube Builder, simply import a cube from one of the supported data sources. The top left portion of the screen lists all of the dimensions while the bottom left displays all of the measures of the selected cube in a hierarchical tree. Upon import of the cube, the Roambi Mini Cube Builder will pre-populate the selected measures and dimensions using an internal heuristic.

Edit Options

If the user needs to modify which measures or dimensions are included in the mini cube there are two options:

1. Remove each measure and dimension that is not needed in the mini cube by clicking on the small „x‟.

2. Click on the „clear‟ button at the top right-hand part of the screen - which will remove all dimensions, measures and filters. The user can then drag measures and dimensions from the left part of the screen to the right to build their mini cube. Instead of dragging, users can single-click on a measure or dimension to add it to their respective area.

If the dimension names are not indicative of the actual values, simply hover over the dimension to show a sample of the values. This is particularly helpful when the names of the dimensions are vague. Hovering over the dimension will help your construct the desired mini cube.




6

Browsing Available Dimensions

To easily find dimensions users may be looking for, the Roambi Mini Cube Viewer has four different dimension view options, which are listed in the small dropdown at the top right-hand side of the dimension area:

Flat List A-Z

Flat List Z-A

Tree Expanded

Tree Collapsed

In addition to these options, users can also leverage the search capability to find a particular dimension.

Browsing Available Measures

In addition to search, users can sort the list of available measures (either ascending or descending) to easily find the measure(s) they are looking for.




7

Filters

If the user wishes to limit the cube dataset, but does not wish to include a dimension in the actual cube, they can add it to the filter section and pick a single selection. If you add multiple dimensions to the filter section, as you filter one dimension, the available results for the other filtered dimensions will respect your selection if the dimensions are correlated (the Roambi Mini Cube Builder treats each dimension level as a dimension on its own).

Example using Adventure Works: If I add the „Country‟ dimension to the filter section and I choose „United States‟ in the state filter, and then I will only see USA regions when I add „Region‟ as a filter.

But if I change „Country‟ dimension to „Canada‟ Region, filter will be empty.

To search for a value in a dimension, simply type a letter in the search box, hit return and the list will dynamically update to only show the values that meet your criteria. To remove a filter, click on the „x‟.




8

After you've constructed your mini cube, simply click on the „Apply‟ button at the top right-hand part of the screen to proceed to the refinement step of your RBI construction process.

Refinements

Dimension limit not exceeded

Display Options

If none of the display dimensions selected in the cube builder exceeds 100 items, the user can display all results including all measures selected. The „base measure‟ dropdown will default to „None‟ and the remaining options are disabled.

Dimension Options

Users can perform three actions on the dimension options tab:

Rename - click on the dimension name on the right-hand part of the screen and then rename it on the left-hand side

Reorder - on the right-hand side of the page, click and drag dimensions to reorder

Lock Chart Axis - if you don't want your Roambi viewers to change the chart axis, click on the lock icon in the top right portion of the chart




9

Measure Options

On the Measures tab, users can rename measures by clicking on the measure and editing the input text box on the left.




10

Dimension limit not exceeded (user imposed reduction)

Display Options

Even if all dimensions have no more than 100 items, the user can decide to select a base measure and limit the possible number of items for each dimension. Once the user selects a base measure, they will then need to set these options:

Performers - best, worst

Evaluation - high values are good, high values are bad Now the designer can decide to limit dimensions to a particular number. Users can either drag the slider or type a value directly into the input text box just to the left of the slider. The entries that will be returned are based on the base measure and the performers, evaluation settings. Example: A cube has the State dimension, which has 50 entries, but the designer wants to show only the

top 10 states with respect to the Sales measure. Settings:

Base Measure: Sales

Performers: Show Best Performers

Evaluation: High Values are Good

State Dimension: slider set to 10 Notes: Since the user has imposed the limit, they cannot select „none‟ from the base measure dropdown menu to include all measures from their mini cube. Only the selected measure will get published to Roambi Blink.

Time-based dimensions have a maximum of 52 members and non-time ones have a maximum of 100.




11

Dimension Options

Users can perform three actions on the Dimension Options tab:




Measure Options

On the Measure Options tab, users can rename measures by clicking on the measure and editing the input text box to the left. Since a base measure has been selected, the user can only edit the name of that measure.

Dimension limit exceeded

Display Options

One of my dimensions has more than 100 items, which means that the user must select and configure a base measure. By default Roambi Blink will select the first measure. The user will then need to set these options:

Performers - best, worst

Evaluation - high values are good, high values are bad




12

Now the designer can decide to limit dimensions to a particular number between 1 and 100. Users can either drag the slider or type a value directly into the input text box just to the left of the slider. The returned entries are bound to the base measure and the performers, evaluation settings. Time-based dimensions have a maximum of 52 members and non-time dimensions have a maximum of 100.

Dimension Options

Users can perform three actions on the Dimension Options tab:




Measure Options

On the Measure Options tab, users can rename measures by clicking on the measure and editing the input text box to the left. Since a base measure has been selected, the user can only edit the name of that measure.




13

Roambi Blink Interface

Roambi presents the following interface when a user opens a Roambi Blink view:

An end user can perform the following actions:

To view a particular value in a time-based chart (vertical bars) tap and hold on the bar

To view values in a non-time based chart (horizontal bars) tap once on the bars

To view a different measure, swipe the chart left or right

To change a dimension, move the dimension selector to the dimension you'd like to change. All values for that dimension will be displayed in the dimension value selector (bottom chart) sorted in a descending manner. Swipe the bottom chart to change the dimension

To change other dimensions, simply follow the steps in the previous step

To reset a dimension back to „ALL‟, move the dimension selector to that dimension and double-tap the dimension or manually swipe the bottom chart to „ALL‟

To change the chart axis, simply tap on the data icon in the toolbar and select „chart axis‟. You will now see a screen with all of the dimensions in your RBI. Select the one you want to use as your chart axis. Time dimensions on a chart axis will display a vertical bar chart whereas non-time ones will show a horizontal bar chart. Horizontal bar charts sort the bars according to the bar

values in a descending manner.




14

Roambi Blink Publishing

After the mini cube design and refinement phases, the designer faces the last step to have the Roambi Blink view available to the user community. Publishing in Roambi Blink works the same way as in the other views. The most noticeable difference is the designer has to login to another portal to have the Roambi Blink view published. OLAP databases can store cubes but not files. Roambi needs a portal to save any RBI file. Any portal works: BOE InfoView, Hyperion Workspace, Liferay, SharePoint, etc. Depending on the credentials used to source the cube and the ones to connect to the portal some features might not be available. When designers select „Publish‟, they are presented with the „Change Location‟ tab. From there, they can connect to any available portal previously exposed by the Roambi ES Administrator.

If the designer provides to the portal login the same credentials used to design the Roambi Blink view all Publishing Options are enabled.




15

Users can set „Roambi Update‟ to:

None – the data on the view will never refresh

Manual Refresh – users can manually request for new data from the iOS device

Auto Refresh – users get automatic notifications when new data is available for the

view IMPORTANT: If users have different credentials to access the OLAP layer and the Portal them Roambi update is set to none (by design, this cannot change). Also, it is important that the designers have higher access rights than the end users consuming Roambi Blink cubes. Because at publishing time the data selected is based on the permissions of the designer. But when a final user accesses the Roambi Blink cube, Roambi Blink filters the presented data based on the user rights to the cube.




16

Example: How-to source OLAP data step-by-step

1. Open Roambi ES Publisher

2. Select Roambi Blink view




17

3. Select your data source on the left pane. These data sources have to be previously configured in the „roambi-settings.xml‟ file

4. Browse Essbase applications list and select the desired database




18

5. Select how you would like to display your dimensions list. Each Essbase level is what Roambi considers to be a dimension




19




20

6. You can also select how to display the measures list. Either on ascending or descending order

7. Drag and drop the desired dimensions (Essbase levels) and measures from the left pane into the corresponding placeholders on the middle and right panes respectively




21

8. Press the „Apply‟ button on the top right to let Roambi collect the database metadata information. At this point the Roambi Blink view on the right is fully functional which allows the designer to test the mini cube. Bear in mind that only the metadata is real. At this point the phone only displays sample data to make the process as fast as possible

9. You can either publish your report at this point or refine your view




22

10. If any of the display dimensions have more than 100 members, the designer has to define a base measure, performers and evaluation criteria. Only this measure will get published. Otherwise, the designer can manually force any display dimension to have up to a certain member count. In this case all measures get published

11. Under „Dimension Options‟ the designer can change any display dimension name:




23

12. Under „Measures‟ the designer can change measure names. If any of the display dimensions have more than 100 members, the designer will only be able to rename the base measure as this is the only measure that gets published in the end:

13. In the last step, the designer selects the publishing options. ‘Auto Refresh’ can only be selected if the data source and portal credentials are the same:




24

14. Regardless of the data source, Roambi Blink can be published to any Roambi ES supported portal. This includes Business Objects InfoView, Oracle Hyperion Workspace, and Microsoft SharePoint amongst others:




25

Example: How-to use Roambi Blink on the device

When opened, Roambi Blink displays 4 main regions by default on the device:

The top banner presents the current measure name, the last period name on the chart and its amount (the one in yellow in the chart below the top banner)

The blue bar chart presents the data with the time dimension on axis. The yellow bar represents the last period displayed and the one associated with the top banner label and value

The dimension selector appears below and allow users to navigate between dimensions The member selector presents another bar chart that displays the members of the selected dimension ordered by their data values and bound to the last time period (the one in yellow)

Users can easily change the displayed chart by dragging the dimension selector and selecting new members at the very bottom.

By furthering focusing on new dimensions and selecting new members, users can drill down to a problem or opportunity in the mini cube that Roambi Blink view represents. Both the main chart and the member selector chart will respond to these changes.

By clicking the settings button (the right-most one at the bottom), users can change the chart axis if the designer hasn‟t locked it.

When a time dimension is not on the chart, Roambi Blink will display a horizontal bar chart will all members of the x-axis dimension. This chart is also bound to the dimension selectors down below. In this case the numeric label in the top pane represents the amount of the dimension ALL member. Users can toggle between a chart or bare numbers by tapping on the main chart.

When a user rotates the device, the member selector area moves to the right and instead of a chart users are presented with an ordered list of members with each member amount also displayed.




26

Appendix A –Roambi Blink current limitations

These are the limitations with current Roambi Blink version.

The Roambi Blink View always displays the ALL member for non-time dimensions

Some dimensions like Version, Scenario, Time, and Time Intelligence are not supposed to be aggregated. In MSAS the attribute that correspond to the topmost level of a hierarchy has the property „IsAggregatable‟ set to False. Correspondingly Essbase set the dimension name in the outline to be of type „Label Only‟. In the current implementation, Roambi Blink always shows the ALL member for any dimensions except time. In this case the ALL member amount will correspond to:

In MSAS o The attribute dimension default member set by the property „DefaultMember‟; o In case this property isn‟t defined the first member in the dimension

In Essbase o The first member in the dimension

The Publisher doesn’t allow a base time member to be defined

The Mini Cube Builder will consider Roambi Blink base time member to be the one present in the last non-empty intersection for the selected measures and dimensions. The base time member is the last time member that Roambi Blink displays when a user first opens a Roambi Blink view. In Finance-type cubes where a Version or Scenario dimension is present, there can be an issue depending on what the dimension default member (MSAS) is or the order of members in the dimension (MSAS or Essbase). Example:

If ACTUAL is the default member of the Version dimension and Version is one of the 4 add hoc dimensions, users will only be able to see BUDGET data where ACTUAL data exists. This might be OK in some cases, but;

If BUDGET is the default member of the Version dimension, there is BUDGET data ahead in the future and Version is one of the 4 ad hoc dimensions, users might not be able to see ACTUAL data at all or just a small slice of it.

MSAS server-side sets not supported

In the current implementation, Roambi Blink uses an internal heuristic that will select the top 100 best or worst performs per each add hoc dimension. Users aren‟t allowed to select specific members or use server-side defined sets.

Multiple members selection not supported on filters

Roambi Blink only allows a dimension to be filtered by one and only one member. This limitation cannot be bypassed in the current implementation, as Roambi Blink also doesn‟t support calculated members in dimensions other than Measures (MSAS) or Accounts (Essbase).




27




28

Appendix B – How-to configure connection to Microsoft MSAS

Configure HTTP Access to SQL Server Analysis Services (2005 or 2008)

The first step to source data from MSAS is to expose the cubes through an HTTP connection. We need an IIS box and a web application with a custom ISAPI extension that pumps data from the client to an Analysis Services server and back to the client.

Get the required files for IIS virtual directory

Copy the contents of %SQL Server Installation folder%\OLAP\bin\ISAPI directory into the folder you would like to become the base for the virtual directory in IIS. To take advantage of the full set of security settings, it is important to guarantee that the folder that will be the base for the virtual directory is located on an NTFS-formatted drive. Due to IIS limitations, the path to your directory should not contain spaces. If you are planning to run the HTTP pump on a different server than the Analysis Services server, also make sure that you have OLEDB for Analysis Redistributable package installed.

Create an application pool

Open IIS Manager, right-click „Application Pools‟ and select „Add Application Pool‟. Name your application pool and select „.NET 2.0 Framework‟ and „Classic‟ pipeline mode.

Create an application

Open IIS Manager, expand „Sites‟, right-click „Default Web Site‟ and select „Add Application‟. Give an Alias to your application, select the previously created application pool and point the physical path to the folder created on the very first step.




29

Setup the application properties

Open IIS Manager, expand „Sites‟, expand „Default Web Site‟ and click on the recently created application. On the middle pane, double-click „Handler Mappings‟ and click „Edit Feature Permissions‟ on the right. Make sure both „Read‟ and „Script‟ are selected.

http://bloggingabout.net/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/mglaser/httpasws






30

Also on the right pane (action pane), click „Add Script Map‟. Enter „*.dll‟ in the „Request path‟ text box and the path to MSAS pump DLL in your virtual directory. Name this script map (OLAP in screenshot below).

When you press OK, „IIS Manager‟ will prompt you if you wish to enable ISAPI extensions. Click „Yes‟ to enable it and it will automatically add this extension to the allowable list.

Security Settings

On the middle pane, double-click „Authentication‟ and only enable „Windows Authentication‟.




31

Pump Settings

Open the file „msmdpump.ini‟ from the directory you created on the very first step. Change the <ServerName> tag to point to your MSAS box.

Test your HTTP connection to MSAS

Open „SQL Management Studio‟ and try to connect to your recently created HTTP application. Use http://IIS_SERVER_NAME/IIS_APPLICATION_NAME/msmdpump.dll where:

IIS_SERVER_NAME = name of the server hosting the web application

IIS_APPLICATION_NAME = name of your web application

Update Roambi-Settings.xml

Open WEB-INF\Roambi-settings.xml from Roambi deployment folder and create a new connection to your recently MSAS HTTP access created on previous step. The connection entry looks like: <repository> <name>MSAS OLAP Server</name> <id>MSAS OLAP Server</id> <description>MSAS OLAP Server</description> <type>com.mellmo.roambi.portal.plugins.xmla.XmlaContentSourceFactory</type> <params> <param name=„server_url‟>

http://IIS_SERVER_NAME/IIS_APPLICATION_NAME/msmdpump.dll </param>

<param name=„server_type‟>SSAS</param>

http://iis_server_name/IIS_APPLICATION_NAME/msmdpump.dll

http://iis_server_name/IIS_APPLICATION_NAME/msmdpump.dll





32

<param name=„nt_domain‟>DOMAIN</param> </params> </repository>




33

Appendix C – How-to configure connection to Hyperion Essbase

Configure Hyperion Provider Services XMLA

The Roambi ES Essbase connector relies on XMLA for connectivity. Any XMLA connection against an Essbase cube goes through Oracle Hyperion Essbase Services Provider. To guarantee that a connection against an Essbase server will be successful at least 2 services must be running:

Oracle Essbase Server

Oracle Hyperion Essbase Provider Services Oracle HPS receives XMLA requests and translates them to Essbase API calls.

Update Roambi-Settings.xml

Open WEB-INF\Roambi-settings.xml from the Roambi deployment folder and create a new connection to your Oracle Hyperion Provider Services. Usually HPS runs on port 13080. If this is not the case, make sure you change the port number below. The connection entry should look like: <repository> <name>Essbase OLAP Server</name> <id>Essbase OLAP Server</id> <description>Essbase OLAP Server</description> <type>com.mellmo.roambi.portal.plugins.xmla.XmlaContentSourceFactory</type> <params> <param name=„server_url‟>

http://HPS_SERVER_NAME:13080/aps/XMLA </param>

<param name=„server_type‟>ESSBASE</param> </params> </repository> A quick way to check if Hyperion Provider Services is up and running is to type its URL on a browser. If you get a „page not found‟ message, check the following:

Is server name correct?

Is server port correct?

Is the service running?

http://hps_server_name:13080/aps/XMLA




34

Appendix D – How-to configure publishing to Oracle Hyperion Workspace

As neither Oracle Hyperion Essbase nor Microsoft Analysis Services can host Roambi Blink views (they are not portals at all but OLAP databases) a very common scenario is to publish Oracle Hyperion Essbase based Roambi Blink views to Oracle Hyperion Workspace portal. This appendix presents the required steps to configure Roambi ES server against either Hyperion Workspace 9 or Hyperion Workspace 11. At this point Roambi ES doesn‟t support publishing to both versions at the same time. In this case a second Roambi ES instance is required as Hyperion 9 and 11 jar files conflict with each other.

Hyperion 9.3.x

1. On Roambi ES server create the following folders:

a. C:\HYPERION b. C:\HYPERION\BIPLUS c. C:\HYPERION\BIPLUS\LIB d. C:\HYPERION\BIPLUS\LIB\MSGS e. C:\HYPERION\BIPLUS\SDK f. C:\HYPERION\BIPLUS\SDK\ETC g. C:\HYPERION\BIPLUS\SDK\ETC\LOG4J h. C:\HYPERION\BIPLUS\SDK\MSGS

2. On Roambi ES server create this system variable: a. HYPERION_HOME = C:\HYPERION

3. Update CLASSPATH system variable with the following entries (Obs.: In Windows if running Tomcat as a service this has to be done in Tomcat Configurator):

a. C:\HYPERION\BIPLUS\SDK b. C:\HYPERION\BIPLUS\SDK\ETC\LOG4J c. C:\HYPERION\BIPLUS\LIB

4. From Hyperion 9.3.x server copy the following files to Roambi ES lib folder: a. %HYPERION_HOME%\BIPLUS\LIB:

i. Clientservlet.jar ii. Comutil1_01.jar iii. Foundation.jar iv. Iona63.jar v. Jecf.jar vi. Logi.crypto1.1.2.jar

vii. Sfc.jar viii. Spf.jar

ix. Symbeans.jar b. %HYPERION_HOME%\BIPLUS\SDK\LIB:

i. Rmapi.jar

c. %HYPERION_HOME%\COMMON\CSS\9.3.1\LIB: i. Css-9_3_1.jar

ii. Ldapbp.jar

5. From Hyperion 9.3.x server copy the following files to Roambi ES respective folders created on step 1:

a. C:\HYPERION\BIPLUS\LIB\DEFAULT-DOMAIN.CFG




35

b. C:\HYPERION\BIPLUS\LIB\MSGS\* c. C:\HYPERION\BIPLUS\SDK\ETC\LOG4J\SDKLOG4JCONFIG.XML d. C:\HYPERION\BIPLUS\SDK\MSGS\*

6. On Roambi ES server edit C:\HYPERION\BIPLUS\SDK\ETC\LOG4J\SDKLOG4JCONFIG.XML and replace ${directory}/log/sdk.log with ${directory}/logs/sdk.log

Hyperion 11.x

1. On Roambi ES server create the following folders: 2.

a. C:\HYPERION b. C:\HYPERION\PRODUCTS c. C:\HYPERION\PRODUCTS\FOUNDATION d. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE e. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\LIB f. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\LIB\MSGS g. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK h. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK\ETC i. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK\ETC\LOG4J j. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK\MSGS

3. On Roambi ES server create this system variable: a. HYPERION_HOME = C:\HYPERION

4. Update CLASSPATH system variable with the following entries (Obs.: In Windows if running Tomcat as a service this has to be done in Tomcat Configurator):

a. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK b. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK\ETC\LOG4J c. C:\HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\LIB

5. From Hyperion 11.x server copy the following files to Roambi ES lib folder: a. %HYPERION_HOME%\COMMON\CONFIG\9.5.0.0\LIB:

i. Registry-api.jar b. %HYPERION_HOME%\COMMON\CSS\9.5.0.0\LIB:

i. Css-9_5_0.jar ii. Ldapbp.jar

c. %HYPERION_HOME%\COMMON\JDBC\DATADIRECT\3.7\LIB: i. Hyjdbc.jar

d. %HYPERION_HOME%\COMMON\SHAREDSERVICES\9.5.0.0\LIB: i. Audit-client.jar ii. Xmlrpc-2.0.1.jar

e. %HYPERION_HOME%\PRODUCTS\FOUNDATION\WORKSPACE\LIB: i. Comutil1_01.jar

ii. Foundation.jar iii. Iona63.jar iv. Logi.crypto1.1.2.jar

f. %HYPERION_HOME%\PRODUCTS\FOUNDATION\WORKSPACE\SDK\LIB: i. Rmapi.jar




36

6. From Hyperion 11.x server copy the following files to Roambi ES respective folders created on step 1:

a. C:\ HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\LIB\DEFAULT-DOMAIN.CFG

b. C:\ HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\LIB\MSGS\* c. C:\ HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK

\ETC\LOG4J\SDKLOG4JCONFIG.XML d. C:\ HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK \MSGS\*

7. On Roambi ES server edit C:\ HYPERION\PRODUCTS\FOUNDATION\WORKSPACE\SDK\ETC\LOG4J\SDKLOG4JCONFIG.XML and replace ${directory}/log/sdk.log with ${directory}/logs/sdk.log

whitepaper: roambi blink best practices version 1.0

Documents