Geek asks and answers

Best way to set up a corporate Java application

I have a set of EJBs and other Java classes that need to be configured differently based on the system environment in which they are deployed: production, testing, or laboratory. The configuration information includes data such as URLs and database connection information.

We would like to deploy the same exact product (EAR file) in each environment, and then determine where it is located and what its configuration is, without having to go to each deployment server in each environment to make changes.

What is the best way to configure all of these components in a centralized, reliable, and user-friendly way?

Thanks for your thoughts.

+3
source share
3

, IMHO, JNDI.

, , vars, :

  • : , .
  • JNDI- (. JBoss)
  • webadmin .
+2

/ . .

0

If you deploy the same EAR in three different instances of a specific container, you will have to edit the deployment settings because there is no way for the deployment process to have an idea of ​​which of your three versions you would like to use for a specific deployment.

Deployment options should go into JNDI entries, as Pierre-Yves said.

If I were you, I would establish that my script (Ant?) Deployment correctly populates JNDI entries depending on the environment you are deploying to.

0
source

More articles:


All Articles