Skip to main content

Up to App10, ‘PL/SQL Methods Webservices’ was an easy way to expose PL/SQL Methods for inbound  synchronous messaging in form of SOAP webservices:

https://docs.ifs.com/techdocs/foundation1/050_development/024_integration/020_webservices/020_plsql_methods_webservices/default.htm

No BizAPI, minimal modeling, and it worked and there was a proper WSDL available for them.

 

It seems it is not available any more in IFS Cloud.

I would like to know what is the closest replacement for them.
We want as little changes in the interface as possible, keeping SOAP, not switching to REST.

Might this one (Routing Addresses of PL/SQL type) be part of the solution?:
https://docs.ifs.com/techdocs/23r1/060_development/024_integration/015_connect/025_plsql_methods/

 

What is the easiest way to achieve this?

WSDL is necessary for the 3rd party to use it.

 

Thanks in advance for suggestions.

 

You can still route incoming XML messages to a PL/SQL method. No change between IFS Applications 10 and IFS Cloud. Used it several times and still works fine.

(WSDL was also not available in Apps 10 if you just implemented the interface via PL/SQL method.)

Best regards, Heinz

You can still route incoming XML messages to a PL/SQL method. No change between IFS Applications 10 and IFS Cloud. Used it several times and still works fine.

Best regards, Heinz

Perhaps we do not mean the same thing, I am talking about a SOAP webservice which expects a response. Does your solution cover that too?

Sure it does. The PL/SQL method still must return a CLOB. That’s the synchronous response.

 

Best regards, Heinz

Sure it does. The PL/SQL method still must return a CLOB. That’s the synchronous response.

 

Best regards, Heinz

That is interesting, can you please give me more info on that, a screenshot maybe, how the routing is set up?

No difference in routing to Apps 10. Just create a routing address with type PL/SQL and then use this address in a inbound routing rule. Choose no queue (as it should be synchronous) and use a content based routing (e. g. check for existence of a special node). 

 

Best regards, Heinz

No difference in routing to Apps 10. Just create a routing address with type PL/SQL and then use this address in a inbound routing rule. Choose no queue (as it should be synchronous) and use a content based routing (e. g. check for existence of a special node). 

 

Best regards, Heinz

That sounds good, thanks!
In the meantime I found what the WSDL looked like in App9:
http://<host>:<port>/ifssvc/<Service Name here>?wsdl

Like this:
 



So it made me realize why you said there was no WSDL in App10 (or App9), because PL/SQL Methods Webservices is different thing (https://docs.ifs.com/techdocs/foundation1/050_development/024_integration/020_webservices/020_plsql_methods_webservices/default.htm).
It required a bit of modeling, not only setting up routing.
And it produced a WSDL too.

 

Anyway, your solution would be good too if there was a WSDL attached to it.
Otherwise I would feel embarassed to tell the 3rd party:
“Sorry guys, no WSDL”, because that is a necesary accessory of a SOAP interface, I think.

So the question is still alive.
Anyone knows a good replacement in Cloud for App10 feature ‘PL/SQL Methods Webservices’ with a WSDL?


So it made me realize why you said there was no WSDL in App10 (or App9), because PL/SQL Methods Webservices is different thing (https://docs.ifs.com/techdocs/foundation1/050_development/024_integration/020_webservices/020_plsql_methods_webservices/default.htm).
It required a bit of modeling, not only setting up routing.
And it produced a WSDL too.

 

It was not the PL/SQL method that generated a WSDL. And you will never be able to generate a WSDL file from the PL/SQL code.

The WSDL came from the model. But you won’t have such a model in IFS Cloud.

 

So, if it’s essential to have a WSDL file, I see 2 options:

  • Create the WSDL file manually in any text editor
  • Use any Apps 10 environment where you can create the model, generate the WSDL file and than just slightly modify it in a text editor.

 

Best regards, Heinz


So it made me realize why you said there was no WSDL in App10 (or App9), because PL/SQL Methods Webservices is different thing (https://docs.ifs.com/techdocs/foundation1/050_development/024_integration/020_webservices/020_plsql_methods_webservices/default.htm).
It required a bit of modeling, not only setting up routing.
And it produced a WSDL too.

 

It was not the PL/SQL method that generated a WSDL. And you will never be able to generate a WSDL file from the PL/SQL code.

The WSDL came from the model. But you won’t have such a model in IFS Cloud.

 

So, if it’s essential to have a WSDL file, I see 2 options:

  • Create the WSDL file manually in any text editor
  • Use any Apps 10 environment where you can create the model, generate the WSDL file and than just slightly modify it in a text editor.

 

Best regards, Heinz

Manual editing is not really the way to go for us (revision tracking over time., etc.). 
So I started to get used to the idea of solving it without a WSDL.
Thanks for your contribution!

Reply


Terms & ConditionsCookie settings