Node Manager
Node Manager is a WebLogic Server Utility.
* It will used to start or stop the Administration and managed server by remotely.
* It will monitor the health of an instance of WebLogic Server and automatically restart if it fails.
* Runs a separate process on the same machines as instance of WebLogic Server.
* It can be set as operating system service to start automatically when a system is rebooted.
Traditional model of Node Manager:
Starting process of Node Manager
Some of the import files under Node Manager home directory:
* nodemanager.properties : Define a configuration setting for a Java based Node Manager processes.
* nodemanger.domains : Define a domains which node manager needs to control
* nodemanager.log : It is used by node manager to logging of process.
* nm_password.properties : Stores the encrypted Node Manager username/password that the Node manager client uses to authenticate itself to Node manager.
* boot.properties : It is created by Node Manager to hold a server's encrypted credentials
* startup.properties : It will record the server startup and health monitoring
* servername.lck, servername.pid, servername.state : These files are used by Node Manager to track the server status.
* servername.out : It is a log file for a server started by Node Manager that contains stdout and stderr messages generated by that server.
Deploying the Application into WebLogic server
Software life cycle of WebLogic server:
Type of Java EE deployments:
* It is an XML file packaged within deployment that set properties of the application.
* Each Java EE deployment has a standard and WebLogic specific deployment descriptors.
Application Load and Street testing:
* Load testing measures performance for a system at different level of concurrent request loads.
* Stress testing will be caring a system limit test.
Load testing tools:
* JMeter
* HP LoadRunner
* Oracle Load Testing
* Grinder
The Grinder Architecture Overview:
Major cause of Performance issue:
No comments:
Post a Comment