HCL Connections Reviews

The status updates and the file components are valuable features. Also, we use the profiles a lot to identify people in the organization, to find new talent and for stuff like that.

Sometimes, I've been able to put a face to a name through their profile, connect with people who are other people's connections and find information faster.

There are already forms in there and I like that. Addition of the workflow and Salesforce integration would be nice. We use Salesforce a lot, i.e., both audio and video content. Similarly, IBM Sametime would also be nice.

It's very stable; there is no downtime as far as I've seen.

We've got many thousands of users on it, so it's very scalable.

The support was very good.

We were testing on a bunch of solutions. There was one from Microsoft and Oracle. We just found this one to be the most feature-rich and also it fit our organization's needs.

I was involved in the setup process to an extent. It was quite complex. There's a lot of components of the IBM Connections, i.e., the WebSphere Application Server, the DB2 database environment and other different items. It's not something that you can just click and get through the next stage.

Do your research, but give IBM Connections a full tryout. Do a PoC and I think you'll be happy.

Relationship is the most important criteria while selecting a vendor. We want somebody who is going to be there and listen to our needs/feedback.

I think that the main tools, after file management, are Activities, Community and online documentation management with IBM DOC (embedded in the system). There are many other services such as Blog, Wiki, Forum, Survey, Chat and Conference, Audio/Video, Profiles. Those services are also important, but they are not immediately implemented because other applications or services provide that functionality.

Our customers believe that Activities, Community and IBM DOC are the features that provide particular value.

All files managed by my team are generated directly in Connections, initially as personal files but shared with each other. Ultimately, files are moved into the community for reference and so shared with all members of the team.

All technical documentation is written in the wiki, which is now the central point of reference about everything necessary to work, both on the project and knowledge sharing.

The improvement's are could be more flexibility to manage files and to have a sync file area more intuitive and which respects the characteristics of other similar solutions. That feature should be also only for personal files.

I have used IBM Connections on premise since its birth. I have used IBM Connections Cloud for three years.

All versions are developed on WebSphere Application Server. When we have a well-done installation and configuration, I can confirm that it is very stable and scalable for large environments.

I have absolutely not encountered any scalability issues.

IBM support consists of several levels and we can also engage them by calling technical people directly. In some cases, IBM directly develops a fix for the system; later, this fix might become part of a future update.

Basically, I worked with IBM and the IBM Lotus product for many decades, but I also know Microsoft products, such as SharePoint, etc. I also know many new collaboration tools, but I can assert that the level of integration among the IBM products is unmatched nowadays. They are at a level that other products don't have, even if some products seem to be easier to use or more beautiful to see.

Regarding initial setup, I distinguish between the on-premise and cloud editions:

- Cloud: Everything is active immediately and you can focus directly on the product and its features.
- On premise: There is a lot of work to install and configure the environment and it depends upon which installations you need. Initial setup might be simple or complex (for example in a cluster environment, high availability, large distribution and so on).

The licensing for the two editions is more or less the same, although I think IBM solutions are cheap for the value they provide. However, the market does not seem to acknowledge this point.

As I’ve written, in the enterprise world, the competition for this product comes from Microsoft and its solutions. I do not think that integration with all services is optimal for Microsoft today. So, I chose IBM Connections and the IBM collaboration tool turned things around.

Adoption is the key that makes the difference. If you install/use it without a clear adoption plan, this solution becomes a Black Hole, which is the case for all kinds of these solutions.

We have developed a system of adoption for both solutions, and I think that in most cases, the cloud solution of IBM Connections will be the best choice. The on-premise edition is useful only if you require significant customisation and integration with internal legacy applications.

Wikis and Blogs in combination with Activities, I like to work at home, in my office and mobile without thinking about it. I can access the solution through my tablet, iPhone, BB and Browsers.

We save a lot of mails to big groups. When we want to discuss new ideas or documents, we share them and discuss them online. No one must merge multiple mail attachments after days of changes into a final one. Files and versioning saves us time and bandwidth on the mail servers.

4.5 years

Connections is based on long developed software (WebSphere, DB2, TDI) and need some hardware resources, but when you know the basics of this software it works very stable.

No

High scalable up to multiple hundreds of thousands of users. My biggest deployment handles about 80,000 users.

We used lots of products like wordpress to blog, docuwiki as wiki, bugtracker, todo apps and so on, but Connections delivers all of it integrated in one solution.

Complex, you have to install all prerequisites like WebSphere, DB2, TDI, HTTP Server.

It is the single source of truth that can be shared anywhere. This is the most valuable feature of this solution.

We are trying to save storage costs.

The mobile, Outlook, and desktop Plug-ins associated with this product need to be improved.

There were a few challenges that we have experienced with the stability of the Outlook Plug-in.

The mobile product within the good container is still not a fully matured product.

We did encounter stability issues a few times here and there.

There were no scalability issues.

The technical support is very good.

We have never used any other solution before.

It is a complete setup, which requires a Linux and Windows background.

We looked at other solutions, namely the Microsoft OneDrive for Business and Google for Work.

It is a very good solution, if you are looking for a file-sharing solution. It is scalable to a larger audience.

It's easy to use for both developers and end users.

It is easy to integrate to other parts of the company.

I haven't any particular features to request. I would like to see better stability and performance.

Stability is not good. We've been having a lot of problems lately with the fulfillments.

Scalability is okay.

Technical support is not that good at the moment.

I wasn't involved in the initial setup.

At the moment, I would say, "Think hard about it." I want to trust that a vendor is reliable.

Search functionality and notifications: The search functionality is very well developed and can be easily filtered. All search results take data security into consideration and users will only find data they actually have access to. This functionality also extends fully to the mobile app which is available for both Android and iOS.

File sharing and synchronization over the web to Windows and mobile devices: File sync is a very useful feature that allows users to synchronize files via the Connections system to Windows desktops and mobile devices (iOS and Android) automatically. Similar to how Dropbox or Google Drive would work. This feature is very useful to ensure you always have the latest versions of files available on local devices for off-line/local access.

It has improved collaboration between users. The ability to have a definitive location for data to collaborate around. The search and incidental discovery of content (not a function, but a main feature in my mind) are really key, as is the ability to share and - when necessary - un-share. Also, the ability for the system to interact with external users, as well, if the environment allows this type of interaction.

One of the most used features lately is the ability to invite external (non-company) users and collaborate with them. yhe integration of IBM Docs into the system has made it possible to use the product more widely and allow the interaction no matter what type of device a client is connecting with.

There is an issue with scaling the Solr Search add-on (see the scalability section).

I have used it since 2007, version 1.x.

Deployment can be complex, depending on the customer environment and requirements.

None if the system is configured correctly

The system scales very easily, with the exception of Solr search (search type-ahead), which is only a single server install at this point and cannot be clustered. Currently, implementation only allows for a single search node, so it is a single point of failure when implementing this technology. All of the other components can be scaled and have multiple instances running on multiple physical/virtual machines for better performance and redundancy but Solr cannot.

Technical support is hit-and-miss. In general, the support staff is willing, but there is a large range of capabilities among them, from mediocre to excellent. In this respect, they are not much different from most other professional support organizations, though.

I did not previously use a different solution.

Setup is not overly difficult, but there are multiple components that need installing and integrating. Also, the documentation is not the best and the problem is not getting a base install running (that is not that hard); it is adjusting the system to the individual needs that each client has that can be challenging.

I am an implementation specialist for Connections; I am the guy that gets called in to do the installation. Experienced clients (who have had the system for a while) can do an upgrade themselves; an initial install might be a bit more difficult without an experienced hand to help.

Get somebody to help you with the initial planning and install. The most important part of this product is not the technology but rather the effort you put into adoption of its usage. People will not just flock to it to use it; you have to work at making it valuable to users.

The most valuable feature is Files, because we are working together with our accounting department in different countries.

It's much easier to have control of what's been done and what's not been done. We can even write comments on the board, and again get all the updates when something has been done.

For instance, when you open a Microsoft Excel spreadsheet, you just get a copy of it; you can't put it up again.

Stability is perfect.

I have not used technical support.

I wasn't actually involved in the initial setup.

When looking for a vendor, price is the most important factor for us.

Just do it right now.

• Activity: Because this app offers a lot of possibilities. Our users use this a lot for meetings and do their work in it (Getting Things Done principle and other methods for doing your work such as lean management/agile stuff).
• Communities: To work together with good collaboration. It offers lots of possibilities to collaborate.
• Activity Stream: See what has happened in our network in a short overview, without having to open up all of the tools you are using in collaboration. You don't need mail notifications anymore!
• Wiki: This is a very useful tool for information and means having fewer documents. We use wikis a lot for our intranet (WebSphere portal) and in the communities to inform people about themes and work.
• File sharing: There is no need to mail documents, but rather we can share them in Connections. The possibility to share individual documents with anyone you choose is a great feature in comparison with home and shared drives.
• Forum: For all questions and discussions is great.

Having all features and tools together in one environment is great and gives the users a lot of possibilities to work in the way that want to. We see a great variety of use with these tools.

We collaborate in a different, more effective way, with less mail and less physical meeting time. It supports the new way of working a lot. This solution makes it possible to work in a different way. In other words, working in a more social way with more collaboration.

I would like to see a better UI and more user-friendly user interfaces. I would like to see them make the tool easier and more intuitive.

We hear complaints from our users that Connections, and other IBM products, are not intuitive.

The users find it difficult to find content. The menu and action buttons are not that simple. It is not easy to understand how to use the solution and what action to take.

Not all the apps work the same way with the same buttons for the same actions. An example is the tag cloud. It is not active or looks the same in each location. Sometimes there is a tag cloud in one app, but it isn't there in another app.

It does not have a very visual look and feel. There is a lot of text and many types of menus and menu columns. The locations can be one at the top, one on the left, one on the right, and each one might have a different look and feel.

Every app has its own way of working and makes it hard to understand why it all works in a different way.

It's hard to explain for me, because I've been using it for many years now. It is very familiar to me now and I'm fully used to it. But first-time users experience lots of confusion about what to use for which purpose, and how to use it.

We have been using this solution for four years.

There were a few stability issues.

There were scalability issues. Maximum volume of activity creates a lot of problems. We need more storage.

I did not have contact with support. Our administrators worked with them. We have had different issues and lots of trouble with technical support in the past.

It took us a lot time to upgrade to new versions. A whole new installation is needed to upgrade. That is a big problem.

It takes a lot of money and time, and that is a great loss. Companies are not willing to do upgrades frequently and are often a year or two behind the new versions. Because of this, they are missing a lot of new features.

Be aware that this is a whole new way of working. The product needs an adoption process to help all users. And you need a goal for the solution. Otherwise, you face the risk that only a few users will learn how to use it.

Start with understanding why you want to use it. Be aware that you need the CEO and the rest of management to embrace it to be successful.