The paper presents results from an empirical study about the use of a single sign-on (SSO) system in an integrated open source system landscape for supporting team collaboration. A portal solution, enterprise content man-agement system, groupware, business process management and enterprise search engine are used. The investigation shows that although it is easy to achieve SSO with the Web-based user interfaces of the information systems used, none of the systems was prepared to pass authentication tokens to the API of an integrated system or accept SSO tokens instead of username / password pairs for authentication against the API respectively. Different al-ternatives for achieving the desired functionality are presented and a recom-mendation for improvement of the affected information systems is derived.

Usually, knowledge workers are said to not benefit from business process management (BPM) systems, since their main tasks are weakly structured and not representable by a workflow. However, not all of their tasks are equally weak structured, and with adaptive case management (ACM) solutions, a new category of tools came up to support those processes, even if they are weakly structured. This paper introduces an approach to support the creation of cases for ACM engines by mining activities from an activity stream and suggesting tasks that a knowledge worker can use to create a case. Furthermore, the approach supports maturing of the case towards a workflow by detecting repeating sequences in the execution of tasks and suggesting sub processes for the case which is possible with the case management model and notation (CMMN) together with the business process model and notation (BPMN). To allow for further enhancement of the cases, the ACM solution is extended with social collaboration features, so that people working on the case can comment and rate single tasks. The goal is to show that it is possible to establish ties from social activities and Web 2.0 to ACM and BPM. The presented solution uses a graph database as a basis for activity mining.

This paper presents a concept for integrating social media functionality into existing collaboration systems and using this functionality to also integrate the collaboration systems themselves. Social media functionality is used in the areas contents, contacts and communication to support knowledge sharing and knowledge maturing. Using a micro-service architecture, our concept allows for social media functionality in every collaboration system. Users benefit from a better overview due to a central activity stream with entries of all systems, as well as a consistent UI. They don’t have to chose a certain tool but can use the desired functionality like rating, tagging or commenting everywhere. We further provide information about a technical implementation of the concept with popular open source software like Liferay and OpenXchange.

After the human-oriented, technology-oriented (documents), process-oriented and social KM phases, KM support now needs integration of those beneficial technologies instead of hyping one and neglecting the other. This paper proposes a highly modular yet integrated approach to support KM instruments and shows how this approach is implemented based on open source collaboration systems in the SCHub project which represents an enterprise knowledge infrastructure (EKI). The applicability is shown with three KM instruments in the areas people, contents and processes. Social media and search functionality serve as an integration factor for the EKI.

Docker provides a good basis to run composite applications in the cloud, especially if those are not cloud- aware, or cloud-native. However, Docker concentrates on managing containers on one host, but SaaS provi- ders need a container management solution for multiple hosts. Therefore, a number of tools emerged that claim to solve the problem. This paper classifies the solutions, maps them to requirements from a case study and identifies gaps and integration requirements. We conclude that the Docker ecosystem could help moving from IaaS and PaaS solutions towards a runtime environment for SaaS applications, but needs consolidation.