How will you pass the endpoint url if the ext system is down,in Connect Rest wizard?As usually we pass a url in the wizard at the time of creation of connect rest now if this ext system is down how can we pass then?How will we get the url in that case then?
Generally, we get the URL details beforehand even if the system is not yet ready. Give the initially agreed URL here, and in further steps give the JSON file for input and output data modelling. Later, once the system is ready, we can make changes accordingly to the generated rules.
Is is real implementation question or question from interview’s bank of questions? If the latter please let others now about it in the post.
Hi @Kamil_Janeczek no this is what i am implementing,so basically i am creating a connect rest via wizard but the ext system is down so i dont have the endpoint url,my development is stuck
Not sure if I follow. System can be down but you will still can know its URL. Anyhow as already mentioned this is not a blocker, provide any URL and later you can update it
Ideally, you can still proceed with configuring the Connect REST wizard even if the external system is down. However, when you reach step 3 (data model for response mapping), Pega may throw an error because it cannot get a live response. In that case, you can manually attach a sample response JSON to define the response data model and continue with the configuration. This allows you to complete the Connect REST setup without depending on the external system being available.
Even if the external system is down, you can still create the Connect REST rule.
The URL is usually obtained from the API documentation or shared by the external system team beforehand.
I believe, The availability of the external system is not mandatory for creating the rule. It only affects runtime testing/invocation, not the rule creation itself.
I agree with other members of forum that you don’t need the external service to be available when you start developing the connector in Pega. In general practice, the service contract should be defined first between the systems. once this is confirmed, you can use it with sample payload to build your connector. Make sure you have the entire definition.
In addition to that, do consider if there are any API gateway requirement between the provider and consumer. This can introduce changes to the API contract.
To add on, you can use simulators to even test the functionalities even if the external service is not ready yet.
Thanks.
Hi @Kamil_Janeczek so even if say i am giving the URL as a GRS instead of hardcoding also so i can still continue with the same url?
Hi @RameshSangili yes I do have the request and response payload with me so will use that.Thanks
yes, definitely