Configuring data connections
This table shows the available types of data connection:
Connection type | Variants |
---|---|
Infor EPM OLAP | |
Relational Providers | Microsoft SQL Server |
Oracle Database Server | |
PostgreSQL Server | |
Amazon Redshift | |
Infor Olap Server | |
External Infor Olap Server | |
Built-in Staging database | |
Infor Data Lake |
For all categories of data connection you specify a name and, optionally, a description of the connection on the General tab. The unique name is automatically derived from the name that you specify.
The options of the Connection tab vary according to the category of connection.
Connection tab for OLAP connections
For OLAP data connections, you select the OLAP data source to connect to, in the Data Connection field. This enables other fields on the tab.
In the Authentication Method field, select one of these options:
- Use Existing Connection: Use this option if the currently connected account of a user of Application Studio or another client is also used to connect to OLAP.
- Service Account: Some Application Studio reports and Application Engine processes require OLAP
data access that is out of scope of the current user's permissions. For example,
to copy or process data. In this case, you must create a data connection that
impersonates a user with higher privileges, which are used by those Application Studio reports and Application Engine
processes.Note: We recommend that you do not use service accounts in data connections in Self-Service and Office Integration
To configure a data connection to use a service account, perform these steps:
- Import the service account to Infor EPM.
See "Managing service accounts".
- Register the user of the service account in the Users and User Groups dashboard and assign the required application or data roles, or both to the user.
- On the Connection tab, in the Data Connections dashboard, select as the authentication method.
- From the list of imported service accounts, select the required service
account.
A warning is displayed informing that the account that is used for the data connection may allow users to access data for which their assigned roles have no permission.
For more information, see "Managing service accounts".
Connection tab for relational connections
For relational data connections, you can define a new connection, connect to the built-in staging database, connect to Data Lake, or link to an existing connection in another application. Linking to an existing connection is possible only if linking is enabled on the Usage tab of the existing application.
To define a new connection you select a data provider. The remaining fields of the Connection tab depend on the selected provider.
- Microsoft SQL Server
- In the Host field, select the machine on which the data source is located.
- Oracle Database Server
- You can use an existing TNS and select the service name of the tnsnames.ora file. Or, you can
define the connection manually. If you select Define manually you must specify the
server name, port, and select one of these connection types:
- Default
- Dedicated
- Shared
- TCP/IP
- TCP/IP + SSL
- Named Pipes
- IPC
- PostgreSQL Server
- In the Host field, select the machine on which the data source is located.
- Amazon Redshift
- In the Host field, select the machine on which the data source is located.
- Infor Olap Server
- You can authenticate with the existing connection or select Basic authentication. For Basic authentication, specify the user name and password for the data source.
- External Infor OLAP
- To connect to an External Infor OLAP server, specify the URL of where the data source is located.
Usage tab
On the Usage tab you specify which clients the connection can be used in, and whether the connection can be used in other Infor EPM applications.
Advanced tab for relational connections
You can specify a command timeout and connection timeout. For all providers other than Amazon Redshift, you can select one or more of these options:
- Encrypt
- The SQL Server uses SSL encryption for all data sent between the client and server.
- Connection reset
- Determines whether the database connection is reset when being removed from the pool.
- Persist security info
- Security-sensitive information, such as the password, is not returned as part of the connection.
- Enable AlwaysOn Availability Groups support
- Supports configuration of multiple primary databases and multiple secondary databases for failover.
- Enlist
- Enlists the connection in the creation thread's current transaction context.
- SSL Mode
- For PostgreSQL providers you can select one of these SSL modes:
- Disable
- Allow
- Prefer
- Require
- Other Connection String Parameters
- Any properties of the connection string can be used as parameters.
- Fingerprint
- Click Fingerprint field. The data connection will not accept connections from any server that provides a different certificate. to retrieve the certificate of the remote server and populate the
Example
A requirement for a high availability connection can be configured with the Advanced tab.
check box and the command and connection timeout options on theA connection string created from the selections on the Advanced tab might look like this:
Provider=MSOLEDBSQL;Server=tcp:DEVBILS.<customer>.com,1433;MultiSubnetFailover=Yes;Database=DB_Name; Connect Timeout=30;ConnectRetryCount=10;ConnectRetryInterval=10;
Advanced tab for OLAP connections
Optionally, select the format to use for element unique names. By default, the format that is specified in the database is used.