Unlocking and locking Places during an upgrade using an xml

During an upgrade from Quickr on Domino 8.5.1 to 8.5.3 FP37 I noticed that the customer had a large amount of locked Places. I didn’t want to lock them after the upgrade manually so a little Googling found some old wikis detailing the upgrade from QuickPlace to Quickr which contained the following commands.

The following commands allow you to write to xml the locked Places and then after the upgrade use that same xml to lock the Places.

load qptool report -q [PlaceIsLocked]=1 -o qptool.lockedplaces.xml
Provides a report of the locked places

load qptool lock -i qptool.lockedplaces.xml
locks the places listed in the xml

Rename of Connection Community doesn’t rename return label in Quickr

A customer has come across a problem when using the Quickr Connector for Connections.

The Connector allows a Quickr Place (called a Teamspace) to be created from within a Lotus Connections Community on the Quickr server which allows the Community members to take advantage of all the good stuff Quickr has to offer. It also synchronises the Community membership with the Quickr database ACLs.

This problem appears when the Community name within Connections changes, the Quickr Place (Teamspace) doesn’t change with it and can cause confusion for users.

I created a Community in Connections called “ben test first name”

When you enter the Teamspace in Quickr you see a return link back to the Community “ben test first name” in the table of contents.

In the Community I edited it and changed the name to “ben test second name.”

On returning to the Teamspace the return link still states the old name but the name of the Teamspace has successfully updated placecatalog.nsf and in turn the GUI.

I figured a work around which could involve editing the h_ReturnLabel field with the correct name. This agent could key off the correct field value in placecatalog.nsf or you could manually change the field value.

I logged a PMR to see whether this could be resolved with an ifix or fixpack and it doesn’t look likely. The change would mean some substantial work on Quickr so that the table of contents return link changes when the Community name changes.

It was also suggested that a possible work around could be to use a generic return link (like in the Community “Quickr Teamspace” in the first screen shot) but that again would mean some substantial work.

I have raised an enhancement request to address this in a future release of Quickr possibly 8.5.2.

How to change the Placetype of a Place in Quickr

Once you have created a Place in Quickr it’s not easy to change the Placetype to another for example switching “Standard” to a custom Placetype.

In the Placecatalog you can see

Open \LotusQuickr\bentestplace\main.nsf.

Create an agent to change  h_PlaceTypeName to the name of the custom Placetype.

Run the agent against h_PlaceTypeStamp and check that the value has now changed.

Run load qptool upgrade -p bentestplace -f which will change the PlaceType in the Place Catalog to Custom Placetype, designer will run and the Place will change to the custom Placetype*

*Replaces the elements of a place with the elements in its parent PlaceType. Use this argument with caution because with the exception of elements created in a place that do not originate from the PlaceType, use of the argument removes all changes to elements made directly in the place.
If you do not use this argument, the command refreshes a place with elements from its parent PlaceType, but retains changes to elements made in the place.

Communities/Quickr Connector – Community creator is not the owner of the Teamspace in Quickr

When the Quickr Connector is installed into Communities (Connections) a Quickr Teamspace can be created and linked to the Community to further increase collaboration.

The creation of the Teamspace within Quickr doesn’t use the Community owners credentials but the authentication alias resource created within the ISC.

This can cause confusion for the user who has created the Teamspace from the Community because their name does not appear as the owner. The default setting is for the creator of the Community to be given Manager access to the Teamspace in Quickr but by changing the communities-quickr-config.xml as detailed below the Community owner will now be listed as an owner in Quickr.

From:
<comm:ownersRole>Manager</comm:ownersRole>
To:
<comm:ownersRole>Superuser</comm:ownersRole>

eg

QuickrPlaceType name=”DominoTeamspace” enabled=”true”>
<comm:managedApplicationTypeID>QuickrDominoTeamspace</comm:managedApplicationTypeID>
<comm:placeTemplate>Standard Place</comm:placeTemplate>
<comm:server>DefaultServer</comm:server>
<comm:resourceBundleName>com.ibm.lconn.comm.quickr.resources.QuickrTeamspaceResources</comm:resourceBundleName>
<comm:ownersRole>Superuser</comm:ownersRole>
<comm:membersRole>Editor</comm:membersRole>
<comm:publicRole>Reader</comm:publicRole>
<comm:contentFeedLink>content</comm:contentFeedLink>
</comm:QuickrPlaceType>

When creating a new Teamspace from a Community the owner will be wpsadmin as well as  the user. This may still cause confusion with users asking “who is wpsadmin?”

The way to remove wpsadmin is by removing it from the members folder within the Quickr Teamspace BUT the members folder is hidden by default because the ACL is managed from the Community.

As of Quickr Fix Pack 12 you can now show the members section by using the code below which should be in your qpconfig.xml. Once you have made the below changes, restart HTTP on the Quickr server, have the user log into their Quickr Teamspace and enter the members folder and then remove wpsadmin. Removing wpsadmin will not break the synchronisation of the ACL with the Community.

connection_integration
======================

place_creation
==============

show_members_folder_in_toc
==========================

attribute         value    default  description
=========         =====    =======  ===========
enabled        true     no         Show the members folder when a Quickr place is created from within a Community.
false    yes      Hides the members folder.

–>
<!– =============== START OF SAMPLE =================
<webservices enabled=”true”>
<atomws_response type=”get” />
<connector_install_url>http://server.lotus.com/qkrconn.exe</connector_install_url&gt;
<connectors>
<add_place_action enabled=”true” />
<views_include_rooms enabled=”false” />
</connectors>
<connection_integration>
<place_creation>
<show_members_folder_in_toc enabled=”true” />
<use_short_place_name enabled=”true” />
</place_creation>
</connection_integration>
</webservices>
=============== END OF SAMPLE =================== –>