Thanks for the reply John. Unfortunately, DSO is not an option due to the way our infrastructure is setup.
-Jared On Thu, May 2, 2013 at 8:43 AM, Roger J <rjust2...@aol.com> wrote: > ** > The easiest way to accomplish this transfer is by using DSO. > -----Original Message----- > From: Jared Dean <jldea...@gmail.com> > To: arslist <arslist@ARSLIST.ORG> > Sent: Thu, May 2, 2013 8:37 am > Subject: Exporting data from CLM -> Non-CLM > > ** > Hello All, > > We are currently running CLM 3.0 which contains additional cloud data that > is not present in Atrium 8.0. We initially tried to use the CMDBDriver > utility, but since its version specific we have been unsuccessful. > The issue we are having is that the source Atrium has certain CMDB > extensions that do not (and should not) exist on the target Atrium. > Specifically, the CLM Cloud Extensions are installed on the source Atrium. > When we run an import using the *CMDBDriver utility* on the stand-alone > Atrium 8, we get import errors (120004) complaining that attributes in the > XML import files does not exist in the target dataset. We know what the > issue is, but are unsure how to solve it. Essentially, we want to export a > subset data from CLM 3.0 Atrium. For a given dataset, we want to export all > classes & attributes that exist in the BMC.CORE, BMC.AM, and possibly > BMC.FED namespaces. Even when specifying a specific namespace to export, > the resulting XML files still contain attributes that are provided by other > namespaces. This subsequently causes imports to fail, since there is > "extra" data. > > Thanks for the help! > Jared > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "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"
