hi, we are trying to deploy an application, named Redinet, to Websphere 4.0.5 AE. We are encountering the following error after clicking on Finish to complete the deploy. JWarning: cannot find link for ejbRef, link name is RedinetEJB.jar#Approval 'com.ibm.ejs.resources.RepositoryStrings "7162-2ba11faf-3498703:WSCS-3376207 WebSphere AE 4.0.5 ptf50246.04 &com.ibm.ejs.sm.beans.EnterpriseAppBean d0eeb 21889 suapp01/__adminServer LWarning: cannot find link for ejbRef, link name is RedinetEJB.jar#Settlement 'com.ibm.ejs.resources.RepositoryStrings "7162-2ba11faf-3498703:WSCS-3376207 WebSphere AE 4.0.5 ptf50246.04 &com.ibm.ejs.sm.beans.EnterpriseAppBean d0eeb 21889 suapp01/__adminServer [Warning: cannot find link for ejbRef, link name is RedinetEJB.jar#BuildSunJourn alInputFiles 'com.ibm.ejs.resources.RepositoryStrings "7162-2ba11faf-3498703:WSCS-3376207 Looks like a classpath issue but I cannot work out how it is doing the lookup. I have looked at the MANIFEST.MF files but have not spotted anything obvious. Have also been able to successfully install to Websphere 4.0.1 SSE. Unfortunately this is our development box. System specs ------------ Sun Solaris 8 Websphere 4.0.5 AE iPlanet 6 web server on separate server with plugin installed. Thanks in advance, Ralph Roper
ralph roper
Greenhorn
Joined: Nov 25, 2001
Posts: 25
posted
0
This is getting interesting. Has anyone been able to deploy an ear file created in WSAD 5 on Win NT to Websphere 4.0.x AE on Unix (preferably Sun Solaris)? I have read in other posts that you can deploy from WSAD to Websphere single server but you need to use AAT to deploy to Webpshere advanced edition. Is this true and if so, why? Ralph
Green Horn UniCon
Greenhorn
Joined: Jul 03, 2003
Posts: 4
posted
0
U don't actually need AAT. If ur using WSAD 5 and deploying it on Websphere 4.0, WSAD makes things easier for you. I am using WSAD 5.0 to deploy my application on Websphere 4.0 installed on Sun Solaris machine. Everything works out fine without using the AAT at all.
ralph roper
Greenhorn
Joined: Nov 25, 2001
Posts: 25
posted
0
are you using Websphere 4 single-server or multi-server advanced edition? We only receive these errors when deploying to multi-server.
George Secillano
Greenhorn
Joined: Jul 11, 2003
Posts: 7
posted
0
Are you guys using WSAD on solaris or in windows. I am actually having problems deploying EJBs in solaris.
ralph roper
Greenhorn
Joined: Nov 25, 2001
Posts: 25
posted
0
George, we are developing with WSAD 5 on Windows and and trying to deploy to WAS 4.0.x AE multi-site server on Sun Solaris. We lodged a call with IBM 2 weeks ago and is now in the hands of IBM development in the US. Please note as in previous post we have not had an issue deploying to WAS 4.0.x AE single server on Sun Solaris. regards, Ralph
Chak Radar
Greenhorn
Joined: May 05, 2003
Posts: 7
posted
0
HI What is the option enabled for module visibility in websphere console.(by default it is module) Thanks Chakradar
ralph roper
Greenhorn
Joined: Nov 25, 2001
Posts: 25
posted
0
Chak, have tried 1. Application visibility 2. setting J2EEApplication system property to true regards, Ralph
ralph roper
Greenhorn
Joined: Nov 25, 2001
Posts: 25
posted
0
Problem solved! IBM support have got back in contact with me and confirmed there is a defect when using WSAD 5.0.x against WAS 4.0.x. The problem is that when WSAD creates the web.xml file it references the EJB links with <application web.jar>#<EJB link ID>. WAS 4 cannot interpret the leading application jar and throws a EJB ref link error. There are a couple of ways to resolve the problem. 1. Upgrade WSAD 5.0.x to 5.1 2. Use the AAT tool to regenerate the web deployment descriptor links. Admittedly we did notice other problems taking this route so I would recommend option 1. Hope this helps anyone who comes across this problem. Ralph
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
0
