Cisco Cisco Prime Service Catalog 10.0 Referências técnicas

Custom styles allow designers to customize Service Catalog web pages, headers and footer. Custom 
styles may be applied to all users of an application instance, or different styles may be applied to users 
based on their home organizational unit.

You must have access to the file system of the application server, specifically to the “custom” 
directory of the RequestCenter.war archive and its subdirectories. You need both read and write 
access to this directory and to its subdirectories. 

You must have a user role which includes the Administration capability to “Manage Global Settings” 
in order to turn on or off the use of custom style sheets, headers, and footers.

Browser page caching must be turned off in order for you to test style sheet changes.

Ideally, you should have access to an application instance where you can test your changes without 
disturbing the work of other analysts or developers.

A style sheet editor and other editing tools are highly recommended, but not required.

The procedure below gives the basic steps to follow in order to customize the appearance of styles used 
in the built-in modules, namely My Services, Service Catalog, Service Manager, and Reporting. 
Additional details on these styles are given in the following sections.

Create a directory on the application server, under the RequestCenter.war/custom directory, where 
the files required for the custom styles will reside. The directory will typically have an images 
subdirectory, for any custom images. The directory name should indicate the tenant/organization 
name to which the styles will apply.

If you use the Service Catalog module as the end user module, copy all the files located in the 
custom/ServiceCatalogExamples directory into the new directory created in Step 1. If you use My 
Services module, copy all the files located in the custom/CustomExamples instead. Location of this 
archive will vary, based on your application server and installation setting.

In the new directory, remove the "example_" prefix of files in the directory as well as in the 
application directory under it. Modify the css files and add image files as needed to tailor the look 
and feel of the user interface as needed.

Use the Custom Styles page in the Administration module to define the style, specify the directory 
on which required files reside, and assign the organizations to which the style applies.

Use the Settings page in the Administration module to turn on custom stylesheets. 

Restart the browser session of Service Catalog—the pages should appear with the customizations 
applicable to the logged in user. You must exit and restart the Service Catalog session when custom 
stylesheets are initially activated. To test subsequent changes to the styles, it is sufficient to copy the 
revised style sheet to the application server and refresh the current page. The new styles will be 
applied, provided page caching is not in effect.

Once you change the Administration Settings to use custom stylesheets, the custom.css file should be 
present on the specified directory. If the file is not present, Service Catalog will use its standard styles. 
Similarly, if the option to use a custom header or footer is turned on, the corresponding files must be 
present on the specified directory.