This page describes the Resources tab in the Appian RPA Console. You'll use this tab to setup and monitor resources, which connect to the Console via agents. Agents establish communication between the resource and the Appian RPA Console. Agents are required to be up and running for robotic processes to execute properly and communicate the results back to the console.
Through the Resources tab on the Appian RPA Console, you can access to the list of resources associated with your user profile.
Admins can set up new resources to run robotic processes. Developers won't see this option in the Appian RPA Console.
To execute a robotic process on a new resource, remember to install the agent.
This list displays all resources available for your user, based on your permissions. You can access the details of a resource by clicking on any of its columns.
The resources are listed in alphabetical order in a grid with the following information:
You can perform several actions on resources in the list. Actions depend on the resource's connectivity, whether the agent is started, and on whether its status is "Online" or "Offline."
Click the lock icon to access the resource's permissions management. You can add new permissions and select or deselect existing permissions. This action is not available for basic users.
|Switches off a resource with connectivity and "Online" status.|
|Switches on a resource with connectivity and "Offline" status.|
|Removes the session currently associated with the resource. Useful when we do know that the session doesn't exist anymore, but the console needs more time to be sure of that.|
|Production||A production resource has no restriction at all.|
|Development||A development resource is not permitted to execute robotic processes that take more than 2 hours.|
|Development without restrictions||In the same console there can be, at most, one resource of this type.|
|Remote development||A resource specifically configured to remote development, where the resource is the one connecting to the developer.|
|Windows resource||The agent is executed on a Windows operating system.|
|Linux resource||The agent is executed on a Linux operating system.|
|macOS resource||The agent is executed on a macOS operating system.|
Appian RPA components rely on shared tags for security. Users, robotic processes, and resources must have tags in common to see and interact with each other.
To assign permissions to a resource:
Some information is related to the computer where the agent is running, and other information is related to the agent itself.
Depending on whether the resource has connectivity, and on whether its status is "Online" or "Offline", different icons will be available.
|If the resource is offline and its license has not expired, you can download the agent to install it on your computer.|
|Launch the remote-control screen for a resource with connectivity. If the resource was disabled, it may look like it is "Offline" but even so you can access it remotely.|
|Disables the local plugins of the agent. It only works if the agent, in the moment of its creation, plugins was added in it and these are enabled.|
|Enables the local plugins of the agent. It only works if the agent, in the moment of its creation, plugins was added in it and these are disabled.|
|Lock the input from the keyboard and the mouse on a resource with connectivity. Only available if the agent is executed on the resource using an administrator profile.|
|Unlock the input from the keyboard and the mouse on a resource with connectivity. This action works only if the agent is executed on the resource using an administrator profile.|
|Send an agent for remote debugging. A new executable is downloaded on the resource, named jidoka-remote.exe, specifically designed for debugging robots remotely when you cannot debug them directly on the port involved.|
|Execute the agent for remote debugging.|
|Stop the agent from remotely debugging (only on the resource under remote debugging).|
|Executes the agent for remote debugging (JJDWP). This debugging is less common and requires its own execution setup. By clicking on this icon, a pop-up window will ask you for the IP, port and timeout for the connection.|
|Stops the agent from remotely debugging (JJDWP). Unlike the non-JJDWB version, this debugging must be stopped from the resource that launched it, and not from the resource being debugged.|
|Restart the agent, so that it can initiate itself and prevent, among other things, low memory problems in the computer where it is running, that is, the resource.|
|Completely remove the resource from the console. This action cannot be undone and is only available for "ADMIN" profiles.|
In the context of Appian RPA and its resources, a container is a set of software elements guaranteeing the right execution of a robotic process, assuring the environment is always the same. For this reason, the configuration of a resource helps keep the executions from being influenced by changes in the environment.
From section Container configuration, it is possible to configure two different types of containers for a resource: Docker and VirtualBox. Depending on the chosen container, we must fill some fields or others.
Once the configuration is done, the console is able to integrate with the container to start and to stop it.
For a Appian RPA Docker image sample, contact your Appian RPA administrator.
Additionally, it is possible to use Kubernetes as a Docker containers manager.
For Docker, you have to fill the following fields:
Putting all together, the console generates a Docker command to send to the machine to start or stop it.
For VirtualBox, you have to fill the following fields:
Putting it all together, the console generates a VirtualBox command to send to the machine to start or to stop it.
This option is only available for Administrator and Developer users.
You can remotely visualize and operate the desktop on which the robot is running.
To start monitoring, click on the Monitor icon (), which will show you a set of icons that allow you to perform certain actions on the desktop where the robot is executing.
|Take a screenshot|
|Request the log file. It allows you to download the local error log.|
|Open the scripts editor Groovy. It allows you to execute Groovy code on the client.|
|Control remotely. It will show the position of the mouse pointer on screen, allowing you to click and drag elements on the desktop as usual. By enabling it, you will also see a text box where you can send text to the resource as well as the coordinates of the mouse pointer.|
It is important that you click on the Monitor icon again after you have finished monitoring the resource. This way the agent will consume fewer resources while there is no need for monitoring.
When you restart services, a request is sent to the agent for it to try to restart the open connections with the console. This functionality should only be used under maintenance tasks of the agent, as it is more advisable to relaunch the agent from the console and manually restart the agent, in this order, when you detect any issue with its operation. You can also restart the resource automatically.
The agent's requirements for RAM memory are low. However, depending on the version of the operating system, RAM available, the number of robots in execution, and maximum memory assigned to the agent, memory usage may increase too much. To avoid this situation, you can make a resource to restart automatically when a specified percentage of the total memory is exceeded.
For example, suppose you want to specify on a 2GB memory resource, that the agent should restart whenever the memory used by the agent exceeds 1.6 GB, that is, 80% of the total.
On the resource details, enter that percentage of memory not to be exceeded. This will trigger an event to restart the agent whenever it is exceeded. Events are explained in detail on the Monitoring page.
On This Page