opendev/gerrit
Code Issues Proposed changes

Fix the order of steps in the J2EE Installation document

Browse Source 
It is better to first define the JNDI data source in the application
server and then deploy Gerrit than opposite. This should avoid errors
like "No DataSource" on the first deployment.

Change-Id: I89a2d1ab11bf0f7a44ee62f6d9083ab83bdd25a6
Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
This commit is contained in:
Sasa Zivkov 2013-02-05 17:28:40 +01:00
parent 70f4853152
commit 3b61df35a0
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/install-j2ee.txt
View File

@ -27,12 +27,6 @@ Installation
review_site/bin/gerrit.sh stop review_site/bin/gerrit.sh stop
---- ----
* Deploy the 'gerrit.war' file to your application server.
+
The deployment process differs between servers, but typically this
can be accomplished by copying 'gerrit.war' into the 'webapps/'
subdirectory of the container's installation.
* Configure JNDI DataSource 'jdbc/ReviewDb'. * Configure JNDI DataSource 'jdbc/ReviewDb'.
+ +
This DataSource must point to the database you created above. This DataSource must point to the database you created above.
@ -40,6 +34,12 @@ Don't forget to ensure your JNDI configuration can load the
necessary JDBC drivers. You may wish to ensure connection pooling necessary JDBC drivers. You may wish to ensure connection pooling
is configured and enabled within the DataSource. is configured and enabled within the DataSource.
* Deploy the 'gerrit.war' file to your application server.
+
The deployment process differs between servers, but typically this
can be accomplished by copying 'gerrit.war' into the 'webapps/'
subdirectory of the container's installation.
* ('Optional') Install Bouncy Castle Crypto API * ('Optional') Install Bouncy Castle Crypto API
+ +
If you enabled Bouncy Castle Crypto during 'init', copy the JAR If you enabled Bouncy Castle Crypto during 'init', copy the JAR