Shyam, Can you let me know one thing?
We have similar environment like yours and recently upgraded from CMDB 1.1 to 2.0.1 patch 5 following BMC's white paper. But now we see that we cannot relate Computer CI to another Computer CI or to a Printer CI from the Related Items tab like we could do with CMDB 1.1. The following relations are possible: Monitor to Computer Sys/Printer Computer System To Monitor Printer To Monitor In all the above possible combinations common to Monitor, only Component - Hosted System is available as relationship menu option. I submitted a tkt to BMC for verifying but till date I have got no response from them. Do you see the same combinations? Can you let me know? Thanks, Mohan --- Shyam Attavar <[EMAIL PROTECTED]> wrote: > Manish, > > I am not sure specifically if ITSM 6.0 version of > the apps will have an > impact if run under AR System 7.1.0. By and large > this should work without > any issues unless AR System 7.1.0 release notes > state this and if so what > pieces would be impacted. I am not fully clear, > since I have not read the > 7.1.0 documentation yet. > > We moved from AR 6.3.0 Patch 20 running ITSM 6.x (HD > 6.x AM 6.x and CMDB > 1.1) to AR 7.0.1 Patch 2 last year running ITSM 6.x > (but only difference was > we moved from CMDB 1.1 to CMDB 2.0.1) after the AR > upgrade. Our apps are > running without any issues in production and we are > extremely happy with the > setup. > > One thing I would recommend is to upgrade AR from > 6.3 to AR 7.1.0 in place > with the Upgrade option (which will just upgrade the > AR components without > impacting the application). What you have mentioned > below will not work - > quoted here again:- "We are looking fwd for the > feasibility, if we 1. > Install ARS7.1 2. Apply our existing database dump > of application (Incident > Management 6.0 + Change Management 6.0 + SLA 2.0) 3. > Install Mid Tier 7.1 4. > Install Oracle 10g 5. Install CMDB2.0" > > Also, upgrading CMDB 1.1 to CMDB 2.0 is a multi-step > manual process and I > hope you have the white paper that describes how to > do this methodically > without impacting the data in your current CMDB. > > HTH, > -- > Shyam > ----- Original Message ----- > From: "Manish SINGLA" <[EMAIL PROTECTED]> > Newsgroups: gmane.comp.crm.arsystem.general > To: <[email protected]> > Sent: Sunday, June 22, 2008 10:10 PM > Subject: Feasibility of migration of ARS6.3 to > ARS7.1 keeping Application > Incident Mgmt and Change Mgmt v6.0 > > > > Hello List, > > We are into overall architecture change of our > existing Remedy > infrastructure. > Currently we are on ARS6.3 + Incident Management 6.0 > + Change Management 6.0 > + SLA 2.0 + CMDB1.1 + Oracle 9i. > > While testing Oracle 10g with our existing ARS6.3, > we realized that ARS6.3 > in not compatible with Oracle 10g client. > So we foresee ARS6.3 as a bottle neck to our > Architecture update w.r.t to > Oracle and other components of Remedy as well for > e.g. we can't be On > CMBD2.0 unless we don't have ARS7.1. > > We are looking fwd for the feasibility, if we 1. > Install ARS7.1 2. Apply our > existing database dump of application (Incident > Management 6.0 + Change > Management 6.0 + SLA 2.0) 3. Install Mid Tier 7.1 4. > Install Oracle 10g 5. > Install CMDB2.0 > > WILL MY SYSTEM WORK AS IT IS WORKING NOW. If not > what are the issues behind > and how we can overcome those. > > Your input on this keeps very value for me. > > Thanks > Best Regards > Manish. > +91 98107 98076 > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where > the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
