Is there any way to add a local atom to a new account?
You mean to say migrate the existing atom to the new account? OR Creating a new atom in the new account?
We can do both. We can create a new atom in the new account. We can also migrate the atom from one account to other account.
Michael Morthala - Actually that is not correct: you cannot move atoms between accounts. Atoms are tied to a single account, using the account-specific keystore for encryption, etc.
You would need to install a brand new atom associated with the new account.
I can understand why there is a need for a handshake, key exchanges and the like, but I'd have thought that you'd want to be able to attach a local atom to a new account, if you wanted to?
So the same process as creating a new one - get the token - and associate it to the new account, but without having to do a fresh install?
Anyway, my question is answered.
Thanks for correcting me Adam Arrowsmith. But to what we could migrate an atom?
In the online training: Architect 3 - 2 - Operational Management, it does have:
Moving an AtomReasons:• New hardware / hardware upgrade / hardware failure• Different Atom installation directory, resource with more disk space•In general, don’t move an atom, create a new Atom in the new server,then migrate process from one to the other.– Do NOT duplicate Atoms by copying the installation from one machine to another or image a machine for use on another server. If you must copy a server image or atom installation, you must not start both atoms at the same time. You SHOULD delete the atom installation of the unused installation once the migration is complete.– Note: If you are creating an exact mirror of the current machine/VM, you shouldonly need to verify settings vs. changing values.
the following 3 slides discussed moving it a different folder on same server, and changes related to java and web services.
fwiw, there was a sample in the Process Library for moving schedules...
Retrieving data ...