| Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
download [2018/06/04 16:01]
felipe |
download [2018/06/04 16:14]
felipe |
| ====== Requirements ====== | ====== Requirements ====== |
| To provide real-time communication services, the ContextNet's middleware communication layer, **S**calable **D**ata **D**istribution **L**ayer (SDDL), uses the [[wp> Data_distribution_service|Data Distribution Service (DDS)]] protocol in its core network and the [[MR-UDP]] protocol in the edges. DDS in an OMG standard for Real-Time Publish/Subscribe communication. Thus, usage of ContextNet requires the installation of a DDS implementation (vendor). Currently, we supports the following DDS- compliant vendors: OpenSplice DDS, RTI's Connext, and TwinOak's CoreDX. MR-UDP is an extended version of the Reliable UDP protocol and is included in the ContextNet middleware. | To provide real-time communication services, the ContextNet's middleware communication layer, **S**calable **D**ata **D**istribution **L**ayer (SDDL), uses the [[wp> Data_distribution_service|Data Distribution Service (DDS)]] protocol in its core network and the [[MR-UDP]] protocol in the edges. DDS in an OMG standard for Real-Time Publish/Subscribe communication. Thus, usage of ContextNet requires the installation of a DDS implementation (vendor). Currently, we support the following DDS- compliant vendors: OpenSplice DDS, RTI's Connext, and TwinOak's CoreDX. MR-UDP is an extended version of the Reliable UDP protocol and is included in the ContextNet middleware. |
| |
| ---- | ---- |
| ====== Download ====== | ====== Download ====== |
| |
| ContextNet middleware is composed of a set of components and technologies, such as [[wp> Data_distribution_service|Data Distribution Service (DDS)]], [[MR-UDP]], and [[ClientLib]]. The ContextNet middleware is distributed as a set of software modules in the form of **JAR** files. In order to develop applications based on ContextNet services you will need to include these libraries in you application build path (Eclipse, Netbeans, etc). If preferred, instead of downloading manually the JAR files, we also provide a {{icon>external-link-square}} [[https://maven.apache.org/|Maven]] repository to include the ContextNet middleware as a dependency for your project. Here are the two download options: | ContextNet middleware is composed of a set of components and technologies, such as [[wp> Data_distribution_service|Data Distribution Service (DDS)]], [[MR-UDP]], and [[ClientLib]]. The ContextNet middleware is distributed as a set of software modules in the form of **JAR** files. In order to develop applications based on ContextNet services, you will need to include these libraries in your application build path (Eclipse, Netbeans, etc). If preferred, instead of downloading manually the JAR files, we also provide a {{icon>external-link-square}} [[https://maven.apache.org/|Maven]] repository to include the ContextNet middleware as a dependency for your project. Here are the two download options: |
| |
| === Direct link to JAR files === | === Direct link to JAR files === |
| |
| ====== Running ====== | ====== Running ====== |
| To execute a ContextNet application, one needs to first create the gateway, which will instantiate the core infrastructure if none exists. You can create a gateway by running the ContextNet middleware jar file. The gateway receives three parameters: a public IP address, a given port number, and a DDS vendor implementation to be used. For example, for a local deployment, you can choose the loopback IP ''127.0.0.1'' as the gateway address, the default middleware port ''5500'', and ''OpenSplice'' as its DDS implementation. To do this, open a shell, and run the following line command: | To execute a ContextNet application, one needs to first create the gateway, which will instantiate the core infrastructure if none exists. You can create a gateway by running the ContextNet middleware jar file. The gateway receives three parameters: a public IP address, a given port number, and a DDS vendor implementation to be used. For example, for a local deployment, you can choose the loopback IP ''127.0.0.1'' as the gateway address, the default middleware port ''5500'', and ''OpenSplice'' as its DDS implementation. To do this, open a shell, and run the following line command: |
| |
| $ java -jar contextnet-2.7.jar 127.0.0.1 5500 OpenSplice | $ java -jar contextnet-2.7.jar 127.0.0.1 5500 OpenSplice |