Serverkonfiguration > Post Server Configuration > Configuring the HTTP2 Protocol
  
Configuring the HTTP2 Protocol
Windchill RV&S supports the BEEP protocol for the Swing and CLI clients, and the HTTP and HTTP/2 protocols for the Web and Refreshed Web Interface clients (browser-based).
Windchill RV&S 13.1 onward, the HTTP/2 (or HTTP2) protocol is supported for Swing and CLI clients.
HTTP2 protocol is not supported for the following:
Swing and CLI clients of versions earlier than 13.1.
Windchill RV&S Agent of the current or previous versions.
Configuration Management features (server, proxy, and client).
To use HTTP2 protocol with Swing and CLI clients, the administrator must configure the appropriate settings on the server and on the client. HTTP2 is used only if the Windchill RV&S environment is set up in secure mode.
Enabling the server for HTTP2
To enable the server for HTTP2 requests, ensure that the following property is present in the is.properties file:
mksis.http.protocol.upgrade=true
This property ensures that browser-based clients connect to the server over HTTP2.
To enable the server for HTTP2 requests, ensure that the following property is added in the is.properties file:
mksis.rmi.transport=http
This property ensures that the Swing and CLI clients connect to the server over HTTP2.
* 
If you intend to use HTTP2 protocol, all servers across deployments (including staging servers), must be configured for HTTP2. Mixed mode protocol configuration is not supported.
For the Swing and CLI clients, mksis.http.protocol.upgrade=false and mksis.rmi.transport=http is not recommended.
If mksis.rmi.transport=http is not present, the Swing and CLI clients will use the default non-HTTP protocol.
Enabling the client for HTTP2
To use the HTTP2 protocol with the Swing and CLI clients, in addition to the server-side changes, the following property must be added to the IntegrityClientSite.rc file:
IntegrityClient.rmi.transport=http
Administrators must ensure that the updated properties are present in the IntegrityClientSite.rc file, that can be used for a manual update, or included in the silent install. For information on silent install, see Using Silent Install.
* 
When the Swing or CLI clients are launched, the Windchill RV&S server checks the protocol of the clients. If the Windchill RV&S server detects that a client is using a different protocol than the server, the user is prompted to close the client to automatically change the protocol on the client side, and to restart the client.