Deploying Pega .ear Fle in Jboss EAP 7.0
I am trying to deploy pega .ear in jboss EAP 7.0.ut deployment fails as pega ear file contains Hornetq-jms.xml and thrwing error WFLYMSGAMQ0055: Could not parse file META-INF\\hornetq-jms.xml Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}}
***Edited by Moderator Marissa to update platform capability tags****
Accepted Solution
Pegasystems Inc.
US
Hi Smruti,
That was the issue. You should use prpc_j2ee14_jboss7JBM.ear file for JBoss 7 server.
You can find the archive file from the Pega Distribution media folder.
Eg:- For Pega 8.3 below is the folder structure.
116466_Pega<8.x>\archives
Let me know if that helps!
Pegasystems Inc.
IN
Hi Smruthi,
Could you please check this article.
Please let me know if this helps.
Warm regards,
Venkat
Deloitte
IN
Hi Janav,
hornet-jms.xml in ear is like below ,still getting the error.
<messaging-deployment xmlns="urn:jboss:messaging-deployment:1.0">
<hornetq-server>
<jms-destinations>
<jms-topic name="PegaAsyncTopic">
<entry name="topic/jms/PRAsyncTopic"/>
</jms-topic>
</jms-destinations>
</hornetq-server>
</messaging-deployment>
Pegasystems Inc.
US
Also, make sure you are using prpc_j2ee14_jboss7JBM.ear file for deployment in JBoss 7 versions.
Use the EAR file only if you need one of the following EAR-only features. Else, consider WAR file deployment as a best practice.
- Java Messaging Service (JMS): Pega connectors and services
- Java Transaction API (JTA): Two-phased commits to the database
- Enterprise Java Beans (EJB): Pega connectors and services
- Java Connector Architecture (Connect JCA)
Accepted Solution
Pegasystems Inc.
US
Hi Smruti,
That was the issue. You should use prpc_j2ee14_jboss7JBM.ear file for JBoss 7 server.
You can find the archive file from the Pega Distribution media folder.
Eg:- For Pega 8.3 below is the folder structure.
116466_Pega<8.x>\archives
Let me know if that helps!