Hi,

I’m trying to call a WS, using ws consumer end point alias.

In the alias, I mentioned the proxy and keystore(having my org’s private key)

Now, when I’m testing this connector, I’m getting timeout exception.

If I set the SSL key ( in Security > Certificates tab) with the same keystore, the connector is working fine.

Would like to know -

1. why the keystore in ws endpoint alias is not working
2. When will these certificate settings (Security > Certificates) come into picture? Is it not only for incoming requests from clients ?

Attaching the two screen shots(certificates & ws end point alias)

Thank you

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/b05432b19a038c4291e5ae4612d5980f7793a1a5.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/b05432b19a038c4291e5ae4612d5980f7793a1a5.jpeg 2x" data-dominant-color="D4D6CD">

WS alias.JPG547×503 54.2 KB

The port alias of the binder was not in place. So, in the first try its looking for the alias Keystore.
If not present, looking for the keystore in Certificates.

/Naidu