Application already exists in the configuration repository on 6.0.1?

[mar...@medscheme.co.za]

I'm experiencing a problem when trying to install EARs in WebSphere 6.0.1: no Enterprise Applications are displayed in the admin console, and yet when I try to install an application anyway the console tells me that the "Application already exists in the configuration repository" after the second page of the deploy process.

I know for a fact that the application I'm trying to install is there, along with the ivtApp and DefaultApplication, because I can access them. I've tried using wsadmin's $AdminApp object to uninstall the application (btw, it actually reports successfully removing the application), but the same problem happens when installing again.

Out of sheer desperation, I then went and deleted any files containing references to my application in <WAS_ROOT>\profiles\<myprofile>\wstemp. I think that this is where WAS stores temporary config files? Anyway, I can install the application after doing that, but there's still nothing in my Enterprise Applications list.

This is my configuration;

WebSphere Application Server 6.0.1 (the latest interim fixpack) running on Windows 2000 (all prerequisites met in installation) in the following configuration:

* Installed Application Server profile ONLY.
* Installed IHS as a local Web Server
* WebSphere is running with all the default installation options.

I should mention that when I first tried to install applications on this server, I experienced a problem where WebSphere could not install the application because it was unable to remove files in -- you guessed it -- the wstemp directory.

Could this be some bizarre Win2K-related bug?

[Michael Burmeister]

This is a know bug in the WAS 6.0 product. It happens when you installed
the Plugin server. The name you gave to the plugin comes later in the
alphabet than the server name "server1" and causes all your applications to
disappear.
To get them back you need to go to the profiles directory where your
applications are installed and find each application installed in that cell.
In each application there is a deployment folder with a "deployment.xml"
file.
In there the last xml entries with the server name in it must have "server1"
listed last or after your webserver plugin entry or you won't be able to see
this application in the console.

Michael

<mar...@medscheme.co.za> wrote in message
news:2139004824.1116396299974.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...

[a...@nyangau.fsnet.co.uk]

This is interesting, and sounds like a problem I am seeing.

I have observed that with 6.0.1.0 standalone (default) profile, mapping
an application to a web server node makes the application vanish from
the console (can only be removed using wsadmin).
But, in a network deployed configuration, this doesn't happen.

My application was called "Rect", the app server was "server1" and the
web server node was called "ihs6ws1_node", so I had the ordering with
the problem.

In my configuration, the web server node is "remote", and I'm using
Linux.

> This is a know bug in the WAS 6.0 product.

Is it known to IBM, and do they have an eFix, or a date for an eFix
yet?
Is there a PMR raised for this issue?

The first time this bit me, the application vanished from the console
and I didn't realise it was still there, so I tried to install again.
It is somewhat annoying that I wasn't told the application was already
present until I had gone pretty much all the way through the Wizard.
Surely it can tell as soon as I've told it the application name.

{{{ Andy