By msreddy on Sep 17, 2007
The asadmin component comes in 2 flavors, remote and local. By remote, the commands are communicated via http/s to DAS and needs the command name and arguments, the admin user id, password, host name and port are automatically provided. The local command doesn't need the admin user id, and password so no values are automatically provided to the local command.
In addition to running adhoc asadmin commands, it is possible to save the commands for repeated/later use by using 'Create Component' version of Remote and Local commands.
Pl. see the image below to visualize the N1SPS admin console support for asadmin commands under the category of 'Other Tasks'.
Remote Command: This procedure allows user to execute an asadmin remote command on multiple domains as the targetable host. The required variable is "asadminCommand" and "asadminArguments" is optional.
Create Remote asadmin Component: This procedure popups a wizard for user to create a custom component from the generic asadmin remote component. User can name the component to easily identify the asadmin command and can be tracked in the "Activity Log". User can overwrite the variables "asadminCommand" and "asadminArguments". When executing the custom component, user will not required to create a variable set since the default values already contain the values that are required to execute the command.
Local Command: The procedure is similar to the "Remote Command" except the asadmin is executed locally. The targetable host is the AppServer Install virtual host name.
Create Local asadmin Component: This procedure is similar to the "Create Remote asadmin Component" except the custom component created is for executing asadmin command locally.
To understand how the provisiong works with the Application Server, pl. refer to Prashant's blog on Provisioning GlassFish V2 with N1SPS.
I would like to thank Jane Young for providing certain content for the above blog.