Hi

I can't tell you exactly how to do such a thing, because of the monitoring and the automatic database connexion, but the solution to keep a service running, detached from the client, is to run it asynchronously (/async).

We've use this for our interoperability module (which is by nature detached from any client), and it works quit well since 2000. But the key point is to monitor correctly those asynchronous services, to be able to stop or restart them.

Best regards,
Richard

We have the same functionnality.

Our implementation is :

On Windows :

- Create a service

   Command : uniface.exe /asn=... /ini=... Startupshell myService

   You must specify all variables for your service (PATH,...)

   Those informations are in the registry

- Launch service

- Create a schedule task who check each minutes if the process uniface.exe of the user UserWhoLaunchService

    If the number of process doen't correct, stop service, move log ($putmess_logfile) start service

On Unix

  We must think about the implementation, because, it's our future target.

Regards.

Running a service using uniface.exe will have the 'bad' habit of using up a user licence for that service.

I tried a number of things, and in the end, exposed my service component as a web service (was using web services anyway, so not a big deal).

I then wrote a windows service in .NET and use this to call the operation in my web service every minute. The service is set to Automatic start, so this should take care of the rebooting issue.

Thanks for the tips.

Martin

Great that you have a solution.

Maybe take a look at the urouter monitor API. I've used this in combination with post message to achieve what you are after. It is similar to using regular /asyn activation, however this technique can open numerous other possibilities too.

Hi

Have you more materials for this usage of the monitor API with postmessage ? I'm interested, but the first time I tried, the API crashed while getting the client list, and I'm not sure about the postmessage thing : you mean the messageing API or the proc postmessage (which really is a sendmessage) ?

Best Regards,
Richard