Whether you are updating from a major release such as Mobility Pack 1.2 or a minor release such as Mobility Pack 1.2.x, the procedure is the same.
NOTE:If you prefer not to receive minor updates through the Novell Update channel of the Novell Customer Center, you can use the same procedure to install the minor update that you used to install the last major update.
Log in to the Novell Customer Center.
In thedrop-down list, select your organization that is entitled to the Mobility Pack.
Click, then click .
Under, locate , then make a note of the activation code in the field.
In a terminal window on the Synchronizer server, enter the following command:
suse_register -a regcode-mobility=registration_code -a email=email_address -L /root/.suse_register.log
Replace registration_code with the Mobility Pack activation code that you obtained from the Novell Customer Center in Obtaining the Mobility Pack Activation Code from the Novell Customer Center. Replace email_address with the e-mail address that you used to log in to the Novell Customer Center. Notifications about future Mobility Pack updates will be sent to this e-mail address. You can then choose when to install each minor update.
Enter the following command to verify that the Novell Update channel for the Mobility Pack has been added on your Synchronizer server:
This command lists all product-specific channels where you are registered to receive updates. The following Mobility Pack update channel should be listed:
Continue with Applying a Minor Update to the Synchronizer Server.
Enter the following command:
zypper up -r nu_novell_com:Mobility-1.2-Updates
Several Mobility Pack packages are listed for update through the channel.
Enter YES to start the update process.
Continue with Running the Mobility Pack Update Script
Running the Update script updates the Synchronizer database (datasync) and the Mobility database (mobility) for use with the updated software.
Change to the following directory:
Make sure that PostgreSQL is running:
Execute the Update script:
For some version updates, the update process finishes quickly. However, when the version update includes database schema modifications, the update process can be lengthy for a large database.
Continue with Restarting the Synchronizer Services.
Stop the Synchronizer services:
Verify that all Synchronizer services have stopped:
ps -eaf | grep datasync
Start the Synchronizer services: