WebLogic Installation
Installation Environment CentOS 6.4 x64
You can search WebLogic Install silent
Reference Documentation:
http://g14n.info/2014/11/install-weblogic-12c/
Official documents:
Https://docs.oracle.com/middleware/1213/core/WLSIG.pdf
1. Download and extract WebLogic
Oracle account needs to be registered, Oracle can develop learning, but production mode must have license
Address: http://www.oracle.com/technetwork/middleware/fusion-middleware/downloads/index.html
WebLogic is now part of the Fusion middleware, we choose the smallest zip download package
Download Ant
Http://mirrors.hust.edu.cn/apache//ant/binaries/apache-ant-1.9.4-bin.zip
2. Create users and Groups
# Groupadd WebLogic
# useradd-g WebLogic WebLogic
# passwd WebLogic
Alias start_weblogic= ' nohup/opt/weblogic/mydomain/bin/startweblogic.sh > $HOME/start_weblogic.nohup 2>&1 & '
Alias stop_weblogic= '/opt/weblogic/mydomain/bin/stopweblogic.sh '
########### #结束
Make the above environment variable effective
$ source ~/.bash_profile
6. Installation
$ Export mw_home=/opt/weblogic/wls12130
$ cd $MW _home
$./configure.sh
Do your want to configure a new domain? [y/n]? N
Remember to select N, or you will automatically create a mydomain, which is not recommended
7. Create domain
Set the environment variables first, the environment variables set by the previous script are obsolete, because our previous script has stopped, we need to reset
Execute the following command to find Classpath=
$/opt/weblogic/wls12130/wlserver/server/bin/setwlsenv.sh
The invariant directory is created somewhere else.
$ cd/opt/weblogic/mydomain
$ $JAVA _home/bin/java $JAVA _options-xmx1024m-xx:maxpermsize=256m WebLogic. Server
Would the server to create a default configuration and boot? (y/n): Y
Enter username to boot WebLogic server:weblogic
Enter Password to boot WebLogic server: Note that the password is at least 8 digits, must contain strings and numbers, or create domain failure
For confirmation, re-enter password required to boot WebLogic server:
Show after success
Server state changed to RUNNING
Then you can access the WebLogic management console
Http://localhost:7001/console
8. Shutdown and start
$ start_weblogic
Show: 1[8105]
$ stop_weblogic
After startup, you can check the log with the following command:
$ tail-f $HOME/start_weblogic.nohup
Tip: log4j Configuration
You can configure a single line in the WebLogic user's. Bash_profile to develop log4j configuration
Modify the port, you can modify it in the admin console, you cannot access the admin console you can modify the configuration file
# VI./domains/mydomain/config/config.xml
New in front <listen-address/>
<listen-port>9001</listen-port>
Resolving problems with WebLogic console access slow
Modify the JDK $JAVA _home/jre/lib/security/java.security files used on Linux WebLogic
Change the Securerandom.source=file:/dev/urandom to
Securerandom.source=file:/dev/./urandom
Error resolution
<Error> <Server> <BEA-002606> <the Server is unable to create a server socket for listening on Channe L "Default".
The address 61.149.195.0 might are incorrect or another process is using port 9999:java.net.bindexception:cannot assign R Equested address>
Solving method
1) to see if WebLogic is running
# Ps-ef | grep WebLogic
2 to see if the port is occupied
# Netstat-an | grep 9999
3 Empty Cache Directory Restart try
Delete the Mydomain/servers/myserver directory directly
Cache Data tmp
4) Check the IP address in the file/etc/hosts
5) Check the mydomain/config/config.xml of the listening address listen-address
6) Check Mydomain/nodemanager/nodemanager.properties
In general, listen-address modified to localhost or host name
-----------------------------------------------------------
-----------------------------------------------------------
-----------------The above content has been tested and validated CentOS 7 Weblogic 12c 12.1.3
-----------------------------------------------------------
-----------------------------------------------------------
Two. Start WebLogic Service, instructions are as follows:
# CD .../domains/mydomain--point to the domain name
# nohup Startweblogic.sh &--running WebLogic service in the background
Three. Stop WebLogic Service, instructions are as follows:
./stopweblogic.sh generally difficult to close, need to kill the background process (often)
View background processes
#ps-ef|grep WebLogic such as:
Root 28596 28558 2 16:10 pts/1 00:00:18/opt/oracle/middleware/jr ...
Root 28880 28778 0 16:22 pts/2 00:00:00 grep weblogic
Kill background Process: # kill-9 28596 can
Linux self-Startup setting method:
1.
Create a/etc/init.d/weblogic file with the following file contents:
Create the Security folder under this folder to create the file boot.properties
The contents of the Boot.properties file are as follows
Username=weblogic
password=11111111
7. Start WebLogic:
# service WebLogic Start
8. Stop WebLogic:
# Service WebLogic Stop
For an explanation of step 6
WebLogic in development mode, startup is not required to enter the administrator's username and password, but in the production mode, is needed. How can I automatically enter the administrator's password in production mode? The method is as follows:
The first method:
1. Create a password store file in the same directory as the WebLogic startup script boot.properties,
File contents:
Username= your WebLogic startup user
Password= your WebLogic's boot code.
2, start WebLogic again, at this time do not need a password can carry out the system.
3, delete the boot.properties file that you just created. (It has to be done, or it won't get in when it starts next time)
4, start WebLogic again, and then no password.
Note:
The development mode is used during installation and can be changed to production mode in the console.
The other is the D:\bea\user_projects\domains\mydomain\servers\ instance server to create a security directory, the boot.properties file into the line. Steps that do not require a 2,3,4.
Pay attention to the problem a chown–r weblogic:bea/u02
Give the WebLogic folder permissions to the WebLogic users under the BEA group
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
