Connectors in mule
- 2. The File connector allows your Mule application to exchange files with a file system. The connector can be configured to filter the file it reads and the way files are written, such as whether Mule places the output in a new file or appends the output to an existing file.
- 3. General : Display Name Path Move to Pattern Connector Configuration Polling Frequency File Age File Name Regex Filter File Name / Pattern
- 4. Advanced : Address Response Timeout Encoding Disable Transport Transformer MIME Type Connector Endpoint
- 5. Display Name : Defaults to the generic endpoint name. Change the display name, which must be alpha-numeric, to reflect the endpoint’s specific role, such as Order Entry Endpoint Path : The target directory on the connected file system. If File is implemented as an inbound endpoint, this would be the location within the connected file system of the file being transferred into the flow. For an outbound File endpoint, this would be the directory on the connected file system to which the file currently in the flow is written.
- 6. Move to Pattern : (Applies to inbound File endpoints only) . The pattern to be used when moving a file according to the Move to Directory property. It can use the patterns specified by the filename parser configured (often through a Connector template) for this particular File endpoint. Connector Configuration : Use the dropdown list to select a previously created connector configuration for this endpoint. If you have not created a connector configuration for this type of endpoint, you can do so from this window by clicking Add . Click Edit to modify a previously created global element.
- 7. Polling Frequency : (Applies to inbound File endpoints only.)Specify how often the endpoint should check for incoming messages. The default value is 1000 ms. File Age : (Applies to inbound File endpoints only.)Sets a minimum period a file must wait before it is processed. This helps ensure that long files are received in their entirety before processing starts. However, Mule and the connected file system must be on synchronized time for this feature to work properly.
- 8. File Name Regex Filter : (Applies to inbound File endpoints only.)Configure a filter to restrict the files being processed. File Name / Pattern : (Applies to outbound File endpoint only). Specify a filename or pattern for naming files that are sent from the File endpoint to the connected file system. If not set, the File endpoint uses the same file-naming pattern used for incoming files.
- 9. Address : Enter the address for this endpoint, like http://localhost:8081/file. Response Timeout : Specify how long (in ms) the endpoint waits for a response from the connected file system. Encoding : Choose from a drop-down list the character set used for message data. (such as UTF-8).
- 10. Disable Transport Transformer : Check this box if you do not want to use the endpoint’s default response transport. MIME Type : Select from the dropdown list one of the formats this endpoint supports. Connector Endpoint : Use the dropdown list to select a previously configured global endpoint reference. If you have not created a global element for this type of endpoint, you can do so from this window by clicking Add. Click Edit to modify a previously created global element.
- 11. The Quartz Connector supports the scheduling of programmatic events, both inside and outside your Mule flow. An inbound quartz endpoint can be used to trigger inbound events that can be repeated, such as every second. Outbound quartz endpoints can be used to schedule an existing event to fire at a later date. Users can create schedules using cron expressions, and events can be persisted in a database.
- 12. The attributes under general properties available while configuring Quartz connector are : Display Name Cron Expression Repeat Interval Repeat count Start delay Job : Connector Configuration
- 13. a. Display Name : It can be anything. b. Cron Expression : A cron expression is a string comprised by six or seven fields in it separated by white space. Fields can contain any of the allowed values, along with the various combinations of allowed special characters for that field.
- 14. We can use cron expressions to create schedulers. Cron expression can be as simple as : * * * * ? *. More complex expression is : 0 0/5 14,18,3- 39,52 ? JAN,MAR,SEP MON-FRI 2002-2010. The CronTrigger uses the powerful "cron expressions" that helps to set more powerful schedules like "Executing a job every Thursday morning at 6.00 AM" or "Executing a job at 45 minutes past midnight on a daily basis" etc.
- 16. c. Repeat Interval : This acts as a default scheduler. If no cron expression is given, then this helps in providing the required time schedule. But this is not as powerful as cron. It has only three fields : Hours, minutes and seconds. We cannot use this repeat interval to schedule for a day in a week or month or year.
- 17. d. Repeat count : Represented in milli seconds. If the Repeat Count is 0, then the instruction will be interpreted as FireNow. If the Repeat Count is > 0, then the instruction will be interpreted as RescheduleNowWithExistingRepeatCount. If the Repeat Count is -1, then the instruction will be interpreted as FireNowAndRepeatForever.
- 18. e. Start delay : Represented in milli seconds. It is the delay before starting the job for the first time. f. Job : Jobs are used to perform an action when a time trigger occurs from the Quartz component. Mule provides number of jobs for generating and scheduling events.
- 19. g. Connector Configuration : Use the dropdown list to select a previously configured connector configuration for this endpoint. If you have not created a connector configuration for this type of endpoint, you can do so from this window by clicking Add. Click Edit to modify a previously created global element.