http://blog.saasinct.com/2009/03/19/integration-frustrations-and-why-i-am-no-longer-a-fan-of-sas-itrm/?utm_source=rss&utm_medium=rss&utm_campaign=integration-frustrations-and-why-i-am-no-longer-a-fan-of-sas-itrm :: Sharing with the world everything we discover about SAS. Tue, 25 Oct 2011 14:27:49 +0000 hourly 1 http://wordpress.org/?v=3.3 http://blog.saasinct.com/2009/03/19/integration-frustrations-and-why-i-am-no-longer-a-fan-of-sas-itrm/comment-page-1/#comment-243 Brian Mon, 01 Jun 2009 01:57:49 +0000 http://blog.sasinct.com/2009/03/19/integration-frustrations-and-why-i-am-no-longer-a-fan-of-sas-itrm/#comment-243 Yes, I think you were being a bit harsh. Its not so hard as you make it out - the templates provide the same support for many data sources including BMC - and v2.7 did not come with prebuilt datamarts (PDBs) and reports for BMC either - but the adapater for reading the BMC data was there - and it is there in ITRM v3 too. We have had no issues with having a custom repository, and generally find it runs well with all pieces on a single tier. You would only have a seperate instance of WRS if you going to integrate this all into an existing DI setup - which I dont think is a good architectural choice anyway. Why place system performance data processing as an overhead on production systems? If your data feed breaks, ITRM would need to wait for it to arrive, in which case you have the risk of running performance processing during your production processing window. Not good. I think its a matter of expectations, and while v3.2 seems to be adressing much of that in a significant way, I still find that using ITRM sure beats writing your own. The idea of writing your own in ITRM is not like completely writing your own. ITRM comes with so much of the work already done. Even for a brand new custom data source, at most you do a one off exercise to define the metadata and then use the DI functionality to build the rest. I would always choose ITRM over the alternatives because it gives me a significant head start compared to 'building your own'. Yes, I think you were being a bit harsh. Its not so hard as you make it out – the templates provide the same support for many data sources including BMC – and v2.7 did not come with prebuilt datamarts (PDBs) and reports for BMC either – but the adapater for reading the BMC data was there – and it is there in ITRM v3 too. We have had no issues with having a custom repository, and generally find it runs well with all pieces on a single tier. You would only have a seperate instance of WRS if you going to integrate this all into an existing DI setup – which I dont think is a good architectural choice anyway. Why place system performance data processing as an overhead on production systems? If your data feed breaks, ITRM would need to wait for it to arrive, in which case you have the risk of running performance processing during your production processing window. Not good. I think its a matter of expectations, and while v3.2 seems to be adressing much of that in a significant way, I still find that using ITRM sure beats writing your own. The idea of writing your own in ITRM is not like completely writing your own. ITRM comes with so much of the work already done. Even for a brand new custom data source, at most you do a one off exercise to define the metadata and then use the DI functionality to build the rest. I would always choose ITRM over the alternatives because it gives me a significant head start compared to ‘building your own’.

]]> http://blog.saasinct.com/2009/03/19/integration-frustrations-and-why-i-am-no-longer-a-fan-of-sas-itrm/comment-page-1/#comment-199 Tapan Patel Thu, 19 Mar 2009 20:40:39 +0000 http://blog.sasinct.com/2009/03/19/integration-frustrations-and-why-i-am-no-longer-a-fan-of-sas-itrm/#comment-199 The upcoming SAS ITRM product release (ITRM 3.2), built using the latest SAS 9.2 components/technologies, addresses your requirements regarding “dependent repositories” (e.g. ITMS repository) and will also deliver out-of-the-box reports for supported SAS ITRM adapters. Having said that we would like you to continue your support for the product in future. If you shoot me an email, we can discuss your concerns in more detail. The upcoming SAS ITRM product release (ITRM 3.2), built using the latest SAS 9.2 components/technologies, addresses your requirements regarding “dependent repositories” (e.g. ITMS repository) and will also deliver out-of-the-box reports for supported SAS ITRM adapters. Having said that we would like you to continue your support for the product in future. If you shoot me an email, we can discuss your concerns in more detail.

]]>