And what is the problem if InDesignServerService just launch InDesignServer.exe?
The problem is that when I run a script by ExtendScript Toolkit, it says it's going to start InDesign Server. Which gives me the idea that it is'nt really up and running.
I don't really know if this is a feature or a bug but this is the normal behaviour (since the CS3 release). I just tried on every of my development boxes (CS3, CS4, CS5 and CS 5.5)
The only way to target InDesignServer from the EST is to run it from the command line (without any option, this is obvious)
PS: I am BTW sure the server is running and listening to the specified port
Out of the box, ESTK only knows about the default configuration/port.
Sometimes you can connect to other instances, by using an application specifier extended with the configuration name. On different Mac OSX servers I had varying success with that approach - more recent machines have no problems at all, while older installations with 10.5 won't connect (need not be interrelated). I am glad to have no Windows machines in that project, so I can't tell whether it works there the same way.
For example, for a server launched with SOAP port 12345, the specifier would be
You would then address that instance by a #target line within your starting jsx.
If recognized, the server is added to the application dropdown of ESTK.
Thank you Dirk! This is something I was missing Best, Luca
I am sorry, I only mentioned running from estk because this gives a different result in task manager than when trying to autostart the server from indesignserverservice.
We are making a transfer form Mac server to Windows 2008, and things like daemon we already use work different on Windows.