NOTE: The components installed by the Framework EDI installers may change from one version
to the next. The components listed in this documentation apply to this version
only.
When installing, a path has to be specified as the target folder where all
the files are to be copied to. The target folder is further subdivided
into the following:
BIN. This folder contains the core library, program
executables and documentation that make up the product.
SAMPLE. This folder contains the sample programs if any are
provided. Otherwise this folder is not created.
TEMP. This folder may or may not be created. The programs initially determines the user's temporary folder first and
uses that folder for temporary files, otherwise the TEMP folder is created
under the target path.
WARNING: If the TEMP folder is created, DO
NOT save important files in the TEMP folder. Files will be erased under this
folder. Also, the TEMP folder could also be
completely deleted when the Framework EDI product is uninstalled -- erasing all files and folders
created under it.
The following components are installed to the target path.
Edidev_SEC.dll. This file is the Standard Error Code library
that provides description of error codes generated throughout the
product. If this DLL is missing the error generated will not have an
error description, and in some cases the program may abnormally
terminate. This DLL must be located in the same path as the component
or executable file that is using it, and, in general, it should always be
located in the target folder. This file is installed by all product
installer, and must be deployed with the application.
EDIdEv_eAnalyzer.exe. This executable file is the eAnalyzer
utility. Not available on some installers.
EDIdEv_eFileManager.exe. This executable file is the
eFileManager utility. Not available on some installers.
EDIdEv_SefManager.exe. This executable file is the SefManager
utility. Not available on some installers.
EDIdEvHelp.chm. This file is the on-line documentation.
Not available on some installers.
eSecurityConsole.exe. This executable is the eSecurity
Console utility. Not available on some installers.
FrediAs2Isapi.dll. This file is the ISAPI DLL.
Available only on the Enterprise and later edition. This DLL requires
the HTTP server to work.
frediIsapiConsole.exe. This executable file is the ISAPI
Console utility. Available only on the Enterprise and later
edition. This utility should be installed where the ISAPI DLL is
installed as well because it is used to configure the ISAPI DLL.
The following DLLs are self-registering, and by default the files are
installed to the target path. However, as long as they have been
registered, these DLLs do not have to be located in the target folder in order
for the clients to locate them. Some DLLs do require that the Standard
Error Code file (Edidev_SEC.dll) must be in the same path otherwise an error
will be generated.
Edidev_Dictionary.dll. This file is the Standard Reference
Library that provides the published standard of implementation guidelines
for various versions of the ASC/X12 standard and UN/EDIFACT standard.
If an implementation guideline is not provided, Framework EDI may use the
implementation guidelines stored in this library. If this DLL is
missing, an error will be generated if no other implementation guideline has
been provided where it is needed. This file requires Edidev_SEC.dll.
Edidev_SEF.dll. This file is the Standard Exchange Format (SEF)
component that processes SEF files for clients that process EDI files.
If this DLL is missing and a SEF file has been provided for processing an
EDI file, an error will be generated. This file requires
Edidev_SEC.dll.
Edidev_SEF.tlb. This file is the type library for the SEF
component (Edidev_SEF.dll). Mostly required for development only to
enumerate objects, methods and properties of SEF objects in a development
environment. No error is generated if this file is missing, but, if
present, it must be in the same folder as Edidev_SEF.dll to be registered
properly.
Edidev_UNDED.dll. This file contains the description of UN/EDIFACT
semantic objects. If this file is missing, no description is provided
for data segment, data elements, etc.
Edidev_X12DED.dll. This file contains the description of ASC/X12
semantic objects. If this file is missing, no description is provided
for data segments, data elements, etc.
Edidev_UN1AD02B.dll. This file contains the description of
UN/EDIFACT codes. If this file is missing, no code description is
provided.
Edidev_X121A4012.dll. This file contains the description of
ASC/X12 codes. If this file is missing, no code description is
provided.
Fredi.dll. This file is the core component of Framework
EDI. This is the DLL that the client interfaces to use EDI, SEF, and
other general functions to create a full blown eBusiness application.
This component is installed in most installer editions, except for those
that require the desktop utilities only.
Fredi.tlb. This file is the type library for the Framework
EDI (fredi.dll). Mostly required for development to enumerate objects,
methods and properties of EDI objects in a development environment. No
error is generated if this file is missing, but, if present, it must be in
the same folder as fredi.dll to be registered properly.
To manually register, or unregister these DLLs, use the REGSVR32.EXE utility that comes with the Windows
operating system.
The Framework EDI .NET hybrid file is called EDIdEv.FrameworkEDI.NET.dll.
This file is the core component for .NET applications that use EDI, SEF, and
general functions required to build a full blown eBusiness application. At
installation it is
automatically installed into the Global Assembly Cache (GAC). This component is installed in most installer editions, except for those
that require the desktop utilities only. To manually install the file to the GAC, use the GACUTIL.EXE utility. Example,
The program executable responsible for uninstalling Framework EDI is Edidev_SDK_Uninstall.exe.
This is the executable invoked when selecting to uninstall "Edidev
Framework EDI" in the "Add or Remove Programs" of the Control
Panel. Currently it uninstalls any existing copies of Framework EDI components that
have been installed in the target folder specified by the registry entry Software\Edidev\Setup.x86\Target.
If any Program Menu has been specified in the same key, it is removed as
well.
There are 4 possible ways a product can be uninstalled.
When a runtime installer is executed from the command line, any previous
installation of Framework EDI is uninstalled.
When running an installer using the GUI interface, if a previous
installation is detected, a wizard dialog box will show an option to "Remove"
the previous installation. Selecting the "Remove" option will completely
uninstall the previous operation.
Invoking the "Add or Remove Programs" from the control panel, and then
selecting "EDIdEv Framework EDI" will uninstall the previous
installation.
Manually running the Edidev_SDK_Uninstall.exe
file directly on the target folder. No command line parameter is
required. Information on what gets uninstalled is read
from the Software\Edidev key of the registry.
When the product is uninstalled, the components are deleted from the
folder where they were originally installed. All components self-registered are
first unregistered before getting deleted. The .NET hybrid is removed
from the GAC. All registry entries created by the product are also removed.
NOTE: Any system or shared file replaced, or added, are not deleted or reverted
to the older version. Please see System and Shared Files.
For applications and components to function properly, certain setup and
state information are stored in the registry. For 32-bit
installers installing on 32-bit Windows, registry
keys are created directly under the HKEY_LOCAL_MACHINE (HKLM) and/or
HKEY_CURRENT_USER (HKCU) registry hives. However, the same
registry keys are redirected into a separate logical registry view by
64-bit Windows. This separate logical registry view is mapped to a
subnode called Wow6432Node, which is created
automatically by the WOW64 component of the operating system, so that a
registry key in 32-bit created in "HKLM\Software\Edidev" would
be redirected to"HKLM\Sotware\Wow6432Node\Edidev".
The following registry keys are created by FREDI Installers:
Software\Edidev. This registry key is created to contain
general setup and state information for all Edidev
applications. In 32-bit Windows, the key is created in:
HKLM\Software\Edidev
HKCU\Software\Edidev
In 64-bit Windows, the same registry key is redirected to:
HKLM\Software\Wow6432Node\Edidev
Software\Edidev\Setup.x86\UninstallInfo. This registry key is
created to contain information for all files that have been
installed. If the files are to be later uninstalled, the
uninstaller utility Edidev_SDK_Uninstall.exe will read
the list of files in this registry hive to remove them from the
system. In 32-bit Windows, the key is created in:
In 64-bit Windows, the same registry key is redirected to:
HKLM\Software\Wow6432Node\Edidev\Setup.x86
Software\Microsoft\Windows\CurrentVersion\RunOnce. If an existing file denies access to an update then the new file is
recorded to be updated later after the computer restarts. In this case,
the installation is not completed until after the computer has rebooted, the
user has logged on, and the small utility program Edidev_SDK_RunOnce.exe
is executed. The program executable is entered in this registry
key. After the user has logged on, the system takes note of the
executable to run, deletes the registry entry, and then runs the
executable. This guarantees that the program is ran only once, after
which the installation is complete. The Edidev_SDK_RunOnce.exe utility
program registers Framework EDI components installed after restart.
Software\Microsoft\Windows\CurrentVersion\Uninstall\Edidev
(32-bit). To uninstall Framework EDI from the "Add or Remove Programs" in the control
panel, the installer records an uninstaller utility
program in this registry key. The name of the program is Edidev_SDK_Uninstall.exe
and is labeled as "EDIdEv Framework EDI".
The following Microsoft Windows system and shared files may be
installed by
FREDI installers.
MFC42.DLL (6.0.8447.0)
MSVCRT.DLL (6.0.8397.0)
OLEAUT32.DLL (2.40.4275.1)
OLEPRO32.DLL (5.0.4275.1)
REGSVR32.EXE (5.0.1641.1)
MSVCP60.DLL (6.0.8972.0)
MFC71.DLL (7.10.3077.0) (Shared)
MSVCP71.DLL (7.10.3077.0) (Shared)
MSVCR71.DLL (7.10.6004.4) (Shared)
These files will be copied over to the Windows System directory and will
overwrite older versions of existing files. However, provisions are
made to prevent inadvertently replacing these system files if they
are not required. They are:
For operating systems Microsoft Windows 2000 and
higher, these file are not updated, even if by chance the version of the
existing files are older. If the version of the files are older, it is
recommended that the computer should be updated using the latest software
package carrying the latest version (example Internet Explorer 5.0 or later),
or updated with the latest service pack available from Microsoft.
However, if these file do not exist in the system folder, the
following action is undertaken:
Microsoft Windows 2000 only. These files are added to
the system folder, except for those shown as
"isolated".
Operating systems higher than Microsoft Windows 2000.
Only those files shown as "shared" are added to the
system folder as shared system files.
To
further protect the client operating system, these files will update
depending on the system file's Windows File Protection (WFP) status. Under
WFP, files marked by the operating system as protected will not
be updated by the installer.
Finally, an option not to install these files
is also provided. If the installer detects that any of the above files
are going to be installed, the installation wizard will list the files
and request confirmation to install. A "no" confirmation will
prevent the files from being installed. If the installer is executed
from the command line, the "-w" parameter can be included to prevent any
installation of the system files. For XP and higher, the files
marked as isolated will still be installed on the application's
target path.
NOTE: When the product is uninstalled, the system and shared files are not
deleted or reverted to the older version before the product
was installed. Isolated system files, that have been installed
on the applications target path, will be uninstalled.
