This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
You can create a new profile instead of doing a reinstall. This has the same effect as a reinstall but works a heck of a lot faster. Run the profile wizard in the WAS_HOME directory. Can't remember the exact folder/file name but its pretty easy to find.
Your right Roland, I had read this post a tad too briefly (relying on Graham Thorpe comment that the server was all ready corrupted). Fixing the variable should repair most of the issues.
In the case that the server configuration was corrupt, though, do you have a way repair it without creating a new profile, or regardless, is it easier to just create a new profile?
Joined: Apr 15, 2004
Anytime you deal with resources on a file system, you run the risk of files becoming corrupt. I have have corupt servers in WAS, WebLogic, JBoss, and many other servers that store their configurations in XML on the file system. Because we provide a sophisticated file replication over the network for WAS ND, there is risk of networks going down during tranmission of files, etc...
Luckly, we have provided a tool since WAS 5 called backupConfig.bat and restoreCOnfig.bat. They are located in the bin directory of WebSphere. One of the Best practices we have is running the backupConfig.bat utility when making major config changes. The backup config file will store these changes in a single file. Then if a configuration becomes corrupt, you can run restoreConfig and point to the file. You should do this with each profile.
Originally posted by Sivachandran Sundararajan: Hi all,
I am using WebSphere 6.0 and try to do ejbdeploy but i got the error.Can anyone please help me in this regard.This works fine in WebSphere 5.1.0 & 22.214.171.124
Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified)
I had the same problem last month, and struggled for a while. I found the point is, we have to use <ws_home>\profiles\AppSrv01\bin\ws_ant.bat to call ant, instead of calling ant directly. By using ws_ant.bat, it will initialize some env variables, and using IBM's JVM to do the job. Another thing is, in build script, I need to define property "wasinstall" as websphere install home. This property will be used as ejb deploy task's attribute "wasHome"'s value.