...
Required Configuration Changes
- Modify the idp.war file.
Extract the war file (<shibboleth_home/war/idp.war) to a directory (i.e. (<shibboleth_home>/war/idp). And open the directory <shibboleth_home>/war/idp/WEB-INF. In this directory you will need to create a file named "weblogic.xml". The content of this file is:Code Block xml xml <?xml version="1.0" encoding="UTF-8"?> <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd"> <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> </container-descriptor> </weblogic-web-app>
- Endorse Xerces and Xalan:
- Copy the .jar files included in the IdP source
endorsed
directory into$JAVA_HOME/jre/lib/ext
directory. The XML libraries provided with Weblogic are not compatible with Shibboleth, but there is no harm endorsing the Shibboleth libraries by the JDK. - Create an XML Registry in Weblogic as defined below
- Copy the .jar files included in the IdP source
- Add the following parameters to the JAVA_OPTS environment variable (all ### is the amount of memory in megabytes to allow for the option):
- -Xmx###m - this is the maximum amount of memory that Weblogic may use, at least 512M is recommended
- -XX:MaxPermSize=###m - (Sun JVM specific option) the maximum amount of memory allowed for the permanent generation object space. Set this to half of the maximum memory (specified above).
- Enable SSL on Weblogic; this is required as some operations require the use of SSL
- Edit the Server settings using Weblogic administration console for the Weblogic server running the IDP
- Enable SSL on the desired port (by default 7002) and make sure the Keystores contains the correct information; by default this is the Demo Identity and Trust store
...