Chapter 5 Migrating StarOffice 7 Configuration Data to the Java Desktop System Configuration Manager

This chapter describes how to migrate StarOffice 7 configuration data from the StarOffice Configuration Manager to the Java Desktop System Configuration Manager.

This chapter is only relevant if you currently use the StarOffice Configuration Manager to manage configuration data for StarOffice 7.

Overview of the Differences Between the StarOffice Configuration Manager and the Java Desktop System Configuration Manager

The StarOffice Configuration Manager can only manage configuration data for StarOffice 7. The Java Desktop System Configuration Manager can manage the configuration data forStarOffice 8 as well as other applications.

StarOffice configuration data is organized into keys. Each key represents a setting that affects the behavior of a StarOffice application. For example, a key can correspond to a setting that you customize in the Tools - Options menu of StarOffice.

You can use both configuration managers to centrally assign values to keys for specific entities in a Lightweight Directory Access Protocol (LDAP) repository. An entity is an element of the enterprise organizational structure. Both configuration managers can manage the following configuration data:

• Organizations

• Roles

• User entries

StarOffice Configuration Manager

The StarOffice Configuration Manager (SCM) allows you to set the StarOffice 7 configuration keys that are available for organization, user, and role entities in the LDAP repository. Settings that are customized by users in StarOffice 7 are also saved to the LDAP repository. The priorities that you assign to roles in the same organization determine the order in which the SCM applies the configuration data to StarOffice 7.

Java Desktop System Configuration Manager

StarOffice 8 uses the Java Desktop System Configuration Manager to manage configuration data for different applications. More specifically, the Configuration Manager provides policy-based configuration for desktop applications. A policy is a collection of configuration settings for an application that the Configuration Manager applies when you start the application. If you want, you can combine policies into a group for a set of applications. For example, you can use the Configuration Manager to define a policy group to configure StarOffice for novice users. The Configuration Manager supports the assignment of policy groups to the following entities:

• Organizations

• Users

• Roles

• Hosts

• Domains

You can define policy groups globally or directly for organizations, domains, users, or hosts. This centrally stored data is complemented by read-only default settings as well as user preferences that are stored on client machines. Priorities that you assign to global policy groups determine the order in which the policy data of the groups are accessed when you start the corresponding application.

Migrating Configuration Data From the StarOffice Configuration Manager to the Java Desktop System Configuration Manager

The SCM to APOC migration tool helps you to migrate StarOffice 7 configuration data from the SCM to the Configuration Manager. This tool converts SCM data that is associated with organizations, roles, and users into Configuration Manager policy groups. The Configuration Manager assigns these policy groups to the organization, rule, or user that held the SCM data.

Before you migrate your SCM configuration data, you need to prepare the LDAP repository that contains the data for use with Configuration Manager. See the Java Desktop System Configuration Manager Release 1.1 Installation Guide at http://docs.sun.com/app/docs. for details on how to prepare an LDAP repository for use with the Configuration Manager.

The SCM to APOC migration tool uses organizational mapping information from SCM to identify the entities that have been assigned SCM configuration data. The entities include organizations, users, and roles. For each organization and user entity, the tool creates a policy group that is local to the entity. The name of the group is taken from the name of the policy group of the default entity. For each role entity, the tool creates a global policy group with a generated display name. The tool also assigns a priority to the policy group to ensure that the groups have the same configuration precedence after the migration.

Migrating Users and Policy Groups

By default, the SCM to APOC migration tool only migrates SCM configuration data that is assigned to organizations and roles. User preferences, such as the list of recently opened files, are lost during the migration. Users need to reset these preferences after the migration. The tool does not overwrite policy groups that have the same name in the Configuration Manager repository.

The SCM to APOC migration tool provides command-line options to migrate user data and to overwrite existing policy groups. See Using the scm2apoc Command to Migrate Configuration Data for details.

Configuration data that is assigned to roles by SCM are converted by the SCM to APOC migration tool to global policy groups in Configuration Manager. The SCM to APOC migration tool uses the format SCM Migration <Role Name> <Identifier> to name the policy groups. The <Identifier> is an arbitrary integer that is used to avoid conflicts between different roles that have identical names.

The SCM to APOC migration tool creates new policy groups each time you run the tool in the same Configuration Manager LDAP repository. To prevent excessive accesses to the repository, delete the automatically generated policy groups before you run the tool again in the same repository.

Using the scm2apoc Command to Migrate Configuration Data

The scm2apoc command requires the following information from the SCM and Configuration Manager LDAP repositories:

• LDAP server name

• Port number

• Base DN

• Service entry

The following LDAP repository information is optional:

• Anonymous user connection

• User credentials to create and to assign policy groups

The syntax for the scm2apoc command is as follows:

scm2apoc <options>

-s <SCM parameters file>

File name path of the SCM access parameters file

In a standard SCM installation, the file name path of this file is <tomcat installation directory>/jakarta-tomcat-4.0.4/webapps/scm/WEB-INF/jproxy.cfg

-a <Configuration Manager file>

File name path of the Configuration Manager access parameters file

In a standard Configuration Manager installation, the name of this file is /usr/share/webconsole/apoc/WEB-INF/policymgr.cfg

-h <hostname>

Name of LDAP server host

-p <port>

Port number of the LDAP server

-b <base DN>

Base Distinguished Name of the LDAP server

-e <service entry name>

Name of SCM service entry

-D <user DN>

Distinguished Name for LDAP access

Use this option to specify the name of a user that has administrator rights for the Configuration Manager LDAP repository so that you can create policy groups. The user DN takes precedence over a user that you specify with the -a option.

-w <user password>

User password for LDAP access

If you want the tool to prompt you for an LDAP password, do not use -w with the -D option.

-m

Migrates the user configuration data that is in the SCM LDAP repository

If you do not use this option, the tool only migrates the organization and role configuration data.

-c

Overwrites existing policies

-o <log file name>

Generates a log file with the name that you specify.

The type of information that is contained in the log file is indicated by an [INFO] tag or an [ERROR] tag.

Example 5–1 Sample scm2apoc Command Line to Create New Policies

This command specifies the name of a user that has administrator rights on the LDAP server. The command also prompts you for a user password. This information is required if you want to create new policies during the migration. The location of the LDAP server is taken from the access parameter files of the SCM and Configuration Manager installations. The results of the command are stored in the log file in the directory where you issued the command.

scm2apoc -s /opt/tomcat/jakarta-tomcat-4.0.4/webapps/scm/WEB-INF/jproxy.cfg
 -a /usr/share/webconsole/apoc/WEB-INF/policymgr.cfg 
-D "uid=apocadmin,ou=people,o=mybase.com" -o log file

Example 5–2 Sample scm2apoc Command Line to Migrate User Data and to Overwrite Existing Policies

This command uses the same host, port, and base DN configuration data for the SCM and the Configuration Manager LDAP servers. The command also specifies the DN of a user that has administrator rights on the LDAP servers, migrates users, and overwrites existing policies. The results of the command are stored in the log file file in the directory where you issued the command.

scm2apoc -h localhost -p 389 -b "o=mybase.com" -e OfficeRegistry -D
 "uid=apocadmin,ou=people,o=mybase.com" -w sikr3t -u -c -o log file

Example 5–3 Sample scm2apoc Command Line to Not Migrate User Data and to Preserve Existing Polices on the Configuration Manager LDAP Server

This command uses the SCM access parameters file to access SCM entities and uses command line options to access Configuration Manager entities. The command does not migrate users, overwrite existing policies, or generate a log file output file. During the operation, the command prompts you for a user name that has access rights to the SCM and Configuration Manager LDAP servers.

scm2apoc -s /opt/tomcat/jakarta-tomcat-4.0.4/webapps/scm/WEB-INF/jproxy.cfg
 -h localhost -p 389 -b "o=mybase.com" -D "uid=apocadmin,ou=people,o=mybase.com"