Deployment with abstract wsdl

The deployment of a composite is failing with the following error:
There was an error deploying the composite on AdminServer: Deployment Failed: Unable to find a WSDL that has a definition for service {<namespace>}<ep> and <port>. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server
( I removed the service , ep and port values)
Only the wsdl it's referering to an abstract wsdl that is already in the project.
This is failing on my local server setup, I can deploy just fine on our development environment.
Anybody have any clue on why this error occurs in this situation?

Made a mistake , I was using the concrete WSDL, so I'm getting the error when deploying with a concrete wsdl.
This post says to use a abstract wsdl to solve this:
http://blog.ipnweb.com/2011/01/unable-to-find-wsdl-that-has-definition.html

Similar Messages

External Definition (wsdl) with abstract xsd element

Hello All,
we are trying to call a webservice, here is the wsdl:
https://www.1link.com/fr/demo-sn/site/gaiwebservice.asmx?WSDL
the problem is that the GAIJobLine element is defined as abstract:
<s:complexType name="GAIJobLine" abstract="true">
and there several elements which are extending GAIJobLine, for example:
<s:complexType name="GAITyreLine">
<s:complexContent mixed="false">
<s:extension base="tns:GAIJobLine">
So in our mapping we need to map to those element which are extending base element and not to the abstract one, but Graphical mapping displays only GAIJobLIne base element.
Does anybody know how we can map to extended elements without mannually changing wsdl?
Best Regards,
Artsiom Anichenka

thanks for your reply!
the extended elements are seen when I open wsdl in XMLSpy.
they are also visible in external definition object, but the main problem is that in the mapping only the base lement is displayed and there is no possobility to choose the extension.
Maybe this kind os XSDs (with abstract base types and extended elements) are just not supported by PI711?

What's wrong with my wsdl?

Hello,
I am struggling with a web service that won't deploy. My wsdl is valid: I checked it with Eclipse but the web service won't deploy. When I try to browse it I get an empty html table saying "Port Name Status Information".
Can anyone help?
Julien.
<?xml version="1.0" encoding="UTF-8"?>
<definitions
name="MonServiceWebUn"
targetNamespace="http://localhost:8080/jaxrpc-MonServiceWebUn"
xmlns:tns="http://localhost:8080/jaxrpc-MonServiceWebUn"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="passArgument">
<part name="pass" type="xsd:string"/>
</message>
<message name="GetResponse">
<part name="monMessage" type="xsd:string"/>
</message>
<portType name="monPort">
<operation name="maMethode">
     <input message="tns:passArgument"/>
     <output message="tns:GetResponse"/>
</operation>
</portType>
<binding name="monPortBinding" type="tns:monPort">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
      <operation name="maMethode">
      <input>
        <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://localhost:8080/jaxrpc-MonServiceWebUn"/>
      </input>
      <output>
        <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://localhost:8080/jaxrpc-MonServiceWebUn"/>
      </output>
    </operation>
</binding>
<service name="MonServiceWebUn">
<port name="monPort" binding="tns:monPortBinding">
    <soap:address location="http://localhost:8080/jaxrpc-MonServiceWebUn/MonServiceWebUn"/>
</port>
</service>
</definitions>

WSDL looks valid. Which version of JWSDP are you using ?
-Arun

Duplicate error for Abstract WSDL and Concrete WSDL

Hi,
I am trying to consume a webservice from ABCS Provider.
Here is what I have done:
1. Loaded target webservice wsdl into MDS by removing it's wsdl:service element.
2. Created a composite with a partnerlink referring to MDS wsdl.
3. Added binding.ws location (with concrete wsdl url) and port.
But when I compile I am getting an error, seems it is conflicting with MDS wsdl and concrete:
Error(73): query "/ns1:createComplaint/arg0/instrumentInstallDate" is invalid, because Global Type declaration/definition of name '{http://tempuri.org/}createComplaintResponse' are duplicated at the following locations:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [line#: 130]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [line#: 120]
There are at least two of them looking different:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [difference starting at line#:132]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [difference starting at line#:122]
Global Type declaration/definition of name '{http://tempuri.org/}createComplaint' are duplicated at the following locations:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [line#: 121]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [line#: 11]
There are at least two of them looking different:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [difference starting at line#:123]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [difference starting at line#:13]
Global Type declaration/definition of name '{http://tempuri.org/}updateComplaint' are duplicated at the following locations:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [line#: 136]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [line#: 134]
There are at least two of them looking different:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [difference starting at line#:138]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [difference starting at line#:136]
Global Type declaration/definition of name '{http://tempuri.org/}updateComplaintResponse' are duplicated at the following locations:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [line#: 145]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [line#: 143]
There are at least two of them looking different:
oramds:/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/wsdls/AgileComplaint_v1.wsdl [difference starting at line#:147]
http://172.25.86.11:8001/holxagileservice/AgileComplaintPort?xsd=1 [difference starting at line#:145]
Thanks
Sai

see :
http://blogs.oracle.com/aia/entry/aia_11g_best_practices_for_dec
http://docs.oracle.com/cd/E17904_01/doc.1111/e17364/bestpractices.htm#BABCGHEH
http://eai.ittoolbox.com/groups/technical-functional/tibco-l/abstractconcrete-wsdl-1091495
abstract wsdls can be used on designtime, so in that case the backend service don't have to be online to implement your process.
on runtime the concrete wsdl will be used to lookup for example the actual endpoint (service) and bindings

Should abstract wsdl services in oracle soa mds contain partner links ?

Consider the following scenario:
Service A has defined abstract definition and needs to be implemented as Mediator component. For this we deploy the abstract definition of Service A to MDS repository and create a mediator composite project which is also deployed to soa infra server.
Services B and C are consumer processes which are developed as separate composites and they are clients to Service A. If B and C are implemented as BPEL processes, JDeveloper creates Service_A_Wrapper wsdl file in each of the composite projects.
Is it preferable to add the partner link to the abstract definition wsdl of Service_A, since it only uses the definition of the port types only and the define the interfaces of the requester / callback dependency of two wsdl interfaces ?
Thanks
Edited by: pavle on 24-May-2012 05:24

You might want to post this question on the SOA integration forum
Applications Integration using Oracle Fusion Middleware
Thanks
JC

Web service deployment using generated wsdl

Hi,
As u know app server is generating the wsdl and mapping files in deployment time if you dont include these files in the archive.
What i m trying to do is to use the pregenerated wsdl and mapping file in the archieve, i don't want app server to generate wsdl and mapping. I'm generating these files in build phase and placing them under META-INF folder of resulting jar file.
And i expect oc4j to use these supplied files but it continues to generate and uses the generated.
(I'm using wsa.jar to generate wsdl, mean i'm generating in oracle way, not other tool)
(I dont want to use the auto generated wsdl cause i need to update them before deployment. Auto generated wsdl have data definition with object graphs which is not supported by document-literal message format. i will try to clean object graph dependencies in wsdl and deploy) Or shall i use Rpc-Encoded which supports object graphs??
Thanks...

it seems that it is hard to extract main question from the preview post. The question is that:
how can i deploy web service for a stateless session bean annotated with @webService annotations with supplied wsdl and mapping file in the ejb jar file...
(oc4j always generates a new wsdl,does;t use the one given in the jar)

Http post issue in soa suite 11g with 10g wsdl

I have 10g process that has http post wsdl as below. When I'm trying to create a project in 11g 11.1.1.4 with same wsdl, getting the following error at building the project. "Error(12,61): Parse of component type files failed, check the adf-config.xml file : "Error at line 34 char 64: Malformed WS Binding port. Missing # between namespace URI and service/port names."
I'm sure that http post mechanism is changed in 11g, but can you please help what exactly is wrong ?
<?xml version="1.0"?>
<definitions name="HTTPPostService"
targetNamespace="http://services.otn.com"
xmlns:tns="http://services.otn.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
          xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
          xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
>

<types>
<schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://services.otn.com"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="Postreq">
<complexType>
<sequence>
<element name="Order_Update_Request">
<complexType>
<sequence>
<element name="ORD_ID" type="string"/>
<element name="E_MAIL" type="string"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
<element name="Postresp">
<complexType>
<sequence>
<element name="Order_Update_Response">
<complexType>
<sequence>
<element name="RETURN_STATUS" type="string"/>
<element name="MESSAGE_TEXT" type="string"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
</types>

<message name="HTTPPostServiceRequestMessage">
<part name="payload" element="tns:Postreq"/>
</message>
<message name="HTTPPostServiceResponseMessage">
<part name="payload" element="tns:Postresp"/>
</message>


<portType name="HTTPPostService">
<operation name="IScript_Update_Order">
<input message="tns:HTTPPostServiceRequestMessage" />
<output message="tns:HTTPPostServiceResponseMessage"/>
</operation>
</portType>
<binding name="HTTPPost" type="tns:HTTPPostService">
<http:binding verb="POST"/>
<operation name="IScript_Update_Order">
<http:operation location="/PSIG/HttpConnector?From=PSFT_XINBOUND&MessageName=ABC_ORD_UPDORDER&MessageType=sync&MessageVersion=v1"/>
<input>
<mime:mimeXml part="payload"/>
<mime:content type="text/xml"/>
</input>
<output>
<mime:mimeXml part="payload"/>
          <mime:content type="text/xml"/>
</output>
</operation>
</binding>
<service name="HTTPPostService">
<port name="HTTPPost" binding="tns:HTTPPost">
<http:address location="http://myserver.mycompany.com"/>
</port>
</service>

<plnk:partnerLinkType name="HTTPPostService">
<plnk:role name="HTTPPostServiceProvider">
<plnk:portType name="tns:HTTPPostService"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>

Can you make sure your helloworld is using adf bindings as mentioned in thread Re: Urgent :: 11g Invoking Composite from Java/From Webservice Proxy

What's wrong with the wsdl

We are trying to create a proxy from the following wsdl file and getting an error message: illegal syntax: API:Parameter BINDING has initial value
The webservice that we are trying to consume is from TIBCO .
Can someone please help me to find out what's wrong with the wsdl.
<?xml version = "1.0" encoding = "UTF-8"?>

<wsdl:definitions name = "Untitled" targetNamespace = "http://xmlns.example.com/1268018884234/OperationImpl" xmlns:soap = "http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns = "http://xmlns.example.com/1268018884234/OperationImpl" xmlns:wsdl = "http://schemas.xmlsoap.org/wsdl/" xmlns:xs = "http://www.w3.org/2001/XMLSchema">
     <wsdl:types/>
     <wsdl:service name = "TIBCO__ABAP">
          <wsdl:port binding = "tns:SOAPEventSourceBinding" name = "SOAPEventSource">
               <soap:address location = "http://192.168.9.58:10001/TIBCO_ABAP"/>
          </wsdl:port>
     </wsdl:service>
     <wsdl:portType name = "PortType">
          <wsdl:operation name = "Operation">
               <wsdl:input message = "tns:Input"/>
               <wsdl:output message = "tns:Output"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name = "SOAPEventSourceBinding" type = "tns:PortType">
          <soap:binding style = "document" transport = "http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name = "Operation">
               <soap:operation soapAction = "http://192.168.9.58:10001/TIBCO_ABAP" style = "document"/>
               <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
               <wsdl:output>
        <soap:body use="literal" />
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:message name = "Input">
          <wsdl:part name = "Param1" type = "xs:int"/>
          <wsdl:part name = "Param2" type = "xs:int"/>
     </wsdl:message>
     <wsdl:message name = "Output">
          <wsdl:part name = "Result" type = "xs:int"/>
     </wsdl:message>
</wsdl:definitions>

Léon Hoeneveld's response works for me. You will need to download a tool that allows you to edit the WSDL and reorder the values.
I've used a freeware tool like notepad++ collapsed all the levels and opened up the <wsdl:definitions xmlns:wsdl... segment and reordered the subgroups beneath it accordingly.
1. types
2. message
3. portType
4. binding
5. service
Thanks again Léon!

Java DC not deployed with WebDynPro DC

Hi,
I've been testing the DC functionality and I'm trying to create the following:
1) WebDynPro DC (DCA)
2) Java DC (DCB)
DCB has code for reading data from a database table (three classes, one is set as a public part). This code is functioning ok in another WebDynpro project where I've used it as an external jar file located in the lib directory and added to classpath.
DCA has a small table in the view that I'm filling (or trying to) with data from the database.
DCB has one java class as a Public Part. DCA has this PP defined in the Used DC's (DC Metadata --> DC definition --> Used DC's). I can see the DCB code fine from the DCA's view (I can use the methods from the class).
I see no code errors and everything compiles ok. I've built the DCA and DCB separately (Development Component --> Build) before doing the project build and deployment.
When I deploy, I'm getting java.lang.NoClassDefFoundError for the DCB class (User.class) when the program starts. So it seems that the DCB is not deployed with the DCA. I've tried to look at the properties and java classpath but nothing I've done has helped.
Purpose is set to compilation, and there is a
<at-build-time/>
tag in the .dcdef file.
Deployment of normal (no DC) Webdynpro projects works fine and the jars in the lib directory are deployed to the server OK.
Seems like I've tried everything but have found no solution yet. Refreshed every part, re-created everything, re-built, re-deployed etc...
Shortly: how to get DCB to deploy ?
Any help is appreciated here
Kind Regards,
Jari Pakarinen

Hi,
What is the Java DC for then ? If it cannot be used as a part of another DC (deployable unit) then how should it be used ? What is the use if it does not end up at the server with Webdynpro code ?
The scenario I'm looking for is to include Java classes in a Webdynpro project as a part of the project (not jars done somewhere else, I can do that already) deployed to the server with the Webdynpro.
Thank you for your help, I'm not blaming you or anything
Regards,
Jari

How to use MDS deploying with EAR file

Hi everybody.
I would to use MDS in my web application in order to use customization across the sessions. I've performed every step to do this on JDeveloper (11.1.1.3.1). I've tested my application deploying directly from JDeveloper using Application menu > Deploy > "myApp" to "myApplicationServer" (in this way I can choose the repository with a window like this: http://i.stack.imgur.com/Kci9c.png). The repository was prevoiusly registered on the server. In this way my application works fine and they all lived happily ever after.
My problem occurs when I perform the deployment with "myApp to EAR" mode. When I try to install my EAR file in weblogic, it reply me with this error message:
An error occurred during activation of changes, please see the log for details.
+:oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.+
I've looked for a solution around the web (included this forum) and I think that I should modify something in adf-config.xml file (below).
Which steps I have to perform in order to install my application correctly with an EAR file?
Thanks in advance.
<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config"
xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
xmlns:sec="http://xmlns.oracle.com/adf/security/config"
xmlns:ads="http://xmlns.oracle.com/adf/activedata/config">
<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
<adf-property name="adfAppUID" value="BDO_GC_WEBAPP.bdogc"/>
</adf:adf-properties-child>

<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
<sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
authorizationEnforce="true"
authenticationRequire="true"/>
</sec:adf-security-child>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
<persistent-change-manager>
<persistent-change-manager-class>
oracle.adf.view.rich.change.MDSDocumentChangeManager
</persistent-change-manager-class>
</persistent-change-manager>
<taglib-config>
<taglib uri="http://xmlns.oracle.com/adf/faces/rich">
<tag name="column">
<attribute name="displayIndex">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="frozen">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="noWrap">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="selected">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="visible">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="width">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
<tag name="table">
<attribute name="filterVisible">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
</taglib>
</taglib-config>
</adf-faces-config>
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
<cust-config>
<match path="/">
<customization-class name="oracle.adf.share.config.UserCC"/>
</match>
</cust-config>
</mds-config>
</adf-mds-config>
</adf-config>

Any suggestion?

Proxy Generation Problem with Separate WSDL

Hi,
I'm trying to create Proxy with seperate WSDL, then i'm getting error. It is a simple Hello world BPEL and OSB.
Here is my WSDL
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="http://www.uk.gov.hmrc.chiefste.org/hello"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.uk.gov.hmrc.chiefste.org/hello"
xmlns:imp1="http://xmlns.oracle.com/HelloWorld"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/">
<types>
<xsd:schema targetNamespace="http://www.uk.gov.hmrc.chiefste.org/hello/types"
elementFormDefault="qualified">
<xsd:import schemaLocation="Hello.xsd"
namespace="http://xmlns.oracle.com/HelloWorld" id="hello.xsd"/>
</xsd:schema>
</types>
<message name="helloRequest">
<part name="inputParam" element="imp1:process"/>
</message>
<message name="helloResponse">
<part name="outputParam" element="imp1:processResponse"/>
</message>
<portType name="HelloService">
<operation name="sayHello">
<input message="tns:helloRequest"/>
<output message="tns:helloResponse"/>
</operation>
</portType>
<binding name="HelloServicePortBinding"
type="tns:HelloService">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation style="document"
soapAction="http://www.uk.gov.hmrc.chiefste.org/common/sayHello"/>
<input>
<soap:body use="literal" parts="inputParam"/>
</input>
<output>
<soap:body use="literal" parts="outputParam"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloServicePort"
binding="tns:HelloServicePortBinding">
<soap12:address location="temp"/>
</port>
</service>
</definitions>
And here is my xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
          elementFormDefault="qualified"
          targetNamespace="http://xmlns.oracle.com/HelloWorld"
          xmlns="http://www.w3.org/2001/XMLSchema">
     <element name="process">
          <complexType>
               <sequence>
                    <element name="input" type="string"/>
               </sequence>
          </complexType>
     </element>
     <element name="processResponse">
          <complexType>
               <sequence>
                    <element name="result" type="string"/>
               </sequence>
          </complexType>
     </element>
</schema>
This is the WSDL i used to create a proxy service.
And this is the WSDL i used to generate Business Service (Which i got from my BPEL)
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions name="HelloWorld" targetNamespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:documentation>
<abstractWSDL>http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB!1.0/HelloWorld.wsdl</abstractWSDL>
</wsdl:documentation>
- <plnk:partnerLinkType name="HelloWorld">
- <plnk:role name="HelloWorldProvider">
<plnk:portType name="client:HelloWorld" />
</plnk:role>
</plnk:partnerLinkType>
- <wsdl:types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" schemaLocation="http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB/helloworld_client_ep?XSD=xsd/HelloWorld.xsd" />
</schema>
</wsdl:types>
- <wsdl:message name="HelloWorldRequestMessage">
<wsdl:part name="payload" element="client:process" />
</wsdl:message>
- <wsdl:message name="HelloWorldResponseMessage">
<wsdl:part name="payload" element="client:processResponse" />
</wsdl:message>
- <wsdl:portType name="HelloWorld">
- <wsdl:operation name="process">
<wsdl:input message="client:HelloWorldRequestMessage" />
<wsdl:output message="client:HelloWorldResponseMessage" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="HelloWorldBinding" type="client:HelloWorld">
<soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="process">
<soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" soapAction="process" />
- <wsdl:input>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" />
</wsdl:input>
- <wsdl:output>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="helloworld_client_ep">
- <wsdl:port name="HelloWorld_pt" binding="client:HelloWorldBinding">
<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB/helloworld_client_ep" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thx,
Rahul

Yes, U r rite. It takes input like that in SoapUI.
And in OSB Console it takes like below:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<hel:process xmlns:hel="*http://xmlns.oracle.com/HelloWorld*">
<hel:input>?</hel:input>
</hel:process>
And this is my Input for Business Service in OSB Console:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<hel:process xmlns:hel="*http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld*">
<hel:input>?</hel:input>
</hel:process>
Note: And if i use the Bolded namespace of Business Service in Proxy,, it is working.
This is my Request XQuery:
(:: pragma bea:global-element-parameter parameter="$process1" element="ns1:process" location="../Proxy/wsdl/Hello.xsd" ::)
(:: pragma bea:global-element-return element="ns0:process" location="../Business/wsdl/XMLSchema_1137514867.xsd" ::)
declare namespace ns1 = "http://xmlns.oracle.com/HelloWorld";
declare namespace ns0 = "http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld";
declare namespace xf = "http://tempuri.org/Hello/xquery/dsha/";
declare function xf:dsha($process1 as element(ns1:process))
as element(ns0:process) {
<ns0:process>
<ns0:input>{ data($process1/ns1:input) }</ns0:input>
</ns0:process>
declare variable $process1 as element(ns1:process) external;
xf:dsha($process1)
Response XQuery:
(:: pragma bea:global-element-parameter parameter="$processResponse1" element="ns0:processResponse" location="../Business/wsdl/XMLSchema_1137514867.xsd" ::)
(:: pragma bea:global-element-return element="ns1:processResponse" location="../Proxy/wsdl/Hello.xsd" ::)
declare namespace ns1 = "http://xmlns.oracle.com/HelloWorld";
declare namespace ns0 = "http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld";
declare namespace xf = "http://tempuri.org/Hello/xquery/resp/";
declare function xf:resp($processResponse1 as element(ns0:processResponse))
as element(ns1:processResponse) {
<ns1:processResponse>
<ns1:result>{ data($processResponse1/ns0:result) }</ns1:result>
</ns1:processResponse>
declare variable $processResponse1 as element(ns0:processResponse) external;
xf:resp($processResponse1)
Thx,
Rahul

EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

Hi All ,
           I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
1 . 3 EJB3.0 session DCs
2. 1 JPA DC
I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
--- Deploying file(s):
     D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
--- Status:
     Deploy finished with warnings.
--- Description:
            S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed:           0
Deployed with warnings:           1
Failed deployments:                0
~~~~~~~~~~~~~~~~~~~
1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
     Name:erecapp
     Vendor:asianpaints.com
     Location:J2N_ERECTT_D
     Version:20090217100038
     Deploy status:Warning
     Version:HIGHER
     Description:
          1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
     at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
     at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:Warning

You have to give an explicit data source in your persistence.xml to solve this error normaly.
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
     <persistence-unit name="YOUR_UNIT">
    <jta-data-source>DSNAME</jta-data-source>
Frank

SCCM: Application deployment vs Package deployment with requirements and prerequisits.

Hey,
My organization is in the process of implementing a new remote networking solution for all employees, however some employees require additional software vs others. What I am trying to find out is if there is a way to have one package with supersedes and
requirements that we can use to do a massive deployement.
Here are the different scenarios with order of installation:
Financial group Desktop:
1.Install New solution
2.Install Configuration
3.Install Token Authentication
(nothing crazy)
Financial Group Laptops
1.Install Token Authentication
2.Install New Solution
3.Install COnfiguration
4.Un-uninstall Old Solution
5.Un-install Tunnel Guard application (requires a reboot, that's why it's last). (this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 5, but do 4, when 4 is triggered, it does 3 first, etc...)
All other laptops
1.Install New Solution
2.Install COnfiguration
3.Un-uninstall Old Solution
4.Un-install Tunnel Guard application (requires a reboot, that's why it's last).(this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 4, but do 3, when 3 is triggered, it does 2 first, etc...)
Because of the different requirements, is there a way to have one deployment with multiple deployment types to say based off:
1. Computer types (we have a naming convention that identifies laptops and desktops.
2. Only install certain pieces of software (Token validator in this case if financial application is detected on the machine).
Or should I create different applications for each case with different collections or go with 3 different packages and collections with install this package first set in the package deployment
Thanks for your help.

The problem is the last uninstall, because it's not applicable to all machines. That means that if you would deploy that with all it's dependencies, it wouldn't do anything on the desktops as it's not applicable to them.
In this case, if you want to use one deployment, the easiest solution is a task sequence. That way you can target everything in one time and still build some logic to prevent some (un-)installs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Patch deployment with status "Enforcement state unknown"

Hi All
I am pretty new to the patch deployment.
I generated a report and see there is Last State column with "Enforcement state unknown", not sure if it means failed for those hostnames or will be retried for the installation.
Kindly clarify.
Regards
Ramesh
Regards Ram

They will only start to install updates automatically when there is an active update deployment with a scheduled deadline that has past. See for a lot more information:
http://technet.microsoft.com/en-us/library/gg682168.aspx#BKMK_SUMCompliance
Also, when Days since last communication is more than 0, that's usually an indication that the client is not communicating any more. That can be caused by a lot of things including something simple as that the device is turned of, or not
connected with the network.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Deployable Proxy with two wsdl files

Hello,
I have a problem with deployable proxies and two wsdl files.
In wsdl A returns a method an object of type Foo.
In wsdl B a method expects a parameter of type Foo.
Foo is a class of the Web service provider.
I created a new deployable proxy called p.
For both wsdl files I chose Create -> new client proxy definiton and for both of them I had to create a new package (a and b).
Now I have two Foo classes:
p.a.types.Foo and p.b.types.Foo
But I would like to have only one Foo class and use it for both proxy definitions.
Is this possible?
Thanks and regards
Patrick

Hi,
no I haven't found a solution.
> I was looking for options to create single proxy with multiple wsdl files
I was thinking the same because the folder is called WSDL Files.
Hope somebody could help.
Regards
Patrick

Deployment with abstract wsdl

Similar Messages

Maybe you are looking for