Red Hat Bugzilla – Bug 793431
Docs: Installation Guide
Last modified: 2012-02-28 11:33:44 EST
Affects: Documentation (Ref Guide, User Guide, etc.)
A tracker for issues relating to the EPP Installation Guide.
Please open separate JIRAs for new issues and link them to this tracker.
Link: Added: This issue is a dependency of JBEPP-455
No Release Note Required: JIRA pertains to documentation not product
Release Notes Docs Status: Added: Not Required
Link: Added: This issue depends JBEPP-569
Link: Added: This issue depends JBEPP-673
Chapter 2.2 - Location should be $JBOSS_HOME/server/[configuration]/deploy/ gatein.ear/02portal.war/WEB-INF/web.xml instead of $JBOSS_HOME/server/[configuration]/gatein.ear/02portal.war/WEB-INF/web.xml
Chapter 5.4.4 Setup Tomcat configuration - I think that this section should be removed in EPP installation guide, no sense to talk about Tomcat here. Only JBoss paragraph 5.3.4 should remain.
4.4. Disabling Authentication
- examples refer to HTTP GET and POST methods in web.xml
Fixed. Thanks Andrew.
In Section 2.1, it currently has: "Unfortunately existing JBoss Enterprise Portal Platform 5.0 or 5.0.1 installations cannot be upgraded in order to deploy JBoss Enterprise Portal Platform 5.1.0" Both EPP 5 and 5.0.1 can be upgraded to 5.1.0.
For SP installation guide, we need to mention that SP can not be installed with EPP 5.0 or EPP 5.0.1
The section "5.4.4. Setup Tomcat configuration to use your key" needs to be removed.
For mysql example, since there is example of DB create script for gateinjcr, there should be same for gateinidm. This way gatein-ds.xml will be more consistent and complete.
The section 2.1 about not upgrading has been removed and the Tomcat section had already been removed.
Sorry, but I'm not sure what you mean in your last comment. Can you explain a little more?
Should the command <mysql> CREATE DATABASE gateinjcr;> in step two of the "Creating a MySQL Database" procedure be repeated as <mysql> CREATE DATABASE gateinidm;>
That way the line "Do the same with gateinidm." would be replaced with an example of the step.
Is there more to it that should be documented? Should the whole procedure be repeated, and if so, what needs to be different?
Nope..that should be enough. Usually I like it when an example is complete so instead of "do the same with blah", it's better to say "do this". It's about same amount of work for you anyway. ;-)
Done. Thanks Prabhat.
- Just noticed that warning about disable POST method in login servlet before going to production is duplicated. Same thing is mentioned in section "2.3. Recommended Practices" and in section "4.4. Disabling Authentication" in the final paragraph "Disabling Pre-configured Accounts".
- Site publisher add-on is mentioned in both section "2.1. Upgrading and Add-ons" and in "Chapter 6. Installing Add-ons". I think it may be good to add all these informations into one section? Or at least add some link from section 2.1 into chapter 6 .
- There is still note "MORE INFO NEEDED HERE ON HOW TO DO THIS." in section "2.1. Upgrading and Add-ons". I believe that this is known issue so I am only reminding it :-)
The duplicated sections (Disabling the POST method the and mentions of Site Publisher) are ok to stay as they are. They're in context in those places.
Thanks for the shout about it though.
And the "MORE INFO NEEDED" para in sect 2.1 has been replace by some info.
Closing this JIRA as EPP core docs development is stopping for the 5.1.0 release.
For minor issues, please open a JIRA against EPP 5.1.1.
Only re-open this JIRA for blocker or critical issues.