Tuesday, 18 March 2014

Weblogic Server Migration Process




Web logic 12.1.2 Domain Reconfiguration


WebLogic 12.1.2 Domain Reconfiguration 
In this post you will learn basic WebLogic domain upgrade processes for WebLogic 12c(12.1.2) version and migration processes.
  1. Install last JRockit or JDK-7
  2. Install WebLogic 12.1.2
  3. Backup old WebLogic domain folder with its AdminServer and managed servers
  4. Move the old domain folder to weblogic 12.1.2 domains folder. The reconfiguration wizard updates the domain on selected folder, will not create a new weblogic 12.1.2 domain folder.
  5. Start reconfig.sh or reconfig.cmd
1
2
Windows: ORACLE_HOME\oracle_common\common\bin
UNIX: ORACLE_HOME/oracle_common/common/bin


 Start Re-Configuration Wizard

6. Select the  old domain which moved to under WebLogic 12c domains folder.


Select old domain folder

In this step configuration wizard, updates the files and folders, and reconfigures WLS Infrastructure successfully.

Before:
1
2
3
  <name>test_domain</name>
  <domain-version><strong>10.3.6.0</strong></domain-version>
  <security-configuration>
After:
1
2
3
  <name>test_domain</name>
  <domain-version><strong>12.1.2.0.0</strong></domain-version>
  <security-configuration>

7. Select domain mode and Java Version: I chose other JDK which I preferred Oracle-JRockit.


Choose Java Version

8. Update current datasources. If you are going to upgrade the database or move it this feature will be helpful, otherwise, this feature is useless. Select “Don’t convert”


Datasources Configuration – In this screen there is a non-functional bug exists, it is pointed with a red circle.

On the datasources screen, if you select “Convert to Gridlink” or “Convert to RAC multi datasource”  option, the wizard will add one more screen for the next step.

I realized when you select “Convert to Gridlink” option, there is a minor non-functional bug which is the label name for this step’s screen on the left. I reported this to Oracle WebLogic team. Nothing serious, just this screen is not mostly used, and I thought this screen not tested properly.

9. Test JDBC datasources: For my test domain, I have developed an application which uses and connects two databases, one is MySQL and the other one is Oracle.



Test JDBC Datasources

10. Advanced Configuration: In this step, choose “Managed Servers, Clusters and Coherence” and “Deployment Services” options. It’s better to select these options for the upgrade process. These means we will see 6 additional reconfiguration wizard screens.


Advanced Configuration: Managed Servers, Clusters, Coherence, Deployments and Services

 11. Managed Servers:  In this step you can list managed servers and its current listen addresses and ports. You can add, further managed servers in this screen.
Note: Do not use “Add” button, always prefer clone button for your current managed servers.


Customize Managed Servers

IMPORTANT NOTE: In this screen, I have got null pointer exception and could not move on to the next step, just click on cancel and start from the beginning. REMEMBER delete the current folder, and copy it from the original again.

12. Clusters: In this step, you can configure your current cluster and add new cluster. If you don’t have any cluster just skip this step by clicking next.


Configure Clusters

13. Assign servers to clusters: In this step, assign managed servers to the clusters.

14. Assing servers to Machines: In the managed server screen I have cloned one more managed server and assigned this under my admineer.local machine.


Assign Servers to Machines

15. Deployments targeting: Deployments must be targeted to the new managed servers or clusters.


Deployments Targeting
16. Service Targeting: The JDBC and other services must be edited and reconfigured in this step. I have two datasource and reconfigured again according to my new WebLogic 12.1.2 domain.


Service Targeting

17. Configuration Summary: In this last step, the reconfiguration settings are finished. Just summarize the settings again, and if something is wrong go back (remember you can directly reach the relevant screen by clicking on text on the left) and fix them.


Reconfiguration Progress

NOTE: At the reconfiguration progress, you can see warning like this: “CFGFWK-40318: Invalid or missing JDBC datasource connection parameters”. If you tested your datasource and got successful result, just ignore this warning.
IMPORTANT NOTE: If you press on the “reconfig” button there is no chance to go back again, the only method is start from beginning.
18. Just click on “reconfig” button, then “Oracle WebLogic Server Reconfiguration succeeded”. Existing test_domain updated and upgraded successfully.
Domain Reconfiguration Applied Successfully

19. Exciting moments! Go to the your new WebLogic 12.1.2 domain and start admin server. After the start process, you should see the new WebLogic version as below with 12.1.2.0.0 version, in the admin server start logs.

WebLogic domain upgrade post processes for WebLogic 12c(12.1.2) version.

1. Start the upgraded domain’s admin server.
2. Login to new admin console.

WebLogic 12.1.2 admin console has a problem for Internet Explorer 10 (IE 10). The login-GC-page-BG.png picture could not loaded in IE10. Here is the screen caputure of the problem. For Firefox and Chrome there is no problem.


WebLogic 12.1.2 Admin Console IE-10 Problem
Relevant Picture’s Source: http://localhost:7001/console/framework/skins/wlsconsole/images/login-GC-page-BG.png
In login.css the current code does not work for IE-10.

CSS
1
2
3
4
5
#top {
background: url("../framework/skins/wlsconsole/images/login-GC-page-BG.png") repeat-x scroll left top #FFFFFF;
height: 600px;
min-width: 920px;
}

2. Advanced user can do the upgrade process by wlst with these commands below. By using WLST, you don’t have any chance to edit current domain.

Shell
1
2
3
4
5
6
# Open the domain for upgrade.
wls:/offline> readDomainForUpgrade('c:/domains/my_domain')
# Save the updated domain.
wls:/offline/my_domain> updateDomain()
# Close the domain.
wls:/offline/my_domain> closeDomain()

3. NodeManager Configuration:
After the domain upgrade, I don’t recommend to migrate previous nodemanager data to the new WebLogic 12.1.2 domain.
  1. Run  $WEBLOGIC_12.1.2_HOME\wlserver\server\bin>setWLSEnv.cmd
  2. Fow Windows, start command prompt with “run as administrator” then run  $WL_HOME\wlserver\server\bin\ installNodeMgrSvc.cmd
  3. Copy default DemoIdentity jks from your domain, to weblogic 12.1.2 nodemenager/security folder.According to my local environment, I have did: cp C:\Middleware\wls12c\user_projects\domains\test_domain\security C:\Middleware\wls12c\oracle_common\common\nodemanager\security
  4.  For 12.1.2 domain configuration connect wlst and run nmEnroll WLST command.
nmEnroll() Process
PowerShell
1
2
3
4
5
6
C:\Middleware\wls12c\wlserver\common\bin>wlst.cmd
wls:/offline> connect()
Please enter your username :weblogic
Please enter your password :
Please enter your server URL [t3://localhost:7001] :t3://localhost:7001
wls:/test_domain/serverConfig> nmEnroll("C:/Middleware/wls12c/user_projects/domains/test_domain","C:/Middleware/wls12c/oracle_common/common/nodemanager")

5. Start new nodemanager windows service that we created in step-2.
That’s it! I have upgraded my 10.3.6 WebLogic domain to WebLogic 12.1.2 domain by using Domain Reconfiguration Wizard. And my local application worked without any problem.


Anymore, my application works on WebLogic 12.1.2 Application Server

For the mission critical applications, the processes would not be like these simple. So, always progress your upgrade plan with your experienced team


Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)