Topics: |
You can control many key aspects of DataMigrator Server operations directly from the DMC.
The DMC allows you to:
You can set up your DataMigrator Server to send an email message that notifies recipients of the successful completion or failure of every flow execution.
In addition, from the DMC, you can enable the distribution of email messages at any point in a process flow.
However, to enable either variation on the email notifications process, you must first configure a SMTP service. (You need to set up your server for email before it will work anywhere in the flow.)
Note: You must be logged on as a Server Administrator with the appropriate privileges to make these configurations.
The Scheduler Configuration dialog box opens.
The DataMigrator Scheduler runs as a task under the iWay DataMigrator Server. The Scheduler must be running to submit flows and stored procedures and to execute scheduled data flows and flows that run in parallel groups in a process flow. The following image shows the Scheduler Configuration dialog box.
The Scheduler Configuration dialog box contains the following fields/options:
Specifies whether the Scheduler should check for flows automatically. The options are:
Automatically starts the Scheduler when the server starts. This is the default value.
Does not start the Scheduler when the server starts.
Note: The Scheduler must be running to execute not only scheduled data flows, but also restarted flows and flows run in parallel in a process flow.
If this option is enabled, the DFM listener will start with the server.
Specifies the application name of the location of deferred requests and reports.
Specifies the physical location of the deferred requests and reports, if the dfm_app value is not set.
This is the agent service that the DataMigrator Scheduler will use when running DM flows. If this is not set, the DEFAULT service will be used.
Specifies the time interval in seconds between restart attempts for all restartable flows. The default value is 60.
Note: This value cannot be less than 0.
Specifies the number of times that failed agents will be restarted. If the value is 0, they will not be restarted. If it is -1, they will be restarted indefinitely. The default value is -1.
Specifies how often CMASAP agents are removed from the agents list, in seconds. When set to -1, this is never. The default value is 300.
Maximum number of lines that the DataMigrator Scheduler is to write to the log for each flow. When the maximum number of lines is reached, logging stops. When set to -1, the number of lines is unlimited. When set to 0, there is no logging.
The default value is set to 20.
Note: Some essential lines will still be imposed into the ETL LOG, even when the number of lines (sched_log_lines) is limited to a positive integer.
Select this option to have a separate log file for every job.
The name of the application in which the individual log and statistics files are located. This option is only applicable if you select sched_standalone_log.
Specifies the maximum time interval in seconds that can elapse before log data is committed to the DataMigrator log. The default value is 10.
Specifies the maximum number of log lines to collect before committing them to the DataMigrator log. The default value is 1000.
Select this option to set the output from a report to go to the log. Only text output is displayed to a maximum width of 80 characters. This is the prior behavior.
Note: To view report output, in the browser, right-click on the flow name and click Logs. Then, click Last Output to view the output from the last run, or select Log and Statistics. For Report Range select All, and then right-click the job id in the report and click Show Output.
Specifies the maximum number of days that deferred reports are kept.
Specifies the maximum size of a deferred report.
Sends an email when the Scheduler starts.
Sends an email when the schedule completes.
Sends an email if the schedule fails.
Specifies the email attachment size limit, in Kb.
Enter an email address, user ID, or procedure name.
If this option is enabled, the schedule specified for server wide email will be followed.
If this option is enabled, the email address associated with the user ID will be retrieved from the security provider.
Note: Before you can use email notification, you must configure an email server. For more information, see How to Configure the Server for E-mail Notification.
If the Scheduler is running, select Stop.
If the Scheduler is not running, select Start.
APPLICATION-level administrators can change their configured passwords from the DMC.
The User Information dialog box opens.
Note: Changes to the password will take effect the next time the server or scheduler is restarted.
To enable email notifications, you must first configure an SMTP service. (You need to set up your server for email before it will work anywhere in the flow.)
The E-mail SMTP Server dialog box opens, as shown in the following image.
Note: If an antivirus program is running on this computer, please make sure that the tscom3.exe, edapgwy.exe, and edaplog.exe processes are excluded.
Never send email.
Send email when a flow finishes.
Send email when a flow fails.
Note: This setting applies to every flow.
The Miscellaneous Settings dialog box opens, as shown in the following image.
The following Miscellaneous Settings are saved in the edaserv.cfg file:
Determines whether the server will automatically recover crashed listeners and/or special services. The default is n.
Selecting y, activates the iWay Transaction Coordinator. A Two-Phase Commit will be used when XA-Compliant databases participate in a transaction. The default is n.
Defines the time (in seconds) allowed for an agent to stop before soft kill is sent. The default is 16.
Defines the time (in seconds) allowed for a soft kill to work before a hard kill is sent. The default is 32.
By default, crashed agents are kept in the agents table for diagnostics purposes, and are only removed when they are explicitly killed. When this set to y, crashed agents are automatically removed from agents list when the Workspace Manager detects a crash. The default value is n.
If crashed_cleanup is set to y, this determines the number of memory dump files retained for later diagnosis.
Defines the time window in seconds for the calculation of running response time averages. The default is 600.
Specifies whether to encode HTML tags in data as plain text in order to prevent attacks by inserting executable code into data. Valid values are y and n. The default value is n.
Defines a proxy server, which acts as an intermediary on requests for resources from other servers.
Defines the port number of the proxy server.
Defines a user ID for the proxy server.
Defines a password for the user ID connecting to the proxy server.
Required for SSL when using self-signed certificates on i5 systems.
Required for SSL when using self-signed certificates on i5 systems.
Required for SSL when using self-signed certificates on i5 systems.
Required for SSL when using self-signed certificates on i5 systems.
Required for SSL when using self-signed certificates on i5 systems.
Defines the upper limit for the number of rows in a session log. When the limit is exceeded, only the latest records will be kept in the session log and the number of records will equal the limit. The default is 1000.
Defines the time in seconds to wait before the popup timer appears. The default is 5.
For details on the server configuration, see the Server Administration manual.
The Core Engine Global Variables dialog box opens.
The Configuration Files Backup dialog box opens.
Application settings control some aspects of use of application directories. You must be a server administrator to change any of these settings, and they require a restart of the server to take effect.
When you connect to the server, a temporary directory called foccache is added as the first directory in the search path. When you want to be able to reuse data within the same session, you can store the data in the form of a HOLD, SAVE, or SAVEB file in the foccache directory. As long as the session remains active, the files stored in the foccache directory can be referenced in requests. Foccache is also used to store some system created temporary files.
To change server application settings:
The Application Settings dialog box opens, as shown in the following image.
The following options are available:
Defines the location of the foccache directory. The default location is edatemp/foccache/....
Defines the maximum number of minutes that a foccache directory will last. When the maximum foccache retention time is reached, the foccache directory is removed by the server and can no longer be referenced. The default is 180 minutes.
When set to y, nested applications are enabled. This is the default value. To disable, set to n.
Lists the file extensions that are allowed for upload files.
A home application directory provides each user with a private application directory with full access privileges to store private focexecs and data for the test runs and ad hoc reports.
The operating system specific pathname. Defines the location of home application root directory. If defined, each connected user will see the My Home applications folder on the Application tree. User can create new applications (home applications) in this folder. These applications will be visible and available only to the connected user and the server administrators. The user will have full access to their home applications. For this setting to work, nested_app should be set to y.
Global variables can be used by various users, regardless of the fact that each user has their own profile, by changing a listener configuration property.
Note: This is available for HTTP Listener only.
The Listener Configuration dialog box opens.
The values of any global variables will now be kept active as long as you stay connected to the server.
WebFOCUS | |
Feedback |