Tomcat is not completely set up yet, but you can access the default splash page by going to your domain or IP address followed by in a web browser:. Now we will go deeper into the installation of Tomcat.
Note: This section is not necessary if you are already familiar with Tomcat and you do not need to use the web management interface, documentation, or examples. If you are just getting into Tomcat for the first time, please continue.
With the following command, we will install the Tomcat online documentation, the web interface manager webapp , and a few example webapps:. Answer yes at the prompt to install these packages. We will get into the usage and configuration of these tools in a later section.
Next, we will install the Java Development Kit. If you are planning on developing apps on this server, you will want to be sure to install the software in this section. Running the following command will install openjdkjdk:. In addition to JDK, the Tomcat documentation suggests also installing Apache Ant, which is used to build Java applications, and a source control system, such as git. For more information about Apache Ant, refer to the official manual. In order to use the manager webapp installed in Step 3, we must add a login to our Tomcat server.
We will do this by editing the tomcat-users. This file is filled with comments which describe how to configure the file. You may want to delete all the comments between the following two lines, or you may leave them if you want to reference the examples:. You will want to add a user who can access the manager-gui and admin-gui the management interface that we installed in Step Three.
You can do so by defining a user similar to the example below. Be sure to change the username and password to something secure:. Save and quit the tomcat-users. To put our changes into effect, restart the Tomcat service:. The Web Application Manager is used to manage your Java applications. Is there documentation that can be consulted about this? The easiest way to get tomcat8 version 8. I haven't seen any milestones except for that. Sign up or log in Sign up using Google.
Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 3. Hot Network Questions. Question feed.
Example package names below may differ from packages available in your Linux distribution repository. After upgrading Apache Tomcat to a later major version for example Apache Tomcat version 7.
Guacamole is included in the repositories of several Linux distributions. If your distribution provides Guacamole packages for you, this is the preferred method of installing Guacamole. If your distribution does not provide Guacamole packages, or the packages provided are too old, you can build Guacamole from source fairly easily.
Be aware that Guacamole is a remote desktop gateway, and cannot access your desktop's display without a remote desktop server of some kind to connect to. Your distribution of choice will provide documentation for setting up VNC, as will the documentation provided by those that created the VNC server you wish to use.
If you are going to use RDP to connect to Windows computers, Microsoft and many others on the internet provides documentation describing how to set up remote desktop. Installing Guacamole from your distribution's guacamole package will typically install the web application and the proxy guacd , along with support for VNC libguac-client-vnc. After the Guacamole packages are installed, the web application may still need to be deployed to your servlet container.
Some packages, like the Debian package called guacamole-tomcat , will do this for you, but if your distribution provides no such package, you will have to deploy Guacamole yourself.
The Debian repositories contain packages for all of Guacamole's components, and Ubuntu has inherited those packages being Debian-based. There is also a PPA which contains the most recent stable build of Guacamole while updates to the official Debian and Ubuntu repositories are pending. If you don't want to wait for the main repositories to update, users of Ubuntu can just add the PPA and install the packages from there:.
The guacamole-tomcat package will install Tomcat and automatically create the necessary symbolic links to deploy Guacamole.
If you don't want to use Tomcat, or you want to deploy Guacamole manually, you can install the guacamole package instead, and follow the deployment instructions provided in this chapter. If you install the guacamole-tomcat package, you will be prompted for whether you wish to restart Tomcat automatically.
Tomcat must be restarted after Guacamole is installed or upgraded. If you don't want to do this, or you want to do this manually, choose 'No' the default. Choosing 'Yes' will restart Tomcat for this and future installs of Guacamole. The Debian and Ubuntu packages will set up guacd such that it runs as its own reduced-privilege guacd user, for the sake of security. Similarly, the user-mapping. The guacamole-tomcat package will automatically put the tomcat6 user in the guacamole-web group, but if you are installing Tomcat manually or using another servlet container, you must ensure your servlet container's user is a member of the guacamole-web group.
If you do not do this, your servlet container will not be able to read user-mapping. By default, VNC support will be installed as a dependency of the guacamole package. Recent versions of Debian and Ubuntu have a recent-enough version of FreeRDP and include libguac-client-rdp0 , but if you're using an older version of Debian such as Debian 6.
Fedora has an excellent Guacamole package, guacamole , which will automatically install deploy Guacamole to Tomcat. It does not depend on guacd , however, and you thus must install the guacd package manually alongside guacamole :. Most users will want at least libguac-client-vnc. If you want SSH support, or access to RDP servers, you will need to install libguac-client-ssh or libguac-client-rdp respectively.
Once everything is installed, you will still need to configure guacd and Tomcat to start automatically on boot assuming this is what you want :. You do not need to restart Tomcat after editing this file; it will be reloaded automatically by Guacamole. If you distribution isn't listed above, there is still a chance your distribution provides Guacamole packages. A search for 'guacamole' in your distribution's package manage should answer that question quickly.
If no package is provided, your only option is to build Guacamole from source. Building Guacamole from source is not hard. In most cases, all you need to do is download the latest source for guacamole-server , and the latest guacamole.
The method for installing Guacamole is fairly constant across platforms, and the instructions given here should apply almost universally and in the case that they don't, you probably already know what you need to do. Building the components of Guacamole from source is not difficult, providing you have the necessary tools installed already. The source for the entirety of Guacamole is available from the Guacamole project web site in convenient source archives, each named after the component they contain.
Guacamole is separated into two pieces: guacamole-server , which provides the guacd proxy and related libraries, and guacamole-client , which provides the client to be served by your servlet container.
In most cases, the only source you will need to build is guacamole-server , and downloading the latest guacamole. Building guacamole-client is really only necessary when you wish to modify the source or when you want to try the latest unreleased changes.
To compile the C components, you will need a C compiler such as gcc and the libraries that each component depends on. Note that many Linux distribution separates library packages into binary and 'development' packages; you will need to install the development packages.
These will usually end in a '-dev' or '-devel' suffix. It provides a common C library, libguac , which all other native components depend on, as well as separate libraries for each supported protocol, and a proxy daemon, guacd , the heart of Guacamole. It effectively translates between common remote desktop protocols like VNC or RDP by dynamically loading protocol support plugins.
Building guacd creates an executable called guacd which can be run manually or, if you wish, automatically when your computer starts up. In order to build guacamole-server , you will need Cairo , a graphics library, and libpng , the official PNG library. These libraries are strictly required in all cases. Guacamole cannot be built without them. The other dependencies of guacamole-server are optional. Which libraries you will need to install depends on what support you need.
Each protocol corresponds to a separate library that will be built with guacamole-server if you have its corresponding optional dependencies. Cairo is used by libguac for graphics rendering. Guacamole cannot function without Cairo installed. Guacamole cannot function without libpng. If you do not wish to build RDP support, this library is not needed. Pango is a text layout library which Guacamole's SSH support uses to render text. If you do not wish to build SSH support, this library is not needed.
If you do not wish to build VNC support, this library is not needed. If you are not going to be using the experimental audio support for VNC, you do not need this library.
If you have libssl installed, guacd will be built with SSL support, allowing communication between the web application and guacd to be encrypted.
0コメント