Because of popular demand, I'll post my findings to date. Let me preface this by saying that independently, the documentation and customization methods are fine for 2.5 and 7.6.x. So if you are a customer going to 7.6 from scratch, following the customization procedures should ensure a good path moving forward... for the most part.
Again, if ANY of you have done this successfully and can prove me wrong, that will be great because it means we can move forward with our project. I REALLY hope someone has done this upgrade but so far, I haven't been able to find anyone. Here's the issue when upgrading. 1. In 2.5, BMC recommendation for customization was just to use standard naming conventions and things like that. Great. We did that. 2. In 7.6, BMC recommends creating a linked custom universe which "sits on top of" the OOB ITSM universe and doing all the customizations there. (You preserve your OOB universe that way and in the future, you just break the link and recreate the link between your custom and new OOB universe) Great. We did that too. 3. They then recommend running the import tool for Boxi to pull the reports and users over from old to new. Here's where the fun begins a. All of the 2.5 reports are attached to the "ITSM" universe which is OOB. When importing, they still retain that universe relationship. b. Because of this, it doesn't see (not that it matters) any of your customizations in the custom universe. The reports will import without error but all the custom objects will be dropped. c. Let's say you find a creative way to change your reports in 2.5 to the same name as the custom universe you created for 7.6 (we found a way and thought we were awesome). d. You go back to running the import tool but still, the objects are dropped. Why? Because the import tool looks at a CUID which is a backend GUID for each object. This object just won't match because you created them brand new in the new universe! e. The first recommendation from support was to use the Import tool to bring over the 2.5 Universe... yeah... but... we'd lose all the benefits of upgrading. f. The final blow to us was this... Let's say a field like "Change - Task Notes" is missing from the universe in 2.5. We went ahead and added it. Now, in 7.6, the object is included in the OOB universe. You can't really use that new object because all of your reports are pointing to the custom object. So what have we done? We're now looking at recreating 800+ reports in the new environment. Complete recreation of every report. Obviously, we're not happy. -Tauf Chowdhury 646-483-2779 From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Robert Molenda Sent: Tuesday, May 31, 2011 8:19 AM To: arslist@ARSLIST.ORG Subject: Re: Note to the list about upgrading to 7.6.x of Analytics ** Interesting thread - count me in - as far as I can recall - I have never seen any "Best Practice" documentation on customizations to the BO Environment (Universe)... can you kindly share the reference material? (Document name / link..) Thanks On Thu, May 26, 2011 at 7:42 AM, Chowdhury, Tauf <tauf.chowdh...@frx.com> wrote: ** All, I'm still working through BMC to work this out (I'm at the level of talking to R&D/ Product Managers) but basically the issue we have is in the upgrade/migration/whatever you want to call it of going from Analytics 2.5 to Analytics 7.6.04. Basically, if you follow what BMC recommends as far as customizations in the 2.5 and the best practices of how to do customizations in the new environment, it is impossible. I can provide more detail off list as I know the Analytics community is not as big as AR/ITSM... -Tauf ________________________________ This e-mail and its attachments may contain Forest Laboratories, Inc. proprietary information that is privileged, confidential or subject to copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this e-mail to the intended recipient, you are hereby notified that any dissemination, distribution, copying or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ -- _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ********************************************************************** This e-mail and its attachments may contain Forest Laboratories, Inc. proprietary information that is privileged, confidential or subject to copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this e-mail to the intended recipient, you are hereby notified that any dissemination, distribution, copying or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
