Skip navigation
All Places > Alfresco Process Services & Activiti (BPM) > Blog

(08/01/18 - 15/01/18) Last week the team released 7-201712-EA - you can read about the 7-201712-EA release at https://community.alfresco.com/community/bpm/blog/2018/01/09/activiti-activiti-cloud-7-201712-ea-are-out

 

@constantin-ciobotaru finished modeling service for release and fixed bugs

@mteodori integrated dependency check from develop into 5.x and updated libraries with known vulnerabilities https://github.com/Activiti/Activiti/issues/1657

@lucianoprea worked on making mongo default for Audit #1661, tested the examples after the release and start looking into finding a easy way to turn on debug logging in our apps #1678

@ffazzini continued working on AWS deployment, now having used helm to solve a problem of needing to use the dynamically-assigned AWS url at deploy time

@ryandawsonuk fixed a problem with connector transaction management (#1660), improved the performance of the trending topics twitter example (#1671 ) and managed the release process for 7-201712-EA

@erdemedeiros added the node id (‘id’ attribute fro BPMN file) to Integration Requests and Integration results (https://github.com/Activiti/Activiti/issues/1655). Considered the different possibilities to improve the Integration Results delivery (https://github.com/Activiti/Activiti/issues/1666)

 

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7

If you want to get started with Activiti Cloud visit our Gitbook: https://activiti.gitbooks.io/activiti-7-developers-guide/content/

In this short post, I’ll outline the steps to launch an all-in-one installation of Alfresco Process Services (APS) using our CentOS 7.2 Linux Amazon Machine Image (AMI) available from the AWS Marketplace.

Step 1: Visit the AWS Marketplace

From the AWS Marketplace page, search for the Alfresco products.

 AWS Marketplace

Select Alfresco Process Services (BPM), then click on the Continue to Subscribe button to access the software launch wizard.

AMI for APS

Step 2: APS “1-Click Launch” on EC2

Using the “1-Click Launch”, you only need to select the region of your choice and can keep the default values for the other settings, (e.g., EC2 instance type, VPC settings, security groups and key pairs). Please ensure that this AMI is deployed to a public-facing subnet. The public subnet automatically assigns public ip addresses so the instances are accessible over the web. If you deploy the instance in a private subnet, you won't have web access to the instance.

EC2 launch wizard

Click the Launch with 1-click button. A confirmation page informs you that an instance of APS is being deployed on EC2.

Click on the ‘EC2 Console’ link in the green banner at the top of the page to navigate to the AWS EC2 Console, and select, from the instance list, the instance that you have just launched.

The EC2 instance will be in the ‘initializing’ state for no longer than 2 to 3 minutes, before APS will be accessible, denoted by the EC2 instance changing to the ‘running’ state.

Confirmation page 

Select the Description tab of your newly created instance and click on the Security groups link. Edit the Inbound rules and add a custom rule with the following values:

  • Type: custom TCP
  • Protocol: TCP
  • Port Range: 8080
  • Source: My IP

Security inbound rule

Step 3: Logging in to APS

 

Once the instance state is ‘running’ and all status checks passed, open a browser page using the URL: http://{public_dns_here}:8080/activiti-app.

Login page 

On the login page, use the credentials:

 

If you need a valid product license, it takes less than 2 minutes to get a 30-day trial license by filling out the form at https://www.alfresco.com/platform/process-services-bpm/trial/aws

Step 4: Logging in to APS Admin console (optional)

Open a browser page using the URL: http://{public_dns_here}:8080/activiti-admin. On the login page, use the default credentials: admin/admin.

 

Once logged in to the Admin console,  it is always recommended to update the existing password to something much more secure such as a combination of four words. Check out this post for details about securing passwords.

 

Open the Configuration menu to connect the Admin Console to your APS running application. Edit the REST endpoint settings and apply the corresponding values as shown here below.

REST endpoint configuration 

Save and click on Check REST endpoint. You get a confirmation message with the endpoint status and Engine version.

 

Bravo! You have successfully launched APS using the AMI published by Alfresco. You now have a running APS environment that you can use to explore the Hello World getting started tutorial and try out some of our more advanced community examples.

The activiti team is happy to announce that Activiti & Activiti Cloud 7-201712-EA artifacts are out and we encourage people in the community to try them out.

 

For anybody looking to try out the new Activiti Cloud features in Activiti 7, the best place to start is GitHub - Activiti/activiti-cloud-examples: Activiti Cloud Examples using Docker Images from: https://hub.docker.com/u/ac…  or the gitbook Activiti 7 & Activiti Cloud Developers Guide · GitBook 

 

In the 7-201712-EA release we've added improvements to the way cloud connectors manage transactions, which improves their performance. We've added an example based around marketing campaigns for social media content in which you can see how well the connectors perform. The rate of data input and the number of replicas for cloud components in this example can be controlled in the deployment descriptor so that it's easy to play with these variables to test scalability. We'll be talking more about this example at Alfresco DevCon 2018.

 

We've also added process model and organisation services, which are preparations for future work that will support logical grouping and editing of BPM models/diagrams.

 

As part of this release we also aligned with Spring Boot 2.0.0.M7 and Spring Cloud Finchley.M5.

 

You can find our published artifacts in [Maven Central]
and our Docker Images have been tagged so you can use the 7-201712-EA tag for each of our images. You can find more details on
[Activiti in Docker Hub]

 

Ping us in Gitter if you want to contribute, give feedack, or if you need help reporting an issue: https://gitter.im/Activiti/Activiti7

(01/01/18 - 07/01/18) The team has been focusing on preparing for the next Early Access release and preparing our Trending Topics twitter example to be presented at DevCon. The work has helped us realise some significant improvements in memory profile and demonstrate Activiti Cloud’s scaling capabilities. We’re also working on improving our processes for end to end testing by devoting time to using a fully-featured hosted environment.

 

@constantin-ciobotaru worked on the integration of the new activiti-cloud-process-model-service and activiti-cloud-org-service to resolve some bugs in the way they interact

@lucianoprea worked on the activiti-cloud-modeling-backend in order to build an application using the activiti-cloud-process-model-service and activiti-cloud-org-service as dependencies and publish a docker image containing that application

@ffazzini created a kubernetes cluster running on alfresco aws, deployed and tested successfully activiti main components

@ryandawsonuk improved the memory profile of the components for the trending topics twitter example and applied this back to the other examples, now enabling us to run more replicas of services and process at a higher rate of tweets when running in minikube

@erdemedeiros updated Spring Boot Maven plugin to version 2.0.0.M7. Review and merging pending PRs. Start adding the flow node id (from the process definition) to the integration requests in order to improve the audit events.

 

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7https://gitter.im/Activiti/Activiti7

 

If you want to get started with Activiti Cloud visit our Gitbook: https://activiti.gitbooks.io/activiti-7-developers-guide/content/

(25/12/17 - 31/12/17) This week was Christmas and New Year so many of the Activiti team were on holiday. Those of the team who were around used the time to improve our examples of how to use Activiti Cloud and to make plans for areas to improve in the start of the new year. We also tried to keep chipping in to answer questions from the community, especially in the forums.

(18/12/17 - 24/12/17) We’ve been working hard to eat our own dogfood by fleshing out our Trending Topic Campaigns example to make it as realistic as possible and testing it at high volumes. This is helping us to refine the Activiti Cloud tooling and provide better guidance on how to use it.

 

 

@daisuke-yoshimoto worked through issues and forum questions, helping make progress on issues experienced in the community

@constantin-ciobotaru worked on building an executable for the Activiti Cloud Models module to run in a docker container

@mteodori addressed a vulnerability by removing an unnecessary xerces dep from v5

@lucianoprea worked on building an executable for the Activiti Cloud Organisation module to run in a docker container and flushed out some issues in our gitbook instructions

@ffazzini fix zipkin Boot M7 breaking changes, memory/performance optimisations for applications running on minikube

@balsarori offered advice to help resolve a key issue with the connector implementation

@ryandawsonuk did some refactoring of the trending  Trending Topic Campaigns example and integrated ELK into the example

@erdemedeiros did some code reviews and investigated a random failure around the connector examples. Will be on holidays next week.

@salaboy did some planning for work on the trending topics example and further work into next year as well preparing presentations

 

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7

If you want to get started with Activiti Cloud visit our Gitbook: https://activiti.gitbooks.io/activiti-7-developers-guide/content/

(11/12/17 - 17/12/17) We are getting close to the end of the year and we are focusing on improving our tests and building blocks. We want to start 2018 with a continuous deployment approach for our services and tools that we build. For that reason, we are spending some time in setting up our Trending Topic Campaigns example (which uses Docker & Kubernetes) in an environment that we can run, test and validate our releases.

 

 

@daisuke-yoshimoto added ability to activiti-cloud-runtime-bundle-service to start a process instance by process definition key and business key. Also, he is reviewing the following pull requests.

Fix signal events throw/catch race conditions in transaction scope

Update the persisted historic task instances that are open

@constantin-ciobotaru worked for connectivity between organization service and model services (like process model), added modeling backend starter and improved versioning on process models service

@lucianoprea worked on the  Activiti Cloud Service Organization having the first iteration merged and almost done the Spring Rest Docs integrated for the Audit JPA

@ffazzini spring profiles for logging, Boot M7 breaking changes fixes, investigation around terraform/rancher deployment for having an environment up and running

@ryandawsonuk has been reviewing contributions and checking the latest builds and updating after a recent spring boot milestone upgrade

@erdemedeiros did some bug fixes and worked in the trending topic campaigns example.

@salaboy working on updating our gitbook (https://activiti.gitbooks.io/activiti-7-developers-guide/content/ ) and looking into our modelling backend services. I helped also with reviewing and refactoring some of the bits inside of the Trending Topic Campaign Cloud Examples.

 

 

This week, we will start preparing for our December release, which is full of fixes and most importantly our demo scenario that demonstrate how to build, deploy and scale domain specific Activiti Cloud Applications. I (@salaboy) will be off for 3 weeks so I hope to see you all at DevCon ‘18.

 

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7https://gitter.im/Activiti/Activiti7

 

If you want to get started with Activiti Cloud visit our Gitbook: https://activiti.gitbooks.io/activiti-7-developers-guide/content/

Last week (4/12/17 - 10/12/17) we spend some time some time refining and improving our REST APIs and we are making some interesting progress on the Modelling/Authoring services which will support our new set of front end tools. We are moving forward with distributed monitoring and logging using the ELK stack so expect a blog post about this soon.  I want to highlight a set a blog posts written by one of our community members @daisuke-yoshimoto: (in Japanese) Activiti Advent Calendar 2017

If you are using or writing about Activiti get in touch, we would like to promote your work!

 

 

 

@willkzhou working on building docker image to test elastic-search on. Need to move elastic code from elastic repo to query repo ASAP for consistency.

@daisuke-yoshimoto was adding ability to activiti-cloud-runtime-bundle-service to start a process instance by process definition key. Also, he is writing Japanese blog posts about Activiti through the project called Activiti Advent Calendar 2017. He will write about Activiti 7 in the last week.

@igdianov worked on a PR for Activiti 5.x regarding signal/catch events and on the GraphQL Notification Service PoC.

@constantin-ciobotaru worked on communication between organization service and the other services, added on org side tests for create, update, get a process model using the stub server generated by spring contracts from process-models service.

@lucianoprea worked on Organization service to support nested Groups and Project structures.

@mteodori fixed issue with Spring HATEOAS link templating and created a request to review the third party dependencies and their versions in the Activiti/Activiti engine.

@ffazzini poc distributed logging elk on kubernetes using elastic public images

@ryandawsonuk updated our release jobs to incorporate some new repositories, updated our build jobs to validate maven versions of Activiti artefacts and upgraded the version of keycloak used in Activiti 7

@erdemedeiros worked with @ryandawsonuk on tasks to prepare the next release, fixed an issue related to the CommandCloseListener ( https://github.com/Activiti/activiti-cloud-runtime-bundle-service/pull/20 ) used to send audit events.

@salaboy worked on organizing the release notes and the roadmap update. We also work hard on planning and making sure that our GitHub issues are updated and correctly organized. Also worked on our cloud connectors example now called “trending-topic-campaigns”: https://github.com/Activiti/activiti-cloud-examples/tree/feature/salaboy-1514-twitter-processor-example/trending-topic-campaigns  

 

 

This week we will collaboratively work on getting our Activiti Cloud Connectors example up and running in kubernetes with the rest of the infrastructure. We are also starting to prepare our presentations for the Alfresco DevCon ‘18 in Lisbon: http://devcon.alfresco.com

 

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7

If you want to get started with Activiti Cloud visit our Gitbook: https://activiti.gitbooks.io/activiti-7-developers-guide/content/

Last week we upgraded to Spring Boot M6 and Spring Cloud M4 to make sure that our November Early Access Release was aligned with SB/SC release train. We are making progress into using more Cloud components such as distributed tracing, logging and monitoring.

 

 

 

@willkzhou Pushed Elasticsearch implementation to separate repo created by Salaboy. Need to test Elasticsearch implementation locally first then test using a Docker image before sending for review to Mauricio et al. Updated Elastic POM files to match current release.

@daisuke-yoshimoto working on adding ability to activiti-cloud-runtime-bundle-service to start a process instance by process definition key. Also, he is writing Japanese blog posts about Activiti through the project called Activiti Advent Calendar 2017. He will write about Activiti 7 in the last week.

@igdianov - Implementing GraphQL Websocket subprotocol in Spring Websocket Message Broker. Fixed signal events throw/catch race conditions in process instance scope (PR #1590) in Activiti engine 5.x

@constantin-ciobotaru more work on adding versions to process models

@lucianoprea more work on the Activiti Cloud Service Organization

@ffazzini logging based on ELK and kubernetes investigation

@ryandawsonuk completed changes to runtime bundle to support security restrictions by process definition and added remote debugging options to all the docker images.

@erdemedeiros upgraded to Spring Boot 2.0.0.M6 and worked on the release 7-201711-EA.

@salaboy worked on enabling the Activiti Cloud Twitter example to work on Kubernetes and checked the released artifacts for correctness. This helped me to improve our Activiti Cloud Connectors started and a second iteration was included in our November Early Access Release. I’ve also checked the Runtime Bundle Security Policies initial implementation Pull Request.

We updated the Activiti & Activiti Cloud Project roadmap where we added more milestones covering the first 3 months of next year into our plans. 

 

 

This week we will upgrade to Spring Boot M7 and Spring Cloud M5 followed by a set of refinements to our services. We are planning to make a short XMas release before the end of the year, and we want to make sure that this release includes a set of improvements in our services such as Logging using the ELK stack or something similar, some fixes in our REST APIs and the Activiti Cloud Twitter example up and running.

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7

If you want to get started with [Activiti Cloud visit our Gitbook]

Almost 5 months of heavy work (and 4 Early Access Releases) we are happy to see that our building blocks are maturing to support more complex use cases. We are committed to improve each service iteratively and for that reason we are planning to have a live demo environments where we can push new versions our services in a continuous deployment fashion.  


We are getting more strict with planning and coordination of different teams and collaborators working on different areas, this pushes us to be more diligent with GitHub Issues, Milestones and Pull Requests.  If you want to report an issue, please do, but also we recommend to get in touch via Gitter to make sure that we can have a conversation about the specifics of the issue so we can size it and plan accordingly. 

Our focus remains the same: 

  • Create RFCs for new Cloud Native components and services.
  • Provide a clear specification (APIs) about our Services (REST/Message Based/Configurations). Make sure that these APIs have well defined responsibilities, single focused and can evolve over time without causing consumers any headaches.
  • Make sure that we use standard tools, patterns and development techniques widely adopted by other Open Source Projects/Communities. Spring, Spring Boot, Spring Cloud, Docker, Kubernetes falls into this category, and we are making sure that we provide the right integration with these frameworks/tools. We are not just using them to say that we "support" Docker or Kubernetes. Activiti Cloud is designed from the ground up to work with such technologies.
  • Engage and mentor partners and community members that wants to participate.
  • Doing it in the Open Source way (Transparency & Meritocracy are a must).

Milestone #4 - November 2017 - Ended -

  • Runtime Bundle & Services Hardening
    • Process Def & Instance Security Policies model
  • Tracing & Monitoring integrations common to all our services
  • Activiti Cloud Connectors Examples
  • JHipster Integration and Examples
  • Process Model Service - Initial Draft
  • Kubernetes & AWS deployments improvements

Milestone #4 was all about improving our building blocks to have Tracing & Monitoring capabilities out of the box. We also added our first iteration of the Runtime Bundle Security Policies mechanism which provides and out of the box granular configuration to do endpoint and content based filtering to enforce security restrictions on top of Process Definitions and Instances. 


We also released our second iteration of the Activiti Cloud Connectors, which are now the default integration point for Service Tasks when you are running Activiti Cloud (aka Runtime Bundles).


We are paying a lot of attention to the JHipster community, due the fact that we share a lot of the infrastructural components and technology stack (Angular Front End). For that reason, we will keep pushing the integration with their components forward. 
As part of this Milestone we aligned with Spring Boot M6 and Spring Cloud Finchley M4 which were released, less than a month ago. 

 

Milestone #5 - December 2017 - In Progress -

  • Extended Tests for distributed deployments to a live environment (24/7)
  • Process Model Service - Initial Implementation to release
  • Project & Groups Service - Initial Implementation to release
  • Elastic Search Query Service - Initial implementation to release
  • Notification Service PoC
  • Distributed Logging, Monitoring and Tracing
    • ELK Stack (or similar)
  • Process Runtime & Connectors Registry
  • Automated Release Tests - Initial approach

December Milestone is going to be a short milestone focused on adding 2 new services related to the Authoring tools (Groups & Projects + Process Model Service) for the platform. Until now, we have been focused on Runtime Services only. 


We want to make sure that our services are stable and for that reason we will spend time setting up an example that we can run 24/7 in an AWS/Kubernetes (Pivotal PKS is in our plans as well, we will appreciate Red Hat Openshift contributions) environment  where we can upgrade each of the blocks individually and go through the same process that you will face when implementing Activiti Cloud in your environments.

By having this example live (and publicly  available) we expect to self-document the process of using Activiti Cloud for all our users. 

Distributed Logging is being added, and we expect to include this in our Activiti Cloud Examples for the next release. We also need to get better at our release process, meaning that automated tests for our released artefacts should be in place if we want to make sure that our releases go smoothly. 


We expect also to release the Elastic Search integration/implementation for the Query Module as well as having an initial PoC for the Notification service using GraphQL Subscription Mechanisms. 

Milestone #6 - January 2018

  • Process Runtime APIs (Definition & Refactoring)
  • Process Runtime Service APIs (review and refactoring)
  • Notification Service initial implementation for release
  • Process Engine Clean ups and refactoring
    • BPMN2 Extensions
    • History Service
    • Job Executor
    • Timers
    • Emails Service


On January we have Alfresco DevCon 18 in Lisbon but our main focus will be clean ups at the framework level. We need to build and set up a set of APIs that will be versioned with clear @Deprecation Strategies to make sure that compatibility is tracked across different releases.  


By the end of January the Notification Service initial implementation should be added to our basic set of building blocks. 


Milestone #7 - February 2018 

  • Application Service (Case Management Constructs)
  • Itsio.io Research and initial integration
  • Kubernetes Service Registry and Service Brokers review
  • Security & SSO review
  • JHipster Microservices Infrastructure Integration


February main focus will be around Application Composition and Coordination, this is where the Service Registry & Distributed Configuration Server becomes really important. Security policies and isolation between applications will require review on our mechanisms to make sure that we are aligned to what the industry is expecting.

Tools like Itsio will be analyzed and adopted to improve how we Release and maintain Activiti Cloud Applications. If JHipster migrates to Spring Boot 2, we will add our building blocks to their infrastructure and integrate with their services. 


Milestone #8 - March 2018 

  • Decision Service initial draft implementation
  • Polyglot MicroProcessRuntime PoC
  • Deployment Service & Pipeline (Design and initial implementation)

 

As always, if you want to participate on the development process of some of these components or examples get in touch. We are willing to collaborate with the open community and mentor people that want to learn about the project.

We look forward all community involvement, from comments, concerns, help with documentation, tests and component implementations. If you are looking into getting started with the Early Access Release we recommend to check our Getting Started Guide in Gitbook: [Getting Started · Activiti 7 & Activiti Cloud Developers Guide]

You can always find us in the Gitter channel: [Activiti/Activiti7 - Gitter]

Because we are a world wide community you can always find someone online to chat with, no matter your timezone

I’m happy to announce that Activiti & Activiti Cloud 7-EA201711 artifacts are out and we encourage people in the community to try them out.

This release was focused on expanding our base building blocks to make sure that they can perform in distributed environments (Docker & Kubernetes).
We added monitoring & tracing capabilities to the platform to make sure that we have visibility when things go wrong.

 

As part of this release we aligned our artifacts with [Spring Boot 2.0.0.M6] and [Spring Cloud Finchley.M4].

The following frameworks are now built in in our services:

  • activiti-cloud-services-tracing: which currently includes integration with Sleuth and Zipkin
  • activiti-cloud-services-monitoring: which delegate to the Spring Actuator the Job to expose metrics for health checks, readyness and liveness probes.

You can find an example of tracing included in our deployment descriptors for Docker Compose & Kubernetes in our [Activiti Cloud Examples Repository](L)

We have also introduced the first iteration of our [Runtime Bundle Security Policies. As described in our RFC document]

 

 

The second iteration of Activiti Cloud Connectors was released as well, introducing bidirectional channels by default, which allows our connectors to talk back to Process Runtimes as well as receive IntegrationRequestEvents and send back IntegrationResultsEvents. You can find the source code here: [activiti-cloud-starter-connector]

You can find our published artifacts in [Maven Central]
and our Docker Images have been tagged so you can use the 7-EA201711 tag for each of our images. You can find more details on
[Activiti in Docker Hub]

[We updated our Roadmap and included new Milestones]

For December Milestone we want to include 2 new services (building blocks) to deal with Authoring aspects of the platform. For that reason we have two RFCs documents:

We also have an RFC document for our Notifications Service which we plan to have a PoC by the end of the month:

Ping us in Gitter if you want to contribute, give feedack, or if you need help reporting an issue: https://gitter.im/Activiti/Activiti7

We are getting close to the end of the month so we are trying to close the some pending issues for this milestone (11-2017). Last week (20/11/17 - 26/11/17) we manage to make great progress into the monitoring aspect of our platform and each of our services is getting more and more robust. We are growing and having more people looking into our coding practices and how we build our software is getting and better and better every month.

 

 

 

@willkzhou preparing to test query with Elasticsearch and implementing docker image to test with.

@daisuke-yoshimoto working on adding ability to activiti-cloud-runtime-bundle-service to start a process instance by process definition key

@igdianov working on the notification service using GraphQL subscriptions.

@constantin-ciobotaru working for adding versions to process models

@lucianoprea continued working on the Activiti Cloud Service Organization

@balsarori reviewing and updating form runtime service document. Checking the possibility of using JSON schema validation to do form validation.

@ffazzini introduced tracing in common module, managed to get zipkin running in Minikube and the services sending traces to it. ( https://github.com/Activiti/Activiti/issues/1546 )

@mteodori dev environment configured on new macbook with example on docker and minikube running as in the dev guide, a PR on broken links merged plus one on adding git info to audit service

@ryandawsonuk helped with making actuator available in the services and made common supporting classes available to later be able to apply security restrictions to process definitions in a runtime bundle ( https://github.com/Activiti/Activiti/issues/1493 )

@erdemedeiros added audit events for connector integrations ( https://github.com/Activiti/Activiti/issues/1545 ).

@salaboy worked on our Twitter Cloud Connector Demo. Now the demo works with Docker Compose and we are quite close to get it up and running in a public AWS instance. PR: https://github.com/Activiti/activiti-cloud-examples/pull/28

 

 

 

This week we will be merging Pull Requests, refining the examples and our GitBook to make sure that the latest changes are reflected for the release date. We aim to be releasing by the end of this week so stay tuned!

@salaboy will be in Rome, Italy for the Makers Faire, so if you are around feel free to get in touch via twitter and we can do some hacking together.  

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7

If you want to get started with Activiti Cloud visit our Gitbook: https://activiti.gitbooks.io/activiti-7-developers-guide/content/

(WOW 20 weeks already!) Last week (13/11/17 - 19/11/17) was all about polishing our services and looking into other aspects of our infrastructure such as monitoring, distributed configurations, security and system to system interactions. We spent a good amount of time with our project structures and we will keep  refining our GitBook to keep it as updated and full of examples as possible. As always feedback is more than welcome.

 

 

@willkzhou worked on ElasticSearch Query module implementation, quite close to be completed.

@daisuke-yoshimoto This week, he was maintaining the old version He worked on  backporting call activity business key to 5.x .

@igdianov worked on notification services using GraphQL subscriptions

@constantin-ciobotaru - out on holidays -

@lucianoprea worked on the new Activiti Cloud Service Organization (work in progress)

@balsarori worked on refactoring the Form Service brought from 6.x form service and adding spring integration

@ffazzini Feign client in activiti-cloud-examples and related bug reproducer, Zipkin investigation and PoC.

@ryandawsonuk - out on holidays -

@erdemedeiros mainly worked to provide audit events for integration requests (work in progress). Also did some improvements related to the internal Maven dependency management.

@salaboy worked on testing latest refactorings on dependency management and artifacts alignment, add more documentation to our gitbook and worked on an Activiti Cloud Connectors example that is going to be published as soon as the PRs .

 

This week there are a couple of RFC blog post coming out, so stay tuned and if you are interested in the project please review those blog post and send feedback. It is a great time to influence the project direction, priorities and to engage in collaborations.

 

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7

If you want to get started with Activiti Cloud visit our Gitbook: https://activiti.gitbooks.io/activiti-7-developers-guide/content/

Last week (6/11/17 - 12/11/17) we focused on some core refactorings in how our dependencies are managed and organized across all our repositories. We found some issues and we are planning to fixed them one by one. @igdianov presented on friday a session about GraphQL subscriptions and a PoC to bring those features into our new component called activiti-cloud-notifications. This will enable our services to push notifications via the STOMP protocol to all interested parties. We are also working hard to get some examples with our brand new Activiti Cloud Connectors, to demonstrate how you can scale our services based on demand when hosting in a Cloud Infrastructure such as Kubernetes.

 

 

@willkzhou worked on Elasticsearch repository implementation for querying Tasks and Process Instances. Testing this coming week before committing current code.

@daisuke-yoshimoto only updated Runtime Bundle Endpoints to use content type header instead of PATH.

@igdianov worked on a GraphQL subscription mechanism for Tasks and Process Intances, new RFC post coming. Polished PoC and explored using Spring WebSocket Message Broker for better and more robust web application messaging backbone. This week I am going to prepare and commit PoC in development branch, explore integration with Apollo GraphQL client library  and expand RFC descriptions for review and discussion.

@constantin-ciobotaru - out on holidays -

@lucianoprea working on Spring REST docs for Activiti Cloud Services Audit

@balsarori worked on our first iteration of our new Form Service, which is an evolution of the form services provided in version 6.x

@ffazzini working on kubernetes probes, swagger fixes in audit and query services

@ryandawsonuk - out on holidays -

@erdemedeiros added badges to all the repositories and checked that the quality tools were properly set. Currently working with @salaboy to improve the dependency management across the repositories.

@salaboy worked on improving our Swagger contract for runtime bundles and improved dependency management for all our repositories to be more aligned with JGitflow practices. A blog post about our lesson learned with maven, multi repositories and Jgitflow is coming.

 

 

This week is going to be all about Cloud Connectors and refining our services to support Spring Cloud Contracts and Spring Rest Docs. We are going to provide some examples on how you can test our services against their contracts without the need of starting an instance. We are also working on a Feign generated client for our runtime bundles, so you can leverage the power of service discovery, circuit breakers and much more for service to service interactions.

Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7

After almost 4 months of heavy work (and 3 Early Access releases) we are moving forward our basic Cloud Native Runtime building blocks (Runtime Bundle, Connectors, Query & Audit) forward and we are reaching a point were we can start building up more advanced services. Because of these progress we can clearly define what are our main objectives for November, December and January.  

Our focus is on: 

  • Create RFCs for new Cloud Native components and services
  • Provide a clear specification (APIs) about our Services (REST/Message Based/Configurations). Make sure that these APIs have well defined responsibilities, single focused and can evolve over time without causing consumers any headaches.
  • Make sure that we use standard tools, patterns and development techniques widely adopted by other Open Source Projects/Communities. Spring, Spring Boot, Spring Cloud, Docker, Kubernetes falls into this category, and we are making sure that we provide the right integration with these frameworks/tools. We are not just using them to say that we "support" Docker or Kubernetes. Activiti Cloud is designed from the ground up to work with such technologies. 
  • Engage and mentor community members that wants to participate
  • Doing it in an Open Source way (Transparency / Meritocracy are a must)


Milestone #3 - October 2017 - Ended -

  • Refactor Activiti Cloud Service
    • Process Def & Instance Security model
  • Activiti Cloud Connectors
    • Process Runtime refactoring to avoid JavaDelegates and classpath extensions
    • Kubernetes Services ready
  • Process Model Service (Design and Initial Implementation)
  • Notification Service (Design and initial implementation)
  • Form Runtime Service (Initial discussions and planning)

This milestone was released to Maven Central and Docker Images were tagged in Docker Hub. You can find more about these Early Access Release here

Milestone #4 - November 2017 - In Progress-

  • Runtime Bundle & Services Hardening
    • Process Def & Instance Security model
    • Contracts and Rest Docs
    • Feign Clients Examples and tutorials
    • Improved Swagger APIs
    • Tracing Integration
  • Activiti Cloud Connectors Examples
  • JHipster Integration and Examples
  • Application Context Service - (Design and Initial Implementation)
    • Publish/Deploy/Group Runtime Bundle Service
    • Case Management Constructs (Design and PoC)
  • Notification Service - Initial Implementation
  • Process Model Service - Initial Implementation
  • Form Runtime Service + Cloud Starter
  • Kubernetes & AWS deployments improvements

Milestone #4 is all about hardening our Runtime Bundle and Runtime Services. We need to make sure that these services are production ready, can be tested and consumed in a straight forward way, relaying in standard tools and practices. As part of this hardening we need to improve our Kubernetes Deployments, Docker Images and we need to start testing against a Native AWS setup. 


While we work on improving these services, we are starting to design more high level components that will provide services not only during runtime, but also during authoring. As part of these services we are designing and creating RFC documents for the following new components:

  • Process Model Service
  • Form Model Service
  • Form Runtime Service(Runtime)
  • Notification Service (Runtime)

Finally, we started the design on our initial implementation for adding some case management constructs into the platform. For us it is extremely important to keep these separated from the Process Runtime, but at the same time to make it in a way that it is transparent for the user consuming the services. Case Management is all about aggregation, content integration and allowing people to group and manage resources (process instances, documents, tasks) together under a case instance. 

Milestone #5 - December 2017 -

  • Application Context Service
  • Case Management Scenarios
  • Form Model Service - Initial Implementation-
  • Decision Model Service - Initial Implementation
  • New Decision Runtime (Design and Initial Implementation)
  • Back to Basics Examples

Milestone #6 - January 2018 -

  • Polyglot MicroProcessEngine PoC
  • Deployment Service & Pipeline (Design and initial implementation)
  • Process Engine Clean ups and refactorings
    • Activiti Interfaces Module
    • BPMN2 Extensions
    • History Service
    • Job Executor
    • Timers
    • Emails Service


As always, if you want to participate on the development process of some of these components get in touch. We are willing to collaborate with the open community and mentor people that want to learn about the project.We look forward all community involvement, from comments, concerns, help with documentation, tests and component implementations. 

If you are looking into getting started with the Early Access Release we recommend to check our Getting Started Guide in Gitbook: [Getting Started · Activiti 7 & Activiti Cloud Developers Guide]
You can always find us in the Gitter channel: [Activiti/Activiti7 - Gitter]