The full PKI suite has many parts.

I did a checkout and built:

./pki/scripts/compose_pki_core_packages rpms

This seems to be the option that actually builds the web server pieces. It also builds a bunch of native code:

/native-tools/src/sslget/sslget.c and so forth.

These three are under architecture specific

pki-core-debuginfo-10.0.1-1.f17ayoung.x86_64.rpm
pki-symkey-10.0.1-1.f17ayoung.x86_64.rpm
pki-tools-10.0.1-1.f17ayoung.x86_64.rpm

and these are under no-arch

pki-base-10.0.1-1.f17ayoung.noarch.rpm
pki-ca-10.0.1-1.f17ayoung.noarch.rpm
pki-javadoc-10.0.1-1.f17ayoung.noarch.rpm
pki-kra-10.0.1-1.f17ayoung.noarch.rpm
pki-ocsp-10.0.1-1.f17ayoung.noarch.rpm
pki-server-10.0.1-1.f17ayoung.noarch.rpm
pki-tks-10.0.1-1.f17ayoung.noarch.rpm

I'm assuming that to deploy the CA server, the pieces I would need are:

pki-base for Java code
pki-server for the admin console
and pki-ca for the UI specific to the CA.

pki-server has a subdir called webapps, with a subdir under that called pki. For JBoss, this subdir should be packaged up in a file called ca.war.

pki-ca has a subdi called webapps, with a subdir under that called ca. For JBoss, this subdir should be packaged up in a file called ca.war.

To bundle up for JBoss, the way I learned was to create an enterprise archive called pki.ear:
http://en.wikipedia.org/wiki/EAR_%28file_format%29

Both of these war files would go into pki.ear, would the .jar files from pki-base:
pki-certsrv.jar, pki-cmsutil.jar, pki-nsutil.jar

from: pki-server:
/usr/share/java/pki/pki-cms.jar
/usr/share/java/pki/pki-cmsbundle.jar
/usr/share/java/pki/pki-cmscore.jar
/usr/share/java/pki/pki-silent.jar
/usr/share/java/pki/pki-tomcat.jar

And pki-ca:
/usr/share/java/pki/pki-ca.jar

I suspect that pki-silent would not really be needed, as I recall that does post install configuration. We'd more likely want to capure the majority configuration and put it into the ear file as well.

In the The META-INF directory, it would have an application.xml file with a module entry for pki and ca. Since there are no EJBs, I don't think it would require entries for the jar files.

I don't think there's a particular interest in moving to JBoss at this time. If this is something we still wish to investigate, feel free to reopen.

I think we're too heavily invested in the Tomcat ecosystem, due in part to self-hosting our CA (which requires interacting with NSS and potentially HSMs).

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1058

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.