Funny thing at a Lotus Connections customer today. A user was complaining that he wasn’t able to upload a new version of a file into his Files due to size restrictions. After poking around I found out that the user had uploaded 492 mb of data into Files. After poking some more I found out that a maximum library size is enforced based on policy. By default all users are assigned a policy that allows for 524 mb of data hence why he was unable to upload any more data.
To solve it I changed the default policy to allow for 1 gb of data per user (after asking management). This is done using the administrative service API for Lotus Connections which is quite extensive. Below are my steps with the key values in bold.
The steps are as follows:
- Initialize the wsadmin environment
- Get access to the Files administrative services
- Find the user id using FilesMemberService.getByEmail(email) (user id is f631a9d9-07c4-4dcc-b820-1fdaefc4895c)
- Find the users library id using FilesLibraryService.getPersonalByOwnerId(id) usig the just found user id (library id is 1a60c8d1-fc59-41bc-9d89-c266a9709230). This also shows the user is controlled by the default policy (policy id 00000000-0000-0000-0000-000000000000) and that he is using 93% of the allotted space)
- Edit the default policy using FilesPolicyService.edit(id, name, size) to set a new size of twice the original size)
- Refetch information about the users library using FilesLibraryService.getPersonalByOwnerId(id) to see that the new library size has been applied
D:IBMWASprofilesAppSrv01bin>wsadmin -username wasadmin -password <password> -lang jython WASX7209I: Connected to process "server1" on node SDKFU016Node01 using SOAP connector; The type of process is: UnManagedProcess WASX7031I: For help, enter: "print Help.help()" wsadmin>execfile("filesAdmin.py") Files Administration initialized. wsadmin>FilesMemberService.getByEmail("jdoe@example.com") {isOprhan=false, email=jdoe@example.com, directoryLastUpdate=2011-01-04 17:07:57.167, id=f631a9d9-07c4-4dcc-b820-1fdaefc4895c, name=John Doe, createDate=2010-02-19 13:04:36.404, communityLastUpdate=2011-01-04 17:12:25.084, lastVisit=2011-01-04 17:07:57.167, directoryGroupLastUpdate=2011-01-04 17:12:25.084} wsadmin>FilesLibraryService. getPersonalByOwnerId("f631a9d9-07c4-4dcc-b820-1fdaefc4895c") {lastUpdate=2010-02-19 13:04:36.467, externalInstanceId=null, id=1a60c8d1-fc59-41bc-9d89-c266a9709230, type=personal, ownerUserId=f631a9d9-07c4-4dcc-b820-1fdaefc4895c, title=John Doe, label=24924863-F97C-C455-C125-74C9004077E4, externalContainerId=null, policyId=00000000-0000-0000-0000-000000000000, createDate=2010-02-19 13:04:36.467, summary=, percentUsed=0.9382985649108887, maximumSize=524288000, size=491938678} wsadmin>FilesPolicyService .edit("00000000-0000-0000-0000-000000000000", "Default Policy", 1048576000) The policy with the id 00000000-0000-0000-0000-000000000000 was updated successfully. wsadmin>FilesLibraryService .getPersonalByOwnerId("f631a9d9-07c4-4dcc-b820-1fdaefc4895c") {lastUpdate=2010-02-19 13:04:36.467, externalInstanceId=null, id=1a60c8d1-fc59-41bc-9d89-c266a9709230, type=personal, ownerUserId=f631a9d9-07c4-4dcc-b820-1fdaefc4895c, title=John Doe, label=24924863-F97C-C455-C125-74C9004077E4, externalContainerId=null, policyId=00000000-0000-0000-0000-000000000000, createDate=2010-02-19 13:04:36.467, summary=, percentUsed=0.46914928245544435, maximumSize=1048576000, size=491938678} wsadmin>
Nice step-by-step tutorial.
I’m experiencing same issue with communities, and your post was very helpful.
LikeLike