Main Components

Maybe it is worth to start with main components. AR System is a server-client environment and composed of two components: AR Server and AR Client.

AR Server is responsible for processing the server requests. Do not  even think to write your own AR Server!! :) For sure it is optimized. AR Client is the tool where you can use the application built by AR System. (Most probably it will be an ITSM application). AR Client sends the user requests to the AR Server and gets the response back. Of course BMC has made it compatible to many environments and provided choices. If you would like to use it from your PC, Remedy User tool would fit for your purpose. It is a Windows based client tool. You also have the option to use Remedy Midtier to use your application from web. These two tools are typical AR Client tools.

AR System generally has more than one server: Node and Race. Node server is the one where you generally run your workflow and on Race server, you keep the configuration data and archive data. You usually need a synchronization between these two servers because you would use the configuration data on node server which is your main server. Or you may need to archive some data from node to race for a better performance. For these reasons, BMC invented DSO server which does this synchronization.

Remedy Developer is used for designing forms and workflow. All application design and application rules are made with using Remedy Developer.

For data importing, AR System provides a separate tool AR Import. With this tool, you can import form data easily and you do not need to consider database issues.