Is it ok, supposed to be, not requried, for the JMS component to be installed in the sub slave sites?

I notice that when I go to the JMS component in a slave site, that it does show all the slave sites, even ones created after the slave site in question.

the salve sites do show, PATCH to update.. etc.

Normally JMS should not be installed in slave site but only on the master website.
As some customer prefer to replicate the master website to create many slave site, this is frequent that JMS may be present in the slave site.

The access to the JMS is only autorized to a Super Administrator (not an administrator).
We have just disabled few functionalities in the slave site that may create inconsistency like the install of patches.

Personnally, we would prefer and we recommand to only install JMS on the master website and never in a slave site but we have not control on that except to disable everything.
We have let it also because sometime person are making errors and that may (not all the time) have an alternate access when for example you convert you master website into a slave site (because you have put the master domain in the list of slave).

So in summary, this is normal that you can install JMS in a slave site but it is not recommended to do it.

So then the JMS does get copied over with the replication. I want to remove it from all the slave sites, I see check boxes to propagate to slaves, but not to remove globally??!

so I uninstall the compoenent in each salve admin? or can I do it from the master, jms site admin TOOLS

The propagation checkbox is available with the action that you give to it.
So if you have created many slave site that is a replication of the master website (defined in a JMS template) and that appear as children of the master website, you will also un-instal lthe extension form the master.

Becarefull when you use the JMS tools to un-install and extension from the master website.
This will not execute the potential extrat script that may be implemented to cleanup files on the disk.
This is the case also of JMS that will not un-install the patches when you use the JMS tools to un-instal itself.

The JMS tools should be exclusivelly used with "slave site" and not on the master website except when you know exactly the potential consequence to just un-install and extension in the DB and not cleanup the files and folders on the disk.

Uninstall individually a slave is possible with the JMS tools or benefit to have create a special slave site to group a set of slave sites to simplify their management.
You can also install the extension from the slave site administation itself (as you usually do with Joomla extension / uninstall).

Edwin

I'm also seeing this and I am sorry my understanding of your last reply is not clear. and I am confused.

I wonder if you can explain it again, or if it is now in a FAQ or help page somewhere?

Also, possibly concerning this point, I notice that if I check updates in the slave site it has the error:
" * Some patches are not installed.
* Please check patches and proceed with patch installation to allow mutlisites working properly."

However from the main site all patches are installed


Thanks if you can help

I Repeat that the JMS back-end is not design to be used from a slave site.
JMS should ONLY installed on the MASTER website and should NOT be installed in the SLAVES sites.

What you are trying to do is to use JMS back-end from a slave site.
This is normal that JMS replies that it wants install patches to create a master website.
As you are working in a slave site, some patches are NOT present and you can NOT install them.

Un-install JMS in ALL the slave sites and this avoid you trying install or working with JMS back-end from a slave site.

In ALL the video in the tutorial you will not see us install JMS in a slave site.
Only on the master website.