Show TOC

Background documentationTechnical Parameters

 

RFC Destination and Logical Port

To call the Web service for highlighting (OBNWebService) that points from the CRM application to the portal, you need to make the following settings in the CRM backend:

  1. Create the RFC destination CRM_EP_DEST in transaction RFC Destinations (SM59), under HTTP Connections to External Server with the following settings:

    • Target host: <server name>

    • Service number: <port number>

    • Path prefix: /irj/servlet/prt/soap/OBNWebService?style=doc_lit

    • Logon procedure:

      Make the following settings in the Logon & Security tab page under Logon Procedure:

      • Activate No Logon

      • Deactivate Basic Authentication

      • Activate Send SAP Logon Ticket

  2. Create the logical port in transaction Maintain Logical Ports (LPCONFIG) with the following settings:

    • Under Logical Port:

      • Proxy class: CO_WDR_OBNWEB_SERVICE

      • Logical port: CRM_EP_DEST

    • Under Start of the navigation path General Settings Next navigation step Call Parameters End of the navigation path:

      • HTTP destination: CRM_EP_DEST

    • Under Operations:

      • SOAP actions according to SAP Note 1224422

SAP Authenticate Assertion Ticket

To enable communication between an ABAP system and SAP NetWeaver Portal, you need to configure the SAP Authenticate Assertion Ticket for any application.

  1. Deploy the SSO2 wizard on the J2EE engine and run it, adding the ABAP engine to the list of trusted systems of the J2EE system. For more information, see SAP Note 1083421.

  2. Configure the required application with the ABAP system certificate.

    1. Log on to Start of the navigation path Visual Administrator Next navigation step Server Next navigation step Services Next navigation step Security Provider End of the navigation path.

    2. Choose ticket.

    3. Change to edit mode and click Add New.

    4. Choose EvaluateAssertionTicketLoginModule.

    5. Choose Flag = SUFFICIENT.

  3. Export the engine certificate from key storage and import it to the relevant ABAP system.

    1. Log on to Start of the navigation path Visual Administrator Next navigation step Server Next navigation step Services Next navigation step Key Storage End of the navigation path.

    2. Choose Start of the navigation path TicketKeystore Next navigation step SAPLogonTicketKeypair-cert End of the navigation path and click Export to export the extension type .crt (X.509 type), for example, SOM.crt.

    3. Log on to the ABAP system and start transaction STRUSTSSO2.

    4. Click the first icon (Import Certificate) in Certificate, and choose the engine certificate.

    5. Click Add to Certificate List to make the certificate visible in the certificate list.

    6. Click Add to ACL (system ID is the engine ID; client is always 000, because the J2EE engine has no client).

    7. Click System PSE and choose Distribute in the context menu.

Note Note

If the connection does not work, see SAP Notes 1045019 and 1083421.

For more information, see SAP Help Portal for SAP NetWeaver 7.0 (2004s) in the Security Guide at Start of the navigation path User Administration and Authentication Next navigation step User Authentication and Single Sign-On Next navigation step Authentication on the J2EE Engine Next navigation step Configuring Authentication Mechanism Next navigation step Using Logon Tickets for Single Sign-On Next navigation step Configuring the Use of Logon Tickets Next navigation step Adjusting the Login Module Stacks for Using Logon Tickets End of the navigation path

For more information, see SAP Help Portal for SAP NetWeaver 7.0 (2004s) in the Security Guide at Start of the navigation path User Administration and Authentication Next navigation step User Authentication and Single Sign-On Next navigation step Authentication on the J2EE Engine Next navigation step Configuring Authentication Mechanism Next navigation step Using Logon Tickets for Single Sign-On Next navigation step Configuring the Use of Logon Tickets Next navigation step Configuring the J2EE Engine to Accept Logon Tickets End of the navigation path.

End of the note.
Work Protect Mode

You use the work protect mode to define the handling of unsaved data when you navigate in the portal.

Portal Default Settings

You can define portal default settings that apply for all users; these settings can be overwritten by the individual user.

  1. Choose Start of the navigation path System Administration Next navigation step System Configuration Next navigation step Service Configuration End of the navigation path.

  2. Choose Start of the navigation path Applications Next navigation step com.sap.portal.epcf.loader Next navigation step Services End of the navigation path under Browse.

  3. Choose epcfloader.

Recommendation Recommendation

We recommend the following default settings:

  • workprotect.mode.default = 3 (Required behavior can be selected each time the dialog box appears)

  • workprotect.mode.personalize = on

  • workprotect.window.features = empty

End of the recommendation.
User-Dependent Settings

You can define user-dependent settings that apply for the individual user. Click Personalize in the header area and select WorkProtect Mode in the detailed navigation of the portal.

Recommendation Recommendation

We recommend that you choose the option Choose action in popup on unsaved data, to make sure that the data loss dialog box appears.

End of the recommendation.