A datasource connection is the mechanism used by Logi applications to communicate with datasources through a driver or provider for the purpose of reading and writing data. Selecting and configuring a Connection element is the first step in the process of developing most Logi applications; connections are discussed in this topic.
The following topics provide more details about the available datasource connections:
- Using the Connection Wizard
- Using Vendor-Specific Connections
- Using Generic Connections and Connection Strings
- Using Special-Purpose Connections
- Creating Dynamic Connections
- Connecting with Metadata
About Datasource Connections
Logi applications connect to a datasource in order to read and write its data. In most cases, this is done using a Connection element, which specifies the nature of the communication, including security credentials.
The exceptions are for accessing certain kinds of files, such as XML, CSV, and Excel files, which your Logi application is able to access directly through the web server file system. These sources do not use Connection elements.
Connection elements do not work with datasources requiring SSH.
Connection elements are configured in the _Settings definition and are therefore available application-wide. One connection can be used for multiple report definitions, and a Logi application can have multiple connections, allowing data from multiple sources to be included in a single report. There are three types of connection elements:
Vendor-specific connection elements, such as Connection.MySQL, are the connections we recommend you use. They provide the best performance and easiest configuration. The available vendor-specific Connection elements include:
- Connection.Google Docs
- Connection.Google Maps
- Connection.SQLServer (Microsoft)
Your Logi product, in combination with the .NET framework or Java libraries, contains all of the underlying drivers or providers necessary to make all of these connections work, except for Oracle, DB2, and Sybase. Due to licensing restrictions, these connections are only usable if you have the client driver software that's distributed with the database server, or that you download. See the Usage Notes sections for each of these systems on page two for information about their drivers.
MySQL 5.5 is not supported for use with our DataLayer.ActiveSQL technology.
The configuration of Connection.Google Docs and Connection.Google Maps is discussed in Google Connections.
Salesforce.com has discontinued support for the TLS 1.0 protocol. If you're using Connection.Salesforce, or REST or SOAP API connections to Salesforce, you must be using Logi Info v12.2-SP4 or later, which supports the TLS 1.1 and 1.2 protocols. In addition, Login Java applications must use JDK or OpenJDK 8 or later to use the appropriate protocol version. For more information about which versions of JDK works with Info, see Java Usage Policy.
The most recent .NET and Java drivers shipped with Logi Info v12.6 only work with MongoDB 2.6 and later. If you're using an older version of MongoDB, such as 2.4, you cannot upgrade your Logi application to Info v12.6.
Generic connection elements, such as Connection.OLEDB, require you to provide, or use a wizard to construct, a "connection string". Connection strings are text strings that are passed in code to an underlying driver or provider in order to initiate the connection. The available generic Connection elements include:
Connection.OLAP is used to connect to Microsoft Analysis Services OLAP databases and Connection.SMTP is used to connect to SMTP email servers.
The other generic elements are for connection to a variety of databases. For example, the Connection.OLEDB element allows you to use the Microsoft Jet driver to connect to MS Access database files and can also be configured to connect to Microsoft's SQL Server database server.
Microsoft elected not to include the MS Jet driver in its 64-bit OS versions, but it is possible to use the "MS Ace" OLEDB driver, distributed with Office 2007, instead.
Special-purpose connection elements, such as Connection.Web Service, are designed to connect with specific web services or special Logi services. The available special-purpose Connection elements include:
- Connection.Leaflet Map
- Connection.Logi Application Service
- Connection.Web Service (SOAP)
Connection.DataHub is used to connect to our Logi DataHub data virtualization product. Connection.Logi Application Service is used to connect to Logi Platform Services, installed with Logi Info 12.5+ or the Discovery Module 3.0. Connection.HTTP allows the following datalayers to use a connection to an HTTP or HTTPS datasource that requires authentication:
- DataLayer. CSV
- DataLayer.Fixed Format File
- DataLayer.GPX File
- DataLayer.KML File
- DataLayer.Web Feed
- DataLayer.Web Scraper
The Request Header is a child element of Connection.HTTP and Connection.REST. This element allows custom information, primarily intended for authentication purposes, to be sent through the connection in the HTTP request header.
Connection.Leaflet Map is used to connect to a Leaflet API-compatible map server. See Leaflet Maps for more information.
The Connection.Logi Application Service element is used to connect to a special service installed with the Discovery Module and is only availablein Logi Info if the add-on moduleis installed. Connection configuration details are available in Develop with the Discovery Module 3.1.
Connection.OData, and its OData Parameters child element, allow connection to REST-style APIs.
Connection.REST and Connection.Web Service are similar, in that they both connect to web services. However, Connection.REST works with Representational State Transfer (REST) protocols, such as HTTP, and Connection.Web Service works with the SOAP protocol.
Connection.Scheduler is used with the Logi Scheduler service provided in Logi Info to manage scheduled reporting.
The Studio Connection Element
Logi Studio includes tools, like the SQL Query Builder and the Database Browser, that normally use the configured Connection elements to transparently connect to the data during development. However, for a variety of reasons, the Windows development machine where Studio is installed may not be able to use the configured data connections. For instance, the driver may not be installed on, or may be incompatible with, the Windows machine running Studio. In this case, a special Studio Connection element can be added to provide a separate connection for Studio's tools. Studio Connection is available as a child of the following connections: