OpenSSO Enterprise server supports Geronimo Application Server 2.1.1 with Tomcat on Solaris systems only.
Modify the /geronimo-tomcat6-jee5-2.0.2/bin/geronimo.sh file by adding -X:MaxPermSize=512M, as shown in the following start block:
elif [ "$1" = "start" ] ; then shift touch "$GERONIMO_OUT" $START_OS_CMD "$_RUNJAVA" $JAVA_OPTS $GERONIMO_OPTS \ $JAVA_AGENT_OPTS \ -Dorg.apache.geronimo.base.dir="$GERONIMO_BASE" \ -Djava.endorsed.dirs="$ENDORSED_DIRS" \ -Djava.io.tmpdir="$GERONIMO_TMPDIR" \ -XX:MaxPermSize=512M \ -jar "$GERONIMO_HOME"/bin/server.jar $LONG_OPT "$@" \ >> $GERONIMO_OUT 2>&1 & echo "" echo "Geronimo started in background. PID: $!" if [ ! -z "$GERONIMO_PID" ]; then echo $! > $GERONIMO_PID fi
Provide a deployment plan file either inside or outside of the opensso.war file. If placed inside the opensso.war file, name the plan geronimo-web.xml and place the file in WEB-INF directory. If placed outside of the WAR file, the plan file can be named otherwise. Here is a sample plan file:
<?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.2"> <environment> <moduleId> <groupId>sun</groupId> <artifactId>opensso</artifactId> <version>8.0</version> <type>war</type> </moduleId> </environment> <context-root>/opensso1</context-root> </web-app>
In the above example, the WAR file is deployed at:
geronimo-tomcat6-jee5-2.0.2/repository/sun/opensso/8.0/opensso-8.0.war
The web application is deployed at protocol://server:port/opensso1. You can change the deployment plan depending on your deployment scenario.
Related Information:
Geronimo console URL: protocol://server:8080/console/portal/welcome
Default user name and password: system/manager
To start the Geronimo server:/geronimo-tomcat6-jee5-2.0.2/bin/geronimo.sh start
To stop the Geronimo server: /geronimo-tomcat6-jee5-2.0.2/bin/geronimo.sh stop