Cisco Cisco Prime Service Catalog 10.0 Technical References
5-20
Cisco Prime Service Catalog 10.0 Configuration Guide
OL-31034-01
Chapter 5 System Administration
Managing the Application
newscale.properties
This file is created by the installer during the install or upgrade process and any time the installer is run.
The file produced by the installer is contained in the “RequestCenter.war\WEB-INF\classes\config”
folder. As such, the file is redeployed any time the ear is redeployed. The Service Catalog administrator
should preserve the data contained in the file, but should not simply restore a copy of the file since the
installer may have added new information for the new version. Entries in newscale.properties include:
The file produced by the installer is contained in the “RequestCenter.war\WEB-INF\classes\config”
folder. As such, the file is redeployed any time the ear is redeployed. The Service Catalog administrator
should preserve the data contained in the file, but should not simply restore a copy of the file since the
installer may have added new information for the new version. Entries in newscale.properties include:
•
udk.datasource.jndi – JNDI name for your RC database
•
udk.datamart.jndi – JNDI name for your data mart database
•
All registered EJBs
•
ObjectCache.Application.URL – URL reference back to the application in the emails sent out
•
ObjectCache.email.host – SMTP host for relaying mail
•
Container.Datasource – JNDI name for the RequestCenter database
•
Scheduler.EscalationManagerSchedule – Schedule for evaluating escalations
rcjms.properties
This file is also located in the “RequestCenter.war\WEB-INF\classes\config” folder. It contains the JMS
settings for application internal communications. Please ensure that the queue names match the ones on
the application server.
settings for application internal communications. Please ensure that the queue names match the ones on
the application server.
integrationserver.properties
This file is located in the “ISEE.war\WEB-INF\classes\config” folder. It contains the key properties of
the integration server (Service Link).
the integration server (Service Link).
Managing Logs
Service Catalog maintains log files on the application server to track application activities, both expected
and unexpected. Logs are managed using a log4j-based framework, an open source (Apache) logging
mechanism. By default, logs are configured as “rolling appenders”, with a new log file opened every day.
Location of the log files varies according to the application server type, as does the ability to adjust log
file contents and configuration.
and unexpected. Logs are managed using a log4j-based framework, an open source (Apache) logging
mechanism. By default, logs are configured as “rolling appenders”, with a new log file opened every day.
Location of the log files varies according to the application server type, as does the ability to adjust log
file contents and configuration.
Recommendations:
•
Rotate logs on a daily basis (this is the default behavior)
•
Keep one month of logs “online”
•
Back up or delete logs that are older than a company-specified retention period
Service Catalog does not require log files to be maintained. They are useful primarily as troubleshooting
tools in case an error arises.
tools in case an error arises.
We recommend against changing the format of the default log files because that is the format the Cisco
Technical Assistance Center (TAC) expects. Rather, customers can create their own appenders that suit
their needs.
Technical Assistance Center (TAC) expects. Rather, customers can create their own appenders that suit
their needs.
In addition to the system-wide log files, Service Link is configured to have a separate log file for each
adapter type. These logs, too, are managed by log4j. By default, Service Link logging is enabled. The
adapter-specific log files, written to the ServiceLink\logs directory, are shown below.
adapter type. These logs, too, are managed by log4j. By default, Service Link logging is enabled. The
adapter-specific log files, written to the ServiceLink\logs directory, are shown below.