These steps will show you how to create a bidirectional, internal connection between your openPDC and your SIEGate nodes. This type of connection should only be used
. If you are creating a connection over an unsecured network, please see
Creating secured gateway connections
. Note that very similar steps will apply for creating GEP internal subscriptions between two openPDCs or two SIEGate instances as well.
In this demonstration setup, we have an openPDC (DEMO02PDC
) with sample data flowing in, and a SIEGate (DEMO01SIEGATE
) we wish to connect to.
We'll start with SIEGate. In the menu, click on 'Subscription' -> 'Create Internal Subscription'.
On the 'Create subscription' page, there are five things we need to enter; Acronym, Name, Hostname, Port, and which data to receive.
A brief explanation of these. Acronym refers to the short identifier for the publisher (the system we are connecting to and receiving data from) that will be used to refer to this connection. The name is longer and more descriptive, and does not have the same
restrictions. Hostname is the IP address or the hostname of the system that we are planning on connecting to. The port is different depending on which product you are connecting to, and can also vary based on the configuration. The default ports for openPDC
and SIEGate are listed for convenience. Selecting what data to receive is generally a matter of following the chart and checking the correct box(es).
In this case, the settings will appear as follows:
Once we click save, we're taken to the device configuration page. We can fill in more specific details about the connection we've setup, and can hit 'Save' to enable and start this connection.
After we've saved, we're taken to the Devices list. The connection has already started, and it's found our sample (Shelby) device.
A quick look at the graph measurements screen shows data has started to flow, as well.
If we want to create the reverse of this connection, a very similar series of steps can be followed. First, in the menu, click 'Inputs' -> 'Subscription Based Inputs' -> 'Create Internal Subscription'.
The steps from there are identical to the previous, with the exception of which data we wish to receive. Because the SIEGate is externally-facing, we'll want to grab the External metadata.