Test Connectivity in Connector Rules
What does the Test Connectivity in a Connector Rule Checks? Help says Conenction connection between PRPC and the Java Class Identified. Well am a bit confused because:
1. When i do not use Secured Service (WS), it passes
2. When i use Secured Service, it fails.
What I thought:
It tries to connect the external system(s) through the Endpoint Provided.
What is Actually happening:
In both cases the connector seems to be working as expected as both the EndPoints (http and https) are working.
So the real question hear is:
What role does this Button (Test Connectivity) Plays
Mainak
am using 6.3 sp1.
Hi Mainak,
If you are already logged-in (that is : authenticated) with PRPC in the Designer Studio - and you use the 'Test Connectivity' button - you should have the option to test with 'current requestor' or (something like - sorry I will need to check later) 'new requestor' or 'new context'
If you use 'current requestor' PRPC sees you are already authenticated and you will then be allowed to run Activities (etc) that have the 'Requires Authentication' ticked.
The 'current requestor' also will bypass any Web Services Login Challenge ....I suspect this might be something to do with the confusion you are seeing here ?
Please do post the versions etc that Arvind asked for - we can perhaps build a simple test in-house to see if we can help out with this.
Thanks,
John
John,
The point is am using a secured url (https) to connect to a service. Now when I do a test connectivity it fails but still it works from my application (ie it can connect to the other app). My question is why is this happening? Ideally my connector should not work if the test connectivity is failing.
On the contrary I have an unsecured url also. When I do the same (Test Connectivity) it is successful.
So has it (the failing of https in Test Connectivity) something got to do with the WS profile?
Note: I am not using any of that as such.
Mainak
Can you private check out "Rule-Connect-SOAP", Activity : "ValidateInfrastructure" and add logging to step 5 (or second java step in the activity) which says "Test connection" in the Description and see at which step is it failing.
Hi Mainak,
It sounds like you are using an HTTP Connector or a REST Connector or a SOAP Connector. Please clarify which one is behaving in this way.
thanks,
- Jeff
Am using HTTP Connector
Is it possible to test a Connector Rule in the absense of an endpoint URL?
No. The Test Connectivity button is testing the connection between Pega and the endpoint.
Hi Mainak,
Can you please let us know the PRPC version you are using?
Its always good practice to provide Pega Product details for better understanding of issue.
Regarding your issue, can you try ading Dynamic System Setting "https/allowAllHostnames" in "Pega-IntegrationEngine" ruleset and setting it to "true"?
With this dynamic system setting, Pega does not check whether alias in the certificate (of the public certificate present in trust store, for WS) matches with the hostname.