Review the Unwired.log. x file if there is a problem with service invocation or you are troubleshooting service deployment errors. Unwired Orchestrator server maintains a series of files named Unwired.log. x, for example, Unwired.log.0, Unwired.log.1, and so on.
File path for Unwired.log. x files:
<Runtime server installation directory>\EAServer\bin
The Unwired.log. x files contain the following types of information:
Service invocation.
Service execution.
Business process engine variable assigns, final business process output messages, and intermediate steps in the execution of business processes.
Debug information (if package logging is set to FINER or FINEST).
To view this information in context with EAServer component traces and ASA/ASE traces (if they are installed), view the jaguar.log for EAServer.
The Unwired.log. x log files are regularly overwritten. When the Unwired.log.0 file reaches its maximum size (determined by the value of the java.util.logging.FileHandler.limit variable, set in the logging.properties file), it is renamed Unwired.log.1 and a new Unwired.log.0 is started. If Unwired.log.1 already exists, it is renamed Unwired.log.2, and so on. When the maximum number of Unwired.log. x files has been created (determined by the value of the java.util.logging.FileHandler.count variable, set in the logging.properties file), the highest-numbered log in the series is overwritten.
The maximum file size and quantity of Unwired.log. x files maintained is determined by the value of the following variables found in the logging.properties file, located at <Runtime installation directory>\config\:
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com