Print
Installing WebSphere Community Edition on Mac OS X revisited
Almost two years back, Olexiy Prokhorenko blogged in his SILENT WORDS blog about how to put WAS CE on Mac OS X (PowerPC). Not all that much has changed since then. However, after downloading the WebSphere Application Server Community Edition 2.0, here are the updated steps I took, to get it installed on Mac OS X 10.5.2:

In the terminal:
cd ~/Downloads
chmod 777 ./wasce_setup-2.0.0.2-unix.bin
./wasce_setup-2.0.0.2-unix.bin -is:extract -is:log wasce_extract.log

This creates 8 files in a temporary sub folder like this: ~/Downloads/istemp846105124847. However, the name of your temporary folder may be very different.

TMPINST=~/Downloads/istemp846105124847
export TMPINST
java -cp .:$TMPINST/setup.jar: -Dtemp.dir="tmp" -Dis.jvm.home="/Library/Java/Home" -Dis.jvm.temp="0" -Dis.media.home="$TMPINST/setup.jar" -Dis.launcher.file="wasce_setup-2.0.0.2-unix.bin" -Dis.external.home="." run 1>>wasce_install.log 2>>wasce_errs.log

This will launch the WebSphere Application Server install appliaction and look something like this:


Now, cd into the install folder and set the correct permissions. Again, you may have put the application into a differnt folder.

cd /Applications/Developer/WebSphere
chmod a+x _uninst/ bin/ graphics/ lib/ repository/ schema/ var/
chmod a+x _uninst/*.sh
chmod a+x bin/*.sh

.. and launch the the WebSphere Application.

./bin/startup.sh

which will result in an output something like this:

Using GERONIMO_BASE: /Applications/Developer/WebSphere
Using GERONIMO_HOME: /Applications/Developer/WebSphere
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
Using GERONIMO_OUT: /Applications/Developer/WebSphere/var/log/geronimo.out

Geronimo started in background. PID: 479



Finally, navigate your browser to the console, here http://localhost:8080/console or here https://localhost:8443/console. Initially the user name is system and the password is manager.



Here for instance, I am using the console via https to stop the default TomcatWebConnector on port 8080 and replace it with the Tomcat NIO HTTP Connector, allowing comet-style client server interaction (long-lived HTTP connections).


QR code, to put this blog on your mobile