To copy the properties from one isolated region to another, you can import configuration properties previously exported from another isolated region. You can also use this export and import functionality to back up and restore the isolated region configuration.
Any pending changes for the target isolated region must be either committed or discarded before beginning the import process.
To import isolated region properties:
The following rules apply for importing step processor definitions:
The following tables illustrate importing an isolated region with the overwrite option set.
ID | Type | Name |
---|---|---|
5 | 8 | Approval HTML (FileNet®) |
6 | 4 | Approval Launch HTML (FileNet) |
50 | 2 (def. step) | MyStep |
55 | 1 (def. launch) | MyLaunch |
ID | Type | Name |
---|---|---|
3 | 8 | HTML (FileNet) |
4 | 4 | Launch HTML (FileNet) |
5 | 2 (def. step) | Approval HTML (FileNet) |
6 | 1 (def. launch) | Approval Launch HTML (FileNet) |
ID | Type | Name |
---|---|---|
3 | 8 | HTML (FileNet) |
4 | 4 | Launch HTML (FileNet) |
5 | 2 (def. step) | Approval HTML (FileNet) |
6 | 1 (def. launch) | Approval Launch HTML (FileNet) |
50 | 2 (def. step) | MyStep |
55 | 1 (def. launch) | MyLaunch |
If the source isolated region contains no default processors and one of the entries will alter the existing default in the target isolated region that could result in no default processor, the existing default processor will not be changed.
ID | Type | Name |
---|---|---|
5 | 8 | Approval HTML (FileNet) |
6 | 4 | Approval Launch HTML (FileNet) |
ID | Type | Name |
---|---|---|
3 | 8 | HTML (FileNet) |
4 | 4 | Launch HTML (FileNet) |
5 | 2 (def. step) | Approval HTML (FileNet) |
6 | 1 (def. launch) | Approval Launch HTML (FileNet) |
ID | Type | Name |
---|---|---|
3 | 8 | HTML (FileNet) |
4 | 4 | Launch HTML (FileNet) |
5 | 2 (def. step) | Approval HTML (FileNet) |
6 | 1 (def. launch) | Approval Launch HTML (FileNet) |
If an import fails, you can fix the problem in the source isolated region and re-export the configuration, or in the target isolated region. You can also directly edit the exported XML file and remove items that are causing errors.
The following lists common error messages that might occur during import.
Errors occurred during commit: Can't change field lengths on log, log name="DefaultEventLog, field name=F_SubjectCause: Length of string field cannot be changed in a log file.
Solution: Either remove the F_Subject field from the export xml file or remove the F_Subject field from the target region.
Exception during import from file, The type of exposed field {xxx} does not match existing exposed field typeCause: Field type cannot be changed in a log file.
Solution: Remove the field in the export xml file or change to a different log file.
Attribute values don't match for F_WebServer.4Cause: Location of the Web Applications in the import file does not match the corresponding settings in the target region.
Solution: Either use Process Configuration Console to modify the Web Applications URLs in the import region and re-export the region properties, or modify the target region.
Exception during import from file, Attribute values don't match for F_ComponentDescriptorCause: For the Merge option, the Java™ Authentication and Authorization Service (JAAS) user or password or other settings differ on the source and target region for the Component Queue adaptor configuration in a CE Operations queue.
Solution: The Component Queue adaptor configuration should match, or you can use Overwrite to replace the existing settings.
If you edit the XML file, you might introduce syntax errors that will cause the import process to fail. The following are some common types of errors and the corresponding error messages:
Example 1: Unmatched open tag and end tag
Exception during import from file. Failed to get a document parser. The element type "ModelAttributes" must be terminated by the matching end-tag "</ModelAttributes>".... Element type "Value" must be followed by either attribute specifications, ">" or "/>"...
Example 2: Missing open quote in value clause
...Open quote is expected for attribute "Val" associated with an element type "Value"...
Example 3: Missing close quote in value clause
...The value of attribute "Val" associated with an element type "Value" must not contain the '<' character.
Example 4: Missing open quote in attribute
...Open quote is expected for attribute "Length" associated with an element type “ExposedFieldDefinition".
Example 5: Missing close quote in attribute
...Element type "ExposedFieldDefinition" must be followed by either attribute specifications, ">" or "/>"