JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Java CAPS Master Index Maintenance Guide     Java CAPS Documentation
search filter icon
search icon

Document Information

Oracle Java CAPS Master Index Maintenance Guide

Related Topics

Defining Master Index Data Manager Security

Define Master Index Data Manager User Roles

To Define a User Role

Define EJB User Roles

To Define an EJB User Role

Create Master Index Data Manager User Accounts

To Create a User Account

Master Index Data Manager User Role Properties

Master Index Data Manager User Permissions

EJB User Role Properties

EJB Security Functions

Learning About Master Index Reports

Master Index Command Line Reports

About Production Reports

About Activity Reports

Master Index Report Configuration

Creating Custom Master Index Reports

Masked Data in Master Index Reports

Master Index Production Reports

Assumed Match Report

Deactivated Record Report

Potential Duplicate Report

Merge Transaction Report

UnMerge Transaction Report

Update Report

Master Index Activity Reports

Weekly Activity Report

Monthly Activity Report

Yearly Activity Report

Master Index Database Indexes

Working With Master Index Command Line Reports

Configuring the Master Index Report Environment

To Set up the Environment

Configuring Master Index Command Line Reports

Defining the Command Line Report Configuration

Configuring Command Line Reports

Master Index Command Line Report Properties

Running Master Index Command Line Reports

To Run the Reports Using the Batch File

To Run the Reports Using a Java Command

Maintaining the Master Index Database

Backing up the Master Index Database

Online Backups

Offline Backups

Restoring the Master Index Database

Archiving Master Index Data

Implementing Changes to the Master Index Project

Modifying Master Index Configuration Files

Updating the Object Structure

Updating Normalization and Standardization Structures

Updating the Match String

Modifying the Master Index Database

Modifying Master Index Security

Modifying the Local ID Format

Implementing Changes to the Master Index Project

After a master index application has been in production, you might need to make changes to your project. For example, if you add a new external system, you need to add that system to the master index database and you might need to modify the object structure and OTDs as well as update the application files. Changes occur as the needs of your end users evolve and as additional external systems are added. Do not make changes to the system hastily. Handle changes using the same change management process that was originally used to deploy your project. Applying this same process of planning, configuration, testing, migration, monitoring, and reevaluation will help ensure successful updates.

Modifying Master Index Configuration Files

Over time, you might need to make changes to your configuration files, such as adding fields or objects to the object structure, changing queries, or fine-tuning the matching process. Whenever you make a change to a master index configuration file, you must undeploy the master index server project, regenerate the application, and then redeploy the project.

This section provides tips for updating components of the configuration files. In order for any of these changes to take affect, you must regenerate the application and rebuild and redeploy the project.

Updating the Object Structure

If you make any changes to the object structure, keep the following in mind.

Updating Normalization and Standardization Structures

If you define normalization, standardization, or phonetic encoding for fields that are not currently defined in mefa.xml, or if you change existing standardization structures, make sure to do the following.

Updating the Match String

If you make changes to the match string, update the database indexes and the blocking query in query.xml accordingly. For example, if you remove a field from the match string, you might also want to remove that field from the blocking query and database indexes. If you add a field to the match string, add the field to the blocking query and to the appropriate database index to maintain performance.

Modifying the Master Index Database

There might be times when you need to modify the master index database. For example, you might need to add or modify a stored procedure or index, or you might need to add new common codes. You must modify the database if you add fields or objects to the object structure in order to reflect the new structure in the database tables. If you make changes to the database, rebuild and redeploy the master index server project to ensure the changes are picked up by the application. The only exception to this is when you add external systems.

Modifying Master Index Security

You can define new users for the database at any time using standard SQL statements to create the type of user you want to define. You can also add new users for the midm.xml through the GlassFish Server. Neither of these procedures require any stoppage of the database or of the master index application and redeployment is not required.

Modifying the Local ID Format

If you need to modify the local ID format for an external system, regenerate the application after you make the changes and then redeploy the project. If you extend the length of a local ID past 20 characters, make sure to increase the length of any database columns containing local IDs. Local ID columns are found in the following tables: sbyn_parent_object, sbyn_assumedmatch, sbyn_enterprise, sbyn_systemobject, and sbyn_transaction.