Adding corporate branding to meeting pages using Kubernetes

You can customize meetings to reflect your company's branding and visual presence.

About this task

You can include three levels of customizing for meetings to present a visual representation of your company. You can customize all three or any combination of the three.

Add a company logo. This image is displayed on the login, in-meeting, and logout pages.
Change the Favion and application icons.
Change the background image for meeting tile view.

Procedure

Locate and extract the branded_meetings_web.zip into the same directory where the sametime_meetings.zip file was extracted.
To obtain the branded_meetings_web.zip file, see the File "branded_meetings_web.zip" is required to add corporate branding to meeting pages knowledge article.
To add a logo, replace the branded-meetings-web/customImage.png file with your image file.
The image file can be any size. It is re-sized to approximately 260x260 pixels.
The name of the image file is supplied when performing the Docker build using the CUSTOMIZED_NAME build argument.
To update the favicon and app icons, replace the following files in the branded-meetings-web directory.
- favicon.ico
- sametime192X192.png
- sametime512x512.png
Keep the favicon.ico file to 64x64 for the best resolution. For the other two files, use the size indicated as part of the file name.
To add a custom background image, replace the branded-meetings-web/customBackground.png graphic file with your file.
Specify IN_MEETING_BACKGROUND=true build argument when you build the Docker image.

Build the Docker image.

Include the following build arguments, based on your changes.

CUSTOMIZED_NAME: The name of the logo file to be used.
IN_MEETING_BACKGROUND: Indicate whether in-meeting background is to be used.

docker build --build-arg BUILD_LEVEL=$(cat image-catalog.txt) \
  --build-arg CUSTOMIZED_NAME="my_custom_name" --build-arg IN_MEETING_BACKGROUND=true \
  -t branded-meetings-web:$(cat image-catalog.txt) branded-meetings-web

Update the container to incorporate your changes.
1. Edit the docker-compose.yml file and replace sametime-docker-prod.artifactory.cwp.pnp-hcl.com/meetings-web statement with the branded-meetings-web.
2. Run docker-compose up -d command to apply all changes. Include the required build arguments.

Tag and push the image to your private registry.


docker build --build-arg BUILD_LEVEL=$(cat image-catalog.txt) \
  --build-arg CUSTOMIZED_NAME="My Custom Name" --build-arg IN_MEETING_BACKGROUND=true \
  -t my-private-registry/branded-meetings-web:$(cat image-catalog.txt) branded-meetings-web
docker push my-private-registry/branded-meetings-web:$(cat image-catalog.txt)

Set the base name in the values.yaml file, which is in the helm directory.
```
web:
  baseName: branded-meetings
  fullnameOverride: web
  legacyLabels: true
```
where the branded-meetings is from the tag name that you created.
Apply the changes to your registry.
```
helm upgrade sametime-meetings helm/
```