WSDL Data Object
A WSDL data object is a physical data object that uses a WSDL file as a source. You can use a WSDL data object to create a web service or a Web Service Consumer transformation. Import a WSDL file to create a WSDL data object.
After you import a WSDL data object, you can edit general and advanced properties in the Overview and Advanced views. The WSDL view displays the WSDL file content.
Consider the following guidelines when you import a WSDL:
- •The WSDL file must be WSDL 1.1 compliant.
- •The WSDL file must be valid.
- •Operations that you want to include in a web service or a Web Service Consumer transformation must use Document/Literal encoding. The WSDL import fails if all operations in the WSDL file use an encoding type other than Document/Literal.
- •The Developer tool must be able to access any schema that the WSDL file references.
- •If a WSDL file contains a schema or has an external schema, the Developer tool creates an embedded schema within the WSDL data object.
- •If a WSDL file imports another WSDL file, the Developer tool combines both WSDLs to create the WSDL data object.
- •If a WSDL file defines multiple operations, the Developer tool includes all operations in the WSDL data object. When you create a web service from a WSDL data object, you can choose to include one or more operations.
WSDL Data Object Overview View
The WSDL data object Overview view displays general information about the WSDL and operations in the WSDL.
The following table describes the general properties that you configure for a WSDL data object:
Property | Description |
|---|
Name | Name of the WSDL data object. |
Description | Description of the WSDL data object. |
The following table describes the columns for operations defined in the WSDL data object:
Property | Description |
|---|
Operation | The location where the WSDL defines the message format and protocol for the operation. |
Input | The WSDL message name associated with the operation input. |
Output | The WSDL message name associated with the operation output. |
Fault | The WSDL message name associated with the operation fault. |
WSDL Data Object Advanced View
The WSDL data object Advanced view displays advanced properties for a WSDL data object.
The following table describes the advanced properties for a WSDL data object:
Property | Description |
|---|
Connection | Default web service connection for a Web Service Consumer transformation. |
File Location | Location where the WSDL file exists. |
Importing a WSDL Data Object
To create a web service from a WSDL or to create a Web Service Consumer transformation, import a WSDL data object. You can import a WSDL data object from a WSDL file or a URI that points to the WSDL location. You can import a WSDL data object from a WSDL file that contains either a SOAP 1.1 or SOAP 1.2 binding operation or both.
1. Click File > New > Data Object.
2. Select WSDL data object and click Next.
The New WSDL Data Object dialog box appears.
3. Click Browse next to the WSDL option and enter the location of the WSDL. Then, click OK.
When you enter the location of the WSDL, you can browse to the WSDL file or you can enter the URI to the WSDL.
Note: If the URI contains non-English characters, the import might fail. Copy the URI to the address bar in any browser. Copy the location back from the browser. The Developer tool accepts the encoded URI from the browser.
4. Enter a name for the WSDL.
5. Click Browse next to the Location option to select the project or folder location where you want to import the WSDL data object.
6. Click Next to view the operations in the WSDL.
7. Click Finish.
The data object appears under Physical Data Object in the project or folder in the Object Explorer view.
WSDL Synchronization
You can synchronize a WSDL data object when the WSDL files change. When you synchronize a WSDL data object, the Developer tool reimports the object metadata from the WSDL files.
You can use a WSDL data object to create a web service or a Web Service Consumer transformation. When you update a WSDL data object, the Developer tool updates the objects that reference the WSDL and marks them as changed when you open them. When the Developer tool compares the new WSDL with the old WSDL, it identifies WSDL components through the name attributes.
If no name attribute changes, the Developer tool updates the objects that reference the WSDL components. For example, you edit a WSDL file and change the type for simple element "CustID" from xs:string to xs:integer. When you synchronize the WSDL data object, the Developer tool updates the element type in all web services and Web Service Consumer transformations that reference the CustID element.
If a name attribute changes, the Developer tool marks the objects that reference the WSDL component as changed when you open them. For example, you edit a WSDL and change the name of an element from "Resp" to "RespMsg." You then synchronize the WSDL. When you open a web service that references the element, the Developer tool marks the web service name in the editor with an asterisk to indicate that the web service contains changes. The Developer tool updates the element name in the web service, but it cannot determine how the new element maps to a port. If the Resp element was mapped to a port in the Input transformation or the Output transformation, you must map the RespMsg element to the appropriate port.
The Developer tool validates the WSDL files before it updates the WSDL data object. If the WSDL files contain errors, the Developer tool does not import the files.
Synchronizing a WSDL Data Object
Synchronize a WSDL data object when the WSDL files change.
1. Right-click the WSDL data object in the Object Explorer view, and select Synchronize.
The Synchronize WSDL Data Object dialog box appears.
2. Click Browse next to the WSDL field, and enter the location of the WSDL. Then, click OK.
When you enter the location of the WSDL, you can browse to the WSDL file or you can enter the URI to the WSDL.
Note: If the URI contains non-English characters, the import might fail. Copy the URI to the address bar in any browser. Copy the location back from the browser. The Developer tool accepts the encoded URI from the browser.
3. Verify the WSDL name and location.
4. Click Next to view the operations in the WSDL.
5. Click Finish.
The Developer tool updates the objects that reference the WSDL and marks them as changed when you open them.
Certificate Management
The Developer tool must use a certificate to import WSDL data objects and schema objects from a URL that requires client authentication.
By default, the Developer tool imports objects from URLs that require client authentication when the server that hosts the URL uses a trusted certificate. When the server that hosts the URL uses an untrusted certificate, add the untrusted certificate to the Developer tool. If you do not add the untrusted certificate to the Developer tool, the Developer tool cannot import the object. Request the certificate file and password from the server administrator for the URL that you want import objects from.
The certificates that you add to the Developer tool apply to imports that you perform on the Developer tool machine. The Developer tool does not store certificates in the Model repository.
Informatica Developer Certificate Properties
Add certificates to the Developer tool when you want to import objects from a URL that requires client authentication with an untrusted certificate.
The following table describes the certificate properties:
Property | Description |
|---|
Host Name | Name of the server that hosts the URL. |
Port Number | Port number of the URL. |
Certificate File Path | Location of the client certificate file. |
Password | Password for the client certificate file. |
Adding Certificates to Informatica Developer
When you add a certificate, you configure the certificate properties that the Developer tool uses when you import objects from a URL that requires client authentication with an untrusted certificate.
1. Click Window > Preferences.
2. Select Informatica > Web Services > Certificates.
3. Click Add.
4. Configure the certificate properties.
5. Click OK.