I am trying to add a WebService Service Task to a process in JBPM. I would like to add and configure the task directly from the process design tool.
JBPM has 3 possible tools that you can use to create a process, eclipse plugins: RulesFlow editor and BPMN2 Modeler, as well as a Onyx Designer incorporated into Drools. So far I have not managed to do this in any of them.
I was able to add the WS to the process by manually editing the process XML file (as shown here: http://mswiderski.blogspot.com/2012/07/service-task-with-web-service.html) but we need to be able to do it in a graphical tool (business reasons, don't ask). BPMN2 Modeler comes closest to the generated XML that would in theory work, but when I try to run it, it comes out with a bunch of errors.
I know that the link I provided states that the tools don't yet provide the WS functionality but maybe someone has some ideas as to this problem. Any help will be appreciated.
I don't believe you can directly create a service task from the design tools. I've followed this here :
And after you've created your work item definition, you should be able to see that you can add that service task in your process design. Just remember that you have to register that to your session before you start the process. Hope this helps
Related
I am student and new to learn Drools. I am confused about how to learn the Drools. I know nothing about this area but my professor let me learn this things and make an expert system.
I have installed the drools workbench -- kie-drools-wb-distribution-wars-6.4.0.Final-tomcat7 this version. But I don't know how to learn it well. That means next step and next next step. What I need to do? Would you tell me? Thank you very much!
There are couple of demo applications available on github, you can refer to them and also there is drools documentation you can refer to.
If you just want to learn the Drools language you should use Eclipse/Idea and check out the code examples Drools releases deliver. The Drools documentation describes few of them and walks you through them. Once you can run them in your IDE start changing parts from here and there to see how the run results change.
The workbench offers a lot of tools for authoring rules in different formats: with plain DRL that is the Drools language and with different guided editors that hide the actual Drools syntax and give you a more visual editor for rule authoring.
The workbench also gives you tools for releasing and managing released rule projects, but it is hard to learn the actual language since there is no good way to run the rules in the workbench. You need to either use Test Scenarios to run the rules or build a kjar out of your project and then use it in an application that you would have to write yourself.
Best to start with an IDE and just use the premade examples.
In MS Dynamics CRM how do we register a plugin or a workflow as part of a solution? whatever i register through registration tool, just goes to the root solution of the system.
Expanding on what #Henrik said, the process would be as follows.
For the sake of this example, let's assume you have a single assembly (dll) with two plugins and each needs two steps.
Register the assembly as usual with the Plugin Registration Tool.
For each of the two plugins, register the two steps they require. This should leave you with four in total.
Leave the Plugin Registration Tool and go to your solution in CRM. You will see two sections there: Plug-in Assemblies and Sdk Message Processing Steps.
You will need both of these to fully register a plugin with your solution.
Go to the Plug-in Assemblies section and use the Add Existing button. This will bring up a standard lookup dialogue that will let you select your assembly. Add it.
Next, go to the Sdk Message Processing Steps section and use the Add Existing button to add any plugin steps you want as part of the solution.
That's it. Your assembly, plugins, and steps are now part of the solution. Any step images that may exist are automatically added as part of the step so no need to worry about them.
One caveat though is that assemblies must be stored in the database and not as files for this to properly work. There is no specific limitation on sandboxed plugins (unless deploying to CRM Online) but using those would simplify solution deployment.
Finally, this walkthrough which was taken from the How To button in a solution.
Walkthrough: Register a plug-in using the plug-in registration tool
As for workflows, they need to be added in the Processes section of a solution. This section will cover workflows, dialogs, business process flows, and actions. As before, use the Add Existing button.
There is no direct support for adding plugin assemblies or plugin steps to solutions when registering with the Plug-in Registration Tool.
Your plugin steps and assemblies will always be present in the layer of unmanaged customizations ("root solution").
You can use the Plug-in Registration Tool as usual and only later manually add your assembly and steps to the relevant solution(s).
I am new by to eclipse RCP. I have an requirement in which, I need to copy some information from any "xyz" editor and paste it to "xyz" editor of another instance of same rcp product.
My application already have this copy paste functionality for single instance of the product, for which I am using customised standard ACTION as per my requirement.
I was trying to have something like "Application or Session" scope for web applications, where we can store that information and used it for different instances.
Please let me know, if something else required to understand the requirement.
Thanks in Advance !!!
As greg-449 mentioned they're running in separate JVMs.
This question is related:
inter jvm communication
It requires Java 7, which might not be available for you if you're using 3.x Platform.
You could also try opening a socket between the JVMs. However I did not find any out-of-the-box solutions.
You might find examples of a locally shared database, like the Java Derby technology. But it's way too much stack of technology for a copy/paste action, so don't use it.
I'm trying to use Drools Gorm plugin to build process in my Grails application. Therefore, it is needed to use bpmn diagrams in order to instanciate a process. For this, i'm started to use two eclipse plugins: the BPMN2 and Graphiti (that is required for the first one).
But, when i try to create a .bpmn file on src/diagrams, i'm getting this error on output alert screen:
Error org/eclipse/graphiti/ui/editor/diagrameditorfactory
I looked everywhere and i don't find any reasonable solutions. Any help is welcome!
Did you try the drools jBPM plugin? It seems to work pretty well. If you are alright with using another editor, you should try that. The update site is located here
We've decided to create a custom bootstrapper for our deployment solution. We are currently re-writing and re-designing our deployment strategy for all of our products. Sadly, none of us are deployment experts.
Here's what we have so far:
A. The MSI packages will be authored in InstallShield. We will use whatever feature Installshield offers (IIS integration, COM registration, Registry, etc). The dialog's created by InstallShield will not be used (that is what the bootstrapper is for). The MSIs will be installed silently.
B. Whenever we need to write CA's for stuff that InstallShield can't handle, we will be writing them in managed code (C#) using DTF. We will be creating a "Custom Action Framework" that will "standardize" how we use custom actions.
C. We will create a custom bootstrapper (the "setup.exe") in C# to "handle" the installation.
We have decided to go with a multiple MSI approach and use MSI transaction to "chain" the installation from the boostrapper (inspired from Office 2007 installer)
The boostrapper that we are envisioning to create is inspired from Visual Studio's and SQL Server's bootstrapper. The boostrapper will be responsible for the following:
Prerequisite installation: Each application require a pre-requisite. These pre-requisites are listed in an XML file placed on the same folder as the MSI (inspired from Office 2007 installer) along with other metadata. Depending on current state of the system, the boostrapper will decide which pre-requisite to be installed or not.
Feature selection: We are planning to structure the "internal" MSI's feature in such a way that it will not be appropriate to be displayed right away to the end-user. We will have feature labeled as "Core_Files", or "Vista_Only" or "64bit_Only". Depending on the metadata on the XML file (on item 1) and the target system, the bootstrapper will be responsible in "populating" a "feature tree" that the user can customize (also inspired from Office 2007 bootstrapper).
Pre-installation Checks: The bootstrapper will be responsible in checking if the system is ready to receive the installation. For instance, if a machine needs to reboot prior to installation or if the user needs to manually install a service pack, patch or a windows component. Anything that needs to be done that needs user intervention should be displayed here. Think of it as a check list (a listbox) with checks and exes. (Inspired from SQL server's bootstrapper). The "rules" will be written in C#.
Application Configuration: For application that needs to be "configured" prior to installation. These "parameters" (user configuration) will be passed to the respective MSI via MSI Properties.
Actual Installation: The bootstrapper will then perform the installation. Proper "transaction" should be observed when necessary. All "products" that should be grouped together shall be displayed as one product in Add/Remove Programs (by messing with the ARP entries). Also, proper progress shall be reported by each MSI being installed.
-- That's what we have so far.
I think there are a couple of out-of-the-box solutions for creating a custom bootstrapper like dotNetInstaller and BMG. We've look into it but it's not as flexible as we've hoped. There's also BURN but we're not sure if it's ready for primetime.
So here we are... we've decided to create our own custom bootstrapper.
Question:
Are we crazy? Shouldn't we be creating our own bootstrapper? Which ideas listed above are not realistic? Is there a better approach?
Any input regarding our situation will be greatly appreciated. Also, if you have any questions, please don't hesitate to ask.
Frankly, Burn isn't going to be done for at least a year. You already have InstallShield and IMO it has the best off the shelf bootstrapper currently available. I'd scope your requirements back and make it fit the box. Pretty much everything I read from you can be done using InstallShield if you learn to push it to it's limits.
I would go for Burn anyway or some already existing solution.
I'm sure that after some time you'll face new problems that you can't now really imagine.
If you face them, that means that Burn's developers have already faced them and probably got them solved. If not, Burn has a large community that will fix the potential bug faster than you.
Focus on the software you're developing, not on writing installer/bootstrapper.
If I were in your shoes, I would give a burn a try. I'd get me a couple of days and see if it meets my requirements.