Note: The WebLogic Server 7.0 examples and PetStore are configured to use the
Booting WebLogic Server in Compatibility Security
In previous releases of WebLogic Server, the File realm was configured by default.
Therefore, WebLogic Server could use the File Realm to boot even if there was no
security realm defined in the
Server in Compatibility security, you need to have either a File realm or an alternative
security realm defined in your
If you are unable to boot WebLogic Server in Compatibility security, copy
SerializedSystemini.dat
following:
Boot your configuration under WebLogic Server 6.x, letting the server save the
config.xml
7.0.
Edit your 6.x
<Security Name=mydomain Realm=mysecurity/>
<Realm Name=mysecurity FileRealm=myrealm/>
<FileRealm Name=myrealm/>
ACLs on MBeans
ACLs on MBeans are not supported in WebLogic Server 7.0. For information on
protecting MBeans in WebLogic Server 7.0, see
Operations
default security configuration. It is not possible to run the WebLogic Server
7.0 examples and PetStore in Compatibility security.
config.xml
file, and then port the saved
config.xml
in the Administration Guide.
file. However, in order to run WebLogic
file. Otherwise, your server may not boot.
config.xml
to your new domain folder and then do one of the
config.xml
file to include the following definitions:
Protecting System Administration
BEA WebLogic Server 7.0 Upgrade Guide
Upgrading Security
file to WebLogic Server
1-7
Need help?
Do you have a question about the WebLogic Server 7 and is the answer not in the manual?