Re: Exporting data from CLM -> Non-CLM
Have tried creating a job in Pentaho? We have recently done something similar and Pentaho worked for us! Tim -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jared Dean Sent: Thursday, May 02, 2013 6:28 AM To: arslist@ARSLIST.ORG 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_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Exporting data from CLM -> Non-CLM
how about RRRChive? On Thu, May 2, 2013 at 6:48 AM, Jared Dean wrote: > ** > 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 wrote: > >> ** >> The easiest way to accomplish this transfer is by using DSO. >> -Original Message- >> From: Jared Dean >> To: arslist >> 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_ > > > _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"
Re: Exporting data from CLM -> Non-CLM
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 wrote: > ** > The easiest way to accomplish this transfer is by using DSO. > -Original Message- > From: Jared Dean > To: arslist > 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"
Re: Exporting data from CLM -> Non-CLM
The easiest way to accomplish this transfer is by using DSO. -Original Message- From: Jared Dean To: arslist Sent: Thu, May 2, 2013 8:37 am Subject: Exporting data from CLM -> Non-CLM ** Hello All, We are currentlyrunning CLM 3.0 which contains additional cloud data that is not present inAtrium 8.0. We initially tried to use the CMDBDriver utility, but since its version specific we have been unsuccessful. The issue we arehaving is that the source Atrium has certain CMDB extensions that do not (andshould not) exist on the target Atrium. Specifically, the CLM Cloud Extensionsare installed on the source Atrium. When we run an import using the CMDBDriver utility on the stand-aloneAtrium 8, we get import errors (120004) complaining that attributes in the XMLimport 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 datafrom 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 filesstill contain attributes that are provided by other namespaces. Thissubsequently causes imports to fail, since there is "extra" data. Thanks for thehelp! Jared _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"
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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
