one more thing...
does someone know, if I could use corbaloc or corbaname to connect to IDS instead of using the IOR file?
something like this:
I get a connection to the service, but I always get a org.omg.CORBA.OBJECT_NOT_EXIST exception because I don't know about the naming service and if it's supported at all.
Again, I would appreciate any information...
Actually I dont have a solution for your Question. I am also looking for a straight forward answer for your question.
There is a workaround for everything in this world. This is what I am thinking,
Once you span a inDesign server instance with Corba support, you get an IOR file. Decode the IOR file and get the PORT address. Open the particular port on the Windows Firewall programatically.
Also maintain a list of Ports used by indesign server in a separate log. Constantly monitor the log for un-used ports to close them.
After much local experimentation and iteration with Adobe tech support, we have a fix for Problem nr. 1: cannot define the port that works in our environment (IDS CS4 running as a service, Windows 2008 Server).
Add this parameter to your server startup command line for each instance of InDesign Server you're running:
<serverIP> is the static IP of the server that is running IDS. Note: The OmniOrb docs imply that you can use the server's domain name here, but that didn't work for us. 127.0.0.1 also did not work. The IP number does work. This might help your Problem nr. 2: wrong IP address in the application IOR if you set it to the IP you want to listen on, but we have no experience with that.
<portNumber> is the port you want IDS (via OmniOrb) to listen on. If you're running multiple instances as we are, each instance should have its own unique port number.
I completely agree that, as an enterprise product, IDS's default behavior of boldly going where no one has gone before in your port space at each restart is not the way to play nice in a firewalled, enterprise environment. This should be documented in Adobe's Introduction to InDesign Server in the command line parameter discussions, it would have saved us a lot of time