EAR deploy in a not homogeneus Cluster

Hi,
          we a shared NFS Directory between the Cluster members and we like to deploy on some members only the Web Apps (Presentation) and on the others only the Ejbs (Application Layer). The Ear is currently unjared in a Directory, as the Web Apps in it. We noticed that using the Targets Attribute in config.xml for the different WebApps and Ejbs have no effect:
          <Application Deployed="true" Name="EAR_Test" Path="EAR_Test">
          <EJBComponent Name="EAR_TestBean" Targets="server2,server3" URI="EAR_TestBean.jar"/>
          <WebAppComponent Name="EAR_WebApp2" Targets="server1,server4" URI="EA_Test2"/>
          </Application>
          The Ejbs' Home are clusterable in the DDs.
          Is it possible to deploy an Ear in a not homogeneus Cluster or is it fantasy?
          Best Regards
          Carlo

Hi.
          I suppose it's possible, but I'm not sure how well it will work. Clustering is turned on by default for EJBs - you need to explicitly turn this off in the ejb deployment descriptors by setting home-is-clusterable to false.
          Carlo de Rossi wrote:
          > Hi,
          >
          > we a shared NFS Directory between the Cluster members and we like to deploy on some members only the Web Apps (Presentation) and on the others only the Ejbs (Application Layer). The Ear is currently unjared in a Directory, as the Web Apps in it. We noticed that using the Targets Attribute in config.xml for the different WebApps and Ejbs have no effect:
          > <Application Deployed="true" Name="EAR_Test" Path="EAR_Test">
          > <EJBComponent Name="EAR_TestBean" Targets="server2,server3" URI="EAR_TestBean.jar"/>
          > <WebAppComponent Name="EAR_WebApp2" Targets="server1,server4" URI="EA_Test2"/>
          > </Application>
          >
          > The Ejbs' Home are clusterable in the DDs.
          >
          > Is it possible to deploy an Ear in a not homogeneus Cluster or is it fantasy?
          >
          > Best Regards
          > Carlo
          >
          Michael Young
          Developer Relations Engineer
          BEA Support

Similar Messages

Problem with EAR deployment

hi,
i am getting following error while deploying ear application in WAS
an 10, 2008 11:29:26 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[018]Deployment aborted
Settings
SDM host : javadev0002
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/MOBILE1/LOCALS~1/Temp/temp44178ProcurmentEAR3.ear
Result
=> deployment aborted : file:/C:/DOCUME1/MOBILE1/LOCALS~1/Temp/temp44178ProcurmentEAR3.ear
Aborted: development component 'ProcurmentEAR3'/'sap.com'/'localhost'/'2008.01.10.11.28.46'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ProcurmentEAR3.. Reason: Errors while compiling:C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:80: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:87: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:94: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:185: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:192: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:199: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:281: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:288: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:295: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:369: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:376: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:456: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:463: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:79: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:86: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:175: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:182: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:189: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:262: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:269: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:349: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:356: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:436: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:443: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:527: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:534: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
26 errors
; nested exception is:      com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationException: Errors while compiling:C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:80: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:87: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:94: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:185: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:192: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:199: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:281: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:288: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:295: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:369: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:376: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:456: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:463: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:79: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:86: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:175: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:182: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:189: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:262: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:269: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:349: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:356: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:436: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:443: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:527: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:534: cannot resolve symbol
symbol : method getCategory ()
location: class com.sap.engine.services.rmi_p4.log.P4Logger
                         if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                ^
26 errors
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted

Hi Guruvulu,
I think the ear and war has not been successfully build.
Please build the war and ear successfully. Warning can be skipped.
Also try to restart your application server once before deployment and check whether all the process are running successfully.
Hope this will help you!!!
Regards,
Prashil

Web Services in an EAR Deployment

On deploying an EAR that includes a EJB web service JAR, I find that the WSDL url generated on the Web Services page is incorrect. For example for a web service named WebService1, the WSDL link shown on the WebServices page is ...oraclecloudapps.com/WebService1/WebService1?wsdl but is instead found at ...oraclecloudapps.com/WebService1?wsdl
Also the schemaLocation link within the WSDL is generated incorrectly. It appears as ....oraclecloudapps.com:443/WebService1/WebService1?xsd=1 but is instead found at oraclecloudapps.com:443/WebService1?xsd=1
This naturally leads to auto generation of web services client failing in NetBeans.
I have encountered this issue only when deploying a web service JAR as part of an EAR. It does not occur if the web service is directly part of a WAR that's being deployed.
Thanks
Harshad

Harshad ,
Thanks for pointing this issue, We will investigate and get back to you.

WebLogic Server EAR Deployment Queries!

Hi All,
I have few queries with respect to EAR deployment in BEA WebLogic Server
a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
Any pointers to info source will be REALLY appreciated.
Wiating for your reply.
Many Thanks in Advance,
C R Baradwaj

Hi,
Can anyone from BEA team help me in these queries?
This is very urgent!
have few queries with respect to EAR deployment in BEA WebLogic Server
a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
Thanks and Regards,
C R Baradwaj

WLS 11 Policy migration during EAR deployment

We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
Can anyone explain this behavior and verify if this is expected?
Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
/opt/oracle/admin/snidomain/aserver
/opt/oracle/admin/snidomain/mserver
The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
Can anyone explain this behavior and verify if this is expected?
Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
/opt/oracle/admin/snidomain/aserver
/opt/oracle/admin/snidomain/mserver
The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

How to reference sapjco from EAR deployment descriptors

Hello techies,
I´ve set up an EJB to use the JCo RFC Provider Service of the J2EE engine. Connection from R3 to EJB works but as soon as the EJB gets invoked, I get the error 'incompatible bean type - no processFunction found' from the RFCDefaultRequestHandler.invokeBean(..., JCO.Function) method.
The reason is clear to me - the JCO.Function class is loaded by different class loaders and thus the method parameters don´t match.
I´ve read in earlier postings that it is neccessary to reference the JCO in the module project and the ear deployment descriptor. That´s where my question begins.
How do I reference the JCO in the module project (what´s that?)? I think it has to do with the EJB jar, doesn´t it?
In the DeployTool I found a way how to set a reference to a library in the menu deploy-->libraries. But I am not sure what to specify here. I entered 'sapjco', since I saw an entry in the managers/library.txt file. Is that correct?
Any hints are welcome!
Regards,
Jan

Jan,
you can set the reference to the EAR project using the reference.txt file that exists in the /managers folder.
In the library.txt file set a path which is reference to sapjco.jar files..like
library JCO sapjco.jar
in the refernce.txt add the JCO referece to the EAR project...like
reference Project library:JCO
where Project here is the name of your EAR file..
Ravi

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

Deployed application is not picked up during weblogic startup

I'm having this strange problem, my application is deployed with java.Deployer
tool, works fine, then when ever i reboot the weblogic server, the application
is not accessible untill i explicitly redeploy it again.
Please help!

http://e-docs.bea.com/wls/certifications/certs_810/overview.html
Looks 141_03. But you have to understand what "certification" means.
Typically within minor revs of the VM 141_03 and 142 you are ok and there
should be no problems.
As for the proving it to you... There were lots of changes and improvemetns
to the 8.1 code line for deployment. As for knowing what your testing for,
OOM is a general error with no clear indication of where the problem lies,
its not clear if it is WLS version or the VM itself. I am sure you know the
hard answer there, it takes digging in with a profiler to find the culprit.
You have two options:
1) Drill down with a profiler in your env and figure out exactly WHAT is the
cause of the leak in the current environment
2) switch between different app verndors/versions and VMs.
Either way you have alot of varialbes to track, take care of and compare.
There is no silver bullet as always.
Cheers
mbg
"Stephen" <[email protected]> wrote in message
news:[email protected]...
>
BTW, is 8.1 certified with 1.4.2 on Solaris/Sparc yet? Otherwise it is anon-starter
>
"Stephen" <[email protected]> wrote:
SOS, we hear this one all the time, the new and improved version fixes
the problem.
Is this a 1.4.2 fix that helps 8.1 or something in the code that is
different?
be specific, I have this problem as well and am not willing to give it
another
try unless I know what I am testing for.
"Mark Griffith" <[email protected]> wrote:
My suggestion would be to try 8.1, I developed many sample applications
over
the course of the release and never had to restart the server and could
continually redeploy. The worst it got was having to completely
undeploy
and redeploy the application. (undeploy + redeploy is different that
just
redeploy).
Cheers
mbg
"Tom Wilson" <[email protected]> wrote in message
news:[email protected]...
This probably doesn't help but....we were doing our initial
development
using
Weblogic 7.0 using 1.3.1_08 but finally we got tired of dealing withthe
out
of memory issues resulting from continuously deploying new versionsof JSP
pages on our system. We found that running into the "Out of Memory"exceptions
combined with restarting and redeploying the app wasted too much time- an
average of 7 minutes about 7-8 times a day resulting in about 1 hourworth
of downtime for each developer using Weblogic. We finally trieddeveloping
our system with Tomcat and OpenEJB and now we never get "Out of
Memory"
exceptions requiring us to restart Tomcat - provided we are onlyworking
on JSP's.
Also, we used JDK 1.4.2 with Tomcat which helps get around the memoryleak
issue
that results from compiling JSP's using JDK 1.3.1.
My suggestion...try something else
"Stephen Westbom" <[email protected]> wrote:
I have had the same problem with Weblogic 7.0 sp4 using 1.3.1_08.
I
found that
turning off deadspot helps (otherwise known as hotspot).
It makes it unusable after a while in a production environment.
Our
firm is considering
switching to JBoss because it is simpler and more reliable, despiteno
good user
friendly deployment tools.
Weblogic concentrates too much on bells and whistles that sound good
rather than
reliability and usability. I guess existing customers are not asimportant
as
new business.
"Dmitry Amelchenko" <[email protected]> wrote:
Also, I don't know if that helps, but in general we've been
experiencing
some
other problems with the web logic deployment. For instance, aftera
number
of
redeployments, the application throwth OutOfMemoryException (about
10
deployments
MAX).
Internally we've been discussing what's the best way of deployingthe
ear application
into the weblogic -- using java deploy tool, or using hot deployby
just
dropping
the app in a particular bea folder.
Is there a prefered/recommended way of deployment?
If not, what people have found to be the most stable way of
deploying?
>>>>>>
Please help!
P.S. I'm little dissappointed, isn't bea an industry leader? Isn'tit
supposed
to take all these little issues away from the developpers so theycan
concentrate
on solving the business problems? It has not been the case for usso
far. BTW
-- JBOSS just works.
"Dmitry" <[email protected]> wrote:
I'm having this strange problem, my application is deployed with
java.Deployer
tool, works fine, then when ever i reboot the weblogic server,
the
application
is not accessible untill i explicitly redeploy it again.
Please help!

NWDI - How to control EAR deployment order

We are developing a custom application in NWDI. We have created a software component for the this and have created all required DCs under this software component.
All the J2EE DCs are deployed through separate EAR DCs and there are references from one to another ear DC where ever required.
Deployment of a EAR DC fails if the dependent EARs are missing at that time as it looks for some classes at the time of deployment. We could resolve this in development env as we have the control over individual EAR deployment.
But for deployment in QA through NWDI, where the whole software component is deployed as one SCA file, deployment is failing due to wrong order of deployment for the EARs. We are not able to figure out how to control the order of EAR deployments contained in a single SCA.
Please let me know for any further info.
Points will be awarded for helpful answers
Regards, Chandra

Hi Chandra,
It defines runtime-reference. And should automatically add references to application-j2ee-engine.xml
But as far as I remember it is done only in NW7.1
Regards,
Andrei.

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

Deployment operation was not completed within timeout

I use Eclipse 3.3 and WLS 10. If i deploy my EAR to the server after 5min i get the following error in plugin "com.bea.workshop.wls.core":
"Deployment operation was not completed within timeout. State Type : running; Command Type : distribute; Action Type : execute; Completed : false; Failed : false; Message : null; Exception : null"
The timeout ist just in the eclipse-plugin , the deplyoment on the server runs to end but the application ist not activated.
Anyone has solved this problem?
Thanks
Diego

The timeout happens every time when i deploy the ear the first time to the server and the stubs are generated and compiled.
it is funny that last info before timeout-error 'publishing finished' comes while wls is in full action compiling the myprojEjbEntity-module.
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.091
!MESSAGE Module not added:[myprojEar-TEST]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.091
!MESSAGE Module not added:[myprojEar-TEST,myproj]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.091
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbAllgemein]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbEntity]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbBackoffice]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbCes]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbDisposition]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbFormulare]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbLogistik]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbPerformancetest]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbStammdaten]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
!MESSAGE Module not added:[myprojEar-TEST,myprojEjbRm]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.200
!MESSAGE Getting available modules on Weblogic server.
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.140
!MESSAGE Deployment manager created @13032027
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.218
!MESSAGE Releasing deployment manager @13032027
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.218
!MESSAGE Total deleted modules: 0
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.281
!MESSAGE Publishing beginning.
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.328
!MESSAGE Module Status:
-myprojEar-TEST (add) (deploy)
--myproj (add)
---myprojEjbAllgemein (add)
----myprojEjbEntity (add)
-----myprojEjbBackoffice (add)
------myprojEjbCes (add)
-------myprojEjbDisposition (add)
--------myprojEjbFormulare (add)
---------myprojEjbLogistik (add)
----------myprojEjbPerformancetest (add)
-----------myprojEjbStammdaten (add)
------------myprojEjbRm (add)
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.282
!MESSAGE Deployment manager created @10400586
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.314
!MESSAGE ***dm.getAvailableModules (initModuleNameCache)
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.345
!MESSAGE Deploying library module wls-commonslogging-bridge#[email protected]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.345
!MESSAGE ***dm.distribute (deployLibrary) wls-commonslogging-bridge#[email protected]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.128
!MESSAGE Waiting on ProgressObject:@4026405
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.738
!MESSAGE ProgressObject completed :@4026405
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.738
!MESSAGE ***dm.start (deployLibrary) wls-commonslogging-bridge#[email protected]
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.770
!MESSAGE Waiting on ProgressObject:@14021095
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.895
!MESSAGE ProgressObject completed :@14021095
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.895
!MESSAGE Library module wls-commonslogging-bridge#[email protected] was deployed sucessfully.
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.895
!MESSAGE ***dm.distribute (deploy) myprojEar-TEST
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.989
!MESSAGE Waiting on ProgressObject:@26461882
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.003
!MESSAGE ProgressObject completed :@26461882
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.035
!MESSAGE ***dm.getAvailableModules (initModuleNameCache)
!ENTRY com.bea.workshop.wls.core 2 3000 2007-08-14 07:41:21.097
!MESSAGE Module myprojEar-TEST was not found on the server. Unable to perform undeploy.
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.113
!MESSAGE Releasing deployment manager @10400586
!ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.160
!MESSAGE Publishing finished.
!ENTRY com.bea.workshop.wls.core 4 0 2007-08-14 07:41:21.238
!MESSAGE Module named 'myprojEar-TEST' failed to deploy.
!SUBENTRY 1 com.bea.workshop.wls.core 4 4000 2007-08-14 07:41:21.238
!MESSAGE Deployment operation was not completed within timeout. State Type : running; Command Type : distribute; Action Type : execute; Completed : false; Failed : false; Message : null; Exception : null

How do I change an IP address of SQL Server which is locally hosted and is not on cluster?

Hi All,
How do I change an IP address of SQL Server which is locally hosted and is not on cluster?
I am asking about IP for SQL Server, is there a way we can assign a different IP to SQL Server other than the server's(host) IP address? like the same what we do in a clustered env.
aa

Full explanation can seen here:
SQL Server: Configure Listening IP, Port, and Named pipe
http://ariely.info/Blog/tabid/83/EntryId/151/SQL-Server-Configure-Listening-IP-Port-and-Named-pipe.aspx
[Personal Site] [Blog] [Facebook]

Deployment Manager is not Working after upgrading OIM 9.1.0.1 to 9.1.0.2

Hi,
I have installed the following components successfully
Oracle Database : 10.2.0.1
Weblogic Server : 10.3.0
OIM : 9.1.0.1
Platform : Microsoft Windows XP
Then, I have download the patch : p8484010_9102_Generic and followed necessary documents to upgrade OIM 9.1.0.1 to 9.1.0.2.
Patch installation was successful. While restarting the server we are encountering servlet exception, Nexaweb deployment ends up in failure.
Error Details
========
weblogic.application.ModuleException: [HTTP:101216]Servlet: "ClientClassServlet" failed to preload on startup in Web application: "Nexaweb".
javax.servlet.ServletException: com.nexaweb.server.clientmgmt.ClientClassLoader
Further we faced a number of class not found exception in com.thortech.xlscheduler.schedule.task
Kindly suggest me if we are using correct versions of all OIM components mentioned above for upgrading OIM 9.1.0.1 to 9.1.0.2 and also let us know if we need to upgrade any other components before applying the patch.
Help required at the earliest

Go to Weblogic admin console and see whether both applications are deployed successfully or not.
Also see the patch_weblogic.log whether it has some exception while deploying Nexaweb.
Certification for OIM:
http://www.oracle.com/technology/software/products/ias/files/idm_certification_101401.html

Could not find cluster

I have one type of file that fails out in a weird way when attempting to transcode to h.264. Sometimes. Occasionally we get this error in Search All Jobs...
ERROR: E_REQ_ERROR Encountered error using Compressor: Could not find cluster "Render Cluster".
I know it's not very imaginative, but our cluster is named Render Cluster.
Node 1 is the controller and a compressor.
Nodes 2, 3 and 4 are compressors only.
All files transcode well. Usual source codec are DV25 (NTSC and PAL), DVCProHD, ProRes 422 LT, h.264, MPEG-4 and MPEG-2. The one file that sometimes gives us that weird error about not being able to find the Compressor cluster is
AVC Coding, 640 x 480, Millions
AAC, Stereo (L R), 44.100 kHz
We have the AVC component on the FCSvr server, as well as each of the Compressor nodes. Restarting the nodes hasn't helped. Restarting the FCSvr server hasn't helped. Some files are just cursed.
The files that transcode successfully have the exact same properties as the ones that won't transcode. The files that won't find their way to the compressor cluster consistently fail out. It's not a "sometime this file works and sometimes it doesn't" situation.
The strangest part of this problem is that other files before and after will successfully transcode.
Thank you.
-Cory

Hello Akhtar,
Have you tryed to delete the heador row from your file?
I received the same error when loading a csv file, but when I delete the heador row it worked.
Best Regards,
Juliana Genova

A Connection to the deployment share could not be made....

Hi,
I know this question has been posted a fair number of times on the forums but so far none of the responses have fixed my issue.
I am having trouble connecting to the deployment share receiving the error message below.
"A connection to the deployment share could not be made. The deployment will not proceed.
The following networking device did not have a driver installed PCI\VEN_10EC&DEV_8168&SUBSYS_00041179&REV_10"
I have downloaded the correct network drivers and even installed Windows 7 manually and added
the drivers to check they are correct drivers.
I have added them to the OOB drivers in the deployment share and then updated and also regenerated
the deployment share. Then i have updated the .wim file in the boot images folder but yet i still cannot get past this stage.
Does anyone have any further ideas that i could try?
Thanks,
Adam

Hi,
I can exit to cmd and attempt ipconfig/ping etc. but get confirmation that there is no IP.
The imaging process is working for older versions of laptops and Netbooks but not for the newer models. They are all Toshiba models.
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
_SMSTSORGNAME=(*****)
OSInstall=YES
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=YES
SkipComputerName=NO
SkipComputerBackup=YES
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipDomainMembership=YES
JoinDomain=(*****)
DomainAdmin=Build
DomainAdminDomain=(*****)
DomainAdminPassword=(*****)
SkipFinalSummary=YES
SkipLocaleSelection=YES
KeyboardLocale=en-GB
UserLocale=en-GB
UILanguage=en-GB
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=YES
SkipTaskSequence=NO
SkipTimeZone=YES
TimeZoneName=GMT Standard Time
skipUserData=Yes
FinishAction=LOGOFF
I have removed some of the information of the organisation with (*****)
Thanks,
Adam

EAR deploy in a not homogeneus Cluster

Similar Messages

Maybe you are looking for