A restart of Content Server, including all nodes, will be required. We recommend this disruption be considered when scheduling the uninstall of the Shinydocs Service module.
We recommend a backup or snapshot of the Content Server nodes be done before completing the steps in this article.
A backup is not necessary for Content Server Cloud Edition if deployed in Kubernetes.
This module is typically used as a bridge between Shinydrive and Content Server. Some customers, however, may be using it with other Shinydocs products.
Identify all Content Server nodes, including front-end and Admin nodes. Of these nodes, select one which will be considered the primary node to which the uninstall steps will be performed on.
Ensure all Content Server nodes are accessible, for a restart after the module has been uninstalled.
As an administrator, log into the node identified as the primary node
Open the Content Server Administration page
Navigate to Module Configuration
Select Uninstall Modules
Locate Shinydocs Service and select the X under the Uninstall column
Confirm the uninstall request
Before clicking Restart or Continue, log into all other nodes in a different browser tab or window and repeat the steps above
After the steps above have been repeated for all nodes, return to the primary node and click Restart
Wait for the primary node to come back up
Verify that you can log in
Verify that trace logs are not being generated in the Content Server <otHome>\logs folder
Perform a restart on the remaining nodes
Repeat the verification steps
The Shinydocs Service module has been uninstalled.