Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

Blockchain Connection Properties

Blockchain Connection Properties

When you set up a blockchain connection, you must configure the connection properties.
The following table describes the general connection properties for a blockchain connection:
Property
Description
Name
The name of the connection. The name is not case sensitive and must be unique within the domain. You can change this property after you create the connection. The name cannot exceed 128 characters, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
ID
The string that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection. Default value is the connection name.
Description
The description of the connection. Enter a string that you can use to identify the connection. The description cannot exceed 4,000 characters.
Swagger File Path
The absolute path of the swagger file path that contains the REST API to communicate with the blockchain. The swagger file must be a JSON file that is stored on the Data Integration Service machine. If the swagger file is in a different file format, such as YAML, convert the file to JSON format.
Auth Type*
Authentication method that the run-time engine uses to connect to the REST server. You can use none, basic, digest, or OAuth.
Auth User ID*
User name to authenticate to the REST server.
Auth Password*
Password for the user name to authenticate to the REST server.
OAuth Consumer Key*
Required for the OAuth authentication type. Client key that is associated with the REST server.
OAuth Consumer Secret*
Required for the OAuth authentication type. Client password to connect to the REST server.
OAuth Token*
Required for the OAuth authentication type. Access token to connect to the REST server.
OAuth Token Secret*
Required for the OAuth authentication type. Password associated with the OAuth token.
Proxy Type*
Type of proxy. You can use no proxy, platform proxy, or custom.
Proxy Details*
Proxy configuration using the format
<host>:<port>
.
TrustStore File Path*
The absolute path of the truststore file that contains the SSL certificate.
TrustStore Password*
Password for the truststore file.
KeyStore File Path*
The absolute path of the keystore file that contains the keys and certificates required to establish a two-way secure connection with the REST server.
KeyStore Password*
Password for the keystore file.
Advanced Properties
List of advanced properties to access an asset on the blockchain. Specify the advanced properties using name-value pairs that are separated by a semicolon.
You can use the following advanced properties:
  • baseUrl. Required if the swagger file does not contain the base URL. The base URL that is used to access assets on the blockchain.
  • X-API-KEY. Required if you authenticate to the REST server using an API key.
The advanced properties that you configure in the connection override the values for the corresponding advanced properties in the blockchain data object. For example, if the connection and the data object both specify a base URL, the value in the connection overrides the value in the data object.
Cookies
Required based on how the REST API is implemented. List of cookie properties to specify the cookie information that is passed to the REST server. Specify the properties using name-value pairs that are separated by a semicolon.
The cookie properties that you configure in the connection override the values for the corresponding cookie properties in the blockchain data object.
*
The property is ignored. To use the functionality, configure the property as an advanced property and provide a name-value pair based on the property name in the swagger file.
For example, configure the following name-value pair to use basic authorization:
Authorization=Basic <credentials>


Updated September 28, 2020