Websphere HTTP plugin failover in a clustered environment
We have a Websphere 6.1 vertical cluster i.e 2 JVMs in a single physical machine with IBM HTTP server.
How to Analyze JVM logs (SystemOut.log, SystemErr.log & startServer.log)
Websphere writes formatted text log messages to SystemOut.log,SystemErr.log & startServer.log files. Read more…
Diagnosing IBM Websphere Service logs
The IBM service log
The IBM service log, referred to as the service log, is a binary file. It contains information written to System.out by the Application Server run time as well as special messages that contain extended service information. This extended service information has been useful to IBM WebSphere Service teams in solving complex problems. IBM has now created additional tools to decipher these binary service logs, such as the Log Analyzer in Application Server. However, it is best to solve as many problems as possible during the development phase, before deploying to a production Application Server environment.
Setting the session timeout for the administrative console
1. Edit the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file in a text editor.
2. Locate the xml statement <tuningParams xmi:id=”TuningParams_1088453565469″ maxInMemorySessionCount=”1000″ allowOverflow=”true” writeFrequency=”TIME_BASED_WRITE” writeInterval=”10″ writeContents=”ONLY_UPDATED_ATTRIBUTES” invalidationTimeout=”30″>
Websphere File Synchronization Service: Replicate changes from Dmgr to NodeAgent
In a distributed server environment, the administrative console is located in the deployment manager server, dmgr. In this case, the administrative console provides centralized administration of multiple nodes. Configuration changes are made to the master repository and pushed to the local repositories on the nodes by the deployment manager. In order for the administrative console to run, the dmgr server must be running. In order for the changes to the master repository to be pushed to the nodes, the node agents must also be running.
Logging commands executed through Websphere(WAS) Admin Console
Use this feature if you want to log or capture “wsadmin” commands excuted by WAS internally. It can be very useful when you want to automate your tasks and don’t know exact wsadmin syntaxes to use.
Where is Websphere profile config stored
Use profileRegistry.xml file to locate name of profiles on system. File normally located at /opt/IBM/WebSphere/AppServer/properties
Read more…
Websphere Routing a Request using Plugin-cfg.xml
The Web Server plug-in uses an XML configuration file to determine whether a request is for the Web Server of the application server. When a request reaches the Web Server, the URL is compared to those managed by the plug-in. If a match is found, the plug-in configuration file contains the information needed to forward the request to the web container using the web container inbound chain.
How to Install SSL certificate under Websphere/Http server
1. Navigate to the /bin-directory of your IHS-Installation $IHS_HOME
2. execute ./ikeyman to open Key Management Tool
Websphere Application Server Clusters
Clusters
Logical grouping of application servers is called clusters. Instead of installing an application on individual server we can install it on a cluster to automatically deploy application on each application cluster.
Websphere Silent Installation
Websphere Silent installation consists oof 3 stages. You need to successfully complete all of these.
- Base installation
- IBM Http server
- Plugin Software installation
Websphere : Federation of the WAS nodes
By federating nodes to the deployment manager we can administer all the application servers through one deployment manager console.
Websphere : Deploy an Application using GUI Deployment Manager (Dmgr)
Go to console Enterprise Applications -> install -> location of the application
Websphere Application Server Security
Authentication – is the act of proving a certain user’s identity.
Authorization – is a process of granting access or giving permission to a user to perform certain tasks.
Websphere Clustering and Work Load Management
Work Load Management [WLM]: WLM means share the requests across multiple application servers.
Websphere Application Server Logs
JVM Logs:The JVM logs are created by redirecting the System.out and System.err streams of the JVM to independent log files. The System.out log is used to monitor the health of the running application server. The System.err log contains exception stack trace information that is used to perform problem analysis. One set of JVM logs exists for each application server and all of its applications. JVM logs are also created for the deployment manager and each node manager
Read more…
Tweet