(r3) XeoPrimerBoConfig < WebXEO

WebXEO Web>XeoPrimer>XeoPrimerBoConfig (revision 3) (raw view)~~EditAttach~~
-- Main.PedroRio - 30 Jan 2011
---+ boConfig - XEO Application Configuration

The boConfig.xml file (located at the root of every XEO Application) is the basic configuration file in a XEO Application.

The boConfig.xml file has a root element boConfig and then several child elements, each of them responsible for the configuration of different parts of the XEO Application.
---+++++ Definition Directory

Path to the directory where the XEO Packages (containing the XEO Models) are located (by default "bodef")

Example:
<pre><verbatim><definitiondir>.\bodef\</definitiondir></verbatim>
</pre>

---+++++ Profiles Definition Directory

Path to the directory where workplaces and profile definition files are located (by default "uidef\default")

Example:
<pre><verbatim><uidefinitiondir>.\uidef\default</uidefinitiondir></verbatim>
</pre>

---+++++ Web Context Root

The web context root of the application (it must also be configured in your Application Server as well, this value does not deploy the application in that address) - by default "/xeo".

Example:
<pre><verbatim><webcontextroot>/xeo</webcontextroot></verbatim>
</pre>

---+++++ Encoding

The encoding of the application - default is "UTF-8"

Example:
<pre><verbatim><encoding>UTF-8</encoding></verbatim>
</pre>

---+++++ Deployment - Configurations of the XEO Builder

The deployment section configures the XEO Builder, it has several subconfigurations:
   * Class Directory - Where to put the compiled generated classes by the Builder
   * Source Directory - Where to put the source code for the generated classes by the builder
   * Object Model Directory - Where to put the XEO Models so that they are acessible by the application
   * Java Compiler - Path to the Java compiler (JDK 1.6)
   * Model Templates - TODO
   * JSP Deploy Directory - Where to put the JSP's generated from viewer definition inside Object Models
   * Web Modules Directory - Where to find the web applications from the XEO Core and Modules
   * Library Directory - Where to find Java Libraries required by the project
   * Tablespace - The database tablespace (Oracle), in MySQL, use the database name

Example of a configuration:
<verbatim><deployment>
        <class_dir>.\.build\classes\</class_dir>
        <src_dir>.\.build\src\</src_dir>
        <obj_dir>.\.build\bodef-deployment</obj_dir>
        <obj_compiler>C:/jdk1.6.0_14/bin/javac.exe</obj_compiler>
        <obj_templates>.\.templates</obj_templates>
        <obj_deployjspdir>.\.build\webresources\default\</obj_deployjspdir>
        <obj_moduleswebdir>.\base_lib\modules_web\</obj_moduleswebdir>
        <lib_dir>.\lib\</lib_dir>
        <tablespace>USERS</tablespace>
    </deployment></verbatim>

_
---+++++ Threads - Background work configurations

This section allows to define the background workers (threads) available in the XEO Application (by default, only the FullText Indexer (Ebo_TextIndex) is active)

To know more about Background work, check the Threads and Schedules section.

Example:
<verbatim><threads type="userThreads">
        <thread interval="15000" ejb-name="ejb/boTextIndexAgent" name="boTextIndex Agent"/>
    </threads></verbatim>

_
---+++++ DataSources - Configurations about the datasources used

The datasources section, defines the implementation classes that are used in order to access the relational database

Example (for Oracle connection):
<verbatim><DataSources>
        <DataSource boql="true" name="DATA">
            <Driver>netgest.bo.data.oracle.OracleDriver</Driver>
            <DML>jdbc/xeo</DML>
            <DDL>jdbc/xeo_nojta</DDL>
        </DataSource>
        <DataSource boql="true" name="SYS">
            <Driver>netgest.bo.data.oracle.OracleDriver</Driver>
            <DML>jdbc/xeo_nojta</DML>
            <DDL>jdbc/xeo_nojta</DDL>
        </DataSource>
    </DataSources></verbatim>

_
---+++++ Log Configuration

Configures the Logger for the XEO Application ( [[LogginInXEOApplicationsWithLog4j][read more]])
---+++++ Mail Configuration

TODO
---+++++ ECM Repositories

Not yet available in XEO
---+++++ Repositories

TODO
---+++++ browser

TODO
---+++++ Word Templates

TODO
---+++++ Win 32 Client

TODO
---+++ Modules

When some modules are installed in a XEO Application, additional properties can be configured in boConfig: namely:
---++++++ Content Manager

In order to configure the Content Management you'll need to define the XEO Models that used as Content and the XEO Models that are used as Images, like the following:
<pre><pre>&lt;Content_Manager&gt;
        &lt;Contents_Type&gt;XEOCM_Contents;XEOAG_Contents;XEOCM_Noticias;XEOCM_Contents_Link;XEOCM_Document;XEOCM_Map&lt;/Contents_Type&gt;
        &lt;Images_Type&gt;XEOCM_Image&lt;/Images_Type&gt;
&lt;/Content_Manager&gt;</pre>
</pre>

_
Topic revision: r3 - 2011-03-03 - PedroRio
No permission to view TWiki.WebTopBar
No permission to view TWiki.WebBottomBar