cancel
Showing results for 
Search instead for 
Did you mean: 

FQDN for WDSL

helmut_skolaut3
Active Participant
0 Kudos

Hi all,

I have found SAP Note http://service.sap.com/sap/support/notes/1583506 where you can configure the hostnames of the endpoint URLs to be generated in the WSDL file out of the function "Display WSDL" in the sender agreement of a SOAP Channel (see green boxes below)

I have not found the configuration where the WSDL URL itselfs is configured (see red box):

Any idea where to maintain this?

Thanks

   Helmut

Accepted Solutions (1)

Accepted Solutions (1)

bhavesh_kantilal
Active Contributor
0 Kudos

Have you tried to run the CTC Wizard for the FQDN? Running this CTC Wizard will update all properties to use the FQDN including Exchange Profile, SLD Registration and other HTTP URLs. This should hopefully get the FQDN in place when you say Display WSDL and need the WSDL URL.

http://service.sap.com/sap/support/notes/1320707

Regards

Bhavesh

helmut_skolaut3
Active Participant
0 Kudos

The hint from Praveen is included in Bhavesh's hint, after I did the SLD selfregistration, nothing has changed, nor after the Wizard. I did a reboot afterwards that has done the rest. So I don't know which part was finally responsible.

bhavesh_kantilal
Active Contributor
0 Kudos

Hello Helmut,

Just for sake of other users, the CTC Wizard for FQDN requires a restart of the PI Server and ofcourse, the CTC Wizard also takes care of the SLD Registration HostName.

Regards

Bhavesh

Answers (1)

Answers (1)

former_member182412
Active Contributor
0 Kudos

Hi Helmut,

Did you verify the properties in the SLD as mentioned in the note, is FQDN maintained in URL and SecureURL properties in the SLD??

Regards,

Praveen.

helmut_skolaut3
Active Participant
0 Kudos

Hi Praveen,

yes I did. It's affecting the correct results on the green boxes of picture above. But not affecting any change on the red box.

Regards

   Helmut

former_member182412
Active Contributor
0 Kudos

Hi Helmut,

Maintain these parameters of XPI Service: CPA Cache in NWA as per this note 804124 - HTTP communication with XI Adapter Engine fails


restart the applications "com.sap.aii.af.cpa.app" and "com.sap aii.af.app", or restart the complete J2EE engine. This triggers a new Adapter Engine self-registration


  • "SLD.selfregistration.httpPort"
  • "SLD.selfregistration.httpsPort"
  • "SLD.selfregistration.hostName"

Regards,

Praveen.