Guru Of Geeks

The following terms describe elements in WebSphere Application Server configurations: cell The administrative domain that a Deployment Manager manages. A cell is a logical grouping of nodes that enables common administative activities in a WebSphere Application Server distributed environment. A cell can have one or many clusters. node A node is a logical group of one or more application servers on a physical computer. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP address. application server The application server is the primary component of WebSphere. The server runs a Java virtual machine, providing the runtime environment for the application's code. The application server provides containers that specialize in enabling the execution of specific Java application components. Network Deployment Manager The administrative...

Quick post… If you are not familiar with WebSphere at first you might get confused with its concepts: cell, deployment manager, node, node agent, cluster, server, … First of all, lets start with the concept of a Cell: A Cell is a virtual unit that is built of a Deployment Manager and one or more nodes. I guess a picture will help making things clearer: WebSphere Cell But still there are a few concepts that need to be explained. The next obvious one is the Deployment Manager. The Deployment Manager is a process (in fact it is an special WebSphere instance) responsible for managing the installation and maintenance of Applications, Connection Pools and other resources related to a J2EE environment. It is also responsible for centralizing user repositories for application and also for WebSphere authentication and authorization. The Deployment Manager communicates with the Nodes through another special WebSphere process, the Node Agent. The Node is another v...

GRANT ALL PRIVILEGES ON *.* TO 'root' @ '%' IDENTIFIED BY 'Pa55w0rd' WITH GRANT OPTION ;

There's two steps in that process: a) Grant privileges. As root user execute: GRANT ALL PRIVILEGES ON *.* TO 'root' @ '%' IDENTIFIED BY 'password' ; b) bind to all addresses: The easiest way is to comment out the line in your my.cnf file: # bind-address = 127.0.0.1 and restart mysql service mysql restart By default it binds only to localhost, but if you comment the line it binds to all interfaces it finds. Commenting out the line is equivalent to bind-address=* . To check where mysql service has binded execute as root: netstat - tupan | grep mysql ​​