Set one or several server connections to be able to save, remove, generate, and publish a mapping to a Mapper Server, and to import a mapping from a Mapper Server.
Specify a descriptive name for this connection.
Specify the IP, or the host name, for the Mapper Server.
The Mapper Server is part of the EC Server. For more details on EC server properties access the EC Management Page in Grid.
Specify the Grid port for HTTP or HTTPS communication.
You retrieve the port value from Grid Management > Configuration Manager > Default Router> HTTP value.
Specify the timeout in milliseconds for the connection, for example 5000 ms.
Specify the Context Root for the EC application. You find the Context Root in the Grid Management pages. The Context Root for the module MecMapGen and the Rest Service type must be used.
By default the context root is ecmapgen.
Select Secure Communication (HTTPS) or Unsecure Communication (HTTP).
Secure communication (HTTPS) is recommended. HTTPS and HTTP use different ports, as set up in Grid.
Select Windows User or Custom User.
If Windows User is selected, your current Windows user will be used. The view shows your current domain and user name in the Username field. You cannot change either user name or password for this authentication. To be able to use Windows User authentication, you must enable in Grid the ntlm Authentication method.
If Custom User is selected, you must specify a user name and a password. The Authentication method must be enabled in Grid to be able to use Basic User authentication. Do not use Custom User authentication over HTTP because it will send unencrypted user name and password to Grid.
If Custom User authentication is selected, specify the user name and password.
If the connection is successful, the view shows the Mapper Server version. Otherwise, an error message is displayed. Click OK to return to the Server Connectivity page.
If the file mapper.properties exists in the home directory of Eclipse (eclipse.home.location, where eclipse.exe resides), and the server connection given in the file does not already exist, it will be automatically added.
If the server connection given in the file already exists, confirm whether to update the database connection from the file. This will happen only once when the mapper is (re)started. You can also go toand click in the Default Configuration group. The user can then change or complement these preferences, if necessary.
When the file mapper.properties is changed, the same functionality is triggered the next time the mapper is (re)started. For a list of examples, see "Default Database Connection Preference" in Setting the Mapper database connectivity