As a Ops Manager operator, you can brand Apps Manager by changing certain text, colors, and images on the interface. Developers see the customized interface when logging in, creating an account, resetting a password, or using Apps Manager.

Operators customize Apps Manager by configuring the Custom Branding and Apps Manager Config pages of the VMware Tanzu Application Service for VMs (TAS for VMs) tile.

Custom Branding Pane

To customize your Apps Manager interface:

  1. In a browser, go to the fully-qualified domain name (FQDN) of your Ops Manager deployment and log in.

  2. Click the TAS for VMs tile.

  3. Select Custom Branding.

  4. For Company name, enter the name of your organization. If left blank, the name defaults to VMware.

  5. For Accent color, enter the hexadecimal code for the color used to accent various visual elements, such as the currently selected space in the sidebar. For example, #71ffda.

  6. For Main logo, enter a Base64-encoded URL string for a PNG image, leaving out the mime-type (data:image/png;base64,), to use as your main logo. The image can be square or wide. If left blank, the image defaults to the VMware logo.

  7. For Square logo, enter a Base64-encoded URL string for a PNG image, leaving out the mime-type (data:image/png;base64,), to use in the Apps Manager header and in places that require a smaller logo. If left blank, the image defaults to the VMware logo.

  8. For Favicon, enter a Base64-encoded URL string for a PNG image, leaving out the mime-type (data:image/png;base64,), to use as your favicon. If left blank, the image defaults to the VMware logo.

  9. For Footer text, enter a string to be displayed as the footer. If left blank, the footer text defaults to VMware Software, Inc; All rights reserved.

  10. To add up to three footer links that appear to the right of the footer text:

    • Click Add.
    • For Link text, enter a label for the link.
    • For URL, enter an external or relative URL. For example, https://docs.vmware.com/ or /tools.html.

  11. For special notification purposes such as governmental or restricted usage, use the Classification fields to create a special header and footer:

    • For Classification header and footer background color, enter the hexadecimal code for the desired background color of the header and footer.
    • For Classification header and footer text color, enter the hexadecimal code for the desired color of header and footer text.
    • For Classification header content, enter content for the header in either plain text or HTML. If you enter HTML content, eliminate white spaces and new lines. If you do not provide any content, the custom header does not appear.
    • For Classification footer content, enter content for the footer in either plain text or HTML. If you enter HTML content, eliminate white spaces and new lines. If you do not provide any content, the custom footer does not appear. The Classification footer appears below the normal footer, which you can customize in the Footer text and Footer links fields.

    Note: The header and footer do not appear on the UAA login page.

Apps Manager Pane

To continue customizing your Apps Manager interface:

  1. In a browser, go to the FQDN of your Ops Manager and log in.

  2. Click the TAS for VMs tile.

  3. Select Apps Manager.

  4. For Product name, enter text to replace Apps Manager in the header and the title of Apps Manager. This text defaults to Apps Manager if left blank.

  5. For Marketplace name, enter text to replace the header in the Marketplace pages. This text defaults to Marketplace if left blank.

  6. By default, Apps Manager includes three secondary navigation links: Marketplace, Docs, and Tools. You can edit existing secondary navigation links by clicking the name of the link and editing the Link text and URL fields. You can also remove the link by clicking the trash icon next to its name. If you want to add a new secondary navigation link, click Add and complete the Link text and URL fields.

    Note: Removing any of the default links will remove them from the secondary navigation for all users.

  7. For Apps Manager Buildpack, enter a static content-compatible buildpack you want TAS for VMs to use when deploying the Apps Manager app. By default, this is staticfile_buildpack.

  8. For Search Server Buildpack, enter a Node.js-compatible buildpack you want TAS for VMs to use when deploying the Search Server app. By default, this is nodejs_buildpack.

  9. For Invitations Buildpack, enter a Node.js-compatible buildpack you want TAS for VMs to use when deploying the Invitations app. By default, this is nodejs_buildpack.

  10. (Optional) Enter in MB your desired Apps Manager memory usage. The minimum number you can enter is 128. Leave this field blank to use the default value of 128 MB.

  11. (Optional) Enter in MB your desired Search Server memory usage. This is the memory limit used to deploy the Search Server app. The minimum number you can enter is 256. Leave this field blank to use the default value of 256 MB.

  12. (Optional) Enter in MB your desired Invitations memory usage. This is the memory limit used to deploy the Invitations app. The minimum number you can enter is 256. Leave this field blank to use the default value of 256 MB.

  13. The Apps Manager polling interval field provides a temporary fix if Apps Manager usage degrades Cloud Controller response times. In this case, you can use this field to reduce the load on the Cloud Controller and ensure Apps Manager remains available while you troubleshoot the Cloud Controller. VMware recommends that you do not keep this field modified as a long-term fix because it can degrade Apps Manager performance. Optionally, you can:

    • Increase the polling interval above the default of 30 seconds.

      Note: If you enter a value between 0 and 30, the field is automatically set to 30.

    • Disable polling by entering 0. This stops Apps Manager from refreshing data automatically, but users can update displayed data by reloading Apps Manager manually.

    VMware recommends that you do not keep this field modified as a long term fix because it can degrade Apps Manager performance.

    Optionally, you can:

  14. Increase the polling interval to the default of 30 seconds.

    If you enter a value between 0 and 30, the field is automatically set to 30.

    • Deactivate polling by entering 0. This stops Apps Manager from refreshing data automatically, but you can update displayed data by reloading Apps Manager manually.

  15. The App details polling interval field provides an additional way to reduce the load on the Cloud Controller when the Apps Manager polling interval field is not sufficient. This field controls the rate at which Apps Manager polls for data when a user views the Overview page of an app.

    VMware recommends that you do not keep this field modified as a long term fix because it can degrade Apps Manager performance.

    Optionally, you can:

  16. Increase the polling interval to the default of 10 seconds. If you enter a value between 0 and 30, the field is automatically set to 10.

    • Deactivate polling by entering 0. This stops Apps Manager from refreshing data automatically, but you can update displayed data by reloading Apps Manager manually.
check-circle-line exclamation-circle-line close-line
Scroll to top icon