In the recently released ITRM 3.4 solution, ITRM macros to load and update ITRM tables into the SAS LASR Analytic Server, to start and stop the SAS LASR Analytic Server and to unload the SAS LASR Analytic Server have been added to the solution.  Information about these macros can be found in the ITRM Administration Guide in a section called "Integrating SAS Visual Analytics with IT Resource Management" found in appendix 10. There are no plans to add the SAS Visual Analytics product into the IT Resource Management solution.  This said, elements of Visual Analytics like the LASR server and the Designer and Administration capabilities will be considered for inclusion in future releaes of IT Resource Management .  ... View more

Mr. Seifert,   Yes there are plans for ITRM to support an Adapter for SAS Environment Manager and the SAS development and product management teams for both SAS Environment Manager and ITRM are working together now regarding this integration.  Currently the plan will be for the SAS Environment Manager team to create a set of SAS tables from the information stored in the SAS Environment Manager database and it will be those tables that will serve as the source data for ITRM and for use by Customers who wish to use any other SAS product to analyze this data.  It is anticipated that the SAS Environment Manager SAS tables will be delivered in SAS 9.4M1 and ITRM Adapter support will come in a later release of the solution.   ... View more

Mr. Seifert,   The ITRM product team received the recommendation to support MXG annual releases per your conversations with the SAS Germany Account team and recorded that information in our requirements management system .  Our solution development team is taking steps to stream line the process of allowing ITRM to support MXG releases and we are very hopeful that the results will allow us to deliver updates to ITRM MXG based adapters in a more timely fashion.   ... View more

Mr. Seifert,   Current plans are to release of ITRM 3.4 on SAS 9.4M1 late this year or early 2014.  ITRM features anticipated in this release include: Exception Analysis   Support for analyzing IT data and generating reports for exceptional event and data measurement occurrences Visual Analytics Integration - New Macros to load and unload ITRM data Report Center   Home, Gallery, Resource and Admin Workspaces   Album (point and click galleries) and Watch List features   All ITRM reports can now be referenced by link Adapters   Large volume data source enhancements - override Staging input and output data source locations   Update IT data mart - Add Domain Category to existing IT data marts   Adapter Updates for:     MXG     VMware vCenter     Demand Technology Performance Sentry     HP Performance Manager     Microsoft Systems Center Operations Manager     RRDTool for freeware systems management ... View more

The mentioned paper (Margaret Crevar / Tony Brown) is a good one. An important issue is the monitor monitor monitor sentence (understand your system). This is often ignored as it will cost effort with no obvious result. Monitor tools like NMON are giving a lot (interactive & collectors for daily monthly trends). Monitoring  has to start at OS level. The Tuning of a SAS installation is adding that part of SAS as second (dependant). The SAS automatic macro variables are containing some indicating the used OS version. you could make a list of that, just to be sure. Other setttings (options like max memory) are setting limits on the OS resources. With Unix (Aix) they are mostly set not that high, at a Windows desktop it set/left more open.  Processor speeds are not really different (stable last 6 years) capacity must come from the number of cores. Running a BI/DI (metadataserver) and webserver with all compute servers on a 6Gb memory  would be challenging. The OS has to run the metadataserver has to run the webserver with javacontainers the SAS system and at last on top of all the SAS (compute/user) processes.  The first needed 4 parts are easily needing arround 8Gb of ram. Shortage of ram is recognized by a thrashing, the OS memory manager will be very busy and that can become all he is capable off. So starting at 16Gb is a very sensible choice. The next thing, having enough memory: check your IO (more in detail saswork). IO is by default cached and by that consuming RAM. Accessing big files would need big caches to fit, otherwise it will cause unnecessary overhead.  Segregating Saswork optimizing IO throughput is the next challenge. There is a lot to review and to do for getting en optimal system.   ... View more