Documente Academic
Documente Profesional
Documente Cultură
www.GoUpte.com
Page 1
Why RIA?
It is assumed that readers of this white paper have already made the decision
to transition to RIA (Rich Internet Application), and don't need any further
persuasion about its merits. To be thorough however, we will summarize the
top reasons Magic Software provides for making this switch:
For further information on these benefits, please see "Top Reasons to Go RIA
(January 2011)" from Magic Software.
www.GoUpte.com
Page 2
Abstract
When migrating to RIA, there are many issues which need to be addressed in
order to successfully convert a 2-tier client/server application to a 3-tier
architecture, while still preserving all its existing functionality. Those issues
comprise a lengthy checklist of procedures that must be carried out properly
and in the correct order to ensure a successful conversion. Failure to follow
through on even one of those tasks could wreak havoc on the converted
application, an outcome that could be catastrophic for mission-critical
applications.
www.GoUpte.com
Page 3
Table of Contents
www.GoUpte.com
Page 4
The Tyranny of Non-Automated Solutions
Magic customers who want to convert their application to RIA usually have only
two options:
1. Functionality
The #1 objective of a RIA conversion is to first and foremost preserve the
functionality of the current application. Unlike developing a new RIA application,
migrating to RIA requires taking into account all existing constraints present in
the converted application and its associated database. Applications developed
with client/server architecture typically werent given any consideration during
their design that one day they might be converted to RIA. This issue escalates
in importance and complexity the larger the application is and the more
components it contains, or if its integrated with some other Magic application.
www.GoUpte.com
Page 5
2. Changing the Applications Architecture
The RIA platform is based on a 3-tier model, so the conversion process should
address all relevant issues connected to the architectural changes the
application will undergo. These changes are not only reflected in the
application itself, but also the implementation of the RIA method. For example,
a direct connection no longer exists between the client and database as is
customary in client/server applications. In RIA, brokers are instead used to
facilitate this connection.
3. Performance
In conversions such as these, performance is a major issue. After the
conversion, there are more elements involved in the deployment of the
application (IIS, Magic Broker, Bandwidth, etc.), and these can impact
performance. Another factor to contend with is that the converted application
was not originally designed to be a web application, with all the performance
issue considerations such development requires.
www.GoUpte.com
Page 6
5. Handling Unsupported Elements
Although Magic Software's RIA uses the same studio development environment
as uniPaaS (xpa) client/server, this solution is completely different. As a result,
there are many elements and objects that are not supported anymore by RIA in
a broad swath of areas.
Rather than give customers a list of elements and objects that are no longer
supported, a fairer solution would have been to find alternatives and include
them for implementation during the conversion process. However, for
whatever reason, Magic Software opted not to do that.
7. Costs
Transitioning to RIA should provide benefits to the organization making this
move, and these benefits should be quantifiable so they have a business
justification. If the price of converting to RIA is too high, there may not be a
business justification for migrating to this technology. Manual conversion or use
of unqualified vendors lacking 100% true automated tools will inevitably lead to
higher costs, as well as the unbudgeted involvement of an organization's
internal development resources. Additionally, testing procedures will likely be
greatly extended and the "adventure" of the RIA transition will quickly be
exposed as problematic and expensive.
www.GoUpte.com
Page 7
8. Time Table and Code Freeze
The issues listed thus far in this document highlight only a few of the problems
that can make a transition to RIA complex. The conversion process needs to
handle lots of problematic issues within the constraints of maintaining existing
system functionality and performance. Executing a conversion manually or
using semi-automated tools will inevitably lead to much lengthier project
durations, which could literally end up lasting for years. No organization wants
to find itself dealing with such a nightmarish prospect. Further exacerbating
the timeline is the need for application code-freezes, which can leave an
organization's clients stranded awaiting critical bug repairs and other solutions
that must await completion of a non-automated conversion.
10. Experience
A customer who has no experience in conversions (especially conversions to
RIA), or a sub-contractor who does not specialize in this area, can wreak
enormous damage on an organization migrating to this technology. Such
conversions are complicated and have many moving pieces. RIA's working
environment and deployment require deep familiarity with new technologies
that are not part of the standard Magic/uniPaaS environment, i.e.
Microsoft.Net, IIS, Framework, Broker, etc. Those inexperienced in these
conversion projects yet who try tackling them anyways will generally not have a
very high success rate.
www.GoUpte.com
Page 8
Why You Should Use Up Technologys 100% True Automated Solution
The best way to perform a RIA conversion is by using the true 100% automated
solution from Go Up Technology. This is the only approach which will enforce a
multitude of encapsulated best practices to ensure that EVERY step which
SHOULD be done actually GETS done. Accomplishing this manually would be
extremely difficult and far more time consuming for even a senior-level expert,
who due to schedule constraints might be tempted or even pressured to cut
corners. There are no corners cut when a true 100% automated solution is
utilized, and deadlines are much more likely to be met since no manual
intervention is necessary.
1. Functionality
Go Up Technology's 100% true automated solution ensures your application's
functionality will be preserved, while also adhering to the rules of the RIA
framework. These two unique, but crucial, objectives are handled during the
migration process, which ensures that the solution for each issue will be
standardized throughout the application. Go Up Technology has pioneered
creative solutions to overcome the kind of constraints likely to be found in the
old client/server application that might otherwise have prevented it from
working correctly in the new RIA environment.
www.GoUpte.com
Page 9
3. Performance
Mitigating performance degradation is a specialty of Go Up Technology's 100%
true automated solution. By optimizing various processes executed as part of
the conversion, our tool ensures that performance impacts will be minimal, if
even noticeable. We also ensure implementation of the best solution for any
particular issue based upon the context in which it appears. In addition, we
take advantage of the conversion process to leverage new capabilities the RIA
engine makes available (for example Chunk Size) allowing us to maximize
performance.
www.GoUpte.com
Page 10
7. Costs
There is no doubt that RIA applications enable an organization to streamline the
process of application maintenance, which in turn opens up new market
opportunities. However, these benefits still need to be weighed against the
costs of converting to RIA. As specialists in conversion projects and their
benefits, Go Up Technology understands that the cost of a conversion is a
critical factor in deciding whether to migrate to RIA.
This is the reason we developed our 100% true automated solution. It's the
most economical means of making the transition, and when it comes to cost, it
will beat any other alternative.
10. Experience
"Hundreds of satisfied customers can't be wrong."
www.GoUpte.com
Page 11
Conclusion
www.GoUpte.com
Page 12