There is two Weblogic servers with different versions, one is WebLogic Server 12.1.1.0.3 PSU and the other is WebLogic Server 12.1.1.0.6 PSU.
When I install the .ear on the 3 PSU server everything fine, and if I open the deployed instance all the Beans and DAOs are there az the EJBs section.
When I install it on the 6 PSU and open deployment it says: EJBs - None to display however Modules and Web Services are there.
There is an ejb-jar.xml and weblogic-ejb-jar.xml are present with no ejb definitions, because the beans have annotations like #Stateless, #EJB.
Why the server with the old patch finds the EJBs and the newer dont?
Thanks in advance.
Related
I have a .jar with EJBs and a .war that invokes these EJBs.
They used to be deployed in a Jboss SOA Platform 5 and now must be in a Jboss EAP 6.
The .war is looking up the EJBs with ejbname/remote. This is hardcoded (I checked with a decomplier).
I know that, in EAP 6, the EJBs are registered in the JNDI like [/<application-name>]/<module-name>/<bean-name>[!<full-qualified-interface-name>].
Is there any way for me to change the JNDI registry name of the EJBs. Maybe via Jboss CLI?
I only have the binaries and have no access to the source.
I have an ear maven project which contain an ejb moudle which has 4 stateless session beans annotated as web services. I was doing all my testing in Glassfish and have never complained when i deployed the ear file. Glassfish published the ejb's as web services and generated the WSDL and life was pink.
However, when i tried to deploy the same ear in WAS 8.5 nothing is published, and i can see the status of the service has x icon and when i hover it, it says that the service endpoints are not listening but the deployed asset is running.
I have spent a 3 day trying to solve this but no progress.
Have anyone faced such a problem? how you solved that and managed to publish the ejb as a web service?
For anyone later who may face the same issue. there is a utility in websphere/appserver/bin called endptEnabler. You must run it on your ear before installment in the app server.. Good luck for all
while deployment of webservices you have to enable the check box "Webservice" available in deployment settings in websphere
Jboss version= 6.0 EAP
Need your inputs around Jboss deployment, currently we were deploying custom war files using jboss cli command like deploy custom.war --server-groups=ha-server-group
We have a requirement to deploy custom war into individual jboss servers (ha-server-1,ha-server-2) rather server group name.
Do we have any jboss cli commands which can be used for deploying war file into individual server….?.
Sorry to say but in Domain mode we cant deploy application on specific server which is part of the server-group.
If you deploy application on server group then it will be get deployed on all servers which are part of that server-group.In EAP 6 Domain mode, we can deploy application on server-group only.
If you want to deploy application on specific server instance then you can create new server group.
I want to deploy JBoss FUSE as war or in any other way on application server (Tomcat for example). In documentation for the old version (3.5) of FUSE there was described a simple way for doing that by running special maven project from examples folder.
But for later releases I just can't find any information about possibility of doing that. I thought that deploying ESB as a service on application server is standard way of working with it, but I only found tutorials for installing FUSE as standalone instance or system service.
I would like to know how can I deploy it or why I can't do this if thats the case.
This is no longer supported. JBoss Fuse 6.x is a standalone application that has its own container (based on Apache Karaf).
The current 6.x release requires running on top of Apache Karaf.
Though we have plans to make Fuse (that would be Fuse Fabric) container agnostic so you in the
future would be able to run Fuse on JBoss AS, Tomcat, Karaf, Standalone, in the cloud, etc. Though we focus on JBoss AS, Tomcat, and Karaf as the main containers at first we aim to support.
I am learning EJB3 from last few days. I have many questions regarding EJB, application servers and deployment of EJB.
To start with, I have created one simple helloworld stateless session bean but I don't know how to deploy it on server. It has single bean class, bean interface and one servlet client. I have used eclipse to develop this project.
None of the books that I read gives step by step details about how to put EJB on server and how to access those beans.
I have JBoss 6 server and I also have Java EE budle downloaded from sun website. Does this Java EE bundle contains Glassfish server? or do I need to download it separately?
Can anyone please give me step by step details of how to put my bean and its client on server (JBoss or Java EE)?
And why do we need to include bean interface class in EJB client code? I mean either we need to keep client and bean in same package or if we keep them in seperate packages we need to import bean interfaces in client code. Am I right?
With Java EE 6, you can package your Servlet and your EJB in a WAR (either package your EJB in a JAR and put it in WEB-INF/lib or simply put all classes in WEB-INF/classes). And to deploy this WAR, copy it to:
$GLASSFISH_HOME/domains/<domain1>/autodeploy for GlassFish v3*
$JBOSS_HOME/server/default/deploy for JBoss 6
With Java EE 5, you'll have to package your code in a EAR.
And if you want to deploy your application from Eclipse (using the Eclipse WTP), you'll have to install the appropriate server adapter. For Eclipse Galileo and GlassFish (there is currently no adapter for JBoss 6 AFAIK), right-click the server view, select New > Server, click on Download additional server adapters and select the GlassFish adapter. Finish to define your new GlassFish v3 Java EE 6 server and deploy your application on it (right-click on your application then Run As > Run on Server). For Eclipse Helios and GlassFish, you can follow the link given by #VonC (manual install) or check this answer (install via the Update Site).
You need to add GlassFish to your Eclipse installation (see GlassFish plugin for Eclipse).
The full process is described here (with the latest Eclipse Helios 3.6M6)
You should export as EJB into your jboss<version>\server/default/deploy folder and then add the build path for it on the servlet's web project. You can "Run on Server" and choose an application server just like you would in any project, no need to export the WAR although if you do that, you're gonna have to re-export your WAR every time you modify your code
AFAIK there's no Eclipse plugin for JBoss 6 but Eclipse provides one for 5.1