a resource for builders of the web
  • FTP Improvements Available for Testing June 6, 2025
    ​Starting with the annual baseline release in December 2025, the content of PubMed data distributed via FTP will be generated using the same technology as the PubMed website and E-utilities API.To help users prepare for this transition, a test FTP site is available now with daily update files generated by the new process.
  • Changes to Email Feature May 30, 2025
    On or after July 28​, PubMed will reintroduce the ability to customize subject lines and body text when emailing search results or citations. With this update, the email feature will also require My NCBI login, and PubMed emails will only be sent to the email address associated with the My NCBI account.  
  • Latest Literature on PubMed homepage will be replaced with PubMed Updates March 5, 2025
    The Latest Literature section on the PubMed homepage will be removed and replaced with a PubMed Updates section on or after March 31, 2025. The new section will include PubMed development updates and other PubMed-related highlights.​
  • PubMed 2025 Baseline Released January 14, 2025
    ​The National Library of Medicine (NLM) has released the 2025 production year PubMed baseline files.​ Please refer to the linked article for more information. ​
  • Pharmacological Action Term Mapping December 2, 2024
    ​Searches in All Fields [all] for terms matching a Pharmacological Action now follow PubMed syntax rules for Automatic Term Mapping (ATM).​
  • Filters Interface Improvements October 22, 2024
    ​The PubMed filters interface on the search results page has been updated to provide a more intuitive, user-friendly experience. ​
  • Related Citation Links in Search Results June 17, 2024
    The four PubMed comment correction types​​ labeled in search results now also include a link to the related citation in the summary display: Update in, Retraction in, Retracted and republished in, Corrected and republished in.​​
  • Wildcard Search Improvements June 3, 2024
    ​PubMed search syntax now supports expanded use of the asterisk (*) wildcard character. Previously, a wildcard could only be used for truncation at the end of a term or phrase to search for alternate endings. With this update, wildcards can be used in the middle of a term or phrase, and multiple wildcards can be […]
  • Usability improvement: Links now underlined on mouseover February 12, 2024
    Links on PubMed are now underlined on mouseover. This update is based on recommendations from the U.S. Web Design System (USWDS)​.
  • PubMed 2024 Baseline Released and DTD updated December 20, 2023
    The National Library of Medicine (NLM) has released the 2024 production year PubMed Baseline files and the first set of 2024 PubMed Update files have been posted. Regular daily updates have resumed.The updated 2024 PubMed DTD is available here​.

Citrix Netscaler 10 Understanding Basic Web Site/Application Configuration



Configuring Citrix Netscaler can be very daunting, there are so many options and getting started with VIPs, SNIPs, MIPs can be confusing.  That said configuring web applications and sites for access is actually straightforward once the Netscaler is networked.   You have two basic components and they are both managed through Load Balancing, whether you have one web server or 50 load balancing allows you to link end users to Netscaler and Netscaler to you web servers.  I prefer to start with the resources that are already being accessed, the back-end in this configuration is one or more web servers, if it’s one you aren’t actually “load balancing” but the process is virtually identical.

1) ADD WEB SERVER:  Click Load Balancing > Servers   Add the server by IP address, this is not a VIP, but the actual IP the web server can be reached at.

2) ADD SERVICE:  Click Load Balancing > Service Here you configure the service of the back end server, in the case of HTTP/S all you are doing is specifying what protocol and port to use, so in the simplest case you select HTTP from the list.  Yu then link this HTTP designation to the server and you have a service for that server on HTTP.

NOTE: This is where you add a monitor, in this scenario a monitor allows Netscaler to test it’s own access to the back end.  If you just select HTTP then a simple http request will be made to your service root to check that it responds.   OOTB this monitor fires very frequently, every 3 seconds or so.  The status of your service and virtual server will be based on the monitor.

3)  ADD VIRTUAL SERVER:  Click Load Balancing > Virtual Servers.  To set-up the route to Netscaler for end-users and link it to the Service you created.   Create a Virtual Server in Load Balancing section and assign a VIP to it (Netscaler Virtual IP…provided by your networking team).  Typically the VIP will have the desired end-user accessible DNS entry pointing to it as well, unless it’s being accessed by IP.  You will add  the VIP as provided and name it in the top section in Load Balancing.  Once you add the name and VIP you just select the checkbox for the named Service you created, it is listed in the section below by name, you may have to toggle to show Services instead of Service Groups.

4) TEST THE SET-UP:  Now when an end user browses for the DNS entry which points to the Netscaler VIP they will be routed through Netscaler to your back-end HTTP Service on port 80.  If your back-end server does not have the DNS entry configured in host headers and there is more than one web site bound to http port 80 you have to add the host header.

 

No Comments Yet

Leave a Reply