Technical data

10 Recovering Failed Servers
10-4 Configuring and Managing WebLogic Server
MSI Mode and SSL
If you set up SSL for your servers, each server requires its own set of certificate files,
key files, and other SSL-related files. Managed Servers do not retrieve SSL-related
files from the Administration Server (though the domain’s configuration file does store
the pathnames to those files for each server). Starting in MSI Mode does not require
you to copy or move the SSL-related files unless they are located on a machine that is
inaccessible.
MSI Mode and Deployment
A Managed Server that starts in MSI mode deploys its applications from its staging
directory:
serverroot/stage/appName.
MSI Mode and Managed Server Configuration Changes
If you start a Managed Server in MSI mode, you cannot change its configuration until
it restores communication with the Administration Server.
MSI Mode and Node Manager
You cannot use Node Manager to start a server instance in MSI mode, because Node
Manager requires the presence of the Administration Server. If the Administration
Server is unavailable, you must log onto Managed Server’s host machine to start the
Managed Server.
MSI Mode and Configuration File Replication
Managed Server Independence mode includes an option that copies the required
configuration files into the Managed Server's root directory every 5 minutes. This
option does not replicate a boot identity file. (For more information about boot identity
files, see “Bypassing the Prompt for Username and Password” in Administration
Console Online Help.)
By default, a Managed Server does not replicate these files. Depending on your backup
schemes and the frequency with which you update your domain's configuration, this
option might not be worth the performance cost of copying potentially large files
across a network.
Caution: Do not enable file replication for a server that shares an installation or root
directory with another server. Unpredictable errors can occur for both servers.