06-05-2014 08:53 PM
we have script to execute from different locations, but the timings should be 7AM to 7PM(france time). it should run in INDIA at 10:30 AM, where it is not happening like that. it started at 4 AM., in BSM 8.07 GMT offset in edit shedule-->Time zone not working for me.
please help us.
06-05-2014 09:19 PM
Could you tell more details regarding with the issue you are encountering (BSM 8.07 GMT offset in edit shedule-->Time zone not working for me.) ?
Whether you are having data from BPM to BAC or not?
06-05-2014 09:33 PM
we have deployed a script in BSM, BSM is deployed in france. this has to execute from INDIA and Brazil. the script has to trigger at 7AM(France Time). i.e. in INDIA it has to start at 10:30 AM and in Brazil it has to start at 2 AM. but it was not executing like that. in INDIA it was triggering at 4 AM in Brazil 2 PM. so how to set the time zone to run the scripts at our expected time.
we did for INDIA probe "offset GMT +5:30"
for Brazil probe "GMT -3"
in Edit shedule --> Time zone settings.
06-05-2014 11:00 PM
You can set the timezone to run the script as you expected in Edit Schedule button on the Assign Data Collectors page of the Business Process Profile wizard. Select a "predefined frequency and recurrence range" from the drop-down list, or create a "custom frequency and recurrence range".
Refer to "Chapter 3 • Business Process Monitor Administration" Content "Profile Schedules Dialog Box" page 147 "Using End User Management" for details of those options on below:
06-05-2014 11:27 PM
Thanks for your response.
we were using the same, but we are not getting the expected action.
script should start at 7 AM in france and same script should start at 10:30 at INDIA.
we are executing the script form 2 locations FRANCE and INDIA. but from INDIA it is not executing at expected time.
06-06-2014 12:15 AM
Let me know you are using timezone "Data collector time" or "Offset from GMT"?
If it is "Offset from GMT", try with "Data collector time" and checkback with the results.
The other way to have scripts start at specific times is to add custom code to the scripts.
- Make sure the script is running 24 hours for the days you want the script to run.
- Add the code from the attachment the to start of the script.
See the comments in the code (CPT48024_zip) to understand how it works.
When using the custom code it will use the data collector machine time to know when to start. For example, if there are two BPM servers, one on Eastern time and one on Pacific time, the scripts in the Eastern time zone will run 3 hours earlier and stop 3 hours earlier than the scripts on the machine set to Pacific time.
To resolve this create a separate script for each time zone or set all BPM time zones to be on the same.