![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[z/OS]](../images/ngzos.gif)
Troubleshooting application edition manager
When you encounter a problem with the application edition manager, verify that the servers are running or refer to the log files to further investigate the errors.
Procedure
- While performing a rollout, verify that your servers are running. Node agents, the on demand router (ODR), and servers must be running to perform the rollout action.
- Check the log files of the deployment manager, the node
agents, and the servers that are involved in the current operation.
On distributed operating systems, the log file is the SystemOut.log file.
On z/OS® systems, the log file is the servant job log.
You can use the log files when you encounter errors. If you report the problem, it is helpful to collect and save these files. The preferred mechanism is to use the collector utility on each affected node, including the deployment manager, and be prepared to send the output. The collector utility is in the app_server_root/bin directory on each product installation directory.
- If you are frequently experiencing deployment manager timeout on a z/OS system, increase or decrease the timeout values.
Subtopics
Configuring timeout values for application edition manager on z/OS systems
If you are using application edition manager on a z/OS system, and are experiencing deployment manager timeouts, you should either increase the deployment manager timeout values or set the timeout values to zero.Application edition manager frequently asked questions
When you start to use application edition manager, you might come across some questions about the application edition manager functionality.
Related concepts:


File name: twve_xdappedtrb.html