Jboss Application Server Download For Mac Os X

1.2. Supported Operating Systems
1.3. JBoss Application Server
1.4. Databases
1.5. Source Building

To deal with this problem, you need to obtain a server that can be built from source, and therefore optimized for Mac OS X. Since commercial offerings don't make source available, JBoss quickly rises to the top of the heap. Freely available and completely open source, JBoss works beautifully on Mac OS X. JBoss Web Server gives your IT enterprise a stable and secure web application infrastructure with long-term reliability. Each release benefits from predictable updates—including defect fixes and features—and maintains application compatibility for up to 5 years. JBoss AS 4.0 runs on Java Virtual Machine (JVM) versions 1.4-1.6 and is a Java EE 1.4 application server with a built-in Apache Tomcat 5.5 servlet shell. JBoss also supports many operating systems, including Portable Operating System Interface for Unix (POSIX) platforms, GNU/Linux, Free Berkeley Software Distribution (FreeBSD), Mac OS X. If open-source tools make you a little nervous, fear not—JBoss application server is compliant with Java Enterprise Edition 7 specifications. You can run JBoss application server on Linux, Unix, OS X, and Windows. With a JBoss application server, you get a high class, enterprise-grade platform both reliable and scalable for zero cost.

The following chapter details hardware and software versions that are compatible with JBoss Portal. The hardware and software listed has either been tested, or reported as working by users. Before reporting a problem, make sure you are using compatible hardware and software.

If you successfully installed JBoss Portal on versions not listed here, please let us know so it can be added to this section.

JBoss Portal 2.7.0 is tested with JBoss Application Server (AS) JBoss AS 4.2.3, JBoss Enterprise Application Platform (EAP) 4.2 and JBoss EAP 4.3. It is highly recommended that customers who have access to the JBoss Customer Support Portal (CSP) use JBoss EAP 4.3. Customers who do not have access to the JBoss CSP should use JBoss AS.

Warning

JBoss AS versions 4.0.x are not supported.

MySQL® 4 (use Connector/J 3.1) and 5 (known issue)
PostgreSQL 8.x
Hypersonic SQL
Apache Derby
Oracle® Database 9 and 10g (use the latest driver from the Oracle 10 branch even if you are running Oracle 9)
Microsoft® SQL Server®
MaxDB

JBoss Portal employs Hibernate as an interface to a Relational Database Management System (RDBMS). Most Relational Database Management Systems supported by Hibernate will work with JBoss Portal.

Although numerous commercial J2EE server offerings are available, few of them (as of this writing) have releases built specifically for Mac OS X. Many have Linux and Unix versions of their products, but Mac OS X offerings remain sparse. This situation is expected to change as Mac OS X gains momentum, but for now it creates a problem for enterprise Java developers. To deal with this problem, you need to obtain a server that can be built from source, and therefore optimized for Mac OS X. Since commercial offerings don't make source available, JBoss quickly rises to the top of the heap. Freely available and completely open source, JBoss works beautifully on Mac OS X. This chapter will show you how to get it running.

14.1.1 Downloading a Release

Jboss Download For Windows 10

You can download releases of JBoss from http://www.jboss.org/. The release used here is 3.0.4, which uses the default JBoss web server.

Some releases of JBoss are bundled with the Tomcat web server, which functions as detailed in the last chapter. You are welcome to use that release, and it works well on Mac OS X. However, this chapter assumes the 'pure' JBoss release.

Jboss Web Server

You should download the JBoss-3.0.4.zip file, weighing in at 28.7 MB. This release of JBoss includes a web (HTTP) server, a JSP and servlet container, and support for EJB, CMP 2.0, RMI, IIOP, Clustering, JTS, and JMX.

Acronym Frenzy

Lest all the acronyms overwhelm you, here is a brief rundown of some of the common ones in J2EE:

CMP: Container Managed Persistence, a feature of EJB that allows persisting data to a database
EJB: Enterprise JavaBeans
IIOP: Internet Inter-Orb Protocol, a more traditional protocol for communication over distributed architectures
J2EE: Java 2 Enterprise Edition
JMX: Java Management Extensions, an API that allows other Java applications to interface with a J2EE server programmatically through a standard set of coding paradigms
JSP: JavaServer Pages
JTS: Java Transaction Service, the Java API for handling transactions, committals, and rollbacks of database communication
RMI: Remote Method Invocation, which allows remote components to be interacted with as if they were local objects

14.1.2 Installation

Assuming you've downloaded the JBoss-3.0.4.zip file into your home directory (~), execute the commands below to expand the JBoss distribution:

You'll need to replace the bolded username (wiverson) with the username you want to run JBoss as. This name could be a special user account you created just for this purpose, or your own user account. When you are done, you'll have a complete JBoss installation in the /usr/local/jboss/ directory.

Using NetInfo to create a 'homeless' user is a good way to protect JBoss user accounts. (Refer to O'Reilly's Mac OS X for Unix Geeks for more information.)

14.1.3 Starting JBoss

To start JBoss, simply enter the following command:

After a lot of messages scroll past, you will see a status message along the lines of:

This indicates that JBoss is now running. To verify that it is working properly, open the administrative console at http://localhost:8080/jmx-console/. You should see something similar to Figure 14-1.

Figure 14-1. The JBoss administrative console

JBoss ships with three different configurations: 'minimal,' 'default,' and 'all.' These configurations are stored in the directory /usr/local/jboss/server/. When you start up the server with the default run.sh command, you imply that you wish to use the /usr/local/jboss/server/default directory as your server directory.

This is particularly relevant if you want to deploy JBoss with the absolute minimal server configuration. In that event, copy the minimal configuration directory, and then add library and configuration data to support your application as you add functionality.

Comments are closed.