®

IBM Software Group

IBM WebSphere Application Server V7

Properties-file-based configuration

Ganesan Karuppaiah

WebSphere® Support Technical Exchange

1
 IBM Software Group

Agenda

Overview

Introduction to PropertiesBasedConfiguration

Extracting properties from configuration files.

Validating properties files.

Applying properties files to configuration.

Creating properties file Templates.

Creating and deleting configuration objects using
properties files examples.

Additional WebSphere Product Resources/Links

Questions?

WebSphere® Support Technical Exchange 2 of 25

2
 IBM Software Group

Overview

WebSphere Application Server configuration
repository consists of multiple files in XML and
other formats, spread across many directories.

These configuration objects are complex.

Property files, consisting of name/value
pairs, are more human readable than
other configuration files.

Similar to the old XMLConfig export/import
commands in WebSphere V3.5 and V4

WebSphere® Support Technical Exchange 3 of 25

Until WebSphere version V4, separate relational database was used for
WebSphere configuration data. Along with command line tool wscp
(WebSphere Control Program) we also had another tool "XMLConfig". This
XMLConfig is used to export and import data from database repository.
Using this, WebSphere administrator can extract (export) the WebSphere
configuration from database to a single xml file.

Starting from V5, WebSphere started using xml based configuration files and moved
away from database dependencies for its configuration repositories. During
this change XMLConfig feature did not make it to V5 and from V5 onwards
WebSphere administrators are left with 3 choices. Console, wsadmin, and
Public JMX APIs.

Console is very easy to navigate. Few customer use custom built JMX programs
(using WebSphere APIs) for their administration. Majority of the WebSphere
administrators are using “wsadmin” as their favorite command line
administration tool. Though we have provided a list of sample commands in
our information center, basic understanding of jython/jacl is needed to use
wsadmin tool more effectively.

3
 IBM Software Group

PropertiesBasedConfiguration

WebSphere Application Server V7.0 introduces a simple
properties file based configuration feature that can be used
as a tool for querying and modifying configuration objects.

Application servers

Nodes

Profiles

Virtual hosts

Authorization tables

Data replication domains

Variable maps

Java™ Database Connectivity (JDBC) providers

Uniform Resource Locator (URL) providers

Mail providers

Resource environment providers

Java™ 2 Connector (J2C) resource adapters

WebSphere® Support Technical Exchange 4 of 25

Starting from V7 , new AdminTask commands introduced to help WebSphere

administrators. This is similar to the old XMLConfig tool. Collection of these new
AdminTask commands are called "PropertiesBasedConfiguration". This is used for
querying and modifying configuration objects with simple properties file. This
requires no prior knowledge in Jython or wsadmin and is easy to use.

4
 IBM Software Group

PropertiesBasedConfiguration

Properties file based configuration is not a replacement for
configuration archives and these commands do not extract
all configuration attributes, only the most commonly used.

You can extract the configuration attributes and values
from your environment to properties files.

Copy configuration properties from one environment to
another.

Troubleshoot configuration issues. Apply one set of
configuration properties across multiple profiles,nodes,
cells, servers, or applications.

Note: You cannot apply a z/OS® operating system properties file to a

distributed operating system. Similarly, you cannot apply a distributed
operating system properties file directly to a z/OS operating system.

WebSphere® Support Technical Exchange 5 of 25

It is very important to note that, properties file based configuration is not a

replacement for configuration archives. "Properties file based configuration"
commands do not extract all configuration attributes. We get only the most
commonly used property: value pair.

Properties file based configuration tool can be used in conjunction with

configuration archives for moving profile from one environment to another. Use
configuration archive exportWasprofile command to export the entire cell
configuration to a configuration archive. Follow with properties file based
configuration to make customizations.

AdminTask ConfigArchiveOperations commands.

* exportProxyProfile * importProxyProfile
* exportProxyServer * importProxyServer
* exportServer * importServer
* exportWasprofile * importWasprofile
(Note: Only a base server configuration with single node is supported for the
exportWasprofile command.)

5
 IBM Software Group

PropertiesBasedConfiguration
AdminTask Description
AdminTask.extractConfigProperties Extracts configuration data in the form of
a properties file

AdminTask.validateConfigProperties Verifies that the properties in the

properties file are valid and can be safely applied to
the new configuration

AdminTask.applyConfigProperties Applies properties in a specific properties

file to the configuration

AdminTask.deleteConfigProperties Deletes properties in your configuration as

designated in a properties file

AdminTask.createPropertiesFileTemplates Creates template properties files which are used to

create or delete specific object types

WebSphere® Support Technical Exchange 6 of 25

WebSphere version v7 introduced this new concept of

"PropertiesBasedConfiguration“ using 5 simple wsadmin AdminTask commands.
Like any other wsadmin commands , new AdminTask commands comes with
command line help and interactive assistance.

Interactive Mode & Help commands

Jython
wsadmin> AdminTask.extractConfigProperties ('-interactive')
wsadmin>AdminTask.help (‘validateConfigProperties ')
Jacl
wsadmin>$AdminTask createPropertiesFileTemplates -interactive
wsadmin>$AdminTask help applyConfigProperties

Successful completion of interactive mode, automatically generates regular

wsadmin commands. All changes need to be saved using explicit save command.
This tool creates properties file with variables, such as !{cellName} and actual
values are grouped in the “Environment Variables “ section separately.

6
 IBM Software Group

Properties File
# Configuration properties file for cells/KenGNode05Cell/nodes/TestProfileNode01/servers/server1|server.xml#
# Extracted on Tue Aug 04 10:11:24 EDT 2009
# 1. Header
#
# Section 1.0 ## Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}
#
# SubSection 1.0 # Server Section
ResourceType=Server
ImplementingResourceType=Server
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}
#
#Properties 2. Properties
shortName=null
serverType=APPLICATION_SERVER #readonly
developmentMode=false #boolean
parallelStartEnabled=true #boolean
name=!{serverName}
clusterName=null
uniqueId=null
modelId=null
3. Environment Variables
.....
#Environment Variables
cellName=KenGCell01
nodeName=KenGNode01
hostName=KenG
serverName=server1

WebSphere® Support Technical Exchange 7 of 25

Properties file is divided into multiple sections. Each section contains one
configuration object with header, properties and environment variables.
1. The information in the header is generated automatically, and only ResourceId
should ever be modified. This information is present so that the properties file
based configuration tool knows which implementation to invoke and apply
properties. Header contains:
ResourceType: Indicates the type of resource.
ResourceId: Its a name that uniquely identifies the resource or configuration object.
This should only be modified when the same properties need to be applied to
another object of same type.
ImplementingResourceType : Indicates the class that implements the translation of
attributes to properties.
2.Properties section contains properties of the configuration object identified by the
header, in name/value pairs. Each name and value corresponds to an attribute of
the configuration object.
3.Environment Variables section contains values for variables used within the
properties file. Environment specific properties, such as cellName, serverName,
nodeName, and so on are expressed as variables and the current values of those
variables are placed at the end of the properties file. Having all the variables listed
separately makes it easy to edit.

7
 IBM Software Group

Properties File
Most Common Parameters & Rules.
#
ResourceType=VirtualHost
AttributeInfo=aliases(port,hostname)
#
ResourceType=J2CResourceAdapter
classpath={${WAS_LIBS_DIR}/rsadapter.rar}
name=WebSphere Relational Resource Adapter #readonly
#
ResourceType=JavaVirtualMachine
initialHeapSize=0 #integer
verboseModeGarbageCollection=false #boolean
executableJarFileName=null
#
ResourceType=ActivationSpecTemplateProps
destinationType=javax.jms.Queue #String,required
#
ResourceType=SessionDatabasePersistence
datasourceJNDIName="jdbc/Sessions"

WebSphere® Support Technical Exchange 8 of 25

When multiple attributes are combined to form a single property, AttributeInfo in

the header is used to describe how the multiple attributes are combined. Ex:
AttributeInfo=aliases(port,hostname)

A property value which is list of values is specified within { } symbols.

Ex: classpath={${DERBY_JDBC_DRIVER_PATH}/derby.jar,/my.jar}

If a value of a property is not set in the configuration, it will be represented as null.

Ex: nodeGroupName=null

Type of property (int, long, float, an so on) is represented.

Ex: pingTimeout=300 #integer

If a property is required for a given object, it is represented with

#ObjectName,required.
Ex: targetObject=targetObject #ObjectName,required

A readonly property should not be changed.

Ex: taskName=MapModulesToServers #readonly

A property value containing a space or other special characters is enclosed within

" " Ex:jndiName="jdbc/MyJNDI"

8
 IBM Software Group

Properties File

Special properties
# Create parameters# Replace the line `SKIP=true` with 'SKIP=false' under each section that is needed
# Set necessary parameters under each command or step sections
# Invoke applyConfigProperties command using this properties file.
# Use this section to install a new application on a given server.
# Update ResourceId field with appname ( ResourceId=Deployment=appName )
#
ResourceType=Application
ImplementingResourceType=Application
ResourceId=Deployment=
SKIP=true
CreateDeleteCommandProperties=true
#
#Properties
EarFileLocation=location of earfile #required
Name=appName #required
TargetNode=targetNodeName #required
TargetServer=targetServerName #required

WebSphere® Support Technical Exchange 9 of 25

These special properties can be added to a properties file to indicate whether to

skip or process a given section when applying properties file to configuration:

SKIP
Every section can have a SKIP property set to true or false.
Example: SKIP=true

SKIPSUBSECTIONS
When this property is present in a section and is set to true, all the subsections are
skipped.
Example: SKIPSUBSECTIONS=true

Default value is false.

These are used while using AdminTask.applyConfigProperties

DELETE
When this property is present in a section and is set to true, that section will be
deleted completely from the configuration.
Example: DELETE=true
This property is only used by deleteConfigProperties commands. Default value is
false.

9
 IBM Software Group

Extracting properties from configuration files

Required parameters
-propertiesFileName Name of the properties file to extract

Optional parameters
-configData Configuration Object instance. Ex:Node=node1
Use the configData parameter to specify a Server, Node,
Cluster, or Application instance. If configData is not
specified, the command extracts the cell configuration data.

-options Additional configuration options, such as

GENERATETEMPLATE=true
-filterMechanism Filter information for extracting configuration properties.
(All, NO_SUBTYPES, NO_SUBTYPES_AND_EXTENSIONS,
SELECTED_SUBTYPES and
SELECTED_SUBTYPES_AND_EXTENSIONS)
-selectedSubTypes Configuration properties to include or exclude when the
command extracts the properties. This should be supplied if
NO_SUBTYPES or SELECTED_SUBTYPES is chosen for
-filterMechanism.

WebSphere® Support Technical Exchange 10 of 25

-filterMechanism Options
All: To extract all configuration properties.

NO_SUBTYPES: To extract the properties of the given object without including the
subtypes.

NO_SUBTYPES_AND_EXTENSIONS : To extract the properties of the given object

without including the subtypes and extensions.

SELECTED_SUBTYPES: To extract specific configuration object subtypes

specified with the selectedSubTypes parameter.

SELECTED_SUBTYPES_AND_EXTENSIONS : To extract only properties of the

given object type without including the subtypes. This option also prevents the
command from extracting properties using extensions, if extensions exist for the
object type.

10
 IBM Software Group

Extracting properties from configuration files.

1. Extract a server configuration.
AdminTask.extractConfigProperties('[-propertiesFileName server1.props -
configData Server=server1 -filterMechanism ALL]')
AdminTask.extractConfigProperties('[-propertiesFileName server1.props -
configData Server=server1 ]')
(Note: filterMechanism ALL and ‘No Filters’ gives the same result)

2. Extract node properties without traversing the subtypes of the node.

AdminTask.extractConfigProperties('[-propertiesFileName node.props -
configData Node=KenGNode01 -filterMechanism NO_SUBTYPES]')

3. Extract node properties without traversing the subtypes of the node or

invoking extensions.
AdminTask.extractConfigProperties('[-propertiesFileName node.props -
configData Node=KenGNode01 -filterMechanism
NO_SUBTYPES_AND_EXTENSIONS]')

WebSphere® Support Technical Exchange 11 of 25

configData: To specify the type of resources. Available types are Server, Node,
Cluster and Application

filterMechanism: Used to filter from the configData return value.

Available subtypes and extensions

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.web
sphere.base.doc/info/aes/ae/rxml_7propbasedconfig.html

11
 IBM Software Group

Extracting properties from configuration files.

4. Extract the a server subtype 'WebContainer' configuration for a specific
server.
AdminTask.extractConfigProperties('[-propertiesFileName webcontainer.props
-configData Server=server1 -filterMechanism SELECTED_SUBTYPES -
selectedSubTypes [WebContainer]]')

5. Extract the a server subtype 'WebContainer' configuration for a specific

server.
AdminTask.extractConfigProperties('[-propertiesFileName webcontainer.props
–configData Server=server1 -filterMechanism
SELECTED_SUBTYPES_AND_EXTENSIONS -selectedSubTypes
[WebContainer]]')

6. Extract subtype 'Security' configuration (Note: If -configData is not

provided ,Cell scoped value returned.)
AdminTask.extractConfigProperties('[-propertiesFileName security.props -
selectedSubTypes [Security]]’)

WebSphere® Support Technical Exchange 12 of 25

12
 IBM Software Group

Validating/Applying/Deleting configuration

Required parameters
-propertiesFileName Name of the properties file to extract

Optional parameters
-variablesMapFileName Specifies the name of the variables map file. This file contains values
for variables that the system uses from the properties file.
-variablesMap Specifies the [variables values] pair to use with the properties file.

-reportFileName Specifies the name of a report file that contains the output for the
applyConfigProperties command.
-reportFilterMechanism Specifies the type of report filter mechanism. Specify All to display
all report information. Specify Errors to display error information.
Specify Errors_And_Changes to display error and change
information.

-validate Specifies whether to validate the properties file before applying the
changes. By default, the command validates the properties file.
Specify false to disable validation.

WebSphere® Support Technical Exchange 13 of 25

Before applying changes to the configuration, properties file needs to be validated

for its accuracy. This validation gives the summary of changes that would happen.

There are two ways to validate a properties file.

Before applying it to the configuration using AdminTask.validateConfigProperties

Specifying -validate option with AdminTask.applyConfigProperties

Always validate the entire properties file. Do not validate subsections of files.

13
 IBM Software Group

Validating properties files

1. AdminTask.validateConfigProperties('[-propertiesFileName
myNode.props ]')

2. AdminTask.validateConfigProperties('[-propertiesFileName
myNode.props -reportFileName myReport.txt ]')

3. AdminTask.validateConfigProperties('[-propertiesFileName
myNode.props -reportFileName myReport.txt -
reportFilterMechanism Errors_And_Changes]')

4. AdminTask.validateConfigProperties('[-propertiesFileName
myNode.props -variablesMapFileName myNode.props.vars -
reportFileName myReport.txt –reportFilterMechanism
Errors_And_Changes]‘)

WebSphere® Support Technical Exchange 14 of 25

1. Command returns a value of “true” if the system successfully validates the

properties file.
2. In addition to that it creates report File myReport.txt
ADMG0824I: Start validating properties from file node.props.
ADMG0810I: Not changing value for this property hostName. New value specified is same as current
value KenG.
ADMG0810I: Not changing value for this property name. New value specified is same as current value
KenGNode01.
ADMG0825I: End validating properties from file node.props.

3. Generated report file contains only Errors and Changes.

Note: Upon successful completion of ‘AdminTask.validateConfigProperties’ an
variables properties file get created with extension of .vars .This file includes
all the editable variable:value pair used in this properties file. This file can be
used during AdminTask.applyConfigProperties with - variablesMapFileName
option.
myNode.props.vars
#Environment Variables
cellName=KenGCell01
hostName=KenG
nodeName=KenGNode01

4. During validation any existing variable property file can be validated along with
–variablesMapFileName option.

14
 IBM Software Group

Applying properties files to configuration

Description Command
Apply Config Properties AdminTask.applyConfigProperties('[-propertiesFileName
myNode.props]’)
Using -variablesMap option AdminTask.applyConfigProperties('[-propertiesFileName
to pass variable:value pair myNode.props -variablesMap [ [cellName newCell]
and -validate [nodeName newNode] [hostName newHost] ] -validate true
]‘)
Using - AdminTask.applyConfigProperties('[-propertiesFileName
variablesMapFileName myNode.props -variablesMapFileName node.props.vars ]')
option along with variable
property file which has
variable:value pair defined.
Using -reportFileName AdminTask.applyConfigProperties('[-propertiesFileName
option with - myNode.props -reportFileName myReport.txt -
reportFilterMechanism reportFilterMechanism Errors_And_Changes -validate true ]‘)
Always save the AdminConfig.save()
configuration after apply

WebSphere® Support Technical Exchange 15 of 25

variablesMap: Specify individual name:value pair.

Ex: [ [cellName newCell] [nodeName newNode] [hostName newHost] ]
Validate: validate the properties.
variablesMapFileName: Separate properties file which contains variables
name:value pair.

After any configuration changes save operation used to save the changes to xml
configuration files. Not using save will not post the changes to configuration files.

15
 IBM Software Group

Creating properties file templates.

Configuration templates can be created without extracting
the existing configuration.

Template can be created for Server, Cluster, Application,

or AuthorizationGroup objects.

wsadmin>AdminTask.createPropertiesFileTemplates('[-
propertiesFileName myServer.template -configType Server]')

wsadmin>

WebSphere® Support Technical Exchange 16 of 25

Without extracting properties from existing profile configuration, we can create

standard template using createPropertiesFileTemplates.
This standard template can be used for creating new resources.

16
 IBM Software Group

Modify existing server configuration

Description Command
Extract the AdminTask.extractConfigProperties(‘[-propertiesFileName
configuration myServer.props -configData Server=server1]’)
properties
Modify the file Use your favorite text editor to change properties in myServer.props
and save the changes to the file
Validate the updated AdminTask.validateConfigProperties(‘[-propertiesFileName
properties file myServer.props ]’)

Apply the updated AdminTask.applyConfigProperties(‘[-propertiesFileName

properties file to the myServer.props ]’)
configuration
Save changes AdminConfig.save()

WebSphere® Support Technical Exchange 17 of 25

17
 IBM Software Group

Delete a configuration object

Description Command
Extract the properties AdminTask.extractConfigProperties(‘[-propertiesFileName
file thread.props -configData Server=server1 -filterMechanism
for the configuration SELECTED_SUBTYPES –selectedSubTypes [ThreadPool] ]’)

Modify the file to add #

DELETE=true flag in # SubSection 1.0.1.4 # Thread pools
the initial attribute #
section ResourceType=ThreadPool
ImplementingResourceType=Server
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{server
Name}:ThreadPoolManager=ID#ThreadPoolManager_1:ThreadPo
ol=myThreadPool
DELETE=true
#
Delete the properties AdminTask.deleteConfigProperties(‘[-propertiesFileName
thread.props]’)
Save changes AdminConfig.save()

WebSphere® Support Technical Exchange 18 of 25

18
 IBM Software Group

Delete a configuration using template

Description Command
Create a properties AdminTask.createPropertiesFileTemplates('[-propertiesFileName
file template authorizationGroup.template -configType AuthorizationGroup]')
Change the SKIP #
required property ResourceType=AuthorizationGroup
value from SKIP=true ImplementingResourceType=AuthorizationGroup
to SKIP=false to ResourceId=AuthorizationGroup=
indicate that the SKIP=false
system should apply CreateDeleteCommandProperties=true
the properties in the #
specific section . #Properties
#
authorizationGroupName=authorizationGroupName
#String,required
commandName=deleteAuthorizationGroup
Delete the properties AdminTask.deleteConfigProperties('[-propertiesFileName
authorizationGroup.template]')
Save changes AdminConfig.save()

WebSphere® Support Technical Exchange 19 of 25

Always make a back-up copy of the properties file before you edit it.

19
 IBM Software Group

Create a configuration object

Description Command
Extract the properties file AdminTask.extractConfigProperties('-propertiesFileName
for the configuration ds.props -configData Server=server1 -filterMechanism
SELECTED_SUBTYPES –selectedSubTypes [DataSource]')

Using an existing data # SubSection 1.0.1.0 # DataSource attributes

source section as a #
template, modify the file ResourceType=DataSource
to contain new ImplementingResourceType=JDBCProvider
‘DataSource attributes’ ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{
and ‘Properties’ section serverName}:JDBCProvider=ID#JDBCProvider_1183122153343
by copying existing :DataSource=ID#DataSource_99999
section with new #
resource ID ,name and #Properties
jndiName #
name=My DataSource
...
jndiName="jdbc/MyNewJNDI"

Apply the properties file AdminTask.applyConfigProperties(‘-propertiesFileName ds.props ’)

Save changes AdminConfig.save()

WebSphere® Support Technical Exchange 20 of 25

The unique id used to identify a configuration object is XMI ID.

If XMI id is changed to some thing different that does not exist, it will create a new
object. Otherwise it will update an existing object with new attributes.

We are trying to remove xmi ids from the properties file altogether.
That way one can use some other attribute as key to identify an object uniquely. In
this case alias could be used. This feature is in consideration.

20
 IBM Software Group

Install an application
Description Command
Create a properties AdminTask.createPropertiesFileTemplates(‘-propertiesFileName
file template for app.props –configType Application')
application install
Update the file ResourceType=Application
app.props to contain ImplementingResourceType=Application
the require values for ResourceId=Deployment=
the application you SKIP=false
are installing CreateDeleteCommandProperties=true
#
#Properties
#
EarFileLocation=location of earfile #required
Name=appName #required
TargetNode=targetNodeName #required
TargetServer=targetServerName #required
Apply the properties AdminTask.applyConfigProperties(‘-propertiesFileName
file app.props ’)
Save changes AdminConfig.save()

WebSphere® Support Technical Exchange 21 of 25

21
 IBM Software Group

Summary

Properties file based configuration is a new method for
working with an application server configuration.

Uses wsadmin commands and simple name/value
property files.

Makes configuration automation easier

Copy configuration properties from one environment to
another.

Troubleshoot configuration issues.

Applies one set of configuration properties across
multiple profiles, nodes, cells, servers, or applications.

For trouble shooting, we need to use wsadmin MustGather.

WebSphere® Support Technical Exchange 22 of 25

22
 IBM Software Group

Additional WebSphere Product Resources

SelectedSubTypes subtypes and extensions
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rxml_7propbasedconfig.html

System administration for WebSphere Application Server V7: Part 4: Properties-based configuration
http://www.ibm.com/developerworks/websphere/techjournal/0904_chang/0904_chang.html

Extracting properties files using wsadmin scripting

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_7extractprops.html

Applying properties files using wsadmin scripting

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_7modifyprops.html

Validating properties files using wsadmin scripting

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_7validateprops.html

Creating server, cluster, application, or authorization group objects using properties files and wsadmin scripting
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_7propobjects.html

Deleting server, cluster, application, or authorization group objects using properties files
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_7delpropobjects.html

The WebSphere Contrarian: Changing host names and migrating profiles in WebSphere Application Server
http://www.ibm.com/developerworks/websphere/techjournal/0905_webcon/0905_webcon.html

WebSphere® Support Technical Exchange 23 of 25

23
 IBM Software Group

Join WebSphere Support Technical Exchange on Facebook!

Stay up-to-update on upcoming

webcast sessions

Suggest future topics

Suggest program
improvements

Network with other product
users

And More…

Become a fan now!

http://www.facebook.com/pages/WebSphere-Support-Technical-Exchange/121293581419

WebSphere® Support Technical Exchange 24 of 25

24
 IBM Software Group

Questions and Answers

WebSphere® Support Technical Exchange 25 of 25

25