![\"Install](\"https:\/\/www.howtoforge.com\/images\/how_to_setup_and_install_oracle_weblogic_in_centos_6\/big\/high_level.jpg\" "\\"\\"")
<\/a><\/p>\n1. Preliminary Note<\/h2>\n
For this tutorial, I’ll be using CentOS 7.4 in 64bit version. Please note that even though the configuration\u00a0is made under CentOS 7, yet the steps and modification are mainly the same when\u00a0using RedHat or Oracle Linux flavor. The reason I’ve mentioned this\u00a0is most production installations for Oracle Weblogic will use Oracle Linux itself as the operating system.<\/p>\n
By the end of this tutorial, we will have managed to bring up 2 server nodes that will act as Weblogic Managed Servers which were created by a Weblogic Admin Server. Apart from that, we will be\u00a0using the\u00a0Admin Server dashboard to combine both Managed Servers into a cluster group.<\/p>\n
2. Installation Phase<\/h2>\n
As Oracle Weblogic’s purpose\u00a0is to serve high-performance application code\u00a0in JAVA programming language, it’s quite obvious that the installation for the middleware server itself would require java runtime to be built in. Therefore, for the installation prerequisite, we will need to install JAVA package into our admin server and the two managed nodes. The steps are like below:<\/p>\n
[[email\u00a0protected]<\/a>_mgr opt]# wget –no-cookies –no-check-certificate –header “Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie” “http:\/\/download.oracle.com\/otn-pub\/java\/jdk\/8u131-b11\/d54c1d3a095b4ff2b6607d096fa80163\/jdk-8u131-linux-x64.rpm” 100%[==============================================================================>] 169,983,496 2.56MB\/s in 64s<\/p>\n 2018-06-09 12:58:15 (2.54 MB\/s) – \u2018jdk-8u131-linux-x64.rpm\u2019 saved [169983496\/169983496]\n [[email\u00a0protected]<\/a>_mgr opt]# yum localinstall -y jdk-8u131-linux-x64.rpm<\/p>\n Once done, we continue to make amendment on the environment path to create JAVA_HOME variable inside each server node. Below are the steps:<\/p>\n [[email\u00a0protected]<\/a>_mgr opt]# vi \/root\/.bash_profile [[email\u00a0protected]<\/a>_mgr opt]# source \/root\/.bash_profile For Oracle database installation, it’s a\u00a0requirement that the installation must be done using non-root user. That’s also applies on Oracle Weblogic installation. As for that policy, to proceed let’s create additional user to be owner for Oracle Weblogic. Below are the steps:<\/p>\n [[email\u00a0protected]<\/a>_mgr opt]# useradd -s \/bin\/bash shahril<\/p>\n [[email\u00a0protected]<\/a>_mgr opt]# passwd shahril [[email\u00a0protected]<\/a>_mgr opt]# su – shahril Before we proceed further, let’s configure the environment variables for weblogic owner user for required variables. Below are the best practice variables need to be assign:<\/p>\n [[email\u00a0protected]<\/a>_mgr wls]$ vi \/home\/shahril\/.bash_profile<\/p>\n export ORACLE_BASE=\/home\/shahril\/wls\/oracle export JAVA_HOME=\/usr\/java\/jdk1.8.0_131 [[email\u00a0protected]<\/a>_mgr wls]$ source \/home\/shahril\/.bash_profile Once done, let’s create a file called oraInst.loc and wls.rsp . For filename oraInst.loc: this file is needed to define an inventory location during the Oracle Weblogic installation. For filename wls.rsp, it is optional as it acts as a response file that will be used during the installation. Yet, as moving along we will make the installation from command line interface (CLI), the wls.rsp would be a compulsory for us to have. Now, let’s proceed with the steps as per below:<\/p>\n [[email\u00a0protected]<\/a>_mgr wls]$ pwd inventory_loc=\/home\/shahril\/wls\/oraInventory [[email\u00a0protected]<\/a>_mgr wls]$ vi wls.rsp<\/p>\n [ENGINE]\nResponse File Version=1.0.0.0.0 As exerything is in place, let’s proceed\u00a0with downloading the Oracle Weblogic installer. You can go to website URL here<\/a> and choose your favorite version of Oracle Weblogic.<\/p>\n In our case, we will proceed with downloading Oracle Weblogic version 12.1.3 as by far now it’s the most up-to-date and stable version (base on my current facing experience). Below are the steps:<\/p>\n [[email\u00a0protected]<\/a>_mgr ~]$ cd $ORACLE_BASE 100%[=================================================================>] 923,179,081 1.05MB\/s in 16m 4s<\/p>\n 2018-06-28 16:40:24 (935 KB\/s) – \u2018fmw_12.1.3.0.0_wls.jar?AuthParam=1530174357_1de6ededa212d8bc86524a0fb78ac0df\u2019 saved [923179081\/923179081]\n [[email\u00a0protected]<\/a>_mgr oracle]$ mv fmw_12.1.3.0.0_wls.jar?AuthParam=1530174357_1de6ededa212d8bc86524a0fb78ac0df fmw_12.1.3.0.0_wls.jar<\/p>\n Next, proceed with the installation. Steps are as per shown below:<\/p>\n [[email\u00a0protected]<\/a>_mgr wls]$ java -jar \/home\/shahril\/wls\/oracle\/fmw_12.1.3.0.0_wls.jar -silent -responseFile \/home\/shahril\/wls\/wls.rsp -invPtrLoc \/home\/shahril\/wls\/oraInst.loc Checking if CPU speed is above 300 MHz. Actual 3199.968 MHz Passed Preparing to launch the Oracle Universal Installer from \/tmp\/OraInstall2018-06-10_12-44-24PM The installation of Oracle Fusion Middleware 12c WebLogic Server and Coherence 12.1.3.0.0 completed successfully. Excellent! Now we’ve successfully installed Oracle Weblogic onour CentOS 7 server. Next, we will proceed with the configuration phase.<\/p>\n Now we are in the configuration part, there will be 2 level of configuration that needs to be made which are:<\/p>\n For a Weblogic Administration server, we need to make both of the configuration as the main command of weblogic are under weblogic configuration. But for every Weblogic managed server that will act act the instance node, it just need to setup for Weblogic Configuration only as during the initialization of domain, administrator can decide which instance node will be use for which project domain. Below are the simple example of how weblogic domain works:<\/p>\n For every weblogic managed server, you can create as many instance nodes as you need, this depends on you server resource allocation because each instance node will be point to its dedicated project domain. To point which domain to which instance node can easily done by administration server dashboard.<\/p>\n As per brief, now let’s setup the configuration for weblogic and domain configuration for admin server part. Just to simplified the tutorial process, we will only create 1 domain called TEST. Below are the steps :-<\/p>\n [[email\u00a0protected]<\/a>_mgr wls]$ cd $WL_HOME Welcome to WebLogic Server Administration Scripting Shell<\/p>\n Type help() for help on available commands<\/p>\n wls:\/offline> readTemplate(‘\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/templates\/wls\/wls.jar’) wls:\/offline\/base_domain\/Server\/AdminServer>create(‘AdminServer’,’SSL’) wls:\/offline\/base_domain\/Server\/AdminServer>cd(‘SSL\/AdminServer’) wls:\/offline\/base_domain\/Server\/AdminServer\/SSL\/AdminServer>cd(‘\/’) wls:\/offline\/TEST\/Security\/TEST\/User\/weblogic>closeTemplate() Exiting WebLogic Scripting Tool.<\/p>\n Great, now we’ve done the configuration for both, now let’s start the weblogic and TEST services on admin server. Below are the steps:<\/p>\n [[email\u00a0protected]<\/a>_mgr bin]$ cd $DOMAIN_HOME [[email\u00a0protected]<\/a>_mgr bin]$ .\/startWebLogic.sh & INFO: The Wsee Service is starting<\/p>\n Jun 10, 2018 1:11:51 PM UTC Notice Log Management BEA-170027 The server has successfully established a connection with the Domain level Diagnostic Service. [[email\u00a0protected]<\/a>_mgr bin]$ netstat -apn|grep -i :70 Excellent! Now we have made the complete configuration on the admin server part. Now as the complicated\u00a0parts have been done, you can relax, take a cup of coffee then just make a copy of Weblogic configuration ONLY and paste it on each managed server node. Below are the steps :-<\/p>\n [[email\u00a0protected]<\/a>_mgr bin]$ $WL_HOME\/common\/bin\/pack.sh -domain=$DOMAIN_HOME -template=$WL_HOME\/common\/templates\/domains\/TEST_template.jar -template_name=TEST -managed=true [[email\u00a0protected]<\/a>_mgr ~]$ ls -lh $WL_HOME\/common\/templates\/domains\/TEST_template.jar Shown above we’ve made a copy of weblogic configuration into a jar file. We will bring over only this jar file to each weblogic managed server and set it up from there.<\/p>\n [[email\u00a0protected]<\/a>_mgr ~]$ scp -r \/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/templates\/domains\/TEST_template.jar 172.17.0.7:\/home\/shahril\/wls\/ Now go to the managed server and extract the copied jar file. No configuration is needed as it will bring over related domain we’ve created. Below are the steps:<\/p>\n [[email\u00a0protected]<\/a>_node1 ~]$ cd $WL_HOME Excellent! We have successfully extracted the copied weblogic configuration. Next step, let’s start the Weblogic service in managed server. Below are the steps:<\/p>\n [[email\u00a0protected]<\/a>_node1 wlserver]$ cd $DOMAIN_HOME Welcome to WebLogic Server Administration Scripting Shell<\/p>\n Type help() for help on available commands<\/p>\n Connecting to t3:\/\/172.17.0.6:7001 with userid weblogic … Warning: An insecure protocol was used to connect to the Shutting down the server Node_Server01 with force=false while connected to AdminServer … Done [[email\u00a0protected]<\/a>_node1 bin]$ .\/startManagedWebLogic.sh Node_Server01 t3:\/\/172.17.0.6:7001 & Jun 10, 2018 3:29:48 PM UTC Notice Log Management BEA-170027 The server has successfully established a connection with the Domain level Diagnostic Service. Great! Now we have successfully configured the weblogic services on the managed servers. You can do the process to other managed server and later we will define the cluster grouping from administration server dashboard.<\/p>\n To ensure that our Weblogic architecture works as expected, we’ll just apply a simple test configuration on our servers. For this test, we will open the Weblogic admin server dashboard and from the dashboard console itself we will add our 2 managed servers into the environment and define them as a cluster.<\/p>\n Now, let’s open up our admin dashboard via http:\/\/172.17.0.6:7001\/console . As mentioned before, for this test, we are’ve just creating only 1 DOMAIN which is TEST therefore the default port 7001 are dedicated for this domain. For multiple domains, the configuration can be seperated by its own dedicated port. Once you have launched the URL in the browser, you should see the console like below, enter the username and password that we’ve defined during configuration above. For this test, it’s weblogic\/Test1234 :-<\/p>\n Once you have login successfully, you will see a complete dashboard like shown below:<\/p>\n To proceed with our test, from the dashboard click on Environment -> Servers tab . You will see the results as shown like below which automatically the Weblogic Admin server already included inside TEST domain.<\/p>\n Next, click on the button After that, define the new cluster name you want to the click next. Remain others as per default like example below:<\/p>\n Great, now you’ve include an instance node inside your newly created weblogic cluster. Below are the example snapshot:<\/p>\n Now, let’s bring up the instance node. For this case, we’ll go back to CLI shell and start up the weblogic managed server like command we use before like below:<\/p>\n [[email\u00a0protected]<\/a>_node1 wlserver]$ cd $DOMAIN_HOME Once done, go back to admin URL and refresh the dashboard. You will see that now the instance node you’ve established are up and running. Below is the example\u00a0screenshot:<\/p>\n Next, use the same process to add another Weblogic Managed Server into the defined cluster. As the final result, you will see all instance nodes you’ve added are up and running and\u00a0in load balancing mode. Below is the example result:<\/p>\n Congratulations! Now you’ve successfully created a new weblogic cluster architecture.<\/p>\n Share this page:<\/b><\/p>\n In this tutorial, I’ll guide you on how to setup and install Oracle Weblogic\u00a0on CentOS 7 operation system. Oracle Weblogic is a middleware tool that is widely used by large companies to serve applications that use Java EE as programming language. With its cool UI, proven features like coherence module (for caching purpose), database clustering …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-5385","post","type-post","status-publish","format-standard","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/5385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=5385"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/5385\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=5385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=5385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=5385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n–2018-06-09 12:57:05– http:\/\/download.oracle.com\/otn-pub\/java\/jdk\/8u131-b11\/d54c1d3a095b4ff2b6607d096fa80163\/jdk-8u131-linux-x64.rpm
\nResolving download.oracle.com (download.oracle.com)… 23.49.16.62
\nConnecting to download.oracle.com (download.oracle.com)|23.49.16.62|:80… connected.
\nHTTP request sent, awaiting response… 302 Moved Temporarily
\nLocation: https:\/\/edelivery.oracle.com\/otn-pub\/java\/jdk\/8u131-b11\/d54c1d3a095b4ff2b6607d096fa80163\/jdk-8u131-linux-x64.rpm [following]\n–2018-06-09 12:57:10– https:\/\/edelivery.oracle.com\/otn-pub\/java\/jdk\/8u131-b11\/d54c1d3a095b4ff2b6607d096fa80163\/jdk-8u131-linux-x64.rpm
\nResolving edelivery.oracle.com (edelivery.oracle.com)… 104.103.48.174, 2600:1417:58:181::2d3e, 2600:1417:58:188::2d3e
\nConnecting to edelivery.oracle.com (edelivery.oracle.com)|104.103.48.174|:443… connected.
\nHTTP request sent, awaiting response… 302 Moved Temporarily
\nLocation: http:\/\/download.oracle.com\/otn-pub\/java\/jdk\/8u131-b11\/d54c1d3a095b4ff2b6607d096fa80163\/jdk-8u131-linux-x64.rpm?AuthParam=1528549151_b1fd01d854bc0423600a83c36240028e [following]\n–2018-06-09 12:57:11– http:\/\/download.oracle.com\/otn-pub\/java\/jdk\/8u131-b11\/d54c1d3a095b4ff2b6607d096fa80163\/jdk-8u131-linux-x64.rpm?AuthParam=1528549151_b1fd01d854bc0423600a83c36240028e
\nConnecting to download.oracle.com (download.oracle.com)|23.49.16.62|:80… connected.
\nHTTP request sent, awaiting response… 200 OK
\nLength: 169983496 (162M) [application\/x-redhat-package-manager]\nSaving to: \u2018jdk-8u131-linux-x64.rpm\u2019<\/p>\n
\nexport JAVA_HOME=\/usr\/java\/jdk1.8.0_131
\nPATH=$JAVA_HOME\/bin:$PATH:$HOME\/bin
\nexport PATH<\/p>\n
\n[[email\u00a0protected]<\/a>_mgr opt]# java -version
\njava version “1.8.0_131”
\nJava(TM) SE Runtime Environment (build 1.8.0_131-b11)
\nJava HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)<\/p>\n
\nChanging password for user shahril.
\nNew password:
\nBAD PASSWORD: The password fails the dictionary check – it is too simplistic\/systematic
\nRetype new password:
\npasswd: all authentication tokens updated successfully.<\/p>\n
\n[[email\u00a0protected]<\/a>_mgr ~]$ pwd
\n\/home\/shahril<\/p>\n\n
\nexport ORACLE_HOME=$ORACLE_BASE\/product\/fmw12
\nexport MW_HOME=$ORACLE_HOME
\nexport WLS_HOME=$MW_HOME\/wlserver
\nexport WL_HOME=$WLS_HOME
\nexport DOMAIN_BASE=$ORACLE_BASE\/config\/domains
\nexport DOMAIN_HOME=$DOMAIN_BASE\/TEST<\/p>\n
\nPATH=$JAVA_HOME\/bin:$PATH:$HOME\/bin
\nexport PATH<\/p>\n
\n[[email\u00a0protected]<\/a>_mgr wls]$ mkdir -p $ORACLE_BASE
\n[[email\u00a0protected]<\/a>_mgr wls]$ mkdir -p $DOMAIN_BASE
\n[[email\u00a0protected]<\/a>_mgr wls]$ mkdir -p $ORACLE_HOME
\n[[email\u00a0protected]<\/a>_mgr wls]$ mkdir -p $ORACLE_BASE\/config\/applications
\n[[email\u00a0protected]<\/a>_mgr wls]$ mkdir -p \/home\/shahril\/wls\/oraInventory<\/p>\n
\n\/home\/shahril\/wls
\n[[email\u00a0protected]<\/a>_mgr wls]$ vi oraInst.loc<\/p>\n
\ninst_group=shahril<\/p>\n
\n[GENERIC]\nORACLE_HOME=\/home\/shahril\/wls\/oracle\/product\/fmw12
\nINSTALL_TYPE=WebLogic Server
\nDECLINE_SECURITY_UPDATES=true
\nSECURITY_UPDATES_VIA_MYORACLESUPPORT=false<\/p>\n
\n[[email\u00a0protected]<\/a>_mgr oracle]$ wget http:\/\/download.oracle.com\/otn\/nt\/middleware\/12c\/wls\/1213\/fmw_12.1.3.0.0_wls.jar?AuthParam=1530174357_1de6ededa212d8bc86524a0fb78ac0df
\n–2018-06-28 16:24:15– http:\/\/download.oracle.com\/otn\/nt\/middleware\/12c\/wls\/1213\/fmw_12.1.3.0.0_wls.jar?AuthParam=1530174357_1de6ededa212d8bc86524a0fb78ac0df
\nResolving download.oracle.com (download.oracle.com)… 23.74.208.198
\nConnecting to download.oracle.com (download.oracle.com)|23.74.208.198|:80… connected.
\nHTTP request sent, awaiting response… 200 OK
\nLength: 923179081 (880M) [application\/x-jar]\nSaving to: \u2018fmw_12.1.3.0.0_wls.jar?AuthParam=1530174357_1de6ededa212d8bc86524a0fb78ac0df\u2019<\/p>\n
\nLauncher log file is \/tmp\/OraInstall2018-06-10_12-44-24PM\/launcher2018-06-10_12-44-24PM.log.
\nExtracting files…….
\nStarting Oracle Universal Installer<\/p>\n
\nChecking swap space: must be greater than 512 MB. Actual 7815164 MB Passed
\nChecking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required)
\nChecking temp space: must be greater than 300 MB. Actual 393285 MB Passed<\/p>\n
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
\nLog: \/tmp\/OraInstall2018-06-10_12-44-24PM\/install2018-06-10_12-44-24PM.log
\nCopyright (c) 1996, 2014, Oracle and\/or its affiliates. All rights reserved.
\nReading response file..
\nStarting check : CertifiedVersions
\n\/bin\/cat: \/proc\/sys\/net\/core\/wmem_default: No such file or directory
\nStarting check : CheckJDKVersion
\nExpected result: 1.7.0_15
\nActual Result: 1.8.0_131
\nCheck complete. The overall result of this check is: Passed
\nCheckJDKVersion Check: Success.
\nValidations are enabled for this session.
\nVerifying data……
\nCopying Files…
\nYou can find the log of this install session at:
\n\/tmp\/OraInstall2018-06-10_12-44-24PM\/install2018-06-10_12-44-24PM.log
\n———–20%———-40%———-60%———-80%——–100%<\/p>\n
\nLogs successfully copied to \/home\/shahril\/wls\/oraInventory\/logs.<\/p>\n3. Configuration Phase<\/h2>\n
\n
<\/a><\/p>\n
\n[[email\u00a0protected]<\/a>_mgr wlserver]$ cd common\/bin\/
\n[[email\u00a0protected]<\/a>_mgr bin]$ .\/commEnv.sh
\n[[email\u00a0protected]<\/a>_mgr bin]$ .\/wlst.sh
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
\nInitializing WebLogic Scripting Tool (WLST) …
\nJython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.<\/p>\n
\nwls:\/offline\/base_domain>cd(‘Servers\/AdminServer’)
\nwls:\/offline\/base_domain\/Server\/AdminServer>set(‘ListenAddress’,’172.17.0.6′)
\nwls:\/offline\/base_domain\/Server\/AdminServer>set(‘ListenPort’,7001) ## Port that will be assign to each domain<\/p>\n
\nProxy for AdminServer: Name=AdminServer, Type=SSL<\/p>\n
\nwls:\/offline\/base_domain\/Server\/AdminServer\/SSL\/AdminServer>set(‘Enabled’,’True’)
\nwls:\/offline\/base_domain\/Server\/AdminServer\/SSL\/AdminServer>set(‘ListenPort’,7002)<\/p>\n
\nwls:\/offline\/base_domain>cd(‘Security\/base_domain\/User\/weblogic’)
\nwls:\/offline\/base_domain\/Security\/base_domain\/User\/weblogic>cmo.setPassword(‘Test1234’)
\nwls:\/offline\/base_domain\/Security\/base_domain\/User\/weblogic>setOption(‘OverwriteDomain’,’true’)
\nwls:\/offline\/base_domain\/Security\/base_domain\/User\/weblogic>writeDomain(‘\/home\/shahril\/wls\/oracle\/config\/domains\/TEST’)<\/p>\n
\nwls:\/offline>exit()<\/p>\n
\n[[email\u00a0protected]<\/a>_mgr TEST]$ cd bin\/
\n[[email\u00a0protected]<\/a>_mgr bin]$ pwd
\n\/home\/shahril\/wls\/oracle\/config\/domains\/TEST\/bin<\/p>\n
\n[1] 19303
\n[[email\u00a0protected]<\/a>_mgr bin]$ .
\n.
\nJAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m
\n.
\nCLASSPATH=\/usr\/java\/jdk1.8.0_131\/lib\/tools.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/weblogic_sp.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/weblogic.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/oracle_common\/modules\/net.sf.antcontrib_1.1.0.0_1-0b3\/lib\/ant-contrib.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/modules\/features\/oracle.wls.common.nodemanager_2.0.0.0.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/oracle_common\/modules\/com.oracle.cie.config-wls-online_8.1.0.0.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/derby\/lib\/derbyclient.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/derby\/lib\/derby.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/xqrl.jar .
\nPATH=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/bin:\/home\/shahril\/wls\/oracle\/product\/fmw12\/oracle_common\/modules\/org.apache.ant_1.9.2\/bin:\/usr\/java\/jdk1.8.0_131\/jre\/bin:\/usr\/java\/jdk1.8.0_131\/bin:\/usr\/java\/jdk1.8.0_131\/bin:\/usr\/java\/jdk1.8.0_131\/bin:\/usr\/java\/jdk1.8.0_131\/bin:\/usr\/local\/bin:\/bin:\/usr\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/home\/shahril\/bin:\/home\/shahril\/bin:\/home\/shahril\/bin .
\n***************************************************
\n* To start WebLogic Server, use a username and *
\n* password assigned to an admin-level user. For *
\n* server administration, use the WebLogic Server *
\n* console at http:\/\/hostname:port\/console *
\n***************************************************
\nstarting weblogic with Java version:
\njava version “1.8.0_131”
\nJava(TM) SE Runtime Environment (build 1.8.0_131-b11)
\nJava HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
\nStarting WLS with line:
\n\/usr\/java\/jdk1.8.0_131\/bin\/java -server -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/weblogic.policy -Xverify:none -Djava.endorsed.dirs=\/usr\/java\/jdk1.8.0_131\/jre\/lib\/endorsed:\/home\/shahril\/wls\/oracle\/product\/fmw12\/oracle_common\/modules\/endorsed -da -Dwls.home=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server -Dweblogic.home=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server -Dweblogic.utils.cmm.lowertier.ServiceDisabled=true weblogic.Server
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
\nJun 10, 2018 1:11:46 PM UTC Info Security BEA-090905 Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.
\nJun 10, 2018 1:11:46 PM UTC Info Security BEA-090906 Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.
\nJun 10, 2018 1:11:47 PM UTC Info WebLogicServer BEA-000377 Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 25.131-b11 from Oracle Corporation.
\nJun 10, 2018 1:11:47 PM UTC Info Management BEA-141107 Version: WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337
\nJun 10, 2018 1:11:48 PM UTC Notice WebLogicServer BEA-000365 Server state changed to STARTING.
\nJun 10, 2018 1:11:48 PM UTC Info WorkManager BEA-002900 Initializing self-tuning thread pool.
\nJun 10, 2018 1:11:48 PM UTC Info WorkManager BEA-002942 CMM memory level becomes 0. Setting standby thread pool size to 256.
\nJun 10, 2018 1:11:48 PM UTC Notice Log Management BEA-170019 The server log file \/home\/shahril\/wls\/oracle\/config\/domains\/TEST\/servers\/AdminServer\/logs\/AdminServer.log is opened. All server side log events will be written to this file.
\nJun 10, 2018 1:11:50 PM UTC Notice Security BEA-090082 Security initializing using security realm myrealm.
\nJun 10, 2018 1:11:51 PM UTC Notice WebLogicServer BEA-000365 Server state changed to STANDBY.
\nJun 10, 2018 1:11:51 PM UTC Notice WebLogicServer BEA-000365 Server state changed to STARTING.
\nJun 10, 2018 1:11:51 PM weblogic.wsee.WseeCoreMessages logWseeServiceStarting<\/p>\n
\nJun 10, 2018 1:11:51 PM UTC Notice WebLogicServer BEA-000365 Server state changed to ADMIN.
\nJun 10, 2018 1:11:51 PM UTC Notice WebLogicServer BEA-000365 Server state changed to RESUMING.
\nJun 10, 2018 1:11:51 PM UTC Notice Security BEA-090171 Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file \/home\/shahril\/wls\/oracle\/config\/domains\/TEST\/security\/DemoIdentity.jks.
\nJun 10, 2018 1:11:51 PM UTC Notice Security BEA-090169 Loading trusted certificates from the jks keystore file \/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/DemoTrust.jks.
\nJun 10, 2018 1:11:51 PM UTC Notice Security BEA-090169 Loading trusted certificates from the jks keystore file \/usr\/java\/jdk1.8.0_131\/jre\/lib\/security\/cacerts.
\nJun 10, 2018 1:11:51 PM UTC Notice Server BEA-002613 Channel “DefaultSecure” is now listening on 172.17.0.6:7002 for protocols iiops, t3s, ldaps, https.
\nJun 10, 2018 1:11:51 PM UTC Notice Server BEA-002613 Channel “Default” is now listening on 172.17.0.6:7001 for protocols iiop, t3, ldap, snmp, http.
\nJun 10, 2018 1:11:51 PM UTC Notice WebLogicServer BEA-000331 Started the WebLogic Server Administration Server “AdminServer” for domain “TEST” running in development mode.
\nJun 10, 2018 1:11:51 PM UTC Notice WebLogicServer BEA-000360 The server started in RUNNING mode.
\nJun 10, 2018 1:11:52 PM UTC Notice WebLogicServer BEA-000365 Server state changed to RUNNING.<\/p>\n
\n(Not all processes could be identified, non-owned process info
\nwill not be shown, you would have to be root to see it all.)
\ntcp 0 0 172.17.0.6:7001 0.0.0.0:* LISTEN 19360\/java
\ntcp 0 0 172.17.0.6:7002 0.0.0.0:* LISTEN 19360\/java<\/p>\n
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
\n<< read domain from “\/home\/shahril\/wls\/oracle\/config\/domains\/TEST”
\n>> succeed: read domain from “\/home\/shahril\/wls\/oracle\/config\/domains\/TEST”
\n<< set config option Managed to “true”
\n>> succeed: set config option Managed to “true”
\n<< write template to “\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/templates\/domains\/TEST_template.jar”
\n………………………………………………………………………………
\n>> succeed: write template to “\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/templates\/domains\/TEST_template.jar”
\n<< close template
\n>> succeed: close template<\/p>\n
\n-rw-r—– 1 shahril shahril 51K Jun 10 14:11 \/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/templates\/domains\/TEST_template.jar<\/p>\n
\n[email\u00a0protected]<\/a>‘s password:
\nTEST_template.jar 100% 50KB 58.2MB\/s 00:00<\/p>\n
\n[[email\u00a0protected]<\/a>_node1 wlserver]$ pwd
\n\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver
\n[[email\u00a0protected]<\/a>_node1 wlserver]$ $WL_HOME\/common\/bin\/unpack.sh -template=\/home\/shahril\/wls\/TEST_template.jar -domain=$DOMAIN_HOME
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
\n<< read template from “\/home\/shahril\/wls\/TEST_template.jar”
\n>> succeed: read template from “\/home\/shahril\/wls\/TEST_template.jar”
\n<< set config option DomainName to “TEST”
\n>> succeed: set config option DomainName to “TEST”
\n<< write Domain to “\/home\/shahril\/wls\/oracle\/config\/domains\/TEST”
\n……………………………………………………………………………………….
\n>> succeed: write Domain to “\/home\/shahril\/wls\/oracle\/config\/domains\/TEST”
\n<< close template
\n>> succeed: close template<\/p>\n
\n[[email\u00a0protected]<\/a>_node1 TEST]$ cd bin\/
\n[[email\u00a0protected]<\/a>_node1 bin]$ .\/stopManagedWebLogic.sh Node_Server01 t3:\/\/172.17.0.6:7001 weblogic Test1234
\nStopping Weblogic Server…
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
\nInitializing WebLogic Scripting Tool (WLST) …
\nJython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.<\/p>\n
\nSuccessfully connected to Admin Server “AdminServer” that belongs to domain “TEST”.<\/p>\n
\nserver. To ensure on-the-wire security, the SSL port or
\nAdmin port should be used instead.<\/p>\n
\nNo stack trace available.
\nProblem invoking WLST – Traceback (innermost last):
\nFile “\/home\/shahril\/wls\/oracle\/config\/domains\/TEST\/shutdown-Node_Server01.py”, line 4, in ?
\nFile “”, line 1199, in shutdown
\nFile “”, line 552, in raiseWLSTException
\nWLSTException: Error occurred while performing shutdown : No Server with name “Node_Server01” configured in the domain<\/p>\n
\nStopping Derby Server…<\/p>\n
\n[1] 5378
\n[[email\u00a0protected]<\/a>_node1 bin]$ .
\n.
\nJAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m
\n.
\nCLASSPATH=\/usr\/java\/jdk1.8.0_131\/lib\/tools.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/weblogic_sp.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/weblogic.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/oracle_common\/modules\/net.sf.antcontrib_1.1.0.0_1-0b3\/lib\/ant-contrib.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/modules\/features\/oracle.wls.common.nodemanager_2.0.0.0.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/derby\/lib\/derbyclient.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/common\/derby\/lib\/derby.jar:\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/xqrl.jar
\n.
\nPATH=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/bin:\/home\/shahril\/wls\/oracle\/product\/fmw12\/oracle_common\/modules\/org.apache.ant_1.9.2\/bin:\/usr\/java\/jdk1.8.0_131\/jre\/bin:\/usr\/java\/jdk1.8.0_131\/bin:\/usr\/java\/jdk1.8.0_131\/bin:\/usr\/local\/bin:\/bin:\/usr\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/home\/shahril\/bin
\n.
\n***************************************************
\n* To start WebLogic Server, use a username and *
\n* password assigned to an admin-level user. For *
\n* server administration, use the WebLogic Server *
\n* console at http:\/\/hostname:port\/console *
\n***************************************************
\nstarting weblogic with Java version:
\njava version “1.8.0_131”
\nJava(TM) SE Runtime Environment (build 1.8.0_131-b11)
\nJava HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
\nStarting WLS with line:
\n\/usr\/java\/jdk1.8.0_131\/bin\/java -server -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=Node_Server01 -Djava.security.policy=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server\/lib\/cacerts -Xverify:none -Djava.endorsed.dirs=\/usr\/java\/jdk1.8.0_131\/jre\/lib\/endorsed:\/home\/shahril\/wls\/oracle\/product\/fmw12\/oracle_common\/modules\/endorsed -da -Dwls.home=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server -Dweblogic.home=\/home\/shahril\/wls\/oracle\/product\/fmw12\/wlserver\/server -Dweblogic.management.server=t3:\/\/172.17.0.6:7001 -Dweblogic.utils.cmm.lowertier.ServiceDisabled=true weblogic.Server
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
\nJava HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
\nJun 10, 2018 3:29:41 PM UTC Info Security BEA-090905 Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.
\nJun 10, 2018 3:29:41 PM UTC Info Security BEA-090906 Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.
\nJun 10, 2018 3:29:42 PM UTC Info WebLogicServer BEA-000377 Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 25.131-b11 from Oracle Corporation.
\nJun 10, 2018 3:29:42 PM UTC Info Management BEA-141107 Version: WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337
\nJun 10, 2018 3:29:43 PM UTC Notice WebLogicServer BEA-000365 Server state changed to STARTING.
\nJun 10, 2018 3:29:43 PM UTC Info WorkManager BEA-002900 Initializing self-tuning thread pool.
\nJun 10, 2018 3:29:43 PM UTC Info WorkManager BEA-002942 CMM memory level becomes 0. Setting standby thread pool size to 256.
\nJun 10, 2018 3:29:43 PM UTC Notice Log Management BEA-170019 The server log file \/home\/shahril\/wls\/oracle\/config\/domains\/TEST\/servers\/Node_Server01\/logs\/Node_Server01.log is opened. All server side log events will be written to this file.
\nJun 10, 2018 3:29:45 PM UTC Notice Security BEA-090082 Security initializing using security realm myrealm.
\nJun 10, 2018 3:29:46 PM UTC Notice WebLogicServer BEA-000365 Server state changed to STANDBY.
\nJun 10, 2018 3:29:46 PM UTC Notice WebLogicServer BEA-000365 Server state changed to STARTING.
\nJun 10, 2018 3:29:46 PM weblogic.wsee.WseeCoreMessages logWseeServiceStarting
\nINFO: The Wsee Service is starting<\/p>\n
\nJun 10, 2018 3:29:48 PM UTC Notice Cluster BEA-000197 Listening for announcements from cluster using unicast cluster messaging
\nJun 10, 2018 3:29:48 PM UTC Notice WebLogicServer BEA-000365 Server state changed to ADMIN.
\nJun 10, 2018 3:29:48 PM UTC Notice WebLogicServer BEA-000365 Server state changed to RESUMING.
\nJun 10, 2018 3:29:48 PM UTC Notice Cluster BEA-000162 Starting “async” replication service with remote cluster address “null”
\nJun 10, 2018 3:29:48 PM UTC Notice Server BEA-002613 Channel “Default” is now listening on 172.17.0.7:8001 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.
\nJun 10, 2018 3:29:48 PM UTC Notice WebLogicServer BEA-000332 Started the WebLogic Server Managed Server “Node_Server01” for domain “TEST” running in development mode.
\nJun 10, 2018 3:29:48 PM UTC Notice WebLogicServer BEA-000360 The server started in RUNNING mode.
\nJun 10, 2018 3:29:48 PM UTC Notice WebLogicServer BEA-000365 Server state changed to RUNNING.<\/p>\n4. Testing Phase<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a> , it will forward you to page below. Fill in the Weblogic Managed Server information like it’s IP addresses and the weblogic port as per shown then click next.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\n[[email\u00a0protected]<\/a>_node1 TEST]$ cd bin\/
\n[[email\u00a0protected]<\/a>_node1 bin]$ .\/startManagedWebLogic.sh Node_Server01 t3:\/\/172.17.0.6:7001 &<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a>
\n<\/a>
\n<\/a>
\n<\/a><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"