Websphere upgrade

we are upgrading websphere Application server from 5.0.2.8 to 5.1.1.1 that would also include moving from JVM 1.3 to i.4
I would really appreciate if some of you who have gone through a similar upgrade could put down their experiences any good links some problems to look for and some steps to avoid.
thanks a lot

I didn't have any problems.Not quite true. I did have problems understanding how IBM packaged the stuff and what I was supposed to run to install the upgrades. But I had no problems with installing the upgrades.

Similar Messages

WebSphere 6.0 upgrade

Hi,
I am in the process of investigating an upgrade from WASv5.1 to WASv6.0. When performing the upgrade, we need a contingencey plan in case the upgrade fails we can continue to run the application on WASv5.1.
I plan to continue to run the application on WASv5.1 while the upgrade takes place. Is it possible to run WASv5.1 and WASv6.0 on parrallel on the same physical machine. Or would I require another physical machine to host WAS?
Thanks

You are already using the only WebSphere version certified within Peopletools 8.49.
The only way to go on WEbSphere 8.5 is an upgrade of your application (9.0) as well an upgrade of your Peopletools (8.53).
To be honest, managing such upgrade can be painful just because of the WebSphere upgrade across all your env., unless you are planning for several weeks of works and have the budget for this.
Nicolas.

Getting WSDL in reverse order after server upgrade from WAS 5.1 to 6.1

Hi All.I need your help.I am working in RAD 7.0 .After the IBM websphere upgrade from 5.1 to 6.1 i am getting the wsdl generated exactly in reverse order(in 6.1) as compared to that in version 5.1.Can you tell me wat can be the issue .We are using glue-pro jar for generating the WSDL.is there any setting in RAD or WAS which need to be changed so that i can get WSDL in old format.
Any suggestion or opinion is welcomed.

Does it matter? And if so, why does it matter?
From my previous experience with Glue you don't want to have it generate WSDLs anyway. It's not very good at it at all, generates WSDL that are full of errors.
Better to write your own WSDL and tell Glue to use those.

Websphere 4.0.4 crash on heavy load after solaris 8 upgrade

We have our application running on solaris 8 with websphere 4.0.4 and IBM HTTP Server. Things seem to be fine since one year. We recetly went with a solaris patch upgrade (may 2005) applying
108528-29 SunOS 5.8: kernel update and Apache patch
116973-01 SunOS 5.8: Apache Patch
Since than websphere is crashing with the following error
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start(Native Method)
at com.ibm.ws.util.CachedThread.start(ThreadPool.java:126)
at com.ibm.ws.util.CachedThread.wakeup(ThreadPool.java:111)
at com.ibm.ws.util.ThreadPool.getThread(ThreadPool.java:453)
at com.ibm.ejs.oa.pool.ThreadPool.startWorkerThread(ThreadPool.java:83)
at com.ibm.CORBA.iiop.IIOPConnection.processInput(IIOPConnection.java:879)
at com.ibm.CORBA.iiop.StandardReaderThread.run(StandardReaderThread.java:187)
libthread panic: cannot create new lwp : dumping core (PID: 7313 LWP 2)
stacktrace:
ff361c90
0
Not sure if the solaris patch has caused it.
Any suggestions will be very helpful.
Thanks,
Praveen

No specific ideas but take a look at this trouble-shooting article.
You could try trashing the preferences again as described in it and if that does no good it might be worth uninstalling it exactly as described and reinstalling .
http://support.apple.com/kb/TA24195?viewlocale=enUS&locale=enUS

HttpUtils deprecated URGENT (upgradation websphere 4.0 to 5.1)

for this code,
String reqURL= new String(HTTPUtils.getRequestURL(request));
i am getting the following warnigs,
Java compile: the method getRequestURL(HTTPServletRequest) from the type HttpUtils is deprecated.
JavaCompile : The type HttpUtils is deprecated
i also tried replacing HTTPUtils.getRequestURL(request) with HttpServletRequest.getRequestURL(request));
but i getting erroe like,
the method getRequestURL() in the type HTTPServletRequest is not applicabille for the argumnets(HTTPServletRequest)
please help me
thanks and regards
sojanjohn

see reply here:
http://swforum.sun.com/jive/thread.jspa?threadID=45683&tstart=0

Upgrade to OIM 9.1

Hi,
Oracle released OIM 9.1 but with NO upgrade path included. Oracle promises to roll out the upgrade patch by June 08. Hope it materializes. It is still not clear if they would add any more (older) OS and App Server versions to the supported list by then and maintain the upgrade path continuity from earlier versions.
The upgrade from OIM 8.5.3 to 9.0.1.x is clear. We realize there is always a continuity or overlap of versions of OS, App Server and Database server from one OIM version to next. For example, all of them supported Solaris9 and WebSphere 5.1.x.
But as per its Release Notes, OIM 9.1 requires Solaris10 and WebSphere 6.1.0.9. How can we upgrade OS, App Server and OIM all at once ? I dont think, it would be as simple as upgrading only OIM.
Could it be that you just create a fresh install of OIM 9.1 on any OS and App Server you want and run the upgrade scripts only against the database schema of previous OIM, and then point the new OIM 9.1 installation to the upgraded database schema ?
If this is possible, then one can land up with a hardware, OS, App Server of his/her wish and OIM 9.1 with all the history/audit data of all users/resources.
Any opinions ?
Any knowledge how is Oracle going to tackle this ?
Many Regards.

Ok, I got an answer to a part of the question from Re: OIM Patches - do I need 9102? that I have to install the base patch of 9.1.0.2 and then apply BP12 patch. Could anyone please let me know the answers to the rest of the questions?

Problem with JMS Adapter after upgrade to 7.1

Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PM

does following JAR files in place in aii_af_jmsproviderlib.sda.
●      com.ibm.mq.jar
●      com.ibm.mqbind.jar
●      com.ibm.mqjms.jar
●      connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag

Windows Server Upgrade and Weblogic 8.1

Hi,
We have a J2EE Application currently running on Windows 2000 Server with "Websphere App Server 8.1.5", JDK 1.4.2 and Documentum 5.2.5. Plnning to upgrade the windows server to 2008. I hope Weblogic Server 8.1 can be installed on 2008 server, but can anybody had hands on experience of installing and working with weblogic 8.1.5 on windows 2008 server. Any information on this is appreciated.
Thanks
Sam

That is an internal use API that you shouldn't be using.
I don't know enough about what your jndi authenticator code needs to suggest
a replacement, but it sounds like it needs a JCE provider. You could try to
replace it with
another JCE provider (maybe SunJCE, or BouncyCastle would work?)
Tony
"Pam Schultz" <[email protected]> wrote in message
news:[email protected]..
>
In Weblogic 7.1, we had an jndi authenticator class for SSL with this lineof code:
>
java.security.Security.addProvider(new com.certicom.ecc.jcae.Certicom());
The com.certicom.ecc.jcae.Certicom() class was included in the 7.1eblogic.jar
file. It is no longer part of the 8.1 weblogic.jar file. Anyone know whatit should
be replaced with?
Thanks...

BOE XI 3.1 + SAP Integration Kit on AIX 5.3 with WebSphere 6.1 (SOLVED)

Hi everybody!
On a recent installation I encountered a problem with SAP Integration Kit using BW Query with prompts; I want to share with you what I did to solve this problem:
First of all, the environment:
IBM Server with AIX 5.3
BO Repository on DB2 9.5
Application Server IBM WebSphere 6.1
BOE XI R3.1
Crystal Reports 2008 SP1
After installing and configuring everything on the system, I encountered some problem launching in InfoView reports created with Crystal Reports 2008 based on BW query with SAP Prompts.
The error that I recieved everytime was:
com.sap.mw.JCO.$Function
What I did to solve this was:
1) Configure the absolute complete classpath inside the Application Server (path/sapjco.jar)
2) Put the sapjco.jar version 2.18 at 32bit (unix version) that you can download at https://websmp108.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000463654&
Hope this helping you
Bye
Andrea

Dear Gurus,
The issue I am facing is described exactly in the document "Upgrading to CR 2008 V1 / SP1" by Blair Wheadon.
The problem occurs when installing CR2008v1 and BOE 3.1 on the same machine.
The solution is to download and install SP1.
Unfortunately for me, I have downloaded SP1 but the installation is not going well.
Message prompts that installation files are corrupt and that I should download again.
I have downloaded twice. And tried several times.
So I guess it might be due to the platform.
But why wasn;'t the message displayed after BOE3.1 installation was completed?
Do you guys have an idea?
Alice

Error in Toplink 10.1.3 cache coordination using Websphere JMS

I' am trying to setup Cache Coordination for Toplink 10.1.3 in Websphere 7 using Websphere's implementation of JMS. However I' am getting a NamingException
when I try to lookup the Topic and TopicFactory from the JNDI tree. Admin Security is enabled in the server but not application security. I' am able to lookup
the queues using InitialContext. Upgrading to Toplink 11 is not an option right now for us. Please help in finding out if anything is missing in my Toplink configuration.
<?xml version="1.0" encoding="UTF-8"?>
<toplink-sessions
     version="10g Release 3 (10.1.3.0.0)"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <session xsi:type="server-session">
          <name>default</name>
          <remote-command>
               <commands>
                    <cache-sync>true</cache-sync>
               </commands>
               <transport xsi:type="jms-topic-transport">
                    <topic-connection-factory-name>jms/jobtrax.TCF</topic-connection-factory-name>
                    <topic-name>jms/jobtrax.ToplinkTopic</topic-name>
                    <jndi-naming-service>
                         <url>corbaloc:rir:/NameServiceServerRoot</url>
                         <initial-context-factory-name>com.ibm.websphere.naming.WsnInitialContextFactory</initial-context-factory-name>
                    </jndi-naming-service>
               </transport>
          </remote-command>

          <logging xsi:type="toplink-log">
               <log-level>fine</log-level>
               <logging-options>
                    <log-exception-stacktrace>true</log-exception-stacktrace>
                    <print-thread>true</print-thread>
                    <print-session>false</print-session>
                    <print-connection>false</print-connection>
                    <print-date>true</print-date>
               </logging-options>
          </logging>
          <primary-project xsi:type="class">com.pstechnology.toplink.ToplinkProject</primary-project>
          <login xsi:type="database-login">
               <platform-class>com.pstechnology.eaf.persistence.toplink.Oracle10Platform</platform-class>
               <external-connection-pooling>true</external-connection-pooling>
               <external-transaction-controller>false</external-transaction-controller>
               <sequencing>
                    <default-sequence xsi:type="native-sequence">
                         <name>Default</name>
                    </default-sequence>
               </sequencing>
               <datasource>jdbc/jobtrax_job_datasource</datasource>
               <bind-all-parameters>true</bind-all-parameters>
          </login>
     </session>
</toplink-sessions>
[2/17/11 16:22:10:696 EST] 00000018 SystemOut O [TopLink Warning]:
2011.02.17 04:22:10.690--Thread(Thread[server.startup : 0,5,main])--Local
Exception Stack:
Exception [TOPLINK-22103] (Oracle TopLink - 10g Release 3 (10.1.3.0.0)
(Build 060118)): oracle.toplink.exceptions.RemoteCommandManagerException
Exception Description: Could not look up remote connection under name
jms/jobtrax.TCF with URL corbaloc:rir:/NameServiceServerRoot
Internal Exception: javax.naming.NamingException: Error during resolve
[Root exception is javax.naming.AuthenticationException: Login failed:
com.ibm.websphere.security.auth.WSLoginFailedException [Root exception is
com.ibm.websphere.security.auth.WSLoginFailedException]]
at
oracle.toplink.exceptions.RemoteCommandManagerException.errorLookingUpRemoteConnection
(RemoteCommandManagerException.java:75)
at
oracle.toplink.remotecommand.jms.JMSTopicTransportManager.getTopicConnectionFactory
(JMSTopicTransportManager.java:206)
at
oracle.toplink.remotecommand.jms.PstJMSTopicTransportManager.createJMSTopicRemoteConnection
(PstJMSTopicTransportManager.java:67)
at
oracle.toplink.remotecommand.jms.JMSTopicTransportManager.createLocalConnection
(JMSTopicTransportManager.java:106)
at
oracle.toplink.remotecommand.jms.JMSTopicDiscoveryManager.startDiscovery
(JMSTopicDiscoveryManager.java:44)
at oracle.toplink.remotecommand.RemoteCommandManager.initialize
(RemoteCommandManager.java:132)
at oracle.toplink.publicinterface.DatabaseSession.login
(DatabaseSession.java:517)
at oracle.toplink.tools.sessionmanagement.SessionManager.getSession
(SessionManager.java:379)
at
com.pstechnology.eaf.persistence.toplink.TopLinkRepository.getServerSession
(TopLinkRepository.java:163)
at
com.pstechnology.eaf.persistence.toplink.TopLinkRepository.getClientSession
(TopLinkRepository.java:198)
at
com.pstechnology.eaf.persistence.toplink.TopLinkRepository.getReadSession
(TopLinkRepository.java:216)
at com.pstechnology.eaf.persistence.toplink.TopLinkRepository.read
(TopLinkRepository.java:318)
at
com.pstechnology.repository.admin.ApplicationPropertyRepository.findApplicationPropertyByEnumId
(ApplicationPropertyRepository.java:70)
at
com.pstechnology.service.admin.AdministrationService.findApplicationPropertyValue
(AdministrationService.java:179)
at
com.pstechnology.scheduling.trigger.AbolishedTaskSimpleTrigger.getTimerRepeatIntervalValue
(AbolishedTaskSimpleTrigger.java:45)
at
com.pstechnology.scheduling.trigger.AbolishedTaskSimpleTrigger.afterPropertiesSet
(AbolishedTaskSimpleTrigger.java:30)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods
(AbstractAutowireCapableBeanFactory.java:1198)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
(AbstractAutowireCapableBeanFactory.java:1167)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:427)
at org.springframework.beans.factory.support.AbstractBeanFactory
$1.getObject(AbstractBeanFactory.java:249)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton
(DefaultSingletonBeanRegistry.java:155)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:246)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:160)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons
(DefaultListableBeanFactory.java:291)
at
org.springframework.context.support.AbstractApplicationContext.refresh
(AbstractApplicationContext.java:352)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>
(ClassPathXmlApplicationContext.java:122)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>
(ClassPathXmlApplicationContext.java:66)
at com.pstechnology.service.SchedulingContext.initialize
(SchedulingContext.java:56)
at com.pstechnology.servlet.InitializationServlet.init
(InitializationServlet.java:52)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init
(ServletWrapper.java:358)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init
(ServletWrapperImpl.java:169)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize
(ServletWrapper.java:1809)
at
com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper
(WebExtensionProcessor.java:98)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings
(WebApp.java:678)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally
(WebApp.java:429)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize
(WebAppImpl.java:304)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication
(WebGroupImpl.java:100)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication
(VirtualHostImpl.java:166)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp
(WSWebContainer.java:731)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication
(WSWebContainer.java:616)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install
(WebContainerImpl.java:376)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start
(WebContainerImpl.java:668)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start
(ApplicationMgrImpl.java:1122)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart
(DeployedApplicationImpl.java:1319)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start
(DeployedModuleImpl.java:609)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start
(DeployedApplicationImpl.java:944)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication
(ApplicationMgrImpl.java:725)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start
(ApplicationMgrImpl.java:2046)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start
(CompositionUnitMgrImpl.java:439)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start
(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start
(CompositionUnitMgrImpl.java:382)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300
(CompositionUnitMgrImpl.java:110)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl
$CUInitializer.run(CompositionUnitMgrImpl.java:949)
at com.ibm.wsspi.runtime.component.WsComponentImpl
$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
Internal Exception Stack:
javax.naming.NamingException: Error during resolve [Root exception is
javax.naming.AuthenticationException: Login failed:
com.ibm.websphere.security.auth.WSLoginFailedException [Root exception is
com.ibm.websphere.security.auth.WSLoginFailedException]]
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup
(CNContextImpl.java:1840)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup
(CNContextImpl.java:1749)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt
(CNContextImpl.java:1500)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup
(CNContextImpl.java:637)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:455)
at
oracle.toplink.remotecommand.jms.JMSTopicTransportManager.getTopicConnectionFactory
(JMSTopicTransportManager.java:204)
at
oracle.toplink.remotecommand.jms.PstJMSTopicTransportManager.createJMSTopicRemoteConnection
(PstJMSTopicTransportManager.java:67)
at
oracle.toplink.remotecommand.jms.JMSTopicTransportManager.createLocalConnection
(JMSTopicTransportManager.java:106)
at
oracle.toplink.remotecommand.jms.JMSTopicDiscoveryManager.startDiscovery
(JMSTopicDiscoveryManager.java:44)
at oracle.toplink.remotecommand.RemoteCommandManager.initialize
(RemoteCommandManager.java:132)
at oracle.toplink.publicinterface.DatabaseSession.login
(DatabaseSession.java:517)
at oracle.toplink.tools.sessionmanagement.SessionManager.getSession
(SessionManager.java:379)
at
com.pstechnology.eaf.persistence.toplink.TopLinkRepository.getServerSession
(TopLinkRepository.java:163)
at
com.pstechnology.eaf.persistence.toplink.TopLinkRepository.getClientSession
(TopLinkRepository.java:198)
at
com.pstechnology.eaf.persistence.toplink.TopLinkRepository.getReadSession
(TopLinkRepository.java:216)
at com.pstechnology.eaf.persistence.toplink.TopLinkRepository.read
(TopLinkRepository.java:318)
at
com.pstechnology.repository.admin.ApplicationPropertyRepository.findApplicationPropertyByEnumId
(ApplicationPropertyRepository.java:70)
at
com.pstechnology.service.admin.AdministrationService.findApplicationPropertyValue
(AdministrationService.java:179)
at
com.pstechnology.scheduling.trigger.AbolishedTaskSimpleTrigger.getTimerRepeatIntervalValue
(AbolishedTaskSimpleTrigger.java:45)
at
com.pstechnology.scheduling.trigger.AbolishedTaskSimpleTrigger.afterPropertiesSet
(AbolishedTaskSimpleTrigger.java:30)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods
(AbstractAutowireCapableBeanFactory.java:1198)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
(AbstractAutowireCapableBeanFactory.java:1167)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:427)
at org.springframework.beans.factory.support.AbstractBeanFactory
$1.getObject(AbstractBeanFactory.java:249)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton
(DefaultSingletonBeanRegistry.java:155)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:246)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:160)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons
(DefaultListableBeanFactory.java:291)
at
org.springframework.context.support.AbstractApplicationContext.refresh
(AbstractApplicationContext.java:352)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>
(ClassPathXmlApplicationContext.java:122)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>
(ClassPathXmlApplicationContext.java:66)
at com.pstechnology.service.SchedulingContext.initialize
(SchedulingContext.java:56)
at com.pstechnology.servlet.InitializationServlet.init
(InitializationServlet.java:52)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init
(ServletWrapper.java:358)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init
(ServletWrapperImpl.java:169)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize
(ServletWrapper.java:1809)
at
com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper
(WebExtensionProcessor.java:98)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings
(WebApp.java:678)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally
(WebApp.java:429)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize
(WebAppImpl.java:304)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication
(WebGroupImpl.java:100)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication
(VirtualHostImpl.java:166)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp
(WSWebContainer.java:731)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication
(WSWebContainer.java:616)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install
(WebContainerImpl.java:376)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start
(WebContainerImpl.java:668)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start
(ApplicationMgrImpl.java:1122)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart
(DeployedApplicationImpl.java:1319)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start
(DeployedModuleImpl.java:609)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start
(DeployedApplicationImpl.java:944)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication
(ApplicationMgrImpl.java:725)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start
(ApplicationMgrImpl.java:2046)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start
(CompositionUnitMgrImpl.java:439)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start
(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start
(CompositionUnitMgrImpl.java:382)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300
(CompositionUnitMgrImpl.java:110)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl
$CUInitializer.run(CompositionUnitMgrImpl.java:949)
at com.ibm.wsspi.runtime.component.WsComponentImpl
$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
Caused by: javax.naming.AuthenticationException: Login failed:
com.ibm.websphere.security.auth.WSLoginFailedException [Root exception is
com.ibm.websphere.security.auth.WSLoginFailedException]
at com.ibm.ws.naming.util.SecurityUtil.login(SecurityUtil.java:121)
at com.ibm.ws.naming.jndicos.CNContextImpl.login
(CNContextImpl.java:4516)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve
(CNContextImpl.java:2781)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup
(CNContextImpl.java:1790)
... 60 more
Caused by: com.ibm.websphere.security.auth.WSLoginFailedException
at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate
(LTPAServerObject.java:998)
at com.ibm.ws.security.server.lm.ltpaLoginModule.login
(ltpaLoginModule.java:643)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at javax.security.auth.login.LoginContext.invoke
(LoginContext.java:795)
at javax.security.auth.login.LoginContext.access$000
(LoginContext.java:209)
at javax.security.auth.login.LoginContext$4.run
(LoginContext.java:709)
at java.security.AccessController.doPrivileged
(AccessController.java:251)
at javax.security.auth.login.LoginContext.invokePriv
(LoginContext.java:706)
at javax.security.auth.login.LoginContext.login
(LoginContext.java:603)
at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login
(JaasLoginHelper.java:354)
at com.ibm.ws.security.auth.ContextManagerImpl.login
(ContextManagerImpl.java:4024)
at com.ibm.ws.security.auth.ContextManagerImpl.login
(ContextManagerImpl.java:3728)
at com.ibm.ws.security.auth.ContextManagerImpl.login
(ContextManagerImpl.java:3724)
at com.ibm.ws.security.auth.ContextManagerImpl.login
(ContextManagerImpl.java:3475)
at com.ibm.ws.naming.util.SecurityUtil$1.run(SecurityUtil.java:115)
at com.ibm.ws.naming.util.SecurityUtil$1.run(SecurityUtil.java:111)
at com.ibm.ws.security.util.AccessController.doPrivileged
(AccessController.java:118)
at com.ibm.ws.naming.util.SecurityUtil.login(SecurityUtil.java:109)
... 63 more
Caused by: com.ibm.websphere.security.PasswordCheckFailedException
at com.ibm.ws.wim.registry.util.LoginBridge.checkPassword
(LoginBridge.java:204)
at com.ibm.ws.wim.registry.WIMUserRegistry$1.run
(WIMUserRegistry.java:181)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs
(ContextManagerImpl.java:4610)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem
(ContextManagerImpl.java:4698)
at
com.ibm.ws.wim.security.authz.jacc.JACCSecurityManager.runAsSuperUser
(JACCSecurityManager.java:432)
at
com.ibm.ws.wim.security.authz.ProfileSecurityManager.runAsSuperUser
(ProfileSecurityManager.java:964)
at com.ibm.ws.wim.registry.WIMUserRegistry.checkPassword
(WIMUserRegistry.java:170)
at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword
(UserRegistryImpl.java:338)
at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate
(LTPAServerObject.java:973)
... 83 more
Caused by: com.ibm.websphere.wim.exception.PasswordCheckFailedException:
CWWIM4537E No principal is found from the 'admin' principal name.
at com.ibm.ws.wim.ProfileManager.loginImpl(ProfileManager.java:3607)
at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod
(ProfileManager.java:292)
at com.ibm.ws.wim.ProfileManager.login(ProfileManager.java:400)
at com.ibm.websphere.wim.ServiceProvider.login
(ServiceProvider.java:485)
at com.ibm.ws.wim.registry.util.LoginBridge.checkPassword
(LoginBridge.java:169)

We are taking another run at TopLink 10.1.3 and have run into this problem again.
It turns out that this is fairly reproducable. It occurs when we remove the last item (or all of the items) from the parent collection.
It occurs with transparent indirection on or off.
I've added several tests to our Junit suite to detect this behavior with various objects. Sometimes they fail, sometimes they pass. Going back to TopLink 9, a couple of the tests that fail in 10 fail, but most of them pass.
Given the number of folks who shared our probem in TopLink9, I wonder how many have a similar problem in 10. I also wonder why the behavior differs somewhat between 9 and 10. Though our expanded test suite is now detecting the behavior in 9, it is less frequent.

Using XML with websphere jdbc adapter 2.6 on 11.2.0.2

Hi,
while upgrading a DB from 10g to 11R2, the developers encountered problems with the websphere adapter for JDBC while using XML.
the adapter is working with the oracle XML libraries such as xmltype_lib and the adapter fails to run the package procedures (specifically xmltype.createxml).
to my understanding, it works with 11R1 (the dev team tested it), and my guess is that the implementation of the xmltype_lib library changed in 11R2.
any idea how to approach this issue? is there any known overall changes to xmltype_lib in 11R2 ? if my assumption is correct there should be no problem fixing this issue by compiling older libraries or some sort of similar approach.

If you ask this question in a Java forum you are looking for someone that has run into this before and found a solution - what you need is someone experienced with Websphere, so you really should ask in a Websphere forum (which you can find on the IBM website).
But this part of your question:
is there any known overall changes to xmltype_lib in 11R2 ?relates to the Oracle DBMS which takes it out of the realm of Java altogether. If you want an answer to that, again, ask in the right forum. I'm guessing this one:
XML DB

TopLink 11g Cache Coordination failure in WebSphere 6.1

Hello,
I've recently upgraded to TopLink 11g and I am trying to make cache coordination feature work in WebSphere 6.1 using JMS. Once configured I am getting the following errors on the server side:
[4/14/09 17:22:25:321 PDT] 00000032 SibMessage E [:] CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1511:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol. at com.ibm.ws.sib.msgstore.transactions.MSDelegatingXAResource.addWork(MSDelegatingXAResource.java:140) at com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink.cmdRemove(AbstractItemLink.java:1330) at com.ibm.ws.sib.msgstore.AbstractItem.remove(AbstractItem.java:828) at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.receive(JSLocalConsumerPoint.java:1487) at com.ibm.ws.sib.processor.impl.ConsumerSessionImpl.receiveWithWait(ConsumerSessionImpl.java:421) at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receiveInboundMessage(JmsMsgConsumerImpl.java:1525) at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receive(JmsMsgConsumerImpl.java:707) at oracle.toplink.internal.remotecommand.jms.JMSTopicRemoteConnection.run(JMSTopicRemoteConnection.java:229) at java.lang.Thread.run(Thread.java:810)
[4/14/09 17:22:25:353 PDT] 00000032 SystemOut O [TopLink Warning]: 2009.04.14 17:22:25.353--ServerSession(1261194028)--Thread(Thread[Thread-65,5,WebSphere_EJB_Timer_Service_WorkManager: WM Service Group])--Local Exception Stack:
Exception [TOPLINK-22109] (Oracle TopLink - 11g (11.1.1.0.1) (Build 081030)): oracle.toplink.exceptions.RemoteCommandManagerException
Exception Description: Failed to receive JMS message from JMS provider
Internal Exception: javax.jms.JMSException: CWSIA0103E: An exception occurred while receiving a message: com.ibm.websphere.sib.exception.SIResourceException: CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1526:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol..
     at oracle.toplink.exceptions.RemoteCommandManagerException.errorReceivingJMSMessage(RemoteCommandManagerException.java:139)
     at oracle.toplink.internal.remotecommand.jms.JMSTopicRemoteConnection.run(JMSTopicRemoteConnection.java:257)
     at java.lang.Thread.run(Thread.java:810)
Caused by: javax.jms.JMSException: CWSIA0103E: An exception occurred while receiving a message: com.ibm.websphere.sib.exception.SIResourceException: CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1526:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol..
     at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receiveInboundMessage(JmsMsgConsumerImpl.java:1637)
     at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receive(JmsMsgConsumerImpl.java:707)
     at oracle.toplink.internal.remotecommand.jms.JMSTopicRemoteConnection.run(JMSTopicRemoteConnection.java:229)
     ... 1 more
Caused by: com.ibm.websphere.sib.exception.SIResourceException: CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1526:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol.
     at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.receive(JSLocalConsumerPoint.java:1521)
     at com.ibm.ws.sib.processor.impl.ConsumerSessionImpl.receiveWithWait(ConsumerSessionImpl.java:421)
     at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receiveInboundMessage(JmsMsgConsumerImpl.java:1525)
     ... 3 more
Caused by: com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol.
     at com.ibm.ws.sib.msgstore.transactions.MSDelegatingXAResource.addWork(MSDelegatingXAResource.java:140)
     at com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink.cmdRemove(AbstractItemLink.java:1330)
     at com.ibm.ws.sib.msgstore.AbstractItem.remove(AbstractItem.java:828)
     at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.receive(JSLocalConsumerPoint.java:1487)
     ... 5 more
Any idea what I am doing wrong here?
Lukas

Fixing listener is not enough. Old and lastest code has this for references to ServerPlatform.launchContainerRunnable, which WebSpherePlatform do not override:
CommandPropagator:
public void asynchronousPropagateCommand() {
// The async logic is in the run() method
rcm.logDebug("async_propagation", (Object[])null);
this.rcm.getServerPlatform().launchContainerRunnable(this);
public void propagateCommand(RemoteConnection conn) {
Object[] arguments = { command.getClass().getName(), conn.getServiceId() };
rcm.logDebug("propagate_command_to", arguments);
try {
// The result will be null on success, and an exception string on failure
Object result = conn.executeCommand(command);
if (result != null) {
// An error occurred executing the remote command
handleExceptionFromRemoteExecution(conn, (String)result);
} catch (CommunicationException comEx) {
// We got a comms exception.
this.handleCommunicationException(conn, comEx);
JMSTopicRemoteConnection:
DiscoveryManager:
public void startDiscovery() {
if (rcm.isCommandProcessorASession()) {
rcm.getCommandProcessor().processCommand(new ProfileDiscoveryStartedCommand());
// Only start if we are currently stopped
if (this.isDiscoveryStopped()) {
this.rcm.getServerPlatform().launchContainerRunnable(this);
JMSTopicTransportManager:
public Hashtable getConnectionsToExternalServicesForCommandPropagation() {
if(this.getConnectionsToExternalServices().isEmpty() && !this.rcm.isStopped()) {
this.createExternalConnection();
if(this.localConnection == null) {
// It's a good time to create localConnection,
// in a new thread - to return externalConnections promptly.
this.rcm.getServerPlatform().launchContainerRunnable(new Runnable() {
public void run() {
try {
createLocalConnection();
} catch (RemoteCommandManagerException ex) {
// Ignore exception - user had a chance to handle it in createLocalConnection method:
// for instance to change host url and create a new local connection.
return super.getConnectionsToExternalServicesForCommandPropagation();
}

Non Standard password on configurator during upgrade...

Hi,
As specified in the recommendations, the Configurator password has been changed from its default.
Now, upgrading to 8.1.0 (and then on to the latest and greatest) I wonder if its possible to add the password
to the install command as you can do with a manual one?
i.e.
install -nodisplay -U configurator -P <password>
or something similiar... I cant find it in the documentation, but I can see that the install script do send the given arguments on to the install class as it sends the exec java on...
If I run it without specifying the password, it seems to upgrade it, but it stops logging what it does so I cant be sure...
Anyone?

I got around this problem by changing the Configurator password back to its default... configurator
However, the current password policy stopped me from doing so and I could not start the service up again because
of local reasons (i.e. I did not have the websphere to run it under, just access via lh console)
I went in to lh console with
# lh console -u Configurator -p <myoldsafepassword>
Configurator> changePassword Configurator configurator
that responded with a java exception due to the policy violation (i.e. accountid etc etc not part of password)
Configurator> listObjects Policy
that listed the various policys in question
I looked them through, using the java output as a guide to which was in question...
Configurator> getObject Policy '<name on policy from listObjects>'
when I got the one I needed to change i checked it out to a local file
Configurator> checkout Policy '<name of policy to change>' policy_to_change.xml
I then edited that xml file to lighten the rules so that the password would pass...
i.e. removed all reserved words except email :D
I then checked the policy in again...
Configurator> checkin policy_to_change.xml
and then the password change went through afterwords...So I am ok to upgrade now... :D
Edited by: Dhurgan on Jul 26, 2011 12:05 PM

Upgrading from 11.1.1.2 to 11.1.2.1 question(s)

Hey guys, I have a question about upgrading Essbase. I'm pretty new to Essbase and most of my experience with it has to do with loading data and MAXL.
my environment is setup as follows:
App box 1 - Essbase 11.1.1.2 - AIX
App box 2 - Essbase 11.1.1.2 - AIX
Web box 1 - Websphere, APS, EAS, SS, Dodeca
Web box 2 - Websphere, APS, Dodeca
F5 Load balancer in front of the web tier
I believe they have APS and Dodeca clustered. App box 1 and 2 have different Essbase applications running on each box.
My first thought was to upgrade Essbase and migrate the cubes for both applications at once. Further down the road that could be 5-6 applications and it doesn't look so easy.
So my question is, is it possible to upgrade only one of the application boxes and web tier to 11.1.2.1?
Possible setup might look like this:
my environment is setup as follows:
App box 1 - Essbase 11.1.1.2 - AIX
App box 2 - Essbase 11.1.2.1 - AIX
Web box 1 - Websphere, APS, EAS, SS, Dodeca
Web box 2 - Websphere, APS, Dodeca, SS 11.1.2.1, EAS 11.1.2.1, APS too?
F5 Load balancer in front of the web tier
Would you upgrade all the web tier and just have App box 1 on an older version of Essbase?
If anyone has any suggestions on sites/material to catch up on it would be appreciated (I'm working my way through epm_install_11121, epm_install_start_here and epm_install_troubleshooting right now).
Thanks,
Phil Matre

John, thanks for taking the time to read over my issue. We got a hold of an Oracle engineer and this is what he had to say "Shared Services must be at the same level across all applications! So net is you can’t mix the two. Also the upgrade to 11.1.2.1 is NOT an in place upgrade, must be a new environment."
So the WebLogic part was another question bouncing around in my head. I guess I didn't want to believe I would have to use it. In the end it will probably save us some dollars on two WebSphere licences. The boss men will be happy about that. I hope all upgrades are this exciting!
Thanks,
Phil

Upgrade related query- Repository Update

Hi All,
As mentioned in the upgrade guide :
After installation of MDM 7.1 and having started the MDM 7.1 Server use the MDM Console to update
your repositories. Choose Update Repository from the context menu of each repository. The MDM Console then updates
the repository so that it can be used with the latest builds. The data in the repository is automatically
upgraded.
But, i did the same thing but in my case after un-archiving the repository and login in with respective correct repository credentials,Right clicking on repository the option "Update Repository" is not active ...How will i do this action ?how do i update the repository now ?
( I have tried by Loading & Unloading also )
Please suggest !
Regards,
Harmony

Hi Harmony,
Please follow below steps :
Steps involved in the MDM 7.1 Upgradation
1.     Installation of MDM 7.1 in Dev Environment
2.     Archive MDM 5.5 repository from the Production system
3.     Unarchive the repository in the Dev system
4.     Update repository in the Dev
5.     Update and Test Import Maps
6.     Update and Test Syndication Maps
7.     Testing at the Portal level
8.     Java API upgrade and check the custom made functionalities with API in the repository
9.     CLIX Command Scripts need to be reworked
10.     MDM ports to be reworked with the help of repository schema
11.     Import the repository schema to the production environment after installation of 7.1 in production system.
12.     Transportation from Dev to Production of JAVA API, CLIX
Others Activities which need to be Noted/Performed
MDM Servers
Installed in different directory
MDM Archive Files
Archive files to be copied to the new directory
MDM GUI Client
Different Installation directory
MDM Log files:
5.5 Version is XML based
7.1 version is CSV based
MDM 7.1 doesnu2019t support the log format of 5.5 version.
Copy the files from the u2018logu2019 and u2018report folderu2019 to an extra folder together with MDM_log.xsl, which allows viewing of logs from the browser
Distribution Folder content
Copy the files from the 5.5 directory to the new directory
MDM Server Setting
Mds.ini parameter settings to be checked.
Some parameters are obsolete, some parameters are replaced with newer one
MDM Import Server Settings
Mdis.ini parameters need to be checked
MDM Syndication server setting
Mdss.ini setting to be checked.
Transfer the settings of
SLD Registration u2013 Reuse the MDM 5.5 SLD Registration
Wily Instrumentation
Wily Instrumentation level Threshold
MDM Java API activities
Deploy the 7.1 Java APIs and test the existing Java programs running for the repository
Checking the MDM Compatability with WebSphere Portal
Uninstallation of MDM 5.5 SP06 (Optional)
Thanks and Regards
Praful.

Websphere upgrade

Similar Messages

Maybe you are looking for