HowToPega: Why endpoint URL in connectors is prefixed with = at times

Case Management

Keystore and Truststore

Troubleshooting

Global Resource Setting(GRS)

Cross Origin Resource Sharing (CORS)

Database Normalization

Interview Questions

F12-BrowserDevTool

Request Article

Contribute Article

Saturday, January 28, 2017

Why endpoint URL in connectors is prefixed with = at times

Why endpoint URL in connectors is prefixed with = at times

No comments:

Post a Comment

Newer Post Older Post Home

Subscribe to: Post Comments (Atom)

About Author

My Certifications

PCLSA

Pega Certfied Lead System Architect

PCSSA

Pega Certified Senior Sys Architect

PCSA

Pega Certified System Architect

PCMC

Pega Certified Marketing Consultant

PCDC

Pega Certified Decisioning Consultant

PCDS

Pega Certified Data Scientist

Authentication Series

SAML SSO Authentication Part 1

SAML SSO Authentication Part 2

SAML SSO with Mashup use-case

Open ID Connect SSO with Pega

Pega Basic Authentication

Integration Series

SOAP Service Endpoint and WSDL

Invoking SOAP Service from POSTMAN

Invoking SOAP Service from Pega

Global Resource Settings

Trace Connect-SOAP Request and Response

HTTPS/SSL Series

View certificates list in truststore

Import certicate into trust-store

Pega connecting to HTTPS One Way SSL

How to enable SSL/HTTPS in tomcat server

Get new posts by email:

Popular Posts

PRBasic Authentication

Expose REST Service in Pega

Create Application from scratch

Cross Origin Resource Sharing (CORS)

Database Normalization

Calling RUF from other RUF

Set pega property from JavaScript

Advanced Agents performance

Logical AND short circuit

Call activity from Data transform

Serialize or Deserialize using DT

Value population for dropdowns

How to parse JSON to Pega

How to parse JSON which has spaces in its keys

How to view the list of certificates in truststore

Search This Blog

Powered by Blogger.

HowToPega : All rights reserved and the contents are copyrighted to Pavan Kumar Naidu