Updating the version of your integration runtime
The IBM product team controls the operator version for App Connect Enterprise as a Service. If you're on the VPC hours plan, you can choose the modification release version of your integration runtimes.
About this task
- Operator version
- IBM controls and updates the operator version of App Connect
Enterprise as a Service,
which is based on the version of IBM® App Connect Enterprise (for example, version
13.0). If you select the operator version for your runtime, rather than a specific modification
release, the latest modification release is used.
To find out how the release of App Connect Enterprise 13.0 affects you, see Upgrading to version 13.0.
- Modification releases
- The operator version supports the current and previous modification releases (for example, 13.0.5 and 13.0.4), which contain new features and bug fixes. If you're on the VPC hours plan, you control which of the two available modification release versions your integration runtimes use. You can find out which features are added in modification releases in New functions added in IBM App Connect Enterprise Version 13.0 modification packs in the App Connect Enterprise documentation.
- Fix pack releases
- IBM releases security updates in fix packs (for example, 13.0.2.4). The fix pack version of your runtime is updated automatically and because fix packs contain essential security updates, you can't select a particular fix pack release.
The operator version of App Connect Enterprise as a Service always supports the two most recent modification releases. When a new modification release is added, the oldest modification release is removed. IBM publishes a notification before the modification release is updated so that you can plan to update your runtimes. When the IBM product team updates the operator or modification release version, the versions of all integration runtimes are checked. If the version of the integration runtime is behind the minimum supported version for the operator, the integration runtime version is updated to the minimum supported version. If you don't need to control the modification release version of your integration runtime, you can choose the operator version instead (for example, version 13.0). If you choose the operator version, your integration runtime is updated automatically to the latest modification release version when it's available.
When you create in integration runtime, you choose the version, but you can edit the runtime to change its version at any time. To change the version of an integration runtime, complete the following steps.
Procedure
- Go to the Manage page, then click Integrations.
- For each runtime that you want to update, open the tile menu and click Edit.
- Select the new version for your integration runtime.
- Click Save changes.
Results
Upgrading to version 13.0
About this task
- If you're on the flow runs plan, your instance is updated automatically to use version 13.0.
- On VPC hours and flow runs plans, the default integration runtime that is used to test event-driven and API flows in App Connect Designer is also updated automatically to version 13.0.
| Modification release | Estimated end of support |
|---|---|
| 12.0.11 | December 2024 |
| 12.0.12 | March 2025 |
| 13.0.1 | March 2025 |
- Default JRE version
- The default JRE version for App Connect Enterprise 13.0 is IBM Semeru Java™ 17. Java 17 doesn't
support the following features.
- Web Services Security (WS-Security)
- WS-Trust
- Integration with Tivoli Federated Identity Manager (TFIM)
- Message flows that use the global cache
- Message flows that contain CORBA nodes.
- DataDirect supported cipher suites
- For a list of SSL encryption cipher suites that Progress DataDirect ODBC drivers support, see SSL encryption cipher suites in the Progress documentation.
- IBM Semeru Runtimes
- For a list of changes to SSL handling in Java 17, see the IBM Semeru Runtimes security migration guide. The guide describes changes
when you migrate to version 11 of the IBM Semeru Runtimes but also applies to version 17. The
changes apply to the following message flow nodes.
- CD Input and Output nodes
- CICS Request node
- CORBA Request node
- Database Retrieve and Route nodes
- Email Input and Output nodes
- Endpoint Lookup node
- HTTP Request, Async Request, and Async Response nodes
- IMS Request node
- Java Compute node
- JDEdwards Input and Request nodes
- JMS Input, Output, Receive, and Reply nodes
- Kafka Consumer, Producer, and Read nodes
- Kerberos node
- LDAP node
- Mapping node
- MQTT Publish and Subscribe nodes
- ODM Rules node
- PeopleSoft Request and Response nodes
- Registry Lookup node
- REST Request, Async Request, and Async Response nodes
- Salesforce Request node (no discovery)
- SAP Input, Reply, and Request nodes
- Security PEP node
- Siebel Input and Request nodes
- SOAP Reply, Request, Async Request, and Async Response nodes
- TCPIP nodes
- TFIM node
- JSON parser settings
- The values for some JSON parser settings are changed in the default
server.conf.yaml file that is created when you create an integration server in
App Connect Enterprise 13.0. The following values now override JSON parser behavior.
allowScientificNotation: falsenumberPrecisionType: decimal
Following these changes, the JSON parser has the following default behavior.- The parser parses all incoming numbers that contain decimal points into a DECIMAL type in the message tree instead of a FLOAT type.
- The parser serializes all FLOAT values in the message tree as decimals (for example, 0.02) instead of scientific numbers (for example, 2E-2).