If you are using one or more InfoSphere® MDM test
environments as a development environment for the MDM Workbench,
you access Test Environment Preferences to reset
an instance, to verify an instance, and to view the properties of
an instance.
When you are developing for InfoSphere MDM,
it is possible for the operational server to become corrupted in a
number of different ways: test data used to check installation could
become outdated or incorrect, changes may occur to the server configuration,
or changes may occur to the applications installed on the server.
Any of these issues could affect instance functionality, and can be
resolved by removing the incorrect data from the database, by resetting
the test server configuration, or by doing both.
The Test Environment Preferences dialog lists the name and home
location of InfoSphere MDM operational
server, if any. When an operational server is selected, operations
can be performed on it.
The Test Environment dialog supports the following :
- Resetting DB2®, Oracle, and
SQL Server database objects installed by InfoSphere MDM
- Resetting the server and configuration for an InfoSphere MDM installation
on a server
- Secure Storage and modification of credentials in the MDM Workbench (running
in IBM® Rational® Application Developer)
- Verification of operational server instances
- Viewing properties of an operational server instance
Important: It is not advisable to install the MDM Workbench in
a production environment because it is possible to use the Reset
Functionality in the Test Environment dialog
on an operational server in a Production environment to remove the
existing data and applications.
Database reset
If values
in the database get corrupted, you can use the reset database operation
to restore a vanilla instance of the database without having to create
a new one. Resetting the database occurs in two stages: an uninstall
and an install stage. The reset database operation drops the tables,
triggers, and indexes present in the InfoSphere MDM schema
in the database and removes the existing data source in the uninstall
stage. The install stage then creates the configuration management
tables, domain related tables, populates required data in the tables,
and creates the data source. The detail of the corresponding InfoSphere MDM operational
server is populated in the relevant tables in the database.
Server reset
If the
application server configuration is corrupted during development phase
by use of additions and extensions, you can restore the operational
server to the state at which it was immediately after installation
by using the reset server operation. The server reset operation is
performed in two stages: an uninstall and install stage. You must
start the deployment manager and the node before invoking this operation.
First, the operation uninstalls the EBA and related bundles installed
for use by InfoSphere MDM and
removes any other related configurations on the test server that were
done for use by InfoSphere MDM.
It then performs the configuration and installation of files to bring
back the server to a vanilla state. Details of the InfoSphere MDM operational
server instance are also populated in the corresponding database.
Secure storage of credentials
The
user name and password corresponding to the database, application
server, and messaging server, if applicable, are stored securely in
the MDM Workbench environment.
It is advised to use a password for secure storage so as to strengthen
the security. Details on secure storage are also available in the IBM Rational Application Developer help
system.
InfoSphere MDM operational
server verification
After resetting an operational server,
you must run the verify operation to ensure that the instance works
as expected. After you have run the verify operation, the location
of the response files is displayed, and you must manually look at
the files in the directory to determine whether the response files
indicate success.
Operational server properties
The operations
performed on an operational server depend on the properties of that
operational server. You can view the properties using this tool. Note
that the password values are not displayed.
All available instances
are listed in a table in the Test Environment Preferences dialog.
If there are no instances, an empty table is displayed. Only those
instances that have an existing installation directory are displayed.
When you select an operational server, the Reset, Properties, and
Verify buttons are enabled.
Description of the
Reset
Test Environment dialog:
- Reset the Server: select this check box
to reset the server
- Reset the Database: this check box to reset
the database
- Database Authentication: the details in
this section can be modified
- Messaging Authentication: the details in
this section can be modified. This appears only if the messaging type
is IBM WebSphere® MQ (if your installed messaging
type is WebSphere Embedded
Messaging (WEM), the messaging authentication section is grayed out).
- Application Server Authentication: the
details in this section can be modified
- Save Passwords: select this check box if
you have made changes to the authentication credentials; changes are
saved to secure storage.
Verify dialog
The Verify operation is similar
to the Installation Verification Testing that is performed immediately
after an installation. This operation enables you to verify whether
a list of transactions is giving successful responses. After you run
the verification, the location of the results is displayed in a dialog
box.
Properties dialog
When an instance is selected
in the Test Environment page and the Properties button is clicked,
the properties of the instance are displayed. These properties are
used during the reset operation.
IBM InfoSphere Master Data Management, Version 11.3