on 03-11-2005 9:21 PM
Hi,
I have a J2EE application in which an EJB uses 3 variables which allow it to connect to another environment (url, user and pwd)
For now , I am passing the variables as environment properties of the EJB but this forces me to redeploy the application every time I need to change the parameters.
I don't have a database for this application.
Do you have any other suggestions ?
Thanks.
Thierry
Please consider using the "Configuration Manager" service provided by the SAP Web AS.
The related help and tutorial can be found at the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/f9/1cda5c00a048c58dcdcf8e841cbd2d/frameset.htm
Hope this helps.
Regards,
Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thierry,
The answer depends on how often you want to change these parameters in your application. If you often change these variables, you might consider passing them at runtime as parameters to a business method in the bean. If you change them rarely, you can use the environment entries (as you do it) but you are right that this requires redeployment of your application every time.
There are plans in the next releases to add the option to administer these environment entries from the administration tools. Until then, you can use one of the suggested solutions above.
Best regards,
Viliana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thierry,
you could store the parameters in your JNDI context and expose an interface to change them. Some kind of dirty flag might be useful as well.
Regards,
Heiko
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.