Page Comparison

...

Part of this will involve updating the master datasource. More on that is described in OLE Database Master Data Source Management Process. But, I will refer to that master datasource here as OLEDBA. (Happens to be the name of the Oracle database schema.)

...

For more complex data updates (such as entering documents which have many affected tables), you can dedicate a (or bring up a special) test environment for the data entry. Then, bring down the instance and extract the updated data using a database tool. You then replay that data into the OLEDBA schema.

The trick with this option is identifying all the changes you want to extract. This is a place that the impex tool could help. Take an export of the database after the data entry into a new directory. Then, compare that to the baseline export from subversion. The data files which have been changed will tell you which tables were updated. This will probably still require some manual filtering out of the "noise" tables, but will definitely show you every table which was modified.

Option 3 - Special Batch Jobs to Load Data

...

As an example, the configuration below is in spring-test-env-beans.xml, a special spring file which is only included in testing environments. It defines a new job with a trigger that runs it 5 minutes after server startup.

    <bean id="purapModuleConfiguration" parent="purapModuleConfiguration-parentBean">
   		<property name="jobNames">
			<list merge="true">
				<value>purapMassRequisitionJob</value>
			</list>
		</property>
		<property name="triggerNames">
			<list merge="true">
				<value>purapMassRequisitionJobTrigger</value>
			</list>
		</property>    
    </bean>
	
    <bean id="purapMassRequisitionStep" class="org.kuali.kfs.module.purap.batch.PurapMassRequisitionStep" parent="step">
	    <property name="documentService" ref="documentService" />
	    <property name="requisitionService" ref="requisitionService" />
	    <property name="purapService" ref="purapService" />
	    <property name="boService" ref="businessObjectService" />
	    <property name="psService" ref="persistenceStructureService" />
    </bean>
    
	<bean id="purapMassRequisitionJob" parent="scheduledJobDescriptor">
		<property name="steps">
			<list>
				<ref bean="purapMassRequisitionStep" />
			</list>
		</property>
	</bean>
	
	<bean id="purapMassRequisitionJobTrigger" parent="simpleTrigger">
		<property name="jobName" value="purapMassRequisitionJob" />
        <property name="startDelay" value="300000" />
        <property name="repeatCount" value="0" />
	</bean>

Non-Option 4 - DON'T TO THIS - Point an instance to OLEDBA

...