SDC RPC

The SDC RPC origin enables connectivity between two SDC RPC pipelines. The SDC RPC origin reads data passed from an SDC RPC destination. Use the SDC RPC origin as part of an SDC RPC destination pipeline.

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. You can also configure SSL/TLS properties, including default transport protocols and cipher suites.

When you configure the SDC RPC origin, you define the port that the origin listens to for data. The port number must be specified in one of the RPC connections defined in the SDC RPC destination.

Similarly, the RPC ID in the SDC RPC origin must match the RPC ID used in the SDC RPC destination.

Configuring an SDC RPC Origin

Configure an SDC RPC origin to process data from an SDC RPC destination.

  1. In the Properties panel, on the General tab, configure the following properties:
    General Property Description
    Name Stage name.
    Description Optional description.
    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.
  2. On the RPC tab, configure the following properties:
    RPC Property Description
    RPC Listening Port Port number to listen to for data. Must match one of the port numbers associated with the SDC RPC destination that provides the data.
    Note: No other pipelines or processes can already be bound to the listening port. The listening port can be used only by a single pipeline.
    RPC ID User-defined ID. Must match the RPC ID defined in the SDC RPC destination.
    Batch Wait Time (ms) Number of milliseconds to wait before sending a partial or empty batch.
  3. Optionally, click the Advanced tab to configure advanced properties:
    Advanced Property Description
    Max Record Size (MB) Maximum size for a record. Larger records are routed to the pipeline for error handling.

    Default is 10.

  4. To use SSL/TLS, on the TLS tab, configure the following properties:
    TLS Property Description
    Enable TLS

    Enables the use of TLS.

    Truststore File The path to the truststore file. Enter an absolute path to the file or a path relative to the Data Collector resources directory: $SDC_RESOURCES.

    For more information about environment variables, see Data Collector Environment Configuration.

    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.
    Truststore Trust Algorithm The algorithm used to manage the truststore.

    Default is SunX509.
    Use Default Protocols Determines the transport layer security (TLS) protocol to use. The default protocol is TLSv1.2. To use a different protocol, clear this option.
    Transport Protocols The 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 Determines the cipher suite to use when performing the SSL/TLS handshake.

    Data Collector provides a set of cipher suites that it can use by default. For a full list, see Cipher Suites.
    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.