• hawkeye
  • NEWBIE
  • 0 Points
  • Member since 2010

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 0
    Replies
Hi all,

Informatica documentation describes the process of setting up web service connections as shown below.  Does any one know if this will work with an apex webservices exposed from a salesforce org?  Has anyone tried this?

 

There is a seperate process for "PowerExchange for Salesforce Connections", but I believe this exposes calls available through the partner api only (i.e. not a custom written web service).

 

---------------------------

 

 

PowerExchange for Web Services Connections

The Integration Service can use Web Services Consumer application connections to extract data from web service sources, write data to web service targets, or transform data using Web Services Consumer transformations. Web Services Consumer application connections allow you to control connection properties, including the endpoint URL and authentication parameters.

To connect to a web service, the Integration Service requires an endpoint URL. If you do not configure a Web Services Consumer application connection or if you configure one without providing an endpoint URL, the Integration Service uses the endpoint URL contained in the WSDL file on which the source, target, or Web Services Consumer transformation is based.

Use the following guidelines to determine when to configure a Web Services Consumer application connection:

*
Configure a Web Services Consumer application connection with an endpoint URL if the web service you connect to requires authentication or if you want to use an endpoint URL that differs from the one contained in the WSDL file.
*
Configure a Web Services Consumer application connection without an endpoint URL if the web service you connect to requires authentication but you want to use the endpoint URL contained in the WSDL file.
*
You do not need to configure a Web Services Consumer application connection if the web service you connect to does not require authentication and you want to use the endpoint URL contained in the WSDL file.

If you need to configure SSL authentication, enter values for the SSL authentication-related properties in the Web Services application connection. For information about SSL authentication, see the PowerExchange for Web Services User Guide.

To create a Web Services Consumer application connection:

1.
In the Workflow Manager, connect to a PowerCenter repository.
2.
Click Connections > Application.
The Application Connection Browser dialog box appears.
3.
From Select Type, select Web Services Consumer.
4.
Click New.
The Connection Object Definition dialog box appears.
5.
Enter a name for the application connection.
6.
Enter the following connection information:
Connection Attributes
Description
User Name
User name that the web service requires. If the web service does not require a user name, enter PmNullUser.
To define the user name in the parameter file, enter session parameter $ParamName as the user name, and define the value in the session or workflow parameter file. The Integration Service interprets user names that start with $Param as session parameters.
Use Parameter in Password
Indicates the web service password is a session parameter, $ParamName. If you enable this option, define the password in the workflow or session parameter file, and encrypt it using the pmpasswd CRYPT_DATA option. Default is disabled.
Password
Password that the web service requires. If the web service does not require a password, enter PmNullPasswd.
Code Page
Connection code page. The Repository Service uses the character set encoded in the repository code page when writing data to the repository.
End Point URL
Endpoint URL for the web service that you want to access. The WSDL file specifies this URL in the location element.
You can use session parameter $ParamName, a mapping parameter, or a mapping variable as the endpoint URL. For example, you can use a session parameter, $ParamMyURL, as the endpoint URL, and set $ParamMyURL to the URL in the parameter file.
Domain
Domain for authentication.
Timeout
Number of seconds the Integration Service waits for a connection to the web service provider before it closes the connection and fails the session. Also, the number of seconds the Integration Service waits for a SOAP response after sending a SOAP request before it fails the session.
Trust Certificates File
File containing the bundle of trusted certificates that the Integration Service uses when authenticating the SSL certificate of the web services provider. Default is ca-bundle.crt.
Certificate File
Client certificate that a web service provider uses when authenticating a client. You specify the client certificate file if the web service provider needs to authenticate the Integration Service.
Certificate File Password
Password for the client certificate. You specify the certificate file password if the web service provider needs to authenticate the Integration Service.
Certificate File Type
File type of the client certificate. You specify the certificate file type if the web service provider needs to authenticate the Integration Service. The file type can be either PEM or DER. For information about converting the file type of certificate files, see the PowerExchange for Web Services User Guide.
Private Key File
Private key file for the client certificate. You specify the private key file if the web service provider needs to authenticate the Integration Service.
Key Password
Password for the private key of the client certificate. You specify the key password if the web service provider needs to authenticate the Integration Service.
Key File Type
File type of the private key of the client certificate. You specify the key file type if the web service provider needs to authenticate the Integration Service. PowerExchange for Web Services requires the PEM file type for SSL authentication. For information, see the PowerExchange for Web Services User Guide.
Authentication Type
Select one of the following authentication types to use when the web service provider does not return an authentication type to the Integration Service:
-
Auto. The Integration Service attempts to determine the authentication type of the web service provider.
-
Basic. Based on a non-encrypted user name and password.
-
Digest. Based on an encrypted user name and password.
-
NTLM. Based on encrypted user name, password, and domain.
Default is Auto.
7.
Click OK.
The application connection appears in the Application Connection Browser.