This section discusses the general structure of an XML element.
For detailed information about each object,
see the
package summary file.
See also the full export example topic.
Each object tag in the XML document contains:
An object type, such as virtual-host
A name attribute that identifies the particular resource on which
to perform the action
An action attribute that controls the behavior of the import or
partial export operation
For example, an application server named MyAppServer has the following object tag:
In this case, the action is update. The following list describes all of the
available actions.
Unless otherwise stated, actions apply only to the import operation.
create
Adds the specified resource to the administrative domain. If the resource
already exists, the create action is treated as an update action.
When using this action, you must specify all required attributes for the object
type.
update
Updates the properties of a specified resource. You need only specify the
properties that you want to update.
However, if the resource does not exist, the update action becomes a create.
In such a case, if some of the properties are not specified, an error
occurs.
delete
Removes the specified resource and its children (recursive delete).
locate
Locates the specified resource. Use this action to provide the containment
path to specific child resources.
Applies to the partial export operation as well as the import operation.
export
Exports the configuration of the specified resource and its children to
the output XML document. Applies only to the partial export operation.
start
Starts the specified resource (if applicable).
stop
Stops the specified resource, (if applicable).
stopforrestart
Stops the specified resource, and restarts it.(if applicable). Node only.
restart
Stops the specified resource and starts it again (if applicable).
enable
Makes the specified resource available for user requests (currently applies
only to servlets and Web applications).
disable
Makes the specified resource unavailable for user requests (currently applies
only to servlets and Web applications).
Some operational actions, such
as start and stop, do not apply to all object types.
In general, if the operation
is supported in the WebSphere Administrative Console, it is supported in the XML
import operation.