Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Configure servers with scripting
Configure the Java virtual machine using scripting
Use wsadmin.sh to configure settings for a Java virtual machine (JVM). As part of configuring an application server, you might define settings that enhance the way your operating system uses of the Java virtual machine.
There are three ways to perform this task. Use the steps in this topic to use the setJVMDebugMode command for the AdminTask object or the AdminConfig object to modify your JVM configuration. Alternatively, you can use the configureJavaVirtualMachine Jython script in the AdminServerManagement script library to enable, disable, or configure the debug mode for the JVM. The wsadmin tool automatically loads the script when the tool starts. Use the following syntax to configure JVM settings using the configureJavaVirtualMachine script:
AdminServerManagement.configureJavaVirtualMachine(nodeName, serverName, debugMode, debugArgs, otherAttributeList)For additional information and argument definitions, see the documentation for the AdminServerMananagment script library.The Java virtual machine (JVM) is an interpretive computing engine responsible for running the byte codes in a compiled Java program. The JVM translates the Java byte codes into the native instructions of the host machine. The application server, being a Java process, requires a JVM in order to run, and to support the Java applications running on it. JVM settings are part of an application server configuration.
Procedure
- Start wsadmin.sh.
- There are two ways to complete this step. We can use the setJVMDebugMode command or the AdminConfig object to modify your JVM configuration. Choose one of the following configuration methods:
- Use the AdminTask object:
### Jacl
$AdminTask setJVMDebugMode {-serverName server1 -nodeName node1 -debugMode true}### Jython
AdminTask.setJVMDebugMode (['-serverName', 'server1', '-nodeName', 'node1', '-debugMode', 'true'])
- Use the AdminConfig object:
- Identify the server and assign it to the server1 variable, as the following example demonstrates:
### Jacl
set server1 [$AdminConfig getid /Cell:mycell/Node:mynode/Server:server1/]### Jython
server1 = AdminConfig.getid('/Cell:mycell/Node:mynode/Server:server1/') print server1
Example output:
server1(cells/mycell/nodes/mynode/servers/server1|server.xml#Server_1)
- Identify the JVM that belongs to the server of interest and assign it to the jvm variable:
### Jacl
set jvm [$AdminConfig list JavaVirtualMachine $server1]### Jython
jvm = AdminConfig.list('JavaVirtualMachine', server1) print jvm
Example output:
(cells/mycell/nodes/mynode/servers/server1:server.xml#JavaVirtualMachine_1)
- Modify the JVM to enable debugging:
### Jacl
$AdminConfig modify $jvm {{debugMode true} {debugArgs "-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777"}}### Jython
AdminConfig.modify(jvm, [['debugMode', 'true'], ['debugArgs', "-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777"]])
- Save the configuration changes.
Save the configuration changes:
AdminConfig.save()
- Synchronize the node.
Use the syncActiveNode or syncNode scripts in the AdminNodeManagement script library to propagate the configuration changes to node or nodes.
- Use the syncActiveNodes script to propagate the changes to each node in the cell:
AdminNodeManagement.syncActiveNodes()
- Use the syncNode script to propagate the changes to a specific node:
AdminNodeManagement.syncNode("myNode")
Configure the JVM
Automate server administration using wsadmin.sh
Related
Node administration scripts
Server settings configuration scripts
Commands for the AdminConfig object using wsadmin.sh