Saturday, 6 March 2010

Creating and updating blogs in ... WebSphere Portal Express 6.1.5

Having spent some time playing around with the new blog and wiki templates in WP/WCM 6.1.5, one of my clients asked how a non-administrative user could create new blogs and add comments to existing blogs.

I realised that, in my limited exposure to the new components ( which are a very clever combination of portal page automation - creating new pages and adding components via a very nice GUI - and Lotus WCM content and resource libraries ), I'd done everything as the wpsadmin ID, which isn't particularly useful outside of my own Ubuntu-based demonstration environment.

Therefore, I dug into things a little bit more, and wrote up the following: -


In order to meet the requirement of a non-admin user creating/editing blogs, you'd need to add the required additional users/groups to the Editor role of the WCM library that forms the basis of the blog itself.

As an example, I created a new page called My Blogs, and then used the Blog Template library to create a blogging site called Blog-o-matic ( I did this via the Edit Page -> Customise -> Add Blog Library dialogue, as the portal administrator - wpsadmin ).

This allowed me to create blogs within the library, and add posts and comments. Other users could see the page/blog library/blogs/comments, but weren't able to create their own blogs etc.

Therefore, as wpsadmin, I navigated to the Administration page, and selected Portal Content -> Web Content Libraries and then clicked the Set Permissions button. From the Resource Permissions page, I then hit the Edit Role button for the Editor role and, in my case, added the "group" All Authenticated Portal Users to that role.

This means that any portal user can now log in, access the My Blogs page, create a new blog, view and comment upon other people's blogs etc.

Depending upon your requirements, you may want to restrict the usage of certain blogs to certain user groups ( in LDAP ) rather than using All Authenticated Portal Users.



And it looks sweet  ..

And here's a screenshot, by popular demand :-

 


2 comments:

Henning said...

If it looks sweet why not add a screenshot?

Henning said...

Thank you for the update, very much appreciated.

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...