Creating a Master Index Application (Repository)

The wizard provides a simple method for you to create
the object definition and the runtime configuration files for your master
index application. This section provides instructions for creating a new project
and using the wizard to create the configuration files for the master index
application. To create the initial master index framework, follow these steps.

Step 5: Define Parent and Child Objects (Repository)

After you define the deployment environment for the
master index application, you can begin to define the structure of the object
you want to index. The primary object will be the parent object for any other
objects defined. Child objects are not required if all information is stored
under the parent object.

You can create new undefined objects, create objects using predefined
templates, or use a combination of both methods to create the objects in your
enterprise object. Perform any of the following actions to define the objects
in the enterprise object.

The names of database constraints are created based on the parent
and child object names. Due to database naming restrictions, the length of
the parent object name plus the length of any of the child object names must
be 21 characters or less. Give the parent object the same name you gave to
the application earlier in the wizard.

Creating Undefined Objects

When you create undefined objects, you create an empty object
with no predefined fields or child objects.

Deleting an Object from the Structure

If you add an object in error, or do not want to use one of the
objects in a predefined template, you can delete the object from the structure.

To Delete an Object From the Structure

On the Define Enterprise Object window, select the object you
want to remove.

Do any of the following:

Right-click in the object tree panel, and then select Delete.

Press the Delete key.

In the wizard toolbar, click Delete.

The object and
any fields associated with that object are deleted. If you remove the parent
object, all child objects are deleted.

Step 6: Define the Fields for Each
Object (Repository)

After you define all the parent and child objects for your enterprise
object, you need to define the fields in each object. Every field has a set
of properties that must be configured before creating the master index configuration
files. If you chose a predefined template to create your objects, be sure
to check the properties for all predefined fields to be sure they are configured
correctly for your implementation.

After you define the parent and child objects, you can perform any of
the following actions to define the fields for those objects.

Configuring Field Properties

When you create a field, a set of default properties is defined
for that field. You can modify the property configuration for each field to
suit your data processing, storage, and display requirements. After you modify
a property value, press Enter to apply the change.

Figure 11 Field EDM Properties

Deleting a Field

If you add a field in error, or do not need one of the predefined
fields from a template, you can delete the field.

To Delete a Field

In the object tree panel of the Define Enterprise Object window,
select the field you want to delete.

Right-click in the object tree panel.

From the context menu, select Delete.

The field is
removed from the object tree.

Step 7: Generate the Project Files (Repository)

Once
you have named the application and configured the source systems, deployment
environment, objects, and fields for the master index application, you need
to generate the configuration files and database scripts. You
have the option to create all additional project files at this time (such
as the JAR files and OTDs) or to wait until you have customized the configuration
files for the master index application. Review the configuration files
to be sure the application is set up correctly for your data processing environment.