{"id":1827,"date":"2018-03-19T22:55:16","date_gmt":"2018-03-20T01:55:16","guid":{"rendered":"https:\/\/zmsolution.laraclaud.com.br\/?p=1827"},"modified":"2018-03-20T23:46:36","modified_gmt":"2018-03-21T02:46:36","slug":"instalando-o-oracle-soa-12-2-1-parte-3","status":"publish","type":"post","link":"http:\/\/zmsolution.com\/instalando-o-oracle-soa-12-2-1-parte-3\/","title":{"rendered":"Instalando o Oracle SOA 12.2.1 \u2013 Parte 3"},"content":{"rendered":"

Parte 3<\/strong>\u2013\u00a0Configurando o\u00a0 Oracle\u00a0SOA Su\u00edte\u00a0<\/strong><\/p>\n

 <\/p>\n

Neste artigo Instalando o Oracle SOA 12.2.1 \u2013 Parte 3<\/strong>\u00a0 vou falar de algumas configura\u00e7\u00f5es que s\u00e3o\u00a0imprescind\u00edveis\u00a0 na prepara\u00e7\u00e3o do nosso ambiente, vamos iniciar com o\u00a0boot.properties\u00a0<\/strong><\/p>\n

Criando o arquivo boot.properties<\/strong><\/p>\n

Todas as vezes que precisamos subir o nosso ambiente, o weblogic solicita que seja digitado o usu\u00e1rio e a senha da aplica\u00e7\u00e3o como mostrado na abaixo:<\/p>\n

INFO: JPS bootstrap service started.\r\n<Mar 15, 2018 9:12:49 PM BRT> <Info> <RCM> <BEA-2165021> <\"ResourceManagement\" is not enabled in this JVM. Enable \"ResourceManagement\" to use the WebLogic Server \"Resource Consumption Management\" feature. To enable \"ResourceManagement\", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.>\r\n<Mar 15, 2018 9:12:49 PM BRT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.2.1.3.0 Thu Aug 17 13:39:49 PDT 2017 1882952>\r\n<Mar 15, 2018 9:12:55 PM BRT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>\r\nEnter username to boot WebLogic server:weblogic\r\nEnter password to boot WebLogic server:<\/pre>\n
Isso acaba dificultando um pouco colocar o startup do weblogic em blackground e facilita que a senha do weblogic seja descoberta.<\/p>\n
Para resolver esse problema podemos criar o arquivo\u00a0 boot.properties<\/strong>, ap\u00f3s a sua cria\u00e7\u00e3o o weblogic criptografa a senha e toda vez que seja necess\u00e1rio um restart da aplica\u00e7\u00e3o o weblogic buscara a senha no arquivo.<\/p>\n
A cria\u00e7\u00e3o do arquivo \u00e9 bem simples:<\/strong><\/p>\n
cd \/u02\/middleware\/config\/domains\/soa_domain\/servers\/AdminServer\r\nmkdir security\r\ncd security\r\ntouch boot.properties\r\nedite o arquivo\u00a0 boot.properties e adicione as linhas:\r\nusername=weblogic\u00a0\u00a0 \r\npassword=oracle123<\/pre>\n
salve e reinicie o seu weblogic<\/p>\n
nohup .\/startWebLogic.sh &<\/strong><\/p>\n
Mar 15, 2018 9:28:54 PM oracle.security.jps.JpsStartup startWithRetry\r\nINFO: Jps started.\r\n<Mar 15, 2018 9:28:54,328 PM BRT> <Notice> <Security> <BEA-090946> <Security pre-initializing using security realm: myrealm>\r\n<Mar 15, 2018 9:28:54,907 PM BRT> <Notice> <Security> <BEA-090947> <Security post-initializing using security realm: myrealm>\r\n<Mar 15, 2018 9:28:55,659 PM BRT> <Notice> <Security> <BEA-090082> <Security initialized using administrative security realm: myrealm>\r\n<Mar 15, 2018 9:28:55,706 PM BRT> <Notice> <Security> <BEA-090083> <Storing boot identity in the file: \/u02\/middleware\/config\/domains\/soa_domain\/servers\/AdminServer\/security\/boot.properties.><\/pre>\n
<Mar 15, 2018 9:31:46,916 PM BRT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN.>\r\n<Mar 15, 2018 9:31:46,963 PM BRT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING.>\r\n<Mar 15, 2018 9:31:46,963 PM BRT> <Notice> <JMX> <BEA-149535> <JMX Resiliency Activity Server=All Servers : Resolving connection list DomainRuntimeServiceMBean>\r\n<Mar 15, 2018 9:31:47,466 PM BRT> <Notice> <WebLogicServer> <BEA-000329> <Started the WebLogic Server Administration Server \"AdminServer\" for domain \"soa_domain\" running in production mode.>\r\n<Mar 15, 2018 9:31:47,466 PM BRT> <Notice> <Server> <BEA-002613> <Channel \"Default\" is now listening on 192.168.56.109:7001 for protocols iiop, t3, ldap, snmp, http.>\r\n<Mar 15, 2018 9:31:47,467 PM BRT> <Notice> <Server> <BEA-002613> <Channel \"Default\" is now listening on 192.168.56.109:7001 for protocols iiop, t3, ldap, snmp, http.>\r\n<Mar 15, 2018 9:31:47,608 PM BRT> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>\r\n<Mar 15, 2018 9:31:47,618 PM BRT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.><\/pre>\n
Observe como ficou o nosso arquivo ap\u00f3s iniciarmos o weblogic :<\/p>\n
vi boot.properties\r\n\r\n#Thu Mar 15 21:30:13 BRT 2018\r\npassword={AES}8k7Wn0+JaMJgHVQEwgPVji7YcejS9\/LhrDMv6Uthis0\\=\r\nusername={AES}9X3Hz63otO3AG5v4n3898xIvr7US9w6JDRbd\/fOgnqE\\=<\/pre>\n
Nodemanager<\/strong><\/p>\n
O Nodemanager<\/strong>\u00a0server para iniciar os Managers Server<\/strong> remotamente ,sem a necessidade de iniciarmos pelo SO<\/strong>.<\/p>\n
Vamos tentar iniciar os Managers\u00a0<\/strong>\u00a0Servers<\/strong> sem o Nodemanager<\/strong> configurado e inicializado:<\/p>\n
\"\"<\/p>\n
Observe a mensagem informando que n\u00e3o \u00e9 poss\u00edvel iniciar os Mangers Servers devido ao Nodemanager.<\/p>\n
\"\"<\/p>\n
Configurando o Nodemanage:<\/strong><\/p>\n
Entre no diret\u00f3rio nodemanager:<\/strong><\/p>\n
cd \/u02\/middleware\/config\/domains\/soa_domain\/nodemanager\r\nvi nodemanager.properties<\/pre>\n
Altere os par\u00e2metros SecureListener<\/strong> para false <\/strong>e\u00a0StartScriptEnable<\/strong> para True\u00a0<\/strong><\/p>\n
Observe como ficou o nosso arquivo\u00a0nodemanager.properties<\/p>\n
#Node manager properties\r\n\r\n#Fri Mar 09 00:26:56 BRT 2018\r\n\r\nDomainsFile=\/u02\/middleware\/config\/domains\/soa_domain\/nodemanager\/nodemanager.domains\r\n\r\nLogLimit=0\r\nPropertiesVersion=12.2.1\r\nAuthenticationEnabled=true\r\nNodeManagerHome=\/u02\/middleware\/config\/domains\/soa_domain\/nodemanager\r\nJavaHome=\/u01\/app\/oracle\/java\/jdk1.8.0_161\r\nLogLevel=INFO\r\nDomainsFileEnabled=true\r\nListenAddress=localhost\r\nNativeVersionEnabled=true\r\nListenPort=5556\r\nLogToStderr=true\r\nweblogic.StartScriptName=startWebLogic.sh\r\nSecureListener=false\r\nLogCount=1\r\nQuitEnabled=false\r\nLogAppend=true\r\nweblogic.StopScriptEnabled=false\r\nStateCheckInterval=500\r\nCrashRecoveryEnabled=false\r\nweblogic.StartScriptEnabled=true\r\nLogFile=\/u02\/middleware\/config\/domains\/soa_domain\/nodemanager\/nodemanager.log\r\nLogFormatter=weblogic.nodemanager.server.LogFormatter\r\nListenBacklog=50<\/pre>\n
Entre no diret\u00f3rio bin<\/strong><\/p>\n
cd \/u02\/middleware\/config\/domains\/soa_domain\/bin<\/pre>\n
Inicie o weblogic\u00a0 no arquivo\u00a0startNodeManager.sh<\/strong><\/p>\n
nohup .\/startNodeManager.sh &<\/pre>\n
<Mar 15, 2018 10:13:22 PM BRT> <INFO> <12.2.1.3.0>\r\n\r\n<Mar 15, 2018 10:13:22 PM BRT> <INFO> <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.>\r\n\r\n<Mar 15, 2018 10:13:22 PM BRT> <INFO> <Plain socket listener started on port 5556, host localhost\/127.0.0.1><\/pre>\n
O pr\u00f3ximo passo \u00e9 a configura\u00e7\u00e3o das Machines,\u00a0As\u00a0Machines\u00a0\u00a0s\u00e3o o mecanismo que atribuem o Nodemanager ao Weblogic.<\/p>\n
Para iniciarmos vamos alterar a console para o modo Edi\u00e7\u00e3o<\/p>\n
\"\"<\/p>\n
V\u00e1 em Machines<\/strong><\/p>\n
\"\"<\/p>\n
Acesse a aba Node Manger<\/strong><\/p>\n
\"\"<\/p>\n
Altere o type para Plan<\/strong><\/p>\n
\"\"<\/p>\n
Salve e Aperte em Active Changes<\/strong> para salvar as alter\u00e7oes .<\/p>\n
\"\"<\/p>\n
Reinicie o weblogic<\/strong><\/p>\n
nohup .\/startWebLogic.sh &<\/pre>\n
Agora vamos tenta reiniciar os Managers Servers<\/strong> novamente:<\/p>\n
\"\"<\/p>\n
\"\"<\/p>\n
\"\"<\/p>\n
O pr\u00f3ximo\u00a0 passo das nossas configura\u00e7\u00f5es b\u00e1sicas , ser\u00e1 a melhoria da memora dos nossos Manages Server.<\/p>\n
Podemos observar na figura abaixo que a configura\u00e7\u00e3o de mem\u00f3ria default \u00e9 bem pequena fazendo com que os Managers n\u00e3o aguente a carga e acabe reiniciando, para isso n\u00e3o ocorrer ,vamos alterar a configura\u00e7\u00e3o de memoria dos nossos Managers Servers.<\/p>\n
\"\"<\/p>\n
Acesse:\u00a0 http:\/\/localhost:7001\/console\/<\/p>\n
Aperte o bot\u00e3o Lock & Edit<\/strong><\/p>\n
\"\"<\/p>\n
V\u00e1 em Servers<\/strong><\/p>\n
\"\"<\/p>\n
Click em soa_server1<\/strong><\/p>\n
\"\"<\/p>\n
V\u00e1 em configuration -> server start<\/strong><\/p>\n
\"\"<\/p>\n
Em arguments adicione o novo valor da memoria do Manager Server<\/strong><\/p>\n
\"\"<\/p>\n
Salve e Ative as altera\u00e7oes<\/strong><\/p>\n
\"\"<\/p>\n
Reinicie o Manager que teve a mem\u00f3ria alterada<\/p>\n
\"\"<\/p>\n
\"\"<\/p>\n
\"\"<\/p>\n
Podemos verificar que agora existe mais uma linha nas vari\u00e1veis do nosso Manager<\/p>\n
\"\"<\/p>\n
Agora que j\u00e1 estamos com o nosso SOA suite<\/strong> configurado\u00a0 j\u00e1\u00a0podemos\u00a0 finalizar o nosso artigo, No pr\u00f3ximo Vamos instalar o\u00a0 Oracle\u00a0<\/strong>HTTPS Server<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Parte 3\u2013\u00a0Configurando o\u00a0 Oracle\u00a0SOA Su\u00edte\u00a0   Neste artigo Instalando o Oracle SOA 12.2.1 \u2013 Parte 3\u00a0 vou falar de algumas configura\u00e7\u00f5es que s\u00e3o\u00a0imprescind\u00edveis\u00a0 na prepara\u00e7\u00e3o do nosso ambiente, vamos iniciar com o\u00a0boot.properties\u00a0 Criando o arquivo boot.properties Todas as vezes que precisamos subir o nosso ambiente, o weblogic solicita que seja digitado o usu\u00e1rio e a senha da aplica\u00e7\u00e3o como mostrado na abaixo: INFO: JPS bootstrap service started. <Mar 15, 2018 9:12:49 PM BRT> <Info> <RCM>[…]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0},"categories":[2,20,18,19,23,22],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts\/1827"}],"collection":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/comments?post=1827"}],"version-history":[{"count":0,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts\/1827\/revisions"}],"wp:attachment":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/media?parent=1827"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/categories?post=1827"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/tags?post=1827"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}