Used in
Application Server Administration Parent elements
PSERVERS VSERVER Syntax
| <PSERVER | Attribute Description Table |
When parent element is PSERVERS and adding a Spatial Server:
(r)machine="string"
type="add"
When parent element is PSERVERS and deleting a Spatial Server:
(r)id="string"
(r)machine="string"
type="remove"
When parent element is VSERVER and associating the Spatial Server to a Virtual Server:
(r)id="string"
(r)threads="integer"
>
No Child Elements
</PSERVER >
|
(r): Attribute or child element is required.
|
Description
Allows adding, removing, and setting the number of instances for an ArcIMS Spatial Server using the command line.
Notes
- PSERVER is used one of two ways:
- When PSERVERS is the parent element, PSERVER is used to add or remove a Spatial Server.
- When VSERVER is the parent element, PSERVER is used to first assign a Spatial Server to a Virtual Server and secondly to assign the number of instances for that Spatial Server.
- PSERVER is used to administer ArcIMS Spatial Servers from the command line. To do this, two files are used:
- An ADMINCMD XML file
- A batch file or script
The ADMINCMD XML file contains the instructions for adding, starting, stopping, and removing ArcIMS services. See the examples for proper construction of an ADMINCMD XML file.
On Windows, the batch file contains one line:
<jre directory>\java.exe com.esri.aims.admincore.cmd.Exec http://mymachine.domain.com Username Password file filename
Where:- <jre directory>\java.exe is the location of a java.exe file. If the directory path has spaces, you must use quotes, for example, "C:\Program Files\arcGIS\ArcIMS\Jre\bin\java.exe"
- http://mymachine.domain.com is the host machine.
- Username is the user name for ArcIMS administration.
- Password is the password for ArcIMS administration.
- Filename is the full pathname and name of the ADMINCMD XML file, for example, c:\arcims\axl\admincmd.xml.
- Note: the parameter "file" must be included before the filename.
The above command can also be typed on the command line in lieu of using the batch file.
On UNIX, a script file is used. In the following example, note that the line beginning with "java -cp" is all one line:
#!/bin/csh
setenv JARHOME $AIMSHOME/Manager/lib
setenv AIMSHOST $argv[1]
java -cp $JARHOME/jaxp.jar:$JARHOME/parser.jar:$JARHOME/esri_mo10.jar:
$JARHOME/esri_mo10res.jar:$JARHOME/arcims_admincore.jar:$JARHOME/arcims_admin.jar:
$JARHOME/jcert.jar:$JARHOME/jnet.jar:$JARHOME/jsse.jar:$JARHOME/arcims_resadmin.jar com.esri.aims.admincore.cmd.Exec http://$AIMSHOST Username Password file $argv[2]
Where:- $argv[1] is the hostname.
- $argv[2] is the name of the ADMINCMD XML file, for example, admincmd.xml.
- Username and Password are the username and password for ArcIMS adminstration.
- Note: the parameter "file" must be included before $argv[2].
Attribute Descriptions for PSERVER
When parent element is PSERVERS and adding a Spatial Server:| Attribute | Usage |
|---|
| machine | Machine name where Spatial Server resides. Include the domain (mymachine.domain.com) if applicable. |
| type | Use "add" to specify adding a Spatial Server. |
When parent element is PSERVERS and deleting a Spatial Server:| Attribute | Usage |
|---|
| id | Spatial Server name to remove such as mymachine.domain.com_5. |
| machine | Machine name where Spatial Server resides. Include the domain (mymachine.domain.com) if applicable. |
| type | Use "remove" to specify removing a Spatial Server. |
When parent element is VSERVER and associating the Spatial Server to a Virtual Server:| Attribute | Usage |
|---|
| id | Spatial Server name to add to a Virtual Server such as mymachine.domain.com_5. |
| threads | Number of instances (or threads) to assign to the Spatial Server. |
Back to top Examples for PSERVER
Example 1: When adding a new Spatial Server (PSERVER) or to associate one or more Spatial Servers with a Virtual Server (VSERVER)<?xml version="1.0"?>
<ADMINCMD version="1.0">
<!--Add two new Spatial Servers-->
<PSERVERS>
<PSERVER type="add" machine="mymachine"/>
<PSERVER type="add" machine="mymachine"/>
</PSERVERS>
<!--Create a new Image Server-->
<VSERVERS>
<VSERVER type="add" name="ImageServer2" access="Public" description="ImageServer Example" servicetype="ImageServer" version="" >
<!--Associate the new Spatial Servers to the new Image Server-->
<PSERVER id="mymachine_4" threads="2"/>
<PSERVER id="mymachine_5" threads="2"/>
</VSERVER>
</VSERVERS>
<!--Add and start an Image Service-->
<SERVICES>
<SERVICE type="add" name="world_image" axl="c:\arcims\axl\myworldservice.axl" vsname="ImageServer2" imgloc="c:\arcims\output" imgurl="http://mymachine.domain.com/output" imagememory="4" cleanup="20" imgtype="GIF" />
<SERVICE type="start" name="world_image" />
</SERVICES>
</ADMINCMD> |
Example 2: When removing a Spatial Server.<?xml version="1.0"?>
<ADMINCMD version="1.0">
<VSERVERS>
<VSERVER type="remove" name="ImageServer2"/>
</VSERVERS>
<PSERVERS>
<PSERVER type="remove" machine="mymachine.domain.com" id="mymachine.domain.com_4"/>
<PSERVER type="remove" machine="mymachine.domain.com" id="mymachine.domain.com_5"/>
</PSERVERS>
</ADMINCMD>
|
Back to top