WebSphere to Wildfly migration- How to convert ibm-ejb-jar-bnd.xmi content to ejb-jar.xml - websphere

We are migrating from WebSphere to Wildfly 26.1. We are facing issue with ibm-ejb-jar-bnd.xmi. As we are not able to resolve JNDi name in Wildfly. how to convert contents of ibm-ejb-jar-bnd.xmi so it can be supported in wildfly 26.1.
Unable to configure ejb-resource-ref to jndi on wildfly

Related

JBoss EAP 7 - Client JMS without standalone-full.xml?

I have two JBoss EAP platform: JBoss1 and JBoss2 (different boxes and obviously different standalone configurations). In the JBoss1 server I have JMS messaging (i.e. the standalone-full.xml configuration). In the JBoss2 client I have a standalone.xml configuration. When I try to connect this environment with JBoss1 I catch an error of misplaced or needed classes (i.e. ActiveMQ Artemis core classes). In the module.xml (the descriptor of my custom lib module) I put the correct dependencies, but the error is the same. The client in JBoss2 is a simple WAR with a jboss-deployment-structure.xml. In jboss-deployment-structure.xml I don't have the same dependencies in module.xml. Is this the problem? Or the configuration of JBoss2 client must be with a standalone-full.xml?

Stadlaone-full set up for wildfly

i'm tryin to run an app that runs on jboss EAP , on jboss Wildfly , but i'm having problems with the standalone-full.xml because some services like hornetq aren't available on Wildfly
is there a possible way to migrate from eap to wildfly?
any help?
This depends on your app.
Wildfly 10 ships with ActiveMq rather than HornetQ.
If your app uses standard JMS then you can configure the WF10 standalone-full to have the same JMS endpoints as your old deployment. If however your app is using the HornetQ specific client you will have to do some more work. ActiveMQ artemis integrates HornetQ protocols but it probably won't work without some trial and error in the configuration.
I would suggest starting with standalone-full.xml from Wildfly 10 and compare it with your JBoss EAP configuration. There should be an analog for each service you need. Once that is set try running your app and see what happens.

Configuring resource in Tomcat's context.xml to access remote Weblogic JMS queues

What I intend to do is access remote queues in Oracle Weblogic JMS (version 10.3.4) from a spring application deployed in Tomcat7.
For this I am trying to configure a Resource (eg JMS connection factory, queues etc) in Tomcat's context.xml file. Then access this resource using jndi lookup in the spring configuration file and provide it to the necessary beans. I have already created connection factory and queues in Weblogic JMS and they can be accessed using jndi names.
I am able to make it work successfully when using ActiveMQ instead of Weblogic JMS. However with Weblogic JMS, I am facing an issue with configuring the Resource element. I am not sure what attributes to be used with Resource tag while connecting to Oracle Weblogic JMS.
When working with ActiveMQ the resource element config looks like below
<Resource name="jms/MyConnectionFactory" auth="Container"
type="org.apache.activemq.ActiveMQConnectionFactory"
factory="org.apache.activemq.jndi.JNDIReferenceFactory"
description="JMS Queue Connection Factory"
brokerURL="tcp://localhost:61616" brokerName="MyActiveMqBroker"/>
I am struggling to find the configuration to be used with Oracle Weblogic JMS. I have gone through documentations to see how to do it but with no luck.
Any help or pointers would be highly appreciated.
Thanks.

JMS Client for WebSphere Application Server 8.5.5 and 7.0.0.13 with Oracle Java 8

I am using Java JMS client to connect to Websphere Application Server 8.5.5.0 and 7.0.0.13. I using following set of jars in classpath of client:
ibmorb.jar, ibmorbapi.jar, com.ibm.jaxws.thinclient_.jar, com.ibm.ws.ejb.thinclient_.jar, com.ibm.ws.sib.client.thin.jms_.jar.
It works fine with Oracle Java 7. But with Oracle Java 8 it gives java.lang.NoClassDefFoundError: sun/io/MalformedInputException during JNDI lookup. The ibmorb.jar is using sun.io.MalformedInputException class which is no longer shipped with Java 8. I also tried using com.ibm.ws.orb_.jar in place of ibmorb.jar but got same exception.
What is the suggested approach to solve this problem?
I tried with ibmorb.jar from optional IBM Java Developer Kit 7 provided with 8.5.5.3 and it worked. I did not find standalone installer for IBM Java 7 and I don't want to upgrade the AppServer on server side. If using jars from IBM Java 7 is the only option then how can I get the standalone IBM Java 7 installer or IBM Java 7 for 7.0.0.13?
You can get IBM JDK from here - http://www.ibm.com/developerworks/java/jdk/index.html

JSTL SQL setDataSource not working with Webshpere 8.5

<sql:setDataSource var="TCIT" scope="application"
driver="${driver}"
url="${url}"
user="${username}"
password="${password}" />
The above code is used in a legacy application deployed in OC4J that is being migrated to WebSphere 8.5. The properties in {} above are fetched from a property file. Ensured the values are coming correctly form there. However, when the database connection is created the application is encountering the following exception: Unable to get connection, DataSource invalid: "java.sql.SQLException: No suitable driver" . I have the ojdbc14.jar in the WEB-INF/lib folder, still facing the issue.
Finally the issue got resolved creating a JDBC connection pool at Application server level. Turns out Websphere does not allow the connection to be created using the above method. Below is the modified tag that is using JNDI lookup for accessing the JDBC connection pool at application level.
<sql:setDataSource var="connPool" scope="application" dataSource="${jndi.devPool}"/>

Resources