A fix is available
APAR status
Closed as new function.
Error description
Customer's environment has involved IBM DataPower as middle layer between Information Server and External Network Connection. Therefore, the reference ULR that defined in the InfoSphere Information Server SalesForce Connector could not be use the direct domain name that provided by SalesForce. As above reason, when browering the object from SF connector, customer always encounters the timeout error.
Local fix
Problem summary
Salesforce Connector cannot connect to Salesforce when there is a Gateway intermediate between the Salesfroce Connector and the Salesforce.com Server, and the URL specified in the job is the is the Gateway URL. Note, here the Gateway will have a methodology to send the connection request recieved from the Salesforce Connector to Salesforce.com Server and receive the response from the Salesforce.com Server and send it back to the Salesforce Connector
Problem conclusion
When the Salesforce Connector connects using the Gateway URL, for example "https://gateway.somemachine.com/services/Soap/u/32.0", on the Gateway it will be redirected to the Salesforce URL for example "https://cs17.salesforce.com/services/Soap/u/32.0/00Dg0000006SK8 4". When the response is received back from Salesforce, the Salesforce Connector will try to read from the later Salesforce URL, but it cannot connect to it. The requirement is to connect to the Gateway URL (which receives the response from the Salesforce Server) to get the response back from Salesforce.com Server. Resolution: Implemented the requirement by using the environment variable "SF_CONNECT_LOGIN_URL". When this environment variable is set as "true", the Salesforce Connector will not use the URL returned by the Salesforce Server, but the URL specified in the Job Property URL will be used to connect to Salesforce.
Temporary fix
Comments
APAR Information
APAR number
JR54851
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
912
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-12-01
Closed date
2016-02-12
Last modified date
2016-02-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R912 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"912","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
13 October 2021