I was looking for a way to implement web installer mode which would be running just after unpacking of archive. The easiest and I think the best way would be to add example etc/init.properties file which would configure only HTTP API component so it could start web installer mode.

This simplified etc/init.properties config file could contain only following lines:

--comp-name-1=http
--comp-class-1=tigase.http.HttpMessageReceiver

This are all informations needed to setup HTTP API component with setup module ready. This way we would have this module running all the time (during initial installation and during normal operation of Tigase XMPP Server) without introduction of dependency in which Tigase XMPP Server would depend on Tigase HTTP API which would create circular dependencies. Also this way we will have it working in OSGi mode in the same way.

I have just updated default init.properties files in our code repo. However, one minor problem is that, it needs HTTP API component jar to work. This would be the case for our public binary packages, so not much of an issue.

Please note, that tigase-http-api is currently only bundled with installer and -dist-max package so it won't work with bare-boned -dist package. Shall we include the component in it?

Eric, please test this feature, how it works, support for different databases, preparing configuration, etc... Verify if this feature is "consumer" ready.

Also while you run all these tests, please also work on a "user guide" document describing how to install and configure Tigase using the Web installer mode.

%kobit What form should the guide be? Wiki, Blog, AsciiDoc?

I would like it to be a part of this document: http://docs.tigase.org/tigase-server/snapshot/Administration_Guide/html_chunk/

We can have a chapter: "Installation using web UI installer" or something like this.

I've commited an AsciiDoc userguide to the repo, the page should be generated in tonights build. Derby, and MySQL work fine. There were a few hitches with Postgres which were discussed in another thread https://projects.tigase.org/issues/2605.

The guide looks quite OK. A few remarks.

For the Tigase startup command it is better to specify tigase.conf file explicitly, like this:

$ scripts/tigase.sh start etc/tigase.conf
$ scripts/tigase.sh stop etc/tigase.conf

Also, it also worth mentioning about possible changes in the tigase.conf file, mainly how to increase memory for Tigase as this is the most common thing to do after installation is complete.

I left tigase.conf out because when I tried to run the server initially, from a fresh download, with scripts/tigase.sh start etc/tigase.conf: it wouldn't run because JAVA_HOME was wrong. I wanted to see if Tigase would pick that up from the envirnoment using scripts/tigase.sh start and it did.

I've checked in updated documentation with your suggestions.