Updating the InstallManager.htm File
To install a database or the Development Client onto a Development Client machine, the user runs this program:
\\<deployment server name>\<release>\OneWorld Client
Install\InstallManager.exe
This program displays a Graphical User Interface that provides several options for the
user to perform. The options that InstallManager.exe
displays are read
from the file InstallManager.htm
that resides in the same directory as
InstallManager.exe
.
The JD Edwards EnterpriseOne administrator can edit this file to rename the options or to add new options. Instructions are inside the file.
InstallManager.htm
is in HTML format, it is a restricted HTML
that the InstallManager.exe
can read. Some text file editing
programs add extraneous HTML tags that InstallManager.exe
cannot
recognize. The Microsoft Windows program Notepad.exe
is an
example of a program that is known to not add these extra tags, making it safe to
use. Before you make any changes to the file, it is good practice to save a copy in
case any changes that you make are not recognized by
InstallManager.exe
when it reads it.Note that the installation path of the Development Client's installer
(setup.exe
) changed with Tools Release 9.1. This means that you
will need to change the path of the Development Client's installer in the
InstallManager.htm
when you first install Tools Release 9.1 and
greater onto a Deployment Server that has a tools release prior to 9.1 installed.
The following is an example of a line in a pre-9.1 InstallManager.htm
that creates the link to install the Development Client (this should be on a single
line):
<a class="sectionItem" id="LaunchLink" link="setup.exe"
href="InstallManager.htm">EnterpriseOne Client</a>
The Development Client's installer prior to Tools Release 9.1 is called
setup.exe
. It should be in the same directory as
InstallManager.exe
and InstallManager.htm
. The
value of the link in the above line should be a path and executable for the installer.
If a relative path is used (for example, the path starts with neither a drive letter
followed by a colon nor a backslash), the path is relative to the location of
InstallManager.exe
. If no path is given, Setup.exe
and InstallManager.exe
are in the same directory.
Here is an example of a similar line for Tools Release 9.1 and greater (this should be on a single line):
<a class="sectionItem" id="LaunchLink" link="install\setup.exe"
href="InstallManager.htm">EnterpriseOne Client</a>
Note the addition of this relative path: install
. With Tools Release 9.1
and greater, the Development Client's installer (which, is also called
setup.exe
) is now located in a subdirectory called
install
under the path where InstallManager.exe
resides.