Difference in application upgrade approaches from Weblogic 10.0 to Weblogic 10.3.6

Hi,
I am new to Weblogic 10.3.6. Till now I was using Weblogic 10 and now we are planning to migrate to Weblogic 10.3.
While going through the Oracle documentation, I came across 3 different approaches for application upgrade.
Choose one of the following ways to upgrade your Portal 9.2 or 10.0/10.2 application to 10.3:
Open an existing 9.2 or 10.0/10.2 portal application as a workspace in Workshop for WebLogic
Import an existing exploded 9.2 or 10.0/10.2 project into Workshop for WebLogic
Import an archived 9.2 or 10.0/10.2 project file into Workshop for WebLogic.
I know the steps to execute all the above mentioned appraoches, but I want to know the pros and cons of all of them to decide which one should I go with.
Please help.

Similar Messages

Upgrade approach from CRM 5.0 to CRM 7.0 w.r.t ISA applications

Hi All,
Currently we have a CRM 5.0, ECC 6.0 and NW7.0(+ Apache HTTP server 2.2.3) system landscape, where in we are running the ISA applications on the NW Java instance.
There will be a possible upgrade to CRM 2007.
So what would be the architectural differences during this updgrade with respect to ISA applications?
Will our ISA applications still run properly after the upgrade? what sort of dependecies/compatibilty issues will occur during this process. And what would be the solution approach for it.
Please let me know the necessary points to be taken careoff during the upgrade of CRM 5.0 to CRM2007.
Finally, is CRM2007 = CRM 6.0 or its CRM 7.0?
Please share your valuable inputs on this
Thanks,
Aman.

We did a similar upgrade. Very important to note: please follow the Best Practice documentation from SAP. This is very important for the ISA part.
Can you share with us the Best Practice Documentation? Is it a upgrade best practice or upgrade master or something else? Thanks.

Difference between JSF and JPF from WebLogic workshop

Hi i am new to JSF , currently i am working on JPF and i got a chance to work on JSF..
I feel that event drivent programming as same as JSF and In JPF.
Can any body explaine in detail difference between JSF and JPF
Thanks in Advance
Suneel.

JSF is Sun's MVC framework for web applications.
I've never heard of JPF, so it might not be part of Sun.

Porting j2ee application from Weblogic to Oracle 10g AS

What are the common guidelines/consideration when we port a J2EE application on Oracle Application server 10g. from WebLogic 8.1. If you have some inputs on pin points/guidelines/Architecture decisions that we might need to consider when we port a J2EE application on different J2EE application server
I got the link for app server migration but it is broken :
http://www.oracle.com/consulting/technology/appserver_migration_ds.pdf
Our application uses the following J2EE components
1. JDBC 2.0
2. JNDI
3. DAO
4. EJB
5. JMS
6. JAAS
7. JAVA Mails.
8. Servlets, JSP’s
I can think following point that needs to take care while porting
1. Its deployment configuration vis-a-vis the apps on top
2. The APIs it exposes (actually the information it allows the apps to pass in to the framework
3. The data it encapsulates (in order to be app-server agnostic; does it need to be now exposed to apps?)
Some J2EE specific areas
1. JNDI usage and exposure to apps 2. Properties files/XML files
2. Location specification 3. Resource bundle location specification
4. EJB deployment descriptors
5. Class/jar references between wars and ears
6. Jar sharing model across ears
7. Class loader differences across app-servers
8. JMS settings (queues, topics, factories, durability etc)
9. UI tags 10. Startup services
11. Managed services (JMX)
12. Security context passing
13. Clustered configurations if any and how they port across app-servers
Thanks
Santosh Maskar

This document is very old.
Take a look at the recent migration guide in the Oracle AS 10.1.3.1 documentation
http://download-uk.oracle.com/docs/cd/B31017_01/migrate.1013/b31269/toc.htm

Error upgrading from weblogic 7 to weblogic 10.3

We are upgrading app from weblogic 7 to 10.3. Thie app compiles ok and every page before the login is displayed successfully. When we try to login we are getting the following error:
Exception in thread "main" java.lang.AbstractMethodError: weblogic.xml.schema.binding.BeanCodecBase.getCompositor()Lweblogic/xml/schema/binding/ModelGroupCompositor;
     at weblogic.xml.schema.binding.BeanCodecBase.gatherContents(BeanCodecBase.java:299)
     at weblogic.xml.schema.binding.CodecBase.serializeFill(CodecBase.java:297)
     at weblogic.xml.schema.binding.CodecBase.serialize_internal(CodecBase.java:234)
     at weblogic.xml.schema.binding.CodecBase.serialize(CodecBase.java:193)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:192)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:178)
     at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:335)
     at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:304)
     at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:651)
     at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:209)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:146)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:473)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:459)
     at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:306)
     at com.workscape.aws.examples.weblogic.clientclases.PINService_PortType_Stub.authenticateUser(Unknown Source)
could someone advise how to fix this problem?
Thanks in advance

Hi,
Your EJB 2.1 application should deploy and run fine on WLS 10.3 without modification.
- Matt

Application upgrade does not work

Ever since I upgraded to 2.0.2, I have had nothing but problems. The latest is that now, I can't download any applications, or application upgrades directly from my phone. It says that I need to connect to my computer in order for the upgrade to download. But even when I connect to Itunes Store on my computer, the message on my phone still says "Unable to download application. It will be available for download when you log in to the iTunes store on your computer." But I'm already connected and logged on
GRRR Is anyone else having this issue?

DO NOT UPDATE ON THE PHONE ITSELF! Never do this! You risk bricking your iPhone and seeing the Silver Apple Logo of Death due to incomplete downloads and/or crashing! This has happened to me on my old iPhone as well as thousands of others. Use iTunes and iTunes only to update Apps!

Upgrade from Weblogic 10.3.1 to 10.3.3 Issues

Hi
We are in process of migrating/upgrading from Weblogic server 10.3.1 to 10.3.3.
A heavily distributed application is being migrated with high volume transaction on clustered environment.
Have anybody experienced any issues/ concerns when migrating from Weblogic 10.3.1 to 10.3.3?
Please share your experience.
Thanks
Edited by: user4151568 on Oct 28, 2011 8:55 AM
Edited by: user4151568 on Oct 28, 2011 8:55 AM
Edited by: user4151568 on Oct 28, 2011 8:55 AM

Hi,
Use the below link to upgrade from 10.3.5 to 10.3.6
https://gdgprasad.wordpress.com/2014/05/03/how-to-upgrade-web-logic-server-wls-10-3-5-to-10-3-6-in-windows-64-bit/
http://docs.oracle.com/cd/E24902_01/doc.91/e18840/upgrade_1036.htm#EOHWL193
How Can I Download Upgrade Installers for Oracle WebLogic Server (WLS)? [ID 1074946.1]
First try to upgrade your test Environment and then you can see if you face any issue or not.
Hope it helps

Upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration

Can anyone offer any advice to assist me in upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration 9.2.1?
Here are some nuances of the project:
* The JNDI, JDBC, & JMS server resources are secured; access is controlled by Deployment Descriptor run-as/security-role/... tags and custom CSPs
* The application is currently build for deployment using wlwBuild ant task (class in workshop.core.WlwBuildTask which is located in the 8.1.3 {weblogic.home}/workshop/wlw-ide.jar - so far I can't find this class/task in my 9.2.1 install)
* The following are the application characteristics (and utilized WLI features): multiple web apps, EJBs, JMS, Page flow/netUI, web services, WLI controls (process, java, transformation), XMLBeans
* One of the project goals is to not make any functional changes and modify as little code as necessary (the only expected justification for a modification is a) fallout out from the JVM 1.5 upgrade or b) something is no longer available in WLI 9.2)
I know there is a edocs page with a tutorial for upgrading from 8.1.4 or 8.1.5 to 9.2, but I am interested in knowing if anyone has insight on upgrading directly from 8.1.3?
Thanks in advance for any and all assistance.
Regards,
Andy Frank

just as a followup to my original message.. regarding the 8.1.4 install log that had all the warnings with the msi it expected and the different one it found... at the bottom of the log..this is what I got;
Property(S): SourcedirProduct = {AC76BA86-7AD7-1033-7B44-A81300000003}
MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 - Update 'KB408682' installed successfully.
MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 -- Installation operation completed successfully.
when i go into adobe reader -> help -> about i stillget 8.1.3

How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

Dear All,
I have one statement int weblogic 5.1 weblogic.propertis as follow,
weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
but after converting to weblogic 6.1 there are no corresponding statement in
the file config.xml. And when i start the new application, error occured.
what should I do?
The error message is:
<2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
.\config\tbcn\config.xml
<2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initializatio
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception

Dear Satya,
My weblogic propertis file as follow,
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=12345678
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
# TBCN EJB PROPERTIES
weblogic.ejb.deploy=\
C:/weblogic/myserver/AccountSB.jar, \
C:/weblogic/myserver/AddressEntryDet.jar, \
C:/weblogic/myserver/AddressEntry.jar, \
C:/weblogic/myserver/Affiliate.jar, \
C:/weblogic/myserver/ContactPerson.jar, \
C:/weblogic/myserver/ContactSB.jar, \
C:/weblogic/myserver/Factory.jar, \
C:/weblogic/myserver/FactorySups.jar, \
c:/weblogic/myserver/LoginUsers.jar, \
c:/weblogic/myserver/Member.jar, \
c:/weblogic/myserver/MemberQuotaUsage.jar,\
c:/weblogic/myserver/MemberToCategory.jar,\
c:/weblogic/myserver/Organization.jar, \
c:/weblogic/myserver/Person.jar, \
c:/weblogic/myserver/QuotaType.jar,\
c:/weblogic/myserver/Registration.jar, \
c:/weblogic/myserver/TempAccounts.jar, \
c:/weblogic/myserver/TempDomain.jar, \
c:/weblogic/myserver/UserAccount.jar, \
c:/weblogic/myserver/UserRole.jar, \
c:/weblogic/myserver/BuyerProducts.jar, \
c:/weblogic/myserver/Catalog.jar, \
c:/weblogic/myserver/Categories.jar, \
c:/weblogic/myserver/CategoryToCategory.jar, \
c:/weblogic/myserver/CountryToCategory.jar, \
c:/weblogic/myserver/InvitedMember.jar, \
c:/weblogic/myserver/ProductOrigin.jar, \
c:/weblogic/myserver/ProductOtherFee.jar,\
c:/weblogic/myserver/ProductSups.jar, \
c:/weblogic/myserver/Products.jar,\
c:/weblogic/myserver/ProductToCategory.jar, \
c:/weblogic/myserver/SecondaryQcEntry.jar, \
c:/weblogic/myserver/CodeClass.jar,\
c:/weblogic/myserver/ConfirmationSB.jar, \
c:/weblogic/myserver/PurchasedPackage.jar,\
c:/weblogic/myserver/RejectReasonCode.jar, \
c:/weblogic/myserver/ServiceOrder.jar,\
c:/weblogic/myserver/ServiceOrderLog.jar,\
c:/weblogic/myserver/ServiceOrderState.jar,\
c:/weblogic/myserver/ServiceOrderType.jar,\
c:/weblogic/myserver/ServicePackageDetails.jar, \
c:/weblogic/myserver/ServicePackage.jar, \
c:/weblogic/myserver/ServicePayment.jar, \
c:/weblogic/myserver/ServiceReqSB.jar, \
c:/weblogic/myserver/TAM.jar, \
c:/weblogic/myserver/SubscriptionEB.jar, \
c:/weblogic/myserver/PostingCategoryEB.jar, \
c:/weblogic/myserver/PostingBrowsedEB.jar, \
c:/weblogic/myserver/PostingInfoEB.jar, \
c:/weblogic/myserver/TransactionLogEB.jar, \
c:/weblogic/myserver/PostingSB.jar
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
weblogic.httpd.register.beanManaged=\
examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection pools:
#weblogic.jdbc.connectionPoolcreate.admin=joe,jill
# Read more about setting up and using connection pools in the
# developers guide for WebLogic JDBC at:
# http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
# TBCN JDBC CONNECTION POOL MANAGEMENT
weblogic.jdbc.connectionPool.oraclePool=\
url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=tbcn;password=ca91768
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
# WEBLOGIC DEMO CONNECTION POOL PROPERTIES
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# This connection pool uses the sample Cloudscape database shipped
# with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
# Uncomment to use:
#weblogic.jdbc.connectionPool.demoPool=\
# url=jdbc:cloudscape:demo,\
# driver=COM.cloudscape.core.JDBCDriver,\
# initialCapacity=1,\
# maxCapacity=2,\
# capacityIncrement=1,\
# props=user=none;password=none;server=none
# Add a TXDataSource for the connection pool:
#weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
# Add an ACL for the connection pool:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
# WEBLOGIC HTTP SERVLET PROPERTIES
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
# WebLogic offers different types of servlets for various uses.
# Classpath servlet registration
# The ClasspathServlet is used to serve classes from
# the system CLASSPATH. It is used by applets to load
# classes they depend upon, and is registered against
# the virtual name 'classes' here by default. This means
# you should set your applet codebase to "/classes".
# You can register multiple virtual names for this servlet.
# Note that it can also be used to serve other
# resources/files from the system CLASSPATH.
# Don't confuse the ClasspathServlet with the ServletServlet. The
# ClasspathServlet is used for serving classes for client-side Java only.
# The ServletServlet is used to invoke unregistered servlets.
# See the Administrators Guide "Setting up WebLogic as an HTTP server"
# http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
info.
weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
# We also set an open ACL for everyone to call the ClasspathServlet
# so that applets work without requiring further changes.
weblogic.allow.execute.weblogic.servlet.classes=everyone
# File servlet registration
# FileServlet searches below the documentRoot for the requested file
# and serves it if found. If the requested file is a directory,
# FileServlet will append the defaultFilename to the requested path
# and serve that file if found.
weblogic.httpd.register.file=weblogic.servlet.FileServlet
weblogic.httpd.initArgs.file=defaultFilename=index.html
weblogic.httpd.indexFiles=zh_TW/index.htm
# ServerSideInclude servlet registration
# SSIServlet searches below the documentRoot for the
# requested .shtml file and serves it if found.
weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
# Example URL: http://localhost:7001/portside/welcome.shtml
# for the file /weblogic/myserver/public_html/portside/welcome.shtml
# PageCompileServlet (used by JHTML)
# See the information below under WebLogic JHTML
# JSPServlet (used by JSP)
# See the information below under WebLogic JSP
# ServletServlet registration
# Allows unregistered servlets in the servlet classpath (see Servlet
# reload properties below) to be r

Upgrade IDSM2 from 4.1(5)S225 to 5,1 using application partition

can i upgrade an IDSM2 (WS-SVC-IDSM2-BUN)in a 6513 from 4.1(5)S225 to 5.1 by copying the 5.1 application partition to the sensor
[from the cisco userguide]
Chapter 10 Configuring the Sensor Using the CLI
Reimaging Appliances and Modules
Reimaging the IDSM-2
This section contains the following topics:
Catalyst Software, page 10-124
Cisco IOS Software, page 10-126
Catalyst Software
To reimage the application partition, follow these steps:
Step 1 Obtain the application partition file from Software Center on Cisco.com and copy
it to an FTP server.
Step 2 Log in to the switch CLI.
Step 3 Boot the IDSM-2 to the maintenance partition:
cat6k> (enable) reset module_number cf:1
Step 4 Log in to the maintenance partition CLI:
login: guest
Password: cisco
Step 5 Reimage the application partition:
[email protected]# upgrade ftp://user@ftp server IP/directory
path/image file
Step 6 Specify the FTP server password.
After the application partition file has been downloaded, you are asked if you
want to proceed:
Upgrading will wipe out the contents on the hard disk. Do you want to
proceed installing it [y|n]:
Step 7 Type y to continue.
When the application partition file has been installed, you are returned to the
maintenance partition CLI.
Step 8 Exit the maintenance partition CLI and return to the switch CLI.
Step 9 Reboot the IDSM-2 to the application partition:
cat6k> (enable) reset module_number hdd:1
Step 10 When the IDSM-2 has rebooted, check the software version.
Step 11 Log in to the application partition CLI and initialize the IDSM-2.
See Initializing the Sensor, page 10-2, for the procedure.
IF NOT, THEN IS THERE A SHORT CUT FROM 4.1 to 5.1 ?

Just wanted to clarify some things.
As Scott has already confirmed you can re-image using the method described and following Scott's advice on what additional updates to install.
BUT understand that any configuration you have your 4.1 sensor will be lost during that method of re-imaging to 5.1.
Another alternative is to first upgrade from 4.1(5)S225 to 5.0(1), and then to upgrade to 5.1(1).
The upgrade to 5.0(1) will convert the 4.1 configuration into a compatible 5.0 format.
I saw another post you made implying that you had to downgrade back to 4.1(5)S189 to do the 5.0(1) upgrade. This is not the case. You can upgrade directly from your current 4.1(5)S225 to 5.0(1).
You can install the IPS-K9-maj-5.0-1-S149.rpm.pkg file directly on your current 4.1(5)S225 sensor.
When S225 was installed on your 4.1(5) sensor, it also placed in storage the corresponding S225 update for your 5.0 sensor.
So when IPS-K9-maj-5.0-1-S149.rpm.pkg is installed on the sensor it will detect that stored off S225 for 5.0 and install it at the same time.
So once installed you will be immediately at 5.0(1)S225.
Once at 5.0(1)S225, then you can upgrade directly to 5.1(1) using the IPS-K9-min-5.1-1d.pkg upgrade.
(NOTE: 5.1-1d file was created to fix some upgrade bugs, but still installs the same 5.1(1) files as the original 5.1(1) upgrade package).
So you will wind up at 5.1(1)S225.
Now at this point I would recommend installing at least one later signature update (S226 or higher in your case) BEFORE installing the 5.1(1p1) patch.
And AFTER the signature update, then install the 5.1(1p1) Engineering Patch (contact the TAC for this patch).
Because of this specific upgrade path, the best way to avoid some issues is to install at least one signature update before installing the 5.1(1p1) patch. The signature update helps to ensure the sensor is ready for the 5.1(1p1) upgrade. Some of the files needed for the 5.1(1p1) upgrade have been seen to not get carried forward properly in the upgrade from 5.0(1) to 5.1(1), but a signature update corrects those issues.
NOTE: This precaution of installing the signature update BEFORE the 5.1(1p1) is only needed when upgrading from 5.0(1) to 5.1(1). If imaging directly to 5.1(1) using the maintenance partition, then the 5.1(1p1) can be installed before a signature update without an issue.
Once 5.1(1p1) is up and running and monitoring packets and generating alarms, then additional signature updates can be installed afterwards.

Migrating applciation from weblogic to oracle 9i application server(OC4J)??????

Hi,
I am migrating my ejb application from weblogic to oracle 9i application server.What changes are needed to be made in code and what configuration changes are required.
In my application i use a couple of session beans wherin a session bean calls the method of the other session bean which acceses the database.I am using a jdbc thin driver for the database connection. is it possible for a session bean to call a method of another session bean which access the database??This concept works well in weblogic where the current application is running.
The problem is that while migrating the application to the orion server, it gives an OrionCMTException ...
memory leak..etc.
Could any one clarify.
Thanks in advance!!!

Hi Avi and Harrison,
Cease Fire avi!!!!.First of all let me clear the issue of posting the same problem twice.Well, when i mentioned the problem the first time , i found the title session bean deployment was not right and few people would look into it as it was a common problem so i thought it would be appropriate if i mentioned the title correctly , so i posted the query again with the change in title.
Now coming to the answer for ur questions.
The platform used is MS Windows NT.
The (OC4J) version is 1.0.2.2.1.
I am not using JDeveloper.
The database is oracle 8i and i am using the thin driver.
The beans to be deployed are stateless session beans.
The client involved is a web client i.e a jsp application.
The first session bean is as follows.
import java.sql.Connection;
import java.sql.Statement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.Vector;
import java.sql.Timestamp;
import java.rmi.RemoteException;
import java.util.Date;
import javax.ejb.*;
import javax.naming.*;
import initcontext;
import PrintMessage;
import JB_B2B_ERROR_PARSER;
* @stereotype SessionBean
* @homeInterface DB_UTILITYHome
* @remoteInterface DB_UTILITYRemote
public class DB_UTILITY implements SessionBean
     private SessionContext context;
private ResultSet rs = null;
private Statement stmt = null;
private Connection con = null;
private PrintMessage print = null;
public DB_UTILITY()
rs = null;
stmt = null;
con = null;
print = new PrintMessage();
     public Connection getConnection()throws RemoteException
          InitialContext initctx = null;
          Connection con = null;
          try
               initctx = initcontext.getContext();
               javax.sql.DataSource ds =
(javax.sql.DataSource)initctx.lookup("java:comp/env/jdbc/ePool");
               con = ds.getConnection();
//(javax.sql.DataSource)initctx.lookup("java:comp/env/jdbc/ePool");
catch(NamingException namingexception)
print.printUserMessage("DB_UTILITY", (new
Date()).toString(), "", namingexception);
throw new
EpoolException(JB_B2B_ERROR_PARSER.getErrorMessage("AppError",
"Epool-10001", "DB_UTILITY.getConnection"));
catch(SQLException sqlexception)
print.printUserMessage("DB_UTILITY", (new
Date()).toString(), "", sqlexception);
throw new
epoolException(JB_B2B_ERROR_PARSER.getErrorMessage("DBError",
JB_B2B_ERROR_PARSER.getSQLCode(sqlexception),
"DB_UTILITY.getConnection"));
catch(Exception exception)
print.printUserMessage("DB_UTILITY", (new
Date()).toString(), "", exception);
throw new
epoolException(JB_B2B_ERROR_PARSER.getErrorMessage("EpoolError",
"Epool10005", "DB_UTILITY.getConnection"));
          return con;
     public String getDate()throws RemoteException
          String Date=null;
          try
               con=getConnection();
               stmt=con.createStatement();
               rs=stmt.executeQuery("SELECT
TO_CHAR(SYSDATE,'YYYY-MM-DD HH:MI:SS') FROM DUAL");
               while(rs.next())
                    Date=rs.getString(1);
               stmt.close();
               con.close();
catch(SQLException sqlexception)
     print.printUserMessage("DB_UTILITY", (new
Date()).toString(), "", sqlexception);
throw new
EpoolException(JB_B2B_ERROR_PARSER.getErrorMessage("DBError",
JB_B2B_ERROR_PARSER.getSQLCode(sqlexception), "DB_UTILITY.getDate"));
catch(Exception exception)
     print.printUserMessage("DB_UTILITY", (new
Date()).toString(), "", exception);
throw new
EpoolException(JB_B2B_ERROR_PARSER.getErrorMessage("epoolError",
"Epool10005", "DB_UTILITY.getDate"));
finally
try
if(con != null && !con.isClosed())
con.close();
catch(Exception exception2)
stmt = null;
con = null;
          return Date;
     public void setSessionContext(SessionContext context)
          this.context = context;
     public void ejbActivate()
     public void ejbPassivate()
     public void ejbCreate()
     public void ejbRemove()
Also the xml files are as follows.
web.xml
<?xml version="1.0"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems,
Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>

<display-name>AddressBook Web Application</display-name>

<description>Web module that contains an HTML welcome page, and 4 JSP's.</description>

<welcome-file-list>
<welcome-file>B2B_COUNTRY_CODE.jsp</welcome-file>
</welcome-file-list>
<ejb-ref>
<ejb-ref-name>SB_B2B_COUNTRY_CODEHome</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>SB_B2B_COUNTRY_CODEHome</home
<remote>SB_B2B_COUNTRY_CODERemote</remote>
</ejb-ref></web-app>
Application.xml
<?xml version="1.0"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN" "http://java.sun.com/j2ee/dtds/application_1_2.dtd">
<application>
<display-name>Country Code</display-name>
<module>
<ejb>epool_CountryCode-ejb.jar</ejb>
</module>
<module>
<web>
<web-uri>epool_CountryCode-web.war</web-uri>
<context-root>/epool_CountryCode-web</context-root>
</web>
</module>
</application>
ejb-jar.xml:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
<ejb-jar>
<description>epool_CountryCode</description>
<enterprise-beans>
<session>
<display-name>CountryCode Session
Bean</display-name>
<ejb-name>SB_B2B_COUNTRY_CODERemote</ejb-name>
<home>SB_B2B_COUNTRY_CODEHome</home>
<remote>SB_B2B_COUNTRY_CODERemote</remote>
<ejb-class>SB_B2B_COUNTRY_CODE</ejb-class>
<session-type>Stateless</session-type>
<ejb-ref>
<description>EJB Epool DButility</description>
     <ejb-ref-name>DB_UTILITYRemote</ejb-ref-name>
               <ejb-ref-type>Session</ejb-ref-type>
               <home>DB_UTILITYHome</home>
               <remote>DB_UTILITYRemote</remote>
          </ejb-ref>
          <ejb-ref>
          <description>EJB Entity Bean</description>
<ejb-ref-name>EB_B2B_COUNTRY_CODERemote</ejb-ref-name>
               <ejb-ref-type>Entity</ejb-ref-type>
               <home>EB_B2B_COUNTRY_CODEHome</home>
          <remote>EB_B2B_COUNTRY_CODERemote</remote>
          </ejb-ref>
</session>
<session>
<display-name>DbUtility Session Bean</display-name>
<ejb-name>DB_UTILITYRemote</ejb-name>
<home>DB_UTILITYHome</home>
<remote>DB_UTILITYRemote</remote>
<ejb-class>DB_UTILITY</ejb-class>
<session-type>Stateless</session-type>
</session>
<entity>
<ejb-name>EB_B2B_COUNTRY_CODERemote</ejb-name>
     <home>EB_B2B_COUNTRY_CODEHome</home>
     <remote>EB_B2B_COUNTRY_CODERemote</remote>
     <ejb-class>EB_B2B_COUNTRY_CODE</ejb-class>
     <persistence-type>Container</persistence-type>
     <prim-key-class>EB_B2B_COUNTRY_CODEPK</prim-key-class>
     <reentrant>False</reentrant>
     <cmp-field>
     <field-name>country_code_desc</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>phone_format_flag</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>country_code</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>active_date</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>date_created</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>active_flag</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>country_phone_code</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>country_tax_percent</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>sort_order</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>date_modified</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>user_created</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>user_modified</field-name>
     </cmp-field>
     <resource-ref>
     <description></description>
     <res-ref-name>jdbc/ePool</res-ref-name>
     <res-type>javax.sql.DataSource</res-type>
     <res-auth>Container</res-auth>
     </resource-ref>
</entity>
</enterprise-beans>
<assembly-descriptor>
     <container-transaction>
          <method>
               <ejb-name>EB_B2B_COUNTRY_CODERemote</ejb-name>
               <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
</container-transaction>
<security-role>
<description>Users</description>
<role-name>users</role-name>
</security-role>
</assembly-descriptor>
</ejb-jar>
The session bean which uses the above session bean is as follows.
import javax.ejb.SessionContext;
import javax.ejb.SessionBean;
import java.sql.*;
import javax.naming.Context;
import java.sql.Timestamp;
import java.util.Vector;
import initcontext;
import DB_UTILITYHome;
import DB_UTILITYRemote;
import EB_B2B_COUNTRY_CODEHome;
import EB_B2B_COUNTRY_CODERemote;
import EB_B2B_COUNTRY_CODEPK;
* @stereotype SessionBean
* @homeInterface SB_B2B_COUNTRY_CODEHome
* @remoteInterface SB_B2B_COUNTRY_CODERemote
public class SB_B2B_COUNTRY_CODE implements SessionBean
     private SessionContext context;
     * Sets the context of the bean
     * @param context The Bean's Context
     public Vector selectCountryCode(String query,String
countquery, String pagenos) throws Exception
          Context ctx = initcontext.getContext();
          Connection con=null;
          Vector records=new Vector();
          int pageno=Integer.parseInt(pagenos);
          int min=(pageno-1)*10;
          int max=pageno*10;
          int counter=0;
          boolean recordsfound=false;
          try
               DB_UTILITYHome home =
(DB_UTILITYHome)ctx.lookup("java:comp/env/DB_UTILITYRemote");
               DB_UTILITYRemote remote =
(DB_UTILITYRemote)home.create();
               con=remote.getConnection();
               Statement stmt = con.createStatement();
               ResultSet rscount =
stmt.executeQuery(countquery);
               while(rscount.next())
                    int temp=rscount.getInt(1);
                    int pagecount=temp;
                    pagecount=pagecount/10;
                    if((temp%10)>0)
                    pagecount=pagecount+1;
                    records.addElement(""+pagecount);
               ResultSet rs = stmt.executeQuery(query);
               while(rs.next())
                    counter++;
                    if(counter>min && counter<=max)
                         String row[]=new String[8];
                         recordsfound=true;
                         row[0]=rs.getString(1);
                         row[1]=rs.getString(2);
                         row[2]=rs.getString(3);
                         row[3]=rs.getString(4);
                         row[4]=rs.getString(5);
                         row[5]=rs.getString(6);
                         row[6]=rs.getString(7);
                         row[7]=rs.getString(8);
                         records.addElement(row);
          con.close();
          catch(Exception e)
               System.out.println("Error in selecting Country
Code "+e);
               throw new Exception("Error in selecting Country
Code "+e);
          return(records);
     public void insertCountryCode(String country_code, String
country_code_desc, String country_phone_code, String
phone_format_flag,String active_flag, String sort_order,String
country_tax_percent)throws Exception
          Context ctx = initcontext.getContext();
          Double Sort_Order=null;
          Double cntry_tax_prct=null;
          if(sort_order!=null && sort_order.length()>0)
          Sort_Order=new Double(sort_order);
          if(country_tax_percent!=null &&
country_tax_percent.length()>0)
          cntry_tax_prct=new Double(country_tax_percent);
          String user_created=null;
          Timestamp date_created=null;
          Timestamp active_date=null;
          String user_modified=null;
          Timestamp date_modified=null;
          try
               DB_UTILITYHome dbhome =
(DB_UTILITYHome)ctx.lookup("java:comp/env/DB_UTILITYRemote");
               DB_UTILITYRemote dbremote =
(DB_UTILITYRemote)dbhome.create();
               user_created=dbremote.getUser();
date_created=Timestamp.valueOf(dbremote.getDate());
               active_date=date_created;
               EB_B2B_COUNTRY_CODEHome home =
(EB_B2B_COUNTRY_CODEHome)ctx.lookup("java:comp/env/EB_B2B_COUNTRY_CODER
emote");
               EB_B2B_COUNTRY_CODERemote remote =
(EB_B2B_COUNTRY_CODERemote)home.create(country_code, country_code_desc,
country_phone_code,active_flag, phone_format_flag,user_created,
date_created, active_date, Sort_Order, user_modified,
date_modified,cntry_tax_prct);
          catch(Exception e)
               System.out.println("Error in Creating COUNTRY
Code "+e);
               throw new Exception("Error in Creating COUNTRY
Code "+e);
     public void setSessionContext(SessionContext context)
          this.context = context;
     public void ejbActivate()
     public void ejbPassivate()
     public void ejbCreate()
     public void ejbRemove()
The jsp client which acces the beans is as follows.
<BODY >
<%@ page language="java" %>
<%@ page import="java.sql.*" %>
<%@ page import="initcontext" %>
<%@ page import = "java.util.*" %>
<%@ page import="DB_UTILITYHome"%>
<%@ page import="DB_UTILITYRemote"%>
<%@ page import="javax.naming.*"%>
<%Connection con=null; %>
<script src="search_getvalues.js">
</script>
<form name=frm1>
<%! int intCount,intI,intRowCount,intJ;
String strtname=new String();
String strhidden=new String("txthdn");
     Statement st;
     ResultSet rs;
     ResultSetMetaData rmeta;
....%>
<%
try
     Context ctx = initcontext.getContext();
     DB_UTILITYHome dbhome =
(DB_UTILITYHome)ctx.lookup("java:comp/env/DB_UTILITYRemote");
     DB_UTILITYRemote dbremote = (DB_UTILITYRemote)dbhome.create();
     con=dbremote.getConnection();
     st=con.createStatement();
     rs=st.executeQuery(strsqlquery);
     rmeta=rs.getMetaData();
intCount=rmeta.getColumnCount();
....... %>
</form>
</BODY>
</HTML>
The resulting exception generated is as follows:
D:\oc4j\j2ee\home>java -jar orion.jar
Auto-unpacking
D:\oc4j\j2ee\home\applications\epool_CountryCode\build\epool_CountryCod
e.ear... done.
Auto-unpacking
D:\oc4j\j2ee\home\applications\epool_CountryCode\build\epool_CountryCod
e\epool_CountryCode-web.war... done.
Auto-deploying epool_CountryCode (New server version detected)...
Auto-deploying epool_CountryCode-ejb.jar (No previous deployment
found)... done.
Error deploying
file:/D:/oc4j/j2ee/home/demo/messagelogger/messagelogger-ejb.jar homes:
No javax.jms.Destination found a
t the specified destination-location (jms/theTopic) for
MessageDrivenBean com.evermind.logger.MessageLogger
Oracle9iAS (1.0.2.2.1) Containers for J2EE initialized
Auto-deploying epool countryCode example (New server version
detected)...
************************1
************************2
COUNT QUERY :SELECT COUNT(COUNTRY_CODE) FROM BAP_COUNTRY_CODE
QUERY :SELECT
COUNTRY_CODE,COUNTRY_CODE_DESC,COUNTRY_PHONE_CODE,PHONE_FORMAT_FLAG,COU
NTRY_TAX_PERCENT ,SORT_ORDER,ACTIVE
FLAG,ACTIVEDATE FROM BAP_COUNTRY_CODE order by COUNTRY_CODE
Error in selecting Country Code java.rmi.RemoteException: Error
(de-)serializing object: com.evermind.sql.OrionCMTConnec
tion; nested exception is:
java.io.NotSerializableException:
com.evermind.sql.OrionCMTConnection
JB:Error in selecting country cd java.lang.Exception: Error in
selecting Country Code java.rmi.RemoteException: Error (d
e-)serializing object: com.evermind.sql.OrionCMTConnection; nested
exception is:
java.io.NotSerializableException:
com.evermind.sql.OrionCMTConnection
Error in Selecting Records
OrionCMTConnection not closed, check your code!
LogicalDriverManagerXAConnection not closed, check your code!
(Use -Djdbc.connection.debug=true to find out where the leaked
connection was created)
Auto-unpacking
D:\oc4j\j2ee\home\applications\epool_CountryCode\build\epool_CountryCod
e.ear... Error unpacking: IO Error:
The system cannot find the path specified
Error updating application epool_CountryCode: Unable to find/read
assembly info for D:\oc4j\j2ee\home\applications\epool_C
ountryCode\build\epool_CountryCode (META-INF/application.xml)
But if the DBUTILITY session bean is changed to a simple bean and accessed the code works fine and i am able to retrieve the data.Is the problem there because u one session bean cannot access a database connection method from another one or could it be because of the driver???
I hope i am clear.Please revert back in case any more references are needed.
Thanks in advance!!!!!!

How to migrate a full J2EE application from WebLogic to NetWeaver?

I have an independent J2EE application which can be run on WebLogic successfully. Now, I want to migrate it to the platform of NetWeaver. Could you tell me how to do with it? And where can I find the jar files of the application I deployed?
Thank you very much!

Have you tried the "exploded" format?
          Also, do you mean Weblogic 6.1 (sp2?).
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/
          "adurthy" <[email protected]> wrote in message
          news:[email protected]..
          >
          > HI All,
          >
          > I am trying a migrate a application Jsp application with taglibs from
          tomcat 4.0
          > to weblogic 6.2
          >
          > I tried the example way but none seems to work
          >
          > any help or articles are appreciated
          >
          > thanks
          > sivaji

Migration from Weblogic 8.1 SP1 server to Sun Java Application Server 8

Hi,
I have to migrate an existing application from Weblogic 8i to Sunone Application Server 8.
Can anyone please help me to know the kind of problems encountered in such a migration.
Also, If i have to port an application which uses 'Mssql' as the backend in weblogic and migrate it to sunone server and use Oracle as backend what r the changes to be made??
Also, If any weblogic specific api's or tag libraries are used then what r the changes to be made at the time of migration.?
Thanks in advance
Geeta

The type of issues you will encounter migrating this app depends on its complexity and how observant the programers were to writing portable code.
You will need to determine how compatible Mssql is to Oracle.
There may be changes you will need to make in the app deployment descriptors for this data.
You will need to replace the weblogic specific API's and tags.
This may require class substition, or writing emulators for the
APIs, or rewriting the code to not use these APIs.
The AVK can help you identify such portability issues.

Moving web-application from WebLogic 10.0.0 to 10.3.3 - EJB Exception

Hello all,
I've moved my web-application from weblogic 10.0.0 to the new platform with Weblogic 10.3.3. After this I had some JMSEceptions (unable to run JMS methods inside of servlet or EJB) and they were fixed. For now I got new exception:
####<07.12.2012 16:03:06 FET> <Info> <EJB> <pc-XXXXXX> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-00340877198035A73969> <1354885386932> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@14df37f threw exception: javax.ejb.EJBTransactionRolledbackException: EJB Exception: : java.lang.ClassCastException: com.XXX.XXXX.XXXXXX.persistence.OperatorBean cannot be cast to com.XXX.XXXX.XXXXXX.persistence.SwitchboardBean
at com.XXX.XXXX.XXXXXX.SwitchboardDataImpl.initialize(SwitchboardDataImpl.java:147) // itsSwitchboardBean = itsEntityManager.find(SwitchboardBean.class, switchboardNumber);
at com.XXX.XXXX.XXXXXX.SwitchboardDataImpl.create(SwitchboardDataImpl.java:86)
at com.XXX.XXXX.XXXXXX.SwitchboardDataEJB.create(SwitchboardDataEJB.java:64)
persistence.xml:
... <persistence-unit name="xxxSwitchboard_PU" transaction-type="JTA">
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<jta-data-source>jdbc/xxSwitchboard</jta-data-source>
<non-jta-data-source>jdbc/xxSwitchboard</non-jta-data-source>
<class>com.XXX.XXXX.XXXXXX.switchboard.persistence.OwnerBean</class>
<class>com.XXX.XXXX.XXXXXX.switchboard.persistence.OperatorBean</class>
<class>com.XXX.XXXX.XXXXXX.switchboard.persistence.SwitchboardBean</class>
<class>com.XXX.XXXX.XXXXXX.switchboard.persistence.CallBean</class>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
</persistence-unit>...
@Entity
public class OperatorBean extends OwnerBean
@ManyToOne(optional = true, fetch = FetchType.EAGER)
private SwitchboardBean switchboard;
@Entity
public class SwitchboardBean extends OwnerBean
@OneToMany(mappedBy = "switchboard", cascade = CascadeType.PERSIST, fetch = FetchType.LAZY)
private List<OperatorBean> itsOperators = new ArrayList<OperatorBean>();
Seems that it happened due to updating weblogic version (changes in jee, jms, ejb, jpa versions?). Could you please advice me how to fix this issue?
Thanks, Ilya

I belive there is no problems for this change, because the versions are the same for java at least for OaS, for weblogic you should see documentation. I think you can try deploying you app to new environment if you get any noclassdeffound error or something like it then you could have problems for versions.
Regards

Oracle Applications upgradation from 11.5.10.2 to 12.1.1 Parallel Upgrade

Hi All
We are planing to upgrade Oracle Application from 11.5.10.2. to 12.1.1.
Any expert advice?
Any recommendations?
Any Documents to follow?
to complete this phase successfully.
Is there any possibility that we run 2 Instances of 11i
1.Production and
2.Upgradation Instance.
Production stay live as we perform up gradation on other instance. But both servers have same updated data in Databases.
After up gradation completes we just shut down Production and Live Up-grade Instance.
regards,
Muhammad Salahuddin Manzoor.

Hi,
Please refer to these links/docs.
Note: 761570.1 - Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade
Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1
http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121upgrade.pdf
How can we reduced the patch time for u6394500.drv
How can we reduced the patch time for u6394500.drv
Note: 432597.1 - Reducing Down Time When Applying Patch for Oracle E-Business Applications 11i
Note: 225165.1 - Patching Best Practices and Reducing Downtime
After up gradation completes we just shut down Production and Live Up-grade Instance. This cannot be implemented as you are going to have live transactions during the upgrade, and you will need to have those transactions/data in the upgraded instance.
Thanks,
Hussein

Difference in application upgrade approaches from Weblogic 10.0 to Weblogic 10.3.6

Similar Messages

Maybe you are looking for