PS Default Install under Admin instance
Is the default install really under the Admin instance for App Server? I find this hard to believe since if I have to restart the portal server (to accept new authlessanonymous users), I have to do it from the command line?
Why was this decision made?
I would think you would have the portal under it's own instance, then admin under another?
We tried to get it working under another instance and it wouldn't work, any ideas or comments on this?
[472 byte] By [
barddzen] at [2007-11-26 6:23:52]
# 1
Sounds like installer is not able to see the other app server instances....I ran into the same problem.
I had to manually configure the portal to run under a seperate app server instance running in another domain.
Hopefully, someone in the know can comment on the installer picking only the default server instance.
# 2
We tried to get it working under another instance and ran into issues; right now, I just don't have time to monkey with it, but I see this as a pretty serious implementation flaw, bug, issue, etc...
# 3
The SUN installers in general are not robust. They assume that you want to install everything in the same instance (the DAS instance at that!) I recently attempted to install Sun Portal 7 into a seperate instance using Sun Application 8. The installer asks for the location of the instance root and docroot. (It diodn't even bother to ask if I wanted to deploy across a cluster). The install completed. I loged into the DAS console just to find that the targets of the war files was 'server' (the DAS instance) and all JVM configs were applied to that instance and not the instance I setup. However, the server policy and docroot were updated on the one I setup and not the DAS instance. Very disappointing.
