Generating Web Service from PL/SLQL procedures using ODSI

Question

1) Is there a way for us to generate REST based web services from PL/SQL procedures using Oracle data services Integrator? If Yes, Can you please point me to any available documentation
2) I am trying to create a phyiscal data source based on PL/SQL procedures in the hope of turning these data sources into web services. I created a JDBC connection in web logic server console and am trying to view the packages under APPS but ODSI always crashes after selecting APPS. Is there a way to resolve this?
Thanks
Bhanu

Answer 1

Hi..
We came accross this problem a while back (I think it was us that the patch was created for). The patch was released under CR369707.
Additionally it took us a while to figure out how to use it correctly.. Here's the info for it from a mail i receievd from our support contact..
Here is more information from engineering on the patch:
This is patch for filtering Stored Procedures in the New Physical Data Service Wizard. It is a partial fix to the problem. It just does filtering - it still retrieves all the jdbc metadata for everything that matches the filter. Ideally, the wizard would let you explore the stored procedures - retrieving the name only - and once you selected a stored procedure, it would retrieve the argument types (which is the expensive part).
Copy these two files to a safe place
<bea_home>\<aldsp_home>\eclipse-plugins\dsp\eclipse\plugins\com.bea.dsp.ide.external_10.3.0\dsp-ide-ldshredder.jar
<bea_home>\<aldsp_home>\eclipse-plugins\dsp\eclipse\plugins\com.bea.dsp.ide.import_metadata_10.3.0.jar
Replace the files with the ones provided in the patch (which I sent you be eMail recently).
Creating Relational Database Physical Data Services -> Stored Procedures will be affected as follows :
The Search field used to represent a pattern for the stored procedures only, and this patterns were applied against every schema visible to ALDSP. The patch allows you to also specify a list of catalogue patterns (useful only when applicable), a list of schema patterns and a list of procedure name patterns. These lists are separated by the pipe symbol, and the lists themselves are command-separated. The catalogue and schema patterns are regular expressions, the procedure pattern is for a database 'like' clause. For, Oracle, the catalogue patterns are not applicable.
Example:
|ODM1,ODM2|B% // look in schemas containing the strings ODM1 or ODM2 for procedures that start with B
// possible results would be MY_ODM1.BUILDER, ODM2.BOTTOM
|^ODM$|B%D // look in the ODM schema for procedures that start with B and end with D.
Also - if there is a search string in the Search box, that search string will be applied to the schema when you click on the + to expand it in the Tree.
Note that once a schema has been 'explored' - either by a search, or by expanding it in the tree, further searches will not update it's children. You would need to quit the wizard and restart.
Once you get the patch if you have issues let me know..