Ever since I switched to my Mac, a little over 2 years ago, one of the things on my todo list has been to install WebLogic and get it running on the Mac.  It’s unsupported, but heck, it’s a Java application, so how hard could it be?  And it’s the Java application server that I am most familiar with (other than Tomcat), so I want to be able to use it.

A quick Google search revealed no information about WebLogic Server 10 on the Mac at all, so I reached further back.  It’s pretty easy, since the same steps that worked for WebLogic Server 9.x seem to work for 10.

1. First, download the “generic” installer for IBM AIX (that would be the ONLY installer for AIX).  You end up with a jar file called

   server100_generic.jar

2. Open up Terminal, and run the jar file using this command, to get around a problem in the installer that checks for free space by OS name:
   

   java -Dos.name=unix -jar server100_generic.jar

   I chose to install to /bea, so the adjust the path names appropriately, if you install elsewhere.
   
   
3. Update your /bea/wlserver_10.0/samples/domains/wl_server/bin/setDomainEnv.sh file to increase some memory parameters like so:
   

   MEM_ARGS=”-Xms512m -Xmx1024m -XX:MaxPermSize=128m”

4. Start your WebLogic Server by running:
   

   /bea/wlserver_10.0/samples/domains/wl_server/bin/startWebLogic.sh

5. Go to http://localhost:7001/index.jsp … Done!
   
   
6. Ok, not quite done, when you want to stop the server gracefully you need to run:
   

   /bea/wlserver_10.0/samples/domains/wl_server/bin/stopWebLogic.sh 

Work on a Mac notebook.  Plug in to an external monitor with a higher native resolution than your notebook screen.  While Eclipse is maximized to fill your external monitor, close it.  Unplug external monitor.  Start Eclipse again.  See the magic of having a window that is maximized, on all sides, beyond the edges of your screen.  Enjoy the dysfunction, because it cannot be fixed.  You cannot get to any menu or screen edge, which will allow you to resize or move the window.

After you’ve pulled sufficient hair out trying to fix this, hopefully you’ve Googled for a solution, and found this page.  You can’t resize your “too large” Eclipse window, but you can wack the wonky settings by closing Eclipse, deleting this file, and letting Eclipse regenerate it when you restart:

.../workspace/.metadata/.plugins/org.eclipse.ui.workbench/workbench.xml

I wonder if this means we’ll have to rename ourselves TeamC? (Just kidding, Fraz!)

Press Release: Borland forming CodeGear to focus exclusively on developer productivity

Borland Software Corporation (NASDAQ: BORL, www.borland.com), today announced its decision to separate the Developer Tools Group into a wholly-owned subsidiary focused on maximizing developer productivity. The newly formed operation, CodeGear, will be responsible for advancing the four primary product lines formerly associated with Borland’s Integrated Development Environment (IDE) business. These include Developer Studio (Delphi®, C++Builder® and C#Builder®), JBuilder® (including the upcoming Eclipse-based “Peloton” offering), Turbo® and Interbase.

It’s hard to believe that anyone could have missed this news this morning, but just in case…

James Gosling: on the Java Road

GPL V2 wins!

I’m really happy that after months of arguing and analysis, we finally agreed on using the GPL version 2 with the classpath exception as the license for JavaSE. We’re also taking the first couple of baby steps in getting actual source code relicensed. All of it will follow, eventually. But there’s a lot of work to do, like migrating millions of lines of code from TeamWare to Mercurial.

Yay!

Joe McGlynn

We’re already hard at work on the next release of JBuilder, codenamed “Peloton”. At the same time, we’re working on Service Pack 1 for JBuilder 2006.

So get on to Quality Central and enter your bugs, and vote for bugs NOW, while they still have time to work on them.

Because Eclipse is eating JBuilder’s lunch, according to this study…

This is exciting. I tried to get this working off and on for months, but I didn’t really need it (been working in Ruby), so I wasn’t really working very hard on it.

Anyway. Today Paul Furbacher posted a script that almost lets you get JBuilder 2005 running on the new Intel Macs. His efforts inspired me, and I got back to working on a script (screw the launchers, wasted too much time on them) for JB2006.

• Workspace comes up mangled (MessagePane only). Reset to default works fine.
• Java source files come up with a “first and default” pane of “History”. This is seriously irritating.
• Strange CFMessage messages in the message pane when I run or debug.

• A machine to install JBuilder 2006 on (one that is officially supported)
• Download and install JDK 5 for your Mac

1. Install JBuilder 2006 on another machine (I did Windows)
2. Zip up the contents of your JBuilder2006 directory, excluding the jdk. (Note this should give you a zip file with stuff like the bin and lib directories in the root of the zip)
3. Transfer the zip to your Mac
4. Copy your old JBuilder 2005 for Mac install into a JBuilder2006 directory
5. Remove the contents of the JBuilder2006/JBuilder.framework directory and replace with the contents of your zip file
6. Copy the jbuilder2006.command script file (posted on news://borland.public.attachments) to your Mac
7. Double click on the script file and see if it works.

My article on using Apache Derby (aka Cloudscape) in JBuilder has finally been published.

Apache Derby is a pure Java™ database, like JDataStore. Since the future of JDataStore is uncertain (read the JBuilder 2006 release notes), it is probably a good idea to investigate all your options.