Calling a Axis2 Secure Web Service with JDeveloper 11g

We are attempting call a Blackboard (Axis2) web service using Oracle JDeveloper 11g. We are currently unable to generate the security header required, could anyone please point me in the right direction?
I have following the following steps highlighting my issue. What steps might I be missing? Should I have created a keystore? Should I implement this with the metro stack? Any help or suggestions to go in a different direction would be greatly appreciated.
1. Install JDeveloper 11.1.1.5.0 (accept defaults)
2. Open JDeveloper
3. Create a Project by selecting File > New > Generic Project > Finish
4. Right-click newly created project and select New
a. Select Web Services in the Categories
b. Select Web Service Proxy, then Next
c. Next
d. Select JAX-WS Style, then Next
e. Enter http://gpstc.blackboard.com/webapps/ws/services/Context.WS?wsdl for the WSDL Document URL, then Next
f. Next
g. Remove “:80” from the Endpoint URL in each row, the first row should be http://gpstc.blackboard.com/webapps/ws/services/Context.WS, then Next
h. Next
i. I don’t see an option for WSSOAP12Binding which this webservice utilizes, so I selected “oracle/wss11_username_token_with_message_protection_client_policy”
j. Next
k. Finish
5. As a test, add the following code after “// Add your code to call the desired methods.”
GetServerVersionResponse myv = new GetServerVersionResponse();
myv = contextWSPortType.getServerVersion(new GetServerVersion());
System.out.println(myv.toString());
6. Run the Project
7. Received the following exception “Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: WSDoAllReceiver: Incoming message does not contain required Security header"
Currently running JDeveloper 11g with Oracle WebLogic Server 11gR1
Attempting to connect to Blackboard, Release 9.1.50119.0
Thanks, Adam Ham

Hi,
Did you configure the Axis2 in Jdeveloper?
Best Regards
Sunny

Similar Messages

Debugging a Web service with JDeveloper 902

JDeveloper (902) is the major development tool in my project, and till now we used RMI for remote function calls. We are considering to use SAOP instead.
I've installed JWSDP and I manage to run SOAP based Web service with Tomcat.
However, after deploying a Web service, even its screen output is hidden.
My problem is how to debug a Web service with JDeveloper?

JDeveloper (902) is the major development tool in my project, and till now we used RMI for remote function calls. We are considering to use SAOP instead.
I've installed JWSDP and I manage to run SOAP based Web service with Tomcat.
However, after deploying a Web service, even its screen output is hidden.
My problem is how to debug a Web service with JDeveloper?

Problem with tutorial; "Build a Web Application with JDeveloper 11g Using "

I've got a rather new installation of Vista Business x64 on my developer rig, and last week I installed the new JDeveloper 11g version. The installation was all-inclusive, no customization on my end.
In addition I've got a test installation of an Oracle DB 11gR1 on an available server here.
To familiarize myself with the new JDeveloper I decided to spend some time with the JDeveloper 11g tutorials found here: http://www.oracle.com/technology/obe/obe11jdev/11/index.html.
I've started twice on the second tutorial, "Build a Web Application with JDeveloper 11g Using EJB, JPA, and JavaServer Faces", and find myself repeatedly stuck at step 19 in section "Creating the Data Model and Testing it".
It seems impossible to deploy the application to the default application server. The server starts fine on its own, I can access it via the admin console on port 7001 and it looks good. However, when I try to run the HRFacadeBean funny things are happening, symptomized by the following error messages seen in the IDE log-area:
The "Messages" pane displays:
"Compiling...
Context: MakeProjectAndDependenciesCommand application=HR_EJB_JPA_App.jws project=EJBModel.jpr
C:\Oracle\Middleware\jdk160_05\jre\bin\java.exe -jar C:\Oracle\Middleware\jdeveloper\jdev\lib\ojc.jar -g -warn -nowarn:320 -nowarn:372 -nowarn:412 -nowarn:413 -nowarn:415 -nowarn:486 -nowarn:487 -nowarn:489 -nowarn:556 -nowarn:558 -nowarn:560 -nowarn:561 -nowarn:705 -Xlint:-fallthrough -Xlint:-serial -Xlint:-unchecked -source 1.6 -target 1.6 -noquiet -encoding Cp1252 -d C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\classes -namereferences -make C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\classes\EJBModel.cdi -classpath C:\Oracle\Middleware\jdk160_05\jre\lib\resources.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\rt.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\jsse.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\jce.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\charsets.jar;C:\JDeveloper\mywork\HR_EJB_JPA_App\.adf;C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\classes;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\toplink.jar;C:\Oracle\Middleware\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\Oracle\Middleware\modules\javax.persistence_1.0.0.0_1-0.jar;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\eclipselink.jar;C:\Oracle\Middleware\jdeveloper\modules\oracle.xdk_11.1.1\xmlparserv2.jar;C:\Oracle\Middleware\jdeveloper\modules\oracle.xdk_11.1.1\xml.jar;C:\Oracle\Middleware\modules\javax.jsf_1.2.0.0.jar;C:\Oracle\Middleware\modules\javax.ejb_3.0.1.jar;C:\Oracle\Middleware\modules\javax.enterprise.deploy_1.2.jar;C:\Oracle\Middleware\modules\javax.interceptor_1.0.jar;C:\Oracle\Middleware\modules\javax.jms_1.1.1.jar;C:\Oracle\Middleware\modules\javax.jsp_1.1.0.0_2-1.jar;C:\Oracle\Middleware\modules\javax.jws_2.0.jar;C:\Oracle\Middleware\modules\javax.activation_1.1.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.mail_1.1.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.soap_1.3.1.0.jar;C:\Oracle\Middleware\modules\javax.xml.rpc_1.2.1.jar;C:\Oracle\Middleware\modules\javax.xml.ws_2.1.1.jar;C:\Oracle\Middleware\modules\javax.management.j2ee_1.0.jar;C:\Oracle\Middleware\modules\javax.resource_1.5.1.jar;C:\Oracle\Middleware\modules\javax.servlet_1.0.0.0_2-5.jar;C:\Oracle\Middleware\modules\javax.transaction_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\Middleware\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar;C:\Oracle\Middleware\wlserver_10.3\common\lib -sourcepath C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src;C:\Oracle\Middleware\jdk160_05\src.zip;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\toplink-src.zip;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\eclipselink-src.zip C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\Dept.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\Emp.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacadeLocal.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacadeClient.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacade.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacadeBean.java
[11:45:27 PM] Successful compilation: 0 errors, 0 warnings.
[Application HR_EJB_JPA_App is bound to Server Instance DefaultServer]
[Starting Server Instance DefaultServer]
#### Server Instance DefaultServer could not be started: Server Instance was terminated.
The "Running: DefaultServer" displays:
"C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
[Server Instance DefaultServer is shutting down. All applications currently running will be terminated and undeployed.]
Process exited.
C:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://localhost:7101 with userid weblogic ...
This Exception occurred at Wed Oct 29 23:47:40 CET 2008.
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
 java.net.ConnectException: Connection refused: connect; No available router to destination]
 at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
 at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
 at weblogic.jndi.Environment.getContext(Environment.java:315)
 at weblogic.jndi.Environment.getContext(Environment.java:285)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
 at javax.naming.InitialContext.init(InitialContext.java:223)
 at javax.naming.InitialContext.<init>(InitialContext.java:197)
 at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:512)
 at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
 at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:305)
 at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
 at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
 at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:125)
 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:597)
 at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
 at org.python.core.PyMethod.__call__(PyMethod.java:96)
 at org.python.core.PyObject.__call__(PyObject.java:248)
 at org.python.core.PyObject.invoke(PyObject.java:2016)
 at org.python.pycode._pyx4.connect$1(<iostream>:16)
 at org.python.pycode._pyx4.call_function(<iostream>)
 at org.python.core.PyTableCode.call(PyTableCode.java:208)
 at org.python.core.PyTableCode.call(PyTableCode.java:404)
 at org.python.core.PyFunction.__call__(PyFunction.java:184)
 at org.python.pycode._pyx16.f$0(C:\Oracle\Middleware\user_projects\domains\base_domain\shutdown.py:1)
 at org.python.pycode._pyx16.call_function(C:\Oracle\Middleware\user_projects\domains\base_domain\shutdown.py)
 at org.python.core.PyTableCode.call(PyTableCode.java:208)
 at org.python.core.PyCode.call(PyCode.java:14)
 at org.python.core.Py.runCode(Py.java:1135)
 at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
 at weblogic.management.scripting.WLST.main(WLST.java:129)
 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:597)
 at weblogic.WLST.main(WLST.java:29)
Caused by: java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
 java.net.ConnectException: Connection refused: connect; No available router to destination
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
 at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
 at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
 ... 38 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
 java.net.ConnectException: Connection refused: connect; No available router to destination
 at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
 at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
 at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
 at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
 at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
 at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:303)
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:193)
 ... 43 more
Problem invoking WLST - Traceback (innermost last):
File "C:\Oracle\Middleware\user_projects\domains\base_domain\shutdown.py", line 1, in ?
File "<iostream>", line 22, in connect
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7101 Use dumpStack() to view the full stacktrace
Done
I'm not that familiar with these things but it seems to me that there is an issue with port numbers here. The application seems to expect a app.server service at port 7101, but does'nt find one.
Any suggestions on how to fix this problem would be appreciated?
LA$$E

Jupp,
It fails in a similar way.
What I did was; create a simle 'Hello World' html file, saving it with the jsp extension. In Jdev11g i made a new application and an emtpy project, then loaded the jsp file and made it the default run-target. This compiles nicely.
When running the project it first attempts to start the WebLogicServer (WLS). After a few minutes it is started as seen in the "Running: DefaultServer" pane:
C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=;C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.5/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\jdeveloper\modules\features\adf.share_11.1.1.jar;;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;;
PATH=C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.5\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\oracle_client\product\11.1.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -DproxySet=false -Djbo.34010=false -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Doracle.home=C:\Oracle\Middleware\jdeveloper -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\oracle\jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_TW.jar>
<30.okt.2008 kl 19.20 CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
<30.okt.2008 kl 19.20 CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Mon Aug 18 22:39:18 EDT 2008 1142987 >
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<30.okt.2008 kl 19.20 CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<30.okt.2008 kl 19.20 CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<30.okt.2008 kl 19.20 CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<30.okt.2008 kl 19.20 CET> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddi.war'.>
<30.okt.2008 kl 19.20 CET> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddiexplorer.war'.>
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<30.okt.2008 kl 19.20 CET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<30.okt.2008 kl 19.20 CET> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<30.okt.2008 kl 19.20 CET> <Warning> <Server> <BEA-002611> <Hostname "Kromp.lan", maps to multiple IP addresses: 10.0.0.8, 127.0.0.1>
<30.okt.2008 kl 19.20 CET> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.0.0.8:7001 for protocols iiop, t3, ldap, snmp, http.>
<30.okt.2008 kl 19.20 CET> <Warning> <Server> <BEA-002611> <Hostname "127.0.0.1", maps to multiple IP addresses: 10.0.0.8, 127.0.0.1>
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Development Mode>
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
DefaultServer startup time: 121552 ms.
DefaultServer started.
In the "Messages" pane, however, things are not looking so good:
Context: MakeProjectAndDependenciesCommand application=TestAppJsp.jws project=TestProjJsp.jpr
[7:20:49 PM] Successful compilation: 0 errors, 0 warnings.
[Application TestAppJsp is bound to Server Instance DefaultServer]
[Starting Server Instance DefaultServer]
#### Server Instance DefaultServer could not be started: Server Instance was terminated.
But, of course, the server is actually running as I can access it via its Admin Console.
So, I try to run the project again, and this time the following is shown in the "Messages" pane:
Compiling...
Context: MakeProjectAndDependenciesCommand application=TestAppJsp.jws project=TestProjJsp.jpr
[7:26:39 PM] Successful compilation: 0 errors, 0 warnings.
[Application TestAppJsp is bound to Server Instance DefaultServer]
[Starting Server Instance DefaultServer]
#### Server Instance DefaultServer could not be started: Server Instance was terminated.
The "Running: DefaultServer" now comes up with:
C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
[Server Instance DefaultServer is shutting down. All applications currently running will be terminated and undeployed.]
Process exited.
The WLS is still running though as I can still access its adm console.
To me it seems that it is attempting to start a separate instance of the WLS for each run attempt, but then I could be wrong.....:(
Later I'll try to change the default WLS port from 7001 to 7101 as suggested in another port here.
I must admit that I'm a bit surprised that the JDev11g doesn't work fine at this very simple level when performing a default install.

Securing web services with Sun Access Manager

Hi!
I have gone through some documentation about Sun Access Manager, and I'm a little bit confused.
What I want is to secure some web services which are deployed on a BEA WebLogic 9.1 server (WLS). Two solutions are possible: To install some kind of plugin into WLS or to place some kind of proxy in front of WLS. In both cases, the purpose would be to authenticate the caller based on some kind of ticket (SAML or similar) and authorize access to the web service.
I have read about the "Sun Java System Access Manager Policy Agent 2.2 for Weblogic 9.1" (those guys really like long names....), but in this documentation web services aren't mentioned at all. They only seem to care about HTTP requests from a browser.
I have also read about the Policy Agent 2.2 in the documentation called "Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Application Server 9.0/Web Services" (puh...). This document explicitly talks about securing web services the way I want.
My questions are:
1) Is it possible to secure WLS based web services in the same way using the Policy Agent for WLS?
2) Are there any documentation/tutorials/etc?
Thanks in advance :-)
Anders

what you need is a webservices agent that would enable you to "protect" your webservice provider, which I assume is on a BEA weblogic provider.
the "Sun Java System Access Manager Policy Agent 2.2 for Weblogic 9.1" is "NOT" awebservices agent, but a normal J2EE policy agent.
So.. having said that. here's what I'd recommend.
1. install the webservices agent on bea weblogic. (note: NOT the J2EE policy agent)
2. configure it to use your access manager instance for authentication.
3. configure your webservices client to use the webservice provider. (note: you'd need the webservices APi's available on the client too... so the quick dirty method would be to install the webservices agent on your client too....) you can later bundle the webservices client independently and provide your"customers" with a webservices client bundle...
4. voila... your webservices are not "protected" by acces manager ;-)

Connect to Secure web service with certificate from SAP EP

Hi Experts,
Here is the current situation:
1. Our business requirement is to connect 3rd party RESTful web service which requires secure connection with private client certificate attached
2. I've tested in my Java test application and successfully attached private certificate to HttpsURLConection request to the web service and made a connection. No problem at all.
KeyStore keyStore = KeyStore.getInstance("PKCS12");
InputStream inputStream = new FileInputStream("privateKeyCert.p12");
keyStore.load(inputStream, "myPassword".toCharArray());
KeyManagerFactory keyManagerFactory = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
keyManagerFactory.init(keyStore, "myPassword".toCharArray());
KeyManager[] kms = keyManagerFactory.getKeyManagers();
SSLContext sslContext = SSLContext.getInstance("SSL");
sslContext.init(kms, null, new SecureRandom());
SSLSocketFactory sockFact = sslContext.getSocketFactory();
URL url = new URL("https://www.thirdpartywebservice.com/testroot/");
HttpsURLConnection conn = (HttpsURLConnection) url.openConnection();
conn.setSSLSocketFactory(sockFact);
conn.setRequestMethod("POST");
conn.setDoOutput(true);
conn.setDoInput(true);
conn.setUseCaches(false);
conn.setDefaultUseCaches (false);
conn.setRequestProperty("Content-Type", "text/xml");
3. Next, I tried to apply my Java application to SAP EP NetWeaver, and found that I have to use SecureConnectionFactory:
https://help.sap.com/saphelp_nw70ehp1/helpdata/en/e2/71c83edf72e16be10000000a114084/content.htm
4. So, I modified my Java code for SAP EP:
KeyStore keyStore = KeyStore.getInstance("PKCS12");
InputStream inputStream = this.getClass().getClassLoader().getResourceAsStream("privateKeyCert.p12");
keyStore.load(inputStream, "myPassword".toCharArray());
SecureConnectionFactory scFactory = new SecureConnectionFactory(keyStore);
HttpURLConnection conn = scFactory.createURLConnection("https://www.thirdpartywebservice.com/testroot/");
conn.setRequestMethod("POST");
conn.setDoOutput(true);
conn.setDoInput(true);
conn.setUseCaches(false);
conn.setDefaultUseCaches (false);
conn.setRequestProperty("Content-Type", "text/xml");
And I'm facing the following error message:
Exception: java.security.UnrecoverableKeyException: ja
va.security.GeneralSecurityException: Unable to decrypt private key: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 253
Could you please help me what this error message means?
Do you think do I need to to do some other configuration to make connection to web service with client certificate?
This is our first approach. Please help...
Thank you in advance.

SunJSSE implement SSL server CertificateRequest in a strict mode, if client failed to find a proper certificate corresponding the server request, it does not guess what's the proper certificate and send to the server. In your case, because there is no intermediate certificate in the client context, so there is no way to make the decision which certificate would be acceptable by server, so client does not send any cert to server. That's why you got a handshaking error.
I guess your client key store does not contains a full certificate path from the client end-entity certificate to the root CA. Please import the full certificate path into the key store.
BTW, these approaches should work, but I found no reason why one does not adopt #1:
1. import the full certification path of client certificate into client key store.
2. as a workaround, configure the server to send a list including the intermediate certificates;
3. as a workaround, you will have to customize the client KeyManager if you don't want to or are not able to configure the server to send a list including the intermediate certificates.

Web services with JDeveloper - serialization error

Dear all,
I have an issue with web services created with JDeveloper 10.1.3.2.0.
Namely, this is what I do:
1. I've created some TopLink classes from tables; one of this classes is called Task (and it's located in a package called "integration")
2. I've created another class, called Integration, where I use these TopLink classes; in this new class I have a method called getTasksStatus, which returns an ArrayList containing Task objects
3. I've created a web service from this class (Integration) by right-clicking on the class name in Applications Navigator and choosing Create J2EE Web Service.
When I call the method getTasksStatus from the test web service (endpoint),
I get this error:
Oct 8, 2007 7:14:30 PM oracle.webservices.service
SEVERE: serialization error: no serializer is registered for (class integration.Task, null) serialization error: no serializer is registered for (class integration.Task, null)
When I call a method which returns a primitive type, everything is fine.
I understand the problem, but I don't know a solution yet. Could you please help ?
Thank you,
Best regards,
Sorin

One solution to this problem is to make sure that the complex type you are using in yous service interface do implement the JAVA Bean as per the spec (at least Oracle's interpretation of it).
You need to have getter/setter for all members and you need to have an empty ctor() to create new instances of your objects. In some cases, the design time let you get by, but the runtime fails in the code generation.
In your case, the 'Task' class may have some issue.
Hope it helps,
-eric

JAX-WS PL/SQL Web Service with JDeveloper (Weblogic problem)

Hello,
does anyone know how to create a JAX-WS webservice based on a pl-sql package using JDeveloper? Maybe it is possible with a newer version of JDeveloper 11.1.2.3, currently I'm using 11.1.1.6 which only offers a JAX-RPC for PlSql Web services.
I'm facing a problem right now trying to deploy an jax-rpc web service on Weblogic 10.3.4. Actually it seems to be an WebLogic problem because weblogic doesn't support the older standard (JAX-RPC). So I've extended the weblogic domain using Fusion Middleware Configuration Wizard like described for example here . Unfortunately it doesn't help. Deploying my applicaiton on a forms11g (11.1.1.4) domain (which goes hand in hand with the weblogic domain (?)) is successful. But anyway I can't call the WSDL or test the web service using weblogic console. Other services (jax-ws) work without any problem on the same forms domain.
I would appreciate any hint, how to automatically produce an jax-ws web service from an plsql package or how to run a jax-rpc web service on weblogic 10.3.4. It's Weblogic Basic Server actually, but I'm of the opinion it doesn't play a role in my case.
Thank you in advance for your hints.
Kind regards,
Anton
Edit: I would appreciate any hint how to check if a weblogic domain supports jax-rpc (if extended correctly). Thanks.

We can generate jaxws from 11.1.2.0 onwards using This is now provided by the TopLink web service provider builder, which can be via the TopLink DBWS provider wizard from JDeveloper since the 11.1.2.0.0 release
1.4.4 Database Web Services (DBWS)
http://docs.oracle.com/cd/E23943_01/doc.1111/e26045/general.htm#CHDIEEHG
Hope that heps
Regards,
Sunil P

How to use ComplexType in Web Services with Jdeveloper

I've look an article which says:
If the parameter is created as a JavaBean that implements the java.io.Serializable interface and exposes all of its properties using the accessor style of getX and setX, Oracle Application Server will handle the XML serialization and deserialization automatically.
but when I use jdeveloper to create a web Service it only comes up with the warning:
Method addCourse:the following parameter types do not have an XML Schema mapping and/or serializer specified:
mypackage.CourseJavaBean
my code is:
package whut.mypackage;
import java.io.Serializable;
public class CourseJavaBean implements Serializable

Hi Dugu,
Can you give the link to the specific article and the version of JDeveloper you are using to help you further?
One thing to keep in mind is that the accessors must be public - using package access (no modifier) is not going to work.
Hope this helps,
Eric

Web services with Jdeveloper using weblogic as server

Hi,
I try to test creating PL/SQL web services by using a connection hosted by weblogic server instead of OC4J. The problem is what I try to publish a package of the database in the second stage when it asks for the connection to use, in the list I don't found the connection I create to weblogic . It presents as choice only connections used the server OC4J.
I do not Know if it is possible to publish a package as web service by using weblogic server connection, and how to do it.
can anyone help me please .
Nawal

Web services can only be published to BEA if you install Apache SOAP on BEA and use the Apache SOAP option of JDeveloper. The J2EE Web Services implementation framework is specific to Oracle9iAS.
The PL/SQL Web Services server implementation is based on the J2EE Web Services option and as a result is not really portable to BEA.
To publish a PL/SQL Web service on BEA with JDeveloper you would have to write the Java wrapper code to invoke the stored procedure using standard JDBC and then publish that Java class as a Web service using Apache SOAP. Then if you had Apache SOAP installed on BEA you would be set.
Portability of Web services implementations is a big feature coming with JAX-RPC - currently what most vendors have is interoperability between implementations because of things like SOAPBuilders and WS-I. When JAX-RPC becomes part of J2EE 1.4 roughly in June and vendors start putting out implementations on it you should get closer to portability.
In the meantime, the easiest way to get portability is to use the same SOAP server on both servers - Apache SOAP is a good example.
Hope this helps.
Mike

Consuming web services with JDeveloper

Hi everyone, Im trying to consume a web service from an Oracle database 9.2.0.6, which has Java 1.3.1. I started using JDeveloper 10.1.2 with sdk 1.4, but when ever I tried to deploy into the database a bunch of libraries had to be pointed in order to successfully load it into the database, and besides it never worked.
I assumed that it was for the java versions, since in the database I have an older one. I then downloaded java 1.3.1 in my PC and when I compiled my code (defining a 1.3.1 profile before to point to javaw in 1.3.1 version) but when I tried to execute I get the error (Unsupported major.minor version 48.0). I read that this happens according to the VM version.
I decided to move then to JDeveloper 9i, but when creating my stub and uploading it to the database, it keeps asking to add libraries which some of them I don't know where are (oracle/bali, oracle/jsp..etc)
What do I need to generate my stub correctly and then deploying it to database? What versions for Jdev and Java SDK do I need to get it working correctly?

One solution to this problem is to make sure that the complex type you are using in yous service interface do implement the JAVA Bean as per the spec (at least Oracle's interpretation of it).
You need to have getter/setter for all members and you need to have an empty ctor() to create new instances of your objects. In some cases, the design time let you get by, but the runtime fails in the code generation.
In your case, the 'Task' class may have some issue.
Hope it helps,
-eric

Error when publishing a PL/SQL Web Service with JDeveloper 10.1.3!!!!!!!!!

Hi,
When I publish a PL/SQL package as a web service in J2EE 1.4 (Jax-RPC) Web Service version get this error:
oracle.j2ee.ws.common.tools.api.ValidationException: Error in database webservices assembly
     at oracle.j2ee.ws.tools.wsa.db.WSADBPlugin.processDBEndpoint(WSADBPlugin.java:329)
     at oracle.j2ee.ws.tools.wsa.Util.processDBEndpoint(Util.java:887)
     at oracle.jdeveloper.webservices.model.plsql.PLSQLGenerator.preparePLSQLPortTypes(PLSQLGenerator.java:734)
     at oracle.jdeveloper.webservices.model.plsql.PLSQLGenerator.doGeneration(PLSQLGenerator.java:233)
     at oracle.jdeveloper.webservices.model.Generator.generateImpl(Generator.java:447)
     at oracle.jdeveloper.webservices.model.Generator.generate(Generator.java:295)
     at oracle.jdeveloper.webservices.model.WebService.saveEditImpl(WebService.java:3971)
     at oracle.jdeveloper.webservices.model.WebService.mav$saveEditImpl(WebService.java)
     at oracle.jdeveloper.webservices.model.WebService$1.run(WebService.java:3817)
     at oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:446)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
     at java.lang.Thread.run(Thread.java:595)
GRAVE: JPublisher error: please check assembler settings, database connection and database schema. Use debug=true for details.
and when use J2EE 1.3 (Oracle) version WEb Service get this error:
java.lang.NullPointerException
at oracle.jdevimpl.webservices.generator.WrapperClassGenerator.generate(WrapperClassGenerator.java:262)
at oracle.jdevimpl.webservices.generator.SPWebServiceGenerator$1.run(SPWebServiceGenerator.java:285)
at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
at java.lang.Thread.run(Thread.java:595)
..... Is this a BUG????
please help!

OK, This is the PL/SQL package:
Function:
FUNCTION Obtener_paises RETURN res_webservice AS
v_respuesta res_webservice;
i PLS_INTEGER:=1;
CURSOR C_paises IS
SELECT cpais, tpais
FROM paises
ORDER BY tpais;
BEGIN
v_respuesta := res_webservice(null,null);
v_respuesta.error := res_error(null,null,null);
v_respuesta.error.cerror := 0;
v_respuesta.error.cerror_ora := 0;
v_respuesta.error.terror := null;
v_respuesta.datos := res_datos ();
FOR v_pais IN C_paises LOOP
v_respuesta.datos.extend;
v_respuesta.datos(i) := reg_datos(null,null);
v_respuesta.datos(i).codigo := v_pais.cpais;
v_respuesta.datos(i).descripcion := v_pais.tpais;
i := i + 1;
END LOOP;
Insertar_log(NULL,SYSDATE,'C','Obtener_paises',NULL,'ERROR:0');
RETURN v_respuesta;
EXCEPTION
WHEN OTHERS THEN
v_respuesta.error.cerror := 1;
v_respuesta.error.cerror_ora := SQLCODE;
v_respuesta.error.terror := substr(SQLERRM,1,80);
Insertar_log(NULL,SYSDATE,'C','Obtener_paises',NULL,'ERROR:1 '||substr(SQLERRM,1,120));
RETURN v_respuesta;
END Obtener_paises;
TYPES USED:
CREATE OR REPLACE
TYPE res_webservice AS OBJECT (error res_error, datos res_datos);
CREATE OR REPLACE
TYPE res_error AS OBJECT (cerror NUMBER(1), cerror_ora VARCHAR2(12), terror VARCHAR2(80));
CREATE OR REPLACE
TYPE res_datos AS TABLE OF reg_datos;
CREATE OR REPLACE
TYPE reg_datos AS OBJECT(codigo VARCHAR2(12), descripcion VARCHAR2(150));
Thanks in advanced...
Could happen this bacause of these defined types???

Read web service with JDeveloper

I have web service from AJPES, but i have problem how to read it. I search for good how to but i can not find it. Does anyone know any good how to for reading web service and manipulate with it?
regards
Mitja

http://www.oracle.com/technology/obe/obe11jdev/ps1/webservices/ws.html

Securing Web Services with Access Manager

Hello All
I have installed the java_app_platform_sdk-5_04-windows.exe that comes with Acces Manager 7.1.
I want to secure a webservice, so I have created a webapplication (with netbeans 6) with a webservice inside. I have also create a web client application that calls the webservice. The providers are configured in the server and I have enabled the soap security .
When I use anonymous authentication everything works fine, but if I used any other security method the following exception arises:
[#|2008-04-29T09:41:07.343+0200|SEVERE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=21;_ThreadName=httpSSLWorkerThread-8080-0;_RequestID=1a997eb3-6287-41f4-a540-0b9c86841683;|AMServerAuthModule.validateRequest: Failed in Securing the Request.|#]
[#|2008-04-29T09:41:07.375+0200|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=21;_ThreadName=httpSSLWorkerThread-8080-0;_RequestID=1a997eb3-6287-41f4-a540-0b9c86841683;|java.lang.reflect.InvocationTargetException
     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:597)
     at com.sun.identity.agents.jsr196.as9soap.AMServerAuthModule.validateRequest(AMServerAuthModule.java:173)
     at com.sun.enterprise.security.jmac.config.GFServerConfigProvider$GFServerAuthContext.validateRequest(GFServerConfigProvider.java:1179)
     at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:168)
     at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
     at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:159)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
     at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
Caused by: com.sun.identity.wss.security.SecurityException: Unsupported security mechanism.
     at com.sun.identity.wss.security.handler.SOAPRequestHandler.validateRequest(SOAPRequestHandler.java:232)
     ... 46 more
|#]
[#|2008-04-29T09:41:07.390+0200|SEVERE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=21;_ThreadName=httpSSLWorkerThread-8080-0;_RequestID=1a997eb3-6287-41f4-a540-0b9c86841683;|SEC2002: Container-auth: wss: Error validating request
com.sun.enterprise.security.jauth.AuthException: Validating Request failed
     at com.sun.identity.agents.jsr196.as9soap.AMServerAuthModule.validateRequest(AMServerAuthModule.java:188)
     at com.sun.enterprise.security.jmac.config.GFServerConfigProvider$GFServerAuthContext.validateRequest(GFServerConfigProvider.java:1179)
     at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:168)
     at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
     at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:159)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
     at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
Caused by: java.lang.reflect.InvocationTargetException
     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:597)
     at com.sun.identity.agents.jsr196.as9soap.AMServerAuthModule.validateRequest(AMServerAuthModule.java:173)
     ... 41 more
Caused by: com.sun.identity.wss.security.SecurityException: Unsupported security mechanism.
     at com.sun.identity.wss.security.handler.SOAPRequestHandler.validateRequest(SOAPRequestHandler.java:232)
     ... 46 more
|#]
It�s says something about th security mechanism is not supported. But I don�t know why. �Any idea?
Thank you

Hello again,
I am not using ssl. I am using the usernametoken or de saml-voucer mechanish and It happens in both. But with the anonymous mechanism doesnt happen.
...

401 Unauthorized Error When calling a SharePoint REST web service from SharePoint 2013 Workflow

We have our Workflow Manger installed on the same server as our SharePoint 2013 WFE development environment. When creating a SharePoint 2013 Workflow all Calls to a SharePoint 2013 REST web service results in a 401 Unauthorized error.
As an example I created a simple workflow that should return a JSON result. The REST Url returns the results in the browser without error.
Set Variable:webServiceUrl to https://<hostnamedsitecollection>/_vti_bin/client.svc/web/lists/getbytitle('ISR%20Approvers')/Items?$select=Title&$filter=Title%20eq%20%27General%27
then Build{...} Dictionary (Output to Variable:requestHeaders)
then Call [%Variable:webServiceUrl%] HTTP web service with request (ResponseContent to Variable:responseContent |ResponseHeaders to responseHeaders | ResponseStatusCode to Variable:responseCode)
The RequestHeader is set to the requestHeaders variable though the web service call properties
then Log Variable:responseCode to the workflow history list
After manually running the workflow in SharePoint on a list item in the ISR Approvers list it Logs "Unauthorized" in the Workflow History Log. It does this with every SharePoint REST web service call that I have tried through the workflow.
It doesn't have anything to do with the Workflow Manger being installed on the same machine as the SharePoint WFE does it?
Thank You for any insight

Hi,
According to your post, my understanding is that you had 401 Unauthorized Error when calling a SharePoint REST web service from SharePoint 2013 Workflow.
Please make sure you use the ‘Call HTTP Web Service’ correctly.
You can enter the URL into the brower to check whether it is correctly.
You need to
create the Request header requestHeaders
using a Dictionary:
Accept : application/json;odata=verbose
Content-Type : application/json;odata=verbose
To associate the
requestHeaders variable, select the Call action
property, set the RequestHeaders property to
requestHeaders.
Please refer to the following articles:
Working with Web Services in SharePoint 2013 Workflows using SharePoint Designer 2013
Calling the SharePoint 2013 Rest API from a SharePoint Designer
Workflow
In addtion, you need to make sure you install the workflow manager correctly.
More information:
Install and configure workflow for SharePoint Server 2013
Known Issues in Workflow Manager 1.0
Troubleshooting Workflow Manager 1.0 Management and Execution
Best Regards,
Linda Li
Linda Li
TechNet Community Support

ABAP Web Service with tables

Hello,
 
 
We need to build a web service with a predefined message in our ERP (ABAP), without PI or WebAS JAVA.
 
 
We thought it should be a simple task, because we had no problem with many other applications and systems when building the same service, but were not able to build it with SAP ABAP, probably as a consequence of our lack of knowledge on ABAP SOAP runtime.
 
 
We have an external asynchronous process that delivers information to many other systems using web services (information diffusion). Concecuently, the web service call's structure is determined by the caller, so we have to fulfill this structure if we want to receive the info.
 
 
The owner of the process defined a very simple service call, in which one kind of "record" can be repeated 1 to n times:
 
 
 
 
 
 
<reglasSuscripcion>
 
 <!Zero or more repetitions:>
 
 <nombre>?</nombre>
 
 <valor>?</valor>
 
 <nombre>?</nombre>
 
 <valor>?</valor>
 
 <nombre>?</nombre>
 
 <valor>?</valor>
 
 
 <nombre>?</nombre>
 
 <valor>?</valor>
 
</reglasSuscripcion>
 
 
 
In order to receive this info, we have to implement an abap web service handler to accept this kind of call, the same way other applications/systems have already done.
 
 
We tried to build a RFC function call and create a web service with the wizard and it resulted in a web service with the following WSDL:
 
 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:sap-com:document:sap:soap:functions:mc-style">
 
 
 
 
 <reglasSuscripcion>
 
 <!Zero or more repetitions:>
 
 <item>
 
 <nombre>?</nombre>
 
 <valor>?</valor>
 
 </item>
 
 
 
 
<item>
 
 <nombre>?</nombre>
 
 <valor>?</valor>
 
 </item>
 
 </reglasSuscripcion>
 
 
 
 
We found two main problems:
 
 
1.- When "wrapping" the RFC as a WS with the wizard, for a table datatype it automatically includes the <item></item> tag, so we break the predefined calling rules.
 
 
2.- The namespace is fixed by the wizard, and we would like to use a common namespace for all the "susbscribers", logically, the namespace fixed by the information diffusion service.
 
 
We also tried to find info on the outside-in approach for building a web service from the WSDL, but all the info we found required the ESR and we have no PI, just the ERP.
 
 
Any ideas on how to proceed?
 
 
Thanks in advance,
 
 
Joseba M. Iturbe
 
 
Edited by: Soporte Desarrollo on Mar 5, 2010 10:56 AM

#2. I've recently had to "zap" some namespaces in an ECC5 system because the calling (TIBCO) system didn't appreciate the default SAP "urn" default - something to do with multiple colons in the address. There were, I think, just three table this affected, all VEP* ones. I think I should have been able to change these via the virtual interface in SE80 except that the ECC5 code was a bit "light" in this respect, so you may be able to do this now in SOAMANAGER in ECC6 (btw, I also had to re-save the WS definition within WSCONFIG and re-activate the virtual interfaces after this "zap" to generated the associated handler class again).
#1. Given your "name / value" pairs represent a complex type, then it might be better practice to have them as "item" which is probably why SAP proposes it this way... what does your custom function module parameter list look like?
Jonathan

Calling a Axis2 Secure Web Service with JDeveloper 11g

Similar Messages

Maybe you are looking for