sorry for buggin you guys ... :-)
i found the answer, and here it is:
Configure SSL in JBoss
For JBoss 2.4.6, using JDK 1.2 or higher is ok. With JBoss 3.0 and later, you will need JDK 1.4 for JAAS and LOG4J support.
Generate a key using the keytool.exe that comes with JDK. This part is pretty easy. The alias should be "tomcat".
keytool -genkey -keyalg RSA -keystore mykeys.store -alias tomcat
After generating the mykeys.store file, place it in the C:\ for this example. It can actually be placed wherever you want as long as you edit the connector (below) to point to it.
NOTE: when starting JBoss, the gateway will not autostart within JBoss unless the ear is also within the deploy directory.
JBoss 2.4.6 / Tomcat 4.0.3
Edit the C:\icjis\jboss\conf\catalina\jboss.jcml file and verify that you have the following entry and then restart.
<!-- The embedded Tomcat-4.x(Catalina) service configuration -->
<!-- Define a non-SSL HTTP/1.1 Connector on port 80 (verify port 80 is free before enabled -->
<!-- Define an SSL HTTP/1.1 Connector on port 443 -->
<!-- Define an AJP 1.3 Connector on port 8009 -->
Jboss 3.07 / Tomcat 4.1.24
For this version of JBoss you do not have a jboss.jcml file. Instead, you need to find the tomcat41-service.xml within the C:\jboss\server\default\deploy directory and verify the following entry exists and then restart the server.
instant <!-- you may switch to "interval" -->
<!-- Access logger -->
<!-- Default context parameters -->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 80 -->
<!-- An AJP 1.3 Connector on port 8009. Used by Apache mod_jk for example -->
Note: you may need to remove the existing log4j.jar from the Thinkstream jars classpath if it conflicts with the log4j.jar that comes with JBoss.