How does E1 fat client's local database work ?

Hi, what is local db used on fat client ? 

According to Oracle, You can access the Data from DB Server by bypassing the Security Server but you will not be run any jobs on the Server.

For the second query the same scenario applies, user will be able to fetch the data but will not be able to run the UBEs.

The prime purpose of local database is used to store the specs locally. Local Database must be started before you try to login to either FAT or Deployment server, or else the login will fail irrespective of the fact whether Security Server is turned on or off.

This database is used when a developer executes any HTML or web application locally.

The information is populated to a local copy of the HTML serialized object tables (F989999 and F989998).

This enables the developers to examine code prior to checking that code in.

This database also serves to contain a copy of the Central Object information on a fat client (as of 8.12 Central Objects

moved to an XML format instead of the old TAM format). In this way the fat client uses the copy of Central Objects contained locally to execute the EnterpriseOne code.

Changing the Object Owner Password Post E1 Install

If there is a need to change the object owner passwords after EnterpriseOne is installed and running, that is done at the database level.  We still recommend adding the [DSPWD] (as described above) to the Deployment Server JDE.INI in case of a future install or upgrade to EnterpriseOne.  

For SSE or OEE Local Database

SSE (SQL Server Express)

• The EnterpriseOne install delivers the 'sa' user account on a workstation install and the 'sa' AND jde accounts on the Deployment Server install.
• The 'sa' user account will always use an encrypted password.
• To encrypt the 'sa' user password, use ReconfigureMSDE.exe.  The exe will generate an encrypted password based on the disk volume where the local DB is installed.  
• If logging into E1 (and SSE), it will use the sa account and the generated/encrypted password.  If you are logging into the SSE (outside of E1) using the SQL Management Tool, you will need to run ReconfigureMSDE.exe to set the password to a known value (e.g., "admin").  Then, when you are ready to run E1 again, you will need to run ReconfigureMSDE.exe again to set the password to a generated/encrypted value.
• The 'sa' user password should not be changed.
• The local database name is JDESSELocal.
• There are no local schemas.
• E1 does not use JDE to connect to the local database, it uses the sa account. 
• Important!  SSE is supported through EnterpriseOne 9.0.  EnterpriseOne 9.1 and above application release does not support SSE.  Check the Certifications page for details.

OEE (Oracle Enterpise Edition)

• The EnterpriseOne install delivers the system and JDE user accounts.
• The system user account will always use an encrypted password.
• To encrypt the system user password, ReconfigureMSDE.exe is used.  The exe will generate an encrypted password based on the disk volume where the local DB is installed.
• The system user password cannot be changed.  This password is generated on the fly by EnterpriseOne.
• The local database name is E1Local.
• Tablespaces (schemas) are delivered in OEE.  The tablespaces are (Ex: SPEC_910, JDEPLAN910, JDECTL910, JDEDD910, JDSYS910, JDEVL910, JDEOL910 and JDEData910).
• E1 does not use these DB owners to connect to the local database. 
• The passwords for the tablespaces (schemas) and JDE user can be changed using the sqlplus command.
• E1Local is installed with a setting in x:\oracle\E1local\network\admin\sqlnet.ora -- SQLNET.AUTHENTICATION_SERVICES=(NONE) -- which prevents any user on any machine from connecting to the local database using Windows permissions.

Hope that's clear..