In this step, you define the server settings in your application back-end system.
Prerequisites
This step must be executed in your application back-end system, as described in the following,
unless you are using the ABAP SMI hub. If you want to use the ABAP SMI hub, for
example, to redirect and execute the calls from the SAP Gateway server, you have
to enter the address of the REST tunnel instead on the back-end system, and define
the connection to SAP Jam on the SAP Gateway server. For the
configuration of the REST tunnel, see Configuring REST Tunnel.
Procedure
-
In Customizing for SAP NetWeaver, choose (or run transaction
CLB2_PLATF).
The Change View "Server Communication": Overview
screen appears.
-
Under Server Communication, select the line with the
following values:
| Field |
Value |
| Service Provider Type |
Jam |
| Server |
Jam productive |
| Name of Local Service
Provider |
sapjam.com |
-
Choose Details (Ctrl+Shift+F2).
The Change View "Server Communication": Details
screen appears.
-
Complete the fields as follows:
Field
|
Value
|
|---|
Send Notification
|
To distribute notifications to SAP Jam, activate this option.
|
bgRFC Destination
|
(Optional) The parallelization of the send scenario for different target servers is achieved
through bgRFC processing.
If you leave the field empty, the system assumes that the destination
IWFND_ODATA_PUSH
exists in transaction
SBGRFCCONF
and that the scheduler settings are made for this
destination.
Note
This is the same destination used by the notification processing of the SAP Gateway server.
-
You can also specify a separate bgRFC destination
for ABAP SMI in transaction
SBGRFCCON.
You must then enter this destination in the ABAP
SMI server settings.
|
Gateway Dest.
|
Not required
|
-
Save your entries.
Results
Your application system is now connected to
SAP Gateway and ready to retrieve
business object notifications.
UI Technologies 
SAP Jam Integration 
(or run transaction
CLB2_PLATF).
The Change View "Server Communication": Overview screen appears.