Upload
liran-zelkha
View
5.441
Download
0
Embed Size (px)
Citation preview
LIRAN ZELKHA VP BD SCALEBASE
OC4J to WLS Migration
Agenda
• What do we gain• How to do it
WHAT DO WE GAIN
Should We Migrate
• OC4J is dying, if not dead– WLS is the new king
• WLS is so much better– Better management– More features
• Migration is difficult– Takes a long time– Doesn’t have to…
HOW DO WE DO IT
The Process
Chose easiest
application
Move to JDev11g
Try to move to
WLS
Fix any problems that arise
Run Full QA
Choose Easiest Application• Try to answer the following questions:
– OC4J version:– iAS version:– Java
• Java version?• Does the application open internal threads?• JDBC?
– J2EE Technologies in use:• Servlets• JSP• JSF• EJB
– Version• XML
– Does the application parse XML files on its own?– If yes, how?– XSL?
• JMS• JNDI lookup• JCA
Choose Easiest Application – Cont’– Security:
• Single Sign On?• JAZN?• Build a custom JAZN module?
– ADF• ADF?• BC4J?• TopLink?
– Database• Oracle version?• RAC enabled?
– OC4J configuration• Custom start parameters for the OC4J instance?• Shared libraries?• JARs in LIB directory?• Management tool integration?
– Deployment?• WAR• JAR• EAR
Choose Easiest Application – Cont’
• Choose the application with the minimal number of proprietary features used
• Some applications can’t be migrated easily– Old (not supported Java version, ADF migration)– Proprietary features (will be discussed later)
Move To JDev11g
• Great tool• Integrated with WLS• Can generate EAR, JAR, WAR files for WLS for you– Including proprietary files
• Remember to have enough RAM on your developers machines
• Note:– If you use ADF – migration might be necessary
(depending on your ADF version)
Try To Move To WLS11g
• Configuration– Data sources– JMS sources– Security
• Just run your app• Probably deployment issues will arise…
Fix Problems
• Deploy– Keep your fingers crossed
• Identifying failures– Failed to start app in WLS– Exceptions in server console– Can’t access web application– Can’t see EJBs in JNDI view
Fix Problems – Class Path
• Classpath issues– Are you using app-inf/lib?– Are you using lib/endorsed?
• XML libraries issues– Have you used standard XML parser or Oracle?
Deployment Descriptors
• Missing info in weblogic.xml, weblogic-ejb-jar.xml files
• Weblogic.xml replaces orion-web.xml– Needed for resource/ejb references– Class loader management– Context root for standalone WAR files
Deployment Descriptors – Cont’
• Weblogic-ejb-jar.xml replaces orion-ejb-jar.xml– Used for JNDI naming– Needed for resource/ejb references– MDB configuration– weblogic-cmp-rdbms.xml used for CMP beans
Libraries
• Toplink– XML libraries
• Libraries that come with WLS might collide with your app– JSF– Log4J
Web App
• OC4J auto exposed servlets– WLS does not. Make sure servlet and servlet-
mapping tags exist in your web.xml file• SSO configuration– No more jazn– Configuration is done at WLS level, not web-app
• SSL configuration
EJB App
• CMP beans migration is a pain– EJB3 migration is much easier…
• JNDI naming is different• JNDI tree is different– Use JNDI view to recognize names
• If app client is used– Classpath is different– new InitialContext() parameters are different
Run Full QA
• Make sure full tests run on the web application
• Same as releasing a new version
2 Words On WLS Terminology
Domain
Admin Server
Managed Server
Managed Server
Eco System
• Scripts– Management – install app, start server, stop
server, etc.– WLST against domain server – vs. opmnctl
• Security– SSL certificates, users
Eco System
• Admin training• Forms/Reports/BI
AQ&