Cisco Cisco Prime Service Catalog 10.0 Technical References

Turning on custom style sheets and headers and footers is just the first step to configuring a customized 
appearance for the web pages. Administrators need to design the styles to be used, upload appropriate 
files to the application server, and use the  option of Administration to associate styles with the site or 
with specific organizations within the site. 

Turning on directory integration is just the first step to integrating Service Catalog with an enterprise 
LDAP directory, which provides personnel (person and organization) data for use in Service Catalog, as 
well as external authentication against that directory and Single Sign-On capability. Directory 
integration can temporarily be turned off by changing this setting to “Off”. 

Directory integration configuration includes the ability to override external authentication or Single 
Sign-On, for troubleshooting, testing, or other reasons. This administrative override should typically be 
restricted to users who have Site Administrator privileges.

For details on directory integration, see the 

Historical Requisition Partitioning feature migrates completed requisitions, namely, requisitions that 
have "Closed", "Canceled", "Delivery Canceled" or "Rejected" status, to historical transaction tables.  
The use of Historical Requisition Partitioning provides overall application performance improvement as 
a result of reducing the amount of data in the current transaction tables. The improvement can be seen 
in the filter and search of tasks, requisitions and external messages in the Service Manager, My Services 
and Service Link modules.  ETL and request workflow processing will also benefit from the smaller 
population of data in the current transaction tables.

Historical Requisition Partitioning is controlled by the system setting "Enable Historical Requisitions 
Scheduler" in the Administration module. When it is enabled, requisitions that have been completed for 
more than 365 days are migrated by a background process to the historical transaction tables. The 
365-day retention period is configurable and may be modified based on the specific needs of your 
organization. You may also execute the migration process of historical requisitions on an ad-hoc basis 
in the Administration > Utilities page when the scheduler is disabled.

Enable Historical Requisitions 
Scheduler

Requisitions that have been completed for more than 365 days are 
migrated to the historical transaction tables by default. The 
scheduler processes 1000 requisitions with a batch size of 100 for 
every 30 min of interval by default. These properties are 
configurable in the newscale.properties file and may be modified 
based on the specific needs of your organization.

When enabled, Closed Requisitions will be archived.

Default is off.

For more information, see 

 and 

Enable Service Catalog

When the setting is on, the module menu shows Service Catalog and 
Order Management instead of My Services. You may override this 
common setting by changing their profile preference.

Default is on.