| Author |
Message
|
| kittet |
 Posted: Mon Nov 24, 2008 7:02 am Post subject: WebServices dynamic |
 |
|
Novice
Joined: 18 Nov 2008
Posts: 12
|
Here I'm again!
I have a lot of flows that share the same structure but with different webservices calls, I would like to know if there is any chance to create a universal flow and somehow be able to select the correct service configuration. I've read something about promoting properties but the ones i'm interested on, as WSDL file name, are not available for promote.
Any suggestion? can it be done?
thank you! |
|
| Back to top |
|
 |
| ggriffith |
| Posted: Mon Nov 24, 2008 8:40 am Post subject: |
|
|
Acolyte
Joined: 17 Oct 2007
Posts: 67
|
If you just want to dynamically assign the webservice address then set the OutputLocalEnvironment.Destination.HTTP.RequestURL to the required value. You could maybe define a database table to hold the relevant values.
But if each service has different inputs and outputs, I guess things are going to get quite complex. |
|
| Back to top |
|
|
| kittet |
| Posted: Mon Nov 24, 2008 11:49 pm Post subject: |
|
|
Novice
Joined: 18 Nov 2008
Posts: 12
|
| ggriffith wrote: |
| But if each service has different inputs and outputs, I guess things are going to get quite complex. |
That's my case :_(
For each service I do have differents inputs and obviously differents outputs. Any idea? |
|
| Back to top |
|
|
| ggriffith |
| Posted: Tue Nov 25, 2008 2:28 am Post subject: |
|
|
Acolyte
Joined: 17 Oct 2007
Posts: 67
|
Personally I'd keep things simple ( someone else might have to support your work in the future, and it might be me  ), but you know your application better than I do.
Do you really want all your web services directed through a single flow. It might be better to spread the load. |
|
| Back to top |
|
|
| kittet |
| Posted: Tue Nov 25, 2008 8:11 am Post subject: |
|
|
Novice
Joined: 18 Nov 2008
Posts: 12
|
| I'll do it separately and in the simple way, thanks! |
|
| Back to top |
|
|
| Mandeep |
| Posted: Fri Nov 28, 2008 2:07 am Post subject: |
|
|
Apprentice
Joined: 03 May 2004
Posts: 33
|
You would need to implement some kind of registry look up approach, where you can keep your end point information (like webservice URL's) associated with the service ID's like service requestor ID.
You can have a small database table implementation or you can look at the WSSR (Service Registry Repository) kind of soln if your requirements are complex.
Input messages can be all XML and transformations can be all XSLT based. You can keep XSL file names in that lookup table along with endpoint info and invoke the transformations dynamically through XML Transform Node. Message validations if required can be done without creating message sets through the use of support pac IA9A (XML Validator Node).
So I've told you features a generic flow shoudl have, which helps you achieve loose coupling of service requestor and provider. Validation, transformations, URL invocation become all dynamic. |
|
| Back to top |
|
|
|
|
