Hi Jeff,I hope this topic is still of some interest as it is for me.I made some attemps on the Community edition 4.2.c, trying to integrate the Activity admin console module (taken from the Enterprise Edition), after upgrading the Activiti engine from version 5.10 to 5.13. The outcome was not exciting…After upgrading to Community 4.2.e. that became a much easier task!So here it is!I'm sorry I'm not very good at packaging extensions, neither I would know where to place an amp to be shared with the Community…These are the libraries needed that I've taken from the Enterprise edition distribution and put into webapps\alfresco\WEB-INF\lib:<ul> activiti-explorer-5.13-alf-20130918.jar activiti-json-converter-5.13-alf-20130918.jar activiti-simple-workflow-5.13-alf-20130918.jar activiti-webapp-explorer2-5.13-alf-20130918-ui-jar.jar vaadin-6.8.8.jar</ul>Furthermore the following classes (from org.alfresco.enterprise.workflow.activi package) are needed:<ul> ActivitiLoggedInUser.class ActivitiScriptNodeListRenderer.class ActivitiScriptNodeRenderer.class AlfrescoLoginHandler.class</ul>I've repackaged the above into an alfresco-enterprise-repo-4.2.0-EXTRACT.jar file.Then you need the activiti-context.xml file in<ul> webapps\alfresco\WEB-INF\classes\alfresco\enterprise</ul>(here you can comment the beans for MultiTenant management, if it's not your case) and the activiti-admin webscripts<ul> activiti-admin.get.desc.xml activiti-admin.get.js activiti-admin.get.html.ftl</ul>to be copied into<ul> webapps\alfresco\WEB-INF\classes\alfresco\enterprise\webscripts\org\alfresco\enterprise\activiti</ul>Finally you need to declare the new servlet into web.xml:
<servlet>
<servlet-name>Vaadin Application Servlet</servlet-name>
<servlet-class>org.activiti.explorer.servlet.ExplorerApplicationServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>Vaadin Application Servlet</servlet-name>
<url-pattern>/activiti-admin/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Vaadin Application Servlet</servlet-name>
<url-pattern>/VAADIN/*</url-pattern>
</servlet-mapping>
I have also added a link to this console into the admin-console.jsp page, by adding a navigation rule in faces-config-custom.xml:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config>
<navigation-rule>
<from-view-id>/jsp/*</from-view-id>
<navigation-case>
<from-outcome>showActivitiConsole</from-outcome>
<to-view-id>/activiti-admin</to-view-id>
</navigation-case>
</navigation-rule>
</faces-config>
and the action link in admin-console.jsp:
<a:actionLink value="Activiti admin console" image="/images/icons/workflow.gif" padding="2" action="dialog:showActivitiConsole" styleClass="title" />
I saw that even in the Enterprise edition the link to the Activiti modeler is broken.Jeff, would you please help me in understanding whether: 1) there is no licensing issue in using this Enterprise component 2) there is a useful Activiti modeler available tobe integrated with the Activiti admin console?Thanks a lot for all your help you are giving us!Carlo Giuliano