plugin.cfg.xml parameters

WAS (WebSphere) Plugin Configuration XML (plugin-cfg.xml) Parameters – ConnectTimeout and ServerIOTimeout

July 31, 2007

In this link, you can find out all the available parameters that you can modified / set inplugin-cfg.xml. The 2 parameters that I am interested in, which is related to how long the plugin connects to WebSphere Application Server: ConnectTimeout andServerIOTimeout.

ConnectTimeout identifies how long (in seconds) the plugin will wait to get connect to WebSphere Application Server (WAS). If the plugin waits longer than the value, it will mark the server unavailable.

By default (without the parameter set in the plugin-cfg.xml) or setting the value to 0, it represents a blocking connect, that is, the thread will keep waiting to obtain a connection until the operating system time out the request.

ServerIOTimeout identifies how long (in seconds) the plugin will wait for the server to response to the request. If the plugin waits longer than the value before the response is completed, it will time out.

By default, the plugin uses blocked I/O. So basically it will block wait until TCP connection times out.

Diff betwwn thin And Thick client

Thin Clients
1.Easy to deploy as they require no extra or specialized software installation
2.The data captured is verified by the server.
3.Clients run only and exactly as specified by the server
4.Reduced security threat


Thick Clients
1.More expensive to deploy
2.Data is verified by client and not by server 
3.Can store local files and applications, Reduced server demands
4.Increased security issues

WSAdmin Objects

WSAdmin Objects

The wsadmin command exposes following four objects

1.             AdminControl:The AdminControl scripting object is used for operational control. Itcommunicates with MBeans that represent live objects running a WebSphere server process. It includes commands to query existing running objects and their attributes and invoke operations on the objects.

2.             AdminConfig: The AdminConfig object is used to manage the configurationinformation that is stored in the repository. This object communicates with the WebSphere Application Server configuration service component to make configuration inquires and changes. In a distributed server environment, the AdminConfig commands are available only if a scripting client is connected to the deployment manager. When connected to a node agent or a managed application server, the AdminConfig commands will not be available because the configuration for these server processes are copies of the master configuration that resides in the deployment manager.

3.             AdminApp: The AdminApp object can update application metadata, map virtual hosts to Web modules, and map servers to modules for applications already installed. Changes to an application, such as specifying a library for the application to use or setting session management configuration properties, are performed using the AdminConfig object.

             4.     AdminTask: The AdminTask object is used to access a set of task-oriented administrative commands                     that provide an alternative way to access the configuration commands and the running object management commands. The administrative commands run simple and complex commands. The administrative commands are discovered dynamically when the scripting client is started. The set of available administrative commands depends on the edition of WebSphere Application Server you install. You can use the AdminTask object commands to access these commands

Websphere Questions?

Websphere Questions?

1.what is websphere or Application Server?

2.what is webserver?

3.what is profile and its benefits in websphere?

4.what is deployment manager?

5.what is node agent?

6.what is node?

7.what is vertical and horizontal scaling?

8.what is port no for admin console(HTTP & HTTPS)?

9.what is port no for webcontainer(HTTP & HTTPS)?

10.what is synch node?

11.what is federated node?

12.what is wsadmin?

13.which are the five java objects in wsadmin?

14.how websphere and webserver communicate to each other?

15.how to start & stop application server by command line?

16.what is the log files location in websphere?

17.How will you check that application server is properly started or not?

18.who will start the application server automatically while you trying to stop it?

19.what is the diff in was 5 & was 6?

20.what is the diff between webphere and application server?

21.what is garbase collection?

22.what is thin and thick clinet?

23.what is CA siteminder(SSO)?

24.what is ldap and its port no?

25.what is SSL and its port no?

26.what is load balancer?

27.How application server communicate to database server?

28.what is webserver(http) plug-in and plug in-cfg.xml?

29.what is soap and its port no?

30.what is RMI and its port no?

31.what is UDDI?

32.what is web base application environment?

33.which are the comman HTTP error codes?

34.which are the websphere edge component?

35.which are the application component?

36.what is proxy server and what is diff between farward and reverse proxy?

37.what is hot deployment?

38.what is managed and unmanaged nodes?

39.how IBM http server managed by websphere?

40.what is the long form of XML,EJB,JSP,EAR,J2EE,JVM and HTML?

41.what are the  J2EE roles?

42.what is application serevr toolkit?

43.how will you problem determine in websphere?

44.how will you start dmgr,nodeagent and node,application server by wsadmin?

45.what is the directory structure in was 6?

46.what is workload management and hoe it managed by webserver?

47.how will you do websphere secure?

48.what is client/server computing?

49.what is thread dump and heap dump?

50.how will you create thread dump file?

51.what wstemp directory in was 6.0?

52.what is IP spraying?

53.how will you check if you are not able to access remote server?

54.where the deployment manager resides Inside or outside the cell?

55.what is the websphere architectur?

56.which are the websphere v6.0 packaging?

57.how synchronization done in webshere?

58.how will you check the process in websphere with instances?

59. how will you check the process in webserver with instance count?

60.how will you check the disk space?

61.what is the command for monitoring the serevr?

62.how will you check the ports?

63.how will you check job shedular and schedule the job?

64.how will you check file permission?

65.what is vi editor and how to use vi editor with options?

66.what is ssh and its port no?

67.what is default port no for http and https?

68.what is the command for compress & uncompress the file?

69.what is the diff between http & https?

70.what is the command for archieving the file?

71.which are the log files in websphere?

72.what happened when you delete the .hello file?

73.rm * command delete evrything,will it delete . & .. dir also?

74.what you will do if your log file is increasing and ur partition becomes full?

75.what happened when you delete .hello file?

76.do you know shell scripts?

77.how you will remove a file?

78.i have asterix file how will you delete?

79.how will you remove a *a file?

80.what is admin console secure port no ?

81.what is the https port no?

82.webserver,application server and db server,which sequence you follow for shutdown?

83.how will you check the file type?

84.what is node sync?

85.how is emon?

86.If your customer says my website is opening slowly,what you will do?what will be your answer?

87.whaich file shows port no information?

88.how you will feel about this e-bis profile?

89.how will you check memory in windows machine?

90.which tool you were using for monitoring the system?

91.how will you monitor the sever?

92.how will you check cpu utilization on windows machine?

93.how will you copy the line vi editor?

94.how will you extract the file with tar command?

95.what you will do if you log file is increasing continuously and your partition becomes full?

96.what happened when you delete .hello file?

97.rm * command delete everything will it delete . & .. dir also?

98.do you know shell scripts?

Class Loader

Class Loader !!

Java Class Loader:

Class Loader is a process which enables the Java Virtual Machine (JVM) to load java classes.

Types of Java Class Loader:

·         Bootstrap Class Loader – responsible for loading only the core java libraries like vm.jar,core.jar etc.

·         Extension Class Loader – responsible for loading the code in the extensions directories -<JAVA_HOME>/jre/lib/ext

·         Application Class Loader – responsible for loading the code that is found on java.class.path, which ultimately maps to the system CLASSPATH variable.

WEBSPHERE CLASS LOADER:

Websphere Extensions Class Loader: The Websphere extensions class loader is where Websphere itself is loaded. In WAS6.1, Websphere runtime classes are stored in the <was_home>\plugins directory.

Application Class Loader:EJB modules, utility JARs, resource adapter files, and shared liabries associated with an application are always grouped together into same class loader which is called application class loader. Utility JARs contain code used by both EJBs and servlet. Application class loader can be share by multiple applications (EARs) and also can be unique for each application.

WAR Class Loader:

Every web module comes with their own class loader called WAR class loader which is used to load the contents of the WEB-INF/classes and WEB-INF/lib directories.

If the WAR class loader policy is set to Single class loader for application, the Web module contents are loaded by the application class loader in addition to the EJBs, RARs, utility JARs, and shared libraries

Introduction to WebSphere Plug-in

-Plug-in is a glue between a Web Server and WebSphere
   Application Server
- Plug-in’s primary responsibility is to forward HTTP requests to
   the WebSphere Application Server
- The web server plug-in is developed native C language
- The plug-in code varies slightly depending on the operating
   system (OS) and the Web server being used although its
   operation and functionality remains the same.
- The plug-in code is in the form of a DLL library on Windows®,
    and SO library on Unix® (ie. AIX®, Solaris®, and so on).
- This library resides on the Web server machine and is loaded
    by the Web server startup process


Plug-in is an Agent:
You can think of the WebSphere plug-in as an “agent”
using the HTTP protocol.
redirecting HTTP requests from the WebServer to the application server
As seen in Figure 1, an HTTP request from a Web browser enters the Web server
and is then redirected to the application server.
This redirection is performed by the WebSphere plug-in.

 Plug-in Operation:
-The plug-in “sends” HTTP requests, and acts as an HTTP
  client.
-The application server receives those requests, and is
  therefore an HTTP Server.
- The component inside the application server which does the
  job of an HTTP Server is known as the HttpTransport.
-The HttpTransport of the appserver, listens on specific ports
  for HTTP (ie. 9080) and for HTTPS (ie. 9443).
-If there are multiple application server on the same node,
they must be configured to use unique port numbers.

what is proxy server and what is diff between farward and reverse proxy?

what is proxy server and what is diff between farward and reverse proxy?

In computer networks, a proxy server is a server (a computer system or an application program) which services the requests of its clients by forwarding requests to other servers. A client connects to the proxy server, requesting some service, such as a file, connection, web page, or other resource, available from a different server. The proxy server provides the resource by connecting to the specified server and requesting the service on behalf of the client. A proxy server may optionally alter the client's request or the server's response, and sometimes it may serve the request without contacting the specified server.

- In an enterprise that uses the Internet, a proxy server is a server that acts as an intermediary between a workstation user and the Internet so that the enterprise can ensure security, administrative control, and caching service. A proxy server is associated with or part of a gateway server that separates the enterprise network from the outside network and a firewall server that protects the enterprise network from outside intrusion.

A forward proxy is typically used when you have internal users of your network trying to access external sites. The internal users must configure the client browser to use the proxy to access external sites.
In contrast, a reverse proxy server is typically used to appear as the actual Web server to the client. The reverse proxy server takes all requests, and sends the requests to the content HTTP server. When the proxy server receives a response, it sends the results back to the client as if it were the original server. A reverse proxy is typically used when you want clients to access a server that is behind a firewall