This documentation supports the 18.05 version of Knowledge Management.

To view the latest version, select the version from the Product version menu.

Updating the migrator.properties file

The migrator.properties file is installed with BMC Knowledge Management, and is located in the InstallationHome/BMCRemedyITSMSuite/Shared_Component/plugins directory. This file contains various parameters that are used to configure conversions of version 7.2 and 7.5 articles.


Migrator.properties file parameters

The following table lists the parameters that you can configure in the migrator.properties file.

Parameter nameDescription
rkm.db.type

Specifies the type of database server that you are using.

Possible values are:

  • 0 = MySQL Server
  • 1 = MSSQL Server
  • 2 = Sybase Database Server
  • 3 = Oracle Database Server
rkm.db.url

Specifies the connection URL for the specified database server.

Possible values are:

  • MySQL jdbc:msql://ServerName:PortNumber
  • MSSQL jdbc:sqlserver://ServerName:PortNumber
  • Sybase jdbc:sybase:tds:ServerName:PortNumber
  • Oracle — jdbc:oracle:thin:@ServerName:PortNumber

Note: Do not specify the DB/schema name for version 7.2 or 7.5.

rkm.db.schema

Specifies the database schema or instance name for version 7.2 or 7.5. 

Note: For Oracle Database Server, provide the schema ID (SID) instead of the schema or instance name.

rkm.db.user

Specifies the database administrator user name. 

Note: You can clear this value after completing the conversion.

rkm.db.password

Specifies the password for the database administrator's account.

Note: You can clear this value after completing the conversion.

rkm.resume.conversion

Specifies whether you are resuming a conversion or starting a new conversion job. 

Possible values are:

  • true = You are resuming a conversion job.
  • false = You are starting a new conversion job.

Note: The default value of the parameter is false.

rkm.resume.ArticleMigrationBackUpFile

Specifies the name and location of the backup file in which the article IDs of the processed articles will be stored. This is used if you are resuming a conversion job.

Recommendation: BMC recommends that you select a location that does not specifically require you to grant write access.

rkm.backUp.chunkSpecifies the batch size for backing up the article IDs of the knowledge articles that have been processed.
rkm.article.conversion.threads

Specifies the number of knowledge articles that will be parsed simultaneously.

rkm.default.assignedUser

Specifies the fallback value to be used if no Assignee is specified in the original knowledge article.

Provide the value in the following format:

fullName (userName)

rkm.default.supportGroupSpecifies the fallback value to be used if no Assignee Support Group is specified in the original knowledge article.
rkm.default.author

Specifies the fallback value to be used if no Author is specified in the original knowledge article.

Provide the value in the following format:

fullName (userName)

Mapping article statuses in version 7.2 and 7.5

You can use the migrator.properties file to mapping knowledge article statuses in version 7.2 and 7.5 to statuses that are used in newer versions of BMC Knowledge Management. Refer to the following examples that show how the default statuses are mapped:

  • Work\ In\ Progress=Work In Progress
  • Draft=Draft
  • Spelling=Optional Review 1
  • SME\ Review=SME Review
  • Final\ Review=Optional Review 2
  • KMSPublish=Published
  • KMS_Retired=Retired

Note

In the examples, the combination of a backslash ( \ ) followed by a space indicates the presence of spaces in the names of statuses in version 7.2 and 7.5.

Was this page helpful? Yes No Submitting... Thank you

Comments