Skip to main content

How a Global Admin knows about the communities to modify?



Moderation in Connections 4.5  is an awesome feature, but may be pretty cumbersome. If you decide to moderate everything before it get published (ex-ante), you will enforce an strict rule over you social network. If you moderate after publishing (ex-post) ,you are basically relying on good will of other users flagging content around your organization. 

IBM Connections not offers you the very powerful role of Global Admin. It's a J2EE role, it is present both on Communities and Search (and other features too), but now let's focus on these two features.
So, a global admin can do everything on every community: great stuff, but how he gets to know a community exists?  With the basic community ui you have access to 

1) Communities you own
2) Communities you are a member of
3) Public communities

And the global admin role technically is neither of three. That's why the global admin role is also on search application, where he can see everything. So global admin could simply go to the search panel and looks for all communities? Well, the problem is search UI by default  will not accept a blank search argument. So you have to search for a letter, or something. So you won't have access to every community! How you can do this without using wsadmin script? Very simply using the atom feed!

http://connections.ibm.com/communities/service/atom/communities/all

This will show you every community you are entitled to see! So, if you are global admin, it will allow you to modify every community in your Connections! 

Comments

Popular posts from this blog

Multiple controllers with Spring Boot

Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work So these two together will NOT work (or just one of them will work) These two instead WILL work.

WASService.sh and ulimit.... a tricky combo

From version 7 onward, the Application Server scripts and configuration scripts have the good manner to set by themselves the right ulimit valu. So ulimit is now less a problem than it was before. The problem is that, sometime when dealing with linux services,things do not always get right. For example you get exceptions such as [11/14/13 12:06:15:483 CET] 00000066 exception     E com.ibm.ws.wim.adapter.ldap.LdapAdapter authenticateWithPassword                                  com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E  The 'javax.naming.CommunicationException: ldapus.ldap.domain.com:389 [Root exception is java.net.SocketException: Too many open files]' naming exception occurred during processing. (In case you are asking, yes, network connections are counted as open files) That's why I strongly suggest to modify your /etc/security/limits.conf (on RedHat) bef...