Layer7 Identity Management

Expand all | Collapse all

ca identity manager high availability & jboss clustering

Jump to Best Answer
  • 1.  ca identity manager high availability & jboss clustering

    Posted 10-06-2015 01:28 PM

    Looking for more information on how to setup JMS to use MSSQL rather than hypersonic on Jboss 5 / IdM 12.6 SP2.

     

    So far here's what I've found:

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec563361.aspx

     

    CA Identity Manager High Availability & JBoss Clustering - IDMWORKS : Blog

     

    I don't think either of these documents are complete and would like more information on how to successfully implement this.

     

    Please do share, as this is a common problem with any CA IdM customer running on Jboss cluster. (which is a huge set of CA customers).

     

    Please respond with any questions or concerns.

    Thank you.

    Regards,

     

    Chris Thomas

    IdM Architect

    Information Security

    MUFG Union Bank, N.A.

    https://www.linkedin.com/in/chrisryanthomas



  • 2.  Re: ca identity manager high availability & jboss clustering

    Posted 10-07-2015 05:11 AM

    Hi Chris,

     

    Good to hear from you.

    Usually the JBoss messaging solution is not strictly within the CA responsibility.

    I can suggest the following URL:

    https://developer.jboss.org/message/809461 It shows the steps to configure MSSQL as the messaging repository.

    You can use that along with the CA technical documents you mentioned.

     

    I do not see any other article that explains more other than the two you mentioned.

     

    If there is a specific issue, please feel free to open a support case so we can assist.



  • 3.  Re: ca identity manager high availability & jboss clustering
    Best Answer

    Posted 10-13-2015 07:49 AM

    I do not know how to implement this in a HA environment, but this is what I did on my single JBoss server (Windows) running 12.6.4

     

    1. Delete JBoss\server\default\deploy\hsqldb-ds.xml
    2. Copy JBoss\docs\examples\jca\mssql-ds.xml -> JBoss\server\default\deploy
      Change parameters to reflect your setup
    3. Delete JBoss\server\default\deploy\messaging\hsqldb-persistence-service.xml
    4. Copy JBoss\docs\examples\jms\mssql-persistence-service.xml -> JBoss\server\default\deploy\messaging
      Change DataSource parameters to reflect your setup (use DS from mssql-ds.xml)
    5. Restart JBoss

     

    As I am only using one db connection fraom JBoss, I just use java:/DefaultDS as DS