As you might already know Sun announced End Of Life for JDK 1.4 to be October 2008. Since WebLogic 8.1 runs only on JDK 1.4, BEA announced EOL for WebLogic 8.1. This is the statement from BEA Support site.
After the EOL date, WebLogic Server and WebLogic Platform configurations that run on J2SE 1.4.2 will no longer be running on fully supported configurations. BEA will continue to support these environments on a best-effort basis. Lack of support from an SDK vendor, however, may limit BEA’s ability to resolve certain SDK-related issues.
If you care about not using EOL products in your Application stack, you have 2 Options and a dilemma to deal with.
Option 1:
The obvious, migrate your application to JDK 5 or greater. This depends on the complexity of your application, for all you know all you have to do is deploy your application to WebLogic 9.x or 10.x and fingers crossed your application with run flawlessly.
Option 2:
If you believe you cannot make the October 2008 deadline, contact Sun and see if you can extend your support contract to include support for JDK 1.4. If you have some extra budget you probably would go with this easiest no hassle option, atleast for now.
Dilemma:
Well, the dilemma is if you upgrade to WebLogic 9.x or 10.x, you will have to upgrade again in October 2009, because both these versions of WebLogic only support Java 5 which is going EOL in October 2009.
There is no WebLogic version out there that supports JDK 6 yet, from my reliable sources WebLogic Server 10.3 is slated for release end of July, 2008.
My Suggestion:
If your application uses the base WebLogic Server, I would wait for 10.3 release and migrate to it hoping that 10.3 is released on time. You will have 3 months to migrate giving you an ample time to test and deploy your application. If you are using WebLogic Platform products like WebLogic Portal or WebLogic Integration you may have to wait for those products to be released, since these Platform products are usually released a few months after the base WebLogic Server is released.
If you cannot wait until 10.3 is relased, BEA made the Technology Preview of WebLogic Server 10.3 available. You can download it and test your application to make sure you do not see any major issues.
Powered by FireStats
Weblogic 10.3 is available to download from oracle technology network.
I need a urgent help . We are trying to Migrate our Application from weblogic 8.1 to 10.0 . But i am unable to identify the correct procedure and the major changes that are needed for this migration to become a success . I have been working on this for like 1 month but no success till now .
I fear there might be fingers pointing at me soon from the management as its taking a lot of time . I have had no prior experience with Weblogic sever and its deployment and i am the only one who is working on this project , i tried to follow the BEA Guide for the upgrade but it didnt help much caz its more a generic one and doesnt fir in the way our application is configured.
I am sending a summary of the steps I have taken so far and the issues and concerns I have.
First a Glimpse of our current Environment.
Weblogic server 8.1
JSP’s Front Tier
EJB’s , MDB’s middle Tier
I Planet for authentication purposes
Middlegen-2.0 for Autogenerating CMP’s.
Oakgrovesystems For Workflows within our application
SQL sever 2005
ANT 1.6
Windows XP Professional
Velocity 1.5 Used to generate Template Type Files that are used to generate Stored Procs, Html Files etc
We are planning to migrate to Weblogic 10.0
Here are the steps I have taken so far:
1. Ran the build & deployment procedure in the WLS 8.1 environment.
2. Installed WLS 10.0 in parallel and changed the environment variables pointing to JDK 5.0 and BEA10.
3. Tried to Upgrade the deployed domain using the WebLogic Domain upgrade Wizard. But it says the selected domain directory is already a version 10.0 directory since the config.xml file inside the config folder is version 10.0 xml file, But it does not contain the configurations of the original configuration file that we had for 8.1.
4. When I start the weblogic server using the startweblogic.cmd file that resides in the bin folder of wls 10 , it comes in running mode.
5. After starting the admin console I found datasources, Deployments are all empty. in wls 8.1 we were only concerned with configuring security realm manually but not datasources,Deployments
5. After I try to manually install the ear files and the Datasources [The server starts throwing numerous errors like SQL_SERVER is not a legal value for GeneratorType. The value must be one of the following: Sequence, SequenceTable , I have attached the log file for reference.
6. For the above problem i ran the DDConverter Utility of wls 10.0 which when run across the wrong generators-type tags, creates the correct xml you need to deploy to your app to weblogic.
7. I tried to follow the Bea guide for the upgrade but it’s not helpful enough in our case.
I am unable to find the correct path towards this deployement.
1. Do we need to change our build.xml file and the respective targets inside it?
2. Does the config.xml file needs change and how to do it?
3. During the deployment I found that our build file is pointing to the lib directory of wls 8.1 which has weblogic.jar . That I guess needs a definite change.
4. Do we need middlegen upgrade?
5. Do we need Velocity Upgrade?
5. The startweblogic.cmd now resides in bin directory prior to this it used to reside in the root directory of wls 8.1 and it has numerous references to pointbase server. So in what ways this script must be modified.
Please let me know incase more information is required regarding the current environment or anyother such related things.
[...] 1.4 and slowly every one in the team moved on to different things. Now due to EOL and other issues (see my post on JDK 1.4 and WebLogic 8.1 EOL) all the the applications co-hosted in the Datacenter would like to Upgrade and he is forced to [...]