Page History

...
The controller_install.xml file is explained with the code listing below. The comments included are intended to be self-explanatory.
Download: controller_install.xml
Code Block
language	xml
title	Configuration of the controller_install.xml file
linenumbers	true
collapse	true
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- 
XML configuration file for JS7 Controller setup

The JS7 Controller is available with a dual licensinglicense model.:
- GNU GPL 2v3.0 License, (see httphttps://www.gnu.org/licenses/gpl-23.0.en.html)
- JS7 Commercial License, (see licence.txt)

The setup asks you for the desired license model ,
(see below <entry key="licenceOptions" .../> below).

If you callrun the setupinstaller withand thisdo XMLnot filespecify thena youcommercial acceptlicense key
then at the same time you accept the terms of the
licence chosen license agreement. agreement under the GNU GPL v3.0 License.
-->
<AutomatedInstallation langpack="eng">
    <com.izforge.izpack.panels.UserInputPanel id="home">
        <userInput/>
    </com.izforge.izpack.panels.UserInputPanel>
    <!--com.izforge.izpack.panels.UserInputPanel id="licences">
        <userInput-->
        <userInput-->
        
            <!-- Select the license model (GPL or Commercial) -->
            <!--entry key="licenceOptions" value="GPL"/-->
            
            <!-- If you select 'GPL' as the license model than the licence must be empty.
                 Otherwise please add a license file if available.
        
         It is also possible <!-- Selectto add the license modelfile (GPL or Commercial) later. -->
            <!--entry key="licenceOptionslicence" value="GPL"/-->
            
        </userInput>
    </com.izforge.izpack.panels.UserInputPanel-->
    <com.izforge.izpack.panels.HTMLLicencePanel id="gpl_licence"/>
    <com.izforge.izpack.panels.HTMLLicencePanel id="commercial_licence"/>
    <com.izforge.izpack.panels.TargetPanel id="target">
        
        <!-- SELECT THE INSTALLATION PATH
             The installationinstaller expands this path with the JS7 Controller ID as a subdirectorysub-directory.
             The Itpath must be absolute!
             The default Forpath exampleis C:\Program Files\sos-berlin.com\js7\controller -->
        <installpath>C:\Program Files\sos-berlin.com\js7\controller</installpath>
        
    </com.izforge.izpack.panels.TargetPanel>
    <com.izforge.izpack.panels.UserPathPanel id="userpath">
        
        <!-- SELECT THE DIRECTORY FOR CONFIGURATION FILES AND LOG FILES
             The installationinstaller expands this path with the JS7 Controller ID as a subdirectorysub-directory.
             The path must be absolute!
             The Defaultdefault path is C:\ProgramData\sos-berlin.com\js7\controller -->
        <UserPathPanelElement>C:\ProgramData\sos-berlin.com\js7\controller</UserPathPanelElement>
        
    </com.izforge.izpack.panels.UserPathPanel>
    <com.izforge.izpack.panels.UserInputPanel id="network">
        <userInput>
        
            <!-- ID of the JS7 Controller -->
            <entry key="controllerId" value="controller"/>
            
            <!-- Choose 'yes' if the JS7 Controller instance is a standby Standby-Controller instance in a cluster -->
            <entry key="isStandby" value="no"/>
            
            <!-- Choose ('yes' or 'no)' wetherwhether the JS7 Controller should be started at the end of the after installation -->
            <entry key="launchController" value="yes"/>
            
            <!-- HTTP port of the JS7 Controller -->
            <entry key="controllerPort" value="4444"/>
            
            <!-- SetOptionally optionallyspecify an ipIP address or hostname. Itthat could beis used forto indicatingindicate which network 
                 interfacesinterface the JS7 Controller should listen to when using HTTP. If it is empty then 
                 itthe Controller listens to allany available network interfaces. -->
            <entry key="controllerHost" value=""/>
            
            <!-- The JS7 Controller will be installed as a Windows serviceService. You can set the service
                 account otherwise the local system account will be used. The account has to be
 the form 
              specified according to the pattern 'Domain\User'. -->
            <entry key="serviceAccount" value=""/>
            <entry key="servicePassword" value=""/>
            
        </userInput>
    </com.izforge.izpack.panels.UserInputPanel>
    <com.izforge.izpack.panels.UserInputPanel id="environment">
        <userInput>

            <!-- Directory where the JS7 Controller's log files are stored (default:
 
                (default: '[above userconfiguration path]\logs'). -->
            <entry key="logPath" value=""/>
            
            <!-- Directory where the JS7 Controller's pidPID file is stored (default:
 
                (default: above log path). -->
            <entry key="pidFilePath" value=""/>
            
            <!-- Working directory for all jobs which started by the JS7 Controller
                 e.g. %USERPROFILE% (default: [installation path]) -->
            <entry key="workPath" value=""/>
            
            <!-- The JS7 Controller requires a Java JRE at leastminimum version '1.8'. You can choose 
                 a different Java environment than the Java which is used during this installation. -->
            <entry key="javaHome" value=""/>
            
            <!-- SetOptionally optionallyspecify Java options (default: -Xmx500m). -->
            <entry key="javaOptions" value=""/>
            
        </userInput>
    </com.izforge.izpack.panels.UserInputPanel>
    <com.izforge.izpack.panels.UserInputPanel id="end">
        <userInput/>
    </com.izforge.izpack.panels.UserInputPanel>
    <com.izforge.izpack.panels.InstallPanel id="install"/>
    <com.izforge.izpack.panels.ProcessPanel id="process"/>
    <com.izforge.izpack.panels.FinishPanel id="finish"/>
</AutomatedInstallation>
...
Space shortcuts

Page tree

Versions Compared

Old Version 18

New Version 19

Key
