PATCH process
The PATCH process sends data to a specified URL. Also, the PATCH process can send a data file to the URL.
The following table describes the process inputs for the HTTP adapter with the PATCH process.
Input | Description | Required |
|---|---|---|
<adapter-name> | Specifies the name of the adapter. | No |
<URL> | Specifies the URL for the target page | Yes |
<use-ssl-certificate> | Determines whether to establish a secure connection. | No |
<install-certificate> | Determines whether to install certificates. If true, the security certificates are installed automatically (a common practice). If false, the user must manually export the security certificate from the specified target server and manually import it to the cacerts file on a local peer. | No |
<allow-unsigned-certificate> | Specifies whether to allow unsigned certificates from trusted zones. | No |
<passphrase> | Specifies the Java Standard Trust Keystore passphrase Verify the cacerts passphrase using the following command in UNIX or Linux: $ /opt/bmc/ao/cdp/jvm/bin/keytool -list -keystore | No |
<file-path> | Specifies the path of the file to be sent to the URL | No |
<file-content-type> | Specifies the content type of the file to be uploaded | Conditional; used if the adapter request contains a <file-path> element |
<data-format> | Indicates the data type for the adapter response | No |
<data> | Contains the data to be posted JSON sample for specifying the <body> element { --- formatted json for patch --- } Sample format for specifying <body> for a multi-part data request { "op": "replace", "path": "/name", "value": "Nitin" } | No |
<user-name> | Specifies the user name required for basic authentication | No |
<password> | Specifies the password corresponding to the user name provided for basic authentication | No |
<character-set> | Specifies the supporting CharSet, which includes identifiers describing a series of universal characters. Note: If you do not specify the supporting character set, the adapter response is parsed based on the character set in the HTTP response header. | No |
<connection-properties> | Specifies an XML document that includes HTTP connection properties, which contains the <user-name> and <password> elements for a basic or NTLM authentication. | No |
<include-expect-header> | Specifies whether to include the expect header in the adapter request Valid values: true (default), false | No |
<user-name> | Specifies the user name required for basic or NTLM authentication specified in <http-connection-properties> | No |
<password> | Specifies the password corresponding to the user name specified in <http-connection-properties> | No |
<signature-mode> | Contains the elements that specify information about the public key (X.509 certificate) and the private key that are used for the digital signature
| No |
<keystore-file> | Specifies the path to the JKS that contains the client certificate | Conditional; required when <signature-properties mode="keystore"> |
<client-alias> | Specifies the name of the alias in the JKS that identifies the Public Key Certificate (PKC) that the web server uses to authenticate the client | Conditional; required when <signature-properties mode="keystore"> |
<key-password> | Specifies the password of the key contained in the JKS | No |
<keystore-password> | Specifies the password to the JKS | Conditional; required when <signature-properties mode="keystore"> |
<private-key-file> | Specifies the file containing the private key that is used to sign the HTTP request
| Conditional; required when <signature-properties mode="key-files"> |
<certificate-file> | Specifies the file containing the public key (X509 Certificate)
| Conditional; required when <signature-properties mode="key-files"> |
<private-key-data> | Contains an XML file specifying the private key in an Base64-encoded PEM format | Conditional; required when <signature-properties mode="key-data"> |
<certificate-data> | Contains an XML file specifying the public key (X509 Certificate) in an Base64-encoded PEM format | Conditional; required when <signature-properties mode="key-data"> |
<enable-json-conversion> | Specifies whether the adapter should treat the input data in the request and the data received in the adapter response as a JavaScript Object Notation (JSON) string
| No |
<request-timeout> | Specifies the time (in seconds) to wait when establishing a connection | No |
<krb-login-conf-path> | Specifies the path to the login.conf file For example, /etc/java.login.conf | No |
<krb-conf-path> | Specifies the path to the krb configuration file For example, /etc/krb5.confa | No |
<krb-use-subject-creds> | Specifies whether to use user credentials while obtaining a ticket. Valid values: true, false (retrieves the ticket from the kinit cache). | No |
<ignore-line-break-in-response> | Specifies whether to ignore the line breaks while generating the adapter response. If true, the line break markups are ignored and the response is returned as a single line. If false, the line break markers (if specified in the adapter response) are retained. Valid values: true (default), false | No |
The following table describes the process output parameters for the HTTP adapter with the PATCH process.
PATCH process outputs
Outputs | Description |
|---|---|
status code | Specifies the HTTP status code |
status reason | Specifies the HTTP status reason |
header lines | Specifies the HTTP header lines |
message body | Specifies the message body |