How can we enable additional tracing in Deployment Engine if we cannot determine the cause of the workflow failure?
If setting log level to defect in log4j does not help you identify the cause of your Common Agent Service (CAS) related workflow problem, you can set Java Developer Kit (JDK) tracing in the Tivoli Provisioning Manager deployment engine. The Tivoli Provisioning Manager deployment engine uses JDK logging mechanism for components related to CAS. • Prepare a jdklogging.properties file with the following content on the UNIX platform: ********************************************************************************* handlers= java.util.logging.FileHandler java.util.logging.FileHandler.level=ALL java.util.logging.FileHandler.pattern=/var/IBM/tivoli/common/COP/logs/deploymentengine/jdk_logs%u.log java.util.logging.FileHandler.limit=50000 java.util.logging.FileHandler.count=5 java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter. com.ibm.pvcws.osgi.level=ALL .level=ALL ******************************************************************************** • On the Windows platform,
Related Questions
- What approach would you recommend to determine the root cause of failure and the least cost solution to marine propulsion machinery failures?
- How can we enable additional tracing in Deployment Engine if we cannot determine the cause of the workflow failure?
- How to enable additional downloads for my Podbean eStore orders?
