cancel
Showing results for 
Search instead for 
Did you mean: 

Data Services communication with SAP - physical/logical server name

warwick_tagg
Explorer
0 Kudos
73

Iu2019m having trouble connecting Data Services to SAP.

Environment details:

Data Services version 12.2.1.2 on Windows 2008 SP2

ERP and SRM on Windows 2008 (database SQL Server 2008 SP1)

Repository on SQL Server 2008 SP1

All servers (SAP and Data Servers) have had logical systems defined over the physical system names and they use these logical names to communicate with each other. The Data Services server, hence has two names (logical and physical) and two corresponding IP addresses.

The problem weu2019re having is that when the SAP server communicates back to the Job Server it needs to use the logical server name and corresponding IP address. Currently it is using the physical server name and IP address, causing communication failures.

When I run the host_name() function within Data Services it returns the physical host name.

Is there a way to determine how Data Services identifies itself and whether this can be manipulated? Is it possible to configure Data Services to run in a logical environment?

Any thoughts or commends would be appreciated. Thanks

View Entire Topic
werner_daehn
Active Contributor
0 Kudos

I am not that good with more complex SAP ERP setups, keep that in mind. But my understanding is that we always connect to the SAP message server.

Our DS 12.2 rfc.ini feature might help maybe?

warwick_tagg
Explorer
0 Kudos

Looked at this from another angle. We were using Direct Download transport method which processes in the foreground and uses the SAPGUI for communication. It seems as though it was how SAPGUI communicates with the SAP server on Data Services behalf that was causing the problem.

We managed to motivate to get a share setup between the SAP server and the Data Services box which allows us to use Shared Directory transport method. This also allows for background processing - eliminating the part of the SAPGUI communication that was causing the problem.