Shared Content for Data Engineering All Products
... -o option_name=value option_name=value ...
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.
Authentication method that the run-time engine uses to connect to the REST server. You can use none, basic, digest, or OAuth.
User name to authenticate to the REST server.
Password for the user name to authenticate to the REST server.
Required for the OAuth authentication type. Client key that is associated with the REST server.
Required for the OAuth authentication type. Client password to connect to the REST server.
Required for the OAuth authentication type. Access token to connect to the REST server.
Required for the OAuth authentication type. Password associated with the OAuth token.
Type of proxy. You can use no proxy, platform proxy, or custom.
Proxy configuration using the format
The absolute path of the truststore file that contains the SSL certificate.
Password for the truststore file.
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.
Password for the keystore file.
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:
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.
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: