Customizing › How to Customize XSL, XML, JavaScript, and Image Files

How to Customize XSL, XML, JavaScript, and Image Files

CA Service Catalog includes several hundred XSL, XML, JavaScript, and image files. Together, they are used to form every page and every page element in the product. Each file represents one page or a part of a page, such as a dialog, menu option, form field control, message, or picture.

Every file is named intuitively to illustrate its function. You can optionally customize any of these files to meet your requirements. To customize XSL, XML, JavaScript, and image files, follow this process:

1. Determine the specific page or part of a page that you want to customize.
2. Locate the file whose name matches the element you want to change. For example:
   • To modify the configuration information of any of the integrated products, locate the toolsconfig.xsl file.
   • To modify states of request lifecycle, locate the requestshared.xml file.
   • To modify the messages that appear when a user tests the connection for a new administration configuration setting, locate the toolsconfig.js and toolsconfig.xsl files.
   • To modify the edit button of the Administration, Configuration page, locate the modify.gif and toolsconfig.xsl files.
   • Modify the request status list by editing the requeststatus.xml file.

   Note: For information about customizing forms using Javascript and other methods, see the Administrator Guide.

3. Open the file, review its contents, and verify that it controls the element or behavior that you want to change.
4. Using the table at the end of these steps as a reference, copy the file from its original location to the custom location.
5. Modify the file to meet your requirements.
6. If you customized a JavaScript or image file, perform this step; otherwise, skip it.
   1. Copy the customized JavaScript file to the \FileStore\custom\explorer\scripts folder.
   2. Copy the customized images to the \FileStore\custom\images folder.
   3. Locate the XSL file in the custom location in which the JavaScript or image file is used.
   4. Update this XSL file to specify the new custom path name of the JavaScript or image file. To do so, prepend "FileStore/" to the relative path of the JavaScript or image file. Use the following example as a model:

         <script src="FileStore/custom/explorer/scripts/custom_form_example.js"></script>
      

      This action is required because the XSL file references the filestore location for the customized script files.

   Important! If you are using multiple Service View computers, verify that the filestore is shared among all of them.

7. Clear the %USM_HOME%\view\translets folder on all Service View computers: Delete all files in this folder, but do not delete the folder itself.
8. Restart all Service View computers.
9. Verify that the changes are working in CA Service Catalog as you intended.

In the following table, the parent folder is %USM_HOME%/view/webapps/usm. The filestore folder is %USM_HOME/filestore. The folder entries, such as /explorer and /custom/explorer, are subfolders under the parent and filestore folders.

*The folder name icusen applies to English-language implementations only. If you are using a non-English implementation, your locale-specific folder name is different. In such cases, use your locale-specific folder name instead of icusen.