Anode versus Dnode licensing
Article ID: 111933
Updated On:
Products
Issue/Introduction
When looking at the license key (COMM) .pdf file, the Platform is listed as ANODE or DNODE - what is the difference between these two?
Environment
Component: Automation Engine
Resolution
Deployment Nodes:
License Code: DNODE
Platforms: Any AUTOMIC supported Operating System
Explanation and Example:
Any "server or virtual" machine that needs to be included within an AUTOMIC automation process or against which AUTOMIC needs to execute a script, need to be licensed as a deployment node.
For certain mid-tier and mainframe systems, each partition or LPAR is deemed to be a Node. For the automation of Web Services, each URL is a Node. Example - a web application running on 2 web application server, and one DBMS server, will require 3 Deployment Nodes even though the AUTOMIC Database adapter may perform a number of automated functions on an agentless basis.
Application Nodes:
License Code: ANODE, ANODE-USER
Platforms: Any AUTOMIC supported Independent Software Vendor (ISV).
Explanation and Examples:
Any logical instance of an ISV application or data warehouse supported via an AUTOMIC adapter must be licensed as an Application Node in order to be included in an AUTOMIC automation process. **IF LICENSED ON A PER INSTANCE BASIS**, each Application Node includes a Deployment Node (right to deploy relevant OS Agent on the machine running the ISV instance).
Example 1 - an application running on 2 web servers, 1 application server, and 1 DB server requires 4 Nodes - 3 Deployment Nodes and 1 Application Node.
**IF LICENSED ON A PER USER BASIS**, Deployment Nodes must be purchased separately for non-APA process automation.
Example 2 - a SAP application with 100 users, running on 4 web servers, 3 application back-end servers and 1 DB server requires an Application Node for 100 users + 5 Deployment Nodes + up to 3 D-Nodes if the application servers need to be included in ITPA processes such as SAP System Copy or ARA.
Attachments
Feedback
