Here's a link to the Monarch Server Automator tutorial - http://docs.datawatch.com/datawatchserver/Monarch_Server_Automator_Tutorial.pdf
Scheduling is in Lesson 3 (for setting up for nightly production).
Hope this helps get you started!
Thanks for posting your question.
Typically with Automator, the training is delivered by Professional Services.
Automator has a lot of functionality, core areas being;
- Standard Processes
- Visual Processes
- Command line options
- API capabilities
- Multiserver deployment to support complex requirements (e.g. active/passive standby, failover)
Within each of these is substantial functionalities but not all will necessarily be relevant to your requirements or you might need advise on what to best leverage and how to do so to meet your specific needs.
The way the training is delivered, we go through and cover the application functionality and then have a workshop where you would bring along existing input sources, models and projects. We upgrade them to run in Automator and in doing so, take advantage of all the extra functionalities that subsequently make the process richer (e.g. wildcard input processing, alerting, input / output distributions).
The workshop is usually 0.5 days but we can extend this further if desired either based on fixed deliverables or just a block of time in which we try and cover as much as is possible in the same.
It's just not possible to provide a single document that would give you all of what you are asking given the complexities and variety that the product allows in terms of deployments and functional usage.
There are a number of items on the community that discuss many of the features and abilities but again, whether they are relevant to you is subjective.
If you want to discuss the training offering further, you can speak to your Account Manager or alternatively, call us directly on +1800.445.3311 or: +1978.441.2200, option 3 for training.
Hope this helps.
The full set of documentation is available on Product Documentation - Datawatch Corporation
See link for Automator Documentation. Theres some extra stuff there also.
Oh - and in regards to accessing files on the network - make sure the services are running using a domain account that has permissions to the resources you either want to read or write to.
When specifying paths, you should use UNC's to prevent issues with mapped drive letters; this gives you better portability and removes the dependency of drive letters being mapped in the first instance and mapped consistently in the second.
You might want to make use of the Named Paths functionality also to help store these in a more friendly way; essentially you add them to the Named Paths library and instead of having to remember the path each time, you just pick it from the drop down.