Uninstalling Module Suite
Uninstallation procedure¶
We will refer to the Content Server installation directory as %OTCS_HOME%
Before proceeding with the uninstallation of Module Suite modules you need to complete some housekeeping routines. These routines are not strictly mandatory and should only be performed if you do not intend to reinstall the Module Suite on your system in the future.
-
Shutdown CSEvents feature:
This feature generates records in the Distributed Agent framework table, which are then managed by the CallbacksManagerCS handler. After uninstalling the Content Script module this type of handler will not be longer available, with the result that several errors will be generated in the DA framework's tables. To prevent these errors from occurring, it is safer to disable the feature completely and wait for all occurrences of this type of activity to be processed by the DA.
- From the Administration Home, select AnswerModules Administration > Base Configuration, then enter 34 in the amcs.core.debugEnabled property and save the current configuration.
RESTART REQUIRED
A service rest of all the nodes that are part of your cluster is required.
amcs.core.debugEnabled is now 'Module Suite - Configuration Options'
In recent version of Module Suite the property amcs.core.debugEnabled has been associated with the label Module Suite - Configuration Options in the Base Configuration
- Once all the nodes have been restarted wait until all the occurences of CallbacksManagerCS jobs have been processed and removed from the DA table. You can monitor this process by executing the query below:
1 2 3 4 5
select count(1) as "Total", 'WorkerQueue' as "Queue" from WorkerQueue where HandlerID = 'CallbacksManagerCS' union all select count(1) as "Total", 'WorkerQueuePending' as "Queue" from WorkerQueuePending where HandlerID = 'CallbacksManagerCS' union all select count(1) as "Total", 'WorkerQueueCurrent' as "Queue" from WorkerQueueCurrent where HandlerID = 'CallbacksManagerCS'
-
Delete all Content Server's columns or facets having a Content Script script as their datasource.
-
Stop and delete all instances of worklows using Module Suite modules. Upon Module Suite uninstallation all the currently active workflows, which make use of a feature related to one of the Module Suite modules, will not be able to continue correctly, to avoid errors you must wait for these workflows to end or stop and delete them.
Modify Workflow Map
Remove any Content Script Step, Content Script Workpackage, Content Script Event Script from all your Workflow Maps
-
Stop any scheduled script
-
From the Administration Home, select AnswerModules Administration > Manage Content Script Scheduling unschedule any previously scheduled Content Script script.
-
Wait the completion of any previously scheduled script execution. You can monitor this process by executing the query below:
1 2 3 4 5
select count(1) as "Total", 'WorkerQueue' as "Queue" from WorkerQueue where HandlerID = 'ScheduleCS' union all select count(1) as "Total", 'WorkerQueuePending' as "Queue" from WorkerQueuePending where HandlerID = 'ScheduleCS' union all select count(1) as "Total", 'WorkerQueueCurrent' as "Queue" from WorkerQueueCurrent where HandlerID = 'ScheduleCS'
-
-
(OPTIONAL) Collect and delete all the Content Script, Smart Pages, and Beautiful WebForm Views Object objects on your system.
- Although not strictly necessary, this action will prevent you from having objects on your system that the application can no longer handle correctly.
In order to easily find collect and delete the afore mentioned objects we suggest you to create and execute the script below, which it will create in the same container where the script was created a collection containing all the scripts pages and views in your system.
1 2 3 4 5 6 7 8
collection = docman.createCollection(self.parent, "Module Suite Objects", "Module Suite Managed Objects") /* 43100 BWF Views 43200 Content Script 43300 SmartPages */ nodes = docman.getNodesFastWith(sql.runSQLFast("""select distinct DataID "DataID" from DTree where SubType in (43100, 43200, 43300 ) """, false, false, -1).rows.collect{it.DataID as Long}, [], [:], false, false,false) collection.addNodes(nodes)
Execute the script as Admin
Don't forget to create and run the above script as an "Admin" user to make sure you can collect all objects on your system regardless of the associated permissions.
- Although not strictly necessary, this action will prevent you from having objects on your system that the application can no longer handle correctly.
In order to easily find collect and delete the afore mentioned objects we suggest you to create and execute the script below, which it will create in the same container where the script was created a collection containing all the scripts pages and views in your system.
-
(OPTIONAL) Delete the Content Script Volume and its content.
- Although not strictly necessary, this action will prevent you from having objects on your system that the application can no longer handle correctly. From the Administration Home, select AnswerModules Administration > Open The Content Script Volume once in the volume delete the volume's content.
-
Delete Beautiful WebForm SmartEditor table.
- From the Administration Home, select AnswerModules Administration > Base Configuration then click on the link DELETE under the Manage Beautiful WebForms database section. The action will require confirmation.
-
Using standard Content Server features uninstall all the Module Suite modules
Uninstallation complete
The Module Suite is no longer on your system. We miss you already.