This document provides an overview of migrating applications from Oracle Containers for J2EE (OC4J) to WebLogic Server (WLS). It discusses the benefits of migrating such as improved management and features in WLS. The process involves choosing the easiest application to migrate first, moving it to JDeveloper 11g for configuration, deploying to WLS 11g, fixing any errors, running full testing, and learning WLS terminology and management practices. Migrating involves addressing differences in classpaths, deployment descriptors, libraries, web and EJB applications between the two platforms.

2. LiranZelkha VP BD ScaleBase

3. OC4J to WLS Migration

4. AgendaWhat do we gainHow to do it

5. What Do We Gain

6. Should We MigrateOC4J is dying, if not deadWLS is the new kingWLS is so much betterBetter managementMore featuresMigration is difficultTakes a long timeDoesn’t have to…

7. How Do We Do It

8. The Process

9. Choose Easiest ApplicationTry to answer the following questions:OC4J version:iAS version:JavaJava version?Does the application open internal threads?JDBC?J2EE Technologies in use:ServletsJSPJSFEJBVersionXMLDoes the application parse XML files on its own?If yes, how?XSL?JMSJNDI lookupJCA

10. Choose Easiest Application – Cont’Security:Single Sign On?JAZN?Build a custom JAZN module?ADFADF?BC4J?TopLink? DatabaseOracle version?RAC enabled?OC4J configurationCustom start parameters for the OC4J instance?Shared libraries?JARs in LIB directory?Management tool integration?Deployment?WARJAREAR

11. Choose Easiest Application – Cont’Choose the application with the minimal number of proprietary features usedSome applications can’t be migrated easilyOld (not supported Java version, ADF migration)Proprietary features (will be discussed later)

12. Move To JDev11gGreat toolIntegrated with WLSCan generate EAR, JAR, WAR files for WLS for youIncluding proprietary filesRemember to have enough RAM on your developers machinesNote:If you use ADF – migration might be necessary (depending on your ADF version)

13. Try To Move To WLS11gConfigurationData sourcesJMS sourcesSecurityJust run your appProbably deployment issues will arise…

14. Fix ProblemsDeployKeep your fingers crossedIdentifying failuresFailed to start app in WLSExceptions in server consoleCan’t access web applicationCan’t see EJBs in JNDI view

15. Fix Problems – Class PathClasspath issuesAre you using app-inf/lib?Are you using lib/endorsed?XML libraries issuesHave you used standard XML parser or Oracle?

16. Deployment DescriptorsMissing info in weblogic.xml, weblogic-ejb-jar.xml filesWeblogic.xml replaces orion-web.xmlNeeded for resource/ejb referencesClass loader managementContext root for standalone WAR files

17. Deployment Descriptors – Cont’Weblogic-ejb-jar.xml replaces orion-ejb-jar.xmlUsed for JNDI namingNeeded for resource/ejb referencesMDB configurationweblogic-cmp-rdbms.xml used for CMP beans

18. LibrariesToplinkXML librariesLibraries that come with WLS might collide with your appJSFLog4J

19. Web AppOC4J auto exposed servletsWLS does not. Make sure servlet and servlet-mapping tags exist in your web.xml fileSSO configurationNo more jaznConfiguration is done at WLS level, not web-appSSL configuration

20. EJB AppCMP beans migration is a painEJB3 migration is much easier…JNDI naming is differentJNDI tree is differentUse JNDI view to recognize namesIf app client is usedClasspath is differentnew InitialContext() parameters are different

21. Run Full QAMake sure full tests run on the web applicationSame as releasing a new version

22. 2 Words On WLS TerminologyDomainManaged ServerAdmin ServerManaged Server

23. Eco SystemScriptsManagement – install app, start server, stop server, etc.WLST against domain server – vs. opmnctlSecuritySSL certificates, users

24. Eco SystemAdmin trainingForms/Reports/BI

25. Q&A