Full qualified host name not appearing in url within WSDL generated from PI

[Former Member]

Hi

We are on PI711 ( AIX OS ) and are stuck with an issue of the fully qualifed hostname not appearing within WSDL file generated in PI71 for a webservice it exposes using the Integration builder

We changed the host name in exchange profile ( all locations ) from hostname to hostname.companyname.intra and also in the ABAP stack as recommended in all OSS notes.

We use the Integration Directory --> Sender Agreement --> Display WSDL option to generate the WSDL.

Its to be noted that all locations ( including url for WSDL ) have the fully qualified hostname except the url within the WSDL.

Dioes anyone come across this issue/ know which parameters to be updated on the PI server to make the url within the WSDL for the PI webservice to have the fully qualified host name ?

[marksmyth]

Hello

Check note #1583506 FQDN missing from generated WSDL URL in PI Directory. I think this answers the original question in this thread but I'm not sure if you are generating the WSDL from a Sender Agreement in the Directory.

Regards

Mark

[Former Member]

Hi

No you are right..You can use the display wsdl option of Sender Agreement and the consumer can download the wsdl using the link.

Regarding fully qualified hostname, please chekc whether you have maintained FQDN (Fully qualified domain name) in the Exchange profile and RZ10.

Do not forget to restart the system.

Regards

Monika

[Former Member]

Hi Monika

We did change parameters in RZ70 and also all connection properties in exchange profile and restarted the server ( ABAP and JAVA ).

All locations in PI ( exchange profile, RZ70, urls for Integration builder applications ( Ir, ID, RWB )) reflect FQDN including the url in the generate WSDL window. But the SOAP location within the WSDL has the short name and not the FQDN.

The calling application in this case uses the url within the WSDL to make the calls in runtime and hence cannot resolve the short host name within the wsdl.

Do we need to do a full cache refresh after the restart for the changes to reflect in WSDL generation ( from sender agreement ->Display WSDL option )

[helmut_skolaut3]

I have the same question, how can I configure the FQDN in the WSDL that is generated out of http://<host>:<port>/dir/wsdl?p=sa/<guid>;

[Former Member]

HI Karthik,

As Mentioned by Baskar donu2019t use proposed URL .. while creating WSDL in Id.. but instead provide URL in following format and use it in that place and create WSDL.. details about URL format..

the URL format is fix. and it is simple.

http://host:HTTPPort/XISOAPAdapter/MessagingServlet?channel=party:sendersystem:CC_sender

in above URL provide your sender service component name instead of sender system.

and provide SOAP sender communication channel name in place of CC_sender

provide your PI system host and http name in place of host and https and use this..

for more details about URL..

Thanks,

Bhupesh

[agasthuri_doss]

Karthik,

As Gopal mentioned avoid proposed url & try this

http://<hostname:<portno>/XISOAPAdapter/MessageServlet?channel=:<SenderService>:<SenderSOAPCC>;

Cheers

Agasthuri

[baskar_gopalakrishnan2]

have you tried another way of generating WSDL in ID where we specify URL ,namespace and interface manually ?

i.e Tools --> Display WSDL .... and follow the steps..

Note: Dont use proposed URL during this step.

Follow this thread

[Former Member]

Hi

Not sure whether I understand what you folks are suggesting. In PI 711, we are using the url method of specifiying the webservice defintion . The web service consuming client in our case is directly reading the url and picking up the web service definition ( WSDL) based on the url . So, we use Sender Agreement --> Show WSDL option which then generates the url and the WSDL.

We DON'T WANT TO PASS WSDL files across in email .

Not sure whether your method of creating the WSDL ( by setting the url parameters ) will aid us giving out the url for the WSDL.

Please clarify.

[Former Member]

ok do you mean to say you are not providing WSDL file to your sender application? then how they are getting WSDL and how they are consuming the WSDL..

could you explain more about this..and your problem..? because most of the time if you have Web service sender application and if PI is going to provide WSDL then following is the flow..

you generate WSDL file as mentioned above in ID side.. use specific URL format.. and provide URL and WSDL to sender application so that they can consumed that WSDL in their application use the provided specific URL format to hit the PI system.. and send request..

Thanks,

Bhupesh