Error 404: No target servlet configured for uri: +websphere 6.0
My server is running properly, but I got Error 404: No target servlet configured for uri: error while launching my project on web sphere 6.0
see my web.xml and strut-config.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
id="WebApp_ID"
version="2.4"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>supportPortalWeb</display-name>
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>validate</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet>
<servlet-name>OrganizationDataServlet</servlet-name>
<servlet-class>com.harcourt.supportportal.web.OrganizationDataServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>OrderProcessingServlet</servlet-name>
<servlet-class>com.harcourt.supportportal.web.ordermgmt.OrderProcessingServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>OrganizationValidationServlet</servlet-name>
<servlet-class>com.harcourt.supportportal.web.OrganizationValidationServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>ProductValidationServlet</servlet-name>
<servlet-class>com.harcourt.supportportal.web.ProductValidationServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>ProductGradeServlet</servlet-name>
<servlet-class>com.harcourt.supportportal.web.ProductGradeServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>action_tmp</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>3</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>3</param-value>
</init-param>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>OrganizationDataServlet</servlet-name>
<url-pattern>/servlet/OrganizationDataServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>OrderProcessingServlet</servlet-name>
<url-pattern>/servlet/OrderProcessingServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>OrganizationValidationServlet</servlet-name>
<url-pattern>/servlet/OrganizationValidationServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ProductValidationServlet</servlet-name>
<url-pattern>/servlet/ProductValidationServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ProductGradeServlet</servlet-name>
<url-pattern>/servlet/ProductGradeServlet</url-pattern>
</servlet-mapping>
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/spring-config/spring-config.xml</param-value>
</context-param>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<jsp-config>
<taglib>
<taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-nested.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-nested.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-template.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-template.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-tiles.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-tiles.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/epc.tld</taglib-uri>
<taglib-location>/WEB-INF/supportportal.tld</taglib-location>
</taglib>
</jsp-config>
<resource-ref>
<res-ref-name>jdbc/SupportPortalDataSource</res-ref-name>
<res-type>java.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
<!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Struts Configuration 1.1//EN" "http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd">
<struts-config>
<!-- Data Sources -->
<data-sources />
<!-- Form Beans -->
<form-beans>
<form-bean name="signOnHandlerForm" type="com.harcourt.supportportal.struts.signon.actionform.SignOnHandlerForm" />
<form-bean name="signOffHandlerForm" type="com.harcourt.supportportal.struts.signon.actionform.SignOffHandlerForm" />
<form-bean name="updatePersonForm" type="com.harcourt.supportportal.struts.sample.actionform.UpdatePersonForm" />
<form-bean name="searchPersonsForm" type="com.harcourt.supportportal.struts.sample.actionform.SearchPersonsForm" />
<form-bean name="updateProductForm" type="com.harcourt.supportportal.struts.product.actionform.UpdateProductForm"/>
<form-bean name="searchProductsForm" type="com.harcourt.supportportal.struts.product.actionform.SearchProductsForm"/>
<form-bean name="searchOrganizationForm" type="com.harcourt.supportportal.struts.mdr.actionform.SearchOrganizationForm"/>
<form-bean name="updateOrganizationForm" type="com.harcourt.supportportal.struts.mdr.actionform.UpdateOrganizationForm"/>
<form-bean name="exportOrganizationForm" type="com.harcourt.supportportal.struts.mdr.actionform.ExportOrganizationForm"/>
<form-bean name="exportProductForm" type="com.harcourt.supportportal.struts.product.actionform.ExportProductForm"/>
</form-beans>
<!-- Global Exceptions -->
<global-exceptions />
<!-- Global Forwards -->
<!-- Action Mappings -->
<action-mappings type="org.apache.struts.config.SecureActionConfig">
<action
path="/start"
type="org.apache.struts.actions.ForwardAction"
parameter="loginRendererDef"/>
<!-- <action -->
<!-- path="/product"-->
<!-- type="org.apache.struts.actions.ForwardAction"-->
<!-- parameter="productInputDef"/>-->
<action path="/product" type="org.springframework.web.struts.DelegatingActionProxy"
name="updateProductForm" parameter="method" scope="request" validate="false">
<forward name="success" path="productInputDef"/>
<forward name="failure" path="productInputDef"/>
</action>
<!-- <action -->
<!-- path="/organization"-->
<!-- type="org.apache.struts.actions.ForwardAction"-->
<!-- parameter="organizationIndexDef"/>-->
<action
path="/report"
type="org.apache.struts.actions.ForwardAction"
parameter="reportIndexDef"/>
<action
path="/user"
type="org.apache.struts.actions.ForwardAction"
parameter="userIndexDef"/>
<action path="/login" type="org.springframework.web.struts.DelegatingActionProxy" name="signOnHandlerForm" scope="request" input="loginRendererDef" validate="true">
<set-property property="secure" value="false"/>
<forward name="success" path="loginLandingDef" />
<forward name="failure" path="loginRendererDef" />
</action>
<!-- sample -->
<action path="/updatePerson" type="org.springframework.web.struts.DelegatingActionProxy" name="updatePersonForm" scope="request" input="productInputDef" validate="true">
<set-property property="secure" value="false"/>
<forward name="success" path="personIndexDef" />
<forward name="failure" path="personInputDef" />
</action>
<action path="/searchPersons"
type="org.springframework.web.struts.DelegatingActionProxy"
name="searchPersonsForm"
scope="request"
parameter="method"
validate="true">
<set-property property="secure" value="false"/>
<forward name="success" path="personIndexDef" />
<forward name="failure" path="loginRendererDef" />
</action>
<!-- end sample -->
<action path="/updateProduct" type="org.springframework.web.struts.DelegatingActionProxy"
name="updateProductForm" parameter="method" scope="request" input="productInputDef" validate="true">
<set-property property="secure" value="false"/>
<forward name="success" path="loginLandingDef" />
<forward name="failure" path="/product.do?method=createOrUpdateProduct" />
</action>
<action path="/deleteProduct" type="org.springframework.web.struts.DelegatingActionProxy"
name="updateProductForm" parameter="method" scope="request" validate="false">
<set-property property="secure" value="false"/>
<forward name="success" path="loginLandingDef" />
<forward name="failure" path="/product.do?method=createOrUpdateProduct" />
</action>
<action path="/searchProducts"
type="org.springframework.web.struts.DelegatingActionProxy"
name="searchProductsForm"
scope="request"
parameter="method"
validate="true">
<set-property property="secure" value="false"/>
<forward name="success" path="productSearchDef" />
<forward name="failure" path="loginLandingDef"/>
</action>
<action path="/loadProducts" type="org.springframework.web.struts.DelegatingActionProxy"
name="searchProductsForm" parameter="method" scope="request" validate="true">
<forward name="success" path="productIndexDef"/>
<forward name="failure" path="userIndexDef"/>
</action>
<action path="/exportProduct" type="org.springframework.web.struts.DelegatingActionProxy"
name="exportProductForm" parameter="method" scope="request" validate="true">
<forward name="failure" path="loginLandingDef" />
</action>
<!-- Organization Actions -->
<action path="/searchOrganization" type="org.springframework.web.struts.DelegatingActionProxy"
name="searchOrganizationForm" parameter="method" scope="request" validate="true">
<forward name="success" path="orgSearchDef"></forward>
<forward name="failure" path="loginLandingDef"/>
</action>
<action path="/organization" type="org.springframework.web.struts.DelegatingActionProxy"
name="updateOrganizationForm" parameter="method" scope="request" validate="false">
<set-property property="secure" value="false"/>
<forward name="success" path="orgInputDef" />
<forward name="failure" path="loginLandingDef" />
</action>
<action path="/loadOrganizations" type="org.springframework.web.struts.DelegatingActionProxy"
name="searchOrganizationForm" parameter="method" scope="request" validate="true">
<forward name="success" path="orgIndexDef" />
<forward name="failure" path="loginLandingDef" />
</action>
<action path="/updateOrganization" type="org.springframework.web.struts.DelegatingActionProxy"
name="updateOrganizationForm" parameter="method" scope="request" input="orgInputDef" validate="true">
<forward name="success" path="/loadOrganizations.do?method=loadOrganizations"></forward>
<forward name="failure" path="/organization.do?method=createOrUpdateOrganization"/>
</action>
<action path="/exportOrganization" type="org.springframework.web.struts.DelegatingActionProxy"
name="exportOrganizationForm" parameter="method" scope="request" >
<forward name="failure" path="loginLandingDef" />
</action>
</action-mappings>
<!-- Register Support Portal RequestProcessor -->
<controller>
<set-property property="processorClass" value="com.harcourt.supportportal.struts.common.action.SupportPortalRequestProcessor" />
</controller>
<!-- Message Resources -->
<message-resources parameter="com.harcourt.supportportal.resources.ApplicationResources" />
<!-- tiles plugin -->
<plug-in className="com.harcourt.supportportal.tiles.SupportPortalSecureTilesPlugin">
<set-property property="definitions-config" value="/WEB-INF/tiles-def/tiles-defs.xml" />
<set-property property="httpPort" value="80"/>
<set-property property="httpsPort" value="80"/>
<set-property property="enable" value="false"/>
<set-property property="addSession" value="false"/>
</plug-in>
<!-- spring plugin -->
<plug-in className="org.springframework.web.struts.ContextLoaderPlugIn">
<set-property property="contextConfigLocation" value="/WEB-INF/spring-config/spring-config.xml"/>
</plug-in>
</struts-config>
If your EAR has actually started, try this:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/xrun_jvm_sendredirect.html
If you are not on z/OS, the link is actually under server->server infrastructure->Java and process management->environment entries
for setting the property
Similar Messages
-
Error 404: No target servlet configured for uri
hello there..
this error start comming suddenly, i dont know why??
when i try to run html page then IE7 display the following error
Error 404: No target servlet configured for uri: webpage uri
if any one already know this then please post any solution to fix it.
thanksthanks Mr evenafets for ur quick reply
i m sorry not to post the html page i have problem in.
below is mypage.html
and i m accessing it trough uri http://localhost:9080/myproject/mypage.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<link rel="stylesheet" href="theme/Master.css" type="text/css">
<title>mypage</title>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta name="GENERATOR" content="Rational Application Developer">
</head>
<body>
<!--"CONVERTED_APPLET"-->
<!-- HTML CONVERTER -->
<object
classid = "clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
codebase = "http://java.sun.com/update/1.6.0/jinstall-6u20-windows-i586.cab#Version=6,0,0,6"
WIDTH = "300" HEIGHT = "200" >
<PARAM NAME = CODE VALUE = "myclass.class" >
<PARAM NAME = ARCHIVE VALUE = "RegistrationApplet.jar" >
<param name = "type" value = "application/x-java-applet;version=1.6">
<param name = "scriptable" value = "false">
<comment>
<embed
type = "application/x-java-applet;version=1.6" \
CODE = "myclass.class" \
ARCHIVE = "RegistrationApplet.jar" \
WIDTH = "300" \
HEIGHT = "200"
scriptable = false
pluginspage = "http://java.sun.com/products/plugin/index.html#download">
<noembed>
</noembed>
</embed>
</comment>
</object>
<!--
<APPLET CODE = "myclass.class" ARCHIVE = "RegistrationApplet.jar" WIDTH = "300" HEIGHT = "200">
</APPLET>
-->
<!--"END_CONVERTED_APPLET"-->
</body>
</html>and below is web.xml file
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>
UASEProject</display-name>
<context-param>
<param-name>crystal_image_uri</param-name>
<param-value>crystalreportviewers</param-value>
</context-param>
<context-param>
<param-name>crystal_image_use_relative</param-name>
<param-value>webapp</param-value>
</context-param>
<servlet>
<servlet-name>TilesServet</servlet-name>
<servlet-class>
org.apache.struts.tiles.TilesServlet</servlet-class>
<init-param>
<param-name>definitions-config</param-name>
<param-value>/WEB-INF/tiles-defs.xml</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
</web-app> -
Error 404: No target servlet configured for uri exception in RAD6.0
Hello there,
I have recently migrated from WSAD5.1 to RAD6.0. I have created a servlet in my client Web project. I have configured the deployment descriptor correctly to define a url-mapping for the servlet as follows:
<servlet>
<description>
</description>
<display-name>
RulesServiceServlet</display-name>
<servlet-name>RulesServiceServlet</servlet-name>
<servlet-class>
com.kai.rulesservice.RulesServiceServlet
</servlet-class>
<load-on-startup>-1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>RulesServiceServlet</servlet-name>
<url-pattern>/RulesServiceServlet</url-pattern>
</servlet-mapping>
However, whenever, I try to run my servlet:
http://localhost:9080/RS2Web/RulesServiceServlet
I get the error:
Error 404: No target servlet configured for uri
I am not sure what this error means. Could someone please tell what I might be missing or what might be going wrong?
Thanks in advance!If your EAR has actually started, try this:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/xrun_jvm_sendredirect.html
If you are not on z/OS, the link is actually under server->server infrastructure->Java and process management->environment entries
for setting the property -
ERROR: XIAFUSER user is not configured for keystore.....
Hi all,
When I am running the an adpater on XI that uses digital signatures that I have loaded into the TrustedCA's keystore view I get this error in my monitor.
ERROR: XIAFUSER user is not configured for keystore TrustedCA's.
How do I configure a user for a specific keystore?
Kind Regards,
ChrisHi
You can find it from XI config doc here
https://websmp106.sap-ag.de/~sapidb/011000358700001697502004E.PDF
Also refer installation & post installation from here
https://websmp106.sap-ag.de/~sapidb/011000358700009389172004E.PDF
Cheers
Jawahar Govindaraj
PS:Reward pts -
Error: Exception while jar file setup for uri
Our environment is set up as
Adminserver running on one machine.
Managed servers running on another machine.
Communication via node manager.
Machines physically in the same location.
Trying to deploy application using the wldeploy script or the weblogic console.
I get the following error while deploying my application on one of the managed
server
Can anybody throw some light on what could be wrong ?
####<Apr 19, 2004 2:30:11 PM PDT> <Error> <Deployer> <tin.rose.hp.com> <GSOeProc-EMEA_3_0_AM_tin_AM>
<ExecuteThread: '23' for queue: 'default'> <kernel identity> <> <149201> <The
Slave Deployer failed to complete the deployment task with id 16 for the application
GSOeProc-EMEA_3_0_55.>
weblogic.management.ApplicationException: Module creation failed. Task Id = 16
Module Name: email_mdb.jar, Error: Exception while jar file setup for uri : email_mdb.jar
in Module :
TargetException: java.util.zip.ZipException: error in opening zip file
at weblogic.j2ee.J2EEApplicationContainer.addFindersForAllModules(J2EEApplicationContainer.java:660)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:554)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1096)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:764)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)Does your app work if you deploy it to a single server environment?
It's complaining that it can't find the email_mdb.jar file.
-- Rob
Satya wrote:
Our environment is set up as
Adminserver running on one machine.
Managed servers running on another machine.
Communication via node manager.
Machines physically in the same location.
Trying to deploy application using the wldeploy script or the weblogic console.
I get the following error while deploying my application on one of the managed
server
Can anybody throw some light on what could be wrong ?
####<Apr 19, 2004 2:30:11 PM PDT> <Error> <Deployer> <tin.rose.hp.com> <GSOeProc-EMEA_3_0_AM_tin_AM>
<ExecuteThread: '23' for queue: 'default'> <kernel identity> <> <149201> <The
Slave Deployer failed to complete the deployment task with id 16 for the application
GSOeProc-EMEA_3_0_55.>
weblogic.management.ApplicationException: Module creation failed. Task Id = 16
Module Name: email_mdb.jar, Error: Exception while jar file setup for uri : email_mdb.jar
in Module :
TargetException: java.util.zip.ZipException: error in opening zip file
at weblogic.j2ee.J2EEApplicationContainer.addFindersForAllModules(J2EEApplicationContainer.java:660)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:554)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1096)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:764)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210) -
Deployment error when the server is configured for debugging
Hi,
I am using NW 2004s, when I configure one of server nodes to enable debugging (in config tool I check three checkboxes - debuggable, enabled debug mode, restricted load balance) the deployment is failed with the following error:
[006]Deployment aborted
Settings
SDM host : main-jr-ep7t
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/olesyab/LOCALS1/Temp/temp54994ClassActionLoad.ear
Result
=> deployment aborted : file:/C:/DOCUME1/olesyab/LOCALS1/Temp/temp54994ClassActionLoad.ear
Aborted: development component 'ClassActionLoad'/'local'/'LOKAL'/'0.2007.12.10.15.11.59'/'0':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [main-jr-ep7t] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:168)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
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.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
... 38 more
Caused by: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:701)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:689)
at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:424)
... 1 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted
If I uncheck debug options everything is ok and the deployment is finished successfully.
Can anyone help with this problem?
Thanks,
OlesyaHi,
I am using NW 2004s, when I configure one of server nodes to enable debugging (in config tool I check three checkboxes - debuggable, enabled debug mode, restricted load balance) the deployment is failed with the following error:
[006]Deployment aborted
Settings
SDM host : main-jr-ep7t
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/olesyab/LOCALS1/Temp/temp54994ClassActionLoad.ear
Result
=> deployment aborted : file:/C:/DOCUME1/olesyab/LOCALS1/Temp/temp54994ClassActionLoad.ear
Aborted: development component 'ClassActionLoad'/'local'/'LOKAL'/'0.2007.12.10.15.11.59'/'0':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [main-jr-ep7t] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:168)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
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.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
... 38 more
Caused by: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:701)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:689)
at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:424)
... 1 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted
If I uncheck debug options everything is ok and the deployment is finished successfully.
Can anyone help with this problem?
Thanks,
Olesya -
Error: MSS inbox execute process configuration for FPM processes
Hi,
I got struck up with the error 'Specify a valid Person.' when executing work item from manager inbox for FPM (Webdynpro) forms.
I am using Launchpad handler for POWL mss inbox to execute approvals of process.
I created LPD_CUST config for my process, when executed from approving manager inbox I am getting this error.
Anybody please suggest, I will give full points..
Thanks,
Hareesh KThe pernr should be picked from the workitem in the case of approval.
Ensure you do the POWL inbox configuration as has been done for in standard delivery of HR Admin role.
APPL ID ASR_HRADMIN_INBOX
TASK ID TS17900101
for the MANAGER_MSS_INBOX*.
For HR Admin role WI is passed as a parameter in the view IBO_C_WF_APS:
APPL ID ASR_HRADMIN_INBOX
ACTION ID EXECUTETASK
PROP NAME OBJECTVALUE
PROP VALUE WI_ID=${ITEM.EXTERNALID}
Regards. -
Error while setting up the configuration for XI integration builder
Hi experts,
I am trying to configure the XI integration builder.
I have created an entry in table SPROXSET and created an RFC destination of type G.
After that I am trying to execute the SPROXY, I am getting an error "IFR_HTTP_DEST must not be set in table SPROXSET;"
( IFR_HTTP_DEST is the entry in the table SPROXSET)
Please give me solution to this error....This is very urgent.....
Thanks,
Madhuri.I am having the same problem:
detail:
I have set the echange parameters
com.sap.aii.server.contextRoot.repository.services=rep
com.sap.aii.server.httpport.repository=50000
com.sap.aii.server.name.repository=xiserver
TA: SLDAPICUST hostname=xiserver
=>Check/maintain with report SPROX_CHECK_IFR_ADDRESS
returns
im exchange profilealdxi01:50000/rep
=>Check with report SPROX_CHECK_IFR_RESPONSE
givers: Integration Builder data not un
se38 shows a wrong url when debuging
http://xiserver:50000/rep/ifraccess?service=query&type=namespace
any suggesting
sproxy only shows the local entries and not the XI interfaces -
Receiving an Error 404 when downloading build 994254 for LR 5.7.1?
Receiving this error when downloading build 994254? Is there a work around?
If you download 5.7.1 from this link and then check for updates it will ask you to update to 994254. When you click "Download..." it redirects you to Digital photography software | Download free Adobe Photoshop Lightroom CC trial instead of the update. This is the same problem that version 5.7 users are experiencing build 991162 - I got an update notification today regarding "New software for Lightroom is available!".
How do we update to the latest version? -
Financial Reporting - PDF has not been configured for this web server.
When I try a Print Preview of my report, I received this error "PDF has not been configured for this web server".
As far as I know, this error is confusing because when I look on my log files I found this:
--- FRLogging.log ---
[APP: FINANCIALREPORTING#11.1.2.0] The system cannot access the Print Server at this time. Try again later or confirm the print server name.
[APP: FINANCIALREPORTING#11.1.2.0] Cannot connect to server on xxxHFRCE04.cf.gouv.qc.ca
[APP: FINANCIALREPORTING#11.1.2.0] Attempt to get an undefined configuration property
--- FRPrintLogging.log ---
HyperionReportException: Could not connect to the server.Please make sure that the server is running as specified in the logon dialog (including port number if not default).
I read a lot of document but it seem to be au communication issues!!!
Can someone help me with that.I believe the supported version for ghost script is 7.0.6; I had the same problem and after installing the lower version it worked like a charm.
If you cant find the older version let me know, I'll email it to you or place it in my website. -
Error 404 - no link to download?
Can anyone please lead me to a site to download the EVALUATION versions of SAP on LINUX? All attempts to download following the given link on the SDN page is returning error 404!!! Thanks for your help.
Hi,
the pages in SDN seem to be broken. The SDN page only refers to the direct ftp links. They are as follows:
N4S Testdrive (x86_64 only):
ftp://ftp.sap.com/pub/linuxlab/test_drive/N4S/x86_64/N4S_TestDrive_MaxDB.iso_Part_aa
ftp://ftp.sap.com/pub/linuxlab/test_drive/N4S/x86_64/N4S_TestDrive_MaxDB.iso_Part_ab
ftp://ftp.sap.com/pub/linuxlab/test_drive/N4S/x86_64/N4S_TestDrive_MaxDB.iso_Part_ac
ftp://ftp.sap.com/pub/linuxlab/test_drive/N4S/x86_64/N4S_TestDrive_MaxDB.iso_Part_ad
ftp://ftp.sap.com/pub/linuxlab/test_drive/N4S/x86_64/N4S_TestDrive_MaxDB.iso_Part_ae
ftp://ftp.sap.com/pub/linuxlab/test_drive/N4S/x86_64/N4S_TestDrive_MaxDB.iso_Part_af
ftp://ftp.sap.com/pub/linuxlab/test_drive/N4S/x86_64/N4S_TestDrive_MaxDB.iso_Part_ag
NW4 Testdrive (i386 only):
ftp://ftp.sap.com/pub/linuxlab/test_drive/NW4/i386/NW4_TestDrive.iso_Part_aa
ftp://ftp.sap.com/pub/linuxlab/test_drive/NW4/i386/NW4_TestDrive.iso_Part_ab
ftp://ftp.sap.com/pub/linuxlab/test_drive/NW4/i386/NW4_TestDrive.iso_Part_ac
ftp://ftp.sap.com/pub/linuxlab/test_drive/NW4/i386/NW4_TestDrive.iso_Part_ad
ftp://ftp.sap.com/pub/linuxlab/test_drive/NW4/i386/NW4_TestDrive.iso_Part_ae
The m5sums are:
8a2459a8396e7e937fa1301eda5c77e0 N4S_TestDrive_MaxDB.iso_Part_aa
638be1e5d39e389008247b82a54ef784 N4S_TestDrive_MaxDB.iso_Part_ab
0fa22828317a1721ff1fd73be46b0709 N4S_TestDrive_MaxDB.iso_Part_ac
b5f0b83f549009d69cc0f209f14f49a9 N4S_TestDrive_MaxDB.iso_Part_ad
3df0c19f7e65eb18947e0c50bdfaf721 N4S_TestDrive_MaxDB.iso_Part_ae
3cd5fe69b322d40d4790d3809348f4b5 N4S_TestDrive_MaxDB.iso_Part_af
28b348d803c9b68fe82350fb302be751 N4S_TestDrive_MaxDB.iso_Part_ag
f81835728564079f21dacdb99f36f640 NW4_TestDrive.iso_Part_aa
243c3abc65cc41068b2b048330f17dd8 NW4_TestDrive.iso_Part_ab
e86fb33e636e9ff58107adcf87b12140 NW4_TestDrive.iso_Part_ac
9172a8fcc46fd95eefdfc6b4690ea509 NW4_TestDrive.iso_Part_ad
e39bf88ccaee500f8947cbda75c752db NW4_TestDrive.iso_Part_ae
Best Regards,
Hannes
Edited by: Hannes Kuehnemund on Jan 10, 2008 11:29 AM -
While running servlets getting errors 404 or 505 resource not found
Hi all,
I'm novice to J2EE.
I've encountered a problem while accessing the deployed module in weblogic 8.1 server.
I'm sure that the webapplication module is deployed as i saw my module in administration console & also the status said that it is deployed.
when i access my web application by specifying the proper server and port no and context root it is showing
either 505 - resource not found error(http://localhost:7001/Suresh-2/Suresh) or 404 - not found error.( http://localhost:7001/Suresh-2/Suresh)
Now let me elaborate what i've done till now.
My webapplication folder structure is : C:\bea\user_projects\domains\mydomain\applications\Suresh\WEB-INF\classes\Sai\ServExamp.class
My servlet is ServExamp.java
I created a folder called "Suresh". In that folder created another folder called "WEB-INF". In WEB-INF created a folder called "Classes".
Since my servlet is in package "Sai", the .class file reside in \Suresh\WEB-INF\Classes\Sai\ServExamp.class
The source code is :
package Sai;
import javax.servlet.;*
import javax.servlet.http.;*
import java.io.;*
public class ServExamp extends HttpServlet
public void doPost(HttpServletRequest req,HttpServletResponse res)throws IOException
PrintWriter out=res.getWriter();
java.util.Date today=new java.util.Date();
out.println("<html>"+"<body>"+
*"<h1 align=center>HF\'s Chapter1 Servlet </h1>"*
+"<br>"+today+"</body>"+"</html>");
Now i'm almost done creating a web application. Next, I constructed a simple web.xml descriptor that gives a web friendly name for my servlet, and points to the servlet. I constructed web.xml descriptor file in the WEB-INF folder (C:\bea\user_projects\domains\mydomain\applications\Suresh\WEB-INF\).
The web.xml file source is :
*<!DOCTYPE web-app*
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
*"http://java.sun.com/dtd/web-app_2_3.dtd">*
*<web-app>*
*<display-name>Hello World Web Application</display-name>*
*<description>Test Servlet</description>*
*<servlet>*
*<servlet-name>ServExamp</servlet-name>*
*<servlet-class>Sai.ServExamp</servlet-class>*
*</servlet>*
*<servlet-mapping>*
*<servlet-name>ServExamp</servlet-name>*
*<url-pattern>/Suresh</url-pattern>*
*</servlet-mapping>*
*</web-app>*
Now I have told Weblogic that the URI /Suresh corresponds to my servlet "Sai.ServExamp".
My Web Application is ready to be deployed at this point. I logged onto Weblogic's admin console,
*1) clicked on deployments, then navigated to "Web Application Modules" .*
*2) Clicked "Deploy new Web Application Module"*
*3) Navigated to the location of your web application folder (Suresh). There was a radio button next to it indicating that I can select that folder as a valid web application.*
*4) I Clicked that radio button and clicked "Target Module".*
*5) It informed that my web application "Suresh" will be deployed to myServer.It asked a name for my web application deployment. By default it was "Suresh"*
I clicked Deploy.
*6) After deployment, my web application "Suresh" appeared in the "Web Application Modules" tree on the left.*
I Clicked on "Suresh"( my web application) then clicked the testing tab, then clicked the link shown there(http://localhost:7001/Suresh-2).
It was not showing my servlet (showed a 403 error)
Error - 403
This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
I think so it came b'coz I don't have an index.html or index.jsp page.
*7)Instead,I added my servlet on to the URL it provided.*
http://localhost:7001/Suresh-2/Suresh
It is showing these error code: Http: 505 resource not allowed
The page cannot be displayed
The page you are looking for cannot be displayed because the address is incorrect.
Please try the following:
If you typed the page address in the Address bar, check that it is entered correctly.
Open the localhost:7001 home page and then look for links to the information you want.
Click Search to look for information on the Internet.
when i just type : http://localhost:7001/ -> Error 404 not found error
it's showing
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
*10.4.5 404 Not Found*
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
I want to run my web application & any help would be appreciated.
Thanks in advance.
with regards,
S.SayeeNarayanan.
Note: I even deployed my war file, which i got by execution of (jar cv0f webapp.war . ) command from the root directory of my web application i.e. Suresh
Then executed my webapplication it is showing
error-505 resource not allowed.
--------------------------------------------------------------------------------------------nammathamizhan wrote:
Hi all,
I'm novice to J2EE.
You're also a novice to this forum.
First, turn off the bold font.
Second, post your question once and only once to a single forum. You only waited an hour before reposting your question. That's not the way this works. Asking your question multiple times will not increase the likelihood that you''ll get an answer. As a matter of fact, you're guaranteed nothing at all. Give it your best effort and hope for success. This isn't a paid consultancy - we're volunteers.
I've encountered a problem while accessing the deployed module in weblogic 8.1 server.
I'm sure that the webapplication module is deployed as i saw my module in administration console & also the status said that it is deployed.
when i access my web application by specifying the proper server and port no and context root it is showing
either 505 - resource not found error(http://localhost:7001/Suresh-2/Suresh) or 404 - not found error.( http://localhost:7001/Suresh-2/Suresh)
If you're correct, and it's deployed, that would suggest that the URL you gave is incorrect.
>
Now let me elaborate what i've done till now.Good info - almost too much.
% -
Error 404 -- Not Found, when a Servlet is invoked from browser
Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
even the simplest servlet.
I painstakenly went through all the steps that are listed in the WebLogic
Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
have missed a step somewhere.
I have modified the weblogic.properties file as per all the instrustions,
but the server simply won't recognize any servlets, not even the SqlServlet
that came with the server as an example.
It would require more than 1 exchange of posts to resolve it for me, and I
am wondering if one of you is willing to work with me on this until I have
managed to configure the server to make a servlet work on it.
The server does function as a Web server as I can run the index.html
document by entering the URL: http://localhost:7001/index.html
I am pasting the contents of weblogic.properties file below to get the
person who is willing to help me started.
The machine I have is a Pentium III with Windows 2000 Professional on it.
It's a home machine and the WebLogic server is the freely downloadable
version. I am using it to prepare for a potential contract work.
I have managed to modify setEnv.cmd file and have managed to compile the
SqlServlet.java, which is an example servlet. Neither this particular
servlet nor a HelloWorld type of very basic servlet I have written are
recognized by the server.
As you can see from my weblogic.properties file (pasted at the end of this
post), the SqlServlet has been registered. I have also uncommented the lines
to allow for the following type of URL:
http://localhost:7001/servlet/myServlet
Thanks!
Anjum Jaleel
CONTENTS OF MY weblogic.properties file
# THE WEBLOGIC PROPERTIES FILE
# This file, which conforms to the java.util.Properties file
# definition, configures your WebLogic products. You cannot run
# WebLogic Server without setting required configuration properties in this
# file. Required properties are marked and appear first in the file.
# Details on each entry and important information about configuration
# and security are documented on our website. Please go to:
# http://www.weblogic.com/docs51/admindocs/properties.html
# for full instructions on how to edit this file.
# You do not need to include properties in this file unless you want to
# change the default, embedded property. Some properties on the
# AdminProps page are not listed here because the default property
# is being used. You can change the default by adding the property and
# its value to this file.
# You cannot set weblogic.system.home in this file, since the WebLogic
Server
# must know where home is in order to retrieve this file. You can
# change WebLogic home on the command line when you start the
# WebLogic Server.
# CLUSTER USERS: Note that the (shared) per-cluster properties file should
# contain most all of the properties in this file. The only properties
# that potentially belong in a per-server properties file for a server
# running in a cluster are the registration (startup class) of pinned
# RMI objects, and a few tuning properties that may be different for
# servers in the cluster, depending upon hardware and memory. If you use
# a per-server properties file, please REMOVE all properties except those
# that are specifically required in the per-server properties file. You
# can find specific notes on clusters by searching through this file for
# "CLUSTER USERS".
# The way this file is organized:
# Core properties (includes REQUIRED and RECOMMENDED)
# Core system properties
# Core security-related properties
# Core security-related properties for SSL
# Core HTTPD administrative properties
# Optional properties
# Administrator properties
# System properties
# System startup files
# System shutdown files
# Security-related properties for Workspaces
# Jolt for WebLogic properties
# WebLogic Enterprise Connectivity properties
# WebLogic File properties
# WebLogic JMS demo properties
# WebLogic RMI demo properties
# WebLogic EJB demo properties
# WebLogic XML demo properties
# WebLogic ZAC demo properties
# HTTPD administrative properties
# WebLogic JDBC driver properties
# WebLogic JDBC connection pool management
# WebLogic demo connection pool
# WebLogic HTTP Servlet properties
# Proxy servlet registration
# Classpath servlet registration
# File servlet registration
# ServerSideInclude servlet registration
# PageCompileServlet (used by JHTML)
# JSPServlet (used by JSP)
# ServletServlet registration
# Servlet reload properties
# Servlet ACLs
# WebLogic JSP properties
# WebLogic JHTML properties
# WebLogic RMI over IIOP properties
# User-written and demo servlet registrations
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=lovkako1
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
weblogic.httpd.enable=true
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# OPTIONAL PROPERTIES
# These properties affect the behavior of the WebLogic Server.
# You only need to set these properties if you want
# to change the default setting, which is the property shown.
# ADMINISTRATOR PROPERTIES
# Administrator properties are optional information properties,
# particularly useful for clusters.
#weblogic.administrator.location=3355 California Drive, West Hampshire, CA
94104
#weblogic.administrator.name=Joe Administrator
#weblogic.administrator.phone=1 415 555 1234
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
p/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
#weblogic.ejb.deploy=\
# g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# g:/weblogic/myserver/ejb_subclass.jar, \
# g:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
#weblogic.httpd.register.beanManaged=\
# examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=g:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\Problem Resolved!
I found out that I had 'http' instead of 'httpd' in the statement where I
registered my servlet, SqlServlet.
Now, I am having difficulty with hot deployment. The server is returning
error 404.
-
Getnode returned null for uri error for caldav server
Hello,
I am trying to install the Oracle UCS ( SUN 7 update 2 ) server.
https://wikis.oracle.com/display/CommSuite7U2/Communications+Suite+on+a+Single+Host+%28Linux%29#CommunicationsSuiteonaSingleHost%28Linux%29-InstallingtheExample
So far, I have successfully:
Checked the installation requirements
Installed Communications Suite 7 Update 2 Software
Installed and Configured the Directory Server
Prepared the Directory under ( Configuring Communications Suite Components )
Configured Delegated Administrator and Communications CLI
Configured Messaging Server
Configured MYSQL Server
Configured Calendar Server
I have just installed a caldav server. I checked that it was enabled by running:
# asadmin list-components -p <admin-port> --type=web
davserver <web-module>
Command list-components executed successfully.
# asadmin show-component-status -p <admin-port> davserver
Status of davserver is enabled.
Command show-component-status executed successfully.
that was from this page:
https://wikis.oracle.com/display/CommSuite7RR92909/Calendar+Server+7+Troubleshooting
In Firefox, I try to hit the suggested pages under "Testing Calendar accounts". However, this errors out every time for me.
http://domain.com/davserver/dav/h/myDomain.com/myusername/calendar
wheremyDdomain.com is my actual domain that I will not list here
and myUsername is my actual username which I will not list here
( I edited both of these in the logs below )
I checked my log in /var/opt/sun/comms/davserver/logs:
INFO [2012-02-11T11:46:02.729-0500] <...DavServer.<init>> Server Startup succeeded
INFO [2012-02-11T11:46:02.730-0500] <...DavServer.loadBackend> Loading backend defaultbackend with backendid defaultbackend
INFO [2012-02-11T11:46:02.730-0500] <...DavServer.loadBackend> JDBC JNDI Name = jdbc/defaultbackend
INFO [2012-02-11T11:46:09.033-0500] <...DavServer.loadBackend> Loading backend ischedulebackend with backendid ischedulebackend
INFO [2012-02-11T11:46:09.033-0500] <...DavServer.loadBackend> JDBC JNDI Name = jdbc/ischedulebackend
INFO [2012-02-11T11:46:09.427-0500] <...DavServer.loadBackends> iSchedule enabled
INFO [2012-02-11T11:46:09.439-0500] <...DavServer.loadBackends> modified ischedule collection at /ischedule/
INFO [2012-02-11T13:33:18.967-0500] <...URIInfoManagerImpl.getEntryFromSearchFilter> found 0 corresponding to: (uid=caldav)
INFO [2012-02-11T13:33:59.844-0500] <...URIInfoManagerImpl.getEntryFromSearchFilter> found 0 corresponding to: (uid=caldav)
FINE [2012-02-11T13:42:39.157-0500] <...DavServerServlet.service> [REQ] GET /davserver/browse/h/myDomainName/myUserName/calendar 127.0.0.1 myDomainName
FINE [2012-02-11T13:42:39.808-0500] <...LDAPSingleHostPool.getConnection> got connection from getConnection() for pool Pool number:0. Host=myDomainName
FINE [2012-02-11T13:42:41.441-0500] <...LDAPSingleHostPool.getConnection> got connection from getConnection() for pool Pool number:0. Host=myDomainName
FINE [2012-02-11T13:42:41.460-0500] <...LoginModuleHelper.checkIfUserInAdminGroup> user: admin; isMemberOf = cn=Service Administrators, ou=Groups, o=isp
FINE [2012-02-11T13:42:41.684-0500] <...DavBrowserServlet.service> Got a non standard condition: getNode returned null for uri /davserver/browse/h/myDomainName/myUserName/calendar
FINE [2012-02-11T13:42:41.684-0500] <...DavServerServlet.service> [RES] [404] Command execution time: 2.527 secs
I can hit this page from the browser:
http://myDomainName:4848
From my understanding, that is the admin port. That brings up the GlassFish server admin page.
I do not remember creating a calendar account anywhere is my first thought. I followed the example deployment step by step so far and nowhere does it have me create a calendar user account. So, maybe there is no account at this point?
So, my first question would be:
How can I verify that I have a calendar account to begin with? ( or is this what I am doing by trying to log into the sites suggested under 'Test Calendar Accounts').
My next question would be:
What does this error mean: "getnode returned null for uri error for caldav server"?
Spin off question from that:
What should I do to fix that error?
Thanks in advance!I did not put a slash at the end of the uris I was testing
http://myDomain.com:80/davserver/browse/h/myDomain/myUserName/calendar
http://myDomain.com:80/davserver/dav/h/myDomain/myUserName/calendar
Once I put the slash at the end of the uri, the configuration page appeared and the error was not displayed about getNode anymore:
http://myDomain.com:80/davserver/browse/h/myDomain/myUserName/calendar/
http://myDomain.com:80/davserver/dav/h/myDomain/myUserName/calendar/ -
Alert Configuration not showing up: Error 404
Hi, we engaged this issue some days now and we already checked some entries in this forum but altering doesn't show up in RWB!
So we already did:
1. Activated all services concerning Alerts (SICF)
2. added all user rules to the users in charge
3. checked notes 913858, 750287 etc.
we found sth. what we don't know if its right. When looking in exchange profile we edited the parameter com.sap.aii.rwb.server.centralmonitoring.r3.ashost in the fully qualified hostname. But when checking entries like com.sap.aii.ib.server.connect.webas.r3.ashost we only see the hostname - not fully qualified. so paremeters look like this:
com.sap.aii.rwb.server.centralmonitoring.r3.ashost = server02.domain.local
com.sap.aii.ib.server.connect.webas.r3.ashost = server02
Doesn't these parameters have to be in same structure?! So when we changed com.sap.aii.rwb.server.centralmonitoring.r3.ashost in server02 we could not sign on to RWB service with any user.
Can somebody help us on this issue?! We have to activate altering but its is not showing up in RWB at all!
brhI,
Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
Regards
Maybe you are looking for
-
Macbook air battery cut in half after Mavericks upgrade- help?
Hey everyone, I have a mid-2013 MBA that would get 10-12 hours of life, on average, with ML. After upgrading to 10.9 though, the battery life has been cut in half. Not only that, but the battery still drains when I have the lid closed and runs hot in
-
Skype number is suddenly not working for me and my...
Skype number is suddenly not working for me and my colleagues to RECEIVE outside calls. Any ideas? When I try to call my skype from my cell, it doesnt ring on either end. It appears connected on the cell phone since the counter clock for the call i
-
Korean messages broken into multiple lines
When I send messages to other iOS running devices from my Mac with Messages beta, the message I typed in non-Roman characters (Korean) will be broken into multiple lines word-by-word quite frequently, Also, there seems to be random punctuation added
-
Having problem with update new os4.3.2 of ipod touch G4
Dear All can anyone help to solve my problem, that i can't update lastest version OS 4.3.2 of Ipod Touch, because now i have problem on screen display by using os4.3 as i have tried many times but i can't get the lastest one. so please give me sugge
-
Ooh When I select Reporting Scorm, project won't run
I can run my course fine in the published version and in preview. BUT When I select, Reporting, Standard Scorm and then try and preview the project the course is a foggy colour and it wont run. I haven't got a SCORM LMS link until next week and wa