ESI Tool question
When we create an Event Source Package, it creates the ini, txt files, etc. It also creates a vbs script. Once the vbs script is run, is the new event source supposed to be included in the "Manage Device Types" window (after restarting all services)? Or is there something else that needs to be done to get a new syslog event source included?
I have created an xml file from a lsdata-retrieved .unx file, all messages are parsed, no vaildation errors, but nothing once installed on the system.
You must first create a a new folder with the name of the event source (the one you used when you started EventSource Integrator) in the ..etc\devices directory, . No spaces, suffix, prefix. The *.zip package goes there, then expand it and then double-click the UpdateESType.vbs file.
Glad to see you're using the shiny new tool!
Point of clarification...
You state: "You must first create a a new folder with the name of the event source (the one you used when you started EventSource Integrator) in the ..etc\devices directory,"
Where in the ESI tool do we specify the name of the event source? We are asked to specify the name of the XML file, and the directory to place it, but not the name itself. Am I to asuume that the event source name is whatever I entered for the XML file without the msg at the end? Or is it the name of the directory I placed the XML file in?
For example, I named the XML WebDefendmsg, and I placed it in a directory called WebDefend, and I copied the package to ..etc\devices\WebDefend and ran the vbs script.
Am I doing it wrong? The tool says there are no vaildation errors, and all events from a 8000 + line .unx file are parsed.
Thanks in advance,
Kent, I assume you have unzipped all the files in ..etc\devices\WebDefend folder on enVision appliance? Once you have done that execute .vbs script (double click). After 30 seconds or so you will receive a poopup telling dtype number is updated. This script is pretty simple, it just updates the dtype number in .ini files (by scanning through all available event sources to make sure it finds the next available unique number). Lot of this information is also provided in overview guide as well as online help. Have you had a chance to go through that yet?
I would use the approved method of creating the script package and using the VBS script. That is how the product is designed to work. However, I have also done it "old school". Use ESI to create the XML, then use UDS on the server to create the event source. Replace the UDS created xml file with the ESI created one and the results should be the same.
Yes, I read the admin guide and followed the directions.
Again, here is exactly what I did:
1)unzipped the contents of the zip file to ../etc/devices/WebDefend
Here are the contents:
2) Ran the vbs script.
Message popped up that it had assigned # 513 to the device.
3) Deleted the old device that was listed as "unknown"
4) Restarted all services.
5) Waited for device to be created under "Manage Device Type" It never does.
6) Eventually device is re-discovered as "unknown" again.
We also tried to create a new device using an existing configuration by changing the name in the ini file, and putting it in a new folder, and no device was created either.
Are we missing a step? How is the device created so that we can see it in the "manage Device Type" window?? Not by the vbs script.
I have attached our zip file for you to look at.