Legolas Woodland wrote:
>
> Hi, Thank you for the answer.
>
> Please correct me about the following statement:
>
> Usually all asadmin commands take a host and port parameters, but they
> are the address of the application server which we like that the
> command affect them. for example if i execute
>
> "create-jdbc-connection-pool --host 192.65.36.69 <http://192.65.36.69>
> --port 8989 ...."then it will create the connection pool on the server
> which is running on the remote computer,
>
Wherever the application server is installed(even locally), the --host
and --port will be used to communicate to the DAS. If the application
server is installed locally and the DAS port is 4848 then you donot need
to mention the --host and --port. By default --host is localhost and
--port will be whatever set in install/config/asadminenv.conf (by
default it is set to 4848). So even in local machine asadmin will use
the --host --port parameters to talk to DAS. If you mention --echo=true
in any command you will see the list of parameters being passed to asadmin.
Since create-jdbc-connection-pool is a operation that has to be
performed by the DAS the --host and --port will be immediately used by
the asadmin to talk to DAS and hence it becomes a remote command. So a
command becomes remote or local based on whether it needs to talk to
DAS. If it needs to talk to DAS it becomes remote, if not it is a local
command.
> but now on my local host glassfish server, Am I correct about the
> statement?
>
> It is different for the create-node-agent command, because --port and
> --host point to the DAS address instead of the address of the
> application server which we want to create a node agent for it. <== Is
> it correct?
>
In create-node-agent command --host & --port is supplied to tell the
node agent whom it needs to talk to when it starts up. The --port and
--host will not be used right away, hence it is a local command since it
is not communicating with the DAS when the command is executed.
>
> "generally we have two tyes of asadmin commands, remote commands and
> local commands." If it is correct, what commands are remote and what
> commands are local?
>
The command manpage will tell whether a command is local or remote, in
V3 the asadmin list-commands will list local and remote commands separately.
>
> Thank you.
>
>
> On 6/16/08, *Sankar Neelakandan* <Sankar.Neelakandan_at_sun.com
> <mailto:Sankar.Neelakandan_at_sun.com>> wrote:
>
> Hi Legolas,
> When you create nodeagent you mention --host and --port
> parameters to the asadmin command which will be used to
> communicate to DAS.
>
> asadmin create-node-agent --host ipaddress_or_hostname --port
> das_port_number node_agent_name
>
> -Sankar
>
>
> Legolas Woodland wrote:
>>
>> Hi Wolfram,
>>
>> Can you please tell me how does NA understand the IP address of
>> the DAS?
>>
>> Should we tell it the DAS address beforehead?
>>
>> Thanks
>>
>>
>> On 6/16/08, *Wolfram Rittmeyer* <w.rittmeyer_at_jsptutorial.org
>> <mailto:w.rittmeyer_at_jsptutorial.org>> wrote:
>>
>> Hi Legolas,
>>
>> actually it is the node agent who notifies the DAS of its
>> creation. If the DAS is down at the time of creation the NA
>> retries periodically until the intial contact has taken place.
>>
>>
>> --
>> Wolfram Rittmeyer
>>
>>
>>
>> Legolas wood wrote:
>>
>> Hi
>> Thank you for reading my post.
>> Can someone please explain how does DAS find out that we
>> create a
>> node-agent in one of our computers in the network?
>> should we introduce the node agent to the DAS or there
>> are some
>> discovery mechanism in place?
>>
>> Thanks
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> users-unsubscribe_at_glassfish.dev.java.net
>> <mailto:users-unsubscribe_at_glassfish.dev.java.net>
>> For additional commands, e-mail:
>> users-help_at_glassfish.dev.java.net
>> <mailto:users-help_at_glassfish.dev.java.net>
>>
>>
>