IBM Websphere RAD Setup/Compile/Runtime Issues

Installing Plugin between iPlanet and Webshpere 6.x server

If you are doing a plain vanilla installation with Webserver listening on port 80 than regular steps will help. However if we are installing in any other port we need to do some manual changes for the plugin to work correctly.
Below are the list of files that you would have to change the port name manually:

- Plugin-cfg.xml
This is the file that connects between the webserver and appserver that we mentioned during the plugin installation. We need to make the following changes
virtualhostgroup name="default_host"
virtualhost name="*:9080"
virtualhost name="*:80"
virtualhost name="*:9443"
virtualhostgroup

Modify the line in red from 80 to the port your webserver is listening.
Also don’t forget to add this line to provide access to your application root in the :
- Virtualhosts.xml
This is located in your profiles directory as below:
C:\Program Files\IBM\SDP70\runtimes\base_v6\profiles\AppSrv01\config\cells\DCpnu31956Node01Cell\virtualhosts.xml
Look for the following lines
aliases xmi:id="HostAlias_2" hostname="*" port="80"
aliases id="HostAlias_2" port="9443" hostname="*">Change the port of the webserver from 80 to the port your server is listening.



Compile Errors
If you are moving from WSAD to RAD you might observer some compile time issues that did not exist in WSAD. If you are using version “IBM® Rational® Application Developer 7.0.0” immediately get the latest update using your “IBM Installation Manager” there are lot of bugs with this version.


If you are seeing any duplicate exceptions, please check your .classpath and .project to remove the entries mentioned in the compile errors.


Runtime Errors
# 1: Error com.ibm.ws.exception.ConfigurationWarning: Multiple ConfigurationWarning exceptions encountered
Cause
The message com.ibm.ws.exception.ConfigurationWarning: Multiple ConfigurationWarning exceptions encountered can be encountered in a number of situations; one being the Portlet Project WAR is already deployed to the Portal server and you are trying to deploy another WAR/EJB with the same name or Context root. Interestingly you will not see the other one through admin console.
com.ibm.ws.runtime.component.ApplicationMgrImpl]
com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.ConfigurationWarning: Multiple ConfigurationWarning exceptions encountered
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:509)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:570)
Caused by: com.ibm.ws.exception.ConfigurationWarning: Multiple ConfigurationWarning exceptions encountered
at com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplications(ApplicationMgrImpl.java:699)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplications(ApplicationMgrImpl.java:565)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:507)
... 17 more
Caused by: com.ibm.ws.exception.ConfigurationWarning: com.ibm.etools.j2ee.commonarchivecore.exception.NoModuleFileException: A file does not exist for module element having uri: aisleCore-ejb.jar
at com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplication(ApplicationMgrImpl.java:433)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplications(ApplicationMgrImpl.java:671)
... 19 more
Resolution:
- Right Click on Server -> Add and Remove Projects ...
Now remove any projects you have in “Configured projects:” to the “Available Projects” list box. Click Finish
- Now restart the server with only the default application.
- Now add the application back to the server using “Add and Remove Projects ...”
This should resolve the above issue.



#2 Error java.util.MissingResourceException: Can't find bundle for base name
[4/17/09 10:31:32:188 EDT] 00000012 ServletWrappe E SRVE0100E: Did not realize init() exception thrown by servlet EMTStartupServlet: java.lang.ExceptionInInitializerError
at com.nextel.emt.presentation.common.EMTStartupServlet.init(EMTStartupServlet.java:72)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:310)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1696)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:140)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:820)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:547)
at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:419)
at com.ibm.ws.webcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:117)
at com.ibm.ws.webcontainer.VirtualHost.addWebApplication(VirtualHost.java:128)
at com.ibm.ws.webcontainer.WebContainer.addWebApp(WebContainer.java:939)
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:892)
at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:167)
at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:391)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1228)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1067)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:547)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:751)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:892)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1412)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1366)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1012)
……
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPConnector.java:345)
at com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:212)
at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:55)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:680)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:484)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
Caused by: java.util.MissingResourceException: Can't find bundle for base name com.nextel.nol.util.Logging, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:825)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:794)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:532)
at com.nextel.nol.util.Logger.(Logger.java:73)
... 46 more
Resolution
These resource properties files are loaded by classloader same as other java classes. So we need to include them in our runtime classpath.
These resources have fully-qualified-resource-name, similar to a fully-qualified-class-name, excerpt you can't import a resource into your java source file. Because its name takes the form of a string.
Open admin console while the server is running, go to “Application Servers > Server1 > Java and Process Management -> Process Definition “ set “Working Directory” to where your files. Also check the “Java Virtual Machine” and set the class path to point the location of the resource files.

Comments

Popular posts from this blog

Navigating the College Application Labyrinth: A Parent's Journal from Junior Year

Empowering Sales Excellence: Gen AI-Driven Sales Call Planning

ATG Repository Exception | ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE