Booking events in DMA are associated with a timestamp and are used to schedule the execution of a script to configure resources. I have the feeling some of the events you're describing are more booking states on our side.
A booking in DMA has 4 events by default:
- Beginning of preroll (START_BOOKING_WITH_PREROLL)
- End of preroll (START)
- Beginning of postroll (STOP)
- End of postroll (START_BOOKING_WITH_POSTROLL)
At each of these events, you can trigger the execution of an automation script ( LSO script - Lifecycle Service Orchestration) to initiate the configuration of resources part of the booking. At the time defined by these events, DMA will automatically launch the LSO script.
If more events are required, Booking Manager allows to define extra. For extra event, you can launch a script to configure resources, under the condition that the events are defined between start time and end time of your booking ( otherwise , you would take the risk to configure resources that are maybe used by other bookings ).
The other 'events' you're indicating are not really defined as events on our side, and not all of them are applicable to our framework to manage bookings. There is a relation with our Booking Life Cycle states :
- Partial : user is busy defining the booking. Each resource being selected by the user can immediately be reserved
- Confirmed: booking is ready to start. All resources are reserved for that booking, only during the timeslot defined by the booking.
- Cancelled: booking is cancelled , resources are released. There is no way to reschedule the booking.
- Service Preroll : after the first event, orchestration has succeeded
- Failed Service Preroll : after the first event, orchestration has failed configuring one or multiple resources
- Service Active: after the second event, orchestration has succeeded
- Failed Service Active: after the second event, orchestration has failed configuring one or multiple resources
- Service PostRoll: after the third event, orchestration has succeeded
- Failed Service PostRoll: after the third event, orchestration has failed configuring one or multiple resources
- Completed : booking is completed. Resources are released
When actions related to booking management fail, you can either launch custom code in case you were triggering the action from within a script.
Or you can also use the Monitoring element to trigger alarms when things go wrong : Configuring SRM alarm monitoring | DataMiner Docs. THen you can use regular Correlation rules to capture alarms and launch custom scripts.
There are many ways to achieve this. To run the subscripts based on reservation events, here are some ways I can think of for now:
1. Update the LSO script to run a particular script based on the state, as the LSO script is responsible for orchestrating bookings according to service state transitions (e.g., Start, Stop, Standby, etc.).
2. In the Booking Manager, under the Data Pages, you can find the Events page, where you can also define the script to be run based on the states, as follows:
Here, you can define the time reference point or timing type at which you want the subscript to be run.
To run based on the alarms related to the services, you can use a Correlation rule to achieve this. Please refer to this link to find more information on how you can configure a Correlation Rule based on your requirements.