Promoting MCOs to Implemented State

Business Administrators can set the system to automatically promote MCOs that are at the Release state to the Implemented state when they reach their start dates. The following two steps are needed to promote MCOs to the Implemented state:

This page discusses:

Configure the Timer Servlet

The timer servlet allows a command to be executed at a specified interval

It uses the following properties in the web.xml file:

ematrix.timer.agent--The user name for the context that executes the command. User privileges can be handled internally in the program.

ematrix.timer.agent.key--The password for the user. User privileges can be handled internally in the program.

ematrix.timer.interval--The elapsed time, in seconds, between execution of the command.

ematrix.timer.command--The command to run. If you are using the AEF, use the command shown in the example below.

To use one or more of the properties, add them to the properties file before you run the warutil.

Following is an example of the properties with sample values:

<context-param id="ContextParam_15">

<param-name>ematrix.timer.agent</param-name>

<param-value></param-value>

</context-param>

<context-param id="ContextParam_16">

<param-name>ematrix.timer.agent.key</param-name>

<param-value></param-value>

</context-param>

<context-param id="ContextParam_17">

<param-name>ematrix.timer.interval</param-name>

<param-value>21600</param-value>

</context-param>

<context-param id="ContextParam_18">

<param-name>ematrix.timer.command</param-name>

<param-value>execute program emxProjectSpace -method 

performTaskEscalation</param-value>

</context-param>

Write the JPO

You can write a simple JPO method that finds all MCOs in the Release state with the start date <= the system date. You can map this JPO method in web.xml.