Automate Desktop

Getting Started with System Settings

Chapter 7 | Automate 101

Learn about the many system settings within Automate to help you make the most out of your solution. This video gives you an overview of each system setting available, from Task Service settings to SNMP settings. Join Andrew Usher, Technical Representative, as he takes you through each option and provides you with the information you need to customize Automate. In this video, you’ll get an overview of the following:

  • System Settings menu
  • Log Management settings
  • Backup & Restore settings
  • Service User settings
  • Execution settings
  • Plus, many more

Start this chapter now and learn how to customize Automate with a variety of setting features.



[Andrew Tewksbury:] So what you can see here are a number of settings that we can define for this system. So if we take a look at the first setting, Task Service, this is where we can define the TCPIP and the HTTP ports for the Automate task service. We can also define where the default [00:00:30] manage task location is. So basically, this is where your AML files that are created are stored.

Then we have your Indicators as well, so really this is where you can define how to stop a task or interrupt a task if it's running, and really you have an option in the bottom right, for example, when a task is running it can give you an update of whereabouts [00:01:00] in that step, how far in that step is it processed, how far is it in the actual task. So it gives you a running update of where that task is in terms of completion.

You have the Remote Administration. This basically allows you to connect your runtime agents into your desktop version of Automate. So this is where you define a password, and then when you connect that runtime [00:01:30] agent into Automate you will need to enter this password in there.

We have the Log Management. So really, this basically is what do you want to log. Do you want to log when a task starts, when it fails, when the step started, when the step ends? There are a number of things that you can log, and also you can actually define where these logs are stored. So at the moment they are stored in the program data [00:02:00] in your C drive, but you can actually define them to a location of your choice.

Due to the size of these logs, over a period of time they're obviously going to grow, so we can actually trim these logs into how much we want to trim these during the process. It is also worth noting that we can actually log ... Create our logs and send them to a database as well, so we can store the information in a database.

[00:02:30] We have the Backup & Restore. Again, as simple as it sounds, if you want to back up your Automate settings environment, your tasks and triggers, then we can specify the backup option, the location where you wish to store the backup, and whether you want to include the backup tasks and triggers or include the constants and system preferences. Equally, the same goes for the restore. Do you want to just restore the tasks and its triggers, [00:03:00] or do you want to restore the constants and system preferences as well?

We have the Event Monitor User. Here is the Event Monitor User, so we can have the first user logged on, or you can actually specify user as well.

We have Constants. So constants are a really useful feature within the product. Unlike a variable, a constants value never changes unless [00:03:30] you change it within here. So a variable is a placeholder for information that can be updated within a task. A constant, again, is a placeholder for information, but it cannot be updated within a task. The key thing with constants here is that if you reference a constant within your task, you don't have to go into that task to automatically update the value of that constant. What you need [00:04:00] to do is you need to go into the Constants page that we're on here now, and just update the constant within.

Creating or updating a constant is very simple. First of all you click on New, specify the name of your constant, so we can say Name and then we want to say if we use that constant, then it's going to have the name Andrew. Equally, to modify it we can just click Modify and then [00:04:30] we can change the name as well. Changing this name here automatically updates wherever this constant is referenced across all of your tasks, so it can actually save you time by having to go into each individual task to rename this constant, whereas all you need to do is just come into this window, rename the constant as shown, and it's as simple and easy as that.

We have SQL Connections. Again, SQL connections [00:05:00] within here are very useful, this is where you predefine your SQL connections. So you can, for example, click on New, and again reference what you'd like your SQL connection to be called, and then you go and build your connection. So you reference your provider, and then you look at your SQL server, so where is your SQL server, what is the instance you wish to connect to, and you can reference a specific username or password in here as well, [00:05:30] and then after that you reference what database you wish to connect to on there.

So if we take a quick look at the one I created earlier, we can see that this is the server we want to use. We're not using a specific username and password, we're using the one we log on with, and this is the database we wish to connect to. What you can do at the end is do a test connection to ensure that the SQL connection is successful and works.

[00:06:00] Load Management. This could be very useful if you have multiple tasks running on one machine, and you don't want to obviously overload your machine and run it down. What we can do is we can specify how many tasks are running at one moment in time, and once that limit is reached how many tasks can actually be stored in the queue so that, once one finishes, the next one starts.

[00:06:30] SNMP. This is where you reference where your MIB files are located, and this is the port that we need to listen for traps on.

Your Service User. This is basically what you want your Automate service to run under. If you leave this as default, it runs under your default machine policy. If not, and you've referenced a username and password within here, it will run under there.

[00:07:00] You have your Execution. How fast do you want your steps to run? Sometimes maybe it's not best practice to get your tasks to run as quick as possible because sometimes it may actually miss steps out. And this is the option, is that when you use interactivity actions this will keep the window that we're working on in the foreground, and it won't time out, so that we can always have a hold on that task, that window.

[00:07:30] Finally, we have the Holidays. Within here, there are a number of countries, and we have all of their holidays listed. And as you can see as well, we have a list of all the different holidays that are around. If there's any specific ones that you want to add in, say for example you have your financial month end process, then we can actually name this as a financial month end, and then we can actually [00:08:00] reference the date that it is as well. Again, nice and simple.


Ready for the next chapter?

Chapter 8: Getting Started with Server Settings for Automate Enterprise