Configuring automated, file-based deployment

The Deployment Template supports a file-based configuration option to simplify the deployment of an EAC Application. This automation may be especially useful during development, when the deployment process must be repeated many times.

You can create a deployment configuration file that contains name/values that satisfy the deploy script prompts, so you do not have to respond to the prompts manually. You specify the deployment configuration file as an argument to the --install-config flag when you run the deploy script.

The deployment configuration file should specify the application name, deployment path, deployment type, and all ports. The following example specifies the installation of a Dgraph deployment named Discover: 

<install app-name="Discover">
  <deployment-path>/localdisk/endeca/apps</deployment-path>
  <base-module type="dgraph" />
  <options>
    <option name="eac-port">8888</option>
    <option name="workbench-port">8006</option>
    <option name="dgraph1Port">15000</option>
    <option name="authoringDgraphPort">15002</option>
    <option name="logserverPort">15010</option>
    <option name="jps-config-location">ToolsAndFrameworks/<version>/server/workspace/credential_store/jps-config.xml</option>
    <option name="application-export-directory">ToolsAndFrameworks/<version>/server/workspace/state/repository</option>  
  </options>
</install>

To configure automated/file-based deployment:

  1. Start a text editor, create a new text file, and copy/paste the example above.

  2. If necessary, modify the default port values for the EAC Central Server, Workbench, Live Dgraph, Authoring Dgraph, and the Log Server to new values.

  3. Save and close the file.

  4. Run the deploy script and specify the --install-config flag and the location of the deployment configuration file.

    The following example specifies the deployment descriptor (deploy.xml) for a version of the Discover Electronics reference application, then the --install-config flag with an argument to the deployment configuration file (app-install-config.xml): 

    ./deploy.sh --app /localdisk/endeca/ToolsAndFrameworks/*/reference/discover-data/deploy.xml --install-config
			 /localdisk/infrontSetupScripts/config/app-install-config.xml --no-prompt

When a configuration file is specified for the Deployment Template, the deployment attempts to retrieve and validate required information from the document before proceeding. If any information is missing or invalid, the Deployment Template prompts for that information. To truly automate the install process, the --no-prompt flag may be passed to the installer, instructing it to fail (with error messages) if any information is missing and to bypass interactive verification of the Guided Search version.

Copyright © Legal Notices