If you want to move a template from a development system
to a production system, you can use the Monitor action services data
export and import tool to export the defined actions and templates
data, which are stored in the Monitor database, to an XML file. You
can also use the tool to import this XML file into another Monitor
database.
Procedure
- Go to WAS_home\scripts.wbm\AAMExport\,
and open the batch file named runAAMExport.bat in
edit mode.
- Ensure that the %JDBC_DIR% variable is set and points to
the correct Java JDBC directory for the database type you are using
for the Monitor database.
- Ensure that the %JDBC_DRIVER% variable is set to the correct
JAR file for the database type you are using. See the config.properties file
for details about the JAR file name for each supported database type.
- Save and close the file.
- Open the file named config.properties in
edit mode.
- Ensure that the correct database section is uncommented
for your installation.
- To set the source and target of the tool, modify the values
for each property in this file.
- Save and close the file.
- Run the runAAMExport.bat file as follows:
- Open a command-line window.
- Call the batch file by typing runAAMExport.bat and
pressing Enter.
- If you want to specify a different location for the config.properties file,
add the following code to the command-line after the batch file name:
-DActionManager.mover.configFile=config.properties_new_file_name_and_path
For example, you can change the location as follows: runAAMExport.bat
-DActionManager.mover.configFile=C:\temp\example.properties
- You can also enter any property with its value in this
command line to override the value that exists in the config.properties file.
You override the value as follows:
-D property_name=property_value
Note: The tool will overwrite any actions or templates with
the same name that already exist in the Monitor database.