Win a copy of Node.js Design Patterns: Design and implement production-grade Node.js applications using proven patterns and techniques this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Preconfigured Install-Package

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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






 
author & internet detective
Posts: 40747
827
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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?
 
Heri Bender
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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.
 
You would be much easier to understand if you took that bucket off of your head. And that goes for the tiny ad too!
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic