Editar

Partilhar via

Import BPEL4WS in BizTalk Server

  • Artigo

You can import from existing BPEL4WS to create an orchestration.

Important

This release of BizTalk Server supports BPEL4WS 1.1. You cannot import or export BPEL4WS 1.0.

For an example of how to import BPEL4WS, see BPEL Import (BizTalk Server Sample).

Import BPEL4WS into an orchestration

  1. Create a new project.

  2. From the BizTalk Project types, double-click BizTalk Server BPEL Import Project, or select BizTalk Server BPEL Import Project and press OK.

  3. In the wizard, select the BPEL, WSDL and XSD files that should be imported to form the new BizTalk project. Include all files that are referenced via import and include statements.

  4. Select WSDL files for invoked Web services.

    You can now modify or deploy the new orchestration.

    Import restrictions on BPEL4WS

  • When importing BPEL and WSDL, make sure that the Name property of the WSDL definition node and the BPEL process node do not match.

  • Do not use XLANG/s reserved words in BPEL4WS that you import. For a complete list, see XLANG/s Reserved Words.

  • Only XSD predefined simple types are supported.

  • xsd:QName is not supported; it is imported as System.String. Use xsd:string instead.

  • Consider using canonical XPaths when importing BPEL4WS.

    It is good practice to import only canonical XPaths in order to achieve optimal performance. The entire path from root to the promoted node must be spelled out by using '/*[local-name()="someName" and namespace-uri()="someUri"]'.

    If you import a non-canonical XPath, you can remove a promotion and repromote the same field in order to have the Schema Editor create the correct canonical XPath.

    Example: (targetNamespace = http://BizTalk_Server_Project3.Schema1)

    <element name=Root type=complexType>  
            <sequence>  
                        <element name=promotedField/>  
            </sequence>  
</element>

    XPath - /*[local-name()='Root' and namespace-uri()='http://BizTalk_Server_Project3.Schema1']/\*[local-name()='promotedField' and namespace-uri()='']

    Canonical XPath Non-Canonical XPath
    BizTalk Editor displays a special icon (Icon that represents the BizTalk Editor.) to denote that the field has been promoted. Usage of canonical XPath expressions to promote fields improves performance through more efficient traversal of the XML BizTalk Editor does not display a special icon. Both the compiler and the promotion dialog give warnings. There is a linear but nontrivial effect on performance as the message size increases.

See Also

How to Export BPEL4WS
XLANG-s to BPEL4WS Type Conversions