Items that are not migrated
The following items are not exported by the environment migration tools. These items are not available for import into a target environment and the validation process does not identify these items as missing.
If any of the items that you plan to migrate has a dependency on one or more of these items, you need to move the dependent item or items manually prior to using the environment migration tools. For help determining if any dependencies will not be migrated and how to move those dependencies manually, contact IBM® OpenPages® Support.
Configuration settings that are not migrated
The configuration settings listed in Table 1, are not migrated by the environment migration tools.
For example, if you export all settings, the settings in this table are not included in the exported JAR file.
| Setting description | Location |
|---|---|
| Mail server name | |
| SMTP user name | |
| SMTP password | |
| SMTP security type | |
| SMTP port number | |
| SOCKS Proxy private IP address | |
| Guest password on server | |
| JMS listener Urls for all paired servers | |
| Default OpenPages email sender address | |
| Default OpenPages email server | |
| Default OpenPages email username | |
| OpenPages detail page name for reference by reporting tool | |
| OpenPages server name for reference by reporting tool | |
| OpenPages server port for reference by reporting tool | |
| OpenPages application protocol for reference by reporting tool | |
| Export File Name Prefix | |
| Index search server URL | |
| Request search server URL | |
| Search server administration URL | |
| Solr user ID | |
| Solr password |
Metadata items not migrated
The following metadata items are not migrated by the environment migration tools. If any of these items is not in the target environment, you need to move the items manually.
- Triggers
- Custom query subjects
- JSPs
- Role templates
- Instance data
Although role templates and instance data are not part of the environment migration JAR files, you can migrate them by exporting them with ObjectManager and then importing the XML files with Import Configuration.
For the other items, such as JSPs, you need to copy the files from one environment to the other.
User security not migrated
User security is not migrated by the environment migration tools.
If there are profiles in the system containing user fields that have been scoped to specific security domain groups, verify that the same security domain groups are in place in the target environment. If not, configure the target environment to match the source.
The import validation process stops the import if any required security domain group is not present in the target environment. An error in the following format is displayed in the validation Log Details report:
<line#> Processing 'displayTypePropertyValue', Attribute: 'name', Value: '<group Name>' is not defined in the migration package or in the target system!: Group Missing!User fields can have a scope defined that filters the amount of returned search data. This scope definition is based on security domain groups in the OpenPages with Watson™ environment. However, these security groups are not migrated by the environment migration.
If a user field has a scope defined in the source environment, but that configuration does not exist in the target environment, the import will be stopped.
Reports not migrated
Reports are not migrated by the environment migration tools.
If a profile contains an embedded report that is not available in the target environment, a user with that profile sees a message in the OpenPages with Watson interface that the report is missing.