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.
Similar Messages
-
WLS 8.1 issue with .ear deployment ....
I think the weblogic8.1 seems to have some NEW bug now. We have a .ear file that
works just PERFECT in WLS6.1. But now when we try to DEPLOY this .ear file our
WLS8.1 server(via the new look and feel of WLS8.1' console)....we are getting
the Exception like ...."pl read inline below":
...All i know is that WLS 8.1 has introduced something like : "single J2EEC -
EAR compiler, replacing the separate compilers in previous releases" ........is
it may be because of this ????
If somebody has any idea ....please let me know asap ...and just above the EXCEPTION
we are also getting something like ...."Deployment descriptor "/WEB-INF/ups-html.tld"
is malformed" ....what is going wrong now ?
Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
Read inline for the Exception:
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
DTD: Element type "info" must be declared. (line 334, column 9).>
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
(line 335, column 8).>
MessageResourcesFactory.createFactory
java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
<Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
java.lang.NullPointerException
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
>
<Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "service"
failed to preload on startup in Web application: "ABL".
javax.servlet.UnavailableException: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1043)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
thx, sangitaRob,
These are the 3 files that you need:
1) wlstart_cap (this is the start up script that we use to start the Managed server
while on WLS6.1) ....please read inline:
-----------Inline 1-----------------
#!/bin/ksh
# BEA WebLogic Start Script - Version 1.1
# Add support for STARTMODE MKG 03/08/2002
# Set user specified variables
JAVA_HOME=/usr/j2sdk1_3_1_01
JAVA_OPTIONS="-D$1 -ms128m -mx128m -noclassgc"
BEA_HOME=/opt/bea
WL_HOME=$BEA_HOME/wlserver6.1
WL_SCRIPT=$WL_HOME/config/Subsidiary
export WL_SCRIPT
EXPORT_LIB=$WL_HOME/lib
#### Set locale to US English MKG 2003/01/16
LC_MESSAGES=C
LC_TIME=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_MONETARY=en_US.ISO8859-1
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
export LC_MESSAGES LC_TIME LC_NUMERIC LC_MONETARY LC_COLLATE LC_CTYPE
#### End locale settings
#### UPSCAP-clientmanger App settings --- Begin
# workaround for strange bug in code that requires an x-server
# to be present when graph code is initialized.
# Note that this is my sun workstation. MKG 05/16/2002
DISPLAY=bluewolf.telecom.ups.com:0.0
export DISPLAY
#### UPSCAP-clientmanger App settings --- End
#### EUP App settings --- Begin
VANAPI_HOME=/opt/vanapi
VANPATH=$VANPATH:$VANAPI_HOME/vanapi/share
LD_LIBRARY_PATH=$VANAPI_HOME/vanapi:$VANAPI_HOME/vanapi/vanjavi:$LD_LIBRARY_PATH
PATH=$VANAPI_HOME/perl_dir/bin:$PATH
EUP_CLASSPATH=$WL_HOME/config/Subsidiary/serverclasses
export VANPATH LD_LIBRARY_PATH VANAPI_HOME PATH EUP_CLASSPATH
#### EUP App settings --- End
CLASSPATH=$WL_HOME/lib/CR061106_61sp2.jar:$WL_HOME/lib/CR072612_61sp2.jar:$WL_HOME/lib/CR071109_610sp2.jar:$WL_
HOME/lib/CR058352_61sp2.jar:$WL_HOME/lib/weblogic.jar:$BEA_HOME:$EUP_CLASSPATH
if [ -n "$LD_LIBRARY_PATH" ]; then
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$WL_HOME/lib/solaris:
else
LD_LIBRARY_PATH=$WL_HOME/lib/solaris:
fi
export LD_LIBRARY_PATH
ADMIN_URL=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerURL|awk '{print $2}')
ADMIN_SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerName|awk '{print
$2}')
DOMAIN_NAME=$(cat $WL_SCRIPT/config.weblogic|grep Domain|awk '{print $2}')
PATH=$WL_HOME/bin:$JAVA_HOME/bin:$PATH
export PATH
WLS_PW=$(cat $WL_SCRIPT/bea.check | awk '{print $1}')
export $WLS_PW
#################################export LOG_HOME=/export/bea/netsite/ext-admin/logs/bea
export LOG_HOME=/export/bea/logs
# echo all of the variable settings
#echo
#echo "BEA_HOME=$BEA_HOME"
#echo "WL_HOME=$WL_HOME"
echo "EXPORT_HOME=$EXPORT_HOME"
echo "CLASSPATH=$CLASSPATH"
#echo "LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
#echo "PATH=$PATH"
#echo "JAVA_OPTIONS=$JAVA_OPTIONS"
#echo "DOMAIN_NAME=$DOMAIN_NAME"
#echo "ADMIN_URL=$ADMIN_URL"
#echo "ADMIN_SERVER_NAME=$ADMIN_SERVER_NAME"
#java -fullversion
#echo
#echo
# Grab some file descriptors.
maxfiles='ulimit -H -n'
if [ ! $? -a "$maxfiles" != 1024 ]; then
if [ "$maxfiles" = "unlimited" ]; then
maxfiles=1025
fi
if [ "$maxfiles" -lt 1024 ]; then
ulimit -n $maxfiles
else
ulimit -n 1024
fi
fi
# Set Production Mode. When set to true, the server starts up
# in production mode. When set to false, the server starts up
# in development mode. The default is false.
STARTMODE=true
if [[ -n $1 ]]; then
if [[ $1 = "admin" ]]; then
echo "Starting admin server...."
###### echo "See /export/netsite/ext-admin/logs/bea/admin.start for more info"
# Change to the WebLogic directory
cd $WL_HOME
echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Name=$ADM
IN_SERVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dweblogic.Production
ModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
-Dweblogic.ma
nagement.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Name=$ADMIN_SE
RVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dweblogic.ProductionModeE
nabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
-Dweblogic.managem
ent.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
$LOG_HOME/admin.start 2>&1&
echo
shift
# Change back to the domain directory
cd config/$DOMAIN_NAME
echo $! > admin.pid
else
while [[ $# -gt 0 ]];do
SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep $1|awk '{print $2}')
if [[ $SERVER_NAME = "" ]]; then
echo "ERROR: unable to locate an entry for "$1" in config file"
shift
else
echo "Starting server: "$SERVER_NAME
######### echo "See /export/netsite/ext-admin/logs/bea/$SERVER_NAME.start
for more info"
# Change to the WebLogic directory
cd $WL_HOME
echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Nam
e=$SERVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dw
eblogic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW
weblogic.Server
nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Name=$SE
RVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dweblog
ic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW weblogic.Server
$LOG_HOME/$SERVER_NAME.start 2>&1 &
shift
# Change back to the domain directory
cd config/$DOMAIN_NAME
echo $! > $SERVER_NAME".pid"
fi
done
fi
else
echo ""
echo ""
echo "FATAL ERROR: You must specify the server to start. Either 'admin' or
the server token"
echo ""
fi
-----------Inline 1 ends-----------------
2) startManagedWebLogic.sh(this is the Managed server start up script at wls8.1)
---------Inline 2 starts---------
#!/bin/sh
# This script is used to start a managed WebLogic Server for the domain in the
# current working directory. This script reads in the SERVER_NAME and
# ADMIN_URL as positional parameters, sets the SERVER_NAME variable, then
# starts the server.
# Other variables that startWLS takes are:
# WLS_USER - cleartext user for server startup
# WLS_PW - cleartext password for server startup
# PRODUCTION_MODE - Set to true for production mode servers, false for
# development mode
# JAVA_OPTIONS - Java command-line options for running the server. (These
# will be tagged on to the end of the JAVA_VM and MEM_ARGS)
# JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
# -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory arguments
# passed to java
# For additional information, refer to the WebLogic Server Administration Guide
# (http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html).
#Set the New Java Path
PATH=/opt/bea/jdk141_02/bin:$PATH
# set up WL_HOME, the root directory of your WebLogic installation
WL_HOME="/opt/bea/weblogic81"
# set up common environment
# Set Production Mode. When this is set to true, the server starts up in
# production mode. When set to false, the server starts up in development
# mode. If it is not set, it will default to false.
PRODUCTION_MODE="true"
# Set JAVA_VENDOR to java virtual machine you want to run on server side.
JAVA_VENDOR="Sun"
# Set JAVA_HOME to java virtual machine you want to run on server side.
JAVA_HOME="/opt/bea/jdk141_02"
set USE_CURRENT_JAVA_HOME "$@"
. "${WL_HOME}/common/bin/commEnv.sh"
shift 1
# Set SERVER_NAME to the name of the server you wish to start up.
ADMIN_URL=http://153.2.255.51:8001
SERVER_NAME=
# Set WLS_USER equal to your system username and WLS_PW equal
# to your system password for no username and password prompt
# during server startup. Both are required to bypass the startup
# prompt.
WLS_USER=
WLS_PW=
# Set JAVA_VM to java virtual machine you want to run on server side.
# JAVA_VM="-server"
# Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
# are more than one, include quotes around them. For instance:
# JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
usage()
echo "Need to set SERVER_NAME and ADMIN_URL environment variables or specify"
echo "them in command line:"
echo 'Usage: ./startManagedWebLogic.sh [SERVER_NAME] [ADMIN_URL]'
echo "for example:"
echo './startManagedWebLogic.sh managedserver1 http://localhost:7001'
exit 1
# Check for variables SERVER_NAME and ADMIN_URL
# SERVER_NAME and ADMIN_URL must by specified before starting a managed server,
# detailed information can be found at http://e-docs.bea.com/wls/docs81/adminguide/startstop.html.
if [ ${#} = 0 ]; then
if [ "x${SERVER_NAME}" = "x" -o "x${ADMIN_URL}" = "x" ]; then
usage
fi
elif [ ${#} = 1 ]; then
SERVER_NAME=${1}
if [ "x${ADMIN_URL}" = "x" ]; then
usage
fi
elif [ ${#} = 2 ]; then
SERVER_NAME=${1}
ADMIN_URL=${2}
else
usage
fi
# Start WebLogic server
# Reset number of open file descriptors in the current process
# This function is defined in commEnv.sh
resetFd
CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
export CLASSPATH
# Start WebLogic server
echo CLASSPATH="${CLASSPATH}"
echo
echo PATH="${PATH}"
echo
echo "***************************************************"
echo "* To start WebLogic Server, use a username and *"
echo "* password assigned to an admin-level user. For *"
echo "* server administration, use the WebLogic Server *"
echo "* console at http://<hostname>:<port>/console *"
echo "***************************************************"
"$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} \
-Dweblogic.Name=${SERVER_NAME} \
-Dweblogic.management.username=${WLS_USER} \
-Dweblogic.management.password=${WLS_PW} \
-Dweblogic.management.server=${ADMIN_URL} \
-Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy" \
weblogic.Server
-------Inline 2 ends----------
3) startWebLogic.sh(this is the Admin start up script at wls8.1)
---------Inline 3 starts-------
#!/bin/sh
# This script is used to start WebLogic Server for the domain in the current
# working directory. This script simply sets the SERVER_NAME variable
# and calls the startWLS.sh script under ${WL_HOME}/server/bin.
# To create your own start script for your domain, all you need to set is
# SERVER_NAME, then starts server.
# Other variables that startWLS takes are:
# WLS_USER - cleartext user for server startup
# WLS_PW - cleartext password for server startup
# PRODUCTION_MODE - Set to true for production mode servers, false for
# development mode
# JAVA_OPTIONS - Java command-line options for running the server. (These
# will be tagged on to the end of the JAVA_VM and MEM_ARGS)
# JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
# -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory arguments
# passed to java
# For additional information, refer to the WebLogic Server Administration
# Console Online Help(http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html)
#Set the New Java Path
PATH=/opt/bea/jdk141_02/bin:$PATH
# set up WL_HOME, the root directory of your WebLogic installation
WL_HOME="/opt/bea/weblogic81"
# set up common environment
# Set Production Mode. When this is set to true, the server starts up in
# production mode. When set to false, the server starts up in development
# mode. If it is not set, it will default to false.
PRODUCTION_MODE="true"
# Set JAVA_VENDOR to java virtual machine you want to run on server side.
JAVA_VENDOR="Sun"
# Set JAVA_HOME to java virtual machine you want to run on server side.
JAVA_HOME="/opt/bea/jdk141_02"
set USE_CURRENT_JAVA_HOME "$@"
. "${WL_HOME}/common/bin/commEnv.sh"
shift 1
# Set SERVER_NAME to the name of the server you wish to start up.
SERVER_NAME=Admin
# Set WLS_USER equal to your system username and WLS_PW equal
# to your system password for no username and password prompt
# during server startup. Both are required to bypass the startup
# prompt.
WLS_USER=
WLS_PW=
# Set JAVA_VM to java virtual machine you want to run on server side.
# JAVA_VM="-server"
# Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
# are more than one, include quotes around them. For instance:
# JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
# Reset number of open file descriptors in the current process
# This function is defined in commEnv.sh
resetFd
# Start WebLogic server
CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
export CLASSPATH
"$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
-Dweblogic.management.username=${WLS_USER} -Dweblogic.management.password=${WLS_PW}
-Dweblogic.ProductionModeEnabled=${PRODUCTION_MODE} -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy"
weblogic.Server
--------Inline 3 ends---------
I think we are getting closer to a solution !
thanks rob,
Rob Woollen <[email protected]> wrote:
Yes, your $CLASSPATH could be the issue. Can you show me the $CLASSPATH
used in each version of the server?
-- Rob
sangita wrote:
Thanks Rob, I understood changing the DOCTYPE ...and i will give ita try.
And iam assuming you might have read my previous response in this chain,Iam using
WLS6.1 & WLS8.1 BOTH on the same hardware unix server....iam just wonderingif
there is any CLASSPATH issue that might have been causing this NoClassDefFoundError......?
just wanted to let you know that iam running WLS6.1 + WLS8.1 on thesame BOX.
I will try other options that you have suggested ....thanks again !
Rob Woollen <[email protected]> wrote:
sangita wrote:
Rob,
Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
definition to the Taglib 1.1 DTD or change the tld file to conformto
the 1.2 DTD. how do i do either of the 2 options ?To change your taglib to be the 1.1 DTD you just need to change the
DOCTYPE header to be
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
"http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
Otherwise, you'll need to change the tld file to be JSP 1.2 compliant.
If you post your tld file here, then I can help.
Iam just guessing here, is it may be due to this DTD/.tld issue thatiam not been
able to DEPLOY the .ear file(now that wls8.1 checks the validity beforedeloying
the app)....are the 2 errors that iam getting, in any ways inter-related?
I'm not sure they're related. It is possible.
i.e is it possible that due to DTD/.tld ....am i getting this NoClassDefFoundError
JUST CURIOUS ???
WELL THANKS FOR YOUR TIME ON THIS ...REALLY APPRECIATE IT !
No problem.
-- Rob
Regards, sangita
Rob Woollen <[email protected]> wrote:
sangita wrote:
1) This is how my .tld looks like:
<?xml version="1.0" encoding="UTF-8" ?>^M
<!DOCTYPE taglib^M
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"^M
"http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd">^M
Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
definition to the Taglib 1.1 DTD or change the tld file to conformto
the 1.2 DTD. Unfortunately WLS 6.1 didn't validate the tld file
against
the DTD, but it should have, and you'll need to correct your application.
<taglib>^M
<tlib-version>1.0</tlib-version>^M
<jsp-version>1.2</jsp-version>^M
<short-name>html</short-name>^M
2) the MANIFEST.MF file is located within the ABL.war.
3) I will try placing the struts-util.jar in the WEB-INF/lib directoryof the
ABL.war file. And I will let you if it works or not ?Right. My guess is this is a bug in WLS 8.1. I can see no reasonwhy
the manifest class-path isn't working for you. That's why I askedif
you could send the EAR file so I could investigate, but I understand
that's not always possible.
I suspect the WEB-INF/lib will work, but it's just a workaround.
I'm
not sure if you're using 8.1 or 8.1SP1, but if you're not using SP1,
then you might consider trying that. (java weblogic.version willtell
you.)
Otherwise, I think you should open a case with [email protected]
-- Rob
thx, sangita
Rob Woollen <[email protected]> wrote:
sangita wrote:
Rob, here is the information that you need: Please read inline:
---------------------------iam doing cut&paste
<attribute>^M
<name>styleClass</name>^M
<required>false</required>^M
</attribute>^M
(this is the 334 line)<info>applys the style of
the
number text
if it passes the conditional given</info>^M
</tag>^M
</taglib>^MWell, it looks like you have a JSP 1.1 tld, but it's being validated
against the JSP 1.2 tld. I suspect that you have not declareda
DOCTYPE
and 6.1 defaulted to the older JSP spec.
Anyway, check the first line of your tld file. It should look
something
like this:
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
"http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
I have an ABL.ear file and this is what it looks like:
ABL.ear
META-INF/
META-INF/MANIFEST.MF
ABL.jar
ABL.war
lib/
lib/struts-util.jar
META-INF/application.xml
and in the ABL.war ...there is a META-INF/MANIFEST.MF file ...and
when
i open
this file ...this is what it contains:Just to double-check, the MANIFEST.MF file is located within the
ABL.war, right?
Manifest-Version: 1.0
Created-By: Ant 1.4.1
Class-Path: lib/struts-util.jar
there is nothing in the CLASSPATH that contains this application'sspecific .jar/.war
...or any classes specific to this application ........BOTH IN
WLS6.1(and
now
in WLS8.1)Hmm, I'm not sure yet what the problem is here. Does it work ifyou
place the struts-util.jar in the WEB-INF/lib directory of the ABL.war
file? (I suspect it will.)
This might be a WLS bug. If you can post your ear file here (oremail
it to me rwoollen at bea dot com), then I can dig into it more.
-- Rob
thx, sangita
Rob Woollen <[email protected]> wrote:
It looks like there are 2 errors.
The first error /WEB-INF/ups-html.tld is most likely the result
of
WLS
8.1 doing more validation on your tld file. If you'd show us
either
the
entire ups-html.tld or just the part around line 334, then wecan
help.
As for the NoClassDefFoundError, you'll have to provide some
more
details about your ear file and environment. Do you have anythingin
the $CLASSPATH on either the 6.1 or 8.1 environments?
-- Rob
Sangita wrote:
I think the weblogic8.1 seems to have some NEW bug now. We have
a
.ear
file that
works just PERFECT in WLS6.1. But now when we try to DEPLOY
this
.ear
file our
WLS8.1 server(via the new look and feel of WLS8.1' console)....we
are
getting
the Exception like ...."pl read inline below":
...All i know is that WLS 8.1 has introduced something like
"single
J2EEC -
EAR compiler, replacing the separate compilers in previous releases"........is
it may be because of this ????
If somebody has any idea ....please let me know asap ...and
just
above
the EXCEPTION
we are also getting something like ...."Deployment descriptor
"/WEB-INF/ups-html.tld"
is malformed" ....what is going wrong now ?
Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
Read inline for the Exception:
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248>
<[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
against
the
DTD: Element type "info" must be declared. (line 334, column
9).>
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248><[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
against
the
DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
(line 335, column 8).>
MessageResourcesFactory.createFactory
java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
<Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
java.lang.NullPointerException
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext. -
Error during EAR deployment with EJB and web service
I created a simple stateless EJB with one method called echo that returns a string. I created a web service using the wizard, did a build and deployed. The deployment did not report an error, but the logs in the visual administrator showed the follwoing message, and the web service did NOT deploy.
Am I missing something related to EJB and web service security?
PLEASE HELP ME.
>>> Warning: delete security configuration [apps/com.areva/ear/ejb/security/com.areva~ejb.jar]
[EXCEPTION]
java.lang.Exception
at com.sap.engine.services.security.server.PolicyConfigurations.unregisterPolicyConfiguration(PolicyConfigurations.java:153)
at com.sap.engine.services.ejb.EJBAdmin.remove(EJBAdmin.java:2538)
at com.sap.engine.services.deploy.server.application.RemoveTransaction.removeApplication(RemoveTransaction.java:294)
at com.sap.engine.services.deploy.server.application.RemoveTransaction.prepare(RemoveTransaction.java:178)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
at com.sap.engine.services.deploy.server.DeployServiceImpl.remove(DeployServiceImpl.java:820)
at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.remove(DeployRuntimeControlImpl.java:271)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)I have the same message. I am running sp11.
Does anyone have an answer for this?????
>>> Warning: delete security configuration [apps/avalero.com/rtfa-ear/contextRoot]
[EXCEPTION]
java.lang.Exception
at com.sap.engine.services.security.server.PolicyConfigurations.unregisterPolicyConfiguration(PolicyConfigurations.java:153)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.removeSecurityResources(WebContainerHelper.java:905)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.remove(WebContainerHelper.java:447)
at com.sap.engine.services.servlets_jsp.server.container.RemoveAction.remove(RemoveAction.java:50)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.remove(WebContainer.java:150)
at com.sap.engine.services.deploy.server.application.RemoveTransaction.removeApplication(RemoveTransaction.java:294)
at com.sap.engine.services.deploy.server.application.RemoveTransaction.prepare(RemoveTransaction.java:178)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
at com.sap.engine.services.deploy.server.DeployServiceImpl.remove(DeployServiceImpl.java:821)
at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.remove(DeployRuntimeControlImpl.java:271)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) -
Error during ear file deployment
Hi,
I am getting the error while trying to deploy ear file using SDM.
The error log is
Starting Deployment of MyzipBean
Aborted: development component 'MyzipBean'/'sap.com'/'localhost'/'2008.06.13.17.44.31'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/MyzipBean.. Reason: Incorrect application sap.com/MyzipBean:Bean MyzipBean: can not find method ejbCreate() in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean MyzipBean: can not find method ejbCreate() in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/MyzipBean:Bean MyzipBean: can not find method ejbCreate() in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean MyzipBean: can not find method ejbCreate() in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.
What could be the reason?
Thanks,
JaishankarHi,
1. Restart the upgrade
2. When it shows the error above open callSdmViaSapinst.log and search for the application that can't be deployed
3. If application is STOPPED start it
4. Undeploy the application if it is STARTED
5. Press the "Retry" button in the error message dialog box from the
upgrade
6. If it fails again for another application go to 2.
Please refer SAP NOte 851590. I don't know if it work for u, as i have given this , it seems for Upgrade as you are developing.
Look into this thread also
Unable to deploy a module into XI Server
Regards
Aashish Sinha
Edited by: Aashish Sinha on Jun 13, 2008 3:20 PM
Edited by: Aashish Sinha on Jun 13, 2008 3:28 PM -
Hi,
I have an Fusion application (ADF Security) deployed onto WLS-1, and the same Application onto WLS-2. My requirement is to migrate application policies from one env to another (i.e. from WLS-1 to WLS-2). After deploying the application onto WLS-1, the Administrator logs into FMWControl (EM) and do some modifications in the policies associated (let us say granted or revoked). And now, I want to migrate these changes onto WLS-2 (thru some WLST Scripts or OPSS).
I used WLS Import/Export utility from WLS Console and it only migrates the user credentials (users & groups, i.e. content from Embedded LDAP and not from system-jazn-data.xml).
I found some WLST script that migrates policies from Code Base onto WLS during deployment. But my requirement is from one WLS to another WLS.
Please help me with some idea/pointers.
Application Policy Migration
Thanks
RazaWell in this case I'm think that APPWORKSPACEDIR refers to your existing JDeveloper application directory. You may want to ask the JDev forum:
JDeveloper and ADF
In general, I think the teams are very open to constructive feedback on what specifically needs to be improved with the documentation.
[email protected] is the WLS feedback. For JDev, I would contact some of the bloggers like Shay:
http://blogs.oracle.com/shay/
Good luck. -
EAR Deployment Aborted...
I am creating a servlet client to test a secured web service (Document Authentication Basic (Username/Password)).
When I deploy the EAR,I get error:
Result
=> deployment aborted : file:/C:/DOCUME~1/uname/LOCALS~1/Temp/temp1530011368822716654CapsWS_EAR.ear
Aborted: development component 'CapsWS_EAR'/'sap.com'/'localhost'/'2009.08.21.09.06.42'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/CapsWS_EAR.ear. Reason: Cannot make reference between sap.com/CapsWS_EAR and sap.com/CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
The version of J2EE engine is 7.00 SP17
Anybody have any idea how to resolve this...
Do I need an upgrade for this ?
Thanks
Srinivas
Edited by: srinivas M on Aug 21, 2009 5:55 PMHi Srinivas,
The reason is clear:
Reason: Cannot make reference between sap.com/CapsWS_EAR and sap.com/CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server
You may have created an entry for the same EAR in the application.xml file of your EAR Project. Remove it and redeploy.
Regards,
Alka. -
I have created a servlet client to test a secured web service.
When I deploy the EAR,I get error:
Result
=> deployment aborted : file:/C:/DOCUME~1/uname/LOCALS~1/Temp/temp1530011368822716654CapsWS_EAR.ear
Aborted: development component 'CapsWS_EAR'/'sap.com'/'localhost'/'2009.08.21.09.06.42'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/CapsWS_EAR.ear. Reason: Cannot make reference between CapsWS_EAR and CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server.
Deployment exception : The deployment of at least one item abortedAnybody have any idea how to resolve this...
Thanks
SrinivasBalusC wrote:
seenuFour wrote:
Cycle of references is created, which is not allowed for the current version of the server.This is pretty self-explaining I think. Just do not create a cycle of references, or upgrade/change the server version.
At least this problem is not related to the Servlet API, but to the appserver in question. Try the SAP homepage/forum/mailinglist/whateversupport if you stucks and don't get more help here.I totally agree with you. I am not able to figure out where I am doing "cycle of references". Is this a generic error at all ?
I am a noob. Thanks for your reply! -
Exception during application deployment
Hi all,
I'm trying to deploy a wd application from NWDS (NW2004 sp19) and I get an error:
The application references the following jars - com.sap.security.api, com.sap.security.api.ep5, bc.rf.framework_api and bc.util.public_api. I also defined a Sharing Reference - "PORTAL:sap.com/com.sap.km.application".
Full error stacktrace:
06/10/2008 10:20:25 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[007]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[D:\usr\sap\EPT\JC00\SDM\program\log\sdmcl20081006082023.log]/>
<!PATTERN[sdmcl20081006082023.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1255]/>
<!LOGHEADER[END]/>
Oct 6, 2008 10:20:23 AM Info: -
Starting deployment -
Oct 6, 2008 10:20:23 AM Info: Error handling strategy: OnErrorStop
Oct 6, 2008 10:20:23 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Oct 6, 2008 10:20:23 AM Info: Update strategy: UpdateAllVersions
Oct 6, 2008 10:20:23 AM Info: Starting deployment prerequisites:
Oct 6, 2008 10:20:23 AM Info: Loading selected archives...
Oct 6, 2008 10:20:23 AM Info: Loading archive 'D:\usr\sap\EPT\JC00\SDM\program\temp\temp86DepthVisit.ear'
Oct 6, 2008 10:20:24 AM Info: Selected archives successfully loaded.
Oct 6, 2008 10:20:24 AM Info: Actions per selected component:
Oct 6, 2008 10:20:24 AM Info: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: Ending deployment prerequisites. All items are correct.
Oct 6, 2008 10:20:24 AM Info: Saved current Engine state.
Oct 6, 2008 10:20:24 AM Info: Starting: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: SDA to be deployed: D:\usr\sap\EPT\JC00\SDM\root\origin\local\DepthVisit\LOKAL\0\0.2008.10.06.10.20.19\temp86DepthVisit.ear
Oct 6, 2008 10:20:24 AM Info: Software type of SDA: J2EE
Oct 6, 2008 10:20:24 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Info: Begin of log messages of the target system:
08/10/06 10:20:24 - ***********************************************************
08/10/06 10:20:24 - Start updating EAR file...
08/10/06 10:20:24 - start-up mode is lazy
08/10/06 10:20:24 - EAR file updated successfully for 63ms.
08/10/06 10:20:24 - Start updating...
08/10/06 10:20:24 - EAR file uploaded to server for 79ms.
08/10/06 10:20:24 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployApplicationDuringUpdate(DeployServiceImpl.java:701)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:666)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 12 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.webdynpro.util.Procedures.switchio(Procedures.java:40)
at com.sap.engine.services.webdynpro.ArchiveParser.extractEntry(ArchiveParser.java:127)
at com.sap.engine.services.webdynpro.ArchiveParser.process(ArchiveParser.java:101)
at com.sap.engine.services.webdynpro.PApplication.process(PApplication.java:170)
at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:838)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 18 more
For detailed information see the log file of the Deploy Service.
08/10/06 10:20:24 - ***********************************************************
Oct 6, 2008 10:20:24 AM Info: End of log messages of the target system.
Oct 6, 2008 10:20:24 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Error: Aborted: development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 6, 2008 10:20:24 AM Info: Starting to save the repository
Oct 6, 2008 10:20:25 AM Info: Finished saving the repository
Oct 6, 2008 10:20:25 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Oct 6, 2008 10:20:25 AM Error: -
At least one of the Deployments failed -Hi,
Building the ear file is not the problem.
The deployment fails.
Seems that somehow I dont have those jars on the server.....
Aviad
Edit: I've done a search on the server and all the relevant jars are there, none is missing.
Whats next?
Edited by: Aviad Levy on Oct 6, 2008 4:41 PM -
How to do Credential and Policy migration in 10g?
Hi, I installed BPEL manager 10g on my machine and want to run the embed demos/tutorials. I noticed the demos are using JAZN as identity service but my installation on Weblogic Server does not support it. As a result I couldn't use JDeveloper BPEL UI designer (to add a participant type) since I couldn't find JAZN.com realm and underlying users.
I found an article regarding how to migrate Credential and Policy to weblogic server:
http://www.oracle.com/technology/products/jdev/tips/muench/credmig111100/index.html
Simplified ADF 11g Application Credential and Policy Migration to Standalone WebLogic Servers
But it is totally different between 11g and 10g.
How can I do similar job in 10g?The way I did it is,
Created an Execution Mode work repository for the QA purpose and thus only Scenarios & Load Plans were deployed on this QA repo. This had its own Master Repo as well.
For dev the Dev mode work repo is created where all the interfaces, packages, procedures can be developed or modified as and when required.
Thus, the testers have access only to the QA environment.
Otherwise you can assign roles to the users after the installation in the security tab. Give the operator, connect role to the testers. -
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 abortedHi 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 -
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 BaradwajHi,
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 -
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,
JanJan,
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 YouHi.
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 -
Hi..I recently bought an IPAD and I absolutely love it. I have been Skyping w/my family during this deployment for the past two weeks until yesterday. The camera on my side just stopped working. I am able to see my family. Any help.
Try closing the Camera/Skype app:
1. Double-click the Home button to reveal the Task Bar
2. Hold down the Camera/Skype app for a second or two until you see the minus sign
3. Tap the minus sign to close app
4. Tap area above Task Bar to return to Home screen
If the above doesn't solve the problem, do a reset:
Hold the Sleep and Home button down for about 10 seconds until you see the Apple logo. Ignore the red slider -
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, ChandraHi 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.
Maybe you are looking for
-
CS4 Master Collection wont fully uninstall
I have been running CS4 Master Collection on Windows Vista for some time, upgraded to Windows 7, had a few installing issues with putting CS4 MC back on my PC. Decided to start from scratch so uninstalled it, using Add/Remove AND the CS4 Cleanup Scri
-
Application Server : File writes only 255 characters
Hi Friends, I am trying to writes data to application server file . My line size is 1100 charqacters. When I use open dataset for output in text mode encoding default and transfer contents to file. I am only able to write contents upto 255 characters
-
Program details / T-Code for automatic clearing for AP Check Encashment
Hi Friends, Please provide me the details of the std program used or (if t-code is there) for the AUTOMATIC CLEARING for AP Check Enchasment) . I am trying in SDN , but could not find. Thanks in advance. Vengal Rao.
-
Problem making slideshow. "Data rate to high"
Using Encore CS3 on Win XP. Trying make dvd on a short film and some slideshows. Total c 2,5 GB. Building stops telling me: PGC "Lenas" has an error at 00:01:31:08. The data rate is too high for DVD. You must replace the file with one of a lower rate
-
hi, i am calling a alv-screen with FM REUSE_ALV_GRID_DISPLAY as the output-table changes in some situations, is it possible to 'refresh' the alv-out-tab automaticly in ABAP ? reg, Martin