Before using this information and the product it supports, read the information in “Notices and trademarks” on page 1011.
First Edition (December 2008)
This edition applies to version 3, release 7, modification 2, level 0 of IBM WebSphere DataPower XML Security
Gateway XS40 and to all subsequent releases and modifications until otherwise indicated in new editions.
IBM®WebSphere®DataPower®SOA Appliances are purpose-built, easy-to-deploy
network appliances that simplify, help secure, and accelerate your XML and Web
services deployments while extending your SOA infrastructure. These appliances
offer an innovative, pragmatic approach to harness the power of SOA while
simultaneously enabling you to leverage the value of your existing application,
security, and networking infrastructure investments.
Who should read this document
This document is intended for administrators of IBM WebSphere DataPower who
are responsible for the configuration and maintenance of web services, security,
and data communications equipment. These administrators are expected to have
familiarity with XML and XSLT.
This document assumes that you have installed and initially configured the
appliance as described in the IBM WebSphere DataPower SOA Appliances: 9003:
Installation Guide or in the IBM WebSphere DataPower SOA Appliances: Type 9235:
Installation Guide, depending on the model type.
Publications
The IBM WebSphere DataPower library is organized into the following categories:
v “Installation and upgrade documentation”
v “Administration documentation” on page xx
v “Development documentation” on page xx
v “Reference documentation” on page xx
v “Integration documentation” on page xxi
v “Problem determination documentation” on page xxi
v “Supplemental documentations” on page xxi
Installation and upgrade documentation
v IBM WebSphere DataPower SOA Appliances: 9003: Installation Guide
Provides instructions for installing and powering up the Type 7993 (9003)
appliance, creating a startup configuration script, and placing the appliance in
operation.
v IBM WebSphere DataPower SOA Appliances: Type 9235: Installation Guide
Provides instructions for installing and powering up the Type 9235 appliance,
creating a startup configuration script, and placing the appliance in operation.
v IBM WebSphere DataPower SOA Appliances: Type 9235: Hardware Problem
Determination and Service Guide
Provides information about diagnosing and troubleshooting hardware problems,
ordering consumable replacement parts, and replacing parts.
v IBM WebSphere DataPower SOA Appliances: Upgrade and Rollback Guide: Generation
2 Firmware
Provides instructions for upgrading Generation 2 firmware and for rolling back
firmware upgrades.
v IBM WebSphere DataPower SOA Appliances: Appliance Overview
Provides an introduction and understanding of the IBM Websphere DataPower
SOA appliances.
v IBM WebSphere DataPower SOA Appliances: Administrators Guide
Provides instructions for using the DataPower GUI for managing user access,
network access, appliance configuration and system configuration of the
appliance.
v IBM WebSphere DataPower SOA Appliances: Hardware Security Module Guide
A user guide for using a Hardware Security Module (HSM) installed in the
appliance.
Development documentation
v IBM WebSphere DataPower SOA Appliances: XSL Accelerator Developers Guide
Provides instructions for using the WebGUI to configure XSL Proxy and XSL
Co-Processor services.
v IBM WebSphere DataPower SOA Appliances: XML Firewall Developers Guide
Provides instructions for using the WebGUI to configure XML Firewall services.
v IBM WebSphere DataPower SOA Appliances: Web Application Firewall Developers
Guide
Provides instructions for using the WebGUI to configure Web Application
Firewall services.
v IBM WebSphere DataPower SOA Appliances: Multi-Protocol Gateway Developers
Guide
Provides instructions for using the WebGUI to configure Multiple-Protocol
Gateway services.
v IBM WebSphere DataPower SOA Appliances: Web Service Proxy Developers Guide
Provides instructions for using the WebGUI to configure Web Service Proxy
services.
v IBM WebSphere DataPower SOA Appliances: B2B Gateway Developers Guide
Provides instructions for using the WebGUI to configure B2B Gateway services.
v IBM WebSphere DataPower SOA Appliances: Low Latency Messaging Developers
Guide
Provides instructions for using the WebGUI to configure a DataPower appliance
for low latency messaging.
Reference documentation
v Product-specific documentation for using commands from the command line.
The documentation is specific to each of the following products. Each document
provides an alphabetical listing of all commands with syntactical and functional
descriptions.
– IBM WebSphere DataPower XML Accelerator XA35: Command Reference
– IBM WebSphere DataPower XML Security Gateway XS40: Command Reference
– IBM WebSphere DataPower XML Integration Appliance XI50: Command Reference
– IBM WebSphere DataPower B2B Appliance XB60: Command Reference
– IBM WebSphere DataPower Low Latency Messaging Appliance XM70: Command
Reference
xxCommand Reference
v IBM WebSphere DataPower SOA Appliances: Extension Elements and Functions
Catalog
Provides programming information about the usage of DataPower XSLT
extension elements and extension functions.
Integration documentation
The following documents are available for managing the integration of related
products that can be associated with the DataPower appliance:
v IBM WebSphere DataPower SOA Appliances: Integrating with ITCAM
Provides concepts for integrating the DataPower appliance with IBM Tivoli
Composite Application Management for SOA.
v IBM WebSphere DataPower SOA Appliances: Integrating with WebSphere
Transformation Extender
Provides concepts for integrating the DataPower appliance with WebSphere
Transformer Extender.
v IBM WebSphere DataPower XML Integration Appliance XI50: WebSphere MQ
Interoperability
Explains the concepts and common use patterns for connecting DataPower
services to WebSphere MQ systems.
Problem determination documentation
v IBM WebSphere DataPower SOA Appliances: Problem Determination Guide
Provides troubleshooting and debugging tools.
Supplemental documentations
v IBM WebSphere DataPower SOA Appliances: Understanding Web Services Policy
Provides conceptual information about how the DataPower appliance can use
Web Services Policy (WS-Policy).
v IBM WebSphere DataPower SOA Appliances: Understanding WS-Addressing
Provides conceptual information about how the DataPower appliance can use
WS-Addressing.
v IBM WebSphere DataPower SOA Appliances: Understanding LTPA
Provides conceptual information about how the DataPower appliance can use
Lightweight Third Party Authentication.
v IBM WebSphere DataPower SOA Appliances: Understanding SPNEGO
Provides conceptual information about how the DataPower appliance can use
SPNEGO.
v IBM WebSphere DataPower SOA Appliances: Optimizing through Streaming
Provides conceptual information about and procedures for optimizing the
DataPower appliance through streaming.
v IBM WebSphere DataPower SOA Appliances: Securing the Last Mile
Provides conceptual information about and procedures for understanding the
DataPower appliance while securing the last mile.
v IBM WebSphere DataPower SOA Appliances: Configuring the DoD PKI
Provides conceptual information about and procedures for configuring the
DataPower appliance with Department of Defense Public Key Infrastructure.
Prefacexxi
Reading syntax statements
The reference documentation uses the following special characters to define syntax:
[]Identifies optional options. Options not enclosed in brackets are required.
...Indicates that you can specify multiple values for the previous option.
|Indicates mutually exclusive information. You can use the option to the left
of the separator or the option to the right of the separator. You cannot use
both options in a single use of the command.
{}Delimits a set of mutually exclusive options when one of the options is
required. If the options are optional, they are enclosed in brackets ([ ]).
When the order of the options or parameters must be used in a specific order, the
syntax statement shows this order.
Directories on the appliance
The file system contains many examples and critical configuration files. These
directories and their contents are as follows:
audit: This directory contains the audit logs. Each appliance contains only one
audit: directory. This directory cannot be the destination of a copy. This
directory is available from the command line in the default domain only.
To view the audit log from the WebGUI, select Status → View Logs → Audit
Log.
cert:This encrypted directory contains private key and certificate files that
services use in the domain. You can add, delete, and view files, but you
cannot modify these files while in the domain. Each application domain
contains one cert: directory. This directory is not shared across domains.
chkpoints:
This directory contains the configuration checkpoint files for the appliance.
Each application domain contains one chkpoints: directory. This directory
is not shared across domains.
config:
This directory contains the configuration files for the appliance. Each
application domain contains one config: directory. This directory is not
shared across domains.
dpcert:
This encrypted directory contains files that the appliance itself uses. This
directory is available from the command line in the default domain only.
export:
This directory contains the exported configurations that are created with
the Export Configuration utility. Each application domain contains one
export: directory. This directory is not shared across domains.
image: This directory contains the firmware images (primary and secondary) for
the appliance. This directory is where firmware images are stored typically
during an upload or fetch operation. Each appliance contains only one
image: directory. This directory is available in the default domain only.
local:This directory contains miscellaneous files that are used by the services
within the domain, such as XSL, XSD, and WSDL files. Each application
domain contains one local: directory. This directory can be made visible to
xxiiCommand Reference
other domains. When viewed from other domains, the directory name
changes from local: to the name of the application domain.
logstore:
This directory contains log files that are stored for future reference.
Typically, the logging targets use the logtemp: directory for active logs. You
can move log files to the logstore: directory. Each application domain
contains one logstore: directory. This directory is not shared across
domains.
logtemp:
This directory is the default location of log files, such as the
appliance-wide default log. This directory can hold only 13 MB. This
directory cannot be the destination of a copy. Each application domain
contains one logtemp: directory. This directory is not shared across
domains.
pubcert:
This encrypted directory contains the security certificates that are used
commonly by Web browsers. These certificates are used to establish
security credentials. Each appliance contains only one pubcert: directory.
This directory is shared across domains.
sharedcert:
This encrypted directory contains security certificates that are shared with
partners. Each appliance contains only one sharedcert: directory. This
directory is shared across domains. However, you must be in default
domain to create or upload keys and certificates.
store:This directory contains example style sheets, default style sheets, and
schemas that are used by the local appliance. Do not modify the files in
this directory.
Each appliance contains only one store: directory. By default, this directory
is visible to all domains. You can make changes to the contents of this
directory from the default domain only.
The store: directory has the following subdirectories:
metaThis encrypted subdirectory contains files that are used by the
appliance itself.
msgcat
This subdirectory contains the message catalogs.
policies
This subdirectory contains the following subdirectories. The
contents of these subdirectories affect Web services policy.
custom
This subdirectory contains custom style sheets.
mappings
This subdirectory contains mapping style sheets.
templates
This subdirectory contains XML files.
profiles
This subdirectory contains style sheets that are used by DataPower
services.
Prefacexxiii
schemas
dpThis encrypted subdirectory contains files that are used by the
pubcerts
tasktemplates:
This directory contains the XSL files that define the display of specialized
WebGUI screens. Each appliance contains only one tasktemplates: directory.
This directory is visible to the default domain only.
temporary:
This directory is used as temporary disk space by processing rules. Each
application domain contains one temporary: directory. This directory is not
shared across domains.
Object name conventions
The name must be unique in this object namespace. The following characters in an
object name are valid:
v a through z
v A through Z
v 0 through 9
v _ (underscore)
v - (dash)
v . (period)
This subdirectory contains schemas that are used by DataPower
services.
appliance itself. This subdirectory is available from the command
line only.
This encrypted subdirectory contains files that are used by the
appliance itself. This subdirectory is available from the command
line only.
Typeface conventions
The following typeface conventions are used in the documentation:
boldIdentifies commands, programming keywords, and GUI controls.
italicsIdentifies words and phrases used for emphasis and user-supplied
variables.
monospaced
Identifies user-supplied input or computer output.
xxivCommand Reference
Chapter 1. Initial login and common commands
This chapter provides an alphabetic listing of the commands that are available
before entering a specific configuration mode (available at initial login) and
commands that are available in most, if not all, configuration modes.
Initial login commands
For a list of the commands that are available after an initial login, refer to Table 1.
This table provides a listing of the available commands and their purpose. To
determine whether these commands are available to a specific user-type class after
an initial login, refer to Table 2.
Table 1. Initial login commands and their general purpose
CommandPurpose
1
alias
1
clock
configure terminalEnters Global configuration mode.
1
disable
disconnectCloses a user session.
echoEchoes text to the console.
enableEnters Privileged mode.
execCalls and runs a target configuration script from another
exitCloses the CLI connection.
helpDisplays online help.
loginLogs in to the appliance as a specific user.
1
ntp
pingDetermines if a target host is reachable on the network.
showDisplays configuration or status information
shutdown
2
switch domainMoves to a specified domain.
template
test schema
1
1
test tcp-connection
topReturns users to their initial log in mode.
traceroute
1
Creates a command macro.
Sets the date or time.
Enters User Mode.
configuration script.
Identifies an NTP server.
Restarts or shuts down the appliance.
Runs an interactive command line script.
Tests conformity of an XML file against a schema.
1
Tests the TCP connection to a remote host.
Traces the network path to a target host.
1
Also available in Global mode.
2
Also available in Flash configuration mode.
Table 2. Commands by type of user that are available after initial login
Commandadmin userPrivileged-type userUser-type user
Table 2. Commands by type of user that are available after initial login (continued)
Commandadmin userPrivileged-type userUser-type user
clockYesYesNo
configure terminalYesYesNo
disableYesYesNo
disconnectYesYesNo
echoYesYe sYes
enableNoNoYes
execYesYesNo
exitYesYe sYes
helpYe sYesYes
loginYesYesNo
ntpYesYesNo
pingYesYe sYes
showYesYesYes
shutdownYesYesNo
switchYesYe sYes
templateYesYe sYes
test schemaYe sYesYes
test tcp-connectionYesYesYe s
topYe sYesYes
tracerouteYe sYesYes
Common commands
For a list of the commands that are available in most configuration modes, refer to
Table 3. This table provides a listing of the available commands and their purpose.
Table 3. Common configuration commands and their general purpose
CommandPurpose
admin-stateSets the administrative state of an object.
cancelCancels changes to the current object and returns to the parent
disconnect
1
echo
1
exit
1
help
1
ping
resetRestores default values.
1,2
show
summarySpecifies a brief object-specific comment.
test tcp-connection
traceroute
configuration mode.
1
Closes a user session.
Echoes text to the console.
Applies changes to the current object and returns to the parent
configuration mode.
Displays online help.
Determines if a target host is reachable on the network.
Displays configuration information
1
Tests the TCP connection to a remote host.
1
Traces the network path to a target host.
2Command Reference
admin-state
Syntax
Parameters
Table 3. Common configuration commands and their general purpose (continued)
CommandPurpose
1
The command is also available after initial log in, which is before you explicitly enter
a configuration mode. To determine whether these commands are available to a
specific user-type class after an initial login, refer to Table 2 on page 1.
2
The output from the command differs when invoked after initial log in and when
invoked while in a configuration mode.
Sets the administrative state of an object.
admin-state {enabled | disabled}
enabled
(Default) Places an object in the enabled (active) state
disabled
Places an object in the disabled (inactive) state
alias
Guidelines
The admin-state command sets the administrative state of an object.
Administrative states are not equivalent to operational states. When an object has
an administrative state of enabled, its operational state might be up, down,or
pending. However, when an object has an administrative state of disabled, its
operational state is always down.
Examples
v Disables the object.
# admin-state disable
#
Creates a command macro.
Syntax
alias alias command
no alias alias
Parameters
aliasSpecifies the name of the object.
command
The name can contain a maximum of 32 characters. For restrictions, refer to
“Object name conventions” on page xxiv.
Specifies a sequence of commands and arguments.
Chapter 1. Initial login and common commands3
Guidelines
Also available in Global configuration mode.
If creating a macro that uses multiple commands, you can either
v Surround the string in quotes and separate commands with a semicolon. For
example:
alias eth0 "configure terminal; interface ethernet 0"
v Separate commands with an escaped semicolon. For example:
alias eth0 configure terminal\;interface ethernet0
Use the no alias command to delete a command macro.
Related Commands
show alias
Examples
v Creates an alias eth0. When invoked, moves to Interface configuration mode
(with the configure terminal and interface commands) for Ethernet Port 0.
# alias eth0 configure terminal\;interface eth0
Alias update successful
#
v Creates an alias mgmport. When invoked, moves to Interface configuration mode
with the configure terminal and interface commands) for Management Port 0.
# alias "mgtport configure terminal; interface management 0"
Alias update successful
#
v Creates an alias back2. When invoked, moves back two configuration modes. If
invoked from Validation Credentials configuration mode, moves to Global
configuration mode.
# alias back2 "exit; exit"
Alias update successful
#
v Creates an alias proxies. When invoked, displays information about XSL Proxy
objects.
# alias proxies show xslproxy
Alias update successful
#
v Creates an alias update-cfg. When invoked, restarts the appliance with an
updated configuration script.
# alias update-cfg configure terminal\;flash\;del config:runningconfig.cfg\;
copy http://10.10.1.1/configs/39.3.cfg config:///runningconfig.cfg\;
boot config runningconfig.cfg\;shutdown
Alias update successful
#
v Deletes the eth0 alias.
# no alias eth0
Alias 'eth0' deleted
#
cancel
Cancels changes to the current object and returns to the parent configuration mode.
4Command Reference
Loading...
+ 1036 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.