Migrate from web container mode to standalone mode
An IG .war file isn’t created or delivered from IG 2024.3. Consider these points when migrating from a .war delivery to a .zip delivery.
Session replication between IG instances
High-availability of sessions isn’t supported by IG in the .zip delivery.
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 can’t be reused.
If the property is set to false
, the setting is ignored.
Replacement settings for migration from web container mode with Tomcat
Feature | Setting for web container mode with Tomcat | Replacement setting |
---|---|---|
Port number |
Configure in the
|
Configure the |
HTTPS server-side configuration |
Create a keystore, and set up the SSL port in the |
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). |
Session cookie name |
Configure |
Configure the |
Access logs |
Configure with |
Configure in the Audit framework. For information, refer to Audit the deployment and Audit framework. |
JDBC datasource |
Configure in the |
Configure with the JdbcDataSource object. For information, refer to JdbcDataSource. For an example, refer to Password replay from a database. |
Environment variables |
Configure in |
Configure in |
Jar files |
Add to to web container classpath; for example
|
Add to |