Remember, this is Friday:
I recently tried the 4.5.2 User (and Admin) tool against an 8.1 Server, it
did not go well. 
Now I will skip ahead without explaining why I even tried that.

The structures are too different. Mostly I think it is all the new ARSystem
admin forms need more recent features, so you will have to upgrade them to
the 7.6.04P? User tool. That worked fine of course.

My guess would be that the page field would work in the User Tool and not on
the web, but just a guess. Can't wait to hear the answer.

Of course I  would be remiss if I didn't suggest any developer or admin that
isn't up to speed on 8.1 at a minimum should go to WWRUG13 to learn about
the latest.

I will get pounced on for this but I personally loved 4.5.2 and would stick
to an updated Windows User Tool if I could. 
(I also hate and distrust VMs even though I have been working with them for
30 years, or perhaps because I have).

Daniel

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe D'Souza
Sent: May 31, 2013 3:36 PM
To: [email protected]
Subject: Re: 7.6.4 Client with 8.1 server

You have received many responses including one from the 'creator' which may
have answered your main question.

I would like to add something to "For any development, you would want to
move to the 8.1 version of Dev Studio.  You do need to remember that any
client side feature that was added since 7.6.04 will not be available to the
Windows client." that Doug mentioned.

Considering your jump is enormous, by any standards, there have also been
some features that were deprecated along the way (not just additions of new
features), which are no longer available. One that jumps to mind is the
ability to 'share' fields across pages in a page field which I think was
introduced in 4.5? Since you are a custom shop, if you have used that
feature, upgrading 'may' carry forward the already developed feature, but
once upgraded, you will not have the ability to create a similar feature if
at all you choose to replicate it in your future state some place else.

You might either need to reconsider using that feature in the future version
by developing it NOW and move it up, or drop it and modify it to maintain
consistency in your app. I recall I spent quite some time on a version it
was deprecated from, to figure out why I could not develop that feature.

There may be other such features that might have been dropped but I can't
think of any.

Cheers

Joe


-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Mueller, Doug
Sent: Friday, May 31, 2013 1:57 PM
To: [email protected]
Subject: Re: 7.6.4 Client with 8.1 server

I would strongly encourage you to go with 8.1 for the AR System.

The 7.6.04 Windows client is fully compatible with and runs with full
functionality and capability against the 8.1 server and we have many
customers who use this combination for environments or situations where
there is still some use of the Windows native client.  And, I see there have
been several responses to the list of customers with this combination with
no issues.

For any development, you would want to move to the 8.1 version of Dev
Studio.  You do need to remember that any client side feature that was added
since 7.6.04 will not be available to the Windows client.

As noted by another list member, all 8.1 server side features will be fully
available.

Now, I would also set up the 8.1 mid-tier and validate that your application
runs without issue there.  You can have that up and available for anyone who
wants to come in that route.  You do not have to force it, people can use
the WUT if they desire, but as people find that they can move around to
different machines and have full access to things on the Web and the app in
its full capability is available there, transition does start to happen.

And, if you do add to the functionality using things that take advantage of
8.x features, they will work just fine in the mid-tier (although not in WUT)
and you can continue moving your application forward as another draw to the
web delivery.

The system does allow you to take things in stages and to have gradual
transitions from where you are to where you want to be in the future.

The upgrade should be nice and simple and transparent (of course try in dev
first and in a test environment second to make sure that there are no
problems -- with backups to protect from failure.  this is all of course
just good practice).
The
AR System upgrades are generally clean and easy -- OK, an occasional issue
in the past if you have customized a system form but even that is better in
the newer releases.

Happy journey as you move forward with your solution,

Doug Mueller

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of PCB
Sent: Friday, May 31, 2013 9:44 AM
To: [email protected]
Subject: 7.6.4 Client with 8.1 server

Hello - 

I'm involved in a bit of a nightmare project. 
I'll spare you most of the details, but, I'm upgrading a custom Remedy app
from 4.5 to either 7.6.4 or 8.1.

It's currently on 15+ year old hardware that's failing. (Unix, Oracle.) We
have new modern hardware ready to go for the replacement.

I've been doing remedy dev since 1999, so I'm up to the task.

There are a million things I'm going to run into, but my one big question is
related to the Windows User tool.
All of the users have only ever used the User tool; they've never even seen
the midtier. I'd like to use 8.1 because it will remain supported longer and
this will likely go a long time before being upgraded again. Also, there are
some new features I'm interested in. However, if the 7.6.4 client doesn't
play well with 8.1, I'll be forced to install 7.6.

My questions: Have you been running the 7.6.4 user tool against an 8.1
server? For how long? How well is it working?

Based on past experiences with backwards compatibility with Remedy, I'm
imagining it will work well enough, but I wanted to check to make sure.

Oh, and to head off anyone saying to just force them to use the midtier -
that will be a political battle, not a technology battle. We are going to
make the midtier available to them, but the app is used by another
department and they have dictated that they need the user tool.

Thanks everyone.

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers
Are, and have been for 20 years"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to