Installation Parameters

EOS is default installed on port 1100. It may happen that other applications or services use this port already. In such case the IT administrator can assign a different (arbitrary) port number to EOS, PRIOR to EOS installation.

In the /bin folder, edit the 'wrapper.conf' file in a simple text editor and search for the line :

wrapper.app.parameter.3=-port:1100

Change the port number, save the file and re-install the service. From now on you can connect to EOS through the new port number.

Note: you must STOP and REMOVE the service before uninstalling EOS.

A Windows “Service” is a special type of program which, unlike a traditional application, starts automatically when the computer starts before the user logs on. Because of this unique behavior, services are useful in software that performs operations in the background such as server applications and system automation software. Because services start before user logon, they do not run under the same user-context as applications that are started after logon. Rather, most services run in a special system account called LocalSystem. LocalSystem is a built-in account that has a high level of access rights in that system. Programs that run in the LocalSystem account have full access to the entire system. The drawback to this approach is that LocalSystem does not have the same access rights to the network that are normally associated with standard user accounts.

Because the EOS Service runs in the LocalSystem account, special configuration may be required to allow it to access network drives. If this configuration is not performed, any dataset, database or resource operations can fail if they require network access. It is common for this to cause user confusion.

For example, if a user creates a dataset and attempts to configures the EOS Service to open that dataset, at design-time, the user is able to browse to the folder to the network drive. However, when the user attempts to put the dataset into production, the EOS is unable to see the network drive. The reason for this lies in the fact that at design time the dataset is created, downloaded or installed with applications running under the user-context of the currently logged in user, whereas the EOS Service started before the user logged on and continues to run under the LocalSystem account.

The EOS Console displays the network drives defined in the user-context of the currently logged in user on the computer that runs the EOS Service. As long as that user remains logged in on the computer, the EOS service can access those chosen network files. If the user is logged out, such as after a reboot, the EOS Service is unable to access the network files.

1. Run the EOS Service on the target system that contains the datasets, databases or resources to be opened
   If it is possible to run the EOS Service on the server that contains all resources on its local discs, this will result in faster, more efficient operations as the data will not have to transverse the network. Furthermore, permissions will not need to be modified.
2. Grant privileges to the computer account on the domain for the share that needs to be accessed.
   In order to grant network permission to the LocalSystem account of a given machine the Computer object (not the user object) must be granted privileges to the network resource. If the system group “Everyone” already has access, this step is not necessary because the “Everyone” group includes computer objects. To configure a network resource to have access for a computer: from an administrative account on the server, browse to the folder in question, right click the folder, select Sharing, the sharing dialog box will be displayed, click “Permissions”, tab and click the button “Add”. Browse for the Computer (the computer on which EOS is running) and add it to the list.
   IMPORTANT: The security must be modified on the actual share on the server via sharing properties and not by simply accessing the properties of the folder and modifying its security settings.