Provide the tools for request creation and management(REST API, Web GUI)
Validate the requests parameters.
Manage the request life cycle (in terms of providing tools to update status, priority and other parameters)
Store the request data in DB (couch db backend)
Provide search tools on request data (REST API, Web GUI)
DBBackends (CouchDB)
reqmgr_workload_cache: stores request metadata and spec files.
reqmgr_config_cache: stores config files for parameter set which is used by RuntimeScritpt and CMSSW
reqmgr_auxiliary: stores config files to control components - users can use this to control agent functionality
wmdatamining: stores the data for request summary periodically to provide historical overview (deprecated)
acdcserver: stores file information from failed job. (Technically is it is not part of reqmgr2 since it is deployed separately but it could be integrated to ReqMgr2)
Services
ReqMgr2 APIs: RequestManager provides APIs to create, updates and retrieve data from backend database.
List of APIs are here ReqMgr2 APIs
It provides GUI for yours to create, updated and search some of the requests' information. (i.e Supports bulk assignment and reject)
CMS Production request manager
Provides threads which periodically runs in background (Cherrypy Thread)
StateChangeTasks: collect the information from the GlobalWorkQueue and WMStats to determine each individual request status and advance them if the proper condition met
HeartbeatMonitor: Monitor backgrounds services and report them to WMStats
AuxCacheUpdateTasks: update reqmgr_auxiliary db parameters periodically - currently only updates CMSSW versions
CouchDBCleanup: Clean up ACDC entries for archived workflow
WMDataMining: periodically gets the snapshot of job information in requests and updated to wmdataminig db. Which intern provides plots for different aspects of data. (deprecated)