Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Scripting Deployment : Log Files

Log Files
Both the AppManage and buildear utilities write information to a log file.
AppManage Log Files
The AppManage utility writes information to a log file. The log file location depends on whether you are accessing an administration domain or not.
If you are not accessing an administration domain, the log is written to the TIBCO_HOME/tra/version/logs/ApplicationManagement.log file.
If you are accessing an administration domain, the log is written to the TIBCO_HOME/tra/domain/domain/logs/ApplicationManagement.log file.
A comparison log file is generated if you export from an EAR file without specifying an administration domain. This information can help you decide whether you need to change the deployment configuration file after an EAR file changes.
For example, using the following command line, the AppManage utility compares the oldconfiguration.xml file with the given EAR file. If any service, global variables, or both have been added, removed, or updated, a log file is created in the same directory where the oldconfiguration.xml file resides, using the file name, oldconfiguration.xml.log.
AppManage -export -ear c:\ears\timer_wait.ear -deployConfig oldconfiguration.xml -out newconfiguration.xml
buildear Log File
The buildear utility writes information to the designer.log file. By default, on Windows, the log is located in the C:\Documents and Settings\user-name\.TIBCO\logs directory.
Note that the default log location can be changed in TIBCO Designer.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved