Hi, we have a requirement to create a tool that will invoke javascript but also need it to execute SQL as well. We cannot seem to get this to work. 

Example 

script(foreach="true",language="JavaScript")
  {

some code 

if (x=1) {

}

else {

sql(foreach="true",url="$(SERVER)/_tb37b/ael/Tool/Controller")
  {
    structure
    {
      text(data="update alerts.status set Location='")
      variable(name="username")
      text(data=");\u000d\n")
    }
  }

}

Any ideas on how we can get the above to work? 

And once this is created manually, it can't be pulled in via the Dash Admin Tools function and edited because it will only save the SQL or Javascript part, depending on what tab is open when you click save. 

Hi Prem,

tools are either/or - you can't combine SQL and Javascript.

And given that the javascript-Tool runs in the user's browser, it doesn't have any access to the ObjectServer.

Not sure what you need to achieve - if you need javascript functions in the user's browser and want to modify the event, then one way I can think of is to launch a cgi-script from the javascript-Tool. The cgi then could modify the event via nco_sql. Not at all ideal, but would work.

If you just need to run different SQLs based on a variable x, consider adding the variable to the update's where clause (I'm using Severity instead of your x in the example):

update alerts.status set Location='%username' where Serial in ( $selected_rows.Serial ) and Severity < 3;
update alerts.status set Customer='%username' where Serial in ( $selected_rows.Serial ) and Severity >=3;

If you need the user to enter the "x" value you can even use a prompt to retrieve the info from the user.

HTH,

Michael

or you could your code in an impact policy 
do your javascript and then do a eventenrichment in the same policy

and have a simple http call to to restapi to launch it..
https://www.ibm.com/docs/en/tivoli-netcoolimpact/7.1.0?topic=servers-accessing-policies-remotely-using-rest-api

if you have impact that is :-)

Saury.  its a webgui question  :-)  so no aiops..  but NOI

Hi Prem,

This issue is that the Web GUI Tool definition doesn't support nesting an sql block directly inside a script block like that. The Tool Editor forces you to choose a single type (Script, SQL, CGI, etc.), which is why it strips out the 'other' part when you save.

To get this to work, you should create a Script Tool (pure JavaScript) and use an AJAX request to execute the SQL update when your condition is met. You can do this by calling the ObjectServer REST API (OSLC) or the internal standard REST interface.

Here is an example of how to structure the Script Tool to do this:

// 1. Perform your Client-Side Logic
var x = 1; // Your logic here
var serial = row.Serial; // Get data from the selected row

if (x == 1) {
    // Do nothing or handle the 'if' case
    console.log("Condition met, no update needed.");
} 
else {
    // 2. Prepare the SQL Update payload
    // Note: You typically use the OSLC/REST interface for this.
    // This example uses a standard XMLHttpRequest to hit the ObjectServer REST API
    
    var updateUrl = "/objectserver/restapi/alerts/status/" + serial;
    var payload = {
        "Location": username // Assuming 'username' is a variable you have defined
    };

    var xhr = new XMLHttpRequest();
    xhr.open("PATCH", updateUrl, true);
    xhr.setRequestHeader("Content-Type", "application/json");
    
    xhr.onreadystatechange = function() {
        if (xhr.readyState === 4) {
            if (xhr.status === 200 || xhr.status === 204) {
                alert("Update successful");
            } else {
                alert("Error updating: " + xhr.statusText);
            }
        }
    };
    
    xhr.send(JSON.stringify(payload));
}

In Dash Webgui you cannot reliably mix JavaScript and SQL in the same tool block, which is why one part gets overwritten when saving. The recommended approach is to move the SQL logic to a server side controller or API and call it from JavaScript using an HTTP or AJAX request. Keep your conditional logic in JavaScript and trigger the SQL execution through the endpoint only when needed. This also ensures the tool can be safely edited and saved through Dash Admin Tools without losing code.

To make your script work, try separating the JavaScript and SQL execution logic: use JavaScript to handle conditions and PNW Prestige Exteriors then send an AJAX request to the server to execute the SQL query. This way, both parts will work together, and you can avoid issues with saving the script in Dash Admin Tools by treating them as distinct client-side and server-side components.