Hi Dojo,
I have some questions related to the SRM virtual platform functionality which aren’t addressed in SRM : Booking manager – Virtual Platform setting
In Service and Resource Management Concepts it states that this is a logical collection of resource pools. But what does this mean exactly?
Sometimes I see that the name of the resource pool starts with the name of the virtual platform. But does this mean that a resource in a pool that starts with the name of virtual platform A can’t be used in a booking manager configured with virtual platform B?
Hi Jens,
A resource can belong to multiple pools, so in you example if a resource needs to be used in both booking managers you should have it in two resource pools, each one starting with the virtual platform that is defined in the respective booking manager.
Yes, it’s always advised to have a virtual platform set per booking manager
This is explained in more detail here: https://docs.dataminer.services/user-guide/Standard_Apps/SRM/srm_concepts/srm_instantiations.html#virtual-platform
I’ll add a link on the page mentioned in the question to make it easier to find this info.
Related to “A booking application is always linked to a specific virtual platform. As a result, only resource pools and service definitions that are linked to that specific virtual platform will be available for bookings created with that booking application.”: May I assume that this only counts when using the scripts provided by the framework? In other words, will I be able to book a resource from another virtual platform resource pool with a silent script?
Yes that will work, but goes against the virtual platform concept.
Hi Jorge, is this also needed when working with Resource Scheduling or Resource Orchestration and custom scripts are used for creating new bookings?