all you need to know about Node Manager for by Jacco H. Landlust zaterdag 8 december 12

Transcription

1 all you need to know about Node Manager for by Jacco H. Landlust

2 Jacco H. Landlust 35 years old Deventer, the Netherlands 2

3 Jacco H. Landlust / idba Independent Red Stack Administrator Oracle since 2000 Oracle ACE since 2006 idba since 2010 Architecture, Clustering, High Availability, Performance & Management 3

4 Agenda Introduction of Node Manager How Node Manager Works Configuration of Node Manager Using Node Manager Q & A 4

5 Why Would You Need One? 5

6 Node Manager Administrator's Guide for Oracle WebLogic Server (E ) Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. 6

7 What You can do with Node Manager Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. 7

8 Start, Shut down & Restart Start with pre-defined startup properties Shut down upon request Restart upon failure Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. 8

9 Accessing Node Manager Administration Server WebLogic Scripting Tool (WLST) Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. 9

10 Agenda Introduction of Node Manager How Node Manager Works Configuration of Node Manager Using Node Manager Q & A 10

11 Versions Java-Based Script-Based 11

12 Configuration Files nodemanager.properties nodemanager.domains Expected in Node Manager Home nm_data.properties / SerializedSystemIni.dat nm_password.properties One set of files per Node Manager 12 Expected in Domain Home

13 nodemanager.properties central configurationfile located in NodeManagerHome commandline overrides property file 13

14 nodemanager.domains Specifies the domains that a Node Manager instance controls syntax: domain-name=domain-directory 14

15 nm_data.properties & nm_password.properties nm_data.properties / SerializedSystemIni.dat stores the encryption data the Node Manager uses as a symmetric encryption key. nm_password.properties stores the encrypted Node Manager username and password 15

16 Server Specific Configuration Files startup.properties boot.properties startup.properties server_name.addr Each Managed Server instance has its own startup.properties file with properties that control how Node Manager starts up and controls the server. Node Manager automatically creates this file by using properties passed to Node Manager when the Administration Server was last used to start the server. This allows a Node Manager client or startup scripts to restart a Managed Server using the same properties last used by the Administration Server. server_name.lck For more information on startup.properties, see Step 6: Setting Server Startup Properties. These properties correspond to the server startup attributes contained in ServerStartMBean and the health monitoring attributes in ServerStartMBean. server_name.pid This file is located in DOMAIN_HOME/servers/ server_name/data/nodemanager. server_name.state server_name.addr One Set of Files per Server server_name.addr stores the IP address added when a server starts or is migrated. This file is generated after the server IP address is successfully brought online during migration.server_name.addr is deleted when the IP address is brought offline. The server IP address is used to validate remove requests to prevent addresses being erroneously removed while shutting down the server. This file is located in DOMAIN_HOME/servers/ server_name/data/nodemanager. server_name.lck Expected in an internally used lock ID. server_name.lck is generated by each server and contains This file is located in DOMAIN_HOME/servers/ server_name/data/nodemanager. Server Home server_name.pid nmgenboot StartupProps server_name.pid is generated by each server and contains 16 the process ID of the server. Node Manager checks the process ID generated by the server during crash recovery. This file is located in DOMAIN_HOME/servers/

17 Logfiles Node Manager Log File Server Instance Log Files WebLogic Server Log Files Depending upon issue check different logfile Information at multiple levels 17

18 Agenda Introduction of Node Manager How Node Manager Works Configuration of Node Manager Using Node Manager Q & A 18

19 Node Manager Config Files If they don t exist, the config files are generated upon first startup Do not store config files at default location Software Tree should be read-only 19

20 Set Basic Properties DomainsFile NodeManagerHome javahome LogFile ListenPort PropertiesVersion JavaHome 20

21 Specify Username & Password nm_password.properties nmenroll() Only change after you create domain from config.sh GUI you unpacked the domain on new location 21

22 Specify Username & Password 22

23 Specify Username & Password MOS ID How to check/verify/modify Node Manager username & password? 23

24 Store Credentials The user-configuration file contains an encrypted username and password. The key file contains a secret key that is used to encrypt and decrypt the username and password. Only the key file that originally encrypted the username and password can decrypt the values. If you lose the key file, you must create a new userconfiguration and key file pair. 24

25 Store Credentials Caution: You must ensure that only authorized users Files can be stored on external device (USB stick) can access the key file. Protect files with OS security 25

26 Store Credentials java weblogic.admin -username username [ -password password] [ -userconfigfile config-file ] [ -userkeyfile keyfile ] STOREUSERCONFIG storeuserconfig([userconfigfile], [userkeyfile], [nm]) Protect these Files! 26

27 Plain versus SSL Default SSL with demo certificates SecureListener in nodemanager.properties One Way SSL only Do not run production on demo certificates 27

28 SSL: configuration KeyStores=CustomIdentityAndCustomTrust CustomIdentityAlias=*host* CustomIdentityKeyStoreFileName=<config>/ssl/*host*_identity.jks CustomIdentityKeyStorePassPhrase=***** CustomIdentityKeyStoreType=JKS CustomIdentityPrivateKeyPassPhrase=***** CustomTrustKeyStoreFileName=<config>/ssl/truststore.jks in nodemanager.properties 28

29 SSL: Identity Store Uniquely and securely identify yourself If custom CA s are not in cacerts File, include in Indentity Store cacerts can be found at $JAVA_HOME/jre/lib/ security 29

30 SSL: Trust Store Knowledge of whom to trust Default CA s When self signed, store identity in TrustStore Keytool and non-default TrustStore 30

31 SSL -Dweblogic.security.SSL.trustedCAKeyStore when using non default CA store. for internal applications 31

32 CrashRecoveryEnabled Allows restart of a server after a system crash Start managed servers with Node Manager (not from shell) Based upon contents of server_name.lck, server_name.pid & server_name.state Do not use together with other inittab or other process protector 32

33 DomainsDirRemoteSharingEnabled NMHostName property in servers startup.properties While starting the server, Node Manager sets the NMHostName property While recovering the server, Node Manager compares the NMHostName property with the HostName on which it is currently running. Upon match Node Manager will recover the server. Useful in setups with shared filesystems 33

34 Agenda Introduction of Node Manager How Node Manager works Configuration of Node Manager Using Node Manager Q & A 34

35 Start Node Manager Classic startup script in MW_HOME From WLST: startnodemanager([verbose], [nmproperties]) set CLASSPATH && java [java_option=value...] -D[nodemanager_property=value] -D[server_property=value] weblogic.nodemanager java -Xms32m -Xmx200m -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy -DPropertiesFile=/u01/app/oracle/admin/nodemanager/${DOMAIN}/nodemanager.properties -DNodeManagerHome=/u01/app/oracle/admin/nodemanager/${DOMAIN} -DQuitEnabled=true weblogic.nodemanager -v & 35

36 wlst, rlwrap & Node Manager rlwrap runs the specified command, intercepting user input in order to provide readline s line editing, persistent history and completion. Do not start Node Manager while using wlst with rlwrap Node Manager will be child of rlwrap and die upon exit on rlwrap 36

37 Stop Node Manager From WLST: stopnodemanager() Kill the process from the OS Not so elegant, but frequently found at customer sites 37

38 Run Node Manager as a Service installnodemgrsvc.cmd rc.d service opmn / Grid Infrastructure 38

39 Connect to Node Manager nmconnect([username, password], [host], [port], [domainname], [domaindir], [nmtype]) nmconnect([userconfigfile, userkeyfile], [host], [port], [domainname], [domaindir], [nmtype]) 39

40 Check Status 40

41 Check Status Reachable weblogic.nodemanager.nmconnectexception javax.net.ssl.sslhandshakeexception 41

42 Starting Administration Server 42

43 Starting Managed Server 43

44 Starting a Server, some Reminders through WLST: nmstart Startup arguments are retrieved from Administration Server If startup.properties exists, that superseeds whatever is configured in WebLogic CrashRecoveryEnabled and DomainsDirRemoteSharingEnabled influence boot sequence 44

45 Check Server Status nmserverstatus Node Manager checks: server_name.lck server_name.pid server_name.state 45

46 Shut down Server 46

47 Shutdown Server, some Reminders nmkill No such thing as a graceful shutdown from Node Manager 47

48 This is all you need to know about WebLogic s Node Manager 48

49 Sources of Information Node Manager Administrator's Guide for Oracle WebLogic Server (E / E ) ssl_for_weblogic_server_11g 49

50 Questions? 50