Publishflow Block : Initialization: Difference between revisions
From MoodleDocs
(New page: For the entire MNET ensemble to produce its "learning system" effet, each MNET node within the network needs to know the platform type of his peers. Moreover, this initialization brings in...) |
Tim Bahula 2 (talk | contribs) m (→top: clean up, typos fixed: deployement → deployment) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
For the entire MNET ensemble to produce its "learning system" effet, each MNET node within the network needs to know the platform type of his peers. Moreover, this initialization brings into each Moodle a proxy representation of the available categories of the remote peers. This will allow a better performance when proposing targets for publication and/or | [[Course Publishing block (publishflow)|Back to index]] | ||
For the entire MNET ensemble to produce its "learning system" effet, each MNET node within the network needs to know the platform type of his peers. Moreover, this initialization brings into each Moodle a proxy representation of the available categories of the remote peers. This will allow a better performance when proposing targets for publication and/or deployment. | |||
==Getting knowledge of the network topology== | ==Getting knowledge of the network topology== | ||
| Line 5: | Line 7: | ||
The herein procedure must be run on each platform belonging to a Publishflow ensemble. | The herein procedure must be run on each platform belonging to a Publishflow ensemble. | ||
* Go to the Administration > PLugins > | * Go to the Administration > PLugins > Blocks > Manage blocks menu | ||
* Enter in the "Course publication/deployment" | * Enter in the "Course publication/deployment" configuration page | ||
* Run the "Adcquiring the network structure" script. | * Run the "Adcquiring the network structure" script. | ||
Tou should observe the network configuration table being fed with each node's description. | Tou should observe the network configuration table being fed with each node's description. | ||
Additionally the description of the remote category tree is stored to speed up category choice when deploying. | |||
Latest revision as of 15:47, 22 September 2021
For the entire MNET ensemble to produce its "learning system" effet, each MNET node within the network needs to know the platform type of his peers. Moreover, this initialization brings into each Moodle a proxy representation of the available categories of the remote peers. This will allow a better performance when proposing targets for publication and/or deployment.
Getting knowledge of the network topology
The herein procedure must be run on each platform belonging to a Publishflow ensemble.
- Go to the Administration > PLugins > Blocks > Manage blocks menu
- Enter in the "Course publication/deployment" configuration page
- Run the "Adcquiring the network structure" script.
Tou should observe the network configuration table being fed with each node's description.
Additionally the description of the remote category tree is stored to speed up category choice when deploying.
