Project Module > Major features and functions > TRAVEL > Working environment import for TRAVEL

The "working environment" refers to everything needed to do the job. That involves symbol libraries, catalogues, drawing frames, report definitions, script sequences, numbering algorithms, document code definitions and much more.

A feature in cadett ELSA named Import from other cadett ELSA, is used to import that kind of data from one installation of cadett ELSA to another. For travelling, import will be made from the network installation to a local installation. Basically, that is the same feature that is used to import user data from an old version to a new one, when updating cadett ELSA to a new release. However, when updating, the import is always made "soft", without any overwriting. Soft import means that objects from the installation to which import is made will have priority over objects with the same name in the installation from which import is made. User defined objects will be imported since they do not exist in the new standard installation of the new version, but all cadett ELSA standard objects in the new version will remain untouched, and not overwritten with older versions with the same names from the old version.

In a travelling situation, the described functionality has its limitations. Therefore, an extended feature called "remote import" with the option of "hard" import, is available in cadett ELSA Enterprise.

As mentioned, the same function used when updating cadett ELSA to a new version can in principle be used to import all user data from one cadett ELSA installation to another, such as from the server to a local installation. However, there are several limitations in the cadett ELSA Professional and lower. One of them is that exclusive access to the cadett ELSA from which the import is made is required. No one is allowed to run cadett ELSA in the network when the import is to be made. It is also necessary to have direct file access to the server.

To avoid these restrictions, cadett ELSA Enterprise has a remote import feature. That means that it is possible to make the import during full operation on the server, even if several users run their cadett ELSA's fully, and that the import can be done "remotely" via, for example, VPN. No direct file access is required. Remote import is optimised through the use of data compression and an ability to configure the function so that unnecessary information is not transmitted. In that way, the import can be done efficiently even over a relatively slow connection.

Another limitation of the import function available for user data in cadett ELSA Professional is that it is always "soft". This means that it never overwrites anything. This in turn means that new objects will be transferred but changes to existing objects will not be included. In the cadett ELSA Enterprise, it is possible to instead import "hard", with overwriting. Then all changes will be included in the import. That type of import is better suited to the TRAVEL situation.

The two sub-topics that are referred below, discusses in general terms the procedure for working environment import depending on the product level that is available to you:

•Hard remote import with cadett ELSA Enterprise

•Soft direct import with cadett ELSA Professional, LT and Basic

A detailed description of the Import from other cadett ELSA feature is found in a separate topic that describes just that.