Agenda
- Create needed "Software Products" inside Rapid.Space
- Create needed "Allocation Supply" for rPLC coupler inside Rapid.Space
- Create needed "Allocation Supply" for edge server inside Rapid.Space
- Check all software is supplied on rPLC and edge server
Requirements
- an edge server
- rPLC coupler
- an account on Rapid.Space
Goal
At end of this how to you will have setup inside Rapid.Space for configuring the software and its instances for your rPLC and edge server. This howto thus is a summary of the essential configurations which you need to apply using our generic tutorials.
Create needed "Software Products" inside Rapid.Space
At time of writing of this tutorial you will need to define following "Software Products" with their respective URL(s).
Please use this tutorial to add all of these 3 Software Products.
Screenshot of Beremiz runtime "Software Product".

Screenshot of rPLC coupler "Software Product".

Create needed "Allocation Supply" for rPLC coupler inside Rapid.Space
You will need to use following tutorial and apply accordingly this table which defines the "Software Product" which needs to be allocated on respective rPLC coupler. Like described on the table below it is just one Software Product for rPLC coupler.
Server (s) |
Product to define in "Allocation Supply" |
your rPLC coupler |
rPLC coupler |
Create needed "Allocation Supply" for edge server inside Rapid.Space
You will need to use following tutorial and apply accordingly this table which defines the "Software Product" which needs to be allocated on respective edge server. Like described on the table below there are two Software Products for you edge server.
Server (s) |
Products to define in "Allocation Supply" |
edge server |
Beremiz runtime |
edge server |
oi-sensor |
Check all software is supplied on rPLC and edge server
It will take a bit of time before in Rapid.Space you can see that the "Software Products" are properly installed in respective "Servers".
This is what the view of a successful installed product looks like.
