15
Application already exists in the configuration repository error.
Posted by | Posted in WebSphere | Posted on 15-04-2008
Tagged Under : WAS, WebSphere, WebSphere Application Server
Application already exists in the configuration repository error when installing new EAR in WAS admin console.
If we can screw up our enterprise application installation properly, we would reach to a state where we cannot go forward and backward. It is a nice state in which if we try to uninstall the application we would get an error message from WebSphere. Whatever may be the reason we will not be able to uninstall the enterprise project using WAS admin console. Then we will try our luck by installing new enterprise application unluckily WAS wouldn’t allow us to do that also. This time WebSphere Application Server would give a nice error message. “Application already exists in the configuration repository”.
The solution to this issue is to manually delete/uninstall the application by editing the configuration file. Do a search for your ear file in the file system and delete all the occurrences of the XXX.ear folder (You can see one .ear directory in your WAS_INSTALL_DIR/profiles/
WAS_INSTALL_DIR\profiles\<profileName>\config\cells\<cellName>\nodes\<nodeName>\ |
And edit the file serverindex.xml.
In this file we can see an entry for our application within the tag
<deployedApplications>xxx.ear</deployedApplications> |
Delete this entry. We are done. Now we can install our application using WebSphere admin console without any issues.
This work only if I want to delete the existing Application. Sometimes it may be required to keep both the applications in the same server. In that case how can I avoid the Application already exists error message? Or how to install two versions of the same EAR in the same WAS?
Hi Albin,
whatever said by you and is correct. I have personally done this twice for solving the issue.
But lately, i got the same “Application exists in server configuration repository” thing in a completely different situation, hence i thought i will share…
Actually, there was a Web App called MyWebApp (EAR file) present in IBM WAS. I wanted to duplicate this EAR (same code), only pointing to different Database environment.
So, i downloaded the EAR file of the App from the config folder (/home/webapp/IBM6.1/WebSphere/AppServer/profiles//config/cells//applications/), and perform the following changes to create a new EAR…
(a) Changed the name of the WAR file
(b) Changed the name of the EAR file
(c) Edited the META-INF/aplication.xml file in the EAR file
(d) Bundled the edited WAR file and the application.xml file in the eidited EAR file.
When i attempted to install this EAR, it gave me the above error, although there does not exists any EAR or WAR file with the name i gave to them.
After digging a little, i found one small thing in the Web.xml file (WEB-INF in WAR file). It seems, the property “id” of the tag “” in Web.xml was the culprit. When i changed the value of this “id attribute to something else, it worked.
Conclusion, during installation, it compares the “id” of the Web App with the ones already installed and hence the error.
Hi Prasanna, This was something new to me. Thanks.
thanks albin…this worked, though i dint have to edit the serverindex.xml.
My dear friend in my case i have 2 ear files same code with different context root and installed in the same server both are working fine but just now i try to install on ear file and even though it does not exist it is giving Application already exists in the configuration repository as you said i already changed id in web.xml and it doesnt work…..please give me the solution…
Thanks man, I faced same problem, and removed entry in serverindex.xml and its working now.