Impressions from todays Social Business project meeting:
Next week we will upgrade our existing social business infrastructure from IBM Connections Version 4.0 to Version 4.5.
Which does NOT include the new file management capabilities like nested folders. Nobody told us before. Not IBM. Not the system integrator. Nested folders are one of the main requests from the customers key users.
So we need to license and install the required IBM Connections Content Manager add on (the artist formely known as Filenet), Version 4.5 of course. Which is available, but needs to run on a separate machine.
Which does NOT include IBM Docs for collaborative content creation and editing. Which everybody expected to ship with IBM Connections 4.5. Because everybody who tested this on Greenhouse and saw the colorful slides believed in it. But this feature requires licensing and installating IBM Docs Version 4.5. Or Version 1.0.3. Which is currently not available. Maybe in three months. Current version would require some components running on Linux Red Hat, other components on Windows – and the document converter is still far from usable.
Today IBM released IBM Connections App Version 4.1 to support the features from IBM Connections Version 4.5. Which does not contain the promised “dropbox style” sync capabilities. Maybe this will come in App Version 4.5?
So what will we have after upgrading to IBM Connections Version 4.5? A new Websphere Version. Ahh. And @mentions. Ohh.
You need to understand. This is not Web 2.0 tools simply transfered to Enterprise 2.0. This is enterprise software. This is IBM.
Still think IBM Connections is one of the best E2.0 suites out there in the market. Hopefully IBM will not IBMify this solution.
Versions Out Of Control http://t.co/JROffFQ7hK
Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
RT @vowe: Versions Out Of Control – http://t.co/9iVJ9l0Hzx
Für die Nested Folders braucht man den CCM? Das klang in den Ankündigungen tatsächlich anders.
Ich habe den eben im Test Deployment ohne Probleme auf die gleiche Kiste installiert. Bin auch nirgends einen Verweis auf “needs to run on a separate machine.” gestolpert.
Ja, den CCM kann man offenbar doch ohne Probleme auf der gleichen Maschine betreiben. Ich habe auch gehört, dass Deployments mit mehreren tausend Usern so betrieben werden.
Aber wenn man die Ex-Filenet-Jungs fragt, dann erhält man eine andere Antwort.
IBM Connections Content Manager does not need to be installed on a separate machine. When installed as a new deployment together with IBM Connections (IBM’s recommendation when you don’t have Filenet P8 yet) it will become part of the same WebSphere environment.
That depends on who you ask at IBM. After I asked the right person I understood.
This is what we got from Jon Brunn (IBM; Senior Software Engeneer Social Software):
Unless they have an existing FileNet domain they absolutely need to use, we’d recommend they use the CCM installer to install FileNet.
Even if they have an existing FileNet domain they think they have to use, they might still be better off using the CCM installer to install FileNet.
Post by @alecmcint on how updating on-premises #socbiz sw is not as easy as the vendor (this case IBM) makes it sound http://t.co/e2J1JNOyqk
1. “Nobody told us before. ” -> wrong IBMer, wrong System Integrator, all relevant facts are know for over 1/2 a year.
2. IBM never said IBM Docs was part of IBM Connections 4.5.
3. IBM Connections Content Manager does not needs to run on a separate machine.
Felix, ist alles richtig, aber wer liest denn den Beipackzettel? Der Kunde glaubt den markigen Sprüchen auf den Slides. Dass aus Seite 127 dann steht: Um all dieses Features zu nutzen, brauchst Du aber x, y und z – das hört er nicht und das müßte IBM dann ein wenig lauter sagen.