Update v36.2¶
Complete the following steps before deploying Insight v36.2.
Update Java and WildFly¶
Update the runtime used by Insight Middleware and all custom WildFly-based images:
- Install JDK 25 for non-containerized Insight Middleware deployments and update
JAVA_HOME. - Update custom WildFly-based images to use WildFly
41.0.0.Final-jdk25. - Rebuild and test custom extensions and deployment overlays with JDK 25 and WildFly 41.
Update Groovy Dependencies¶
For custom extensions, scripts, and dependency constraints:
- Update dependencies from Groovy 3 to Groovy 5.
- Replace the former Maven group ID with
org.apache.groovywhere applicable. - Rebuild and test Groovy-based integrations before deployment.
Upload v2 Configurations¶
After updating to v36.2, upload all required v2 configurations once with the Insight CLI. This is required because v2 configurations are loaded from the SchemaDB of the Insight Middleware and must be available there.
Configure Role Replication¶
Role replication is mandatory with v36.2.0. Configure
roles.replication.type explicitly through v36.2.8; from v36.2.9, the default
is derived from eam.type. See the role replication guide
for the default mapping and configuration details.
Update the Insight Connector¶
Update the Insight Connector for v36.2 before deploying Insight v36.2. The
Maximo-Connector 36.2.1 includes a breaking change to attribute.options.hint.
See the compatibility matrix for the required
connector version and change details.
Update the Insight CLI Endpoint¶
Configuration uploads now use the application URL, including the /insight
path, rather than a direct server connection on port 8080. Update the
INSIGHT_URL environment variable and the Insight CLI --url argument.
See configuration parameters.