1 2 3 Previous Next 39 Replies Latest reply on Dec 1, 2004 3:23 PM by 433785 Go to original post
      • 30. Re: Using webutil

        What is version of your forms?

        Alexandre E.
        • 31. Re: Using webutil

          I configured the webutil in forms 9DS. Now I want to configure in 9iAS and with DataBase..
          I think I must to make a small change..Right? What?


          Alexandre E.
          • 32. Re: Using webutil
            Thank you for quick reply.

            I am runing developer suite 9.0.2 and webutil version is 1.0.5. I noticed that you run on webutil version 1.0.2, but I could have download only 1.0.5.

            However, I can not immagine that 1.0.2 does and 1.0.5 does not support iDS9.

            • 33. Re: Using webutil
              Hello Alexandre!!

              To access to the database you have to include the following parameter inside the webutil config:


              That's is the easy way, but if you want to be formal you have to define a DAD (Database Access Descriptor)and asociate the bd with the webutil config in that way.
              I found how to define a DAD in the document "How to implement Single Sign-On (SSO) for Oracle Forms 9i / 10g?"
              under the title Oracle Forms Single Sign-On Oracle Internet Directory Configuration.

              Hope its helps!

              • 34. Re: Using webutil

                I don't have idea if webutil 1.05 is supported by iDS9i, but the 1.02 version can be downloaded from


                • 35. Re: Using webutil
                  Hi :

                  Let me thank everybody who responded to my messages specially to Beatriz for sending his document for webutil and also tell you that I could fix my problem,

                  Actually I was using a wrong version/release of webutil. SO everyone who has the problem just check that first

                  • 36. Re: Using webutil
                    Hi Sead,

                    Even I faced this problem, try and download

                    I hope that works

                    • 37. Re: Using webutil
                      I am running iDS 9.0.2 on MS Windows XP and trying to get WU_TEST_105.fmb to work in order to be able to see that the setting I made works fine. It is not the case and I am really having a hard time putting it together.

                      Bellow I described in detail my actions, so if there is anyone who can help, PLEASE DO, I am exhausted in attempts to make it work. Where did I go wrong?

                      1. I unzipped webutil_102.zip to directory: C:\Orant\webutil\

                      2. I created user webutil_db (grant connect, resource)

                      3. Connected as SYSTEM I run dbmslob.sql, utlraw.sql and utlenc.sql

                      4. Grant execute to WEBUTIL_DB on DBMS_LOB, UTL_RAW and UTL_ENC

                      5. Connected as WEBUTIL_DB I run create_webutil_db.sql.

                      6. Connected as SYSTEM I created PUBLIC SYNONYM to WEBUTIL_DB. WEBUTIL_DB package

                      7. Connected as WEBUTIL_DB I granded EXECUTE to <shema> who should use the webutil procedures.

                      8. I placed jacob.jar and jacob.dll into C:\Orant\webutil\lib\ directory.

                      9. I downloaded jdk1.3.1_14 SDK, installed it into C:\jdk1.3.1_14 and performed digital signining to JACOB as described in “readme.html”

                      10. My forms90.conf looks like below:

                      # $Id: forms90.conf,v 1.8 2002/03/01 01:11:53 pkuhn Exp $
                      # Name
                      # forms90.conf
                      # Purpose
                      # Apache mod_oc4j and mod_jserv configuration file for Forms 9i Services.
                      # This file should be included into the Oracle Apache HTTP Listener
                      # configuration file (typically by adding an include statement to the
                      # oracle_apache.conf file)
                      # Remarks
                      # If Forms is to be used with JServ, the jserv.properties file needs editing
                      # to add the "forms90" servlet zone with properties file forms90.properties
                      # Notes
                      # Virtual paths: We use AliasMatch when defining virtual paths for
                      # security reasons (prevents directory browsing).

                      # Virtual path mapping for Forms Java jar and class files (codebase)
                      AliasMatch ^/forms90/java/(..*) "C:\Orant\Forms_Reps9/forms90/java/$1"

                      # Virtual path for JInitiator downloadable executable and download page
                      AliasMatch ^/forms90/jinitiator/(..*) "C:\Orant\Forms_Reps9/jinit/$1"

                      # Virtual path for runform.htm (used to run a form for testing purposes)
                      AliasMatch ^/forms90/html/(..*) "C:\Orant\Forms_Reps9/tools/web90/html/$1"

                      #Virtual path for webutil
                      AliasMatch ^/forms90/webutil/(..*) "c:/Orant/webutil/lib/$1"

                      # Configuration for JServ (if mod_jserv.c is available and not mod_oc4j.c)
                      <IfModule mod_jserv.c>
                      # Only configure for JServ if mod_oc4j is NOT available:
                      <IfModule !mod_oc4j.c>
                      # Virtual path mapping for FormsServlet and ListenerServlet.
                      # Purpose: paths to invoke the servlets should be /forms90/f90servlet
                      # and /forms90/l90servlet respectively.
                      # We map f90servlet to servlet.if90, and l90servlet to servlet.ifl90.
                      # The apJServAction directives (below) will then remap those.
                      AliasMatch ^/forms90/f90servlet(.*) "/servlet.if90"
                      AliasMatch ^/forms90/l90servlet(.*) "/servlet.ifl90"

                      ApJServMount /forms90/servlet /forms90
                      # Let the servlets be called by file extension (e.g /servlet.if90)
                      ApJServAction .if90 /forms90/servlet/f90servlet
                      ApJServAction .ifl90 /forms90/servlet/l90servlet
                      # Prevent access to the Forms Servlets by paths other than
                      # /forms90/f90servlet and /forms90/l90servlet.
                      # 1. Prevent access via the .if90 and .ifl90 file extensions:
                      <LocationMatch ^.*\.if.*90>
                      order deny,allow
                      deny from all
                      # 2. Stop access by class (by paths like
                      # /forms90/servlet/oracle.forms.servlet.FormsServlet)
                      <LocationMatch ^/forms90/servlet/oracle\.forms.*>
                      order deny,allow
                      deny from all

                      # Config. for OC4J
                      <IfModule mod_oc4j.c>
                      Oc4jMount /forms90 OC4J_BI_Forms
                      Oc4jMount /forms90/f90servlet OC4J_BI_Forms
                      Oc4jMount /forms90/f90servlet/* OC4J_BI_Forms
                      Oc4jMount /forms90/l90servlet OC4J_BI_Forms
                      Oc4jMount /forms90/l90servlet/* OC4J_BI_Forms

                      11. My formsweb.cfg looks like below:

                      # $Id: formsweb.cfg,v 1.23 2002/01/25 06:51:41 oraforms Exp $
                      # -------------------------------------------------------
                      # formsweb.cfg - Forms Servlet default configuration file
                      # -------------------------------------------------------
                      # This file defines parameter values used by the FormsServlet (f90servlet)

                      # ********************************
                      # DEFAULT CONFIGURATIONS
                      # ********************************
                      # These are the default settings. Any of them may be overridden in the
                      # Named Configurations section. If they are not overridden, then the
                      # values here will be used.
                      # System Paremeters cannot be overridden in the URL. User Parameters can.

                      # SYSTEM PARAMETERS
                      # -----------------
                      # These have fixed names and give information required by the Forms
                      # Servlet in order to function. They cannot be specified in the URL query
                      # string. But they can be overriden in a named configuration (see below).
                      # Some parameters specify file names: if the full path is not given,
                      # they are assumed to be in the same directory as this file. If a path
                      # is given, then it should be a physical path, not a URL.

                      # baseHTMLjinitiator=basejini.htm
                      # baseHTMLjpi=basejpi.htm
                      # baseHTMLie=baseie.htm



                      # WorkingDirectory defaults to <oracle_home>/forms90 if unset.

                      # The next parameter specifies how to execute the Forms applet under
                      # Microsoft Internet Explorer 5.x. Put IE=native if you want the
                      # Forms applet to run in the browser's native JVM.

                      # USER PARAMETERS
                      # ---------------
                      # These match variables (e.g. %form%) in the baseHTML file. Their values
                      # may be overridden by specifying them in the URL query string
                      # (e.g. "http://myhost.mydomain.com/servlet/f90servlet?form=myform&width=700")
                      # or by overriding them in a specific, named configuration (see below)

                      # 1) Runform arguments:

                      # These settings support running and debugging a form from the Builder:
                      otherparams=debug=%debug% buffer_records=%buffer% debug_messages=%debug_messages% array=%array% query_only=%query_only% quiet=%quiet% render=%render% host=%host% port=%port% record=%record% tracegroup=%tracegroup% log=%log% term=%term%
                      # debug=no
                      # debug_messages=no
                      # array=no
                      # query_only=no
                      # quiet=yes
                      # render=no

                      # 2) HTML page title, attributes for the BODY tag, and HTML to add before and
                      # after the form:
                      pageTitle=Oracle9iAS Forms Services

                      # 3) Values for the Forms applet parameters:


                      # The following archive settings are for
                      # archive_jini - settings for JInitiator
                      # archive_ie - settings for IE native JVM
                      # archive - settings for all other cases (Java Plugin, Appletviewer, etc)


                      # Number of times client should retry if a network failure occurs. Only
                      # change after having read the documentation.

                      # 4) Parameters for JInitiator (used with Windows clients)

                      # Page displayed to Netscape users to allow them to download JInitiator.
                      # If you create your own page, you should set this parameter to point to it.

                      # Parameters related to the version of JInitiator.

                      # 5) Parameters for the Java Plugin (used with non-Windows clients)

                      # Page displayed to users to allow them to download the JPI
                      # (NOTE: you should check this page and possibly change the settings)

                      # Parameters related to the version of the Java Plugin

                      # 6) EM config parameter
                      # Set this to "1" to enable Enterprise Manager to track Forms processes

                      # 6) OID Config parameters (for Single Sign-On)

                      # ********************************
                      # NAMED CONFIGURATIONS
                      # ********************************
                      # You may define your own specific, named configurations (sets of parameters)
                      # by adding special sections as illustrated in the following examples.
                      # Note that you need only specify the parameters you want to change. The
                      # default values (defined above) will be used for all other parameters.
                      # Use of a specific configuration can be requested by including the text
                      # "config=<your_config_name>" in the query string of the URL used to run
                      # a form. For example, to use the sepwin configuration, your could issue
                      # a URL like "http://myhost.mydomain.com/servlet/f90servlet?config=sepwin".

                      # Example 1: configuration to run forms in a separate browser window with
                      # "generic" look and feel (include "config=sepwin" in the URL)

                      # Example 2: configuration affecting users of MicroSoft Internet Explorer 5.x.
                      # Forms applet will run under the browser's native JVM rather than
                      # using Oracle JInitiator.

                      # Example 3: configuration forcing use of the Java Plugin in all cases
                      # (even if the client browser is on Windows)

                      # Example 4: configuration running the Forms ListenerServlet in debug mode
                      # (debug messages will be written to the servlet engine's log file)

                      12. Environmet variables:



                      13. My webutil.cfg looks like:
                      # -------------------------------------------------------
                      # webutil.cfg - WebUtil default configuration file
                      # -------------------------------------------------------
                      # This file provides all of the configuration settings
                      # for webutil. These are divided into the following
                      # sections:
                      # 1. Logging Options
                      # 2. Installation Options
                      # 3. FileUpload and Download Options
                      # 4. Untranslatable Strings
                      # 5. Translatable Strings

                      # 1. Server Side Logging Options for logging errors and log messages
                      # You must set Enabled to true to allow mid tier logging without this
                      # mid tier logging will not take place no matter what PL/SQL or URL
                      # options are supplied to switch it on
                      # Once logging is enabled the other settings come into play
                      # Details
                      # -------
                      # file : Defines the file name and location of the log file.
                      # Note that WebUtil does no log file management you may
                      # need to manually clean this file up from time to time
                      # enabled : Can be TRUE or FALSE
                      # errorsonly : Can be TRUE or FALSE setting to true will ensure that
                      # only errors and not normal informational log messages
                      # are written to the log file
                      # For product use this would normally be set to TRUE
                      # connections: Can be TRUE or FALSE setting to true will cause each connection
                      # from a form using WebUtil to write into the log as it sets up.


                      # 2. Installation Options
                      # WebUtil needs to download some files to the client in order to perform
                      # certain integration operations such as OLE or Registry Access
                      # These files are downloaded the first time that you access one of the
                      # functions than needs them
                      # You have to define the location of these files on the server
                      # Details
                      # -------
                      # syslib.location: The vitual path to the directory holding the
                      # the webutil library files on the server side
                      # this must either be an absolute URL or a url
                      # URL that is relative to the documentbase
                      # syslib.<os>.<package>.<n>: The name(s) of the libraries required for particular
                      # webutil beans
                      # The format of this is name|size|version|showDownloadDialog
                      # multiple libraries can be downloaded per package but
                      # ensure that the <n> values are consecutive and start at 1


                      ## Do not change the following lines unless instructed to do so

                      ## But you can add your own libraries in here

                      # 3. Upload / Download options
                      # For the file upload and download options you can define the default
                      # locations on the server that webutil can use as a work area
                      # Optionally you can switch upload and download off
                      # Details
                      # -------
                      # transfer.database.enabled: Can be TRUE or FALSE - allows you to disable
                      # upload and download direct from the database
                      # server.
                      # transfer.appsrv.enabled: Can be TRUE or FALSE - allows you to disable
                      # upload and download direct from the application
                      # server.
                      # transfer.appsrv.workAreaRoot: The root of the location in which WebUtil can
                      # store temporary files uploaded from the client.
                      # This location is always readable and writable
                      # no matter what the settings in appsrv.read and
                      # appsrv.write are.
                      # This setting is required if you need the
                      # Client side READ /WRITE_IMAGE_FILE procs
                      # transfer.appsrv.accessControl:Can be TRUE or FALSE - allows you to indicate
                      # that uploads and downloads can only occur from
                      # the directories named in the
                      # transfer.appsrv.read.n and transfer.appsrv.write.n
                      # entries and their subdirecories. If this setting
                      # is FALSE transfers can happen anywhere.
                      # transfer.appsrv.read.<n>: List of directory names that downloads can read
                      # from.
                      # transfer.appsrv.write.<n>: List of directory names that uploads can write
                      # to.

                      #NOTE: By default the file transfer is disabled as a security measure
                      #List transfer.appsrv.read.<n> directories
                      #List transfer.appsrv.write.<n> directories

                      # 4. Untranslatable Strings
                      # These errors can happen early in the initialisation process before we
                      # have the client locale information to use to detect the correct
                      # language version for the error
                      EN.msg.error.error008=WUC-008: Server side logging was requested but no log file was specified - logging is disabled

                      # 5. Translatable Strings
                      # The following properties represent Strings displayed in various server
                      # side error messages
                      # They are available here to allow customisation
                      # Messages are in the Format "<countrycode>.msg.key
                      # The message reading code picks up the country code automatically from the
                      # client. If the required country code cannot be found then the english (EN)
                      # message is displayed as a default.
                      # You may alter the EN versions of each key, but do not remove them!
                      # General Dialog titles
                      EN.msg.install.progress.title=WebUtil Install
                      EN.msg.install.progress.subtitle=Downloading required libraries; Please wait...
                      EN.msg.errordialog.title=WebUtil Error

                      # App Server side errors
                      EN.msg.error.error007=WUC-007: Unable to write to WebUtil logging file
                      EN.msg.error.error015=WUC-015: Your Form must contain the following Bean for this function to be available:
                      EN.msg.error.error408=WUH-408: The WebUtil Client code sent back a bad Process ID - Please report this error
                      EN.msg.error.error110=WUT-110: Database LOB is of zero length
                      EN.msg.error.error111=WUT-111: Database LOB is un-initialised
                      EN.msg.error.error112=WUT-112: Invalid open mode for Blob. Value should be W or R
                      EN.msg.error.error113=WUT-113: Too many rows match the supplied where clause
                      EN.msg.error.error114=WUT-114: SQL Error
                      EN.msg.error.error115=WUT-115: Checksum Failed
                      EN.msg.error.error116=WUT-116: Transfer already in progress
                      EN.msg.error.error117=WUT-117: Application Server file name cannot be null
                      EN.msg.error.error118=WUT-118: Application Server file does not exist or is of zero length
                      EN.msg.error.error119=WUT-119: Error reading data from Application Server file
                      EN.msg.error.error120=WUT-120: Zero bytes read from Application Server file
                      EN.msg.error.error121=WUT-121: This file transfer has been forbidden by the Adminstrator
                      EN.msg.error.error122=WUT-122: Java Functions are not available on the Appliciation Server
                      EN.msg.error.error123=WUT-123: The webutil.jar file cannot be found on the Appliciation Server Classpath - Some file transfer functions will not work.
                      EN.msg.error.error124=WUT-124: Unable write data on the application server
                      EN.msg.error.error125=WUT-125: Checksum error closing file on application server
                      EN.msg.error.error126=WUT-126: Error closing application server file
                      EN.msg.error.error127=WUT-127: Unable to create workarea
                      EN.msg.error.error128=WUT-128: Exception creating workarea

                      14. FORMS_BUILDER_CLASSPATH in registry looks like:

                      15. FORMS90_PATH in registry looks like:

                      Here is the connect string:

                      I constantly getting message “FRM-40039 cannot attach library webutil while opening form WU_TEST_105”

                      HELP!!!! I am dying allone here.

                      Thanks in advance to anyone willing to check this for me.

                      • 38. Re: Using webutil
                        Hi Sead,

                        I am just wondering if you have webutiljpi.htm, webutilbase.htm with webutil_102.zip because mine doesn't have them,

                        did you check if you are able to download webutil by specifying the virtual path


                        Try creating a new form

                        Attach the library webutil.pll
                        then copy the object from webutil.obj

                        Add one simple function like

                        filename:= client_get_file_name(null,null,null,null,OPEN_FILE,TRUE);

                        compile all shift+ctrl+k

                        Hope it would work

                        • 39. Re: Using webutil
                          Belive it or not, it works...

                          Yes, it did miss those two .htm files, and when I copied it, magic started for me...

                          Thanks a lot. Hopefully I will experiance not so many problems implementing the rest of it.
                          1 2 3 Previous Next