Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Exporting Activity Monitoring Configuration Information

You can export activity monitoring configuration information from your iProcess Engine to an XML file, which you can subsequently import to the same or another iProcess Engine if required. You can export the configuration information for all procedures or a specific procedure, depending on your requirements.

To export your activity monitoring configuration information, enter the following command:

    swutil EXPMONITOR [procname]

where `procname` is the procedure name. You can specify a main procedure or a sub-procedure.

Note | You must run this command for each procedure or sub-procedure that has activity monitoring configuration information set. For example, if you have a main procedure that calls sub-procedures and you run this command for the main procedure only, the sub-procedures are not included in the export file.

The information is written in XML format. By default, it is written to the console or you can redirect it to a file.

Note | You can locate the file wherever you want. TIBCO iProcess Engine does not require that it is located in a specific place.

The XML format conforms to the `SWMonitorList.xsd` schema (see Overview for more information). This enables it to be used in a `swutil IMPMONITOR` command to amend or overwrite activity monitoring configuration information on another iProcess Engine.

If no procedure name is specified in the `swutil EXPMONITOR` command, then all the activity monitoring configuration information is exported. This causes the `FullImport` element to be set to `true` in the XML file. For example,

    <FullImport>true</FullImport>

This means that when you import the activity monitoring configuration information, the import will overwrite the existing activity monitoring configuration on iProcess Engine with the configuration information in the XML file. If you specify a procedure name, the `FullImport` element is set to `false`. This means the imported activity monitoring configuration information is added to the existing activity monitoring configuration information.

Note | If this does not meet your requirements, you can amend the `FullImport` element directly in the XML file.

The server processes the activity monitoring configuration information, and reports and logs any errors it encounters:

| • | Progress is reported to the console.

| • | Serious errors are logged either to the `sw_warn.log` file or to the `sw_error`.log file located in the `SWDIR``\logs` directory. See "Error Handling" in TIBCO iProcess Engine Administrator's Guide for more information.

Note | If you have changed the log files directory in the `staffpms` file, errors will be logged to the `sw_error.log` file and the `sw_warn.log` file located in the directory you have specified.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2025. Cloud Software Group, Inc. All Rights Reserved.