Sunday, July 12, 2009

Creating an RFC Destination for SAP EP 6.0

Maintenance of a RFC destination using Display and Maintenance of RFC Destinations (transaction SM59) is necessary for integration between SAP BW 3.5 and SAP EP 6.0.

This setting is required for all integration scenarios .


Before you create an RFC destination in the BW system you have to Create an RFC Destination in the J2EE Engine.


Using the Maintaining Portal Server Settings for EP 6.0 Customizing activity, you can enter this RFC destination into the RSPOR_T_PORTAL table so that the BW system recognizes the RFC destination as a connected portal. Communication between the BW system and the SAP Enterprise Portal takes place through the RFC destination.

1. Start the transaction Display and Maintenance of RFC Destinations (transaction code SM59).

2. Choose Create.

3. Maintain the RFC destination:

¡ RFC destination:

¡ Connection type: T for TCP/IP connection

¡ Description:

¡ Technical settings

§ Activation type: Registered server program

§ Program ID: _PORTAL_

§ Gateway host:

§ Gateway service: sapgw

¡ Logon/security

§ Send SAP logon ticket: Activate

4. Save your entries.

Settings for the RFC Destination

Name of the RFC destination

The name of the RFC destination for an Enterprise Portal should be selected carefully.

The name of the RFC destination is saved in the Information Broadcasting settings. Saving is necessary to be able to uniquely identify the used, connected Enterprise Portal for integration with Knowledge Management.

The broadcast settings can be transported between BW systems. For this reason, the name of the RFC destination should be identical in the source and target systems.

The name recommended by SAP for the RFC destination to the connected portal is SAP_EP.

Connection type

Select a connection type T for TCP/IP Connection.

Description of the RFC destination

You can maintain the description of the RFC destination language dependently. The language-dependent description is used when publishing iViews from the BEx Web Application Designer and BEx Query Designer if multiple portals are connected to the BW system.

Activation type

Select Registered Server Program as the activation type.

Registered server program

The server program is set up under the program ID on the J2EE engine. The recommended naming convention is _PORTAL. You can find more information under Creating RFC Destinations in the J2EE Engine.

Gateway options

Under Gateway Options, enter the gateway host and the gateway service with which the J2EE engine communications with the BW system. The gateway host, an application server for the BW system, and the gateway service can be comprised generically of sapgw. You can determine the parameters for the gateway with the Gateway Monitor transaction (transaction code SMGW) using Goto ® Parameter ® Display.

Send SAP logon ticket

The option Send SAP Logon Ticket will be possible from SAP BW 3.5 SP 11 with SAP NetWeaver 04 SP Stack 11. You can avoid the use of the portal user bw_service by using this option. For more information.

If the RFC destination is also set up on the page for the J2EE engine, you can check the connection with the Connection button.

1 comment:

seventyros said...

Excellent Online Resource for SAP EP and SAP Web Dynpro ABAP. visit
Learn Sap Online