AROUTPUT- Can be used for any Remedy Regular Form OOTB or CUSTOM.
While CMDBOUTPUT- Is used for CMDB Class
But CMDB Class data can be updated using AROUTPUT so why BMC has provided two different steps.
as a best practice You Should first Load your CI in Staging Data Set. There may be Different Discovery Sources for each you create a Staging Data Set. For these Purposes You need CMDBoutput Step to load data into Staging Data Set. Once you have Data in Staging Data Set - After than Recon job will push the CI into Golden Data Set of CMDB.
Now coming on ARoutput Step- This needed to even do a simple load in any of the remedy Form from Spoon job and One of the cases are your AST:Forms where you are loading your data. WHat about loading some data into Users form etc.
Hope this helps.
Uploading data on staging dataset that can also be possible through AROUTPUT (We can directly map data set name with data set ID field)
I use AROUPUT to Skip recon jobs and load directly in Golden Data sets- Short term Quick Loads. I have not tested this but try the same and put CI in Staging data set using AROUTPUT Step and then Run Recon job. Since AST Forms are joins and It also uses AST:Attributes form this is where i suspect the issue will come.
This is why we use CMDBOUTPUT Step and specially data is pushed to AST:Attribue form.
Please let us know how that goes...
my understanding is that technically both works with the same mechanism, may be cmdbinput is all about getting further specific by passing some field default values like dataset by inbuilt that are related to cmdb forms/classes?
As suggested, I have uploaded one CI using AR output and another CI using CMDB output steps in staging dataset then created reconciliation job and did not find any issue, both CI's record has been created on AST:Attributes form.
Using AR Input any of the AR Forms including CMDB forms data can be transfered
here you need to map dataset id compulsory
Using CMDB Input plugin CMDB forms data can be transfered to any of the forms, tables or files
Use cache or Use checksum options are there in cmdbInput plugin so that user can create Delta job
Using AR Output data can be load in any of the remedy Form
Using CMDB Output data can be transfered only to the CMDB forms to load data into Staging Data Set.
ARoutput is the generic step packaged along with the remedy server platform whereas CMDBOut is specially designed to create/update CI in the CMDB and part of Atrium Integrator. We need to keep in mind that CI is not just a another record in the remedy and has to handle carefully.
You can create/update CI in any CMDB class based on some key values AND under specific DATASET. It is very important from CMDB perspective. You can specify list of attributes that need to be updated during the transaction if there is a existing CI matching with the qualification.
Again it is specially designed for BULK transactions with some special characteristics like 'use cache', 'use checksum'. (Checksum, itself has some special meaning in CMDB book).
2 of 2 people found this helpful
It is true that AROutput can replace CMDBOutput in most cases but not all. If you have a categorization subclass CIs to be loaded then AROutput may not be useful.
A few advantages already listed down by few others but reiterating
1. use of Cache will optimize your data load time
2. Update qualification will help you avoid unnecessary updates.
3. CMDBOutput provides you OUT column value InstanceId that can be further used to update certain relationships or even asset lifecycle data in the same load step.
4. The qualification builder is suitable for CMDB CI operations.