16. september 2008 00:59Dear Community,
I am using MS Windows Server 2003, and am trying to call the command line job submission command from a perl script.
Whilst the Script works OK from the command line, it fails in an IIS environment, as the 'job.cmd' command can not be called.
I think this is because it is a cmd file that calls cscript to run job.vbs. I think that the cscript.exe command is blocked from IIS as it is in the System/Windows32 directory.
Whilst I understand that this is an IIS issue, it still prevents me from using the cluster in a particular way. Has anyone managed to configure IIS to allow this to work (and not leave a big security hole)?
Windows Server 2008 does not seem to have this problem - job.exe is an executable.
I managed to work around this constraint by writing a C# program that connected to the cluster using ccpapi.dll. I notice that it appears to allow you to submit jobs from machines other than the headnode. Is there any documentation on how to configure the cluster to accept jobs from other machines? I tried to do this from a machine not in the Cluster (or the Active Directory) and I got a System.Security.Authentication.InvalidCredentialException.
17. september 2008 00:50RedaktørSimon,
The recommended way of doing this is almsot certainly what you're already doing; namely using our C+ API. As for how credentials/remote connections work, this should be covered in the SDK documentation.
When submitting from a client machine which is not in AD, the security can be a little wonky; try using the Network Passwords tool in the control panel to set the credentials to use for the connection (these will need to be a domain account with permissions for the cluster).