how many ways we can find it ......
we can check in the log.txt in that you can find "instconfsuccefull" message and Even you can check with Installation verification Tool (IVT) also
================================================================
2)what is the scenario where we will go for Appserver profile and what is the scenario where will go for Custom profile and what is the diff b/w appserver profile and custom profile
We would install an Appserver profile if just need a standalone appserver . It has its own JVM and apps could be installed in it.
Anyways we could federate the appserver profile to the Cell whereever we want it in future .
Whereas a custom profile would be an empty profile ( no preinstalled Appservers .. config etc ) which would be federated to the Dmgr Cell and we can then create the Appserver with our own customized settings etc
Differences
Appserver profile --- Is a standalone appserver -- ie server1 is installed by default
Custom profile --- Its an Empty profile
Appserver profile -- It has its own Admin console to manage the server1 and other config
Custom Profile --- As its and empty profile with no appservers it doent have and admin console.
====================================================================
3)Suppose If I forgot my dmgr console username and password . Where I can get those credential details....
The username /password within the WAS are encrypted so i dont thing you can get the old pwd .. there is one thing though
Within the <DMGRPROFILE_HOME>/config/cells/Cellname
Within the <DMGRPROFILE_HOME>/config/cells/Cellname
(or)
In the real env
the user name and password of the dmgr wil be stored in the soap.client.prop file
in the /opt/IBM/WebSphere/AppServer/Profiles/Dm
The user name is not encrypted..and the password only encrypted..you can decode the encrypted password using following url
http://www.sysman.nl/wasdecoder/
or otherwise you can search in the security.xml and there you will find the primayradminID=username and the sample ="password" (encrypted)
if you decode the password you can use the above url.....
=========================================
the user name and password of the dmgr wil be stored in the soap.client.prop file
in the /opt/IBM/WebSphere/AppServer/Profiles/Dm
The user name is not encrypted..and the password only encrypted..you can decode the encrypted password using following url
http://www.sysman.nl/wasdecoder/
or otherwise you can search in the security.xml and there you will find the primayradminID=username and the sample ="password" (encrypted)
if you decode the password you can use the above url.....
=========================================
4)how do we configure the custome registry to the standalone application server...can any one explain me in details
Its very easy to configure custom registry to standalone application server .
1)Create registry files for users and groups
2)Save this in a new folder .
3)open the console and select global security
under registries select custom registry
4)Give the server user id and password (Administrator user name and password)
5)save them and select custom properties and then click on new
6)Configure the userfile name and next give the path of the usersfile
7)similarly configure the groupsfile also.
8) select the authentication mechanisms of ltpa and give some password and confirm password.
9)Then enable gloabal security and disable java 2 security
10) select the ltpa authentication in authentication mechanisnms and custom registry in the registries and then save and restart the server
11)then give any username and password that u had created in the registry.
and next the concept is as same like creating the user and assigning roles to the user and accesing the console
1)Create registry files for users and groups
2)Save this in a new folder .
3)open the console and select global security
under registries select custom registry
4)Give the server user id and password (Administrator user name and password)
5)save them and select custom properties and then click on new
6)Configure the userfile name and next give the path of the usersfile
7)similarly configure the groupsfile also.
8) select the authentication mechanisms of ltpa and give some password and confirm password.
9)Then enable gloabal security and disable java 2 security
10) select the ltpa authentication in authentication mechanisnms and custom registry in the registries and then save and restart the server
11)then give any username and password that u had created in the registry.
and next the concept is as same like creating the user and assigning roles to the user and accesing the console
===========================================
5)does any tell me about wsadmin and the objects in wsadmin script?
Interacting with application server will be done by using administrative clients.
1. Browser based,
2. wsadmin
3. Script Based.
1. A browser based console will be open by using any internet explorer to administrate the appserver.
2. when coming wsadmin, here we have to invoke the wsadmin objects to administrate the appserver.
wsadmin objects are 5 types.
* AdminTask
* AdminControl
* AdminConfig
* AdminApp
* Help.
all these commands will be executed in command in the following location
<INSTALL_ROOT>/bin>wsadmin
3. Script based means we will run JACL/Jython scripts to administrate the appserver.
=================================
6)Using WAS command-line client wsadmin (run with root privileges):
. Open a connection to local WAS in offline mode
wsadmin -conntype NONE
2. Turn off global security
wsadmin> securityoff
3. Save
wsadmin> $AdminConfig save
you login the console now with no password
======================================
7)Policy files
There are 3 different policy files.
1)App.policy : This file contains the entries that are used by the developers to gain the access of any system resource like connecting to printer etc.
2)was.policy : This file contains all the default entries, by which we can access to default system resoureces.
3)Filter.policy ; The first 2 files are used by the developers to gain the access to system resources. The filter.policy file will be used by the was admin to block the accessing of system resources by the developer.
===============================================
8)hat is class loader policy.How many types are there. What is the main use of it?
The class loaders are used to load the class files to the JVM .
1. Browser based,
2. wsadmin
3. Script Based.
1. A browser based console will be open by using any internet explorer to administrate the appserver.
2. when coming wsadmin, here we have to invoke the wsadmin objects to administrate the appserver.
wsadmin objects are 5 types.
* AdminTask
* AdminControl
* AdminConfig
* AdminApp
* Help.
all these commands will be executed in command in the following location
<INSTALL_ROOT>/bin>wsadmin
3. Script based means we will run JACL/Jython scripts to administrate the appserver.
=================================
6)Using WAS command-line client wsadmin (run with root privileges):
. Open a connection to local WAS in offline mode
wsadmin -conntype NONE
2. Turn off global security
wsadmin> securityoff
3. Save
wsadmin> $AdminConfig save
you login the console now with no password
======================================
7)Policy files
There are 3 different policy files.
1)App.policy : This file contains the entries that are used by the developers to gain the access of any system resource like connecting to printer etc.
2)was.policy : This file contains all the default entries, by which we can access to default system resoureces.
3)Filter.policy ; The first 2 files are used by the developers to gain the access to system resources. The filter.policy file will be used by the was admin to block the accessing of system resources by the developer.
===============================================
8)hat is class loader policy.How many types are there. What is the main use of it?
The class loaders are used to load the class files to the JVM .
Parent First , Parent Last are class loader delegation models.these are not class loaders
class loaders in jvm are
1) Boot Strap classloader
2) extension class loader
3) Appplication class loader
1) Boot Strap classloader
2) extension class loader
3) Appplication class loader
=====================================================
9)
9)
No comments:
Post a Comment