PowerExchange for Web Services User Guide for PowerCenter

10.5.4
- 10.5.9
- 10.5.8
- 10.5.7
- 10.5.6
- 10.5
- 10.4.0

Back Next

Importing a Web Services Consumer Transformation

You can import a Web Services Consumer transformation from a remote or local WSDL file. When you import a Web Services Consumer transformation, you can select a web service operation from a WSDL file located on a URL or a local WSDL file.

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. Web Services Consumer Transformation supports TLS 1.2, TLS 1.1, and TLS 1.0 protocols. The Designer can import Web Services Consumer transformations from nested WSDL file definitions where the WSDL file contains information to import other WSDL files.

When you import a WSDL file and create a Web Services Consumer transformation, you define the structure of the transformation. You can import the transformation with one of the following relationships:

Entity relationships
. Creates groups for multiple-occurring or referenced elements and complex types. It creates relationships between views instead of creating one large hierarchy. When you import a transformation with entity relationships, the Designer creates multiple groups.

Hierarchical relationships
. Creates a root and expands the XML components under the root. If you create a hierarchical relationship, then you create a normalized view. In a normalized view, every element or attribute appears once. One-to-many relationships become separate XML views with keys to relate the views.

When you import a WSDL file and create a transformation, you can create one or both of the following ports:

Cookie port
. Creates a cookie port that can accept cookies and pass them to subsequent PowerCenter Integration Service calls. The PowerCenter Integration Service uses the cookie to authenticate subsequent calls in other Web Services Consumer transformations. Create a cookie port when a remote web server implements user sessions based on cookies.

URL port
. Creates a URL port that can receive information about authenticated URLs and pass them to subsequent PowerCenter Integration Service calls. The PowerCenter Integration Service uses the information to authenticate subsequent calls in other Web Services Consumer transformations. Create a URL port when you want to pass a dynamically generated endpoint URL instead of a static endpoint URL to the PowerCenter Integration Service. The value in this column overrides the endpoint URL that you specify in the transformation properties.

To create a Web Services Consumer transformation:

Open the appropriate Designer tool.

If you use the Mapping Designer or Mapplet Designer, you must create a mapping or a mapplet before you create a Web Services Consumer transformation.

Click Transformation > Create. Or, click the Web Services Consumer Transformation icon in the toolbar. Then click in the workspace to open the Import from WSDL (Web Services Consumer) dialog box. You can also use this method to replace a transformation. Go to step 6.

Select Web Services Consumer as the transformation type.

Enter a name for the transformation and click Create.

The Import from WSDL (Web Services Consumer) dialog box appears.

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.

You can select the following options:

Option	Description
Override all infinite lengths	You can specify a default length for fields with undefined lengths, such as strings.
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 XMLColumn 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: N ameOfView_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.

Option

Description

Override all infinite lengths

You can specify a default length for fields with undefined lengths, such as strings.

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 XMLColumn 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:

ameOfView_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.

After you configure these options, the Designer applies them to all Web Services Consumer transformation you create.

Click URL to import from a remote WSDL file located on a URL. Or, click Local File to import from a local WSDL file.

Or, click UDDI to import from a remote WSDL file listed in a UDDI directory. Reserved for future use.

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.

Click Open.

If you did not configure the advanced settings in step 5, 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.

Step 1 of the Web Services Wizard appears.

Select the web service operation that you want to import and click Next.

You can only import web service operations
from a WSDL file. The Import from WSDL (Web Services Consumer) dialog box displays the WSDL definition hierarchy so that you know which port and binding a web service operation is associated with.

A web service operation might be available to import from more than one port within the same WSDL definition. Make sure that you import the web service operation from the port you want.

Step 2 of the Web Services Wizard appears.

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.

Optionally, select Create Cookie Port to create a cookie port for the transformation.

Optionally, select Create URL Port to create a URL port for the transformation.

Click Finish.

Web Services Consumer Transformation

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal