1. Using Oracle Managed File Transfer
  2. Monitoring Oracle Managed File Transfer

5 Monitoring Oracle Managed File Transfer

Learn to use the Monitoring page of the Oracle Managed File Transfer console. The Monitoring page displays information about deployments of source, target, and transfer artifacts, the page also displays dashboards for all artifacts, for all artifacts of a specific type (source, transfer, or target), or for an individual artifact.

Dashboards provide information about in-progress and completed file delivery instances. This chapter includes the following sections:

5.1 Monitoring Deployed Sources, Targets, and Transfers

After you deploy source, transfer, or target artifacts, you can view them in the Deployments tab on the Monitoring page.

You can select which artifacts to view:

  • Order by time deployed, time updated, name, or artifact type, ascending or descending.

  • Select a range using Deployed or Updated and From or To with dates and times.

  • Select, Unselect, or Invert All. Inverting means selecting unselected artifacts and deselecting selected ones.

  • Show Only Sources, Targets, or Transfers. You can show any or all types.

  • Show Deployment Details shows labels and dependent artifacts for the selected artifact. The label is the name of the deployment corresponding to the artifact on the Oracle WebLogic Server managed server for Oracle Managed File Transfer. Artifacts associated with the same transfer are mutually dependent.

    Note:

    The Created timestamp refers to the creation of the label, not the artifact. Editing and redeploying an artifact creates a new label.

To refresh the display according to these selections, click the Filter or Go icon. The Go icon appears when you change these selections. To clear these selections and display according to the defaults, click the Erase icon.

5.1.1 Disabling Sources, Targets, and Transfers

All deployed artifacts are enabled by default. Disabling an artifact makes it inactive without undeploying it.

The steps for this process are:

  1. Check the box to the left of the artifact.

  2. Click the Disable button.

    The Disable Deployments dialog appears, showing dependent artifacts affected by the proposed disabling. You can enter an optional comment.

  3. Click the Yes button.

    The Disable Deployments dialog shows whether disabling was successful.

  4. Click the OK button.

    If disabling was successful, the Status column entry for the artifact changes from Enabled in green to Disabled in red. Dependent artifacts may also be shown as disabled.

5.1.2 Reenabling Sources, Targets, and Transfers

You can reenable a disabled artifact.

The steps for this process are:

  1. Check the box to the left of the artifact.
  2. Click the Enable button.

    The Enable Deployments dialog appears. It displays a confirmation dialog about associated artifacts. Select the Enable all associated Transfers checkbox to enable all the associated transfers with the selected source. Or leave the checkbox blank to enable only the selected source. You can enter an optional comment in Comment for Enabling Deployments (Optional) textbox.

  3. Click the Yes button.

    The Enable Deployments dialog shows whether enabling was successful.

  4. Click the OK button.

    If enabling was successful, the Status column entry for the artifact changes from Disabled in red to Enabled in green.

Note:

If dependent artifacts were disabled, you must reenable them separately. For example, if you disabled a source and the associated transfer was disabled, reenabling the source does not reenable the transfer.

5.1.3 Undeploying Sources, Targets, and Transfers

If you want to both inactivate and edit an artifact, undeploying it might be preferable to disabling it. Oracle Managed File Transfer maintains versions of its artifacts (source, transfer and target). When an artifact is deployed, the current version of the artifact is deployed. These versions are stored for future auditing. When you undeploy an artifact, the following occurs:

  • The artifact becomes eligible for purging using a WLST command as described in Oracle Managed File Transfer Utilities.

  • That version cannot be deployed again. You cannot roll it back to previous version.

The steps for this process are:

  1. Check the box to the left of the artifact.
  2. Click the Undeploy button.

    The Remove Deployments dialog appears. You can enter an optional comment.

  3. Click the Yes button.

    The Remove Deployments dialog shows whether undeployment was successful.

  4. Click the OK button.

    If undeployment was successful, the artifact is removed from the Deployments tab.

Note:

You cannot undeploy a source or target if the associated transfer is deployed. The Undeploy button remains grayed out.

5.1.4 Redeploying Sources, Targets, and Transfers

To redeploy an artifact, open its tab on the Design page and click Deploy. See Deploying a Source_ Target_ or Transfer.

5.1.5 Versioning Sources, Targets, and Transfers

Oracle MFT uses MDS to store metadata. The MDS Repository maintains versions of the documents in a database-based repository. Versioning allows changes to metadata objects to be stored as separate versions rather than simply overwriting the existing data in the metadata repository. It provides version history, as well as the ability to label versions so that you can access the set of metadata as it was at a given point in time. An artifact can modified after deployment, however the original version will be used at runtime until the newer version is deployed. To activate and apply the latest changes, you must redeploy the artifact.

You can use WLST commands to perform the following operations on the MDS Repository.

  • getSourceDeploymentHistory used to list all the deployment history.

  • exportDeployedArtifact used to export the deployed versions of the artifact.

  • deleteArtifactDeployment used to delete the older deployment history.

For detailed information on using the MDS Repository, see Managing the Metadata Repository in Administering Oracle Fusion Middleware.

5.2 Interpreting Artifact Instance Messages

The Messages view is a searchable table of file delivery instance messages for the artifact for which the dashboard was opened. You can use % as a wildcard.

This table displays:

  • Report: Click on the report link to open a source, transfer, or target report. See Source Reports, Transfer Reports, or Target Reports.

  • Purge: Click Purge to remove the selected source instance and related target and transfer instances. The source is not deleted but only the selected source instance and its related target and transfer instances are purged from the system.

  • File Name: The name of the transferred file. The file might be renamed at the target; see Moving and Renaming Files After Delivery.

  • Size: The size in bytes of the transferred file. Compression or encryption might change the file size at the target; see Setting Up Source Processing Actions and Setting Up Transfer Preprocessing and Postprocessing Actions.

  • Create Time: The date and time that the file was written to the source or target location.

  • Status: Active, Failed, or Completed. Substatuses of Active are:

    • Delivery In Progress

    • In Progress

    • Paused

    • Pending

    • Pending Delivery

    • Post Processing

    • Pre Processing

    • Retrying

    • Scheduled

    Substatuses of Failed are:

    • Error

    • Partial Error

    • Post Processing

    • Pre Processing

    The only substatus of Completed is Successful.

  • Priority: Priority of the transfer.

5.3 Monitoring Transfer Flows Using the Main Dashboard

Use the main Dashboard to monitor the transfers. The main Dashboard displays real-time and recent file-delivery data. The Dashboard tab on the Monitoring page is always open.

The Main Dashboard displays data in four views:

You can expand each view to cover the entire tab by clicking the Expand icon in the upper right corner. To collapse the view and return to the Main Dashboard, click the Restore icon in the upper right corner of the expanded view.

The Design page and the Deployments tab show source, transfer, and target artifacts, which structure how file deliveries happen. In contrast, the Main Dashboard shows source, transfer, and target instances, which are the individual file deliveries themselves.

5.3.1 Interpreting Main Dashboard Metrics

The Metrics view displays a variety of statistics about recent transfers. You can use these statistics to determine which transfers are used frequently, failing, or taking a long time to complete.

To determine how recent the transfers are, select one of these interval values from the View Data drop-down list:

  • Last Hour

  • Last 6 Hours

  • Last 24 Hours (default)

  • Last 3 Days

  • Last Week

Note:

If you use 'truncate table' to clean the environment, the materialized view will stop refreshing and metrics on MFT dashboard will not refresh. To fix this issue, you need to execute a database procedure MFT_REFRESH_MV which will enable refresh of materialized view again.

The statistics displayed in the unexpanded view are:

  • Transfers: Total, Completed, Active, and Failed

  • Most Active Transfers: Transfers with the most instances in the selected interval

  • Status: A pie chart of completed, active, and failed transfers

  • Failure Ratio: The percentage of failed transfers

  • Payload File Size: Average, Minimum, and Maximum in bytes

  • Transfer Speed: Average, Minimum, and Maximum in bytes per second

  • Total Time: Average, Minimum, and Maximum in milliseconds

The expanded view adds an All Transfers table with these columns:

  • Transfer: Click on the name to open a transfer report. See Transfer Reports.

  • Refresh: Refresh the page with updated data.

  • Eraser Icon: Clears a selection from the transfer table. The icon is enabled if any section of the pie chart is clicked causes the transfer table to be displayed.

  • Sort By: Choose whether to sort by status or by name.

  • Source: The source associated with the transfer. Click on the name to open a source report. See Source Reports.

  • Status: Active, Failed, or Completed

  • Substatus: The transfer substatus. The substatuses of Active are:

    • Delivery In Progress

    • In Progress

    • Paused

    • Pending

    • Pending Delivery

    • Post Processing

    • Pre Processing

    • Retrying

    • Scheduled

    Substatuses of Failed are:

    • Error

    • Partial Error

    • Post Processing

    • Pre Processing

    The only substatus of Completed is Successful.

  • Initiation Time: The date and time that the transfer started

  • Content Type: The type of the file transferred, for example, XML. Content filters define content types. See Setting Up Content Filters.

5.3.2 Using the File Finder

The File Finder view provides a table that lets you search for transfer instances using names of associated files, sources, or targets as your search criteria.

In the unexpanded view, you can search for a file name, a source or target name, or both. Searches are case-sensitive and use the Starts With operator. You can use % as a wildcard. Table columns are:

The expanded view provides additional features:

  • A choice of operators: Starts With, Exact Match, or Contains

  • A Case Sensitive check box

  • An icon you can use to clear all search parameters

  • Two additional table columns:

    • Type, with these possible values: B2B, SOA, Healthcare, OSB, ODI, Source Resubmit, or External

    • Sender, the name of the user that initiated the transfer

  • Search fields for each column

Note:

Postprocessing occurs after file delivery. Therefore, the Active Deliveries and File Finder views show different statuses if file delivery succeeds but postprocessing fails. Specifically, the Active Deliveries view displays a Completed status but the File Finder view displays a Failed status.

5.3.3 Monitoring Active Deliveries

The Active Deliveries view is the same unexpanded and expanded. For recent and in-progress deliveries, it displays:

  • Transfer Name: Click on the name to open a transfer report. See Transfer Reports.

  • Start Time: The date and time that the transfer started.

  • Progress: The percent complete. If the progress is less than 100% and is not changing, this might indicate that the transfer is paused or has failed. See Pause and Restart a Transfer or Diagnose Transfer Errors.

  • Refresh: Choose the refresh interval of active deliveries.

5.4 Interpreting Dashboards for All Transfers, Sources, or Targets

A source, transfer, or target dashboard displays real-time and recent data for file deliveries, or instances, that is related to all artifacts of the same type. Unlike the main Dashboard, an all-artifact dashboard must be opened.

Click Transfer Instances, Source Instances, or Target Instances in the left pane navigator to view the dashboard. The views on an artifact dashboard are:

Unlike the views on the Main Dashboard, the views on the artifact dashboards have no Expand icons.

5.4.1 Interpreting Instance Messages

The Messages view is a searchable table of file delivery instance messages for all artifact of the type for which the dashboard was opened. You can use % as a wildcard. This table displays:

  • ID: Click on the ID link to open a single-artifact source, transfer, or target dashboard. See Interpreting Single Artifact Transfer_ Source_ and Target Dashboards.

  • Name: The name of the artifact.

  • Status: Active, Failed, or Completed. Substatuses of Active are:

    • Delivery In Progress

    • In Progress

    • Paused

    • Pending

    • Pending Delivery

    • Post Processing

    • Pre Processing

    • Retrying

    • Scheduled

    Substatuses of Failed are:

    • Error

    • Partial Error

    • Post Processing

    • Pre Processing

    The only substatus of Completed is Successful.

  • URI: The URI for the source location, in the source dashboard only.

  • Type: The source or target type, in the source and target dashboards only.

  • Create Time: The date and time that the file was written to the source or target location.

5.4.2 Interpreting Dashboard Metrics

The Summary Statistics view displays a variety of statistics about recent transfers related to the artifact type for which the dashboard was opened. You can use these statistics to determine whether these transfers are used frequently, failing, or taking a long time to complete.

To determine how recent the transfers are, select one of these interval values from the View Data drop-down list:

  • Last Hour

  • Last 6 Hours

  • Last 24 Hours (default)

  • Last 3 Days

  • Last Week

The statistics displayed are:

  • Transfers: Total, Completed, Active, and Failed

  • Status: A pie chart of completed, active, and failed transfers

  • Most Active Artifacts: Names of the most active transfers, sources, or targets

  • Failure Ratio: The percentage of failed transfers

  • Payload File Size: Average, Minimum, and Maximum in bytes

  • Transfer Speed: Average, Minimum, and Maximum in bytes per second

  • Total Time: Average, Minimum, and Maximum in milliseconds

5.5 Interpreting Single Artifact Transfer, Source, and Target Dashboards

A single-artifact source, transfer, or target dashboard displays real-time and recent data for file deliveries, or instances, that is related to a specific artifact. Unlike the main Dashboard, an artifact dashboard must be opened.

The steps for this process are:

  1. Click the arrow to the left of Transfer Instances, Source Instances, or Target Instances in the left pane navigator.

    The artifacts of that type are listed.

  2. Click the artifact name or right-click it and then select the Open menu item.

    The dashboard tab for the artifact opens.

The views on an artifact dashboard are:

Unlike the views on the Main Dashboard, the views on the artifact dashboards have no Expand icons.

5.5.1 Interpreting Artifact Instance Messages

The Messages view is a searchable table of file delivery instance messages for the artifact for which the dashboard was opened. You can use % as a wildcard.

This table displays:

  • Report: Click on the report link to open a source, transfer, or target report. See Source Reports, Transfer Reports, or Target Reports.

  • Purge: Click Purge to remove the selected source instance and related target and transfer instances. The source is not deleted but only the selected source instance and its related target and transfer instances are purged from the system.

  • File Name: The name of the transferred file. The file might be renamed at the target; see Moving and Renaming Files After Delivery.

  • Size: The size in bytes of the transferred file. Compression or encryption might change the file size at the target; see Setting Up Source Processing Actions and Setting Up Transfer Preprocessing and Postprocessing Actions.

  • Create Time: The date and time that the file was written to the source or target location.

  • Status: Active, Failed, or Completed. Substatuses of Active are:

    • Delivery In Progress

    • In Progress

    • Paused

    • Pending

    • Pending Delivery

    • Post Processing

    • Pre Processing

    • Retrying

    • Scheduled

    Substatuses of Failed are:

    • Error

    • Partial Error

    • Post Processing

    • Pre Processing

    The only substatus of Completed is Successful.

  • Priority: Priority of the transfer.

5.5.2 Interpreting Artifact Information

The Artifact Information view displays the following information, if applicable, for the artifact for which the dashboard was opened. For sources, information about referencing transfers is also displayed. For transfers, information about the referenced source and targets is also displayed.

To open the artifact for which the dashboard was opened in a tab on the Designer page, click View Definition. See Creating a Source, Creating a Target, or Configuring a Transfer.

5.5.3 Interpreting Artifact Dashboard Metrics

The Summary Statistics view displays a variety of statistics about recent transfers related to the artifact for which the dashboard was opened. You can use these statistics to determine whether these transfers are used frequently, failing, or taking a long time to complete.

To determine how recent the transfers are, select one of these interval values from the View Data drop-down list:

  • Last Hour

  • Last 6 Hours

  • Last 24 Hours (default)

  • Last 3 Days

  • Last Week

The statistics displayed are:

  • Transfers: Total, Completed, Active, and Failed

  • Status: A pie chart of completed, active, and failed transfers

  • Failure Ratio: The percentage of failed transfers

  • Payload File Size: Average, Minimum, and Maximum in bytes

  • Transfer Speed: Average, Minimum, and Maximum in bytes per second

  • Total Time: Average, Minimum, and Maximum in milliseconds

5.6 Interpreting Source, Transfer, and Target Reports

A report provides a wealth of detailed information about the involvement of a source, transfer, or target in a specific file delivery instance.

You can access a report from:

You can also perform operations on transfers from reports. See Pause and Restart a Transfer and Resubmit a Transfer.

5.6.1 Using the Flow Diagram

At the top of every source, transfer, or target report is a flow diagram, which shows all artifacts related to the file delivery instance for which the report is generated. Figure 5-1 shows a typical flow diagram.

Figure 5-1 Flow Diagram

Description of Figure 5-1 follows
Description of "Figure 5-1 Flow Diagram"

The source is highlighted, indicating that this flow diagram is for a source report. You can click on the transfer or target icon to go to the transfer or target report. Each artifact has a green check, which indicates successful file delivery at each stage.

A down arrow to the right of an artifact indicates a fan-out. A flow diagram for a transfer with more than one target shows a fan-out at the target. Figure 5-2 shows a fan-out at the transfer, which means that more than one transfer uses the same source.

Figure 5-2 Flow Diagram with Fan-Out

Description of Figure 5-2 follows
Description of "Figure 5-2 Flow Diagram with Fan-Out"

The green gear on the source icon indicates that a preprocessing action, such as compression or encryption, is being performed at the source.

To display a list of all the artifacts in the fan-out, click the down arrow as shown in Figure 5-3. You can then select from the list and go to the report for that artifact.

Figure 5-3 Flow Diagram with Fan-Out List

Description of Figure 5-3 follows
Description of "Figure 5-3 Flow Diagram with Fan-Out List"

A flow diagram can also indicate warnings, errors, and resubmission attempts. Figure 5-4 shows a flow diagram for a file delivery instance that was resubmitted at the source.

Figure 5-4 Flow Diagram with Resubmission, Warning, and Error Icons

Description of Figure 5-4 follows
Description of "Figure 5-4 Flow Diagram with Resubmission, Warning, and Error Icons"

The green circle with the black arrow around it on the source icon indicates that a resubmit occurred. The yellow triangles with exclamation points indicate that warnings occurred at the source and transfer. The red circle with the exclamation point indicates that an error occurred at the target.

5.6.2 Source Reports

A source report includes the following sections:

  • Flow Display and Control: The flow diagram, Refresh button, report title, and Resubmit Source button

  • Summary: The file name, source location, payload size, resubmission count, and other basic information

  • Error: The error code, level, category, instance ID, timestamp, description, and other information about the error, if one occurred

  • Resubmitted Instances: The instance ID, user comment, user name, timestamp, and other information about the source resubmission, if one occurred

  • Transfer Instances: Information about transfers associated with the source. Click on a transfer name to go to the transfer report.

  • Source Processing: Information about preprocessing actions such as compression, decompression, and encryption

  • Advanced: Less commonly accessed information such as the source label and internal ID

  • Security: Information related to security, if applicable, such as algorithms, certificates, and encryption

For full details about the information displayed in source reports, see Source Report in the MFT Composer Online Help.

5.6.3 Transfer Reports

A transfer report includes the following sections:

  • Flow Display and Control: The flow diagram, Refresh button, report title, and Resubmit Transfer button

  • Summary: The file name, status, resubmission count, and other basic information

  • Error: The error code, level, category, instance ID, timestamp, description, and other information about the error, if one occurred

  • Resubmitted Instances: The instance ID, user comment, user name, timestamp, and other information about the transfer resubmission, if one occurred

  • Target Delivery: Information about targets associated with the transfer. Click on a target name to go to the target report.

  • Advanced: Less commonly accessed information such as the internal ID

  • Security: Information related to security, if applicable, such as algorithms, certificates, and encryption

For full details about the information displayed in transfer reports, see Transfer Report in the MFT Composer Online Help.

5.6.4 Target Reports

A target report includes the following sections:

  • Flow Display and Control: The flow diagram, Refresh button, report title, Pause button, Resume button, and Resubmit Target button

  • Summary: The file name, target location, total time, resubmission count, and other basic information

  • Error: The error code, level, category, instance ID, timestamp, description, and other information about the error, if one occurred

  • Resubmitted Instances: The instance ID, user comment, user name, timestamp, and other information about the target resubmission, if one occurred

  • Target Pre-Processing: Information about preprocessing actions such as compression, decompression, and encryption

  • Target Post-Processing: Information about postprocessing actions such as decompression

  • Advanced: Less commonly accessed information such as the transfer and target labels and internal target ID

  • Security: Information related to security, if applicable, such as algorithms, certificates, and encryption

For full details about the information displayed in target reports, see Target Report in the MFT Composer Online Help.

5.7 Pause and Restart a Transfer

You can pause an in-progress transfer from the target report, and restart a paused transfer.

You can access the target report in these ways:

  • In the File Finder view, change Search For to Target, search for the file or target name, then click the name of the target to open the report.

  • In the Active Deliveries view, click the name of the transfer to open the transfer report, then click the target icon in the flow diagram to open the target report.

Note:

If a transfer has multiple targets, you must pause the transfer for each target separately.

From the target report, click Pause to pause the file delivery to the target. To restart file delivery, click Resume.

5.7.1 Diagnose File Delivery Failures

Sometimes no error occurs, but a file does not arrive at the target location as expected. If this occurs, check the following settings:

5.8 Resubmit a Transfer

You can resubmit a successful transfer to redeliver the file. You can resubmit it from the source, transfer, or target report.

Click the Resubmit Source, Resubmit Transfer, or Resubmit Target button. If a transfer has a status of Failed, you can resubmit it to try again. Whether you resubmit from the source, transfer, or target report depends on where the failure occurred. For more information about errors, see Diagnose Transfer Errors.

Resubmission occurs immediately and any schedule defined in the parent artifact is ignored. For example, if you resubmit from the target, any schedule defined at the target is ignored. However, if you resubmit from the source, a schedule defined at the target is still honored.

Note:

You need to manually refresh the page to view the details of the resubmit status.

The Resubmit button may be disabled for a number of reasons, including:

  • The file to be transferred has been deleted.

  • The transfer is still in progress.

  • The transfer has a schedule and the delivery time is in the future.

  • The target artifact has been disabled.

  • You don't have permission to perform resubmit actions.

  • You don't have permission to resubmit this particular transfer.

5.9 Bulk Resubmit

You can resubmit messages in bulk using an asynchronous WLST command. Multiple criteria provide you with the flexibility to customize the resubmissions to meet your needs.

For example, you could choose to resubmit all the failed messages to a given target for a given duration or resubmit the source for all the instance messages for a given time duration.

Supported Criteria

Syntax:

resubmitMessages (resubmitType, state, artifactName, startDate, endDate, chunkSize, chunkDelay, ignoreIds, comments, previewMode)

You can choose from the following criteria for bulk resubmits:

Option Description Comments

resubmitType

SOURCE, TARGET, TRANSFER_INSTANCE, TARGET_INSTANCE

Required

Example: wls:/mydomain/serverConfig> resubmitMessages('SOURCE')

state

FAILED, COMPLETED, ACTIVE

Optional.

The system will consider all states (FAILED, COMPLETED, ACTIVE).

artifactName

The name of the artifact.

Optional.

Example: wls:/mydomain/serverConfig> resubmitMessages('SOURCE','FAILED', artifactName='test src')

startDate

endDate

Start and/or end date for message creation. Format: dd-MM-yyyy H:m:s:S

Optional.

Example: wls:/mydomain/serverConfig> resubmitMessages('SOURCE','FAILED', startDate="12-12-2050 00:00:00:00", endDate="30-12-2050 00:00:00:00")

chunkSize

Batch size for resubmit.

Optional.

Default = 1000 messages

chunkDelay

Delay in seconds between the two batch resubmits.

Optional

Default = 30 seconds

Example: wls:/mydomain/serverConfig> resubmitMessages('TRANSFER_INSTANCE','FAILED', artifactName='test transfer', chunkSize=100, chunkDelay=60, comments='test', previewMode='false')

ignoreIds

Comma separated list of corresponding message IDs to be ignored during resubmit.

Optional.

comments

Add any user comments.

Optional.

previewMode

When the command is run in preview mode, it lists the count of messages that will be resubmitted for the given criteria as well the entire WLST object.

Optional.

Default = true

If true, no record will be resubmitted. It can be used to get info such as how many records will be resubmitted for given criteria.

Example: wls:/mydomain/serverConfig> resubmitMessages('TRANSFER_INSTANCE','FAILED', artifactName='test transfer', startDate="12-12-2050 00:00:00:00", endDate="30-12-2050 00:00:00:00", chunkSize=100, chunkDelay=60, ignoreIds='42F03A2A-D8DB-4EF5-A295-246EA93FAB29,5A6AA40C-61CC-4B5B-8E65-0D3D27098CD0', comments='test', previewMode='false')

Chunking and Resubmit Delay Duration Support

The criteria given for a resubmit may result in a huge number of instances to be resubmitted and a high load on the system. To avoid such scenarios, you can optionally specify two options: chunkSize and chunkDelay. For example, if the resubmit criteria results in 1000 records and chunk size is 200 and resubmit delay is 30 sec then 5 chunks(1000/200) are created and the delay between two chunks is 30 sec.

Based on the average expected time to process the resubmit message, you should provide the appropriate chunk size and the delay time by either specifying the parameter as part of the resubmit command, or by overriding the system defaults using the Mbeans for these properties:

  • resubmitChunkSizeDefault

  • chunkResubmitDelayDefault

For more information about MBeans, see Understanding WebLogic Server MBeans in Developing Custom Management Utilities Using JMX for Oracle WebLogic Server.

5.10 Diagnose Transfer Errors

The unexpanded Recent Errors view on the Dashboard tab of the Monitoring page displays error codes, messages with endpoints, and timestamps.

The expanded Recent Errors view is a searchable table of errors, with additional information, including detailed descriptions, instance types (source, transfer, or target), levels, and severities. You can use % as a wildcard.

Clicking an error code in the unexpanded view or an error message in the expanded view opens the report for the source, transfer, or target at which the error occurred. The report includes an additional section with the error information. From the report, you can view additional information and resubmit the transfer; see Resubmit a Transfer.

5.10.1 Diagnosing Error Messages and Descriptions

For more details about specific error messages that can appear in the MFT Console, such as in the Recent Errors view, on the WLS command line, or in the diagnostic logs, see Error Messages.