Error in uploading BDC Models (Server name missing from URL in Property wcfmexURL)

Question

Hi,
We are using multiple Dialogue Instances in DUET Enterprise.
Problem: Before we did the Reverse Proxy Configuration for App Servers, Our BDC Models got imported in SharePoint Successfully (Correct WSS Setup and STS Urls) but After doing the Reverse Proxy Configurations, when we regenerated the BDC Models, apparently Server Name is missing from URL of the Propoerty "wcfmexurl".
Below is the Error Text:
[ERROR] The LobSystem (External System) / LobSystemInstance (External System Ins
tance) Property with Name 'WcfMexDocumentUrl' has an invalid value 'https/sap/bc
/srt/wsdl/bndg_CF37C550B825080AE1000000AC1F18FD/soap12/wsdl11/allinone/ws_policy
/document?sap-client=400'.
    Error was encountered at or just before Line: '65' and Position: '20'.
Failed to import model: Role
[ERROR] The LobSystem (External System) / LobSystemInstance (External System Ins
tance) Property with Name 'WcfMexDocumentUrl' has an invalid value 'https/sap/bc
/srt/wsdl/bndg_CE38C550B825080AE1000000AC1F18FD/soap12/wsdl11/allinone/ws_policy
/document?sap-client=400'.
    Error was encountered at or just before Line: '42' and Position: '20'.
Failed to import model: UserRoles

Answer 1

Hi Holger,
Thanks a lot!
This Error is gone after implementing the Note. Now the generated BDC Models have the correct URL for wcfmexURL property.
now we have the Following Error:
[ERROR] Error loading URL 'https://sapbwX.srv.XXX.com/sap/bc/srt/wsdl/bndg_92
38C550B825080AE1000000AC1F18FD/soap12/wsdl11/allinone/ws_policy/document?sap-cli
ent=XXX'. This normally happens when URL does not point to a valid discovery doc
ument, service description, or XSD schema.
    Error was encountered at or just before Line: '48' and Position: '20'.
Failed to import model: Account
For this Error, our SharePoint Administrator is checking below Steps.
1.    1) Open “wcfmexDocumentUrl” URL in the browser and copy all SSL certificates (including Root Certificates) to a file. Then import these certificates in the Trust Relationships section. Then try the import of the BDC Models
2.   
2) 2) Verifying Your server uses a virtual hostname and all the configuration (e.g. SSL certificate) is done for this virtual hostname. Also the URLs that are created and used in the BDC model are Same virtual hostnames, but not the ones from the physical server.
3.  3)Re-verify SAML Authentication type and transport security at SAP.
4) 4) Browse WSDL at SharePoint Server and verify “WSP:Policy”  and in WSDL make sure that it contains an entry:
<sp:RequestSecurityTokenTemplate>
<wst:KeyType>http://docs.oasis-open.org/ws-sx/ws-trust/200512/PublicKey</wst:KeyType>
<wst:TokenType>http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1</wst:TokenType>
</sp:RequestSecurityTokenTemplate>
I will update the Results after these checks!
Thanks,
Saumil