Publication state cleanup
When a publication is performed, Communications Manager Repository automatically removes all saved publication states that have been superseded before the configured threshold.
You may need to perform a cleanup of old saved publication states without creating a new publication. For example, when the system becomes inactive, you can manually trigger the cleanup. For that, use the PurgePublications.exe command-line tool that resides in: <deploy root>\CommunicationsManager\Programs\<version>\Management\Instance.
Parameters
The tool has the following parameters:
| Parameter | Required / Optional | Description |
|---|---|---|
| Instance!Number | Required | Communications Manager instance number the tool should operate on.
For Docker, it is always set to 1. |
| Repository!User | Optional
Only required when the LDAP mode is disabled. |
User account in Communication Manager Designer. This account needs no special authorization. |
| Repository!Password | Optional
Only required when the LDAP mode is disabled. |
Password for the Communication Manager Designer user account. |
| Repository!Token |
Optional Only required when the LDAP mode is enabled. |
Logon token generated with Communication Manager Designer. For more information, see "Log in to Communications Manager Designer and Communications Manager Designer for Windows" in Communications Manager Designer Help. |
| Action!Perform | Optional | If set to
True, the cleanup is performed.
If omitted or set to another value, the actions that the cleanup would perform are shown, but not executed. |
Example 1: LDAP mode is disabled
PurgePublications.exe Instance!Number=1
Repository!User=administrator Repository!Password=******
Action!Perform=trueExample 2: LDAP mode is enabled
PurgePublications.exe Instance!Number=1
Repository!Token=1n2Z58JX
Action!Perform=true