Web services info page

How can I make the printer stop printing the web services page on my "LJ400 color M451dn" printer. I went into the printer web interface and the web services appear to be not enabled. I do have it on a small network... do I have to go to every pc and check to see if it is enabled ??
Thanks

Hi JLPlus,
I am sorry, but to get your issue more exposure, I would suggest posting it in the commercial forums, since this is a commercial product. You can do this at http://h30499.www3.hp.com/hpeb/
I hope this helps.
Regards,
Happytohelp01
Please click on the Thumbs Up on the right to say “Thanks” for helping!
Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
I work on behalf of HP

Similar Messages

Unable to open web service tester page

Hi
I'm three days trying to resolve this problem. I 'dont find a solution. I'm using ejb3.0 and web service. When I test the the application show me the messages Unable to open web service tester page. The application server is start up.
I'm trying this example. http://www.netbeans.org/download/flash/platform_55/platform_ws/
When I try to deploy the application show me this error.
C:/Sun/AppServer/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext;C:/Sun/AppServer/javadb/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain=appserv-ws.jar,commons-logging.jar,commons-launcher.jar
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=%HADB_HOME%/lib/hadbjdbc4.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbm.jar,%HADB_HOME%/lib/hadbmgt.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.configName=server-config
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Sun/AppServer/jdk/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/imq/lib/imqxm.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,appserv-ws.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.xml.bind,javax.help,javax.portlet
-Dcom.sun.aas.classloader.serverClassPath=C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Microsoft SQL Server\80\Tools\Binn\;C:\Archivos de programa\subversion-1.3.2\;C:\Archivos de programa\Subversion\bin;C:\Archivos de programa\QuickTime\QTSystem\;;;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.installRoot=C:/Sun/AppServer
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=
-Dcom.sun.aas.ServerClassPath=
-cp
;C:/Sun/AppServer/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start|#]
Starting Sun Java System Application Server Platform Edition 9.0 (build b48) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_06] from [Sun Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
sgmt.service_initialized
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://dani:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
autoDeployment status dir missing, creating a new one
[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\MEjbApp.ear for autodeployment.
deployed with moduleid = MEjbApp
[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.
[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.
deployed with moduleid = __ejb_container_timer_app
[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.
[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__JWSappclients.ear for autodeployment.
deployed with moduleid = __JWSappclients
[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__JWSappclients.ear.
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
WEB0302: Starting Sun-Java-System/Application-Server.
WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]
WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]
WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server [server] at [/__JWSappclients]
sending notification to server...server
CORE5051: Shutting down all J2EE applications ...
CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...
CORE 5061 : Resource adapters Stop() Complete
CORE5052: Application shutdown complete.
[AutoDeploy] Disabling AutoDeployment service.
WEB0303: Stopping Sun-Java-System/Application-Server.
WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 4848
Waiting for 1 instance(s) to be deallocated
Waiting for 1 instance(s) to be deallocated
Waiting for 1 instance(s) to be deallocated
C:/Sun/AppServer/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext;C:/Sun/AppServer/javadb/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain=appserv-ws.jar,commons-logging.jar,commons-launcher.jar
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=%HADB_HOME%/lib/hadbjdbc4.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbm.jar,%HADB_HOME%/lib/hadbmgt.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.configName=server-config
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Sun/AppServer/jdk/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/imq/lib/imqxm.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,appserv-ws.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.xml.bind,javax.help,javax.portlet
-Dcom.sun.aas.classloader.serverClassPath=C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Microsoft SQL Server\80\Tools\Binn\;C:\Archivos de programa\subversion-1.3.2\;C:\Archivos de programa\Subversion\bin;C:\Archivos de programa\QuickTime\QTSystem\;;;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.installRoot=C:/Sun/AppServer
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=C:\Sun\AppServer\domains\domain1\lib\mysql-connector-java-3.1.12-bin.jar
-Dcom.sun.aas.ServerClassPath=
-cp
;C:/Sun/AppServer/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start|#]
Starting Sun Java System Application Server Platform Edition 9.0 (build b48) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_06] from [Sun Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
sgmt.service_initialized
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://dani:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
WEB0302: Starting Sun-Java-System/Application-Server.
WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]
WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]
WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server [server] at [/__JWSappclients]
ADM1041:Sent the event to instance:[ResourceDeployEvent -- reference-added jdbc/aae]
CORE5004: Resource Deployed: [jdbc:aae].
wsgen successful
DPL5306:Servlet Web Service Endpoint [AAEWebService] listening at address [http://dani:8080/WebAAEstates/AAEWebServiceService]
deployed with moduleid = WebAAEstates
WEB0100: Loading web module [WebAAEstates] in virtual server [server] at [/WebAAEstates]
naming.bind
topLink_version
application_server_name_and_version
login_successful
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/WebAAEstates'
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/WebAAEstates'
exception caught
javax.naming.NameNotFoundException
        at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
        at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
        at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
        at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
        at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
        at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
|#]
Servlet web service endpoint 'AAEWebService' failure
java.lang.RuntimeException: javax.naming.NameNotFoundException
        at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:50)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
        at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
        at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
        at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.naming.NameNotFoundException
        at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
        at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
        at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
        ... 34 more
|#]
StandardWrapperValve[AAEWebService]: Allocate exception for servlet AAEWebService
javax.servlet.ServletException
        at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:273)
        at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
        at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: java.lang.RuntimeException: javax.naming.NameNotFoundException
        at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:50)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
        at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
        ... 26 more
Caused by: javax.naming.NameNotFoundException
        at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
        at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
        at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
        ... 34 more
|#]
exception caught
javax.naming.NameNotFoundException
        at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
        at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
        at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
        at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
        at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
        at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
|#]
Servlet web service endpoint 'AAEWebService' failure
java.lang.RuntimeException: javax.naming.NameNotFoundException
        at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:50)
        at sun.reflect.NativeConstructorAccessorImpl.newIn

Hello,
you can check it at GlassFish Admin console (usually running on port 4848).
You need to log on to Admin console with the (default) or changed password (depends if you changed it during installation).
There you could see your web service deployed (usually in the "folder" Web services).
If you can see it you should see also wsdl - for your web service.
link:
http://developers.sun.com/appserver/reference/techart/ws_mgmt.html
Regards,
Miro

Web Services Test Page: No input fields for SOAP header parameters?

Hello,
we're using OracleAS / OC4J 10.1.3.1 and have developed a web service that has some self defined SOAP header parameters.
I would like to use the Web Services Test Page provided by the OAS but it seems that there is no opportunity
to provide input values for these SOAP header parameters.
Do I miss something there or is it not supported by OAS?
I've read the documentation but could not find a clue.
any help is appreciated,
Regards,
Martin

I hear you. As you have probably heard, OC4J is being replaced by WebLogic Server and the 10.1.3.x releases are the last that will be produced. We'll do maintenance on it of course, but little/no new feature work. This would be a new feature we'd have to add, so I'm afraid there's not much chance in having it done.
It's not ideal, and of course more work for you, but if you want to provide your client with a test page that exposes the SOAP headers as form fields, you could always develop and ship one yourself.
-steve0

URL for WSDL only shows web service information page

Using tomcat6 and jwsdp 2.0.
After requesting the WSDL, I instead get the Web Service information page which shows this in a table form:
Web Services,
Port Name, Status, Information
etc.
Why doesn't it give me back the WSDL instead?

The information page must contain end point wise information displayed.
Each end point information contains web service address, WSDL address(you are looking for this I hope), Implementation class etc.
Also, try giving *?wsdl* parameter at the end of your web service address, it must lead you to the WSDL file of the web service.
-typurohit (Tejas Purohit)

WebLogic Web Services Home Page and authentication

I've generated a set of web services using a session bean and have secured
my EJB methods. I'd like to enable testing of these methods via the WebLogic
Web Services Home Page service, but I can't figure out how to pass along the
authentication parameters. I've tried appending
'&username=myUser&password=myPassword' to the URL and this doesn't appear to
work (yeah, I know, but you can't blame me for trying).
Any ideas on how I might do this?
Thanks,
Rob

Looks like a bug. filed CR086448.
Contact support for patch.
regards,
-manoj
"Rob Moore" <[email protected]> wrote in message
news:[email protected]..
Hi, Manoj,
We're using WLS 7.0.0.1.
Thanks,
Rob
"manoj cheenath" <[email protected]> wrote in message
news:[email protected]..
The browser should pop up the user name/passwd dialog,
if the WS is secured. Which version of WLS are you using?
This could be a bug.
regards,
-manoj
"Rob Moore" <[email protected]> wrote in message
news:[email protected]..
I've generated a set of web services using a session bean and have
secured
my EJB methods. I'd like to enable testing of these methods via theWebLogic
Web Services Home Page service, but I can't figure out how to pass
along
the
authentication parameters. I've tried appending
'&username=myUser&password=myPassword' to the URL and this doesn't
appear
to
work (yeah, I know, but you can't blame me for trying).
Any ideas on how I might do this?
Thanks,
Rob

Customize Web Service Home Page in OC4J

I am using OC4J 10.1.2, I have developed a webservice using JDeveloper 10.1.3 by selecting j2ee sebservice version J2EE 1.3 (Oracle) Web Service. On accessing the webservice using the browser I am getting the WebService Homepage with the option to access the methods exposed. How can I disbale the home page or customize it.

Not sure if this is an exact match to your problem, but I've had problems with systems based on WebAS 7.00 truncating the hostname when generating the url for the WSDL. You may want to check the hostname is complete.
Regards,
Nick

Web Service 'Home Page' in WLS 9, can I have one like WLS 8.1 ?

Hi,
I've been using Web Services on WebLogic Server for a long time. I've just migrated from WLS 8.1 to WLS 9.2.
With 8.1, if a user entered the Endpoint of the Web service in a browser they got a nice page which showed the operations for the Web Service.
With 9.2 I'm getting a very basic page with a link to the WSDL and to the Test Page.
Is there any way I can get a nice page that looks like the one in 8.1 ?
Thanks
Dave

Not sure if this is an exact match to your problem, but I've had problems with systems based on WebAS 7.00 truncating the hostname when generating the url for the WSDL. You may want to check the hostname is complete.
Regards,
Nick

Web Service Home Page Test

Hi everyone
we are on ECC5. I have created a simple web service from a RFC, but when I try to test the home page in trnx wsadmin, I get the following error :
Cannot download WSDL from
We have created the J2EE server, but it seems like the server can not connect back to the application server (SAP) when it tries to download the WSDL.
Thanks for your assistance

Not sure if this is an exact match to your problem, but I've had problems with systems based on WebAS 7.00 truncating the hostname when generating the url for the WSDL. You may want to check the hostname is complete.
Regards,
Nick

Soap response the web service test page

Hi
I am trying to write the static client for a wlw web service. This web service doesn't have @jws:protocol specified, so it has get, post and soap. When I call one of its method using soap port in my static client, it returns the html looks like the weblogic test page for this web service. Here it is:
<-------------------- RESPONSE TO CLIENT --------------->
URL           : http://localhost:7001/webservices/testWS.jws
Response Code :200
Headers       :
Date=Thu, 07 Feb 2008 17:18:08 GMT
Content-Length=11724
Content-Type=text/html; charset=UTF-8
Expires=Thu, 01 Jan 1970 00:00:00 GMT
Connection=Keep-Alive
Set-Cookie=JSESSIONID=Hr9Qt7BTQQzvM0pGZhvyPjL7typsrTK1GLp0BZZQnRGFwfx90x8K!606
033313; path=/
Envelope   :
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<title>BEA WebLogic Workshop: testWS.jws Web Service</title>
<link rel=stylesheet href="testWS.jws?.RESOURCE=shared.css">
<body>
<table border=0 cellspacing=0 cellpadding=0 width="100%">
.....First why doesn't it return soap message? And it doesn't execute the method at all. How can I make it call the method and return the soap message?
Thanks
Edited by Holy at 02/08/2008 9:45 AM

Figured out that the testWS.jws is deployed to use ssl. But the wsdl generated has http. It works fine after I manually changed to https.

Web Services Integration issues on Oracle Web Service Example Page..

The Oracle hosted pages for the Web Services Integration, all of the applications are dying when you try and run them. 1/2 of them are having ACL (Access Control List issues)..
Don't know if this is because of the change-over to APEX 4.0 or a new version of teh database being used, just though Oracle should know and they MIGHT want to fix them..
Thank you,
Tony Miller
Webster, TX

Tony:
Thanks for pointing that out. They should now all be fixed with the exception of the Amazon sample. Amazon changed their API some time ago to require a signature parameter, I blogged about this here: http://jastraub.blogspot.com/2009/10/rest-now-supported-in-flexwsapi-and.html.
Regards,
Jason

Web service info in SICF

ECC 6.0, SP16 here. I created a web service from a BAPI recently using the WS creation wizard from SE37 (btw, using wizard from se80 gives the same results). Everything went fine, but when i go to SICF now, i see that my Web service has three extra nodes under it. I named by Web service z_tickets. So in SICF under the path /default_host/sap/bc/srt/rfc/sap i see a node z_tickets which has a node 100 (probably the client no.) which has a node under it called z_tickets which has another node under it called z_tickets. So now, the correct URL to call my web service is myhost/sap/bc/srt/rfc/sap/z_tickets/100/z_tickets/z_tickets which looks kind of awkward .... All my old web services use to be simply single node in SICF. IS this normal ???? what am i doing wrong ?? or is it because of Sp14 where the new soamanager, end of wsadmin etc kicked in ???? Please advise.

MercAMG,
I am using SOAmanager but that only to retrieve the wsdl file,nothing fancy and this step comes only after i have created the WS. The multiple nodes get created right away in SICF before i even go to soamanager to do or check anything. So, its definitely not a matter of FM being duplicated somewhere etc.
As far as the parameters in teh WS creation wizard are concerned, I am using very normal ones, give a z name for WS, choose FM as the endpoint, choose low or No security profile, check box for deploy service (even unchecking it doesnt help), choose my transport request and package and complete. any clues ?

Cannot test authenticated web service from Web Service test page

I tried to test my page from using http://localhost:7001/wls_utc. It seems to work fine in my production environment but not in my local machine. I got the following error:
Parse of wsdl (http://localhost:7001/mywebservice?WSDL) failed due to weblogic.testclient.WsdlParseFailedException: weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from InputSource due to -- java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'http://localhost:7001/mywebservice?WSDL'.
With the following access log
127.0.0.1 - username [31/May/2007:16:37:45 -0400] "GET /mywebservice HTTP/1.1" 200 68509
127.0.0.1 - - [31/May/2007:16:37:45 -0400] "GET /mywebservice HTTP/1.1" 401 283
127.0.0.1 - username [31/May/2007:16:37:43 -0400] "GET /wls_utc/begin.do HTTP/1.1" 200 2648
I noticed that the second line did not appear in my production server. Is there something wrong in my configuration?
Thanks,
Edited by nluengna at 05/31/2007 1:45 PM

Thanks for your help,
I don't have hardware firewall. But in gateway server of company, we have a firewall. I doubt if the 80 port in this firewall is blocked. You say that some ISP block port 80, what does it mean, does it mean that port 80 on the server of our company is blocked? But we have also web page, I can acess it from internet.
another question: if one process send some message to another, it uses the fixed port or any port selected from the free port? e.g does one process send http request using fixed 80or 8080?
Thank you

Add your printer to your ePC account/Print Web Services Info Sheet

I do not get the "Sign Up" when I go to the "Sign In", so the whole process ibs maddenningly circular. I'm just wANTING TO sign up and enter my printer code, but I can't get to that point!

Hi dellis1,
Welcome to the HP Support forums. I understand that you have run into difficulties when trying to create your ePrintCenter account.
I have included screen shots for you to find where to create the account on HP's ePrintCenter web site.
Regards,
Happytohelp01
Please click on the Thumbs Up on the right to say “Thanks” for helping!
Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
I work on behalf of HP

Web Services, hiding test page.

How do you configure Workshop 8.1 to hide the Web Services test page for deployment.
This question has been posted and answered, but the answer had to do with editing
the
web-service.xml file. Workshop does not deploy a web-service.xml file.

Tim
You can change this behavior by passing notestconsole to the
startweblogic.cmd or by setting the testConsoleFlag variable to false in
the startweblogic.cmd script. Also testconsole is turned off by default for
all EAR files.
Please refer to the following document for more information on this
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/reference/commands/cmdStartWebLogicCommand.html
Regards,
Raj Alagumalai
Backline Workshop Support
"Tim " <[email protected]> wrote in message
news:3f8af6cc$[email protected]..
>
How do you configure Workshop 8.1 to hide the Web Services test page fordeployment.
This question has been posted and answered, but the answer had to do withediting
the
web-service.xml file. Workshop does not deploy a web-service.xml file.

Deploy web service on 9iAS

I have gone through the tutorial of creating a web service based on PL/SQL code. This all worked fine on my local machine, but now i would like to deploy a web service on a 9iAS application server.
I have managed to create a connection to 9iAS. When i want to deploy the web service i get the messages :
C:\jdev\jdk\jre\bin\javaw.exe -jar C:\jdev\j2ee\home\admin.jar
ormi://ifawagont014s.minlnv.agro.nl:3110/ admin **** -deploy
-file C:\apps\pcd\PCDWebService\pcd-PCDWebService-WS.ear -deploymentName pcd-PCDWebService-WS
Error: javax.naming.NamingException:
Lookup error: javax.naming.NoPermissionException: This operation was denied.
The admin.jar utility can not be used to perform operations against OPMN managed OC4J instnaces.
Please use Enterprise Manager or dcmctl instead.
Refer to the Oracle9iAS Admin Guide or the OC4J User's Guide for more details.;
nested exception is:
javax.naming.NoPermissionException: This operation was denied. The admin.jar utility can not be used to perform operations against OPMN managed OC4J instnaces. Please use Enterprise Manager or dcmctl instead. Refer to the Oracle9iAS Admin Guide or the OC4J User's Guide for more details.
Exit status of OC4J admin tool (-deploy): 1
Elapsed time for deployment: 7 seconds
#### Deployment incomplete. #### 21-feb-03 16:15:26
Apparently i don't have enough privileges to register the web service?
So i move to Enterprise Manager. I generate a WAR-file and deploy this WAR-file on 9iAS in the OC4J_HOME instance.
When i test the web service by calling the WSDL file using :
ttp://ifawagont014s.minlnv.agro.nl:7777/pcd-PCDWebService-context-root/pcdws.PostcodeWebService
the respons is :
pcdws.Postcode WebService
Sorry, I don't speak via HTTP GET- you have to use HTTP POST to talk to me.
Servlet Path: /pcdws.PostcodeWebService
QueryString Info: null
I think the webserver can find something, but it isn't quite right!
Who can help me?
Regards, Dick Dral

Actually, it sounds like your deployment worked fine ... the message:
"Sorry, I don't speak via HTTP GET- you have to use HTTP POST to talk to me."
is the message that comes up in Oracle9iAS 9.0.2 at a Web service endpoint. Add a ?WSDL to the URL and you should get the WSDL for the Web service. Add a ?proxy_source to the URL and you should be able to download a client to the Web service.
Check out this tutorial at step 24 (http://otn.oracle.com/tech/webservices/htdocs/series/plsql/content.html) and you will see how the endpoint URL generates a more satisfying Web service home page in Oracle9iAS 9.0.3 versus the cryptic, but valid message in 9.0.2.
As for your deployment, the use of admin.jar for deployment only works on stand-alone OC4J's versus real full installations of Oracle9iAS - this is why the Enterprise Manager interface you used worked but the admin.jar did not. There is also a command line interface for Oracle9iAS called DCM which you can read about at:
http://download-west.oracle.com/docs/cd/A97329_03/core.902/a92171/dcm.htm#620714
that gives similar functionality. The reason that admin.jar does not work is that DCM and OEM solve a bigger problem in that they also support deployment to and configuration of a clustered environment so have that extra functionality built in.
Hope this answers your questions and gets you going.
Mike.

Web services info page

Similar Messages

Maybe you are looking for