EES running in IBM Websphere

Has anyone successfully configuredEES with IBM WAS 4.x ??If so, I would appreciate any tips.Has anyone developed web applicationsthat can use EES as an EJB and haveyour application EJBs talk to EES (EJB)and deliver reporting information ??If so, any tips are appreciated.Thanks.

Hi "npatil", I ask in that servant wanted to carry out the implementation of the EDS as a EJB, since that the application server executes in N platforms, doesn't mean that the EDS either like alone program, as EJB, as servlet or as a object CORBA, it can be connected to Essbase, the verification point resides in that the classes that make the bridge process, as I mention it "jcole", they use a characteristic of Java called JNI (Java Native Interface), therefore the interaction between your classes of Java and the server of Essbase, carries out it in fact a dll group (win32) or so libraries (unix) of the one it run-cheats of Essbase, therefore you have the restrictive of platform compatibility and version of where it executes the version of Essbase that do you want to use, I recommend you to verify on that platform of operating system implemented your development in Java. Currently in one of our clients has several developments of business applications in WebLogic 6.0 and 6.1 in Solaris 8 (SunOS 5.8), it is planned to carry out an automation system and monitor for its servers of Essbase, the proposal is to use the JAPI of Essbase, the problem resides in that the version of the operating system in the development environment is Solaris 2.6 (SunOS 5.6) in this the run-time of Essbase version 6.5.1 it doesn't execute, therefore, even if the developing, implementing and making the deployment of all the component ones in a satisfactory way, to the moment of run your application any call toward the server didn't execute.For example the versions of AIX for Essbase 6.5.1 are AIX 4.3.3 and 5LOmar Aecio Garcia RamirezBusiness Intelligence ArchitectOmniSys S.A. de [email protected]

Similar Messages

JMX monitoring front Coherence cache running on IBM WebSphere

I have a question regarding JMX monitoring a Coherence front cache running in a IBM WebSphere v6.1 JVM (1.5).
My setup is that I have three Coherence nodes (back cache) each running 10 JVMs each. Via JMX all these 30 JVMs are setup to be monitored from one of the 30 JVMs which is configured to be the JmxServer for the other 29 instances. The other 29 JVMs set -Dtangosol.coherence.management.remote=true at startup to indicate that their MBean tree will be managed centrally. This works fine but when I try to extend this to also be able to manage the front cache (running on WebSphere on a separate node in the tier above) by adding the same flag (-Dtangosol.coherence.management.remote=true) it does not appear in the MBean tree as the other 30 Coherence cache (Sun) JVMs do.
Are there other things I have to consider to get this working? There are no firewalls in between the nodes so that is not the problem. How much of IBM WebSpheres (non-standard) JMX-functionality is required to get this to work?
/Jonas

How is the WebSphere node connected to the cluster? Is it using TCMP? Extend?
Local, Distributed, Replicated, Near, Overflow, External and Optimistic cache statistics appear in the Coherence JMX server. However, near and local caches created on extend nodes do not appear. Therefore the -Dtangosol.coherence.management.remote=true on an Extend client will not register the near or local caches.
Thanks,
Everett

* IBM Websphere Vs Oracle's Weblogic server *

IBM Websphere Vs Oracle's Weblogic server
Can ODI run on IBM Websphere?
How feasible is it to shift ODI from Oracle Web logic to IBM Websphere?
What challenges , efforts required in ODI code to do so?
Please suggest.
Thanks in Advance.
Regards,
Dinesh.

1. Well for your 1st question I believe you can.
2. I believe it will go fine because you just need one application server to deploy your ee agent.
3. I have never tried IBM websphere as an application sewrver in ODI but it shouldnt be that much completed as you are thinking. Better you do R&D in your local system. Also I am not sure about the issues you will face in future. ( for ex maple PermGen errors, issues in clustering etc)
Thanks

IBM Websphere to ActiveDirectory ( Win 2003 ) LDAP SSL.

I am trying to connect to Win 2003 Ad LDAP from websphere Application server.
I have installed certificates Win2k in to local key store.
I used ikeyman of Websphere. Win 2k3 certificates were in .arm format ( thatz how Win2k3 admin gave me) . I succesfully installed the certificates in local keystore. and pointed to the keystoere when LDAP connection is happening.
I am getting a MalformedURLException canot parse url ldaps://xx.xx.x.x:636
Not an LDAP url .
At the same time i also tried with Sun JDK . it shows another error .
default context init failed: java.security.cert.CertificateParsingException: java.io.IOException: subject key, Unknown k
ey spec: Invalid RSA modulus size.
Please help me . I want this program to run from IBM Websphere Env.
Please find my code below
thanks in advance.
import java.util.Hashtable;
import javax.naming.*;
import javax.naming.ldap.*;
import javax.naming.directory.*;
import java.io.*;
public class Test {
public static void main(String args[] ) {
          //String userName = "CN=Renjith\\, Vasudevan";
          String userName = null;
          String test = ",OU=xx,OU=xx,DC=xx,DC=xxm";
          String newPassword = "xxx";
          String oldPassword = "xx";
          Hashtable env = new Hashtable();
          //Hard coded values - will be moved to properties file.
          env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
          //env.put(Context.PROVIDER_URL, "ldap://X.X.X.X:389");
          env.put(Context.PROVIDER_URL, "ldaps://X.X.X.X:636");
          env.put(Context.SECURITY_AUTHENTICATION, "simple");
          //env.put(Context.SECURITY_PRINCIPAL, "[email protected]");
          env.put(Context.SECURITY_PRINCIPAL, "[email protected]");
          env.put(Context.SECURITY_CREDENTIALS, "xxxx");
          //env.put(Context.SECURITY_PROTOCOL,"ssl");
          String keystore = "C:\\j2sdk1.4.2_04\\jre\\lib\\security\\cacerts";
          System.setProperty("javax.net.ssl.trustStore",keystore);
          System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
          try {
               // Create the initial directory context
               LdapContext ctx = new InitialLdapContext(env,null);
               // This following code only for getting correct dn - Hardcoded dn had some tabbing/char problem.
               // Renjith - begin
               SearchControls constraints = new SearchControls();
               constraints.setSearchScope(SearchControls.SUBTREE_SCOPE);
               String[] strAttributes = { "sAMAccountName", "memberOf" };
               //String FILTER = "(&(objectClass=user))";
               String FILTER = "(&(objectClass=user)(sAMAccountName=prrev))";
               String searchBase = "OU=xx,OU=xx,DC=infores,DC=xx";
               constraints.setReturningAttributes(strAttributes);
               NamingEnumeration results =
                    ctx.search(searchBase, FILTER, constraints);
               System.out.println("results : " + results);
               while (results != null && results.hasMore()) {
                    SearchResult sr = (SearchResult) results.next();
                    String dn = sr.getName();
                    //String dn = ((Context)sr.getObject()).getNameInNamespace();
                    if(dn.indexOf("Renjith") != -1 ) {
                    System.out.println("Distinguised Name : " + dn);
                    //System.out.println("Charg"+dn.toCharArray());
                    userName = dn+test;
                    break;
               // Renjith - end.
               //set password is a ldap modify operation
               ModificationItem[] mods = new ModificationItem[2];
               String oldQuotedPassword = "\"" + oldPassword + "\"";
               byte[] oldUnicodePassword = oldQuotedPassword.getBytes("UTF-16LE");
               String newQuotedPassword = "\"" + newPassword + "\"";
               byte[] newUnicodePassword = newQuotedPassword.getBytes("UTF-16LE");
               mods[0] = new ModificationItem(DirContext.REMOVE_ATTRIBUTE,
                          new BasicAttribute("unicodePwd", oldUnicodePassword));
               mods[1] = new ModificationItem(DirContext.ADD_ATTRIBUTE, new BasicAttribute("unicodePwd",
                         newUnicodePassword));
               System.out.println("Trying to reset Password for: " + userName);
               // Perform the update
               ctx.modifyAttributes(userName, mods);
               System.out.println("Reset Password for: " + userName);
               ctx.close();
          catch (NamingException e) {
               e.printStackTrace();
               System.out.println("Problem resetting password: " + e);
          catch (UnsupportedEncodingException e) {
               System.out.println("Problem encoding password: " + e);
}

The first error you described "malformed URL" is possibly due to the fact that your JRE version 1.4 does not support the ldaps URL.
If using 1.4 then you must use the following syntax:env.put(Context.PROVIDER_URL,"ldap://servername:636");If using 1.5, then it supports the syntax:env.put(Context.PROVIDER_URL,"ldaps://servername:636");I can't comment on the other error message you receive, however I am concerned at two things, one is that in your sample code you are using a "null" user name, and secondly, I have no idea what certificate you have installed. I do not recall seeing a Windows CA cert with the extension of .arm. Normally the Root CA exported trust cert has the extension of .cer

Can AQ be used when running in IBM's WebSphere Application Server?

Hi,
We are using IBM WebSphere Application Server (WAS) but not planning to use MQSeries. We want to use Oracle AQ. Is it possible to run an app in WAS with Oracle AQ functionality being used?
Anyone out there is doing this?
Any info. is greatly appreciated!
Thanks.
Alex

If you ever find the answer, please let me know. I am trying to do the same with WebLogic but with little success. I have participated in the following discusiions:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=6218
http://marvel.oracle.com/pls/otn/f?p=17000:8:25148205767784132::NO::F17000_P8_DISPLAYID,F17000_P8_CRITERIA:40460583213,
If you are not using MDB in WAS or WAS MDB supports transacted session, then there is a good chance that you can use AQ/JMS. BTW, why don't you want to use MQ Series?

RFC in IBM Websphere server

Hi all,
I want to run a Java application that calls SAP RFC in an IBM Websphere server. Right now its working fine in Tomcat server.(I have installed JCO for Tomacat).
What all are the steps (intallations and configurations) I need to do in Websphere server.
I came across terms like SAPODA and JCO. Is SAP ODA neccessary??? or JCO installation alone will work?
Thanks in advance
George

u need only sapjco.jar file and dll files ..............
u put sapjco.jar file in ibm/sdp/6.0/portal/eclipse/plugins/eis.webtools.sap.6.0_0
here u copy that file.....
go to dynamic webproject, right click>properties>java build path-->add external
jars>add that sapjco.jar file and click okfinish..
now u write ur program..........
it works fine...........

JMS Receiver Adapter - com.ibm.websphere.naming.WsnInitialContextFactory

Hello experts,
I am trying to configure JMS Adapter to Access Websphere Application Server via JNDI. The configuration is as follow:
Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Connection Factory: jms/messageQueueCF
Server URL: iiop://ammtnode.iubs.intra:2809/
Queue Name: jms/EXT_INPUT_QUEUE
I deployed all required jar files but Iu2019m still unable to connect to WAS because adapter cannot initialize ORB:
javax.naming.NamingException: Failed to initialize the ORB
I wrote a small java class to check where the problem was:
============================================================================
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://ammtnode.iubs.intra:2809/");
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
Context jndiContext = null;
try {
jndiContext = new InitialContext(env);
ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.lookup("jms/messageQueueCF");
Connection qConn = connectionFactory.createConnection();
Session qSession = qConn.createSession(false,Session.AUTO_ACKNOWLEDGE);
Queue q = (Queue) jndiContext.lookup("jms/EXT_INPUT_QUEUE");
MessageProducer producer = qSession.createProducer(q);
TextMessage message = qSession.createTextMessage();
message.setText(text);
producer.send(message);
producer.close();
qSession.close();
qConn.close();
} catch (Exception e) {
     e.printStackTrace();
============================================================================
I got the same error until I wrote this line:
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
And everything worked fine. Now I want to do the same in my JMS Receiver adapter but I donu2019t know how to introduce this line in the Initial Context Environment. I tried as JMS additional parameters and additional properties as well. However, nothing worked. Does anybody know what Iu2019m doing wrong?
Thank you in advance!

Here I post the entire error:
0#0#Warning##Java###Catching #1#com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection fact
oryjms/messageQueueCF, for profile: ConnectionProfile of channel: CC_I002_AMM_JmsReceiveron node: 5949650 having object id: 0
360697bc61b3666aba07a2708ca095a: javax.naming.NamingException: Failed to initialize the ORB
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:134)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
        at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class
com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:libra
ry:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
        at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
        at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
        at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
        ... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
        at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
        at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
        at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
        ... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
        at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
        at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
        at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
        ... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
        at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
        at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
        at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
        ... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
        at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
        at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
        at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
        at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
        at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
        at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
        at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
        ... 19 more

Apache Tomcat vs IBM Websphere

Hi,
In our current deployment, I am using Apache Tomcat as the Java Application Server that comes bundled with Hyperion Planning 9.3.1 suite of applications. The documentation also suggests Oracle Application Server, IBM Websphere and BEA WebLogic. Currently the application stack is Hyperion Planning only, with Financial Reporting for the reporting needs.
For our current situation, we have shortlisted between using the bundled Apache Tomcat or IBM Websphere. For comparison I wanted to know how stable Apache Tomcat is in general compared to websphere? How many concurrent users can it handle? Are there any specific limitations of Apache Tomcat that I should consider? Can someone list the major pros and cons of each?
Thanks in advance
Shehzad

I agree with Jake.. Tomcat can handle much more than a few users. Whether it can handle the load for your environment may depend on your usage pattern, size of forms, etc.
We typically use Tomcat for our Dodeca product that uses the Java API to talk to Essbase. It doesn't product 'forms' but rather just transfers data via XML between the client and server. With that product, we do have one customer that is serving appx 7,000 users on a single Tomcat server. In that case, however, the usage pattern is that field users log in daily (or sometimes weekly) and run a few reports (that retrieve data via XML).
Note that Tomcat has a configuration parameter in the server.xml file to set the max number of threads that can be spawned by the process. You may want to tune that parameter if you decide to run Tomcat in production (and absolutely be sure to give it more heapsize in the java options).
Tim Tow
Applied OLAP, Inc

IBM WebSphere App.Server 3.5 StdEd + Oracle 8i for repository ?

I want to install IBM WebSphere Application Server (WAS) 3.5 Std
but I don't have a DB to hold the repository.
One of the possible DB mentionned in the install doc is ORACLE
8i but I have no experience whatsoever with this line of
products.
I would like to hear of people running such a config.
Any tips, do's and don't ?
Is it a stable, recommended configuration to start with ?
E.G.:
WAS 3.5 standard on Win2000
+ ORACLE 8i as a repository DB
+ AS400 serving corporate data
Thanks for your help,
Frederic.
PS - I know DB2 is another possibility but I would like to skip
that one for some reasons.

Matt :
I eventually chose to keep the InstantDB repository because
someone told me it would be fine for a small web application.
One thing I am wondering about though : IBM doc mentions Oracle
8i but on the Oracle site they mention 9i only so
- where do you find the 8i ?
- is the 9i fine too ?
- what edition is acceptable ? the cost for the personal/pro
etc. licences do vary quite a lot so which is the cheapest
acceptable one ?
I am still looking for that info.
Any hint ?
Thanks !

Oracle BAM 10.1.3.4 and IBM WebSphere MQ 6.0, Enterprise Link Plan does not

Hello All,
1. I have a BAM 10.1.3.4 installation and a IBM Webspehere MQ client V6.0 installed in the same server
2. Have configured JmsAdmin appropriately to have a Topic Connection Factory and a Topic Pointing to a Queue in the Server
3. Have tested the client connectivity using ivtRun and MQIVP.class, they seem to work fine connecting to the channel and the topic.
4. I have configured an EMS for IBMWebSphereMQ in BAM with the below given parameters
Name:      BPEL_TO_BAM
Owner:      AMERICAS\Jai_Mani
Created:      12/1/2009 2:07:48 AM
Last modified:      12/1/2009 9:48:03 AM
Type:      IBM WebSphere MQ
Initial Context Factory:      com.sun.jndi.fscontext.RefFSContextFactory.
JNDI Service Provider URL:      file:/C:/JNDI-BOSS-DAO.
TopicConnectionFactory Name:      ivtTCF.
Topic Name:      ivtT.
JMS Message Type:      TextMessage.
Durable Subscriber Name (Optional):      .
Message Selector (Optional):      .
Client ID (Optional):      .
Name      Flow name      Type      Max size      Formatting
rawData.      rawData.      String      40000      (none).
5. I have a subscribe plan configured in to enterprise Link which has a EMSReceiever and a grid to display the messages
6. I have the "run forever" flag checked in the Receiver and go a head and post a message in the Queue configured in the server.
7. The plan does not display any messages in the grid.
All configuration on the MQ Server and Client side are proper but BAM EL Plan is not displaying the data in the grid.
Have also had turned on DEBUG on the servers and restarted BAM, they don't seem to throw any errors.
Kindly advice, what could be wrong in the Plan or EMS configuration which is causing this.
Thanks & regards,
Jai.

Is this working for you? What errors do you get in the logs (bam, EL)?

XI to IBM Websphere Default JMS Provider with JNDI

Hello everybody!
We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
We have the following versions installed:
    SAP XI: 7.0 SP8 , Sun JDK 1.4.2
    IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.
For connecting, the following JMS-provider settings were used at IBM WebSphere side:
   JMS Providers: Default Messaging Provider
   Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
   Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
<b>Variant 1.</b>
    Adapter type: JMS
    Type: Receiver
    JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
    JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory
    JNDI Lookup Name of JMS Queue: jms/Queue
    Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
    JNDI Server Address: iiop://WEBSPHERE.HOST:2809/
    As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
    "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
<b>Variant 2</b>
    The same settings as in Variant 1 above, were used and additionally the following settings were done:
    - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
    - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
    - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
    As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
   "No adapter registered for this channel"
We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

IBM WEBSPHERE EXCEPTION

I'm getting the following exception while starting the IBM websphere server administrator's console:
Exception:
Namecom.ibm.ejs.sm.exception.AttributeNotSetException: Name
     at com.ibm.ejs.sm.beans.Attributes.getGeneric(Compiled Code)
     at com.ibm.ejs.sm.beans.Attributes.getName(Attributes.java:185)
     at com.ibm.ejs.sm.client.TypeInstance.<init>(TypeInstance.java:132)
     at com.ibm.ejs.sm.client.InstanceTree.insert(InstanceTree.java:658)
     at com.ibm.ejs.sm.client.InstanceTree.insert(InstanceTree.java:767)
     at com.ibm.ejs.sm.client.InstanceTree.addInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree$Loader.run(InstanceTree.java:1308)
com.ibm.ejs.sm.client.ClientException: Exception occurred
     at com.ibm.ejs.sm.client.ExceptionManager.handleExc(Compiled Code)
     at com.ibm.ejs.sm.client.TypeInstance.<init>(TypeInstance.java:136)
     at com.ibm.ejs.sm.client.InstanceTree.insert(InstanceTree.java:658)
     at com.ibm.ejs.sm.client.InstanceTree.insert(InstanceTree.java:767)
     at com.ibm.ejs.sm.client.InstanceTree.addInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree$Loader.run(InstanceTree.java:1308)
Exception:org.omg.CORBA.TRANSACTION_ROLLEDBACK:   minor code: 0 completed: No
com.ibm.ejs.sm.client.ClientException: getAttribute Failure. Attributes may be invalid.
     at com.ibm.ejs.sm.client.AttributeCollector.getAttributes(AttributeCollector.java:443)
     at com.ibm.ejs.sm.client.TypeInstance.<init>(TypeInstance.java:131)
     at com.ibm.ejs.sm.client.InstanceTree.insert(InstanceTree.java:658)
     at com.ibm.ejs.sm.client.InstanceTree.insert(InstanceTree.java:767)
     at com.ibm.ejs.sm.client.InstanceTree.addInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree.addAllInstances(Compiled Code)
     at com.ibm.ejs.sm.client.InstanceTree$Loader.run(InstanceTree.java:1308)

No idea... better post this in WebSphere forum.

IBM WebSphere Studio and Apache Tomcat Server

Hi all of you , my question is Can I add Apache TomCat web server to my IBM WebSphere Dev. Studio 5.0. ? If it's so, How can I do ? If you hurry up,I'll be really appreciated.
Thanks in advance.
Ergin

When I do an add server from WSAD 5.1.2 I see the option of Tomcat 3.2, 4.0 & 4.1. I don't know if 5.0 has them.
You can always run tomcat outside of WSAD and point it at your webapp root in WSAD. Doesn't provide all the nice integration but works OK.
-- Frank

Webdynpro ABAP applications visible in IBM Websphere

Hi,
I have a requirement wherein I have to make Webdynpro ABAP applications visible in IBM Websphere.
Can someone help me out with the steps involved in this.Iam using EHP4.
Regards,
Anil

Hi,
Do you want to access/run the WD application from IBM Webspehere.
As every WDA is associated with an URL, you can make use of this URL in Webspehere and test it out.
Regards,
Lekha.

Xmlparserv2.jar cause IBM WebSphere v5.1 down.

Anyone knows:
I have a j2ee project based on IBM WebSphere v5.1 + Oracle DB 10g(XMLDB included).There's a big trouble bother me.
My project used Oracle xml implemention,such as DOM parser included in xmlparserv2.jar.and when i deploy my project to WAS(WebSphere Application Server),it throws errors and can not startup normally.it's sounds that WAS cann't determine which xml implemention it should choose:
Error message below:
==============================================
*** å¯å¨æå¡å¨ ***
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O java.net.MalformedURLException: unknown protocol: f
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java(Compiled Code))
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java(Compiled Code))
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java:450)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:214)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:177)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.xml.BaseFactory.load(BaseFactory.java:191)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.xml.BaseFactory.load(BaseFactory.java:173)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.loadVersionInfo(WASProduct.java:1876)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.getVersionInfo(WASProduct.java:1829)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.getPlatform(WASProduct.java:845)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.TraceImpl.initialize(TraceImpl.java:59)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
[05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
[05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
[05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
[05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
[05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at java.lang.reflect.Method.invoke(Method.java:386)
[05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
************ Start Display Current Environment ************
Host Operating System is Windows XP, version 5.1
Java version = J2RE 1.4.1 IBM Windows 32 build cn1411-20031011 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51
user.install.root = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51
Java Home = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre
ws.ext.dirs = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/lib;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/classes;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/classes;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/ext;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/web/help;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;F:\document\musicool\CVS\libs\xsdbeans.jar;F:/Program_Files/IBM/SQLLIB/java/db2java.zip;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.1/runtime/worf.jar
Classpath = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/properties;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/properties;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/bootstrap.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/j2ee.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/lmproxy.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/urlprotocols.jar;F:\document\musicool\CVS\libs\workflow.jar;F:\document\musicool\CVS\libs\DBClient.jar;F:\document\musicool\CVS\libs\log4j-1.2.8.jar;F:\document\musicool\CVS\libs\log.jar;F:\document\musicool\CVS\libs\utility.jar;F:\document\musicool\CVS\libs\webwork.jar;F:\document\musicool\CVS\libs\xdb.jar;F:\Oracle\product\10.1.0\Client_1\lib\xsu12.jar;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1/runtime/wteServers.jar;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1/runtime/wasToolsCommon.jar
Java Library path = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/jre/bin;F:\Program_Files\IBM\WebSphere_Studio\eclipse\jre\bin;.;F:\Program_Files\IBM\WebSphere_Studio\eclipse\jre\bin;F:\eclipse\301\bpelz_install\bin;f:\Oracle\product\10.1.0\Client_1\bin;f:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin\client;f:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;f:\Program_Files\IBM\WebSphere_Studio\extras\bin;f:\Program_Files\IBM\WebSphere_Studio\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre\bin\classic;f:\Program_Files\UltraEdit;f:\Program_Files\SecureCRT;F:\PROGRA~1\IBM\SQLLIB\BIN;F:\PROGRA~1\IBM\SQLLIB\FUNCTION;F:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL;C:\Program Files\Common Files\Ulead Systems\MPEG;;;;;f:\Program_Files\Real\Helix_Producer_Plus;F:\Program_Files\Rational\common;F:\eclipse\301\bpelz_install\bin;f:\Program_Files\UltraEdit
************* End Display Current Environment *************
[05-5-2 12:06:49:938 CST] 3d455614 ManagerAdmin I TRAS0017I: å¯å¨è·è¸ªç¶ææ¯ *=all=disabledã
[05-5-2 12:06:50:609 CST] 3d455614 AdminInitiali A ADMN0015I: AdminService åå§å
[05-5-2 12:06:50:656 CST] 3d455614 MBeanDescript W ADMN0001W: æ æ³è¯æ³åæ MBean æè¿°ç¬¦æä»¶ com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: æ æ³è¯æ³åæ MBean æè¿°ç¬¦æä»¶ com/ibm/ws/management/descriptor/xml/JVM.xmlã
at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
ã
[05-5-2 12:06:50:688 CST] 3d455614 WsServer E WSVR0003E: æå¡å¨ server1 æ æ³å¯å¨
com.ibm.ws.exception.ConfigurationError: Problem initializing AdminImpl:
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:413)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Caused by: com.ibm.ws.exception.ConfigurationWarning: Problem registering JVM MBean.
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:283)
... 11 more
Caused by: com.ibm.websphere.management.exception.AdminException: ADMN0005E: æ æ³æ¿æ´» MBeanï¼ç±»å JVMãåä½è [email protected]c1619ãéç½®æ è¯ JVM åæè¿°ç¬¦ nullã
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
... 11 more
Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: æ æ³è¯æ³åæ MBean æè¿°ç¬¦æä»¶ com/ibm/ws/management/descriptor/xml/JVM.xmlã
at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
... 13 more
---- Begin backtrace for nested exception
com.ibm.ws.exception.ConfigurationWarning: Problem registering JVM MBean.
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:283)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Caused by: com.ibm.websphere.management.exception.AdminException: ADMN0005E: æ æ³æ¿æ´» MBeanï¼ç±»å JVMãåä½è [email protected]c1619ãéç½®æ è¯ JVM åæè¿°ç¬¦ nullã
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
... 11 more
Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: æ æ³è¯æ³åæ MBean æè¿°ç¬¦æä»¶ com/ibm/ws/management/descriptor/xml/JVM.xmlã
at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
... 13 more
---- Begin backtrace for nested exception
com.ibm.websphere.management.exception.AdminException: ADMN0005E: æ æ³æ¿æ´» MBeanï¼ç±»å JVMãåä½è [email protected]c1619ãéç½®æ è¯ JVM åæè¿°ç¬¦ nullã
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: æ æ³è¯æ³åæ MBean æè¿°ç¬¦æä»¶ com/ibm/ws/management/descriptor/xml/JVM.xmlã
at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
... 13 more
---- Begin backtrace for nested exception
com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: æ æ³è¯æ³åæ MBean æè¿°ç¬¦æä»¶ com/ibm/ws/management/descriptor/xml/JVM.xmlã
at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
[05-5-2 12:06:50:703 CST] 3d455614 WsServer E WSVR0009E: å¯å¨æé´åçéè¯¯
=================================
Best Regard.
Musicool

I had this issue too. I removed all non-Oracle classes (javax, org.w3c) from the jar file and things then worked as expected. Basically, these javax and w3c files were duplicating versions already existing in the WPS classpath (I presume) and were causing the failure.
Hope this helps.
-Tim

EES running in IBM Websphere

Similar Messages

Maybe you are looking for