EAR Deployment Problem UNIX vs Windows

Hi Experts,
My WAS is 6.40. We are running on AIX Unix System. On my portal I need to deploy an EAR File. I can very well deploy that EAR file through the SDM but when I try to call the JSP, it throws an error "No calss def found". This error corresponds to a Class file which is inside a JAR. It is not able to locate that class file. We are using some external JARS. I have packages these JARS in my EAR.
One point to notice is that If I deploy this EAR on a WINDOWS server. It runs absolutely fine and it also is able to find the class in the JARS. The problem is with the AIX UNIX server only.
Is there some config that I need to do on the UNIX system ? I think the EAR structure is giving the problem. But then It should not run on Windows also.
Any suggestions ?
Regards
/sab

HI Kedar,
Thanks for your reply. Do u mean to say that the JARS for AIX have to be different ?
One observation. The EAR works fine on SAP WAS (Windows) and TOMCAT (Windows) but refuses to run on AIX.
Following is the error :
Application error occurred during request processing.
Details: java.lang.NoClassDefFoundError: tellustech/licensing/ClientChecker
Exception id: [001125A6424A0054000000060007608C00043ECE62BAC38A]
What is it about the .SO files ? What is their role in this chain ? Can u pleaese help me undesrand that more ?
"3. As you have mentioned the problem causes if files mismatch between 32 bit & 64 bit." what I had mentioned was a question asking that If my AIX box is 64 bit and I develop my application on a 32 bit laptop. Whould this kind of difference cause this problem ?
So u mean to say that I should provide the following Info to my JAR provider for giving me JARS specific to AIX?
1.Machine Type
2.Operating System
3.Processor
4.System Type
5.Operating System Version
6.Release Level
7.CPU Version
8.Java Version
9.Java Path
10.Compiler Used
11.Compiler Path
Dont worry about the points U'll get the max. Help me resolve this ?
Are u in India, can we talk on the phone for this. I really need to fix this ASAP.
Regards
/sab

Similar Messages

War an ear deployment problem

hi,
I got a war and ear that share common classes. I would like to deploy both of them on the same application server.
I started with weblogic and it worked fine.
Now I am running it on Websphere - the problem is the ear application failed to start - it cant find one of it's property files even though it is in the class path.
I see that the jar containing all the properties is in the class path - the application can access all other properties files except this one.
The problematic properties file is my.commons.logging.properties which is a refactoring to the common.logging jar.
I also see that if the war is not deployed - the ear is deployed without a problem.
the war contains commons.logging.properties and because Websphere also had it's own common.logging i had to use "parent last" for the war deployment.
If i change the load order of the applications(the ear is loaded first) - the properties file is found.
I will be happy to hear any idea you got about this.
I don�t understand how two different applications affect each other that way.
Thanks!!!

Sounds like a bug. You can report it to [email protected]
-- Rob

Ear deploy problems if dir contains '.' in the name

Is there a fix that will allow Weblogic 8.1 SP for RedHat to deploy an ear that contains directory structure containing '.' in the name?
We currently have to extract the ear and modify the application.xml to deploy the app in question due to this limitation.

"Don Maxwell" <[email protected]> wrote in message news:27286804.1095364176807.JavaMail.root@jserv5...
Is there a fix that will allow Weblogic 8.1 SP for RedHat to deploy an ear that contains directory structure containing '.' in thename?
>
We currently have to extract the ear and modify the application.xml to deploy the app in question due to this limitation.What is the problem? Can you show a stacktrace?
óÌÁ×Á

WSDL Web Services Client and EAR deploy problem

Hi!
I have allready posted this on "Web AS General", with no result.
So I hope this forum is a better choise.
Environment:
SAP EP / SAP NW04 / SPS14
NW DevStudio
I just deployed an ear file (first time ...) with SDM.
The ear file represents an auto generated web services client on basis of a WSDL file.
(done from web services perspective in NWDS choosing "New Deployable Proxy Project")
When running a test I get the following error:
"Could not find portal application Unknown provider of external application: J2EE::sap.com/NWTPINWSClient"
.. where NWTPINWSClient is the name of the EAR - file
The test code contains this:
The portalapp.xml has the following tag:
<application-config>
<property name="SharingReference" value="J2EE::sap.com/NWTPINWSClient">
</property>
</application-config>
I'm new to this, so please feel free to consider newbie misstakes.
BRGRDS
Peter M

Can you/anybody post solution. I have the same problem.
Thanks
Srinivas

EAR Deployment Problem with weblogic 10.2. Need help.

Hi,
I have a EAR file exported from MyEclipse IDE. When i am deploying the EAR file in weblogic 10.2, i am not seeing classess and properties were not exploded under WEB-INF/classes in the web project. I can see the classes folder but it's empty.
When i opened i can see EJB project JAR file and web project .war file in the EAR file. I checked the .war file content and i can see all the classes and properties available in the .war file.
Please help me to find, why the classes and properties are not being exploded when i am deploying as package.
Note: When i am deploying from myeclipse as exploded deployment i was able to run the application but i am failing when i deploy as a package (.ear file).
Thank you,
Vijay M

I found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html

Display image in forms & reports developed on windows and deployed on Unix

Hi,
We are upgrading from Forms and reports 6i to forms10g.
We need to insert image in forms and reports. Recompile and deploy on unix server.
So can anyone let me know the exact steps to create jar file containing images, where to place the jar file.
Corresponding folder, file and configuration changes required on windows and unix.
Av.

Hi Frank,
thanks for the link it helped me in understanding how images work for forms.
But my real concern is how this will work in reports?
As we dont have any reportsweb.cfg nor any java path for reports?
Can you help me in understanding how to embed image in reports that will be displayed even after porting the report on unix oas.
Regards,
Av.

Deployment problems EAR & WAR

I have serious problems deploying an EAR, containing 25 ejb-jars and 3 wars.
The history of the project is that it was first developed on WLS 4.5 & 5.1. We
have later moved to Orion were the actual development takes place. Now we can
run the application on Orion and WLS 5.1. We now want to deploy the application
on WLS 6.1 sp 2. We have setup the whole application to be deployed as one EAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think it was).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to the console,
however when I tried to access servlets or JSPs, they simply weren't there (Error
404--Not Found). When I deployed the EAR from the console I got a number of zipexceptions.
After asking around, I was recommended to remove the compression in the jar,war
& earfiles. When I did that I got a number of errors in static initializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed those and
the application was deployed without errors (when I start WLS and the EAR is deployed
by being in the config.xml file). Still when I deploy it from the console it still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there. The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'm also
confident that modules are correct, it does work in Orion, which has similar classloading.
From other developers, I have heard that I need to use WLS 6.1 sp 2, no compression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB) files.
What really annoys me that I do not seem to get any errors, logs or anything.
The console indicates that everything is deployed even if apparently is not.
And I can deploy PerStore and everything works. If I deploy the wars, and ejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I think that
I have to skip my first intent and deploy an exploded EAR instead of having (almost)
the same deployement as in Orion, which kind of pisses me of. I am also disappointed
that BEA has apperantly skipped java-modules all together. It is after all in
the specification.
I have talked to a number of people and they say that the whole EAR deployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik Romson

EAR deployment works fine from my own experience. Use JAR and turn off
compression for the WARs and JARs and the EAR itself, although I've never
seen a ZIP exception and I use JAR and ZIP and Winzip and whatever else I
can grab to muck with the files. 6.5MB is not tiny, but it isn't very large
either -- WL can handle much bigger EARs. Normally we don't suggest having
so many JARs and WARs in the EAR, but that is more preference ... are you
using manifest class path? ... are you referring to any of the files in the
WARs from any of the classes in the JARs?
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Erik Romson" <[email protected]> wrote in message
news:[email protected]...
>
I have serious problems deploying an EAR, containing 25 ejb-jars and 3wars.
The history of the project is that it was first developed on WLS 4.5 &5.1. We
have later moved to Orion were the actual development takes place. Now wecan
run the application on Orion and WLS 5.1. We now want to deploy theapplication
on WLS 6.1 sp 2. We have setup the whole application to be deployed as oneEAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think itwas).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to theconsole,
however when I tried to access servlets or JSPs, they simply weren't there(Error
404--Not Found). When I deployed the EAR from the console I got a numberof zipexceptions.
After asking around, I was recommended to remove the compression in thejar,war
& earfiles. When I did that I got a number of errors in staticinitializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed thoseand
the application was deployed without errors (when I start WLS and the EARis deployed
by being in the config.xml file). Still when I deploy it from the consoleit still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there.The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'malso
confident that modules are correct, it does work in Orion, which hassimilar classloading.
>
From other developers, I have heard that I need to use WLS 6.1 sp 2, nocompression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB)files.
>
What really annoys me that I do not seem to get any errors, logs oranything.
The console indicates that everything is deployed even if apparently isnot.
>
And I can deploy PerStore and everything works. If I deploy the wars, andejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I thinkthat
I have to skip my first intent and deploy an exploded EAR instead ofhaving (almost)
the same deployement as in Orion, which kind of pisses me of. I am alsodisappointed
that BEA has apperantly skipped java-modules all together. It is after allin
the specification.
I have talked to a number of people and they say that the whole EARdeployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik Romson

J2ee Deployment problem

Hi All,
I created a simple j2ee appl .
I deployed that ......
It shows some error like this
12:12:42 PM /userOut/deploy (com.tssap.j2ee.ui.core.deploy.DeployThreadManager) [Deploy Thread] ERROR:
Finished deployment of file:C:/Documents and Settings/Nageswar_Mandapati/Documents/SAP/workspace/myEarProject/myEarProject.ear
Deploy exception : Server epl did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server epl at port 50018: Connection refused: connect
Inner exception was : Server epl did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server epl at port 50018: Connection refused: connect
Deploy with SDM
==> Host is : epl
==> Port is : 50018
Pls help me...
SDM node not started and it is only red color.
regards
BHI

I assume you are working on Windows. If not use the appropriate UNIX commands to stop and start SAP (stopsap j2ee; startsap).
On Windows go to your management console and stop the Instance 00. Restart the instance again. After startup look in the process list to make sure SDM is running correctly and the node should be green. If not take a look at your startup logs to identify the problem.

Deployment problem.

What I did wrong? This is a fusion web application, works fine in IDE, but I cannot deploy it.
---- Deployment started. ---- Oct 19, 2008 10:29:54 AM
Target platform is (Weblogic 10.3).
Running dependency analysis...
Building...
2008-10-19 10:31:25.515: Writing WAR file to C:\JDeveloper\mywork\AppSimple\ViewController\deploy\AppSimple_ViewController_webapp1.war
2008-10-19 10:31:36.343: Wrote WAR file to C:\JDeveloper\mywork\AppSimple\ViewController\deploy\AppSimple_ViewController_webapp1.war
2008-10-19 10:31:36.671: Writing WAR file to C:\JDeveloper\mywork\AppSimple\ViewController\deploy\AppSimple.war
2008-10-19 10:31:44.625: Wrote WAR file to C:\JDeveloper\mywork\AppSimple\ViewController\deploy\AppSimple.war
WARNING: The commonly named resources listed below could cause reusability errors for your consumers.
Provide a more unique name for the indicated resources in this project, or start with a different project.
model/DataBindings.cpx
model/Model.jpx
model/common/bc4j.xcfg
Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
Wrote JAR file to C:\JDeveloper\mywork\AppSimple\Model\deploy\AppSimple_Model_adflibAppSimple1.jar
2008-10-19 10:31:52.703: Writing EAR file to C:\JDeveloper\mywork\AppSimple\deploy\AppSimple_application1.ear
2008-10-19 10:32:03.406: Wrote EAR file to C:\JDeveloper\mywork\AppSimple\deploy\AppSimple_application1.ear
Deploying Application...
[Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppSimple_application1 on examplesServer.: Unmarshaller failed.
weblogic.management.DeploymentException: Unmarshaller failed
#### Deployment incomplete. #### Oct 19, 2008 10:33:04 AM
Deployment Failed
This is mesage on server:
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=
48m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=C:\oracle\Middleware\wlserver_10.3\samples\server\examples\build\serve
rclasses;C:\oracle\MIDDLE~1\patch_wlw1030\profiles\default\sys_manifest_classpat
h\weblogic_patch.jar;C:\oracle\MIDDLE~1\patch_wls1030\profiles\default\sys_manif
est_classpath\weblogic_patch.jar;C:\oracle\MIDDLE~1\patch_jdev1111\profiles\defa
ult\sys_manifest_classpath\weblogic_patch.jar;C:\oracle\MIDDLE~1\patch_cie660\pr
ofiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\oracle\MIDDLE~1\JDK1
60~1\lib\tools.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\o
racle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\oracle\MIDDLE~1\modules\fea
tures\weblogic.server.modules_10.3.0.0.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\
lib\webservices.jar;C:\oracle\MIDDLE~1\modules\ORGAPA~1.5/lib/ant-all.jar;C:\ora
cle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\oracle\MIDDLE~1\WLSERV
~1.3\common\eval\pointbase\lib\pbembedded57.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\co
mmon\eval\pointbase\lib\pbclient57.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\
xqrl.jar;;
PATH=C:\oracle\MIDDLE~1\patch_wlw1030\profiles\default\native;C:\oracle\MIDDLE~1
\patch_wls1030\profiles\default\native;C:\oracle\MIDDLE~1\patch_jdev1111\profile
s\default\native;C:\oracle\MIDDLE~1\patch_cie660\profiles\default\native;C:\orac
le\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\oracle\MIDDLE~1\WLSERV~1.3\server
\bin;C:\oracle\MIDDLE~1\modules\ORGAPA~1.5\bin;C:\oracle\MIDDLE~1\JDK160~1\jre\b
in;C:\oracle\MIDDLE~1\JDK160~1\bin;C:\oracle\ora92\bin;C:\Program Files\Oracle\j
re\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOW
S;C:\WINDOWS\System32\Wbem;C:\oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oc
i920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Starting WLS with line:
C:\oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThre
shold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dootb.examples.url.name=/inde
x.jsp -Xverify:none -da -Dplatform.home=C:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.hom
e=C:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\oracle\MIDDLE~1\WLSERV
~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.tes
tConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\oracle\MIDDLE~1\patch
wlw1030\profiles\default\sysextmanifest_classpath;C:\oracle\MIDDLE~1\patch_wls
1030\profiles\default\sysext_manifest_classpath;C:\oracle\MIDDLE~1\patch_jdev111
1\profiles\default\sysext_manifest_classpath;C:\oracle\MIDDLE~1\patch_cie660\pro
files\default\sysext_manifest_classpath -Dweblogic.Name=examplesServer -Djava.se
curity.policy=C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy weblogi
c.Server
<Oct 19, 2008 10:27:12 AM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following
extensions directory contents added to the end of the classpath:
C:\oracle\Middleware\patch_wls1030\profiles\default\sysext_manifest_classpath\we
blogic_ext_patch.jar;C:\oracle\Middleware\wlserver_10.3\L10N\beehive_ja.jar;C:\o
racle\Middleware\wlserver_10.3\L10N\beehive_ko.jar;C:\oracle\Middleware\wlserver
_10.3\L10N\beehive_zh_CN.jar;C:\oracle\Middleware\wlserver_10.3\L10N\beehive_zh_
TW.jar;C:\oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ja.jar;C:\oracle\Middlew
are\wlserver_10.3\L10N\p13n_wls_ko.jar;C:\oracle\Middleware\wlserver_10.3\L10N\p
13n_wls_zh_CN.jar;C:\oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;C:\
oracle\Middleware\wlserver_10.3\L10N\testclient_ja.jar;C:\oracle\Middleware\wlse
rver_10.3\L10N\testclient_ko.jar;C:\oracle\Middleware\wlserver_10.3\L10N\testcli
ent_zh_CN.jar;C:\oracle\Middleware\wlserver_10.3\L10N\testclient_zh_TW.jar;C:\or
acle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ja.jar;C:\oracle\Middleware\wls
erver_10.3\L10N\tuxedocontrol_ko.jar;C:\oracle\Middleware\wlserver_10.3\L10N\tux
edocontrol_zh_CN.jar;C:\oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_TW
.jar;C:\oracle\Middleware\wlserver_10.3\L10N\workshop_ja.jar;C:\oracle\Middlewar
e\wlserver_10.3\L10N\workshop_ko.jar;C:\oracle\Middleware\wlserver_10.3\L10N\wor
kshop_zh_CN.jar;C:\oracle\Middleware\wlserver_10.3\L10N\workshop_zh_TW.jar>
<Oct 19, 2008 10:27:14 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting We
bLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsys
tems Inc.>
<Oct 19, 2008 10:27:16 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLog
ic Server Temporary Patch for CR380042 Thu Sep 11 13:33:40 PDT 2008
WebLogic Server Temporary Patch for 7372756 Fri Sep 12 17:05:44 EDT 2008
WebLogic Server 10.3 Mon Aug 18 22:39:18 EDT 2008 1142987 >
<Oct 19, 2008 10:27:24 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to STARTING>
<Oct 19, 2008 10:27:24 AM EDT> <Info> <WorkManager> <BEA-002900> <Initializing s
elf-tuning thread pool>
<Oct 19, 2008 10:27:25 AM EDT> <Notice> <Log Management> <BEA-170019> <The serve
r log file C:\oracle\Middleware\wlserver_10.3\samples\domains\wl_server\servers\
examplesServer\logs\examplesServer.log is opened. All server side log events wil
l be written to this file.>
<Oct 19, 2008 10:27:39 AM EDT> <Notice> <Security> <BEA-090082> <Security initia
lizing using security realm myrealm.>
<Oct 19, 2008 10:27:52 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to STANDBY>
<Oct 19, 2008 10:27:52 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to STARTING>
47 reviewService INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kern
el.Default (self-tuning)'] openjpa.Runtime - Starting BEA Kodo 4.2.0load03
109 reviewService INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.ker
nel.Default (self-tuning)'] openjpa.jdbc.JDBC - Using dictionary class "org.apac
he.openjpa.jdbc.sql.PointbaseDictionary".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After the server has booted, your browser should
automatically launch and point to the
BEA WebLogic Server Samples Introduction Page
running on this server. If your browser fails to launch,
point your browser to the following URL:
"http://68.197.139.27:7001/examplesWebApp/index.jsp"
Note: On Unix-based systems, browser defaults to Netscape.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[LoginFilter]: LoginFilter constructed ...
<Oct 19, 2008 10:28:49 AM EDT> <Notice> <Log Management> <BEA-170027> <The Serve
r has established connection with the Domain level Diagnostic Service successful
ly.>
<Oct 19, 2008 10:28:49 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to ADMIN>
<Oct 19, 2008 10:28:49 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to RESUMING>
<Oct 19, 2008 10:28:50 AM EDT> <Notice> <Security> <BEA-090171> <Loading the ide
ntity certificate and private key stored under the alias DemoIdentity from the j
ks keystore file C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<Oct 19, 2008 10:28:50 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\oracle\MIDDLE~1\WLSERV~1.3\server\li
b\DemoTrust.jks.>
<Oct 19, 2008 10:28:50 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\oracle\MIDDLE~1\JDK160~1\jre\lib\sec
urity\cacerts.>
<Oct 19, 2008 10:28:51 AM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultS
ecure[1]" is now listening on 127.0.0.1:7002 for protocols iiops, t3s, ldaps, ht
tps.>
<Oct 19, 2008 10:28:51 AM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultS
ecure" is now listening on 68.197.139.27:7002 for protocols iiops, t3s, ldaps, h
ttps.>
<Oct 19, 2008 10:28:51 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[
1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.
>
<Oct 19, 2008 10:28:51 AM EDT> <Warning> <Server> <BEA-002611> <Hostname "localh
ost", maps to multiple IP addresses: 68.197.139.27, 127.0.0.1>
<Oct 19, 2008 10:28:51 AM EDT> <Warning> <Server> <BEA-002611> <Hostname "privat
e-q10rki6", maps to multiple IP addresses: 68.197.139.27, 127.0.0.1>
<Oct 19, 2008 10:28:51 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default"
is now listening on 68.197.139.27:7001 for protocols iiop, t3, ldap, snmp, http
.>
<Oct 19, 2008 10:28:51 AM EDT> <Notice> <WebLogicServer> <BEA-000331> <Started W
ebLogic Admin Server "examplesServer" for domain "wl_server" running in Developm
ent Mode>
<Oct 19, 2008 10:28:51 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to RUNNING>
<Oct 19, 2008 10:28:51 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server st
arted in RUNNING mode>
<Oct 19, 2008 10:33:02 AM EDT> <Error> <J2EE> <BEA-160197> <Unable to load descr
iptor C:\oracle\Middleware\wlserver_10.3\samples\domains\wl_server\servers\examp
lesServer\upload\AppSimple_application1\app\AppSimple_application1.ear/META-INF/
application.xml of module AppSimple_application1.ear. The error is weblogic.desc
riptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(Mar
shallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDesc
riptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescript
orBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescr
iptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescrip
torBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescrip
torBean(AbstractDescriptorLoader2.java:768)
at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(A
pplicationDescriptor.java:311)
at weblogic.application.internal.EarDeploymentFactory.findOrCreateCompon
entMBeans(EarDeploymentFactory.java:174)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentM
Beans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(
MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBean
FactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationM
Bean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationF
orAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MB
eanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.co
mpatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.se
tupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:88)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.bea.xml.XmlException: weblogic.descriptor.BeanAlreadyExistsExcept
ion: Bean already exists: "weblogic.j2ee.descriptor.ModuleBeanImpl@f9378ab7(/Mod
ules[weblogic.descriptor.internal.DescriptorBeanKey@f80f1892])"
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(Refl
ectionUtils.java:54)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty
.setValue(RuntimeBindingType.java:531)
at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRunti
meProperty.fillCollection(AttributeRuntimeBindingType.java:385)
at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiI
ntermediary.java:52)
at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalOb
jectFromIntermediary(AttributeRuntimeBindingType.java:145)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(U
nmarshalResult.java:190)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(Unma
rshalResult.java:159)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(Unmarshalle
rImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(Mar
shallerFactory.java:141)
... 27 more
Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists:
"weblogic.j2ee.descriptor.ModuleBeanImpl@f9378ab7(/Modules[weblogic.descriptor.i
nternal.DescriptorBeanKey@f80f1892])"
at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceM
anager.java:227)
at weblogic.j2ee.descriptor.ApplicationBeanImpl.setModules(ApplicationBe
anImpl.java:422)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(Refl
ectionUtils.java:48)
... 35 more
.>
<Oct 19, 2008 10:33:02 AM EDT> <Error> <Deployer> <BEA-149605> <Failed to create
App/Comp mbeans for AppDeploymentMBean AppSimple_application1. Error - weblogic
.management.DeploymentException: Unmarshaller failed.
weblogic.management.DeploymentException: Unmarshaller failed
at weblogic.application.internal.EarDeploymentFactory.findOrCreateCompon
entMBeans(EarDeploymentFactory.java:189)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentM
Beans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(
MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBean
FactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationM
Bean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j
2ee.descriptor.ModuleBeanImpl@f9378ab7(/Modules[weblogic.descriptor.internal.Des
criptorBeanKey@f80f1892])"
at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceM
anager.java:227)
at weblogic.j2ee.descriptor.ApplicationBeanImpl.setModules(ApplicationBe
anImpl.java:422)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Truncated. see log file for complete stacktrace
>
<Oct 19, 2008 10:33:02 AM EDT> <Error> <Deployer> <BEA-149265> <Failure occurred
in the execution of deployment request with ID '1224426781031' for task '0'. Er
ror is: 'weblogic.management.DeploymentException: Unmarshaller failed'
weblogic.management.DeploymentException: Unmarshaller failed
at weblogic.application.internal.EarDeploymentFactory.findOrCreateCompon
entMBeans(EarDeploymentFactory.java:189)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentM
Beans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(
MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBean
FactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationM
Bean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j
2ee.descriptor.ModuleBeanImpl@f9378ab7(/Modules[weblogic.descriptor.internal.Des
criptorBeanKey@f80f1892])"
at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceM
anager.java:227)
at weblogic.j2ee.descriptor.ApplicationBeanImpl.setModules(ApplicationBe
anImpl.java:422)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Truncated. see log file for complete stacktrace
>
<Oct 19, 2008 10:33:03 AM EDT> <Warning> <Deployer> <BEA-149004> <Failures were
detected while initiating deploy task for application 'AppSimple_application1'.>
<Oct 19, 2008 10:33:03 AM EDT> <Warning> <Deployer> <BEA-149078> <Stack trace fo
r message 149004
weblogic.management.DeploymentException: Unmarshaller failed
at weblogic.application.internal.EarDeploymentFactory.findOrCreateCompon
entMBeans(EarDeploymentFactory.java:189)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentM
Beans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(
MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBean
FactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationM
Bean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j
2ee.descriptor.ModuleBeanImpl@f9378ab7(/Modules[weblogic.descriptor.internal.Des
criptorBeanKey@f80f1892])"
at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceM
anager.java:227)
at weblogic.j2ee.descriptor.ApplicationBeanImpl.setModules(ApplicationBe
anImpl.java:422)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Truncated. see log file for complete stacktrace
>
Edited by: SNikiforov on Oct 19, 2008 8:09 AM

Hi
I am also getting the Unmarshaller failed error.
I am trying to install my ADF 11.1.1 application on to the Standalone WLS 10.3 .while installing WLS i installed ADF runtime library also.
still i am getting it.
Can you tell me where i went wrong

Java develoment in unix or windows

Sometimes people ask u 'have u done java development in unix or wondows'. Whats the difference between developing java apps in unix or windows

also if you have developed under windows, and a few different unix platforms (Mac OS X, linux, solaris, HP/UX etc..) then you learn where the "Write Once, Run Anywhere" slogan doesn't quite hold (don't get me wrong this is usually in trivial ways)
eg. GUI layout needs a once-over on each platform usually just to make sure everything looks sensible, you may have relied on a behaviour of an API that was coincidental rather than in the spec, and another platform has implemented differently
there are also real-world deployment problems like users running your program on a machine that hasn't been patched properly, or hitting bugs in the API that only exist on one platform

RE: [iPlanet-JATO] Re: Deployment problem

Chidu,
I think that you are mired in the very common confusion of the default
behavior of the ApplicationServletBase.parsePathInfo() which will determine
the controlling/handling ViewBean via a URL design pattern. Lets take a look
at the URL
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
is decomposed as follows:
/NASApp -> well, this is long story but is absolutely necessary, welcome to
iAS
/MigtoolboxSampleAppWar -> is the web application name, taken as the name of
the WAR file when there is no EAR file (this allows the Servlet/JSP
container to deferences the web application root under
<ias>/APPS/modules/MigtoolboxSampleAppWar) I think this part of the URL is
called th Context Path
/MigtoolboxSample -> is the Servlet Path, and will either directly reference
or match a Servlet Mapping
for instance
<servlet-mapping>
<servlet-name>MigtoolboxSampleServlet</servlet-name>
<url-pattern>/MigtoolboxSample/*</url-pattern>
</servlet-mapping>
tells the Servlet Container that the Servlet Path
/MigtoolboxSample
maps to the Module Servlet MigtoolboxSampleServlet
This is how EVERY request makes its way to the "front controller" pattern in
JATO. It is fundamental to JATO Applicatioan that every request pass
through the ModuleServlet.
every else on the URL past the Servlet Path is the PATH INFO. Based on this
understanding, you will see why the
ApplicationServletBase.parsePathInfo()
is so important. In parsePathInfo() the PATH INFO is compared to the design
pattern
/VIEWBEANNAME*
to determine the handling ViewBean from the first String Token in the path
info. For instance, the starting URL of the Sample Application is
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage
The PATH INFO is [IndexPage]
and IndexPage[ViewBean] is the handling ViewBean. Therefore, any simiarl
URL like
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.matt
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.mike
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.chidu
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.XXX
will all result in the same handling View Bean
IndexPageViewBean
It is very important to understand that you CANNOT hit the JATO JSPs
directly. You must hit the "front controller" ModuleServlet which will
always delegate control to the handling ViewBean (a la, the "service to
workers" pattern)
You can attempt to hit the JSP directly but you need the right J2EE URL
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSampleApp/MigtoolboxSample/IndexPag
e.jsp
this URL will directly hit the JSP. However, you will recieve an error
because the JATO framework quickly determines that there is no
RequestContext in the HttpRequest attributes and assumes that the "front
controller" was bypassed. Try it. You will get ERROR.
Lets go back to what you are trying to do, place Models and Viewbeans in
separate directories. I recommend that you move the Models. Models are
ONLY referenced by TYPE via the ModelManager, the compiler will ensure that
your code is correct and matches the packages, file locations, import
statements, etc. ViewBeans, on the other hand are related to the
ModuleServlet their are contained in and are loaded via type names according
to a design pattern.
if you want to separate models and Viewbean then simply move the Model and
make sure everything compiles.
you cannot move the ViewBeans
if you do want to move the JSP peers of the Viewbeans, then you can put them
anywhere in the web application doc root. When you do, update the
DEFAULT_DISPLAY_URL as Mike suggested
matt
-----Original Message-----
From: Mike Frisino [mailto:<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217193234150166091061">Michael.Frisino@S...</a>]
Sent: Thursday, July 26, 2001 10:48 PM
Subject: Re: [iPlanet-JATO] Re: Deployment problem
Chidu,
Did you have it running fine in the original default configuration, before
you started changing things around? The URL should not access the .jsp
directly. The URL should look more like this
"/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage", without the
.jsp.
Also, please read the "Migration Tech Notes" document that is
linked to the
main doc index page. There is some information in there related
to trying to
run the sample application under iAS (see Tech Note 4 in
particular, "Note
on running the iMT "MigtoolboxSample" in iPlanet Application Server )
----- Original Message -----
From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164140244063078048234051197">chidusv@y...</a>>
Sent: Thursday, July 26, 2001 7:27 PM
Subject: [iPlanet-JATO] Re: Deployment problem
Hi Mike,
I tried changing the url in all the viewbeans to reflect the new sub-
directory for the viewbeans(I have placed the jsps and viewbeans in
a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
still not able to get access to the jsps. I basically see the
message "GX Error Socket Error Code missing!!" error on the browser
thrown by iPlanet, but the log doesn't tell me anything. Does the url
which I give to access the jsp change accordingly, i.e., should I
give something other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
If I try to use any other url other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
see the FileNotFoundException in the log.
I guess I'm still missing something.
Thanks for your help.
--Chidu.
--- In <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166136158139046209">iPlanet-JATO@y...</a>, "Mike Frisino" <<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217130152150">Michael.Frisino@S...</a>> wrote:
Chidu.
Did you also adjust the following member in each of the ViewBeans?
public static final String DEFAULT_DISPLAY_URL=
"/jatosample/module1/Index.jsp";
Try adjusting this to be consistent with your new hierarchy.
Also, if you still have problems, send us the error message thatyou recieve
when you try to access the page. That would help.
----- Original Message -----
From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164036129208">chidusv@y...</a>>
Sent: Thursday, July 26, 2001 4:48 PM
Subject: [iPlanet-JATO] Deployment problem
Hi,
We have a requirement to seperate the models and viewbeans and
keep
them in seperate directories. Is it possible to seperate the
viewbeans and models not be in the same directory?
I tried seperating the two in the MigtoolboxSampleApp application
provided by JATO. I changed the package and import statements
accordingly in the viewbeans, jsps and the models. But when I
deployed the application, I'm not able to access the Index page or
any of the jsps. Does the ApplicationServletBase always look forthe
viewbean in the same path as that of the module servlet?
Any help will be appreciated.
Thanks,
Chidu.
<a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
<a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
<a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>

Hi Mike,
I tried changing the url in all the viewbeans to reflect the new sub-
directory for the viewbeans(I have placed the jsps and viewbeans in
a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
still not able to get access to the jsps. I basically see the
message "GX Error Socket Error Code missing!!" error on the browser
thrown by iPlanet, but the log doesn't tell me anything. Does the url
which I give to access the jsp change accordingly, i.e., should I
give something other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
If I try to use any other url other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
see the FileNotFoundException in the log.
I guess I'm still missing something.
Thanks for your help.
--Chidu.
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
>
Chidu.
Did you also adjust the following member in each of the ViewBeans?
public static final String DEFAULT_DISPLAY_URL=
"/jatosample/module1/Index.jsp";
Try adjusting this to be consistent with your new hierarchy.
Also, if you still have problems, send us the error message that you recieve
when you try to access the page. That would help.
----- Original Message -----
From: <chidusv@y...>
Sent: Thursday, July 26, 2001 4:48 PM
Subject: [iPlanet-JATO] Deployment problem
Hi,
We have a requirement to seperate the models and viewbeans and
keep
them in seperate directories. Is it possible to seperate the
viewbeans and models not be in the same directory?
I tried seperating the two in the MigtoolboxSampleApp application
provided by JATO. I changed the package and import statements
accordingly in the viewbeans, jsps and the models. But when I
deployed the application, I'm not able to access the Index page or
any of the jsps. Does the ApplicationServletBase always look for the
viewbean in the same path as that of the module servlet?
Any help will be appreciated.
Thanks,
Chidu.
[email protected]

Deployment Problems of Enterprise Application in NWDS 7.1

Hello Everyone, 
 
I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer. SUMMARY 
~~~~~~~~~~~~~~~~~~~ 
Successfully deployed: 0 
Deployed with warnings: 0 
Failed deployments: 1 
~~~~~~~~~~~~~~~~~~~ 
ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it. 
 
1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear 
 Name:test~sgj_ent_app_test_three 
 Vendor:sap.com 
 Location:PDI_J2EETST1_D 
 Version:20100716152020 
 Deploy status:Aborted 
 Version:HIGHER 
 
 Description: 
 1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container. 
 
Exception: 
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
 at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
 at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 ... 11 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 ... 12 more
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
 at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
 at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
 at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Edited by: Savin on Aug 5, 2010 10:25 PM
Edited by: Savin on Aug 5, 2010 10:26 PM
Edited by: Savin on Aug 5, 2010 10:31 PM
Edited by: Savin on Aug 5, 2010 5:27 PM
Edited by: Savin on Aug 5, 2010 5:38 PM
Edited by: Savin on Aug 5, 2010 5:44 PM

Hi Veera/Abhi
I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
On my NWDS PDA Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
2009-02-11 13:02:40 ... (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
Madhu--
Please find my ans to the following points mentioned by you
1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
It is assigned
2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
Rule is activated
3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
Rule is activated
4) Make sure that you have installed the following components in the following sequence in the PDA
- Creme
- MinDB/DB2e
- PDA_eswt_container
- PDA Runtime.
Client is installed in this sequence only. I referrred to help.sap.com while installing
the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking up the data. giving the above mentioned error.
Regards
Priya

SCUP - Deploy Updates for both Windows 7 and Windows 8.1 rules Detection

Hi all,
I encounter a little issue regarding the update deployment from SCUP.
For example, I would like to deploy Firefox updates on both Windows 7 and Windows 8.1. Firefox Updates are deployed and installed on Windows 7 without any problem. But Nothing happen on Windows 8.1.
I think my problem is on my Installable Rule I have created. As it's not possible to select Windows 8.1 as a condiftion (like Windows 7) I have created a WMI query.
Before using a WMI query, I tried to use Major version and Minor version without success.
Does anyone has already used this sort of scenario ?

Shouldn't you do the following things (see also:
http://technet.microsoft.com/en-us/library/hh134743.aspx):
Add Windows Language is French to the top AND;
Change the second AND to an OR;
Add the WMI Query to the new OR (so it's at the same level as the
Windows Version = Windows 7 SP1);
Remove the last OR (as it's not being used anymore).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Migration from Sun to HP Unix to Windows

Hi ,
There is hardware and OS migration activity is scheduled in my current project. To give you the detail, BI system will be migrated from SUN to HP servers and OS will be changed from Unix to windows.
I am asked to test the system to check that any existing functionality that works before migration should work after migration.
I was suggested to have a look at the Installation guide to prepare the checklist. I know that the guides are available on service market place, however I am wondering which one I need to refer for the BI 7.0 installation.
Can any one please send the link of Installation guide specifically for BI 7.0. ?
If any one has done the similar kind of migration activity before then please share the pre and post migration test steps that you have performed during migration.
Regards,
Neeraj

Thanks Effen,
DB will remain ORACLE. I have just gone through the system copy guide . I found it bit confusing
I have prepared a list of all necessary activities and check required pre and post migration. Appreciate if you just have a look at it. Add any check that you think should be added in the list.
Pre Migration check:
SAP R3 Side:
u2022Take the snapshot of SM37 for all the LIS jobs whether it is in released state.
u2022Need to flush all the delta queues from LBWE
u2022Make the delta Queues Zero (By scheduling the respective info packages for the data targets).
SAP BW:
Analysis phase
u2022Understand the BW landscape and identify all Interfaces (SAP and Non SAP).
u2022Prepare a list of all outstanding issues of BAU. Also record all problems if any thing is broken and not working pre migration.
u2022Prepare the test scripts for technical and functional testing.
Migration Phase:
u2022Run process chain to flush all the delta queues.
u2022Remove all the jobs from Schedule position; identify all the chains based on event and Schedule chains.
u2022Stop all chains, remove them from schedule.
Post Migration check:
SAP R3 Side:
u2022Change the state of the jobs position from Schedule to Release and schedule the LBWE job to flush the records from LBWQ to RSA7 as per the one Hour frequency
u2022Check the next released job time and makes sure that the LBWE job is started sending the records from LBWQ to RSA7.
u2022Take the screen shots before sending the data from LBWQ to RSA7.
u2022Check for the number records in RSA7 as well as LBWQ.
u2022After the successful job run, check for the number of records in RSA7.
u2022Make sure that the records in RSA7 are matching with the LBWQ.
u2022Keep an eye on all the LIS jobs for two or three consequent runs.
SAP BW Side:
Technical Check:
u2022Before going to start the process chains, check all the source system connections. This includes SAP and Non SAP source systems.
u2022Check the connection of all SAP source systems with BW. Ensure that the RFC connection is established for all SAP source systems.
u2022Check the connection of all Non SAP source systems with BW. Ensure that the DB connect setting is correct and connection is established. Need to check all the source system connections through DB to make sure that all the tables/Views are not dropped out after migration. If there is any table with inactive status need to bring to the notice of the admin people of that particular database.
u2022Double check all the process chains based on Event and Schedule are successfully scheduled as per the existing timings.
u2022While scheduling the jobs, there might be some chances that system will automatically postpone the loads by one day based on the job priority defined, ensure that the jobs are running as per the scheduled date and time.
u2022Need to keep an eye on all the critical process chains like APO loads Etc... Mentioned in the excel sheet.
u2022Keep on monitoring the process chains running also compare the execution time for performance check.
u2022Randomly check the infocubes, update rules, Info objects and other objects and verify that the objects are in active mode.
u2022Ensure that all externally scheduled processes are rescheduled Backups, DB statistics, monitoring processes, etc
u2022Verify that the connectivity with SAP portal.
u2022For verifying the BI Java configuration, run the IP transaction RSPLAN, open BI admin cockpit and check that it is working fine after migration.
u2022Verify the all infocubes administration activities like index creation/deletion, aggregate roll up, compression & DB ststistics refresh are working fine after migration.
u2022Create/delete/ maintain BW objects: DSO, infocube, infosource, update rule, transformation, DTP etc in dev systems.
u2022Check that Full Request InfoPackage, Repair Full Request InfoPackage, Initialisation with Data Request InfoPackage, Initialisation without Data Request InfoPackage and Delta Request InfoPackage can be executed successfully.
u2022Check RSRV transactions for consistency.
u2022Create, delete and modify the Query in query designer. Verify that the query designer works properly after migraition.
Functional Check:
Execute all functional test scripts and validate that the data is being loaded in all relevant info providers.

IBFBS failed to deploy in Embedde OC4J but works with EAR deploy.

Hi
When i try to deploy IBFBS sample project in JDevloper by Embedde OC4J : its giving
an error saying "there is no EJB module to deploy".
But when i deployed through EAR deployment method its working fine.
PLease kindly help me.
Sai.

Hi,
Can you pls post the Version of JDeveloper and OC4J that you are using?
I tried to deploy IBFBS using JDeveloper 9.0.3.988 (JDK 1.3.1) on Standalone OC4J server (9.0.3) and it works fine.
One constraint for not running the application from JDeveloper (by using embedded OC4J) is that, the OC4J where the FBS is deployed needs to have the -userThreads option enabled.
This option is enabled by starting OC4J with -userThreads option.
java -jar oc4j.jar -userThreadsRef : Connection to embedded OC4J per FBS Setup Tutorial-Problem.
Let us know if your problem still persists.
Thanks
-- OTN@IDC Team

EAR Deployment Problem UNIX vs Windows

Similar Messages

Maybe you are looking for