Externalize wsdl url from

Hello
Can we externalize wsdl url ( get wsdl url from property in runtime) from wsimport generated stub though changing server handle by changing location from property file.
Regards
Haroon Idrees

Yes, you can use WSDL generated from ICO. ICO simply represents combination of RD,ID and agreement objects.

Similar Messages

Development and access to external WSDL URL

Hi All,
I am developing a SOA application with BPEL composite which also makes calls to an external third party webservice. Due to security reasons, the external third party webservice URL is only accessible from our Development server machine (and not my local machine running JDeveloper). Issue with this is the SOA application development is done using Jdeveloper 11.1.1.4 on my local machine.
Overview of my application is
WebService (Synchronous Request/Response Client interface ) ---> BPEL ---> Third Party webService (Partnerlink)
1) Using the Client interface the user enters startTime and EndTime values
2) The startTime and endTime is input message to the BPEL process.
3) The BPEL process then sends the request to the third party web service (partnerlink) and gets a response message back and returns to the client.
I tried workaround for the same by asking the third party for WSDL and associated XSDs and included these locally in my SOA application project. However trying to deploy the completed SOA application and keep getting this error.
ERROR MESSAGE_
[03:40:25 PM] Error message from server:
There was an error deploying the composite on WLS_SOA: Error occurred during deployment of component: DataRetrievalService to service engine: implementation.bpel, for composite: DataRetrievalService: ORABPEL-09705
Could not initialize variable.
An error occurs while initializing BPEL variable RetrieveEventSummary_GetEventSummary_InputVariable; the schema processor cannot find the element {http://schemas.internet.com/asiapac/cad/integration/1.0.0}GetEventSummaryRequest in the following schemas: oracle.fabric.common.wsdl.SchemaManager@1cf57b6b.
The XSD element on which the variable was based was not properly defined in XSD or the WSDL.
Ensure that the element named in the error message is valid in the XSD or the WSDL.
Questions_
1) Please suggest, is it possible to develop a SOA application which makes service call to external URL, while the local development machine cannot access the external WSDL URL.
2) Also, in such cases in future deployments to test and production do I still need access to external WSDL URL from my machine. I deploy the completed SOA application from my local machine to the Development Server. The Development Server machine is configured to accessed the third-party WSDL URL.
Thanks
Edited by: user5108636 on 11/07/2011 23:53

It seems WSDL is not complete or invalid. Check whether it references element {http://schemas.internet.com/asiapac/cad/integration/1.0.0}GetEventSummaryRequest and this element has been defined in the XSD imported/defined in WSDL.
1) Please suggest, is it possible to develop a SOA application which makes service call to external URL, while the local development machine cannot access the external WSDL URL.Yes, it is possible but complete and valid WSDL must be available locally.
2) Also, in such cases in future deployments to test and production do I still need access to external WSDL URL from my machine. I deploy the completed SOA application from my local machine to the Development Server. The Development Server machine is configured to accessed the third-party WSDL URL.If server can access the third party WS URL then that is sufficient. No need to have access from local machine. Just deploy it on server and then test there.
Regards,
Anuj

Not able to read the wsdl file from server Premature EOF encounter

Hi All,
I am facing issue while accessing a web Service from server. Here is the clear view about it.
I created a simple SyncBpel process in a composite and deployed in to the server and it is working fine. Later i created a new Asyn bpel process in a composite and in the external reference i dragged a web Service and imported the wsdl url from server of the SyncBpel and wired the Asynbpel process to webserive .
Now here i am facing peculiar behavior which i am not able to trace it out.
1) For the first time when i import the url of syncBpel from the server i am not facing any error and it is working fine as expected but when i close the Jdeveloper and open it i am not able to user the web Service and it is saying as "Not able to read the wsdl file from server Premature EOF encounter"
2)When i close and open the Jdeveloper i can see the url of the wsdl which imported in webserver is changing from http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/bpelsync_client_ep?WSDL to http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/BPELsync.wsdl
3)when I open and see the url http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/bpelsync_client_ep?WSDL I can see the soap address as *<soap:address location="http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel!1.0*soa_5cfb8416-c106-40a2-a53b-9054bbe04b9c/bpelsync_client_ep"/>*
I don’t understand why the soap end contains “*soa_5cfb8416-c106-40a2-a53b-9054bbe04b9c” and this kind of url for soap address is coming to all the bpel process which I am deploying in the server.
I checked the in Jdeveloper where webproxy is uncheck and the server is also up but still I am facing issue of reading the error.
Can someone please help in resolving the issue.
I am using SOA 11g 11.1.1.5 and Jdeveloper 11.1.1.5
Many thanks.
Tarak
Edited by: user11896572 on Jan 17, 2012 5:22 PM

Hi,
Setting default from the jdeveloper -
During composite deployment from Jdeveloper (wizard driven), you will be given an option to choose the version of the composite and there will also be an option for you to choose if the composite needs to be deployed as default.
Setting default from the em console -
After deploying a composite, login to the em console and click on the composite that you want to set as default, and you will find a tab - "Set as Default". please note that this tab will not be seen, if the composite is already set as default.
Refer -
http://docs.oracle.com/cd/E12839_01/integration.1111/e10226/soacompapp_mang.htm
8.2 Managing the State of Deployed SOA Composite Applications
Thanks

How to generate wsdl url in Siebel 8.1

Dear Gurus,
Please help, how to generate wsdl url from inbound web services in Siebel 8.1
Regards,
Eldin

Hi Raj,
I've tried, this url did'nt recognize as a web service.
For example, in Oracle E-Business Suite ( Integration Repository ) there's a button to generate wsdl url. The wsdl url is http://servername/webservice/pls/test?WSDL.
So is it possible we generate wsdl url like in E-Business Suite ? Or there's something we need to configure so Siebel wsdl url will recognize as web service in E-Business Suite.
Thanks for your response.

WSDL url for sender and receiver SOAP adapter

Dear Experts,
I am working on SOAP --> SAP PI --> SAP ECC synchronous scenario. That means I have to create 2 Cc for SOAP i.e. Sender as well as Receiver adapter. I am responsible for creating the Request as well as Response structure in SAP PI. The sender application team is dependent on me to get the WSDL file.
Please provide the suggestions on the below.
Sender SOAP adapter.
1. I will create the WSDL from Sender Aggreement. How to get the url and what is the navigation step? Should I provide the    same url to sender application team to call the service.
Receiver SOAP adapter:
2. In the receiver SOAP adapter , Should I have to get the web service parameter of the sender application. As mentioned , I am creating the response structure as well. That means I can not import the WSDL from the sender application. How to get target url in the receiver SOAP Cc.
I refered to the forum SOAP SENDER - test in soapui but its not clear.
Regards
Alice Rebecca
Edited by: Alice@xi on Dec 20, 2011 5:48 PM

Dear Bhaskar,
For synchronous scenario
                                                            Request
MS Application (SOAP)<--> SAP-PI <--
> SAP ECC.
                                                                                Response
I am creating the Request as well as Response structure in SAP-PI and its agrreement for both
the ways.
So for the MS appl team, I will give the WSDL url from the sender agreement to make the request to SAP-ECC.
Now for receiving the response from SAP ECC, from where I should find the value to enter in the target url of SOAP
receiver channel.
1.Should I take the target url value from the MS Application team?
2.How to know whether the MS Application or SAP ECC is hosting the web service?
Regards
Alice

OSB WSDL invocation from java /jsp client!

Hi ,
I did a sample work on invoking osb wsdl(based on DB adapter) from a java/jsp application.It worked fine!
Its a simple select query wth parameter that was configured in my DB adapter.
Below are the steps I follow -
a.Created a DB adapter for collective response
b.created BS out of jca
c.Generated PS based on above BS.
d.Performed some xquery tranformation in PS message flow response piepeline.
e.Exported WSDL and tested it in SOAP UI ,getting the transformed response as required.
When we generate Java client out of above WSDL in Eclipse ,it generates client for DB data,transformed data fields are not seen -How to obtain transformed data too through Java client?will this work ?
Is it gud practice to generate java client directly n Eclipse (OEPE) or do we have any other alternative ways to generate Java client out of OSB WSDL?
Please assist.
Thanks,
Ani

Hi Anuj-
My proxy was generated out of business ,i get 2 wsdl like master-child .Master wsdl holds referecnce to child wsdl.I hope wsdl generation is fine.
When i invoke the proxy wsdl url from Java client ,i get below error -
Exception in thread "main" AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Invalid element in com.oracle.xmlns.pcbpel.adapter.db.PhysicalTampered_Meter.PhysicalTampered_MeterOutput - PhysicalTampered
faultActor:
faultNode:
faultDetail:
     {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Invalid element in com.oracle.xmlns.pcbpel.adapter.db.PhysicalTampered_Meter.PhysicalTampered_MeterOutput - PhysicalTampered
     at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
     at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
     at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
     at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
     at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
     at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
     at org.apache.axis.client.Call.invoke(Call.java:2467)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.oracle.xmlns.pcbpel.adapter.db.CoreAnalytics.PhysicalTampered_Meter.PhysicalTampered_Meter.PhysicalTampered_Meter_pttBindingStub.physicalTampered_Meter(PhysicalTampered_Meter_pttBindingStub.java:175)
     at Client.JavaClient.main(JavaClient.java:25)
     {http://xml.apache.org/axis/}hostname:B7B-3F-149-4HJV

Failed to read wsdl file from url

Hi all,
I am struggling with WL 9.2, consuming a WSRP enabled portlet at the following point:
Having created a proxy portlet, refering to the WSDL of the WSRP producer, I did successfully deploy the portal. When accessing the portal and consuming the portlet the following exception is thrown:
com.bea.wsrp.faults.TransportException: Failed to read wsdl file from url due to -- java.net.ConnectException: Tried all: '8' addresses, but could not connect over HTTP to server: 'www.w3.org', port: '80';
The WSDL includes a schema (http://www.w3.org/2001/XMLSchema). The URL is definetely accessible by the server.
I am open for any kind of support ;) Thanks in advance!
Kind regards,
Matthias

Yes, they are all local schemas. The way ALSB works, even if the import path in the wsdl or parent schema doesn't exist, relative to the current directory, you can specify which schema resolves that reference. My WSDL imports several schemas, all of which import others. When I was done importing all the schemas and resolving references, all the references in WSDLs and XSDs were assigned and valid. However, after all of those imports and reference resolution, it still says the WSDL is invalid, with the following odd error message:
The WSDL is not semantically valid: Failed to read wsdl file from url due to -- java.net.MalformedURLException: no protocol: /XMLSchema/PaymentServices/Resources/PaymentServices-200802.
That path listed refers to one of the schemas imported by the WSDL. The reference to that schema in the WSDL was resolved, and it doesn't complain about that reference.

Invoking a web service with the WSDL URL given at run time

I have created a very Simple Web Service using Netbeans 6.0 as an EJB Module. I have successfully created clients to access the web service, both through a Composite Application and through a simple Java Desktop Application, using the create "New Web Service Client" option, either by pointing to the EJB project either by providing the WSDL URL.
What I want now, is for the Java Desktop application to be able to consume the service after it has discovered the WSDL URL at runtime (e.g. through UDDI).
From what I have been able to find on the web, I should use the javax.xml.ws.Service class. But when I attempt to use the getPort method I get the exception:
"com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class mypackagename.jaxws.MyWebServiceName is not found. Have you run APT to generate them?"
Since I know that this class is not needed for the Web Service to be accessed, when the two procedures I describe above are used, I wonder what I can do to get this to work.
I have tried using apt from the command line but it can't find Java EE classes, so it doesn't work.
Nikos

Hi Yarecki,
I'm afraid I'm also a newbie, and I'm feeling my way around things.
I have written some code. However, you should be warned that... it doesn't work!
        String wsdlLocation;//=...some URL...
        String input;//=...XML...either SOAP message either SOAP payload
     try{
         java.net.URL wsdlURL = new java.net.URL(wsdlLocation);
            //these should be extracted from the service WSDL document
            java.lang.String serviceName = "CalculationServiceService";
            java.lang.String portName = "CalculationServicePort";
            String namespace = "http://localhost:8080/CalculationServiceService";
            javax.xml.transform.Source inputSource = new javax.xml.transform.stream.StreamSource(new java.io.StringReader(input));
            javax.xml.namespace.QName serviceQName = new javax.xml.namespace.QName(namespace, serviceName);
            javax.xml.namespace.QName portQName = new javax.xml.namespace.QName(namespace, portName);
            javax.xml.ws.Service service = javax.xml.ws.Service.create(wsdlURL, serviceQName);
            javax.xml.ws.Dispatch<javax.xml.transform.Source> dispatch =
                  service.createDispatch(portQName, javax.xml.transform.Source.class, javax.xml.ws.Service.Mode.MESSAGE);
       //javax.xml.ws.Dispatch<javax.xml.transform.Source> dispatch =
           //service.createDispatch(portQName, javax.xml.transform.Source.class, javax.xml.ws.Service.Mode.PAYLOAD);
//alternative method, with different input
            javax.xml.transform.Source replySource = dispatch.invoke(inputSource);
            javax.xml.bind.JAXBContext jc = javax.xml.bind.JAXBContext.newInstance(nikos.test.CalculationResult.class);
            javax.xml.bind.Unmarshaller unm = jc.createUnmarshaller();
            nikos.test.CalculationResult result = (nikos.test.CalculationResult)unm.unmarshal(replySource);
            System.out.println(result.getResult());
        } catch (JAXBException ex) {
            JOptionPane.showMessageDialog(this, ex);
            ex.printStackTrace();
        } catch (MalformedURLException ex) {
            ex.printStackTrace();//this should not happen.
        }In fact I'm getting a weird error
javax.xml.ws.soap.SOAPFaultException: java.lang.NullPointerException
        at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:187)
        at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:108)
        at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:187)
        at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
     //lines from my source code are here
Caused by: javax.xml.ws.WebServiceException: java.lang.NullPointerException
        at com.sun.enterprise.security.jmac.config.PipeHelper.makeFaultResponse(PipeHelper.java:328)
        at com.sun.enterprise.security.jmac.config.PipeHelper.getFaultResponse(PipeHelper.java:366)
        at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:223)
        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.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:113)
        at com.sun.enterprise.webservice.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
        at com.sun.enterprise.webservice.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:200)
        at com.sun.enterprise.webservice.EjbWebServiceServlet.service(EjbWebServiceServlet.java:129)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at com.sun.enterprise.web.AdHocContextValve.invoke(AdHocContextValve.java:114)
        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 com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:87)
        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:270)
        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:339)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
        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.NullPointerException
        at com.sun.xml.ws.tx.service.TxServerPipe.process(TxServerPipe.java:163)
        at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:218)
        ... 39 moreAs I've said before I've called this web service successfully using three different methods.
It appears it has something to do with security issues, but I've no security at all...

WSDL URL is invalid or the WSDL file is not valid or incorrect

Hi All,
I am using Oracle Soa Suite 11g. I have got Oracle database, Oracle weblogic admin server, Oracle SOA server all installed on my laptop.
I have deployed a sample BPEL process. When I am trying to test the process it is giving an error
"Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http://KSNPavan-PC:8001/soa-infra/services/default/MyHumanWorkFlowSample1Project/vacationrequestprocess_client_ep?WSDL", caused by: java.net.ConnectException. : java.net.ConnectException: Connection refused: connect "
Now, when I change the url address to
"http://localhost:8001/soa-infra/services/default/MyHumanWorkFlowSample1Project/vacationrequestprocess_client_ep?WSDL"
(Please note the difference in host name from KSNPavan-PC to localhost.)
and click parse wsdl it is working well. I mean the test page is opening successfully and I am able to test the service.
Testing the service from admin console is fine. Now I want to use this BPEL process service in another BPEL process. So, when I am piciking this service wsdl in JDeveloper it is throwing me the same error and I am unable to go ahead.
Can anyone please tell me whetherI have to set property in the admin server console so that it always take local host in all the wsdl urls and solve my problem.
Thank you,
KSN Pavan.

Hi All,
My problem has got solved with the help of my colleagues. Actually the problem was that the host name KSNPavan-PC is not there in the C:\Windows\System32\Drivers\etc\hosts file. I Added the host name in the file with the IP same as that of local host and everything isworking well now.
Thank you,
KSN Pavan

Either the WSDL URL is invalid or the WSDL file is not valid or incorrect.

Hi ,
i deployed one bpel process in weblogic.
when i am click on test below is error is coming. ( its on oracle soa 11)
below is coming for all the process. previously it is working fine.
Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://xxxx:8001/soa-infra/services/default/ReadJMS/readtraxjms_client_ep?WSDL: HTTP connection error code is 503
Please help me how it is resolved.
Regards
jan

Hi Jan,
We had the same issue in 11.1.1.3 and we used to restart the server to fix it. Hopefully before going to PROD we upgraded to 11.1.1.5 and next time we saw this issue was only when there was some problem with the OHS (it was down etc.).
Which version you're on?
Regards,
Neeraj Sehgal

How to get WSDL url for a webservice created in Oracle Apex

Can someone please help me in understanding the below:
I want to create a web service in Apex and invoke it from OBIEE.
I have created a web service in Apex but not sure what will be its WSDL url which I can provide in OBIEE action link.
Can some one please guide me here?

Hi,
You may export the HTML code for the Muse Site via the "Export as HTML" option under the File menu.
Hope it helps,
Sonam

How to find the WSDL URLs in NW CE 7.1 EhP1?

Hi,
I have upgraded my dev system from NW CE 7.1 SP5 to NW CE 7.1 EhP1. In this new version, the layout of the Web Service Navigator changed.
I used to use the old WS Navigator to find out the URLs where the WSDLs for services are available. I deployed my components (EJB projects with web services implemented by Enterprise Beans), located them in the WS Navigator and used the WSDLs there to generate Java clients to that services.
However, the new WS Navigator does not show the WSDL URL any more if you choose "Vendor System (Anwendersystem)" and then "Local AS Java (Lokaler AS Java)".
Any ideas where I can get the WSDL URLs? I have been searching the whole NW Administrator, but could not find that information.
Best regards,
Patrik
Edited by: Patrik Spiess on Feb 18, 2009 3:58 PM
Edited by: Patrik Spiess on Feb 18, 2009 3:59 PM

Patrik, you can also view the WSDL url in WS Navigator:
1 - In "Service Test" tab, choose your service, and follow all steps until to get the result of the service execution (step 4);
2 - In Step 4 (Result), click in "Add to Test Scenario";
3 - In "Test Scenario" tab, choose the test scenario of your service and click in "Change Services Access";
4 - Now, you can see the WSDL url in the popup.
Best regards,
Fabiano Rosa

Clear wsdl cache from java

hi ,
I am trying to clear wsdl cache from java , some errors are coming,
Please any one help me
this is my code
package bpeltest;
import com.oracle.bpel.client.BPELProcessId;
import java.util.Properties;
import com.oracle.bpel.client.IBPELDomainHandle;
import com.oracle.bpel.client.Locator;
import com.oracle.bpel.client.ServerException;
public class UnDeployBPELProcess {
public static void main(String[] args) throws ServerException {
UnDeployBPELProcess unDeployBPELProcess = new UnDeployBPELProcess();
//Properties with BPEL server connection information
Properties props = new Properties();
props.put("orabpel.platform", "ias_10g");
props.put("java.naming.factory.initial", "com.evermind.server.rmi.RMIInitialContextFactory");
props.put("java.naming.provider.url", "opmn:ormi://EC3-VEDARRA:6005:home");
props.put("java.naming.security.principal", "oc4jadmin");
props.put("java.naming.security.credentials", "oracle1");
props.put("dedicated.connection","true");
//Get a locator in default domain
Locator locator = new Locator("default","oracle1",props);
//Get a handle to the domain
IBPELDomainHandle iBPELDomainHandle = locator.lookupDomain();
iBPELDomainHandle.undeployProcess(new BPELProcessId("default","MyUndeployedBPELProcess"));
System.out.println("iBPELDomainHandle" + iBPELDomainHandle);
iBPELDomainHandle.clearWSDLCache();
compilation errors:
C:\jdevstudio10131\jdk\bin\javaw.exe -client -classpath C:\jdevstudio10131\jdev\mywork\javatest\BPELTest\classes;C:\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel.jar;C:\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel-common.jar;C:\product\10.1.3.1\OracleAS_1\j2ee\home\lib\oc4j-internal.jar;C:\product\10.1.3.1\OracleAS_1\opmn\lib\optic.jar;C:\jdevstudio10131\j2ee\home\lib\ejb.jar -Dhttp.proxyHost=157.204.22.4 -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=*.2o7.net|32.85.*|chipsndip|157.204.*|localhost|127.0.0.1|*.wlgore.com|EC3-VEDARRA|tigger -Dhttps.proxyHost=157.204.22.4 -Dhttps.proxyPort=8080 -Dhttps.nonProxyHosts=*.2o7.net|32.85.*|chipsndip|157.204.*|localhost|127.0.0.1|*.wlgore.com|EC3-VEDARRA|tigger bpeltest.UnDeployBPELProcess
Exception in thread "main" java.lang.Exception: Failed to create "ejb/collaxa/system/FinderBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/FinderBean not found
     at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:52)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.oracle.bpel.client.util.BeanRegistry.lookupFinderBean(BeanRegistry.java:337)
     at com.oracle.bpel.client.Locator.getFinder(Locator.java:920)
     at com.oracle.bpel.client.Locator.lookupDomain(Locator.java:228)
     at bpeltest.UnDeployBPELProcess.main(UnDeployBPELProcess.java:29)
     at com.oracle.bpel.client.util.ExceptionUtils.handleServerException(ExceptionUtils.java:82)
     at com.oracle.bpel.client.Locator.getFinder(Locator.java:926)
     at com.oracle.bpel.client.Locator.lookupDomain(Locator.java:228)
     at bpeltest.UnDeployBPELProcess.main(UnDeployBPELProcess.java:29)
Caused by: java.lang.Exception: Failed to create "ejb/collaxa/system/FinderBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/FinderBean not found
     at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:52)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.oracle.bpel.client.util.BeanRegistry.lookupFinderBean(BeanRegistry.java:337)
     at com.oracle.bpel.client.Locator.getFinder(Locator.java:920)
     at com.oracle.bpel.client.Locator.lookupDomain(Locator.java:228)
     at bpeltest.UnDeployBPELProcess.main(UnDeployBPELProcess.java:29)
     at com.oracle.bpel.client.util.BeanRegistry.lookupFinderBean(BeanRegistry.java:351)
     at com.oracle.bpel.client.Locator.getFinder(Locator.java:920)
     ... 2 more
Process exited with exit code 1.
and one more
where we find thiis value
"java.naming.factory.initial"= "com.evermind.server.rmi.RMIInitialContextFactory"
Regards
janardhan

I think there is error with this line in code
props.put("java.naming.provider.url", "opmn:ormi://EC3-VEDARRA:6005:home");
Please see the post for details
http://oraclebpelindepth.blogspot.com/2008/08/bpel-context-properties-for-client-api.html
The value should be
props.put("java.naming.provider.url", "opmn:ormi://EC3-VEDARRA:6005:home/orabpel");
Every Little Helps
Kalidass Mookkaiah
http://oraclebpelindepth.blogspot.com/

Use Service URL from OWSM Gateway in Service Registry

Hi,
Is there a scenario in which the Service URL from the OWSM gateway is used in the UDDI registry?
Eg:
WebService <--------> OWSM Gateway <----------> OSR (UDDI)
Any information on this is much appreciated
Regards

Hi Vikas,
Well..you don't registrate a gateway in uddi.
When you registrate a service in owsm, it will generate a new wsdl for you. This wsdl you just need to registrate in uddi just like any other service with wsdl-interface.
So the authentication fields aren't in uddi configered either...those are just a policy step in owsm. Overthere you can decide how to propegate the values of username/password etc

Why do I get parsing errors with my WSDL URL for Web Services usage

Hi,
I am puzzled with the errors I get when I want to create a Web Service datastore.
Scenario: I have created a SAP Web Service from CRM using SOAMANAGER. The WSDL URL produced by SOAMANAGER is accessibile when pasting the URL directly in Internet Explorer. WSDL URL [http://UXCIQ0M.WDF.SAP.CORP:50076/sap/bc/srt/wsdl/srvc_CBDCB34C89C29304E10000000A4282C0/wsdl11/allinone/ws_policy/document?sap-client=504]
When using the WSDL URL in the Web Service datastore URL field, I get the error An error occurred while importing metadata: WSDLException; faultcode=PARSER_ERROR: Problem parsing: The element type "br" must be terminated by matching tag "/br". (BODI-1111469) (BODI-1112446)
When I save the WSDL defintion in a local file and use a local file path, I get the errors An error occurred while importing metadata: WSDLException (at /wsdl:definitions/wsdl:portype/wsp:Policy): faultcode=INVALID_WSDL: Encountered unexpected element 'Policy. (BODI-1111469) (BODI-1112446)
My questions:
- Why do I get different parsing errors despite the fact that the XML is the same?
- The WSDL is generated by SOAMANAGER. Shouldn't it work directly when integrating with Web Services generated from an SAP environment?
- Is this related to confiurgation issue? I have set the Job Manager to Support adapter, message broker and SNMP communication
- What is the difference between the datastore of type Adapter and the datastore Web Service? In the white paper [http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20bd5e60-11f9-2b10-2bbb-b5109cceff08?quicklink=index&overridelayout=true] it is mentioned to use the Adapter type to consume a Web Service. It is not clear to me why we have those 2 types.
Thanks & Best Regards
Isabelle

Some updates on this issue, which might help others in the community.
- Data Service doesn't support ws_policy.
- SAP NetWeaver 7.0 SOAMANAGER generate WDSL with ws_policy. In future releases, it is possible to specify not to use ws_policy
- In most cases, replacing ws_policy with standard in the URL directly, works. It doesn't work with Data Services :(.
- Replacing ALL ws_policy in the XML directly is currently the only way to have the WSDL definition being parsed properly by Data Services.

Externalize wsdl url from

Similar Messages

Maybe you are looking for