Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dsa_wiki:home [2017/05/11 22:52]
wikieditor [Upstream and Downstream Connections]
dsa_wiki:home [2021/09/20 14:35] (current)
Line 29: Line 29:
 To connect two DSA installations:​ To connect two DSA installations:​
   - From the downstream broker, right-click **sys** > **upstream**,​ and choose **Add Upstream Connection**.   - From the downstream broker, right-click **sys** > **upstream**,​ and choose **Add Upstream Connection**.
-  - For **Name**, specify the node name that you want to appear in the downstream tree to represent the upstream broker. +  - Specify connection settings as follows: 
-  ​- For **Url**, specify the port, followed by ''/​conn'', ​for example ''​http://​localhost:​8081/​conn''​. +  * **Name**: The node name that you want to appear in the downstream tree to represent the upstream broker. 
-  ​- For **Broker Name**, specify the name that you want to appear in the upstream tree to represent the downstream broker. +  ​**Url**: The connection endpoint; ​for example ''​http://​localhost:​8081/​conn''​. 
-  ​- For **Group**, specify the permission group for the upstream ​broker. +  ​**Broker Name**: The name that you want to appear in the upstream tree to represent the downstream broker. 
-  - Log in to the upstream broker. +  ​**Group**: The permission group for the upstream broker.
-  - To authorize the downstream broker to remove it from quarantine, from the upstream broker, choose **sys** > **quarantine** > **Deauthorize**,​ and specify the downstream ​broker.+
  
 +To remove the downstream broker from quarantine:
 +  - Log into the upstream broker.
 +  - Choose **sys** > **quarantine** > **Deauthorize**,​ and specify the downstream broker.
  
----- 
  
 +----
 ===== Supported Data Types ===== ===== Supported Data Types =====
-DSA supports ​these data types: +DSA supports ​the following ​data types: 
-  * **String**sequence ​of characters or an empty string. + 
-  * **Number**A number or a null value. +  * **String**series ​of characters or an empty string. 
-  * **Bool**A true or false value. +  * **Number**A number or a null value. 
-  * **Array**An array object or a null value. The values in the array are of the dynamic data type. An example array of number +  * **Bool**A true or false value. 
-values is ''​[2,​3,​5,​7,​11]''​. An example array of map values is ''​[{"​hello":"​world","​number":​1},​{"​hello":"​world"​}]''​. +  * **Array**An array object or a null value. The values in the array are of the dynamic data type. An example array of number values is ''​[2,​3,​5,​7,​11]''​. An example array of map values is ''​[{"​hello":"​world","​number":​1},​{"​hello":"​world"​}]''​. 
-  * **Map**A map object containing key/value pairs, or a null value. The key is always a string, and the value is the dynamic data type. An example value is ''​{"​hello":"​world","​primes":​[2,​3,​5,​7,​11]}''​. +  * **Map**A map object containing key/value pairs, or a null value. The key is always a string, and the value is the dynamic data type. An example value is ''​{"​hello":"​world","​primes":​[2,​3,​5,​7,​11]}''​. 
-  * **Binary**A byte array expressed as a string, or a null value. The string begins with ''​\u001Bytes:''​ and ends with a byte array encoded in base 64. +  * **Binary**A byte array expressed as a string, or a null value. The string begins with ''​\u001Bytes:''​ and ends with a byte array encoded in base 64. 
-  * **Dynamic**A value that can be any of the above types.+  * **Dynamic**A value that can be any of the above types.
  
 ---- ----
Line 57: Line 59:
 If you are installing DSA on a Raspberry Pi, BeagleBone Black, or DGBox, you can also follow the steps in [[http://​www.dglogik.com/​company/​blog/​206-raspi-dsa|this blog post and video]]. If you are installing DSA on a Raspberry Pi, BeagleBone Black, or DGBox, you can also follow the steps in [[http://​www.dglogik.com/​company/​blog/​206-raspi-dsa|this blog post and video]].
  
-If you install DSA with DGLux5, and do not have a DGLux5 ​license, follow the steps to request a license when you are prompted to do so.+If you install DSA with DG Solution Builder, and do not have a DG Solution Builder ​license, follow the steps to request a license when you are prompted to do so.
  
 ---- ----
  
-===== Orientation to the DGLux5 ​Data and Metrics Panels with DSA ===== +===== Orientation to the DG Solution Builder ​Data and Metrics Panels with DSA ===== 
-The following image shows the [[dglux5_wiki:​workspace_and_workflow:​panels_and_menus:​data_panel|Data panel]] and [[dglux5_wiki:​workspace_and_workflow:​panels_and_menus:​metrics_panel|Metrics panel]] in DGLux5 ​when DSA is used.+The following image shows the [[dgsb_wiki:​workspace_and_workflow:​panels_and_menus:​data_panel|Data panel]] and [[dgsb_wiki:​workspace_and_workflow:​panels_and_menus:​metrics_panel|Metrics panel]] in DG Solution Builder ​when DSA is used.
  
 {{:​dsa_wiki:​data_metrics.png?​300|}} {{:​dsa_wiki:​data_metrics.png?​300|}}
Line 191: Line 193:
  
 ---- ----
-====== The C Broker ====== + 
-The C Broker is a small-footprint ​version of the DGLux Server (to be precise, the DART Broker). The C Broker ​is intended for embedding in devices where economy of scale is important. This document tells you how to build, configure and launch the C Broker. This document assumes you are familiar with DSA and DGLux5. ​+/*====== The C Broker ====== 
 +The C Broker is a small-footprint ​DSA broker that is intended for embedding in devices where economy of scale is important. This document tells you how to build, configure and launch the C Broker. This document assumes you are familiar with DSA and DGLux5. ​
  
 The C Broker receives data from devices by way of DSLinks, in the same way as the DGLux Server. To use the DGLux5 GUI to manage DSLinks that connect to an instance of the C Broker, install and run the LifeCycle Manager as described below. The following figure shows a standard topology on the left and an embedded topology on the right. The C Broker receives data from devices by way of DSLinks, in the same way as the DGLux Server. To use the DGLux5 GUI to manage DSLinks that connect to an instance of the C Broker, install and run the LifeCycle Manager as described below. The following figure shows a standard topology on the left and an embedded topology on the right.
Line 379: Line 382:
 ===== Troubleshooting ===== ===== Troubleshooting =====
 Both the C Broker and LifeCycle Manager log all their messages to standard output and do not create any physical logs. Both the C Broker and LifeCycle Manager log all their messages to standard output and do not create any physical logs.
 +
 +----*/
 +
 +
 +**Using This Wiki**
 +
 +[[dsa_wiki:​dslinks:​home | DSLinks]]