J2EE Application Servers Survey

Folks:
Pls take a couple of moments to fill out a brief survey to help us gather requirements for the next generation of J2EE Application Servers.
http://see.sun.com/Apps/DCS/mcp?q=ST1WG05TFqfbpsF
We will provide respondents with a concise summary of our findings as well as access to a new Application Server market study conducted by an independent party.
You do not need to be a current Sun Application Server user to participate .
Thank you.
Ashesh Badani
Product Marketing
Sun Java System Application Server

I thought I resolved some bugs with updating JSC continuously; BUT there is a bug I just do not like very much:
Make changes to a project, save them with "save all" command; then run the changed project and surprise surprise, the changes do ont take effect, instead I get the old version of the project. Far better is it afer recognizing such a bug to shut down and restart JSC with the intention of getting a natural refresh. No matter it gets worse, buttons are placed anywhere within a jsp page, just not located there where intended to be.
danny
http://www.work-at-home-profits.com

Similar Messages

J2EE Application Server Survey

Folks:
Pls take a couple of moments to fill out a brief survey to help us gather requirements for the next generation of J2EE Application Servers.
http://see.sun.com/Apps/DCS/mcp?q=ST1WG05TFqfbpsF
We will provide respondents with a concise summary of our findings as well as access to a new Application Server market study conducted by an independent party.
Thank you.
Ashesh Badani
Product Marketing
Sun Java System Application Server

I thought I resolved some bugs with updating JSC continuously; BUT there is a bug I just do not like very much:
Make changes to a project, save them with "save all" command; then run the changed project and surprise surprise, the changes do ont take effect, instead I get the old version of the project. Far better is it afer recognizing such a bug to shut down and restart JSC with the intention of getting a natural refresh. No matter it gets worse, buttons are placed anywhere within a jsp page, just not located there where intended to be.
danny
http://www.work-at-home-profits.com

Two related questions: ColdFusion 10/Java applications and J2EE supported servers

I have two related questions:
1. CF10 and integration with Java Web applications
We have a couple of Java applications running on JRun and interfacing with CF9 applications. The JRun clusters were created through the JRun Admin and, apart from lack of Axis 2.0 support, have served us well for years now. And, as would be the case, the ColdFusion9/Java/Flash application is a critical public-facing application that the business uses for bidding on projects.
It appears that with ColdFusion 10 on Tomcat, we will not be able to run those Java applications on a Tomcat-CF10 JVM cluster. Is this correct? IF so, what are our options?
2. J2EE Application Servers supported by Adobe for CF10
Which of these is correct?
A. This URL (http://www.adobe.com/products/coldfusion-enterprise/faq.html) states "ColdFusion 10 supports IBM® WebSphere, Oracle® WebLogic, Adobe JRun, Apache Tomcat, and JBoss."
B. This URL (http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/coldfusion/pdfs/cf1 0/coldfusion10-support-matrix.pdf) states:
"J2EE application servers: WebLogic Server 10.3, 11.1, WebSphere Application Server 7, ND 7 JBoss 5.1, 6.0, 7.1.0"
I *think* "A" above is wrong re. support for Adobe JRun. It does not specify a version of Apache Tomcat unless it is simply referring to the custom version the comes with CF10.
Option "B" above shows no support of Adobe JRun or 'standard' Apache Tomcat.
Thanks,
Scott

Question 1 above was answered: "No support for Java web applications under CF10's custom version of Tomcat"
Question 2: No answer yet: Is Apache Tomcat (NOT Adobe's customized version) supported for CF10 J2EE deployment? I do not see any installation instructions on how to install CF10 on Apache Tomcat 6 or 7.
Is anybody using Apache Tomcat as their J2EE app servers and, again, NOT Adobe's customized/limited version?
Thanks,
Scott

Which application servers are J2EE 1.4 compliant?

After having some trouble to test a simple sayHello .ear created with Sun J2EE 1.4 reference implementation in app servers like WebSphere or WebLogic http://forum.java.sun.com/thread.jsp?forum=331&thread=535582 ...
Which application servers could the J2EE 1.4 sayHello stateless session bean sample .ear been deployed to? Or, which application servers out there are J2EE 1.4 compliant???
J2EE 1.4 compliant:
Sun Java Application Server 8 (coming with J2EE 1.4 RI) :-)
IBM WebSphere 6.0 developer preview
About to become J2EE 1.4 compliant:
JBoss.org JBoss +4.0 (about to get J2EE 1.4 compliancy)
Not at this time J2EE 1.4 compliant:
Bea WebLogic server 8.1
What about Tomcat, could you deploy an (J2EE 1.4) .ear there?
Any other application servers? Oracle?
Merten

Please see the link below for J2EE 1.4 compatible implementations.
http://java.sun.com/j2ee/compatibility.html
Tomecat is a web container so you could deploy J2EE web applications to Tomcat (war files).

Load balancing across multiple application servers not working with JCo RFC

We have a problem where inbound messages to the Mapping Runtime engine (ABAP -> J2EE) are not load balanced over application servers. However, load balancing does take place across server nodes within one application server.
Our system comprises of the following:
Central Instance (2 X server nodes)
Database Instance
2 X Dialog Instances (with 2 X server nodes each)
The 1st application server that starts is usually the one that is used for inbound messaging.
We have looked at the sap gateway configuration and have tried various options without much luck:
i.e.: local gateways vs. one central gateway, load balancing type by changing parameter gw/reg_lb_level, see: http://help.sap.com/saphelp_nw70/helpdata/EN/bb/9f12f24b9b11d189750000e8322d00/frameset.htm
Here are our release levels:
SAP_ABA     700     0012     SAPKA70012
SAP_BASIS     700     0012     SAPKB70012
PI_BASIS     2005_1_700     0012     SAPKIPYJ7C
ST-PI     2005_1_700     0005     SAPKITLQI5
SAP_BW     700     0013     SAPKW70013
ST-A/PI     01J_BCO700     0000          -
Any help would be greatly appreciated.
Many thanks

Tim
Did you follow the guide here:
How to Scale Up SAP Exchange Infrastructure 3.0
Learn what the most likely scaled system architecture looks like, and read about a step by step procedure to install additional dialog instances. The guide also walks you through additional configuration steps and the application of Support Package Stacks.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c3d9d710-0d01-0010-7486-9a51ab92b927
We followed this guide for XI3.0 and PI7.0 and works successfully!

Best practice for distributing/releasing J2EE applications.

Hi All,
We are developing a J2EE application and would like some information on the best
practices to be followed for distributing/releasing J2EE applications, in general.
In particular, the dilemma we have is centered around the generation of stub, skeleton
and additional classes for the application.
Most App. Servers can generate the required classes while deploying the EJBs in the
application i.e. at install time. While some ( BEA Weblogic and IBM Websphere are
two that we are aware of ) allow these classes to be generated before the installation
time and the .ear file containing the additional classes is the one that is uploaded.
For instance, say we have assembled the application "myapp.ear" . There are two ways
in which the classes can be generated. The first is using 'ejbc' ( assume we are
using BEA Weblogic ), which generates the stub, skeleton and additional classes for
the application and returns the file, say, "Deployable_myapp.ear" containing all
the necessary classes and files. This file is the one that is then installed. The
other option is to install the file "myapp.ear" and let the Weblogic App. server
itself, generate the required classes at the installation time.
If the first way, of 'pre-generating' the stubs is followed, does it require us to
separately generate the stubs for each versions of the App. Server that we support
? i.e. if we generate a deployable file having the required classes using the 'ejbc'
of Weblogic Ver5.1, can the same file be installed on Weblogic Ver6.1 or do we
have to generate a separate file?
If the second method, of 'install-time-generation' of stubs is used, what is the
nature/magnitude of the risk that we are taking in terms of the failure of the installation
Any links to useful resources as well as comments/suggestions will be appreciated.
TIA
Regards,
Aasif

Its much easier to distribute schema/data from an older version to a newer one than the other way around. Nearly all SQL Server deployment features supports database version upgrade, and these include the "Copy Database" wizard, BACKUP/RESTORE,
detach/attach, script generation, Microsoft Sync framework, and a few others.
EVEN if you just want to distribute schemas, you may want to distribute the entire database, and then truncate the tables to purge data.
Backing up and restoring your database is by far the most RELIABLE method of distributing it, but it may not be pratical in some cases because you'll need to generate a new backup every time a schema change occurs, but not if you already have an automated
backup/maintenance routine in your environment.
As an alternative, you can Copy Database functionality in SSMS, although it may present itself unstable in some situations, specially if you are distributing across multiple subnets and/or domains. It will also require you to purge data if/when applicable.
Another option is to detach your database, copy its files, and then attach them in both the source and destination instances. It will generate downtime for your detached databases, so there are better methods for distribution available.
And then there is the previously mentioned method of generating scripts for schema, and then using an INSERT statement or the import data wizard available in SSMS (which is very practical and implements a SSIS package internally that can be saved for repeated
executions). Works fine, not as practical as the other options, but is the best way for distributing databases when their version is being downgraded.
With all this said, there is no "best practice" for this. There are multiple features, each offering their own advantages and downfalls which allow them to align to different business requirements.

Multiple Database in J2ee Application

Dear sirs,
I have a J2ee application which is running in JBOSS Server. The Data tier is MySql.
Now the scenario is like this,
We are having two clients, and the clients have different sub users. The clients are using two seperate database for the same application. Now the application is working in two different servers assigned for each clients. Now we are planning to integrate it to a single application . I would like to know whether
1. Is it possible to specify the JNDI names for more than one database in the deployement descriptor?
2. if it is then, how can we instruct the container to lookup dynamically for the appropriate database based on the user logged in to the application .
I am planning to setup a new DB for the users information sothat the container can select the appropriate DB based on the user logged in...
Thankyou,
Sudheesh K S,

Did you setup multiple realms correctly?
Steps to follow (depending on your version of OID):
- define second realm (OIDDAS)
- Reconfigure SSO (login.jsp)
- enable hosting (wwhost script)
- add second subscriber (addsub script)
- change searchbase (OIDDAS/ldif)
All documented in the Oracle® Internet Directory Administrator's Guide,
10g Release 2 (10.1.2) at
http://download-west.oracle.com/docs/cd/B14099_19/idmanage.1012/b14082/toc.htm
Pay attention to chapter 7 and appendix G

Porting j2ee application from Weblogic to Oracle 10g AS

What are the common guidelines/consideration when we port a J2EE application on Oracle Application server 10g. from WebLogic 8.1. If you have some inputs on pin points/guidelines/Architecture decisions that we might need to consider when we port a J2EE application on different J2EE application server
I got the link for app server migration but it is broken :
http://www.oracle.com/consulting/technology/appserver_migration_ds.pdf
Our application uses the following J2EE components
1. JDBC 2.0
2. JNDI
3. DAO
4. EJB
5. JMS
6. JAAS
7. JAVA Mails.
8. Servlets, JSP’s
I can think following point that needs to take care while porting
1. Its deployment configuration vis-a-vis the apps on top
2. The APIs it exposes (actually the information it allows the apps to pass in to the framework
3. The data it encapsulates (in order to be app-server agnostic; does it need to be now exposed to apps?)
Some J2EE specific areas
1. JNDI usage and exposure to apps 2. Properties files/XML files
2. Location specification 3. Resource bundle location specification
4. EJB deployment descriptors
5. Class/jar references between wars and ears
6. Jar sharing model across ears
7. Class loader differences across app-servers
8. JMS settings (queues, topics, factories, durability etc)
9. UI tags 10. Startup services
11. Managed services (JMX)
12. Security context passing
13. Clustered configurations if any and how they port across app-servers
Thanks
Santosh Maskar

This document is very old.
Take a look at the recent migration guide in the Oracle AS 10.1.3.1 documentation
http://download-uk.oracle.com/docs/cd/B31017_01/migrate.1013/b31269/toc.htm

Application use survey

-- found a survey that may be of interest for some - it is available here:
http://www.tech-surveys.net/Start15.aspx
it surveys which applications servers and database applications are mostly used throughout US and Canadian companies.
The results which will be available for these entering the survey - these results will help you gauge where your organization stands versus your peers in terms of the implemented technologies and can help you realign skills best on the technologies and applications that are mostly used.
In addition, there is are prizes for those entering the survey.
Just FYI.
Joe
Got my Tech Job at
http://www.tech-centric.net

Any survey that solicits input from unknown volunteers is useless.

Selection of application servers

Recently, much of application is being covered with J2EE/WAS Servers like weblogic.
But in ACID heavy big database transactions in large telecom company's customer and billing database,
I wonder which is better selection between was and tuxedo(TP).
for SOA and Service Bus integration, WAS may be mandatory
but for oltp transaction, I wonder which is better between
the following options
option1, WAS(Presentation) + TP(biz logicfor big oltp transaction)
Option2, WAS only(Preseantation + j2EE/EJB,Bizlogic)

Hi Chanyoung,
With regards to references for using a web server or J2EE app server (your was?) and a TPM, that would be something you would need to work through your BEA account team. We have many customers in many industries using a combination of J2EE and TPMs and as I think I mentioned before, this is the recommendation that Gartner made in a report a year or two ago.
As for examples of failed web server only solutions, that will be harder to get as failures often don't see the light of day. Perhaps others reading this can contribute some examples.
I have read nothing that indicates TPMs will be relegated to the dust pile of outdated technologies. TPMs have a long history of providing highly scalable and highly reliable infrastructure for building and deploying applications. J2EE app servers such as WLS are catching up, but still don't provide the reliability and scalability of TPMs. When they do, other considerations as I mentioned earlier will still come into play as to which solution to choose.
I see TPMs playing a valuable role in OLTP for the foreseeable future. Things like an ESB focus on a different problem. TPMs host your business services and provide your application infrastructure. ESBs provide service infrastructure that allows you to more easily and flexibly utilize the business services built on TPMs and other application infrastructures.
Regards,
Todd Little
BEA Tuxedo Engineering

J2EE APPLICATION ON OAS10G AND J2EE APPLICATION ON IBM Websphere

Hi All,
As you all know that there are many application servers in the market for deploying the application so I just want to know why we all choose Oracle Application Server 10g for deploying J2ee application and why some choose IBM Websphere for deploying J2ee application. Is there any doc which specifies that Deployng J2ee application on Websphere is better than OAS 10g.
Regards
Kumar

If you have to choose an architecture now, I would advice not to choose Oracle Application Server, but BEA WebLogic. On Oracle Open World I learned that Oracle will stop developing on OC4J, so WebLogic seems the smarter choise.
To either choose weblogic or websphere has to do with a lot more then just the J2EE specs. It also has to do with knowledge of your collegues (who have to support either of these products), company strategy, etc. Therefore this question cannot be answered that easy.
Personally I think an all Oracle stack is just fine, WebLogic has a richer featureset then WebSphere (AFAIK). WebSphere is not a bad product though.

J2EE Application server for CCA (Solaris 10)

I know that CCA doesn't document Sun GlassFish Enterprise Server v2.1 for Solaris SPARC as a supported J2EE application server, but has anyone installed CCA with the newer versions of Sun GlassFish application servers? Can you share you experience if you've used other application servers on Solaris 9 or 10. Our install of CCA will use Windows for Telephony servers and the J2EE app/session servers on Solaris 10.
Thanks in advance!

We will be doing an install in January with planned Solaris 10 running Weblogic 10.3 and the Application servers will be running windows.
The Matrix does not show this combination but we have mixed Linux web servers in the past with Windows application server OK with a 10G back end DB.

Version control J2EE applications

Hello,
This is a fairly general question regarding version control. I want to bundle a J2EE application as an EAR file and deploy it to a number of different application servers. On every server where the EAR file is deployed, I would like to keep a history of what version of the J2EE application was installed, and when.
For example, say I have 3 servers (S1, S2, and S3), and want to deploy myApp.ear to all 3. Something's gone wrong (the application doesn't deploy to S2), and we're not aware of any problems until users start complaining. How can I check which version of my J2EE application has been successfully deployed on each server at a glance?
Are there any logs kept regarding J2EE deployment histories in the Enterprise Manager? How are these logs maintained? Are they self maintianing?
We currently have a custom made installation system for non J2EE apps that adds an entry to a table on one of our databases that records the username, date, time and version of a particular application when it is installed. We can't use this custom installation system when we bundle our applications as EARs.
Basically, how have you guys (other professionals) managed software releases with EARs? Can you recommend any methods, articles, or utilities? Does 10g Application Server provide any means of managing releases?
Thanks for your input!

Hello,
You bring up an interesting problem. At the moment 10.1.2 does not have anyway to manage releases, however there is a simple way out of this.
When creating the ear file (i.e. pre-deploy), you can add a versions.txt to your ear file which will have the version number of the application. In regards to the time-stamp, the application server will create a directory (under applications and application-deployments) for the respective deployment. In conjunction with the version.txt and the timestamp of your files on the OS, you could get a pretty good feel of releases.
If you implement your own logging into a file system (which means writing more code), you could do this as well.
You could also write a servlet that starts-up and writes this data to the DB, however please note that this write will happen every time you start the OC4J instance, so this might not be a good solution.
Hope this helps.
Deepak

Help on java/j2ee application development framework

hello java-gurus,
I'm new to java and is working in java for just 15 months.i want to know more about the platform/framework which is used in the development of java/j2ee projects.To be more specefic i want to build a java/j2ee project .
-->The project will be located in the eclipse workspace.
-->The eclipse will be connected to the cvs and will save the latest code in the repository.
-->The project will have a build.xml file which on being executed
will check the latest code from cvs.
will run j unit test.
on success from the junit it will compile the project.
It will make a .war,.ear etc file..
It will then be deployed in the application server.
So i want to make a framework of this kind.So i want help from u guys how to proceed.
I'm just a starter with ant scripts .know how to clean,build and make war files ..I also know about eclipse like connecting to cvs,generating ant script from it etc..
i'm also comfortable with struts,java,servlet etc..
So do give me some guidelines how to proceed .
thanks

Hello,
i'm working in project same style of what you want. here are details :
- eclipse for development - lomboz plugins for j2ee support.
- using subclipse plugin for svn support checkout and commit, in case of cvs i think it is default in eclipse.
- the framework is Struts, which is a very very powerful J2EE framework.
- eclipse plugin lomboz supports creating and deal with struts project
it also offers GUI for configuring struts xml files.
- lomboz contains plugin for creating and define application servers and containers like tomcat and jboss, so you can compile, run and debug your code from your eclipse.
- i use many other tools for creating UML diagrams and ERD diagram and reflect contents to existing projects.
i think with struts,eclipse and lomboz you need nothing else.

2 J2EE RI servers which communicate with each other

Hi all,
I'm wondering whether the following scenario is possible, and if so, of course I would like to now how I have to achieve it.
I want to run two j2ee ri application servers on two different machines. What I want, is that the applications on the two different servers can communicate with each other.
Any help on this will be greatly appreciated.

Greetings,
that does the lookup, so I have the bean clasees in
the classpath of the project (is that what you
ment?).In addition to the bean classes, the client needs the stub files generated by deploytool - the reason for the ClassCastException is due to that the cast actually gets made against the server stub(s) which, in this case, isn't available to the client. The stubs are generated during deployment and have the same name as your interfaces with the suffix '_impl' (implementation). The first dialog of the deployment wizard has the option to "Return client jar" - select it (a checkbox) and add the resulting jar file (has the same name as your .ear file with the ending 'Client.jar'), to your client's CLASSPATH (just mount it as a filesystem in Forte4J ;). This file has the stubs along with the rest of your bean's associated classes.
Can you help? I'm realy stuck.I hope this helps.
Thanks.
Oded "Shushu" HasidiRegards,
Tony "Vee Schade" Cook

J2EE Application Servers Survey

Similar Messages

Maybe you are looking for