Install Presto dev edition onto an existing Tomcat container

This assumes, Timm, that you are not working with Mashup Studio and that it is OK to move the Presto Repository and all Presto scripts to a folder on the remote host with your existing Tomcat instance.

If you have the Developer Edition installed, you will find a folder Presto2.6.0/server/apache-tomcat-5.5.20/webapps. This has all the Presto WAR files, as well as the fully-expanded web application folders.

The best solution is to copy both the WAR files and the fully exploded web app folders to your remote Tomcat installation. Then,  copy the rest of the Presto installation to another folder on the remote host and:

* edit the Presto2.6.0/jbenv.bat or jbenv.sh file and update the environmental variables defined in this script.

* update port configuration for Presto as needed. See the topic on Configuring the Presto Server with Custom Ports in documentation at http://www.jackbe.com/prestodocs/v2.5/prestoadmin/index.html for full information.

* you may also want to check through the documentation for topics on configuring Presto for a proxy server.

Hope this helps.

Thank you very much. I will give it a try.

Hi Sara,

I have a server on which I installed Presto. The server already has a tomcat installation. I want to use Mashup Studio on the same server, is the recommended procedure that I install Presto with its own tomcat but just different IP ports assigned? This means that I would have two tomcat installations running one for the existing application on port 8080 and the Presto tomcat installation running on port 9080.

Thanks,

Mike

Hi Mike,

1. Did you mean Mashup server when you said Mashup Studio?

2. Presto can work on your existing Tomcat instance, provided other applications deployed on your existing instance do not cause issues in Presto's working (like conflicting ports). In case you want to deploy Presto in your existing tomcat, I would suggest you run the setup script and specify the default port numbers (in case you are using non-default port number(s) for your existing tomcat installation specify those port number(s) during the setup).

3. Once the setup process is complete, required changes have been made to the presto web application. Copy all the presto war files from the new tomcat instance (<app server home>/webapps/) to your existing tomcat instance. Change the values for APPSERVER_HOME, TOMCAT_HOME, CATALINA_HOME in jbenv.bat or jbenv.sh (depends on your OS) to point to your current instance of tomcat.

4. Now start the Presto Repository

5. Start the Mashup server

You should be good to go.

Hi Mike,

You can run Mashup Studio with the Presto instance that you installed in your existing server, as long as you keep some things in mind:

* Mashup Studio has configuration to identify one or several Presto Mashup Servers to work with. There is a default configuration, called the Embedded Server, which actually only uses the Presto Repository.

* For the Embedded Server to work, the Presto Repository must be running on the same host as Mashup Studio and it must use the default database (HSQL) installed with Presto with the default port.

* You can only debug against the Embedded Server.

* You can define additional "remote" server configurations that can run against Presto on the local box or on remote boxes. To use a remote server configuration, the Mashup Server at that address must be running.

* Unfortunately, there are a few known issues in Mashup Studio with the Embedded Server. It may be more reliable to use a remote server configuration pointing to your local Presto instance when you are using the Services view or Service Inspector view. Then use the Embedded Server configuration for debugging. As long as both configurations are using the same Presto Repository, you are essentially working with a single 'view' of Presto.

Hope this helps,

Sara