Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Showing results for 
Search instead for 
Did you mean: 

Executing a procedure

Occasional Visitor

Executing a procedure

hi im new to pl/sql. i have written a procedure and i know it has created correctly but its meant to output a webpage with tables but it doesn't. is this because i havent set up a dad. also could someone give me more information on dads. thanks
James Specht
Trusted Contributor

Re: Executing a procedure

You do need a DAD to show web pages through a browser...but you can test your procedure simply by executing it in an sql window.

SQL> exec my_proc();

If your output is what you expect then you're on the right track.

If you need it I can try and walk you through setting up a DAD. first question would be is do you have Oracle's IAS installed somewhere?
"Everyone can be taught to sculpt: Michelangelo would have had to be taught how not to. So it is with the great programmers."
Honored Contributor

Re: Executing a procedure


Database Access Descriptor (DAD)
The information configured in DADs include username, password, connect-string, document upload path & procedure, file extensions requiring long raw upload, path alias & associated procedure and confirmation on connection pooling and Single Sign-On compatibility.

It essentially have 8 parts that needs to be configured:

A. Database Connectivity Information
This information is used to connect to the database. Depending upon the authentication mode selected below, you may be required to enter a user name and password. For example, when using Single Sign-On authentication for Oracle Portal 3.0, you are required to enter the user name and password for the schema owner of the Oracle Portal instance. For WebDB 2.x which requires the use of Basic authentication, you may leave the user name and password blank, which will require the users to authenticate themselves at runtime. A TNS connect string is required if the gateway is running in a different Oracle Home than the database being connected to. Also, instead of a TNS connect string, a :: combination can be used as well. is the hostname running the database. is the port number the TNS listener is listening on. is the Oracle SID name of the database instance. For example, myhost:1521:ORCL.

B. Authentication Mode
Select the authentication mode to be used for validating access through this DAD. For Oracle Portal 3.0, the use of Single Sign-on authentication is required. For WebDB 2.x, the use of Basic authentication is required. Please consult the documentation for information of the remaining three authentication modes: Global Owa, Custom Owa, and Per Package.

C. Session Cookie
In most cases, the session cookie name should be left blank. A session cookie name must be specified only for Oracle Portal 3.0 instances that need to participate in a distributed Oracle Portal environment. For those Oracle Portal 3.0 nodes you want to seamlessly participate as a federated cluster, please ensure that the session cookie name for all of the participating nodes is the same. Independent Oracle Portal nodes need to use distinct session cookies.

D. Package/Session State Management
This setting determines whether database package/session state is preserved or is reset for each database request. For WebDB 2.x and Oracle Portal 3.0, this parameter must be set to Stateless (Reset Package State), resulting in the package/session state getting reset for each request.

E. Connection Pool Parameters
For maximum performance, keep the gateway's database connection pooling on.

F. Default(Home)Page
This procedure will be called if no procedure name is specified in the URL.

G. Document Access Information
This information is used by the gateway to upload/download documents into the database associated with this Database Access Descriptor. By default, all the documents will be uploaded as BLOB. This default can be over-ridden by specifying comma separated file extenstions in the Long Raw field. A value of '*' in this field will cause all documents to be uploaded as Long Raw. The Document Access Path specifies the virtual path that is used for accessing documents. The Document Access Procedure field specifies the procedure that the gateway invokes to process a document request.

H. Path Aliasing
Provide this information if the application, connected through this gateway, supports mapping of absolute path to a keyword .

Normally, you should use the WEB interface to configure your DAD.
E.g. http://:/pls/admin_/gateway.htm

Rest is very easy.

If you need further information, please let us know.

Best Regards
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)