<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic //J engine in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64370#M40570</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I work for the Atos company. We use BPMN for our payment applications.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Among all our BPMN models we have "transaction processing" model types. These models do not require any human intervention and we want them to be as fast as possible. So no human task in it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I made quite some tests on the Activiti engine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It works nicely for most of our needs.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;However when it comes to the threading customization or if we need to have a very fast process, the engine is maybe not suitable anymore for us. The DB is of course the primary bottleneck. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We developed a tool named //J that is perfectly suitable for such a kind of BPMN models. This tool is open source and available here : &lt;/SPAN&gt;&lt;A href="http://www.parallelj.org/" rel="nofollow noopener noreferrer"&gt;http://www.parallelj.org/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So one idea we had was to convert these BPMN models into //J ones for "transaction processing" models. We have a POC that works for basic BPMN models diagrams but we haven't made any decision yet.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Maybe you are interested in such a thing. If that so we'd be glad to discuss it with you ! I'm sure you have lots of ideas in mind.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Many thanks !&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jean-Sébastien Scrève.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Nov 2011 15:18:30 GMT</pubDate>
    <dc:creator>jscreve</dc:creator>
    <dc:date>2011-11-24T15:18:30Z</dc:date>
    <item>
      <title>//J engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64370#M40570</link>
      <description>Hello,I work for the Atos company. We use BPMN for our payment applications.Among all our BPMN models we have "transaction processing" model types. These models do not require any human intervention and we want them to be as fast as possible. So no human task in it.I made quite some tests on the Act</description>
      <pubDate>Thu, 24 Nov 2011 15:18:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64370#M40570</guid>
      <dc:creator>jscreve</dc:creator>
      <dc:date>2011-11-24T15:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: //J engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64371#M40571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What kind of transaction handling is implemented in the //J tool to overcome the limitations of the DB?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Do you mean it would be feasible to integrate //J in Activiti?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Nov 2011 13:23:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64371#M40571</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2011-11-25T13:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: //J engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64372#M40572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We don't have transaction mechanisms. Or I would say : there will be a transaction mechanism for loops only. That's why it is so fast. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also : the model and links are not read from the DB. Everything is in the generated Java code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Of course such a behavior is useful when we have Service Tasks only, no human tasks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So it's faster because we almost don't use the DB, everything is in the Java code. And we can configure threads the way we want.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As far as we are concerned, we consider using //J as the engine for such kind of processes. We have a prototype actually working : we generate //J diagrams from Activi diagrams.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Nov 2011 13:54:56 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64372#M40572</guid>
      <dc:creator>jscreve</dc:creator>
      <dc:date>2011-11-25T13:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: //J engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64373#M40573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What kind of database did you use for your tests ? Have you tried Activiti with in memory DB ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Atif&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jan 2012 21:36:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/j-engine/m-p/64373#M40573</guid>
      <dc:creator>atifelkhachine</dc:creator>
      <dc:date>2012-01-25T21:36:46Z</dc:date>
    </item>
  </channel>
</rss>

