Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Gladson Soans (GladsonS3738) Commonwealth Bank of Australia Devops Engineer
Commonwealth Bank of Australia
AU
GladsonS3738 Member since 2017 9 posts
Commonwealth Bank of Australia
Posted: Feb 11, 2018
Last activity: Feb 15, 2018
Posted: 11 Feb 2018 5:53 EST
Last activity: 15 Feb 2018 13:25 EST
Closed
Solved

Getting error while generating build in Devops pipeline

Hi

I'm getting below error when generating build for devops pipleine. Its publishing successfully to the artifactory but the pycallbackurl is invalid. How can I update the pycallbackurl from Pega?

2018-02-11 21:49:22,261 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ EventFW:01.01.01] (apper.Pega_Int_Pipeline.Action) INFO deploymentmanager - Task execution completed for task : publish
Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"EventFW"
,"pyApplicationVersion":"01.01.01"
,"pyBuildArtifactName":"EventFW_010101_8.zip"
,"pyCallBackURL":"https://localhost:443/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask"
,"pyDoPackage":"true"
,"pyID":"PEGA-PIPELINE-CD EVE-14"
,"pyProductName":"EventFWProductRule"
,"pyProductVersion":"01-01-01"
,"pyRepositoryName":"DevArtifactory"
,"pyStatusMessage":"Artifact is successfully published to the repository."
,"pyStatusValue":"SUCCESS"
,"pyBuildArtifact":{
"pxObjClass":"Data-Artifact"
,"pyArchiveName":"EventFW_010101_8.zip"
,"pyArtifactName":"EventFW"
,"pyName":"EventFW_010101_8.zip"
,"pySize":"13848301"
,"pyTargetLocation":"/application/EventFW_01.01.01/EventFW_010101_8/EventFW_010101_8.zip"
,"pyType":"application"
}
}

Show More

Hi

I'm getting below error when generating build for devops pipleine. Its publishing successfully to the artifactory but the pycallbackurl is invalid. How can I update the pycallbackurl from Pega?

2018-02-11 21:49:22,261 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ EventFW:01.01.01] (apper.Pega_Int_Pipeline.Action) INFO deploymentmanager - Task execution completed for task : publish
Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"EventFW"
,"pyApplicationVersion":"01.01.01"
,"pyBuildArtifactName":"EventFW_010101_8.zip"
,"pyCallBackURL":"https://localhost:443/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask"
,"pyDoPackage":"true"
,"pyID":"PEGA-PIPELINE-CD EVE-14"
,"pyProductName":"EventFWProductRule"
,"pyProductVersion":"01-01-01"
,"pyRepositoryName":"DevArtifactory"
,"pyStatusMessage":"Artifact is successfully published to the repository."
,"pyStatusValue":"SUCCESS"
,"pyBuildArtifact":{
"pxObjClass":"Data-Artifact"
,"pyArchiveName":"EventFW_010101_8.zip"
,"pyArtifactName":"EventFW"
,"pyName":"EventFW_010101_8.zip"
,"pySize":"13848301"
,"pyTargetLocation":"/application/EventFW_01.01.01/EventFW_010101_8/EventFW_010101_8.zip"
,"pyType":"application"
}
}

2018-02-11 21:49:24,494 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ EventFW:01.01.01] (apper.Pega_Int_Pipeline.Action) ERROR deploymentmanager - Problem occurred while fetching log contents of CICD task.null
java.lang.NullPointerException
at com.pega.pegarules.priv.CICDLogHelper.getAppenderContent(CICDLogHelper.java:49) ~[prpublic.jar:?]
at com.pega.pegarules.priv.CICDLogHelper.getAppenderContentAndRemove(CICDLogHelper.java:59) ~[prpublic.jar:?]
at com.pegarules.generated.activity.ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.step11_circum0(ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.java:880) ~[?:?]
at com.pegarules.generated.activity.ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.perform(ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.java:264) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3586) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:646) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(ThreadRunner.java:572) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(PRThreadImpl.java:473) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(QueueProcessor.java:297) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:362) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:1055) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1304) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1052) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:934) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:761) ~[prprivate.jar:?]
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991) ~[prjsr166java6-3.0.jar:?]
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532) ~[prjsr166java6-3.0.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]
2018-02-11 21:49:25,234 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ EventFW:01.01.01] ( connect.rest.RESTConnector) ERROR Rule-Connect-REST.Pega-Int-Pipeline.pzPostTaskStatus deploymentmanager - HTTP connect execution failure: org.apache.http.conn.HttpHostConnectException: Connect to localhost:443 [localhost/ Proprietary information hidden] failed: Connection refused
java.lang.RuntimeException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:443 [localhost/ Proprietary information hidden] failed: Connection refused
at com.pega.pegarules.integration.engine.internal.client.rest.ComponentsRESTClient.invokeRESTClient(ComponentsRESTClient.java:206) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.invokeREST(RESTConnector.java:1462) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.executeRequest(RESTConnector.java:1876) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.perform(RESTConnector.java:338) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.invoke(RESTConnector.java:184) ~[printegrint.jar:?]
at com.pega.pegarules.integration.config.internal.connect.PRConnectorFactory.invokeConnector(PRConnectorFactory.java:82) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.util.PRConnectorUtilsPriv.invokeConnector(PRConnectorUtilsPriv.java:168) ~[printegrint.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.invokeConnector(Executable.java:11317) ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.step1_circum0(ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.java:164) ~[?:?]
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.perform(ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.java:70) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3586) ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_invoke_adde9d91fce1256a22f0ed90194a2db1.step7_circum0(ra_action_invoke_adde9d91fce1256a22f0ed90194a2db1.java:1001) ~[?:?]
at com.pegarules.generated.activity.ra_action_invoke_adde9d91fce1256a22f0ed90194a2db1.perform(ra_action_invoke_adde9d91fce1256a22f0ed90194a2db1.java:173) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3586) ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_pzsendtaskstatus_3b04054e056e09a766344cb3aa28613c.step2_circum0(ra_action_pzsendtaskstatus_3b04054e056e09a766344cb3aa28613c.java:317) ~[?:?]
at com.pegarules.generated.activity.ra_action_pzsendtaskstatus_3b04054e056e09a766344cb3aa28613c.perform(ra_action_pzsendtaskstatus_3b04054e056e09a766344cb3aa28613c.java:88) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3586) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10770) ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.step12_circum0(ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.java:935) ~[?:?]
at com.pegarules.generated.activity.ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.perform(ra_action_pzcreatetaskwrapper_0bece77cd6628dd684d383f4ac46d83f.java:284) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3586) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:646) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(ThreadRunner.java:572) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(PRThreadImpl.java:473) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(QueueProcessor.java:297) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:362) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:1055) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1304) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1052) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:934) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:761) ~[prprivate.jar:?]
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991) ~[prjsr166java6-3.0.jar:?]
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532) ~[prjsr166java6-3.0.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:443 [localhost/ Proprietary information hidden] failed: Connection refused
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:158) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.conn.BasicHttpClientConnectionManager.connect(BasicHttpClientConnectionManager.java:338) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71) ~[httpclient-4.5.2.jar:?]
at com.pega.pegarules.integration.engine.internal.client.rest.ComponentsRESTClient.invokeRESTClient(ComponentsRESTClient.java:196) ~[printegrint.jar:?]
... 33 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_60]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_60]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_60]
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_60]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_60]
at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_60]
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.conn.BasicHttpClientConnectionManager.connect(BasicHttpClientConnectionManager.java:338) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[httpclient-4.5.2.jar:?]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71) ~[httpclient-4.5.2.jar:?]
at com.pega.pegarules.integration.engine.internal.client.rest.ComponentsRESTClient.invokeRESTClient(ComponentsRESTClient.java:196) ~[printegrint.jar:?]
... 33 more


Show Less
To see attachments, please log in.
DevOps

Accepted Solution

Posted: 6 years ago
Updated: 6 years ago
Posted: 14 Feb 2018 22:21 EST
Updated: 15 Feb 2018 13:25 EST
Jithamanyu Manne (mannj1) PEGA Principal Software Engineer
Pegasystems Inc.
IN

Hi,

pycallbackurl will always be the url of the ReleaseManagement system when you created the pipeline.

When creating the pipeline you must be using a https ReleaseManagement system,that is the reason you are seeing https in the pycallbackurl

 ex: https://xx.xx.xx.xx:443/prweb

If you dont want that then please login to a http ReleaseManagement system when creating the pipeline

ex: http://xx.xx.xx.xx:443/prweb

To see attachments, please log in.
Posted: 6 years ago
Posted: 13 Feb 2018 1:03 EST
Jithamanyu Manne (mannj1) PEGA Principal Software Engineer
Pegasystems Inc.
IN

Hi,

Can you delete this pipeline and recreate it again?

If yes while recreating the pipeline make sure that you access the Release Manager by giving the IP address in the URL rather than localhost.

ex: http:// Proprietary information hidden:443/prweb

This should fix the problem

To see attachments, please log in.
Posted: 6 years ago
Posted: 13 Feb 2018 3:52 EST
Gladson Soans (GladsonS3738) Commonwealth Bank of Australia Devops Engineer
Commonwealth Bank of Australia
AU

Hi,

Its picking up the same url after recreating the pipeline

"pyCallBackURL":"https://localhost:443/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask"

To see attachments, please log in.
Posted: 6 years ago
Updated: 6 years ago
Posted: 14 Feb 2018 0:57 EST
Updated: 14 Feb 2018 4:23 EST
Gladson Soans (GladsonS3738) Commonwealth Bank of Australia Devops Engineer
Commonwealth Bank of Australia
AU

Hi,

Yes using ipaddress seems to have resolved the connection refused exception . I'm now getting error related to SSL. How can I disable SSL call ?

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Helvetica} span.s1 {font-kerning: none}

Show More

Hi,

Yes using ipaddress seems to have resolved the connection refused exception . I'm now getting error related to SSL. How can I disable SSL call ?

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Helvetica} span.s1 {font-kerning: none}

018-02-14 16:46:54,382 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [sFoundation:01.01.01] (    connect.rest.RESTConnector) ERROR Rule-Connect-REST.Pega-Int-Pipeline.pzPostTaskStatus  - Rule-Connect-REST: https:// Proprietary information hidden:443/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask - Caught unhandled exception: java.lang.RuntimeException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target - javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
java.lang.RuntimeException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    at com.pega.pegarules.integration.engine.internal.client.rest.ComponentsRESTClient.invokeRESTClient(ComponentsRESTClient.java:206) ~[printegrint.jar:?]
    at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.invokeREST(RESTConnector.java:1462) ~[printegrint.jar:?]
    at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.executeRequest(RESTConnector.java:1876) ~[printegrint.jar:?]
    at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.perform(RESTConnector.java:338) ~[printegrint.jar:?]
    at com.pega.pegarules.integration.engine.internal.connect.rest.RESTConnector.invoke(RESTConnector.java:184) ~[printegrint.jar:?]
    at com.pega.pegarules.integration.config.internal.connect.PRConnectorFactory.invokeConnector(PRConnectorFactory.java:82) ~[printegrint.jar:?]
    at com.pega.pegarules.integration.engine.internal.util.PRConnectorUtilsPriv.invokeConnector(PRConnectorUtilsPriv.java:168) ~[printegrint.jar:?]
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeConnector(Executable.java:11317) ~[prprivate.jar:?]
    at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.step1_circum0(ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.java:164) ~[?:?]
    at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.perform(ra_action_pyinvokerestconnector_b52c161733c13a95270b391bad11b998.java:70) ~[?:?]


Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 14 Feb 2018 2:24 EST
Mudit Sharma (sharm) PEGA Technical Lead
Pegasystems Inc.
IN

hi Gladson,

  You seem to be using an https system, but certificates are probably not properly installed. You may find helpful information at http://magicmonster.com/kb/prg/java/ssl/pkix_path_building_failed.html.

  If you want to use an https make then make sure to keep "Require TLS/SSL for REST services in this package" checked in CICD and API service package.

  You would also need to ensure that your server has rights to send a request to itself.

   Please work with your IT team to apply these resolutions.

Thanks,

Mudit Sharma

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 14 Feb 2018 5:29 EST
Gladson Soans (GladsonS3738) Commonwealth Bank of Australia Devops Engineer
Commonwealth Bank of Australia
AU

Hi Mudit,

I'm getting the same issue when using  http system as well. Can you please explain what exactly happens when this APi is called?  https:// Proprietary information hidden:443/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask

Why do I need a certificate if I'm calling Pega itself?

To see attachments, please log in.
Posted: 6 years ago
Posted: 14 Feb 2018 5:53 EST
Mudit Sharma (sharm) PEGA Technical Lead
Pegasystems Inc.
IN

hi Gladson,

  Please post the error message you get when working on an HTTP system.  Orchestrator and candidate systems interact with each other using REST calls. In your case, as a single system is used across the pipeline, the system will make calls to itself. 

   Please work with your IT to ensure that your system is enabled to get requests from itself. Most of time it is not enabled by default.

Thanks,

Mudit Sharma

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 14 Feb 2018 18:29 EST
Gladson Soans (GladsonS3738) Commonwealth Bank of Australia Devops Engineer
Commonwealth Bank of Australia
AU

Hi Mudit,

The logs for HTTP system is the same i.e. its still asking for valid certificate. I can get this certificate sorted out but how do I ensure that pycallbackurl is using http and not https ?

Regards,

Gladson

To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Updated: 6 years ago
Posted: 14 Feb 2018 22:21 EST
Updated: 15 Feb 2018 13:25 EST
Jithamanyu Manne (mannj1) PEGA Principal Software Engineer
Pegasystems Inc.
IN

Hi,

pycallbackurl will always be the url of the ReleaseManagement system when you created the pipeline.

When creating the pipeline you must be using a https ReleaseManagement system,that is the reason you are seeing https in the pycallbackurl

 ex: https://xx.xx.xx.xx:443/prweb

If you dont want that then please login to a http ReleaseManagement system when creating the pipeline

ex: http://xx.xx.xx.xx:443/prweb

To see attachments, please log in.
Posted: 6 years ago
Posted: 14 Feb 2018 23:34 EST
Gladson Soans (GladsonS3738) Commonwealth Bank of Australia Devops Engineer
Commonwealth Bank of Australia
AU

Thanks for the response guys! I got the certificate issue fixed and able to get pycallback url in http as well

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice