SDC RPC (deprecated)

Supported pipeline types:

  • Data Collector
The SDC RPC destination enables connectivity between two SDC RPC pipelines. The SDC RPC destination passes data to one or more SDC RPC origins. Use the SDC RPC destination as part of an SDC RPC origin pipeline.
Important: This stage is deprecated along with SDC RPC pipelines, and may be removed in a future release. You might replace SDC RPC pipelines with pipelines that use the HTTP Server origin to write to the HTTP Client destination.

You can use SDC RPC pipelines across a single Data Collector instance on a single machine, or across a local network or the public internet to a remote Data Collector.

When you configure the SDC RPC destination, you specify the RPC ID and RPC connections to use. You can optionally enable encryption to pass data securely and define retry and timeout properties. You can also configure SSL/TLS properties, including default transport protocols and cipher suites.

For more information, see SDC RPC Pipeline Overview (deprecated).

RPC Connections

In an SDC RPC destination, the RPC connections define where the destination passes data.

The RPC connection is the host and port number of the SDC RPC origin to receive the data. Define multiple connections to allow the SDC RPC destination to round-robin through multiple pipelines in case of bottlenecks.

Disabling Compression

The SDC RPC destination compresses data by default when passing data to an SDC RPC origin. When necessary, you can disable compression in the destination.

The SDC RPC destination compresses data to enhance performance. When the destination processes small records, compression might not enhance pipeline performance. When tuning pipeline performance, you might try disabling compression in the destination when working with small records.

Configuring an SDC RPC Destination

Configure an SDC RPC destination to pass data to one or more SDC RPC origins in another pipeline.
Important: This stage is deprecated along with SDC RPC pipelines, and may be removed in a future release. You might replace SDC RPC pipelines with pipelines that use the HTTP Server origin to write to the HTTP Client destination.
  1. In the Properties panel, on the General tab, configure the following properties:
    General Property Description
    Name Stage name.
    Description Optional description.
    Required Fields Fields that must include data for the record to be passed into the stage.
    Tip: You might include fields that the stage uses.

    Records that do not include all required fields are processed based on the error handling configured for the pipeline.
    Preconditions Conditions that must evaluate to TRUE to allow a record to enter the stage for processing. Click Add to create additional preconditions.

    Records that do not meet all preconditions are processed based on the error handling configured for the stage.
    On Record Error Error record handling for the stage:
    • Discard - Discards the record.
    • Send to Error - Sends the record to the pipeline for error handling.
    • Stop Pipeline - Stops the pipeline. Not valid for cluster pipelines.
  2. On the RPC tab, configure the following properties:
    RPC Property Description
    SDC RPC Connection Connection information for the destination pipeline to continue processing data. Use the following format: <host>:<port>.

    Use a single RPC connection for each destination pipeline. Using simple or bulk edit mode, add additional connections as needed.

    Use the port number when you configure the SDC RPC origin that receives the data.
    SDC RPC ID User-defined ID to allow the destination to pass data to an SDC RPC origin. Use this ID in all SDC RPC origins to process data from the destination.
    Verify Host in Server Certificate Verifies the host in the SDC RPC origin keystore file.
  3. On the Advanced tab, configure the following properties:
    Advanced Property Description
    Retries Per Batch Number of times the destination tries to write a batch to the SDC RPC origin.

    When the destination cannot write the batch within the configured number of retries, it fails the batch.

    Default is 3.
    Back Off Period Milliseconds to wait before retrying writing a batch to the SDC RPC origin.

    The value that you enter increases exponentially after each retry, until it reaches the maximum wait time of 5 minutes. For example, if you set the back off period to 10, the destination attempts the first retry after waiting 10 milliseconds, attempts the second retry after waiting 100 milliseconds, and attempts the third retry after waiting 1,000 milliseconds.

    Set to 0 to retry immediately.

    Default is 0.
    Connection Timeout (ms) Milliseconds to establish a connection to the SDC RPC origin.

    The destination retries the connection based on the Retries Per Batch property.

    Default is 5000 milliseconds.
    Read Timeout (ms) Milliseconds to wait for the SDC RPC origin to read data from a batch.

    The destination retries the write based on the Retries Per Batch property.

    Default is 2000 milliseconds.
    Use Compression Enables the destination to use compression to pass data to the SDC RPC origin. Enabled by default.
  4. To use SSL/TLS, on the TLS tab, configure the following properties:
    TLS Property Description
    Enable TLS

    Enables the use of TLS.

    Use Remote Truststore Enables loading the contents of the truststore from a remote credential store or from values entered in the stage properties. For more information, see Remote Keystore and Truststore.
    Trusted Certificates Each PEM certificate used in the remote truststore. Enter a credential function that returns the certificate or enter the contents of the certificate.

    Using simple or bulk edit mode, click the Add icon to add additional certificates.
    Truststore File

    Path to the local truststore file. Enter an absolute path to the file or enter the following expression to define the file stored in the Data Collector resources directory:

    ${runtime:resourcesDirPath()}/truststore.jks

    By default, no truststore is used.

    Truststore Type Type of truststore to use. Use one of the following types:
    • Java Keystore File (JKS)
    • PKCS #12 (p12 file)

    Default is Java Keystore File (JKS).

    Truststore Password Password to the truststore file. A password is optional, but recommended.
    Tip: To secure sensitive information such as passwords, you can use runtime resources or credential stores. For more information about credential stores, see Credential Stores in the Data Collector documentation.
    Truststore Trust Algorithm Algorithm to manage the truststore.

    Default is SunX509.
    Use Default Protocols Uses the default TLSv1.2 transport layer security (TLS) protocol. To use a different protocol, clear this option.
    Transport Protocols TLS protocols to use. To use a protocol other than the default TLSv1.2, click the Add icon and enter the protocol name. You can use simple or bulk edit mode to add protocols.
    Note: Older protocols are not as secure as TLSv1.2.
    Use Default Cipher Suites Uses a default cipher suite for the SSL/TLS handshake. To use a different cipher suite, clear this option.
    Cipher Suites Cipher suites to use. To use a cipher suite that is not a part of the default set, click the Add icon and enter the name of the cipher suite. You can use simple or bulk edit mode to add cipher suites.

    Enter the Java Secure Socket Extension (JSSE) name for the additional cipher suites that you want to use.