Every component in a Prophecy system writes logs to the logs directory under the Prophecy home directory (the directory where you elected to install Prophecy):
Designer logging uses the Log4J framework and is configured in the designer-logging.xml file in the config directory under the Prophecy home directory. Users familiar with the Log4J framework will have no problem changing the settings to suit their own needs. By default, Designer writes to four different files, one for each component that makes up designer:
deployment.log – the log for the deployer
reporting.log – the log for the reporting component
runtime.log – the log for the runtime engine
ui.log – the log for the visual interface used to design, manage and monitor applications
MC
The Management Console (MC) logging uses the Log4J framework and is configured in the designer-logging.xml file in the config directory under the Prophecy home directory. Users familiar with the Log4J framework will have no problem changing the settings to suit their own needs. By default the MC writes to two different files, one for the agent and one for the controller (note that the controller log will not be written to if the server is a member server belonging to a community with the controller being a different server).
sipmethod
SIPMethod is the (SIP) application server that ships with a Prophecy system. Prophecy uses two instances of SIPMethod: one to serve controller services and another one to serve other components (like the VoiceXML SIPServlet and the Prophecy Home page) as well as components deployed by the end user. This directory contains log files for both these instances, and only contain log messages from the SIPMethod instance, not log messages produced by applications deployed on SIPMethod. SIPMethod uses the Log4J framework and is configured in the designer-logging.xml file in the config directory under the Prophecy home directory. Users familiar with the Log4J framework will have no problem changing the settings to suit their own needs.
vcs
VCS (also known as the Voxeo Prophecy Server), contains logs from the VCS component. This component includes, amongst others, CallXML, CCXML and MRCP logs.
vxlaunch
VXLaunch (also known as the Service Control Manager (SCM)) is the component that controls the starting and stopping the other components. If a component fails to start you should check these logs.
vxml
VXML contains the logs produced by the VoiceXML SIP servlet, the component containing the VoiceXML and SCXML browser. VXML uses the Log4J framework and is configured in the designer-logging.xml file in the config directory under the Prophecy home directory. Users familiar with the Log4J framework will have no problem changing the settings to suit their own needs.
ANNOTATIONS: EXISTING POSTS
0 posts - click the button below to add a note to this page
