WebLogic installation deployment of SUSE systems (non-graphical installation)

Directory
Introduction 1
Purpose 1
Range 1
Document Conventions 1

1. Apply Deployment Readiness 2
   1.1. Application Package and description 2
   1.2. Hardware environment 2
   1.3. Software Environment 2
   1.4. Action Tool 2
2. XLCPT Project deployment 3
   2.1. WebLogic configuration Information 3
   2.2. WebLogic Installation Preparation 3
   2.2.1. Create a WebLogic user and set a password with the same name (WebLogic user only installs) 3
   2.2.2. Create a XLCPT user and set a password with the same name (XLCPT user is used to publish the project) 3
   2.2.3. Install JDK 3
   2.2.4. Install Cronolog log cutting software 4
   2.3. WebLogic Install 4
   2.3.1. Create the WebLogic installation file 4
   2.3.2. Execute WebLogic Installation file 5
   2.4. Create WebLogic Domain 6
   2.4.1. Create the WebLogic Domain installation script file 6
   2.4.2. Execute the WebLogic Domain Setup script file 8
   2.5. Create WebLogic Master Managed startup script 8
   2.5.1. Lead domain startup script 9
   2.5.2. Managed domain Startup script 9
   2.6. The WebLogic data source is configured with the
   2.7. Redis installation deployment,
   2.7.1. Redis configuration information,
   2.7.2. Redis installs the
   2.7.3. The Redis configuration file modifies the
   2.7.4. Redis launches the
3. XLCPT Project Release-
4. Application Deployment FAQs and solutions.

1. Application Deployment Readiness
1.1. Application Package and Description
Application Package/Document System path Package/Documentation Brief description
Xlcpt.war/home/xlcpt/apphome/xlcpt.war Workshop Platform Core system
1.2. Hardware environment
Host type operating system disk space CPU memory amount
XLCPT Application Server SLES11 (x86_64) SP3 245G 16 Core 128G 2 units
XLCPT Application Server SLES11 (x86_64) SP3 245G 16 Core 64G 1 units
Redis Server SLES11 (x86_64) SP3 245G 16 Core 128G 1 units
Database server IBM AIX 6.1 100G (data storage 2T) 16 Core 64G 2 units
1.3. Software Environment
Software name software version
Weblogic 12c (12.1.3)
JDK 1.7.0_75
Redis 3.2.8
Cronolog 1.6.2
Oracle 11g R2 (11.2.0.3.0) 64bit

1.4. Operating Tools
Server Connection tool: SecureCRT, Xshell
2.XLCPT Project Deployment
2.1. WebLogic Configuration information
Host name/IP Domain primary managed name Port purpose
F23-B4-E1-B1/
10.133.212.29 xlcpt_domain AdminServer8001 8,001 Cluster Management
ManagedServer8002 8002 Managed Services 1
ManagedServer8003 8003 Managed Services 2
F23-B4-E1-B2/
10.133.212.30 ManagedServer8004 8004 Managed Services 3
ManagedServer8005 8005 Managed Services 4
F23-B4-E1-B5/
10.133.212.31 ManagedServer8006 8006 Managed Services 5
ManagedServer8007 8007 Managed Services 6
2.2. WebLogic Installation Preparation Work
Just take the first host (10.133.212.29) as an example, and the other two hosts perform the same operation.
2.2.1. Create a WebLogic user and set a password with the same name (WebLogic user for installation only)
f23-b4-e1-b1:~ # Groupadd WebLogic
f23-b4-e1-b1:~ # useradd-d/home/weblogic-m-G weblogic-g WebLogic WebLogic
f23-b4-e1-b1:~ # echo WebLogic | passwd--stdin WebLogic
2.2.2. Create a XLCPT user and set a password with the same name (XLCPT user to publish the project)
f23-b4-e1-b1:~ # Groupadd XLCPT
f23-b4-e1-b1:~ # useradd-d/home/xlcpt-m-G xlcpt-g WebLogic XLCPT
f23-b4-e1-b1:~ # echo XLCPT | passwd--stdin XLCPT
2.2.3. Installing the JDK
Different versions of WebLogic require a different version of JDK, please inquire beforehand
f23-b4-e1-b1:~ # TAR-ZXF Jdk-7u75-linux-x64.tar.gz-c/usr/local/jdk/
f23-b4-e1-b1:~ # Vim/etc/profile (add the following four lines of content)
Export Java_home=/usr/local/jdk/jdk1.7.0_75
Export classpath=.: $CLASSPATH: $JAVA _home/lib/dt.jar: $JAVA _home/lib/tools.jar
Export path= $JAVA _home/bin: $PATH
Export Jre_home= $JAVA _home/jre
f23-b4-e1-b1:~ # Source/etc/profile
2.2.4. Installing Cronolog log Cutting software
f23-b4-e1-b1:~ # TAR-ZXF Cronolog-1.6.2.tar.gz
f23-b4-e1-b1:~# CD CRONOLOG-1.6.2/
f23-b4-e1-b1:~/cronolog-1.6.2 #./configure--prefix=/usr/local/cronolog
f23-b4-e1-b1:~/cronolog-1.6.2 # Make
f23-b4-e1-b1:~/cronolog-1.6.2 # Make Install
f23-b4-e1-b1:~/cronolog-1.6.2 # cd/usr/local/cronolog/sbin/
F23-b4-e1-b1:/usr/local/cronolog/sbin # CP */usr/local/sbin/
2.3. WebLogic Installation
Just take the first host (10.133.212.29) as an example, and the other two hosts perform the same operation.
2.3.1. Create a WebLogic installation file
WebLogic installation takes the form of silent installation, which is automatically installed through the corresponding script file, the file and the WebLogic installation package has been uploaded to the/soft directory beforehand
1) generate the Orainst.loc file with the file contents as shown below
Inventory_loc=/home/weblogic/orainventory
Inst_group=weblogic
2) generate the WLS.RSP response file, the file content is as follows
[ENGINE]
#DO not.
Response File version=1.0.0.0.0
[GENERIC]
#The Oracle Home location. This can is an existing Oracle home or a new Oracle home
Oracle_home=/home/weblogic/weblogic12
#Set this variable value to the installation Type selected. e.g. WebLogic Server, Coherence, complete with Examples.
Install_type=weblogic Server
#Provide the My Oracle support Username. If you wish to ignore the Oracle configuration Manager configuration provide empty string for user name.
Myoraclesupport_username=
#Provide the My Oracle support Password
Myoraclesupport_password=<secure value>
#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle support username would ignore the Oracle Configuration Manage R Configuration
Decline_security_updates=true
#Set this to true if My Oracle support Password is specified
Security_updates_via_myoraclesupport=false
#Provide the Proxy Host
proxy_host=
#Provide the Proxy Port
proxy_port=
#Provide the Proxy Username
Proxy_user=
#Provide the Proxy Password
Proxy_pwd=<secure value>
#Type String (URL format) indicates the OCM Repeater URL which should be of the format [Scheme[http/https]]://[repeater ho St]:[repeater Port]
Collector_supporthub_url=
2.3.2. Execute the WebLogic installation file
[Email protected]:~> java-jar/soft/fmw_12.1.3.0.0_wls.jar-silent-responsefile/soft/wls.rsp-invptrloc/soft/ Orainst.loc "
After the progress display 100%, the WebLogic is installed.
2.4. Create a WebLogic Domain
WebLogic after installation, you need to create a domain to provide an environment for subsequent publishing projects
With the first host (10.133.212.29) as an example, the other two hosts fully copy the created domain directory to the/home/xlcpt/domains directory.
2.4.1. Create a WebLogic domain installation script file
[Email protected]:~> vim createdomain.py
Readtemplate ('/home/weblogic/weblogic12/wlserver/common/templates/wls/wls.jar ')
CD (' Servers/adminserver ')
Cmo.setname ("AdminServer8001")
Set (' ListenAddress ', ' 10.133.212.29 ')
Set (' Listenport ', 8001)

CD ('/')
CD ("/security/base_domain/user/weblogic")
Cmo.setpassword ("weblogic123")
SetOption ("Overwritedomain", ' true ')
SetOption (' Serverstartmode ', ' prod ')
Writedomain ('/home/xlcpt/domains/xlcpt_domain ')
Closetemplate ()

Readdomain ('/home/xlcpt/domains/xlcpt_domain ')

CD ('/')
Create (' ManagedServer8002 ', ' Server ')
CD (' server/managedserver8002 ')
Set (' Listenport ', 8002)
Set (' ListenAddress ', ' 10.133.212.29 ')

CD ('/')
Create (' ManagedServer8003 ', ' Server ')
CD (' server/managedserver8003 ')
Set (' Listenport ', 8003)
Set (' ListenAddress ', ' 10.133.212.29 ')

CD ('/')
Create (' ManagedServer8004 ', ' Server ')
CD (' server/managedserver8004 ')
Set (' Listenport ', 8004)
Set (' ListenAddress ', ' 10.133.212.30 ')

CD ('/')
Create (' ManagedServer8005 ', ' Server ')
CD (' server/managedserver8005 ')
Set (' Listenport ', 8005)
Set (' ListenAddress ', ' 10.133.212.30 ')

CD ('/')
Create (' ManagedServer8006 ', ' Server ')
CD (' server/managedserver8006 ')
Set (' Listenport ', 8006)
Set (' ListenAddress ', ' 10.133.212.31 ')

CD ('/')
Create (' ManagedServer8007 ', ' Server ')
CD (' server/managedserver8007 ')
Set (' Listenport ', 8007)
Set (' ListenAddress ', ' 10.133.212.31 ')

CD ('/')
Create (' Xlcpt_cluster ', ' Cluster ')
Assign (' Server ', ' managedserver8002,managedserver8003,managedserver8004,managedserver8005,managedserver8006, ManagedServer8007 ', ' Cluster ', ' xlcpt_cluster ')
CD (' Cluster/xlcpt_cluster ')
Set (' MulticastAddress ', ' 237.0.0.101 ')
Set (' Multicastport ', 8050)
Set (' weblogicpluginenabled ', ' true ')

Updatedomain ()
Closedomain ()

Exit ()
2.4.2. Execute the WebLogic domain Setup script file
[Email protected]:~>/home/weblogic/weblogic12/wlserver/common/bin/wlst.sh createdomain.py
When you are prompted to create successfully, the entire cluster domain environment is created successfully.
2.5. Create a WebLogic primary managed startup script
To create a startup script The following is an example of a 10.133.212.29 host, the other 2 servers managed by the startup script are similar, note to modify the IP address and the corresponding port number can be
Create a log folder at the root of the WebLogic domain to store the history log, create a servers directory where the user holds the supervisor and the managed generated files and data, and create a secure file to resolve the interoperability issue when the user starts.
[Email protected]:~/domains/xlcpt_domain> pwd
/home/xlcpt/domains/xlcpt_domain
[Email protected]:~/domains/xlcpt_domain> mkdir Log
[Email protected]:~/domains/xlcpt_domain> mkdir-p./servers/{adminserver8001/security,managedserver8002/ security,managedserver8003/security}br/>[email protected]:~/domains/xlcpt_domain>
< p="">

Username=weblogic
Password=weblogic123
Eof
[email protected]:~/domains/xlcpt_domain> CP./servers/adminserver8001/security/boot.properties./servers/ManagedServer8002/ security/
[email protected]:~/domains/xlcpt_domain> CP./servers/adminserver8001/security/boot.properties./servers/ManagedServer8003/ security/
2.5.1. Competent domain startup scripts
[email protected]:~> Cd/home/xlcpt/domains/xlcpt_domain/bin
[email protected]:~/domains/xlcpt_domain/bin> Vim startadmin8001.sh
#!/bin/bash
Export user_mem_args= "-xms2048m-xmx2048m-xx:permsize=512m-xx:maxpermsize=1024m"
rm-rf/home/xlcpt/domains/xlcpt_domain/servers/adminserver8001/tmp/
Sleep 2
/usr/bin/nohup sh startweblogic.sh | /usr/local/sbin/cronolog "/home/xlcpt/domains/xlcpt_domain/log/8001/adminserver8001.out.%y-%m-%d" 2>&1 &
Sleep 2
Tail-f/home/xlcpt/domains/xlcpt_domain/log/8001/adminserver8001.out.$ (Date +%f)
2.5.2. Managed domain Startup scripts
[email protected]:~/domains/xlcpt_domain/bin> vim startmanaged8002.sh
#!/bin/bash
Export user_mem_args= "-xms8192m-xmx8192m-xx:permsize=512m-xx:maxpermsize=1024m"
rm-rf/home/xlcpt/domains/xlcpt_domain/servers/manasgedserver8002/stage/
rm-rf/home/xlcpt/domains/xlcpt_domain/servers/managedserver8002/tmp/*
Sleep 2
/usr/bin/nohup sh/home/xlcpt/domains/xlcpt_domain/bin/startmanagedweblogic.sh ManagedServer8002 t3:// 10.133.212.29:8001 | /usr/local/sbin/cronolog "/home/xlcpt/domains/xlcpt_domain/log/8002/managedserver8002.out.%y-%m-%d" 2>&1 &
Sleep 2
Tail-f/home/xlcpt/domains/xlcpt_domain/log/8002/managedserver8002.out.$ (Date +%f)
2.6. WebLogic Data Source Configuration
Login to the WebLogic console, i.e. access http://10.133.212.29:8001/console/
1) Click Lock and Edit, service data source new

2) Select the generic data source, set the JDBC data source name to: Masterdatasource, the database type is Oracle, and select the database driver for the JDBC Gridlink. Source-0,jndi Name:

3) Enter the database connection information and select Next

4) Click Test All listeners, the database connection test, the connection test is successful, the data source configuration is successful, click Next

5) Select the managed target for the data source, select all the servers in the cluster here, and click Finish

6) When the configuration is complete, the interface is as follows

2.7. Redis Installation Deployment
2.7.1. Redis configuration information
The Redis server configuration information is as follows:
Host name/IP port usage
f23-b4-e1-b6/
10.133.212.32 6379 Redis Server
2.7.2. Redis Installation
F23-b4-e1-b6:~/software # TAR-ZXF Redis-2.6.17.tar.gz-c/usr/local/
F23-b4-e1-b6:~/software # cd/usr/local/redis-3.2.8/
f23-b4-e1-b6:/usr/local/redis-3.2.8 # Make
f23-b4-e1-b6:/usr/local/redis-3.2.8 # Make Install
2.7.3. Redis Configuration file Modification
f23-b4-e1-b6:/usr/local/redis-3.2.8 # Vim Redis.conf
The relevant contents of the modified file are:
Bind 10.133.212.32
Daemonize Yes
Pidfile/usr/local/redis-3.2.8/redis_6379.pid
LogFile "/usr/local/redis-3.2.8/redis_6379.log"
Dbfilename Dump6379.rdb
dir/usr/local/redis-3.2.8
2.7.4. Redis Boot
f23-b4-e1-b6:/usr/local/redis-3.2.8 # Redis-server Redis.conf
3.XLCPT Project Release
Open the competent domain: Enter Http://10.133.212.29:8001/console in the browser
Enter user name and password weblogic/weblogic123
1) Click Deploy, select Install in the popup screen

2) Locate the project package directory, tick the box and click Next

3) Click Next

4) Select the cluster deployment, select the default configuration for the rest click Next until the deployment is complete.

5) Start the project, tick the project package, click Start

Click Yes

6) Click on Activate changes, the app package will start running
7) The status of the console is active, which means the project is published successfully.
It's best to restart managed Services!

WebLogic installation deployment of SUSE systems (non-graphical installation)