Hi,

Is RC dependent on WF to start as a service or does the order that they both start not really matter?

If the order matters does anyone know how to create a dependency in Win 2003? I've read the MS doc to do this and it says to go to the registry but I don't see Report Caster as a service in the registry where MS tells me to look.
Even if you have knowledge of Win 2K, it might help so don't be shy.

Thanks,
Greg

From my experience the order doesn't really matter.

I'm surprised my windows 2003 install with 7.6.2 contains a "ReportCaster 76" Service which points to "D:\ibi\ReportCaster76\bin\schbkr.exe"

If you post the MS Link here, I can see if i can find it in my registry.

Several ways:
1) Put it into '.../ibi/apps/baseapp/' which is in the default path (APP PATH) for all MRE and RCaster users. This default user is often named 'EDA',
2) Put it into a directory of your choice inside '.../ibi/apps/' then include that folder in the APP PATH of any user-specific profiles that need to use the application. Also include it into the default user (EDA) if it is to be available to MRE users, and into any RCaster user profiles of users that will be submitting scheduled jobs needing the included objects. You can name this folder inside '.../ibi/apps' whatever you like, but something related to the application would be better. We have a whole series of such libraries inside '.../ibi/apps/', each related to business application and containg all files related thereto, and a 'PUBLIC' folder for things shared by multiple applications.
3) If you're not using APPATH, then include the fully qualified path to the
chosen '.../ibi/apps' location in the EDAPATH variable mentioned in EDASPROF.prf ('.../ibi/srv###/wfs/etc/edasprf.prf').

Sorry folks, my post, above, was intended for the "Includes" topic.

In my experience, the order IS important, but the timing could still throw you off. RC needs to be able to connect to the repository and to WFS to start properly. If you put RC as a dependent task to the WFS, the server requires a few seconds to initialize after it starts. What it really should be is dependent to WFS with a delay of about 5 seconds or so.

To avoid problems, I have multiple windows installs where I set the RC service "Recovery" properties to:
First failure: Restart the Service
Second failure: Restart the Service

If the "Restart service after" property is set to 1 minute, then this is plenty of time for the DB and the WFS to be up and running, without having to create dependent services.

i agree with Toronto.
Server first, then Caster.
And when taking the system down, its just the reverse...take caster down first and then the server.
I had this drilled in to me by the a fabulous CSS rep, Lourdes Perez.
Toronto has a nice idea about tinkering with the timing...