We've designed tutorials that provide a gradual introduction to Corus.
We suggest you follow the tutorials in the order in which they're
presented below. We also suggest you read the
In order to go through the tutorials, you'll have to check out Corus
and build it from source - that is in fact
the subject of the first tutorial.
All other tutorials are based on sample applications that are part
of the Corus source tree. You need to build Corus from source in order
to move on to the other tutorials. We're showing you how in this
See how a Grails web app is deployed into a Jetty container that is
itself deployed into Corus. The tutorials illustrate the full
development-to-deployment cycle. At the end of this tutorial you'll
have a very good grasp of what Corus is about.
What is it exactly? How is it used? The descriptor tells Corus
how to start your applications. It's the only Corus-specific config
file you'll need when deploying standalone Java apps into Corus.
The command-line interface mimicks Linux/Unix commands and is
the primary tool through which you interact with Corus.
Explore the various features, play around with wildcards,
learn about clustered commands.
The real power of Corus lies in its "collective management"
capabilities. You can manage a whole domain of Corus instances through
the Corus command-line, without more hassle than you do a single
There are more features in stores to streamline deployments and
ease the pain of maintenance operations. In this tutorial, we're
exploring these hassle-saving features.