Configuring the P4 Port with Remote Delta Link Usage

Applicable to: remote delta links

Use

When implementing the remote delta link usage in a federated portal network, communication between the consumer and producer portal requires use of the P4 port of both portals.

Your portal (the consumer) tries to calculate the P4 port number of the producer portal by taking the HTTP port of the producer (entered by an administrator on your portal in the Producer Wizard or Editor) and replacing the last HTTP port digit by 4.

●      If the resultant value is not the same as the actual P4 port on the producer (which may be the case as a result of load balancing or changes made by a system administrator, for example), then you must enter it in the portal service ProducerInformationService on your portal according to the procedure described below.

●      If the resultant value is the same as the actual P4 port on the producer, then you do not need to add any information to the ProducerInformationService service. You can skip this procedure.

Conversion Examples:

●      HTTP: 50000 → converted to P4: 50004 

●      HTTP: 50007 → converted to P4: 50004 

●      HTTP: 51002 → converted to P4: 51004 

Examples for when manual update of ProducerInformationService service is necessary:

●      HTTP port is 50000; producer P4 port is 50005 (the portal updates the P4 port to 50004 based on the existing HTTP port)

●      HTTP port is 51000; producer P4 is 50004 (the portal updates the P4 port as 51004 based on the existing HTTP port)

Prerequisite

●      You have the producer alias of the producer portal. To obtain the alias you need to first add the producer instance to your portal.

More information: Viewing a Producer Alias 

●      You have the P4 port number of the producer.

You may want to determine if your own P4 port can be calculated by the producer portal using the formula described above. If not, then you need to provide your own P4 port information to the system administration on the producer portal.

To identify your own P4 port, use the SAP Management Console to view the communication ports of the server. On the Java instance (not on the central server node), browse the tree structure of the SAP system to locate the Access Points node.

More information: SAP Management Console and Viewing and Configuring the Communication Ports 

Procedure

...

If you have determined (as described above) that you need to update the ProducerInformationServiceservice, do the following:

       1.      Using SAP NetWeaver Administrator on the consumer portal, find the Web module, com.sap.portal.fpn.persistance. Then in the Web module, select the portal service, ProducerInformationService.

For information about how to access services in SAP NetWeaver Administrator, see Accessing Portal Services in SAP NetWeaver Administrator.

       2.      Update the AliasToPorts property in the following format: <producer_alias>=<producer_P4port_number>

For example: alias1=50004;alias2=56004