How to Migrate JMS Provider from JBoss 4.2.3 to WildFly 8.1

[glen.medina]

Hi Guys,

Is it possible to migrate below settings from JBoss 4.2.3 to WildFly 8.1?

This application uses JMS queues to send and receive messages between the Manager and

Adapter components.

In every installation there must be at least two queues for the application to function, a request queue that carries messages from the manager to the Adapter, and a response queue that carries messages from the Adapter to the Manager.

For jbossmq-service.xml

<!--================================================================-->

<!--Queue Connection Factory Alias=======================-->

<!--================================================================-->

<mbeancode="org.jboss.naming.NamingAlias"

name="jboss.mq:service=NamingAlias,fromName=DCS/JMS/QCF">

<attributename="ToName">XAConnectionFactory</attribute>

<attributename="FromName">DCS/JMS/QCF</attribute>

</mbean>

<mbeancode="org.jboss.naming.NamingAlias"

name="jboss.mq:service=NamingAlias,fromName=DCS/JMS/TCF">

<attributename="ToName">XAConnectionFactory</attribute>

<attributename="FromName">DCS/JMS/TCF</attribute>

<depends>jboss:service=Naming</depends>

</mbean>

For jbossmq-destinations-service.xml

<!--================================================================-->

<!--Queues===============================================-->

<!--================================================================-->

<mbeancode="org.jboss.mq.server.jmx.Queue"

name="jboss.mq.destination:service=Queue,name=RequestQueue">

<dependsoptional-attribute-name="DestinationManager">

jboss.mq:service=DestinationManager

</depends>

</mbean>

<mbeancode="org.jboss.mq.server.jmx.Queue"

name="jboss.mq.destination:service=Queue,name=ResponseQueue">

<dependsoptional-attribute-name="DestinationManager">

jboss.mq:service=DestinationManager

</depends>

</mbean>

<!--================================================================-->

<!--Queue Aliases =======================================-->

<!--================================================================-->

<mbeancode="org.jboss.naming.NamingAlias"

name="jboss.mq:service=NamingAlias,fromName=DCS/JMS/RequestQueue">

<attributename="ToName">queue/RequestQueue</attribute>

<attributename="FromName">DCS/JMS/RequestQueue</attribute>

</mbean>

<mbeancode="org.jboss.naming.NamingAlias"

name="jboss.mq:service=NamingAlias,fromName=DCS/JMS/ResponseQueue">

<attributename="ToName">queue/ResponseQueue</attribute>

<attributename="FromName">DCS/JMS/ResponseQueue</attribute>

</mbean>

<!--====================================================================-->

<!-- Topics ======================================================-->                        

<!--====================================================================-->

<mbeancode="org.jboss.mq.server.jmx.Topic"

name="jboss.mq.destination:service=Topic,name=Bus">

<dependsoptional-attribute-name="DestinationManager">

jboss.mq:service=DestinationManager

</depends>

</mbean>

<!--=================================================================== -->

<!-- Topic Aliases ===============================================-->                     

<!--====================================================================-->

<mbeancode="org.jboss.naming.NamingAlias"

name="jboss.mq:service=NamingAlias,fromName=DCS/JMS/Bus">

<attributename="ToName">topic/Bus</attribute>

<attributename="FromName">DCS/JMS/Bus</attribute>

<depends>jboss:service=Naming</depends>

</mbean>

[armahdi]

Hello Glen or any one. This issue is out there but no one has an answer for it?? Its also mentioned on http://wildfly-development.1055759.n5.nabble.com/Naming-Alias-on-Jboss-7-td5709943.html

how do we convert this type of configuration to the wildfly.