There is a way to run the AdminClient using the local option.
The allows the server-config.wsdd to be created in the directory you run
the client from. Here is an example from my ant script. I have left
out my classpath, etc...
... Copy over a template file
<!-- Run admin client to deploy, then copy to WEB-INF -->
<copy tofile="./server-config.wsdd" overwrite="true"
file="${server-config.wsdd}"/>
... Undeploy
<java fork="yes" classname="org.apache.axis.client.AdminClient">
<arg value="${undeploy.wsdd}"/>
<arg value="-llocal://"/>
<classpath refid="classpath.deploy"/>
</java>
... Deploy
<java fork="yes" classname="org.apache.axis.client.AdminClient">
<arg value="${deploy.wsdd}"/>
<arg value="-llocal://"/>
<classpath refid="classpath.deploy"/>
</java>
... List
<java fork="yes" classname="org.apache.axis.client.AdminClient">
<arg value="-llocal://"/>
<arg value="list"/>
<classpath refid="classpath.deploy"/>
</java>
On Tue, 2003-09-30 at 09:59, Massimo Barabino wrote:
> Hi,
> I' m running the axis context on a host wich isn' t assigned the
> localhost (127.0.0.1) address but a LAN IP address instead.
> It seems the AdmniClient requires enableRemoteAdmin true, otherwise it
> returns a 'Forbidden' error. I copied the server-config.wsdd file from
> another old axis installation into my webapp/WEB-INF dir, added the
> enableRemoteAdmin true parameter and everithing works fine.
> My question is the following.
> Suppose I have just one fresh axis installation (the server-config.wsdd
> hasn' t been created yet) not on the localhost. The server-config.wsdd
> file gets created only when I deploy some services, but the AdminClient
> won't run untill I specify the remoteAdmin param in the server-config
> file. Obviously I cannot specify such param because the file doesn' t
> exist yet.
> How can I solve this? Is there another way (apart from deploying
> services) to create the server-config file?
>
> Thanks in advance
>
> Massimo Barabino
--
Benjamin Tomasini
NetEverything, Inc.
1-877-270-1391
