Link to home
Start Free TrialLog in
Avatar of kmocampo
kmocampoFlag for Spain

asked on

Compiling forms

I am developing forms using Oracle Form Builder 9.0.2.1. These forms are going to be integrated in a Datastream application (MP7) in a company that has installed LINUX. I develop in a Windows 2000 environment, and then i compile my forms and work fine. But now i don't know what to do to take them to the client company. Should i take the fmb files and recompile them? Which command should i use to recompile? In which directory can i find it once i am in that linux environment? Where can i find the configuration files to see the forms and reports paths?
Avatar of gacki
gacki

Not sure what you mean with "Datastream application (MP7)". Normally forms are deployed using Oracle application server.

You take the fmb files and compile them on the LINUX box using the f90genm.sh script in $ORACLE_HOME/bin. Make sure you set the FORMSXX_PATH environment variables properly, e.g. with a separate script. Runtime settings for the application server are stored in $ORACLE_HOME/forms90/server/default.env.

Avatar of kmocampo

ASKER

I tried to compile the forms and i get a frm-91500 error. I think i have set the variables properly, i executed the f90genm.sh but it fails, any ideas?  I've seen some comments in metalink and they talk about having a display variable. I don't have a DISPLAY variable in my environment...
Mmm, another comment, my application is one commercial application that runs using oracle application server.
I have added DISPLAY and NLS_LANG variables, but still doesn't work. I set:
DISPLAY=:0.0
NLS_LANG=AMERICAN_AMERICA.EE8ISO8859P2
I don't know if it's useful but i have linux 2.4.9-e.57 (well, at least that's what it displays when i execute uname -a.... i haven't used linux before so i'm not familiar with it)
Check out this possible cause I found on Metalink:

Assumes : ORACLE_HOME is set correctly.
                NLS_LANG variable is set correctly.
                DISPLAY variable is set correctly.
                ORA_NLS33 is set correctly.
                LD_LIBRARY_PATH is set perfectly

Motif version installed on Linux is not Motif 2.1.30 (Motif 2.1 patch: 108940-37 or higher).
ASKER CERTIFIED SOLUTION
Avatar of DLyall
DLyall

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Well, i stil have the FRM-91500 error, no matter what i do or which environment variables i set, i always get that error. See, i'm sure that the problem is that i work in a completely character mode in the server, and as i've read in metalink, the f90genm shell is a motif based tool. i think i have wrongly installed something because when i try to execute something like startx or xclock i just get an error. Does it mean that i only can compile my forms in linux in a graphic environment?
I also have searched the f90gen and i don't have it, i only have f90genm...
f90genm.sh is motif based.

With Oracle9i forms the only executable available for compiling the forms is f90genm

and it requires the display variable DISPLAY to be set to point to an active x-windows session. In

forms 6i there is f60gen executable which can be used with batch=yes and without

display variable being set. But in Oracle9i forms, the character mode executables

are no longer supported and the equivalent of f60gen is not there.


In Developer 9i Forms, you can invoke the forms generator by a script f90genm.sh

Also you can give the command similar to following for command line execution.

f90genm.sh module=/u02/home/usupport/users/forms90users/tsriniva/dept.fmb  
userid=scott/tiger@ora901

For a list of compile options you can give

f90genm.sh without arguments which will list out the list of options available as in

forms 6i.
Hi :kmocampo

Coudl you close this call if you have no further comments.


Many Thanks

DLyall
Well, i only have one final question. The problem was on the DISPLAY environment variable, i set it correctly and the fgenm.sh runs. But as i've always worked in windows platforms, i don't know what should i do to specify the path of my own libraries. I have two of them and i put the plx files in the same directory of the fmx. But it seems the compiler cant' find where they are. I included that directory in the LD_LIBRARY_PATH and in the PATH variables, but it still doesn't work. Any ideas? The libraries are already compiled in linux.
set env file before compiling fmb
environment path in the linux : example : /oracle/prodappl/PROD_oraapps.env
and copy fmb file to linux from ftp
fmb location : /oracle/prodappl/au/11.5.0/resources/
compile fmb file this command : f60gen module=xxxxxx.fmb userid=apps/apps password
after compile frms copy your patch
example : /oracle/prodappl/xxtc/11.5.0/forms/US
you can see forms and reports path look at the env file
forms path : /oraappl/prodora/8.0.6/forms60
reports patch : /oraappl/prodora/8.0.6/reports60
if you use advanced forms compile
Usage: f60genm Module=<formname> Userid=<userid/password> [Parameters].
Optional parameters are (default values given):

Module_Type=FORM          Module type (FORM, MENU, LIBRARY, PECS).
Module_Access=FILE        Module access (FILE, DATABASE).
Statistics=NO             Show statistics.
Logon=YES                 Logon to database.
Batch=NO                  Don't display messages on the screen.
Output_File=<file>        Write output to file.
Script=NO                 Write script file.
Parse=NO                  Parse script file.
Delete=NO                 Delete module from database.
Insert=NO                 Insert module into database.
Extract=NO                Extract module from database.
Upgrade=NO                Upgrade module to current version.
Upgrade_Roles=NO          Upgrade SQL*Menu 5.0 role information.
Version=45                Version to upgrade (23, 30, 40, 45, or menu 50).
Crt_File=<crt file>       CRT file for version 2.x form upgrade.
Build=Yes                 Build a runform/runmenu file when upgrading.
Add_Triggers=NO           Add KEY-UP/DOWN triggers during upgrade.
Nofail=NO                 Add NOFAIL keyword to trigger steps.
Debug=NO                  Build/Run with debug information.
Compile_All=NO            Compile all PL/SQL code.
Strip_Source=NO           Strip pl/sql source code from library.
Window_State=Normal       Root window state: (Normal, Maximize, Minimize.)
Help=NO                   Show this help information.
Options_Screen=NO         Display Options window (on bitmap only).
Widen_Fields=NO           Add one character to display width.
Print_Version=NO          Print version used to save module.
Forms_Doc=NO              Print Forms Doc report.