In <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.pairing.agent.cfg, remove the value of the remote.engine.id property.
Delete the <RemoteEngineInstallationDirectory>/data/cache directory.
Re-pair the engine
Choose one of the following methods to re-pair your engine.
Using the web configuration interface:
Launch the Talend Remote Engine console on your machine (trun.bat).
In a browser, open http://localhost:8043/configuration.
Paste the new preauthorization key in the key field.
Enter your deployment region if prompted.
Click Pair Remote Engine.
In the engine console, type list then press Enter.
All bundles display as Active when re-pairing is successful.
Using the configuration file:
Use this method for headless or CLI-only environments. The engine must remain stopped while you edit the file.
In <RemoteEngineInstallationDirectory>/etc/preauthorized.key.cfg, update the remote.engine.pre.authorized.key property with the new preauthorization key.
Start the engine by launching the Talend Remote Engine console (trun.bat).
In the engine console, type list then press Enter.
All bundles display as Active when re-pairing is successful.
Results
Your Remote Engine is now paired. The status updates to Paired in
Talend Management Console.
To run tasks with this engine, ensure you have the Operator
(Execute) right on the space where the engine is located.
If you need to know the Java version used by the engine, click the
Configuration tab in the Engine details
blade. There you can see the version Talend Remote Engine is
using for start and also the Java version it uses to run tasks and plans. Note that by
default, Talend Remote Engine uses
the Java it starts with to run tasks and plans.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!