Difference between revisions of "OS4X Portal - plugins"

From OS4X
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
[[File:Bildschirmfoto 2019-04-08 um 13.49.31.png]]
 
[[File:Bildschirmfoto 2019-04-08 um 13.49.31.png]]
  
= Plugin groups =
+
= Transmission plugin groups =
 +
The by default provided plugin groups handle the incoming and outgoing data transmissions of portal jobs:
 +
*Portal send plugin group ''(transmit data and job meta information from the internal zone to the DMZ)'':
  
 +
[[File:Bildschirmfoto 2019-04-08 um 14.47.45.png]]
 +
 +
*Portal receive plugin group ''(handle a single job, generated in the DMZ for the transmission to the internal zone)'':
 +
 +
[[File:Bildschirmfoto 2019-04-08 um 14.48.32.png]]
 +
 +
'''After the execution of this plugin group, the recipient's plugin group (resolved by its hierarchy) is being executed on the internal zone''', so other plugin executions are done after this plugin group. The DMZ instance doesn't start the recipient's plugin group.
 +
 +
= Other plugin groups =
 +
Some helpful plugin groups exist for managing data security and internal processes of portal jobs. Optionally, these plugin groups can have fault tolerance enabled, so if one plugin in the configured plugin group is exiting with an error code (not equal zero), the plugin group is not stopped but executed until the end and the corresponding job is not aborted.
 +
 +
These plugin groups are:
 +
 +
== Internal zone only ==
 +
*Reminder plugin group for outgoing portal jobs ''(start a reminder for received portal jobs, after a configurable timeout of job inactivity)''
 +
*Reminder plugin group for incoming portal jobs ''(start a reminder for sent portal jobs, after a configurable timeout of job inactivity)''
 +
 +
== Both internal zone and DMZ ==
 +
*Plugin group for fetched outgoing portal jobs ''(handler for fetched outgoing portal jobs, typically used for cleanup tasks)''
 +
*Plugin group for fetched incoming portal jobs ''(handler for fetched outgoing portal jobs, typically used for cleanup tasks)''
  
 
[[Category:OS4X Portal]]
 
[[Category:OS4X Portal]]

Latest revision as of 12:51, 8 April 2019

Plugins

A licensed OS4X Portal instance is able to run all available plugins (also custom ones). The basis for all portal jobs is the correct configuration of the required plugins and the used plugin groups. The two main (synchronous) plugins are:

  • Portal receive job
  • Portal send job

Bildschirmfoto 2019-04-08 um 13.49.31.png

Transmission plugin groups

The by default provided plugin groups handle the incoming and outgoing data transmissions of portal jobs:

  • Portal send plugin group (transmit data and job meta information from the internal zone to the DMZ):

Bildschirmfoto 2019-04-08 um 14.47.45.png

  • Portal receive plugin group (handle a single job, generated in the DMZ for the transmission to the internal zone):

Bildschirmfoto 2019-04-08 um 14.48.32.png

After the execution of this plugin group, the recipient's plugin group (resolved by its hierarchy) is being executed on the internal zone, so other plugin executions are done after this plugin group. The DMZ instance doesn't start the recipient's plugin group.

Other plugin groups

Some helpful plugin groups exist for managing data security and internal processes of portal jobs. Optionally, these plugin groups can have fault tolerance enabled, so if one plugin in the configured plugin group is exiting with an error code (not equal zero), the plugin group is not stopped but executed until the end and the corresponding job is not aborted.

These plugin groups are:

Internal zone only

  • Reminder plugin group for outgoing portal jobs (start a reminder for received portal jobs, after a configurable timeout of job inactivity)
  • Reminder plugin group for incoming portal jobs (start a reminder for sent portal jobs, after a configurable timeout of job inactivity)

Both internal zone and DMZ

  • Plugin group for fetched outgoing portal jobs (handler for fetched outgoing portal jobs, typically used for cleanup tasks)
  • Plugin group for fetched incoming portal jobs (handler for fetched outgoing portal jobs, typically used for cleanup tasks)