This type of job is perfect for Meta-Update.
A simple script would create all the output files containing the job set
definitions and another script would do the reverse. Things like request ids
could be the same or different as you wish.
With a bit more work, you could even attach components of jobs to other jobs
such as copying an output set from one job to another
With Meta-Update you can automate any type of data transform in minutes.
Cheers,
Ben Chernys
Senior Software Architect
Canada / Deutschland
Mobile:+49 171 380 2329 GMT - 7 + [ DST ]
Mobile +1 403 554 0887
Email:<mailto:Ben.Chernys_AT_softwaretoolhouse.com>
Ben.Chernys_AT_softwaretoolhouse.com
Web: <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com
We are a BMC Technology Alliance Partner
Check out Software Tool House's free Diary Editor and our Freebies Section for
ITSM Forms and Fields spreadsheet.
<http://www.softwaretoolhouse.com/product/SthMupd/index.html> Meta-Update, our
premium ARS Data tool, lets you automate your imports, migrations, in no time
at all, without programming, without staging forms, without merge workflow.
<http://www.softwaretoolhouse.com/product/SthArch/index.html> Meta-Archive
does ITSM Archiving your way: with your forms and your multi-tenant rules,
treating each root request as a complete tree and checking associatuions.
Archive output to different servers, HTML pages with links to attachments or
archive forms.
<http://www.softwaretoolhouse.com/product/Databot/index.html> Meta-Databot is
an automated, extensible BMC Data Wizard. It reads a file of data changes and
sports an Undo feature.
Pre ITSM 9.1.04? Clarify? HP? Roll your own? No problem! You can keep your
valuable data!
<http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/
From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Jaffer Mahsoob
Sent: February-08-18 4:30 PM
To: arslist@arslist.org
Subject: Copying AI transforms/jobs
I am looking for a reasonable way to copy portions of the AI repository between
systems, for example from DEV to QA. Exporting/Importing the repository makes
the folders, but none of the content (Jobs/Transformations). Exporting to XML
and then importing is painful at best, I have approximately 300
transformations, and 100 or so jobs, which are arranged by folder... I was
thinking that essentially, the repository is just data stored in the
UDM:Repository:* forms, but I just can't wrap my head around how I could
programmatically export everything into a usable format that could be moved to
another system.
I'm open to suggestions...
Thanks,
Jaffer
--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist