8/11/2019 Key Files in WAS

1/4

Please refer the below to know the key les in WAS.

WebSphere stores its conguration to set of XML les. When we usethe Admin console to congure WebSphere certain XML les areupdated internally.

CELL-scope

! admin-authz.xml"ontains the roles set for administration of the Admin console.#prole$root%&appsr'()&cong&cellscell$name%&

! profleRegistry.xml"ontains a list of proles and prole conguration data

!resources.xml*enes operating cell scope en'ironmental resources including +*,"+MS +a'aMail -L end point conguration and so on.

! security.xml"ontains security data including all user /* and password information.

! virtualhosts.xml"ontains 'irtual host and Multipurpose /nternet Mail 01tensions 2M/M034type congurations.

! variables.xml"ontains cell le'el WebSphere 'ariables

! wimconfg.xml"ontains the federated repository congurations for global security#prole$root%&cong&cellscell$name%&wim&cong&

N!E-scope

8/11/2019 Key Files in WAS

2/4

8/11/2019 Key Files in WAS

3/4

sas.client.props flecom.ibm."6,A.login-serid7com.ibm."6,A.loginPassword7Also set the following property8com.ibm."6,A.loginSource7properties

Log $iles

%#& logs

native_stderr.log,native_stdout.log

stdout and stderr streams are redirected to log les at applicationser'er startup which contain te1t written to the stdout and stderrstreams by nati'e modules that is Linu1 Modules and so on. /n

normal error4free operations these logs les are typically empty.

startServer.log/t is created in your logs directory when the ser'er starts up. 9his log is'ery useful to determine +:M parameters used in the start4up processthe ser'er;s process id and also the date and time in which the ser'erwas started. /f there are errors e1perienced during the start4up 2fore1ample security conguration errors where the application ser'ercannot start3 then log information will e1ist for problem determination.

stopServer.logwhen ser'er was stopped 'ia a command line the log will be written tothis. /f the ser'er has trouble stopping then +a'a stack traces will bewritten to the log which can be used in determining why a gi'enapplication ser'er failed to stop.

SystemErr.logcontains +a'a e1ceptions and stack traces. An empty System0rr.log ledoes not necessarily indicate a successfully running application ser'er

+:M.

8/11/2019 Key Files in WAS

4/4

so it is 'ery common for the System6ut.log to be your rst port of callin application debugging.

.pid

contains the process id of the ser'er. /n Linu1 this is the actual processid assigned to the +:M process.

$$!C logs

==*" directory contains detailed logs of e1ceptions found during theruntime of the WebSphere Application Ser'er. "an be found atWAS$669&proles&logs&>dc