Automate Desktop

Getting Started with Server Settings for Automate Enterprise

Chapter 8 | Automate 101

Get an overview of the different server settings available in Automate Enterprise. Ricky Wilcox, Presales Engineer, gives you a guided tutorial through each individual server setting. In this video you’ll learn the settings available for:

  • Data Store: the connection between Automate Enterprise and your backend database
  • SSL: determines if you want to use SSL to encrypt communications between the server component and all the connected agents in your environment
  • Email: how to set up a default email address for Automate to notify you of errors or messages
  • Log Management: controls how data is handled and determines how long execution data should be stored
  • Staging: provides the users with the capabilities to segregate workflows into distinct stages like production, development, or testing
  • Constants: global variables so you don’t have to create variables at every task or workflow level
  • SQL Connections: create the default SQL connections for Automate Enterprise
  • System Security: dictate permissions to specific users and user groups
  • Load Balancing: apply limitations to the number of currently running workflows
  • Holiday: configure and edit a custom holiday schedule
  • Management Console Sessions: determines various standards regarding individual user sessions
  • API Permissions: manage and protect Automate’s API resources through authentication
  • Revision Management: enable or disable the ability to revert a task or workflow object to a previous version and how long to keep previous versions

Watch this chapter now to learn how to get started.

 

Transcript

Ricky:           Today, we're gonna go through all the different service settings for Automate Enterprise. As you can see here, we have a handful of different things to go through. First, we'll go through data store. What data store is is it's defining that connection between your Automate Enterprise and where your back end database will be. As you can see here, we can configure and change it as needed. I'm really just about [00:00:30] pointing to a server, a database, and authenticating.

                                Next we have SSL. This determines whether you want to use SSL to encrypt your communication between the server component and all the connected agents in your environment. To use SSL, you want to make sure that you have a valid and registered certificate installed on the execution and management server.

                                Next we have email, so with [00:01:00] this configuration allows us to do is set up a default email to use for all of the standard email transmissions from Automate, so anytime you set up air handling or want to send messages inside of an Automate task or workflow, instead of having to configure that process or that credentials every single time, you can reference a default email address that you set up here. With the log management does is really controls how data's handled. [00:01:30] The parameters you see here below allow you to determine how long this execution data should be stored within Automate Enterprise.

                                Next we have staging, so what this allows you to do is staging really provides the users the capability to segregate workflows into distinct stages, so what that means is as you develop and build your workflows, you can set different stages on a production or in development testing, and with this will do is depending on the stage [00:02:00] you set, even though you have a completed workflow with tasks and various conditions and triggers assigned to it, it won't fire off, so basically you can check this box here and say only run workflows with a completion state equal or greater to whatever stage you'd like it to be, so that way, even though you've got these completed workflows, again fully complete with triggers and tasks, but you're not ready for them to run, if you put them in a stage like testing, for example, they won't fire off.

                                [00:02:30] Next we have contacts, so what constant are from an Automate perspective are really global variables, so instead of having to create tasks at the workflow level or variables at the task level or variables at the workflow level, what you can do is create a global variable called contents. You can edit and manipulate them, but you can come up here and click on a new, give them a [00:03:00] name, and give them a value. What this allows you to do is create these predefined variables, and you can reference them throughout any task in any workflow inside of Automate Enterprise.

                                Going on to SQL connection, so similar how you can create a default email address to use, sames goes for default connections. If you're doing a lot of database integration and [00:03:30] you don't want to have to define that connection every time you use it in a various task, you can predefine a lot of these connections here. That way, whenever you need to make that database connection, you can simply define one of your prebuilt connections versus, again, having to specify those parameters and those details every single time.

                                System security really allows you of dictate permissions for users and user groups really in order to protect Automate and the resources that it [00:04:00] uses, so what you're really saying is by defining these permissions, it's granting a user or user group permission to edit settings in the environment, generate reports, look at the dashboard, things like that. Again, it can be either user group added or an individual user.

                                Load balancing allows us to apply some limitations to the number of concurrently running workflows. You can determine the amount of workflows to run simultaneously [00:04:30] by checking this box here and applying that number. Any workflow that has been triggered that is above this concurrent number would be placed into a queue until a workflow completes, and then the next one in the queue would automatically start up.

                                What this bottom checks box allows us to do is if a server were to reboot ... On startup, for example, you don't want necessarily a bunch of workflows to fire up. This allows you to put a little delay in between that fire off and/or place those workflows into a queue. These holiday setting really [00:05:00] allows you to configure and edit a custom holiday calendar. This holiday calendar's really used in conjunction with the schedule condition, so if you had your own corporate company holiday you wanted to import into this, for example, you can simply edit these fields, add your company holidays and then apply that using a schedule condition to make sure that your task and workflows don't fire off on any one of your company holidays.

                                The management console sessions [00:05:30] really determines various sessions regarding to a user session. Enable user lockout, for example, so you can determine if a user has incorrectly typed their password a certain amount of times in a certain amount of minutes. We can lock them out and then determine how long we want to keep that person locked out of the environment and also enable a session time so if you're logged in and you forget to log off and close out of Automate Enterprise, we can set some factors that [00:06:00] will kick the user out of your session just for security reasons.

                                API security is found in Automate Enterprise Edition. It really just gives the administrators the ability to manage and protect Automate Enterprise API resources through authentication. With the API security, you can assign elements of authority to various users and user groups. The types of permission you can determine are these calls here, so being [00:06:30] able to make calls against your different tasks and workflows and other information inside of the Automate environment.

                                Lastly, we have revision management, and this is a brand new feature in 11.1. What revision management is for us is being able to revert a task or workflow or object in the Automate Enterprise environment to a previous version, so what you need to do is essentially come up here to enable so that, again, you can go back and look at historical information and be able to undo changes in your Automate environment, [00:07:00] but what you're setting up here is first you're enabling the revision management, but also defining how long you want to hold on to previous version based on the number of previous versions or maybe a certain amount of time before previous versions get deleted.

Ready for the next chapter?

Chapter 9: Variables, Datasets, and the Expression Builder