編輯“EJBCA/EJBCA的安裝”（章節(jié)）

===整合===
*拷貝文件%EJBCA_HOME%\conf\ejbca.properties.sample到%EJBCA_HOME%\conf\ejbca.properties,這個文件是ejbca的主配置文件，可以進(jìn)行自定義配置，例如對CA的配置：
<pre># ------------ Basic CA configuration ---------------------
# When upgrading, the important options are:
# - ca.keystorepass
# - ca.ocspkeystorepass
 
# This installation will create a first administrative CA. This CA will be used to create the first
# superadministrator and for the SSL server certificate of administrative web server.
# When the administrative web server have been setup you can create other CA:s and administrators.
# This is only used for administrative purposes,
# Enter a short name for the CA.
ca.name=AdminCA1
 
# The Distinguished Name of the CA.
# This is used in the CA certificate to distinguish the CA.
ca.dn=CN=AdminCA1,O=EJBCA Sample,C=SE
 
# The keysize in bits of the CA, only digits.
ca.keysize=2048
 
# The keytype, can be RSA or ECDSA
ca.keytype=RSA
 
# The validity in days for the CA, only digits.
ca.validity=3650
 
# The policy id of the CA. Policy id determines which PKI policy the CA uses.
# Type your policy id or use '2.5.29.32.0' for 'any policy' (rfc3280) or 'null' for no policy at all.
ca.policy=null
 
# This password is used internally to protect CA keystores in database (i.e. the CAs private key).
# foo123 is to keep compatibility with default installations of EJBCA 3.0, please change this if possible
# If upgrading from EJBCA 3.0.x, you should take this value from src/ca/ca/META-INF/ejb-jar.xml -> keyStorePass.
# The default value is the same for convenience.
ca.keystorepass=foo123
#ca.keystorepass=!secret!
 
# Password user to protect OCSP keystores in the database (CAs OCSP signer certificate).
# If upgrading from EJBCA 3.0.x, you should take this value from src/ca/ca/META-INF/ejb-jar.xml -> OCSPKeyStorePass.
# The default value is the same for convenience.
ca.ocspkeystorepass=foo123
#ca.ocspkeystorepass=ocsp!secret!
 
# Password user to protect XKMS keystores in the database (CAs XKMS signer/enc certificate).
# The default value is the same for convenience.
ca.xkmskeystorepass=foo123
 
# Password user to protect CMS keystores in the database (CAs CMS signer/enc certificate).
# The default value is the same for convenience.
ca.cmskeystorepass=foo123
由于只是實驗性的學(xué)習(xí)，所以保持默認(rèn)配置。原文檔說明為：The default values works fine for a test installaton. If you are using JBoss < 4.0.3 you must
configure the property web.jsfimpl in conf/web.properties.
# Specifies the JSF implementation used by the application server EJBCA is deployed on.
# Possible values are: myfaces
# Using nojsf means that the admin-GUI will be limited with some functions not working.
# It can however be useful if there are problems with your application server and JSF/MyFaces.
# Use nojsf for JBoss < 4.0.3
#
# Default: myfaces
#web.jsfimpl=myfaces
如果使用的JBoss版本< 4.0.3，需要修改默認(rèn)配置。</pre>

*將mysql[[數(shù)據(jù)庫]]jdbc鏈接程序包mysql-connector-java-5.0.6-bin.jar拷貝到%JBOSS_HOME%\server\default\lib目錄下

*ejbca支持的數(shù)據(jù)庫有MySQL, [[PostgreSQL]] 7 and 8, [[Oracle]] 8 and 9, [[Sybase]], [[HypersonicSQL]], [[SAPDB]] and [[MSSQL]]，默認(rèn)的數(shù)據(jù)庫配置是JBoss內(nèi)建的HypersonicSQL數(shù)據(jù)庫（該數(shù)據(jù)庫有以下缺點：內(nèi)存消耗太大、不支持全部SQL語句集），我們將其修改為MySQL的配置：

<pre># ------------- Database configuration ------------------------
 
# jndi name of the datasource to use in deployment descriptors of ejbs.
#datasource.jndi-name=EjbcaDS
 
# Prefix for the jndi name of the datasource to use in deployment descriptors of ejbs.
# JBoss requires 'java:/' as divfix, while Weblogic does not want anything (''), and Glassfish wants jdbc/
# default: java:/
#datasource.jndi-name-divfix=java:/
#datasource.jndi-name-divfix=
#datasource.jndi-name-divfix=jdbc/
 
# Weblogic in combination with Oracle requires special handling of LONG/BLOB columns
# If, and only if, you are using Weblogic and Oracle, uncomment the row below.
# Use OracleBlob in Weblogic 8.x and Blob in Weblogic 9.x
# default:
#weblogic-oracle-columntype=@weblogic.dbms-column-type OracleBlob
 
# The database name selected for deployment, used to copy XDoclet merge files.
# All supported databases are defined below, others can easily be added
# See the document doc/howto/HOWTO-database.txt for database specifics and tips and tricks.
# Default: hsqldb
database.name=mysql
 
# The datasource mapping selected for deployment.
# The J2EE server needs to be configured with the appropriate datasource mapping.
# For JBoss this maps to a setting in standardjbosscmp-jdbc.xml and must match the database chosen above.
# All supported mappings are defined below, others can easily be added
# Default: Hypersonic SQL
datasource.mapping=mySQL
 
# Database connection url.
# This is the URL used to connect to the database, used to configure a new datasource in JBoss.
# Default: jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB
database.url=jdbc:mysql://127.0.0.1:3306/ejbca?characterEncoding=UTF-8
 
# JDBC driver classname.
# The J2EE server needs to be configured with the appropriate JDBC driver for the selected database
# Default: org.hsqldb.jdbcDriver
database.driver=com.mysql.jdbc.Driver
 
# Database username.
# Default: sa (works with hsqldb)
database.username=root
 
# Database password.
# Default: (blank works with hsqldb)
database.password=root
</pre>