Do I need to install both the Server and the Node on every machine?

No. Only one Server instance is required. All tests are to be launched from the machine that has the Sage Server instance. The Server will distribute behavior files to the target Nodes via message. This gives Sage users the ability to control complex test scenarios, involving multiple nodes and agents across various machines, from a single controller entity.

How can I verify the server is running?

To verify a running Sage Server instance, check the prompt window and confirm that the following text is displayed, “Sage server started listening on port: IP_portNo”. This indicates that the Sage Server is active and listening over the selected port.

Is there a default port number that is commonly used?

There is no default port number for Sage. It is recommended to avoid using dedicated port numbers, such as 21 (FTP), 22 (SSH), and 80 (HTTP). For a list of unassigned port numbers visit Internet Assigned Numbers Authority (IANA).

When I deploy Sage agents to other VMs, how can I verify that they are fully operational?

It is important to not confuse the terms Sage agents and Sage nodes. Sage agents are created on-the-fly using a Sage controller interface (Robot Framework by default). Currently, there is only support for agent creation using Built-in Sage keywords, Create Agent. When you create an agent, it is deployed to a Sage Node. Sage nodes are containers that are deployed to a VM/machine. These containers store agents upon their creation.

When you initialize a node, you will assign it a IP Address and a port number value. The IP Address value should be the IP Address of the server VM/machine. The port number must match that of the recipient server’s port number. A matching port number and valid IP is essential for connecting a node to the intended Sage Server. Once connected, check the prompt window for the following text, “Connected to Sage runtime using ip address IP_address : IP_portNo”, to verify the node is operational. It is recommended to download the example files to get a better understanding of the Sage Node deployment and agent creation process.

Why am I getting a python27.dll is missing error when attempting to connect a Sage Node?

This error either means there are multiple Python instances installed on your machine, a non-supported Python version installed on your machine, or your installed Python bit version differs from that of the installed Sage. Sage currently supports Python 2.6 or 2.7. Be sure you have one of the two installed. Next, be sure the bit version is consistent with the installed Sage bit version. To check the Python bit version, start Python in the command prompt and it will display the bit number. Check your Python directory e.g C:\Python27 and verify that the python27.dll file is there. If not, it is recommended to uninstall the current Python instance and to do a fresh install. Be sure your Environment variables PYTHONHOME and PATH are set and updated, respectively. Visit here to learn how to add and edit environment variables.

Why am I getting a jvm.dll is missing error when attempting to connect a Sage Node?

This error either means there are multiple Java instances installed on your machine, a non-supported Java version installed on your machine, or your installed Java bit version differs from that of the installed Sage. Sage currently supports Java 8 . Be sure you have a supported version installed. Next, be sure the bit version is consistent with the installed Sage bit version. To check the Java bit version, type java -version in the command prompt. Check your Java JDK server directory e.g C:\Program Files\Java\jdk1.8.0_91\jre\bin\server and verify that the jvm.dll file is there. If not, it is recommended to uninstall the current Java instance and to do a fresh install. Be sure your Environment variables JAVAHOME_x64 or JAVAHOME_x86 and PATH are set and updated, respectively. Visit here to learn how to add and edit environment variables.

Why am I receiving a ‘sageframework.SageLocalInterfaceWrapperPINVOKE’ exception upon starting the Sage Server Application?

The Sage Server Application goes through a behavior discovery process to locate local “Native”, “Java”, and “Python” behavior files. This exception is thrown if both Java and Python are not found on your machine. Be sure your Environment variables PYTHONHOME, JAVAHOME_x64 or JAVAHOME_x86, and PATH, are set and updated. Visit here to learn how to add and edit environment variables.

How do I resolve “error while loading shared libraries: libjvm.so” when starting a Node on Linux?

SAGE needs JVM dynamic library to be in the runtime library search path. This is accomplished by including the location in the LD_LIBRARY_PATH environmentvariable. This is typically done by including the definintion in .bashrc file or .profile file. It can also be temporarily set using the same command, typically: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:{JRE_HOME}/lib/amd64/server.

Why am I getting “ImportError: No module named robot”?

This error is returned when the robot framework module cannot be found. By default, robot-framework is distributed with SAGE and appended to the Environment variables CLASSPATH system Environment variable upon install. Be sure to verify that the robotframework-2.9.2.jar is located in the “C:\Program Files\NRL\SageServer” directory. In addition, check the Environment variables CLASSPATH environment variable to ensure the absolute path to the jar “C:\Program Files\NRL \SageServer\robotframework-2.9.2.jar” has been added and appears as the first item in the list.