SDC RPC (deprecated)

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.
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. 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.

For information about using the SDC RPC origin in an SDC RPC pipeline, see SDC RPC Pipeline Overview (deprecated).

Configuring an SDC RPC Origin

Configure an SDC RPC origin to process data from an SDC RPC destination. For information about using the SDC RPC origin in an SDC RPC pipeline, see SDC RPC Pipeline Overview (deprecated).

  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.
    Max 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
    Use TLS

    Enables the use of TLS.

    Use Remote Keystore Enables loading the contents of the keystore from a remote credential store or from values entered in the stage properties. For more information, see Remote Keystore and Truststore.
    Private Key Private key used in the remote keystore. Enter a credential function that returns the key or enter the contents of the key.
    Certificate Chain Each PEM certificate used in the remote keystore. 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.
    Keystore File

    Path to the local keystore 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()}/keystore.jks

    By default, no keystore is used.

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

    Default is Java Keystore File (JKS).

    Keystore Password Password to the keystore 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.
    Keystore Key Algorithm Algorithm to manage the keystore.

    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.