2. LiranZelkha VP BD ScaleBase

3. OC4J to WLS Migration

4. Agenda What do we gain How to do it

5. What Do We Gain

6. 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…

7. How Do We Do It

8. The Process

9. 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

10. 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

11. 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)

12. 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)

13. Try To Move To WLS11g Configuration Data sources JMS sources Security Just run your app Probably deployment issues will arise…

14. 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

15. 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?

16. 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

17. 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

18. Libraries Toplink XML libraries Libraries that come with WLS might collide with your app JSF Log4J

19. 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

20. 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

21. Run Full QA Make sure full tests run on the web application Same as releasing a new version

22. 2 Words On WLS Terminology Domain Managed Server Admin Server Managed Server

23. Eco System Scripts Management – install app, start server, stop server, etc. WLST against domain server – vs. opmnctl Security SSL certificates, users

24. Eco System Admin training Forms/Reports/BI

25. Q & A