jimcpl
asked on
Problem deploying EAR + some general WebLogic questions
Hi,
I built a relatively simple portal project in Workshop, with basically just a UserLogin portlet and a 2nd portlet with a form in it. I got it working in Workshop, then used Build->EAR in Workshop to build an EAR (myjlportal.ear).
I wanted to try to deploy this EAR into WebLogic running on a different server, on a Solaris machine using the WebLogic console. The WebLogic server name (target) was "AdminLMIServer", and the WebLogic domain name is the "LMIDomain" domain.
Before I tried to do the deployment in WebLogic, I was looking at the directory structure on the Solaris machine, and I noticed that there was an "/apps/bea/user_projects/d omains/LMI Domain" directory, but there was not an an "applications" directory at all under the "user_projects" directory, and I was guessing (hoping) that WebLogic would create and populate a "/apps/bea/user_projects/a pplication s/myjlport al" these directories when it was deploying the EAR.
When I did the deply in WebLogic console, I clicked "Upload" and pointed the browser to my EAR file. I selected the "AdminLMIServer" Server as the target, then tried to do the deploy, but I got the following errors:
####<Apr 14, 2005 7:09:23 PM GMT> <Error> <Deployer> <solaris2> <AdminLMIServer> <main> <<WLS Kernel>> <> <BEA-149027> <Unable to activate application, _appsdir_META-INF_dir, from source, /apps/bea/user_projects/do mains/LMID omain/appl ications/M ETA-INF. Reason: [J2EE:160028]No J2EE deployment descriptor found at "/apps/bea/user_projects/d omains/LMI Domain/app lications/ META-INF". >
####<Apr 14, 2005 7:09:23 PM GMT> <Error> <Application Poller> <solaris2> <AdminLMIServer> <main> <<WLS Kernel>> <> <BEA-149410> <Runtime deployment error while deploying - weblogic.management.Manage mentRuntim eException : weblogic.management.Applic ationExcep tion: [J2EE:160028]No J2EE deployment descriptor found at "/apps/bea/user_projects/d omains/LMI Domain/app lications/ META-INF". .
weblogic.management.Manage mentRuntim eException : weblogic.management.Applic ationExcep tion: [J2EE:160028]No J2EE deployment descriptor found at "/apps/bea/user_projects/d omains/LMI Domain/app lications/ META-INF".
at weblogic.management.runtim e.Deployer RuntimeMBe an_Stub.ac tivate(Dep loyerRunti meMBean_St ub.java:10 73)
at weblogic.management.deploy .Applicati onsDirPoll er.doActiv ate(Applic ationsDirP oller.java :216)
at weblogic.management.deploy .GenericAp pPoller.do it(Generic AppPoller. java:290)
at weblogic.management.deploy .Applicati onsDirPoll er.><init> (Applicati onsDirPoll er.java:88 )
at weblogic.management.mbeans .custom.Ap plicationM anager.sta rtAdminMan ager(Appli cationMana ger.java:6 30)
at weblogic.management.mbeans .custom.Ap plicationM anager.sta rt(Applica tionManage r.java:494 )
at sun.reflect.NativeMethodAc cessorImpl .invoke0(N ative Method)
at sun.reflect.NativeMethodAc cessorImpl .invoke(Na tiveMethod AccessorIm pl.java:39 )
at sun.reflect.DelegatingMeth odAccessor Impl.invok e(Delegati ngMethodAc cessorImpl .java:25)
at java.lang.reflect.Method.i nvoke(Meth od.java:32 4)
at weblogic.management.intern al.Dynamic MBeanImpl. invokeLoca lly(Dynami cMBeanImpl .java:731)
at weblogic.management.intern al.Dynamic MBeanImpl. invoke(Dyn amicMBeanI mpl.java:7 10)
at weblogic.management.intern al.Configu rationMBea nImpl.invo ke(Configu rationMBea nImpl.java :484)
at com.sun.management.jmx.MBe anServerIm pl.invoke( MBeanServe rImpl.java :1557)
at com.sun.management.jmx.MBe anServerIm pl.invoke( MBeanServe rImpl.java :1525)
at weblogic.management.intern al.RemoteM BeanServer Impl.priva te_invoke( RemoteMBea nServerImp l.java:985 )
at weblogic.management.intern al.RemoteM BeanServer Impl.invok e(RemoteMB eanServerI mpl.java:9 43)
at weblogic.management.intern al.MBeanPr oxy.invoke (MBeanProx y.java:946 )
at weblogic.management.intern al.MBeanPr oxy.invoke ForCaching Stub(MBean Proxy.java :481)
at weblogic.management.config uration.Ap plicationM anagerMBea n_Stub.sta rt(Applica tionManage rMBean_Stu b.java:677 )
at weblogic.management.AdminS erverAdmin .startAppl icationMan ager(Admin ServerAdmi n.java:629 )
at weblogic.management.Admin. finish(Adm in.java:22 17)
at weblogic.management.AdminS erverAdmin .finish(Ad minServerA dmin.java: 458)
at weblogic.t3.srvr.T3Srvr.re sume(T3Srv r.java:971 )
at weblogic.t3.srvr.T3Srvr.ru n(T3Srvr.j ava:361)
at weblogic.Server.main(Serve r.java:32)
Caused by: weblogic.management.Applic ationExcep tion: [J2EE:160028]No J2EE deployment descriptor found at "/apps/bea/user_projects/d omains/LMI Domain/app lications/ META-INF".
at weblogic.j2ee.J2EEApplicat ionContain erFactory. handleErro r(J2EEAppl icationCon tainerFact ory.java:7 39)
at weblogic.j2ee.J2EEApplicat ionContain erFactory. initialize Deployment (J2EEAppli cationCont ainerFacto ry.java:47 5)
at weblogic.management.deploy .DeployerR untime.unp rotectedAc tivate(Dep loyerRunti me.java:84 8)
at weblogic.management.deploy .DeployerR untime.acc ess$000(De ployerRunt ime.java:6 3)
at weblogic.management.deploy .DeployerR untime$1.r un(Deploye rRuntime.j ava:1520)
at weblogic.security.acl.inte rnal.Authe nticatedSu bject.doAs (Authentic atedSubjec t.java:321 )
at weblogic.security.service. SecurityMa nager.runA s(Security Manager.ja va:118)
at weblogic.management.deploy .DeployerR untime.che ckAndPerfo rmDeployer Actions(De ployerRunt ime.java:1 511)
at weblogic.management.deploy .DeployerR untime.act ivate(Depl oyerRuntim e.java:186 )
at weblogic.management.deploy .DeployerR untime.act ivate(Depl oyerRuntim e.java:176 )
at sun.reflect.NativeMethodAc cessorImpl .invoke0(N ative Method)
at sun.reflect.NativeMethodAc cessorImpl .invoke(Na tiveMethod AccessorIm pl.java:39 )
at sun.reflect.DelegatingMeth odAccessor Impl.invok e(Delegati ngMethodAc cessorImpl .java:25)
at java.lang.reflect.Method.i nvoke(Meth od.java:32 4)
at weblogic.management.intern al.Dynamic MBeanImpl. invokeLoca lly(Dynami cMBeanImpl .java:731)
at weblogic.management.intern al.Dynamic MBeanImpl. invoke(Dyn amicMBeanI mpl.java:7 10)
at com.sun.management.jmx.MBe anServerIm pl.invoke( MBeanServe rImpl.java :1557)
at com.sun.management.jmx.MBe anServerIm pl.invoke( MBeanServe rImpl.java :1525)
at weblogic.management.intern al.RemoteM BeanServer Impl.priva te_invoke( RemoteMBea nServerImp l.java:985 )
at weblogic.management.intern al.RemoteM BeanServer Impl.invok e(RemoteMB eanServerI mpl.java:9 43)
at weblogic.management.intern al.MBeanPr oxy.invoke (MBeanProx y.java:946 )
at weblogic.management.intern al.MBeanPr oxy.invoke ForCaching Stub(MBean Proxy.java :481)
at weblogic.management.runtim e.Deployer RuntimeMBe an_Stub.ac tivate(Dep loyerRunti meMBean_St ub.java:10 64)
I guess that I'm a bit perplexed by these error messages.
What, exactly, is WebLogic trying to tell me?
And, how do I fix this problem?
As for my general WebLogic question: Basically, I'm kind of puzzled about "deployment" with the WebLogic console. As mentioned above, I did the upload of my EAR file in the WebLogic console, and I selected the AdminLMIServer as the target. But, the thing that I don't understand is HOW does WebLogic determine where (in which directory) to put the EAR? During the deploy process with WebLogic console, I don't get a chance to specify the destination directory, so WebLogic must be figuring that out somehow...
Thanks in advance,
Jim
I built a relatively simple portal project in Workshop, with basically just a UserLogin portlet and a 2nd portlet with a form in it. I got it working in Workshop, then used Build->EAR in Workshop to build an EAR (myjlportal.ear).
I wanted to try to deploy this EAR into WebLogic running on a different server, on a Solaris machine using the WebLogic console. The WebLogic server name (target) was "AdminLMIServer", and the WebLogic domain name is the "LMIDomain" domain.
Before I tried to do the deployment in WebLogic, I was looking at the directory structure on the Solaris machine, and I noticed that there was an "/apps/bea/user_projects/d
When I did the deply in WebLogic console, I clicked "Upload" and pointed the browser to my EAR file. I selected the "AdminLMIServer" Server as the target, then tried to do the deploy, but I got the following errors:
####<Apr 14, 2005 7:09:23 PM GMT> <Error> <Deployer> <solaris2> <AdminLMIServer> <main> <<WLS Kernel>> <> <BEA-149027> <Unable to activate application, _appsdir_META-INF_dir, from source, /apps/bea/user_projects/do
####<Apr 14, 2005 7:09:23 PM GMT> <Error> <Application Poller> <solaris2> <AdminLMIServer> <main> <<WLS Kernel>> <> <BEA-149410> <Runtime deployment error while deploying - weblogic.management.Manage
weblogic.management.Manage
at weblogic.management.runtim
at weblogic.management.deploy
at weblogic.management.deploy
at weblogic.management.deploy
at weblogic.management.mbeans
at weblogic.management.mbeans
at sun.reflect.NativeMethodAc
at sun.reflect.NativeMethodAc
at sun.reflect.DelegatingMeth
at java.lang.reflect.Method.i
at weblogic.management.intern
at weblogic.management.intern
at weblogic.management.intern
at com.sun.management.jmx.MBe
at com.sun.management.jmx.MBe
at weblogic.management.intern
at weblogic.management.intern
at weblogic.management.intern
at weblogic.management.intern
at weblogic.management.config
at weblogic.management.AdminS
at weblogic.management.Admin.
at weblogic.management.AdminS
at weblogic.t3.srvr.T3Srvr.re
at weblogic.t3.srvr.T3Srvr.ru
at weblogic.Server.main(Serve
Caused by: weblogic.management.Applic
at weblogic.j2ee.J2EEApplicat
at weblogic.j2ee.J2EEApplicat
at weblogic.management.deploy
at weblogic.management.deploy
at weblogic.management.deploy
at weblogic.security.acl.inte
at weblogic.security.service.
at weblogic.management.deploy
at weblogic.management.deploy
at weblogic.management.deploy
at sun.reflect.NativeMethodAc
at sun.reflect.NativeMethodAc
at sun.reflect.DelegatingMeth
at java.lang.reflect.Method.i
at weblogic.management.intern
at weblogic.management.intern
at com.sun.management.jmx.MBe
at com.sun.management.jmx.MBe
at weblogic.management.intern
at weblogic.management.intern
at weblogic.management.intern
at weblogic.management.intern
at weblogic.management.runtim
I guess that I'm a bit perplexed by these error messages.
What, exactly, is WebLogic trying to tell me?
And, how do I fix this problem?
As for my general WebLogic question: Basically, I'm kind of puzzled about "deployment" with the WebLogic console. As mentioned above, I did the upload of my EAR file in the WebLogic console, and I selected the AdminLMIServer as the target. But, the thing that I don't understand is HOW does WebLogic determine where (in which directory) to put the EAR? During the deploy process with WebLogic console, I don't get a chance to specify the destination directory, so WebLogic must be figuring that out somehow...
Thanks in advance,
Jim
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
sompol,
Thanks for the responses.
I know that I can manually deploy the exploded EAR into WebLogic, but I think that I need to find out how to specify where to deploy the EAR during the WebLogic console deployment, so I look forward to your information (or others).
Thanks,
Jim
Thanks for the responses.
I know that I can manually deploy the exploded EAR into WebLogic, but I think that I need to find out how to specify where to deploy the EAR during the WebLogic console deployment, so I look forward to your information (or others).
Thanks,
Jim
ASKER
sompol,
With the info at the link, and some testing, I was able to get this working, two different ways:
1) Manually placing the exploded EAR:
- Copy the EAR to a directory (../applications/myapp) under the "applications" directory
- Unzip the EAR file in-place
- Start the WebLogic console, then do a "Deploy a new..."
- Click to the "applications" directory. Console then showed the "myapp" directory
- Click on "myapp". Console then showed the application with a radio button.
- Select "myapp", then click the Deploy button
2) Manually placing the EAR:
- Copy the EAR to a directory (../applications/myapp) under the "applications" directory
- Start the WebLogic console, then do a "Deploy a new..."
- Click to the "applications" directory. Console then showed the "myapp" directory
- Click on "myapp". Console then showed the EAR with a radio button.
- Select "myapp.ear", then click the Deploy button
Thanks,
Jim
With the info at the link, and some testing, I was able to get this working, two different ways:
1) Manually placing the exploded EAR:
- Copy the EAR to a directory (../applications/myapp) under the "applications" directory
- Unzip the EAR file in-place
- Start the WebLogic console, then do a "Deploy a new..."
- Click to the "applications" directory. Console then showed the "myapp" directory
- Click on "myapp". Console then showed the application with a radio button.
- Select "myapp", then click the Deploy button
2) Manually placing the EAR:
- Copy the EAR to a directory (../applications/myapp) under the "applications" directory
- Start the WebLogic console, then do a "Deploy a new..."
- Click to the "applications" directory. Console then showed the "myapp" directory
- Click on "myapp". Console then showed the EAR with a radio button.
- Select "myapp.ear", then click the Deploy button
Thanks,
Jim
I think you may have a problem with deployed directory. As I see in the error message that WebLogic print out, it told us that it's trying to find deployment descriptor in the location "user_projects/domains/LMI
But I think you deployed files would be in "user_projects/application
The thing we need to find out is how to specify or tell the server where our deployed files are located.
This problem will not occur if you setup WorkShop to have the same directory structure as the server have. But I think we can specify the location when we are deploying too. I will try to find how to configure for you and I will be back again.
SoMPOL