Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd dp Command Reference
  16. infacmd idp Command Reference
  17. infacmd edp Command Reference
  18. Infacmd es Command Reference
  19. infacmd ihs Command Reference
  20. infacmd ipc Command Reference
  21. infacmd isp Command Reference
  22. infacmd ldm Command Reference
  23. infacmd mas Command Reference
  24. infacmd mi Command Reference
  25. infacmd mrs Command Reference
  26. infacmd ms Command Reference
  27. infacmd oie Command Reference
  28. infacmd ps Command Reference
  29. infacmd pwx Command Reference
  30. infacmd roh Command Reference
  31. infacmd rms Command Reference
  32. infacmd rtm Command Reference
  33. infacmd sch Command Reference
  34. infacmd search Command Reference
  35. infacmd sql Command Reference
  36. infacmd tdm Command Reference
  37. infacmd tools Command Reference
  38. infacmd wfs Command Reference
  39. infacmd ws Command Reference
  40. infacmd xrf Command Reference
  41. infacmd Control Files
  42. infasetup Command Reference
  43. pmcmd Command Reference
  44. pmrep Command Reference
  45. Working with pmrep Files

Blockchain Connection Options

Blockchain Connection Options

Use connection options to define a blockchain connection.
Enter connection options in the following format:
... -o option_name=value option_name=value ...
To enter multiple options, separate options with spaces. To enter a value that contains a space or other non-alphanumeric character, enclose the value in quotation marks.
The following table describes blockchain connection options for infacmd isp CreateConnection and UpdateConnection commands:
Property
Description
swaggerFilePath
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.
authType*
Authentication method that the run-time engine uses to connect to the REST server. You can use none, basic, digest, or OAuth.
authUserID*
User name to authenticate to the REST server.
authPassword*
Password for the user name to authenticate to the REST server.
oAuthConsumerKey*
Required for the OAuth authentication type. Client key that is associated with the REST server.
oAuthConsumerSecret*
Required for the OAuth authentication type. Client password to connect to the REST server.
oAuthToken*
Required for the OAuth authentication type. Access token to connect to the REST server.
oAuthTokenSecret*
Required for the OAuth authentication type. Password associated with the OAuth token.
proxyType*
Type of proxy. You can use no proxy, platform proxy, or custom.
proxyDetails*
Proxy configuration using the format
<host>:<port>
.
trustStoreFilePath*
The absolute path of the truststore file that contains the SSL certificate.
trustStorePassword*
Password for the truststore file.
keyStoreFilePath*
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.
keyStorePassword*
Password for the keystore file.
advancedProperties
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 October 22, 2020