Friday, April 17, 2020

HCL Connections - how manage community library file space when it's filled up

Working with Connections sometimes could happen to fill up a community usable space getting an error with new file uploads.

Connections spaces are managed with a set of policies that define the space occupation limits for communities, wikis, etc.

To manage these spaces some wsadmin commands are required. To simplify the reading of this post I've shorted the long id generated with a label like CommunityID.


First of all start the file administration:

execfile("filesAdmin.py") 

with the following command, with the communityID (visible in the URL) it's possible to get the space info's about a community library

FilesLibraryService.getByExternalContainerId("CommunityID") 

{summary=, percentUsed=99.97249487787485, label=LabelID, type=community, title=Community Name, themeName=default, externalInstanceId=LabelID, externalContainerId=6bd7b2a9-99da-4786-b0ac-a1e1bf733740, size=5367232450, policyId=00000000-0000-0000-0000-000000000001, lastUpdate=Thu Nov 12 09:21:42 CET 2015, ownerUserId=00000000-0000-0000-0000-000000000000, maximumSize=5368709120, id=LibraryID, createDate=Wed Oct 28 16:19:36 CET 2016}

the 3 red numbers are the percent of the space used, the size used and the maximum size.

As first step to fix the issue is possible to check the existing policy, to see if any policy present in the system could fix the space needed.

 FilesPolicyService.browse("title", "true", 1, 25) 

this output of the command will be a list of policy available with size (expressed in bytes !! ) , id and description

maximumSize=524288000, id=00000000-0000-0000-0000-000000000005, title=!Default for Application}

To create a new policy, eg 10GB  use the following command


 FilesPolicyService.add("10 GB Policy", 10737412742L) 

As output will be printed a PolicyID  that should be used with the assign Policy command

FilesLibraryService.assignPolicy("PolicyID", "LibraryID") 

This commands (and more) are available at  this page in the HCL docs 

 

No comments:

Post a Comment