Stateless and State-full Process Execution

Scenario #2: Stateless and State-full Process execution

User

1
Stateless Process is
executed

Change State;
Progress to the
next in the
Initiate
Initiate Stateless
Stateless process
process process flow

1.1 1.2
<HTTP>
2.6, 2.13

xCP Application
data directory Content Server
<Application server> DFC
<file system> Docbroker port: 1489
Port: 8000

Database
2.2, 2.10 2.5, 2.12
2.1 2.9'
<HTTP> File System
Initiate
Initiate State-full
State-full process
process
Process
Automatic Task/
DFC Engine 2.3, 2.11
Events
Port: 9080

2.4
2.9

Process Integrator
2.8
Port: 8040

Incoming
Incoming email
email Send
Send Email
Email
data directory
<file system>

2.7 Email Exchange Server

User  initiates  a  “Stateless  process”  in  the  xCP  application

1.1. An HTTP request is sent to the xCP Application which is running on the application server (Tomcat/ tcServer). xCP Application parses the HTTP request
and communicates with the Content Server over DFC.
1.2 Executed by the Stateless Process Engine residing within the Application Server. The state of the Object is changed and the user should be able to view
the resultant state.

User  initiates  a  “State-full  process”  in  the  xCP  application

2.1 An HTTP request is sent to the xCP Application. xCP Application parses the HTTP request and communicates with the Content Server over DFC.
2.2 Since this is a State-full process, the request is forwarded to the Process Engine which is running in the realm of the Method Server
2.3 The Process Engine executes the task
2.4 The  resultant  of  the  execution  of  the  task  in  this  example  is  a  “send  email”  task.
2.5 The Process Engine sends back the response to the Content Server
2.6 The state of the process is changed
2.7, 2.8 The Process Integrator (PI) listens to the Email Exchange Server for any new emails
2.9 On receiving a new email, the PI processes the email and updates the repository
2.10, 2.11, 2.12, 2.13: If there is an automatic activity in the state-full process, the task is executed in the Method Server and the workflow state is
changed