Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Using the OracleAS 10

Using the OracleAS 10

Ratings: (0)|Views: 478|Likes:
Published by dbwalya

More info:

Categories:Topics, Art & Design
Published by: dbwalya on Dec 29, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Using the OracleAS 10.1.2 Forms and Reports Builders with OracleApplications Release 12 [ID 444248.1]
Using the OracleAS 10.1.2 Forms and Reports Builders with OracleApplications Release 12
Last revised: August 2, 2010 12:34 PM
See Change RecordThe most current version of this document can be obtained in Oracle
 Note 444248.1.Ensure that you have the most current version before you begin.
In This Document
Section 1: Overview
The Forms and Reports objects shipped with Oracle Applications Release 12 are built using Forms10.1.2 and Reports 10.1.2, both components of Oracle Application Server 10.1.2 (OracleAS 10.1.2).By default, the standalone OracleAS 10.1.2 product does not include the builders, as it is designed toprovide a runtime deployment environment, not a development environment. OracleAS 10.1.2 onlyincludes the compilers and runtime, so customers wishing to develop their own Forms and Reportswould need to use OracleAS 10.1.2 Developer Suite (DS 10.1.2).For Applications Release 12 customers, the OracleAS 10.1.2 Oracle home created by Rapid Installincludes the Forms and Reports builders, but only for Linux, Solaris and Windows. The builders wereincluded by Oracle Applications Development (with the support of the Application Server developmentgroup) for the convenience of Applications customers, to help with support and maintenance of Release 12 environments. Customers developing their own Forms and Reports applications, or customizing, should still license the builders separately.Developer Suite 10.1.2 is only available on Linux, Solaris and Windows. It was not possible to includethe builders in the Applications Release 12 Rapid Install for AIX, HP-UX and HP-Itanium platforms,because they had never been ported to these platforms. Customers will need either a Windows,Linux, or Solaris machine with DS 10.1.2 installed if they need to use the builders. Instructions aregiven below.In terms of UI and functionality, the 10.1.2 builders are very similar to the Developer 6
versions.However, there are some architectural differences. The builders require the 1.4.2 version of the JDKinstalled under the OracleAS 10.1.2 Oracle home,
the JDK used by Oracle Applications runtime.Both builders now start up in-process JVMs, so it is important that $CLASSPATH,$LD_LIBRARY_PATH, and so on are set correctly.
On UNIX/Linux platforms, always run the builders using the script provided, and not by running thestandalone executable: this way, you can be sure CLASSPATH and LD_LIBRARY_PATH will be setcorrectly.As for Developer 6
, the builders on Linux and Solaris are Motif executables, so require a valid Xserver and display. They can be run from a properly configured X emulator.To test that you will be able to run the builders, try running a standard X application such as xclock. If you cannot do so successfully, you must resolve the issue before trying to run the builders.
Section 2: Running the Forms Builder 
This section assumes you are running the builder on the Release 12 Application tier for either Linux,Solaris or Windows.
Linux and Solaris
First, source the Oracle Applications generated OracleAS 10.1.2 environment file. The environmentfile will be located under the 10.1.2 subdirectory of the Release 12 instance home. For example,assuming Release 12 is installed under /slot01/appmgr, and the instance name is "txk123", source thefollowing file:
The above could also be written as $ORACLE_CONFIG_HOME/txk123.env, or $INST_TOP/ora/10.1.2/txk123.env. You can look up $ORACLE_CONFIG_HOME in the Help->AboutWindow of a Release 12 Forms session if you are not sure of the underlying directory structure. TheForms Help->About Window displays settings for the OracleAS 10.1.2 Oracle home.Second, modify the environment variable FORMS_PATH, so the referenced forms can be found.Referenced forms are only required by the builder and compiler. The compiler merges in everything itneeds from the referenced form when it generates the .fmx, so the referenced forms are not used atruntime; this is the reason they are not in the default FORMS_PATH.
This assumes you are working with the US English version of the form. For other languages, add theappropriate language subdirectory to FORMS_PATH in place of US. The referenced objects will thenbe in the correct language.Launch the builder by running the following command:
frmbld.sh &
use the frmbld.sh script, under $ORACLE_HOME/bin. Do not run the executablestandalone. After sourcing the 10.1.2 environment file, $ORACLE_HOME should be set to~/apps/tech_st/10.1.2, and $ORACLE_HOME/bin should be included in $PATH.Be aware that Forms searches the current working directory ($PWD) for referenced forms andlibraries before FORMS_PATH. If you run the builder from your home directory, and have old copiesof fmb's and pll's saved there, these will be picked up instead.
On Windows, you need to set the appropriate variables in the registry. For the Applications Release12 Forms runtime on Windows, the FORMS variables are set in the Applications startup script, rather than the registry. Consequently, FORMS_PATH may not exist in the registry, or may exist with thedefault DS 10.1.2 values. You will therefore have to set it appropriately if you want to use the builder,by defining the relevant variables under theHKEY_LOCAL_MACHINE/Software/Oracle/<AS10.1.2DevSuiteHome> registry key. (Even if FORMS_PATH is not defined, you should see several other FORMS_* variables, plusORACLE_HOME, so you can identify the correct registry key.) Set FORMS_PATH to<$AU_TOP>/resource;<$AU_TOP>/forms/US (where $AU_TOP is replaced with the full directorypath, and directories are separated with a semicolon).In addition to FORMS_PATH, set the following variables in the registry. These are required to compileApplications forms cleanly, when using either the builder or compiler.
 Failure to set the above variables will result in a large number of warnings relating to mirror items, or errors such as the following on compiling some forms.
PL/SQL ERROR 512 at line 1140, column 55
Implementation Restriction: 'FND_API.G_MISS_CHAR': Cannot directly access remote package variable or cursor 
Launch the Forms builder from the Windows Start Menu:Programs -> Oracle Developer Suite -> Forms Developer -> Forms Builder You will not be able to run applications forms in the DS environment because you will not have theApplications user-exits for that platform. User-exits are only required at runtime - the builder andcompiler do
verify that the user-exit call is valid, other than checking that the parameters passedto the user-exit built-in are syntactically correct.When you test a form, the Forms builder now launches the web runtime, as client-server is notsupported in Forms 10.1.2. Instructions for running Applications forms standalone are not provided:this was never supported in the past with client-server, and many Applications forms will not work in astandalone Forms session in any case.
Section 3: Running the Reports Builder 
First, source the Applications-generated OracleAS 10.1.2 environment file, as described in the Formsbuilder section above.Next, unset the following environment variables which are required by Forms, but in somecircumstances can cause problems for Reports. Reset the variables before either running the Formsbuilder or compiling forms manually.
unset EVENT_10932unset DE_DISABLE_PLS_512
Open $ORACLE_HOME/bin/reports.sh in a text editor and comment out the following lines.

Activity (4)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
Wafaa Wafaa Wafaa added this note
i created 3 new string keys at the registry for the following varivables: EVENT_10932=8 DE_DISABLE_PLS_512=1 FORMS_FLAG_DIFFERENT_SUBORD=1 but i still have the same problem at complilation time
Wafaa Wafaa Wafaa added this note
I've the error :Implementation Restriction: 'FND_API.G_MISS_NUM': Cannot directly access remote package variable or cursor ,, any idea ?

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->