WSO2 support on IBM Power system - aix

Is wso2 platform supported on AIX or other operating systems on Power systems?
This particulary applies to the support of the IBM JDK. I'm getting different errors which seem to be targeted at the IBM JDK. Is the IBM JDK supported?
Thanks,
There are still errors i'm getting. Latest one is in BPS 2.1.2 :
[2012-05-01 10:14:27,521] INFO - Database - Using DAO Connection
Factory class org.apache.ode.dao.jpa.BPELDAOConnectionFactoryImpl.
Exception in thread "Attachment 33002"
java.lang.UnsupportedOperationException: cannot get the capability,
performing dispose of the retransforming environment
at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl(Native
Method)
at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary(Attachment.java:252)
at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent(Attachment.java:230)
at com.ibm.tools.attach.javaSE.Attachment.doCommand(Attachment.java:140)
at com.ibm.tools.attach.javaSE.Attachment.run(Attachment.java:101)
And another post about esb with the thrift connection also gives errors on security implementation differences in oracle/ibm

WSO2 platform is tested on AIX. And also supports and tested with IBM jdk.

Related

How to monitor JVM usages for Websphere Applications?

I'm trying to monitor JVM usages in IBM Websphere Server. Normally I use jstat tool from the JDK but since that's not available with IBM WAS, is there any other tool available for the same?
WAS uses IBM's J9 JVM under the hood. So, some of the HotSpot JVM's debugging tool will not work with it. WAS exposes all details using Performance Monitoring Infrastucture(PMI). You should be able to get lots of metrics using it. You need to enable this feature in order to get metrics.

How can I trace Operational Analytics in MobileFirst Platform 6.3 to determine why data is being lost?

I'm working in a scenario where we are trying to get Operational Analytics working within an MFP 6.3 environment. There is a MobileFirst client application (hybrid, if it matters), a MFP 6.3 server, and an Operational Analytics server (the system is for dev/test only, so is lightly loaded, and no uptime/performance concerns exist).
Currently, we are seeing intermittent problems, where data sometimes appears in the Operational Analytics console on adapter invocations etc., and then for some periods (sometimes days) go past with no data showing up.
How can we trace or log the behaviour of the Operational Analytics engine? As I understand it, there is a queueing mechanism on the MFP 6.3 server (currently wl.analytics.queue=1 and wl.analytics.queue.size=0) for forwarding data from the client to the OA server. Is there a way to see what messages are put or got from this queue?
This environment uses WAS ND.
From an IBM engineer:
IBM MobileFirst Platform 6.3 does not provide traceability options in
the MFP Operational Analytics component. This was greatly improved in
MFP 7.0 in the log output from the various analytics components,
including the queues and sender embedded in MFP server and the
receiver, processors, and storage in the Analytics server, and more is
planned for the future.
If deemed required in MFP 6.3 consider opening a PMR (support ticket). Or upgrade to MFP 7.0 if possible.

IBM Worklight 6.2 - decode proguard obfuscated trace

Is it possible to use IBM Worklight Log and Analytics feature to upload and decode obfuscated crash reports (e.g. ProGuard or the iOS alternative) to the Worklight Server?
Android ProGuard is currently not supported in Worklight (5.x - 6.2.0.x) applications, so in that respect this option is not available regardless. I am not familiar with an iOS equivalent to ProGuard.
AFAIK the Worklight Operational Analytics platform does not provide the ability to decode uploaded logs. You can however control what exactly you'd like to upload.

Worklight + WebSphere eXtreme Scale

I tried the integration of these products based on this article and I hit the same problem already documented in the article.
"invocation of javascript function 'getRSSFeeds' has failed: Could not initialize class com.ibm.websphere.objectgrid.ObjectGridManagerFactory
FWLSE0101E: Caused by: [project ExtremeScaleInWorklight]java.lang.NoClassDefFoundError: Could not initialize class com.ibm.websphere.objectgrid.ObjectGridManagerFactory"
It seems that it is caused by a Java class collision of log4j.
My solution was to create a separate Liberty server and install the WXS client for Liberty. This solved the problem, but then I cannot use the WL Development Server anymore which turns the development less efficient.
What is the best way to develop this kind of solution?
I have seen this integration of products on several slides, but I can't find an official guide on how to achieve this. Is there any?
Have You tries to get the IBM WebSphere eXtremeSCale Liberty profile developer tools 8.6 also installed in your WL Development Server ?
SO WXS has two components Client ( libraries) and Serer side components. They can be housed in the same JVM -- for tests, in production this does not really make sense. Serer side hosts storing of objects and enforcing the 'grid management' policies that you may employ using the xml confg files.
perhaps you can use IBM WebSphere eXtremeSCale Liberty profile developer tools 8.6 also installed in your WL Development Server and include then in the classpath.

WebSphere JVM MXBeans

When using Oracle JVM, we can obtain a large amount of useful JVM data using the provided MXBeans like GarbageCollectorMXBean, MemoryMXBean etc. Are the same MXBeans available in case of a WebSphere JVM ?
Thanks in advance.
Yes, they are available also on WebSphere, but it is somewhat tricky to access them remotely. I just completed a documentation that explains what you need to know to access these MXBeans:
http://code.google.com/p/xm4was/wiki/WebSphereJmx
The XM4WAS project also provides some tools to make that easier. The following document describes how to use them to set up VisualVM to monitor a WebSphere JVM:
http://code.google.com/p/xm4was/wiki/VisualVMHowTo
Yes, if it is java 1.5+.
WAS also has PMI you should look into.