OWSM PrivilegedActionException Problem

I'm using an OWSM gateway for outbound service calls. I've set up some services that map to the external web services I'm calling. When the attempt is made to call the external server, I'm seeing the following in gateway.log (and seeing a corresponding stack trace in the oc4j log):
WARNING: Unable to connect to URL: http://myhost:7777/gateway/services/SID0003009 due to java.security.PrivilegedActionException: javax.xml.SOAPException: Message transmission failure, response code: 500.
I can enter 'http://myhost:7777/gateway/services/SID0003009' in by browser and get to the page that includes a link to the wsdl. When I click on the link, I get the wsdl itself. If I go to the ccore "Test Page" page under Tools, enter the request information (in XML), and click the "Invoke" button, I see the same warning in gateway.log.
Has anyone seen this before and been able to correct it? If so, how?
Thanks.

It’s a WARNING though and you are able to get the WSDL from SID url. That means gateway is configured properly and may be the service is down.
Response code: 500 looks to me that the service has some problems.
I would suggest checking whether the actual service is running fine and responding to the requests.

Similar Messages

OWSM GATEWAY PROBLEM .xsd error

Hi,
I am working on OWSM gateways.I deployed a mail web service and tried to virtualise it using OWSM gateways. I have registered the service . When i use the link for service wsdl generated by OWSM in internet explorer i can see the wsdl file but when do the same using test page in OWSM i get the following error.
java.io.IOException: The document 'http://localhost:8888/gateway/services/alshirawiMail.xsd' contains HTML tags.
Also i have only tried with web services but when i try to virtualise THE WHOLE BPEL PROCESS i get error like
java.io.IOException: The document 'http://localhost:8888/gateway/services/rule_doesnot_work.xsd' contains HTML tags.
Please reply.
Thanks and regards.
Vishnu
Message was edited by:
user607746

Hi
The problem with xsd resolved but now when i invoke the service from test page i am getting this error.
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">null
<env:Body>
<env:Fault
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>ORABPEL-08021 Cannot find partner wsdl. parnterLink "OWSM_SYNC_BPEL_PROCESS" is not found in process "OWSM_SYNC_BPEL_PROCESS" (revision "1.0") Please check the deployment descriptor of the process to find the correct partnerLink name. </faultstring>
null</env:Fault>
</env:Body>
</env:Envelope>

OWSM install problems

Hi!
I run into following problem. I have 2 Windows XP PC-s, on one SOA Suite 10.1.3.1, on the other PC I Installed with the same installer only the J2EE Server and HTTP Server. The PC with SOA suite uses the WS-es deployed on the other PC. This works fine. Now I have to secure the WS-calls from the BPEL process. I decided to use OWSM Agents.
I tried to Install OWSM on the PC with only J2EE and HTTPS server from the installer I used before. There I select to install into the oracleas1 (where the J2EE and HTTP servers are installed). Installation completes, I can see the owsm directory in the Oracle_HOME directory.
In Start -> All Programs a new Application owsm oracleas1.
When I start Application server with Start -> All Programs -> Oracle-home-> Start SOA suite (this is only a J2EE server + http server, I guess this name of the start command is because the installer originally instals SOA suite) I can login to the page [hostname]/em, but page [hostname]/ccore does not appear.
How to get OWSM run correctly? Or how to check if only the owsm console is not running?
I checked Readme, and tried to start AS and OWSM with ORACLE_HOME\opmn\bin\opmnctl startall command. Again I can login to the page [hostname]/em, but page [hostname]/ccore does not appear.
I compared this installation to the install of OWSM in the SOA suite and realized that many files are missing.
I run ORACLE_HOME\owsm\bin wsmadmin initialize and after it wsmadmin install. The install command went wrong for some tries, after according to the installed OWSM on the other PC I modified install.properties. Installation went wrong with following message:
[stopwatch] [install.buildApps.policymanager.time: 2.484 sec]
[stopwatch] [install.buildApps.time: 43.656 sec]
deploy.checkServer:
[echo] Checking server status...
[echo] Server is DOWN.
deploy.waitForServer:
[echo] Waiting for server initialization...
oc4j.query.opmn:
[echo] Querying OPMN for its request host and port...
[echo] Using MAGUS:6004.
[stopwatch] [oc4j.query.opmn.time: 1.875 sec]
oc4j.checkOPMN:
[echo] Checking OPMN managed OC4J URI...
[echo] deployer:oc4j:opmn://MAGUS:6004/home
[stopwatch] [oc4j.checkOPMN.time: 22.688 sec]
oc4j.checkCluster:
[echo] Checking OPMN managed clustered OC4J URI...
[echo] deployer:cluster:opmn://MAGUS:6004/home
[stopwatch] [oc4j.checkCluster.time: 1.062 sec]
oc4j.checkRMI:
[echo] Checking stand-alone OC4J URI...
[echo] deployer:oc4j:MAGUS:6004
[stopwatch] [oc4j.checkRMI.time: 1.157 sec]
BUILD FAILED
C:\product\10.1.3.1\OracleAS_1\owsm\scripts\install.xml:1996: The following error occurred while executing this line:
C:\product\10.1.3.1\OracleAS_1\owsm\scripts\deploy.xml:395: The following error
occurred while executing this line:
C:\product\10.1.3.1\OracleAS_1\owsm\scripts\oc4j.xml:24: Unable to locate a valid OC4J URI. The server is probably down.
(I checked, and 6004 is the correct port for opmn (dont know why it is not the default 6003) and the missing files were created)
I tried to start OC4J server with with Start -> All Programs -> Oracle-home-> Start SOA suite, ORACLE_HOME\opmn\bin\opmnctl startall. I can log in into [hostname]/em, but wsmadmin install fails again. I also tried ORACLE_HOME\owsm\bin wsmadmin start and wsmadmin startOC4J.
c:\product\10.1.3.1\OracleAS_1\owsm\bin>wsmadmin start
Buildfile: c:\product\10.1.3.1\OracleAS_1\owsm\bin\..\scripts\wsm.xml
deploy.checkServer:
[echo] Checking server status...
[echo] Server is DOWN.
BUILD SUCCESSFUL
Total time: 2 seconds
But wsmadmin install still fails with server down, and [host]\ccore does not appear.
Can you please help me?
Thanks Greg

Hi!
Dont ask me how, I tried anything several times, and somehow wsmadmin install succeded. The jsso login was set in the install.properties to true, but when I am trying to access [host]/ccore, I get error
Not Found
The requested URL /jsso/SSOLogin was not found on this server.
Oracle-Application-Server-10g/10.1.3.1.0 Oracle-HTTP-Server Server at MAGUS Port 80
Any ideas?
Thanks,
Greg

Problems using Gateway on OWSM 10.1.3.1 and OWSM 10.1.3.3

Hi,
I have a problem reaching a Gateway WSDL defined on OWSM 10.1.3.3. My scenario is the following:
I have a SOA Suite 10.1.3.1 on a machine1 and I have defined a Gateway for a Webservice http://arqc:7021/CasaBolsaProxy
<?xml version="1.0" encoding="utf-8" ?>
- <s0:definitions name="CasaBolsa" targetNamespace="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
- <s0:types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:client="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://xmlns.oracle.com/BPELPreCasaBolsa">
<import namespace="http://xmlns.oracle.com/BPELPreCasaBolsa" schemaLocation="http://arqc:7021/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa" />
</schema>
</s0:types>
- <s0:service name="BPELPreCasaBolsaBindingQSService">
- <s0:port binding="s1:BPELPreCasaBolsaBinding" name="BPELPreCasaBolsaBindingQSPort">
<s2:address location="http://arqc:7021/CasaBolsaProxy" />
</s0:port>
</s0:service>
</s0:definitions>
The URL generated by the gateway is http://arqc:8890/gateway/services/SID0003017?wsdl
<?xml version="1.0" encoding="UTF-8" ?>
- <s0:definitions name="CasaBolsa" targetNamespace="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
- <s0:types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:client="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://xmlns.oracle.com/BPELPreCasaBolsa">
<import namespace="http://xmlns.oracle.com/BPELPreCasaBolsa" schemaLocation="http://192.168.20.134:7021/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa" />
</schema>
</s0:types>
- <s0:service name="BPELPreCasaBolsaBindingQSService">
- <s0:port binding="s1:BPELPreCasaBolsaBinding" name="BPELPreCasaBolsaBindingQSPort">
<s2:address location="http://arqc:8890/gateway/services/SID0003012" />
</s0:port>
</s0:service>
</s0:definitions>
and if try to test it from the menu "tools->test page" on my OWSM I don't have problems.
By needs I have another machine with SOA Suite 10.1.3.3 and I have made the same configuration as in the first machine, when I register the service on the gateway this generate the following URL http://arqdatabase:8888/gateway/services/SID0003011?wsdl and the following code:
<?xml version="1.0" encoding="UTF-8" ?>
- <s0:definitions name="CasaBolsa" targetNamespace="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
- <s0:types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:client="http://xmlns.oracle.com/BPELPreCasaBolsa" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://xmlns.oracle.com/BPELPreCasaBolsa">
<import namespace="http://xmlns.oracle.com/BPELPreCasaBolsa" schemaLocation="SID0003011,33/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa" />
</schema>
</s0:types>
- <s0:service name="BPELPreCasaBolsaBindingQSService">
- <s0:port binding="s1:BPELPreCasaBolsaBinding" name="BPELPreCasaBolsaBindingQSPort">
<s2:address location="http://arqdatabase:8888/gateway/services/SID0003011" />
</s0:port>
</s0:service>
</s0:definitions>
When I try to test this URL again by the menu "tools->test page" on my OWSM I reach the following message:
java.io.IOException: Fallo al leer WSDL de http://arqdatabase:8888/gateway/services/SID0003011,35/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa: No se ha encontrado WSDL.
I have analized the generated code by the two OAS and I´ve noticed that on the version 10.1.3.3 the WSDL to reach the webservice is different from the 10.1.3.1 version. The 10.1.3.3 version adds a "SID0003011,33" on the section schemaLocation of the WSDL, while the version 10.1.3.1 it has schemaLocation="http://192.168.20.134:7021/
Any idea to solve this issue. Why this difference??
Thank's in advance

ENGLISH AND SPANISH RESPONSE
ENGLISH
Hi!
Yes i had the same problem.
And I dont now why but the OWSM is defining WRONG in the wsdl the endpoint...
so ...
if u check the :
http://arqdatabase:8888/gateway/services/SID0003011?wsdl
in some part... in defines the endpoint... u must see the endpoint:
http://arqdatabase:8888/gateway/services/SID0003011,35/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa:
That endpoint doesnt exists!!!...
I workaround this doing the following:
I download the WSDL to my machine (http://arqdatabase:8888/gateway/services/SID0003011?wsdl )
i save it in test.wsdl
and i changed the endpoint in test.wsdl file
i change this: http://arqdatabase:8888/gateway/services/SID0003011,35/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa
to this:
http://arqdatabase:8888/gateway/services/SID0003011 (try first that u can reach this URL)
When u create the client, for example in JDEV, specify the wsdl file instead specify the URL
and it works...
SPANISH
Hola!
Yo tambien tuve el mismo problema... no se porque el OWSM genera mal el wsdl... pero me paso y lo pude resolver de cierto modo...
Si te das cuenta en la URL
http://arqdatabase:8888/gateway/services/SID0003011?wsdl
te debe de mostrar el endpoint al que va a llamar el cliente del web service...
asi que a ti ... (como me paso a mi) te muestra esto:
http://arqdatabase:8888/gateway/services/SID0003011,35/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa:
Esa direccion NO EXISTE!
Ese endpoint esta mal, no se porque lo genera asi, pero esta mal.
El endpoint deberia ser http://arqdatabase:8888/gateway/services/SID0003011
Asi que entra a la url del WSDL:
http://arqdatabase:8888/gateway/services/SID0003011?wsdl
y guarda en tu maquina este archivo. yo le puse este nombre:
test.wsdl
ya que lo guardaste
Cambia a mano, el endpoint
en lugar de esto:
http://arqdatabase:8888/gateway/services/SID0003011,35/CasaBolsaProxy?SCHEMA%2FMaqueta+ESB%2FServicios+de+Negocio%2FBpel%2FBPELPreCasaBolsa
pon esto:
http://arqdatabase:8888/gateway/services/SID0003011
(Prueba primero que este endpoint funciona)
Y ya que tienes eso, cuando general el cliente del WS, por ejemplo si lo haces desde el jdeveloper, en vez de especificar el URL WSDL... especifica la ubicacion del archivo test.wsdl.
eso debe funcionar.
Saludos!
Mauricio

OWSM: problem with content routing

Hi,
I am working on OWSM and i have registerd a service on owsm and tested it through it. it works fine. But the problem is when i click on content routing it gives me this error "The following exception occurred when processing the JSP:
Could not connect to Gateway using its URL.The Gateway is not running or there was a problem establishing connection with the Gateway. Please ensure the Gateway is running before trying this operation.
Use your browsers "Back" button if you would like to try again."
i cant use the content routing option in policy management link , otherwise the service is running fine.
Thanks in advance.
Regards,
Abhi...
Message was edited by:
Abhishek saurabh

Hi all,
Any updates??
If case of any clues, please let me know because its urgent.
Regards,
Abhi...

File authentication problem in OWSM

Hi all,
I want to create file authentication in owsm for that i created .htpasswd file in that i have given username:password. But when i am running the following command in the command prompt it's giving the problem.
Oracle_home\owsm\bin>wsmadmin md5encode username password .htpasswderror message : Target .htpasswd does not exist in this project.
pls anybody can help on this.
thanks
kmr

Hi mani,
You are giving a wrong commands. The command should be:
Oracle_home\owsm\bin>wsmadmin md5encode .htpasswd username
then it will ask for the password, give the password, then it will finish encoding.
Bye...
Chandra.

OSB problem - "mds-owsm" not open

I have a problem where my OSB proxy is not writing to my Queue and here is my error:
<Oct 9, 2011 4:03:28 PM EDT> <Info> <JDBC> <MDM2008> <osb_server1> <MDSPollingThread-[owsm, jdbc/mds/owsm]> <<anonymous>> <> <0000JBdcmk0DwW05zzWByW1E^TEz000001> <1318190608605> <BEA-001517> <Connection Pool "mds-owsm" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Oct 9, 2011 4:03:28 PM EDT> <Info> <Common> <MDM2008> <osb_server1> <MDSPollingThread-[owsm, jdbc/mds/owsm]> <<anonymous>> <> <0000JBdcmk0DwW05zzWByW1E^TEz000001> <1318190608611> <BEA-000628> <Created "1" resources for pool "mds-owsm", out of which "1" are available and "0" are unavailable.>
I checked in the console and the MDS-OWSM seems to be ok, my database is running fine. I am at the end of looking where the problem could be.
Test of mds-owsm on server AdminServer was successful.
Any help would be greatly appreciated.
Thank you.

lodestarguy
its not the error,these are captured at info level from weblogic logs.try searching for string ERROR in osb server logs and paste here

OWSM: Problem with AXIS 1.1 serveragent

Hi everybody,
Web service environment: Win XP, Tomcat 4.1, Axis 1.1, JDK 1.4 running on localhost
OWSM environment: Win XP, Oracle SOA Suite, Oracle XE database on some remote PC.
The problem: I get the following error in serveragent.log :--
com.cfluent.coreman.sdk.CoremanException: Could not get RMI ICoremanAdaptor
The root cause of this is that the server agent tries to poll localhost instead of the OWSM PC as a result I am able to apply poilicies but unable to collect statistics.. I tried changing a number of files but nothing works (even rmi to soap). What do I do so that the serveragent points to OWSM PC?
Everything works fine if the serveragent is on the same PC as that of OWSM. Has anybody tried such a scenario? Any tutorial/pointers would be helpful.
Please help!!!
Thanks

Hi,
Thanks for the update. I will try with some other J2EE server and come back on this.
However, I am not sure that the server agent will still not poll the RMI port of the localhost. Ideally should point to the remote machine on which OWSM is running.
Regards,
Kaanu

OWSM SAML Verify step problem: Missing Security Header in SOAP message

I'm having a problem with SAML steps. From gateway log:
2008-09-17 13:21:32,987 INFO [HTTPThreadGroup-58] saml.InsertSAMLSVStep - User attributes map set to generate the attribute assertions: null
2008-09-17 13:21:33,034 INFO [HTTPThreadGroup-60] saml.SAMLProcessor - Assertion Major Version :1 , Minor Version :1
2008-09-17 13:21:33,034 WARNING [HTTPThreadGroup-60] saml.SAMLProcessor - SAML Assertion verification error: An invalid token was provided
2008-09-17 13:21:33,034 WARNING [HTTPThreadGroup-60] saml.VerifySAMLStep - SAML Token verification failed:
2008-09-17 13:21:33,096 SEVERE [HTTPThreadGroup-58] wssecurity.OSDTWSSecurity - Missing Security Header in SOAP message
2008-09-17 13:21:33,096 WARNING [HTTPThreadGroup-58] wssecurity.SecurityBaseStep - Failure while applying XML Security
FAULT CODE: InvalidSecurity FAULT MESSAGE: Missing WS Security header in the SOAP message
at com.cfluent.policysteps.security.wssecurity.OSDTWSSecurity.decryptVerify(OSDTWSSecurity.java:369)
at com.cfluent.policysteps.security.wssecurity.DecryptStep.performXmlSecurity(DecryptStep.java:131)
at com.cfluent.policysteps.security.wssecurity.SecurityBaseStep.execute(SecurityBaseStep.java:238)
at com.cfluent.pipelineengine.container.DefaultPipeline.executeStep(DefaultPipeline.java:124)
but the wsse:Security header with SAML assertion IS confirmed in the incoming message log. Anybody seen this issue?

Below is the log of the incoming message just prior to the failing SAML Verify step:
<?xml version="1.0" encoding="UTF-8" ?>
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://exception.common.periop.gehc.com" xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:ns2="http://www.patient.patientmanager.periop.gehc.com/service/" xmlns:ns3="http://entity.common.periop.gehc.com" xmlns:ns4="http://entity.patient.patientmanager.periop.gehc.com" xmlns:ns5="http://entity.allergy.patientmanager.periop.gehc.com" xmlns:ns6="http://pdo.domain.customizer.periop.gehc.com" xmlns:ns7="http://entity.cases.scheduler.periop.gehc.com" xmlns:ns8="http://entity.insurance.patientmanager.periop.gehc.com">
- <env:Header>
- <ns1:Security>
- <saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="158RBY2QvCFPiTqdXYWh9A22" IssueInstant="2008-09-17T19:58:43Z" Issuer="GE" xmlns="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">
<saml:Conditions NotBefore="2008-09-17T19:58:13Z" NotOnOrAfter="2008-09-17T19:59:43Z" />
- <saml:AuthenticationStatement AuthenticationInstant="2008-09-17T19:58:43Z" AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password">
- <saml:Subject>
<saml:NameIdentifier NameQualifier="www.ge.com" Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">gowri</saml:NameIdentifier>
- <saml:SubjectConfirmation>
<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
</saml:SubjectConfirmation>
</saml:Subject>
</saml:AuthenticationStatement>
</saml:Assertion>
</ns1:Security>
</env:Header>
- <env:Body>
- <ns2:getPatient>
<ns2:patientId>137115</ns2:patientId>
</ns2:getPatient>
</env:Body>
</env:Envelope>

OWSM problems while associating clientAgent with BPEL process

Hi All,
Refering to the PDF *"Securing Oracle SOA Applications by Using Oracle Web Services Manager (Oracle WSM) Agents.pdf"* we made an clientAgent and associated that with a simple BPEL process. After that we did the following:
1) Change the Configuration Directory (with the component id of the clientAgent)
2) Enable Web Services Agent (which was not mentioned in the pdf).
3) Restart the SOA server.
At the time of executing the BPEL process it is giving an error like "internal server error". Log is not being generated for clientAgent. At BPEL domaim log it is giving the following error:
ORABPEL-02152
Instance not found in datasource.
The process domain was unable to fetch the instance with key "0ec681d22ef098ba:-529c35a1:1220cecf7e4:-7fcf" from the datasource.
Please check that the instance key "0ec681d22ef098ba:-529c35a1:1220cecf7e4:-7fcf" refers to a valid instance that has been started and not removed from the process domain.
Please reslove as early as possible.
Thanks in Advance.
Chandra.

There are a few things you can do when trying to troubleshoot this kind of problem:
1) tunnel the interaction between the BPEL server and the web service to see what SOAP messages are exchanged.
2) try to turn debugging of the ws layer on: BPEL Console>Manage Domain>Logging
2) email us your project, including the WSDL of your service so that we can take a look at it.
Finally, one best practice is to never think in terms of Java object. Instead always start by designing your WSDLs and XSDs thinking of ports and XML documents and then generate the stubs. This will guaranty that your service is interoperable.
Edwin

OWSM GATEWAY VIRTUALIZED BPEL PROCESS INVOCATION PROBLEM

Hi
This is the error i am getting when i try to invoke the VIRTUALIZED BPEL process from test page of OWSM. i have created a component and added service to it. But this error surfaced when i try to invoke the service. I can see the virtualized WSDL in internet explorer though.
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">null
<env:Body>
<env:Fault
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>ORABPEL-08021 Cannot find partner wsdl. parnterLink "OWSM_SYNC_BPEL_PROCESS" is not found in process "OWSM_SYNC_BPEL_PROCESS" (revision "1.0") Please check the deployment descriptor of the process to find the correct partnerLink name. </faultstring>
null</env:Fault>
</env:Body>
</env:Envelope>

Hi Gurus,
Any update on the issue???
Regards,
Dev

OWSM problem in OSB 11g

I'm running Oracle Service Bug 11gR1 PS3 (11.1.1.4). At installation I choose the domain extension options to enable for OWSM and also included EM to act as an OWSM, but in Proxy service i am not able to see policy tab.
Please suggest me that any configuration i have to do.
Thanks in advance

OWSM for OSB is supported only for SOAP based services.

OWSM Custom Step SOAPMessage Class Problem

I have SOA Suite installed on several different machines. All have BPEL, ESB, and OWSM installed. I have a BPEL process that calls a web service hosted on a remote machine that uses a OWSM client agent to do "security stuff". I have a custom OWSM step that does the "security stuff". On one machine everything works as it should. On another machine, I am getting the following error in the execute() method of my custom step implementation:
java.lang.UnsupportedOperationException: getSOAPBody must be overridden by all subclasses of SOAPMessage:
at my.custom.step.CustomStep(CustomStep:83)
at com.cfluent.pipelineengine.container.DefaultPipeline.execute(DefaultPipeline.java:124)
at com.cfluent.pipelineengine.container.DefaultPipeline.execute(DefaultPipeline.java:97)
at com.cfluent.pipelineengine.container.DefaultPolicy$DeferredPipeline.execute(DefaultPolicy:63)
at com.cfluent.pipelineengine.container.DefaultPolicy$DeferredPipeline.access$300(DefaultPolicy:18)
<snipped>
Here's the snippet of code from the execute() method of the custom step:
SOAPMessage soapMsg = messageContext.getRequestMessage();
if ( soapMsg.getSOAPBody().hasFault()) // !!!!!!!!!!!!!!!!!!!!!!!! Here's where the error is occurring
When I log out soapMsg.getClass().getName() I get "org.apache.axis.Message".
Now, when I execute the same piece of code on another machine, it works fine and the class for SOAPMessage
is oracle.j2ee.ws.saaj.soap.soap12.Message12.
Any idea why the class difference? Is there some SOAPFactory configuration value somewhere?
Thanks in advance.

mrmora,
After opening a Service Request and communicating with one of Oracle's reps, I was told that the HttpServletRequest (and I guess other client info) is never available for either the Server Agent or Client Agent.
I created a Gateway, instead, and and I'm now getting the HttpServletRequest and the client's IP. Both of these codes now work:
HttpServletRequest request = (HttpServletRequest)messageContext.getProperty("javax.servlet.request");
String clientIP = httpSrvltRqst.getRemoteHost();
=====
String clientIP = ((MessageContext)messageContext).getRemoteAddr();
Thanks.

OWSM - XPath for Extract Credentials step problem.

Per the OWSM documentation, I'm trying to get the "Extract Credentials" step to work with XPath. Below are the parameters used straight out of the doc.
Credentials location (*): /soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/
Namespaces: soap=http://schemas.xmlsoap.org/soap/envelope,wsse=http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
UserID xpath:wsse:Username
Password xpath:wsse:Password
I keep getting in the gateway log that it can't find the username and password. I've checked for whitespace in the XPath and namespace statements. Anybody have any luck?
Thanks.

Has anyone got this working with both namespaces declared?
I'm using SOA suite 10.3.1.3.
I got it working by just using the WS-Security namespace and a global XPath:
Cred Location: //wsse:Security/wsse:UsernameToken/
Namespaces: wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
UserID: wsse:Username
Password: wsse:Password
It also works with the absolute Location, but omit the soap namespace declaration:
Cred Location: /soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/
Namespaces: wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
UserID: wsse:Username
Password: wsse:Password
As soon as I add soap to the namespace declaration, it starts failing. For instance:
Cred Location: /soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/
using
Namespaces: soap=http://schemas.xmlsoap.org/soap/envelope/, wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
UserID: wsse:Username
Password: wsse:Password
Result is "...SimpleXMLCredsExtractor failed to Extract creds"
Anyone else seeing this strange behavior?

OWSM EMPTY BPEL PROCESS VIRTUALIZATION PROBLEM!!!!!!!!!!

Hi,
I developed an EMPTY BPEL PROCESS which gets instantiated by a FILE ADAPTER . I am trying to virtualize the process by using OWSM GATEWAYS, but get error when i test it in the test page option unders tools link in OWSM MONITOR.
I am also not sure about the efficacy of using gateways to virtualize an EMPTY BPEL PROCESS.
CAN WE USE GATEWAYS TO VIRTUALIZE AN EMPTY BPEL PROCESS INITIATED BY A FILE ADAPTER???????
Regards,
Vishnu

Hi,
I developed an EMPTY BPEL PROCESS which gets instantiated by a FILE ADAPTER . I am trying to virtualize the process by using OWSM GATEWAYS, but get error when i test it in the test page option unders tools link in OWSM MONITOR.
I am also not sure about the efficacy of using gateways to virtualize an EMPTY BPEL PROCESS.
CAN WE USE GATEWAYS TO VIRTUALIZE AN EMPTY BPEL PROCESS INITIATED BY A FILE ADAPTER???????
Regards,
Vishnu

OWSM PrivilegedActionException Problem

Similar Messages

Maybe you are looking for