Hi Nishant,

We've been upgrading a large Versata Java app from 5.6.3 to 6.3 and it's been a
*lot* of
work. But it is a large, complex app with a *lot* of custom code.

This is not a trivial endeavour -- depending on how much custom code you have.
If you
have very standard Versata applications and business objects, with very little
custom code,
the transition should be relatively easy (I emphasize relatively).

If, however, you do have a non-trivial amount of custom code (and all real-world
apps do),
there will be some work involved. The API's have changed quite a bit, the
behaviors of
these API's have also changed in subtle ways, and of course the environment is
completely
different (welcome to Eclipse). You'll also have to deal with a new version of
the app
server.

How big is your repository? How many data objects, query objects, apps and
pages/screens (HTML or Java)? Have you measured your repository using the
Automation
Analyzer? It's very handy to assess where you stand.

Be prepared for some bumps in the road... If you can provide additional details,
we can go
further into what you can expect.

-- Max Tardiveau - Integrity Logic


--- In versatausersgroup@yahoogroups.com, nishantvij <no_reply@...> wrote:
>
> Dear All,
>
> I am new to versata and looking for people who can guide me about
> the same.
>
> I am working on the application created in versata 5.6.2.
>
> My question to you is if I need to move the current application
> which is developed in Versata logic Studio (versata 5.6.2 build 52)
> to versata-6-workbench-6.3-build44761.
>
> ~ What should I consider the most?
> ~ Will there be a code change?
> ~ Will there be any issue in porting the current application?
> ~ According to you which features may not work and what should be
> the approach for porting the existing application to the higher
> version?
>
> Waiting for your guidance!
>
> Sincerely,
> Nishant
>