WebSphere Application Server important Log Files?

Basically, the files are divided into these below parts

>>> XML Configuration Files
>>> Property files
>>> Log Files

WebSphere stores its configuration to set of XML files. When we use the Admin console to configure WebSphere, certain XML files are updated internally.

CELL-scope:-
---------------

• admin-authz.xml
Contains the roles set for administration of the Admin console.
/appsrv01/config/cells//

• profileRegistry.xml
Contains a list of profiles and profile configuration data

• resources.xml
Defines operating cell scope environmental resources, including JDBC, JMS, JavaMail, URL end point configuration, and so on.

• security.xml
Contains security data , including all user ID and password information.

• virtualhosts.xml
Contains virtual host and Multipurpose Internet Mail Extensions (MIME)-type configurations.

• variables.xml
Contains cell level WebSphere variables

• wimconfig.xml
Contains the federated repository configurations for global security
/config/cells//wim/config/

NODE-scope

• namestore.xml
Provides persistent JNDI namespace binding data

• resources.xml
Defines node scope environmental resources, including JDBC, JMS, JavaMail, URL end point configuration, and so on

• serverindex.xml
Specifies all the ports used by servers on this node

• variables.xml
Contains node level WebSphere variables

SERVER-scope:--
--------------------

• resources.xml
Contains the configuration of resources, such as, JDBC, JMS, JavaMail, and URL end points at server scope

• server.xml
Contains application server configuration data

• variables.xml
Contains server level variables

properties files:-
-------------------

If the global security is enabled WebSphere Application Server cell, you need to manually enter the username and password every time you run the wsadmin tool. By editing the sas.client.props and the soap.client.props files, you can specify the username and password you have configured for global security so you are not prompted to enter the username and password every time you run administrative scripts.

soap.client.props file
com.ibm.SOAP.securityEnabled=
com.ibm.SOAP.loginUserid=
com.ibm.SOAP.loginPassword=
Optionally, set the following property:
com.ibm.SOAP.loginSource=none

sas.client.props file
com.ibm.CORBA.loginUserid=
com.ibm.CORBA.loginPassword=
Also, set the following property:
com.ibm.CORBA.loginSource=properties


Log Files:--
-------------

JVM logs
native_stderr.log,native_stdout.log
stdout and stderr streams are redirected to log files at application server startup, which contain text written to the stdout and stderr streams by native modules, that is, Linux Modules, and so on. In normal error-free operations, these logs files are typically empty.

startServer.log
It is created in your logs directory when the server starts up. This log is very useful to determine JVM parameters used in the start-up process, the server’s process id, and also the date and time in which the server was started. If there are errors experienced during the start-up (for example, security configuration errors where the application server cannot start), then log information will exist for problem determination.

stopServer.log
when server was stopped via a command line, the log will be written to this. If the server has trouble stopping, then Java stack traces will be written to the log which can be used in determining why a given application server failed to stop.

SystemErr.log
contains Java exceptions and stack traces. An empty SystemErr.log file does not necessarily indicate a successfully running application server JVM. You may need to consult the other logs in this directory.

SystemOut.log
This log file contains messages as generated by the JVM during runtime. Some messages are informational, some are warnings or status updates. Applications can be configured to write to the log and so it is very common for the SystemOut.log to be your first port of call in application debugging.

.pid
contains the process id of the server. In Linux, this is the actual process id assigned to the JVM process.

FFDC logs
FFDC directory contains detailed logs of exceptions found during the runtime of the WebSphere Application Server. Can be found at WAS_ROOT/profiles/logs/ffdc

What is mean of fix pack in websphere? how do you apply a fix pack?

WebSphere product update is done in terms of “Fix pack” and “interim fix” .Fix packs are the standard maintenance delivery vehicle for Version
6.1. WebSphere Application Server V6.1 provides fix packs containing cumulative fixes
that are updated regularly, roughly at interval of 12 weeks. This provides a consistent
maintenance approach you can follow as you manage your products. Each fix pack
delivery can consist of multiple fix packs for the following components:
− Application Server
− Application Client
− Web server plug-ins
− IBM HTTP Server
− Java SDK
IBM’s product update terminology has changed from earlier releases of
WebSphere.

Type of update:
---------------
1. Release

Definition:
---------
1.This is the term used by WebSphere Development
and Support for a “major” version of WebSphere.
The first two digits of the product version number
identify the release (e.g., 6.1).


2. Fix pack

Definition:
---------
2. This is the term now used to describe a product
update that in fact includes only defect fixes. (The
previous term for this type of update was cumulative
fix.) The version number’s fourth digit identifies a
fix pack (e.g., 6.1.0.10, 6.1.0.11).

3. Fix and Interiam Fix
Definition:
---------
3. These two terms indicate a temporary or emergency
product update focused on a specific defect. (This
type of update used to be referred to as an
emergency fix or efix.) A fix isn’t identified by
digits in the product version number. You’ll find
fixes listed in the output of the versionInfo utility


Depending on the type of update, the acceptance process starts in development
and moves through different test environments to staging and finally to production.
Acceptance of releases should start with the development team environments because
releases contains major product enhancements and changes. Acceptance of fix packs
tends to start in the test team environments. If a test team discovers some incompatibility
between an application and a fix pack, the development team should get involved. Once
the product update has been run through all the testing stages, the operations team can be
confident that the applications will run properly on the updated version of WebSphere
Application Server.
You should install the product updates referred to as fixes (or interim fixes or
efixes) only if your development or test team has determined that a fix is needed in order
for applications running in a given environment to operate properly. IBM intends fixes as
emergency corrections to defective product behavior. If the applications you’re
developing, testing, or running aren’t experiencing the defect addressed by a fix, don’t
install the fix.

how to federate the node to deployment manager in websphere?

>> by using addNode.bat command u can federate the node to the dmgr.
> please follow the below command for the node federation.

command:
---------
C:\Program Files\IBM\WebSphere\AppServer\bin>addNode.bat localhost 8879 -profileName AppSrv02 -username wasadmin -password wasadmin

>>after the command the below sripts is available.

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv02\logs\addNode.log
ADMU0128I: Starting tool with the AppSrv02 profile
CWPKI0308I: Adding signer alias "CN=localhost, O=IBM, C=US" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
BF:3F:09:3F:DD:2A:34:77:0E:50:0B:71:49:63:BB:A4:B2:CA:1B:3F
CWPKI0308I: Adding signer alias "dummyclientsigner" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
0B:3F:C9:E0:70:54:58:F7:FD:81:80:70:83:A6:D0:92:38:7A:54:CD
CWPKI0308I: Adding signer alias "dummyserversigner" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
FB:38:FE:E6:CF:89:BA:01:67:8F:C2:30:74:84:E2:40:2C:B4:B5:65
ADMU0001I: Begin federation of node vision2kNode01 with Deployment Manager at localhost:8879.
ADMU0001I: Begin federation of node vision2kNode01 with Deployment Manager at localhost:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: localhost:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU2010I: Stopping all server processes for node vision2kNode01
ADMU0512I: Server server1 cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: vision2kNode01
ADMU0014I: Adding node vision2kNode01 configuration to cell: localhostCell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: vision2kNode01
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
4100
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: server1
ADMU9990I:
ADMU0300I: The node vision2kNode01 was successfully added to the localhostCell01 cell.
ADMU9990I:
ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone localhostCell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the localhostCell01 Deployment Manager
with values from the old cell-level documents.
ADMU9990I:
ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the localhostCell01 cell using wsadmin $AdminApp or the Administrative Console.
ADMU9990I:
ADMU0003I: Node vision2kNode01 has been successfully federated.

C:\Program Files\IBM\WebSphere\AppServer\bin>

How to create the profiles in websphere on windows?

we have 2 ways for creating the profiles on windows:

1) manageprofiles.bat available at websphere installation path location.by using this command u can create a profile.
please find the below complete path

C:\Program Files\IBM\WebSphere\AppServer\bin>manageprofiles.bat -create -templatePath "C:\Program Files\IBM\WebSphere\AppServer\profileTemplates\default" -profileName "AppSrv02" -profilePath "C:\Program Files\IBM\WebSphere\AppServer\profiles"

now u can get the AppSrv02 profile.
>
>
>
> templatePath Details:
1. Default: application server profile
2. dmgr: Deployement manager profile
3. managed: custom profile
4. cell: deployment manager+federateapplication server


2) go to the below path and client the 'pmt.bat'.

C:\Program Files\IBM\WebSphere\AppServer\bin\ProfileManagement

How to check Websphere Application Server status in window/linix?

u need go to the bin directory of websphere installation path. here u can find out the 'serverStatus.bat' on Windows and serverStatus.sh' on unix
please execute the below command for finding out the server status on websphere application server.

C:\Program Files\IBM\WebSphere\AppServer\bin>serverStatus.bat -all
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\serverStatus.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: dmgr
ADMU0508I: The Deployment Manager "dmgr" is STARTED

C:\Program Files\IBM\WebSphere\AppServer\bin>

How to Start the Websphere Applisation Server in Windows?

WebSphere Installation path:
---------------------------
C:\Documents and Settings\Leena>cd C:\Program Files\IBM\WebSphere\AppServer\bin

Deployment Manager start:
-------------------------

C:\Program Files\IBM\WebSphere\AppServer\bin>startManager.bat -profileName Dmgr01
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\startServer.log
ADMU3027E: An instance of the server may already be running: dmgr


Node Agent start:
-----------------

C:\Program Files\IBM\WebSphere\AppServer\bin>startNode.bat -profileName AppSrv01

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent\startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 3916


Application Server start:
------------------------

C:\Program Files\IBM\WebSphere\AppServer\bin>startServer.bat -profileName AppSrv01 server1
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 3908

C:\Program Files\IBM\WebSphere\AppServer\bin>

*****************************************************************

Websphere6.1 Information

www.websphere-zone.blogspot.com