Import Server Information (Page 3 of 4)

Add selected source directory to recent directory list even if import fails Allow imported servers to replace existing servers which are duplicates Delete all existing servers and replace with imported data Do not import any security data Do not import deployed services and packages | Do not proceed with import if any imported servers are duplicates of existing servers Only import servers which are not duplicates of existing servers Replace the existing Security Manager Pool and security references with imported data Set initial state to Stopped for all servers

Import Server Information (Page 3 of 4)

  Use this page to specify options for importing servers and security data.import server definitions.

  Top

Set initial state to Stopped for all servers

  Check this if you want the status of the imported server to be set to Stopped. This is the default behaviour. You should choose this only if you know that the servers you are importing are not already started.

  If you uncheck this option, the imported server will have the status that it had when it was exported; for example, if you exported data for server while that server was running, the imported server will have an initial status of Started whether or not it is actually running. You should do this only if you know that the restored statuses will match the current statuses of your enterprise servers. One reason for doing this might be to import changed configuration information for an existing server that is currently running.

  Top

Do not import deployed services and packages

  Check this to exclude deployed services (that is, services with an associated package and handler) when importing server definitions.

  Top

Add selected source directory to recent directory list even if import fails

  Check this to ensure that the directory is added to the recently used list. By default the directory will only be added to the list if the import is successful.

  Top

Do not proceed with import if any imported servers are duplicates of existing servers

  Check this if you want to cancel the import where any of the servers being imported has the same name as an existing server.

  Top

Only import servers which are not duplicates of existing servers

  Check this to exclude from the import any server that has the same name as an existing server.

  Top

Allow imported servers to replace existing servers which are duplicates

  Check this if you want any existing server that has the same name as one being imported to be replaced by the imported server.

  Top

Delete all existing servers and replace with imported data

  Check this if you want to replace all of the existing servers with the imported servers. If you choose this, when the import completes only servers that were imported will be present in the repository.

  Top

Do not import any security data

  Check this if you do not want the security information to be imported. This option is only present where the source directory contains security information.

  Where you check this, or where the security details were not included in the export, the imported servers will use the Default ES Security configured on the importing system.

  Top

Replace the existing Security Manager Pool and security references with imported data

  Check this if you want the Security Manager definitions, the Security Manager lists and other security configuration details to be completely replaced by the definitions from the from the source directory. This option is only present where the source directory contains security information.

  One consequence of checking this option is that servers that are not replaced during the import will have their security details set to use the Default ES Security configuration.

  Top