After reading the release notes it states that if you already have VMware Update Manager installed in the same server you must change the Jetty SSL port from 8084 which is being used by VUM. I did as I was told and changed the port to 18084.
After opening vCenter and trying to enable the new plug-in you are faced with this error.
I added some firewall exceptions, but this did not help. I checked to make sure the Dell MD Storage Array VMware vCenter Application Service was started and it was.
Did some digging around in the jetty folder.C:\Program Files\Dell\MD Storage Array VMware vCenter Plug-In\jetty and found that although I have specified port 8088 during the setup the XML file, wsconfig.xml had the wrong port!!!
The fix was to stop the Dell MD Storage Array VMware vCenter Application Service service, correct the port number in my case 8088 and start the service once more. Sorted!
While you in that folder you might want to edit appserver64.ini and reduce the amount of RAM java will drink. Unless you have a large amount of arrays to monitor reduce this to 128MB's
#localize these lines (Items to the right have the =)
service.name=Dell MD Storage Array VMware vCenter Application Service
service.description=Dell MD Storage Array VMware vCenter Application Service
#Do not localize below this point
vmarg.1=-Dconfig.file=C:\Program Files\Dell\MD Storage Array VMware vCenter Plug-In\jetty\wsconfig.xml
vm.location=C:\Program Files\Dell\MD Storage Array VMware vCenter Plug-In\jre\bin\server\jvm.dll
Note if the service won't start you might need to remove and reinstall using another port number. You can use netstat -an | find ":portnumber" to see if a port is in use.