aspose file tools*
The moose likes JForum and the fly likes Preconfigured Install-Package Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » JForum
Bookmark "Preconfigured Install-Package" Watch "Preconfigured Install-Package" New topic
Author

Preconfigured Install-Package

Heri Bender
Greenhorn

Joined: Jan 07, 2011
Posts: 16
Hi

For a customer I want to provide a preconfigured install package without having the need of fulfilling the built in install wizard.

From reverse engineering I learnt that the install wizard starts if
- key "installation.config" not exists (or)
- File jforum-custom.conf not exists (or)
- key "installed" is not present or not set to TRUE

The "installation.config" key is provided in released SystemGlobals.properties, the jforum-custom.conf would be provided by my install package.

Studying the workflow of the install wizard, it seems that only the new admin password finds its way to persistence. Or is one of the settings into the several contexts also persisted?
Beside this: the key "install" is removed from templatesMapping.properties. But I assume this is not really important, neither the entry "Modified by JForum Installer". Is this assumption correct?

I plan to fulfill following steps while installing:
1. deploy the released jforum.war into tomcat 7
2. startup Tomcat, in order that JForum gets unpacked and deployed
3. stop Tomcat (before accessing the first time the jforums index.jsp)
4. setup the DB, incl. the hashed admin password
5. manually deploying the prepared jforum-custom.conf and other customizations
6. restart Tomcat

Is this a valuable approach?

Thanks for reviewing this draft. Please hint me on details which I probably missed.

Heri Bender






Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 29287
    
140

Beside this: the key "install" is removed from templatesMapping.properties.

I'm pretty sure this happens so someone doesn't accidentally re-run the install. I think you should remove it in your pre-configured version.

Your approach seems reasonable. How are you providing the admin password to be hashed? Prompting the user in a script?


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Heri Bender
Greenhorn

Joined: Jan 07, 2011
Posts: 16
I think you should remove it in your pre-configured version

You probably right.
How are you providing the admin password to be hashed? Prompting the user in a script?

Probably. Not sure yet.

Thanks anyhow for your review. Meanwhile I found the "Manual installation guide" in the google WIKI which more or less describes the same steps.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Preconfigured Install-Package
 
Similar Threads
Upgrading to version 2.1
Searching chinese is actually working
JForum 2.1.8 - Admin Access
Jforum SSO - restrict direct forum access => redirect to login page if not loged in please help!!!
Error: Send a test email