ObjectGears components

ObjectGears system consists of several components, that ensure the complete functionality.

Component	Description
Web	Basic component for communication with user and external systems.
Database	Data repository of the ObjectGears system.
Windows service	Service providing processes without interaction with user (jobs, workflow, time operations...).
Administrator tool	Configuration and migration tool for environments with more ObjectGears instances.
Programme Piklo	Programme for execution of Powershell scripts
DiskSizer	Utility for finding out folder structure size.

 

All these components can run on a single server. From the view of server roles segregation, security and performance improvement it may be appropriate to:

• Operate the database on a special database server.
• Operate the windows service and programme Piklo on a special server.
• Operate the web on a special server.

Components web and windows service need for their operation technical account.

Component communication scheme

Following picture describes communication of particular components. There are two types of users displayed in the scheme, which we distinguish from the perspective of component communication.

• Common user (from this perspective we consider also IT model owner as a common user)
• Administrator of ObjectGears instance

There are only the most crucial communication relations indicated. (The scheme e.g. does not show communication with Active Directory, if Windows authentication is used or component Browser that is used at communication with web server).

 

 

 Coomunication can be initiated by:

• Common user
• Administrator
• ObjectGears Windows service
• Other system (it communicates in form of http request or web services same like Common user)

 

Number	Description
1	User (Common user or Administrator) sends http request from his/her browser to Web OG
2	Web processes the incoming request and sends a request to database
3	Database processes incoming request and sends a response to web
4	Web processes database response (data and business logic created by user and stored in the database) and sends response in form of a web page that is displayed to the user
5	When processing the request web can also call programme Piklo. Even if this is principially possible, we do not recommend that as Best practise (for reasons see description of Piklo)
6	Windows service regularly check the database and sends requests for email sending, workflow, job or time operations execution etc.
7	Database responses to Windows service requests
8	Windows service can within its activities also start programme Piklo (based on business logic returned from the database)
9	Administrator can besides web interface (see communication 1-5 above) use also a special tool.
10	Tool communicates with the database.