At a client, we are running into the following issue trying to get their jobs all working on an updated, migrated environment (4.2 SP10).
A Real-Time job is called which process the incoming payload data and then triggers a Batch Job for further processing. This Batch Job is triggered through the Run_Batch_Job web services call against the Data Services Job Server environment.
In our new environment, I cannot get that Run_Batch_Job service to work - it immediately errors with “web service not responding”. The Real-Time Service created for this process works fine though - it accepts the payload and triggers the Real Time Job perfectly. It’s the Run_Batch_Job call within that job that fails.
To simplify testing, we are testing this on a single-stack environment - with Tomcat, CMC (IPS) and Job Server running on 1 server and the repository databases and CMS database on a separate SQL Server environment.
However, the SOAPUI tool I can trigger both web services just fine myself so I’m not sure why the Job Server (while running the Real-Time Job) immediately fails when trying to call the Run_Batch_Job web service. I have also tried to change the web service data store address to use http localhost on port 8080 - although we normally have it configured for https using SSL certificates against its FQDN, the latter working just fine in SOAPUI even from remote servers as well. Note that we have also removed the Session ID authentication requirement on the web services as well to eliminate that issue.
Are there any particular privileges required by the job server service account to trigger this web service? Because it immediately fails with a “web service not responding” error I suspect this to be a rights / infrastructure issue rather than something not setup correctly in Data Services especially as I can trigger all these web services fine using SOAPUI?
Any tips on where to look for would be much appreciated!
ErikR 
(BOB member since 2007-01-10)