Can anyone suggest books to understand writing rules looking upon business process and integrating that into ESB? I know how to write a rule and run a java application. That is where I reached for last 2 days. Anything useful will help me in catching up with all these.
Did you check the jbpm.org documentation site and the drools.org documentation site?
I'm promoting a Community Training Course about Drools and jBPM5 you can find it here:
http://salaboy.com/2011/01/24/announcing-jbpm5-community-training/
http://salaboy.com/2011/02/23/drools-5-community-training-announced-roadmap/
If you find it useful please give us feedback.
Related
We had deployed jboss4.2.3GA in 2012,and now we want to upgrade to Wildfly,but now we have no sufficient technical to do that.so someone can tell what we can to step by step ? and are there any technology guide?
We have compared the document structures of the two versions, but they are far different. So we want to find a guide that can actually guide us step by step. I wonder if there is such a document?
I have requirements to establish a CMS system for enterprise and it has to be java based open source, I found out that liferay has CMS capabilities but I'm not able to find any detailed description of the features introduced on its CMS , also I found some people are talking about integrating Liferay with Alfresco ! does this mean that Liferay is not a complete CMS ? appreciate if anyone can guide me through this and provide me with any resources detailing liferay CMS features
Yes, Liferay has CMS features - coming from a portal background the CMS is only one of the many features delivered out of the box. A portal typically is an integration platform for any kind of application. If you ever only need CMS, it might be that "pure" CMS products offer a bit more of functionality, however, many people are very happy with the CMS functionality Liferay provides. And if you're not, it's typically easy to extend (this is the point of a portal).
Systems that start being a CMS and want to extend that with applications (who doesn't want that) typically have a different mindset - "everything is content" - and naturally your application feels a bit more like "content". The portlet standard, together with the additional APIs that you have available, is a nice way to start.
For CMSs the way to go is typically a proprietary API to extend it. In a portal, a CMS is one of the possible applications available.
Regarding Alfresco: Yes, you can combine it with Liferay. While Alfresco tends to come more from the Content-side, Liferay comes from the portal/integration side. I'd ask you to evaluate both first and see if you are missing vital features in any. Then evaluate which pain you'd like better: 1) Add the missing features you want in the system you decide for, or 2) integrate both systems and run them both. Of course, the optimum result is if only one of the two is sufficient for your requirements. Then project into the future and try to find out what you'll miss first.
There is no correct answer to this question, it all depends on your requirements, experience and ability to learn and administrate one or both of the systems.
Disclaimer: See my profile to detect my implicit bias - I hope to not stress it too much in this answer.
I am relatively new to the concept of rules engines and was trying to work with Drools.
Has anyone already worked this tool before and is it similar to Cognos?
My understanding was that Cognos is a reporting tool and Drools will promote more increased control over the business logic implemented.
Am I on the right track? Any link which would help me differentiate between the 2 would also be helpful.
Thank you.
Cognos is a business intelligence reporting tool. It is meant to query over data sources including data warehouses and data marts, to help provide insight into your data and help you make decisions, view trends, etc. Here is IBM's Cognos product page. Here is a definition of Cognos from Wikipedia which I find helpful.
Drools is a Rete algorithm based Java rules engine that allows you to define business rules within your application and then have your application validate against those rules. Here is its definition from Wikipedia. And here is the Drools community page.
We actually use Drools in some of our applications for client side verification of business rules. And our business is planning on using Cognos (and another tool called QlikView) to do business intelligence reporting over our data warehouses and data marts.
As for how you use Drools, I'd look at the community page. In the version we used (2.0-Beta-10, which was way before Drools was acquired by JBoss) you generally define your rules in XML based files with a .drl extension from what I remember. We use an older version of Drools so it may have changed since then. We also extended Drools in our case so we could write our rules in Java code for run time debugging versus using XML files (since our Business analysts weren't writing the rules anyway).
Hope this helps!
You can use Drools & jBPM5 if your application will define Business Processes and Business Rules. The business rules will allow you to define business logic in a declarative way and the rule engine will allow you to do inferences over the information that you have in your domain. Visiting the community sites and looking for examples will probably help you out to understand how the project look like now and how you can use it.
Cheers
Does anyone know what tumblr is written in? I have been trying to figure it out.
It's PHP...
http://www.marco.org/55384019
spiteshow:
I wonder if the Tumblr guys are using a framework or if it is all home brew.
Both: it’s a homebrew framework to add MVC structure and a useful secondary function library to PHP 5 that we started in 2006 and have constantly evolved into a very finely tuned framework for our needs. The same framework runs some of Davidville’s former consulting-client sites as well as all of my personal sites and projects. It’s not available publicly anywhere, but we may release it in the future.
The lead developer's blog features a lot of PHP-related material, and Tumblr was advertising for PHP developers a while ago. This isn't strong evidence, but it's possibly indicative and it's the best I could find.
Here's the full stack as of 2013.
"We're a LAMP based stack (Linux Apache MySQL PHP) with Scala for our many services. Other pieces of tech we use currently in production are Memcached, Varnish and Redis."
http://smcdermott.tumblr.com/post/46847264498/what-language-is-tumblr-written-in-all-php
I just logged in to my account and added the index.php and it worked, so it must be php.
http://www.tumblr.com/dashboard/index.php
The general consensus is that devlopment of MOSS publishing sites, should be done using site definitions, Solutions, Features but due to project timescales we had to do all list/site column/content type/master page development using the SharePoint UI and SPD. We then used the contentdeployment wizard to migrate everything from devlopment.
Having done this, the future plan is to possibly, given the budget, change what has been built to use a site definition and features to get in line with best practices.
Has anyone done anything similar or have any tips on how best to plan for this?
Kind Regards
This is somewhat dependent on how large and complex your solution is. I was in the same situation with a project I started to work in. They initially started to do everything in SharePoint Designer. But when I was thrown in to the project, I decided to scrap all those changes, starting from the requirements and build up everything as site definitions/solutions/features in Visual Studio. In this case, it was feasible since the customizations were not too complex.
You can take a look at the SharePoint Solutions Generator, to see if that could help you as well. It can give you at least a good starting point.