Here is the procedure, at a high level, for migrating processes from one atom/molecule to another.
The following instructions assume that you have environments, with extensions enabled on your account. If not, work with a Support Team member to discuss alternative steps if necessary
1.) Engage the Dell Boomi Support Team by creating a support case.
During the migration, you will be attaching your processes to both the old and new Atom. This may require additional licenses, which will be provided for a pre-defined time period during the migration
The Support Team representative, will work with your Account Executive, to allocate free, temporary licenses, for use during this migration.
Discuss with the Support Team member and the Account Executive, how long a period of time you need to complete the migration. The support team will schedule time at the end of that period, to work with the Account Executive to create a second opportunity to deprecate/deactivate those licenses.
3.) Configure new atom or molecule:
You may need to import Java certs into new JRE keystore.
You may need to install Unlimited Strength Cryptography files
You should check container.properties, vmoptions, and other molecule related settings
You should also check web server settings from Atom management.
Note: If new atom is on the same server, you must use a different port within web server settings
4.) Custom Scripts / Drivers / userlib:
If any of your processes use custom scripts or drivers, the contents of the "userlib" folder must be migrated to the new atom.
In many cases the files may be copied, but if you are changing OS, or architecture, you may require new jar files or drivers to meet the new system's requirements
5.) Attach the new Atom to the existing environment
From Atom Management, select environment, select Extensions
Enter values for all passwords
7.) To Migrate Schedules:
Deploy the new process to any atom.
Use the GET Process Schedules object to pull the current schedules from the current atom and use the UPDATE to pass this information to the new atom.
Confirm schedules have been copied to new atom, but have not yet started.
8.) Deployment History:
Because you are attaching to the same environment, your deployment history will be carried over automatically
9.) Process Properties, EDI Sequence #s, CDC data:
You may choose to migrate all processes at once, or one at a time, to allow for testing/validation of the new atom.
For each ( non-listener ) process you wish to move:
a.) Stop the schedules for that process on old atom
b.) Process Properties:
In order to preserve "Last Successful Run Date" and other persistent process properties:
Copy the "execution/<component_id>.properties" file from old atom to new.
c.) Counters / EDI Sequence #s / etc
Copy the "counters/<component_id>" folder from old atom to new.
d.) Find Changes
Copy the "work/cdc/<component_id>" folder from old atom to new
e.) Start the schedules for that process on new atom
10.) Listener processes ( HTTP Server, AS2 listener, etc ):
For listener processes, you may test the new listeners, by using the port defined on the new atom in Web Server settings.
If you are directing client requests to your service via a router configuration, you may simply be able to re-route those requests to the new server/port.
If you are using an external load balancer, you may be able to redirect the requests using the balancer.
You may also choose to have your clients update their connection points to connect to your new servers.
Or, finally, you may choose to detach the old processes from the environment ( stopping the listeners ), and then change the web server settings on the new atom to the old port number.
11.) Execution History
For simplicity, execution history will not be copied to the new atom. If information is required for past executions, you must query process reporting for the atom where the execution took place
12.) Once the migration is complete, and all processes and listeners are now running on the new atom
Detach the old atom from the environment.
Your account owner, will then remove the temporary licenses from your account.
You may then consider uninstalling the old atom.