![]() ![]() Ws.ext.dirs=/usr/WebSphere/AppServer/java/lib /usr/WebSphere/AppServer/classes. Work.dir=/usr/WebSphere/PortalServer/config/work At the bottom of the log, you should see something similar to this: Scroll to the bottom of the file to review the most recent failure. Review the ConfigTrace.log to determine the nature and timing of the failure. You have executed a WPSconfig.sh task and have received a BUILD FAILED message. This log is never overwritten and is appended to each time another configuration task is executed.Īnalyze Failures with Configuration Tasks that is made up of a series of sub-tasks.įailures during the configuration tasks are common and this information is intended to help you understand how the tasks work and how we can begin problem determination when a configuration task fails. When invoking a configuration task you are simply invoking a parent task, for example. The configuration tasks are a series of ANT scripts that are invoked by running the WPSconfig.sh script from. WebSphere Portal uses configuration tasks to configure Portal to LDAPs, databases, etc. This page describes portal problem determination methods for WebSphere Portal and WebSphere Application Server (WAS). Services Oriented Architecture and Portal.Update Portal Wizard Graphical User Interface Overview.Downloading the Portal Update Installer.Use ANT script to automate portal server operations.Use wsadmin to automate application server configuration change. #Oneview reapply profile to degraded server installUse InstallFactory to build custom WAS install image.WebSphere Portal version 6.0 Information Center.Troubleshooting - WebSphere Portal V6 Enterprise Scale Deployment ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |