Migration to IG in Standalone Mode
IG is delivered as a standalone Java executable in a .zip file, as well as in a .war file. Consider these points to migrate from IG in web container mode to IG in standalone mode.
- Session replication between IG instances
-
Use only stateless sessions, as described in Sessions. Stateful sessions are not supported.
- Streaming of 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 tostreaming
, the setting is ignored. For information, see ClientHandler and ReverseProxyHandler. - Connection reuse when a client certificate is 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 tofalse
, the setting is ignored. For information, see ClientHandler and ReverseProxyHandler. - Tomcat configuration alternative
-
- Port number
-
-
Standalone: Configure the
connectors
property of$HOME/.openig/config/admin.json
, where$HOME/.openig
is the instance directory. For information, see AdminHttpApplication (admin.json). -
Tomcat: Configure in the
Connector
element of/path/to/tomcat/conf/server.xml
:<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />
-
- Configuring IG for HTTPS server-side
-
-
Standalone: Create a keystore, set up secrets, and configure secrets stores, ports, and ServerTlsOptions in
$HOME/.openig/config/admin.json
, where$HOME/.openig
is the instance directory. For information, see Configure IG For HTTPS (Server-Side) in Standalone Mode. -
Tomcat: Create a keystore, and set up the SSL port in the
Connector
element of/path/to/tomcat/conf/server.xml
. For information, see Configure IG for HTTPS (Server-Side) in Tomcat.
-
- Session cookie name
-
-
Standalone: Configure the
session
property of$HOME/.openig/config/admin.json
, where$HOME/.openig
is the instance directory. For information, see AdminHttpApplication (admin.json). -
Tomcat: Configure
WEB-INF/web.xml
when you unpack the IG .war file.
-
- Access logs
-
-
Standalone: Configure in the Audit framework. For information, see Auditing Your Deployment and Audit Framework.
-
Tomcat: Configure with AccessLogValve.
-
- JDBC datasource
-
-
Standalone: Configure with the JdbcDataSource object. For information, see JdbcDataSource. For an example, see Log In With Credentials From a Database.
-
Tomcat: Configure in the
GlobalNamingResources
element of/path/to/tomcat/conf/server.xml
.
-
- Environment variables
-
-
Standalone: Configure in
$HOME/.openig/bin/env.sh
, where$HOME/.openig
is the instance directory. -
Tomcat: Configure in
/path/to/tomcat/bin/setenv.sh
.
-
- Jar files
-
-
Standalone: Add to
$HOME/.openig/extra
, where$HOME/.openig
is the instance directory. -
Tomcat: Add to to web container classpath; for example
/path/to/tomcat/webapps/ROOT/WEB-INF/lib
.
-