The Pre-Configured Install is designed to run standalone on a single machine using http://localhost:8080/pentaho
as the base URL. If you do not need access to the server from other computers, you can skip the "Running as a server" step.
Running as a server
Modify web.xml
To allow other computers to access the Pentaho BI Platform, the base URL must be set in the web.xml file
- Locate the web.xml file, its default location is: pentaho-demo/jboss/server/default/deploy/pentaho.war/WEB-INF
- Open web.xml in an XML or text editor.
- Set the param-value of the context parameter base-url with the URL for the server. The URL should have the DNS Name or IP address of the machine, the port default 8080 and the context pentaho. If you want to change the port that the server uses, see the Advanced Install Guide.
The final result should look like:
<context-param> <param-name>base-url</param-name> <param-value>http://myserver.pentaho.org:8080/pentaho</param-value> </context-param>
Modify start-pentaho.(bat|sh)
Beginning with Pentaho BI Server 1.6-RC2 and later, an extra step is required in order to access the server from other hosts. Set the JBoss bind address by editing start-pentaho.(bat|sh). Add the -b parameter. More documentation for this parameter can be found on the JBoss wiki
.
@echo on
setlocal
set PENTAHO_PATH=%~dp0
set JAVA_HOME=%PENTAHO_PATH%jre
set PATH=%PENTAHO_PATH%jre\bin;%PATH%;
cd jboss\bin
start run -b myserver.pentaho.org < lines.txt
#!/bin/sh
cd jboss/bin
sh run.sh -b myserver.pentaho.org
@echo "C:\pentaho\bi-server\jboss\bin\run.bat" -b myserver.pentaho.org ^< lines.txt > "C:\pentaho\bi-server\jboss\bin\wrapper.bat"
Or you could also add the -D parameter: in the above snippets, replace the "-b myserver.pentaho.org" for "-Djboss.bind.address=YOUR.IP.GOES.HERE". This will change JBoss binding address and you will need to edit only web.xml to point to the same IP. However, this is a quick & dirty fix, for it breaks the shutdown scripts. As you can simply kill the server, it might help when a fast fix is needed to help things get going.
Modify stop-pentaho.(bat|sh)
If you added the -b parameter to start-pentaho.(bat|sh), you'll also need to make the following modification to stop-pentaho.(bat|sh).
@echo on
cd data
start stop_hypersonic.bat
cd ..\jboss\bin
shutdown -S -s myserver.pentaho.org< lines.txt
exit
cd data
./stop_hypersonic.sh &
cd ../jboss/bin
./shutdown.sh -S -s myserver.pentaho.org
Thanks... for this tip
Now I am able to access the server remotely but when I try to stop it with stop-pentaho.sh I am getting Exceptions and the server is not stopping. Do I need to modify stop-pentaho.sh as well?
Thanks!
I found one answer on my previous question about required modifications at stop-pentaho.sh.
./shutdown.sh -S -s <server IP Address or name>
Is this the correct way?
Thanks!
The start-pentaho.bat file that ships with the windows installer looks nothing like the abovesample. Can someone update this information?
It calls several other files based on the parameters supplied. I assume that this is because the installer created a windows service?
sd
Can anyone explain what to change in in the latest version of start/stop pentaho.bat ? thanks.
I have modified the web.xml without any problem, but the start-pentaho.bat that I have is completely different than the one here. Could anyone please update this? What should I do to be able to access to the pentaho server remotely?
Could someone update this with the latest version because it looks totally different from above.
Thanks.
Yes, the latest version of pentaho is different from the above stated files.
I just replaced all my start/stop bat/sh files with the above corresponding codes and with a few changes ...
web.xml <context-param>
<param-name>base-url</param-name>
<param-value>http://systemname:8080/pentaho
</param-value>
</context-param> start-pentaho.bat
@echo on
setlocal
set PENTAHO_PATH=%~dp0
set JAVA_HOME=%PENTAHO_PATH%jre
set PATH=%PENTAHO_PATH%jre\bin;%PATH%;
cd jboss\bin
start run -b systemname < lines.txt
start-pentaho.sh
#!/bin/sh
cd jboss/bin
sh run.sh -b systemname
stop-pentaho.bat
@echo on
cd data
start stop_hypersonic.bat
cd ..\jboss\bin
shutdown -S -s systemname< lines.txt
exit
stop-pentaho.sh
cd data
./stop_hypersonic.sh &
cd ../jboss/bin
./shutdown.sh -S -s systemname
This configuration doesnt work at all with 1.6 GA Pentaho BI Suite.
Agreed, this documentation is horribly outdated (as is much of the other documentation in the BI suite.) This small issue is keeping us from deploying ANY of our new reports, so it would be great if someone could get to updating these things.
Agreed, this documentation is horribly outdated (as is much of the other documentation in the BI suite.) This small issue is keeping us from deploying ANY of our new reports, so it would be great if someone could get to updating these things.
QuotedThanks a lot !
How to modify start-pentaho.(bat|sh) helps me to solve my problem. I didn't know this new step before reading your post.
I'm sure it will help a lot of people ![]()
This is your solution, I've just read it and I believe it could work, I'll test it today :
http://forums.pentaho.org/showpost.php?p=177005&postcount=7![]()
Good luck !![]()
the start-pentaho.bat included with exe installer
@echo "C:\pentaho\bi-server\jboss\bin\run.bat" -b myserver.pentaho.org ^< lines.txt > "C:\pentaho\bi-server\jboss\bin\wrapper.bat"
is not working for me. I still cant make pentaho run as server.
Am I the only one having this problem???
With the version pentaho_demo_hsqldb-1.6.0-RC2.820, I just change the web.xml file and the start-pentaho.bat as described here, and works PERFECTLY, no problems! but the one with the EXE installer has been a NIGHTMARE for me for months!
surely <lines.txt is not correct the > must be going the wrong way if its for logging purposes.
I have the same problem and I solve it. Open server.xml in pentaho\bi-server\jboss\server\default\deploy\jboss-web.deployer . There is a line <Connector port="8080" address=..... Change it to <Connector port="8080" address="your.ip".........
Thank you Ivan. Modifying server.xml solved my problem accessing pentaho as server.
Existing feature request for a configuration tool: http://jira.pentaho.com/browse/BISERVER-206![]()
The lines.txt redirection isn't for output, it is for input. It's providing carriage-returns to the process so you don't have to "Press Any Key To Continue".
I have modify the files as describe :
- Pentaho\bi-server\jboss\server\default\deploy\pentaho.war\WEB-INF\web.xml :
<context-param> <param-name>base-url</param-name> <param-value>http://tmgbkp02:8080/pentaho/</param-value> </context-param>
- Pentaho\start-pentaho.bat :
@echo "F:\Pentaho\bi-server\jboss\bin\run.bat" -b tmgbkp02 ^< lines.txt > "F:\Pentaho\bi-server\jboss\bin\wrapper.bat"
- Pentaho\stop-pentaho.bat :
@echo "F:\Pentaho\bi-server\jboss\bin\shutdown.bat" -s tmgbkp02 -H0 ^< lines.txt > "F:\Pentaho\bi-server\jboss\bin\wrapper.bat"
At this point the web server doesn't respond on the http://tmgbkp02:8080
URL but always on the http://127.0.0.1:8080
. As tell by Ivan Georgiev, I have modify the server.xml file like this :
- pentaho\bi-server\jboss\server\default\deploy\jboss-web.deployer\server.xml :
<!-- <Connector port="8080" address="${jboss.bind.address}"--> <Connector port="8080" address="tmgbkp02" maxThreads="250" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8" /> <!-- <Connector port="38011" address="${jboss.bind.address}" protocol="AJP/1.3" emptySessionPath="true" enableLookups="false" redirectPort="8443" /> --> <Connector port="38011" address="tmgbkp02" protocol="AJP/1.3" emptySessionPath="true" enableLookups="false" redirectPort="8443" />Ok, now the server is responding on the http://tmgbkp02:8080
and work fine. But i think that it will be better to set the variable jboss.bind.address instead of replacing them. So my questions : - where can i set the variable jboss.bind.address ?
Regards
Hubert
Thanks a lot !
How to modify start-pentaho.(bat|sh) helps me to solve my problem. I didn't know this new step before reading your post.
I'm sure it will help a lot of people