Hello community, I'm trying to find the iTop best-practice for adding SaaS software to the CMDB to be able to associate with Change tickets. For example, Office 365 tenant or Salesforce.com. What kind of CI do you all use to create these types of systems?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good question! It really depends what kind of info you'd like to link to your SaaS software I guess.
We used to document them as "Web Application" or "Application Solutions" (because we could link a lot to a solution).
Recently I started working on a different approach to software and middleware; mostly for licensing options we needed (share licenses across organizations; also be able to use downgrade rights and still link a proper license). https://github.com/jbostoen/itop-jb-software-mgmt
As you'll see, a "Software" here is now either typical client software, server software, cloud software or an operating system. Users, devices are then linked to this software.
So it really depends on your own views/approach; and what kind of links you'd like to add in the future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm, grappling with this at the moment.
In some ways I think notion of cloud is possibly more like a location or farm (in which case it would be in a region - (location).
For instance if I am running EC2 instances (Virtual Machine) with our software then AWS region would be like a farm or possibly represent EC2 as a hypervisor ?
A lambda service would be (not sure)?
DynamoDB could be a Schema ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello community, I'm trying to find the iTop best-practice for adding SaaS software to the CMDB to be able to associate with Change tickets. For example, Office 365 tenant or Salesforce.com. What kind of CI do you all use to create these types of systems?
Good question! It really depends what kind of info you'd like to link to your SaaS software I guess.
We used to document them as "Web Application" or "Application Solutions" (because we could link a lot to a solution).
Recently I started working on a different approach to software and middleware; mostly for licensing options we needed (share licenses across organizations; also be able to use downgrade rights and still link a proper license).
https://github.com/jbostoen/itop-jb-software-mgmt
As you'll see, a "Software" here is now either typical client software, server software, cloud software or an operating system. Users, devices are then linked to this software.
So it really depends on your own views/approach; and what kind of links you'd like to add in the future.
Hmm, grappling with this at the moment.
In some ways I think notion of cloud is possibly more like a location or farm (in which case it would be in a region - (location).
For instance if I am running EC2 instances (Virtual Machine) with our software then AWS region would be like a farm or possibly represent EC2 as a hypervisor ?
A lambda service would be (not sure)?
DynamoDB could be a Schema ?