Hi,

We'd like to establish the following in CA CMDB:

Application A has an interface with Application B. In addition we want to specify the type of interface and maybe extra attributes for that interface.

Sadly CA CMDB does not allow to specify attributes on the relationship itself (e.g. "This is an interface using a component that is running on a 3rd CI", or "it uses SOAP XML web service calls on HTTP port 443"). Is there any reason why that is? Or what would be a good way to establish the above relationship(s) in CA CMDB? The path chosen should allow us to easily view / query the CMDB to show all applications that use web service integrations running on a given framework and the applications that integrate with each other that way.

Short of adding custom fields on the CI relationship object I can't see any working solution.

Thanks in advance for any pointers you may have.

Maarten

Does anyone have any advice for Maarten?

How to best represent an interface in CMDB and Visualizer

This question is Not Answered.(Mark as assumed answered)

MAARTEN DE RIDDER Feb 24, 2015 11:18 AM

Hi,

We'd like to establish the following in CA CMDB:

Application A has an interface with Application B. In addition we want to specify the type of interface and maybe extra attributes for that interface.

Sadly CA CMDB does not allow to specify attributes on the relationship itself (e.g. "This is an interface using a component that is running on a 3rd CI", or "it uses SOAP XML web service calls on HTTP port 443"). Is there any reason why that is? Or what would be a good way to establish the above relationship(s) in CA CMDB? The path chosen should allow us to easily view / query the CMDB to show all applications that use web service integrations running on a given framework and the applications that integrate with each other that way.

Short of adding custom fields on the CI relationship object I can't see any working solution.

Thanks in advance for any pointers you may have.

Maarten

Hi mderidde

The only thing that CA CMDB offers in this context is that you can create custom relationship types and as such more descriptive ones than what is provided OOTB. I would warn though that this becomes next to impossible to read from the CMDB Visualizer if you make the relationship types too long textually.

Thanks,

John Sorensen