Server Side plugin are not visible in RTC6.0
I used to deploy the plugins in 5.0.2 ccm->conf->sites folder
and ini in provision_profile folder. I used to configure it to the project area as a follow up action.
I have upgraded the server to 6.0. I am deploying plugins in the similar way. My plugin is not visible in follow up action to configure to the Project Area. Please help what needs to be done in 6.0!!
Regards,
Chandan
One answer
Also the extensions contain dependencies to the API which can include a version info. If done wrong, this can result in the plugin not being deployable. You would see all this in a 6.0 development environment.
Comments
Hello Ralph,
Also the extensions contain dependencies to the API which can include a version info. If done wrong, this can result in the plugin not being deployable. You would see all this in a 6.0 development environment.
Please can you elaborate on the above . How to check this version info.
You can see and edit the dependency versions in the development environment in the plugin.xml. You can also see errors there if you look at it in 6.0.
Dependency versions
https://rsjazz.wordpress.com/2014/06/12/is-the-extension-deployed-how-can-i-redeploy/ shows how to check if the components are available and the ccm.log would show problems that happen when loading the extensions.
why component status of a plugin is not visible in 6.0 like in 5.0.2 ?
As i check some ccm logs of 6.0 , most of the service is getting failed to be activated.
I am not seeing any follow up action to configure it to my PA.
I have proven, at least to me, that there is no change in how deployment works in RTC 6.0 and my extensions deploy fine the same way they ever have.
So my assumption is that you are doing something wrong. Since you also fail to provide any valuable information that would allow to get any idea what could be wrong, I don't think we can help.