We currently have a Domino 12 Server with Enterprise Integrator (v12) installed.
recently created a new server to replace the above server which is Domino 14.5 with Enterprise Integrator (v14.5) installed.
Can I copy the Activity and Connection documents from the “HEI Administrator” V12 Server Database to the “HEI Administrator” V14.5 Server Database or do I have to recreate the document in the V14.5 database?
Yes, rather than an ad-hoc copy of documents, which may omit critical profile data and configuration metadata, you should migrate the HEI Administrator database file directly and refresh the design to v14.5.
It is also vital to account for the transition to a 64-bit environment. Any ODBC or native client connections (Oracle, DB2, etc.) previously configured for 32-bit on your v12 server will require the installation of corresponding 64-bit drivers on the new server to ensure connectivity within the Domino 14.5 runtime.
Just a stupid question: Is there a reason why you created a new server instead of updating the existing one in place? That could have saved you a ton of work…
Even if it is a new operating system, it can be “in place”:
stop and disable Domino service on old server
copy Domino program and data directory to new server
start setup of new version, select the same program and data directory
Sorry for the delayed response. Much has been happening.
We created a new server due to random issues with the old one. It had many legacy settings that would take time to review. We wanted a clean start with a new server (OS & Domino). The new server is configured with all appropriate ODBC connections, JAR files, and more.
I was hoping we could copy documents from the V12 HEI Administrator Database to the V14.5 HEI Administrator Database.
I submitted a Support Ticket and got the following reply.
“The answer to your question is yes, you can copy your connection and activity documents from your 12 admin to your 14.5 admin. As a matter of fact when I am assisting a customer where we are moving HEI to a new server, I always recommend to do a clean install on the new server and then just copy over the connection and activity documents. We only want to copy the connection and activity documents and not any of the server documents. The server documents are unique for each server and we can get into trouble copying those from a different server.”
I will try this on Monday and let you all know how it goes.
I agree. It’s better to make a new HEI server and you will have a new server docs and HEI server name. Assuming your new server has a different HEI server name, once you copy the Activity docs, you will need to update the HEI server name on them to the new name. That was the only thing I had to do once I copied-n-pasted the documents from the old server to the new server. You can manually change each doc or write a simple agent.
The reason to make a new server is so you can run in parallel. I like having a new server and them move an Activity to it (and the related Connections) and then disable the activity on the old server. If there are issues running the activity on the new server, you can go to the old server and manually run that Activity until you get everything working on the server. Using this process is also a great time to cleanup. Don’t move Connection or Activity docs to the new server that are no longer used.
the job won’t execute if you don’t have the correct HEI server chosen. When it is time to run the Activity, and it is not set to the current HEI server, it will throw an error to the log that it can’t run the activity on this server, or something to that affect.
You can manually update that field by editing the activity and changing the “Designated Server” to the correct HEI server name. When you manually do this, you should only see options for the new HEI server you configured.
once you know it works to manually update it, if you have many activities to update, you can write an agent to update the “DesignatedServer” field.