Ok..One additional information and important one which I missed:
Since summer 2007, VMPerl 3.1.0 is no more available.
Only VMPerl 2.3.2 is available.
For using this version, 3 steps must be do :
1/ install the API in the directory <TD>\etc\action_util\VMPerl\3.1.0
2/ in scripts getserver.pl and getvm.pl, lines 5, 6 and 7 replace \ by /, in script getinfo.pl, lines 17, 18 and 19 replace \ by /
3/ in the 3 scripts replace Code:
#my $port = 902;
my $port = 0;
Also, please note:If you are discovering only ESX servers, it's better to use the VirtualCenter method rather than the VMWare API.
Indeed, you can discover the ESX 3.x servers using the Virtual Center method with ESX credentials only (not using Virtual Center credentials). There is no need to actually have Virtual Center: you can discover ESX directly through the VMWare Infrastructure API.
If you need to discover GSX servers or the VMWare Console (older 1.x and 2.x technology), then you can use the VMPerl API method (follow Alok's suggestion above). Please note, however, that you can also use Virtual Center to manage GSX servers – and then use the VMWare Infrastructure API (Virtual Center method)to discover GSX through the Virtual Center.
Hope this helps.
Has BMC formally addressed this problem? Seems that to put instructions in the FD/TD install guide to download an API that is no longer supported by its own vendor is a big issue. What is the correct way to go forward with this?
In the next release installation guide you should be able to find the changes.