In order for the client to know to which system or framework database to connect to, connectivity must be defined. It is possible to define more than one connectivity. User can then choose which one to use on login form. Single client can be connected to multiple servers from which it can receive solution updates. All connectivity and channels definitions are stored in connectivity.xml file which is located in root folder of MX-Client.

Several commands are available for working with connectivity and channels. Commands are accessible through menus located on the ribbon. Command executes action based on the section currently selected or displayed. They can either operate with connectivity or channel.

Command	Description
New	Creates new empty item. Item is added to the end of the bottom list.
Safe	Saves current configuration to connectivity.xml file located in MX-Client root folder.
Remove	Removes currently selected item. The deletion must be confirmed.

Every creation, deletion or any other modification must always be saved. Connectivity xml file is only influenced by save operation or command.

Connectivity

Several types of connectivity exist. Most common type is Data type which is used to retrieve system data from framework database. At least one data connectivity must exist in order for the user to be able to login into MX-Client.

Type	Description
Data	Connection type intended for connection to framework database.
Report	Connection type that defines the connection setting to reporting service server.
Update	Functionality is obsolete.
Loader	Connection type that defines the loader implemented with MxLoader component.

Each connectivity is defined by several fields. These fields determine the type and the connection string used to connect to the database.

Field	Description
Name	Defines the name of the connectivity element.
Alias	Defines the alias of the connectivity element. By the alias connectivity will be recognized on the login form.
Value	If in Type field Data option is selected, value of this field defines the connection string. This is the connection string to a MX-Frame framework database. Otherwise field can be empty.
Bootstrapper	Defines the type of the data server where framework database is located. If database is on Microsoft SQL Server, select SQL option. If database is on Oracle, select Oracle option. If Loader option is selected in field Type, enter the information about loader component. Enter Namespace.ClassName, AssemblyName of the MxLoader component designed in design time.
Type	Defines the type of the connectivity, the intention and the purpose of the connectivity. Individual types are described in table above.

Channel

Channels are used to determine where the client seeks for any possible updates. It is possible to search for more than one solution on more than one MX-Server. Two types of channels exist.

Type	Description
Framework	If Framework type is selected client can download system and content libraries. This means that client itself can also be updated along with any content developed with MxLibrary.
Library	If Library type is selected only content libraries are updated. This means only dll files developed with MxLibrary.

Each channel is defined by several fields. These fields determine the type and the server where updates are located.

Field	Description
Name	Defines the name of the channel. The name is used only for the recognition of the channel.
Target	Defines the server which will be searched for updates. The target string must be of the following format: http://<server_name>/Mx.Services/UpdateService.asmx Instead of <server_name> string enter server name or IP address of the server.
Type	Defines the type of libraries that will be downloaded. It is possible to download system or content libraries, or both.

To create a connectivity to connect to a framework database

1. Run MX-Client.
2. Login using account with administrative privileges.
3. Click application menu button and select Control Panel and Connectivity Channels in Client section. It is also possible to access Connectivity Channels by clicking application menu, selecting Settings option and Connectivity Channels. 
4. Click New menu on the ribbon. 
5. In field Name enter the name of the connectivity.
6. In field Alias enter string by which the connectivity will be recognized on the login form.
7. In field Value enter connection string for a database server. For SQL server connection string looks like this: data source = server_name; initial catalog=framework_database; Integrated Security = true;
8. In field Bootstrapper select SQL.
9. In field Type select Data.
10. Click Save menu on the ribbon.

New connection element is added to the connectivity.xml file. File is created if it did not exist before.

Upload to the Server

In systems with large number of clients it would be totally unpractical if one would have to create connectivity and channels by hand. Therefore it is possible to upload configuration of connectivity and channels to MX-Server. With automatic updates feature configuration is deployed to all clients. Next time client is started all libraries defined here will be accessible to the user.

Upload can be achieved by clicking Upload menu on the ribbon. Before that two fields must be filled in order to determine the server and the solution.

Field	Description
Address	Defines the address of the server where MX-Server is installed. Replace <server_name> string with server name or IP address of the server where MX-Server is installed.
Solution	Enter the name of the solution for which the configuration is intended. Configuration will then only be available to MX-Client which hosts the entered solution.

To upload a configuration

1. Define the configuration by managing connectivity and channels in sections Connectivity and Channel.
2. Enter the name of the server or IP address of the server in field Address instead of <server_name> string.
3. Enter the name of the solution in Solution field.
4. Click Upload menu on the ribbon.

Configuration will be retrieved by Enterprise MX-Client when the client is updated. 

See Also