IBM Connections 5.5 : how to expand maximum file size from default

In past I already wrote  a post about this topic for Connections 5.0 . but I saw that steps are not enough for IBM Connections 5.5 because now we had 2 directive to change.

If you have to expand the size from  512MB to 1GB follow these steps:

• open a  wsadmin prompt and make a files config checkout
• edit this value <media maximumSizeInKb="1048576"/>
• edit this vale <simpleUploadAPI maximumSizeInKb="1048576">
• checkin of files config 
• upgrade version stamp of the environment 
• restart Files Application

that's it ! 

P.s best practice say to not set files bigger than 2GB and don't forget to expand the file library policy too

IBM Connections how to: increment file maximum size

In IBM Connections 5 the default maximum size for file upload is set to 500MB
This post would be a simple reminder for the step needed to extend the size:

Start a  wsadmin client

Start files admin

execfile("filesAdmin.py")    

Check-out of files config

FilesConfigService.checkOutConfig("/opt/ibm/workdir", "ConnecitonsCell01")

Set the file masimum size to 1GB 

FilesConfigService.updateConfig("file.media.maximumSizeInKb", "1048576") 

Chek-in files config

FilesConfigService.checkInConfig("/opt/ibm/workdir", "ConnecitonsCell01")

Sync connections node

synchAllNodes()

Check the files config to see if previous command has worked fine

FilesConfigService.showConfig()

If you have expanded the maximum file size probably would be nice to expand the personal library policy too for example to  2GB

FilesPolicyService.editPersonalDefault(2147483648L)

To be sure that users gets the configuration you have to force the browser cache to be purged changing the version stamp.

IBM reccomand to not exceed   2GB about maximum file size.
If your user is working with big files i suggest also to check if http or was config for download files was done during Connections setup.

IBM Connections community and conflict when adding Files

Today a customer has asked me why adding Files app to a community he was getting a confict error

This case could happens when you try to add an app to a community but is still present inside the database an orphaned app .

This is the steps to do for fix this kind of issue:

1. start a  wsadmin prompt 
2. start files admin  execfile("filesAdmin.py")       
3. to identify the Library Id associated with the Community Id use this command                  FilesLibraryService.getByExternalContainerId("communityID")
4. To delete the library ID  use the following command                  FilesLibraryService.delete("string libraryId")

The communityID is inside the url of the community ,

This could be an example of the command in point 3:

FilesLibraryService.getByExternalContainerId("d1234567-cde1-1234-1abc-01a2b1cde3fg")

with the following output where you can find below in  red the Library id 

{maximumSize=2147483648, size=421307226, percentUsed=0.19618646521121264, summary=EL Team, createDate=Fri Jan 20 10:06:02 C
ET 2012, policyId=00000000-0000-0000-0000-000000000001, externalContainerId=d1234567-cde1-1234-1abc-01a2b1cde3fg, themeName
=default, label=We1234d404cc5_40c4_9cb9_6b43ce1f455d, title=Titolo Della Community in oggetto, ownerUserId=00000000-0000-0000-0000-000000000000, type=community, id=12345678-9a12-3abc-d4e5-aa12b34c5d67, externalInstanceId=We1234d404cc5_40c4_9cb9_6b43ce1f455d, lastUpdate=Fri Feb 20 18:03:21 CET 2015}

now you can delete the library:

FilesLibraryService.delete("12345678-9a12-3abc-d4e5-aa12b34c5d67")

and you will get this response:

The library with the id 12345678-9a12-3abc-d4e5-aa12b34c5d67 is now deleted.

Now you will be able to add Files to the community!