Skip to content







Service manager

API Explorer

Integrate package web pages

If your Integrate package has a web directory, it will be scanned and added to Tomcat during package start-up as a web application. Furthermore, the presence of a web.xml file in the web/WEB-INF directory tells TORO Integrate and Tomcat that your webapp's configuration is customized, and thus this configuration will be used as opposed to the default webapp configuration TORO Integrate creates for packages without web.xml files.

Effectively, this means you can deploy your web applications to TORO Integrate and use all the APIs available to get your sites up faster than ever before. You can invoke Gloop services and have them render JSP pages and serve web pages the MVC way using either Gloop or Groovy APIs!.

The package lifecycle and Tomcat

If a package is stopped, then its associated web context will be stopped and removed from Tomcat, too.

Coder support for HTML, JSP, CSS, and JS

You can create and edit your HTML, JSP, CSS, and JS files in Coder Studio. Coder Cloud, however, only offers support beginning v1.3; previous versions only allowed the viewing of these files but does not offer the capability to create them.

Creating a default package homepage

It's easy to create a default homepage for your packages! All you have to do is place a JSP web page in your package's web directory and ensure it is named index.jsp. A restart is not required. You may view your package's homepage at <host>:<port>/<name-of-package> where <host>:<port> is the root address of your TORO Integrate server.