000032701 - SOAP Connector fails if WSDL namespace contains spaces or special characters in RSA Via Lifecycle and Governance

Document created by RSA Customer Support Employee on Aug 20, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000032701
Applies ToRSA Product Set: RSA Via Lifecycle and Governance (RSA Via L&G)
RSA Version/Condition: 6.9.1
 
Issue

The Test Connection for a SOAP Connector fails with the following error:


Unexpected exception: Could not find service named 
{http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits20Version2C3Dneutral20PublicKeyToken%3Dnull}
RemoteProgramExitsService in wsdl http://test.testla.testfrd.xyz.com:XXXX/RemoteProgramExits.soap?WSDL
CauseThis error will occur if the WSDL namespace contains special characters such as a percent (%) sign or a space. Prior to 6.9.1 P11, the SOAP connector did not parse the namespace URL properly if a special character is used in the WSDL namespace.
Here is one example:
The actual target namespace is http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits%2C%20Version%3D1.0.4671.27345%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Dnull
User-added image

The parsed target namespace is http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits20Version2C3Dneutral20PublicKeyToken%3Dnull.
Unexpected exception: Could not find service named 
{http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits20Version2C3Dneutral20PublicKeyToken%3Dnull}
RemoteProgramExitsService in wsdl http://test.testla.testfrd.xyz.com:XXXX/RemoteProgramExits.soap?WSDL

 
ResolutionThis issue has been been fixed in 6.9.1 Patch 11. 
Workaround
  1. Go to <AFX_HOME>/mule/apps/<AFX_CONNECTOR>.
  2. Open the connector-flow.xml in any text editor.
  3. Locate the namespace that you see in the error and replace it with the original namespace defined in the WSDL definition. In this WSDL, we would be replacing the value of namespace=http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits20Version2C3Dneutral20PublicKeyToken%3Dnull for the configured capability (e. g., 'CreateAccount'  with namespace="http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits%2C%20Version%3D1.0.4671.27345%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Dnull"
  4. Save the file after making changes. In step 3, we replaced the truncated namespace with actual namespace.
  5. Open the mule-config.xml in any text editor. Locate </mule> add a new line after and then save the file.
  6. In the above step, we have performed hot deployment of the connector.
  7. Check that the connector is in a running state. If it is running, then run the command using test capability to verify the workaround.

Attachments

    Outcomes