A Installing a Development Client from the Command Line

Caution:

Be sure to follow the guidelines in the preceding sections of this guide entitled:

Instead of using the OUI-based installer in interactive mode for the Development Client, optionally you can run the installation from the Microsoft Windows command line. This may be more efficient if you have many Development Clients that you need to install.

The OUI installer for the Development Client is setup.exe, which is located in this directory:

\\<deployment server name>\<release>\OneWorld Client Install\install

You can provide options to the setup.exe on the command line. Most of the options are generic OUI options, but a few are specific to the EnterpriseOne Development Client installer.

You can enter the following line to get a list of and descriptions of the generic OUI options:

\\<deployment server name>\<release>\OneWorld Client Install\install\setup.exe -help

Below is an example command line string using some of the available options (which are listed and described later in this section). The command should be entered on a single contiguous line with no line breaks or returns:

setup.exe -debug -force PACKAGE_NAME=DV910FA E1_INSTALL_MODE=Compact ORACLE_HOME=c:\E910 ORACLE_HOME_NAME=JDE_E910_Client

Below is a list of the most useful generic OUI options:

  • -logLevel

  • -debug

  • -force

  • -help

  • -silent

  • ORACLE_HOME

    • Directory where EnterpriseOne will be installed

    • Required

    • Must be of the form ORACLE_HOME=installation_directory

    • Case sensitive

  • ORACLE_HOME_NAME

    • Name of the Oracle Home directory.

    • Required

    • Must be of the form ORACLE_HOME_NAME=name

    • Case sensitive

Note:

Any generic options other than those listed above have not been tested with the EnterpriseOne Development Client installer.

The EnterpriseOne-specific options are specified as KEY=value pairs. The keys are case sensitive.

The following table lists the command line options for OUI for the Development Client.

Key Description Case Sensitive? Required? Example
E1_USER EnterpriseOne user account No Yes, if installing an update package that has XML specs stored in the database. E1_USER=JDE
E1_PASSWORD EnterpriseOne user password. Must be specified in plain text; it cannot be encrypted). Yes Yes, if installing an update package that has XML specs stored in the database. E1_PASSWORD=MyPassword
PACKAGE_NAME Name of package to install. Yes Yes PACKAGE_NAME=DV910FA
E1_INSTALL_MODE Indicates which EnterpriseOne objects to include in the installation.

Valid values are

Typical = include the pathcode's development and production objects (default).

Compact = include the pathcode's production objects only.

 Yes No E1_INSTALL_MODE=Compact
COPY_FILES Specifies whether package's files should be copied to the target.

Valid values are

A string starting with 'N', 'n', 'F', or 'f' = do not copy the files

Any other string = copy the files (default)

Useful if you are repeating an installation that failed after all files were copied to the target machine.

 No No COPY_FILES=Y