|
Development Tools
I've settled on a few development tools to supplement the raw command line interface provided by USS. On this page, I'll discuss:
This page explains the desktop side of things. I use Windows 2000 Professional (service pack 3) for my desktop operating system. There are also several pieces on the mainframe. Please see the links page for information on other IDEs. If you have suggestions for other development tools (particularly any cool WSAD plug-ins), please let me know and I'll add these to the list.
This is IBM's IDE (integrated development environment) for developing java code, JSPs, EJBs, HTML pages, Ant scripts, and all kinds of java and J2EE things. It replaces IBM's previous IDE which was called Visual Age for Java which itself came in several "flavors" or editions called Entry, Professional, and Enterprise. WSAD is based on the IBM-developed open source Eclipse project. WSAD is implemented as a series of plug-ins that plug in to Eclipse. You can download a trial version of WSAD here. There are versions for Win2K, Win98, Linux, WinME, and WinNT.
Some people say that WSAD has a steep learning curve but I haven't found that to be the case. It is a relatively smooth transition from Visual Age for Java and there are lots of good articles on the internet and a tutorial built into the help system.
WSAD version 4 is the current generally available version. If you use WSAD, be sure to bring it up to the current service level and apply any of the further fixes that are appropriate. Downloadable service for WSAD version 4.x is here. WSAD 4 is based on Eclipse 1.0.
WSAD version 5 is available in an "early availability" edition. Everyone except IBM calls this a beta version. WSAD 5 is based on Eclipse 2.0 and has a lot of nifty features. Many of these are inherited from Eclipse 2.0 but many are inside WSAD 5 itself. In addition, a lot of little things have been cleared up from WSAD 4 to WSAD 5, such as project organization for web projects.
I really like the Eclipse IDE, especially Eclipse 2.0. It was developed by people who understand how programmers work. In addition, a number of items are customizable utilizing a preferences dialog. Therefore, my indenting style doesn't need to fit into somebody else's idea of how indenting should look. Since Eclipse 2.0 is open source with a lot of community input, it seems to be improving rapidly and frequently. Eclipse 2.1 is current scheduled for release in 1Q2003 and incorporates a lot of nice features as well.
Eclipse 2.0 supports a number of refactoring tools that really speed up and ease the refactoring process. Another nice feature is that it automatically cleans up compile errors!
The other thing that like a lot about Eclipse is that it integrates very nicely with CVS for version control. Other SCM vendors have developed their own plug-ins to interface with their source code management systems. The CVS interface in Eclipse 1.0/WSAD 4 was only fair (but usable) and it has improved significantly. Eclipse 2.1 promises additional improvements.
A related product is called WebSphere Studio Application Developer Integration Edition (WSAD IE). As far as I can tell, WSAD IE offers basically three things over plain WSAD: JCA connectors, Enterprise Services, and what are called Service Flows. Enterprise Services are a way of looking components as services. These components can be EJBs, JCA connectors, or components that support a SOAP interface, for example. Service Flows allow you link together various services to make more complex services.
WSAD IE is currently at release 4.1 which is built on top of WSAD release 4.0.3. WSAD IE uses some of the same plug-in names as WSAD except that they're actually different code. Therefore, WSAD fixes and enhancements cannot be applied to WSAD IE. The WSAD IE fixes and upgrades lag significantly behind WSAD and in some cases the WSAD fixes are never retrofitted into WSAD IE. If IBM wants WSAD IE to succeed, it needs to devote more resources to development and support, in my opinion. If I am buying a product that is more expensive than WSAD, there is no reason that I should have to wait weeks or monthds for WSAD fixes to be retrofitted. Also, there's no reason that I should have to make explicit requests of IBM to fix bugs in WSAD IE that have already been fixed in WSAD. Since I was unhappy with the support and since I don't use any of the features of WSAD IE at the moment, I've dropped back to WSAD. I cannot recommend WSAD IE in its current incarnation.
Yet another related product is WebSphere Studio Enterprise Developer (WSED). This is built on top of WSAD IE. It includes a Visual Builder, an improved version of the Visual Composition Editor of Visual Age for Java. It also supports a visual Struts development environment. WSED is currently at release 5 and became available in an Early Availability (ie beta) on September 30, 2002. I don't plan on using this either, at the moment.
Microsoft NT Services for Unix
Back in the early days of Visual Age for Java, Enterprise Edition for Windows, one needed a way to effectively access HFS files on the mainframe from the desktop. Today this problem is solved since SMB is included with OS/390 and z/OS. However, in the early days, there was no IBM-supported SMB server available for the mainframe. In order to effectively use the mainframe integration facilities of Enterprise Toolkit/390 for Visual Age for Java, Enterprise Edition for Windows, you needed an NFS client that connected with your USS NFS server, which IBM did provide. This allowed you to save files on the mainframe just as if the mainframe files were on any other network drive. You mapped a network drive to a certain node in the USS or in the MVS file system and then you just referenced files on that drive.
This required an NFS client since NFS was not natively supported by Windows. The client which I used most was something called Microsoft NT Services for UNIX, release 1.0. It was pretty straightforward to use. There are a number of other NFS clients out there and I've tried some of them. For shops which already license lots of Microsoft software, this seems to be the easiest and fastest way to get an NFS client from the purchasing and legal bureaucracies. Microsoft upgraded Microsoft NT Services for UNIX and released version 2.0 which did not work well with the IBM NFS server.
Fortunately at that time, IBM began to fully support SMB and introduced enough features to make it usable from Windows. Since NTSFU was no longer working properly, I switched over to SMB and haven't had any problems since. You can safely stay away from NFS.
The Rose Suites
I don't personally use any of the Rational tools. However, I've worked with people who have. These are the high-end standard for object-oriented design using the UML (Unified Modeling Language) and the associated RUP (Rational Unified Process). The centerpiece is Rational Rose, a visual modeling tool, that lets you draw UML models and generate some Java code from them as well. Rose is licensed most economically as part of one of the Rational Suites. Although quite expensive by PC standards, I think the DevelopmentStudio is probably the best choice of the suites for the Java for OS/390 developer. There is also a version that integrates with WSAD. The problem for me is that I mostly use UML to examine interesting problems with hand-drawn class diagrams or sequence diagrams. I really don't have a need or desire to document an entire system using UML at this point.
|