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. The target isolated region must be initialized and any pending changes must be either committed or discarded before beginning the import process. See Export isolated region properties for information on exporting properties.
To import isolated region properties
This option is appropriate for importing from a development environment into a newly initialized region that will be used for a production environment.
CAUTION If you use the Overwrite option to import into a target region that has been in use for some time, items of the same name will be overwritten, which can lead to unexpected results.
If the exported source contains a UDDI repository, the business name, authorized user, operator, and other business and contact information are imported; the inquiry URL and business key are generated for the target region.
For an in-use target region, this option preserves any existing properties in the target region, adding only new properties from the source region.
If the exported source contains system properties, the import will skip the import of the user information if that user is not defined on the target system. This applies to both overwrite and merge.
If the exported source contains a UDDI repository, only contact information is imported; business information is not imported.
TIP If you import with System Properties from a non-default region, click Refresh to update display of the properties.
The following rules apply for importing step processor definitions:
NOTE If a source step processor set contains an entry that will alter the existing default setting, and there is no other default step processor in the source set, then the import will not change the existing default setting.
The following examples illustrate import with overwrite:
Source isolated region | Existing target isolated region | Result | |||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
If the source contains no default and one of the entries will alter the existing default leaving no default, the existing default will not be changed.
Source isolated region | Existing target isolated region | Result | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
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 occur during import.
Errors occurred during commit:
Can't change field lengths on log, log name="DefaultEventLog, field name=F_Subject
Cause: 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 type
Cause: 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.4
Cause: 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_ComponentDescriptor
Cause: For Merge only, 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 "/>"