Pentaho Business Intelligence Suite 3.7 A guide to getting started with Oracle 10g and 11g and Linux

Pentaho Business Intelligence Suite 3.7A guide to getting started with Oracle 10g and 11g and Linux

Table of Contents1. Table of Contents 2. Introduction 1. License 2. Donate 3. You can donate to my PayPal account by clicking here. 4. About 5. The Community 6. Thanks 3. Getting Started 1. Installing and Configuring Java 2. Deploying the Platform 1. Packaged Apache-Tomcat Server 2. Existing Apache-Tomcat Server 1. webapps 3. Oracle JDBC Thin Client Driver 4. SQL Script Pack 4. Configuring the Databases 1. Extract the Oracle 10g or 11g SQL Script Pack 2. Modify SQL Script Pack 1. 1_create_repository_ora.sql 2. 2_create_quartz_ora.sql 3. 3_load_sample_users_ora.sql 3. Load the SQL scripts 5. Configuring JDBC Security 1. applicationContext-spring-security-jdbc.xml 2. applicationContext-spring-security-hibernate.properties 3. hibernate-settings.xml 4. oracle10g.hibernate.cfg.xml 6. Configuring Hibernate and Quartz 1. context.xml 2. quartz.properties 7. Configuring Apache-Tomcat Server 1. solution-path 2. fully-qualified-server-url 3. Disable HSQL Database Startup 4. TrustedIpAddrs 5. Other Parameters 8. Configuring SMTP (mail server) 9. Configuring Publishing 10. Configuring the Administration Console 11. Starting the Business Intelligence Platform 12. Starting the Administration Console

IntroductionLicenseThis work is licensed under a Creative Commons Attribution 3.0 Australia License.

DonateThis tutorial is accessed by thousands on a monthly basis, from most of the feedback many found it extremely helpful! But contrary to belief I do not work for Pentaho and all of this work is voluntary, so even $1 can help me with producing bigger and better tutorials! You can donate to my PayPal account by clicking here.

AboutTo use this guide It is assumed that readers have intermediate to advanced knowledge in their setup of choice and basic knowledge of Pentaho (although it is not needed). The following operating systems and databases are supported:

Windows o MySQL 5.x o PostgreSQL 8.x.x o Oracle 10g & 11g Linux * o MySQL 5.x o PostgreSQL 8.x.x o Oracle 10g & 11g *

* This tutorial is for Linux and Oracle 10g or 11g setup.

The CommunityDon't forget about the other hardworking projects which are part of the Pentaho community and also deserve a donation: PAT (Pentaho Analysis Tool) An alternative to Pentaho's current OLAP analyser tool, JPivot. CDF (Community Dashboard Framework) A framework for building dashboards within Pentaho's Business Intelligence Server User Console. CBF (Community Build Framework) Is an ant build.xml file script and alternate way to setup and deploy Pentaho based applications CDA (Community Data Access) A data access layer for CDF (Community Dashboard Framework).

ThanksThanks to the following blogs, individuals, companies and groups: ##pentaho & ##pentaho.pat IRC channels found on Freenode (Pentaho and Pentaho PAT). Pentaho Wiki & Pentaho Forums The first place any new user to Pentaho should look. Open Source Business Intelligence Provided a working copy of the sample database for MySQL. Bizcubed Provided a working copy of the sample database for PostgreSQL - they are also Australian! Pentaho Solutions: Business Intelligence and Data Warehousing with Pentaho and MySQL A book by Roland and Jos van Dongen.

Getting StartedInstalling and Configuring JavaThe Pentaho BI Platform requires a JVM (Java Virtual Machine) to be installed on your PC or server. To check if Java is already installed issue the following command (seen in bold) at the terminal prompt:

user@terminal:~# java -version java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing) If a similar output (seen above) is displayed Java is already installed. If not, to install Java on Linux issue the following commands (seen in bold):

Ubuntu user@terminal:~# sudo apt-get install sun-java6-jdk sun-java6-jre Fedora user@terminal:~# sudo su install sun-java6-jdk sun-java6-jre The next step is to check if the JAVA_HOME environment variable is setup correctly, issue the following command (seen in bold) at the terminal prompt:

user@terminal:~# echo $JAVA_HOME /usr/lib/jvm/java-6-sun If a similar output (seen above) is displayed the JAVA_HOME environment variable is already setup. To setup the JAVA_HOME environment variable add this line to the bottom of the /etc/environment file:

JAVA_HOME="/usr/lib/jvm/java-6-sun"

The CATALINA_OPTS environment variable should also be set to tell the Apache-Tomcat server to use more than the default memory, to do this also add the following line to the bottom of the /etc/environment file:

CATALINA_OPTS="-Xms256m -Xmx768m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" From now on every time the PC or server is started/restarted the JAVA_HOME and CATALINA_OPTS environment variables will be set automatically.

Deploying the PlatformYou are able to deploy the platform in many different ways but in this guide I will explain how to deploy it with the packaged Apache-Tomcat server (comes with the Pentaho BI Server installation file) or with an existing ApacheTomcat server.

Packaged Apache-Tomcat ServerYou will need to first download the pentaho-ce-3.7.x.stable.tar.gz file from the Pentaho Sourceforge projects page - this file contains all the files/packages needed for setting up our platform. After downloading extract its contents into a directory you would like to store the Pentaho BI Server - in this example I have chosen /opt/pentaho/. To extract the file and move it the /opt/pentaho/ directory issue the following commands (seen in bold) at the terminal prompt:

user@terminal:/home/pentaho/tmp/# user@terminal:/home/pentaho/tmp/# user@terminal:/home/pentaho/tmp/# user@terminal:/home/pentaho/tmp/#

sudo sudo sudo sudo

tar xvzf pentaho-ce-3.7.0.stable.tar.gz mkdir /opt/pentaho mv ./biserver-ce /opt/pentaho mv ./administration-console /opt/pentaho

The following directories should be visible after you have extracted the TAR file and moved its contents:

opt/ |-- pentaho | |-- adminstration-console | |-- biserver-ce

Existing Apache-Tomcat ServerIf you would like to deploy the Pentaho BI Platform on an existing Apache-Tomcat server first extract the contents of the pentaho-ce-3.7.x.stable.tar.gz file found on the Pentaho Sourceforge projects page. After downloading extract its contents into a directory you would like to store the Pentaho BI Server - in this example I have chosen /opt/pentaho/. To extract the file and move it the /opt/pentaho/ directory issue the following commands (seen in bold) at the terminal prompt:

user@terminal:/home/pentaho/tmp/# sudo tar xvzf pentaho-ce-3.7.0.stable.tar.gz user@terminal:/home/pentaho/tmp/# sudo mkdir /opt/pentaho user@terminal:/home/pentaho/tmp/# sudo mv ./biserver-ce /opt/pentaho

user@terminal:/home/pentaho/tmp/# sudo mv ./administration-console /opt/pentaho The following directories should be visible after you have extracted the TAR file and moved its contents:

opt/ |-- pentaho | |-- adminstration-console | |-- biserver-ce | |-- pentaho-solutions | |-- tomcat | |-- webapps | `-- pentaho | `-- pentaho-styles | `-- sw-styles The directories in bold (seen above) will need to be moved to your existing Apache-Tomcat installation. webapps You will need to copy all the directories under the /opt/pentaho/biserver-ce/tomcat/webapps/ directory to the webapps/ directory under your existing Apache-Tomcat installation. To do so make sure you have stopped your Apache-Tomcat server then issue the following command (in bold) at the terminal prompt: Ubuntu user@terminal:~#/ sudo cp /opt/pentaho/biserver-ce/tomcat/webapps /opt/tomcat/ Fedora user@terminal:~#/ su cp /opt/pentaho/biserver-ce/tomcat/webapps /opt/tomcat/ Where /opt/tomcat/webapps/ is the location of your Apache-Tomcat webapps directory. You have just moved all the webapps which are needed by the Pentaho BI Platform (sw-styles is optional). The last step is to move the pentaho-solutions directory into the /pentaho/ directory or any other location which you would like to store all your pentaho solutions and configuration files. To move the pentaho-solutions folder to the pentaho directory issue the following command (in bold) at the terminal prompt:

Ubuntu user@terminal:~#/ sudo mv /opt/pentaho/biserver-ce/pentaho-solutions /opt/pentaho/ Fedora user@terminal:~#/ su mv /opt/pentaho/biserver-ce/pentaho-solutions /opt/pentaho/ One more step will need to be done to make sure Pentaho knows the new location of the pentaho-solutions directory which will be covered in the "Configuring Apache-Tomcat" section. The new structure of the pentaho-solutions and existing Apache-Tomcat directory looks like this:

opt/ | |-- pentaho | `-- pentaho-solutions | |-- tomcat | `-- webapps

You can now safely remove any other files that came with the original Pentaho BI Platform (only under the biserver-ce\ folder).

Oracle JDBC Thin Client DriverYou will need to download the Oracle JDBC Thin Client JAR file. There are many different types available from the Oracle website depending on your setup (In this guide I was using the ojdbc14.jar which worked with Oracle XE and 11g).

IMPORTANT Make sure if you are using Oracle 10.x.x.x that you get the appropriate ojdbc14.jar file from the Oracle website the ojdbc14.jar that I used will not necessarily work with your Oracle 10.x.x.x version.

Once you have downloaded the JDBC Thin Client driver issue the following commands at the terminal prompt to copy it to both the Apache-Tomcat and Administration Console folders:

Ubuntu user@terminal:~#/ sudo mv [oracle_jdbc_client] /tomcat/common/lib user@terminal:~#/ sudo mv [oracle_jdbc_client] /administration-console/jdbc/ Fedora user@terminal:~#/ su mv [oracle_jdbc_client] /tomcat/common/lib user@terminal:~#/ su mv [oracle_jdbc_client] /administration-console/jdbc/

SQL Script PackA SQL Script Pack is a set off SQL scripts which will configure all the necessary databases. To download the SQL Script Pack for Oracle 10g or 11g click here.

Configuring the DatabasesExtract the Oracle 10g or 11g SQL Script PackAfter downloading the SQL Script Pack for Oracle 10g or 11g you will need to extract the files into a temporary location. These are the five SQL scripts which should be visible after the pack has been extracted:

1_create_repository_oracle.sql Creates the Hibernate database 2_create_quartz_oracle.sql Creates the Quartz database 3_load_sample_users_oracle.sql Creates all the sample users and roles into the Hibernate database NOTE There is no working sample data SQL script available for Oracle, if you have been successful in porting it please let me know!

You must load the above scripts in the order they are listed. Load these SQL scripts using the Oracle sqlplus console.

Modify SQL Script PackBefore you can load these SQL scripts you will need to make some small modifications. Below I have created sections for each SQL script which needs changes and what these changes are.

1_create_repository_ora.sqlOnce you have opened this file locate this section of code:

conn hibuser/password@[TNS]; You will need to add the TNS or host you are trying to connect the hibuser user to, in my example that is ORCL_JUPITER.

conn hibuser/password@ORCL_JUPITER;

2_create_quartz_ora.sqlOnce you have opened this file locate this section of code:

conn quartz/password@[TNS]; You will need to add the TNS or host you are trying to connect the quartz user to, in my example that is ORCL_JUPITER. conn quartz/password@ORCL_JUPITER;

3_load_sample_users_ora.sqlOnce you have opened this file locate tis section of code:

conn hibuser/password@[TNS]; You will need to add the TNS or host you are trying to connect the hibuser user to, in my example that is ORCL_JUPITER.

conn hibuser/password@[ORCL_JUPITER];

Load the SQL scriptsBefore you start make sure that you place all your SQL scripts in the directory which you will be logging into sqlplus, in this example that is /home/pgraju/tmp/. The next step is to issue the following commands at the terminal prompt one after the other (in the example below the user JUPITER_DBA has DBA access to the TNS ORCL_JUPITER):

NOTE Replace JUPITER_DBA with your user who has DBA access and ORCL_JUPITER with your Oracle database TNS or host.

root@terminal:/opt/pentaho/# sqlplus JUPITER_DBA@ORCL_JUPITER@1_create_repository_ora.sql SQL*Plus: Release 9.2.0.1.0 - Production on Thu Jan 7 11:04:30 2010 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Enter password: ...output SQL> exit root@terminal:/opt/pentaho/# sqlplus JUPITER_DBA@ORCL_JUPITER @2_create_quartz_ora.sql SQL*Plus: Release 9.2.0.1.0 - Production on Thu Jan 7 11:04:30 2010 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Enter password: ...output SQL> exit root@terminal:/opt/pentaho/# sqlplus JUPITER_DBA@ORCL_JUPITER@3_load_sample_users_ora.sql; SQL*Plus: Release 9.2.0.1.0 - Production on Thu Jan 7 11:04:30 2010 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Enter password: ...output SQL> exit To check if you have succesfully created the hibernate tables login under the hibuser user and issue the commands seen in bold below (replace ORCL_JUPITER with your TNS or host):

root@terminal:/opt/pentaho/# sqlplus hibuser/password@[ORCL_JUPITER]; SQL*Plus: Release 9.2.0.1.0 - Production on Thu Jan 7 11:04:30 2010 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. SQL> select TABLE_NAME from tabs; TABLE_NAME -----------------------------DATASOURCE GRANTED_AUTHORITIES AUTHORITIES USERS To check if you have succesfully created the quartz tables login under the quartz user and the commands seen in bold below (replace ORCL_JUPITER with your TNS or host):

root@terminal:/opt/pentaho/# sqlplus quartz/password@[ORCL_JUPITER]; SQL*Plus: Release 9.2.0.1.0 - Production on Thu Jan 7 11:04:30 2010 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. SQL> select TABLE_NAME from tabs; TABLE_NAME -----------------------------QRTZ_JOB_DETAILS QRTZ_JOB_LISTENERS QRTZ_TRIGGERS QRTZ_SIMPLE_TRIGGERS QRTZ_CRON_TRIGGERS

QRTZ_BLOB_TRIGGERS QRTZ_TRIGGER_LISTENERS QRTZ_CALENDARS QRTZ_PAUSED_TRIGGER_GRPS QRTZ_FIRED_TRIGGERS QRTZ_SCHEDULER_STATE TABLE_NAME -----------------------------QRTZ_LOCKS* Hibernate will create new tables into the hibernate database after Pentaho BI Platform has started for the first time.

Configuring JDBC SecurityThis section describes how to configure the Pentaho BI Platform JDBC security to use a Oracle server, this means the Pentaho BI Platform will now point to the hibernate database on the Oracle server instead of the packaged HSQL database.

NOTE If you already have a user which you prefer to have access to the hibernate database instead of the default user hibuser, you will need to modify all occurances of hibuser/password in this section.

applicationContext-spring-security-jdbc.xmlThis file is located under the pentaho-solutions/system/ directory. Once the file has opened locate this snippet of code:

Make changes to the highlighted sections so that the section of code looks similar to this: NOTE

Here is a brief description of the url value property: jdbc:oracle:thin:[host]:[port]:[sid] o In this example I have used an IP address of my Oracle 10g database for my host, you would most likely have a host setup in your tns.ora file already. o The port which your Oracle 10g database runs on. o The SID of your Oracle 10g database, in this example it is ORCL.

applicationContext-spring-security-hibernate.propertiesThis file is located under the pentaho-solutions/system/ directory. Once the file has opened locate this snippet of code: jdbc.driver=org.hsqldb.jdbcDriver jdbc.url=jdbc:hsqldb:hsql://localhost:9001/hibernate jdbc.username=hibuser jdbc.password=password hibernate.dialect=org.hibernate.dialect.HSQLDialect Make changes to the highlighted sections so that the section of code looks similar to this: jdbc.driver=oracle.jdbc.driver.OracleDriver jdbc.url=jdbc:oracle:thin:@161.117.117.182:1521:ORCL jdbc.username=hibuser jdbc.password=password hibernate.dialect=org.hibernate.dialect.Oracle10gDialect

hibernate-settings.xmlThis file is located under the pentaho-solutions/system/hibernate/ directory. Once the file has opened locate this snippet of code: system/hibernate/hsql.hibernate.cfg.xml Make changes to the highlighted section so that the section of code looks similar to this: system/hibernate/oracle10g.hibernate.cfg.xml

oracle10g.hibernate.cfg.xmlThis file is located under the pentaho-solutions/system/hibernate/ directory. Once the file has opened locate this snippet of code: jdbc:oracle:thin:@localhost:1521:pentaho Make changes to the highlighted section so that the section of code looks similar to this: jdbc:oracle:thin:@161.117.117.182:1521:ORCL

Configuring Hibernate and QuartzHibernate and Quartz need to specifically use the hibernate and quartz databases which were created on the Oracle server. To do so modifications need to be made to the context.xml file which is located in the

/tomcat/webapps/pentaho/META-INF/ directory.

NOTE If you already have a user which you prefer to have access the hibernate database instead of the default user hibuser, you will need to modify all occurances of hibuser/password in this section.This also applies to the pentaho_user/password used to connect to the Quartz database.

context.xmlOnce the file has opened the following piece of code should be visible: Make changes to the highlighted sections so that the section of code looks similar to this:

quartz.propertiesAn extra change that needs to be done to get Oracle 10g or 11g working with Quartz is to open the quartz.properties file which located under the /pentaho-solutions/system/quartz/ directory. Locate the following snippet of code:

org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.StdJDBCDelegate Make changes to the highlighted section so that the section of code looks similar to this (in bold): org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.oracle.OracleDelegate

Configuring Apache-Tomcat ServerTo configure the settings of the Apache-Tomcat server for your Pentaho BI Platform most of the changes are done inside the web.xml file which is located under the /tomcat/webapps/pentaho/WEB_INF/ directory. You are able to configure the following items (and more) for the Pentaho BI Platform:

pentaho-solutions location URL Disable HSQL database startup TrustedIpAddrs (optional - for the administration console and if you are accessing the server remotely)

If you are happy with the following settings for your Pentaho BI Platform server you will not need to make any changes to this file:

pentaho-solutions/ directory located under the /opt/biserver-ce/ directory Visit http://localhost:8080/pentaho URL to launch the Pentaho BI Platform

solution-pathThe solution-path parameter lets the Pentaho BI Platform know where to locate the pentaho-solutions directory. By default this is set to /opt/biserver-ce/pentaho/ directory.

If you have decided to use an existing Apache-Tomcat server (or have moved your pentaho-solutions directory) you will need to point this to where you have placed your pentaho-solutions directory. In this example my pentaho-solutions directory is under the /opt/pentaho/ directory, now my solution-path code snippet looks like this:

solution-path /opt/pentaho/pentaho-solutions/

fully-qualified-server-urlIf you are happy with visiting the URL http://localhost:8080/pentaho to access Pentaho's BI Platform you will not need to change this parameter, however if you would like others to access the site (remotely or on a network) you will need to make changes to this parameter.

Open up the file and locate this line of code: http://localhost:8080/pentaho/ Make changes to the highlighted section to your PC or server's domain or IP address so it looks similar to this:

http://www.prashantraju.com:8080/pentaho/ or http://192.168.1.10:8080/pentaho/

Disable HSQL Database StartupBy default with 3.7 HSQL database starts up automatically - to prevent this from happening locate the following snippets of code: hsqldb-databases sampledata@../../data/hsqldb/sampledata,hibernate@../../data/hsqldb/hibernate ,quartz@../../data/hsqldb/quartz org.pentaho.platform.web.http.context.Hsqldb StartupListener You can either remove the above snippets or comment it out, if you are commenting it out it will look similar to this: hsqldb-databases sampledata@../../data/hsqldb/sampledata,hibernate@../../data/hsqldb/hibernate ,quartz@../../data/hsqldb/quartz org.pentaho.platform.web.http.context.Hsqldb StartupListener -->

TrustedIpAddrsIf you want to access your Tomcat-Apache server remotely - so in the above step you have not specified localhost or 127.0.0.1 for the base-url parameter - you will need to add your Tomcat-Apache server's IP address to this list. Open up the file and locate this line of code:

TrustedIpAddrs 127.0.0.1 Make changes to the highlighted section add your PC or server's domain or IP address so it looks similar to this:

TrustedIpAddrs 127.0.0.1,[your_ip_address] This will allow the Pentaho Administration Console to 'ping' the server to see if it is up or down - you do not need to do this if you are hosting your server locally.

Other ParametersYou can also change the local language and country under the web.xml file, the changes to these parameters are self explanatory.

Configuring SMTP (mail server)To configure the Pentaho BI Platform to use a SMTP server (mail server) to use for emailing reports etc. you will need to make modifications to the /pentaho-solutions/system/smtp-email/email_config.xml file. Here are the available parameters that can be configured for SMTP support:

mail.smtp.host o This is the address of your SMTP email server for sending email e.g. smtp.gmail.com mail.smtp.port o This is the port of your SMTP email server e.g. for GMail this is 587 mail.transport.protocol o The transport for accessing the email server. Usually this is smtp e.g. for GMail this is smtps mail.smtp.starttls.enable o If you SMTP server uses TTLS authentication set this to true e.g. for GMail this is true mail.smtp.auth o Set to true if the email server requires the sender to authenticate mail.smtp.ssl o This is true if the email server requires an SSL connection e.g. for GMail this is true mail.debug o Output debug information from the JavaMail API mail.pop3 o Not being used. mail.from.default o The from address that emails from the Pentaho BI Platform e.g. prashantraju@gmail.com mail.userid o The userid that is used when authenticating with the SMTP server, mail.smtp.auth must be set to true. mail.password o The password that is used when authenticating with the SMTP server, mail.smtp.auth must be set to true.

Here is an example of a smtp-email.xml file configured for GMail:

smtp.gmail.com 587 smtps true true true false pentahoadmin@gmail.com pentahoadmin@gmail.com password

Configuring PublishingBy default publishing is not enabled, to enable it you will need to specify a password which will need to be used when publishing. To get started you will need to edit the publisher_config.xml file located under the /pentaho-solutions/system/ directory, once open locate the following snippet of code:

Enter a password between the publisher-password tags (this password will be the same for all users) so the snippet of code looks similar to the example below (in this example the publisher password is publishthis):

publishthis From now on when any user tries to publish content to Pentaho BI Platform they will need to specify this password.

Configuring the Administration ConsoleNo configuration is needed when setting up the Administration Console with Oracle 10g & 11g.

Starting the Business Intelligence PlatformThe Pentaho BI Platform is a webapp on the Apache-Tomcat server. To start Apache-Tomcat you will need to run the startup.sh file which is located under the /opt/pentaho/biserver-ce/tomcat/bin folder: user@terminal:/opt/pentaho/biserver-ce/tomcat/bin# startup.sh Using CATALINA_BASE: /opt/pentaho/biserver-ce/tomcat Using CATALINA_HOME: /opt/pentaho/biserver-ce/tomcat

Using CATALINA_TMPDIR: /opt/pentaho/biserver-ce/tomcat/temp Using JRE_HOME: /usr/lib/jvm/java-6-sun Now you should be able to visit http://localhost:8080/pentaho or http:// [your_domain_or_ip]:8080/pentaho. If the Pentaho BI Platform has started successfully you should see the following welcome screen:

After logging in try and run a sample report from the Steel Wheels solution folder:

Starting the Administration ConsoleTo start the Administration Console you will need to run the start-pac.sh file which is located under the opt/pentaho/administration-console/ folder: user@terminal:/opt/pentaho/administration-console# start-pac.sh DEBUG: Using JAVA_HOME DEBUG: _PENTAHO_JAVA_HOME=/lib/jvm/java-6-sun/ DEBUG: _PENTAHO_JAVA=/lib/jvm/java-6-sun/ 2010-01-05 16:27:17.824::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 05/01/2010 4:27:18 PM org.pentaho.pac.server.JettyServer startServer INFO: Console is starting 2010-01-05 16:27:18.118::INFO: jetty-6.1.2 2010-01-05 16:27:38.672::INFO: Started SocketConnector @ 0.0.0.0:8099 05/01/2010 4:27:38 PM org.pentaho.pac.server.JettyServer startServer INFO: Console is now started. It can be accessed using http://D119940:8099 or http://161.117.117.40:8099 Now you should be able to visit http://localhost:8099/ or the other two address's specified in your output (highlighted above). You will be prompted for a Username and Password which by default are "admin" and "password". If you have successfully started and logged into the administration console you should see the following welcome screen:

Page 1 of 1