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".
  • Quick Start
    the Enfold Proxy Configuration Utility icon at any time This can be found in the start menu under Enfold Proxy When starting the controller for the first time there will be no proxy definitions See How to create a proxy definition Therefore you will need to create one For this example we will use originalfunsite but you can use any name After you press Save you should see the originalfunsite proxy definition appear underneath the Proxy category When you click on that the right panel will show the Basic tab This actually is the tab you will be using most often The other listings on the right under Proxy are previously configured proxy definitions If this is your first proxy definition you will see only originalfunsite Next go to the Site tab and associate your proxy definition with the IIS Site In this case the IIS site for www originalfunsite com is called Default Web Server If you have Enfold Server or any Plone site installed on the same machine with the default settings Enfold Proxy will be in effect Important Note This is not a typical or ideal scenario In most cases Enfold Proxy should reside on a separate machine from Enfold Server or Plone To verify that everything works go to www originalfunsite com You should see the Plone site being proxied to the IIS site For more information see Linking Plone with your website troubleshooting checklist common tasks in Enfold Proxy or the FAQ There are three main settings the path on the IIS site where you want Plone to appear the location of the Plone site in its database the Plone instance or instances you wish to proxy by address and port You may click on the more links for detailed explanations of the fields Click

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


  • Adding a Proxy Definition
    www funsite1 com payroll could be used to serve a java servlet you added inside IIS www funsite1 com media could be used to serve videos from a media server you added to IIS When should you NOT create a proxy definition Exactly one proxy definition should correspond to one IIS site You should not need a second proxy definition to point to the same IIS site Having problems Check the troubleshooting checklist or the common tasks in Enfold Proxy or the FAQ For this example we will create a simple proxy definition use Enfold Proxy to map a Plone site to the host http www originalfunsite com Things to do before Creating a Proxy Definition Configure your first IIS host Verify that your IIS host resolves correctly Make sure Plone or Enfold Server is running correctly Creating a Proxy Definition for your IIS Host After you have verified that your host or domain resolves correctly within a browser you can now add a proxy definition to link this host to a Plone site Open the Enfold Server Configuration Utility to do this Start All Programs Enfold Server Enfold Server Configuration Utility Modify write down the management port number for this Zope client Note Each Zope client must have a unique management port number If not then the Check Utility will show an error Disable the HTTP port usually port 80 for the Zope client Your ultimate goal is for Enfold Proxy to listen to port 80 requests to this IIS site and to communicate with the Zope client via port 8080 Here is a screenshot of typical settings for your Zope client in Enfold Server Restart any Zope client s you have modified by choosing the Start Stop option on the left panel Open the EP Configuration Tool Click the folder on the left panel Proxies Choose Add a Proxy Definition Give your proxy definition any name you want Adjust the basic settings if necessary By default the new host comes with the most common defaults Local host Virtual host root Plone These settings will cause the root of your URL to go to the Plone site automatically created within your Zope client The Plone site object should be visible inside the Zope Management Interface ZMI Change these values when necessary You can verify the value for Virtual host root by logging into the ZMI application root and verifying that a folder corresponds to this value already exists For more see Using the ZMI Add the Virtual Host that corresponds to your management port of your Zope client The virtual host can be an IP address or a resolvable host Examples 127 0 0 1 8080 192 168 1 150 8080 localhost 8080 In your Proxy Definition select the Site tab on the top When you come to that screen you will see a dropdown screen for the Site screen Choose the IIS site which is serving the host domain you will be using For this we shall use

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

  • Creating a Plone Site
    initial installation you can view application root by going to http localhost 8080 manage You can find the management port for your Zope Client Enfold Server Open Enfold Server Configuration Utility Start All Programs Enfold Server Enfold Server Configuration Utility Expand the settings for the Zope client you are using if more than one Click on Ports in Use Note the number corresponding to the Management Port default is 8080 and be sure it is enabled Plone generic Open the zope conf file under Plone install directory Client etc zope conf The port number will be listed on a line such as this define ZOPE MANAGEZODB PORT 8080 The other context for viewing the ZMI is specific to a single Plone site You can access it from Plone s control panel From this context you are able to change the settings only for one Plone site and not the others How do you know if the ZMI web page is application root or a ZMI specific to a Plone site These signs will indicate you are looking at application root when you type in the host port number i e http localhost 8080 you see the generic Zope page usually when you append the word manage to the URL i e http localhost 8080 manage you will see a two panel interface with Control Panel appearing at or near the top This will not appear in the context of an individual Plone site you will not see various objects named portal this only appears in the context of the Plone site s ZMI Adding another Plone Site using the ZMI Requirement You must be in the application root of your ZMI and not within the context of another Plone site For this example application root will be at http localhost 8080 One common reason for accessing the Application root of your ZMI is to add a Plone site or even to delete one When Enfold Server is initially installed you will see an object called Plone at the application root i e http localhost 8080 Plone To create another Plone site you need to add a new Plone Site object Use the dropdown menu to Add a New Plone site Give it a unique id not Plone for example For this example give it the id Plone2 Check the application root of your ZMI to make sure the object called Plone2 appears Verify that you can access the new Plone site by going to http localhost 8080 Plone2 You should see a generic Plone site here Note If you go to the URL for this site it will look like a generic Plone site and not include the customized bundle of Enfold products When you first install Enfold Server the default Plone instance will include these customizations Plone sites which are created later will not include these products unless you manually add them You can easily add these Enfold specific products by going to the Plone Control Panel usually http

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

  • Linking Plone with WWW
    security point of view you might want to remove this listing and include only one row with the values indicated above But you can keep it if you wish www originalfunsite com to receive all unspecified host requests to port 80 In general though to minimize the possibility of port conflicts you should specify only one host header per IIS site Next you need to verify that this IIS host resolves correctly in your browser Important Note If your version of IIS doesn t allow you to create multiple IIS sites and you need to configure multiple domains you will need to do this differently See Multiple Domains with only one IIS site Verifying that your IIS Host resolves correctly Before you can add a proxy definition you need to make sure you have a host or domain and that your machine is configured to resolve it properly inside your browser Depending on your environment you can accomplish this in one of two ways Configure your DNS Server s to resolve www originalfunsite com You may have to contact your site administrator to do this To verify that your DNS server can correctly resolve this host open a command window and type nslookup www originalfunsite com For testing purposes only If you don t have easy access to a DNS Server you can fool your local machine into thinking that the local machine is the correct name resolution for www originalfunsite com Edit this file on your test machine C WINDOWS system32 drivers etc hosts You will need to be administrator If IIS is on 192 168 1 150 add this line 192 168 1 150 www originalfunsite com if your browser is on a different machine or 127 0 0 1 www originalfunsite com if your browser is on the same machine as Enfold Server and Proxy After completing either A or B open your browser to www originalfunsite com If you cannot access anything you may need to restart the IIS site Right click Default Web Site Stop and right click Default Web Site again and choose Start If it still does not work verify that the directory path is correct and that IIS has permission to read it Generally C Inetpub wwwroot should work or any directory created underneath that You might need to create a sample index html file inside this directory to view Tip If you are still having trouble viewing a web page within IIS go to IIS right click on the IIS on the left panel and select Properties Select Home Properties Tab and check Directory Browsing You can turn this on when testing but keep this setting switched off again for a real site If you still don t see a directory index page that means IIS doesn t have the right file directory permissions to access the home directory Consult your IIS documentation for how to fix that After verifying that you can test a domain in the browser you can

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

  • Troubleshooting
    your Virtual Hosts value in the correct format It must include the port number and not include the http www Acceptable examples 192 168 1 150 8080 localhost 8080 www testidiot com 80 iissite 8090 Are you using Simple rewrite mode for a Plone site All proxy definitions for Plone sites must use VHM mode Are you using Enfold Server AND using Windows authentication BUT NOT Cookie Authentication or Trusted Proxy Authentication The Authentication Profile needs to include Trusted Proxy authentication or Cookie Authentication for EP to do any proxying See http www enfoldsystems com Products Server Documentation ActiveDirectory for more information See also this diagram about using NTLM Authentication with Active Directory Are you doing Load Balancing and have you manually started and or stopped Zope clients recently Occasionally IIS may need to be restarted to take into account the changed state of Zope clients This is highly unusual Are people using Safari browser seeing error messages when they are attempting NTLM Single Signon There are IIS issues with Safari connecting to Plone through IIS with Single Signon NTLM This is not an Enfold Proxy problem but a problem with the Safari browser Workarounds have been suggested but Enfold recommends that Safari not be used if your users are connecting with NTLM If you are not using single signon then Safari will work fine See the NTLM Troubleshooting Checklist at http www enfoldsystems com software server docs 4 0 troubleshooting ad html troubleshooting checklist for windows single sign on IIS Configuration problems Common Symptoms Error Messages are from IIS not from Enfold or Plone No error page showing up at all IIS site is shown as stopped Bad Request Invalid Hostname This Virtual Directory does not allow contents to be listed IIS shows an error message indicating a port conflict The page must be viewed over a secure channel general erratic IIS behavior You are experiencing login or authentication problems and the resulting page from a failure does not come from Plone or Zope Things to check Have you installed IIS recently for the first time Some users report that for fresh installs of IIS you need to restart Windows before installing EP Have you verified that IIS is running Enfold Proxy won t work at all until you are sure IIS is running A sign that an IIS site is not running is that you will see a crossed out red circle over the Site icon Normally just restarting the IIS will resolve the problem if IIS is improperly configured you may need to resolve that first before you can start using Enfold Proxy Have you verified that the host or domain resolves correctly Here s how to solve name resolution problems if you type ping www originalfunsite do you receive a response if you type nslookup www originalfunsite on the command line do you receive a response valid only when it has been entered on your DNS server Does Plone or Enfold Server currently use port 80 now Generally when you are using EP you will want to disable port 80 in Enfold Server and enable port 80 in IIS In other words IIS will receive port 80 requests and forward them to EP which will forward them to Zope clients via the client s management port usually 8080 So in Enfold Server you will disable the HTTP Port 80 If you have multiple Zope clients in Enfold Server make sure all of the clients have disabled port 80 Is another web server or application using port 80 The IIS needs to have exclusive use of this port Occasionally another application will use this port You can verify that port 80 is available by trying telnet localhost 80 Does each IIS site have one host header declared Although IIS sites are fully capable of accepting requests for more than one hosts or domains this causes problems for your proxy definitions Does the IIS site you are using have the correct Host Header Value such as localhost corresponding exactly to the URL you are trying to access http localhost If you forget to add a host header to your IIS site to be used for Plone IIS might default to another website with different authentication Does more than one IIS site use the same host headers and or port numbers These conflicts will cause web sites to be unable to start Have you verified that the IIS domain root document directory in Windows Explorer actually exists and is accessible If not then your Windows permissions for that directory might be set incorrectly Go to IIS right click web site name Go to Home directory tab Does the local path actually exist on the file system If no you might need to create a directory or sample web page Is Read checked here For testing only you might also enable Directory browsing On the Documents tab have you specified the default content page correctly in most cases it should be index html or index htm This doesn t affect Plone or Enfold Proxy in any way but it useful for troubleshooting IIS Go to IIS right click Site name go to Directory Security tab Have the permissions been set correctly You might wish to uncheck permissions temporarily for testing purpose only Does the browser require you to use HTTPS to access the site That means your IIS is configured to require HTTPS If you right click the IIS site and choose Director Security Secure Communications Edit you might notice that Require Secure Channel is checked Unchecking this might solve this problem See also Security Concerns and SSL Have you modified the identity of your IIS worker processes or Application Pool Changing these settings could potentially affect the performance or reliability of Enfold Proxy You should try to use the default settings when possible For more information see http www isapirewrite com docs security Are you experiencing problems or unexpected behavior with users trying to sign on Are users using

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

  • Reference
    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 select artist td

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

  • Managing Multiple Hosts
    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 Plone

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

  • Integrating Non-Plone Content
    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 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

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



  •