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)
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:
- Click > > > landing page and specify the PMF Connection Details:
- PMF Servlet <host_server.server_domain>:<port#>\prweb\PRServlet
- PMF SOAP URL <host_server.server_domain>:<port#>\prweb\PRSOAPServlet
- Click and see this error message:
The URL entered is not a valid PRPC SOAP Servlet URL.
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 1.1.1.1|Test.rpega.com|Rule-Connect-SOAP.Data-Project-Task.GetCurrentProject PMSysAdmin - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_
4b10dba45aa4cd1bc2f9eca0744d3db2.step15_circum0(ra_action_invokeaxis2_
4b10dba45aa4cd1bc2f9eca0744d3db2.java:4031)
at com.pegarules.generated.activity.ra_action_invokeaxis2_
4b10dba45aa4cd1bc2f9eca0744d3db2.perform(ra_action_invokeaxis2_
4b10dba45aa4cd1bc2f9eca0744d3db2.java:308)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity
(Executable.java:3265)
at com.pegarules.generated.activity.ra_action_invoke_
5e9e0cecbbfdfa9a2b1306e703ec4af8.step8_circum0(ra_action_invoke_
5e9e0cecbbfdfa9a2b1306e703ec4af8.java:1032)
at com.pegarules.generated.activity.ra_action_invoke_
5e9e0cecbbfdfa9a2b1306e703ec4af8.perform
(ra_action_invoke_5e9e0cecbbfdfa9a2b1306e703ec4af8.java:189)
Caused by: com.pega.apache.axis2.AxisFault:
Transport error: 401 Error: Unauthorized
at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse
(HTTPSender.java:312)
at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost
(HTTPSender.java:200)
at com.pega.apache.axis2.transport.http.HTTPSender.send
(HTTPSender.java:76)
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.
writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.
invoke(CommonsHTTPTransportSender.java:224)
at com.pega.apache.axis2.engine.AxisEngine.send
(AxisEngine.java:440)
at com.pega.apache.axis2.description.OutInAxisOperationClient.send
(OutInAxisOperation.java:402)
at com.pega.apache.axis2.description.OutInAxisOperationClient.
executeImpl(OutInAxisOperation.java:229)
at com.pega.apache.axis2.client.OperationClient.execute
(OperationClient.java:165)
at com.pegarules.generated.activity.ra_action_invokeaxis2_
4b10dba45aa4cd1bc2f9eca0744d3db2.step14_circum0
(ra_action_invokeaxis2_4b10dba45aa4cd1bc2f9eca0744d3db2.java:3928)
Explanation
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.
- Open the WebLogic domain's config.xml file for editing.
- Within the
<security-configuration>element, add the<enforce-valid-basic-auth-credentials>and set the value to false.
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
</security-configuration>
- Start or restart all of the servers in the domain.
Example WebLogic config.xml file
