Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vCloud Director does not recognize the new Client Integration Plugin for vCenter 6.0p07 (U3g) (56623)

Last Updated: 1/24/2019Categories: TroubleshootingTotal Views: 3749Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

If vCloud Director users upgrade to 60p07 (U3g) VMware Client Integration Plugin, the plugin will not get recognized by the vCloud Director Flex UI.
This occurs irrespective of whether vCenter Server is upgraded to 60p07 or not.

This behaviour occurs because VMware Client Integration Plugin in 60p07 is split into the Client integration plugin (CIP) and VMware Plugin-Service which introduces changes to the JavaScript API.
These changes are currently not present in the versions of the files that vCloud Director is using.

Solution

If you have already installed the 6.0p07 (U3g) Client Integration Plugin, you can follow one of two routes:

Uninstall the Client Integration Plugin, and Install an earlier version of the  Plugin

Implement the Workaround below

Workaround
vCloud Director requires files to be replaced on all vCloud Director Cells to facilitate changes to the JavaScript API required for Integration with the 6.0p07 (U3g) Client Integration Plugin.

The files you are replacing vCloud Director files are generated at Service Startup.
If you restart the vCloud Director Service, the changes above would need to be implemented again.

This has been resolved in the latest releases of vCloud Director 8.20.0.3 and 9.0.0.3

vCloud Director 8.20.0.3 Download

vCloud Director 9.0.0.3 Download

The latest Client Integration Plugins can be obtained from KB Article 2145401.

Steps

Take a backup of the contents of the directory /opt/vmware/vcloud-director/tmp/jetty-cloud***.osgi/support/javascript/assets/

Delete the content of the directory /opt/vmware/vcloud-director/tmp/jetty-cloud***.osgi/support/javascript/assets/

Extract the JavaScript (.js) files from the attached VMware-csd-js-api.zip to /opt/vmware/vcloud-director/tmp/jetty-cloud***.osgi/support/javascript/assets/

Ensure all Files are owned by vCloud, and vCloud is the only user with Read/Write access (0600) i.e. -rw-------. 1 vcloud vcloud

Close and re-open any vCloud Director Flex UI sessions

Now when you close the browser and access the vCloud Director Flex UI again the new Client Integration Plugin will be recognized.

Note:
If you are accessing vCloud Director via Proxy, you will need to follow the additional steps below.

Additional Steps if Accessing vCloud Director via Proxy

Open the Browser Proxy Settings

Navigate to the Exceptions section

In the 'Do not user proxy server for addresses beginning with' text box, place the text 'vmware-plugin'.

Press OK

See the screenshot below:

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

VMware-csd-js-api.zip

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant