In this task, you make a configuration change to an existing application server, then stop and restart the server to pick up the change. In WebSphere Application Server V5.x, you can only change the attributes in a running server that the server supports explicitly, or by objects it contains. You can determine these attributes online by using the Help attributes scripting command, or by referring to the Mbean documentation. When you use this type of update, you change only the current running state of the server. Your changes are not permanent. The updates that you make to the server configuration do not take effect until you stop and restart the server.
The enum attribute is changed. WebSphere Application Server V4.0 requires that you find the corresponding integer to enum value by making changes with the GUI, and examining the output. In V5.x, the string names of the enum literals are available using online help, using the AdminConfig attributes command, and displaying or updating an attribute.
The following examples demonstrate how to modify and restart an application server in WebSphere Application Server V4.0 and V5.x:
ApplicationServer stop /Node:mynode/ApplicationServer:myserver/
ApplicationServer modify /Node:mynode/ApplicationServer:myserver/ -attribute {{ModuleVisibility 1}}
ApplicationServer start /Node:mynode/ApplicationServer:myserver/
Using Jacl:
$AdminControl stopServer myserver mynode
Using Jacl:
set s1 [$AdminConfig getid /Node:mynode/Server:myserver/] set errStream [$AdminConfig showAttribute $s1 errorStreamRedirect} $AdminConfig modify $s1 {{rolloverPeriod 12}} $AdminConfig save
Using Jacl:
$AdminControl startServer myserver mynode