Abstract: A portal system comprises a portal connected to at least one social backend, a portal object generator for creating a page in the portal, and a backend processing component. The portal system further performs a method comprising: integrating functionality of said at least one social backend into said portal system; implementing association information as meta data entries containing information about a social object of said at least one social backend; receiving a notification about creation of new portal objects by an integration component; creating a new instance of a social object within said at least one social backend by said integration component; receiving a new identification from a newly created social object by said integration component; inserting new social object identification into meta data of said newly created social object; and representing said social object as a portal object to a portal user.

Abstract: A portal system comprises a portal connected to at least one social backend, a portal object generator for creating a page in the portal, and a backend processing component. The portal system further performs a method comprising: integrating functionality of said at least one social backend into said portal system; implementing association information as meta data entries containing information about a social object of said at least one social backend; receiving a notification about creation of new portal objects by an integration component; creating a new instance of a social object within said at least one social backend by said integration component; receiving a new identification from a newly created social object by said integration component; inserting new social object identification into meta data of said newly created social object; and representing said social object as a portal object to a portal user.

Abstract: A portal system comprises a portal connected to at least one social backend, a portal object generator for creating a page in the portal, and a backend processing component. The portal system further performs a method comprising: integrating functionality of said at least one social backend into said portal system; implementing association information as meta data entries containing information about a social object of said at least one social backend; receiving a notification about creation of new portal objects by an integration component; creating a new instance of a social object within said at least one social backend by said integration component; receiving a new identification from a newly created social object by said integration component; inserting new social object identification into meta data of said newly created social object; and representing said social object as a portal object to a portal user.

Abstract: A portal is connected to a social backend. The portal comprises an integration component communicating with the social backend. Functionality of the social backend is integrated into the portal system by creating at least one portal object that is associated with at least one social object. The integration component comprises a portal listening component listening to events triggered by running applications of the portal, and creates an event list by filtering events associated with the social backend. A backend processing component keeps portal applications in synchronization with the social backend regarding changes on a portal side. A backend query component queries application programming interfaces of the social backend for current social objects and their states. A portal model processing component calculates actions based on passed in states of current social objects from the backend query component, and invokes corresponding application programming interface calls on the portal.

Abstract: A portal system comprises a portal connected to at least one social backend, a portal object generator for creating a page in the portal, and a backend processing component. The portal system further performs a method comprising: integrating functionality of said at least one social backend into said portal system; implementing association information as meta data entries containing information about a social object of said at least one social backend; receiving a notification about creation of new portal objects by an integration component; creating a new instance of a social object within said at least one social backend by said integration component; receiving a new identification from a newly created social object by said integration component; inserting new social object identification into meta data of said newly created social object; and representing said social object as a portal object to a portal user.

Abstract: A portal is connected to a social backend. The portal comprises an integration component communicating with the social backend. Functionality of the social backend is integrated into the portal system by creating at least one portal object that is associated with at least one social object. The integration component comprises a portal listening component listening to events triggered by running applications of the portal, and creates an event list by filtering events associated with the social backend. A backend processing component keeps portal applications in synchronization with the social backend regarding changes on a portal side. A backend query component queries application programming interfaces of the social backend for current social objects and their states. A portal model processing component calculates actions based on passed in states of current social objects from the backend query component, and invokes corresponding application programming interface calls on the portal.