Calling ReportNet Job Remotely

[nfeather]

Hi all,

I'm new to the site, but was hoping you could help me out with an issue we are currently having with ReportNet 7.

We have an enterprise schedule running jobs on many servers, including a server where we have ReportNet installed.Ã,  What we'd like to do is run our reportnet jobs after the successful completion of our data mart batch processes.Ã,  We have been unable to find a way to do this, and have reached out to Cognos, with little success.Ã,  I was wondering if any of you have any experience with calling a ReportNet job from a scheduling application such as Tivoli or the like.

Thank you!

[Blue]

Have you considered setting a completion status flag in a table and then using Event Studio to create an event based on this flag to execute the reports?

[nfeather]

Unfortunately, we're stuck on CRN 7.  I think Event Studio is in 8, right?

[Blue]

Yes, Event Studio is in the Cognos 8 BI suite.  Its predecessor was NoticeCast.

Did you get Cognos Scheduler with your CRN install?

Perhaps you can execute your CRN jobs from the command line interface.  If so then these commands could be run from the batch file that runs the ETL jobs. 

What ETL tool are you using?  Most ETL tools also allow you to run DOS/shell commands from a task at the end of the ETL job.

And there's allways the SDK if you like programming in Java. :)

[nfeather]

Thanks, Blue.  I guess we'll have to go through SDK.  We use Informatica, but as far as I can tell, there is no way to kick off jobs via a script unless you create it through SDK.  At this point, it looks like all you can do is reports through command line.

Thanks for your help!

[almeids]

Hi, sorry if I'm stating the obvious but have you looked into event-based triggering with sendevent.bat (sample triggering script provided by Cognos)?  You don't need the SDK for this but do need a way to remotely execute the script from whatever machine your enterprise scheduler runs on.  In our case we run a Windows product on the ReportNet server that allows it to accept commands from the Unix server where our scheduler runs.
HTH
Steve

[nfeather]

Steve,

Thanks for your response.  Where can I find sendevent.bat?  Do you have an example where you are calling a job using this?

If so, this would definitely work for us, since we are able to call the .bat files from our scheduler.

Thanks a lot,
Neill

[almeids]

Neill,
   Sorry, I had the wrong script name - it should have been trigger.bat, and it's in the \crn\webapps\Trigger directory.  The script just needs a single argument, a trigger name (whatever you've put in the event name property of one or more reports' run options), though the command line in it has 4 additional parameters.  I'm not sure if there are options or if this allows you to specify additional triggers for a given run.

   One caution, if you use "save as..." in Report Studio to overwrite changes into your production environment, you do need to reenter the event name afterward.

   Now I need to recall who else I've told about "sendevent.bat" and go make some more apologies...

regards,
Steve

[nfeather]

Steve,

No problem on the naming.  We've used this file to automate a report, but not a job.  As I understand it, you can't use this for calling a job.

We have to run this job because we are bursting a report.   Is there a way to do this?

[almeids]

Thus far in my Cognos experience I've managed to avoid bursting, so I'm afraid you've exhausted my limited knowledge on the subject of remote triggering.  Sorry for the dead end, it sounds like you will need the SDK for this one.  Good luck.
Steve