archive-com.com » COM » E » ENFOLDSYSTEMS.COM

Total: 720

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • EP Reference
    are mostly plain HTML which you can customize as you see fit However you can also include special strings will be replaced with more details about the error String Will be replaced with errnum s The internal error number msg s The internal error message func s When available the part of the program that generated the error XSLT Examples Sample XML File Script This is a small python script that outputs an XML file within Plone It is used in the xslt caching example Create a python script in the python and paste the following into the body request container REQUEST response request RESPONSE response setHeader XSLTStyleSheet container absolute url cdcatalog xsl response setHeader Content Type text xml print xml version 1 0 encoding ISO 8859 1 catalog cd title Empire Burlesque title artist Bob Dylan artist country USA country company Columbia company price 10 90 price year 1985 year cd cd title Hide your heart title artist Bonnie Tyler artist country UK country company CBS Records company price 9 90 price year 1988 year cd cd title Greatest Hits title artist Dolly Parton artist country USA country company RCA company price 9 90 price year 1982 year cd catalog return printed Sample XSLT File for XSLT Caching Example Here is a sample XSLT file for the XSLT caching example xml version 1 0 encoding ISO 8859 1 xsl stylesheet version 1 0 xmlns xsl http www w3 org 1999 XSL Transform xsl output method html version 1 0 encoding UTF 8 indent yes xsl template match html body h2 My CD Collection h2 table border 1 tr bgcolor 9acd32 th align left Title th th align left Artist th tr xsl for each select catalog cd tr td xsl value of select title td td xsl value of

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/reference.html (2016-02-11)
    Open archived version from archive


  • Managing Multiple Hosts
    from the eep ini file located in the Enfold Proxy directory and from the IIS management console Read more about unique identifier IDs and how to confirm that Enfold Proxy is reading them correctly near the bottom Creating a Second Internet Host and Proxy Definition For this example http www originalsite com is the first domain and http www funsite1 com is the second domain you will use Configure your first IIS host in the normal way See Configuring your first IIS host Verify that the first host resolves correctly See Verifying that the IIS Host resolves correctly Use IIS to create a new IIS site Right click on Web Sites within the IIS Manager and select New Web Site If using IIS 7 right click Sites and select Add Web Site Go through the IIS Site Creation wizard In this example the new site will be called funsite1 Notes you will need to indicate a directory for the site root You can simply use the default site root for IIS C Inetpub wwwroot or create one underneath this directory i e C Inetpub wwwroot The most important thing here is that the directory allows read access for the IIS user Enter Port Number 80 Host Header values www funsite1 com IP Address All Unassigned and leave allow anonymous access enabled Restart the Web Site You will not need to restart IIS itself In IIS 6 right click the site name funsite1 in the IIS Manager and choose Start or Restart In IIS 7 the Start Restart option is located on the right panel in the IIS Manager Highlight the funsite1 site in the middle panel and select the Start Restart option Test that your domain works in IIS See Verifying that the IIS Host resolves correctly Create a new

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/multiplesites.html (2016-02-11)
    Open archived version from archive

  • Integrating Non-Plone Content
    names listed must not include any slashes only the name portion must be listed As a special case you may specify a forward slash to indicate the root of the site Note that specifying the root will not automatically specify any default pages in that root such as index html they need to be explicitly specified if required For example if your Local Host Root is Plone and you specify excludes as MyDir then any requests to Plone MyDir Plone MyDir my file Plone mydir etc will be excluded i e ignored by the proxy and handed by IIS but requests to Plone MyDir2 Plone Other MyDir etc will all be processed normally In this example requests to MyDir would not be processed by EP at all as it falls outside our Local Host Root If you require more flexibility for example exclude MyDir wherever it appears in the URL see excludes regex below Using Auto Excludes to Maintaining Existing URLs The main function of auto excludes is to maintain existing URLs from IIS after you add a Plone site Suppose you want Plone to handle most of a domain but you have legacy content still at the root that need to work Auto excludes lets EP check first if IIS content already exists for that URL if it does IIS will serve it otherwise Plone Enfold will handle it Note Be careful that existing legacy IIS content is not preventing people from accessing important parts of the Plone site To set up an Auto Exclude select your proxy definition and choose the Excludes tab If you use Auto Excludes you have to choose what kinds of web content will cause IIS to ignore Plone If you want an Auto Exclude more than likely you will want to choose All The dropdown box for Auto exclude shows these options Choosing All will check to see if there are any virtual directories file system directories or files for a URL under the IIS site If yes then the IIS site will handle it If no then Enfold Plone will handle it This is probably the most common choice if you plan to set up auto excludes Choosing webdirs will only exclude virtual directories specified within the IIS site A virtual directory does not physically exist in the file system underneath the IIS root Instead it may refer to an application or a directory in another location analogous to a Windows short cut Choosing fsdir will only exclude file directories on the file system existing underneath the root for the IIS site These directories actually appear in Windows Explorer and not merely IIS Choosing files will tell IIS to serve files inside IIS document root instead of Plone whenever such a file or files exist Choosing None will deactivate all auto excludes and just cause Enfold Proxy to assume that all HTTP requests should be handled by Plone If you are using auto excludes you do not need to enter anything under Local Excludes although you can After you press Save the changes should take effect immediately If not you may need to restart your IIS site excludes regex excludes regex is very similar to excludes except for two critical differences Each entry specifies a regular expression rather than a literal string Each regular expression is matched against the entire child URL being matched not just the first portion The case of the URL is ignored when matching this is the same behavior as excludes For example if you wished to exclude all jpg files from the plone site thereby causing all requests for such images to be handled by IIS itself you could specify jpg which will match any URL ending in jpg If you only wanted to exclude jpg files from the root of the proxied site you could specify jpg where the second regex fails to match if a slash character appears in the requested URL Note The ordering of the proxy definitions in the ep ini file does not affect how or whether EP will process them You can optionally use excludes regex for more fine grained control over which proxy definition acts upon a particular URL Please refer to the Python regular expressions reference for information on regular expression patterns Using Includes The main rationale for using Includes is to hide most of a Plone site except for one or more selected directories or one or more URLs This can be useful if a certain directory is a domain is using a Plone application for a site which is otherwise almost completely non Plone Keep in mind that you may be able to do this more simply by modifying the Virtual host root and Local host root in your proxy definition For example suppose you have an IIS site and you have a directory in Plone http 192 168 1 150 8080 Plone salesdirectory which you wish to be called up whenever someone types www originalfunsite com salesdirectory Rather than putting salesdirectory in EP s include field for your proxy definition it s more direct to try this instead Local Host Root salesdirectory Virtual Host Root Plone salesdirectory Virtual Hosts 192 168 1 150 8080 includes and includes regex By default if you leave Includes and includes regex blank Enfold Proxy will serve the entire site in a normal way Once you specify anything in the Includes the proxy definition will exclude everything except the directories and files which you have explicitly declared on this tab This means that in most cases you will not use both include settings and exclude settings at the same time in a proxy definition If your requirement was to proxy an entire site apart from a few predefined URLs i e all requests go to Plone except for a few predefined IIS applications you would specify these IIS application roots in excludes and this is the reason that case is ignored for excludes IIS itself ignores the case If your requirement

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/integrating.html (2016-02-11)
    Open archived version from archive

  • Load Balancing
    are running Zope Plone regardless of whether they are running Linux Windows OS X etc Note Before you can load balance you should verify that your Zope clients can be load balanced Adding or Subtracting Load Balancing Clients After you create a proxy definition for your host you can add load balancing clients with one step add another entry in the Virtual host field This Virtual host field is located on the Basic tab of your proxy definition The balancing tab of your proxy definition contains additional options related to load balancing Here are examples of Virtual Hosts to include in your proxy definition on the Basic tab All formats listed here are acceptable localhost 8080 localhost 8090 192 168 1 150 8080 192 168 1 151 8080 www enfoldsystems com 8080 Notes In most cases these URLs will be a Zope client Omit the http prefix Always include the port number You can use IP addresses and or host names Load balancing will not work unless you have 2 or more Virtual hosts listed here After you push save load balancing should work immediately To remove a client from load balancing delete the appropriate line in the Virtual Host field Even though load balancing provides a kind of insurance policy against failures you still need a monitoring tool like Big Brother to make sure individual machines are online A load balanced cluster might have four virtual hosts Zope clients and still work if three of them go offline But if you are never notified about this occurrence you would be at risk if the fourth goes offline also Configure Load Balancing Options The Balancing tab of your proxy definition contains several options to configure for load balancing Verify that your Zope Clients can be load balanced Enfold Proxy has the ability to balance requests from multiple Zope clients These Zope clients can exist on the same machine or be spread out among several machines However load balancing assumes that each Zope client is using the same Zope object database ZODB and the same Zope mount point That means that the zope conf file for each Zope client must be configured to reference the same ZEO server and file storage location regardless of whether the Zope clients are located on one machine or several machines Before you add a Zope client to load balancing you must verify two things First verify that the Zope client can be accessed directly by typing the IP address management port If you can type http localhost 8080 in your browser or the equivalent that is sufficient You should also verify that all Zope clients have identical ZEO servers mount point s and ZODB file By default all Zope clients installed by Plone use one mount point and the same file storage location Here s some basic steps for doing this verification Compare Zope conf files and make sure that the mount directive is identical to the other Zope client s If these Zope clients

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/loadbalancing.html (2016-02-11)
    Open archived version from archive

  • Request Schedulers
    in the vh host section rules Defines a list of filtering rules Enfold Proxy uses the specified scheduler only if all of the rules are matched The Python code corresponding to this logic is as follows regexp1 match environ HEADER1 and regexp2 match environ HEADER2 HEADER1 and HEADER2 are keys in the environment dictionary logged to the proxy log file at the debug log level Associating Schedulers with Hosts After defining one or more schedulers you can also define which schedulers to use for a particular host in the eep ini file like so host website vh host localhost 8080 localhost 8081 schedulers sched1 sched2 In this example you must have previously defined schedulers sched1 and sched2 per the previous section of this document If Enfold Proxy s log level is set to debug it will log the request environment as well as additional scheduling information to the proxy log file SCHEDULER sched1 DOES NOT MATCH on criteria REMOTE ADDR 127 0 0 1 for content html or SCHEDULER sched1 MATCH on criteria REMOTE ADDR 127 0 0 1 for news html Example Here s an example configuration that uses ZEO clients localhost 8081 and localhost 8082 for requests originating from our local network 192 168 1 xx and ZEO clients localhost 8083 for GoogleBot scheduler local vh host localhost 8081 localhost 8082 scheduler leastconns rules REMOTE ADDR 192 168 1 scheduler googlebot vh host localhost 8083 scheduler leastconns rules HTTP USER AGENT Googlebot host site vh host localhost 8080 schedulers local googlebot Handling 500 Errors A proxy definition can also specify some default actions to take when handling 500 errors from the Plone Server You configure these directly in the eep ini file To add an option just add one of these lines to your proxy definition in the

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/schedulers.html (2016-02-11)
    Open archived version from archive

  • Security Concerns
    VPN software to log in remotely to their office machine and access the ZMI from there by typing a private host or I P address along with the management port number http mymachine 8080 Setting up ZMI Access on a Separate Host It is theoretically possible to configure a separate proxy definition and separate IIS site to allow public access to the Zope Management Interface ZMI login screen on port 80 But it is not recommended The best way to login to Plone is to login directly to port 8080 i e http 192 168 1 150 8080 instead of proxying it to port 80 Setting up HTTPS Login for Login Only Setting up HTTPS for your entire site is not practical because it slows IIS performance However you could set up HTTPS to manage initial user login That requires three things First you need to set HTTPS and SSL certificates for your specific IIS site This task lies outside the scope of this document but here is an excellent tutorial for how to configure SSL for IIS http www petri co il configure ssl on your website with iis htm Second you need to verify that the IIS site handles both port 80 and port 443 See the same tutorial Third you need to set up a mechanism in Plone to switch to SSL when logging in and back to non SSL after receiving an authenticated cookie To do this see the Plone how to guide about secure logins http plone org documentation how to secure login without plain text passwords Using NTLM LDAP for User Login One benefit of using Plone and Enfold Proxy on a Windows platform is having the ability to authenticate automatically with Windows domains with the NTLM authentication protocol Once again Enfold Proxy does

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/security.html (2016-02-11)
    Open archived version from archive

  • Monitoring EP
    open the EP configuration tool select Check option on the left panel and choose the Check button Using eep check command line utility eep check exe is the command line version of the Check utility It is located in the Enfold Proxy installation directory Note that this is a console program so you should execute this program from a command prompt rather than by double clicking in explorer The command line version of this utility eep check utility is identical to the utility in the GUI If you run this command via command line you can append a show excludes argument to the command If you do that the print will print not only the normal output but also a list of all items found by this auto exclude processing See Using Excludes The eep check utility can be executed with a show config argument which will print the current configuration values being used by EP The values printed are after any default values and variable substitutions have been applied it shows exactly how configuration file appears to EP For example assuming your configuration file is the complex example above eep check would print eep check show config Effective eep ini configuration options virtualdir plone lines omitted host 1 vh hosts localhost 8080 vh root PloneSite1 lh root PloneSite1 lh server 192 168 0 1 lh port includes lines omitted Worthy of note All configuration sections and values are printed even when they do not appear in the INI file as seen by the options section Although the DEFAULT section is not shown the entries specified in it are reflected in our proxy definition Using and Customizing Your Logs See Using logs to analyze common problems Tip Use a free log monitoring tool like Bare Tail http baremetalsoft com baretail

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/monitor.html (2016-02-11)
    Open archived version from archive

  • Reporting Problems
    the log The default level is WARNING meaning that all warnings and error conditions detected by EP are written to the log Many issues you encounter will be detected by EP as an error so the log level will not need to be changed just open the log file and look for any error messages Issues such as an invalid integer in the configuration are an obvious error so will be written to the log Many other problems are also obviously an error so the logs will have their information However there will sometimes be more subtle issues you need to diagnose For example if a remote server is not available EP will display an error page with details of the error but will not log a WARNING message to the log nothing is wrong with EP in this situation just with the remote server In such cases EP writes an entry to the log at level INFO Adjusting the log level to INFO will display all such conditions information which may be valuable in tracking down external problems The log level DEBUG will yield lots of information many lines for each successful and failed request While this information is designed to allow the developers to diagnose issues with EP it may be of benefit to anyone trying to diagnose strange interactions in the field The log level is adjusted in the proxy log section of the config file by setting log level to a level name eg info or number Using Logs to view Headers The Proxy log level has a special log level called HEADERS If this log level is enabled every request and response will have their headers logged as shown below HEADERS is between DEBUG and URLS if you set the log level to DEBUG you will also see HEADERS but if you set it to URLS INFO or greater you do not Obviously you shouldn t run production servers at this log level For an explanation about what the various cache control and HTTP headers mean check the Cache Headers Reference The HEADERS log level uses arrows to indicate the direction in which HTTP requests are being handled Headers will be shown with one of 4 prefixes means the incoming request ie from the browser but it has some extra X headers our filter adds before it is logged means the request we make to Zope means the response from Zope back to us means our response to the client browser Below is an example Note Enfold Server referred to a special version of Plone for Windows which Enfold used to offer Incoming client request 2008 09 02 16 20 46 812 proxy HEADERS 968 160 client request VirtualHostBase http localhost 3A80 Plone VirtualHostRoot vh Plone Accept text html application xhtml xml application xml q 0 9 q 0 8 Accept Language en us en q 0 5 Connection keep alive snip some headers User Agent Mozilla 5 0 Windows U Windows NT 5 1

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/usinglogs.html (2016-02-11)
    Open archived version from archive



  •