I'm trying to find out how to get iPlanet to use a JVM that's not the default JVM because I'd like to see what happens on a test port to our app if I upgrade from 1.3 to 1.4 before I actually make a system-wide change. I was hoping that there would be a simple place to specify the path to the JVM, but if there is such a simple place, I haven't seen it yet. So, off to the web I go looking for documentation. I found the iPlanet Web Server, Enterprise Edition Programmer's Guide to Servlets: Appendix C JVM Configuration, which hasn't solved my problem, but did offer the following information about setting additional JVM settings:
I am amused.
However, if you need to specify settings for the JVM, such as additional classpath information, you can configure the JVM properties for iPlanet Web Server via the Administrator interface. You can add as many other properties as you want to (up to 64).So, which is it -- can I add as many other properties as I want to, or am I limited to 64? They could have completely left out that part about "as many other properties as you want."
I am amused.
Profile
drmellow- Greg Cohoon
- Knitting Daddy
Page Summary
- chown_me : (no subject) [+1]
- tldz : (no subject) [+3]
- (Anonymous) : (no subject) [+1]
- bodnej : (no subject) [+2]
Comments
Their product is poo, and their documentation matches.
Of course, though, using a different JVM ought to be as simple as setting the relevant environment variables.
Of course, though, using a different JVM ought to be as simple as setting the relevant environment variables.
Well, it is that easy. Except that setting the relevant environment variable (JAVA_HOME, in this case) changes the JVM configuration for every web application being run by the instance of iPlanet, which in this case is unacceptable. I only want to change one of the (about a dozen) instances. My solution will be to install a duplicate instance of iPlanet, configure it for different ports, and change it there, leaving the JVM in our current dev environment untouched.
It's absolutely stupid that I have to do it like this. But that's what happens when you use a product that is composed mostly of poo.
And, yes, I eventually found the JVM path configuration under "Global Settings." Unfortunately, that's not acceptable because we are using iPlanet to serve about a dozen different instances of the app. (It's a dev environment and each developer gets their own instance.) I only want to upgrade the JVM path for one of those instances, but changing it under "Global Settings" will screw up the environment for all my coworkers (which is tempting, but...).
Instead, we're going to install an entire separate instance of iPlanet on the box and I'll play around there.
Or am I completely misunderstanding what you are trying to do?
To their credit, in newer versions of iPlanet, you can do what I wanted to do. But when we upgrade our app server, it'll be to Apache/Tomcat, not to a newer version of iPlanet.