Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
How do I set up the data source for an entity bean using CMP.?
I would like to know how I can bind a database to a entity bean that is using container managed persistence in wen sphere
Asked:
2
1 Solution
Greetings HonorGod,
I have a web application that has been deployed to production . It uses some entity beans. One of the entity beans in production environment is not being persisted properly because it is mapped to a development database and also using an incorrect table name that was mispelled by the developers.
My understanding is that it is using some default mapping which was done at development time in the application.
I would like to correct this information (hopefully through the WAS Admin console) so that the entity bean uses the correct schema and table name .
Is there a place in the admin console where I can change the persistence information and also correct the misspelled table name so that it uses the correct schema and the correct table that is in production.
I know when we migrate a regular web application(without any entity beans) to production we just change the datasources so that they refer to production schemas and everything works because the code uses a resource reference in the jndi look up.
Hope this helps
I have a web application that has been deployed to production . It uses some entity beans. One of the entity beans in production environment is not being persisted properly because it is mapped to a development database and also using an incorrect table name that was mispelled by the developers.
My understanding is that it is using some default mapping which was done at development time in the application.
I would like to correct this information (hopefully through the WAS Admin console) so that the entity bean uses the correct schema and table name .
Is there a place in the admin console where I can change the persistence information and also correct the misspelled table name so that it uses the correct schema and the correct table that is in production.
I know when we migrate a regular web application(without any entity beans) to production we just change the datasources so that they refer to production schemas and everything works because the code uses a resource reference in the jndi look up.
Hope this helps
Yikes. I'm sorry, I completely forgot about this question. Please forgive me.
If the configuration information about the database is hard coded in the application, then the application needs to be changed.
On the other hand, if the information about the database is in the datasource, then you can:
- login to your admin console
- click on & expand the Resources section (left frame)
- click on & expand the JDBC section
- click on the Datasource link
- click on the Datasource name to be modified
- make the changes
- test the connection
- and save your changes.
Good luck
If the configuration information about the database is hard coded in the application, then the application needs to be changed.
On the other hand, if the information about the database is in the datasource, then you can:
- login to your admin console
- click on & expand the Resources section (left frame)
- click on & expand the JDBC section
- click on the Datasource link
- click on the Datasource name to be modified
- make the changes
- test the connection
- and save your changes.
Good luck
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Can you give move information / details?
Thanks