Hi Mike
I have downloaded 2.1rc1 and put the two war files in one instance of
tomcat (5.5.9) on Linux Fedora Core 3. I found with trial and error
that
it is best to drop the author war file in to webapps, start tomcat, let
it bootstrap, stop tomcat, add the public war and then start tomcat
again. The public war always took longer to expand and build than the
author. I also found that to build the initial repository I needed to
increase the java heep size (iXmx) and set it to 2048M. After building
I
reset the size to 128 and the author environment worked, however in
case
the memory size was causing problems, I increased it to 512M
I dropped the war files into an empty tomcat 5.0.28 installation,
renamed them to testAuthor.war and testPublic.war and started up.
Everything runs fine.
You must increase the memory size before you bootstrap. After a out of
memory exception you must restart (clean up) the installation. To be on
the save side we provide always 512M.
Initially I renamed the war files to be catalyst and catalystAuthor but
when I was having problems I reverted to the original names to
eliminate
the change.
Renaming the war files leads to a new context name, this means that you
must reconfigure the Author instance after startup. You do this via the
GUI: config: /subscribers/SubscriberConfig/0001
I have changed the magnolia.root to magnoliaPublic.root in the public
web.xml and adjusted the log4j.xml file accordingly in the same
environment. I use the startup.sh script from within the bin directory.
This was really lack in the default public war file. how every it
should work fine anyway.
I am accessing the two environments using IE 6.0 on an XP machine
connected via a local LAN.
OK
In the author environment, I use superuser to create 2 website nodes
all
at the same level as features. I then activated these and they were
visible in the public environment.
OK
I then set up the role "guest" which has "read only" for "selected and
sub pages" for "/catalyst" and a user called "guest" which was assigned
the guest role. The user and the role were activated but a user
id/password dialog was not displayed for the public area and therefore
both catalyst and consultant pages are visible.
The login of the user is depending on the session. To loose the session
for sure you must exit the browser first.
I then changed Config: server/secureURIList/0001/URI to /.magnolia and
activated 0001 and below. This caused the sign-in dialog to appear in
public but a 403 error was reported.
To change the configuration for the public instance you must call:
http://localhost:8080/magnoliaPublic/.mangolia where you get the
configuration GUI. As far i understand, you want to reach a different
configuration on the public side.
By the way: the default configuration for the public side is /.magolia
I think you can solve you problem with:
- start you installation again (perhaps you get the tomcat bundled
package)
- add the users & activate them (as you did)
- go to the public instance and change server/secureURIList/0001/URI to
/*
Best regards
Philipp
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
