Creating a New Application

To create a new application:

1. Click Create New Application from the Main Console. eaDirect displays the Create New Application screen.

2. Enter the name of the application. The first character in the name must be an alpha. The rest of the name can contain alphanumerics and underscores, but no spaces.

3. Enter the JNDI name of the datasource EJB to use for this eaDirect application. Use the real/global JNDI name as opposed to the local JNDI name ("java:comp/env/…"). The datasource EJB exists in a separate presentation EAR file. To successfully create the application, the JNDI name must exist and the EJB must be properly deployed and available to eaDirect. The Command Center validates the JNDI name before the mapping is persisted. For more details, see "About mapping your application to a datasource EJB" below.

4. From the Index Partition Count drop-down list, select the number of database partitions to use for the application index table. The number of tables you need is dependent on your database platform and the anticipated volume of data. For an Oracle database, we recommend you create one index table and use Oracle’s native table partitioning functionality. For DB2 and SQLServer, we recommend using 4 or 12 index tables for quarterly or monthly index tables.

5. Click Create Application and Continue. eaDirect displays the Create New Job screen.

6. Proceed to create and configure jobs for your application.

About mapping your application to a datasource EJB

You must specify a datasource EJB for each eaDirect application (DDN) you create in the Command Center. When creating an eaDirect application in the Command Center, a datasource refers to an EJB in your application (EAR file) that specifies summary information and location of your document data.

Specifying the datasource EJB at the DDN level allows you to set the JNDI mapping without modifying deployment descriptors, repackaging, and redeploying your web application. It also enables you to retrieve, for example, live data from an external database or archival data from offline storage. In some cases, customizing the datasource can also improve performance and save disk space.

For information on developing a custom datasource EJB, please consult your edocs Professional Services representative and the eaDirect Deploying and Customizing J2EE Applications guide.