We deliver the Activiti Modeler as part of the Explorer application, because there's almost always a need to have something like a model workspace. This model workspace is part of the Activiti Explorer application. But if you only need the editor part of the modeler you can extract it from the Explorer application.
So if you want to use the Modeler separately, yes this requires additional work and some investigation. To separate the Modeler application you need to create a new web application project that includes the activiti-modeler and activiti-engine as a dependency.
Then copy the following items:
- src/main/webapp the api, editor, explorer, and libs folders
- src/main/resources editor.html, plugins.xml, stencilset.json
- in the web.xml it's only important to expose the modeler REST services
Best regards,