NOTE:The instructions in this section assume that your Vibe deployment uses MS SQL 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, as described in Section III, Single-server (Basic) Installation.
IMPORTANT:Select the same encryption algorithm for the Vibe 4 database that you selected for the source Vibe server. If the database encryption algorithms do not match between the source and target 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:\Program Files\Novell\Teaming |
Continue with Preparing the Source Windows Server.
On the source server:
Stop Vibe.
Back up your existing database:
In Microsoft SQL Server Management Studio, browse to and right-click the existing database (named sitescape), then click Tasks > Back Up.
For Backup type, select Full.
Set other backup options as desired, then click OK.
This creates a file named sitescape.bak in the following directory:
c:\Program Files\Microsoft SQL Server\MSSQL\Backup
Ensure that you have a recent backup of your entire system.
Continue with Transferring Data from the Source Server to the Target Server.
On the source server:
Map a drive from the target server to the source server so that data can be copied from one server to the other.
Copy your existing software extensions to the target server:
From: |
c:\home\icecoredata\extensions |
To: |
c:\novell\teaming\extensions |
Beginning with Vibe 3, the extensions directory now contains kablink and liferay.com directories.
Delete the empty kablink directory.
Delete or rename the following directories to make room for the corresponding directories that you are copying from the source server:
c:\novell\teaming c:\novell\teaming\lucene c:\novell\teaming\extensions
Copy the entire data area from c:\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 C:\Program Files\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 Importing the Database to the Target Server.
On the target server:
In Microsoft SQL Server Management Studio, browse to and right-click the existing Vibe database (named sitescape) that was created when you installed the Vibe 4 software, then click Delete.
To import the data from your source database, browse to and right-click Databases, then click Tasks > Restore.
In the To database field, specify sitescape.
In the From device field, browse to and select the sitescape.bak file that you transferred to the target server.
Set other restore options as desired, then click OK.
This creates the sitescape database in the following directory on the target server:
c:\Program Files\Microsoft SQL Server\MSSQL
Backed-up data from the source database is imported into the database for your new Vibe 4 system.
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.