InvokeSoapWS client issue

[active1SM]

I have an assembly line created in V6.1.1 and running on one server in
a cluster. It contacts the web service and gets the requested files.
All is great ! moving over to the TDI -2 system , exact same config
file with the same properties and when I get into the InvokeSoapWS,
Function Call->Before CAll I can see the Soap envelope and it is
exactly like the one that works on the TDI-1 server. But on TDI-2 it
jumps to Default On Error and I got nothing. Looked at the
solution.properties and made sure things are the same. Then moved to
the global.properties and there are differences but they are the fact
that TDI-1 points to it's keyStore/trustStore and TDI-2 looks at it's.
What am I missing and what can I monitor at the port level to make
sure something gets out ? I have talked with the owner of the web
service and from TDI-1 they see a request and data going out. However,
from TDI-2 they never see any activity coming at them ? ideas ?

[flamesnm]

I'd like to start with 'What's TDI-2' ?

[Eddie Hartman]

I assume "TDI-2" is a secondary TDI server (6.1.1)?

In order to use the XML components (like the FC to
invoke ws) you have to create some .jar files. Have
you made these available to the new TDI server?

Also, you could disable your Error Hook and get the
full stack trace in the log output. That would be helpful
to see in sorting this out.

Of course, in the Error Hook you do have the "error"
object, which is an Entry containing Attributes like
"message", "connectorname" and "exception". Just
dumping this to the log will give more to go on:

task.dumpEntry(error);

-Eddie

[flamesnm]

On 4 Dec, 10:58, Eddie Hartman <eddiehart...@gmail.com> wrote:
> I assume "TDI-2" is a secondary TDI server (6.1.1)?

I was scrambling to see whether TDI 7 had been rebranded TDI-2 ??! I
guess Occham's Razor applies here :o)

[Eddie Hartman]

Let's if the time comes, then it gets a cooler name.
Like EDT (electronic duct tape) or BlueGlue :)

-Eddie

[active1SM]

A PMR and response from Lak solved the issue, keytool : had to get a
new cert in the chain, thanks