3.5.3 csmig Syntax (Sun Java System Calendar Server 6.3 Administration Guide)

Sun Java System Calendar Server 6.3 Administration Guide

3.5.3 csmig Syntax

The csmig utility has the following syntax:

csmig [-t DestinationDB]
      [-b Backend-DWPHost]
      [-o OutputFile]
      [-e ErrorFile]
      [-m MappingFile]
      [-c calendarOwner]
      [-r resourceOwner]
      { migrate|dryrun }

The following table lists the utility options, gives a description of each, and gives the default value.

csmig Options	Description and Default Value
`-t` `DestinationDB`	Specifies the destination target database that `csmig` generates. The default is `MigratedDB`.
`-b` `Backend-DWPHost`	Specifies the name of the DWP back-end host server. This name must match the DWP back-end host server name specified in the `ics.conf` file.
`-o` `OutputFile`	Specifies an output file that captures the `csmig` output to the screen as well as any errors that occur. The default is `MigrateOut`.
`-e` `ErrorFile`	The file where `csmig` writes any errors or database entries that cannot be resolved. If database entries cannot be resolved, they are not written to the destination database. The default is `MigrateError`.
`-m` `MappingFile`	Specifies an output mapping file generated in `dryrun` mode that lists entries in the LDAP schema that need to be changed. For example: Old: `calid=jsmith` New: `calid=jsmith:basketball` The mapping file provides only a list of changes to make to the LDAP schema. csmig does not actually make the changes to the schema The mapping file is not used in `migrate` mode.
`-c` `calendarOwner`	Specifies the owner for user calendars that don’t have owners.
`-r` `resourceOwner`	Specifies the owner for resource calendars that don’t have owners.
`migrate\|dryrun`	Specifies which mode the utility is running in. Use `migrate` mode to perform the migration. Use `dryrun` mode to generate the output mapping file before you actually migrate.