openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] OpenJPA > Building and Running OpenBooks
Date Wed, 09 May 2012 20:05:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2042/9/5/_/styles/combined.css?spaceKey=openjpa&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/openjpa/Building+and+Running+OpenBooks">Building
and Running OpenBooks</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~kwsutter@gmail.com">Kevin
Sutter</a>
    </h4>
        <br/>
                         <h4>Changes (21)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >OpenBooks builds with Ant. The Ant
build script is somewhat involved because OpenBooks can be built and packaged either as a
JSE (Swing based) application or a JEE Web Application. By default, OpenBooks is built as
a JSE application. <br> <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">OpenBooks
can be built in JSE and JEE mode -- and to keep things simple the common build steps are available
in main build script {{build.xml}} while JSE and JEE specific packaging steps are described
in separate {{build.jse.xml}} and {{build.jee.xml}}, respectively. Furthermore, for JEE, the
deployment step is further refined for each application server. See {{build.jee.was.xml}}
for WebSphere installation steps. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">OpenBooks
can be built in JSE and JEE mode -- and to keep things simple the common build steps are available
in main build script {{build.xml}} while JSE and JEE specific packaging steps are described
in separate {{build.jse.xml}} and {{build.jee.xml}}, respectively. Furthermore, for JEE, the
deployment step is further refined for each application server. See {{build.jee.was.xml}}
and {{build.jee.liberty.xml}} for build and installation steps for WebSphere Application Server
and the Liberty Profile for WAS, respectively. <br></td></tr>
            <tr><td class="diff-unchanged" > <br>Before you run a build,
configure the build environment by editing {{openjpa-examples/openbooks/build.properties}}.
Essentially, you need to <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" > <br>The next step is to configure
runtime configuration descriptors and environment variables. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">*
JSE <br>** Edit {{persistence.xml}} located in {{openjpa-examples/openbooks/src/main/resources/META-INF}}
directory. Modify the {{javax.persistence.jdbc.driver}} and {{javax.persistence.jdbc.url}}
property to suit your local database and its driver. <br>** Edit {{openjpa-examples/openbooks/run.properties}}
to specify location of OpenJPA class libraries and JDBC Driver used in runtime classpath.
 Here again, the use of the {{openjpa.version}} variable with a Maven repository makes the
library and jdbc driver configuration easy. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
For JSE environment, edit {{persistence.xml}} located in {{openjpa-examples/openbooks/src/main/resources/META-INF}}
directory. Modify the {{javax.persistence.jdbc.driver}} and {{javax.persistence.jdbc.url}}
property to suit your local database and its driver. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">*
JEE <br>** You may already have a JTA data source configured and registered in JNDI.
Of course, then the appropriate configuration is to be edited accordingly in the {{&lt;jta-data-source&gt;}}
and {{&lt;non-jta-data-source&gt;}} clauses. See {{persistence.jee.was.xml}} for WebSphere
environment, or {{persistence.jee.liberty.xml}} for the Liberty Profile.  <br>** OpenJPA
library and JDBC drivers are configured in JEE server and hence variables in this file are
irrelevant. <br>** More information on the build and installation of the OpenBooks example
for application servers can be found in the [WebSphere Application Server|#websphere] and
[Liberty Profile|#liberty] deployment sections. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
In JSE mode, edit {{openjpa-examples/openbooks/run.properties}} to specify location of OpenJPA
class libraries and JDBC Driver used in runtime classpath.  Here again, the use of the {{openjpa.version}}
variable with a Maven repository makes the library and jdbc driver configuration easy. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
In JEE environment, you may already have a JTA data source configured and registered in JNDI.
Of course, then the appropriate configuration is to be edited accordingly in {{&lt;jta-data-source&gt;}}
clause. See {{persistence.jee.was.xml}} for WebSphere environment. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
In JEE mode, OpenJPA library and JDBC drivers are configured in JEE server and hence variables
in this file are irrelevant. <br> <br> <br> <br></td></tr>
            <tr><td class="diff-unchanged" >Both {{build.properties}} and {{run.properties}}
files are commented in-place on what is to be edited. <br> <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >* enhance the persistence domain model
<br>* package the application based on the build.mode as a Swing-based application or
a Web Application Archive. <br></td></tr>
            <tr><td class="diff-changed-lines" >* copy the deployable artifacts
to <span class="diff-added-words"style="background-color: #dfd;">{{target}} and</span>
{{target/openbooks}} <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">directory</span>
<span class="diff-added-words"style="background-color: #dfd;">directories</span>
relative to the current directory. <br></td></tr>
            <tr><td class="diff-unchanged" > <br> <br>h2. Deploy OpenBooks
in an Application Server <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >Deployment techniques and configuration
vary across JEE compliant application servers. Hence, OpenBooks does not provide an uber-deployment
script for all application server. Instead, application server specific steps are encoded
in separate build scripts for each application server. Using generic build as described in
the previous section, the <span class="diff-changed-words">{{<span class="diff-added-chars"style="background-color:
#dfd;">target/</span>openbooks.war}}</span> web archive <span class="diff-changed-words">need<span
class="diff-added-chars"style="background-color: #dfd;">s</span></span> to
be deployed manually. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">{anchor:websphere}
<br>h3. WebSphere Application Server <br> <br></td></tr>
            <tr><td class="diff-unchanged" >For WebSphere Application Server,
automated build scripts are available in {{build.jee.was.xml}}. WebSphere deployment needs
to be triggered by {{ws_ant}} utility as follows <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >{{$ ws_ant \-Dbuild.mode=jee \-Dappserver=was
<span class="diff-changed-words">\-Dwas.home=<span class="diff-added-chars"style="background-color:
#dfd;">&lt;</span>WAS_HOME<span class="diff-added-chars"style="background-color:
#dfd;">&gt;</span>}}</span> <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">where
{{WAS_HOME}} denotes the root directory where WAS V7 with JPA 2.0 feature pack has been installed.
Yes, OpenBooks requires the WAS V7 JPA 2.0 feature pack with a profile augmented to run with
the feature pack. Further information on this feature pack is available [here|http://www-01.ibm.com/support/docview.wss?rs=180&amp;uid=swg27018836].
<br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">where
{{&lt;WAS_HOME&gt;}} denotes the root directory where WAS V7 with JPA 2.0 feature
pack has been installed (at a minimum). Yes, OpenBooks requires features defined by the JPA
2.0 specification, thus the use of the WAS V7 JPA 2.0 feature pack is a minimum requirement.
Further information on this feature pack is available [here|http://www-01.ibm.com/support/docview.wss?rs=180&amp;uid=swg27018836]
or [WebSphere in general|http://www-01.ibm.com/software/websphere/]. <br></td></tr>
            <tr><td class="diff-unchanged" > <br>The WebSphere specific
build will configure appropriate JTA data sources using a python script (found under {{openbooks/scripts/}}
directory before deploying OpenBooks as a web application. The script assumes a single server
instance. If multiple profiles exist, the script will use the first server profile. <br>
<br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">{anchor:liberty}
<br>h3. Liberty Profile in WebSphere Application Server v8.5 <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">For
the Liberty Profile in WebSphere Application Server v8.5, automated build scripts are available
in {{build.jee.liberty.xml}}. Liberty Profile deployment is very easy and needs to be triggered
by {{ant}} as follows <br> <br> {{$ ant \-Dbuild.mode=jee \-Dappserver=liberty
\-Dliberty.home=&lt;WAS_HOME&gt;/wlp \-Dliberty.server=&lt;server name&gt;}}
<br> <br>where {{&lt;WAS_HOME&gt;}} denotes the root directory where WAS
v8.5 has been installed, and &lt;server name&gt; is the name of your Liberty Profile
server.  Instead of specifying these two variables, {{liberty.home}} and {{liberty.server}},
you could modify the build variables in the {{build.jee.liberty.xml}} file.   <br> <br>By
specifying {{liberty.home}} and {{liberty.server}}, the ant script will attempt to &quot;deploy&quot;
the resulting openbooks.war application to the designated Liberty server.  Additional configuration
of your Liberty server may be required before OpenBooks will work.  For example, you will
need to specify the {{jpa-2.0}} and {{jdbc-4.0}} features in your server.xml.  You will also
need to define the JTA datasources used by the OpenBooks application via your server.xml file.
 Examples of a derby configuration can be found in the {{openbooks/scripts/liberty}} directory.
<br> <br>Additional information on the Liberty Profile can be found [here|http://www.wasdev.net/].
 General WebSphere information can be found [here|http://www-01.ibm.com/software/websphere/].
<br> <br></td></tr>
            <tr><td class="diff-unchanged" >h2. Run OpenBooks <br> <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" > <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >If you have <span class="diff-changed-words">buil<span
class="diff-deleted-chars"style="color:#999;background-color:#fdd;text-decoration:line-through;">d</span><span
class="diff-added-chars"style="background-color: #dfd;">t</span></span> OpenBooks
for JEE, a Web Application Archive {{openbooks.war}} will be created in <span class="diff-changed-words">{{openjpa-examples/openbooks/target<span
class="diff-deleted-chars"style="color:#999;background-color:#fdd;text-decoration:line-through;">/openbooks</span>}}</span>
directory. You need to deploy {{openbooks.war}} to a JEE Application Server. Once deployed,
you can point a browser to Application Server URL <br></td></tr>
            <tr><td class="diff-unchanged" > <br> {{http:// &lt; app
server host &gt;:&lt;port&gt;/openbooks/}} <br> <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">to
access OpenBooks as an web application. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">For
example, <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">
{{http://localhost:9080/openbooks/}} <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">to
access OpenBooks as a web application. <br> <br> <br></td></tr>
            <tr><td class="diff-unchanged" >h2. Populate OpenBooks Database <br>
<br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h2><a name="BuildingandRunningOpenBooks-InstructionstodownloadandrunOpenBooksDemo"></a>Instructions
to download and run OpenBooks Demo</h2>

<p>OpenBooks comes with</p>

<ul>
	<li>complete source code</li>
	<li>build scripts to demonstrate how to build a typical OpenJPA application and package
it for JSE or JEE environment</li>
	<li>scripts to run OpenBooks in on your local database installation.</li>
</ul>



<p>Follow the simple instructions below to build and run OpenBooks:</p>

<h2><a name="BuildingandRunningOpenBooks-DownloadInstructions"></a>Download
Instructions</h2>

<p>OpenBooks can be checked out from OpenJPA repository.</p>

<p> <tt>$ svn co</tt> <tt><a href="https://svn.apache.org/repos/asf/openjpa/trunk/openjpa-examples/openbooks"
class="external-link" rel="nofollow">https://svn.apache.org/repos/asf/openjpa/trunk/openjpa-examples/openbooks</a></tt>.</p>

<p>will check out the source code and build scripts of OpenBooks in current directory.</p>

<p>OpenBooks requires following software environment to run:</p>

<ul>
	<li>Java Runtime version 6.0 or higher</li>
	<li>OpenJPA Libraries version 2.0 or higher</li>
	<li>Ant version 1.6 or higher</li>
	<li>Any JDBC complaint database supported by OpenJPA (embedded Derby is the default).</li>
</ul>




<h2><a name="BuildingandRunningOpenBooks-Configurebuildandrunenvironment"></a>Configure
build and run environment</h2>

<p>OpenBooks builds with Ant. The Ant build script is somewhat involved because OpenBooks
can be built and packaged either as a JSE (Swing based) application or a JEE Web Application.
By default, OpenBooks is built as a JSE application.</p>

<p>OpenBooks can be built in JSE and JEE mode &#8211; and to keep things simple
the common build steps are available in main build script <tt>build.xml</tt> while
JSE and JEE specific packaging steps are described in separate <tt>build.jse.xml</tt>
and <tt>build.jee.xml</tt>, respectively. Furthermore, for JEE, the deployment
step is further refined for each application server. See <tt>build.jee.was.xml</tt>
and <tt>build.jee.liberty.xml</tt> for build and installation steps for WebSphere
Application Server and the Liberty Profile for WAS, respectively.</p>

<p>Before you run a build, configure the build environment by editing <tt>openjpa-examples/openbooks/build.properties</tt>.
Essentially, you need to</p>

<ul>
	<li>Point <tt>openjpa.lib</tt> variable to the local directory where OpenJPA
class library(ies) reside. Notice that the variable points to a directory and not a <tt>&#42;.jar</tt>
file. All <tt>&#42;.jar</tt> files found under the directory are included
in compilation classpath. OpenJPA version 2.0, however, is also available with all its runtime
dependencies (such as JPA specification API, Apache Commons Collections and others) packaged
together in a <em>single</em> library (lib).</li>
</ul>


<p><b>Note:&nbsp;</b> Access to the OpenJPA class libraries is easier
if you have a Maven repository (.m2) available on your system.&nbsp; In this case, all
that is required is to update the <tt>openjpa.version</tt> variable to point at
the proper OpenJPA SNAPSHOT version.</p>

<ul>
	<li>Ideally, a JPA-compliant application <em>should</em> not require provider-specific
library during compilation. OpenBooks persistent domain model and application logic also does
not use any OpenJPA specific features, but OpenJPA libraries are still used during compilation
because bytecode for persistent entities are <em>enhanced</em> as a post-compilation
step. This bytecode enhancement is not essential but an important step for using OpenJPA.</li>
</ul>


<p>The next step is to configure runtime configuration descriptors and environment variables.</p>
<ul>
	<li>JSE
	<ul>
		<li>Edit <tt>persistence.xml</tt> located in <tt>openjpa-examples/openbooks/src/main/resources/META-INF</tt>
directory. Modify the <tt>javax.persistence.jdbc.driver</tt> and <tt>javax.persistence.jdbc.url</tt>
property to suit your local database and its driver.</li>
		<li>Edit <tt>openjpa-examples/openbooks/run.properties</tt> to specify
location of OpenJPA class libraries and JDBC Driver used in runtime classpath.  Here again,
the use of the <tt>openjpa.version</tt> variable with a Maven repository makes
the library and jdbc driver configuration easy.</li>
	</ul>
	</li>
</ul>


<ul>
	<li>JEE
	<ul>
		<li>You may already have a JTA data source configured and registered in JNDI. Of course,
then the appropriate configuration is to be edited accordingly in the <tt>&lt;jta-data-source&gt;</tt>
and <tt>&lt;non-jta-data-source&gt;</tt> clauses. See <tt>persistence.jee.was.xml</tt>
for WebSphere environment, or <tt>persistence.jee.liberty.xml</tt> for the Liberty
Profile.</li>
		<li>OpenJPA library and JDBC drivers are configured in JEE server and hence variables
in this file are irrelevant.</li>
		<li>More information on the build and installation of the OpenBooks example for application
servers can be found in the <a href="#BuildingandRunningOpenBooks-websphere">WebSphere
Application Server</a> and <a href="#BuildingandRunningOpenBooks-liberty">Liberty
Profile</a> deployment sections.</li>
	</ul>
	</li>
</ul>




<p>Both <tt>build.properties</tt> and <tt>run.properties</tt>
files are commented in-place on what is to be edited.</p>


<h2><a name="BuildingandRunningOpenBooks-BuildOpenBooksfromsource"></a>Build
OpenBooks from source</h2>

<p>Once you have configured the environment, simply issue (from the <tt>openjpa-examples/openbooks</tt>
directory):</p>

<p> <tt>$ ant</tt></p>

<p>or</p>

<p> <tt>$ ant &#45;Dbuild.mode=jee</tt></p>

<p>The default target of the ant script will</p>
<ul>
	<li>generate metamodel classes (required for Criteria API)</li>
	<li>compile the source code</li>
	<li>enhance the persistence domain model</li>
	<li>package the application based on the build.mode as a Swing-based application or
a Web Application Archive.</li>
	<li>copy the deployable artifacts to <tt>target</tt> and <tt>target/openbooks</tt>
directories relative to the current directory.</li>
</ul>



<h2><a name="BuildingandRunningOpenBooks-DeployOpenBooksinanApplicationServer"></a>Deploy
OpenBooks in an Application Server</h2>

<p>Deployment techniques and configuration vary across JEE compliant application servers.
Hence, OpenBooks does not provide an uber-deployment script for all application server. Instead,
application server specific steps are encoded in separate build scripts for each application
server. Using generic build as described in the previous section, the <tt>target/openbooks.war</tt>
web archive needs to be deployed manually.</p>

<p><a name="BuildingandRunningOpenBooks-websphere"></a></p>
<h3><a name="BuildingandRunningOpenBooks-WebSphereApplicationServer"></a>WebSphere
Application Server</h3>

<p>For WebSphere Application Server, automated build scripts are available in <tt>build.jee.was.xml</tt>.
WebSphere deployment needs to be triggered by <tt>ws_ant</tt> utility as follows</p>

<p> <tt>$ ws_ant &#45;Dbuild.mode=jee &#45;Dappserver=was &#45;Dwas.home=&lt;WAS_HOME&gt;</tt></p>

<p>where <tt>&lt;WAS_HOME&gt;</tt> denotes the root directory where
WAS V7 with JPA 2.0 feature pack has been installed (at a minimum). Yes, OpenBooks requires
features defined by the JPA 2.0 specification, thus the use of the WAS V7 JPA 2.0 feature
pack is a minimum requirement. Further information on this feature pack is available <a
href="http://www-01.ibm.com/support/docview.wss?rs=180&amp;uid=swg27018836" class="external-link"
rel="nofollow">here</a> or <a href="http://www-01.ibm.com/software/websphere/"
class="external-link" rel="nofollow">WebSphere in general</a>.</p>

<p>The WebSphere specific build will configure appropriate JTA data sources using a
python script (found under <tt>openbooks/scripts/</tt> directory before deploying
OpenBooks as a web application. The script assumes a single server instance. If multiple profiles
exist, the script will use the first server profile.</p>

<p><a name="BuildingandRunningOpenBooks-liberty"></a></p>
<h3><a name="BuildingandRunningOpenBooks-LibertyProfileinWebSphereApplicationServerv8.5"></a>Liberty
Profile in WebSphere Application Server v8.5</h3>

<p>For the Liberty Profile in WebSphere Application Server v8.5, automated build scripts
are available in <tt>build.jee.liberty.xml</tt>. Liberty Profile deployment is
very easy and needs to be triggered by <tt>ant</tt> as follows</p>

<p> <tt>$ ant &#45;Dbuild.mode=jee &#45;Dappserver=liberty &#45;Dliberty.home=&lt;WAS_HOME&gt;/wlp
&#45;Dliberty.server=&lt;server name&gt;</tt></p>

<p>where <tt>&lt;WAS_HOME&gt;</tt> denotes the root directory where
WAS v8.5 has been installed, and &lt;server name&gt; is the name of your Liberty Profile
server.  Instead of specifying these two variables, <tt>liberty.home</tt> and
<tt>liberty.server</tt>, you could modify the build variables in the <tt>build.jee.liberty.xml</tt>
file.  </p>

<p>By specifying <tt>liberty.home</tt> and <tt>liberty.server</tt>,
the ant script will attempt to "deploy" the resulting openbooks.war application to the designated
Liberty server.  Additional configuration of your Liberty server may be required before OpenBooks
will work.  For example, you will need to specify the <tt>jpa-2.0</tt> and <tt>jdbc-4.0</tt>
features in your server.xml.  You will also need to define the JTA datasources used by the
OpenBooks application via your server.xml file.  Examples of a derby configuration can be
found in the <tt>openbooks/scripts/liberty</tt> directory.</p>

<p>Additional information on the Liberty Profile can be found <a href="http://www.wasdev.net/"
class="external-link" rel="nofollow">here</a>.  General WebSphere information can
be found <a href="http://www-01.ibm.com/software/websphere/" class="external-link" rel="nofollow">here</a>.</p>

<h2><a name="BuildingandRunningOpenBooks-RunOpenBooks"></a>Run OpenBooks</h2>

<p>If you have built OpenBooks for JSE, then go to the <tt>openjpa-examples/openbooks/target/openbooks</tt>
directory.</p>

<p>Invoke the Ant script to run OpenBooks<br/>
<tt>$ ant &#45;f run.xml</tt></p>


<p>If you have built OpenBooks for JEE, a Web Application Archive <tt>openbooks.war</tt>
will be created in <tt>openjpa-examples/openbooks/target</tt> directory. You need
to deploy <tt>openbooks.war</tt> to a JEE Application Server. Once deployed, you
can point a browser to Application Server URL</p>

<p> <tt>http:// &lt; app server host &gt;:&lt;port&gt;/openbooks/</tt></p>

<p>For example,</p>

<p> <tt><a href="http://localhost:9080/openbooks/" class="external-link" rel="nofollow">http://localhost:9080/openbooks/</a></tt></p>

<p>to access OpenBooks as a web application.</p>


<h2><a name="BuildingandRunningOpenBooks-PopulateOpenBooksDatabase"></a>Populate
OpenBooks Database</h2>

<p>OpenBooks checks for existing data at first connection to the database. If the database
is empty, the schema is defined and populated with initial data. However, you can explicitly
populate the database in JSE build.</p>

<p><b>Note:</b> By default, the OpenBooks example uses and populates an
Embedded Derby instance on "first touch".  So, no further configuration or loading is required
for the default configuration.</p>

<p>Edit <tt>load.properties</tt> to specify load parameters such as number
of Books etc. OpenBooks uses this data to populate a database with some sample data. This
example file has some typical values. If you are satisfied with it, you can leave them as
it is. Then invoke the Ant script</p>

<p> <tt>$ ant &#45;f run.xml load</tt></p>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/openjpa/Building+and+Running+OpenBooks">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=21790751&revisedVersion=8&originalVersion=7">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/openjpa/Building+and+Running+OpenBooks?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message