Keeper integration via MID Server

[Praful_1968]

var name = "Test";

var server = "Keeper";

var command = 'keeper record-add --title Sample Login --record-type login --folder XXXXXXXXXXXX login= password=$GEN url=https://www.google.com "License ID"="9ACB123" url.AlternateURL=https://amazon.com';

var ecc_queue = new GlideRecord("ecc_queue");

ecc_queue.initialize();

ecc_queue.agent = "mid.server." + server;

ecc_queue.name = name;

ecc_queue.queue = "output";

ecc_queue.topic = "Command";

ecc_queue.payload = '<?xml version="1.0" encoding="UTF-8"?><parameters><parameter> name="name" value="' + command + '"</parameter></parameters>';

// Get SysID of new ECC Queue record

var ecc_sysid = ecc_queue.insert();

// Set Response to current record sys_id

ecc_queue.response_to = ecc_sysid;

// Update new ECC Queue record

ecc_queue.update();

I'm executing the above script which executes a keeper(third party system) CLI command via MID Server. A output queue gets created, but it stays in ready state. No, input queue is generated for that. Following command works fine though:

var command = "keeper msp-info";

Any help is really appreaciated. 

[marcguegueniat]

Hello,

Feels like no MID server is taking the job

You should double check the name of the agent you put in ecc_queue.agent = "mid.server." + server;

If unsure of what to put, create a random rest message and add your mid server, launch and see the resulting ecc queue.

If the job is taken but nothing happen, it might be an issue in the MID.

You can set the MID server's log level to DEBUG and then look if anything happens inside the MID logs.

Regards