Differences between revisions 23 and 24
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
|
One way to build the adaptor is using [:Adaptation]. |
|
| Line 16: | Line 18: |
|
. The user access the platform entry point. There he/she founds an authentication mechanism and a single sign on (["SSO"]) system. When the user authenticates, a message is sent via the ["MOM"] to the other applications, telling them that the user has logged in. Once the user is logged in, he/she can access the ["Desktop"], a web application used to access other applications. For instance, from the Desktop the user can use the Identity Managment System (["IMS"]), to add/install applications to his/her group (if the user is a group administrator), or to use the applications his/her administrator allows him to use (if the user is a normal user). The actions the user makes when using the IMS or other applications, can also generate messages than can be used by other applications to update their information. One way the applications can send and receive messages via the MOM is using the [:MOM:OAproject tools]. |
. The user access the platform entry point. There he/she founds an authentication mechanism and a single sign on (["SSO"]) system. When the user authenticates, a message is sent via the ["MOM"] to the other applications, telling them that the user has logged in. Once the user is logged in, he/she can access the ["IMS"] ("Identity Managment System") to edit his/her installed apps, edit users in his/her group, and to access his/her installed applications. |
| Line 22: | Line 22: |
|
= News = ---- === Test platform is up and running === There is now an integration platform for OAproject. Each developer has access to a [http://en.wikipedia.org/wiki/Xen Xen] domain. More info [:Community:here]. |
OAproject development site
What is OAproject?
OAproject is an open source implementation of a plataform to allow web applications interact between them. To do so, applications using the platform send/receive messages through a message oriented middleware.
An application, to interact with other applications in the platform, needs an adaptor. This adaptor takes care of sending and receiving the corresponding messages.
One way to build the adaptor is using Adaptation.
Structure
OAproject is made of different parts. You can find an extended explanation of each part following the links on the right menu. The image on the bottom of this text provides a schema of the different parts that compose the platform basic architecture, and the interaction between them:
This would be a typical usage case of the previous schema:
The user access the platform entry point. There he/she founds an authentication mechanism and a single sign on (SSO) system. When the user authenticates, a message is sent via the MOM to the other applications, telling them that the user has logged in. Once the user is logged in, he/she can access the IMS ("Identity Managment System") to edit his/her installed apps, edit users in his/her group, and to access his/her installed applications.
A library of messages can be found in the Documentation.
Note that not all the applications must be hosted in the same machine.