| 10 | | 1 Stop your IdP (or stop the servlet container, eg. Tomcat), and stop Apache httpd too, if you're using it. |
| 11 | | Make a back-up copy of your $IDP_HOME/conf directory (recent versions of the IdP installer should not overwrite your config unless you answer "yes" in point 7 below). |
| 12 | | Download the .zip archive of the most recent Shibboleth IdP 2.x and unzip the archive. Do not use the .msi installer for upgrading an existing IdP 2.x installation. |
| 13 | | If you don't already have one, it's a good idea to create a source directory specifically for storing the IdP unzipped archives. This makes it easier to manage any additional libraries or branding you might have. |
| 14 | | Copy your additional libraries (e.g. JDBC drivers or plugins and/or filters, like uApprove) into the lib/ directory (i.e. lib/ inside the source directory where you unzipped the archive; not $IDP_HOME/lib/, which is inside the deployment directory). |
| 15 | | If using User Password authentication, reapply any branding you have made: ie. copy your customised login.jsp etc. pages into the /src/main/webapp subdirectory of the unzipped archive. |
| 16 | | Run the install script from the command line in the top-level directory of the unzipped archive (install.sh on Unix machines, install.bat on Windows). |
| 17 | | Provide the location of your $IDP_HOME directory. |
| 18 | | Answer "no" when the installer asks if you wish to overwrite your configuration files. |
| 19 | | If your config files have been overwritten (eg. due to human error) copy the files from your back-up back in to your $IDP_HOME/conf directory. |
| 20 | | Start your IdP (or the servlet container), and start Apache httpd too, if you're using it. |
| | 10 | 1. Stop your IdP (or stop the servlet container, eg. Tomcat), and stop Apache httpd too, if you're using it. |
| | 11 | 2. Make a back-up copy of your $IDP_HOME/conf directory (recent versions of the IdP installer should not overwrite your config unless you answer "yes" in point 7 below). |
| | 12 | 3. Download the .zip archive of the most recent Shibboleth IdP 2.x and unzip the archive. Do not use the .msi installer for upgrading an existing IdP 2.x installation. |
| | 13 | 4. if you don't already have one, it's a good idea to create a source directory specifically for storing the IdP unzipped archives. This makes it easier to manage any additional libraries or branding you might have. |
| | 14 | 5. Copy your additional libraries (e.g. JDBC drivers or plugins and/or filters, like uApprove) into the lib/ directory (i.e. lib/ inside the source directory where you unzipped the archive; not $IDP_HOME/lib/, which is inside the deployment directory). |
| | 15 | 6. If using User Password authentication, reapply any branding you have made: ie. copy your customised login.jsp etc. pages into the /src/main/webapp subdirectory of the unzipped archive. |
| | 16 | 7. Run the install script from the command line in the top-level directory of the unzipped archive (install.sh on Unix machines, install.bat on Windows). |
| | 17 | * Provide the location of your $IDP_HOME directory. |
| | 18 | * Answer "no" when the installer asks if you wish to overwrite your configuration files. |
| | 19 | 8. If your config files have been overwritten (eg. due to human error) copy the files from your back-up back in to your $IDP_HOME/conf directory. |
| | 20 | 9. Start your IdP (or the servlet container), and start Apache httpd too, if you're using it. |
| | 21 | |
| | 22 | |
| | 23 | === UA localization === |
| | 24 | |
