using the mid.jar MANIFEST.MF build details to get the actual ServiceNow version?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
Hi,
We face a challenge with instance upgrades (full and patch) and our CyberArk (CP) integrations. The CyberArk Hash value for mid.jar changes with each version.
We have semi-automated the generation of the Hash value as follows:
- Download the new version of the MID Server Agent zip file from install.service-now.com to the MID Server host (using the build date and tag information)
- Extract the contents of the zip file into a temporary directory
- from the instance (via a custom widget and using a custom flow / powershell), execute the Cyberark Hash utility against extracted mid.jar file
- this will return the hash value and get the package.filename value from agent\packaage\meta\mid-core.meta.properties
I'd like to get to the stage where we only extract the mid.jar file and determine the ServiceNow version from mid.jar. The issue is I cannot find the "friendly" ServiceNow version from the mid.var file. I can get the build info from the manifest file, but have no idea how to get the ServiceNow version from that
- Is anyone aware how to use the MANIFEST.MF (\agent\lib\mid.jar\META-INF\) information in the JAR file to get the ServiceNow version?
- is there anything else in mid.jar that can be used to get the version?
thanks,
Steve
0 REPLIES 0
