NOTE:The instructions in this section assume that your Vibe deployment uses MySQL as the database server. If you use another SQL database, you will need to adjust the steps to fit your deployment.
On the target server:
Install the Vibe 4 software on the target server, as described in Section III, Single-server (Basic) Installation, paying special attention to these important details:
Set up the same Linux user to run the Vibe software that has been used to run the Vibe software in the source Vibe server.
Select the same encryption algorithm for the Vibe database that was used for the source Vibe server.
IMPORTANT:If the database encryption algorithms do not match between the source and target Vibe systems, you cannot log in to the new Vibe 4 site.
Start Vibe on the target server.
Verify that the new Vibe site is working as expected.
Stop Vibe on the target server.
Rename the teaming directory to teaming_backup. In a future step, you will copy the teaming directory from the source server to the target server.
The location of the teaming directory varies by platform:
Linux: |
/var/opt/novell/teaming |
Windows: |
c:\novell\teaming |
Continue with Preparing the Source Linux Server for the Data Transfer.
On the source server:
Stop Vibe.
Back up your existing database:
mysqldump -uusername -ppassword sitescape > sitescape.sql
This creates a file named sitescape.sql in the directory where you executed the mysqldump command.
Ensure that you have a recent backup of your entire Vibe system.
Continue with Transferring Data from the Source Server to the Target Server.
On the source server:
Mount the target server to the source server so that data can be copied from one server to the other.
In a terminal window on the source server, become the Linux user that runs the Vibe software.
Copy the database backup of your existing Vibe database (sitescape.sql file) that you created in Step 2 in Preparing the Source Linux Server for the Data Transfer to a convenient temporary location on the target server.
Copy the entire data area from /var/opt/novell/teaming on the source server to the same location on the target server.
(Conditional) If you are using secure LDAP (LDAPS), you need to copy the cacerts file to the same location on the target server.
Edit the /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties file on the target server to include the same content as the corresponding file on the source server, as follows:
Make sure that the user.pwdenc.default=PROPERTY-VALUE values are the same in the ssf-ext.properties files on both servers.
Copy the following property values in the ssf-ext.properties file on the source server and replace the corresponding property values on the target server with the source server values.
NOTE:We recommending pasting to avoid typing errors.
database.password=PROPERTY-VALUE
mail.SiteScape.out.password=PROPERTY-VALUE
smtp.service.keystore.password=PROPERTY-VALUE
kablink.encryption.key=PROPERTY-VALUE
kablink.encryption.key.initial=PROPERTY-VALUE
Save the modified ssf-ext.properties file on the target server.
Continue with Re-creating Your Source Vibe Database on the Target Server.
On the target server:
Remove the empty Vibe database that was created when you installed the Vibe 4 software:
mysql>drop database sitescape;
Change to the directory where you copied the sitescape.sql file in Step 3 in Transferring Data from the Source Server to the Target Server.
Create an empty database called sitescape:
mysql -uusername -ppassword -e "create database sitescape character set utf8"
Manually re-create the Vibe database with the data that you copied from the source server:
mysql -uusername -ppassword sitescape < sitescape.sql
Start Vibe 4, as described in Starting Vibe on Linux.
Reindex the Vibe site, as described in Rebuilding the Lucene Index
in Site Maintenance
in the OpenText Vibe 4.0.8 Administration Guide.
Your Vibe site should now function just as it did on the original source server.