The following information provides answers to frequently asked questions and includes instructions for managing your catalog content:
Content is modified using the standard Service Builder component of the web browser user interface.
It is strongly suggested that you back up any customized content you have created before and after making changes; use the IXUTIL utility to back up.
Bulk changes to the catalog can be done by exporting the catalog folder or offering to be changed using the IXUTIL utility, editing the exported XML file using a text editor, and then deleting and re-importing the folder into the catalog. This works very well for simple changes in descriptions and naming conventions. For example, if your IT organization were named GIS (General Information Services) you might want to do a bulk change to replace the word "IT" with "GIS" within the catalog.
If you are not familiar with using a text editor for editing XML files, you should get advice from someone with experience. Be especially careful to use a text editor like Notepad, not a word processor like Microsoft Word.
The user is advised to be very careful and take several backups. Due to referential integrity issues, the import may not always import everything. Carefully review the ixutil.log in the %USM_HOME%\logs\install folder after each import to check for duplicate name errors as well as errors caused by syntax errors in the imported data.
It is strongly suggested that you make all changes to catalog content in a test catalog, take a backup, and then load the updated catalog content into your production catalog.
The two entities included in your catalog are the catalog entries themselves and the images and URL links associated with them.
The first step is to use the IXUTIL utility to export the catalog entries from the test catalog.
The next step is to use the IXUTIL utility to import the catalog entries to the production catalog.
This only copies catalog entries (folders, services, service option groups and service option elements) from test to production.
Images, Category/Class/Subclass definitions (category.xml), and state definitions must be copied to the production environment separately.
| Copyright © 2010 CA. All rights reserved. | Email CA Technologies about this topic |