David Ogren

Yes, Sun ONE is both a conceptual architecture ,based on ebXML, J2EE, SOAP, etc., and a product brand for all of Sun's non-OS software. So it's even more expansive than you are suggesting: the Sun ONE brand covers non-Java products like email servers, integration servers, and mail servers.
So, I guess it is a little like MSFT's .NET branding. (Except it isn't vaporware.) And, I suppose, we are having similar successes and challenges with managing a brand that diverse. But at least it is less confusing than the equally diverse iPlanet brand.
--
David Ogren
Desert Topping and Floor Wax Specialist for Sun ONE

Not that I'm aware. And I doubt that there ever will be one given the nature of Eclipse. Sun probably won't write one because Eclipse is such a direct competitor to NetBeans. (The name Eclipse is pretty antagonistic in its own right.) And IBM isn't likely to a plugin either, given that S1AS is a competitor to WebSphere. And if you are talking about iAS 6.5 rather than S1AS 7.0, there's even less of a chance.
Sorry to be the bearer of bad news.

I'm not an expert in iWS (I generally focus on iAS), but this question was answered in another forum so I have the link handy.
Apparently this was a known issue that was resolved in iWS 6.0sp5 by adding some new magnus.conf directives. Docs for the directives can be found here : http://docs.sun.com/source/816-6434-10/rn60sp5.html#1021838
David

Just so that you aren't disappointed ...
I cover iAS 6.x in my book. And iAS 6.x uses either JDK 1.2 (6.0.x) or JDK 1.3 (6.5.x). I do mention JDK 1.4 a couple of times. Essentially to give the reader a heads up about maintaining future compatability (specifically about JDK 1.4 logging and assertions). But I don't go into too much detail because 1.4 isn't an available option for iAS 6.x.
[ February 02, 2003: Message edited by: David Ogren ]

I haven't done the JNDI tutorial, so I can't really give you any feedback on whether it is worth the effort. And the LDAP server is part of the tutorial whether you use Sun ONE's application server or not, so the question of whether getting Sun ONE going is probably irrelevant. LDAP wouldn't be a bad thing to have a working knowledge of anyway, it's getting to be a pretty ubiquitous technology.
Here are some answers to your questions, though:
OpenLDAP has been compiled on Windows. information here, precompiled binaries here.
Sun ONE does have a commercial LDAP server. In fact, it is a very common (70%+ market share) commercial implementation. Evaluation download here.

Which version? Application Server 7.x?

IIRC, session.setMaxInactiveInterval is not supported by iAS and calls to it will be ignored.
On the other hand, I can't tell you why you are getting timed out early. There are some issues (largely when the reaper thread is overloaded) where timeouts don't happen promptly, but I can't say I've heard of any issues where it is happening too soon.

It looks like you have an invalid deployment descriptor. The first error of the stack trace appears to be:
[exec] PMSSYK.hq.cias.com.sg:10 SAXException [exec] Severity 1: DeployLogListener:10 org.xml.sax.SAXParseException: Expected "</session>" to terminate element starting on line 7.
It appears that the SAX parser within the deployment process cannot find a needed </session>.
David

It doesn't matter. Ant is 100% Java based so you don't have to worry about platform issues as long as you have a JVM. (version 1.2 or better is needed for some tasks.)
Pick the TAR, GZ, or ZIP based on what decompression tools are available on your box.

The commit B reference must be a typo in the DTD of the Pet Store. iAS will accept Option B as a viable option, but it is not supported and iAS will treat it as Option C.
DSYNC-Local means that sessions are stored in the DSYNC engine of the KXS, but they are not distributed to other KXS's. So you will have session failover within the instance (from KJS to KJS) but not across instances.
David

The ejb-name attribute in the ias-ejb-jar.xml file defines the name of the EJB in JNDI.
David

Sorry, but it can't be done. Null is not a valid context root.
David

Q #1 (why does iAS put the class files under APPS)
The WAR is a standalone snapshot of your application. It does not contain a "pointer" back to your development directory. In production, you won't have your development classes available on the same box. And even if you did, you wouldn't want production to update any time you changed a .class file.
The standard development cycle (excluding SCM) outlined by J2EE is develop -> compile -> assemble -> deploy. So you _will_ have multiple copies of you .class files. One in the development environment. One in the assembly environment (embedded in the WAR), and one in the production (deployment) environment.
By the way, I'd recommend assembling the WAR into the EAR. It resolves some of the missing items in the WAR, such as context root.
Q#2 (how do I make iAS pick up .class changes, since APPS is a separate copy.)
Personally, I use a "quick deploy" Ant target that copies the files from my development environment to my unit test environment. Since it is just a file copy, it is effectively instantaneous.
Alternatively, you could change your compilation options to compile directly into APPS, but this doesn't seem like a good idea to me.
Q#3: (I don't want to use deploytool repeatedly.)
You aren't alone. GUIs are never good for repeated use. Most people I know use deploytool to generate the original deployment descriptors (if at all) and then use command line tools from then on.
The one I recommend, and talk about in my book, is Ant. There are plenty of samples of Ant build files provided with iAS. You could use make, or any number of other tools, but Ant has built in Java compiler and WAR file support.
One you have a web.xml file and ias-web.xml file (and whatever other DD's you need), you can just assemble the WAR file by hand if you choose.
Q#4 (step-by-step examples)
Most of the iAS samples walk you through deployment step by step. That will give you an idea of how to use Ant.
Chapter 9 of my book also goes through many of these steps. It specifically details how to create an Ant "hot deploy" target, the concepts and purposes of application packaging, and what is happening behind the scenes of the APPS directory.
David

Well, I'm not sure that those superclasses were ever documented. So you may be out of luck. I'm not exactly sure what you are trying to do with setSessionVisibility, but I'd make sure that I had my J2EE deployment descriptors are set as well. It's possible that the J2EE security of 6.x is overriding the settings of these 2.x APIs.
What might be useful to you, however, is the iPlanet Migration Toolkit. (Or whatever we are calling it today.) You will have to get it from your local Sun ONE SE, but it should make porting your application a snap. It does some code conversion, and it also has some runtime libraries that support the Kiva functionality.
David

What are you trying to do? If you have a copy of NAS 2.1, you should already have the docs, right?
Or are you trying to migrate an old 2.1 application, and are trying to find a way to port the API's? (You can't just copy the JAR files, since they hook deep into the internals of the appserver.)
Anyway, the old NAS 2.1 (aka Kiva) API has remained largely unchanged. You can look here : Kiva API, in the iAS docs if you need an API reference. I just wouldn't recommend spending a lot of time with these API's since they are completely deprecated.
David