Per i dettagli sulle convezioni utilizzate nella pagina corrente fare riferimento alla sezione apposita in:
Oltre alle normali convenzioni (Often, for security reasons, it is necessary to isolate the web server (
WS), which provides public access, from the Mago server (
MS) which hosts the installation of Mago.Net.
To get this particular configuration the operations to be performed, summarizing, are: create the Easylook web application onto server Web (the only prerequisite
.Net Framework), link the Mago.Net server, set the File System permissions.
Let's look in detail:
1. from the
MS copy the folder
C:\Program Files\Microarea\installation name\Standard\TaskBuilder\WebFramework\EasyLook
to the
WS in
C:\inetpub\wwwroot path
2. in the
C:\Inetpub\wwwroot\EasyLook\bin folder, create the
InstallationInfo.xml file, whose content is to be set as:
<?xml version="1.0"?>
<InstallationInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<FileSystemServer>%Server name%</FileSystemServer>
<WebServer>%Server name%</WebServer>
<InstallationName>%Installation name%</InstallationName>
</InstallationInfo>
complete it properly with your information (Server and Installation name),
3. through the IIS manager <
inetmgr> create the
Easylook application, pointing to the folder copied in step 1 and setting
Asp.Net 2.0,
4. check that the Windows user, running the aspnet process onto
WS, has the access to the file system both of
MS and
WS. For example in IIS 7 the default user that runs the aspnet process (w3wp.exe) is
NETWORK SERVICE; then this user will have to have full access to the contents of Standard and Custom folders of the
MS and to the installation folder of the
WS.
The first three steps are covered by the Easylook setup (
EasyLookSetup.exe), available onto the Mago.Net Server in:
[installation path]\[installation name]\Apps folder
 EasyLook stand alone setup |
The installation is performed through a wizard which helps the user to make the proper choices.
To start the wizard double-click on the msi file or digit the proper command (
see KB000003 
).
Before starting the installation:
- make sure you are connected as administrator,
- disable the UAC - User Account Control (if the o.s. allows it),
-
)
+R+UserAccountControlSettings.exe
- run the setup through the "Run as Administrator" option (see KB000003 ).
First of all, it checks for requirements.
In details it checks:
- the .Net Framework presence
- the IIS presence
- the status of IIS services
- the status of Server service (needed for sharing over the network)
in case of lack or malfunction of at least one of them, a
Summary form is being displayed
that provides the
Help button, which redirects to the specific section of the Help Center.
Vice versa, if the prerequisites check is successful, a
Welcome form is being displayed to start the setup by performing the following steps:
1. Choose language application
In this step you can choose the preferred language. To add other languages is necessary to choose
Advanced settings.
As certainly already known, one of the main functions of Mago.
net is the
multi-language support. This not only means that the program forms are translated into all the supported languages, but above all that Mago.
net can be fully adapted to the local accounting-fiscal rules.
The
functional localization is embedded in the serial number used for activation and
is not, therefore,
controlled by this parameter.
Please, take the necessary time to carefully read the End User License Agreement before to tick the checkboxes, that allow you to continue to the next step. Thanks to the
Read in PDF button also you can show the EULA, through the PDF reader program available in your system. If the reader lacks, a Windows system message will be showed.
3. Choose the setup type
Choosing the
Default settings, reccomended for demo installation and/or stand-alone configuration, the installation process manages all the parameters:
- Installation Path -> %ProgramFiles%\Microarea (or %ProgramFiles(x86)%\Microarea on 64bit o.s.)
- Installation Name -> MagoNet (corresponding to a subfolder of the above path)
In case it conflicts with homologous virtual folder it is renamed through progressive index e.g.:
MagoNet1. This feature aims to avoid conflicts with previous versions (i.e. 2.x), with virtual folders handmade or related to any incomplete uninstallation, but does not allow multi-instance since it is not provided nor supported.
- Web site -> Default Web Site (usually identified by Id=1 and listening on TCP port 80)
Otherwise, more skilful users can choose the Advanced settings to customize every aspect of the installation
including the above parameters
including the ability to select a different Web site (name and TCP port),
and choose the features to be included or excluded
reminding that:
- Microarea Mago.net is mandatory and can not be excluded,
- Microarea Quick Support adds Team Viewer client, to obtain remote assistance,
- each Language Package contains: the Default data, the Sample data , and the Dictionaries needed to the translation.
The Language Package associated with the Application's language (set in step 1.), is automatically selected, with the exception of English, being the native language with which the program has been developed, does not have the language package. It is always possible to include or exclude others at a later time simply re-running the Setup.
4. Summary installation settings
Before starting the installation process, by pressing the
Install button, a brief summary shows the installation settings (auto-proposals or selected by the user) that will be applied.
Once the installation actions end
the
Client setup generation process starts,
needed to run the Client Setup on the remote clients.