BpmFlow
  • BPM Flow Manual
  • Introduction
    • Road Map
  • Installation
    • GemStone/S
      • Login to GemStone/S
        • Login to GemStone/S with JADE
        • Login to GemStone/S with Topaz
    • BPM Flow
      • Run Web Server from Interactive Session
      • Run Web Server from Script
    • Highcharts
    • Orbeon
  • Application Setup
    • Scripts to run the Application
    • Listing OS Processes
    • Indexing
  • Application Manuals
    • Backoffice Manual
      • Main Menu
        • Applications
          • Manage Environments
          • Manage Applications
          • Manage Orbeon Forms
          • Manage Calendars
        • Processes
          • Processes Definitions
          • Define New Process
            • Performers and Roles
            • Gateways Conditions
            • Versioning
            • Remove BPM Process Definition
            • Define a Task to run a Script
            • Bizagi Extended Attributes
            • RACI roles
            • Import Errors Codes
              • Generic errors codes
              • Activities error codes
              • Gateways error codes
              • Subprocess error codes
              • Runtime evaluations error codes
              • Interprocess Comunication codes
              • Integration error codes
              • Unsupported elements error codes
              • Transitions errors codes
          • Monitor Processes
          • Browse Timers
          • Process Categories
          • Cancelled Processes
        • Users and Roles
          • Monitor Users
          • Manage Users
          • Manage Roles
          • Import Roles and Users
          • Export Roles and Users
        • Messages
          • Inbox
          • Outbox
        • Configuration
          • User Preferences
          • Server Setup
          • Login Mode
          • Change Password
          • Set Language
          • Internationalization
    • Frontoffice Manual
      • Main Menu
        • My Tasks
          • Current Tasks
            • View Process Status
          • Finished Tasks
          • Process Categories
        • Unassigned Tasks
          • View Unassgined Tasks
        • New Process
          • Available Processes
          • Granted Tasks
        • Messages
          • Inbox
          • Outbox
        • Configuration
          • Change Password
          • Display References
          • Set Language
      • Main Menu
    • BI Manual
      • Main Menu
        • Dashboards
          • Current Dashboards
          • Old Dashboard
          • Historical Dashboard
        • User Charts
          • My Charts
        • System Charts
          • Global Charts
          • Applications Charts
          • Untitled
          • Processes Charts
            • Creation Day
            • Field Values
            • Field Evolution
            • Processes Average Time
            • Processes Instances
            • Tasks HeatMap
          • Roles Charts
            • Number of Tasks
            • Number of Users
            • Unassigned Tasks
            • Users in Time
          • Users Charts
            • Current Tasks by Type
            • Possible Tasks
            • Finished Tasks by Type
            • Tasks Average Time
        • Compare Fields
          • Field Comparison
        • Chart Repository
  • Functional and Technical Information
    • Anonymous Process Creation
    • Scalable Vector Graphics Support
    • Timers
      • Event Monitor Timespan
      • Process Creation Timer
      • Task Timers
      • Timers and Caledars
    • States
      • Process States
    • Tasks Assignation Policy
    • Partial Execution Framework
      • Technical Information
      • Functional Information
    • Roles and Performers
    • Debugging Process Execution
      • Manually inspect a BPM Process Instance
      • Automatically Generate a Test Case
  • Engineering Models
    • 4+1 Architecture Models
      • Logical View
        • BPM Components Architecture
        • BPM Environments or Tenants
        • Users & Roles - Processes & Forms
        • BPM Model
        • Orbeon Form Model
        • Seaside Component Model
        • Task Creation Clockwork
        • XPDL Process Generator
        • User Messages
          • User Inbox
          • User Outbox
        • Searching Field values in Bpm Processes
      • Development View
      • Process View
        • Seaside Orbeon Integration
          • GemStone to Orbeon
          • Orbeon to GemStone
      • Physical View
      • Scenarios
    • Architecture for Atop Applications
      • Atop Model Integration with BPM Flow
        • User Methods
          • asBpmUser
          • canDelete
          • finalizeAssignment
          • getAllAvailableTaskAssignmentsIn
          • getAllTaskAssignmentsWithId
          • getApplicationsIn
          • getBackofficeApplicationsIn
          • getBpmEnvironments
          • getCurrentAssignmentsIn
          • getMyTaskAssignmentsWithId
          • getProcessInstanceCategoriesFor
          • getProperty
          • getVisibleRolesIn
          • getVisibleUsersIn
          • isInAdminsEnvironment
          • languageName
          • lateralListPagingSize
          • regularListPagingSize
          • roleName
          • rolesIn
          • take
          • transitionDisplayModeIsExpanded
          • untake
          • username
          • userOptions
        • Role Methods
          • asBpmRole
          • bpmApplication
          • bpmEnvironment
          • getApplicationName
          • isBackofficeRole
          • isGranted
      • BPM Subclassification
        • Create subclass of Bpm Process Browser
        • Create subclass of Process Task List
        • Create subclass of Role Manager
        • Create subclass of User Manager
        • Create subclass of Unassigned Tasks Bag
  • Troubleshooting
    • Requests from Orbeon
  • Orbeon Integration
    • Orbeon Persistence Layer for GemStone/S
      • Install GemStone/S
      • Install Persistence Layer
      • Manage Persistence Layer
        • workwith script
        • List of Scripts
        • upgradeGemStone script
      • Manual Configuration
        • Restrictions when Saving Forms
        • Path for Attachments
        • Maintenance of OS Files and Attachments
        • Search Types
        • Indexing
        • Forms Audit
        • Deferred Processing
      • Service Diagrams
        • Form Runner Home
        • Publish or Unpublish Forms in Form Runner
        • Form Builder Summary
        • Orbeon Form Builder Toolbox
        • Forms Summary
        • Save Form Definition in Orbeon Builder
        • Publish Form Definition in Orbeon Builder
        • New Form with one draft
        • New Form with more than one draft
        • Edit
      • Service Http Methods
        • PUT
        • GET
        • POST
        • DELETE
        • LOCK & UNLOCK
      • Technical Information
        • 4+1 Architectual Model
          • Logical View
            • Objects relation Summary
          • Development View
          • Process view
          • Physical view
          • Scenarios
          • Troubleshooting
            • Request From Orbeon
      • Migration from Relational Database to GemStone/S
        • Migration from MySQL
    • Persistence Layer Backoffice
      • Orbeon Server Configuration
      • Orbeon Application Viewer
      • Create Charts with Highcharts
        • Chart Examples
      • Migrate from Relational Database
Powered by GitBook
On this page
  1. Engineering Models

Architecture for Atop Applications

PreviousScenariosNextAtop Model Integration with BPM Flow

Last updated 5 years ago

This chapter describe how to connect a regular Business Application (atop app) to available BPM structures and interfaces to add workflow capabilities to it.

The following pictures describe the general architecture of the interaction between the Atop Application and BPM Flow. BPM Model: is the Meta Model with all BPM support to define and create processes. BPM Web: is the web interface to interact with BPM Web. Atop App Model: is the model of the Business Application to integrate with BPM Flow. Atop App - Web: is the web interface to interact with Atop App Model. BPM Atop App - Web: is the web interface that operate as a bridge between both applications.

The BPM Atop - Web application is a package composed of classes that operate in the real of BPM Flow and the Atop Application.

In practical terms these classes are subclasses of different BPM Web components that extend some functionalities to operate with both applications.

The Atop Application Model has to be updated and some methods added to be able to interact with BPM Flow. Users and Roles of Atop Application Model are the classes that require more changes in order to be integrated with BPM Flow. .

Once the and the is integrated with BPM Flow then Business Objects of the Atop Application are created as follow:

At design level there two ways to integrate a Business Application and BPM Flow and it is called integration strategy: - Parallel Integration - Contained Integration The integration strategy depends totally on the ATOP Application goals.

Parallel Integration In this integration each BPM Process Instance create (or update) collections of business objects and these objects has relations to each other. These relations form the Business Model.

Each Bpm Process Instance create or update business objects.

Contained Integration In this integration a business object contain a BPM Process Instance that is an integral part of the object. This gives the ability to insert a workflow inside a business object as a part of the object itself. In this case the BPM Process is a part of the Business Model.

More details about subclasses here.
More details about Atop Application Model integration here
model
interface
ATOP and BPM Integration