Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
- Upgrade tasks on the development environment
- Step 1: Duplicate the production environment
- Step 2: Upgrade server and client
- Step 3: Perform preparatory tasks
- Step 4: Load the applications upgrade files
- Step 5: Run the Upgrade Utility
- Step 6: View the upgrade results
- Step 7: Manage the upgrade result data
- Step 8: Resolve exceptions
- Step 9: Resolve conflicts
- Step 10: Perform additional manual tasks
- Step 11: Migrate Process Designer data
- Step 12: Return the system to normal operation
- Step 13: Test the development environment
- Step 14: Back up the system
- Step 15: Build a custom upgrade
Step11: Migrate Process Designer data
You can use the data migration tool to migrate data from legacy process records to new process records within the same Service Manager system. It is not used to migrate data across different Service Manager systems. You can configure the migration tool from the GUI, and it requires administrator privileges.
The migration tool allows an operator to configure the field/value mapping between two files. It also covers customized fields. The out-of-box Process Designer provides several sample migration scripts that you can choose to use according to your migration scenario.
Caution During data migration, there are no dependencies between the modules, however the scripts for each specific module must be executed in the listed order.
| Module | Script |
|---|---|
| PD Framework |
|
| Problem |
|
| Service Level Agreement |
|
| Service Catalog |
|
| Configuration Item |
|
If further migrations are needed, an administrator can use these samples to define their own. Considering that some tables typically have a large data volume, the Data Migration tool supports an SQL batch update mode to ensure good performance.
Note We recommend that you back up the production data before migration.
Run the scripts for specific modules as follows:
| Module | 9.3x non PD | 9.3x PD3 | 9.3x PD4 | 9.40 Classic / 9.41 Classic | 9.40 Codeless / 9.41 Hybrid / 9.41 Codeless | 9.50 Codeless / 9.50 Hybrid / 9.51 Codeless / 9.51 Hybrid | |
|---|---|---|---|---|---|---|---|
| PD Framework | Legacy change model taskplanner data to new taskplanner | √ | √ | ||||
| Legacy change instance taskplanner data to new taskplanner | √ | √ | |||||
| Legacy change/task data to new taskplanner | √ | √ | |||||
| Problem | Legacy problem to new problem | √ | √ | √ | |||
| Legacy problem task to new problem task | √ | √ | √ | ||||
| Legacy known error to new known error | √ | √ | √ | ||||
| Legacy PD known error to new PD known error | √ | ||||||
| Legacy known error related record migration | √ | √ | √ | ||||
| Legacy known error attachment to new known error attachment | √ | √ | √ | ||||
| Service Level Agreement | Legacy SLA to new Agreement | √ | √ | √ | |||
| Service Catalog | Legacy Catalog Items to new Catalog Items | √ | √ | √ | √ | √ | |
| Configuration Item | Legacy configuration item to new configuration item | √ | √ | √ | √ | √ | √ |
How to run a migration script
Note If you are upgrading an existing Service Manager system to Process Designer, you need to customize the legacy out-of-box migration script samples for your specific environment.
To run a migration script, follow these steps:
-
Type db in the command line to open Database Manager.
-
Type migrationSetting in the Table field, and then click Search.
-
In the Migration Script setting detail form, click Migrate Data to run the migration script.
-
When using the Batch Update mode, the Data Migration pop-up window shows the RDBMS SQL Statements that will be run on the database. Check that the SQL statements are correct, and change these SQL statements if needed. Click Next, and then click Finish to start the migration in Batch Update mode.
Note If there is no data to migrate, or if the data is already migrated, you receive the following notification:
"No records match the filter condition. At least one matching record is required."
