Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for Web Services
  3. Configuring PowerExchange for Web Services
  4. Web Service Sources and Targets
  5. Web Services Consumer Transformation
  6. Creating and Configuring Web Service Workflows
  7. Appendix A: Datatype Reference

PowerExchange for Web Services User Guide for PowerCenter

PowerExchange for Web Services User Guide for PowerCenter

Importing a Web Service Source or Target Definition

Importing a Web Service Source or Target Definition

Follow the same steps to import a web service source or target definition from a WSDL. Since the source and target definitions represent different elements in the WSDL, the source definition created by the Designer differs from the target definition.
You can import a web service source or target from a WSDL that you can access locally or through a URL. You can import definitions from a WSDL file with RPC/Encoded or Document/Literal styles. You can also import definitions from a WSDL file over an HTTPS connection. The Designer can import web service source or target definitions from nested WSDL file definitions where the WSDL file contains information to import other WSDL files.
To import a web service source or target definition:
  1. To import a web service source definition, in the Source Analyzer, choose Sources > Import from WSDL (Consumer). Or, to import a web service target definition, in the Target Designer, choose Targets > Import from WSDL (Consumer).
    The Import from WSDL (Web Services Consumer) dialog box appears.
  2. Click Advanced Options to configure the default precision for String datatype fields and to set column naming conventions.
    The Change XMLViews Creation and Naming Options dialog box appears.
    Configure the following options:
    Option
    Description
    Override all infinite lengths
    You can specify a default length for fields with undefined lengths, such as strings. By default, this option is selected.
    Generate names for XML columns
    You can choose to name XML columns with a sequence of numbers or with the element or attribute name from the schema. If you use names, choose from the following options:
    • When the XML column refers to an attribute, prefix it with the element name. PowerCenter uses the following format for the name of the XML column:
    NameOfElement_NameOfAttribute
    • Prefix the XML view name for every XML column. PowerCenter uses the following format for the name of the XML column:
    NameOfView_NameOfElement
    • Prefix the XML view name for every foreign-key column. PowerCenter uses the following format for the name of a generated foreign key column:
    FK_NameOfView_NameOfParentView_NameOfPKColumn
    Maximum length for a column name is 80 characters. PowerCenter truncates column names longer than 80 characters. If a column name is not unique, PowerCenter adds a numeric suffix to keep the name unique.
    Default length for anyType element mapped to string
    Default length of the string port created for an element of type anyType. You can create a port of type string for an element of type anyType. By default, the length of the string is the value you set here.
    To change the length of the string, edit the web service source or target definition in the WSDL workspace. Default is 10,000.
    After you configure these options, the Designer automatically applies them to all web services source and target definitions you create.
  3. Click URL to import from a remote WSDL file located on a URL. Or, choose to import from a local file or a URL.
    If you import from a local file, select a WSDL file in a local folder and click Open.
    If you import from a URL, type a URL or select a URL from the Address list and click Open.
    Or, click UDDI to import from a remote WSDL file listed in a UDDI directory. Reserved for future use.
  4. If you are importing from a remote WSDL file located on a URL, enter the URL in the Address field. Or, if you are importing from a local WSDL file, navigate to the directory that contains the WSDL file and select the WSDL file.
  5. Click Open.
    If you did not configure the advanced settings in step 2, the Designer asks if you want to override the infinite length option. Click Yes to open the Change XMLViews Creation and Naming Options dialog box to configure advanced options.
  6. Select the operation defined in the WSDL for which you want to create the source or target definition.
    Step 1 of the Web Services Wizard appears.
  7. Click Next.
    Step 2 of the Web Services Wizard appears.
  8. Choose whether you want to generate the XML views as entity relationships or as normalized hierarchical relationships.
    If you select Hierarchy Relationships, then Normalized XML Views is automatically selected. The Denormalized XML Views option is reserved for future use.
    If the Designer determines that it will generate more than 400 views from a WSDL schema, the Designer does not generate the definition. You can import the WSDL schema and manually create the XML views in the WSDL workspace.
    When you import a definition from a WSDL schema that has no global elements, the Designer cannot create a root view in the definition. The Designer displays a message that there is no global element.
    Optionally, select Create Cookie Port to create a cookie column for the source or target definition.
  9. Optionally, select Create URL Port to create a URL column for the source or target definition.
  10. Click Finish.

0 COMMENTS

We’d like to hear from you!