[jbossts-issues] [JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL

[Paul Robinson (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12823220#comment-12823220 ] 

Paul Robinson commented on JBTM-1838:
-------------------------------------

Done in 4.17 using EAP: https://github.com/jbosstm/quickstart/commit/5d7a4ea39bea48c90b63de783381ced493ba343e

Gytis: 

can you apply to master using WildFly. I think the commands are the same, but you will need to test them. Also, you will need to rename the occurrences of JBoss EAP 6.1 with WildFly. I think it should be less specific about the actual version downloaded.  Just tell the user to go get WildFly from the download page and then unzip it. This will stop it going out of date every time a new version is released.
                
> Document how to configure XTS to use SSL
> ----------------------------------------
>
>                 Key: JBTM-1838
>                 URL: https://issues.jboss.org/browse/JBTM-1838
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Demonstrator
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.Final
>
>   Original Estimate: 1 day
>          Time Spent: 1 day
>  Remaining Estimate: 4 hours
>
> The documentation should show how to use 'https' for all communications. 
> I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS. 
> We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart. 
> Other options are a community wiki page or blog posting. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira