在WildFly 9.0.1版本上的localhost上启用https

Question

我正在尝试以安全模式https://localhost:8080

运行localhost

我对独立xml做了一些更改，如下所示

<security-realm name="SSLRealm">
    <server-identities>
        <ssl protocol="TLS">
            <keystore path="serverkeystore" relative-to="jboss.server.config.dir" keystore-password="secureworld" alias="servercert"/>
        </ssl>
    </server-identities>
    <authentication>
        <truststore path="servertruststore" relative-to="jboss.server.config.dir" keystore-password="secureworld"/>
    </authentication>
</security-realm>

和

<http-listener name="default" socket-binding="http" max-parameters="5000"/>
<https-listener name="default-https" socket-binding="https" security-realm="SSLRealm" verify-client="REQUESTED" max-parameters="5000"/>

web xml有

<session-config>
    <session-timeout>10</session-timeout>
    <cookie-config>
        <path>/</path>
        <http-only>true</http-only>
        <secure>true</secure>
    </cookie-config>
</session-config>

然后我尝试启动服务器，我认为它缺少密钥库文件

09:45:14,889 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.server.controller.management.security_realm.SSLRealm.key-manager: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.SSLRealm.key-manager: WFLYDM0086: The KeyStore can not be found at C:\work\Servers\wildfly-9.0.1.Final\standalone\configuration\serverkeystore
    at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:114)
    at org.jboss.as.domain.management.security.FileKeyManagerService.start(FileKeyManagerService.java:145)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]

可以帮助我解决这个问题。