Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
docs:3500:0300 [2023/04/05 05:54] – seandocs:3500:0300 [2025/06/12 02:35] (current) – Rename to AwareIM aware_support3
Line 3: Line 3:
 ====== Adding custom processes ====== ====== Adding custom processes ======
  
-The following section describes how to write extensions implementing custom processes and plug them into //**Aware IM**//.+The following section describes how to write extensions implementing custom processes and plug them into //**AwareIM**//.
  
 To implement custom processes and add them to the configuration of your application follow the steps below: To implement custom processes and add them to the configuration of your application follow the steps below:
Line 11: Line 11:
  
 The rest of the section describes how to write the code implementing the custom process (step 1 above). The rest of the section describes how to write the code implementing the custom process (step 1 above).
- 
-===== Writing code for a custom process component ===== 
- 
-When writing a process it is important to understand how processes fit into the architectural framework of //**Aware IM**//. When a process is started //**Aware IM**// creates the //execution context//, which contains the information about the environment in which the process is running. This information contains the data about the user who started the process, the process start-up time, the information about the current database transaction as well as many other things. The execution context is available to the process as the [[docs:3500:0300:0316_executioncontext_interface|IExecutionContext]] interface. Because a process in //**Aware IM**// runs in a "sandbox" there are certain limitations on what the process can do (see guidelines later in this section). 
- 
-A process communicates with //**Aware IM**// through the call-back interface called [[docs:3500:0300:0315_iexecutionengine_interface|IExecutionEngine]]. This interface has a variety of methods that a process can use to change attributes of objects, start other processes, call services of service providers etc. 
- 
-Sometimes a particular process calls a service, which takes a long time to fulfil. In this case the call to the service may time out. If this happens the process is //suspended//. This means that //**Aware IM**// moves the process into the “standby” mode – it is no longer active and is waiting for the reply from the service provider. Whenever such reply arrives (the reply may arrive in a few seconds, hours, days or months or never arrive at all) //**Aware IM**// automatically //resumes// the process and the process continues execution from where it left off. 
- 
-The custom process component must implement ''IProcess'' interface, which has two main methods – [[pr_methods:execute|execute]] and [[pr_methods:resume|resume]]. The execute method is called when the process is started and the resume method is called when the process is resumed after having been suspended. Both methods are described in detail later in the section. 
- 
-The following guidelines should be used when writing a process: 
- 
-  * A process is not supposed to perform any operations with the database directly (such as create, open or modify database tables, manage transactions etc) – this is taken care of by the //**Aware IM**// framework. 
-  * A process generally should not take long to execute as it is running within a context of a database transaction. If a process does take a long time to execute it should every now and again send a special signal to the //**Aware IM**// framework. Having received such a signal //**Aware IM**// would suspend the process, commit the current transaction and continue the process execution (resume the process). This signal can be sent if the process throws ''SuspendProcessException'' and sets its ''resumeImmediately'' flag to true, for example: <code java>throw new SuspendProcessException (true)</code> Before doing so the process should obviously remember its current state so that it can correctly resume itself in the resume method. 
-  * If a process calls a method of the [[docs:3500:0300:0315_iexecutionengine_interface|IExecutionEngine]] interface, which throws ''ServerTimeOutException'' the process is supposed to catch this exception and throw ''SuspendProcessException'' passing the original ''ServerTimeOutException'' to the ''SuspendProcessException'', for example:<code java>try 
-{ 
-    engine.updateEntity (this, entity, null, null); 
-} 
-catch (ServerTimeOutException se) 
-{ 
-    throw new SuspendProcessException (se); 
-}</code> 
- 
-The methods of the ''IProcess'' interface that the custom process components must implement are described below: 
- 
-{{tagtopic>progref:iexecutionengine_methods&linkonly&exclude=/c_template/}} 
  
  
  
 {{simplenavi>:docs:3500:0300:}} {{simplenavi>:docs:3500:0300:}}
- 
  • Last modified: 2023/04/05 05:54