DeveloperInstall

From DOC

Jump to: navigation, search


THIS IS OBSOLETE - APPLICABLE TO Beta4

Contents

Installation

  • To create an installer, first cleaning out all compiled code, but not running the installer (tolven/build.xml targets)
    • clean-build-create-automated-installer, places the zip installer in tolven/installer
    • Extract zip, and execute the install.bat or install.zip file to get IzPack. There is a -headless option which works fine on linux. Although it also works on windows, the process does not appear to exit until the user does a CTRL-C after all the disk crunching is over (to be fixed). Then it prints that it was done all along.
    • Now you should have a new installation directory (never install into the old one) and your old tolven-config directory will be fine if it already existed
    • NB: the tolven-config directory is not configured for the new installation at this stage
  • To create and run an installer, first cleaning out all compiled code, and then running the installer (tolven/build.xml targets)
    • clean-build-create-run-automated-installer, places the zip installer in tolven/installer
    • The target will automatically create a new installation directory (tolvenYYYYMMDDHHSS) without intervention
    • Now you should have a new installation directory (never install into the old one) and your old tolven-config directory will be fine if it already existed
    • NB: the tolven-config directory is not configured for the new installation at this stage
  • To create and run an installer, leaving compiled code (for quicker incremental compiles, with the usual risk of not starting clean), but not running the installer (tolven/build.xml targets)
    • build-create-run-automated-installer, places the zip installer in tolven/installer
    • The target will automatically create a new installation directory (tolvenYYYYMMDDHHSS) without intervention
    • Now you should have a new installation directory (never install into the old one) and your old tolven-config directory will be fine if it already existed
    • NB: the tolven-config directory is not configured for the new installation at this stage
  • To create and run an installer, first cleaning out all compiled code, ant then running the installer (tolven/build.xml targets)
    • clean-build-run-installer, places the zip installer in tolven/installer
    • You will be prompted for the installation directory in the normal IzPack mode
    • NB: the tolven-config directory is not configured for the new installation at this stage

GUI Configuration

  • Run the GUI Configuration Manager from the Start menu

Command Line Configuration

  • For automated configuration from the command line, there are three stages, which can be found by executing:
    • tolvenClient configPhase1 -help -conf c:/tolven-config
    • You can also read the tolvenDocs for linux installs, which is now by definition, all be command line

Eclipse Workspace Ant Target Configuration

  • The only problem with this technique is that currently the targets are running their own jvm and not using any parameters which might be in the tolvenClient shell file in the installation directory. It doesn't really hurt right now, but is worth bearing in mind.
  • Simulated CM
    • tolven/build.xml target: run-cm
  • Simulated Command Line
    • First before any configuration can begin, you need to ensure that the same step which occurs when you select a configuration in the Server tab, happens here too, otherwise you will fail. That is done by attempting to run the tolven/build.xml target run-configPhase1. It will fail if you do not provided a simple custom XML properties file in your workspace, with at least the active.appServerId property in it.
    • If run-configPhase1 succeeds, you can then move onto run-configPhase2 (which only creates schemas in the DB, which you probably don't remove often anyway). It does not hurt to run it always...it will say of the DB schemas are there already.
    • Then you should be able to restart openldap and postgresql (the latter does not seem to need a restart on windows).
    • Finally run-configPhase3 finishes off the install right up to the uploadAll command.
    • A few seconds after this last step you should be able to log into Tolven
Personal tools