WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

328 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Two run modes are always available for each administrative command, namely the batch and

interactive mode. When you use an administrative command in interactive mode, you go

through a series of steps to collect your input interactively. This process provides users a

text-based wizard and a similar user experience to the wizard in the administrative console.

You can also use the help command to obtain help for any of the administrative commands

and the AdminTask object.

8.5 Properties file based configuration

Using complex scripts requires knowledge of the Jacl or Jython scripting languages and the

public MBean interfaces. The use of a properties file-based configuration provides a way to

simplify administrative tasks using wsadmin. WebSphere Application Server configuration can

be extracted into a single file and any configuration attribute can be located in that file in the

form of name/value pair properties.

The following commands in the PropertiesBasedConfiguration command group implement

this type of configuration:

 extractConfigProperties

 validateConfigProperties

 applyConfigProperties

 deleteConfigProperties

 createPropertiesFileTemplates

Properties file-based configuration extracts configuration data to one file that is easy to read

using any editor tool. The configuration attributes are provided as key/value pairs, as shown in

Figure 8-2.

Figure 8-2 Properties for a JDBC provider

After the properties are extracted, you can make any necessary changes to the attributes and

validate the changes before applying them to the server. You can also create or delete

configuration objects.

Example 8-11 on page 329 shows samples of these commands.

#

# SubSection 1.0 # JDBCProvider attributes

#

ResourceType=JDBCProvider

ImplementingResourceType=JDBCProvider

ResourceId=Cell=!{cellName}:JDBCProvider=ID#builtin_jdbcprovider

#

#

#Properties

#

classpath={${DERBY_JDBC_DRIVER_PATH}/derby.jar}

name=Derby JDBC Provider (XA)

implementationClassName=org.apache.derby.jdbc.EmbeddedXADataSource

nativepath={}

description=Built-in Derby JDBC Provider (XA)

providerType=Derby JDBC Provider (XA) #readonly

xa=true #boolean

1. Resource type and Identifier

2. Configuration Information