If you have lost the “wasadmin” account password or any other local WebSphere account, there is a rather simple way to recover it.
Just connect to the server where WebSphere Deployment Manager is running, via RDP or SSH, depending on the OS of the server, and open the “security.xml” file located under “<WebSphere_Installation_Directory>/AppServer/profiles/<Deployment_Manager_Profile>/config/cells/<Cell_Name>” for example “/opt/IBM/WebSphere/AppServer/profiles/ic-dmgr01/config/cells/ic-cell01”.
After that just search for the account name, for which you would like get the password, in the same line you should find the attribute “password”:
When creating Databases for HCL Connections 6.5 using the Database Wizard, you will find that the database “XCC” for the “Community Highlights” Application is missing. If you continue without it and you want to install all Connections Applications, you will get an error during the installation process stating that the Database for “Community Highlights” Application is missing.
To remedy this problem you will have to create the database manually, to do that, just extract the Package containing the Connections 6.5 Wizards, and navigate to the folder with the “icec” database scripts, for example:
Since HCL Connections 6 CR3, we have the possibility to install the “Highlights” Application, which basically is a light version of “Connections Engagement Center”, previously known as XCC and originally developed by TimeToAct Group.
The Highlights Application was well-received by most of our customers and many wanted to at least try out the full version of the HCL Connections Engagement Center.
So the question is, how do you update to the full Version? Well, the XCC or the HCL Connections Engagement Center was never hard to install and maintain, so the Upgrade is also pretty straightforward, that is, unless you are running Connections on Windows OS.
I have done a few upgrades on Linux OS, using the 6.0.2 Version of the setup for Engagement Center. This usually lasts about 10 Minutes and works like a charm. This process is described very well by the official documentation.
Recently, I had an issue upgrading to the full version on Windows platform, with the Connections 6 CR5 Version. Here I had to find out that the “ICECInstaller_Windows.bat” not only fails to upgrade the product, but it also messes up the Highlights Application, which won’t work after the update.
I opened a case at the HCL Support Site and I promptly got an update that the same problem could be reproduced in the HCL Test Environment and that the support is working on a fix for this issue, so stay tuned for that if you are planing an update.
It is possible to update the product manually, which is also a faster way if you know which file to “tweak”, but you may have a Licensing issue, so if you are planing on doing this, make sure to inform and get a confirmation from the HCL Sales Representative or HCL Support.
We have the possibility now to replace Textbox.io editor with TinyMCE. I like this new addition to the product and I did not have any issues with.
Replacing the old editor is really easy, basically you use the same process as updating Textbox.io.
But do take care, some formatting, in Wikis for example, will get lost after you switch the editors. So make sure to fill your test environment with some articles from the production and check with your users if this poses a problem for them.
Recently I came across a problem when exporting the Survey results to an Excel file, export to Open Document Spreadsheet didn’t work also, though export to an XML File worked without any issues.
The error in the GUI I was getting was:
We are unable to process your request. If this error persists, report the problem to your administrator and provide error reference.
The errors I have seen in the Surveys Application Server log:
StandardExcep E com.ibm.form.nitro.platform.StandardExceptionMapper toResponse c29d32cb-eaf7-4c42-a9c3-eaf05d272f69 com.ibm.form.platform.service.framework.exception.ServicesPlatformException: java.lang.NoClassDefFoundError: org.odftoolkit.odfdom.pkg.OdfFileDom
AbstractFrame E com.ibm.form.platform.service.framework.AbstractFramework frameworkEvent Framework error: java.io.IOException: Exception in opening zip file: /tmp/ibm.fsp.temp.1559308546569/configuration/org.eclipse.osgi/bundles/33/1/bundlefile
The environment I was getting this error, was a Connection 6 CR4 environment, thankfully after I updated to WebSphere 184.108.40.206 and Connections 6 CR5 this error was gone. So If you get this error, make sure to update to the latest Version of WebSphere and Connections prior to contacting HCL and opening a case.
Yesterday I took part of the Webcast, “HCL Connections: The Future is Bright”, it was hosted by “DNUG” (a big thumbs up for that). In this Webcast Danille Baptiste showed us the future plans for HCL Connections. And indeed I do think that the future of the product is bright. The HCL is planing integrations with Microsoft Products, Salesforce and SAP just to name a few, and finally, a proper Integration with Domino! 🙂
I always thought that I knew about all the “Connections Assets”, add-ons developed by “IBM Services”, well I was wrong, Danielle mentioned at least ten of them of which I never heard about. And guess what, HCL will make them all generally available, they will also be installed as a part of the Connections installation.
The thing I like the most is, being able to see all the information you need on single screen/browser tab, things like that blow me away and I hope this will come rather soon:
Danielle also presented a Roadmap for Connections, at the end of the Q3 we should get the next CR, and towards the end of the year we will get Connections 6.5. From there on HCL plans to deliver a major release every year.
Here are a few more slides presented.
I like the way the product is heading, the HCL recognizes the products strengths and weakness and you can clearly see that in their vision. We will hear more of that and in greater detail at Social Connections 15 in Munich.
A while ago we had a requirement to restrict the Community types users can create, in the following I will describe how you can do that. First of these settings are primarily managed in “communities-policy.xml”, you must do the following steps to check the file out and be able to edit it.
Start the “wsadmin” command tool and give yourself the administration rights.
Navigate to the folder where you have extracted the community configuration files and open “communities-policy.xml” file in your preferred editor.
Going through the Configuration file you will get the idea what you can do. But simply editing the file won´t get the job done, we also need to make use of the “Security role to user/group mapping” in Websphere console. We will get to that towards the end. Being the case that we cannot create additional user roles in WAS, we must make use of what we have offered, so in the example bellow we will make use of the “Reader” Role in Community application.
The plan was to allow all users to create only Restricted Communities and grant the “Power Users” the ability to create Restricted and Moderated Communities, “Global” Community Administrators will still have the right to create all types of Communities, including Public Communities. In order to do that you have to take the following steps.
Add the following lines under <comm:policy>, Reader section:
Save the changes and check the configuration files back in.
After that, make sure that the WebSphere Nodes are Synchronized.
Change the Security role to user/group mapping.
By using the following settings all Users will be allowed to create Restricted and Moderated Type of Communities.
By mapping the “Special Subjects” to “None” and setting a desired User Group for “community-creator” role, we can achieve the desired settings.
After clicking the “OK” button, the application should be restarted automatically, so you do not have to restart it manually, but keep that in mind, because your users will not be able to access Communities during restart. After doing so, we should have the following result, all users can create Restricted Communities:
Power Users have additionally the ability to create Moderated Communities:
This is just one of the possibilities you have, you could for example also manipulate the configuration file to take away the ability for all users to create Restricted Communities.