Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: PMF SOAP URL Not Valid PRPC SOAP Servlet URL (WebLogic)

Updated on October 2, 2015

As a PRPC administrator trying to integrate Project Management Framework (PMF) 7.1 with Pega 7.x on the WebLogic application server, you see a SOAP Authentication error after taking the following actions:

  1. Click Designer Studio > System > Settings > Project Management landing page and specify the PMF Connection Details:
  2. Click Test Connectivity and see this error message: The URL entered is not a valid PRPC SOAP Servlet URL.

Designer Studio, System Settings, Project Management, PMF Connection Details

Error information

Error on screen

The URL entered is not a valid PRPC SOAP Servlet URL.

Error in log

2014-09-15 09:47:56,772 [fault (self-tuning)'] [TABTHREAD0] [ ] [jectManagement:07.10] ( internal.mgmt.Executable) ERROR||Rule-Connect-SOAP.Data-Project-Task.GetCurrentProject PMSysAdmin - Exception SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_


at com.pegarules.generated.activity.ra_action_invokeaxis2_
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity
at com.pegarules.generated.activity.ra_action_invoke_
at com.pegarules.generated.activity.ra_action_invoke_

Caused by: com.pega.apache.axis2.AxisFault:
Transport error: 401 Error: Unauthorized

at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse
at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost
at com.pega.apache.axis2.transport.http.HTTPSender.send
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.
at com.pega.apache.axis2.engine.AxisEngine.send
at com.pega.apache.axis2.description.OutInAxisOperationClient.send
at com.pega.apache.axis2.description.OutInAxisOperationClient.
at com.pega.apache.axis2.client.OperationClient.execute
at com.pegarules.generated.activity.ra_action_invokeaxis2_


In WebLogic Server 9.2 and later versions, client requests that use HTTP BASIC authentication must pass WebLogic Server authentication, even if access control is not enabled on the target resource. The enforce-valid-basic-auth-credentials flag is set to true by default; this enables the WebLogic Server to perform authentication.

If authentication fails, the WebLogic Server rejects the request because the WebLogic Server does not have knowledge of the user and password.

Clicking Test Connectivity in PMF Connection Details causes the SOAP request to authenticate using the operator ID PM_SOAPOper. This operator ID is the Pega-provided PMF operator ID for use with PMF-PRPC Integration. The WebLogic Server has no knowledge of this operator ID; therefore, it rejects the SOAP request.

Suggested approach

To prevent the SOAP authentication error in PMF 7.1 and PRPC 7.x integration, set the WebLogic Server security configuration for enforcing basic authentication to false.

  1. Open the WebLogic domain's config.xml file for editing.
  2. Within the <security-configuration> element, add the <enforce-valid-basic-auth-credentials> and set the value to false.


  1. Start or restart all of the servers in the domain.

Example WebLogic config.xml file

WebLogic security configuration, enforce valid basic authentication is false

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us