We have installed the JFROG Repository in the Orchestration Server. We are using separate Server for orchestration and not the Dev Environment and it is On-Premises.
The installation and configuration is completely correct by following the steps from Pega. The Repository is able to connect successfully to Development and QA applications. But Orchestrator to Development Repository Connection is failed due to File path Error.
The issue is with the D_pxGetFile DataPage which will be using the File Path.
"The Artifact Cannot be Read from the Development Repository" in the Diagnosis Pipeline.
But in the Logs the error message is due to the File Path Error.
ERROR austlappwd0201.au.qbe.pri|10.88.39.158 DMReleaseAdmin - Unable to construct artifactory url due to invalid file path
java.net.URISyntaxException: Expected closing bracket for IPv6 address at index 25:
Caused by: org.apache.http.ProtocolException: Target host is not specified
Did all the debugging possible by following the recommended configurations for Repository in pega Help, Collaboration and PDN.
Root cause: Pegasystems Bug
Root cause description: A defect in Pegasystems’ code or rules: The root cause of the issue is in ArtifactoryStorage java class. In 8.2.6 version, new code has been introduced to make the url. In this API, if we send the repository path as hostName along with port number(localhost:8081), then this API will throw error stating reported exception. JAVA URI is not accepting the port number. If there is no portNumber in the URL(which contains only DNS), then the issue wouldn't occur. This API is found in 8.2.6 , 8.4, 8.4.1 ArtifactoryStorage class. This is product bug because, we are allowing to save the url with port number in the ruleform and throwing the error with the above API while deploying the codeset. Requirement would be either it should validate the URL properly in the ruleform to save only DNS URL before we save the rule or allow the port numbers to have in the URL.
Solution type: New Release
Solution description: Install or upgrade to the new release: issue is already addressed in 8.4.2 patch