Director: Troubleshooting with client-side tools such as Firebug
Sometimes when you're looking at data Director, you may wonder what happens on the bottom and where the data comes from. You can use existing tools to find the same and to resolve issues Director. A tool used by Citrix mostly to solve these is Firebug.
After reading this blog, you will be able to give an answer to the following questions.
1) What is Firebug?
2) How to install Firebug?
3) How to troubleshoot Citrix Director with Firebug?
What is Firebug?
Firebug is an extension or add-on for Mozilla Firefox, Google Chrome and Safari, etc. Internet Explorer, Google Chrome and Apple Safari also comes with an integrated development tool that is also like Firebug and can be used to solve Director. Firebug allows the user to debug and inspect HTML, CSS, the Document Object Model (DOM) and JavaScript while browsing the site. It detects site performance and track cookies and sessions. We will discuss troubleshooting director with Mozilla Firefox, Internet Explorer and Google Chrome only.
How Firebug?
There are two ways to install Firebug on your machine.
1) Open Firefox, go to Tools> Extensions> Get Addons then search Firebug. Now click Install. Restart after installation and you are ready to use Firebug now.
2) You can go to getfirebug.com and click "Install Firebug for Firefox" button.
Internet Explorer, Google Chrome and Apple Safari comes with the integrated development tool that can be opened by pressing the F12 key.
How to solve Director?
1. Using Firefox with Firebug:
After installing Firebug, you will be able to see a gray icon "Firebug" in bar Firefox navigation tools. Click on the icon to start. Or press F12 to start the Firebug.
After starting Firebug, you will be able to see the Firebug toolbar. This bar of tools Firebug is shown below
toolbar Firebug is to have seven panels
Panel Console: .. This panel shows all calls made to the server from the browser. This panel meets most of our target director troubleshoot. So we will discuss this in detail panel. Other panels mainly used by the developer to test the site
HTML Panel: .. This panel shows the HTML code of the web page opened in that the particular browser tab
CSS Group: This panel shows the CSS used in the current web page
panel Script: .. This panel shows all the scripts used in the current web page
DOM panel: This panel list of all DOM objects shows
net panel: .. This panel is used to monitor calls made from the browser to the server
panel cookies :. This panel shows what the different witnesses are set to build trust between frontend and backend for that particular session
now we will discuss steps to follow for troubleshooting Director.
Open Website Manager in Firefox browser. Open the Firebug or by pressing F12 or by clicking the bug in the right side of the browser navigation bar. Then you'll Firebug UI bottom tab manager in the browser. By clicking on the icon in the Firebug pane you'll get "location Firebug UI" option to move this interface. Select the console panel from the Firebug toolbar and select the "All" under the console panel
Panel Console :.
This panel is widely used for troubleshooting Citrix. As soon as you connect to the manager this panel starts to show all calls to the backend manager from the browser. You can see the time taken by the call from to apply to get the answer. You can also see a fair number after the name of the API. This number is an HTTP status code. If the call is followed by the code 0, this means that the call was successfully returned the server response. If code other than 0, it means that the appeal might was failing to get the server response.
The user can see the particular call answer by clicking on this call. The user will see five tabs under this call
heads :. This tab shows the header of this call. This shows biscuit, X-XSRF-Token, Host, content length, etc.
Post : This tab displays the parameters sent to the background. The user must check if the passed parameters are correct or not
Response :. This tab shows the response received from the back-end as plain text.
JSON : This tab displays the received response back end as JSON. The user can check if the values received from backend are correct or not 
Cookies : .. This tab shows the cookies used for making this call
1.1 Troubleshoot a Failed call
Sometimes you see red calls followed by the 500 code in the console panel as shown below in the screenshot. This means that these calls were failed due to some reason. When you double-click such a call you get an error code and details about the failure in response. As shown in the screenshot below GetConnectedSessionData call screen is failing with error code 105.
Error Code 105: DNS server does not try to
so this is the cause of the failure of this call and need. to give the correct name of the DNS server. You can get the error code and look Firebug which means that the error here
2. Using Internet Explorer :.
IE comes with custom construction development tool that can be used to solve Director. Press F12 to launch this tool.
This tool has eight panels, but especially a panel is needed to solve the problems that director is called Network panel. Once any appeals sent from UI to back-end tool to capture.
You can get the detailed view of the call by clicking on the call. Here is the screenshot of the application of this call header. It is as or more than we saw in the previous section.
Here is the screenshot of the request body of the appeal.
Below is the screenshot of the body of the response call.
Here is the screenshot of the time spent by the call to recover the result.
debugging stages of a failure of the call is quite similar to the measures we discussed in the previous section Firefox .
3. Using Google Chrome:
Google Chrome also comes with custom development tool built that can be used to solve Director. Firebug Lite version also available for the Chrome browser that can be used to solve Director. Chrome Version 32.0 and tool build developer is used for all screenshot in this section. Press F12 to launch this tool.
This tool is very similar to the Internet Explorer development tool, except for some changes in the user interface. It also has eight panels but only Network panel is sufficient for troubleshooting director we have in Internet Explorer. Here is the screenshot of this tool with the information of a call header contains.
Here is the screenshot of the request body of the appeal.
Here is the screenshot of the body of the response call.
Here is the screenshot of the time spent by the call to recover the result.
Google Chrome also have the same stages of debugging a failure of the call we discussed in the previous section of Firefox .
All this information can be used to find out what happens to the AC Backend. If an appeal fails, then we can find what is wrong by looking in the error code in response to this call. These tools are also useful to determine if a call is correct in response values, but the user interface shows incorrect behavior to the user.
We hope at this point you have an understanding of exactly how to solve Director in Firefox or Internet Explorer. If you need further information or assistance then please leave your comment or suggestion, we will be happy to hear from you.
0 Komentar