Def of WSADMIN : It is an interface to websphere that allows commands to modify the runtime environment.
TYPES OF WSADMIN ROLES :
1) Install or uninstall applications
2) Modify an existing application
3) Start or stop servers
4) Initiate node synchronization
5) Create new servers, clusters, virtual hosts, etc.
WSADMIN OPTIONS :
-help and -? : Provides syntax help
a) -C : ---> Designates to run a single command.
-----> Multiple -c options can exist on the command line.
-------> If you invoke the wsadmin tool with the -c option, any changes that you make to the configuration will be saved automatically.
--------> If you make configuration changes and you are not using the -c option, you must use the Savecommand of the AdminConfig object to save the changes.
b) -f : Designates a script to run.
Only one -f option can exist on the command line.
C) -javaoption : Specifies a valid Java standard or a non-standard option.
Multiple -javaoption options can exist on the command line.
e.g., -javaoption -Xmx1024m [to define max heap size of the JVM ]
D) -lang : Specifies the language of the script file, the command, or an interactive shell.
The options for the -langargument include: jacland jython
E) -conntype : Specifies the type of connection to use.
Possible types include: SOAP, RMI, and NONE.
Use the -conntype NONE option to run in local mode.
F) -port : Specify a port to be used by the connector.
The default wsadmin.properties file located in the properties directory of each Websphere Application Server profile provides a value in the port property to connect to the local server.
G) -user or -username : Specify a user name to be used by the connector to connect to the server if security is enabled in the server.
H) -password : Specify a password to be used by the connector to connect to the server if security is enabled in the server.
RESPONSIBILITIES OF WASADMIN:
STEP1 : Start and Stop of Application Servers.
STEP2 : Experience in Installation,Configuration,Deployments on WEBSPHERE APPLICATION SERVER
STEP3 : Experience in deploying EAR,WAR,JAR files on WebSphere.
STEP4 : Federated Multiple Nodes to DMGR.
STEP5 : Experience in setting up of nodes, DataSources, VirtualHosts.
STEP6 : Implemented using HORIZONTAL AND VERTICAL CLUSTERS.
STEP7 : Fine tuned LoadBalancing with Server Weights.
STEP8 : Configured and enabled GLOBAL SECURITY System.
STEP9 : Configured websphere resources including JDBC Providers, JDBC DataSources, Connection Pooling.
0 comments:
Post a Comment