Please enable JavaScript to view this site.

Altova FlowForce Server 2020 

When you export data from FlowForce Server, you can always exclude certain objects from the export. However, some objects may have dependencies on other objects. If you do not export dependencies together with the object that depends on them, this may lead to errors when you later import that data back into FlowForce Server. The examples below are meant to help you understand the implications and how to address them.

 

Example 1: Exclude sensitive data

Let's assume that you have a job ("AddNumbers") which refers to a credential record that is in the same container ("my.credentials").

ff_export_01

If you choose to export both objects to a file (.zip archive) without selecting the Export sensitive data option, the following happens:

 

1.The job will be exported.

2.The credential record will be exported without the password.

 

If you later import the .zip archive into a FlowForce Server environment where the two objects do not exist, both objects will be created successfully. Note that the password associated with the credential record will be empty.

 

If the objects already exist in the target environment, you can overwrite them or clear the corresponding check box and skip them:

ff_export_02

If you choose to overwrite both records, the following happens:

 

1.The job existing in FlowForce Server will be overwritten by the job from the .zip archive.

2.The credential record existing in FlowForce Server will be overwritten by the one from .zip archive, and the destination password will become empty.

 

If you do not overwrite the credential, the existing credential remains untouched.

 

Example 2: Include sensitive data

Let's assume that you export the same two records as above,  and also select the Export sensitive data option during export. In this case, the following happens:

 

1.The job is exported

2.The credential record is exported and includes the password as well.

 

If you later import the .zip archive into a FlowForce Server environment where the two objects do not exist, both objects will be created successfully. The password associated with the credential record will be the one from the .zip file.

 

If the objects already exist in the target environment, you can overwrite them or clear the corresponding check box and skip them. If you choose to overwrite the records, the following happens:

 

1.The job existing in FlowForce Server will be overwritten by the job from the .zip archive.

2.The credential record existing in FlowForce Server will be overwritten by the one from .zip archive. The destination password will also be overwritten by the one from the .zip archive.

 

If you do not overwrite the credential, the existing credential remains untouched.

 

Example 3: Handle missing dependencies

Let's assume that you have the same two records as above and choose to export only the job, without exporting the credential record:

ff_export_03

In this case, the following happens:

 

1.The job will be exported (but it will have a missing dependency)

2.The credential record will not be exported.

 

If you later attempt to import the .zip archive into a FlowForce Server environment where the object /public/Jobs/my.credentials exists, the import is possible because the missing dependency is now resolvable.

ff_export_04

However, if the referenced credential does not exist in the target environment, the import dialog box looks as follows:

ff_export_05

In the image above, notice that the credential record is no longer recognized as such—namely, its type is "configuration" instead of "credential", and the icon is different. The type "configuration" indicates a generic configuration object (another job or credential), whose type is not known. In this example, the "my.credentials" configuration object was not exported, and the exported package has no information about its exact type*, other than the reference path. Therefore, attempting to import the data above into FlowForce Server will result in an error like: "Operation failed: Path does not exist".

 

To fix this error, create the missing record at the path indicated by the error message (in this case, the "my.credentials" record), and then perform the import again.

 

* A credential reference may be a reference to a standalone credential object, and, in some cases, to a job which contains local credentials, see also Referring to Credentials from Jobs .

© 2019 Altova GmbH