Hi Everybody,
Few days back, i came across situation where have to change passwords for SOA suite datasources. So today we will discuss about by default Data-sources on Oracle SOA 11G.
There are a number of component services installed and configured to use an Oracle Weblogic JDBC Data Source out of the box. In this post we will discuss about those data sources and how to modify their passwords at the RDBMS level and also the Oracle Weblogic mid-tier level
By default the Oracle SOA Suite 11G installs and configures a number of JDBC data sources at the mid-tier Weblogic level. They are also used by Oracle Fusion Applications. These are;
Few days back, i came across situation where have to change passwords for SOA suite datasources. So today we will discuss about by default Data-sources on Oracle SOA 11G.
There are a number of component services installed and configured to use an Oracle Weblogic JDBC Data Source out of the box. In this post we will discuss about those data sources and how to modify their passwords at the RDBMS level and also the Oracle Weblogic mid-tier level
By default the Oracle SOA Suite 11G installs and configures a number of JDBC data sources at the mid-tier Weblogic level. They are also used by Oracle Fusion Applications. These are;
In order to change the passwords for any or all of these connections there are two steps to follow;
STEP 1. ORACLE WEBLOGIC LEVEL PASSWORD CHANGE
1) Login to http://host.domain:port/console as the weblogic user.
2) On the left is the Environment structure. Expand the Domain if it is not already, then click on SERVICES
3) Now click into JDBC
4) Then click into Data Sources to see a table on the right of all the Oracle Weblogic managed JDBC data sources.
5) Click on the name for one of the above data sources. In this example we'll assume the first one, BAMDataSource
6) You're now in the BAMDataSource configuration page, showing multiple sub tabs. Click on Connection Pool.
7) Here you'll see the jdbc driver and a 'properties' field. The username will be visible, ie: user=TEST_ORABAM.
NOTE: These user or RDBMS schema names will have been defined during the configuration stage of installation. The RCU or Repository Creation Utility will have requested you give prefixes such as DEV, TEST, UAT, QA, PROD etc - depending on your situation.
8) Below the 'properties' field you will see the 'password' field. The password will be displayed as dots at this time.
9) In order to change the password at the Weblogic level, you have to provide the new password which you defined using Step 2 below. Ensure that sufficient backups have been taken and that you are able to make a password change in a suitable downtime window. At a convenient outage time, enter the new password from Step 2, then click the SAVE button.
10) Ensure the Target Weblogic managed servers (soa_server(x) for example) are started and then with the new password changed, click on the MONITORING tab, then the TESTING subtab.
11) You can now select a managed server and click the TEST DATA SOURCE button for it to login as the user of that data source (TEST_ORABAM) and make a select from dual to validate the connection.
Upon success you have now changed the passwords at the RDBMS level, and also at the mid-tier level for that component.
STEP 1. ORACLE WEBLOGIC LEVEL PASSWORD CHANGE
1) Login to http://host.domain:port/console as the weblogic user.
2) On the left is the Environment structure. Expand the Domain if it is not already, then click on SERVICES
3) Now click into JDBC
4) Then click into Data Sources to see a table on the right of all the Oracle Weblogic managed JDBC data sources.
5) Click on the name for one of the above data sources. In this example we'll assume the first one, BAMDataSource
6) You're now in the BAMDataSource configuration page, showing multiple sub tabs. Click on Connection Pool.
7) Here you'll see the jdbc driver and a 'properties' field. The username will be visible, ie: user=TEST_ORABAM.
NOTE: These user or RDBMS schema names will have been defined during the configuration stage of installation. The RCU or Repository Creation Utility will have requested you give prefixes such as DEV, TEST, UAT, QA, PROD etc - depending on your situation.
8) Below the 'properties' field you will see the 'password' field. The password will be displayed as dots at this time.
9) In order to change the password at the Weblogic level, you have to provide the new password which you defined using Step 2 below. Ensure that sufficient backups have been taken and that you are able to make a password change in a suitable downtime window. At a convenient outage time, enter the new password from Step 2, then click the SAVE button.
10) Ensure the Target Weblogic managed servers (soa_server(x) for example) are started and then with the new password changed, click on the MONITORING tab, then the TESTING subtab.
11) You can now select a managed server and click the TEST DATA SOURCE button for it to login as the user of that data source (TEST_ORABAM) and make a select from dual to validate the connection.
Upon success you have now changed the passwords at the RDBMS level, and also at the mid-tier level for that component.
STEP 2. RDBMS LEVEL PASSWORD CHANGE
Depending on the component data source identified in Step 1 above, you need to login to your rdbms layer as that schema username and password. eg; TEST_ORABAM in this case. If you are not the DataBase Administrator for this system then please work with your DBA if you do not have sufficient RDBMS level administration rights to login as this user.
1) Login as the data source user using any relevant tool like SQL*_Plus, SQL Developer
To change the password for this user the sql statement is;
Depending on the component data source identified in Step 1 above, you need to login to your rdbms layer as that schema username and password. eg; TEST_ORABAM in this case. If you are not the DataBase Administrator for this system then please work with your DBA if you do not have sufficient RDBMS level administration rights to login as this user.
1) Login as the data source user using any relevant tool like SQL*_Plus, SQL Developer
To change the password for this user the sql statement is;
ALTER USER TEST_ORABAM identified by Welcome1;
COMMIT;
where <username> is the data source user= property, and <newPassword> is the new password you've chosen.
Once the commit command has reported success then the password has been changed at the RDBMS level.
You can now complete step 1 above and provide this new password to the data source password property field. You can now start-up the respective Oracle Weblogic managed servers to ensure everything is satisfactory.
I Hope this will help you in your assignment.You can write me on middlewaresolution1@gmail.com.
Enjoy Working with Middleware.
Regards,
Ajinkya Vichare
ajinkya-vichare.blogspot.com
Have you ever thought about adding a little bit more than just your articles?
ReplyDeleteI mean, what you say is valuable and all. But imagine if
you added some great pictures or videos to give your
posts more, "pop"! Your content is excellent but with images and videos, this blog could undeniably be one of the very best in its field. Superb blog!
My homepage used pool tables chicago
Thanks for sharing this great information I am impressed by the information that you have on this blog. Same as your blog i found another one Oracle SOA . Actually I was looking for the same information on internet for Oracle SOA and came across your blog. I am impressed by the information that you have on this blog. It shows how well you understand this subject, you can learn more aboutOracle SOA . By attending Oracle SOA Training .
ReplyDeleteThanks for sharing this great information I am impressed by the information that you have on this blog. Same as your blog i found another one Oracle Fusion Financials . Actually, I was looking for the same information on internet for
ReplyDeleteOracle Fusion Manufacturing and came across your blog. I am impressed by the information that you have on this blog. It shows how well you understand this subject, you can learn more about Oracle Fusion Supply Chain Management Cloud .