WSDL Files in the Solution Composer

Hi Guys!
I am trying to use the WSDL Files for a Enterprise Service Operation from the Solution Composer, but I am always requiered to enter an account and password to get the file.
Where can I get the authorization to use these WSDL files and how?
I will really appreciate any hint!

Hi Edgardo,
If you go to the ESA Preview System Page https://www.sdn.sap.com/sdn/esapreview.sdn?node=linkDnode12-2 you will notice that there is a form to request participation in the ESA Preview System access. Only those Partners and Employees defining a very valid business case for building and testing client applications that consume enterprise services will be accepted to this "limited" capacity program.
At a later date, these WSDL files will be more widely available. For the time being only those accepted as part of this preview system program will have access.
cheers,
Marilyn

Similar Messages

Error occurred in deployment step 'Add Solution': Failed to extract the cab file in the solution.

I have received the follwoing error when I depoly the custom masterpage with css, images, javascript files:
Error occurred in deployment step 'Add Solution': Failed to extract the cab file in the solution.
Any help will soon is appreciated.

Hi Bagalur,
Thanks for your sharing. It will help others who stuck will the same issue.
Best Regards
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jerry Guo
TechNet Community Support

Error occured in deployment step "retract solution".Failed to extract the cab file in the solution.

Hi,
I'm a sharepoint newbie.I'm getting this error (Error occured in deployment step "retract solution".Failed to extract the cab file in the solution. ) when i try to deploy the solution through visual studio 2012.I did some research and tried
the following ways but nothing helped me.
Checked all the file names for any special characters but could not find one.
Recycled the application pool--no use
Checked the wsp file--it doesnt have any duplicate files.
If anyone can help me with this ,it would be great.Spent one whole day to fix this but couldn't achieve anything.
Thanks !

Hi,
Any update?
I suggest you provide some screenshots or your project structure for further research.
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Issue while importing the WSDL file in the External Definitions - PI 7.0

Dear all Experts
After importing the WSDL file in the external External Definitions we are not able to view the " name and namespace " in the messages tab.
Request you to advise on the issue.
We are using the PI 7.0
Regards
Machindra Patade

Dear All
Got the answer"
The problem is in the namespace description LENGTH,
Note the following restrictions for XI or PI installations:
· Maximum length of repository namespaces and XML namespaces: 60 Characters. Due to this restriction, the import of XSD files and WSDL files prepares difficulties as an external definition; you can solve these difficulties using Note 901988.
· Maximum length of object names in the Integration Repository and Integration Directory: 120 characters
As of SAP NetWeaver Process Integration 7.10 Support Package 7, the enhancement of the maximum length of namespaces to 255 is supported in the configuration and runtime.
Please check the below SAP 2 notes in regards to above mail.
SAP Note 901988 - Integration Builder: Namespace of external definitions
SAP Note 870809 - Integration Builder: Length of namespaces and object names

When i add a background image to form and it gives me such kind of issues so i have deleted the resource file in the solution explorer and then when i reopened my projectt it again gives errors of missing root element of InvalidResx.file amd of XMl.

I have already go to properties then resources and try to remove resource option but it was't working.so help me by giving another technique to solve this issue.

I have already go to properties then resources and try to remove resource option but it was't working.so help me by giving another technique to solve this issue.
Hello,
It will be more specific if you could share the screenshot of that error with us.
In addition, if this issue is mainly related to the BackGroundimage property, you could consider using the following suggestion.
We could click our project to expand the nodes and click "InitializeComponent()" to navigate to its desiginer code.
Then check whether there is a line which has " Me.BackgroundImage =", remove that line and then remove the resource file with the following step.
Project property->Resources->Switch "Files" or "Images" to see where you have setted for that image file, find it and remove it.
Then save all your changes to see whether it's OK.
Regards,
Carl
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

MSBUILD - Using MSBUILD I would like to add files into the solution AFTER BUILD process.

Hi,I have the requirement to add files into the project after project has been build. I wish to add some javascript and css files into the project at the PRE BUILD or POST BUILD time. I specified <Content Include="path\filename"/> in
the AFTERBUILD Target element. But it seems not including the files.
Regards,
Senthil

Hello Senthil Kumar T D,
In msbuild files are include/exclude in ItemGroup like the following MSDN article mentioned:
How to: Select the Files to Build
How to: Exclude Files from the Build
So here you need to consider put them in the ItemGroup and use your files in your target.
And if you want to MSBuild and including extra files from multiple builds - See more at:
http://blog.samstephens.co.nz/2010-10-18/msbuild-including-extra-files-multiple-builds/#sthash.G5SdxGag.dpuf
This can be used for multiple builds. Anyway, please follow the first two sample I mentioned to reset your project file.
Best Regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Can't see my header file in the Solution Explorer?

Hi,
I am new to VS and I am working on a school team project where we use a git repository and when I created a header file I commit it, see it in the folder where I have it stored on my system and on github, but I don't see it in my Solution
Explorer in VS. I have used the properties->VC++->include directories and set the path but I still don't see it?
Any ideas is much appreciated!
Thanks

Hi pvdg42,
That's a great question. I have opened an .sln file because when I try to open a source control project I don't see the .vcxproj file and when I go into the git folder to open the .vcxproject a blank VS window opens. There is another file .vcxproj and when
I try to open that one it says modifying this may damage your system.

How to get the wsdl file

hi all,
here java people have given wsdl file to me, how to do the scenario,
and how to get the wsdl file from the java people.
regards,
priya

Hello Priya,
Go to http://<hostname>:50000/wsnavigator or any other UDDI server and search for the web service to be invoked
There you can find the Webservice Definition (WSDL) file.
Check this weblog:
Invoke Webservices using SAPXI
regards
Gangaprasad

Facing while consuming the Echo WSDL file

Hi,
I have requirement to consume a WSDL file from the Echo web service.
I have created an Enterprise service for consuming the WSDL file. Even created a logical Port in SOAMANAGER for the same.
Finally I wrote a program as mentioned below:
DATA : input TYPE ZFREIGHTget_QUOTE_SOAP_IN,
        output TYPE ZFREIGHTget_QUOTE_SOAP_out.
DATA : io_clientproxy TYPE REF TO zfreightco_quote_soap.
*-- variables for text processing
DATA : output_string TYPE ZFREIGHTRATE_QUOTE_TAB,
       ystring type ZFREIGHTRATE_QUOTE.
data: it_ZFREIGHTREQUEST type table of ZFREIGHTREQUEST,
      ls_ZFREIGHTREQUEST type ZFREIGHTREQUEST.
*-- variables for xslt parsing error
DATA : xslt_err TYPE REF TO cx_xslt_exception .
*-- create web service proxy class instance
TRY.
    CREATE OBJECT io_clientproxy
      EXPORTING
        logical_port_name = 'ZFREIGHT_LOGICAL_PORT'.
CATCH cx_ai_system_fault.
ENDTRY.
ls_ZFREIGHTREQUEST-ORIGIN-zip = '33607'.
ls_ZFREIGHTREQUEST-DESTINATION-zip = '33647'.
ls_ZFREIGHTREQUEST-TOTAL_WEIGHT = '1000'.
append ls_ZFREIGHTREQUEST to it_ZFREIGHTREQUEST.
move it_ZFREIGHTREQUEST[] to INPUT-ECHO_RATE_REQUEST-REQUESTS-REQUEST.
*-- call web service methods
TRY.
    CALL METHOD io_clientproxy->GET_QUOTE
      EXPORTING
        input = input
      IMPORTING
        output = output.
CATCH cx_ai_system_fault.
CATCH cx_ai_application_fault.
ENDTRY.
When i execute the program, the exception "cx_ai_system_fault" is raised.
Could someone suggest me, where I am going wrong.
Thanks,
Deepika

Hi Deepika,
You need to know the reason of the exception. Try debugging when the exception is raised or catch the message of the exception.
DATA:
oref TYPE REF TO cx_root,
text TYPE string.
TRY.
CATCH cx_<exception> INTO oref.
    text = oref->get_text( ).
ENDTRY.
Regards,
Isaac Meléndez

Wsdl file location in the apps r12 (service created by using the jdevloper)

Hi,
this is issue is related to apps R12.
I want to edit the WSDL file of the smsservice devloped through JDevloper.
as it is working fine in Prod and I want to test it in test envirnment to how from where I will get wsdl file of the service so that I can change the url of the test in the wsdl file.
Please suggest.
harry

Any suggestions. I also would like to knoe the location of wsdl file.

Solution Composer v/s Visual Composer

I was wondering if Solution Composer is the appropriate tool to perform AS-IS business process mapping of a system. Is Visual Composer a better alternative?
If I edit and customize a solution in the Solution Composer, will it port to Solution Manager?

Kevin,
The answer depends on what you are trying to accomplish, also you should understand that there is a key difference between the two tool sets you mention.
Solution Composer is a high level representation of SAP capability across the different processes and industries. Since it is customisable, it is useful for showing at a high level a map between SAP enabled scenarios and a given current business model. Visual Composer is a tool that can do two things, 1) Create simple composite applications running on NW 7.0 portal as iViews : 2) Used as a reporting tool in the same scenario as option 1.
If you are trying to do an AS-IS of an existing SAP system and do not have a documented Business Blueprint linked to a Business Process Hierarchy in Solution Manager then the answer may be yes, you could possbily use Solution Composer.
However if this was more of a normal AS-IS situation covering business processes on non SAP enabled systems you may be better off doing the AS-IS using a tool such as ARIS (or other modelling tools such as Casewise or Livemodel). Even Visio used in a structured way combined with a generic Business Process Procedure document (in word format) would work. This depends on wether your organisation has a formal approach to Business Process Management.
By the way, you can save Solution Composer models as HTML files, these could then be uploaded and stored within a BPH template on Solution Manager at either Scenario or Process level.

SAP Solution Composer

Hello,
I'm trying to download the SAP Solution Composer. After I hit the SUBMIT I get the same page where I fill out name, e-mail etc. So no file download! Any tips, how to download the Solution Composer? I understood this is a PC based tool.
Regards,
Lucas

Hi,
I'm not quite sure but here are some suggestions:
- is JavaScript turned on?
- try with a different browser
- check security settings of your browser, what happens when hitting SUBMIT is that you can download an install file named smc_public.exe which has to be executed to download Solution Composer. This was actually my problem when I installed Solution Composer the first time.

?WSDL for Business Service or WSDL File

I know that you can append a ?WSDL to the end of a Proxy Service to access the WSDL File for the Service.
Is there a REST/GET way to do the same thing to access a Business Service or a WSDL or a Schema directly?
Thanks,
Jay

See if this might help.
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/configuringandusingservices.htm#i1143285Is
Thanks
Manoj

Web Service WSDL File Generation

hello everybody, I have an outbound interface with sender soap adapter to work as a web service, I tested it by generating the wsdl file in the integration directory, and I tested it with altova xmlspy and it works really fine, but now I have a problem another aplication needs to call the webservice, but when they try to import the wsdl file it turns out that in their system they can only import rpc files and not document style files, is there a way to generate a RPC file from an xi interface, or is there a third tool to do this conversion, or what needs to be done, has anyone found this problem before??? thanks in advance.
Regards,
Julio Cesar

Hi ,
As far as I am aware of ...
3 SOAP encoding styles are there :
SOAP Remote Procedure Call (RPC) encoding, also known as Section 5 encoding, as defined by the SOAP 1.1 specification and later defined in SOAP 1.2 as RPC encodings and conventions
SOAP Remote Procedure Call Literal encoding (SOAP RPC-literal,) uses RPC methods to make the call but uses an XML do-it-yourself method for mar-shaling the data.
SOAP document-style encoding, also known as message-style or document-literal encoding.
Kindly Check this Link out
http://msdn.microsoft.com/msdnmag/issues/03/05/XMLFiles/

Xsl schema import from within a wsdl file

I have a namespace conflict issue validating a bpel process.
The message error is as follow:
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
// Here the BPEL file (SMSMulticast2.bpel)
<pre>

<process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
     
     
     
     
     <partnerLinks>
          
          <partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
          <partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
          <partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
     </partnerLinks>
     
     
     
     
     <variables>
          
          <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
          
          <variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
          <variable name="count" type="xsd:integer"/>
          <variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
          <variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
          <variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
          <variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
     </variables>
     
     
     
     
     
     <sequence name="main">
          
          <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
          
          <assign name="setProperties">
               <copy>
                    <from expression="5"></from>
                    <to variable="count"/>
               </copy>
               <copy>
                    <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
                    <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
               </copy>
               <copy>
                    <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
                    <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
               </copy>
          </assign>
          <while name="foreach" condition="bpws:getVariableData('count') > 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
                    <assign name="decrease"><copy>
                              <from expression="bpws:getVariableData('count') - 1"></from>
                              <to variable="count"/>
                         </copy>
                    </assign>
               </sequence>
          </while>
          
          <reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
     </sequence>
</process>
// Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
     name="SMSSenderEnablerSEI"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
     xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
     xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
     <xsd:schema
          elementFormDefault="qualified"
          targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
          xmlns="http://www.w3.org/2001/XMLSchema"
          xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
          <xsd:complexType name="InvocationContext">
          <xsd:sequence>
          <xsd:element
          maxOccurs="unbounded"
          name="properties"
          nillable="true"
          type="xsd:string"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:complexType name="EnablerException">
          <xsd:sequence>
          <xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
          <xsd:element name="errorCode" type="xsd:int"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
          </xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
<xsd:element name="sendSMS">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotification">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="sendSMSWithNotificationToAliasReturn"
nillable="true"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
               <xsd:complexType name="SMSMessageETO">
<xsd:sequence>
<xsd:element name="content" nillable="true" type="xsd:string"/>
<xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
<xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
<xsd:element name="priority" nillable="true" type="xsd:string"/>
<xsd:element name="recipient" nillable="true" type="xsd:string"/>
<xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
<xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
<xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
<xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<xsd:complexType name="SMSException">
<xsd:sequence>
<xsd:element name="errorCode" type="xsd:int"/>
<xsd:element name="message" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="sendSMSRequest">
<wsdl:part element="impl:sendSMS" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasResponse">
<wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnablerException">
<wsdl:part element="tns2:EnablerException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasRequest">
<wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasRequest">
<wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasResponse">
<wsdl:part
element="impl:sendSMSWithNotificationToAliasResponse"
name="parameters"/>
</wsdl:message>
<wsdl:message name="SMSException">
<wsdl:part element="tns4:SMSException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationResponse">
<wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationRequest">
<wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSResponse">
<wsdl:part element="impl:sendSMSResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="SMSSenderEnablerRemote">
<wsdl:operation name="sendSMS">
<wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
<wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdl:input
message="impl:sendSMSWithNotificationRequest"
name="sendSMSWithNotificationRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationResponse"
name="sendSMSWithNotificationResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
<wsdl:output
message="impl:sendSMSToAliasResponse"
name="sendSMSToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdl:input
message="impl:sendSMSWithNotificationToAliasRequest"
name="sendSMSWithNotificationToAliasRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationToAliasResponse"
name="sendSMSWithNotificationToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding
name="SMSSenderEnablerRemoteSoapBinding"
type="impl:SMSSenderEnablerRemote">
<wsdlsoap:binding
style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendSMS">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SMSSenderEnablerRemoteService">
<wsdl:port
binding="impl:SMSSenderEnablerRemoteSoapBinding"
name="SMSSenderEnablerRemote">
<wsdlsoap:address
location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
<plnk:role name="SMSSenderEnablerRemoteProvider">
<plnk:portType name="impl:SMSSenderEnablerRemote"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
Many Thanks
Guillaume

You need to use the XSLT before you do assignment to achieve this, to
change the message to the correct namespace.
Please refer to sample at
"orabpel\samples\tutorials\114.XSLTTransformations" which talks about
how to use XSLT transformation.
And please refer to
"orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
especially "InvToPo.xslt" which talks about doing transformations
between 2 structures pointing to different namespaces.

WSDL Files in the Solution Composer

Similar Messages

Maybe you are looking for