Skip to content

Commit 7098e0f

Browse files
author
Vladimir Kotal
authored
move more content about webapp config to wiki
1 parent 17eea3d commit 7098e0f

File tree

1 file changed

+1
-43
lines changed

1 file changed

+1
-43
lines changed

README.md

Lines changed: 1 addition & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -521,49 +521,7 @@ java -cp ./opengrok.jar org.opensolaris.opengrok.search.Search
521521

522522
## 7. Change web application properties or name
523523

524-
You might need to modify the web application if you don't store the
525-
configuration file in the default location
526-
(`/var/opengrok/etc/configuration.xml`).
527-
528-
To configure the webapp `source.war`, look into the parameters defined in
529-
`WEB-INF/web.xml` of `source.war` (use jar or zip/unzip or your preferred zip
530-
tool to get into it - e.g. extract the `web.xml` file from `source.war` (`unzip
531-
source.war WEB-INF/web.xml`) file, edit `web.xml` and re-package the jar file
532-
(`zip -u source.war WEB-INF/web.xml`) ) file and change those `web.xml`
533-
parameters appropriately. These sample parameters need modifying(there are
534-
more options, refer to manual or read param comments).
535-
536-
* **CONFIGURATION** – the absolute path to XML file containing project configuration
537-
(e.g. `/var/opengrok/etc/configuration.xml`)
538-
* **ConfigAddress** – port for remote updates to configuration, optional, but advised(since there is no authentication)
539-
to be set to `localhost:<some_port>` (e.g. `localhost:2424`), if you choose `some_port` below 1024 you have to have
540-
root privileges
541-
542-
If you need to change name of the web application from source to something
543-
else you need to use special option `-w <new_name>` for indexer to create
544-
proper xrefs, besides changing the `.war` file name. Be sure that when this
545-
changed you reindex cleanly from scratch. Examples below show just
546-
deploying `source.war`, but you can use it to deploy your `new_name.war` too.
547-
548-
Deploy the modified `.war` file in glassfish/Sun Java App Server:
549-
550-
* **Option 1**:
551-
Use browser and log into glassfish web administration interface: Common Tasks / Applications / Web Applications
552-
, button Deploy and point it to your `source.war` webarchive
553-
554-
* **Option 2**:
555-
Copy the `source.war` file to
556-
`GLASSFISH/domains/YOURDOMAIN/autodeploy` directory, glassfish will try
557-
to deploy it "auto magically".
558-
559-
* **Option 3**:
560-
Use cli from GLASSFISH directory:
561-
562-
```bash
563-
./bin/asadmin deploy /path/to/source.war
564-
```
565-
Deploy the modified `.war` file in tomcat:
566-
just copy the `source.war` file to `TOMCAT_INSTALL/webapps` directory.
524+
See https://github.com/oracle/opengrok/wiki/Webapp-configuration
567525

568526

569527
## 8. Information for developers

0 commit comments

Comments
 (0)