Stop operation through Application Engine script instead of EPM Administration

mis-regiobus

Hi everybody,

does anyone know of a way to stop operations through Application Engine? So far, we experience frequent long lasting operations, often blocking other users from using the system, including dashboards (504 error). As there is no functionality to set a time out period for operations (so far, road map lists this for 2025.10 release), we would like to find a way to stop operations through an Application Engine script. We are able to detect long lasting operations through the SQL databases, but lack a way to stop said operations automatically. Rather, we have to manually stop them through the EPM administration.

Best regards,

Jan

David Swinburne

Hi Jan,

The OLAP Server XML API provides a method to stop long lasting operations on the OLAP Server

Database StopTask

Stops a task.

Request

<Alea:Document xmlns:Alea="<a href="http://www.misag.com">">http://www.misag.com"></a>
  <Alea:Request RequestID="01" Class="Database" Method="StopTask">
    <Alea:User UserId="1"/>
  </Alea:Request>
</Alea:Document>

The method can be encapuslated in a string in BI# and called from Application Engine using the  XMLAExecuteXml function, e.g. 

#define EngineVersion 5.0
#define RuntimeVersion 5.0

void StopTask(string Database, string UserId)
@Description: "Stop Task    ";
@Category: "OLAP Rule Profiling";
@Parameter[Database]: "Target Database";
@Parameter[UserId]: "Target User Task";
@Returns: "void";
{
    string errorMessage = "";
    int errorCode = 0;


    try {

        string olapConnectionString = Database;

        XMLAConnection xmlaOLAPConnection =XMLACreateNamedConnection(olapConnectionString);

        string XMLStopTask= ""+
            "<Alea:Document xmlns:Alea=""+">http://www.misag.com">"+
            "  <Alea:Request RequestID="1" Class="Database" Method="StopTask">"+
            "   <Alea:User UserId=""+UserId+""/>"+
            "  </Alea:Request>"+
            "</Alea:Document>"
            ;

        string XMLResponse=XMLAExecuteXml(xmlaOLAPConnection , XMLStopTask);

        XMLADisconnect(xmlaOLAPConnection);


    } catch  ( errorMessage, errorCode) {
        NotifyInformation(errorMessage+" "+errorCode);

    }
}

UserId can be identified by calling the GetUserList Database method.

Terminating a long lasting operation without understanding the root cause carries risk as I am sure you are aware.

I would recommend focussing on the root cause of the long lasting operation and addressing the issues associated with it rather than routinely cancelling errant tasks. 

Regards

Dave