In this blog, I will describe the way to configure FPN connection, considering the different possible landscapes.

Starting from SAP NetWeaver 7.3, you need to create an FPN connection in order to facilitate the sharing of portal content between two or more portals that reside in a federated portal network (FPN).

An FPN connection pairs one portal with another. The portals in an FPN connection can share content in one direction or both (in the event that both portals are 7.3 and higher). Since you can share content between two portals in both directions, a portal in an FPN connection can be both a producer and a consumer, at the same time.

You use the FPN Connection wizard to configure trust (one way or two way), to create connections and to carry out registration.

Be aware that there are different ways for implementing content consumption between portals. So, before you start creating and configuring FPN connections, review the CONTENT SHARING WITH SAP NETWEAVER PORTAL document and chose the recommended option considering your use case.

Basic Internal Network

When you have just a basic internal network, use the consumer and producer internal network information. That means the direct host and port of the instance, with a fully qualified domain.

Scenario A.PNG

Scenario1.1.PNG

scenario1.2.PNG

When using secure protocol:

  1. From the “Protocol” dropdown list, select “HTTPS”.
  2. From the “RMI-P4 Connection Method and Protocol” dropdown list, select the corresponding “secure” string (e.g. “Connection string or single server (secure)”).
  3. Choose the corresponding ports. By default: HTTPS: port + 1 (e.g. 50201); P4: port + 6 (e.g. 50206). Check the System Information for the correct ports.

Cluster Internal Network

In a cluster environment, where you have a load balancer or a web dispatcher in front of the consumer / producer system, you can use the load balancer or web dispatcher information for the settings.

Scenario B.PNG

If you want to load balance p4 communication, you can only do this by using the message server information. Check the System Information for the message server host and port.

message server.PNG

scenario2.1.PNG

scenario2.2.PNG

External Network – Reverse Proxy

In an external network, where you a have reverse proxy, you also need to configure the “External Network Settings” using the reverse proxy information.

Scenario C.PNG
scenario3.1.PNG

Why do you need to do this?

Because the domains of the external and internal networks can be different. In those cases, trying to use the internal host and port of the consumer will create a cookie with the internal domain (e.g. local.domain) but redirect links will be with the external domain (e.g. proxy.domain) and therefore the access to the producer will fail. Once you have configured external network settings, end users can only access FPN content at runtime if they use the external network host and port. If they use the internal host and port to access the consumer, the FPN content will not be available.

If you choose to use FPN functionality you might find the following SAP Notes helpful:

  1. SAP Note 880482 – FPN: Federated Portal Network Central Note
  2. SAP Note 1295662 – Interoperabilitybetween 2 portals in FPN environment
To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Yogesh Kotwani

    Good info,I have a question regarding the RMI-P4 port for the message server using load balancer.The one highlighted by you is rdisp/msserv_internal i.e. 39<instance number>

    Is this the P4 port for message server ?

    Do we have a SAP note which clearly explains about this RMI-P4 port for message server.

    Mentioned SAP notes and search I did I couldnt find much.

    Thanks

    (0) 
    1. Gitit Sagiv Post author

      Hi Yogesh,

      I have manipulated my screenshot so it will not contain any secure data. The message server host and port mentioned in my screenshot are “dummy” values.
      The purpose of the screenshot is to show where does the message server host and port are exposed in the system information.
      In order to load balance p4 communication, the message server port (visible via the system information) should be used as the RMI-P4 port.

      Regards,
      Gitit

      (0) 
      1. Hrishav Kumar

        Hello Gitit,

        Just a little help.

        Can we use message server HTTP port, instead of message server port while providing connection details for remote system?

        Our consumer portal is based on SAP NW 7.02 and for one of the producer, we want to connect the remote system using the Message server.

        We are providing the message server host-name. Please suggest the value for the port number ( 3932 or 8132 ; 32 being the instance number for central services).

        Regards,

        Hrishav

        (0) 
        1. Michal Zilcha-Lang

          Hi Hrishav,

          The message server is used for load balancing in a cluster environment as it uses the P4 protocol. For load balancing of HTTP you should use something like a web dispatcher.

          Thanks & regards,

          Michal

          (0) 

Leave a Reply