Content moved to Top Viewed CMDB Knowledge Articles
Content moved to Top Viewed CMDB Knowledge Articles
I'm looking for customers who are open to discussing how the Internet of Things is affecting your organization, how you are implementing IoT infrastructure within your organization and your approach to managing these devices within your infrastructure?
I would be looking to have a 30min discussion with those who are interested and implementing IoT in their infrastructure and providing service to their customers.
Please reach out to me via email or post a reply in this thread firstname.lastname@example.org
Well another release of BMC CMDB is in the wild and I wanted to quickly cover what we’ve been upto in 18.05.00 (find out more about the rest of the release here and from the Connect with Remedy webinar we held on Wednesday 20th June).
In 18.05 we have introduced a new searching capability for the CMDB which provides greater flexibility for ‘power users’ and also easier searching for those who do not understand, or need to understand, the way the CMDB is organised and structured to find what they are looking for.
We have CMDB Quick Search for quickly finding CI’s that don’t require complex qualifications or relationship traversal, all you need to define is the Dataset you want to search in, we default to BMC.ASSET the Class you want to search again we provide the most frequently used as the default BMC_ComputerSystem, and the Attribute you want to search, all using typeahead menus etc. to ease the experience.
But we haven’t forgotten ‘power searchers’ in the new experience, here we have implemented some prebuilt complex searches that traverse relationships - the most commonly asked for - and also provided a custom option so you can build your own powerful searches in the UI.
You can then select a search result, or several and view them in our CMDB Explorer or export the results to a .csv file, you are also able to view CI details inline within the search results drawer.
In this release we also introduce our all new CMDB Explorer which relies on the new searching capabilities as it’s root but then allows you to expand your understanding through visualization of the results and ability to filter and add additional search results to the new canvas.
The CMDB Explorer Canvas is where all the action takes place, along the left we have the toolbox which allows you to alter what is displayed and how it’s displayed and then along the top our CMDB Search ‘widget’ so you can search for additional content and bring that into your canvas to view.
We have implemented filtering capabilities, alternate layouts, hover over information when you are on a CI or Relationship object and also ‘inline’ CI Details view so you can see the details of the CI right there in the explorer window without having to jump to another screen, for those of you who are BMC Discovery customers this should appear pretty familiar as we were inspired by the work done in the Modelling interface within the BMC Discovery product.
Our efforts and focus now shift over coming releases to completing our User Experience story, amongst other things, we are now working to bring you Edit capabilities to explorer, Modelling toolsets for Services and other collections of CIs, Sandbox capabilities and also other tools that remain in the CMDB toolset such as Class Manager, Impact Designer and Impact Simulator - these utilities and tools will be updated over coming releases to the new UX paradigm along with existing elements being updated.
You will also note that, as we started in 9.1.04, our product name is being rebranded to BMC CMDB, this release introduces that change in product, you will also notice that in BMC Communities the BMC CMDB community is now located within the BMC Remedy ITSM suite hierarchy, we’ve taken this step to make it easier to find and also more logically aligned with he primary use of the CMDB - this change is a logical move and does not reflect anything functionally changing or aligning in CMDB moving forward - CMDB remains and will continue to be delivered with other BMC products, such as BMC Discovery.
We would love to hear your feedback on our new capabilities in CMDB in this 18.05 release, please make comments below.
CMDB New UI is NOT hosted in mid-tier.
It is hosted on AR contained Jetty server.
Yes, From the home page fly-out menu, Atrium Core – Click on Configuration Manager Dashboard.
Yes, below are typical urls for accessing new CMDB UI :
If there are no load balancers configured on AR Server, CMDB installs the configurations out-of-box and no explicit action is required, including in server group environments.
If you require any modifications due to jetty port change, https configuration change or server name modification or load balancer configurations then only you need to modify these
Home Page Flyout menu – AR System Administration Console – System – General – Centralized Configuration – com.bmc.arsys.server.shared – shared
Make sure that Jetty Port is correct. The out-of-box value is 8008. If you have modified the Jetty port, please reflect in Jetty Port parameter here.
Redirect-URL parameter will typically have following values :
If there are 2 servers in server group, ARServer1 and ARServer2,
then in such cases, Redirect-URL parameter will typically have following values :
Again, when you install server group, these values are populated by CMDB installer. If you require any modifications due to jetty port change, https configuration change or server name modification or load balancer configurations then only you need to modify these parameters.
If there are 2 servers in server group, ARServer1 and ARServer2 , with AR load balancer as remedy.bmc Redirect-URL parameter will need to change as follows
Mid-Tier looks for Redirect-URL parameter values. It looks for the same server from which context url is launched :
http://<MidTier Host>:<Mid Tier Web Server Port>/arsys/forms/<ARServer>AR+System+Customizable+Home+Page/Default+Administrator+View
Make sure the ARServer value here matches the one in Redirect-URL parameter i.e.
There is new servlet - ExternxalLaunchPointServlet released in SP4, so midtier version must be SP4 only.
This servlet (ExternalLaunchPointServlet) and its mapping configured under web.xml of midtier, please check if entry for same is present in midtier’s deployment descriptor i.e. midtier/WEB-INF/web.xml file.
You can check the logs to find out if the servlet is being hit by setting the mid-tiers log level to Fine.
Once you set the log level hit the servlet and check midtier logs, you should see “Entering ExternalLaunchPointServlet” getting printed in the logs.
If web.xml is customized then after upgrade, you should add following :
In such scenario, as Active link CMDB:LaunchCMDBConsole has a hard coded URL that includes
/arsys PERFORM-ACTION-OPEN-URL /arsys/launch/cmdb
you don’t use the default of arsys for your midtier context, then you need to customize this active link accordingly.
With RSSO Configured :
Without RSSO :
When you enable RSSO for AR, as Jetty is embedded in AR and the REST API is also running on Jetty and Jetty is enabled with RSSO, so making all the REST calls fail due to redirection to RSSO.
In such case, in server’s 'rsso-agent.properties' file’s exclude url should contain /api/jwt/login* so that existing REST APIs are not redirected to RSSO.
Any other useful links? Go on Docs pages
This year I'm looking forward to meeting as many of you as possible at the T3:SMAC conference being organised and run by tooltechtrain, sponsored by BMC Software.
I have a session to walk you through our new CMDB User Experience releasing soon and also be available for meetings and hallway conversations of course - see you there!
If you want a new version of our updated CDM Diagram poster make sure you come and find me at the BMC area to grab one - let me know you are attending the conference and when we meet you can get your shiny new poster!
Visit the website are REGISTER for your place at the conference, don't forget to let me know you are coming and come and collect your poster...
When I joined BMC Software just over 3 years ago I came to the company with one key aim in mind, to make the CMDB a better CMDB.
As a team here at BMC we have made strides on that journey but none bigger, outwardly at least, than the version we released just before the holidays, the Atrium CMDB is going through somewhat of a transformation and we want you to be some of the first to see it and also have input to what we are doing.
With the release at the end of 2017 of 9.1.04 we have embarked on the transformation of the Configuration Manager User Experience. Many of our customers have been contacting me asking when this was coming or asking if CMDB was coming to SmartIT as that solution has evolved.
The new user experience is beautiful, intuitive but also functional and helps you 'get things done!' Don't get me wrong there is a learning curve, some things work slightly differently, the UI certainly looks completely different But instead of typing about it, let me show you with some teaser screenshots (for some reason here I wanted to have a James Earl Jones or Morgan Freeman voice over....)
Screenshot: CMDB Login Page
Screenshot: CMDB CI Updates Summary
Screenshot: CMDB Reconciliation Job Listing (Identify)
We have also introduced some new thinking for 'in tool' help and guidance. Introducing a new user experience is fraught with potential issues and isn't something that happens frequently due to this, however in order to make it easier for you, our customers, we want to ease you into the new approach we are taking.
With this in mind we have implemented some new functionality that will help with orientation in the new experience and also provide interactive 'in tool' help this is a mix of walkthrough style help along with video content - it's not all finished yet of course, this is a beta program - but we have exposed some of the ideas and thinking from our documentation team and engineering.
Screenshot: Configuration Managers Dashboard - Health Panel
We would all really appreciate your thoughts on this approach and implementation.
We are looking forward to discussing these changes and evolving them as we move forward, we plan for our next release to introduce changes around consumption of CMDB including a new graphical framework (think replacement for Atrium Explorer) and also improved searching capabilities to make finding the information you are looking for easier and more straightforward.
Lead Product Manager, Atrium CMDB
Hello there and welcome to today's blog post. We'd like to inform our customer base and my fellow technical staff on something that perhaps lacks clarity to some extent.
I'll break the points I need to get across in three sections.
1. Atrium Single Sign ON (ASSO) installation on a bundled tomcat.
Historically we've always recommended to use the bundled tomcat when installing BMC products. My personal understanding of this is that we have coded the features using that instance with a specific version of java and hence trying to maintain that set together as one deployment makes sense. 10 years ago that would have been OK and somewhat expected. But things are changing rapidly and the software community has grown to a sizable workforce.
Having more people collaborate on a platform also helps us to find more vulnerabilities more quickly. Over the last 10 years we, the software community, have identified more sensitive areas than in the previous decades. That means that software vendors have to keep up with these flaws and correct the code and hence release fixes and patches more often. This of course means that our approach to installing with bundled software packages has been met with new challenges of compatibilities. The bundle become obsolete if new fixes can not be applied to it.
ASSO is one of the products where external (also known as existing) Apache Tomcat can be utilized. This gives our customers the ability to maintain fixes and adhere to their IT Department's security policies by subscribing to patches provided directly with the vendor. It should be implied that vulnerabilities of Tomcat are not vulnerabilities of our products and maintaining up to date fixes really is best handled by the software vendor.
2. Remedy Single Sign On (RSSO) installation on an existing tomcat.
RSSO does not even consider bundling the Tomcat with the installer. Based on what is true in section 1. we've already realized that this is the way to do it. Although you will still see Tomcat bundled with Atrium Web Services (AWS), the future of our product installers will likely follow a separate path and hence give the control of installing it back in the hands of IT Departments.
In doing so, IT Departments can maintain a Product Catalog and predict deployments by a controlled version release and patch maintenance. This is ideal.
3. Authentication of products using SSO
The above two points outline the differences between two SSO technologies and what platform they would run on. However, there is a third aspect of this topic and that is the compatibility between the two. ASSO is now becoming a interim legacy product and BMC's future for SSO is in RSSO. That is a clear path forward. However, we're not ready to cut to it just yet.
Some of our products are taking a position in line to get integrated with RSSO while operating under the ASSO flag. These products are getting attention to integrate with RSSO.
One of these products is True Sight 10. As of now TS10 can only get authenticated by ASSO, but the future is already laid out for this product. It will integrate with RSSO and when that happens ASSO will likely become an obsolete product.
A) For RSSO, this means for you is that for now the cut over can be planned, but not realized until RSSO agent is built. Meanwhile as new threats and vulnerabilities are discovered, and you are using RSSO your already installed Tomcat, then please make sure that your Tomcat software is updated as recommended by the Apache Tomcat software vendor. There is no impact on RSSO as of now, Aug 2017. Oracle's Java is already applying Java updates via agents installed on the hosted endpoints. We're not sure how Apache will solve their future updates, so that means that your IT Department is your best line of defense. RSSO provides and hopefully meets your needs for user authentication, but when it comes to patching Tomcat please make sure to keep up with the software vendor.
B) For ASSO bundled Apache Tomcat patching questions please check with BMC support for compatibility issues with new Tomcat releases. For now do not upgrade ASSO Tomcat. Instead ask the BMC AtriumCore support to create an escalation with development.
I got to meet Doug Mueller... Engage 2016 gives you access, (BMC CMDB Architect) and Antonio V. (BMC Discovery Product Manager). in person recently. Here is my recent ah-ha moment with CMDB, and Discovery. I will start with BMC discovery (ADDM) then move to the CMDB topic of service concept. There is lots confusion out there on the difference of technical and business service should be within the CMDB. Some of you might say, I knew that years ago! But, It took me awhile to grabs the concepts even though we used, implemented, and develop the various BMC products. I am a visual and tactical learner. I am writing this blog for those type of students. Diagram 1 explains The Pattern Language (TPL) and how things are discovery
Picture 1 explains the discovery concepts and how things are the development by looking for a pattern within a process(s) running on a device. Once you find that process you write a pattern or use discovery to find that process via TPL. By using the discovered process, you can now create a software instance(s) by the group the process into the software(s).
Diagram 2 shows the structure of the TPL base on Diagram 1. Notice the trigger is on a node of node kind base on the condition. You now see the relationship between the pattern and the TPL. Once you define the software instances into business application instance(s). Once BAI is moved into the CMDB CI called BMC.CORE:BMC_ApplicationSystem, BMC.CORE:BMC_ApplicationInfrastructure. Base on your application model you create using the pattern that is consumed by CMDB common data model in different ways. You also need to know that TPL's foundation is in Python. Those of you are interested in pattern and AI. That's another discussion/blog.
Let's look at BAI and SI from the discovery with SAAM and predefine SI that becomes part of a larger model like BSM.
SAAM's Business Application Instances are consumed by these forms:
Let's look at the CDM for CMDB forms BMC.CORE:BMC_ApplicaitionSystem and BMC.CORE:BMC_Applicaiton. You have to understand that parent class is BMC.CORE_ApplicationSystem. The subclasses are BMC.CORE:BMC_Application, BMC.CORE:BMC_ApplicationInfrastructure, BMC.CORE:BMC_SoftwareServer. (Basics)
|CI Name||CI Class||Description|
|BMC Atrium Discovery and Dependency Mapping Active Directory Proxy 10.1 identified as Active Directory on %hostname%|
|manager module on Apache Tomcat Application Server 7.0 listening on 8005, 8080, 8009 on %hostname%|
|Class that stores information about services that represent low-level modules of an application, for example the components deployed within an application server. This class has no corresponding DMTF CIM class.|
|BSM (Business Service Managment is define pattern via TKU of software instance)|
By understanding the above and what's documented by discovery leaves ITSM team a decision to make between BMC_SoftwareServer or BMC_ApplicationSystem. Why do you have to make a decision is that BMC discovery sync with both of these CI? (BMC did not make the decision for you.)
To understand why let's review and understand model:
To be continue....
It is not comsume by the follwing forms:
(Non-organized brain dump)
If you look at CMDB forums, there is lots of confusion around what technical and business service(s) is defined with CMDB in relationship to BMC discovery. I've consulted with large companies like Duke, Starbucks, and eBay. I am finding that this question is asked over and over again. The way understood @Doug Muller: There is no direct relationship between business and technical services that relate(s) into BMC.CORE:BMC_ApplicationSystem. These definitions can be defined by how your business generate revenue with a business service. (If your company makes cars. Any system that supports selling cars is tied to business services.) . Technical services are defined supporting of business service(s). You can define the technical services without a business service(s). The confusion comes from the type of business your company does and way BMC represents examples of technical vs business service(s). BMC is a company that sells software so a lot of the business services sounds like technical services but, it is not a technical service(s). Becuase those services help generate revenue for BMC software. More to come later...
Why CMDB & Discovery project fail
|Project Scope||The scope of these projects starts out has let's map the services but, the reality is that there are lots of scope creeps. The value creation is loose scoped based on my experience. The value creation for CMDB needs to understand and measure for each ORG.||Discovery covers the automation of discovering IT infrastructure at the data center level but, does not cover end to end communications. Mapping of BAI isn't scoped right. BMC has recognized this issue by adding manage service to map application.|
|Project Constraints||Human Resource, Knowledge Base, Wisdom Base, and Where to start the value creation for an ORG.|
Service Modeling brain Dump
If you want to learn discovery in detail and how you can answer debated question. Please start here: ADDM Support Guide
When you create an application mapping in discovery. You have to create dev, qa, and production instance that sync's into CMDB. Those instance has to be grouped into relationships and parent class. The Parent CI is ApplicationSystem use impact relationship to BMC.CORE:BMC_ConcreteCollection CI is used for tore a generic and instantiable collection, such as a pool of hosts available for running jobs. This class is defined as a concrete subclass of BMC_Collection and was added rather than changing BMC_Collection from an abstract class to a concrete class.
I'd often get questions about how does discovery provided value to application owners vs management. Here are some key thoughts about the value the discovery delivers.
System Administrator & IT Architecture Value
Management & C-Suite Value
T3: Service Management and Automation Conference is NOW OPEN FOR REGISTRATION AND CALL FOR PAPERS
BMC Software and the Tools, Technology & Training (T3) community are listening and you have been heard! We are excited to announce the launching of the first ‘T3: Service Management & Automation Conference’ to be held from 6 to 10 November 2017 at The Palms Hotel and Casino in Las Vegas.
The conference is being put on by TTT: Tools, Technology & Training Company. As the Flagship sponsor, BMC Software is providing the conference with full support in running the conference.
Together, we plan to bring to you a robust conference focused on the Tools, Technology and Training that you need to succeed in your roles and accomplishing your business needs!
The conference website is LIVE and is accessible by going to http://www.tooltechtrain.com/. If you have any questions about the conference, please contact the Board of Directors at email@example.com or call me at 443-812-9891 (leave a message with a phone number and I will get back to you as soon as I can.).
Member of Board of Directors
If you want to use $TIMESTAMP$ or a formula of that to use as part of query to fetch/update data you can do the following supported method.
Use a Get System Info step first to get the actual/current TimeStamp.
Then, run the date here through Select Values to format the date in the way we want it:
yyyyMMdd is the format that ARS will accept here.
Then you can use this TIMESTAMP in your query, for example in CMDBInput here:
You may have received a 'Product Change Notification' notice from the BMC support team (dated Feburary 7th 2017) which notes that the Atrium CMDB Suite has been withdrawn.
I wanted to write a post to clarify what has actually happened to the Atrium CMDB Suite and clear up any confusion, also hopefully lessen the flood of enquiries coming into my mailbox asking about it.
Atrium CMDB has been sold as part of many of our products and also sold separately. What we have actually done is withdraw the product set (Atrium CMDB Suite) that is sold individually as we now see Atrium CMDB as a core part of our AR Platform.
As such this notification should not be seen as Atrium CMDB going away, in fact that is far from the case - we have several updates planned at present and will be delivering updates as part of our service pack and standard releases moving forward all that is changing is how BMC sell and account for the CMDB within our product groupings and solutions removing the need for this separate product listing.
I hope this clears up any confusion that our Product Change Notification may have caused.
Of course if you have any questions or queries please feel free to reach out to me.
Lead Product Manager, Atrium CMDB
BMC Software Inc.
Today's topic is about data quality and CMDB data reconciliation. Data management is impacted when data can not be verified and tracked to its source. We're in the business that seeks data quality and often rely on data auditing to see when a change was made. By whom, when, and why. However, in some cases this may not be as clear cut as it seems by just looking at the change history captured by the AR auditor.
There are less known ways of back tracking changes made to CMDB records, known as CIs and Relationships.
This blog post is about hidden fields in the CMDB application that can help me understand when and how a record was updated.
Let's say that the MarkAsDeleted field has been getting set to a Yes value, while the source record is still set to No.
In such case you'd likely want to know what is making the change and you suspect Reconciliation Merge activity as the culprit.
You can follow markers back to it's source to see if it really is Reconciliation.
Usually the inquiry begins by looking at the recon logs. Logs set to debug level will show what value is being updated.
Value of 0 is No and 1 is Yes. The log can also indicate that MarkAsDeleted is not being updated at all.
For example. Log shows:
Attribute : MarkAsDeleted
Value : 0 << this shows the default value of MarkAsDeleted as No.
From Dataset: BMC.ADDM
In this case we'd want to know "when" exactly did the change occur. I can find the proof by looking at the CI itself. Was it reconciliation doing it? Has it merged the CI with a value for MarkAsDeleted that equals Yes ?
Here is how to research it:
Find the CI in BMC.ASSET dataset that was modified to MarkAsDeleted = Yes and look at the LastModifiedBy value.
Is it "Remedy Application Service" ? If yes, then it could have been Reconciliation, but also Normalization or even AtriumIntegrator using that account.
I am going to need stronger evidence than that. So, my next step is to look in the AttributeDataSourceList field. This field has the footprint of the last merge. It includes the source record Dataset Id and a list of Field Id's that "won" the precedence contest from that dataset. If you see BMC.ADDM followed a list of id's that include the number "400129100" (MarkAsDeleted) in the list then you can assume that the field was updated during the last merge. But there is no guarantee that the value was Yes or No at that point.
But we can do better than that.
1. Run an AR Report to get the value from a hidden field named as LastREJobrunID.
This field is defined as follows in Attribute Definitions form:
Attribute Name* : LastREJobrunId
Data Type* : Character
Field ID : 490001289
ForeignKeyID (Class GUID) : BMC_ASSETBASE
instanceId : CMDB_ATTR_ID_LAST_REJOBRUN_ID
Namespace : BMC.CORE
2. Take the LastREJobrunId value from the CI that was changed, go to form "RE:Job Event" and search it using the value from step 1 using the field named: Job Run Instance Id*.
The result should give you about 3 or so records. One record for each activity and one record for the log location.
3. Take a look at the date range of these activities and see if the ModifiedDate of the CI fits within the activity related to Merge. These records will have a value in "ActivityName" that describe which activity has created them. If the Create Date and Modified Date is outside of the date range of Modified Date of the CI then it was not reconciliation that has set the value. You can stop here because reconciliation simply did not do this. If the value in LasModifiedBy is Remedy Application Service, then the data could have been modified by some other method like Normalization or AtriumIntegrator. However, if the Modified Date is in synch and within the range of the LastJobREId then this record has not been modified by anything else since it was merged into BMC.ASSET dataset.
If you do find that the Modified Date of CI does fit within the Create Date and Modified Date then it was Reconciliation that did it and you'd see this captured in debug level logs.
On the other hand of the investigation did not show that the record was modified within that range of Create and Modified Date in Reconciliation Job Events then some other method was used to make the change.
Hello there fellow AtriumCore enthusiasts.
I got inspired to blog about something I've been working on with customers who synch their ADDM data to CMDB.
As a side note, ADDM is now called BMC Discovery, but I'll use ADDM for now since most people are still referring to it as ADDM. On the CMDB side we are still using dataset Id "BMC.ADDM" and "ADDMIntegrationId". I am not sure if this will change. I hope not, because it would impact previously reconciled data. Provenance (the source) is referenced in AttributeDataSourceList field and changing the DatasetId would impact Precedence rules.
Getting the discovered data across is one thing. Understanding what happens to it on the other side as another. I've sort of expected that ADDM administration skill set also includes AR Server configuration knowledge, but now I know that AR Server and ADDM administration is usually done by two mutually exclusive teams. This blog is likely going to help each side communicate their expectations to the "other" side.
For the ADDM Admin:
You already know that the Remedy AR System hostname and port is the destination for your data. You may also know that there is a Remote Procedure Call (*RPC) queue to which ADDM defaults to but is not restricted to. I'll get to the queue details later, but what is important to know next is that AR Server is running in a server group. I was trying to think of a good way to visualize this and one thing that came to mind is the three headed dog known as Cerberus. I could have also used the multi-headed Hydra as an example, but Cerberus seems more appropriate for what I want to say.
So, the dog Cerberus has three heads and it guards the underworld. If you have a dog then you already know that that dog gets pretty preoccupied when eating with just that one head. Imagine having a dog with three heads. You basically would have a dog that listens for squirrels, smokes a cigarette and has dinner all at the same time. Each head gets to decide what to do while the food goes into just one stomach. That's kind off what the AR Server does. Information is digested and deposited in one data store. Usually three or more AR Servers are interfaced with the AR Midtier and at least one of them is dedicated to processing CMDB data in bulk. Reconciliation, Normalization, and AR Escalations.
These AR System hosted features also use *RPC queues that allow for seamless data exchange between these external API's.
It keeps a dedicated queue opened for them. ADDM synchs its data to CMDB via AR Server using one of these RPC queues.
However, what you need to know is that the CMDB API used by ADDM defaults to queue number “390696”. This queue is actually the CMDB dispatcher queue and using it can sometimes cause contention with other CMDB activities.
This is likely the communication that you will have with the guys that administer AR Server. Unfortunately that CMDB RPC queue can not be changed, but BMC R&D is looking into adding more CMDB queues and perhaps even BMC Discovery (ADDM) dedicated queue. Don't quote me on that. It's a rumor. It can be set differently on the ADDM side. This is probably something that you will have to talk about with the AR Server administrators. Tell them that you want a different queue assigned. By doing so you can add more *RPC queue threads. For example 390699.
This is easily said than done because there are only two CMDB queues available. Queue 390698 and 390699.
The first one is usually used by Reconciliation engine and the other is for Normalization. BMC Discovery will do best if it has its own queue dedicated to it. But that might be difficult if that same server is used for Normalization and Reconciliation.
In this case it would be easier to add another head (AR Server) to the server group and dedicate it exclusively to specific data processing activities. In AR Server version 9.1 you can dedicate another AR Server to run normalization by setting its rank in Failover ranking form. Not the server group ranking. You may still need to install that additional instance if that AR Server provides service to Asset Operators via midtier. This would the best way to ensure best performance for ADDM to CMDB integration.
Cerberus and Hades
There is one more thing. AR Escalations. These are features that trigger when data is created or modified. You want to ask the Remedy admin to not have escalations enabled on the same server that gets the ADDM data.
For the Remedy guys:
All you really need to know is that ADDM uses Java API that send sends the data and it can toggle whether that data is sent as a "pre" or "post" 7603 data model.
Anything after CMDB version 7603 should be sent as 7603 with Impact as an attribute. This means that the CMDB will receive "Impact" relationship designation in an attribute rather the old and deprecated BMC_Impact class. It relieves the need to run the Deprecation plugin that convers the class to an attribute.
AIS supports Weighted Clusters. That means, clusters that are composed of different weighted components. One of the components may be a small server and another a big servers. Maybe both are running the same services, but the users of those services will see a bigger impact if the big server goes down, so this needs to be replicated in the Impact Simulator.
The basic of the behavior is explained in the documentation. Here: Settings that affect the impact model - BMC Atrium Core 9.1 - BMC Documentation
But how does it really works on the background:
ImpactWeight is an attribute of the BMC_BaseRelationship class. It requires an integer value. The impact weight is used in impact relationships to determine how much importance (numerically weighted) to give to each provider relationship that impacts a consumer instance. A higher numerical value indicates a greater importance. Impact weight is used with the WEIGHTED_CLUSTER status computation model.
A consumer instance (C1) has impact relationships with three provider instances (P1, P2, P3). Each impact relationship can be ascribed a status weight to gauge the effect that an event propagating from the provider instance has on the consumer. In this example, the following status weight values are entered for each impact relationship:
C1 and P1: StatusWeight=100
C1 and P2: StatusWeight=50
C1 and P3: StatusWeight=25
All three impact relationships apply the direct propagation model.
Instance P3 has a critical event, making its status UNAVAILABLE, which becomes its propagated status. The propagated statuses of P1 and P2 are classified as OK. The propagated status of one impact relationship is UNAVAILABLE, while the other two are OK.
To determine the weighted impact on the consumer instance, refer to the following table of propagated status values for components and to the following formula:
P3 has the status of UNAVAILABLE, which has a value of 80. P1 and P2 have the status of OK, which is 30. P3 has a status weight value of 25; P1 has a status weight value of 100; P2 has a status weight value of 50.
To calculate the impact that the provider relationships have on the consumer and the consumer's impact status, use the following formula, which applies the status weight to each relationship:
(Propagated Status Value x Status Weight Value) of each impact relationship (P1,P2,P3) / sum of the Status Weight values of all impact relationships
In this example, the formula would be calculated as follows:
[ (30 x 100) + (30 x 50) + (80 x 25) ] / (100 + 50 + 25) = 37.14
In the actual implementation of AIS the table of propagated statuses is much shorter since we do not have that many options in AIS:
This is what we implemented.
UNAVAILABLE(3, "CRITICAL", "Unavailable", 80),
IMPACTED(2, "MAJOR", "Very Impaired", 70),
MINOR(1, "MINOR", "Impaired", 60),
WARNING(0, "WARNING", "Slightly Impaired", 50),
OK(-1, "OK", "Ok", 30)