Deployment question: exploded EAR application

I've been having some EJB connection problems when I try to deploy an exploded
EAR app.
Here is some background info.
Running WL 6.1 SP2 on Solaris 8
I have the following directory structure for my EAR app which
contains my EJB's and WEB app
/deployment/config/mydomain
/myApp
/META-INF/application.xml
/classes
/ejb
/webApp
/WEB-INF/web.xml
/weblogic.xml
The application.xml file contains all the descriptors for each EJB jar file in
the ejb directory as well as the deployment descriptor to the webApp.
In the Weblogic console I can create a new application called myApp and point
it to the above directory (/deployment/config/mydomain/myApp) and it will deploy
all the EJB's and the web app and I can display the login page to my webApp but
as soon as I try to login and the webApp has to connect to a LOGIN ejb it fails
because it cannot connect to the EJB.
If I deploy each ejb jar file separately into a running weblogic environement
I can login which means I can successfully connect to the EJB's.
Has anyone done something similar to this. I'm following the BANK example that
came with WL6.1, but I have not been successful and wondering if anyone can shed
some light here for me.
If you want to see my application.xml or web.xml let me know and I'll post it
up.
Thanks
Ray

Make sure your EJB's have a deployment target. I noticed that when I
deployed an exploded ear file, the EJB's weren't deployed to the server,
they were present in the console, but not deployed.
-Brett Schmoll
"Ray" <[email protected]> wrote in message
news:3c374e60$[email protected]..
>
I've been having some EJB connection problems when I try to deploy anexploded
EAR app.
Here is some background info.
Running WL 6.1 SP2 on Solaris 8
I have the following directory structure for my EAR app which
contains my EJB's and WEB app
/deployment/config/mydomain
/myApp
/META-INF/application.xml
/classes
/ejb
/webApp
/WEB-INF/web.xml
/weblogic.xml
The application.xml file contains all the descriptors for each EJB jarfile in
the ejb directory as well as the deployment descriptor to the webApp.
In the Weblogic console I can create a new application called myApp andpoint
it to the above directory (/deployment/config/mydomain/myApp) and it willdeploy
all the EJB's and the web app and I can display the login page to mywebApp but
as soon as I try to login and the webApp has to connect to a LOGIN ejb itfails
because it cannot connect to the EJB.
If I deploy each ejb jar file separately into a running weblogicenvironement
I can login which means I can successfully connect to the EJB's.
Has anyone done something similar to this. I'm following the BANK examplethat
came with WL6.1, but I have not been successful and wondering if anyonecan shed
some light here for me.
If you want to see my application.xml or web.xml let me know and I'll postit
up.
Thanks
Ray

Similar Messages

Error when I deployed the java EAR application in NWDS 7.1

HI All,
I got the error when I deployed the java EAR application in NWDS 7.1 version..help me out...........................................
com.sap.ide.eclipse.deployer.api.APIException: DeployException,cause=[ERROR CODE DPL.DCAPI.1023] AuthorizationException.
Reason: , An error occurred during the deployer retrieval. Cause =[ERROR CODE DPL.DC.3151] The user LJ4PJW could not be authorized, because doesn't own the (com.sap.engine.interfaces.security.ServiceAccessPermission dc) permission for deploy controller. at com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
Thanks
Costa

The user LJ4PJW could not be authorized, *because doesn't own the* (com.sap.engine.interfaces.security.ServiceAccessPermission dc) *permission for deploy controller. a*t com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
The user is not have proper authorizations. Use some other administrators user id which has all admin roles and authorizations assigned and try to deploy.
Regards,
Ravi

Weblogic 8.1 and exploded EAR application

I have been trying to deploy my eclipse j2ee project in exploded way in weblogic 8.1
I have standard folder structure,
<APP_ROOT>
-> index.jsps etc.
-> WEB-INF/classes
-> APP-INF/lib (for 3rd party libs)
META-INF/ application.xmls and ejb-jar xmls. Now problem is, i am not able to deploy ejbs using classpath WEB-INF/classes.
I tried MANIFEST.MF class-path entry, it didn't work.
Is there any way to define classpath for ejbs at application classloader level?
Ofcourse, if I create new folder say 'ejb' and deploy that as ejb module and put all classes in ejb directory, it works.
my application.xml looks like this
<application>
<display-name>Test Application</display-name>
<module>
<ejb>/</ejb>
</module>
<module>
<web>
<web-uri>/</web-uri>
<context-root>webapp</context-root>
</web>
</module>
</application>

I have been trying to deploy my eclipse j2ee project in exploded way in weblogic 8.1
I have standard folder structure,
<APP_ROOT>
-> index.jsps etc.
-> WEB-INF/classes
-> APP-INF/lib (for 3rd party libs)
META-INF/ application.xmls and ejb-jar xmls. Now problem is, i am not able to deploy ejbs using classpath WEB-INF/classes.
I tried MANIFEST.MF class-path entry, it didn't work.
Is there any way to define classpath for ejbs at application classloader level?
Ofcourse, if I create new folder say 'ejb' and deploy that as ejb module and put all classes in ejb directory, it works.
my application.xml looks like this
<application>
<display-name>Test Application</display-name>
<module>
<ejb>/</ejb>
</module>
<module>
<web>
<web-uri>/</web-uri>
<context-root>webapp</context-root>
</web>
</module>
</application>

NetWeaver exploded ear deployment

Hi
I'm depolying my application on the NetWeaver App Server 7.1 through the script files (DeploymentManager etc.) - question is this:
Is it possible to deploy an exploded ear, if so what entries should be putted into a deploy-manager-config.xml file?
Regards
P

This is not possible.
Regards,
Benny

Deploying jars within a single (exploded) ear

Our project currently uses 8.1 SP3 with split deployment structure.
Currently the project is split into multiple ears deployed on a single (managed) server. It is my understanding that calls made across ear's even on the same server (jvm) need to be marshalled and unmarshalled using pass by value.
We are trying to consolidate all our EJBs and Web apps into a single .ear so that we can take advantage of call-by-reference. We also have a requirement of being able to deploy "groups" of EJBs (within a single jar) and/or a web app. Deploying a single ear for the entire project would be one extreme, as it would be painful to deploy individual modules within the ear. On the other hand, using an exploded ear would be too "granular" a way of deploying our changes (we have many EJBs, etc.).
Is it possible to deploy an exploded ear consisting of jar and war files ? I am in the process of trying this and was looking for feedback. The idea is of being able to deploy parts of the app, such as a .jar or a .war file. Can wlpackage create an exploded ear using .jar and .war files instead of modules consisting of .java/.jsp, etc. files? Thanks for your help!

There is a classpath issue. Normally ejbs are loaded on top of the ears classpath, so whenever you redeploy them, you have to redeploy the webapps, too. In 8.1 you can build your custom class loader hierarchy. Take a look at http://e-docs.bea.com/wls/docs81/programming/classloading.html#1065667
-Kai

Directory Structure ?s for an Exploded Web Application

We have an application that consists only of JSPs and Servlets, no
EJBs. I am researching whether or not it's worthwhile to start using
EJBs. We're also migrating from Weblogic 5 to 6.1. I've managed to
migrate our application fine and have it up and running on WLS 6.1.
I'm confused about the exploded directory structure, the
application.xml file, where to put the EJBs and whether or not I have
to jar them. Here's our current directory structure:
DefaultWebApp/               JSPs here
DefaultWebApp/WEB-INF          web.xml and weblogic.xml here
DefaultWebApp/WEB-INF/classes     Servlets and other classes here
DefaultWebApp/WEB-INF/lib     do my un-jar-ed EJBs go here?
I've been reading a lot of BEA's documentation, particularly
‘Deploying an Exploded J2EE Application' and a ‘Web Application PDF',
and looking for relevant threads on the weblogic.developer.interest
groups. It looks like the application.xml should go in a new
DefaultWebApp/META-INF directory. But where do the EJBs go?
I also see some directory structures with another /web directory
that's confusing me.
Oh, I've also managed to compile and jar up a trial Stateless Session
EJB. Then I think I ‘auto-deployed' it into the /applications
directory, and Weblogic seems to recognize it. But when I tried to
reference it in a JSP, I got an error message ‘class x is public,
should be declared in a file named x.java'. I'm assuming this is
related to the application.xml, where I need to define the ejb
directory.
Thanks.

To deploy your web app together with your EJBs, you need to create
an "EAR" structure. Both your webapp and your EJB jars will be within
this new structure, at the same level. You may jar up your EJBs, or you
may explode their structure, it's up to you.
The resulting structure should look something like below:
EnterpriseApp/ <-- new top level
EnterpriseApp/META-INF/
EnterpriseApp/META-INF/application.xml
EnterpriseApp/lib/ <-- shared libraries (if any)
EnterpriseApp/EJB/ <-- ejbs go here
EnterpriseApp/EJB/META-INF/ejb-jar.xml
EnterpriseApp/EJB/META-INF/weblogic-ejb-jar.xml
EnterpriseApp/EJB/com/your/ejb/classes/here
EnterpriseApp/WebApp/ <-- move your current app here
EnterpriseApp/WebApp/index.jsp <-- JSPs goes here
EnterpriseApp/WebApp/other.jsp
EnterpriseApp/WebApp/WEB-INF/web.xml
EnterpriseApp/WebApp/WEB-INF/weblogic.xml
EnterpriseApp/WebApp/WEB-INF/lib <-- ui libraries go here
EnterpriseApp/WebApp/WEB-INF/classes <-- servlets go here
The above structure is identical to the structure to an EAR file, only "exploded"
as actual files and directories instead of being "jarred" into a single EAR file.
Your application.xml in this case would specify something like:
<application>
<display-name>EnterpriseApp</display-name>
<description>My Enterprise Application</display-name>
<module>
<ejb>EJB</ejb>
</module>
<module>
<web>
<web-uri>WebApp</web-uri>
<context-root>/yourAppRoot</context-root>
</web>
</module>
</application>
And in config.xml you would have an entry similar to:
<Application Deployed="true" Name="EnterpriseApp"
Path=".\config\mydomain\applications\EnterpriseApp">
<WebAppComponent Name="ui" Targets="myserver" URI="WebApp"/>
<EJBComponent Name="ejb" Targets="myserver" URI="EJB"/>
</Application>
regards,
-Ade

Exploded EAR in Weblogic 7.0.2

I'm trying to deploy an exploded EAR file but I must be missing something since WLS doesn't deploy my application.
I've read the documentation from http://e-docs.bea.com/wls/docs70/programming/deploying.html.
Beneath the structure in my 'applications' directory as describes in http://e-docs.bea.com/wls/docs70/programming/deploying.html#1125125. I've put application.xml in the MyApp directory - is it the right place and is the file correct?
MyApp\
\MyApp.war
WEB-INF\
web.xml
classes\
dk\
...(JSP etc.)
\MyApp-ejb.jar
META-INF\
application.xml
ejb-jar.xml
REDEPLOY
weblogic-cmp-rdbms-jar.xml
weblogic-ejb-jar.xml
dk\
...(class files)
application.xml looks like:
<application>
<display-name>MyApp</display-name>
<module>
<ejb>MyApp-ejb.jar</ejb>
</module>
<module>
     <web>
     <web-uri>MyApp.war</web-uri>
     <context-root>myapp</context-root>
     </web>
</module>
</application>
Thanks
Thomas Aagaard Jensen
UNI-C, Uddannelse - IT-undervisningsmidler
WWW : http://www.uni-c.dk/
Tlf. : +45 8937 6673
E-mail : [email protected]

Hie,
          We are facing the same problem; i.e. we are getting the same error message when we are trying to run our struts application on Weblogic 7.0.5 using JDK 1.3.1. This problem occured particularly when we tried to do a load testing using approx 20 concurrent users (a lesser load was supported though). Can you please let us know how this problem was sorted out on your end?
          thanks,
          Debanjan

Redeploying of exploded EJBs within an exploded EAR

Hi all,
I've an exploded EAR application which has an exploded EJB. Inside my exploded EJB, I've a META-INF folder with a REDEPLOY file, if I update my EJB & touches the REDEPLOY file inside the META-INF, the EJB doesn't get redeployed. I'd to touched the REDEPLOY inside the META-INF folder of the exploded EAR, is this behavior correct?
Or am I missing something here?
Thanks!

Hi,
If you are only attempting to read the file, you should read the file as a resource. If you are planning on writing to this file, then it is not a good idea that you depend on where this file is deployed, just place it anywhere else.
Anyhow, if you have to do it, the best way is to obtain the resource URL, and from that the file name. BTW, there is no warranty that the war will get exploded, that you may be able to freely modify the file, nor that the file name be null :-S
{the Classloader of your choice}.getResource(<Resource name>).getFile()
should do the trick.
Regards,
LG

Exploded EAR welcome-file problem

I setup an Exploded Ear application in WLS6.1 sp1 on NT.
It works fine except the welcome page.
when I try http://localhost:7001/MyApp it gives the attached
error message. It works fine if I type .../MyApp/index.jsp.
even I tried with exploded banking example. It doesn't work either.
Error message on browser
Error 403--Forbidden
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization
will not help and the request SHOULD NOT be repeated. If the request method was
not HEAD and the server wishes to make public why the request has not been fulfilled,
it SHOULD describe the reason for the refusal in the entity. This status code
is commonly used when the server does not wish to reveal exactly why the request
has been refused, or when no other response is applicable.
Please can anybody help me.
Thanx
Sankar venkat.

[att1.html]

Exploded EAR deployment supported?

Hi,
I am currently developing with the MyEclipse IDE. Does Sun Java Studio Enterprise 8.1 support exploded deployment of EARs, and can it 'hot deploy' changes into the running Application Server?
Thank You

Hi.
SJSE 8.1 doesn't support exploded deployment of EAR projects. It currently supports exploded deployment of WAR projects.
I know that folks have extended NetBeans to support exploded EAR deployment in NB 6.0...
You can find out more about that in this blog entry and screencast:
http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_directory
http://serverplugins.netbeans.org/screencasts/pfsc1.html
Can you clarify what you mean by 'hot deploy'? Different folks have different definitions of this phrase... I think SJSE 8.1 does 'hot deploy' as I understand it... but my understanding may not match your vision of this feature...
vbk

Deploying exploded ear file

Hi,
I have exploded an ear file, and I am trying to deploy it in weblogic 7.0.
This ear has several jars and war files.
However, when I deploy it
(Access is denied) at java.io.FileInputStream.open(Native Method) -- while trying
to open the war file.
I have followed the same steps as mentioned in the bea docs , by exploding all
the individual wars, jars, inside the ear ..
Any help is appreciated..
Thanks in advance.

I believe manifest class-paths should work fine for exploded EARs as
well. Don't you want 'common' rather than '../common' in your
class-path entry?
-- Rob
Eric Ma wrote:
Rob:
Yes, I was talking about the MANIFEST.MF Class-Path entries. My exploded ear
looks like (under mydomain/applications)
app
--META-INF
----application.xml
--ejb
----com
------abc.class
----META-INF
------MANIFEST.MF
------ejb-jar.xml
--common
----com
------xyz.class
--web
----jsp
----WEB-INF
------web.xml
------lib
--------struts.jar
The MANIFEST.MF file has
Class-Path: ../common/
I read at http://e-docs.bea.com/wls/docs61/ejb/EJB_deployover.html#1074087 that
Class-Path is only supported in the .ear format. Is it true?
Rob Woollen <[email protected]> wrote:
Are you talking about manifest class-path entries? If so, can you show
me what your exploded EAR looks like? (ie its layout and your
class-path entries.)

Application deployment questions

I am looking for help to get proper deployment procedure. Right now it is setup as following:
There is exploded ear ROOT.ear on nfs. Domain has admin server and two managed servers in cluster, on different servers.
For new code deployment we:
stop managed servers,
create new ear file/folder with date stamp,
link ROOT.ear to new folder,
restart coherence (it needs jars from deployment) and do some other necessary stuff,
start managed servers.
We do not explicitly ask to redeploy application, weblogics pick up the latest code. I do not deploy app to Admin Server.
Application is deployed on servers in nostage mode, so they read data from the exploded ear on nfs.
While it works most of the time, sometimes developers complain that it seems there is some stale code in new deployment. Not sure how it is possible.
Is this a good way to deploy applications at all? Can it be improved if it is not good way of doing it?
I noticed also that managed servers do not clean up its tmp folders. Should I manually do it when server is down?
Thanks,
Oleg

You can check the values set for "page-check-seconds", "resource-reload-check-secs", and "servlet-reload-check-secs" in weblogic.xml of you application.
Link : [http://e-docs.bea.com/wls/docs92/webapp/weblogic_xml.html]
I hope you are not using any symbolic links and refreshing them dynamically. Weblogic may not refresh the values of the symbolic links AFAIK.
Edited by: mchellap on May 12, 2009 11:32 PM

How to Deploy portal 8.1 production cluster in exploded ear format in solaris

Hi all,
How can we deploy our PORTAL application in
Weblogic 8.1 SP2 Weblogic 8.1 SP2 Weblogic 8.1 SP2 Weblogic 8.1 SP2
Solaris Solaris Solaris Solaris Solaris Solaris
PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL
APPLICATION
with PRODUCTION MODE = true PRODUCTION MODE = true PRODUCTION MODE = true
PRODUCTION MODE = true
Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster
Cluster (2 x 2 managed servers)
As
exploded ear format exploded ear format exploded ear format exploded ear
format exploded ear format
PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE
don't send me this link
http://e-docs.bea.com/wlp/docs81/deploy/deploy.html#1003591
I used this link 100 times, but no use.
Steps I did
1. Build the application using workshop ( NO ear NO ear NO ear NO ear NO ear
NO ear NO ear NO ear )
2. use wlpackage to pack the built application ( NO ear NO ear NO ear NO
ear NO ear NO ear NO ear NO ear )
3. Deploy using console ( NO stage NO stage NO stage NO stage NO stage)
The Error,
The following error message I got.
[Deployer:149033]preparing application commApp on mgServer1
[Deployer:149033]preparing application commApp on mgServer2
[Deployer:149033]failed application commApp on mgServer1
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is
packaged using the WebLogic Split Development Directory structure. The Split
Development Directory structure can only be used in development environments
with a single WebLogic Server. If you wish to deploy this application to a
separate managed server or cluster, use the wlpackage ant task to create an
exploded or archived EAR.
[Deployer:149033]failed application commApp on mgServer2
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is
packaged using the WebLogic Split Development Directory structure. The Split
Development Directory structure can only be used in development environments
with a single WebLogic Server. If you wish to deploy this application to a
separate managed server or cluster, use the wlpackage ant task to create an
exploded or archived EAR.
Thanks,
Karthi.

Its simple PORTAL application . After deploying this application we can add portlets as a childs to this application .
Now this is simple PORTAL application with CSS file.
Give me some idea about
How to create PORTLET application with CSS files . Where to include this CSS file in a PORTLET application??????
Normally we are creating first PORTAL application and adding CSS files to
Portlet Content-->Themes-->html--> abc.css .
--> Head.jsp we are giving the css file path in this JSP page as
<link href='<wps:urlFindInTheme file="abc.css"/>' rel="styleSheet" type="text/css">
After this I am adding my PORTLET application to this PORTAL .
Then its working fine. But I want to know how to add CSS files to PORTLET application???????
Please help me :-(

Deploying Portal App in exploded EAR format

Hi all,
We are using Portal BEA 8.1 SP2 and we also configured a cluster with
production mode enabled.
We want to deploy our portal app in exploded EAR format.
http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723
But when we use workshop to "Build App" and when the application build is successful.
And when we copy the App folder to the production server and deploy,
We get the following error,
[Deployer:149033]preparing application commApp on mgServer1
[Deployer:149033]preparing application commApp on mgServer2
[Deployer:149033]failed application commApp on mgServer1
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is packaged using the WebLogic Split Development Directory structure. The Split Development Directory structure can only be used in development environments with a single WebLogic Server. If you wish to deploy this application to a separate managed server or cluster, use the wlpackage ant task to create an exploded or archived EAR.
[Deployer:149033]failed application commApp on mgServer2
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is packaged using the WebLogic Split Development Directory structure. The Split Development Directory structure can only be used in development environments with a single WebLogic Server. If you wish to deploy this application to a separate managed server or cluster, use the wlpackage ant task to create an exploded or archived EAR.
What is the problem ?
Thanks,
Karthi.
[att1.html]

To deploy the app as EAR (I am confused by the expression "exploed EAR", my understanding
its either exploded or EAR format) build the app as EAR (there is an option in
the workshop build drop down).
Did this help?
S
"Karthi" <[email protected]> wrote:
>
>
Hi all,
We are using Portal BEA 8.1 SP2 and we also configured a cluster with
production mode enabled.
We want to deploy our portal app in exploded EAR format.
http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723
But when we use workshop to "Build App" and when the application build
=
is successful.=20
And when we copy the App folder to the production server and deploy,=20
We get the following error,
[Deployer:149033]preparing application commApp on mgServer1
[Deployer:149033]preparing application commApp on mgServer2
[Deployer:149033]failed application commApp on mgServer1
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
=
application commApp on devCluster,bkarthiPS.:=20
Exception:weblogic.management.ApplicationException: Application commApp
=
is packaged using the WebLogic Split Development Directory structure.
=
The Split Development Directory structure can only be used in =
development environments with a single WebLogic Server. If you wish to
=
deploy this application to a separate managed server or cluster, use
the =
wlpackage ant task to create an exploded or archived EAR.
[Deployer:149033]failed application commApp on mgServer2
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
=
application commApp on devCluster,bkarthiPS.:=20
Exception:weblogic.management.ApplicationException: Application commApp
=
is packaged using the WebLogic Split Development Directory structure.
=
The Split Development Directory structure can only be used in =
development environments with a single WebLogic Server. If you wish to
=
deploy this application to a separate managed server or cluster, use
the =
wlpackage ant task to create an exploded or archived EAR.
What is the problem ?
Thanks,
Karthi.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#c0c0c0 background=3D"">
<DIV><FONT face=3DArial size=3D2>Hi all,<BR><BR>We are using Portal BEA
=
8.1 SP2 and=20
we also configured a cluster with<BR>production mode enabled.<BR><BR>We
=
want to=20
deploy our portal app in exploded EAR=20
format.<BR><BR>http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723=
<BR><BR>But=20
when we use workshop to "Build App" and when the application build is=20
successful. <BR><BR>And when we copy the App folder to the production
=
server and=20
deploy, <BR><BR>We get the following =
error,<BR><BR>[Deployer:149033]preparing=20
application commApp on mgServer1<BR>[Deployer:149033]preparing =
application=20
commApp on mgServer2<BR>[Deployer:149033]failed application commApp on=20
mgServer1<BR>[Deployer:149034]An exception occurred for task=20
[Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:=20
<BR>Exception:weblogic.management.ApplicationException: Application =
commApp is=20
packaged using the WebLogic Split Development Directory structure. The
=
Split=20
Development Directory structure can only be used in development =
environments=20
with a single WebLogic Server. If you wish to deploy this application
to =
a=20
separate managed server or cluster, use the wlpackage ant task to create
=
an=20
exploded or archived EAR.<BR>.<BR>[Deployer:149033]failed application
=
commApp on=20
mgServer2<BR>[Deployer:149034]An exception occurred for task=20
[Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:=20
<BR>Exception:weblogic.management.ApplicationException: Application =
commApp is=20
packaged using the WebLogic Split Development Directory structure. The
=
Split=20
Development Directory structure can only be used in development =
environments=20
with a single WebLogic Server. If you wish to deploy this application
to =
a=20
separate managed server or cluster, use the wlpackage ant task to create
=
an=20
exploded or archived EAR.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>What is the problem ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Karthi.</FONT></DIV></BODY></HTML>

Deploying Weblogic 8 EAR in exploded format

Hello,
Sorry, was lil away from WLS...
Is there a way I can deploy EAR in the exploded directory structure which means all the WARs included in
the EAR also need to be in exploded structure.
Thanks

I'm not sure I understand exactly what you want to know.
You can deploy applications via the WebLogic Console, the command-line
utility weblogic.Deployer, or the ant-task wldeploy.
Any of these should work fine with an exploded ear.
-- Rob
A B wrote:
Sorry Rob, I did not see the answer..
What do I need to do to deploy WLS8 ear in exploded format?
Thanks

Deployment question: exploded EAR application

Similar Messages

Maybe you are looking for