APAR status
Closed as program error.
Error description
The IDoc listener actually opens two connections: Server and Destination, and the Destination one can use ASHOST and MSHOST. I made a modification that separates the two and uses the MSHOST parameters when load balancing is enabled.
Local fix
use 6.5 Idoc listener binaries as they are compatible with v7.
Problem summary
The IDoc Listener in version 7.0 cannot connect to the SAP message server in a load balanced configuration (regardless if separate or stand alone gateway). Symptom is the error "Connect from SAP gateway to RFC server failed" in the IDOC listener log ( <IIS Location>\Server\DSSAPConnections\<Connection>\IDocListener.log )
Problem conclusion
Code fix. Enabled the use of MSHOST parameter when Load Balancing is enabled.
Temporary fix
Use the IDOC Listener binaries from version 6.5.0.2 (replace whole folder DSSAPbin)
Comments
APAR Information
APAR number
JR49344
Reported component name
IS PACK FOR SAP
Reported component ID
5724Q5500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-13
Closed date
2014-04-10
Last modified date
2014-04-10
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
IS PACK FOR SAP
Fixed component ID
5724Q5500
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCSRJX","label":"DataStage Pack for SAP R\/3"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
10 April 2014