Retrieve a WSDL from a deployed service without develoment

A few weeks ago we published a post about how to retrieve a WSDL from a deployed service using the activity Retrieve Resource that we have in our SOAP palette in the TIBCO BW installation, but in the comments of that post, as you can check from here, one of our readers, Quin, who I want to thank publicly again that spent his time sharing his knowledge with us, do a very interesent comment I want to reproduce here, and share with all of you:

Quinn

This can actually be duplicated within the Advanced Tab on the par file configuration using:
bw.platform.services.retreiveresources.Enabled
bw.platform.services.retreiveresources.Hostname
bw.platform.services.retreiveresources.Httpport

without any need for new processes

So, we are going to try what Quinn are suggested and this would be a important approach for you, because you won’t need to do any extra development to have your WSDL available.

We are going to start from the process we discuss in the previous post, because is an appropiated service to do this kind of test. So the first thing we have to do is remove the extra development that we have made in the previous post and leave only the business service, as you can see here:

ORG

So the only thing you have to do is deploy the Enterprise Archive associated with this development, and in the configuration of the delpoyment, you have available the following properties as Quinn commented previously:

configuration

And now, you can reached the WSDL of the process in the following url, as you can see in the following image:

WSDL

Advertisements

8 thoughts on “Retrieve a WSDL from a deployed service without develoment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s