Que 1-- What is the Exact work of XML broker???

Citrix XML Service and the Citrix XML Broker The Citrix XML Broker functions as an intermediary between the other servers in the farm and the Web Interface. When a user authenticates to the Web Interface, the XML Broker:Receives the users credentials from the Web Interface and queries the server farm for a list of published applications that the user has permission to access. The XML Broker retrieves this application set from the Independent Management Architecture (IMA) system and returns it to the Web Interface. Upon receiving the users request to launch an application, the broker locates the servers in the farm that host this application and identifies which of these is the optimal server to service this connection based on several factors. The XML Broker returns the address of this server to the Web Interface. The XML Broker is a function of the Citrix XML Service. By default, the XML Service is installed on every server during XenApp Setup. However, only the XML Service on the server specified in the Web Interface functions as the broker. (The XML Service on other farm servers is still running but is not used for servicing end-user connections.) In a small farm, the XML Broker is typically designated on a server dedicated to several infrastructure functions. In a large farm, the XML Broker might be configured on one or more dedicated servers. The XML Broker is sometimes referred to as a Citrix XML Server or the Citrix XML Service. For clarity, the term XML Broker is used to refer to when the XML Service functions as the intermediary between the Web Interface and the IMA service, regardless of whether it is hosted on a dedicated server or collocated with other infrastructure functions. This illustration uses a large farm to show how the Web Interface and the XML Broker work together. (1) The user connects to the Web Interface through the XenApp plug-in or a Web browser; (2) the Web Interface contacts the XML Broker to determine which applications are available for this user; (3) the XML Broker queries the IMA service for this information and returns the results to the Web Interface; (4) the Web Interface displays the available applications to the user either through a Web page or by placing shortcuts directly on the users computer.
This illustration uses a large farm to show how the Web Interface and the XML Broker work together. (1) The user connects to the Web Interface through the XenApp plug-in or a Web browser; (2) the Web Interface contacts the XML Broker to determine which applications are available for this user; (3) the XML Broker queries the IMA service for this information and returns the results to the Web Interface; (4) the Web Interface displays the available applications to the user either through a Web page or by placing shortcuts directly on the users computer.

Que2-- After login through WI, user is able to see application but while Clicking on that application, that is not launching ??? Priority Ans 1. The path of that published application is not set up correctly in Citrix farm and it is not hitting the .exe of that published application thats why user is unable to launch application Priority Ans2. Check whether user have correct persmissions on that application in AD/Citrix farm. IF user is not able to view application after login through WI then what the issue ????
Priority 1. User dont have permissions on that application that s why they are not able to see icon of that application.

Que-3 -- What is thin Protocol in Citrix..and also what is thin and thick Application ????

Thin protocol is basically develop for thin clients systems(systems dont have hard disk) and it is very light weight & thin protocol. Eg. ICA thin protocol developed which is very thin and light weight and it is only used for thin clients systems.

Thick client applications are your traditional applications. These are the software that you go out and buy from the store then download onto your computer from a CD like Quicken or MS Office. Such applications are then stored on your personal computers hard drive taking up memory and runs completely on that computers resources. This also means that the security of the application is dependent on the local computer, which in most cases has a limited amount of users and access. These apps, because they are stored on a persons local computer, are always readily available as long as there are no issues with the computer housing them. This also means that the only way to us such an application from a different computer is that it has to be loaded on that machine, and an individual would have to have there information on some kind of portable media so that it can be uploaded an reused. That means these kinds of apps are not very portable and in most cases can not be used with a mobile device. Thin client applications are web applications. These are applications that can be accessed from the internet with out the use of a CD or any other type of media. These applications are purchased by paying for an account or subscription to a website which gives you access to the app, as opposed to purchasing it at a store. With the application itself being used from the web it dose not take up any space on the local computer, but still uses other resources from the local computer. Instead the app resides on a server somewhere that can be accessed by many users at any time, which means a need for greater security measures to be taken. Also thin client apps can be accessed by any computer or mobile device that has internet access making them very portable. With that said thin apps are only as fast and reliable as the users internet connection and the producers server. This also means that if either is not working correctly for any reason then the application could be unreachable or extremely slow.

Que--4 - Difference between CITRIX PS 4.5 and Xenapps 5.0.

Que- 5- User applications are too slow then what will we do on server side?? Answer: 1. We have to logged on that particular server on which user is facing slowness in application and check below things: 1. In task manager check the application tab may be there is any service which is using high CPU usage and causing slowness. (Solution: Kill that service and restart it again and keep monitoring that server.(eg Symantec, IMA citrix protocol sometimes these services take 100% usage) 2. Check the sufficient disk space of that server in C: drive and D: drive both. 3. May be there are many user sessions are disconnected but not cleared from citrix farm and consuming citrix license for each disconnected session and thats why new user is not able to connect to that server if license is not freed up by cleared up those disconnected user sessions manually.