1. You can configure olite database to Mobile client and use automatic synchronization feature of olite server to replicate data between mobile device and oracle database server.
2. You can use an independent olite database with you mobile application.

Whatever way is used, the data in the mobile is stored in small mobile database files with ODB and OBS extension. ODB file contains data while indexes are stored in OBS file. In olite version 10.2.0.1.0, all objects are stored in ODB file.

If you use synchronization method using mobile client and mobile server, olite database is automatically created on mobile device. But if you are using an independent olite database, use following method to create olite database (this guide is for windows but can be used for linux as well).

First install Oracle lite Mobile Development Kit. Oracle lite Mobile Development Kit is part of installer package for oracle Database lite. Olite Mobile Development kit include all tools to create and mange file-based lite databases. To connect a file-based olite database, a DSN (data source name) is required. By default Mobile Development Kit includes a lite database and DSN, both are named as POLITE.  You can use default DSN to create your database.To create your own database, enter following command at command prompt.

Createdb polite MyDb manager

CrateDB: Mobile SQl Command to Create a database

polite: Name of the DSN

MyDb: Name of the File-based olite database

manager: Password of the system user.

Create Oracle Lite Database (odb)

Databases created using default DSN are stored at <ORACLE_HOME>\Mobile\SDK\BIN\OLDB40

Since we used the default DSN to create database, we need to make the default POLITE DSN to point towards our new database.  Locate file named as “ODBC.INI” at  <ORACLE_HOME>\Mobile\SDK\BIN for oracle lite database 10.3.0.3.0. For oracle lite database 10.2.0.1.0 version, “ODBC.INI” can be located at C:\Windows directory. Replace database name with MyDB as shown below in blod Face,

[POLITE]
Driver32=D:\oracle\olite_dev_kit\Mobile\Sdk\BIN\olod2040.dll
Description=Oracle Lite 40 Data Source
DataDirectory=D:\oracle\olite_dev_kit\Mobile\Sdk\oldb40
Database=MyDB
IsolationLevel=Read Committed
Autocommit=Off
CursorType=Static

Now you can connect to you database with polite DSN which now points to MyDb database using following Mobile SQL command

msql system/manager@polite:polite

msql: Mobile SQl command to connect to file-based oracle lite database

system: Default user name

manager: Password of the system user

Polite: JDBC driver

Polite: DSN

Now you can create schema in you database as shown in figure below

Connect to Oracle Lite Database

In above example we used default DSN to create database. If you want to use your own DSN, You first need to register you DSN in ODBC.INI file. For example, add foll0wing command to create a DSN named MyDSN

[MyDSN]
Driver32=D:\oracle\olite_dev_kit\Mobile\Sdk\BIN\olod2040.dll
Description=nohitng
DataDirectory=D:\oraclework\olite
Database=MyDb
IsolationLevel=Read Committed
Autocommit=Off
CursorType=Static

You can also change the location where the new database will be stored be changing the value of DataDirectory Parameter. Now you can use follwing commands to create new database with your DSN

Createdb MyDSN MyDb manager

And use following command to connect to it

msql system/manager@polite:MyDSN

To resolve this problem, you must configure JRE to work with forms services 10g. It is really easy and requires only very little work. Forms services 10g are by default configured to run with JRE 1.4.2_06. To get this working, locate following lines in your FORMSWEB.CFG file,

# System parameter: default base HTML file
baseHTML=base.htm
# System parameter: base HTML file for use with JInitiator client
baseHTMLjinitiator=basejini.htm
# System parameter: base HTML file for use with Sun’s Java Plug-In
baseHTMLjpi=basejpi.htm

Make changes as shown in bold face below.

# System parameter: default base HTML file
baseHTML=basejpi.htm
# System parameter: base HTML file for use with JInitiator client
baseHTMLjinitiator=basejpi.htm
# System parameter: base HTML file for use with Sun’s Java Plug-In
baseHTMLjpi=basejpi.htm

Make sue that following parmaments in FORMSWEB.CFG are as mentioned below.

jpi_download_page=http://java.sun.com/products/archive/j2se/1.4.2_06/index.html
jpi_classid=clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA
jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_4_2-windows-i586.cab#Version=1,4,2,06
jpi_mimetype=application/x-java-applet;jpi-version=1.4.2_06

Now install J2RE version 1.4.2_06  from following URL,

http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase14-419411.html#j2re-1.4.2_06-oth-JPR

OR

you can also omit version no from following line,

jpi_mimetype=application/x-java-applet;jpi-version=1.4.2_06

after ommiting version, above line will look like following

jpi_mimetype=application/x-java-applet

Now you can use any latest JRE version. (Thanks to S Shamji  and JoeAStudent for thier comments related to version change )

Remove Jinitiator from you computer and restart OC4J instance. Now your Forms application 10g will use Sun’s Java plug-in instead of Jinitiator.

Update:

Looks like Firefox 12 does not work by omitting version no from formsweb.cfg. Instead you need to provide correct installed version.

For example, If you have jre 1.6.x installed in your system then edit following line as under.

jpi_mimetype=application/x-java-applet;jpi-version=1.6

The above line covers JRE 6 with all update levels.

Suppose you have created an Entity object for Employees table in HR schema. You have also created the view object and added this view object to default application module. Employees table has a primary key on Employee_Id field.

First part explains database trigger method and second part explains it with application level logic in JDeveloper.

1- Create a database trigger on Employee table as under.

CREATE OR REPLACE TRIGGER employees_generate_pk
BEFORE INSERT
ON employees
FOR EACH ROW
BEGIN
SELECT employees_seq.nextval
INTO :new.employee_id
FROM dual;
END;
This code assumes that you have already created a sequence named “employees_seq” to generate next value for primary key.

2- Edit Employee Entity object and change data type of employee_id to “DBSequence” as shown in figure below.

DBSequence is a special domain. When you insert a new record, ADF creates a negative number for field. When you perform commit, database trigger generates value for that column which is then re-queried by ADF and shown to users.

Application Level Logic to generate Sequence no for Primary key in JDeveloper

1- First Method

Do following steps to achieve this

1. Data type of employee_id field should by Number, uncheck Mandatory check box  on edit attribute page of Entity object.
2. Create a new view object name “Seq_Employee” bases on  “Read-only access through query”  using following query

select nvl(max(employee_id)+1,1) seq_nofrom hr.employees

1. Add a view accessor on Employee Entity object using its “View Accessor” page. And add “Seq_Employee” view object as shown in figure below.

4-Now generate Entity object class for employee entity object as shown in figure below figure

5-Generate view row class for “Seq_Employee” view object. While creating view object class, do not forget to click on “Include accessors” check box. By default, JDeveloper will name this class as “Seq_EmployeeRowImpl” .

6- Open EmployeesImpl entiry object class wich you created in setp 4, and edit it doDML() method. After editing method should look like under.

protected void doDML(int operation, TransactionEvent e) {
if (operation==DML_INSERT){
RowSet seqForThisEmp = (RowSet) getSeq_Employee();
Seq_EmployeeRowImpl nextSeqNoRow =(Seq_EmployeeRowImpl) seqForThisEmp.next();
Number next_seq = nextSeqNoRow.getSeqNo();
this.setEmployeeId(next_seq);
}
super.doDML(operation, e);
}

This method fires just before ADF performs insertion. This method progamatically accesses view accessor to get next sequence no for employee_id and sets the this value for current row.

2- Second Method

Your can also directly use your database sequence in doDML as under

if(operation==DML_INSERT)
this.setEmployeeId(new DBSequence((new SequenceImpl("employees_seq",getDBTransaction()).getSequenceNumber()).longValue()));

Above code assumes that data type of  EmployeeID is DBSequence. If it is Number, remove cast operation as under

if(operation==DML_INSERT)
this.setEmployeeId((new SequenceImpl(“employees_seq“,getDBTransaction()).getSequenceNumber()));

1-      Create an Entity object definition for Table “SCOTT.EMP”.

2-      Now open EMP Entity Object definition in the editor and click its Attribute tab.

3-      Add an attribute by clicking on green plus sign.

4-      Set name as “Dname”, deselect Persistent check box, select “Derived from SQL Expression” and enter following query in Expression box, as shown in figure below.

(Select Dname from dept where deptno=Emp.Deptno)

Do not forget to put parenthesis around SQL query. Otherwise you will get following exception at run-time while trying to update,

(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for Emp.

5-      Now create a default View Object for EMP Entity object and add it to an Application Module. Run Application module and double click View object. Department name will be visible as shown in figure below.

I studied ADF with oracle JDeveloper 11g. Remember there is significant difference between JDeveloper 11g and its previous releases. I started with online learning material from Oracle website along with a book titled “Oracle JDeveloper 11g Handbook, A Guide to Oracle Fusion Web Development”. This book is well arranged and guides through complete process of building a ADF web application.

ADF is a Framework provided by Oracle to develop applications based on JEE standard. You do not need to worry how you maintain JEE standard, as applications built using ADF automatically imply this standard.  When you develop an ADF web application in JDeveloper, application is divided into four layers,

1.       Business Service Layer

2.       Model Layer

3.       View Layer

4.       Controller Layer

1- Business Service Layer

Business services layer defines database objects like table in XML document. Java classes use these XML definitions to create runtime objects which correspond to database tables and other objects. You can ask Framework to create these classes at design time. These classes can then be used to incorporate business rules.  No code is required to create Business Service Layer in the form of XML documents, everything is Wizard based.

You can add validation rules in Business Service layer.  All this can be done declaratively.  You can also provide UI hints in this layer, for example, you can defines Labels for UI fields.

2- Model Layer

Business Service Layer provides different types of services. If you want to call these services directly, you would need different API for different services.  Model layer provides Data Controls that provide a mechanism to call all these services in a consistent way. So Business services are accessed in UI through Model layer. This can be done simply by a dragging a Data Control to UI page.

3- View Layer

View layer of ADF is the user interface. User Interface in ADF is developed in JavaServer Faces (JSF).  ADF has provided a comprehensive library of ADF Faces components. This library contains extremely rich UI controls.  ADF Faces provide much much more than what Oracle Form Builder provide to develop user interface.  ADF Faces also provides a set of components in Data Visualization Tools tag library. These components include Graph, Gauges, Maps and much more to develop a rich user interface.

Most important feature of these controls is use of Ajax technology.  This allows submitting a fragment of the UI to server, while user can interact with other page components. This provides a user interface similar to desktop applications with plain HTML.

Business rules like validation can also be written in this layer.

4- Controller Layer

In typical web application, when user clicks navigation button, logic is hard coded behind click event to navigate to required page.  In ADF when a user clicks a button or link to navigate to another page, calling page raises a navigation event like “gohome“. Now it is responsibility of Controller Layer to determine that which page will be called. Hence all navigation logic is defined declaratively in Controller layer. In future, if there is requirement to change page navigation, this can be done in Controller layer without disturbing view layer.

The style of development in ADF is rapid. Pages can be developed on the fly like oracle Forms builder.  Application built in ADF is more powerful, more reusable, more rich and reliable than application developed in Forms Builder. But no doubt ADF is much more complex than Forms Builder and architecture is totally different. In Forms Builder we have only view layer and data is directory access from Database unlike ADF where Business Service layer and Model layer perform this task. With ADF, Much more effort is required to achieve same level of expertise you have using Forms Builder.

If we talk about Reports development, then ADF and JDeveloper do not do much in this area.  Read-only JSF output serves as basic reporting requirement.  But for Advance reporting you have to rely on some other tools like Oracle BI Publisher (As mentioned in “Oracle JDeveloper 11g Handbook, A Guide to Oracle Fusion Web Development” book).

At the moment it is not clear that what will be the future of ADF and JDeveloper. At the moment ADF is not more popular than oracle Forms Builder.  Also as an IDE, JDeveloper is not as much popular among core JEE developer as NetBeans and Eclipse are. Oracle Fusion Applications (Oracle Next Release for Packaged application) is said to be developed using ADF and JDeveloper. Oracle Fusion Applications are expected to release soon. Things may change after that release.

We can reduce this download time by keeping a copy of these files on client side prior to accessing the application. If we place these file on the default CLASSPATH of JRE , JRE use these files form client side instead of downloading it from server. Suppose JRE is  installed  in C: drive, you can place these files in following directory,

C:\Program Files\Java\jre6\lib\ext

Now when you access Forms 11g application, JRE loads all required JAR files from  \ext directory.  This saves significant time on a slow connection.

In oracle Forms this key mapping is defined in fmrweb.res file. Oracle provided a tool named “Oracle Terminal” in Forms 6i to customize key mapping. In Forms 10g and Forms 11g this file is directly editable.  In Forms 11g this file can be located at following location

$Instance_home\config\FormsComponent\forms

In Forms 10, frmweb.res can be located in \forms directory

As you know, in Forms 10g and 11g “List of values” is mapped to “Ctrl+L” key. Following section explains how to change “List of values” to F9 key. Let have a look at the following line in frmweb.res file which maps “List of values”  to “Ctrl+L” key

76   : 2 : “Ctrl+L”         : 29 : “List of Values”

it very important to understand the syntax.

76: is the key code of  “L” character

2: means that it will be accessed with “Ctrl” key, 1 is used for “Shift” key and  0 is used to access it stand alone

Ctrl+L: it is the key used to access

List of values: it is function called when the “Ctrl+L” is type

To re-map List of values from “Ctrl+L” to F9 key, we need key code of F9 key which is 120. A complete list of key codes can be view at following link

Keyboard keys and Key Values

Now edit key mapping for  List of values as under

120  : 0 : “F9″             : 29 : “List of Values”

To test it, restart your forms application. Now List of values is available with F9 key. similarly if you want to use “Shift+F”  for List of values, use following mapping

120  : 1 : “Shift+F9″             : 29 : “List of Values”

and use following mapping to access List of values with “Ctrl+F9″

120  : 2 : “Ctrl+F9″             : 29 : “List of Values”

Web.Show_Document('http://domainname.com:8090/reports/rwservlet?userid=username/password@db& server=ReportsServer_1&desformat=PDF&destype=cache&report=report.rdf&paramform=yes','_blank');

In above call username and password are visible in URL, causing security problem. Oracle has provieded serveral methods to resolve this problem, one of these solution is to define keymapping in CGICMD.DAT file.  In Reports services 11g this file is located at following location

$DOMAIN_HOME/servers/WLS_REPORTS/stage/reports/reports/configuration/cgicmd.dat

In Oracle Reports services 10g this file can be located in  reportsconf directory.

To define a key mapping, append follwing line at the end of  the file

userlogin:      userid=username/password@db  %*

Restart reports server/Managed server, now you can call your report using following URL

Web.Show_Document('http://domainname.com:8090/reports/rwservlet?userlogin&server=ReportsServer_1&desformat=PDF&destype=cache&report=report.rdf&paramform=yes','_blank');

You can define key mapping for as many parameter as you need using following syntax,

userlogin:      userid=username/password@db server=ReportsServer_1 desformat=PDF destype=cache %*

If reports have been configured with SSO, simply pass  ssoconn=config parameter in reports calling URL, here config is the Resource Access Descriptor defined in OID. This parameter will automatically get login information from Oracle Internet Directory.

Reference: http://download.oracle.com/docs/cd/E12839_01/bi.1111/b32121/pbr_run013.htm


# Parameter related to the version of the Java Plugin
jpi_mimetype=application/x-java-applet;jpi-version=1.6.0_12

Note that forms services is configured with  JRE 1.6 update 12.

Each time Firefox  tries to load java applet, it looks for  java version 1.6.0_12. If your system has other version installed then you get following message,

Additional Plugins are required to display all the media on this page

To resolve this problem either install JRE 1.6 update 12 or edit you FORMSWEB.CFG to omit the java plugin as under

# Parameter related to the version of the Java Plugin
jpi_mimetype=application/x-java-applet

Now as FORMSWEB.CFG do not include any specific version java, Firefox will load java applet with any available java plugin.

Note that, there is no such issue with Internet Explorer.

In case of OID, you can install either Oracle Internet Directory 11g or Oracle Internet Directory 10g (10.1.4.3.0). Until now, Oracle Fusion Middleware has no Single sign-on, so you must install single Sign-on version 10g (10.1.4.0) with Delegated Administration services.

If you want to use OID 11g you can install it with Oracle Database 11g (11.1.0.7.0) or Oracle Database 10g (10.2.0.4). For OID 10g you should use Oracle Database 10g (10.2.0.4). Although OID 10g(10.1.4.3.0) can be installed on 10.1.0.5 or higher version but Portal 11g and Discover 11g repositories support only Oracle Database 10g (10.2.0.4) or oracle Database 11g (11.1.0.7.0) or higher.

Weblogic server is required for Oracle Internet Directory 11g and for Forms, Reports, Portal and Discoverer 11g.

If you have decided to proceed with Oracle Internet Directory 11g, visit following links to view step by step installation guide,

http://forums.oracle.com/forums/thread.jspa?threadID=946863

http://download.oracle.com/docs/cd/E15523_01/install.1111/e10421/toc.htm

http://newappsdba.blogspot.com/2009/11/11g-fusion-middleware-install.html

If you have decided to proceed with Oracle Internet Directory 10g, visit following link

http://exploreoracle.com/2010/04/02/forms-reports-discoverer-portal-11g-installation-with-oid-10g-10143-and-sso-10143/