I've recently been trying to get my secondary machine, a Mac, running Rational Application Developer at least close to how I have it running on my primary Windows machine. (While awaiting hardware fixes and system reload.)
Several things have not worked out-of-the-box, so I figured I ought to document the things I've had to address.
Update an existing installation
First, I already had RAD 9.6 installed and had used it a bit, so I know it was working. It also installs a copy of IBM Installation Manager, which is how you ought to be able to update to a new fix level. I knew 9.6.1 was available, so I tried the "IBM Installation Manager" option from within RAD, from the "Help" menu, but it never worked. I don't remember the exact behavior or error, but I think at one point the application just never appeared, and maybe at another it reported a generic, "An error has occurred... see the log file".
Nor did running the program directly, once I located it under /App
I then tried deleting IM, which under a Mac is not as intuitive to me as Windows, believe it or not. (And, apparently, simply sending those folders - InstallationManager and IMShared - to the Trash is insufficient for a full uninstall. I'll return to that in a moment.)
I then tried installing a new, standalone version of IM, but that found no packages either.
So... I concluded I needed to uninstall everything and start from scratch with 9.6.1. However, when running that installer, the IM installation portion complains that a newer version is still installed.
Now, attempting to run RAD right after installation resulted in the confusing error, "To open "Eclipse" you need to install the legacy Java SE 6 runtime".
Are you kidding me? An up-to-date version of a Java IDE surely isn't requiring an obsolete Java? Plus RAD provides its own version - Java 8 - I can see it right there in its installation directory. Plus 9.6 was running fine.
Web searches seem to indicate this is Mac message rather than an Eclipse or RAD one, which makes sense given that it's not even trying to use RAD's copy of Java yet.
(I also opened a Ques
DougBreaux 270007SMYJ Visits (3256)
Missing IBM Websphere SSL class
I was simply trying to install an Eclipse plugin from the Eclipse Marketplace into my RAD on one system and RSA on another, but I kept getting this error:
Some web searches find that text. After a few unsuccessful attempts, the "alternative" solution from Cann
I guess RAD started and loaded up the WAS SSL support, but RAD itself isn't fully able to use that.
Note also the warning to "reverse" that activity if you want to run WAS again under RAD.
Relevant but not successful
DougBreaux 270007SMYJ Visits (4783)
(I'm assuming this is the same in stock Eclipse, I don't have it installed right now to confirm.)
If you have any source code that is generated by tooling (say, JAX-WS proxy code), you might have compiler warnings for things that are not considered best-practice. (Maybe they were fine in an earlier version of Java that the tooling still supports but are redundant in a later version.)
If you're like me and you prefer to have clean packages & classes in your IDE, here's a small tip that I somehow missed until recently.
If you place your "generated" source code in a separate source folder, which I like for ease of build process as well as organizational utility, you can also tell RAD to ignore compiler warnings for that source folder.
To do this, right-click on the source folder and go to Properties. Under "Java Compiler", check the "Ignore optional compile problems" setting, and you're done.
DougBreaux 270007SMYJ Visits (8782)
I imagine most folks who use Eclipse or its variants already know about this, but just in case...
User Libraries are reusable groupings of jar files that compose a particular library to be used by an application. This is a much easier way to manage the jars needed by your projects than simply adding them one-at-a-time to the Build Path and/or the WEB-INF/lib directory for execution on a local server.
Creating and Managing User Libraries
Window > Preferences > Java > Build Path > User Libraries
Add as many User Libraries as your applications require. Name them so that you can distinguish versions from each other when you work with applications that use different versions of the same library.
Use the "New" button and type a meaningful name, then the "Add JARs" button to locate specific jar files to include.
You can attach a javadoc URL to a library, which will give you more useful help within Eclipse when you're using that library. Expand the added jar file (the small triangle), select the Javadoc location line, and click the "Edit" button. You can point at either local javadoc files or a remote URL.
Similarly, you can attach a source code file or folder to a library, which will enable you to trace into its source if necessary.
Adding User Libraries to the Build Path
Project > Properties > Java Build Path
Adding User Libraries to the Execution Path (JEE Deployment)
Project > Properties > Deployment Assembly