Object and entity are almost always (if not always) the same on persistent objects but don't technically need to be. Object is a metadata name inside of Maximo which will exist for persistent and non-persistent objects. Entity will only exist on persistent objects because it's the name of the table/view in the database. These will typically match because it's weird to have a table named differently than the object but the capability is there to allow it to be different if necessary. A similar feature exists on attributes where in addition to the attributename there is a columnname attribute that can be different. Out of the box the only time this is used that I'm aware of is the new STARTDATEENTERED (and similar) attributes. There's a long backstory on that one but again it'll almost always match.
Service in database configuration I like to simplify and say it provides a way to sort of group related objects together in Maximo. It's not always perfect as some objects really could go across multiple services. There's some functionality here such as when you enable SQL logging you can enable it on a service which will include all objects underneath that service.
In addition to the grouping aspect, each service has its own java class that provides functionality potentially needed by those objects. For example, the AssetService provides a method to move an asset which could be called in a few different places. The service can also expose these methods as a web method to make it available to be called from a REST API for example.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Fri September 10, 2021 03:11 PM
From: User1971
Subject: DB config: Object vs. entity
MAM 7.6.1.2:
In the Database Configuration application:
What's the difference between these fields?
- Object
- Service
- Entity
Thanks.
#Maximo
#AssetandFacilitiesManagement