Migrate from web container mode to standalone mode
Consider these points to migrate from IG in web container mode to IG in standalone mode.
Streaming asynchronous responses and events
In ClientHandler and
ReverseProxyHandler,
use only the default mode of asyncBehavior:non_streaming
; responses are
processed when the entity content is entirely available.
If the property is set to streaming
, the setting is
ignored.
Connection reuse when client certificates are used for authentication
In ClientHandler and
ReverseProxyHandler,
use only the default mode of
stateTrackingEnabled:true
; when a client certificate is used for
authentication, connections cannot be reused.
If the property is set to false
, the setting is ignored.
Tomcat configuration
Feature | Standalone | Tomcat |
---|---|---|
Port number |
Configure the |
Configure in the
|
HTTPS server-side configuration |
Create a keystore, set up secrets, and configure secrets stores, ports, and ServerTlsOptions in admin.json. For information, refer to Configure IG for HTTPS (server-side). |
Create a keystore, and set up the SSL port in the For information, refer to Configure IG for HTTPS (server-side) in Tomcat. |
Session cookie name |
Configure the |
Configure |
Access logs |
Configure in the Audit framework. For information, refer to Auditing your deployment and Audit framework. |
Configure with |
JDBC datasource |
Configure with the JdbcDataSource object. For information, refer to JdbcDataSource. For an example, refer to Password replay from a database. |
Configure in the |
Environment variables |
Configure in |
Configure in |
Jar files |
Add to |
Add to to web container classpath; for example
|