Show TOC

Advanced P4 Protocol Connection ConfigurationLocate this document in the navigation structure

Use

The client is able to connect to the server through HTTP proxies or SAP Routers specifying additional properties in the JNDI environment.

  • HTTP Proxy configuration

    Connection via HTTP Proxy is allowed for HTTP(S) tunneling connection to the server.

    The proxy settings for HTTP(S) tunneling can be configured by JNDI environment parameters or by system properties. Their priority is as follows:

    1. JNDI environment parameters set as InitialContext properties:

      • http.ProxyHost - the host of the proxy

      • http.ProxyPort - the port of the proxy

      • http.ProxyUsername - (optional) HTTP proxy username

      • http.ProxyPassword - (optional) HTTP proxy password

    2. System properties:

      The same JNDI environment properties listed above can be set as system properties of the JVM.

  • SAP Router configuration

    In order to configure a connection through SAP Router, the client should specify the following properties:

    • SAPRouter

      This property specifies that SAP Router is used for the service connection, the host and port obtained form the message server are appended at the end of the string, so the routers must be configured to allow connections to every access point that is published in the message server.

    • NoRouterForMS

      If set, the connection to the message server is also made through the router with the supplied string.

Cluster-wide Load balancing of Secure P4/SSL Connections

The message server is queried for service access points.

Provider URL string:

mshttps://message_server_host:message_server_https_port/P4S

or

mshttp://message_server_host:message_server_http_port/P4S

Optional properties:

  • HTTP_Host

  • HTTP_Port

These optional properties are used to specify an HTTPS proxy for the request to the message server and for the SSL P4 connection.

Secure Communication with SAP Router

Provider URL string:

  • If message server is used for load balancing:

    ms://message_server_host:message_server_https_port/P4S

  • If direct connection is used over a secure connection:

    p4s://host:p4_ssl_port

  • If SAP router is used:

/H/proxy1_host/S/proxy1_port/[P/proxy1_password/][H/proxy2_host/S/proxy2_port/]H/NetWeaver_host/S/NetWeaver_P4_port

Optional properties:

  • SAPRouterPassword - the password required to access the service if the router requires it.

  • NoRouterForMS = " true" - does not use the router for the request to the message server and connects directly to the message server host/port.

Secure Communication to a Direct Server Process

Provider URL string:

P4S://host:p4_ssl_port#serverId

P4://host:P4_port#serverId

The parameter serverId is the "cluster id" of the running server process (server0, server1) behind the ICM that handles the specified host and port.

Cluster-wide Load Balancing of Secure P4/SAP Router Connections

Provider URL string:

ms://message_server_host:message_server_http_port/P4

SAPRouter - the string that is used.

Optional properties:

  • SAPRouterPassword - the password required to access the service if the router requires it.

  • NoRouterForMS = "true" - does not use the router for the request to the message server and connect directly to the message server host/port.

Cluster-wide Load Balancing of P4 Connections with Message Server Provider

URL string:

ms://message_server_host:message_server_http_port/P4

SAP Router Direct Connection to Instance/Server Node

Provider URL string:

  • p4ni://saprouter_string

  • p4://_host:p4_port#sereverId

SAPRouter/SAPRouterPassword - new InitialContext properties to construct the router string internally from the true URL host/port (used when the client wants to connect to AS Java via a configured SAP Router).