• Browse
  • Pages
  • Blog
  • Labels
  • Attachments
  • Bookmarks
  • Mail
  • Advanced

  • What’s New
  • Space Directory
  • Keyboard Shortcuts
  • Confluence Gadgets

1. Dashboard
2. ADDM 8.2
3. Documentation
4. User Guide
5. Export
6. Running an Export
7. Information
8. Page Comparison

Page Comparison - Running an Export (v.1 vs v.2)

Version 1 by David Shorten on Aug 24, 2010 12:06. compared with Current by Andrew Waters on Aug 03, 2011 14:21.

Key This line was removed. This word was removed. This word was added. This line was added.

Comment:

Changes (2)

View Page History

...

{warning}It is strongly advised that you run exports from BMC Atrium Discovery during time periods when no discovery runs are occurring. This ensures that the state of the datastore will not change during the export. Such a change could result in inconsistent data being exported.{warning}

There are two ways to run an export:
* From the User Interface
* From the command line

h2. Running an Export from the User Interface
To run an exporter from the User Interface:
# Navigate to Exporters tab.
# Click on the exporter's Run link.
Only one export can be run at a time. As a result all of the other exporters' run links become unavailable when an export is running.\\
The output for the currently executing exporter is displayed beneath the configuration tabs. It refreshes every few seconds, keeping the output up to date.
# Once the export has finished, the output window displays a "No export is running" message, and will stop refreshing.
# To re-enable the exporters' Run links, close the output window by clicking the Close button.

h2. Running an Export from the Command Line
The export process can also be run from the appliance's command line interface. Do the following to run an export from the command line:
# Log on to the appliance as the {{tideway}} user.
# Run the following command (where {{_exporter-name_}} is the name of the exporter you want to run):
{{$TIDEWAY/java/integrations/bin/export.sh _exporter-name_}}
The export now runs and the clean log (see [#Log Files]) is written to the console. Future exports can be scheduled using cron.

h2. Log Files
There are two types of log files produced by the Export component.
* [#Export Log Files]
* [#Other Log Files]

h3. Export Log Files
Each export writes logs to the normal BMC Atrium Discovery appliance log location.
To view the logs, select Appliance > View Logs

The following logs are written:

* *Clean log* -- This contains information on what the exporter did with each item. These log files are called {{tw_cmdb-export._timestamp_.log}} where {{_timestamp_}} is the data and time the export commenced.

* *Full log* -- This contains much more verbose information about the export process. This log is intended for debugging. The full log is called {{tw_cmdb-export.log}}.

When the full log reaches 50 MB, it is rolled. That is, a .1 log number suffix is appended to its filename and existing logs have their log number suffixes incremented. The oldest log is deleted. Ten logs are retained in addition to the current log.

...

See the [Troubleshooting section|If You Encounter a Problem#To View logs] for more information on viewing BMC Atrium Discovery log data.

h3. Other Log Files
Several other log files are also generated in the BMC Atrium Discovery Appliance log location directory.
* *Startup log* -- When BMC Atrium Discovery is started, a component of BMC Atrium Discovery Export runs to perform some cleanup exercises. The log for this activity is in {{export-creds.log}}
* *Connection test log* -- Whenever a user tests an adapter configuration connection, the messages for the test are written to a log called {{tw_exporter_connection_test.log}}