The Database Explorer is automatically populated
with aliases, for example, from the local DB2 instance. Connections that you
define are stored in the Eclipse workspace and not in your project.
These behaviors have the following implications:
- Your workspaces might not always be portable between DB2® Change Management Expert versions
and Fix Packs. If the workspaces are not portable, you can import the project
that you want to move into the new workspace and then redefine your connections.
- The connections in the Database Explorer are
referenced by an alias. That way different CONNECT statements can uniquely
identify databases with the same name that are on different instances. For
example, the name that is displayed in the Database Explorer might
not necessarily be the same as the database name.
- Connection names in the Database Explorer need not
be the same in different workspaces amongst different users. If there are
CONNECT TO statements in the change command (.chx) files, the connection being
referenced will be the one that is displayed in the Database Explorer.
Take care to use the same connection aliases in the Database Explorer when
you share scripts between multiple users or workspaces. This ensures that
all users are deploying to the correct target environment.