Roll back Java operation
Use the Roll back Java operation to programmatically return a runtime, Runtime cluster, Runtime cloud, Authentication Broker, or Gateway to use the previous version of Java with an EXECUTE operation.
You must have the Runtime Management privilege to use the Roll back Java operation to update any and all containers.
Structure
<JavaRollback atomId=""/>
| Field | Type | Description |
|---|---|---|
| atomId | string | The unique ID assigned by the system to the container. 1. Use the Runtime ID for Runtimes, Runtime clusters, and Runtime clouds found in the user interface by navigating to Manage > Runtime Management and viewing the Atom Information panel for a selected container. 2. Use the Gateway ID found in the user interface by navigating to Configure Server > Gateways > <gatewayName> > Gateway Information panel. 3. Use the Broker ID found in the user interface by navigating to Configure Server > Authentication > <brokerName > Broker Information panel. |
Supported operations
| GET | QUERY | CREATE | UPDATE | EXECUTE | DELETE |
|---|---|---|---|---|---|
| Not supported | Not supported | Not supported | Not supported | supported | Not supported |
Using the EXECUTE operation
-
After performing the EXECUTE operation, you can determine the success of returning to earlier version when the Update to use <new Java version>.<minor_version> link displays on the following pages, indicating that a more recent version is available for upgrade:
- For Runtimes, Runtime clusters, and Runtime clouds — the Atom Information panel (Manage > Runtime Management of the user interface).
- For Brokers — the Broker Information panel (Configure Server > Authentication of the user interface).
- For API Gateways — the Gateway Information panel ( Configure Server > Gateways of the user interface). To verify a successful rollback on a Runtime using the user interface, you can also navigate to Runtime Management > Startup Properties and reference the Java version number listed in the Java Home field.
-
The container must be online to use the Roll back Java operation.
Only the node that runs upgrades (typically the head node) restarts automatically to run the updated Java version for Runtimes, Runtime clusters, and Runtime clouds. You must restart all other cluster nodes to return to a previous version of Java successfully.
For API Management Gateways and Authentication Brokers, you must restart all Gateways and Brokers to return to a previous version of Java successfully.
SOAP implementation
CREATE operation
Sample SOAP request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:api="http://api.platform.boomi.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>user@boomi.com</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password1234</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<api:execute>
<api:objectType>JavaRollback</api:objectType>
<api:objectId>1cbba234-56b7-82d9-0123-f4c5c6789d01</api:objectId>
<api:object xsi:type="api:JavaRollback" atomId="3456789a-bcde-f012-3456-789abcdef012"></api:object>
</api:execute>
</soapenv:Body>
</soapenv:Envelope>
Sample SOAP response:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<bns:executeResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:bns="http://api.platform.boomi.com/">
<bns:results xsi:type="bns:JavaRollback" atomId="3456789a-bcde-f012-3456-789abcdef012"/>
</bns:executeResponse>
</S:Body>
</S:Envelope>