In the new machine:
Make sure the new machine has been configured properly according to the
"Pre-installation requirements" document:
- Create a new Oracle account and set the proper Connect tablespaces. This
temporary account will be used to install Connect in the new machine. This
account cannot be the same one currently used by the working cluster.
- Make sure you can connect through sqlplus to both the new account and the
account currently being used by the working system.
- Install the Application Server in the new machine.
- Install Connect in the new machine using the temporary database account (created
in point 2).
- Start the Application Server and make sure Connect’s UI is accessible. Do NOT
create a new deployment yet. Simply ensure the UI is up and running.
- Log off from Connect and close the web browser.
- Stop Application Server.
- Change the “connection string” in the database.properties in the install
directory of the new machine and replace the temporary Oracle account
information with the current account being used by the working system.
In the current working cluster:
- Prepare a list of the system parameters that reference the install machine, if
any (Event Listener Domain Name | Network | Normal Access, for instance).
- Stop the system (see more details in the document called “Updating Connect:
Automated Guide”):
- Flush the system
- Stop Connect
- Clean storage
- Stop Application Server
- Stop the CRMMonitor services in all machines
Make a backup of the database.
In the new machine:
- Start the application server in the new machine
- Change the value of the system parameters detailed the list prepared previously,
if any
- Create a new deployment using a different deployment directory and launch the
system (see more details in the document "Connect 6: deployment
guide"):
- Open a new browser window and access Connect’s UI
- Create and activate a new deployment though the UI using a different deployment
directory
- Start the nodes through the UI
- Disable flushing in the new deployment
Note: To keep the current Connect log files, copy the contents of the kc\logs directory from
the old install directory to the new machine before bringing the system up (point 6). If
both machines have the same name, then points 3 and 7 are not necessary.