...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<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
I put this one here as a caution. Many operations in KFS have data side affects which you do not want to capture in your master data source. (Additionally, the Rice tables are missing from that schema, so it's not possible without setting up a separate Rice server.) You want to have precise control over what you are putting into the master data source.