Description of problem: Per case number 532381, a US Army customer performing an evaluation of EPP+SP was confused on the point of needing separate repositories for IDM, EPP, and SP. He had combined EPP/SP into a single repository which would not work. Please clarify in the documentation that separate repositories are required. Version-Release number of selected component (if applicable): EPP/SP 5.1.0
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: An issue was found in the Site Publisher Installation Guide regarding the requirement for Site Publisher to have a separate database to Enterprise Portal Platform. A customer identified an issue with the clarity of this information when they encountered a problem with database provisioning for the platform. The Site Publisher Installation Guide has been merged with the Installation Guide. A step has been added to the Database Configuration section, which specified the need for a Site Publisher database separate to IDM and JCR.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -An issue was found in the Site Publisher Installation Guide regarding the requirement for Site Publisher to have a separate database to Enterprise Portal Platform. A customer identified an issue with the clarity of this information when they encountered a problem with database provisioning for the platform. The Site Publisher Installation Guide has been merged with the Installation Guide. A step has been added to the Database Configuration section, which specified the need for a Site Publisher database separate to IDM and JCR.+An issue was found in the Site Publisher Installation Guide regarding the requirement for Site Publisher to have a separate database to Enterprise Portal Platform. A customer identified an issue with the clarity of this information when they encountered a problem with database provisioning for the platform. The Site Publisher Installation Guide has been merged with the Installation Guide. A step has been added to the Database Configuration section, which specifies the need for a Site Publisher database separate to IDM and JCR.
Included in the changes pushed for https://bugzilla.redhat.com/show_bug.cgi?id=794386
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -An issue was found in the Site Publisher Installation Guide regarding the requirement for Site Publisher to have a separate database to Enterprise Portal Platform. A customer identified an issue with the clarity of this information when they encountered a problem with database provisioning for the platform. The Site Publisher Installation Guide has been merged with the Installation Guide. A step has been added to the Database Configuration section, which specifies the need for a Site Publisher database separate to IDM and JCR.+An issue was found in the Site Publisher Installation Guide regarding the requirement for Site Publisher to have a separate database to Enterprise Portal Platform. A customer identified an issue with the clarity of this information when they encountered a problem with database provisioning for the platform. The Site Publisher Installation Guide has been merged with the Installation Guide. The Database Configuration section has been extensively reworked to specify Site Publisher must have its own IDM and JCR database configured, and matching database connector JNDI name directives specified in gatein-ds.xml