Caucho resin installation

Now that you've configured the Resin build process, all you need to do is build and install! To build, just run. We provide a Debian packaged version of Resin that Debian and Ubuntu users can take advantage of. It performs all of the installation steps above for you and creates all the recommended server and content directories.

Alternatively, you can add Caucho's Debian repository to your system's repositories to use automated update tools like Synaptic and apt-get. The native libraries that are included with Resin are precompiled for Windows in both bit and bit mode. These libraries provide:.

Resin and JavaEE organize content into "web applications" or webapps. As an administrator, your developers have probably provided you with a webapp in the form of a. In the Resin root directory is a special subdirectory named webapps which is a webapp deploy directory. Deploying applications in Resin is as easy as copying a. Resin detects the applications and deploys them automatically.

In the directory structure above, notice the special webapp directories named "ROOT". Other webapps will map to their name. Resin is configured to use the content directory structure show above by default. This directory is also the recommended content root for Unix. To specify the root directory to Resin, you pass it on the command line when starting the server.

For example:. If you use the Unix startup scripts mentioned in the next section, they automatically specify the root and log directories. When you installed using the.

This file will start Resin when invoked as:. Resin can install itself as a Windows Service by executing the resin. If you pass other options to resin. To install Resin as a Windows Service using the default options, simply run:.

You can also install Resin using a specific service name or install multiple Resin services using the -install-as option:. Note: the command prompt i. The cmd. One of the most useful tools provided with Resin is the built-in, web-based administration console.

This tool provides detailed information about the operation of the server, a feature that is very useful to administrators, but one which must be kept secure from unauthorized users. If you are deploying Resin to a production machine, it's likely that you won't be running your browser on the same system as the server. In this case, you'll need to configure Resin to allow you to access the server remotely.

Now that you're able to access the administration application, you have to set up a password and install it. In order to prove that you have access to the machine on which Resin is running, the only way to change the password is to create a file with the authentication information on that machine.

Hopefully, the log message will be clear enough for you to figure out the problem. If not, you have a number of resources available to you to help you figure out what's going wrong:. Resin provides a fast servlet runner for Apache 2. Doing so isolates the steps and makes troubleshooting easier. Many users find that the performance, flexibility, and features of Resin make it a desirable replacement for Apache and IIS. These 3rd party HTTP servers add overhead to Resin's operation, therefore you should have a specific reason to run one of them with Resin.

Apache is a frontend server, it handles the request from the browser. Other URLs stay with Apache. Resin needs Apache 2. If you don't have DSO support, you can recompile Apache or install another package from your operating system vendor. Check their documentation for more details. The setup. Replace win32 with win64 above if you're using a bit version of Apache.

The resin. The default resin. The mapping of urls to filesystem locations should be consistent between Apache and the backend Resin server.

To tell Resin to use Apache's document area, you configure an explicit web-app with the appropriate document-directory:. The caucho-status handler is optional and probably should be avoided in a production site. It lets you ask the Caucho Apache module about it's configuration, and the status of the backend server s , valuable for debugging. After any change to httpd. You can also dispatch to Resin directly from the httpd. Instead of relying on the ResinConfigServer directive to determine which url's to dispatch to the backend server, Apache handler's are used to specify the url's to dispatch.

Requests are distributed to all machines in the cluster, all requests in a session will go to the same host, and if one host goes down, Resin will send the request to the next available machine. Optional backup machines only receive requests if all of the primaries are down. It will query that backend server, and learn about all of the other members of the cluster.

The httpd. Manual dispatching in httpd. Of course, adjust these to the correct directories for Java and Resin if they differ from your own. If setup. Some users may need to set the priority to a higher level, e. In other words, you need to configure the document root and any directory aliases. The mapping of url paths from the browser to real files on the disk must be the same for Resin as they are for IIS.

The steps involved are:. If you only have one Resin server, you should not create a resin. You can change the host from localhost to a backend server. You can also add multiple ResinConfigServer items to cluster the configuration. You may need to click "add a new web service extension Find the User on the "Identity" tab, it may be the user named "Network Service" in the drop-down list associated with the radio button labeled "predefined".

This section shows how the plugins for these servers interpret the Resin's configuration and how to change that configuration for your deployment. The ResinConfigServer can be any Resin server. That decision is based on the configuration in the ResinConfigServer's resin. If you put regular expressions in your resin. Apache will handle the request itself. If you want to use regular expressions in servlet-mapping, web-app, or hosts, you must use Apache-specific configuration to send the request to Resin.

All the servlet-mappings in a web-app apply only to the URL suffix. The servlet-mapping only applies to URLs matching the prefix. There's a bit of extra work for virtual hosts that we'll ignore here. Basically, you need to add Apache ServerName directives so Resin knows the name of the virtual host. For dispatching, a host block gathers a set of web-apps.

Each host will match a different set of URLs, depending on the web-app configuration. The default host matches any host not matched by a specific rule. It will ignore all hosts using regexp. To get around this, you can either configure Apache directly see below , or configure the default host with the same set of servlet-mappings.

Resin provides a fast servlet runner for Apache 1. Many users find that the performance, flexibility, and features of Resin make Resin a desirable replacement for Apache. You need a version of Apache with DSO support enabled.

Many distributions, e. Red Hat Linux, will have Apache preinstalled. This tool provides detailed information about the operation of the server, a feature that is very useful to administrators, but one which must be kept secure from unauthorized users.

If you are deploying Resin to a production machine, it's likely that you won't be running your browser on the same system as the server. In this case, you'll need to configure Resin to allow you to access the server remotely. Now that you're able to access the administration application, you have to set up a password and install it. In order to prove that you have access to the machine on which Resin is running, the only way to change the password is to create a file with the authentication information on that machine.

Hopefully, the log message will be clear enough for you to figure out the problem. If not, you have a number of resources available to you to help you figure out what's going wrong:. Resin Server Installation. Preparing for installation Install JDK 1. Download the latest version of Resin 4 from the Resin download page. Grab the Professional version if: You have purchased a Resin Professional license. You have obtained an evaluation Resin Professional license.

You are considering purchasing Resin Professional without a license, Resin Professional simply downgrades to the open source functionality. This will make it easier to upgrade in the future. Unzip or untar the Resin download. If you downloaded Resin Professional, it will extract into resin-pro Configuring the build process for Resin Next we'll change into the Resin directory we just unpacked to configure and build the server.

Building and Installing Resin Now that you've configured the Resin build process, all you need to do is build and install! To build, just run make. Installing Resin using the.

Solaris notes Depending on your Solaris packaging, you make need to give the. Installing Resin on Windows The native libraries that are included with Resin are precompiled for Windows in both bit and bit mode. Resin does not support OpenSSL 1. Resin Content Installation.

Content from the top down Resin and JavaEE organize content into "web applications" or webapps. Permanent content locations Resin is configured to use the content directory structure show above by default. Creating Unix startup scripts for Resin When you installed using the. Creating a password for the Resin Administration Console.

Resin Documentation home company docs app server. To build, just run make If this step went well, you'll now need to install the Resin files as the root user: sudo make install Wherever you install Resin to using the --prefix , we'll refer to that directory as resin.

Creating a password for the Resin Administration Console One of the most useful tools provided with Resin is the built-in, web-based administration console. Replace "localhost" with the name of your host in the URLs below. The recommended username is "admin".

After going to the next page, a new admin-users. Just rename this file to admin-users. The change you made should force Resin to restart and return a error. Just hit refresh in a few moments to bring up the page again. You should now be able to login using the username and password that you gave above. Troubleshooting If something went wrong above, the first place to check for problems is the log.

If not, you have a number of resources available to you to help you figure out what's going wrong: The Resin mailing list. The Resin Forums. Presales technical support for those considering purchasing Resin Professional. Paid technical support directly from the Resin developers. All rights reserved.