In general, we will run the process to define the definition tool to run, but sometimes it is notified that the process name must be changed, this is the problem, how to delete the process template that is discarded in the running period.
First, we know that the MQ workflow period and definition period is a relatively independent system. The two have a separate database saves their respective information, so the process that deletes the defined period will not act to the runtime.
Then, we know that the runtime data is stored in the BD2 database. If the process template related data can be clear by deleting DB2, we can find that we need to clearly master all E / R relationships, slightly inadvertent, possibly Leading serious consequences, in the case where DB2 is not disclosed, the action will have security issues, so this method is not a safe way.
So where is the safe and feasible way? We have found that the FDL script can be imported into the running period by the FMCIBIE tool, and the update script action is executed in the FDL script, then whether the DELETE action is executed? We can try it.
Insert scripts, such as Insert Process XXX, we change to delete process xxx, execute it in the form of command line through the FMCIBIE runtime tool, success!
Performing principle: FMCIBIE Script ==> MQ Series Communication ==> MQ Workflow Service Analysis Production SQL Script ==> DB2 Execution.
Through the above analysis, it can be found that the operation period data by the FDL script is a safe mode, and the process template can be used, which can also be implemented in other data changes in the defined period, such as insertion, update, delete processes, roles, organizations, The data structure, execution program, etc. are equally valid.
Note:
1.FDL statement can refer to the script file exported from the running period or defined period
2.
It doesn't seem to be effective for process instances and tasks
