base node

Consequently, each registered base node might have different user registries configured if security is enabled.

The administrator role is required for you to register or deregister a base node with the administrative agent.

Once a base node has been federated with a deployment manager, it should only be administered through the deployment manager.

is a self contained copy of the administration runtime used to manage a base node.

When working with the administrative subsystem, the required administrative roles to the registered base node are needed.

When a job runs on a registered base node or deployment manager, the user must have privileges that include the role required for that job.

Two new types of nodes are derived from the base node: one for video and another for a podcast.

Similarly the flying robots are required to lay and maintain communications pathways between a base node and users in the environment.

This enables the administrator to continue to use the base node without the ability to manage it with the administrative agent.

For each base node registered with the administrative agent, a new managed node configuration object is created.

After a base node is removed from a deployment manager federation, it can be registered with an administrative agent.

uses the configuration files of the base node that it manages.

If John were to submit a job against the deployment manager cell or the second base node, the job will fail since John is not authorized.

For the same user registry scenario, John may submit a job against the first base node without specifying user name and password.

John can submit a job for the first base node without having to specify a user name or password.