If one installs scheduler via the typical setup; they will not or should not have any issues. It is pretty simple. You need a database for your scheduler tables(This is a given and requirement). You need the scheduler service and you need the presentation service. Now, you really don’t need the presentation services if you are just using scheduler to run only bi publisher jobs! But don’t get me started on BI Punisher…err… I mean BI Publisher(This is another post topic entirely). Scheduler is just a service whose sole purpose is.. you guessed it…scheduling jobs. We use the scheduler with presentation server for iBots. iBots are presentation server specific jobs to pre-run long running reports or run reports to be sent via email, dashboards or to other devices. Oracle highly recommends running scheduler service on the same box as presentation server. This is for reasons discussed later and also due to fact that scheduler will more than likely be used solely with presentation server to scheduler iBot jobs via Delivers. Now, don’t get me wrong you could run scheduler on a different box; but, there are more specific configurations needed. For example, lets say you want to run presentation services on box1, bi server and scheduler on box2. This is what needs to be done.
1. Configure you scheduler either via the job manager UI or at the root config file, which is located at OracleBIData\scheduler\config\instanceconfig.xml (NOTICE HOW THIS IS LOCATED WITHIN THE ORACLEBIDATA DIRECTORY. That is because it is presumed to run on the same machine as the presentation services!!!)
You will want to add the tns entry for your scheduler database here along with the userid/password to access scheduler tables. (As seen below)
Here are the contents of the schedulers instanceconfig. As you can see there are lots of entries. I find it best to use the UI in order to not make XML errors! But for those with lots of XML experience its up to you. As for me I can do both;) (In any case please keep note of the settings highlighted in blue. PLEASE TAKE NOTICE OF DATABASE PASSWORD AS IT IS ENCRYPTED THAT’S WHY IT IS GOOD TO USE THE UI TOOL TO CONFIGURE ALSO.)
2. Run job manager to validate the scheduler services is running correctly and can communicate with the scheduler tables. You could do this on any machine with the job manager exe but just make it simple and run on the box it is setup on. In our case box2. If job manager connects fine to our scheduler all is well with the service itself. If you have issues, look in OracleBI\server\log\ for the scheduler.log for specific issues.
3. Now since scheduler is verified and running, we need to configure presentation services for scheduler so that it can talk with the scheduler service and create jobs. First we need to run cryptotools like it says within the infrastructure guide. Cryptotools.exe can be found in “OracleBI\web\bin” dir. This tool is used to enter the username and password for scheduler within the credentialstore.xml located in “OracleBIData\web\config” and to encrypt it, if need be, with passphrase. Scheduler uses the alias of “admin”. Once this is complete you will need to tell presentation services where the scheduler services is and also to find and locate the credentialstore.xml. If schedulerServer is not specified correctly you will get error from delivers when trying to create ibot. Something like service or server can not be found or communication error. (This is not a problem with standard install where sched server is on same machine as presentation server) Also if you get Authentication error when trying to create iBot this is because the credential store and alias is either not setup or not setup right.
Your instanceconfig.xml for presentation services should now look like this after making entries. The entries for this step is highlighted in blue.
tag below and choose a subset set of language tags from the list. Values must be comma separated. –>
tag below and choose a subset set of locale tags from the list. Values must be comma separated. –>
4. One last thing to remember and this is important and is typically overlooked. You need to configure scheduler to communicate with the presentation server. This way when it runs reports via an iBot, it can run them. Scheduler runs iBots through presentation server as that is where the reports themselves live. And then presentation server in turn submits the report to BI Server to fulfill the logical data request like usual. If you setup scheduler on another box other than presentation server you might get the 77030 error when running an ibot job since the default value for this is local:9710.
So thinking about it, it does not make sense to have scheduler on another box as it needs to communicate directly with presentation server. Thus one more network hop to get a job complete. In our example scheduler on box2 needed to communicate to box 1 (presentation server) to run an iBot job. Then box1 (presentation server) need to communicate to box 2(bi server) to run the report. If we kept presentation server and scheduler on box1 then we would eliminate that one network request as it would just be local request.
If you have any ?s or comments please let me know and I will try to answer them.