I’m a little bit confused how to migrate from Activiti to Camunda. Our current database is on Activiti version 5.14. I wrote a rollbackscript to 5.11 to be able to update from Activiti 5.11 straight to camunda 7.0.0 as described in official Activiti migration guide (https://docs.camunda.org/manual/latest/update/activiti/).
It says Camunda 7.0.0 is basically Activiti 5.11 and the database should be identicial. However in this Camunda blog (https://camunda.com/blog/2016/10/migrate-from-activiti-to-camunda/) I have to execute additional scripts (6.2 to 7.0) and on github (https://github.com/camunda/camunda-bpm-platform/tree/7.0.0-Final/distro/sql-script/upgrade) are some other scripts as well (6.0->6.1, 6.1->6.2, 6.2->7.0).
how to convert all activiti deployed bpmn files to camunda? mentioned the 6.2 -> 7.0 script as well.
Can someone tell me which scripts I have to execute and why?
Thanks!
My same question in the official forum: https://forum.camunda.org/t/required-sql-scripts-for-activiti-to-camunda-migration/25794
Why don't you consider Activiti to Flowable. It's a much easier transition and Flowable is fully supported by the original Activiti team.
P.S> I don't work for Flowable so don't have a dog in the fight.
Related
We have MuleSoft applications and they are deployed in Mule Runtime. We need recommendations on patching MuleSoft applications. The patch can be either in MuleSoft Runtime itself or can be in application.
MuleSoft's recommendation on patching a MuleRuntime is available at https://support.mulesoft.com/s/article/How-to-apply-patches-to-Mule-4-x.
Here, the recommendation to patch MuleRunTime is to replace the jars/plug-in. But with this, how can we maintain/know the version of patch that is applied.
What is the recommended way to patch a application which is deployed in MuleRunTime.
Any help/recommendation on this is appreciated. Thanks.
You can look at infrastructure automation tools that auto install your runtime with the correct patches etc like puppet, chef and so many other tools. So that your runtime is always using the correct doenedencies and is repeatable. Which tool depends on your organisation.
Or just as with your code you can version control your runtime or install scripts in git etc.
The Mule runtime will log its own version and the versions of each plugin and applied patch, whenever it starts your app. So check the log from the last time you started and you'll see the current version and patch level.
So trust the recommendations in the help document you cited in the OP. As Ryan says, you can use any dev-ops tools favored in your organization. (If you don't have a favorite, Maven is integrated very nicely with Anypoint Studio and can help with this.)
I am having a scenario where in I need to migrate the artifacts from HP ALM to VSTS for test management. I know about the ALM API and have worked with that before for exporting defects, and test cases but I am not aware of any such things for VSTS ( am very new with it) and want to create a task and then create a bug with the help of the adapter code and move the details from alm to vsts.
Can anyone please help me get the VSTS API, or some sample adapters based on which I can start coding for the VSTS API?
N.B: I tried finding it over google but no luck till now.
Thanks in advance.
You can try to use OpsHub tool.
Another tool: Microsoft Visual Studio Online Integration
Regarding API, you can try to use VSTS/TFS sdk: Microsoft Team Foundation Server Extended Client. You can check the source code of vstssync migrator (Ove mentioned)
Another option is vstssync migrator created by mrhinsh
https://github.com/nkdAgility/vsts-sync-migration
There is the code to get you started with your adapter.
I need to migrate my application to WAS 6.1 to WAS 8.5.5. I would need list of things to be taken care before migration and what are all the major changes involved.
I googled and sufficient informations I couldnt get. Can some one please help me on this ?
One thing to do is to setup an eclipse with IBM WebSphere Application Server Migration Toolkit and then import your application source code (you may even analyse your binaries with Migration Toolkit for Application Binaries) in the workspace.
You then run Software Analyzer and select the Websphere Migration rules.
I understand what is Elasticsearch, but have no clue on how to write a plugin for Elasticsearch. Can any one tell me the guidelines for writing plugins to Elasticsearch.
Found.no (an Elasticsearch hosting service) has a very good writeup on the Elasticsearch plugin development process. It's as detailed as I've seen out there and is fairly recent (Sept 2013) so should be reasonably up to date. If I was going to build a plugin from scratch that's where I would start:
https://www.found.no/foundation/writing-a-plugin/
The other is to dig around in other plugins on Github:
https://github.com/mobz/elasticsearch-head
https://github.com/elasticsearch/elasticsearch-river-twitter
Lists of other plugins:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-plugins.html
Between the tutorial and looking at all the source code out there you should have a solid foundation.
It depends what you want to do with your plugin!
You can write a plugin in java to send data in elastic for example. You can do what you want for that.
I think a plugin is freedom! You can use elastic APIs or not, or imagine new function when you connect your plugin (java for example) on elastic.
I've been building my C# project from the MS Visual Studio IDE, and by invoking msbuild from Jenkins on Windows. Now I want to build the C# project on Atlassian OnDemand.
However, msbuild is not listed as a builder option in OnDemand and I can't find any documentation on how to build a C# project on OnDemand.
Update
Atlassian OnDemand Bamboo features a Windows stock image as of mid July 2012, see Azwandi Mohd Aris' comment:
Just an update that Bamboo OnDemand now ships with a Windows-based AMI - see release notes at https://confluence.atlassian.com/display/AOD/July+2012#July2012-Bambooupgrade
This image meanwhile also supports MSBuild as per James Dumay's answer from early November 2012.
Initial Answer
The configuration of builders is one of the Restricted Functions in Atlassian OnDemand for Bamboo:
Bamboo OnDemand only runs builds using elastic agents. Hence,
capabilities can only be configured by using a custom image.
So in principle you would need to either use one of the default Stock images provided by Atlassian or Create a custom elastic image of our own. While Atlassian provides a Windows stock image as of Bamboo 3.4, the version of Bamboo for OnDemand is most annoyingly still stuck at 3.0 (see Atlassian OnDemand Application Versions), with the long overdue update including DVCS support recently postponed again (see Lingbo Lu's comment: We are hoping that we can deliver it in July/August timeframe)
So for the time being I'm afraid you'll need to apply the Bamboo 3.0 version of Creating a Custom Elastic Image and create an appropriate custom image for the task at hand yourself.
Update
There are a couple of related threads on Atlassian Answers as well:
James Dumay's answer to How do I run .NET builds on JIRA Studio summarizes the state of affairs and recommends Grace Mollison's instructions for Setting up a windows AMI for use with Elastic Bamboo in turn. However, RodH's comment regarding How can I run Bamboo OnDemand with MSBuild? indicates unspecified issues with this approach/solution.
So be prepared for a rough ride eventually.