Note: This issue was resolved in DSP 6.7, see release notes
Issue
DSP versions prior to DSP 6.7 do not support the use of a load balancing message server with RFC or Data Services package types. When using load balancing via message server, either SYSID or MSSERV needs to be in the set of configuration parameters. Otherwise, when setting up a connection to an SAP Message Server in the dspCommon Data Sources Registry the test connection will return an error.
Workaround
As a workaround, you can use the server name of the underlying server that the message server is pointing to as the [SAP Server Host] value on the {Sap Settings} tab of the source record in Collect.
To add the SAP Server Host name to the source record in Collect:
- Click Collect in the Navigation pane.
- Select the Target connected to the SAP Server.
- Click the Vertical View icon for the SAP Server Target Source in the child pane.
- Click the Sap Settings tab in the Vertical View.
- Click Edit.
- Enter the SAP Server Host name.
NOTE: You don't want to use a message server. The value needs to be changed to the literal SAP application server that the message server is redirecting to.
- Click Save.
- Close the Vertical View.
Why is this happening?
With an "SAP Text" package type, you don't really have a package. When you click the Build Package icon, the DSP pulls the source schema for the table and then creates the table. The refresh is then performed via RFC (no package is executed). That RFC will use the [SAP Server Host] value on the {Sap Settings} tab of the source record in Collect, so that is what you need to adjust to work around this limitation.