/mcpRestart the Tomcat Service You must restart the Cisco Tomcat service for the branding updates to reflect in the Self-Care Portal. Before you begin Make sure that you have completed the following: • To append your logo to the Self-Care Portal, you must first enable branding in Cisco Unified Communications Manager. The branding.zip upload file must include a 44x25 pixel branding_logo.png file with your company logo. For details, Enable Branding, on page 592. • To remove your logo from the Self-Care Portal, you must disable branding in Cisco Unified Communications Manager. For details, Disable Branding , on page 593. Procedure Step 1 Log in to the Command Line Interface. Step 2 Run the utils service restart Cisco Tomcat CLI command. Step 3 Repeat this procedure on all Cisco Unified Communications Manager cluster nodes. What to do next After the service restarts, refresh your browser to see the changes in the Self-Care Portal. Branding File Requirements Before you apply customized branding to your system, create your branding.zip file according to the prescribed specifications. On a remote server, create a Branding folder and fill the folder with the specified contents. Once you have added all the image files and subfolders, zip the entire folder and save the file as branding.zip. There are two options for the folder structure, depending on whether you want to use a single image for the header or a combination of six images in order to create a graded effect for the header. Table 52: Folder Structure Options Folder Structure Branding Option If you want a single image for the header background (callout item 3), your branding folder must contain the following subfolders and image files: Branding (folder) ccmadmin (folder) BrandingProperties.properties (properties file) brandingHeader.gif (20481 pixel image) ciscoLogo12pxMargin.gif (4444 pixel image) branding_logo.png (44*25 pixel image) Single Header Option Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 594 Custom Features Restart the Tomcat Service