You can use the Jython or Jacl scripting languages to manage servers with the wsadmin tool. The commands and parameters in the ServerManagement group can be used to create and manage application server, Web server, proxy server, generic server and Java™ virtual machine (JVM) configurations.
Use the createApplicationServer command to create a new application server.
Target object
Specifies the name of the node (String, required)
Required parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask createApplicationServer ndnode1 {-name test1 -templateName default}
AdminTask.createApplicationServer(ndnode1, '[-name test1 -templateName default]")
AdminTask.createApplicationServer(ndnode1, ['-name', 'test1', '-templateName', 'default'])
Interactive mode example usage:
$AdminTask createApplicationServer {-interactive}
AdminTask.createApplicationServer ('-interactive')
The createApplicationServerTemplate command creates a new application server template.
Target object
NoneRequired parameters
Optional parameters
Websphere:_Websphere_Config_Data_Display_Name=display_name,_Websphere_Config_Data_Id=configuration_idThe configuration Id value is the application server template, which is templates\servertypes\APPLICATION_SERVER|servertype-metadata.xml
Examples
Batch mode example usage:
$AdminTask createApplicationServerTemplate {-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template" -templateLocation Websphere:_Websphere_Config_Data_Display_Name=APPLICATION_SERVER,_Websphere_Config_Data_Id= templates/servertypes/APPLICATION_SERVER|servertype-metadata.xml}
AdminTask.createApplicationServerTemplate('[-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template" -templateLocation Websphere:_Websphere_Config_Data_Display_Name= APPLICATION_SERVER,_Websphere_Config_Data_Id=templates/servertypes/APPLICATION_SERVER|servertype-metadata.xml]')
AdminTask.createApplicationServerTemplate(['-templateName', 'newTemplate', '-serverName', 'server1', '-nodeName', 'ndnode1', '-description', "This is my new template"])
Interactive mode example usage:
$AdminTask createApplicationServerTemplate {-interactive}
AdminTask.createApplicationServerTemplate ('[-interactive]')
AdminTask.createApplicationServerTemplate (['-interactive'])
Use the createGenericServer command to create a new generic server in the configuration. A generic server is a server that the WebSphere® Application Server manages, but did not supply. The createGenericServer command provides an additional step, ConfigProcDef, that you can use to configure the parameters that are specific to generic servers.
Target object
Specifies the name of the node (String, required)Required parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask createGenericServer jim667BaseNode {-name jgeneric -ConfigProcDef {{"/usr/bin/myStartCommand" "arg1 arg2" "" "" "/tmp/workingDirectory" "/tmp/stopCommand" "argy argz"}}}
AdminTask.createGenericServer('jim667BaseNode', '[-name jgeneric -ConfigProcDef [[/usr/bin/myStartCommand "arg1 arg2" "" "" /tmp/workingDirectory /tmp/StopCommand "argy argz"]]]')
AdminTask.createGenericServer('jim667BaseNode', ['-name', 'jgeneric', '-ConfigProcDef', [['/usr/bin/myStartCommand', "arg1 arg2" "" "", '/tmp/workingDirectory', '/tmp/StopCommand', "argy argz"]]])
Interactive mode example usage:
$AdminTask createGenericServer {-interactive}
AdminTask.createGenericServer ('[-interactive]')
AdminTask.createGenericServer (['-interactive'])
The createGenericServerTemplate command creates a new generic server template.
Target object
NoneRequired parameters
Optional parameters
Websphere:_Websphere_Config_Data_Display_Name=display_name,_Websphere_Config_Data_Id=configuration_idThe configuration Id value is the generic server template, which is templates\servertypes\GENERIC_SERVER|servertype-metadata.xml
Examples
Batch mode example usage:
$AdminTask createGenericServerTemplate {-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template" -templateLocation Websphere:_Websphere_Config_Data_Display_Name=GENERIC_SERVER,_Websphere_Config_Data_Id= templates/servertypes/GENERIC_SERVER|servertype-metadata.xml}
AdminTask.createGenericServerTemplate('[-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template" -templateLocation Websphere:_Websphere_Config_Data_Display_Name= GENERIC_SERVER,_Websphere_Config_Data_Id=templates/servertypes/GENERIC_SERVER|servertype-metadata.xml]')
AdminTask.createGenericServerTemplate(['-templateName', 'newTemplate', '-serverName', 'server1', '-nodeName', 'ndnode1', '-description', "This is my new template"])
Interactive mode example usage:
$AdminTask createGenericServerTemplate {-interactive}
AdminTask.createGenericServerTemplate ('[-interactive]')
AdminTask.createGenericServerTemplate (['-interactive'])
Use the createGenericServerTemplate command to create a server template based on a server configuration.
Target object
None.Required parameters
Optional parameters
Websphere:_Websphere_Config_Data_Display_Name=display_name,_Websphere_Config_Data_Id=configuration_idThe configuration Id can be one of the following values:
templates\servertypes\WEB_SERVER|servertype-metadata.xml
templates\servertypes\APPLICATION_SERVER|servertype-metadata.xml
templates\servertypes\GENERIC_SERVER|servertype-metadata.xml
templates\servertypes\PROXY_SERVER|servertype-metadata.xml
Examples
Interactive mode example usage:
$AdminTask createGenericServerTemplate {-interactive}
AdminTask.createGenericServerTemplate('-interactive')
Use the createProxyServer command to create a new proxy server in the configuration. The proxy server is a specific type of application server that routes HTTP requests to content servers that perform the work. The proxy server is the initial point of entry, after the firewall, for requests into the enterprise.
Target object
Specifies the name of the node (String, required)Required parameters
Optional parameters
Optional steps
Examples
Batch mode example usage:
$AdminTask createProxyServer myNode {-name myProxyServer -templateName myTemplate -ConfigCoreGroup [-coregroupName [myCoreGroup]] -selectProtocols [-list [HTTP, SIP]]}
AdminTask.createProxyServer('myNode', '[-name myProxyServer -templateName myTemplate -ConfigCoreGroup [-coregroupName [myCoreGroup]] -selectProtocols [-list [HTTP, SIP]]]')
AdminTask.createProxyServer(myNode, ['-name', 'myProxyServer', '-templateName', 'myTemplate', '-ConfigCoreGroup', '[-coregroupName [myCoreGroup]]', '-selectProtocols', '[-list [HTTP, SIP]]'])
Interactive mode example usage:
$AdminTask createProxyServer {-interactive}
AdminTask.createProxyServer('-interactive')
Use the createProxyServerTemplate command to create a new proxy server template based on an existing proxy server configuration.
Target object
NoneRequired parameters
Optional parameters
Websphere:_Websphere_Config_Data_Display_Name=display_name,_Websphere_Config_Data_Id=configuration_idThe configuration Id value is the proxy server template, which is templates\servertypes\PROXY_SERVER|servertype-metadata.xml
Examples
Batch mode example usage:
$AdminTask createProxyServerTemplate {-templateName proxyServerTemplate -serverName proxyServer1 -nodeName myNode}
AdminTask.createProxyServerTemplate('[-templateName proxyServerTemplate -serverName proxyServer1 -nodeName myNode]')
AdminTask.createProxyServerTemplate(['-templateName', 'proxyServerTemplate', '-serverName', 'proxyServer1', '-nodeName', 'myNode'])
Interactive mode example usage:
$AdminTask createProxyServerTemplate {-interactive}
AdminTask.createProxyServerTemplate('[-interactive]')
Use the createServerType command to define a server type.
Target object
None.Required parameters
Optional parameters
Sample output
The command returns the object name of the server type that was created.Examples
Batch mode example usage:
$AdminTask createServerType {-version version -serverType serverType -createTemplateCommand name -createCommand name}
AdminTask.createServerType('[-version version -serverType serverType -createTemplateCommand name -createCommand name]')
AdminTask.createServerType(['-version', 'version', '-serverType', 'serverType','-createTemplateCommand', 'name', '-createCommand', 'name'])
Interactive mode example usage:
$AdminTask createServerType {-interactive}
AdminTask.createServerType('-interactive')
Use the createWebServer command to create a Web server definition. This command creates a Web server definition using a template and configures the Web server definition properties. Web server definitions generate and propagate the plugin-config.xml file for each Web server. For IBM® HTTP Server only, you can use Web server definitions to administer and configure IBM HTTP Server Web servers with the administrative console. These functions include: Start, Stop, View logs, View and Edit configuration files.
Target object
Specifies the name of the node (String, required).Required parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask createWebServer myNode {-name wsname -serverConfig {{80 /opt/path/to/ihs /opt/path/to/plugin /opt/path/to/plugin.xml "windows service" /opt/path/to/error.log /opt/path/to/access.log HTTP}} -remoteServerConfig {{8008 user password HTTP}}
print AdminTask.createWebServer(myNode, ['-name', wsname, '-serverConfig',[['80','/opt/path/to/ihs', '/opt/path/to/plugin','/opt/path/to/plugin.xml', 'windows service','/opt/path/to/error.log', '/opt/path/to/access.log','HTTP']],'-remoteServerConfig', [['8008','user','password','HTTP']]])
AdminTask.createWebServer('myNode','-name wsname -serverConfig [80 /opt/path/to/ihs /opt/path/to/plugin /opt/path/to/plugin.xml "windows service" /opt/path/to/error.log /opt/path/to/access.log HTTP] -remoteServerConfig [8008 user password HTTP]')
Interactive mode example usage:
$AdminTask createWebServer -interactive
AdminTask.createWebServer ('[-interactive]')
AdminTask.createWebServer (['-interactive'])
The createWebServerTemplate command creates a new Web server template.
Target object
NoneRequired parameters
Optional parameters
Websphere:_Websphere_Config_Data_Display_Name=display_name,_Websphere_Config_Data_Id=configuration_idThe configuration Id value is the Webserver template, which is templates\servertypes\WEB_SERVER|servertype-metadata.xml
Examples
Batch mode example usage:
$AdminTask createWebServerTemplate {-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template" -templateLocation Websphere:_Websphere_Config_Data_Display_Name=WEB_SERVER,_Websphere_Config_Data_Id= templates/servertypes/WEB_SERVER|servertype-metadata.xml}
AdminTask.createWebServerTemplate('[-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template" -templateLocation Websphere:_Websphere_Config_Data_Display_Name= WEB_SERVER,_Websphere_Config_Data_Id=templates/servertypes/WEB_SERVER|servertype-metadata.xml]')
AdminTask.createWebServerTemplate(['-templateName', 'newTemplate', '-serverName', 'server1', '-nodeName', 'ndnode1', '-description', "This is my new template"])
Interactive mode example usage:
$AdminTask createWebServerTemplate {-interactive}
AdminTask.createWebServerTemplate ('[-interactive]')
AdminTask.createWebServerTemplate (['-interactive'])
Use the deleteServer command to delete a server.
Target object
NoneRequired parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask deleteServer {-serverName server_name -nodeName node_name}
AdminTask.deleteServer('[-serverName server_name -nodeName node_name]')
AdminTask.deleteServer(['-serverName', 'server_name', '-nodeName', 'node_name'])
Interactive mode example usage:
$AdminTask deleteServer {-interactive}
AdminTask.deleteServer ('[-interactive]')
AdminTask.deleteServer (['-interactive'])
Use the deleteServerTemplate command to delete a server template. You cannot delete templates that are defined by the system. You can only delete server templates that you created. This command deletes the directory that hosts the server template.
Target object
The name of the template to delete. (ObjectName, required)
Required parameters
None.
Optional parameters
None.
Examples
Batch mode example usage:
$AdminTask deleteServerTemplate template_name(templates/serverTypes/APPLICATION_SERVER/servers /newTemplate|server.xml#Server_1105015708079)
AdminTask.deleteServerTemplate('template_name(templates/serverTypes/APPLICATION_SERVER/servers /newTemplate|server.xml#Server_1105015708079)')
AdminTask.deleteServerTemplate('template_name(templates/serverTypes/APPLICATION_SERVER/servers /newTemplate|server.xml#Server_1105015708079)')
Interactive mode example usage:
$AdminTask deleteServerTemplate {-interactive}
AdminTask.deleteServerTemplate ('[-interactive]')
AdminTask.deleteServerTemplate (['-interactive'])
Use the getJavaHome command to get the Java home value.
Target object
None.Required parameters
Examples
Batch mode example usage:
$AdminTask getJavaHome {-nodeName mynode -serverName myserver}
AdminTask.getJavaHome ('[-nodeName mynode -serverName myserver]')
AdminTask.getJavaHome (['-nodeName' 'mynode' '-serverName' 'myserver'])
Interactive mode example usage:
$AdminTask getJavaHome {-interactive}
AdminTask.getJavaHome ('[-interactive]')
AdminTask.getJavaHome (['-interactive'])
Target object
NoneOptional parameters
Examples
Batch mode example usage:
$AdminTask getServerType {-serverName test2 -nodeName ndnode1}
AdminTask.getServerType('[-serverName test2 -nodeName ndnode1]')
AdminTask.getServerType(['-serverName', 'test2', '-nodeName', 'ndnode1'])
Interactive mode example usage:
$AdminTask getServerType {-interactive}
AdminTask.getServerType ('[-interactive]')
AdminTask.getServerType (['-interactive'])
Target object
NoneOptional parameters
Examples
Batch mode example usage:
$AdminTask listServers {-serverType APPLICATION_SERVER -nodeName ndnode1}
AdminTask.listServers('[-serverType APPLICATION_SERVER -nodeName ndnode1]')
AdminTask.listServers(['-serverType', 'APPLICATION_SERVER', '-nodeName', 'ndnode1'])
Interactive mode example usage:
$AdminTask listServers {-interactive}
AdminTask.listServers ('[-interactive]')
AdminTask.listServers (['-interactive'])
Use the listServerTemplates command to list server templates.
Target object
NoneOptional parameters
Examples
Batch mode example usage:
$AdminTask listServerTemplates {-version 6.0.0.0 -serverType APPLICATION_SERVER}
AdminTask.listServerTemplates('[-version 6.0.0.0 -serverType APPLICATION_SERVER]')
AdminTask.listServerTemplates(['-version', '6.0.0.0', '-serverType', 'APPLICATION_SERVER'])
Interactive mode example usage:
$AdminTask listServerTemplates {-interactive}
AdminTask.listServerTemplates ('[-interactive]')
AdminTask.listServerTemplates (['-interactive'])
Use the listServerTypes command to display all the current server types. For example, APPLICATION_SERVER, WEB_SERVER, GENERIC_SERVER
Target object
The node name for which you want to list the valid types. For example, the types that are only valid on z/OS® will appear on a z/OS node. (String, optional)
Parameters and return values
Examples
Batch mode example usage:
$AdminTask listServerTypes ndnode1
AdminTask.listServerTypes(ndnode1)
AdminTask.listServerTypes(ndnode1)
Interactive mode example usage:
$AdminTask listServerTypes {-interactive}
AdminTask.listServerTypes ('[-interactive]')
AdminTask.listServerTypes (['-interactive'])
Use the setJVMDebugMode command to set the Java virtual machine (JVM) debug mode for the application server.
Target object
NoneRequired parameters
Examples
Interactive mode example usage:
$AdminTask setJVMDebugMode {-interactive}
AdminTask.setJVMDebugMode ('[-interactive]')
AdminTask.setJVMDebugMode (['-interactive'])
Use the setGenericJVMArguments command passes command line arguments to the Java virtual machine (JVM) code that starts the application server process.
Target object
NoneRequired parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask setGenericJVMArguments {-serverName server1 -nodeName node1}
AdminTask.setGenericJVMArguments('[-serverName server1 -nodeName node1]')
AdminTask.setGenericJVMArguments(['-serverName', 'server1', '-nodeName', 'node1'])
Interactive mode example usage:
$AdminTask setGenericJVMArguments {-interactive}
AdminTask.setGenericJVMArguments ('[-interactive]')
AdminTask.setGenericJVMArguments (['-interactive'])
Use the setJVMInitialHeapSize command to set the Java Virtual Machine (JVM) initial heap size for the application server.
Target object
None
Parameters and return values
Examples
Interactive mode example usage:
$AdminTask setJVMInitialHeapSize {-interactive}
AdminTask.setJVMInitialHeapSize ('[-interactive]')
AdminTask.setJVMInitialHeapSize (['-interactive'])
Use the setJVMMaxHeapSize command to set the Java virtual machine (JVM) maximum heap size for the application server.
Target object
None
Parameters and return values
Examples
Batch mode example usage:
$AdminTask setJVMMaxHeapSize {-serverName server1 -nodeName node1 -maximumHeapSize 10}
set nodeparm "node1" $AdminTask setJVMMaxHeapSize [subst {-serverName server1 -nodeName $nodeparm -maximumHeapSize 100}]
AdminTask.setJVMMaxHeapSize('[-serverName server1 -nodeName node1 -maximumHeapSize 10]')
AdminTask.setJVMMaxHeapSize(['-serverName', 'server1', '-nodeName', 'node1', '-maximumHeapSize', '10'])
Interactive mode example usage:
$AdminTask setJVMMaxHeapSize {-interactive}
AdminTask.setJVMMaxHeapSize ('[-interactive]')
AdminTask.setJVMMaxHeapSize (['-interactive'])
Use the setJVMProperties command to set the Java virtual machine (JVM) configuration for the application server.
Target object
NoneRequired parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask setJVMProperties {-serverName server1 -nodeName node1}
AdminTask.setJVMProperties('[-serverName server1 -nodeName node1]')
AdminTask.setJVMProperties(['-serverName', 'server1', '-nodeName', 'node1'])
Interactive mode example usage:
$AdminTask setJVMProperties {-interactive}
AdminTask.setJVMProperties ('[-interactive]')
AdminTask.setJVMProperties (['-interactive'])
Use the setJVMSystemProperties command to set the Java virtual machine (JVM) system property for the process of the application server.
Target object
NoneRequired parameters
Examples
Batch mode example usage:
$AdminTask setJVMSystemProperties {-serverName server1 -nodeName node1 -propertyName test.property -propertyValue testValue}
AdminTask.setJVMSystemProperties('[-serverName server1 -nodeName node1 -propertyName test.property -propertyValue testValue]')
AdminTask.setJVMSystemProperties(['-serverName', 'server1', '-nodeName', 'node1', '-propertyName', 'test.property', '-propertyValue', 'testValue'])
Interactive mode example usage:
$AdminTask setJVMSystemProperties {-interactive}
AdminTask.setJVMSystemProperties ('[-interactive]')
AdminTask.setJVMSystemProperties (['-interactive'])
Use the setProcessDefinition command to set the process definition of an application server.
Target object
NoneRequired parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask setProcessDefinition {-serverName server1 -nodeName node1}
AdminTask.setProcessDefinition('[-serverName server1 -nodeName node1]')
AdminTask.setProcessDefinition(['-serverName', 'server1', '-nodeName', 'node1'])
Interactive mode example usage:
$AdminTask setProcessDefinition {-interactive}
AdminTask.setProcessDefinition ('[-interactive]')
AdminTask.setProcessDefinition (['-interactive'])
Use the setTraceSpecification command to set the trace specification for the server. If the server is running new trace specification the change takes effect immediately. This command also saves the trace specification in configuration.
Target object
NoneRequired parameters
Examples
Batch mode example usage:
$AdminTask setTraceSpecification {-serverName server1 -nodeName node1 -traceSpecification com.ibm.*=all=enabled}
AdminTask.setTraceSpecification('[-serverName server1 -nodeName node1 -traceSpecification com.ibm.*=all=enabled]')
AdminTask.setTraceSpecification(['-serverName', 'server1', '-nodeName', 'node1', '-traceSpecification', 'com.ibm.*=all=enabled'])
Interactive mode example usage:
$AdminTask setTraceSpecification {-interactive}
AdminTask.setTraceSpecification ('[-interactive]')
AdminTask.setTraceSpecification (['-interactive'])
Use the showJVMProperties command to list the Java virtual machine (JVM) configuration for the server of the application process.
Target object
NoneRequired parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask showJVMProperties {-serverName server1 -nodeName node1 -propertyName test.property}
AdminTask.showJVMProperties('[-serverName server1 -nodeName node1 -propertyName test.property]')
AdminTask.showJVMProperties(['-serverName', 'server1', '-nodeName', 'node1', '-propertyName', 'test.property'])
Interactive mode example usage:
$AdminTask showJVMProperties {-interactive}
AdminTask.showJVMProperties ('[-interactive]')
AdminTask.showJVMProperties (['-interactive'])
Use the showJVMSystemProperties command to show the Java virtual machine (JVM) system properties for the process of the application server.
Target object
NoneRequired parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask showJVMSystemProperties {-serverName server1 -nodeName node1 -propertyName test.property}
AdminTask.showJVMSystemProperties('[-serverName server1 -nodeName node1 -propertyName test.property]')
AdminTask.showJVMSystemProperties(['-serverName', 'server1', '-nodeName', 'node1', '-propertyName', 'test.property'])
Interactive mode example usage:
$AdminTask showJVMSystemProperties {-interactive}
AdminTask.showJVMSystemProperties ('[-interactive]')
AdminTask.showJVMSystemProperties (['-interactive'])
Use the showProcessDefinition command to show the process definition of the server.
Target object
NoneRequired parameters
Optional parameters
Examples
Batch mode example usage:
$AdminTask showProcessDefinition {-serverName server1 -nodeName node1 -propertyName test.property}
AdminTask.showProcessDefinition('[-serverName server1 -nodeName node1 -propertyName test.property]')
AdminTask.showProcessDefinition(['-serverName', 'server1', '-nodeName', 'node1', '-propertyName', 'test.property'])
Interactive mode example usage:
$AdminTask showProcessDefinition {-interactive}
AdminTask.showProcessDefinition ('[-interactive]')
AdminTask.showProcessDefinition (['-interactive'])
The showServerInfo command returns the information for a server that you specify.
Target object
The configuration ID of the server. (required)Parameters and return values
Examples
Batch mode example usage:
$AdminTask showServerInfo server1(cells/WAS00Network /nodes/ndnode1/servers/server1|server.xml)
AdminTask.showServerInfo('server1(cells/WAS00Network /nodes/ndnode1/servers/server1|server.xml)')
AdminTask.showServerInfo('server1(cells/WAS00Network /nodes/ndnode1/servers/server1|server.xml)')
Interactive mode example usage:
$AdminTask showServerInfo {-interactive}
AdminTask.showServerInfo ('[-interactive]')
AdminTask.showServerInfo (['-interactive'])
The showServerTypeInfo command displays information about a specific server type.
Target object
Specifies a server type. For example: APPLICATION_SERVER (String, required)Optional parameters
Examples
Batch mode example usage:
$AdminTask showServerTypeInfo APPLICATION_SERVER
AdminTask.showServerTypeInfo(APPLICATION_SERVER)
AdminTask.showServerTypeInfo(APPLICATION_SERVER)
Interactive mode example usage:
$AdminTask showServerTypeInfo {-interactive}
AdminTask.showServerTypeInfo ('[-interactive]')
AdminTask.showServerTypeInfo (['-interactive'])
Use the showTemplateInfo command to display the metadata information for a specific server template.
Target object
Specifies the configuration Id of the server type. (String, required)
Parameters and return values
Examples
Batch mode example usage:
$AdminTask showTemplateInfo default(templates/servertypes/APPLICATION_SERVER/servers/default|server.xml) {isSystemTemplate true} {name default} {com.ibm.websphere.baseProductVersion 6.0.0} {description {The WebSphere Default Server Template}} {com.ibm.websphere.baseProductMinorVersion 0.0} {com.ibm.websphere.baseProductMajorVersion 6} {com.ibm.websphere.nodeOperatingSystem {}} {isDefaultTemplate true}
AdminTask.showTemplateInfo(default(templates/serverTypes/APPLICATION_SERVER/servers/default|server.xml)) '[[isSystemTemplate true] [com.ibm.websphere.baseProductVersion 6.0.0] [name default] [com.ibm.websphere.baseProductMinorVersion 0.0] [description The WebSphere Default Server Template] [isDefaultTemplate true] [com.ibm.websphere.nodeOperatingSystem] [com.ibm.websphere.baseProductMajorVersion 6]]'
AdminTask.showTemplateInfo(default(templates/serverTypes/APPLICATION_SERVER/servers/default|server.xml)) [['isSystemTemplate', 'true'], ['com.ibm.websphere.baseProductVersion', '6.0.0'], ['name', 'default'] ['com.ibm.websphere.baseProductMinorVersion', '0.0'], ['description', 'The WebSphere Default Server Template'] ['isDefaultTemplate', 'true'], ['com.ibm.websphere.nodeOperatingSystem'], ['com.ibm.websphere.baseProductMajorVersion', '6']]
Interactive mode example usage:
$AdminTask showTemplateInfo {-interactive}
AdminTask.showTemplateInfo ('[-interactive]')
AdminTask.showTemplateInfo (['-interactive'])