Install, Configure, and Run - Oracle WebLogic Server 12c Advanced Administration - page 31

WebLogic Server will look for the credentials provided in the boot.
properties file under $DOMAIN_HOME/servers/<servername>/
security/ when starting from the script.
On the other hand, the credentials will be stored automatically in
$DOMAIN_HOME/servers/<servername>/data/nodemanager/
boot.properties if the startup command is issued to the Node
Manager. WebLogic Server will not ask for the username/password.
See also
F Starting the Node Manager
F Starting the Administration Server
Deploying applications
This recipe will cover the deployment of a J2EE Application archived file (EAR), but it also
applies to Web Application (WAR), Resource Adapters(RAR), and other JAR archived files,
such as libraries, EJBs, and Java classes.
The following steps will walk you through the process to deploy the application. The WebLogic
administrator usually assumes the deployer role in a production environment, so make sure to
define a well-structured procedure to deploy the applications and follow it.
Getting ready
This recipe will deploy an archived application file called myApp.ear . The application will be
target of the PROD_Cluster cluster instead of the individual Managed Servers.
How to do it...
Carry out the following steps:
1. Create a new directory to be the application installation directory using the syntax /
oracle/applications/<environment>/<application>/<version> :
[wls@prod01]$ mkdir -p /oracle/applications/prod/myApp/v1
[wls@prod01]$ cd /oracle/applications/prod/myApp/v1
2. Create two directories:
[wls@prod01]$ mkdir app
[wls@prod01]$ mkdir plan