Updating the Rosetta System

Verifying your Rosetta Server Version

Basic information about the version and role(s) of Rosetta running on your server can be retrieved from the shell using the ver command:

il-dps01-d4(1) >>ver

Hostname : il-dps01

Rosetta Server Status : UP

Application role : DEP,REP,DEL,PER,IDX

Rosetta Ver Server Name Server Role Build Date Build Number Rank

----------- ----------- ----------- ---------- ------------ ----

4.0.0 il-dps01.corp.ex DEP,REP,DEL, SATURDAY 33045 (115) 1

librisgroup.com PER,IDX NOVEMBER 23,

2013

pds version : 2.0.1.00001 , (ACTIVE)

For extended information, run ver_full.

Service Pack Installation

For information on installing service packs, see the Rosetta Service Pack Installation Guide in the Installation and Implementation Information directory of the Rosetta customer portal.

Hot Fix Installation

This section explains how to install a hot fix for Rosetta.

Rosetta hot fixes are cumulative rather than incremental. For example, 3.1.2.2 includes 3.1.2.1. Please note that rolling back two or more consecutive hot fixes cannot be done. If there is a need to reverse changes applied by two or more consecutive hot fixes, please contact Rosetta Support.

Information about post-installation sanity tests is not included here.

The following terms are referred to in this segment:

Distributed topology: two or more “all-in-on” application servers
Distributed roles topology: two or more applications servers, each having a different role (for example, deposit, staging repository, or permanent repository)

Installing a Rosetta Hot Fix

Before installing a Rosetta hot fix, back up your Rosetta database using your tools/policies.

To install a Rosetta hot fix (repeat for every server):

Download .tar.gz from the Ex Libris MFT:

util sp

[6] Download Hotfix

You can view the download directory from:

util sp

[1] Customer details

Extract the hot fix:

cd put_Download_directory_here

mkdir hf_7101

tar -C hf_7101 -zxf Rosetta_7_1_0_1.tar.gz

Stop Rosetta:

dps_stop

Install the hot fix:

cd hf_7101
csh -f install_hf.csh

Start Rosetta:

dps_start

In a distributed roles topology, run the script on each of the servers. Note that the script can be run consecutively or concurrently on all servers.

While the hot fix is being installed, a log file is written. The full log file can be found at /exlibris/dps/d4_1/local_sp_install/5.3.0.1/log/install_sp.log.

Rolling Back the Hot Fix Installation

If you must roll back to the previous version, use the following commands:

cd hf_for_v<Rosetta_version>

csh -f rollback_hf.csh

In a distributed topology, repeat these commands for each of the servers .

Restarting Rosetta

Once you have successfully installed the hot fix, restart Rosetta using the dps_start command. In a distributed topology, run this command on each of the servers.

Copying Rosetta System Configurations

The Copy Configuration feature reduces manual work when configuring the same settings in a newly installed environment as in an existing one.

Not all configuration items can be automatically copied. For example, specific environment variables such as IP addresses or NFS paths cannot be copied without causing errors.

Copy configuration is performed at the consortial level. All items from all institutions including the consortium hierarchy are copied.

The following sections include a description of the items that can be copied as well as instructions for performing the copy and transfer of configuration data.

Items Copied in Copy Configuration

Repository
- Task Chains
- SIP Processing Configuration
- Storage Definitions
- Plug-In Instances
Users And Deposit
- Users
- Producers
- Producer Profiles
- Metadata Profiles
- CSV Templates
- Content Structures
- Submission Formats
- Metadata Forms
- Material Flows
Administrative Structure
- Administrative Structure
- UI Customization
Delivery
- Viewers
- Representation Profiles
- Delivery Rules
- Generic Thumbnails
Metadata
- Shared Metadata
- History
General
- General Parameters
- Authentication Profiles
- Transformation Profiles
- Configuration Files
- Quartz Jobs
Code and Mapping Tables
- Code and Mapping Tables
Rules
- Rules

Implementing the Copy Configuration

The Copy Configuration feature is available by clicking General in the Administration module (consortium level). Two options are available from this page, Export Configuration and Import Configuration. Typically, a workflow begins with exporting a configuration, then importing it to a new environment.

To export a configuration:

From the Administration page, under System Configuration > Copy Configuration, click Export Configuration. The Export Configuration page opens.

Export Configuration Page

Click the Export button to continue.
A progress bar is displayed as the export runs. The system creates a file containing the entire configuration. This step may take several minutes, depending on the size of the configuration. The file name containing the exported configuration is <YYYY-MM-DD hh-mm>.zip and is saved locally on the server under …/operational_shared/cc_export_dir/.
If necessary, copy the .zip file to a PC that can access the importing environment.

Do not open or edit the .zip file. Any changes to the file will hinder your success when importing.

To import a configuration:

Confirm that:

the importing system and the exporting system have the same Rosetta version and the same format library. To check which Rosetta version is installed, click the Help link in the upper right corner of the Web page and then About Rosetta. To check the format version, select Preservation > Manage Format Library Version.
the importing environment is clean, without any data.
all NFS storage locations are available and empty.

Log in to the administration module and follow the path System Configuration > Copy Configuration and click Import Configuration. The Import Configuration Page opens.

Import Configuration Page

Click the Browse button and navigate to the exported configuration .zip file you want to import. Select the file and click Open.
The file path and name populate the Select the file you previously exported field.
Click the Import button.
The system imports the configuration. This may take a few minutes. When finished, a confirmation message appears.
Restart Rosetta and perform a sanity test to verify a successful import.

The following activities must be performed manually:

Copy the plug-ins jars (before the restart).
Align NFS path definitions (for example, operational shared paths, submission formats, and quartz jobs parameters).
Fix S3 storage definitions.
Add (S)FTP passwords.
Add logos to UI customizations.