In our daily Business Objects reports scheduling life, we often use events as a key factor for triggering the BO Reports. Data quality can be obtained by fixing the events as a dependency to a BO Report. If I'm not wrong, almost everyone who uses Business Objects follow this event dependency concept to maintain the quality of data in the reports. What else, we can play with those events??...
I thought of sharing on how well we can utilize the BO events for Load balancing, Data quality and Maintenance activities.
Basically, events are classified into 3 types.
To know more about events, read Page#229 in Admin guide.
Load Balancing:
Rudiments:
Dummy Reports - 3 or 4 Reports*
Schedule Events - 3 or 4 Events*
Priority events can be created to maintain the load balancing on BO servers. By creating these events, the reports will be kicked off based on the criticality. The four dummy reports which we have created will be executed every 1 min* and triggers the corresponding schedule events.
Here, we can name those 4 dummy reports as Priority1_Report, Priority2_Report, Priority3_Report and Priority4_Report.
Name those 4 schedule events as Event_P1, Event_P2, Event_P3 and Event_P4. (Fix the events as a OUT Conditions for corresponding Priority reports)
The Priority events will be fixed as a condition to all the BO Reports based on the start time of the reports. For example,
Event Names | Fixed to the reports |
---|---|
Event_P1 | Scheduled to start between 8 AM -10 AM |
Event_P2 | Scheduled to start between 10:01 AM - 11:30 AM |
Event_P3 | Scheduled to start between 11:31 AM - 1:00 PM |
Event_P4 | Scheduled to start after 1:01 PM |
How these events can be used?
Release the "Priority2_Report" after 30-45 mins* after confirming that there are enough resource available for processing the next set of reports. By this time, most of the P1 reports might have completed.
Maintenance Activities:
I divide this module into 2 segments.
For Maintenance on BO Server, Rudiments:
Dummy Reports - 1 Report
Schedule Events - 1 Event
To avoid report failures or to stop all the BO reports from kicking off, we can have this one dummy report to manage all these actions. The dummy reports which we have created will be executed every 1 min* and triggers the corresponding schedule events.
Here, we can name that 1 dummy report as Allow_All_Reports.
Name the schedule event as Event_AllowAll. (Fix this event as a OUT Conditions for "Allow_All_Reports" reports)
How this event can be used?
Note - If you pause this report by mistake then none of your reports will trigger.
For Maintenance on Data Load Server (DB), Rudiments:
Dummy Reports - 3 or 4 Reports*
Schedule Events - 3 or 4 Events*
To avoid report failures or to stop all the BO reports which are hitting specific database during planned or unplanned maintenance on data load servers (DB), we can have these dummy report to manage all these actions. The dummy reports which we have created will be executed every 1 min* and triggers the corresponding schedule events.
Here, we can name that 3 dummy report based on the DB Names like DB1_Report, DB2_Report and DB3_Report.
Name the schedule event as Event_DB1, Event_DB2 and Event_DB3. (Fix these event as a OUT Conditions for respective DB Event reports)
For example, Consider DB1_Report is scheduled for Oracle DB reports. Then, fix the Event_DB1 as a in-condition for all the reports which are hitting the Oracle Database. Incase of any unplanned maintenance or any issues with the database, we don't have to look for the metadata or identify the list of reports hitting the Oracle DB and pause them manually. All you need to do is, go-ahead and pause the DB1_Report which will in-turn hold all the reports which are hitting the Oracle DB since we have scheduled those reports with DB Event conditions.
Event Name | Reports hitting ... |
---|---|
Event_DB1 | Oracle Database |
Event_DB2 | SQL Database |
Event_DB3 | Teradata |
Data Quality:
The Quality of data in the report can be maintained by fixing any of the 3 events (Custom, Schedule or File events). Based on the ETL jobs which loads the data to the tables used by the reports, we can fix the best event type as a condition to the BO Reports.
While scheduling any reports, plan to fix the below events as a dependency to maintain the quality of data, load balancing and to avoid report failures or to pause \ resume any reports during planned \ unplanned maintenance period.
Event to wait for: Event_AllowAll, <<Priority Event>>, <<Database Event>>, <<Data Load Event>>
Points to be noted:
As these reports are not hitting any DB's, instances will complete in few seconds.
*Based on business requirements.
I welcome the feedback, comments and complements.
Thanks
Vijay Madhav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
10 | |
7 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |