Get your environment ready
OpenI assumes you have at least a J2EE server and an OLAP server (that can accept XMLA requests) installed and ready. For J2EE, we have tested OpenI on various versions of Tomcat and JBoss, and for OLAP servers, we have tested on Mondrian 2.4.2/22.214.171.12471/126.96.36.19987, Microsoft Analysis Services (MSAS) 2000, and SQL Server Analysis Services (SSAS) 2005. (Click here
for instructions on setting up OLAP Servers and their XMLA interfaces, and refer here
for a more comprehensive list of system requirements)
- OpenI assumes you have the following roles defined in your J2EE security schema. If you don't have them, add them before you access OpenI
- openi (role to distinguish users who have access to the OpenI web application)
- app_admin (role to distinguish users who have full administrative access to the OpenI web application).
- If you are using tomcat default security, this can be done by editing <tomcat_home>/conf/tomcat-users.xml. If using JBoss default security, you can edit users.properties and roles.properties in <jboss_home>/server/default/conf (if those files are not there, you can create new files). Consult JBoss documentation if you are using a different flavor of security definitions, the bottom line is that OpenI will expect at least one user who belongs to the security roles of openi and app_admin for you to be able to log into OpenI and configure it.
- You may need to restart your J2EE server after changing security configuration.
for further details regarding applicaiton security settings
Download and Deploy the WAR
- If you are deploying on tomcat, download and unzip openi-2.0-RC2-tomcat.zip into an empty folder. If you are deploying on JBoss, or any other J2EE server, download and unzip openi-2.0-RC2-jboss.zip into an empty folder. Click here for the download link.
- Copy the openi.war into the web application deployment folder of your J2EE server . For example, if you are running tomcat as your J2EE server on Linux:
- cp openi.war <tomcat_home>/webapps/
- Similarly, if you are running JBoss as your J2EE server on Linux (assuming "default" configuration):
- cp openi.war <jboss_home>/server/default/deploy
Take a Test Drive, Configure Projects Folder and Deploy Sample Application
- Open browser to: http://localhost:8080/openi
- Log in using the user login you have created that belongs to openi and app_admin security roles (default security assumes you have an administrator login of "openiadmin/passwd" defined in your J2EE security database, and that it belongs to the security groups or roles openi and app_admin. Please see Application Security for security configuration details)
- When you log into OpenI for the first time as an administrator, OpenI will detect that you don't have a "projects folder" (when you create new reports and analyses using OpenI, they need to be stored on a special folder on the OpenI server called the "Projects Folder". A "project" is a collection of analyses belonging to a particular category like a client, or a department, etc., more on projects folder is here). OpenI will offer to create you a default "projects folder" and deploy a the sample "Foodmart 2000" application to this folder.
- OpenI creates this openi-projects folder in the home directory of the user under whose privileges the J2EE server is being run. OpenI does this to ensure that the analyses you create are not in the J2EE server's deployment folders as in the previous versions, which caused issues when users wanted to install a new version of OpenI. To address that, OpenI now assumes that the "project contents", i.e. the folder containing the analyses you create, can be anywhere in the filesystem.
- OpenI uses a properties file called openi.properties to track the location of this openi-projects folder, so at run-time, OpenI expects to find this openi.properties file in the home folder of the user under whose login the J2EE server runs. Normally there is a login called "jboss" for running jboss, and similarly a "tomcat" login for those who are running tomcat -- but this can be different in different configurations. So when you install OpenI for the first time, both the openi-projects folder and openi.properties file will be created by default at the user's home directory ("/home/<username>" on Linux, "c:\Documents and Settings\<username>" on Windows). If you need to run the J2EE server under a different user login other than the one which you used while installing OpenI, you need to make sure openi.properties file is available in that user's home folder.
- If you need to move the openi-projects folder to a different location, you can do that, but you need to make sure you edit the openi.proerties file and set the projects folder attribute to point to the new path location where you have moved openi-projects. Alternately, you can set a system environment variable called PROJECTS_DIR and set it to point to the path where openi-projects is located. This way, OpenI will first look for openi.properties file and if it doesn't find it, it will look for this environment variable to find the openi-projects folder.
- If you have a local Mondrian OLAP Server or a Microsoft SSAS 2005 that contains their default OLAP database (Foodmart 2000), once you have completed the above mentioned steps, you should see a screen of the sample application like this
- If you need to connect to a different OLAP database or connect to an OLAP server on a different machine, you need to configure your OLAP data source definition by going into "Preferences > Data Sources". More details on configuration of data sources are here
Consult the Users Guide
for more information on navigating/configuring the dashboard and the analysis views.