ESI 1.1.1 - redeploying/updating an existing ESI device

[RSAAdmin]

I was able to successfully deploy a new device several weeks ago using the DeployEventSourceSetup.vbs and restarting services, etc. However, after adding several more message Ids to the xml, repackaging the zip, and attempting to deploy, the xml under etc/devices/deviceName is not getting updated.

We have an LS test and prod env, so deployment from just the Asrv would be nice. I see a esiupdatelog.log in the logs directory with the following timely contents on each appliance:

INFO  09 03 2011 14:21:04,731 %NIC-6-701000: AutomaticUpdate, AutoUpdateMain, -, package, 2011039-141431, Detail: 1: 2011/03/09 14:21:04, Automatic update started.
INFO  09 03 2011 14:21:04,872 %NIC-6-701002: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/deviceName_2011039-141431, Detail: 1: date_time: 2011/03/09 14:21:04, package_id: 2011039-141431, patch_id: deviceName_2011039-141431, started.
WARN  09 03 2011 14:21:04,872 %NIC-4-701009: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/deviceName_2011039-141431, Detail: 1: package_id: 2011039-141431, patch_id: deviceName_2011039-141431, patch already applied.
INFO  09 03 2011 14:21:04,872 %NIC-6-701002: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/service_2011039-141431, Detail: 1: date_time: 2011/03/09 14:21:04, package_id: 2011039-141431, patch_id: service_2011039-141431, started.
INFO  09 03 2011 14:21:15,294 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Alerter stopped.
INFO  09 03 2011 14:21:25,606 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC App Server stopped.
INFO  09 03 2011 14:21:25,903 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Collector stopped.
INFO  09 03 2011 14:21:26,185 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Locator stopped.
INFO  09 03 2011 14:21:26,481 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Logger stopped.
INFO  09 03 2011 14:21:26,763 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Packager stopped.
INFO  09 03 2011 14:21:27,044 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Server stopped.
INFO  09 03 2011 14:21:38,685 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Web Server stopped.
INFO  09 03 2011 14:21:49,013 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Service Manager stopped.
INFO  09 03 2011 14:21:59,200 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: Sleep for some seconds.
INFO  09 03 2011 14:22:09,575 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Service Manager started.
INFO  09 03 2011 14:22:09,575 %NIC-6-701003: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/service_2011039-141431, Detail: 1: date_time: 2011/03/09 14:22:09, package_id: 2011039-141431, patch_id: service_2011039-141431, completed successfully.
INFO  09 03 2011 14:22:09,575 %NIC-6-701001: AutomaticUpdate, AutoUpdateMain, -, package, 2011039-141431, Detail: 1: 2011/03/09 14:22:09, Automatic update completed.
 

So from the warning, it looks like the script thinks it has the same version or has already updated? Can I not update an existing device created with the ESI tool using the vbs script? Did I miss something in the overveiw or help? From the overview, it sounds like it should have work. Thanks!

[RobertWengewicz]

You should be able to just manually copy the XML over and place into the folder if you only changed some messages. I think there is a bug in the ESI tool regarding deployment as I created a new device and the script would not install it I manually copied it over and gave it a device number. I have no issues with the device.

Bob

[RSAAdmin]

Yes, I went ahead and copied the xml to each appliance, but also assuming that eventually the tool will update and replicate across the whole domain. At least I know I'm getting the same results as others. Thanks! 

[RSAAdmin]

If you add couple of more rule/definition in existing device using ESI and and generate a zip package using ESI , and then redeploy it in enVision using DeployEventSourceSetup.vbs ( Please follow instruction from ESI online help) , it should update device on all site for you automatically. But if you are  doing manual copy of updated xml on one site, it will not replicate updated xml to other sites.

[RobertWengewicz]

But the issue is that the ESI tool is NOT pushing the devices correctly. Doesn't matter if it is a update or a new device the script will not push the device so you are forced to manually do this. When I was on with support they made a note of it but I am not sure it went any further then that. It sounds like there is a bug in the program as there are more people with the same issue. Yes you can do the work around by copying the xml to the appliances but that is defeating the purpose of the script.

Bob

[RSAAdmin]

If this issue is not resolved, Please file the bug  with all details and we will have a look.

[RSAAdmin]

not sure if you have tried this, but I had the same issue until I was told by the RSA support desk how to do it correctly.  The doco is not specific enough.

what I had to do was unzip the ESI package to "e:\nic\4000\xxx-ES\update"  and then run the deploy..vbs.

What i was doing was unzipping it to "e:\nic\4000\xxx-ES\update\new_device" and it was failing.  I had to delete (backup) the contents of the .\update folder and extract the new device to the .\update folder NOT to .\update\new_device\

anyway, this worked for me..