Managing specific configuration objects using properties files
Use the wsadmin tool to change configuration properties and manage configuration objects of your environment using properties files.
Before you begin
Determine the changes that you want to make to your server configuration or its configuration objects.
Read Properties file syntax so that changes you make to properties files use the supported syntax.
About this task
Using a properties file, you can create, modify, or delete a configuration object.
Extracted properties files identify all required properties and default values for an object of a
given type. Required properties have the comment #required
following a property
setting. Properties that have default values have the comment
#object_type,default(default_value)
following
a property setting. When a property that has a default value is deleted, the value of that property
is set automatically to the default value. If a property does not have default value, it is not
shown. Because extracted properties files contain information about all required and default
properties, you can verify that property values are set properly before applying the properties file
to create, modify, or delete an object.
For example, an extracted properties file of type JDBCProvider identifies all required and default properties:
#
# SubSection 1.0 # JDBCProvider attributes
#
ResourceType=JDBCProvider
ImplementingResourceType=JDBCProvider
ResourceId=Cell=!{cellName}:ServerCluster=!{clusterName}:JDBCProvider=Derby JDBC Provider (XA)
#
#
# Properties
#
classpath={${DERBY_JDBC_DRIVER_PATH}/derby.jar}
name=Derby JDBC Provider (XA) #required
implementationClassName=org.apache.derby.jdbc.EmbeddedXADataSource #required
isolatedClassLoader=false #boolean,default(false)
nativepath={}
description=Built-in Derby JDBC Provider (XA)
providerType=Derby JDBC Provider (XA) #readonly
xa=true #boolean,default(false)
Procedure
What to do next
Save the changes to your configuration.