Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Manager9.41

Develop > Tailoring > Data management > Data Policy > Data Policy and encryption > Change the encryption key value

Change the encryption key value

You can set the KEY value that encrypts data on your system with the encryptionkey parameter in the sm.ini file. This field must be exactly 8 bytes in length. If you change the KEY value, then every field in every file must be checked and re-encrypted. Changing the KEY value results in a significant performance hit to the system while re-encryption takes place.

To change the encryption key value, perform the following steps:

Shut down the HPE Service Manager server.
Restart Service Manager from the command line using the changeencrkey parameter. For example, sm -changeencrkey:XXXX where XXXX is the new 8-byte key.

Starting Service Manager in this way decrypts all encrypted fields using the key defined in the sm.ini file and then re-encrypts those fields using the key specified in the command line parameter changeencrkey. The length of time the conversion takes depends on the size of the database and the number of encrypted tables. You need to update your sm.ini file to the new key immediately after performing this action.

Caution: Encrypting SQL data that is already mapped will increase the size of the data. Therefore, the existing SQL mapping and column definition may not provide enough space to store the whole encrypted value. Be sure to change the SQL data type to accommodate the new column size. If the encrypted value gets truncated, the value can no longer be decrypted.

Use this formula to calculate the new column length:

encrypted_length = (unencrypted_length + 12) * 2.

Send Help Center feedback