I am very new to JBPM.
I've a .net MVC based web application to which I need to integrate JBPM.I am not able to find any sample application or tutorial where I can see these details.
If you want to integrate your non-Java application with jBPM, you can use KIE Server. It is a lightweight application with embedded jBPM engine which can be deployed for example on Tomcat. You can then make use of its REST API to run business processes, complete human tasks, etc.
Yes, you can, but keep in mind that integration is limited - you still have to create process models in kie-workbench.
You can use API for starting and completing a process and getting a variety of informations about process state. You can also extend API by your own functionality. We are working on such integration so feel free to ask me any questions, but please be more specific - at least provide information what for JBPM will be used in your system, and what functionalities you want to integrate.
Related
I have developed a Django app which hosts a bunch of forms that collect information about issues and I want to use this data to create Jira issues programmatically.
I have a conceptual idea of how that can be achieved but my problem is that I am a complete software development newbie and also have never used Jira to this date, hence googling stuff is quite hard as I have an almost non-existent vocabulary in these regards and things get quite overwhelming really fast. I want to know if what I have in mind even makes sense before I delve deeper into documentations and figuring out how to implement stuff.
So I'm going to send POST requests from my Django app containing the issue information in JSON format. These POST requests would then be handled by some Java service which in turn uses the JRJC to create issues on Jira. In my head this implies that I have to develop a whole server (or use some kind of framework for that matter) for django to send its requests to and handle them. Would it be possible to write a plugin for JIRA that bypasses the need for such a server so I could just write the service for handling the requests and expose it on some URL based on the domain of my Jira instance?
I apologize if my question appears vague or ill-structured. Any attempts to shine light on my incompetence or pointing fingers in some direction will be greatly appreciated!
I assume that you're talking about Jira Server (hosted by you) rather than Jira Cloud (hosted by Atlassian).
A Jira plugin can expose a REST endpoint, so yes, you can write such a plugin and POST to an endpoint you define, which then uses the Jira Java API to create issues.
See https://developer.atlassian.com/server/framework/atlassian-sdk/rest-plugin-module/ for information on putting REST endpoints in your plugin.
This is my first time working with eCommerce Application - mobile app for iOS. Previously I have worked in developing many iOS applications - products and business based applications, banking domain, etc. Where, usually data is available at the client server and the communication happens through REST/SOAP services - parse the response - update the UI. I am familiar with this scenario.
I am just walking through the functional document for developing the eCommerce App, I found that they use CQ5 and Hybris as the backend systems.
I am wondering what is the role of CQ5 and Hybris here. In what ways it helps in managing an eCommerce application?
I guess they are for admin purpose. Being an iOS developer, how far I should know about them?
Hybris is the ecommerce system, and CQ5(now Adobe AEM) is the Content Management System (CMS) and Digital Asset management (DAM) portion. Hybris acts as the payment processor and inventory management. From a mobile experience perspective, images and templates for the UI of your app will likely coming from the AEM side (probably analytics too), while customer data is sent and received from hybris APIs. Hybris APIs are traditional REST/SOAP stuff.
If you need to learn something, you need to learn how AEM works and generates templates. Author -> Publisher -> Distributors.
I am wondering what is the role of CQ5 and Hybris here. In what ways it helps in managing a eCommerce application?
hybris is a framework to build ecommerce applications. CQ (AEM) is a CMS and DAM so it's not dedicated to ecommerce at all.
hybris also contains a CMS but CQ CMS is more advanced.
For me CQ is a good addition to hybris to manage pages that will be often contributed. The tool is more easy to use for someone that is not from the SI side. Also it offers more possibilities than hybris CMS.
Being an iOS developer, how far I should know about them?
It depends on what you're supposed to do.
I think CQ is not so hard to learn, at least for basic usage.
For hybris, without the intention of being mean, I would never hire an iOS developer. Indeed it's heavily based on Java EE technologies and Spring. So if you have no background in these techno you'll be quite useless...
Even Java developers I worked with experienced troubles when it comes to advanced development on the hybris platform.
If your role is only restricted to call WS exposed by hybris then you don't need to know anything about hybris. Ask the hybris development team to give you a documentation of the WS your supposed to call and that's it.
I am in the planning stages of building an App for iphone / ipad (yes, very early stages)
I am basically wondering how much work is involved in having a seperate user registration process for an app i.e. letting users register an account and use login using that account and use the app.
Will this involve constructing / coding an entirely new database or is there software available that automates this process?
thanks in advance
You could have a look at a service like StackMob.
This allows you to utilise server based services with no server-side implementation on your part.
These guys here: parse.com are doing a great job to facilitate developers the setup of a cloud database to do many tasks that are common in iOS apps.
In particular there is a section dedicated to user management (sign-up and sessions) that is well described here: Parse iOS guide
Finally the service offers some user interface help also, look here even if probably it is better to give to the UI some personalization by coding your own UI.
There are some implementations, but if your app is going to have custom code executed by server, you'd better make your own code.
Use a server side language (php, perl, ruby, python, java) to do the registration.
You'll probably need a REST service and/or json if you are going for easy peasy stuff (if you are to web apps programming). Otherwise, you'll need to do xml parsing and other stuffs. Use asi-http for the interactions between server and the app, or if you are using ios5.x it has already a json parsing implementation.
I have a Rails application that right now is pretty standard: Heroku/PostgreSQL backend, users go directly to my site to update data, there's no mobile app or anything. We're going to start licensing out the tech to other companies, so that different versions of the interface live on company1.mywebsite.com, company2.mywebsite.com, etc, where all of these interfaces share the same database.
I want some advice on how to go about building this. Do I create a separate Rails app for company1, company2, etc (with a lot of redundant code) and then set up each of them with API keys to query my master app, using its RESTful routes?
Any tutorials to point me to would be great as well.
I recommend you the book Service Oriented Design with Ruby and Rails, by Paul Dix. It has a lot of info about the kind of system that you want to build.
To answer your question:
Build an API server. It serves a JSON – for example – RESTful interface.
api.mydomain/client1/users.json
Build a frontend server. It consume the API service – using typhoeus for example – and serves the final pages. It uses a subdomain or domain name for identification of different clients.
client1.mydomain/users
We have a similar "platform".
What we did:
build a master API app (REST + Push)
build a core plugin for rails which has all the shared code
build a separate rails app for each client which has all the client specific code
We are using this setup for 3 years now and I'm pretty happy with it.
I am going to write a Ruby application that implements a video conversion workflow consisting of multiple audio and video encoding/processing steps.
The application interface has two core features:
queueing new videos
monitoring the progress for each video
The user can access these features using a website written in Ruby on Rails.
The challenge is this: I want make the workflow app a self-sufficient application, not dependent on the existence of the web view.
To enable this separation I think that adding a network API to the workflow application is a good solution because this allows the workflow app to reside on a different server than the web server.
My question is: Which solution do you suggest for such a network API?
A few options are:
implement a simple TCP server and invent my own string based API
use some sort of REST api (I don't know if this is appropriate for this situation)
some sort of web-services solution (SOAP, XML-RPC)
another existing framework
Feel free to share your thoughts on this.
I would suggest two things:
First, use REST as your API. This allows you to write one core application with both a user interface and an API for outside applications to use.
Second, take a look at PandaStream. It's a Merb application that encodes videos from multiple formats into flash. It has a REST API, and there's even a Rails plugin so you can integrate it with your application. It might be a good example codebase, or even a replacement for the one you're trying to build.
Hope my answer helped,
Mike