WSM is a set of python services with focus on manage and calculate daily working hours. This entire project are build keeping in mind integrations with main daily working hours management systems like Microsoft Active Directory, IBM Resource Access Control Facility (RACF). The entire project are separated in five main aplications:
-
Session Server: API that are built with FASTApi tecnology, this part of project hold the entire endpoints to manage user working hours, add, update and remove data that corresponds to clients working hours and also get direct messages from the user of interface, like HR employees to clients. Thats the main user interface.
-
Session Updater Connector: This component read a rabbitMQ queue called "pooling_contas" that is populated from API and deliver this messages to other queues that the name are the same inserted previously into database in table "targets". Each target represent a new queue and a new resource like AD or RACF resource.
-
Session Agent Updater: The main ideia to this component is a reader from rabbitMQ queue called "session_agent" and rewrite the message to a new ZeroMQ queue with ROUTER-DEALER method, this new queue will be read to a other component. This component only holds a client messages like workhours update/insert and direct messages.
-
WSM FlexTime Connectors: This component are responsible to calculate the workhours of users that can't have fixed workhours time.
-
WSM Router: This component manage the entire messages with client, redirect API messages to clients or receive/response client criptographed messages. This component works like a Certificate Authority too, doing all the response and receive certificate assign requests etc.
-
WSM AD Connector: This component read basically the same messages that Session Agent Updater read, but redirects into ZeroMQ queue to Active Directory Service, using ZeroMQ with request response method.
-
WSM Archive Processor: This component manages rabbitMQ messages from WSM Router that refers to users sessions that make logon or logoff events in the client and store into audit database.
-
WSM Audit Server: This component are resposible to maintain historycally all user sessions, to auditory purposes. This module have the self database and the data stored in this database comes to WSM Archive Processor.
Below we have a entire project structure, the components in red refers to this components that we explain earlier:
The database structure are deployed using PosgreSQL, and here we have the structure, keep in mind that structures will be change in the future, when this entire solution will be upgraded.
In the last but not the least each project module is discribed into README files inside the module directory.