This procedure can be used for any command line arguments
you want to add to the application server. The following example is used
for setting SAS traces.
To enable SAS tracing, place the following text in a file called
CmdLineUpdate.xml. Then change the node name and
application-server name to appropriate names.
<?xml version="1.0"?>
<!DOCTYPE websphere-sa-config SYSTEM
"$server_root$$dsep$bin$dsep$xmlconfig.dtd">
<websphere-sa-config>
<node name="pigpen"
action="locate">
<application-server name="Default
Server" action="update">
<command-line-arguments>
<arg>-Dcom.ibm.CORBA.securityDebug=console</arg>
<arg>-Dcom.ibm.CORBA.securityTraceLevel=advanced</arg>
</command-line-arguments>
</application-server>
</node>
</websphere-sa-config>
Use XMLConfig to import this file:
XMLConfig -import CmdLineUpdate.xml -adminNodeName pigpen
In order for the command line arguments to take effect, the application
server must be stopped and restarted. Place the following text into a new
file called stop.xml (and another new file called
start.xml changing the action=stop to
action=start).
<?xml version="1.0"?>
<!DOCTYPE websphere-sa-config SYSTEM
"$server_root$$dsep$bin$dsep$xmlconfig.dtd">
<websphere-sa-config>
<node name="pigpen"
action="locate">
<application-server name="Default
Server" action="stop">
</application-server>
</node>
</websphere-sa-config>
Use XMLConfig to import this file and stop the application
server:
XMLConfig -import stop.xml -adminNodeName pigpen
Use XMLConfig to import this file to start the application
server:
XMLConfig -import start.xml -adminNodeName pigpen
|