1. The future roadmap for Narayana

    I think it could be useful with our Jira issues JBoss Transaction Manager - JBoss Issue Tracker

2. Links about the capabilities of the Narayana Transaction Server and if possible a comparison with Tuxedo

   Narayana Homepage · Narayana

3. Sample code for using Narayana

    https://github.com/jbosstm/quickstart

Thanks,

Amos

Supplementing Amos' answer. Although the home page itself is a great entry point, this is quite a nice overview: Narayana Features · Narayana although its not particular to just BlackTie and applies to the entire Narayana project.

The thing that Tuxedo and BlackTie totally share in common is an implementation of XATMI and TX. Tuxedo and BlackTie then diverge as implementations do on various other features, so if you are considering specific features you want to contrast with Tuxedo please do ask.

Thanks Joice for your interesting with the Blacktie,

Feel free to contact me (zfeng@redhat.com) for any question about the Blacktie and it is great to work with you.

Amos

You could also take a look at the (closed) JIRAs for our NBF buffers and the quickstart:

https://jira.jboss.org/browse/BLACKTIE-330

https://jira.jboss.org/browse/BLACKTIE-334

https://github.com/jbosstm/quickstart/tree/master/blacktie/nbf

Joice Joy wrote:

1. As Wildfly is a part of JBoss EAP, it is safe to say that blacktie is safe to work with JBoss EAP.

Not strictly. BlackTie is a community project that builds on top of WildFly (and Narayana) to provide XATMI compatibility. The only application server it is tested to work with is WildFly, although as WildFly is part of EAP it should be possible to deploy WildFly on top of the EAP version that BlackTie is developed against. You can usually tell the version of WildFly we test against in the pom.xml:  narayana/pom.xml at 5.2.2.Final · jbosstm/narayana · GitHub

An important distinction is that you can purchase commercial support for EAP but not for BlackTie.

2. Blacktie which is now a part of Narayana is shipped with Narayana only or separate as well.

BlackTie requires certain extensions to a transaction manager that are best met by Narayana. For example is uses REST-AT (a REST based transaction protocol) to perform transaction coordination. This would be possible to replace with another REST-AT implementation but we do use I think one proprietary hook into Narayana that would not replicate. It might be possible to break that link into an SPI or something. It is basically a way to look up transactions by their identifier IIRC.

3. Also is Narayana included in Wildfly or does Wildfly uses another Transaction Management software.

WildFly does include Narayana (at least certain components of it). The components in WildFly (and EAP) are: JTA/JTS/XTS. The components in WildFly only (i.e. not commercial support) can be found here: Narayana Features · Narayana

4. I have got a link to future roadmap for Narayana. Does the same apply to Blacktie. If not then what is the future plan for blacktie.

Yes, Narayana and BlackTie share the same roadmap.

Lastly what is the basic difference between Wildfly and Narayana

Narayana is the name for a suite of software known as the premiere open source transaction manager. It is a community project and has all the features listed on: Narayana Features · Narayana - so BlackTie is the sub project of Narayana which provides XATMI/TX APIs. WildFly is a community open source JEE application server. WildFly includes some components of Narayana out of the box: JTA/JTS/XTS/RTS.

EAP is the product that is supported commercially by Red Hat, but it would be better to talk to sales team to get more info on that one - parts of Narayana are supported in an EAP package but BlackTie is not part of EAP.

The only option you have is option 2, but in practical terms it looks more like option 1

i.e. WildFly already includes several parts of Narayana, just not BlackTie out of the box.

Basically you get a WildFly, and add the missing part of Narayana (BlackTie) on top.

This then gives you a JEE application server with the server side services to support C++ clients that use XATMI/TX.

The C++ clients run outside of the application server, the application server hosts the services that these clients need (a message broker and transaction manager). You may have seen it already but running this quickstart should give you the best overview of how it all hangs together: quickstart/blacktie/xatmi/fooapp at master · jbosstm/quickstart · GitHub

tomjenkinson wrote:

 

The C++ clients run outside of the application server, the application server hosts the services that these clients need (a message broker and transaction manager).

Just to confirm, what I mean by the services are the application server components, not the XATMI services.

in other words: "The C++ clients and services run outside of the application server, the application server effectively provides the middleware infrastructure to connect these services and clients"

There shouldn't be a functional difference to you as a user. I have raised: [JBTM-2497] Update or remove references of HornetQ to Artemis - JBoss Issue Tracker to update or remove where possible the references to HornetQ.

Thanks for the report!