Why use a Netscaler to change the response of the XML broker
Citrix NetScaler is a versatile tool to distribute and modify datastreams very generic and powerful way. Especially in enterprise environments, where the protocols are often proprietary, allowing customers to add a little extra piece of plumbing protocols can not control, without the need to hire developers. This blog is about the application of such additional small piece of plumbing to one of its own Citrix protocols, the one who speaks with StoreFront XMLBroker instances of XenApp or XenDesktop. Obviously, this is not officially condoned or supported by Citrix (XMLBroker The room, the room is just regular NetScaler configuration), but it solves a problem that is usually resolved by other means unsupported such as changes in WebInterface.
Citrix NetScaler MPX / VPX is able to rewrite an HTTP response with a very powerful motor. If you set up a store to use a vserver Netscaler load balanced for XML Broker you can change the answer to any request Storefront origin of any type of receiver or device type or OS (Windows, Mac, iPhone, iPad , Android, ...). He also works for Legacy to Receiver StoreFront.
If you want to hide application WebInterface please follow the instructions on http://support.citrix.com/article/CTX123969
Storefront communication with XML Broker
When a StoreFront will list the applications available to you XA / XD environment, it sends an XML request to the XML Broker servers defined in the config (also called Delivery Controller).
a sample XML broker request sent by a Storefront server to obtain the list of applications:
The server then responds XML broker with a list of applications and provides basic fields of all published applications
a sample XML broker response to a request for StoreFront :.
Each published application and desktop is defined by an XML block bounded by the tag
Ie:
application filtering based on the Application Name field in XenApp
the Application Name field specified in a XenApp published application is the "inname" tag d a broker response xml xml.
you have to create a strategy by applying rewriting (or desktop) you want to hide
Step 1 :. Configure XML Broker Vserver your Netscaler
Step 2: Create Rewrite action with the following parameters
| Name | xml_broker_desktop |
| like | delete_all |
| term choose target reference text | HTTP.RES.BODY (50000) |
| Pattern | |
| Options | EXTEND (40300) .REGEX_SELECT (re # s * |
Step 3: Create Rewrite policy
| name | xml_broker_desktop_pol |
| action | action name defined in step 2, namely: xml_broker_desktop |
| term | HTTP.RES.BODY (150) .CONTAINS ( " |
Step 4: Assign the policy to Rewrite vserver XML Broker LB
- Open the vserver
- Go to policies / Rewrite / Answer
- Click "Insert Policy"
- Specify the name of the policy created in step 3
-. a "Goto phrase" select NEXT or END depend on whether this policy is the last or not
Step 5: (Optional) Update the Control your Storefront to use this XML broker vserver
Step 6 :. Enjoy !!!
NOTES
- the regular expression configured in Step 2 for the Rewrite action is to select all starting with: 
and ending with 
- Caring for the value set for the EXTEND command. The first value (40) defines the number of bytes to extend the selection before the pattern matching set.
In this example, the value must be greater than 37.
The second value (300) is the number of bytes from the model .
In this example, the value must be greater than 242.
If you set too high, you can include the previous Application Definition or next as in this example:
- a EXTEND (xx, 515) or greater value will include Desktop_application_name aND Notepad in action delete_all.
Warnings
This method of rewriting package is presented "as is" and are not supported by Citrix Technical Support. I recommend you have a second parallel configured XML Broker vserver in the same Netscaler to troubleshoot your platform access XenApp / XenDesktop.
0 Komentar