Chapter 3 - The Red - Piranha Framework
From Kb
Contact Article Author | Blog of Article Author | FirstPartners.net Home | LinkedIn profile of Author
Chapter 3 - The Case for the Red-Piranha Framework
In the previous chapter we saw 4 problem areas where good Knowledge Management can give an enterprise the competitive edge. This chapter introduces Red-Piranha as an ’out of the box’ solution to these problems. The chapter focuses on the business application of Red-Piranha, with later chapters providing more of the technical details.
Paragraph on how this all ties back to Web 2.0
- Picture of RP Logo
Red Piranha open software project that aims to get knowledge out people’s heads into a machine. Once there it can be copied, scaled , deployed 24/7 or even merged with other knowledge sets. Red-Piranha provides a base set of components , built into 4 ’ready to deploy’ solutions for each of these areas:
| Problem | Solution |
| You have information, but don’t know how to find it. | Red Adaptive Search Search of unconventional Business data using the Red-Piranha Adaptive Search Engine. |
| You’ve found the information but can’t do much with it. | Red Financial Engine Rapid development and deployment of business logic using Rule Engines. |
| You and your team have to work together on the information. | Red Workflow | Red Process Flow - Combine disparate web activities into a Business process using Workflow. |
| You get the information to and from the people that need it. | Red Web 2.0 Interact with the (Business) user using Rich Internet Applications (Ajax). |
The sort of problems Red-Piranha is trying to address manifest themselves in the following ways:
- knowledge walking out the door every night
- inconsistent application of knowledge leading to poor customer satisfaction of worse exposure to regulatory or financial sanction
- knowledge silos people or systems where the information cannot be shared or cross-referenced
- (more?? , tie back to problems in chapter 2)
| 1. WHAT IS RED PIRANHA |
Red Piranha is a set of ready to deploy components that solve business problems. Like Lego Bricks (tm) they can be reconfigured to meet different needs, using as few or as many pieces as required. The pieces integrate with existing investments (be it ...) to deploy more effectively the knowledge your team already has.
Picture of Lego Bricks??
In general , Red-Piranha is deployed into the business layer (as shown in the 3 tier diagram below in th. (bit more talk on what each layer does and how this fits). The exception to this is Red Web 2.0 (the Rich Internet tier) , which sits more comfortably in the presentation tier. It uses existing frameworks (such as JDO and Hibernate) to implement the Service tier.
3- tier diagram to show where RP lives- as a reminder as the original is already in the previous chapter
- Because it is open software, it is easy to extend.
- Because it is component based, you only deploy the parts you need.
- Because it is standards based, it can integrated with systems like Oracle, Jboss , Apache Tomcat, Websphere, SAP.
- Because it is transparant , it is easy to see what is going on and faster to deploy.
- Get the knowledge from people’s brains and into your computer.
- Because you can use it as a web page , command line or XML- WebService , it will work with most languages and platforms, including Java , Perl , C#/.Net and PHP on both Windows and Unix (Linux , Solaris and AIP).
- Because it is open source , it can integrate with any system. As a Java based program , it will run on any platform including Windows , Linux / Unix and Mac.
On a more technical note, Red-Piranha is like Appfuse (which combines a broad spectrum of Java Frameworks), except that it concentrates on Business Knowledge. P is created by the author of this document, is currently on version 3.x , with over 25,000 downloads so far. It is Open software , under the terms of the GPL available from http://red-piranaha.sourceforge.net
.
The Red Manifesto
- Solve the business problem using technology.
- Make it easy for business (non technical) people to understand what is going on.
- Make it clear to review the knowledge that has been captured by RP.
- Work with existing systems , as business have a lot of investments in these.
- Make the information in these systems more sharable
- Work with existing tools; where an existing tool can do the job better, let it get on with it , don’t get in the the way
- Be easy to change : be it takeover , merger, or adapting to the shortened development cycles
- Be a resource for different systems, don’t keep everything to yourself
- Must be low risk to start with: use a little , use a lot, up to the business to decide.
- Don’t reinvent the wheel: focus is on using widely available technologies and frameworks to the specified (Knowledge Management) end
Deployment Options
- Deploy as part your web application.
- Deploy online as a hosted application.
- Deploy the components as part of a command line application.
Business Model
One Analogy for RP is a plumber. You would expect him to arrive on site with all the tools they need. Typically you pay for their time , or per job completed, not for the tool hire. Likewise, Red-Piranha enables consultants to be more productive to fix what you actually want.
| 2. REAL LIFE EXAMPLES AND CASE STUDIES |
Some examples of the problems that Red-Piranha is trying to address :
| Red Adaptive Search | Business Problem: Where you have information, but don’t know how to find it. Solution: Red Adaptive Search engine that ’learns’ what the team wants, and finds more of it. Includes (i) Business Example: Documentation and Wiki search Link to Web 2.0: Unconventional data sources and adaptation to user preferences. |
| Red Financial Engine | Business Problem: Where you have information in Excel sheets, but can’t do much with it. Solution: Demonstrate ability to ’run’ Excel Spreadsheets using RP and Jboss Rules. Business Example: Financial Calculator Link to Web 2.0: Rapid and simple business logic development. The Enterprise Java answer to ruby on rails? |
| Red Workflow | Business Problem: Where several people have to work together on a set of information, following a strict set of steps. Solution: JBoss workflow with RP, with a simple online example Link to Web 2.0: How to orchestrated different systems. These systems may be (external) web 2.0 sites, or internal systems (with RSS capabilities added). Business Example: Expenses management or Insurance processing |
| Red Web 2.0 Rich Internet Applications | Business Problem: How to present this information to people in a easy to deploy, but powerful way. Solution: Demonstrate how to use Ajax and Rich web techniques on the previous samples. Link to Web 2.0: How to do Rich Internet Applications, Enterprise Java Style Business Example: RIA on Financial Calculator from (2) |
| 3. CASE STUDIES |
Red Piranha and it’s components have been deployed in several solutions. Below are some high level use cases to demonstrate what it can do.
Case Study 1– Workflow on Public Sector Exam Results Website.
A leading Irish Educational Institution needed to gather Exam results from 200+ locations. Exam result gathering was a multi-step process , requiring validation and authorisation of results for Multiple Candidates. The existing system , while written in Java was unstructured leading to to performance and maintainability problems.
Parts of the Red-Piranha framework were added to the exam results system. The system itself was refactored to Enterprise Java standards. Basic workflow and Ajax / Web 2.0 Techniques were introduced as well as unit and load testing scripts.
Not all desired changes were implmeneted, but the resulting system performed 5-10 times faster. The steps that had Red-Piranha workflow implemented provided a clear and easy platform for system maintainability. User feedback on the new Web 2.0 / Ajax screens was very postive, with the screens much easier to use , eliminating cluttered popups.
Case Study 2 – Adaptive Document Management for Multinational Pharmacetical Company
A large U.S pharmaceutical company identified that it’s cutting edge was in the management of it’s scientitic knowledge , from initial disoverery, to combination with other information through to it’s application and FDA approved drug release. The problem was that it had too many systems holding the knowledge. In additional , each scientific researcher had their own knowldege domain , making a ’one size fits all’ solution inappropriate.
The adapative Search Component of Red-Piranha was dep[loyed on-site. Documents were indexed and stored in a standard Oracle Database, alongside appropriate meta data. Information from other company specfic systems were included in the global index, and the entire system made available via the company Intranet with a familiar looking web internface.
From phase 1, The scientific researchers got the required ’one stop’ search to all company information. Security and audit were maintained in the original systems. Users were delighted with the ability of RP adaptive search to learn both what they and their teams were looking for in response to feedback.
Case Study 3 – Loan Approval Calculator for Major European Bank
A Major European bank had a complex process for approving or declining loan applications. 3rd Party brokers found submitting applications difficult as the reasons for the decision were obscure and known only to a small number of people in the bank. The challenge was to make the approval process more open , without giving away trade secrets.
Using the Red-Financial and JBoss server components, business rules on how to approve a loan were captured in a standard Excel Spreadsheet. This excel spreadsheet was compiled into Java Class , but the original source remaining intact. This was combined with Ajax (using the DWR toolkit) to produce and a web page deployed on both the company intranet and internet.
The loan approval team were happy because they still had visibility and control of the business rules. 3rd Party brokers because they could quickly get an approval decision, or recommendations on how to gain approval. The banks security team were happy because the application remained on the Bank’s server, even if it felt and performed more like a desktop application.
| 4. BUSINESS REQUIREMENTS - SEARCH |
Search can be seen as a admission of failure: either that we misplaced information, or that we never had it to hand in the first place. Search is a very easy problem to describe , but a difficult one to implement. While Google, Yahoo and MSN have made great strides in recent years, the are still fundamental problems to address
- Typically we search by keywords, but keywords have different meanings in different contexts (semantics)
- Search niches : Google is addressing the global search , but the only valuable searches are the ones that you perform.
- The Value of information being searched for differs from person to person, their team and their role (e.g. Whether they are in 9-5 job). Different results are valued depending on the role you are carrying out at the time.
- What you do after searching: People do not search for the sake of searching , but to apply it in a context (e.g. Make a telephone call with a number, carry out a decision)
- Not all information is available (even to the likes of Google)
- Propriatory Datasources (like corporate Database and mainframe).
- Paper based information
- Corporate Intranets not available to major Web search engines
- Complexity of Enterprise systems to integrate with
- Even where information is in an electronic format
- problem of different formats
- problem of different locations
- finding needle in haystack – the information that really matters, not the 1000’s of spurious results that don’t
Search is only one part of knowledge management. People typically search for something , then do something with it. Later , other people will either want to retrace their footsteps ,
The Red Solution
Red Adaptive search that can actually ’learn’ what you are looking for. It lets you go everywhere , find anything , understand everything.
Red-Piranha allows you to search information with a minimum of effort. With a little effort , it can search *anything* , including Oracle Databases , XML Webservices (including Java/J2EE and .Net webservices) , RSS and even Web based XML feeds such as Google and Amazon.
SUGGESTED USES
- Personal Search Engine for your Desktop (Windows , Linux and Mac).
- Intranet Search Engine - Search your Company or College Intranet. Search your Companies systems (including SAP , Oracle or any other Database / Data source). .
- Part of your Development Project - Have search abilities up and running in a few minutes.
- To provide Search facilities on your website or application - even if your application is Web , Swing , SWT , Flash, Mozilla-XUL, PHP , Perl or even C#/.Net based.
- In conjunction with a wiki, as a knowledge / document management solution. E,g. Provide a Search facility for your project documentation, including PDF , Word and other document formats.
- Scan a set of websites for the data you want (e.g. Search Job sites on a hourly basis).
- Because all meta-information is stored as RDF , it is an ideal starting point for exploring the Semantic web.
- As a Webservice to provide search information to other systems, or as a command line tool , to give searching power to your scripts.
Red Adaptive Search compared to other search solutions
To put red adaptive search into context , we compare it to Google and Apache Lucene. Google (the well known web site), also provides a desktop based search solution that can be installed on your PC
Red Adaptive Search compared to Google
Google provide three different types of solution : Internet (the well known web site), Corporate (A version of Google on a sealed server) and desktop (a program that you can install on your PC. All three products are good solutions and market leaders in their respective areas.
- Desktop search allows you to extend (like RP Can) to encompass other data sources.. However, Desktop Search is primarily an individual , rather than team based solution . It does not allow you to Incorporate results from search into another application, nor results from non-file based data sources.
- Corporate Search (the Google Search appliance) allows you to perform Search operations on a corporate Intranet , but with limited ability for customisation.
- Google , for reasons of Intellectual Property protection, does not allow it’s desktop solution to have the best available search algorithm
Red Adaptive Search compared to Apache Lucene
- Apache Lucene is the standard open search engine, from the people that brought you the defacto web server.
- It as a Search engine , not a search solution. This means that it is a very powerful tool , but needs further development to provide a solution.
- RP Adaptive search, since it uses Lucene internally, provides these extra components to give you the best of both worlds
| 5. BUSINESS REQUIREMENTS – RULES |
Note: This section draws heavily on previous articles written by the author. Rewrite this section to bring it more into line with the aims of the dissertation.
Capturing Business Knowledge using Rules
Most enterprises have a combination of formal and informal rules that they use. With traditional coding techniques , these ’disappear’ and cannot be checked, audited. The transformation from ’business knowledge’ to ’technical knowledge’ also introduces errors that can only be found at the (expensive) end of a project by extensive user testing. What could be more natural than writing business rules using Excel , a format that everybody knows , and then compiling these rules directly from Excel with no intermediate step needed.
Most Web and Enterprise Java applications can be split into three parts ; a front end to talk to the user , a service layer to talk to back end systems such as databases , and business logic in between. There are frameworks to solve problems the first two parts (Web and Database), but no standard way of structuring business logic. Frameworks like EJB and Spring do this at a high level , but don’t help us in organizing our code. Red-Piranha builds on the JBoss Rules Engine (Drools) as a framework to solve the problem.
There are are many aspects to complex business logic that Red-Piranha can help solve.
- How do business people check that the business logic is correct? It’s hard enough for technical people to review. Often , there is no methodical way of testing this
business logic.
- Where applications have similar business rules – if one of the rules change , is the change consistent across all systems? If a new application uses some of these rules , but also adds some new ones , do we need to rewrite all the logic from scratch?
- Is the business logic easily configurable , yet not so firmly tied to Java code that we need to recompile / redeploy every time that a small change is made?
- What if other (scripting) languages want to leverage the existing investment in business rule logic?
- How can we maintain code that is often convoluted and scattered over many files?
Our ideal solution would be compatible with not only Enterprise java applications ,but also ’normal’ Java programs and most of the widely used presentation and persistence frameworks. Such a framework should allow us to do the following:
- Business users should be able to easily read and verify the business logic.
- Business rules should be reusable and configurable across applications.
- The framework should be scalable and performant under heavy load.
- Developers should find it easy to work with.
- Allow storage and versioning of rules.
- Deploy into different environments
- Centralise so that it can be controlled (and hidden)
- Combined with FIT (automated User tests) to ensure their accuracy – both during development and over time
- Based on Excel sheets that users often use anyway to write requirements
Red Finance Rules
One solution that is gaining traction is to use a Rule-Engine. Rule Engines are frameworks for organizing our business logic that allow us to concentrate on things that are known to be true , rather than the low level mechanics of making decisions. Often , Business users are more comfortable with expressing things that they know to be true, than to express things in an if...then format.
When should I use business rules?
. While rule engines (RP) can solve a lot of problems for us , it is worth considering if a rule engine is appropriate for our Enterprise Java application. Some questions to ask are: ·
How complex is my application? For applications that shuffle data to and from a database , but not much more , it is probably best not to use a rules engine. However , where there is even a moderate amount of processing implemented in Java , it is worthwhile considering the use of the RP / Jboss Rules Engine. This is because most applications develop complexity over time.
What is the lifetime of my application? The answer to this is often
’surprisingly long’ - remember the mainframe programmers who thought their
applications wouldn’t be around for the year 2000? Using a rule engine pays off
especially in the medium to long term.
Will my application need to change? The only sure thing about your
requirements is that they will change, either during or just after development.
Drools help you cope with this by specifying the business rule in one or more easy to configure files.
What about performance?
If you’re writing an Enterprise Application , chances are that it will need to scale to hundreds ior thousands of users. While most developers hate to ’lose control’ and rely on other people’s code (i.e. a framework) for performance , consider the points below - Drools may even make your application run faster:
Tools and techniques that make the solution actually run faster the heaver load that is put upon it. (using optimisation and caching techniques)
- Avoids Badly written code: Rules guides developers to do ’the right thing’. Using a framework makes it easier to write good , fast code.
- Optimized framework: How often have you seen business logic that repeatedly access a Database for the same information , slowing down the entire application? Used correctly, Drools can remember not only the information , but also the results of previous tests using this information, giving the entire application a speed boost.
- Rete Algorithm: Many times we apply ’if’ conditions that we didn’t really need. The Rete Algorithm , as implemented by Drools , replaces all the if..then statements with an optimized network. It is important to note that the Rete Algorithim involves a trade off between using more memory to reduce delays at run time.
What Jboss Rules (Drools) Provides
Jboss Rules gives a best of breed Rules Engine, fulfilling all of the above criteria. An example of it’s use (including the advanced decision table features) is as follows.
1. The Business users express the business rules in a format they feel comfortable with.
2. A business analyst (or similar) puts these rules into an excel format similar to to the one pictured below.
Give screenshot of excel spreadsheet
3. All the developer has to do is all the cells (in yellow) to tie the rules to the remainder of the Java application.
That’s it – all the rules are expressed as if this is true , then do this.
What RP gives (over standard Jboss product)
Red Piranha is not just about business rules , but about knowledge management as a whole. It focusses on integrating the existing Jboss Rules Engine into business solutions. Examples of the functionality added with Red-Financial Rules are:
- Better integration with Web 2.0 Technologies (see following sections of this chapter).
- Explain a bit more here
- Integration with process flow technologies (next section). This is in addition to the existing integration with Jboss workflow.
- Integration with adaptive search technology.
- Better integration with Spring and other other application Server, including components to management the deployment and compilation of rules.
- Ready to use samples in the financial rules area
- Ability to plug in differeent rule engines.
- ready to use business rules
- Any others?
All of this additional functionality is optional – if it is useful , then it is available, but it is no forced upon the user of the application.
| 6. BUSINESS REQUIREMENTS – WORK AND PROCESS FLOW |
The problem and the Solution
Many business tasks need be carried out in a sequence , with different people and teams all playing their role. In an ideal world, you would draw your business process – a bit like the diagram below. Then you would plug your existing systems into it and have everything run smoothly. If any part of your business process changed, you would change the diagram and everything would follow the new process.
Diagram of Workflow as presentation / screenshots of workflow sample (expenses)
Red Financial Workflow (based on Jboss JBPM) allows you to do this. You draw the diagram using a visio-like tool. You attach attach actions in Java that "fire’ when the step in the workflow is reached. The actions link to different system and/ or assign tasks to people.
What workflow is
Our definition of workflow includes :
- Visio diagrams & lego bricks – should be able to draw a diagram , and then move pieces around as required.
- Should be able to assign tasks to people as and when required.
- Should be able to see a list of what tasks are where
- Should be able to mix people and automated tasks
- Tasks should be able to be dragged and dropped as appropriate on the workflow
- Workflow should be able to be reconfigured
- Should be an independent engine: most application don’t write their own database engine, why should you write your own workflow engine.
- It should all be available over the web , and can be integrated with other systems easily
What is process flow
- Process flow is similar to workflow , but without human intevention.
All system follow either a simple form of workflow, or processflow
- e.g. Web page: Login , then view banking details
- Eg. Automated overnight process
Advantage of workflow over these existing systems is that the system is broken into actions that can be recombined and reused in different flows and systems.
Workflow Samples
Workflow links together dispararate activies e.g.
- Online booking of fares (e.g. Aer Lingus.com)
- Loan Applications and signoff
- other financial decision making
- Planning applicaitons
- Complex Sales
- Expenses signoff
- Give others
Walk through the sample that comes with RP
Our sample of workflow :insurnace
Sample workflow
Todo – create simple workflow (e.g. Insruance) as diagram
- problem trying to solve
- Insurance Claim : walk through this as static
- Start workflow : claim info
- Auto check of all details (no – request end details from client <end>)
- Web bit
- Retrieve history from database
- Fraud?
- Call Bank webservice
- Check claim level
- less than <1000 : pay on consultant signoff
- between 1000 and 5000 : go to supervisor and consultant
- over 5000 call in loss adjuster & supervisor signoff
- Necessary signoff?
- No : route to missing signature
- Payout
- Send JMS Message to Bank
- Walk through this dynamically
What Jboss workflow gives you
- business process logging & failover
- Threading
- ease of use of workflow
- picture
- drag and drop
- events firing
- Jboss application server
- Visio like means for ’drawing’ the workflow
- Main workflow engine
Go through Jboss workflow feature list
What Red Workflow adds to this
- Jboss application
Spring integrations
Integration with out parts of the Red-piranha knowledge management sutie
ability to plug workflow endgines.
- - allows you to propotype workflow
- Ready to go busioness componetns
- Set of componetns to
- drive this workflow / process flow (e.g. Xml web service starter , db workflow startere)
- components to attach to this workflow
- abiltiy to cahnge workflow engines at later date
- tie into search, and web 2.0
- use components to work with workflow
- notion of process flow
- integration with web 2.0
- ready made samples in the financial area
- db process flow components
- notion of process flow , as well as ’work flow’
- Exception handling within the process and workflow
- Go through RP components to see what we add to this
Tie to Web 2.0
- Workflow and BPEL
Introduce BPEL and Jboss workflow, RP gives a sample based on a Financial application to show how to use it in your organisation
Workflow Link to Web 2.0:
- How to orchestrate different systems. These systems may be (external) web 2.0 sites, or internal systems (with RSS capabilities added).
- Prototyping using Web 2.0 Techniques
- tie into web 2.0
- Ajax
- XML Web service out
- XML Web Service in
| 7. BUSINESS REQUIREMENTS - ENTERPRISE WEB 2.0 |
What is Web 2.0
Use these to tie the other sections together
Web 2.0 is a new paradigm, building on the most successful techniques from the first 10
years of widespread internet use. These techniques include, Rich Internet Interfaces (RIA)
using Ajax, sharing of user data through RSS, RDF and other standard feeds, rapid
development, extension of other internet applications for new uses, orchestration , and the
use of unconventional data sources. Currently the focus of Web is on the consumer market.
At the other end of the scale are Enterprise or Business systems. Web 2.0 has not (yet) made a significant impact here, mainly due to the conservatism of the sector, but the problems to be solved are similar. Enterprise systems seek to take knowledge and put it into a system where the information can be stored, shared, processed or used for further analysis. The current standard for doing this is Enterprise Java, but a lot of the Web 2.0 techniques for knowledge capture and sharing are very applicable.
The combination of the above, ’Enterprise Web 2.0’, gives both opportunities and threats. The opportunities include being able to solve business problems with new and more efficient techniques. The threats include the fact that a Web 2.0 System is far from the ’traditional’ computing environment that we are used to.
Do one more run through from here to upgrade the text to ’ draft’
RP ties The dissertation proposes to look at how 5 key techniques and use them to solve Business problems in an Enterprise Web 2.0 environment.
Link the other strands together with the Web 2.0 notes contained there.
...
The other 3 sections come to the core of web 2.0 , as it all about sharing information
Web 1 was get it out there. Web 2 is make it work [find ref]
What is Enterprise Web 2.0
Tie back to overall theme of dissertation
Find a few more references. We look at how to ’make it work’ in the enterprise (define)
- Ajax and Rich Internet applications
- Mashup connecting systems
- Knowledge Sharing
- What is Web 2.0
- Presentation Techniques (the flexibility of the web with the power of the desktop)
- Collaboration
- Open Systems
- User (or individual added) value for selfish reasons , but with group benefit
- more
What is Enterprise Web 2.0?
Do a search and quote on this
Deploying Knowledge Using Web 2.0
The web is probably the greatest invention for both gathering and distributing information. Web 2.0 build on this , not only to present information in a more user friendly format, but allowing more effecitent machine to machine communication
- Standard formats, easier interoperability
- Rollout via Browser
- Rich Internet Clients
Systems are no good in isolation – they often need to capture information for people at different locations , different levels of skills and different levels of motivation. If a systems is not just easy to use, but appealing to use, the attempt to capture the information will have failed
It is no use capturing information , only to fail to distribute to those people who need it (whether the realise they need it or not)
Presentation techniques
RP and Web 2.0
The Web 2 stuff RP Covers
As a sample of this , we demonstrate how to extend the sample from the rules section in the previous section onto a fully blown online financial calculator.
The RP components used to do this could equally be deployed as part of the following solutions:
- Gather the knowledge of your most experienced staff and make it available to all.
- Knowledge Capture – moving from
- Financial trading systems
| 8. DEVELOPING SOLUTIONS WITH RED PIRANHA |
Why RP is better than traditional development
1. Works with existing systems
2. Works with existing technologies and frameworks
3. Extends these frameworks to give them a business focus
- We focus on the business functionality – the frameworks
- Spring , Apache , Tomcat , JBoss
- Go through the big names
- Oracle, SAP , IBM , Java , .Net , Webshpere , PHP, Ruby,
4. Faster, as using pre-existing lego bricks
5. more transparent as business users can inspect , augdit (and unlikely , but very possible) write the business rules / flow.
6. Java too slow to develop , even though it gives more stable long term solutions. RP enables a ’core’ business knowledge to be developed in (scalable) Java while utilising rapid development solutions such as PHP or Ruby. RP
7. Does not iimpose a particular style or solution – use the parts that are useful , does not dicate that you follow a particlar style
1. All about choice (e.g. Part about different )
| 9. WHERE TO RUN |
- Where to run
1. Standard
2. Hosted
3. Custom
| 10. SUMMARY |
This section introduced the Red-Piranaha framework and outline the Enterprise Web 2.0 problems that it tries to solve – managing and sharing knowledge using Business Rules, Workflow , Search , delivered using rich internet applications. RP doesn’t do everything , but it does seek to make things better by focussing on the business functionality required
The next chapter gives technical details of how to use the Red-Piranha framework to deliver this business functionality.
