WebLogic Server Command Reference
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Sets the specified property (attribute) values for a configuration MBean. This command cannot be used for Runtime MBeans.
If the command is successful, it returns OK
.
When you use this command for an Administration MBean, the new values are saved to the config.xml
file.
We recommend that you do not use this command to set values on a Local Configuration MBean. If you use this command for a Local Configuration MBean, the new values are not saved to the config.xml
file. Depending on the attribute that you set, the subsystem that uses the MBean might not be able to modify its operation per the new value. In addition, some subsystems require that their Local Configuration MBeans be replicated throughout a domain. If you modify the value for a Local Configuration MBean on one server, the new value will not be replicated throughout the domain and the subsystem might not operate correctly.
java [ SSL Arguments ] weblogic.Admin
[-urlURL
]
[ User Credentials Arguments ]
SET {-typembeanType
|-mbeanobjectName
}
-propertyproperty1
property1_value
[-propertyproperty2
property2_value
] . . .
Specifies the listen address and listen port of the Administration Server. Only the Administration Server can access Administration MBeans. If you specify a secure listen port, you must also specify a secure protocol. If you do not specify a value, the command assumes For more information, refer to the Although the |
|
Sets the properties for all MBeans of a specific type. For more information, refer to Specifying MBean Types. |
|
Fully qualified object name of an MBean in the For more information, refer to the Javadoc for |
|
|
The following example sets to 64
the StdoutSeverityLevel property of the local configuration instance of the ServerMBean
for a server named MedRecManagedServer
:
java weblogic.Admin -url http://ManagedHost:8001
-username weblogic -password weblogic
SET -mbean
MedRec:Location=MedRecManagedServer,Name=MedRecManagedServer,
Type=ServerConfig
-property StdoutSeverityLevel 64
For more information about the environment in which this example runs, refer to Example Environment.
If the command succeeds, the server instance writes a log message similar to the following:
<Sep 16, 2002 12:11:27 PM EDT> <Info> <Logging> <000000> <Log messages of every severity will be displayed in the shell console.>
The command prints Ok
to standard out.
The following example sets to 64
the StdoutSeverityLevel property for all administration instances of ServerMBean
in the current domain:
java weblogic.Admin -url http://AdminHost:7001
-username weblogic -password weblogic
SET -type Server -property StdoutSeverityLevel 64
By default, each weblogic.Admin
command that you invoke starts a JVM, acts on a server instance, and then shuts down the JVM. To improve performance for issuing several weblogic.Admin
commands in an uninterrupted sequence, you can use the BATCHUPDATE
command to run multiple commands in batch mode. The BATCHUPDATE
command starts a JVM, runs a list of commands, and then shuts down the JVM.
For example, if a domain contains multiple server instances, you can create a file that returns the listen ports of all Managed Servers in a domain. Then you specify this file as an argument in weblogic.Admin
BATCHUPDATE
command.
![]() ![]() |
![]() |
![]() |