I am using RAD 8.0 with WebSphere 6.1.
When I right click on the Server in the Servers View and select "Add and Remove..." I get a dialog saying "There are no resources that can be added or removed from the server."
What am I missing to get it to let me add my project to the server?
WebSphere 6.1 supports only Java EE 1.4 applications, so if you by chance created new Java EE 5 or 6 EAR you will not be able to deploy it to 6.1.
Related
Our developers currently use the IBM RAD 8.5 to develop web applications (No enterprise Java beans (No J2EE), use Spring framework). The server team is planning to upgrade WebSphere from version 8 to version 9. Last I checked in the servers tab, RAD 8.5 supports WAS version 8, 8.5, and 8.5 Liberty profile. See screenshot.
Is it possible to continue to develop in RAD 8.5, and deploy to WebSphere 9 in the server environment? What kind of snag would I expect to run into? e.g. Assemble the WAR file in RAD 8.5, and deploy the WAR file in WAS 9.
Would there be any problem I should anticipate in the deployment descriptor? e.g. files like web.xml and application.xml?
Moving forward, is it better to use other IDE to do software development if we are not planning to upgrade RAD 8.5 to a newer version? Would MyEclipse(variant of Eclipse with better server support) or Eclipse IDE for Java EE Developers (oxygen) suffice? Do I also need the liberty profile?
https://developer.ibm.com/wasdev/downloads/liberty-profile-using-eclipse/
What kind of issues should I be expecting? Or continue using RAD 8.5 would be a better option?
Here are some of the stackoverflow links I had checked already. There are pretty high level.
what-are-the-differences-when-deploying-on-tomcat-vs-websphere
can-a-war-file-be-deployed-on-any-server
Thanks.
In my experience I could not use RAD 8.5 to control a v9 server. I could not use Java 8 in RAD 8.5. I would not expect RAD 8.5 to know about the newer versions of JPA, JAX-RS and other things in v9. You could continue to develop jee6 apps on a v8.5 server and then move them manually to a v9 server.
Liberty is worth a look but is not completely interchangeable. Liberty has features that traditional does not (MicroProfile) and lacks some older things that traditional has (JAX-RPC).
You might check out the WebSphere Developer Tools for Eclipse that have support for traditional v9. They're not as full featured as RAD but might be enough. More info is at https://www.ibm.com/support/knowledgecenter/en/was_beta/com.ibm.websphere.wdt.doc/topics/wdt_overview.htm
Adding to the information provided by Bruce, IBM had introduced OpenLiberty where one can deploy the war file built with RAD. Deploying to other application server (e.g. tomcatEE
) is possible, but it would require some work. OpenLiberty should be closest to the IBM Websphere in terms of setup and architecture.
Here are some links that provide more information.
OpenLiberty
IBM announces Open Liberty, an open source runtime for Java microservices
Difference between OpenLiberty and Websphere Liberty
We have a web application created using struts 1.2.9. We migrated that application to weblogic 12c. Now I want to use Jdeveloper 12 IDE for our development. So I could use the integrated weblogic 12c server. But it looks like Jdeveloper 12 no longer supports struts I framework. I had to upload the tag libraries manually and I'm not able to run the application using the IDE "Run" play button.
Getting the following error when I tried to run the application.
The target struts-config.xml cannot be started because it is not a runnable target.
Has anyone come across a similar issue and managed to solve it?
While Adding Websphere Portal 8 Server in RAD 9.0.1 results in "The Application Server installation directory is not correct" error.Can you please let me know how to solve this issue.
Check this link Adding Portal 8 Server in RAD 9.0.1 results in "The Application Server installation directory is not correct" error
Potential causes include:
- You have not selected the WebSphere Portal Server 8.0 on WebSphere Application
Server 8.5 adapter.
Note: You may have mistakenly selected the WebSphere Portal 8.0 Server adapter or
you may not even have the WebSphere Portal Server 8.0 on WebSphere Application
Server 8.5 adapter available to choose from in RAD.
- You are not providing the right installation directory for your Portal or WAS
server. The WAS server you are pointing to which is to be used with Portal 8
is not compatible with Portal.
Note: You must be using a WAS ND server
Ensure you have the WebSphere Portal Server 8.0 on WebSphere Application Server 8.5 adapter and not the WebSphere Portal 8.0 adapter.
If you do not see the correct adapter available:
Close RAD
Open IBM Installation Manager
Click Modify > Select the RAD 9.0.1 package group > Next > Next.
You should now be on the feature selection page.
Under the Server tools section, ensure to have the Development tools and the Remote server stub installed for the Portal version and
WAS version you are looking to install
For example: If you are looking to install Portal 8 with WAS 8.5.x, ensure you have the Development tools and the Remote server stub also installed for the WebSphere Portal Server 8.0 on WebSphere
Application Server 8.5 option
Click Next > Modify
I am having troubles with integration WAS [ND/BASE] 8.5 or WAS [ND/BASE] 8.5.5 with Worklight Studio 6.0 in Eclipse or in RAD 9.
What I did:
Installed RAD 9
Installed WAS TE 8.5.5, created AppSrv profile,
secured
Installed Worklight 6.0 on the WAS - worklight console
application installed fine
Installed Worklight Studio 6.0 in RAD 9
Created new Hybrid project in fresh workspace
Now, I am trying to have the project run on WAS 8.5.5 (full profile) server, and Worklight Studio 6 does not support it? When I open "Change Worklight Target Server", create new WAS BASE 8.5.5 server - the server not appear in the drop down for that dialog.
NOTE: Same I had with Eclipse 4.2.2 and standalone WAS 8.5.0.2, using Worklight 6 and Worklight Studio 6. No any support for Websphere full profile. Did I do it wrong?
What I want to do: integrate Eclipse with Worklight Studio with WAS ND (not Liberty Profile) as server for testing.
Thanks in advance.
I'm afraid the Worklight Studio server integration only works with Liberty profile and Tomcat but not with WAS ND.
Don't understand me wrong, even if your scenario fails to work, Worklight WAR will still work as expected on WAS ND as indicated in the Worklight Info-Center.
For debugging that , I suggest you deploy the Studio generated WAR to the WAS server (manually). Then modify the server instance settings and enable its debug mode (see JVM settings in WAS Info Center) and from your eclipse: start remote debug (defult port 7777) the Java code.
I've been asked to get a web application running in WebSphere using RAD 8.0.1, which isn't my usual app.server or development environment.
I'm starting off simple, using the default Ajax Test Server, but from what I can see, the default for a Dynamic Web Application is Servlets 2.5. Is there something buried in the twisty little maze of config dialogs to set it to Servlets 3.0, or must I handle that manually?
IBM Websphere Application Server 8.0 supports Servlet 3.0
IBM Websphere Application Server versions 7.0 and 6.1 do not support it.
So you need to use version 8.0. If you are using Websphere Portal, then you have a problem.
IBM Websphere Portal runs on same version Application Server (though you can for instance run Portal 6.1 on WAS 7 - I ran into some problems with AJAX though). So you might be able to get Portal 7 to run on WAS 8. It's the only way in the short term.
What is the run-time environment that you use?
WebSphere 7.x does not support Servlets 3.0 and it would be supported only by WebSphere 8.0.
WebSphere 8.0 is still in beta.
Interestingly, wikipedia is a good site for the list of supported APIs by WAS.
http://en.wikipedia.org/wiki/IBM_WebSphere_Application_Server
I don't have a RAD 8 handy with me to assist but i would check and ensure that the run-time associated with the project does support Java EE 6 (and Servlets 3.0)
HTH
Manglu
Websphere Application Server 7 can support servlets 3.0 if you installed Fix Pack 7.0.0.37 or later.
That shall upgrade JDK from 1.5.x to 1.6.x. Also you need to install WebSphere Application Server V7 Feature Pack for Web 2.0 and Mobile V1.1