Sun Java System Application server in a zone

crisostomo_enrico · 11-08-2007, 09:41 AM

Hi.

I'm using SJSAS 9.1 installed in /opt/SUNWappserver, in Solaris Express Developer Edition 09/07. The application server was included in the system, and I use instead of the old /usr/appserver.

After booting a new sparse zone, whose purpose is running the application server, I realized that /opt/SUNWappserver was missing in the non global zone:

Quote:

# ls /opt
SUNWjavadb SUNWmlib SUNWspro csw staroffice8

The questions are:
- Why isn't SUNWappserver created in the non global zone, while, for example, SUNWspro and SUNWjavadb are?
- What's the best way to install it in the non global zone? Maybe with an inherited-pkg-dir and then creating the domain in the zone?

Thanks,
Enrico.

jlliagre · 11-08-2007, 05:22 PM

I haven't a Developer Edition to check it but I suspect this /opt/SUNWappserver directory doesn't belong to a package so isn't propagated to the zones.

You should be able to install it on the non global zone as /opt is read-write.

crisostomo_enrico · 11-12-2007, 04:39 AM

Thanks jlliagre.

Quote:

You should be able to install it on the non global zone as /opt is read-write.

It's true indeed. But if I wanted to use the one which is installed in the global zone, in order to propagate its upgrades, wouldn't it be viable to inherit /opt (of the global zone) in a read only directory in the local zone and run it from there? Do you see any problem with this approach? I tried to google 5 seconds for it and found this:
http://developers.sun.com/appserver/...szones/#global

I would say there's no problem about it.

Bye,
Enrico.

jlliagre · 11-12-2007, 03:41 PM

Quote:

Originally Posted by crisostomo_enrico

Thanks jlliagre.

It's true indeed. But if I wanted to use the one which is installed in the global zone, in order to propagate its upgrades, wouldn't it be viable to inherit /opt (of the global zone) in a read only directory in the local zone and run it from there? Do you see any problem with this approach?

Yes, /opt should be read-write by design, and you are missing /var/opt and /etc/opt in your approach.
Inheriting a package is different than sharing a directory.

Quote:

I tried to google 5 seconds for it and found this:
http://developers.sun.com/appserver/...szones/#global

I would say there's no problem about it.

This page is discussing about packaged installations while I was understanding yours was file based. I now think they were real packages, but with propagation disabled as described in the linked page.

crisostomo_enrico · 11-13-2007, 10:40 AM

Thanks jlliagre.

Quote:

Yes, /opt should be read-write by design, and you are missing /var/opt and /etc/opt in your approach.
Inheriting a package is different than sharing a directory.

Yes, I missed that.

Quote:

This page is discussing about packaged installations while I was understanding yours was file based. I now think they were real packages, but with propagation disabled as described in the linked page.

Well, in prodreg I couldn't find any SJSAS installed in /opt (well, neither found I a SJSAS v. 9): it only appears the one installed in /usr/appserver. I think I'm missing something...

Thanks,
Enrico.