You can use an environment definition that you extract
from an existing deployment package.
As an alternative to creating an environment definition
for the source, you can use an environment definition that is extracted
from a
FileNet® Deployment Manager deployment package. This method is often used when
the
FileNet Deployment Manager in the destination system cannot access the source
system in what is known as a disconnected deployment. A deployment
can occur between connected or disconnected environments.
- Connected - one FileNet Deployment Manager instance is able to access the source
and destination at the same time and performs both export and import.
- Disconnected – Separate instances of the FileNet Deployment Manager perform
the export and then the import. As an example, where environments
are separated by firewalls or the solution application is developed
externally.
A deployment tree contains the files that
FileNet Deployment Manager creates.
If the environments are disconnected and more than one instance of
FileNet Deployment Manager is
used, then more than one deployment tree must be created. If the deployment
is connected, only one deployment tree is needed.
To facilitate
a disconnected deployment, FileNet Deployment Manager can create a deployment package, in the
form of a compressed file, which is easier to move between systems.
This package contains the information about the source environment
that is needed to import the assets into the destination environment.
If the systems are disconnected, the source environment is typically
extracted from the deployment package into the deployment tree for
the FileNet Deployment Manager performing the import on the destination.