Carlos Coutinho Ruben de Juan

The C2NET POMA Manager module does { description of the module }

This page includes two Git repositories:

  • Code relates to the code developed to implement this module, and
  • UI is code that will be integrated with the UCP for the User Interface.

Additionally, this page includes a Tickets entry to handle specific issues regarding this module as a whole (which may include management, integration, new features, etc.).

Module Development:

Development Status: POMA Manager
Responsible: CMS
Other Participants:

Features:

Requires: (none)

Dependents: (none)


Related

Ticket: #187
Ticket: #86
Ticket: #87
Ticket: #88
Ticket: #89
Ticket: #94
Ticket: #95
Ticket: #96
Ticket: #97
Ticket: #98
Ticket: #99
Ticket: #100
Ticket: #101
Ticket: #102
Ticket: #103
Ticket: #104
Ticket: #105
Ticket: #106
Ticket: #107
Ticket: #108
Ticket: #109
Ticket: #165
Ticket: #166
Ticket: #167
Ticket: #168

  • Luis
    Luis
    2017-01-03

    • POMA has a mechanism that uses Quartz to schedule the received OP from OPC. This mechanism is already launching jobs periodically.

    • POMA schedules the OPs in RAM storage, which means that every time POMA starts, it needs to schedule all OPs that exist in C2NET DB. The best way is to define a database for Quartz, which enables persistent schedule for the OPs, this removes the need to load all OPs from C2NET DB every time POMA starts. We can implement this DB inside the POMA component, but since C2NET already has a central database, is it possible to have the Quartz DB inside the C2NET DB?

    • The mechanism to trigger event-based jobs still need to be implement, but more info about COT component is needed. From "AutomaticLaunchOptimization" diagram, is COT who is launching the optimization problem (by using the Job Executor) affected by a specific event.

    • Methods for managing OPs still need to convert the received request codes for those used by Dssql ("TO_BE_REDESIGNED").

     
    Last edit: Luis 2017-01-03