Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Designing: Master Index Update Policy Plug-ins (Repository)
 

Classic Java CAPS

Developing Java CAPS Projects

Using SOAP Message Handlers

Creating a Runtime Environment

Designing Business Processes in the Sun Business Process Manager

Working with TCP/IP HL7 Collaborations

Developing Sun Master Indexes (Repository)

Related Topics

Sun Master Index Overview

About Sun Master Index

Master Index Repository Components

Learning about the Master Index Runtime Environment

Master Index Runtime Components

Enterprise Records

Working with Project Components

Master Index Development Process Overview (Repository)

The Master Index Framework and the Runtime Environment (Repository)

Before You Begin Developing a Master Index (Repository)

Preliminary Data Analysis for a Master Index (Repository)

Planning a Master Index Project (Repository)

Master Index Project Initiation Checklist (Repository)

Creating a Master Index Application (Repository)

Step 1: Create a Project and Start the Wizard (Repository)

Step 2: Name the Master Index Application (Repository)

Step 3: Define Source Systems (Repository)

Step 4: Define the Deployment Environment (Repository)

Step 5: Define Parent and Child Objects (Repository)

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

Step 7: Generate the Project Files (Repository)

Step 8: Review the Configuration Files (Repository)

Master Index Wizard Field Properties and Name Restrictions (Repository)

Master Index Wizard Field Name Restrictions (Repository)

Master Index Wizard General Field Properties (Repository)

Master Index Wizard EDM Field Properties (Repository)

Custom Plug-ins for Master Index Custom Transaction Processing (Repository)

Master Index Update Policy Plug-ins (Repository)

Master Index Field Validation Plug-ins (Repository)

Master Index Field Masking Plug-ins (Repository)

Master Index Match Processing Logic Plug-ins (Repository)

Master Index Custom Plug-in Exception Processing (Repository)

Custom Plug-Ins for Master Index Custom Components (Repository)

Master Index Survivor Calculator Plug-ins (Repository)

Master Index Query Builder Plug-ins (Repository)

Master Index Block Picker Plug-ins (Repository)

Master Index Pass Controller Plug-ins (Repository)

Match Engine Plug-ins (Repository)

Standardization Engine Plug-ins (Repository)

Phonetic Encoders Plug-ins for a Master Index (Repository)

Implementing Master Index Custom Plug-ins (Repository)

Creating Master Index Custom Plug-ins (Repository)

Building Master Index Custom Plug-ins (Repository)

Generating the Master Index Application (Repository)

To Generate the Application for the First Time

To Regenerate the Application

Master Index Database Scripts and Design (Repository)

Master Index Database Scripts (Repository)

Master Index Database Requirements (Repository)

Master Index Database Structure (Repository)

Designing the Master Index Database (Repository)

Creating the Master Index Database (Repository)

Step 1: Analyze the Master Index Database Requirements (Repository)

Step 2: Create a Master Index Database and User (Repository)

Step 3: Define Master Index Database Indexes (Repository)

Step 4: Define Master Index External Systems (Repository)

Master Index Database Table Description for sbyn_systems (Repository)

Step 5: Define Master Index Code Lists (Repository)

Step 6: Define Master Index User Code Lists (Repository)

Master Index Database Table Description for sbyn_user_code (Repository)

Step 7: Create Custom Master Index Database Scripts (Repository)

Step 8: Create the Master Index Database Structure (Repository)

Step 9: Specify a Starting EUID for a Master Index (Repository)

Deleting Master Index Database Tables (Repository)

To Delete Database Tables (Repository)

Defining a Database Connection Pool Through the Application Server

Step 1: Add the Oracle Driver to the Application Server

Step 2: Create the JDBC Connection Pools

Step 3: Create the JDBC Resources

Developing Sun Master Patient Indexes

Developing OTDs for Application Adapters

Developing OTDs for Communication Adapters

Developing OTDs for Database Adapters

Developing OTDs for Web Server Adapters

Designing with Application Adapters

Designing with Communication Adapters

Designing with Web Server Adapters

SWIFT Integration Projects

Java EE Based Components

Designing with Sun JCA Adapters

About the TCP/IP JCA Adapter

Defining Constants and Variables

Using Database Operations

Developing Sun Master Indexes

Using the JMS JCA Wizard

Using the JAXB Wizard and Code-Seeder Pallete

Master Index Update Policy Plug-ins (Repository)

For the primary transactions performed by the master index application, you can define additional custom processing to perform against the record that results from a transaction. The policies you define are invoked by the Update Manager and are applied to the resulting records after they are processed by the survivor calculator. The modifications made to a record by an update policy determine how the record is stored in the database. By creating custom plug-ins, you can create additional Java classes to support the update policies you define.

Update policies are specified in the UpdatePolicy section of the Best Record file, and there are several different types. Each policy modifies an enterprise object (class com.stc.eindex.objects.EnterpriseObject) and must implement com.stc.eindex.update.UpdatePolicy, which contains one method, applyUpdatePolicy. The syntax is as follows:

public EnterpriseObject applyUpdatePolicy(EnterpriseObject before, EnterpriseObject after)

This method throws two exceptions: com.stc.eindex.master.UserException and com.stc.eindex.objects.exception.ObjectException.

Enterprise Merge Policy

The enterprise merge policy defines additional processing to perform after two enterprise objects are merged. The processing defined in this policy acts against the surviving record of the merge. In the EnterpriseMergePolicy element in the Best Record file, enter the fully qualified name of this custom plug-in.

Enterprise Unmerge Policy

The enterprise unmerge policy defines additional processing to perform after an unmerge transaction occurs. The processing defined in this policy acts against the surviving record of the merge transaction that was unmerged. In the EnterpriseUnmergePolicy element of the Best Record file, enter the fully qualified name of this custom plug-in.

Enterprise Update Policy

The enterprise update policy defines additional processing to perform after a record is updated. In the EnterpriseUpdatePolicy element of the Best Record file, enter the fully qualified name of this custom plug-in.

Enterprise Create Policy

The enterprise create policy defines additional processing to perform after a new record is inserted into the master index database. In the EnterpriseCreatePolicy element of the Best Record file, enter the fully qualified name of this custom plug-in.

System Merge Policy

The system merge policy defines additional processing to perform after two system objects are merged. The processing defined in this file acts against the surviving enterprise record of the merge (and not the system record). In the SystemMergePolicy element of the Best Record file, enter the fully qualified name of this custom plug-in.

System Unmerge Policy

The system unmerge policy defines additional processing to perform after system objects are unmerged. The processing defined in this file acts against the surviving enterprise record of the system merge transaction that was unmerged. In the SystemUnmergePolicy element in the Best Record file, enter the fully qualified name of this custom plug-in.

Undo Assumed Match Policy

The undo assumed match policy defines additional processing to perform after an assumed match transaction is reversed. In the UndoAssumeMatchPolicy element in the Best Record file, enter the fully qualified name of this custom plug-in.