Before you create a catalog source, ensure that you have the information required to connect to the source system.
Perform the following tasks:
•Assign the required permissions.
•Configure an Oracle, Microsoft SQL Server, or SAP HANA connection in Administrator to connect to the SAP BusinessObjects Data Services repository.
•If your Oracle database is SSL-enabled, specify appropriate values for the Trust Store and Key Store fields in the Oracle connection properties. Test Connection to an SSL-enabled Oracle database fails if either the truststore or keystore value is not specified in the connection properties.
•Create endpoint catalog sources for connection assignment.
Verify permissions
To extract metadata and to configure other capabilities that a catalog source might include, you need account access and permissions on the source system. The permissions required might vary depending on the capability.
Permissions to extract metadata
Ensure that you have the required permissions to enable metadata extraction.
Grant permissions that allow you to perform the following operations:
•select on CONNECTION_SCHEMA.AL_LANG
•select on CONNECTION_SCHEMA.AL_LANGXMLTEXT
•select on CONNECTION_SCHEMA.AL_PARENT_CHILD
Create a connection
Before you configure the SAP BusinessObjects Data Services catalog source, create a connection object in Administrator.
1In Administrator, select Connections.
2Click Add Connection and select Oracle, Microsoft SQL Server, or SAP HANA.
Note: Select the connector that corresponds to your local BusinessObjects Data Services repository type.
3Enter the connection properties.
4Click Test.
5Click Save.
Oracle connection properties
If you use the Oracle connection type, configure the Oracle connection parameters.
Enter properties specific to the Oracle connection type:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
The name of the runtime environment where you want to run the tasks.
Select a Secure Agent, Hosted Agent, or serverless runtime environment.
Select a Secure Agent, Hosted Agent, serverless, or elastic runtime environment.
Oracle Subtype
The Oracle connection subtype that you can use to connect to Oracle on-premises or Oracle Autonomous Database.
Select one of the following options:
- Oracle ADB. Connects to Oracle Autonomous Database.
- Oracle On-premise. Connects to Oracle on-premises.
Authentication Mode
You can configure one of the following authentication modes to connect to Oracle databases:
- Oracle Database authentication
- Kerberos authentication
Default is Oracle Database Authentication.
The following table describes the basic connection properties for Oracle Database authentication:
Property
Description
User Name
User name for the database login. The user name can't contain a semicolon.
Password
Password for the database login. The password can't contain a semicolon.
Host
Name of the machine that hosts the database server.
Port
Network port number used to connect to the database server.
Default is 1521.
Service Name
Service name or System ID (SID) that uniquely identifies the Oracle database.
Specify the SID in the following format to connect to Oracle databases:
SID:<ORACLE_SID>
Schema
The schema name to select tables during object selection in a mapping.
If you want to select tables from multiple schemas, leave the field blank. When left blank, all schemas you have access to are displayed and you can select tables from the available schemas.
Code Page
The code page of the database server.
The following table describes the basic connection properties for Kerberos authentication:
Property
Description
Host
Name of the machine that hosts the database server.
Port
Network port number used to connect to the database server.
Default is 1521.
Service Name
Service name or System ID (SID) that uniquely identifies the Oracle database.
Specify the SID in the following format to connect to Oracle databases:
SID:<ORACLE_SID>
Schema
The schema name to select tables during object selection in a mapping.
If you want to select tables from multiple schemas, leave the field blank. When left blank, all schemas you have access to are displayed and you can select tables from the available schemas.
Code Page
The code page of the database server.
The following table describes the advanced connection properties for Oracle Database authentication:
Property
Description
Encryption Method
The method that the Secure Agent uses to encrypt the data exchanged between the Secure Agent and the database server.
Default is No Encryption.
This property doesn't apply if you use the Hosted Agent.
Crypto Protocol Version
Cryptographic protocols to use when you enable SSL encryption.
Not applicable when you use the Hosted Agent or the serverless runtime environment.
Validate Server Certificate
Validates the certificate that is sent by the database server. If you specify the HostNameInCertificate parameter, the Secure Agent also validates the host name in the certificate.
Trust Store
The location and name of the truststore file.
For the serverless runtime environment, specify the following certificate path in the serverless agent directory:
The password for the keystore file required for secure communication.
Key Password
The password for the individual keys in the keystore file required for secure communication.
Connection Retry Period
Number of seconds the Secure Agent attempts to reconnect to the Oracle database if the connection fails. If the Secure Agent can't connect to the database in the retry period, the operation fails.
Used for all operations. Default is 0.
Metadata Advanced Connection Properties
Additional properties for the JDBC driver to fetch the metadata. Enter properties in the following format:
<parameter name>=<parameter value>
If you enter more than one property, separate each key-value pair with a semicolon.
For example, enter the following property to configure the connection timeout when you test a connection:
LoginTimeout=<value_in_seconds>
Note: The default connection timeout is 270 seconds.
To connect to an Oracle database enabled for advanced security, you can specify the Oracle advanced security options for the JDBC driver.
Additional properties for the ODBC driver to run mappings.
If you specify more than one property, separate each key-value pair with a semicolon.
For example, charset=sjis;
readtimeout=180
To connect to an Oracle database enabled for advanced security, you can specify the Oracle advanced security options for the ODBC driver.
For example, EncryptionTypes=AES256;EncryptionLevel=1;
DataIntegrityLevel=1;DataIntegrityTypes=SHA1;
DataIntegrityTypes=SHA1
Microsoft SQL Server connection properties
If you use the Microsoft SQL Server connection type, configure the Microsoft SQL Server connection parameters.
Enter properties specific to the Microsoft SQL Server connection type:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
The name of the runtime environment where you want to run the tasks.
A runtime environment is either Informatica Cloud Secure Agent or a serverless runtime environment.
Select a Secure Agent, Hosted Agent, serverless, or elastic runtime environment.
SQL Server Version
This property is no longer used. If you select a version, it is ignored.
Authentication Mode
You can configure one of the following authentication modes to connect to Microsoft SQL Server databases:
- SQL Server authentication
- Windows authentication (Deprecated)
- Active Directory Password authentication
- Windows Authentication V2
- Kerberos authentication
- Service Principal authentication
Select the required authentication mode and then configure the authentication-specific parameters.
For SQL Server sources in database ingestion and replication tasks, you must select SQL Server Authentication, Windows Authentication v2, or Active Directory Password. Don't use the Kerberos or Service Principal Authentication mode.
For SQL Server targets in application ingestion and replication tasks and database ingestion and replication tasks, you must select either SQL Server Authentication or Windows Authentication v2. Don't use any other authentication type.
The following table describes the advanced connection properties:
Property
Description
Encryption Method
The method that the Secure Agent uses to encrypt the data sent between the driver and the database server. You can use the encryption method to connect to Microsoft Azure SQL Database.
Default is None.
Crypto Protocol Version
Cryptographic protocols to use when you enable SSL encryption.
Validate Server Certificate
When set to True, Secure Agent validates the certificate that is sent by the database server.
If you specify the HostNameInCertificate parameter, Secure Agent also validates the host name in the certificate.
When set to false, the Secure Agent doesn't validate the certificate that is sent by the database server.
Trust Store
The location and name of the truststore file. The truststore file contains a list of Certificate Authorities (CAs) that the driver uses for SSL server authentication.
For the serverless runtime environment, specify the following certificate path in the serverless agent directory:
The password to access the contents of the truststore file.
Host Name in Certificate
Host name of the machine that hosts the secure database. If you specify a host name, the Secure Agent validates the host name included in the connection with the host name in the SSL certificate.
Metadata Advanced Connection Properties
Additional properties for the JDBC driver to fetch the metadata.
Enter properties in the following format:
<parameter name>=<parameter value>
If you enter more than one property, separate each key-value pair with a semicolon.
For example, enter the following property to configure the connection timeout when you test a connection:
LoginTimeout=<value_in_seconds>
Note: The default connection timeout is 270 seconds.
When you use Kerberos authentication to connect to Microsoft SQL Server, you need to add the KRB5_CONFIG, KRB5CCNAME, and JAASCONFIG properties.
Runtime Advanced Connection Properties
Additional properties for the ODBC driver required at run time.
If you specify more than one property, separate each key-value pair with a semicolon.
When you use Kerberos authentication to connect to Microsoft SQL Server, you need to add the KRB5_CONFIG and KRB5CCNAME properties.
SAP HANA connection properties
If you use the SAP HANA connection type, configure the SAP HANA connection parameters.
Enter properties specific to the SAP HANA connection type:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
The name of the runtime environment where you want to run tasks.
Select a Secure Agent, serverless, or elastic runtime environment.
For more information about how to configure a serverless environment, see Use the serverless runtime environment.
For more information about how to configure an elastic runtime environment, see Use the elastic runtime environment.
Host
SAP HANA server host name.
Port
SAP HANA server port number.
Database Name
Name of the SAP HANA database.
Current Schema
SAP HANA database schema name.
Specify _SYS_BIC when you use SAP HANA database modelling views.
Code Page
The code page of the database server defined in the connection.
Select the UTF-8 code page.
Username
User name of the SAP HANA account.
Password
Password of the SAP HANA account.
The password can contain alphanumeric characters and the following special characters: ~ ` ! @ # $ % ^ & * ( ) _ - + = [ ] | : ; ' < , > . ? /
The following table describes the advanced connection properties:
Property
Description
Metadata Advanced Connection Properties
The optional properties for the JDBC driver to fetch the metadata.
If you specify more than one property, separate each key-value pair with a semicolon.
For example, you can set the connection timeout for the JDBC driver when you connect to SAP HANA.
Run-time Advanced Connection Properties
The optional properties for the ODBC driver to run mappings.
If you specify more than one property, separate each key-value pair with a semicolon.
For example,
charset=sjis;readtimeout=180
Create endpoint catalog sources for connection assignment
An endpoint catalog source represents a source system that the catalog source references. Before you perform connection assignment, create endpoint catalog sources and run the catalog source jobs.
You can then perform connection assignment to reference source systems and run connection-aware scans to view complete lineage with source system objects.
Note: When you create an Oracle endpoint catalog source, configure a different Oracle connection than the one used for the SAP BusinessObjects Data Services catalog source. If you use the same Oracle connection and run the SAP BusinessObjects Data Services catalog source again after connection assignment, you can't view the lineage of data elements.
Enter properties specific to the Oracle connection type: