Starting WLS 10.3.5 Managed Server in MSI mode

Question

(1) The first time you start the managed server in MSI, should the Admin Server be in Running Mode?
Or
(2) The Managed Server can be started in MSI mode (first time) with out having Admin Server in RUNNING MODE.
Which is true?
I think (1) is correct as the managed server directory wont be available under <DOMAIN_HOME>/Servers directory until you start the Managed Server. So only once you start the Managed Server, then only you can copy the config folder under Managed Server to start it in MSI mode (Having ADMIIN SERVER in SHUTDOWN state).
Is that correct?
So you can never ever start the Managed Server in MSI mode for the first time (with out having Admin Server in RUNNING MODE) after you create the managed server.
Is that correct?
Edited by: user734247 on Apr 18, 2012 2:58 PM

Answer 1

Your understanding is right.
The first time you are trying to start a managed server, you need admin server in RUNNING state.
From the next time onwards you can start managed server in MSI mode.
Although, as a workaround you can probably create certain files and directories to try and start managed server in MSI mode the first time itself:
1. Ensure that the entire domain directory is present in the machine where managed server is started.
2. Create directory <DOMAIN_HOME>/Servers/<ManagedServerName>/security
3. Create boot.properties file in <DOMAIN_HOME>/Servers/<ManagedServerName>/security/boot.properties with username and password
4. Create config-msi.xml copying from the config.xml in config directory
This list is not exclusive, it might need some more additional files.
You will have to create additional files like startServer.properties etc if we use node manager to start a managed server in MSI mode.
ORACLE strongly recommends to start the managed server through admin server the first time.
Arun