Webutil installation / configuration  on Application Server 10.2.0.2 at  Suse Linux 9, 64-bits. Combination of several notes:

374128.1 – howto install webutil on oas under Linux/Unix.

333385.1 – Kickstarting WebUtil 1.06 in Developer Suite 10.1.2.0.2

0. Linux and version 10.1.2.0.2
1. Create directory webutil in ORACLE_HOME/forms
2. Transfer in binary mode the following files in the directory $ORACLE_HOME/forms/webutil
d2kwut60.dll
jacob.dll
JNIsharedstubs.dll

3. The following alias was created in the file ORACLE_HOME/forms/server/forms.conf:
AliasMatch ^/forms/webutil/(..*) “ORACLCE_HOME/forms/webutil/$1″

4.The file webutil.cfg was created in the ORACLE_HOME/forms/server and he is looking like:

logging.file=
logging.enabled=FALSE
logging.errorsonly=FALSE
logging.connections=FALSE
install.syslib.location=/webutil
install.syslib.0.7.1=jacob.dll|94208|1.0|true
install.syslib.0.9.1=JNIsharedstubs.dll|65582|1.0|true
install.syslib.0.9.2=d2kwut60.dll|192512|1.0|true

5. Copy/sign jar files in the following directory ORACLE_HOME/forms/java:
frmwebutil.jar
jacob.jar
Download  from http://prdownloads.sourceforge.net/jacob-project/jacob_18.zip
Signing (not always necessary) :
Sign the Jar files, frmwebutil.jar and the jacob.jar, using  forms/webutil/sign_webutil.sh in Linux.
This is a one-time operation, which allows your end-users to trust that the JACOB routines can access client side resources.
1. Make sure that keytool and jarsigner are present in the path (jarsigner.exe , keytool.exe). They are usually available in the bin directory of your Java SDK installation.
2. Issue sign_webutil.sh in Unix/Linux
[Previously this point stated that frmwebutil.jar also needed to be signed. This is no longer neccessary and should not be done.]

6.If you already have a schema in your RDBMS which contains the WebUtil stored code,
you may skip this step. Otherwise have a look at Note 333385.1 , step 4:
Start SQL*Plus as SYSTEM, and issue:
CREATE USER webutil IDENTIFIED BY [password]
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp;
/
GRANT CONNECT, CREATE PROCEDURE, CREATE PUBLIC SYNONYM TO webutil;
/

CONNECT webutil/[password]@[connectstring]
@[OraHome]\forms\create_webutil_db.sql
— Inspect SQL*Plus output for errors, and then
CREATE PUBLIC SYNONYM webutil_db FOR webutil.webutil_db;
/
Reconnect as SYSTEM, and issue:

grant execute on webutil_db to public;
/

7.Copy from webutil_106\java to ORACLE_HOME/forms/java the following two javascript files:

forms_base_ie.js
forms_ie.js

8. Transfer in binary mode the following files :
webutil.olb
webutil.pll
WU_TEST_106.fmb (not in the zip-files nowadays, zo right-click and ‘save as..’), or get it here from Oracle (right side, below Demonstrations, Webutil_Demo).
in the ORACLE_HOME/forms directory

9. Transfer the following files :
webutilbase.htm
webutiljini.htm
webutiljpi.htm
in the directory ORACLE_HOME/forms/server

10. In formsweb.cfg create the following config section
[webutil]
WebUtilArchive=frmwebutil.jar,jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
WebUtilDispatchMonitorInterval=5
WebUtilTrustInternal=true
WebUtilMaxTransferSize=16384
baseHTMLjinitiator=webutiljini.htm
baseHTMLjpi=webutiljpi.htm
archive_jini=frmall_jinit.jar
archive=frmall.jar
lookAndFeel=generic

11. Compile the webutil.pll library:
frmcmp.sh MODULE=$ORACLE_HOME/forms/webutil.pll USERID=webutil/webutil@orcl MODULE_TYPE=LIBRARY
OUTPUT_FILE=$ORACLE_HOME/forms/webutil.plx
– no compilation errors

12. Add jacob.jar and frmwebutil.jar to CLASSPATH or FORMS_BUILDER_CLASSPATH … otherwise there is an error message when opening the canvas in the new created fmb

13. Bounce the OC4J_BI_Forms container on the application server middle tier

14. Compile WU_TEST_106.fmb file
frmcmp.sh MODULE=$ORACLE_HOME/forms/WU_TEST_106.fmb USERID=webutil/webutil@orcl MODULE_TYPE=FORM
OUTPUT_FILE=$ORACLE_HOME/forms/WU_TEST_106.fmx
– no compilation errors

15.Launch the forms demo module:

http://host:port/forms/frmservlet?config=webutil&form=WU_TEST_106.fmx&userid=webutil/webutil@orcl

15.1.Demo module appear on browser.
15.2. Click on the button “Get Client Info” and check if the client info are shown correctly.

zv7qrnb