Anarb
We upgraded from 5.1.2 to 7.0 earlier back in May. We have a homegrown helpdesk application running on Solaris 9 and Oracle 10g. We were converting from ARS/MT 5.1.2 running on Solaris 8 and Oracle 9i. Below are some of the challenges we had. With 7.0, Remedy uses a reserved range of groups ids from 60000 to 69999. We had already used part of this range and had to move them out of the range. Some of the affected forms are Group, SHR:ApplicationGroups, SHR:Groupinfo, User, SHR:People and SHR:People Support Group, in additional to other customized forms where that we had stored the GroupId. DB size was another issue we faced. We are a multinational company with customers in Japan and other countries who desire to use their own language. Pre-5, our customer could work tickets in any language and it would work. Remedy called this garbage-in, garbage-out because the type of language was not specified in either ARS or our Oracle DB. If the Chinese input in their language, it would be a bit pattern stored in Oracle. When retrieved, the bit pattern would be presented in the same fashion and the Chinese could recognize them. For Rel 5, Remedy starting their Unicode implementation. The Java in MidTier translated the incoming national characters into something that resembled US Ascii. When retrieved, they would usually be presented back to the customers as ?????????????'s. We had to put in a workaround to get the web to work for them. In 7, we decided to go full Unicode. This worked great. All countries can input their own language now. But it increased our DB size by 2-3 times. We were not expecting that type of growth. There was also a data organization change between rel 5 and rel 7. We essentially got around that by running a clean install of ARS on a separate server and letting it create the tables in Oracle. We then did an ARS export, import of the data to convert it to the new Rel 7 structure. We also had some MidTier issues. Some of the functionality on our Rel 5 pages did not work well on MT 7. We had some recoding to do there. Stay away from 7.0.1 releases before patch 3. Patch 3 resolved a major memory leak issue with ARS and a major headache for use.. Hope this helps. Dan Dan Wangler, Team Lead, STARS Group Phone: 214-567-8304; email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Client/Server Services, IT Opeations Texas Instruments, Inc. 6500 Chase Oaks Blvd., MS 8401 Plano, Texas, 75023 ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Barber, Dave Sent: Friday, December 07, 2007 9:09 AM To: [email protected] Subject: Re: Upgradation of Remedy server from V6 to V7 The answer would depend on what applications you are running on there. - running standard out of the box applications, its probably a relatively simple process of mapping old data to the revised forms. Note - relatively ..... - running heavily customised v6 (or earlier) applications, then you will have to spend a lot of time scoping the changes that have been made to the application (hoping that all the changes have been adequately documented). - running your own in-house custom applications, you'll mainly have to look into what links you have to the various system/people/group/etc forms, your workflow will have to be amended to reflect the different structure of the system on v7. Regards, and good luck with the migration, Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Arnab Baral Sent: 07 December 2007 15:00 To: [email protected] Subject: Upgradation of Remedy server from V6 to V7 ** Hi, I have an upcoming assignment on Upgradation of Remedy server from V6 to V7. Please give me details on the consequences and implications that might occur while this upgradation is performed. If anybody can provide me with a Doc for the same it would be a great help. Regards Arnab Baral Remedy Developer __20060125_______________________This posting was submitted with HTML in it___ Please consider the environment before printing this e-mail or its attachments. ________________________________ This e-mail (and any attachments) contains information, which is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient you must not copy, distribute or use it for any purpose or disclose the contents to any person. If you have received this e-mail in error, please notify us immediately at [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> . The information contained in this e-mail (and any attachments) is supplied in good faith, but the sender shall not be under any liability in damages or otherwise for any reliance that may be placed upon it by the recipient. Any comments or opinions expressed are those of the originator not of NTT Europe Ltd. unless otherwise expressly stated. NTT Europe Limited is a company registered in England and Wales with company number 2307625. Registered Address: NTT Europe Ltd. 3rd Floor, Devon house, 58-60 St. Katharine's Way, London, E1W 1LB, UK. Telephone +44-20-7977-1000. Facsimile +44-20-7977-1001. Website Link: http://www.ntt.eu <http://www.ntt.eu/> __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
