Migrating Application from weblogic 8.1 to weblogic 10.0 - Urgent

Migration
Edited by: user2647658 on Jan 5, 2009 8:49 PM

Mukul,
Thanks - I may appear as though I know what I'm doing, but I'm at a similar stage to you - I have to upgrade to 10.3 early next year and have so far only moved a single JVM for development use and checked my application works.
What I learnt was that 8.1 - 10.* is a huge step, various JMS/JDBC configuration options you were used to in 8.1 have now been simplified - for example, the JDBC DataSource and Connection pool you had in 8.1 has now been replaced by a single entity.
I'm pleased that the JDBC connection works - where does that SQL statement come from, as it looks like there's something not quite right about that.
Now that you have that working, make a backup of the folder and try to deploy one of your applications. First off, try to do this through the WebLogic console and see what errors, if any you get. Do you have jar files on the system classpath at all in WLS8.1? If you do, you may want to stick them in the lib folder of the domain just to get it working - I don't think that's the recommended approach, but it will do as a test to see if it works.
Upgrade Approach_
As for the approach to upgrade, I have the same issue (although only 6 - 8 developers to worry about) Within WLS 10.* there is a scripting language called WLST, and my aim is to create a base domain for development and once that's ready all the developers will delete the existing 8.1 domain and run the wlst script to create the new one, deploy all the applications and all will work nicely. That's just what I'm aiming for and I'm a long way off at the moment.
So, it will be an automated upgrade, but will be a brand new domain structure - 8.1 and 10 I think are so different, its difficult to make the change seamless - but WLST will help ( I hope )
How I upgrade my production environment with clusters etc I have no idea at the moment
let us know how you get on
Pete

Similar Messages

Does anyone have experience with migrating applications from iAS6.0 SP2 to SP3? Did it go smoothly or are there problems to be expected?

Hi,
I haven't. But, there are lots of changes from each service packs,
henceforth you may have to stick to what the documentation says to avoid
the errors that shoots up. Again, the errors depends upon how you have
coded your application. Please let me know if you have encountered any
errors and the messages for me to help you.
Regards
Raj
Peter Clijsters wrote:
Does anyone have experience with migrating applications from iAS6.0
SP2 to SP3? Did it go smoothly or are there problems to be expected?
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base!

Migrating application from tomcat 3 to tomcat 5

Hello everybody,
Does anyone have information about some kind of manual or tutorial with steps to migrate applications from Tomcat 3 to Tomcat 5??
Thanks a lot,
Johnny

What issues are you having? There have been some important changes between the Servlet and JSP specs between the two but most of these have been additions - nothing that will be too hard to handle.
Does your application use a database? If so there have been configuration changes between Tomcat 3 and 5 but for that the Tomcat 5 docs are very good at telling you what you need.
I would start by trying it and see where you get problems. I think it will be easier than you think, depending on how complicated your app is.

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

Migrating Application from Weblogic to JBOSS

Hi all,
I have an requirement to migrate Application running in Weblogic 8.1 to JBOSS, However my biggest problem is i do not have my JSP files and have only JSP converted Class files which are currently decomplied JAVA files and used in place of JSP. While migating to JBOSS my JSP converted JAVA files are erroring out.
Can any body please help me out. Thanks in advance for the help.

can be any body help me out with this issue

Mail no longer works after migrating applications from Mountain Lion

This weekend I bought a Mac Pro 2.1. I upgraded it to Lion then migrated all my files and applications from my iMac (running Mountain Lion). Now the Mail app doesn't work. I can't uninstall it and Software update says everything is up to date. How can I get my Mail app to work again? I guess I've somehow copied the Mail app from the Mountain Lion mac which is why it won't run.

No unfortunately after the OS is installed the installer package is removed so you'll need to go through the whole procedure again.
There is a way to save the installer and make a bootable flash drive you can install off of. You should be able to find the procedure if you search here or on the net.
regards

Link/checklist for migrating applications from Oracle 9i to Oracle 11g?Help

Hi all,
We need to perform an impact analysis on migratiing an application from Oracle 9i to Oracle 11g. Does any of you have a detailed checklist to follow, in terms of queries, PL/SQL statements, optimizer etc. etc., when attempting this migration. We require something more specific from the application point of view rather than a DBA point of view.
Additionally, we have queries written extensively with rule hints. Should there be a special consideration for the same since now we are moving to CBO in 11g
Even if any one has a link, that would help. Thank you so much!

Hi Nikhil,
Thanks Xaheer,You're welcome :)
I'm going through the link: http://download.oracle.com/docs/cd/E11882_01/server.112/e10819/toc.htm
But it still mentions stuff from a DBA angle. I need from an application angle.
Do I need to change my queries taht are current written with RBO? Do I need to change Pl/SQL blocks ?Please refer tech below notes:
*1)TROUBLESHOOTING: Server Upgrade Results in Slow Query Performance -- 160089.1*
*2)TESTING SQL PERFORMANCE IMPACT OF AN ORACLE 9i TO ORACLE DATABASE 10g RELEASE 2 UPGRADE WITH SQL PERFORMANCE ANALYZER -- 562899.1*
Before upgrading your production database, please perform upgrade of test database and do complete testing.
Hope helps
Regards,
X A H E E R

Problems after migrating application from 10.1.2 to 10.1.3

Hi,
I am encountering the following error while executing the application after migrating it from Jdeveloper10.1.2 to JDeveloper10.1.3. Could you please help me in this regard..
NOTIFICATION J2EE JSP0008 Unable to dispatch JSP Page : java.lang.NullPointerException
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:60)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:416)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:478)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:401)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:332)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:629)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)
Message was edited by:
user491067

Do you have the problem with all JSP pages, or only a few of them ?
Does it happen in the Embedded OC4J only ?
Could you try to deploy your application in the Standalone OC4J and test it from there ?
I had a similar issue where the Embedded OC4J was unnable to run big JSP pages.
There was no problem with the Standalone OC4J.
Hope this helps,
Didier.

Migrating Application from JSP 1.2 to JSP 2.2 and Servets 2.3 to Servlet 3

Hi,
I have an application which is built on JDeveloper 10.1.3.4.
So it uses default JSP and Servlet Runtime i e, JSP 1.2 and Servlets 2.3 versions.
But i want to migrate my application from those versions to Servlet 3.0 and JSP 2.2.
So i downloaded JSP 2.2 API jar and Servlet 3.0 jars and added to my Application Library.
I even removed JSP runtime and Servlet run time.
Now am unable to compile.
How should i migrate my application from older versions to newer.
Thanks,

a) you learn to use your tools properly
b) you fix what you did wrong
c) you feel smug for having done your job

Migrating Application from Planning 11.1.2.1 to 11.1.2.2

Gurus
I am trying to migrate a Planning application from Hyperion version 11.1.2.1 to version 11.1.2.2. Is there a way that I can use LCM? I have tried exporting the application from version 11.1.2.1 and importing it in 11.1.2.2 but all the forms are being registered as invalid.
The application also use business rules and LCM gave the following errors:
Error in migrating artifact, "/Global Artifacts/Business Rules/Global Variables/XXXXX".
Cannot process artifact (XXXXXX). Unsupported artifact type (Global Variable).
Since Calc Manager is the only supported tool would this cause the problem with the migration process? If so, how do I migrate the application successfully.
I saw the upgrade option in the Planning Administration but how is application in the situation.
Thanks in advance.

Hi John
Thank you for this I used the back-end migration and the steps are as follows for those that will need the help:
1. Create a shell Planning app in 11.1.2.2
2. Backup the database for the application created above
3. Synchronize HSS between the source and destination environments (luckily I didn't have to do this)
4. Take a copy of the database for the source application
5. Stop the Hyperion Planning service (I stopped all the Hyperion Services to be safe)
6. Restore the database of the source application on top of the database for the destination application.
7. Confirm that owner SID for the app is still the same in the destination
8. Clear the version of the application in the planning database
9. Start Hyperion services in the destination application.
10. log into planning and it will ask you to upgrade the application.
11. Once thats done remember your substitution variables (in Planning), location aliases and the data (exported & imported as text files through EAS).
Thanks John for the help.

How do I migrate applications from old MacBook Pro to a MacBook Air?

How do I migrate applications such as Word & iWork from my old Macbook Pro running Lion to my new MacbOok Air, running Mountain Lion?
Thanks for advice. Cheers.

One way: if you have a backup of your MBP on an external disk which you could connect to your MBA, or you could establish a connection in between the two Macs, you may want to launch the "Migration Assistant" on the MBA. You'll find it in Applications under Utilities. It guides you through the steps and options.
The other (better) way is re-installing all apps fresh, and best the latest versions and updates to make sure it's all ML compatible. "Purchases" in the App Store are helpful as you simply download and install the latest and greatest again. For MS Word etc you should have the install disks. It's a bit more work but usually worth it.

Migrating application from jdk 1.4 to 1.5

Hi,
I am planing to migrate my application from JDK 1.4 TO 1.5 . I am also using AJAX4JSF in application.Did anyone encounter any issue after migrating or during the migration to JDK 1.5 ?
Thanks in advance

You should be calling wrap() to wrap your keys, not doFinal(), or alternatively initializing your cipher to be ENCRYPT'ing, not WRAP'ing.

Problems migrating application from development server to production server

Well, we succesfully migrated shared library, application settings and BRs, BUT we couldnt migrate permissions and more than half of total forms, possibly because of lack of permissions, could you please point me to the direction of some manual about migrating, or just share an advice.
Thanks in advance!

Version - 11.1.2.0.83
We did migration by LCM using this http://www.oracle.com/webfolder/technetwork/tutorials/obe/hyp/PLN11.1.2_LCM/index.html guide, Importing Planning Applications from the File System into the Destination Environment part

Migrating Application FROM Visual Basic

Hi Everyone,
I have an application written in Visual Basic (Front End) and SQL Server as the Back End. Now this application should run on the web i.e need to web enable the application.I have coded in Java for sometime now,but I do not have any prior knowledge as to build a Web application from scratch.Can anyone let me know
how to procced.I would like to use open source like JDK for development.Eclipse for IDE.
Thanks,
Supriya.

First off let's get VB specific -- Are you using Access as a local database and container for your queries? If you are then read on, otherwise, the information already give is excellent and complete enough to get you well on your way.
1 - You are going to have to conver all of your queries either to SQL and store them in a business layer, or create stored procedures for them on the server. I strongly recomend the stored procedure route to hide any detail of your dataserver as much as possible and supply tighter security for table access.
2 - Your web server is going to be a significant ralleying point for your data and return HTML generation, you should take that into consideration with your IT staff and how it will affect other applications on that server. (It will probably not have sufficient impact, unless you already have your own dedicated server for this application)
3 - As mentioned by the others, the Applet/Servlet or JSP/Servlet configuation will serve you very well for your application.

Migrating Application from JDev 10.1.3.5 to JDev 11.1.2.2.; WebLogic issues

Hi,
I've been in the process of migrating an application we have from JDev 10.1.3.5. to the most current release. This involved migrating from OC4J to the WebLogic Server. After clearing up code-related issues, I have been trying to mitigate errors that came from deploying the application to the WebLogic server. I fixed (or so I think) the original error(see immediately below in italics) by deleting the servlet tag in both of the web.xml files (ViewController and Deploy) that are within the application. I also changed it to 'adfLibResources' per a previous thread on this topic.
+<Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Users\priestem\AppData\Roaming\JDeveloper\system11.1.2.2.39.61.83.1\o.j2ee\drs\Muster\ModelWebApp.war. Please make sure that the annotations are valid. The error is oracle.adf.view.faces.webapp.ResourceServlet>+
Now I am getting the following errors:
<Aug 6, 2012 3:24:28 PM CDT> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Users\priestem\AppData\Roaming\JDeveloper\system11.1.2.2.39.61.83.1\o.j2ee\drs\Muster\ViewControllerWebApp.war. Please make sure that the annotations are valid. The error is >
<Aug 6, 2012 3:24:28 PM CDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1344284600393' for task '0'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'Muster''
weblogic.application.ModuleException: Failed to load webapp: 'Muster'
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.taglib.UIXPanelTag
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
     at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
     Truncated. see log file for complete stacktrace
>
<Aug 6, 2012 3:24:28 PM CDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'Muster'.>
<Aug 6, 2012 3:24:28 PM CDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Failed to load webapp: 'Muster'
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.taglib.UIXPanelTag
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
     at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
     Truncated. see log file for complete stacktrace
>
[03:24:28 PM] Deployment cancelled.
[03:24:28 PM] ---- Deployment incomplete ----.
[03:24:28 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
#### Cannot run application Muster due to error deploying to IntegratedWebLogicServer.
[Application Muster stopped and undeployed from Server Instance IntegratedWebLogicServer]
Can someone please provide insight/direction? I restarted this whole process because I was not sure if I was making mistakes. But I have received this same exact error both times in both copies of the application code.
Thanks,
M. Priester

I think your web.xml that is a part of the application had the following:
<taglib>
<taglib-uri>
http://xmlns.oracle.com/adf/faces
</taglib-uri>
<taglib-location>
/WEB-INF/lib/adf-faces-impl.jar
</taglib-location>
</taglib>
I think this is not even your configuration but something that JDev added, thus you can consider testing removing this part of the code and test your application and verify the functionality.
Regarding the possible issue during migration from 10g to 11g of Jdev, you can review the following thread:
Class not found : oracle.adfinternal.view.faces.taglib.UIXPanelTag
The missing class is a part of "adf-faces-impl-1013.jar" which seems to be specific to the JDev 10g, thus might not be even required by JDev11g.
Also regarding the fact that how this seems to be an issue with missing class, please review the following API doc for better understanding of the classnotfoundexception:
http://docs.oracle.com/javase/6/docs/api/java/lang/ClassNotFoundException.html
Cheers,
AJ

Migrating Application from weblogic 8.1 to weblogic 10.0 - Urgent

Similar Messages

Maybe you are looking for