2.6. Installation Notes for the Solaris Operating System


The preferred method for installing the JBoss Enterprise Web Server on the Solaris operating system is by using the provided Solaris package file; however we will also discuss installation via the zip package.
Download the desired Enterprise Web Server package that you wish to use and that will match your Solaris version and CPU architecture.

Note

For Solaris you can choose between i386 (x86) and x86_64 system versions. If running a x86_64 JVM choose the x86_64 version of the Enterprise Web Server.
If you are building the packages from source, the Tomcat 5 and Tomcat 6 packages (regardless of the Tomcat you choose) will be built by using the srpms.

2.6.1. Installation using the Solaris package

Log into your system as root and use the gunzip and pkgadd commands. The commands will be:
gunzip RHATews-1.0.0*-solaris10-i386.package.gz
Copy to Clipboard Toggle word wrap
and
pkgadd -d RHATews-1.0.0*-solaris10-i386.package
Copy to Clipboard Toggle word wrap
The output will be:
The following packages are available:
1  RHATews     JBoss Enterprise Web Server (i386) 1.0.0,REV=2.el5
					
Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:
Copy to Clipboard Toggle word wrap
Type 1 or just press enter. The following information will now appear:
JBoss Enterprise Web Server(i386) 1.0.0,REV=2.GA
	
	
END USER LICENSE AGREEMENT
JBOSS(r) ENTERPRISE MIDDLEWARE(tm)
	
The end user license agreement ("EULA") governs the use of the various software modules that collectively comprise JBoss Enterprise Middleware
and any related updates, source code, appearance, structure and organization,
regardless of the delivery mechanism.
	
The JBoss Enterprise Middleware EULA can be found here:
http://www.redhat.com/licenses/jboss_eula.html
	
	
## Executing checkinstall script.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <RHATews> [y,n,?]
Copy to Clipboard Toggle word wrap
The package installer contains custom scripts that execute during install and are used for setting up the apache and tomcat user accounts. When package installer asks whether you wish to continue with the installation type y and press enter.
Installation will then commence and the following will be displayed:
## Executing postinstall script.
Apache group (id=48) already exists. +++ or created if not
Apache user  (id=48) already exists.
Generating private RSA key ... OK
Generating new (+++ user hostname displayed here) certificate ... OK
Tomcat group (id=91) already exists.
Tomcat user  (id=91) already exists.
	
-----------------------------------------------------------------------
NOTICE
-----------------------------------------------------------------------
	
JAVA_HOME environment variable is not set.
Either set the  JAVA_HOME  or edit the configuration
scripts inside `/opt/redhat/ews/etc/sysconfig' directory
and set the JAVA_HOME to the installed JDK location.
	
	
Installation of <RHATews> was successful.
Copy to Clipboard Toggle word wrap
After the installation finishes the package is installed within the /opt/redhat/ews directory.
The package information can be checked by executing the following command:
pkginfo -l RHATews
Copy to Clipboard Toggle word wrap

Note

During installation the system generated a notice that the JAVA_HOME environment variable was not set. Configuring this is discussed later in the Section 2.8, “Running on a Solaris Operating System Installation” section.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat