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".
  • Upgrading & Reinstalling EP
    using the configuration utility After verifying that the newest version of Enfold Proxy works uninstall the earlier versions of EP on the live machine Via command line on the live machine turn off IIS services iisreset exe stop Install the latest version of Enfold Proxy onto the same machine as the live server Running the install withat will uninstall the previous EP version Via command line on the live machine turn on IIS services iisreset exe start Second Method Install on the production machine Saves Time Useful for Simple configurations Copy your original eep ini file into a safe place Via command line turn off IIS services iisreset exe stop Install EP Via command line turn on IIS services iisreset exe start Move your original eep ini file back to the Enfold Proxy install directory where it was originally The first method is safest and recommended But if you are already sure your proxy definitions worked before and not doing any special out of the ordinary customizations see reasons for editing the configuration file manually then the second method will usually suffice Previous versions of EP used different terminology and sometimes asked users to configure EP by editing the eep ini file For Version 4 onward Enfold recommends that users configure EP by using the configuration utility instead of hand editing the eep ini file This prevents editing errors and ensures that changes are propagated successfully to Microsoft s Internet Information Services IIS Importing eep ini files from an earlier version of EP to the latest version should generally be safe especially if you generated the file completely from the configuration utility instead of hand editing it If for some reason the settings from your existing eep ini do not work the Enfold Proxy configuration utility will start even though some of the proxy definitions won t be active To see which of your proxy definitions is not functioning run the check utility Another idea is to delete the eep ini file causing problems it will be autogenerated after the configuration tool is restarted and start again from scratch adding one proxy definition at a time Should I restart or reboot IIS when upgrading It is not necessary to reboot the server machine on which IIS runs when upgrading Enfold Proxy All you need to do is to restart the IIS services on your server machine via the command line When upgrading Enfold strongly recommends that you stop and restart the IIS services by running these commands Run iisreset exe stop Run the upgrade install with the Enfold Proxy exe file Run iisreset exe start It is true that IIS 6 and IIS 7 have options in the GUI to restart the IIS server or a IIS website But the best practice is not to use these options and instead start stop services via the command line on Windows When you turn off IIS using the GUI you may in fact be leaving certain IIS services running By running the

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


  • Vista Compatibility
    Services Application Development Features ISAPI Extensions World Wide Web Services Application Development Features ISAPI Filters World Wide Web Services Security Basic Authentication This must be checked if you are using single signon with NTLM World Wide Web Services Security Windows Authentication This must be checked if you are using single signon with NTLM NTLM Single Sign on is a feature which lets Plone authenticate using Active Directory You need to configure Plone to support NTLM either with an addon or a customization in the ZMI If you are not using NTLM you don t need to enable Basic Authentication or Windows Authentication After you make these changes press OK Vista will provide a dialog saying Please wait while the features are configured After a minute or so this dialog will close and EP will be installed See also Installing Enfold Proxy and Upgrading Enfold Proxy Internet Explorer 7 on Vista and Windows Authentication This applies only to sites run by Enfold Proxy and Enfold Server with NTLM Authentication Logged in domain users on a Vista machine SP 1 may experience browser problems on IE 7 with automatic login This issue does not affect NTLM authentication on Firefox If this problem occurs domain users on Vista SP 1 may need to change some settings on IE 7 In the advanced tab browsers in the authenticated domain need to uncheck the option labeled Enable Integrated Windows authentication Note that you still need to keep the option in Security Settings for Automatic Login with current user and password for NTLM to work Editing Config Files in Vista Vista s security model is intended to prevent the user from accidentally writing editing system or configuration files The Encontrol configuration utility will automatically prompt for the necessary elevation of privileges but if you wish to edit this file by hand you will need to do so from a process that is already elevated ie started with Run as Administrator see the Vista documentation about how to do that 64 Bit Issues Enfold Proxy runs as a native 64 bit application on Vista and has better performance than the 32 bit Vista version of Enfold Proxy Generally there are no incompatibility issues Downgrading 64 bit IIS to 32 bit IIS IIS 7 and Enfold Proxy run as native 64 bit applications so Enfold Proxy contains full support for 64 bit IIS Occasionally a need may arise to make 64 bit IIS 7 to run in 32 mode instead of 64 bit mode This can happen for example if you are already using ISAPI filters that need to run in 32 bit mode in this case it would make sense to make IIS 7 run in 32 bit mode Note This method for downgrading 64 bit IIS works only on IIS 7 It does not work on IIS 6 The steps are pretty simple Open IIS Click Application Pools Right click DefaultAppPool Choose Advanced Options A big properties dialog will open On the General Section where the

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

  • Server 2008 Installation
    the Server Manager Start Administrative Tools Server Manager Be sure that the Web Server IIS role appears underneath the Roles section If it is not there you will need to add this role Consult the Server 2008 documentation for how to do that Follow the instructions for how to install IIS 7 Note you may be prompted to insert your installation DVD Add Role Services If you are installing IIS 7 from the Add Roles Wizard this will be the third screen Here are the options you should enable Note that after you make changes you will need to restart IIS Management Tools IIS6 Management Capability IIS Metabase capability Management Tools IIS6 Management Capability IIS WMI capability Application Development Features ISAPI Extensions Security Basic Authentication This must be checked if your Plone site will use single sign on with NTLM Security Windows Authentication This must be checked if your Plone site will use single sign on with NTLM If IIS 7 is already installed you will need to enable several role services not normally enabled by default in IIS 7 on Server 2008 Follow the same steps as above Instead of being prompted to install IIS 7 you will instead need to Add Role Services mentioned above To do this click on the Add Role Services which will be to the right of the role service listing You may need to scroll down a bit After installing IIS you can install EP Depending on the version you installed the path for the logs and executables will be either C Program Files x86 Enfold Proxy if you are installing the 32 bit version C Program Files Enfold Proxy if you are installing the 64 bit version Different appearance behavior Every time you launch the Enfold Proxy configuration utility Server 2008 will

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

  • Quick Start
    launch the graphical controller though 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 Plone 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 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 save to have

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

  • Adding a Proxy Definition
    serve Plone content 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 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 zope conf file 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 Typically the port settings should look like this HTTP Port 80 disabled Management Port 8080 Enabled FTP Port 21 Disabled Webdav Port 8280 Enabled ZEO Server localhost port 9999 Restart any Zope client s whose zope conf you have modified 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 Default Web Site which uses

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

  • Creating a Plone Site
    one or more Plone sites Typically after initial installation you can view application root by going to http localhost 8080 manage To find the management port for your Zope Client 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 Plone is initially installed you will see an object called Plone at the application root i e http localhost 8080 Plone To create another

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

  • Linking Plone with WWW
    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 Plone 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 create a proxy definition in Enfold Proxy Make sure

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

  • Troubleshooting
    generic Zope page and not the Enfold or Plone home page That usually means that Virtual Host root hasn t been set correctly Have you set any includes in your Proxy Definition Specifying any kind of include will hide your entire site except that which you explicitly allow As an alternative consider using an exclude instead or adding enough statements and or directory paths to encompass ordinary HTTP requests Are components of your Plone site not available or is the styling layout absent That can mean that an include in your proxy definition is preventing certain content from being accessed To fix this try to use an include regex See includes regex Is 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 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 currently use port 80 now Generally when you are using EP you will want to disable port 80 in Plone 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 Plone you will disable the HTTP Port 80 If you have multiple Zope clients in Plone 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

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



  •